operating units data segregation:

[k.khan]

hi friends,
In operating unit of one organisation,user is also viewing the data of the other operating unit means in the operating unit of karachi the bank data given here could also be seen from the other operating unit of lahore.Is there is any way to restrict the user?

[karthikeyanp1981]

Hi khan,
can you rephrase your question ! U r referring to Bank Data , what do u mean by that ? Can u give a clear picture by elaborating ur issue for better response !

(Clear Questions always gets the answer it deserves)

[muzaffarnaim]

Mr. Khan users can view only supplier's and bank's header information of all OUs but not supplier site or bank accounts information....If they r also viewing these info or all invoices of other OUs then check if 'MO.Operating Unit' has been properly set on responsibilities or not...In case of invalid information coming on reports, set 'MO:Top reporting level' to valid OU.

Muzaffar Naim

Oracle Consultant

[k.khan]

thanks alot Muzaffar but if we do wish so,is there is any work around of it
some one has told me that replica seed data report from system administration can do this but fail to do so

[anu_uma]

Hi Khan,

Replicate Seed data is for Multi Organizations setup an additional operating unit to an existing structure....

Before running this step, you must define an operating unit and set the
site-level AOL profile option MO: Operating Unit to use your new
operating unit.

When you define additional operating units, the seed data will be replicated for all operating units.

<b>Adding a New Operating Unit</b>

The following steps are required to add new operating units to your
organizational structure:

01. Develop the Organization Structure
02. Define Sets of Books:
03. Define Locations
04. Define Organizations
05. Define Relationships
06. Define Responsibilities
07. Set Profile Options for Each Responsibility linked to the new Operating
Unit. "Set MO: Operating Unit Profile Option"
08. Run the Replicate Seed Data concurrent program
09. Set profile options specific to operating units.
10. Define Inventory Organization Security (optional)
11. Implement the Application Products.
12. Secure Balancing Segment Values (optional)
13. Run the Setup Validation Report
14. Implement Document Sequencing (optional)
15. Define Intercompany Relations (optional)
16. Set the top reporting level (optional)