Create an ou in EBS

Http://blog.csdn.net/kevingao/archive/2010/09/11/5877092.aspx

Create an ou in EBS
1. Establish ou organization and associate sob, le
2. Run concurrency under the system administrator: Replicate seed date
3. Create Po responsibilities, set MO: Default operating unit, and authorize
4. Enter new po responsibilities and set financial options
5. Enter the new po responsibilities and set the purchasing options

Run the replicate seed data request followed by steps:

Navigate to system administration responsibility, requests-> Run-> single request, OK, select replicate seed data-> select the organization which is new created as parameter-> submit
* This will replicate the seed data in your database. You need to do this everytime you make a new organization.

This program points to: ad_morg.replicate_seed_data (x_org_id, null, null );
In addition, there is only one org_id input parameter in the request, which is actually ou, and the other two are left blank, which indicates copying all the basic data at the ou level under this ou.
The seed data replication program works in two modes:
• Single organization: This mode applies when the seed data replication program is executed within the context of a particle operating unit (or org_id ).
• All organizations: This mode applies when the seed data replication program is executed without an operating unit context.

The actual copied table points to the load_table_list method. From this header, we can see that the basic data at the ou layers of AR, AP, Ce,... are copied.

The essential purpose is to copy data in ap_invoices to ap_invoices_all, or to some language table headers.

This request has two functions:
(1) it must be used during multi-organization conversion.
(2) It doesn't matter if you run it normally, but there are too many Oracle bugs. You are not recommended to run it manually. We recommend that you run it under ORACLE support when you discover the problem. FRM-40735 this is often to run this thing.

By the way, it will certainly increase some space, but it is insignificant.

Multi-Organizational Structure

An important selling point of Oracle EBS is its multi-organizational structure. The Oracle EBS documentation shows a tree chart:

Business Group (BG)

|

HR Organization

|

Legal Entity (LE)

|

Operating unit (OU)

|

Inventory Organization

 

 

1. business Group: it represents the highest level of organizational structure, which separates Human Resource Information. for example, when you query a person, it lists all the members allocated to the corresponding business group, and the organization you belong to is only part of the business group. this may lead to a misunderstanding: A company can only have one business group, but there may actually be multiple, but the information cannot be shared between business groups.

2. Book: it cannot be called an organization. It is more like a hierarchy or nature in an organization. A business group may have one or more books.

3. Legal entities: the types of legal entities give organization tax codes and other legal-related attributes. A set of books can be allocated to multiple legal entities.

4. Balanced entity: a balanced entity is a segment in the account structure, that is, a balanced entity. It represents your account entity when preparing the financial statement.

5. operation Unit: if an organization is applied to the cash management, order management, transportation, receivables, payables, and procurement modules, it is an operation unit. it may be a sales center, a branch, or a department. for these applications, EBS separates business information according to legal entities. Each user can only access the information of his or her own operation unit. A legal entity can have one or more operation units.

6. inventory organization: An organization is an inventory organization when it uses inventory items (such as receiving and transferring items) or is responsible for manufacturing and distributing products. it may be a manufacturing plant, warehouse, distribution center or sales department. when the following modules are used, EBS divides the business information according to the inventory organization: Oracle inventory, bills of material, engineering, work in process, master scheduling/MRP, capacity, and purchasing processing functions. when you log on to these modules, Oracle EBS will prompt you to select an inventory organization. similarly, one or more inventory organizations can be created under an operating unit.

7. human Resources Organization: it reflects the basic work structure of a company. only when an organizational unit is a human resource organization can you assign people to it. A business group can contain one or more human resources organizations.

8. Asset organization: asset organization attributes enable the Organization to perform asset-related functions. Oracle assets can be used only when an organization belongs to an asset organization.

Note that an EBS organization cannot belong to only one type. for example, an organization is an operational unit. If Oracle inventory is used in this organization, it is also an inventory organization. therefore, the organization type represents an attribute of the organization, rather than simply classifying the organization.

Oracle organization structure and security
The organizational structure and security of Oracle are closely related, for example, how to shield access to information between different sobs and how to shield information between different ou. these are mainly implemented through responsiblity.

Generally, after creating responsiblity, We need to attach three profiles to the responsibility layer:

1. GL set of book name. This profile is used to block books. If your company uses multiple books, use it to block books for liability, then attach the responsibility to the user. If your enterprise only uses a book, you can set it at the SIT layer. The general practice is to set one at the SIT layer, and then set up a special responsibility.

2. HR: user type. this is actually useful after you have installed the HRMS system. It is used to shield the data access permissions of the payroll system and general HR users. it has three options: HR users, including payroll management system HR users and payroll management system users. generally, we select HR users on the SIT layer, because only the Oracle payroll is installed and the HR security function is used.

3. MO: operating unit. this is to block ou. It is very useful if your company has multiple ou. this value must be set. (you do not need to set inv because ou is used to shield om, AP, and Ar information)

After the above profiles are created, the system can shield ou-level data. If you want to shield inventoty-level data, you can set the inventory Org.

In this way, Oracle does not change the organizational structure. It is the responsibility to bridge the restrictions on user access for data of different organizational types.

Copying inventory organizations
You can create and update a large set of inventory organizations and their business
Entities, such as subinventories, items, bills of material, and resources. These entities
Can be copied and customized as part of an inventory organization copy. This aids in
The management of inventory organizational setup, which is mandatory for the use
Inventory, costing, bills of material and work in process. This feature is useful
Companies that have a large number of inventory organizations.
You can copy a Source Inventory organization's parameters, ults, and settings, in
Single operation, to as your new organizations as you wish for the following setup
Entities:
• Bills of material
• Routings
• Items
• Categories
• Subinventories
• Shipping networks
• Inventory parameters
• WIP Parameters
• BOM Parameters
Organization mass copy is a two-step process. In order to copy Source Inventory
Organization structures, you must first set up entity APIs to load interface tables and
Then run the copy organization concurrent program to export and import the setup
Data.

When copying an inventory organization, the number of items with zero inventory Quantity cannot be specified for the new organization. When the item number with a non-zero inventory quantity is assigned to a new organization, the inventory quantity of the new organization is zero.