Jun 27, 2008

What is Multi Org?

Q. What is Multi Org Architecture?
A. The Multiorg Architecture is meant to allow multiple companies
or subsidiaries to store their records within a single database.
The multiple Organization architecture allows this by partitioning data
through views in the APPS schema. Multiorg also allows you to maintain
multiple sets of books. Implementation of multiorg generally includes
defining more than one Business Group.

Q. How can I know if I am using Multi Org?
A. Run the SQL statement:
select multi_org_flag
from fnd_product_groups;
The result 'Y' means your database is setup for multiorg.

Q. What are the relationships I can define in a multi org environment?
A. You define the relationships among inventory organizations,
operating units, legal entities, Business Groups, and sets of books to
create a multilevel company structure:
. Business Groups separate major segments of a business. Each can have
it's own set of books. Each Group will also have a structure of other
organizations classifications assigned to it.
· Legal Entities post to a Set of Books
· Operating Units are part of a Legal Entity
· Inventory Organizations are part of an Operating Unit
· Inventory Organizations define and maintain items used by other
manufacturing modules (Order Entry, Purchasing, MRP, etc.). They also
collect and pass data to the Financials modules.

Q. I want to Setup Additional Organizations, do I have to setup Multiorg?
A. No, you do not need to setup multiorg. You do not have to be
multi-org to have multiple organizations only if you intend to have multiple
sets of books.

Q. Is there any documentation on how to setup an organization?
A. · Refer to "Oracle Manufacturing Implementation Manual" part#A50765.
· Refer to "Multiple Organizations in Oracle Applications"
part#A58478 for Release 11 and part#50771 for Release 10.
· Also refer to note 76440.1 for Organization setup steps.

Q. When my organization hierarchy changes, can I move an organization from
one set of books or legal entity to another?
A. No, you should not try to move an organization from one set of books
or legal entity to another because your data may not be valid for the
new set of books or legal entity. Instead, you should disable the old
organization and create a new organization for the appropriate set of
books or legal entity. The new organization will contain your new data,
and the disabled organization will act as an "old" or "history" entity
that stores past transactions.

Q. How can I setup a child org to be its own costing organization?
A. Steps:
· Change the attribute control for "default category set" to organization level
· Change the attribute control for "costing enabled" to organization level
· Change the attribute control for "inventory asset value" to organization control
Then you can make a child organization it's own costing organization by
entering the organization name in the column labeled "Costing Organization"

Q. How can I define organization restriction?
A. Use the Organization Access form (INVSDORA) to restrict the list of organizations
displayed for each responsibility level.
Refer to Oracle Inventory User's Guide for steps and important notes.
*WARNING* If you populate any rows in this form, you MUST populate a row for
EACH responsibility that you wish to have access to that Organization.

Q. What responsibility do I need to use to setup organization?
A. Use the General Ledger responsibility to define the Set of Books
Use the Inventory Responsibility to define Organizations and other related
information such as Inventory Key Flexfields, Locations, Workday calendar,
other Organization Classifications, and other inventory information.

Q. What are the main profile options relating to Organization setup and
what are they used for?
A. · HR:User Type = HR User
This is necessary to allow the Inventory responsibility to complete
the organization setup. Setting the profile to a value of 'User' as
opposed to 'Payroll & User' will restrict the Inventory user from
accessing any Payroll information if Oracle Payroll is installed.
· HR: Business Group = {the users Business Group name}
This points the responsibility to the appropriate Business Group.
When multiple Business Groups are defined, you must associate
each responsibility with one and only one Business Group.
A responsibility can not see organization data from more than
one Business Group.
· MO: Operating Unit = {the users Operating Unit name}
Used primarily in a multiorg environment.
This points the responsibility to the appropriate Operating Unit.
Set the site level to the desired default operating unit.
If there is more than 1 Operating Unit Defined,
this profile option must be set at the responsibility level
for each responsibility.

No comments:

OraApps Search

Custom Search

Search This Blog