普華永道implementingoraclefinancialsunder-資料下載頁(yè)
2025-01-20 06:58本頁(yè)面
【正文】 s Not Modified for MultiOrg Examples The Context Diagram below depicts the Oracle Applications that have been modified to operate independently within a MultiOrg Configuration. Thus,each application requires a separate setup only for each Operating Unit within which it is to be utilized . . . . Order Entry Payables Projects Sales Compensation Receivables Sales amp。 Marketing Service Cash Management Purchasing Oracle MultiOrg Configuration Setup once per Operating Unit Applications Not Modified for MultiOrg The Context Diagram below depicts both the Oracle Applications that have been modified to operate independently within a MultiOrg Configuration as well as those that have not (. outside the circle). Each Application outside context requires a separate setup for each Enterprise only within which it is to be utilized . . . Order Entry Payables Projects Sales Compensation Receivables Sales amp。 Marketing Service Cash Management Purchasing Oracle MultiOrg Configuration Setup once per Operating Unit Assets Inventory Manufacturing General Ledger Applications Not Modified for MultiOrg Oracle General Ledger A MultiOrg configuration enables proper segregation of data across operating units . . . . Oracle General Ledger Business Group 1 Business Group 2 Legal Entity 3 Set of Books 3 (G/L, F/A ) Operating Unit 4 (A/P, A/R, P/O, O/E) Inventory Org. 3 (INV and all MFG Apps) Set of Books 1 (G/L, F/A) Legal Entity 1 Operating Unit 1 (A/P, A/R, P/O, O/E) Inventory Org. 2 (INV and all MFG Apps) Legal Entity 2 Set of Books 2 (G/L, F/A) Operating Unit 3 (A/P, A/R, P/O, O/E) Inventory Org. 4 (INV and all MFG Apps) Operating Unit 2 (A/P, A/R, P/O, O/E) Inventory Org. 1 (INV and all MFG Apps) Security Rules Vs. CrossValidation Rules Oracle General Ledger Security Rules Restricts access to a specific accounting flexfield segment(s) . pany segment CrossValidation Rules Used to control the setup of account binations across locations, departments, product codes, etc. Steps in Defining Security Rules Oracle General Ledger Step 1: Determine a pany’s business requirements Step 2: Define online security for account inquiry and data entry Step 3: Define security for FSG’s and Standard reports Step 1: Determine a Company’s Business Requirements Oracle General Ledger CrossValidation Rules Vs. Security Rules Two or more panies operating independently within a single set of General Ledger books Autonomy across values associated with a particular accounting flexfield segment Step 2: Define Online Security for Account Inquiry and Data Entry Oracle General Ledger Define Messages associated with a particular rule Globally “Include” the range of values associated with a particular rule “Exclude” all values not valid for a particular rule Assign Security Rule(s) to a particular responsibility Step 3: Define Security for FSG’s and Standard Reports Oracle General Ledger To define security for Standard Reports: this functionality is not currently available in Applications version To define security for FSG Reports: System Administrator Responsibility set the “System Profile Value Oracle Assets Utilizing a mon thread, such as pany number, throughout the asset flexfields provides processing autonomy as well as security across the applications ... Plant Sample Asset Hierarchy Accounting Key Flexfield CODIVLOCDEPTACCTSUBPROD Company X Asset Book Company Y Asset Book Company Z Asset Book G/L Set of Books Asset Category Flexfield Company No. Major Category Minor Category Asset Location Flexfield Company No. State County City Asset Key Flexfield Company Project CEA Business Segment Oracle General Assets Conclusion Implementing Oracle Financials Under MultiOrg Allison G. Fisher Laura B. DeSantis OAUG Oracle Applications Users Group
教學(xué)課件相關(guān)推薦
鄂ICP備17016276號(hào)-1