Professional Documents
Culture Documents
11i Managing Large Org Structures
11i Managing Large Org Structures
Table of Contents
INTRODUCTION ORGANIZATION HIERARCHIES USING ORGANIZATION HIERARCHIES COPYING ORGANIZATION SETUP DATA SUMMARY OF LARGE ORGANIZATION FEATURES ITEM ORGANIZATION ASSIGNMENT PROGRAM ITEM ATTRIBUTE COPY INVENTORY POSITION VIEW AND EXPORT OPEN PERIODS PROGRAM CLOSE PERIODS PROGRAM GLOBAL TRANSACTION PURGE INVENTORY TRANSACTION OPEN INTERFACE COMMON BOMS ACROSS MULTIPLE ORGANIZATIONS ECO AUTOIMPLEMENT ITEM WHERE USED INQUIRY ECO CHANGES BOM DELETE GROUPS SETTING UP ORGANIZATION HIERARCHIES USING THE HIERARCHIES FORM EXAMPLES RELATED DOCUMENTS
3 3 4 4 5 5 5 6 8 8 9 9 10 10 11 12 13 14 14 15 17
-2-
Introduction
Release 11i includes new features aimed at simplifying the setup and maintenance of manufacturing and distribution applications. These features allow you to efficiently manage upwards of 1,000 inventory organizations and related structures in a single Applications instance. Many of these features are useful even if you have a simple organization structure. This White Paper provides an overview of these features. Supplemental information about the use of Organization Hierarchies is offered at the end of this paper. If you want to learn more about how to use the Copy Organization feature for large organization structures, a separate Implementation Manual is available.
Organization Hierarchies
By establishing Organization Hierarchies for your inventory organizations, you can group together organizations according to your needs and perform operations across all organizations at any level in a given hierarchy.
A1 Headquarters
P1 Plant 1
P2 Plant 2
-3-
Bills Routings Items Categories Subinventories Shipping Networks Inventory Parameters WIP Parameters BOM Parameters
-4-
assign individual items to multiple organizations assign a range of items or item categories to a single organization assign a range of items or categories to many organizations
view and verify that a given item or items have been set up correctly across organizations copy any organization-level item attributes from one model item setup to other organizations that use the item copy item attributes from one item to another within one organization
-5-
-6-
-7-
-8-
-9-
ECO AutoImplement
ECO Autoimplement has been enhanced for large organization structures. Prior to this enhancement, the ECO Autoimplement feature could only implement all the ECOs in the current organization which had been scheduled for implementation. Now the user can implement all ECOs for multiple organizations by naming a hierarchy to which the current organization belongs.
-10-
-11-
ECO Changes
The Create ECO form has been enhanced to allow ECOs to be performed across organization hierarchies. It is now possible to create ECOs, ECO Revisions, Revised Items, Revised Components, Reference Designators and Substitute Components for the current organization or all organizations in the current organization hierarchy according to selections made in the ECO form. You can also schedule revised items for implementation across organizations in a hierarchy using this form.
-12-
-13-
In order to create a hierarchy, you must: Enter a name of the hierarchy you wish to establish. Save your work. Enter a From date. Save your work. In the Subordinates block, choose your top level organization from the list of values. Save your work. Click the down arrow, and the top level organization will appear in the Organization Name field above. You can enter all organizations that exist at the second level in the hierarchy here. Clicking the down arrow will move you to a third level in the hierarchy. Other tips for using the hierarchies form:
-14-
The remainder of this section addresses the use of hierarchies that you create in this form.
Examples
Hierarchy: West Region
P1 Plant 1
Figure 2. Single Organization Hierarchy Figure 2 shows a sample hierarchy created for XYZ Company. Each store in XYZs Western region sells products that originate from Plant 1. Further, there are two Distribution Centers in the West region, DC1 (serving the Northwest) and DC2 (serving the Southwest). The above hierarchy was created to perform tasks that correspond with this organization structure.
Suppose that all the stores may be assigned only items that are produced in Plant 1. XYZ could use this hierarchy to ensure that Item Assignment is performed for this business case, using the Item Organization Assignment concurrent program. Assuming that certain organization level item attributes are determined by the Distribution Center to which a store belongs, the user whose organization context is set to DC1 could name West Region as the hierarchy in the Item Attribute Copy form, and ensure item consistency among all stores belonging to Distribution Center 1.
-15-
P1 Plant 1
P2 Plant 2
In Figure 3, a total of three Hierarchies have been created for XYZ Company. These are East Region, West Region, and Main Hierarchy. Assume that the Organizations in the East Region use a separate Item Master Organization from those in the West Region.
For programs requiring a shared item master organization, if you choose A1 Headquarters as your Hierarchy Origin, you will not be able to select Main Hierarchy from the Hierarchy LOV. Main Hierarchy is not an allowable hierarchy, because its use in these programs would result in errors. Features with this built-in restriction include Item Attribute Copy, Inventory Position View/ Export, Item Organization Assignment, and all Bills of Material features. Assume that organizations in the East Region use a separate Set of Books from the West Region. If you choose A1 Headquarters as your Hierarchy Origin, you will not be able to select Main Hierarchy from the Hierarchy LOV for programs that require that all subordinate organizations share the same Set of Books. This validation is performed for Open and Close Period Status.
-16-
Feature Inventory Transaction Open Interface Global Transaction Purge Item Organization Assignment Inventory Position View/Export Open Period Status Control Close Period Status Control Item Attribute Copy Common BOM Item Where-Used Inquiry Autoimplement ECOs BOM Delete Groups ECO change
Hierarchy Optional Required Required Required Required Required Required Optional Optional Optional Optional Optional
Hierarchy Constraint Value No Restriction No Restriction Same Item Master Organization Same Item Master Organization Same GL Calendar, Chart of Accounts Same GL Calendar, Chart of Accounts Same Item Master Organization Same Item Master Organization Same Item Master Organization Same Item Master Organization Same Item Master Organization Same Item Master Organization
Related Documents
For more information, please see the following:
Oracle Inventory User Guide, Release 11i Oracle Bills of Material User Guide, Release 11i Oracle Human Resources User Guide, Release 11i Copy Organization Setups Implementation Guide
-17-