This action might not be possible to undo. Are you sure you want to continue?
1 Last Revision Date: 14-MAR2005
PURPOSE This document is intended to help users successfully setup organizations for the purpose of Intercompany Invoicing through the Oracle Inventory Application. SCOPE & APPLICATION This document is intended to supplement the documentation provided with the application. Intercompany Invoicing Inventory Setup Information
Type: BULLETI N Status: PUBLISH ED
Steps to Implement the Multiple Organization Support 1. Develop the Organization Structure 2. Define Sets of Books 3. Define Organizations 4. Define Organization Relationships 5. Define Responsibilities 6. Set the Operating Unit Profile Option for Each Responsibility 7. Convert to Multiple Organization Architecture 8. Define Inventory Organization Security (optional) 9. Change Order Entry Profile Options (optional) 10. Update Profile Options Specific to Operating Units 11. Implement the Applications Products 12. Secure Balancing Segment Values by Legal Entity (optional) 13. Run the Setup Validation Report (recommended)
Prerequisites to Using the Intercompany Invoicing Process 1. Define 2. Define 3. Define 4. Define Receivables. 5. Set up your your your your intercompany relations. Oracle Receivables system options. Oracle Payables system options. tax structures in Oracle Payables and Oracle
the Account Generator for the Cost of Goods Sold
Japan. and Operating Unit. D) Select "Accounting Information".accounts.e. Intercompany Relations Defined: A) Navigation: Inventory-> Setup-> Organizations-> Intercompany Relations B) Confirm the Operating Units: Shipping: Selling: C) AR Invoicing for Shipping: Customer: Number: Location: Transaction Type: D) AP Invoicing for Selling: Supplier: Site: Freight Account: E) Revalue Average: 3. Verify Currency Codes: A) Navigation: Inventory-> Setup-> Financials> Currencies-> Currency Codes B) Ensure that the currency codes used are active and have not . E) Open up the "Additional Organization Information". i. US). Inventory Setup Confirmation Steps 1. Verify Set of Books. F) "Accounting Information" flexfield will open with Set of Books. 2. C) Select the Inventory Organization under "Organization Classifications" and click on the "Others" button. Legal Entity. Verify Set of Books: A) B) C) D) E) Navigation: Inventory-> Setup-> Financials-> Books Select the particular Set of Books Chart of Accounts defined Functional Currency defined Accounting Calendar defined 4. & Operating Unit: A) Navigation: Inventory-> Setup-> Organizations B) Select the particular organization in question (Both organizations. Legal Entity. G) Confirm that the information in these fields is accurate and relevant to the particular organizations involved in the Intercompany process.
After you have associated business groups with responsibilities. The Validation Report indicates an error if this is not the case. If you have multiple business groups.been disabled (Scroll to the right) Profiles Options: 1. or if you do not choose to use the default business group provided by Oracle Applications. 3. and notes when profile options should be set at the responsibility level. HR:Business Group This section applies to you only if you have multiple business groups. This . You associate a responsibility with a business group via the HR:Business Group system profile option. verify the HR:Business Group profile option before you define organizations in each business group. Consistent Profile Option Values: All responsibilities in one operating unit must share the same profile option values and the same sequence numbering option. you must also associate each existing responsibility with a business group. If you have multiple business groups. MO:Operating Unit You must set the MO:Operating Unit profile option for each responsibility. This profile option must be set for Oracle Training Administration (OTA) responsibilities when OTA is used in a Multi-Org environment. you can enter business group setup information such as additional organization information and business group classifications. Set this profile option to the appropriate operating unit id (ORG_ID) for each responsibility. If you are upgrading to Multi-Org. 2. you must associate each responsibility with one and only one business group. The operating unit context for each responsibility is set via this profile option.
b) Tax: Allow Override of Tax Code Determines whether tax code information should be passed to AR for freight. e) OE: Item Validation Organization Inventory organization in which the freight item specified in the profile Tax: Inventory Item for Freight is defined. the default operating unit can be any operating unit you have defined. c) Tax: Invoice Freight as Revenue Indicates whether freight lines should be invoiced as revenue lines. Update Profile Options Specific to Operating Units Use the Update System Profile Options window to set profile options that are specific to each operating unit.is to ensure that the OTA customer and supplier functions work correctly in a Multi-Org environment. Some inventory item attributes for Receivables and Order Entry. 4. are specific to an operating unit or an accounting flexfield structure. you should use the OE:Item Validation Organization profile option to define an item validation organization for each operating unit. 6. If this is a fresh installation. Therefore. The following profile options affect the operation of the Create Intercompany AR Invoices process: a) INV: Intercompany Currency Conversion Determines the conversion type for foreign currency invoices. you should assign as the default operating unit the operating unit to which all existing data should belong. including Tax Code and Sales Account. d) Tax: Inventory Item for Freight Use this inventory item when freight lines are invoiced as revenue lines. 5. OE:Item Validation Organization The OE:Item Validation Organization profile option determines the inventory organization that Order Entry uses to validate items. You must also define the default operating unit by setting the MO:Operating Unit profile at the site level. You must set these profile option . If this is an existing installation.
you may want to change your profile options to be visible and updatable at the responsibility level. Oracle General Ledger windows use the GL Set of Books profile option to determine your current set of books. Problem statement: ON POXBWVRP BUYER CAN SEE ALL REQUISITIONS. and GL Set of Books. Profile options specify default values that affect system processes. system controls. including OE:Item Validation Organization. You must set these profile options at the responsibility level. If you have different sets of books for your operating units. and data entry. In a multiple organization environment you may want to confine the effect to a specific operating unit. . DESPITE SECURITY LEVEL=HIERARCHY *** 09/03/04 01:36 am *** ======================================================================= ====== PROBLEM DESCRIPTION ======================================================================= ====== ** DETAILED DESCRIPTION OF PROBLEM. reference data that is secured by operating unit. including AR:Receipt Batch Source and AR:Transaction Batch Source. Some profile options. For profile options that need to differ at the set of books level. you should set the GL Set of Books profile option for each responsibility that includes Oracle General Ledger windows. Therefore. OE:Set of Books. set the values at the responsibility level.values for all relevant responsibilities that connect to each operating unit. including Sequential Numbering. you must set the values at the responsibility level. INCLUDING ALL ERRORS: Customer is using a Document Security Level of Hierarchy in order to restrict the document access on Purchase Requisitions: Users should not see everyone else's Requisitions. For profile options that need to differ at the operating unit level.
POXPOVPO. B creates a requisition.A. 4)Some users and positions are defined: . the document access security is well in place. B are defined as buyers . with a Document Level Access set to 'Hierarchy'. 1) Setup/Purchasing/Document Types For Purchase Requisition document type the Security Level is HIERARCHY.. A will be able to view the same from Requisition Summary form A creates a requisition. POXRQVRQ .. POXBWVRP.A..). find form doesn't check 'Document Security Level' set to 'Hierarchy' on documents and so buyer can view or autocreate all requisitions: . POXBWVRP. . However from Autocreate form B can view and autocreate the requisition created by A . B will not be able to view the same from Requisition Summary form . 5) On the Requisitions Summary form .B's position reports to A's position / A is one level above B . Only the document owner. According documentation . as it is true for other forms (POXRQVRQ. There is a security hole Subje 11i PO ct: POXBWVRP Buyer is able to autocreate requisitions created by . B have positions defined in the same hierarchy . and individuals included in the security hierarchy can access the document' 2) Setup/Personnel/ Position Hierarchy One position hierarchy including all positions that require access to the document types to be controlled with a Security Level of Hierarchy has been defined . This should be true for the autocreate form. subsequent approvers. 3) Setup/organizations/Purchasing Options form POXSTDPO In the Control tabbed region in the Purchasing Options window. and individuals included in the security hierarchy should access the document. subsequent approvers. the Security Hierarchy is indicated so it governs access security for the document. ' Hierarchy : Only the document owner. On the Autocreation form.
B .A.However from Autocreate form C can view and autocreate the requisition created by B cause: Intended Functionality Document security rule will be applicable to only the corresponding document windows i.B and C reports to A .8 fact: POXBWVRP .B and C are in the same level in the hierarchy .A.B and C occupies different positions at the same level . 1 Last Revision 15-SEP-2004 Date: Type: Status: PROBLEM PUBLISHED • • • • • fact: Oracle Purchasing 11.B creates a requisition .A is one level above B and C . B .5. C are defined as buyers .AutoCreate Documents symptom: Buyer is able to autocreate requisitions created by other user symptom: Security Level for the hierarchy is set as "Hierarchy" symptom: Buyer will not able to view these requisitions from requisition summary form change: Note Role : . C are in the same hierarchy .other user Doc ID: Note:241647. . • • fix: Intended Functionality Autocreate window is accessible for all buyers in the organization. C will not able to view the same from Requisition Summary form .e Requisition window or Purchase Order window not for autocreate window.
. INCLUDING ALL ERRORS: Customer is using a Document Security Level of Hierarchy in order to restrict the document access on Purchase Requisitions: Users should not see everyone else's Requisitions. subsequent approvers. B have positions defined in the same hierarchy . the Security Hierarchy is indicated so it governs access security for the document. 1) Setup/Purchasing/Document Types For Purchase Requisition document type the Security Level is HIERARCHY.Hence. if a person is setup as buyer. then all these documents will be visible for him to autocreate to a PO PROBLEM DESCRIPTION =============================================================== ============== ** DETAILED DESCRIPTION OF PROBLEM. .A. 3) Setup/organizations/Purchasing Options form POXSTDPO In the Control tabbed region in the Purchasing Options window. 4)Some users and positions are defined: . and individuals included in the security hierarchy can access the document' 2) Setup/Personnel/ Position Hierarchy One position hierarchy including all positions that require access to the document types to be controlled with a Security Level of Hierarchy has been defined . ' Hierarchy : Only the document owner.
as it is true for other forms (POXRQVRQ..Version: 11. POXRQVRQ . POXPOVPO.1159.pls-115. subsequent approvers. There is a security hole. B will not be able to view the same from Requisition Summary form . the document access security is well in place.1159.9 to 220.127.116.11.). with a Document Level Access set to 'Hierarchy'. The information in this article applies to: Oracle Purchasing . However from Autocreate form B can view and autocreate the requisition created by A .9 This problem can occur on any platform.2 .5. B creates a requisition.3 porelgeb. B are defined as buyers . According documentation . A will be able to view the same from Requisition Summary form A creates a requisition.A.B's position reports to A's position / A is one level above B . POXBWVRP.. 5) On the Requisitions Summary form . and individuals included in the security hierarchy should access the document. This should be true for the autocreate form. find form doesn't check 'Document Security Level' set to 'Hierarchy' on documents and so buyer can view or autocreate all requisitions: . POXBWVRP. Only the document owner. POXBWP1B.. On the Autocreation form.pls-115.
pls-115.48.5 Default PO Promised Date from Need By Date' is introduce d.1159.Symptoms During Autocreation and Create Release processes the Promise Date is not automatically populated from Need-By-Date on Requisition. However. since this functionality was requested. the promise date is autopopul ated from Need-ByDate in Autocreat e and Create releases programs. This .2 this was standard functionality. Need-By-Date is entered by the customer. Cause Before POXBWP1B.pls-115.165.3 and porelgeb. while the input for the Promise Date is coming from the Supplier. a new profile option was introduced to have the possibility to copy over the information from the Need-By-Date from the requisition onto the PO Promised Date Fix A new 11i: How to setup profile Secure User in 'PO: Release 11. Based on this profile.1159. Therefore the information is not copied over automatically. because the information in these two fields is coming from different sources.
Responsi bility and User level. To set up Standard HRMS Security. If set 'Yes' then Promise Date will be copied over from the NeedBy-Date.1 Last Revision Date: 14-NOV2006 "Checked for relevance on 14-Nov-2006" Purpose ------Oracle HRMS provides two different security models which enable you to set up security specifically for your enterprise: Standard HRMS security and Security Groups Enabled security (formerly called Cross Business Group Responsibility Security). This note provides an overview of both models and a simplistic setup for the Security Groups Enabled Model. Type: BULLETIN Status: PUBLISH ED Standard Security Model ----------------------Standard HRMS security restricts access to your enterprise's records and data. By default it is NULL meaning not to default Promise Date. you first create responsibilities and . Subject: Doc ID: Note:73910 .profile is available at Site.
you must ensure that the Enable Multiple Security Groups profile option is set to the default value No. data and records the user can access. you cannot revert to Standard HRMS Security. Navigation: System Administration -> Profile -> System. Set Enable Security Groups profile option for the application Oracle Human Resources to YES. These three elements create a security grouping to which you assign employees. Attention: Once you have set up Security Groups Enabled security. If you are using Standard HRMS Security. The key to re-usability is the relationship between the security elements and the users that you create during the set up process. Branch Manager and Salesperson. Related Documents ----------------Please refer to the on-line documentation 'Security Models' for a more detailed explanation of the process. Security Groups Enabled Model Step-by-Step Setup Information -----------------------------1. and link the security profile and responsibility to a business group. Application = Oracle Human Resources. Security Groups Enabled Model ----------------------------The main difference between the two security models is that the Security Groups Enabled model enables your enterprise to share security profiles and responsibilities between users and business groups. You then create a responsibility for each user type you require. menus items. This reduces the set up time. Find %Enable% . You must then create a security profile for each distinct security grouping of employees your enterprise requires. workflows.then define the windows. The System Administrator then assigns users to as many of these responsibilities as is required to complete their business tasks. and also increases the flexibility of this security model. for example HR Manager.
Attention: Once you have set up Security Groups Enabled security. STEPS TO PERFORM: ================= 1. 3.HRMS Manager Navigation: Process & Reports -> Submit Processes and Reports Select Security List Maintenance PROBLEM DESCRIPTION: ==================== How do you disable an Inventory organization when the organization contains items with on hand quantities? SOLUTION DESCRIPTION: ===================== Enter a date in the 'Date To' field. Responsibility . . Responsibility . Responsibility = <new responsibility>. 6. 2. Close the period for this Inventory organization. Set HR User type profile option for the new responsibility to HR User or HR w/Payroll User. Navigation: Security -> Responsibility -> Define 4.System Administrator. Combine the Username. Save your changes. Find = HR% 5.System Administrator. 8. you CANNOT revert to Standard HRMS Security.HRMS Manager Navigation: Process & Reports -> Submit Processes and Reports Select Enable Multiple Security Group. Transfer all stock on hand out of the Inventory organization. This will remove the organization from the list of organizations available for assignments. Responsibility . . Navigate to Inventory > Setup > Organizations. Responsibility . query up the Inventory organization and enter in date in the 'Date To' field. Run Security List Maintenance (LISTGEN) Responsibility . Define a responsibility. Define a security profile with the restrictions required (organization or position hierarchies or payroll). Navigation: Security -> User -> Define 3. The system will not allow an Inventory organization to be deleted for audit purposes.2. Define a user. Navigation: System Administration -> Profile -> System. Run Enable Multiple Security Group process. this will disable the Inventory organization from that date. Assign security profiles. In the Define Organization form (PERWSDOR).HRMS Manager Navigation: Security -> Profiles 7. Business Group and responsibility as of the appropriate start date.HRMS Manager Navigation: Security -> Assign Security Profiles. Responsibility .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.