Friday, June 18, 2010

R12 MOAC(Multi Org Access Control)& its benefits

-->Use a single installation of any Oracle Applications product to support any number of organizations, even if those organizations use different ledgers

-->Support flexible organizational models

-->Secure access to data so that users can only access relevant information

-->Access one or more operating units using a single responsibility.

-->Perform tasks across multiple operating units:

Enter transactions

Process data

View Information

Run Reports


-->Increase effectiveness of Shared Service Centers or companies that have centralized business functions



Improve Efficiency
Process data across multiple OUs from one responsibility
Process transactions more efficiently for companies that have centralized business functions or operate Shared Service Centers

Obtain better information for decision making
Obtain a global consolidation for decision making
View information, such as supplier sites and customer sites across multiple OUs

Reduce Costs
Speed data entry
Reduce setup and maintenance of many responsibilities.

Payables
Reduce processing time with the ability to enter invoices for multiple operating units without switching responsibilities.
Reduce processing cost with the ability to pay invoices for multiple operating unit in a single pay run.

Receivables
Provide global information for decision making purposes with new cross-org reports.

Purchasing
Ability to negotiate discounts armed with consolidated requisition demands.

CollectionsGlobal collections agency with consolidated view of accounts and collection tasks for multiple operating units.

Accounting Setup ManagerThe Accounting Setup Manager is a central location to define accounting related setup across all financial applications. User Accounting Setup Manager to define legal entities and their accounting context, which includes the ledgers that will contain the accounting data for each legal entity.
Multi-Org is integrated into the Accounting Setup Manager such that users can define operating units and their relationship to ledgers. For each operating unit, users can also select a legal entity to provide a default legal context during transaction processing. This centralizes your setup and makes it easier to inquire on and maintain relationships between ledgers, legal entities, and operating units.

Thursday, June 17, 2010

R12 Purchasing setups with Detail explanation-Part 1

Overview of Setting up
This section contains an overview of each step you need to complete to set up Oracle Purchasing. For instructions on how to complete each task, see the setup sections indicated in each step.

Multiple Reporting Currencies:

If you plan to use Multiple Reporting Currencies (MRC) with Oracle Purchasing, additional setup steps are required. See: Multiple Reporting Currencies in Oracle Applications.

Setup Checklist:

Some of the steps outlined in the setup checklist are required, and some are Optional. Required Step with Defaults means that the setup functionality comes with pre-seeded, default values in the database; however, you should review those defaults and decide whether to change them to suit your business needs. If you want or need to change them, you should perform that setup step. You need to perform Optional steps only if you plan to use the related feature or complete certain business functions. Some of the setup steps you may not need to perform if you've already performed a common-application setup (setting up multiple Oracle Applications products).The following table lists setup steps and a reference to their Oracle Application. After you log on to Oracle Applications, complete these steps to implement Purchasing:

Step No. Required Step Application

Step 1 Required Set Up System Administrator- Common Applications

Step 2 Required Define Accounting Key Flex fields -Common Applications

Step 3 Required Set Up Calendars, Currencies, and Ledgers -Common Applications

Step 4 Required Define Human Resources Key Flex fields -Common Applications

Step 5 Required Define Locations- Human Resources

Step 6 Required Define Organizations and Organization Relationships-Human Resources

Step 7 Required Convert to a Multi-Org Architecture -Common Applications

Step 8 Required Define Inventory Key Flex fields- Common Applications

Step 9 Required Define Units of Measure -Oracle Inventory

Step 10 Optional Define Freight Carriers -Oracle Inventory

Step 11 Required Step with Defaults Define Item Attributes, Codes, and Templates -Oracle Inventory

Step 12 Required Define Categories- Oracle Inventory

Step 13 Optional Define Catalog Groups -Oracle Inventory

Step 14 Required Set Up Personnel -Human Resources

Step 15 Required Set Up Oracle Workflow -Common Applications

Step 16 Required Decide How to Use the Account Generator-Oracle Purchasing

Step 17 Required Open Inventory and Purchasing Accounting Periods-Oracle Purchasing

Step 18 Optional Define Sub inventory Locations- Oracle Inventory

Step 19 Optional Define Cross-Reference Types -Oracle Purchasing

Step 20 Optional Define Taxes -Oracle E-Business Tax

Step 21 Optional Define Payment Terms -Oracle Payables

Step 22 Required Set Up Approval Information -Oracle Purchasing

Step 23 Required Define Lookups and Classes -Oracle Purchasing

Step 24 Optional Define Standard Attachments -Oracle Purchasing

Step 25 Required Define Purchasing Options -Oracle Purchasing

Step 26 Required Define Buyers -Oracle Purchasing

Step 27 Optional Define Items -Oracle Purchasing

Step 28 Required Setup Define Line Types- Oracle Purchasing

Step 29 Required Start the Purchasing Database Administrator-Oracle Purchasing

Step 30 Required Define Financial Options- Oracle Payables

Step 31 Optional Define Transaction Reasons -Oracle Purchasing

Step 32 Required Define Receiving Options -Oracle Purchasing

Step 33 Required Set Up Transaction Managers and Resubmission Intervals-Oracle Purchasing

Step 34 Required Define Suppliers Oracle Payables

Step 35 Required Step Workflow Options- Oracle Purchasing

Step 36 Required Submit Workflow-related Processes -Oracle Purchasing

Step 37 Optional Define Descriptive Flex fields- Common Applications

Step 38 Optional Set Up Automatic Sourcing Oracle Purchasing

Step 39 Required Perform Additional System-Common Applications

Step 40 Required Define Manufacturing System and User Profiles

R12 Inventory with detail explanation

For more info you may click the link to download R12 Inventory
R12 Inventory