Growing Pains Adding MutiOrg Manufacturing onto an Existing Single Org Financial Implementation

1
Growing Pains - Adding Muti-Org Manufacturing
onto an Existing Single Org Financial
Implementation
DARC Consulting Joe Tillmann -SR. Principle
Consultant
2
Growing Pains

• Overview.
• DARC was asked to partner with a leading Chicago
  manufacturing organization to implement and
  integrate the entire oracle ERP suite into their
  existing oracle financials install.
• Client led implementation was started in march of
  2001.

3
Growing Pains

• Background
• Originally implemented G/L and accounts
  receivable in 1995
• Added purchasing, A/P and shared install of
  inventory in 1997
• Selected oracle as a provider for their
  manufacturing and order management applications
  in 2001
• Upgraded to release 11.5.6 and converted to
  multi-org on 1/1/2002
• Added financials (GL, AP, FA, and purchasing) for
  their Canadian company 4/1/2002
• Entire ERP go live for Canada scheduled for
  4/28/2002

4
Growing Pains Approach

• Review existing setups for original Financials
  install
• Gather requirements for the future Manufacturing
  / ERP implementation
• Form a Task force to
• Compare existing setups to requirements for
  Manufacturing / ERP
• Identify required changes to existing setup
• Develop a plan to modify existing setups and
  source data without impacting ongoing business
• Execute Cutover plan

5
Growing Pains Existing Setups

• Organization setup purchasing
• Original setup consisted of one inventory master
  organization (EMO) and one inventory organization
  (CHI)
• Item validation organization for the original
  financial install is the master inventory
  organization (EMO)
• Supplier notes are attached to the supplier header

6
Growing Pains Existing Setups

• Item setups attributes
• Reviewed existing attribute controls to determine
  which are controlled at the master and child
  organization
• Standard costing was setup at the master
  organization
• Standard costs were only on items in the master
  organization

7
Growing Pains Existing Setups

• Item Setups Categories
• Two category structures and category sets were
  setup one used for Purchasing and one for
  Inventory
• Inventory was used as the default category set
  for everything except purchasing
• Categories were maintained only in the Master
  Organization (EMO)

8
Growing Pains Existing Setups

• Item Setups Attachments
• Item attachments exist only in the master
  organization (EMO)
• Majority of the attachments have a category of
  To Supplier

9
Growing Pains - Requirements

• Organizations
• New Operating Units and inventory organizations
  are required for both the US and Canada
• The existing inventory master org (EMO) will be
  the master org for all new inventory
  organizations
• A phased implementation will happen
• Financial Implementation in Canada will require a
  new operating unit and inventory organization.
  Inventory Org will be set up to facilitate
  receiving expense Pos only.
• Manufacturing implementation in Canada full
  install of inventory with items and
  subinventories
• Manufacturing implementation in the US new set
  of books, operating unit, and inventory
  organizations are required

10
Growing Pains - Requirements

• Purchasing
• Ability to add attachments to supplier sites
• Ability to have item attachments that differ by
  operating unit
• Attachments are only visible and print in the
  appropriate operating unit that they are added
• Supplier Headers will only contain information
  which is not operating unit specific
• Purchasing categories will use the same structure
  but may have different values in the different
  operating units

11
Growing Pains - Requirements

• Items Attributes / Templates
• Costs will be controlled at the organization
  level
• Master Org (EMO) attributes should be set at the
  Oracle defaults if they are not common in all
  inventory organizations
• Control level for all attributes have been
  determined and must be set appropriately
• Organization specific templates are required and
  are based upon Oracle defaults being present in
  the master org

12
Growing Pains - Requirements

• Items Categories
• Cost, Order Management, and Planning require
  their own unique default category sets
• Category Set values need to be able to differ by
  organization
• Item - Attachments
• Item attachments must have the ability to differ
  by inventory organization

13
Growing Pains Task Force Setup Issues

• Existing Purchasing Item validation organization
  needs to be changed from the master organization
  to the existing inventory organization
• Purchasing category values have only been
  maintained at the existing item validation org
  and therefore differ between existing item
  validation org (EMO) and the child organization
  (CHI)

14
Growing Pains Task Force Setup Issues

• Item attributes have only been maintained at the
  existing item validation org and therefore differ
  between existing item validation org (EMO) and
  the child organization (CHI)
• Item Attribute values for the master org (EMO)
  are not the same as the original Oracle Defaults
• Default Value sets need to be changed from
  Inventory to newly created value sets for Cost,
  Order Management and Planning

15
Growing Pains Task Force Setup Issues

• Receiving cannot occur in an inventory
  organization where frozen costs do not exist,
  therefore frozen costs must be assigned to the
  child inventory org (CHI)
• Supplier Header attachments will be visible and
  print in all operating units. Attachments must be
  moved from the supplier header to the supplier
  site
• Standard Oracle does not have supplier site
  attachments enabled

16
Growing Pains Task Force Setup Issues

• Inventory item attachments need to be moved from
  the master org (EMO) to the new purchasing item
  validation org (CHI)
• Custom PO report needs modification to print
  supplier site notes

17
Growing Pains Task Force Migration Plan

• The task force reviewed the setup issues to
  determine the the steps required to prepare the
  system for use.
• Each step was reviewed to determine the in what
  sequence needed to occur the steps and if a
  system outage was required for the step to be
  successful

18
Growing Pains Task Force Migration Plan

• Correct existing Purchase Category in the child
  (CHI) org outage required
• Extract existing values from the master org (EMO)
• Use open item interface to first delete the
  values currently assigned in the child org
• Use the item interface to add values extracted
  from the master org (EMO) to the child org

19
Growing Pains Task Force Migration Plan

• Correct child org (CHI) item attribute values
  outage required
• Extracted existing attribute values that were org
  controlled from the master org (EMO)
• Used the open item interface to update the child
  (CHI) org attributes with values from the master
  org (EMO)

20
Growing Pains Task Force Migration Plan

• Correct child org (CHI) frozen costs outage
  required
• Update attribute control for cost from master to
  org
• Use standard functionality to copy costs across
  organizations from master org (EMO) frozen to
  child (CHI) pending
• Use standard functionality to update frozen cost
  in the child org (CHI) from pending

21
Growing Pains Task Force Migration Plan

• Assign item attachments at child org (CHI) and
  eliminate attachments at master org (EMO)
  outage required
• Create SQL script to identify item attachments
  and owning org
• Create SQL script to update organization id from
  master org (EMO) to the child org (CHI) in the
  attachments table

22
Growing Pains Task Force Migration Plan

• Enable supplier site attachments and assign
  supplier header attachments to the the supplier
  site outage required
• Use the Application developer responsibility to
  enable supplier site attachments
• Use an SQL query to identify supplier header
  attachments
• Manually update supplier sites with these
  attachments (volume was less than 100)
• Manually disable supplier header attachments

23
Growing Pains Task Force Migration Plan

• Modify custom PO print program to print supplier
  site attachments
• Update purchasing item validation org in original
  financials setup outage required
• Use purchasing superuser responsibility to update
  purchasing item validation org in the financial
  options

24
Growing Pains Task Force Migration Plan

• Create new cost, order management and planning
  category structures and sets
• Assign values to items for each of these category
  sets
• Update default category sets for cost, order
  management and planning outage required
• Based on requirements update item attribute
  controls

25
Growing Pains Task Force Migration Plan

• Update attribute values in the master org (EMO)
  to Oracle defaults
• Use open item interface to update master
  attributes

26
Growing Pains Conclusion

• Test your migration plan to determine how long of
  an outage may be required to execute the plan
  this may require more than test to get the timing
  down
• Implement your plan

27
Growing Pains Open Discussion

• Questions ?