Saturday, October 17, 2009
Sunday, July 26, 2009
Oracle Release 12 Enhancements
R12 changes in Oracle Financials
1. Describe ledgers versus Set of Books. Explain ledger sets
2. Describe that responsibilities are changing.
3. Describe the changes and new functionality for GIS or Advanced Global Intercompany
4. Explain SLA
5. Brief the major updates for FA.
6. Describe new functionality in Payables for Assets
7. Describe the changes for Vendors/Suppliers, Banks, TAX all being centralized
General Ledger
1. General Ledger now has Ledgers. Replaces Set of Books.
2. A ledger Determines the currency, Chart of Accounts, Accounting Method, Ledger
Processing Options and Subledger accounting method.
3. Ledgers are defined when you create accounting setups in Accounting Setup
Manager.
Ledger Set – Assign to single Responsibility
Logical grouping of ledgers with the same chart of Accounts and
Calendar /Period type. The Calculation Basis for
cross/multiledger Inquiry, Reporting, and shared services
operations.
- Opening/Closing Period
- Creating period closing journals, Allocations & Recurring Journals
- Translating Balances
- Reporting
Responsibilities
Responsibilities
1.One responsibility can now be used to access multiple legal entities and ledgers.
2.Data Access Sets are used to control access.
3.When submitting a concurrent request you can submit the report for one or all the
ledgers/Legal entities that you have been given access to.
4.GL data access profile option replaces GL set of books.
Intercompany New Features
1.New separate product
2.Name: Advanced Global Intercompany System - AGIS
3.Ability to create invoices (AR and AP)
4.Multiple recipients Support
5.Proration of transaction distribution amounts
6.Upload Transaction Batches created in Excel
1. Describe ledgers versus Set of Books. Explain ledger sets
2. Describe that responsibilities are changing.
3. Describe the changes and new functionality for GIS or Advanced Global Intercompany
4. Explain SLA
5. Brief the major updates for FA.
6. Describe new functionality in Payables for Assets
7. Describe the changes for Vendors/Suppliers, Banks, TAX all being centralized
General Ledger
1. General Ledger now has Ledgers. Replaces Set of Books.
2. A ledger Determines the currency, Chart of Accounts, Accounting Method, Ledger
Processing Options and Subledger accounting method.
3. Ledgers are defined when you create accounting setups in Accounting Setup
Manager.
Ledger Set – Assign to single Responsibility
Logical grouping of ledgers with the same chart of Accounts and
Calendar /Period type. The Calculation Basis for
cross/multiledger Inquiry, Reporting, and shared services
operations.
- Opening/Closing Period
- Creating period closing journals, Allocations & Recurring Journals
- Translating Balances
- Reporting
Responsibilities
Responsibilities
1.One responsibility can now be used to access multiple legal entities and ledgers.
2.Data Access Sets are used to control access.
3.When submitting a concurrent request you can submit the report for one or all the
ledgers/Legal entities that you have been given access to.
4.GL data access profile option replaces GL set of books.
Intercompany New Features
1.New separate product
2.Name: Advanced Global Intercompany System - AGIS
3.Ability to create invoices (AR and AP)
4.Multiple recipients Support
5.Proration of transaction distribution amounts
6.Upload Transaction Batches created in Excel
Wednesday, May 20, 2009
Checklist for Oracle Accounts Payable
1. Choose Set of Books
2. Setting up Banks
a. Defining Internal Banks
b. Payable Options
c. Defining Payable Documents
3. Creating Suppliers
a. Overview of Suppliers
b. Supplier Information - Control Region
c. Bank Account Region
d. Supplier Information - Invoice Tax region
e. Entering Basic Supplier Site Information
f. Supplier Site Information - General Region
g. Supplier Site Information - Tax Reporting region
h. Supplier Reports
4. Invoices
a. Invoice Types
b. Assigning a Default GL Date
c. Entering Invoices
d. Batch Control Form
e. Invoice Structure
5. Demo Examples
a. Type of Accounting Flows
b. Invoice Gateway
c. Apply & Release Holds on AP invoices
d. Levels of Invoice Approval
6. Processing Debit and Credit Memos
a. Clearing a Credit
b. Recording a Price Correction
c. Processing Pre-Payments
7. Accounting in Oracle Payables
a. Accounting Events :
b. Creating Accounting Entries :
c. Viewing Accounting entries
d. Overview of Transferring accounting to GL
e. Reviewing accounting Entries
8. Implementing Supplier Invoices
a. Setting Tolerance Levels for invoice Taxes
b. Setting up invoice payables options
c. Implementation considerations
9. Payments
a. Payment overview
b. Create a quick Check
c. Processing Stop Payments
d. Voiding Payments
e. Refund
f. Overview of Payment Batches
g. Overview of Electronic Payment Options
h. Pre-Requisites for processing electronic payments
i. Creating EDI payment batches
10. Implementing Payments
a. Payment Terms
b. Payment Formats
c. Define Financials Options (Required)
d. Define Payables Options (Required
2. Setting up Banks
a. Defining Internal Banks
b. Payable Options
c. Defining Payable Documents
3. Creating Suppliers
a. Overview of Suppliers
b. Supplier Information - Control Region
c. Bank Account Region
d. Supplier Information - Invoice Tax region
e. Entering Basic Supplier Site Information
f. Supplier Site Information - General Region
g. Supplier Site Information - Tax Reporting region
h. Supplier Reports
4. Invoices
a. Invoice Types
b. Assigning a Default GL Date
c. Entering Invoices
d. Batch Control Form
e. Invoice Structure
5. Demo Examples
a. Type of Accounting Flows
b. Invoice Gateway
c. Apply & Release Holds on AP invoices
d. Levels of Invoice Approval
6. Processing Debit and Credit Memos
a. Clearing a Credit
b. Recording a Price Correction
c. Processing Pre-Payments
7. Accounting in Oracle Payables
a. Accounting Events :
b. Creating Accounting Entries :
c. Viewing Accounting entries
d. Overview of Transferring accounting to GL
e. Reviewing accounting Entries
8. Implementing Supplier Invoices
a. Setting Tolerance Levels for invoice Taxes
b. Setting up invoice payables options
c. Implementation considerations
9. Payments
a. Payment overview
b. Create a quick Check
c. Processing Stop Payments
d. Voiding Payments
e. Refund
f. Overview of Payment Batches
g. Overview of Electronic Payment Options
h. Pre-Requisites for processing electronic payments
i. Creating EDI payment batches
10. Implementing Payments
a. Payment Terms
b. Payment Formats
c. Define Financials Options (Required)
d. Define Payables Options (Required
Monday, May 18, 2009
Oracle Accounts Payable
Overview of Accounts Payable
Oracle Payables contains four major processes:
Set up Suppliers: Before entering invoices for a new supplier (vendor), you need to setup the supplier in Oracle Payables
Enter and Approve invoices: You can enter and approve invoices individually or in batches.
Pay invoices: You can also pay approved invoices individually or in batches by check or electronically.
Post transactions to the general ledger: You can transfer the invoices and payment accounting distributions and audit information to the general ledger interface. You can then use your general ledger system to import this information and create entries.
Accounts Payable Questionnaire for Client:
1. Overview of the Accounts Payable operations.
2. Provide samples of vendor master records.
3. Do you differentiate vendor sites which can receive payments and sites which
cannot receive payments?
4. Describe the invoice vouchering process.
5. Are recurring expense distributions for fixed or varying amounts?
6. Explain Payment Terms List, Interest Charges, and Discounts?
7. Should invoices be matched completely, partially or both?
8. Explain Invoice Approval Process? Describe the approval process when invoices
need to be placed on hold and manually released?
9. What requirement is there to process employee expense reports? Please describe.
Provide Sample.
10. What is the current process to generate expense payments to employees?
11. Do your employees have company credit cards? How are company credit cards
managed (issued, audited, reconciled, etc.)?
12. List of Supplier / Payment Banks
13. Is there a requirement to use Electronic Funds Transfer?
14. Is there a requirement to use Wire Transfers?
15. Is there a requirement to process Automatic Payments?
16. Is there a requirement to process Manual Payments? If so, is a separate bank
account used?
17. Is there a requirement to process Partial Payments?
18. Is there a requirement to process Pre-Payments?
19. Is there a requirement to process Recurring Payments?
20. Is there a requirement to process immediately available ‘Quick Checks’?
21. What is the current procedure for vendor advances?
22. How are vendor advances reconciled when the vendor invoice is submitted?
23. Do you have, or do you require, a priority system for payments? Describe its use.
24. What is your current payment cycle? (How often do you print checks?)
25. If recurring payments are used, what is the normal period cycle for these
payments?
26. Is there a requirement to use Computer Generated checks?
27. What is your process to cancel checks?
28. Are all invoices paid in local currency and what currency is used? If not local,
list the foreign currencies used.
29. How many payment formats do you have? Provide samples.
30. Do you print the check number on the check/remittance or is it pre-printed?
31. Should a remittance advice note be produced, and when?
32. What is the policy/procedure for handling stop payments?
33. What is the policy/procedure for handling void payments if they have been
recorded?
34. What are the requirements for reporting tax payments (e.g.
company, rate or tax authority)?
35. Do you have to pay other businesses within the Group
36. Do you use Cash or Accrual Based Accounting?
37. Please provide all copies of Payable reports
38. How long do you do check reconciliation?
Oracle Payables contains four major processes:
Set up Suppliers: Before entering invoices for a new supplier (vendor), you need to setup the supplier in Oracle Payables
Enter and Approve invoices: You can enter and approve invoices individually or in batches.
Pay invoices: You can also pay approved invoices individually or in batches by check or electronically.
Post transactions to the general ledger: You can transfer the invoices and payment accounting distributions and audit information to the general ledger interface. You can then use your general ledger system to import this information and create entries.
Accounts Payable Questionnaire for Client:
1. Overview of the Accounts Payable operations.
2. Provide samples of vendor master records.
3. Do you differentiate vendor sites which can receive payments and sites which
cannot receive payments?
4. Describe the invoice vouchering process.
5. Are recurring expense distributions for fixed or varying amounts?
6. Explain Payment Terms List, Interest Charges, and Discounts?
7. Should invoices be matched completely, partially or both?
8. Explain Invoice Approval Process? Describe the approval process when invoices
need to be placed on hold and manually released?
9. What requirement is there to process employee expense reports? Please describe.
Provide Sample.
10. What is the current process to generate expense payments to employees?
11. Do your employees have company credit cards? How are company credit cards
managed (issued, audited, reconciled, etc.)?
12. List of Supplier / Payment Banks
13. Is there a requirement to use Electronic Funds Transfer?
14. Is there a requirement to use Wire Transfers?
15. Is there a requirement to process Automatic Payments?
16. Is there a requirement to process Manual Payments? If so, is a separate bank
account used?
17. Is there a requirement to process Partial Payments?
18. Is there a requirement to process Pre-Payments?
19. Is there a requirement to process Recurring Payments?
20. Is there a requirement to process immediately available ‘Quick Checks’?
21. What is the current procedure for vendor advances?
22. How are vendor advances reconciled when the vendor invoice is submitted?
23. Do you have, or do you require, a priority system for payments? Describe its use.
24. What is your current payment cycle? (How often do you print checks?)
25. If recurring payments are used, what is the normal period cycle for these
payments?
26. Is there a requirement to use Computer Generated checks?
27. What is your process to cancel checks?
28. Are all invoices paid in local currency and what currency is used? If not local,
list the foreign currencies used.
29. How many payment formats do you have? Provide samples.
30. Do you print the check number on the check/remittance or is it pre-printed?
31. Should a remittance advice note be produced, and when?
32. What is the policy/procedure for handling stop payments?
33. What is the policy/procedure for handling void payments if they have been
recorded?
34. What are the requirements for reporting tax payments (e.g.
company, rate or tax authority)?
35. Do you have to pay other businesses within the Group
36. Do you use Cash or Accrual Based Accounting?
37. Please provide all copies of Payable reports
38. How long do you do check reconciliation?
Monday, May 11, 2009
Purchasing - Setup - Overview
1. Define Employee - Employee setup for document approval
(N) US Payroll Manager>People>Enter and Maintain
Screen - People
2. Define Jobs
(N) US Payroll Manager>Work Structures>Jobs>Descriptions
Screen - Position
3. Define Position
(N) US Payroll Manager>Work Structures>Position>Descriptions
Screen - Position
4. Choose Set of Books
(N) Purchasing>Setup >Organizations > Set of Books > Choose
This step would be required for a new Operating unit set up and if the same
function is not already done in the Accounts Payable module.
5. Create Position Hierarchies
(N) Purchasing>Setup >Personnel>Position Hierarchy
Screen - Position Hierarchy
Steps:
1. Query for the Position Hierarchy Name
2. Click in the Position Block against the Name Field and query for the top
most position in the Hierarchy. All those positions existing in the
Hierarchy will have the Exists in Hierarchy check box checked.
3. Click in the Subordinates field and keep drilling down to see the listed
subordinates below the appearing subordinate.
6. Assign Employees
(N) US Payroll Manager>People>Enter and Maintain > Assignment
Screen - Assignment
7. Assign Employee to the User
(N) System Administrator>Security>User > Define
Screen - Users
Link the User name with the Person (Employee).
8. Run Fill Employee Hierarchy Report
(N) Reports>Run>Fill Employee Report
Run this report to compile the Position Approval Hierarchy. Any change to the
Hierarchy is ineffective until and unless this report is not run.
9. Tax Codes (N) Payables>Setup>Tax>Codes
Description: In the Tax Codes window, you define the tax names, or tax codes, you use on invoices to record invoice taxes you pay to suppliers and tax authorities. Each tax code has a tax type, a tax rate, and an account to which you charge tax amounts.
These Tax code can be defined at various levels i.e. Financial options, Suppliers, Item etc. and can have a predefined hierarchy choosen for defaults on the transactions.
10. Financial Positions (N) Setup > Organizations > Financial Options
Screen - Financial Options
This step is performed for a new Operating Unit. This is a common set up for
Accounts Payable module & Purchasing Module.
11. Purchasing Options (N) Setup > Organizations > Purchasing Options
Screen - Purchasing Options
12. Receiving Options
(N) Setup > Organizations > Receiving Options
Screen - Receiving Options
13. Approval Groups (N) Purchasing>Setup >Approvals>Approval Group
Screen - Approval Group
14. Approval Assignment (N) Purchasing>Setup >Approvals>Approval Assignment
Screen - Assign/Approval Group
For each position in your organization, you assign specific Approval/Control
groups to individual document types. Employees who are assigned to positions
acquire the authorization limits assigned to the respective positions.
16. Define Buyers
(N) Setup > Personnel > Buyers
Screen - Buyers
Only defined Buyers can enter Purchasing Documents
17. Quality Inspection Codes
(N) Setup > Purchasing > Quality Inspection Codes
Screen - Quality Inspection Codes
Quality Codes are used at the time of Quote Comparison, analysis and approval.
New Quality codes can be defined as and when required.
18. Define Payment Terms (N) Setup > Financials > Payment Terms
Description: Define payment terms that you can assign to an invoice to automatically create scheduled payments when you submit the invoice for Approval.
You can define payment terms to create multiple scheduled payment lines and multiple levels of discounts. You can create unlimited number of payment terms.
19. Define Line Types (N) Setup > Purchasing > Line Types
Screen - Line Types
20. Define Document Types
(N) Setup > Purchasing > Document Types
Screen - Document Types
21. Look Up Codes (N) Setup > Purchasing > Look Up Codes
Screen - Purchasing Options
Oracle Purchasing application uses lookup codes to define the list of Quick Pick
values for Quick Picks throughout the system. You can customize your Oracle
Purchasing application for certain fields by adding your own codes to those
initially provided. These lookup codes are used for reference purpose only. Few
default Reports does have these Lookup Codes as one of the Report Parameters.
Assign the Inactive Date as & when any of the Lookup code is not to be used.
Ensure that the Displayed Value and the Description of the Lookup Code is self-
explanatory.
22. Profile Options
(N) System Administration Responsibility > Profiles > System Profiles
23. Open Periods
(N) Setup > Financials > Accounting > Control Purchasing Periods
Description: Open accounting periods to record purchasing activity. Your Oracle Purchasing application lets you create journal entries only for transactions you enter in an open purchasing period. You also need to open your purchasing periods to create correct ‘receipt accrual’ journal entries in your General Ledger, only if the Accrual Option is Perpetual. Use Control Purchasing Periods form to open or close in your Oracle Purchasing application.
Setup > Accounting Close Cycle >Inventory Accounting Periods
We need to open an accounting period to enter transactions in Oracle Inventory. Accounting Periods are defined in Oracle General Ledger and then opened in Oracle Inventory using the Open Accounting Periods form. Oracle Inventory allows to have multiple periods open at any given time.
24. Define Categories
(N) Setup > Item > Categories > Category Codes
Screen - Find Categories
A category is a logical classification of your items.
25. Define Category Set
(N) Setup > Items > Categories > Category Sets
Screen - Category Sets
A category set is a set or group of categories.
Each functional area viz. Purchasing, Inventory, Costing, Order entry can have a
separate default Category set.
26. Define Items
(N) Items > Item Master
Screen - Items
(N) US Payroll Manager>People>Enter and Maintain
Screen - People
2. Define Jobs
(N) US Payroll Manager>Work Structures>Jobs>Descriptions
Screen - Position
3. Define Position
(N) US Payroll Manager>Work Structures>Position>Descriptions
Screen - Position
4. Choose Set of Books
(N) Purchasing>Setup >Organizations > Set of Books > Choose
This step would be required for a new Operating unit set up and if the same
function is not already done in the Accounts Payable module.
5. Create Position Hierarchies
(N) Purchasing>Setup >Personnel>Position Hierarchy
Screen - Position Hierarchy
Steps:
1. Query for the Position Hierarchy Name
2. Click in the Position Block against the Name Field and query for the top
most position in the Hierarchy. All those positions existing in the
Hierarchy will have the Exists in Hierarchy check box checked.
3. Click in the Subordinates field and keep drilling down to see the listed
subordinates below the appearing subordinate.
6. Assign Employees
(N) US Payroll Manager>People>Enter and Maintain > Assignment
Screen - Assignment
7. Assign Employee to the User
(N) System Administrator>Security>User > Define
Screen - Users
Link the User name with the Person (Employee).
8. Run Fill Employee Hierarchy Report
(N) Reports>Run>Fill Employee Report
Run this report to compile the Position Approval Hierarchy. Any change to the
Hierarchy is ineffective until and unless this report is not run.
9. Tax Codes (N) Payables>Setup>Tax>Codes
Description: In the Tax Codes window, you define the tax names, or tax codes, you use on invoices to record invoice taxes you pay to suppliers and tax authorities. Each tax code has a tax type, a tax rate, and an account to which you charge tax amounts.
These Tax code can be defined at various levels i.e. Financial options, Suppliers, Item etc. and can have a predefined hierarchy choosen for defaults on the transactions.
10. Financial Positions (N) Setup > Organizations > Financial Options
Screen - Financial Options
This step is performed for a new Operating Unit. This is a common set up for
Accounts Payable module & Purchasing Module.
11. Purchasing Options (N) Setup > Organizations > Purchasing Options
Screen - Purchasing Options
12. Receiving Options
(N) Setup > Organizations > Receiving Options
Screen - Receiving Options
13. Approval Groups (N) Purchasing>Setup >Approvals>Approval Group
Screen - Approval Group
14. Approval Assignment (N) Purchasing>Setup >Approvals>Approval Assignment
Screen - Assign/Approval Group
For each position in your organization, you assign specific Approval/Control
groups to individual document types. Employees who are assigned to positions
acquire the authorization limits assigned to the respective positions.
16. Define Buyers
(N) Setup > Personnel > Buyers
Screen - Buyers
Only defined Buyers can enter Purchasing Documents
17. Quality Inspection Codes
(N) Setup > Purchasing > Quality Inspection Codes
Screen - Quality Inspection Codes
Quality Codes are used at the time of Quote Comparison, analysis and approval.
New Quality codes can be defined as and when required.
18. Define Payment Terms (N) Setup > Financials > Payment Terms
Description: Define payment terms that you can assign to an invoice to automatically create scheduled payments when you submit the invoice for Approval.
You can define payment terms to create multiple scheduled payment lines and multiple levels of discounts. You can create unlimited number of payment terms.
19. Define Line Types (N) Setup > Purchasing > Line Types
Screen - Line Types
20. Define Document Types
(N) Setup > Purchasing > Document Types
Screen - Document Types
21. Look Up Codes (N) Setup > Purchasing > Look Up Codes
Screen - Purchasing Options
Oracle Purchasing application uses lookup codes to define the list of Quick Pick
values for Quick Picks throughout the system. You can customize your Oracle
Purchasing application for certain fields by adding your own codes to those
initially provided. These lookup codes are used for reference purpose only. Few
default Reports does have these Lookup Codes as one of the Report Parameters.
Assign the Inactive Date as & when any of the Lookup code is not to be used.
Ensure that the Displayed Value and the Description of the Lookup Code is self-
explanatory.
22. Profile Options
(N) System Administration Responsibility > Profiles > System Profiles
23. Open Periods
(N) Setup > Financials > Accounting > Control Purchasing Periods
Description: Open accounting periods to record purchasing activity. Your Oracle Purchasing application lets you create journal entries only for transactions you enter in an open purchasing period. You also need to open your purchasing periods to create correct ‘receipt accrual’ journal entries in your General Ledger, only if the Accrual Option is Perpetual. Use Control Purchasing Periods form to open or close in your Oracle Purchasing application.
Setup > Accounting Close Cycle >Inventory Accounting Periods
We need to open an accounting period to enter transactions in Oracle Inventory. Accounting Periods are defined in Oracle General Ledger and then opened in Oracle Inventory using the Open Accounting Periods form. Oracle Inventory allows to have multiple periods open at any given time.
24. Define Categories
(N) Setup > Item > Categories > Category Codes
Screen - Find Categories
A category is a logical classification of your items.
25. Define Category Set
(N) Setup > Items > Categories > Category Sets
Screen - Category Sets
A category set is a set or group of categories.
Each functional area viz. Purchasing, Inventory, Costing, Order entry can have a
separate default Category set.
26. Define Items
(N) Items > Item Master
Screen - Items
Sunday, May 10, 2009
Oracle Purchasing Terminologies
Terms used in the conventional purchasing system and as referred in Oracle Purchasing may be different. A brief explanation of the ‘Oracle Purchasing’ terms vis-à-vis the existing terminology is provided the following paragraphs. These terms are extensively used in documenting the ‘Purchasing - To Be’ flows and it is recommended that the various users of this system get acquainted with the same.
Requestor: Any Employee who requires specific items to meet his operational needs. Requestor may or may not have the system access to enter the on-line requisitions. Requestor with no computer access will give their requisitions manually on pre-printed requisition form to the requisition ‘Preparer’ within the concerned department.
Preparer: Employee in a department with the responsibility of entering Purchase Requisitions in the system.
Approver: Employee with the responsibility and authority of approving the requisition and / or the Quotation Analysis Document and / or the Purchase Orders.
Buyer: Employee in the Purchase Department with the responsibility of entering the Requests for Quotation, the Quotations received from the Supplier and the Purchase Orders in the new system.
Requisition: Synonym for ‘Indent’.
Request For Quotation (RFQ): Synonym for ‘Inquiry’. RFQs are sent to the vendors, requesting them for their quotations for the items / services required to be purchased.
Quotation: Quotations are the ‘Vendor Offers’ for the required items / services.
Quotation Analysis: It is a ‘Comparative Statement of Quotations’.
Standard Purchase Order: Standard Purchase Orders are created for purchase of various items / services where details such as the quantity to be purchased and the negotiated costs.
Blanket Purchase Agreement: Blanket purchase agreements are signed with the vendor for the supply of goods / services over a period. Such agreements can be used when details of the goods / services you plan to buy from a specific supplier in a period are known, but you do not yet know the details of your delivery schedules. They can also be used to specify negotiated prices for your items before actually buying them.
Blanket Release: You can issue a Blanket Release against a Blanket Purchase Agreement to place the actual order with the vendor. The Releases should be within the Blanket Agreement effectivity dates.
Planned Purchase Order: It is a long term agreement committing to buy items / services from a single source. The tentative delivery schedule is given to the vendor along with other details like quantities and estimated costs.
Schedule Release: This document is issued to the vendor against a Planned Purchase Order to place the actual order. This document will confirm the specific quantity and delivery date to the vendor.
Contract Purchase Agreements: Contract Purchase Agreements may be entered into with suppliers to agree on specific terms and conditions without indicating the goods or services that will actually be purchased. Standard Purchase Orders can be issued at a later date referencing such Contracts.
Requestor: Any Employee who requires specific items to meet his operational needs. Requestor may or may not have the system access to enter the on-line requisitions. Requestor with no computer access will give their requisitions manually on pre-printed requisition form to the requisition ‘Preparer’ within the concerned department.
Preparer: Employee in a department with the responsibility of entering Purchase Requisitions in the system.
Approver: Employee with the responsibility and authority of approving the requisition and / or the Quotation Analysis Document and / or the Purchase Orders.
Buyer: Employee in the Purchase Department with the responsibility of entering the Requests for Quotation, the Quotations received from the Supplier and the Purchase Orders in the new system.
Requisition: Synonym for ‘Indent’.
Request For Quotation (RFQ): Synonym for ‘Inquiry’. RFQs are sent to the vendors, requesting them for their quotations for the items / services required to be purchased.
Quotation: Quotations are the ‘Vendor Offers’ for the required items / services.
Quotation Analysis: It is a ‘Comparative Statement of Quotations’.
Standard Purchase Order: Standard Purchase Orders are created for purchase of various items / services where details such as the quantity to be purchased and the negotiated costs.
Blanket Purchase Agreement: Blanket purchase agreements are signed with the vendor for the supply of goods / services over a period. Such agreements can be used when details of the goods / services you plan to buy from a specific supplier in a period are known, but you do not yet know the details of your delivery schedules. They can also be used to specify negotiated prices for your items before actually buying them.
Blanket Release: You can issue a Blanket Release against a Blanket Purchase Agreement to place the actual order with the vendor. The Releases should be within the Blanket Agreement effectivity dates.
Planned Purchase Order: It is a long term agreement committing to buy items / services from a single source. The tentative delivery schedule is given to the vendor along with other details like quantities and estimated costs.
Schedule Release: This document is issued to the vendor against a Planned Purchase Order to place the actual order. This document will confirm the specific quantity and delivery date to the vendor.
Contract Purchase Agreements: Contract Purchase Agreements may be entered into with suppliers to agree on specific terms and conditions without indicating the goods or services that will actually be purchased. Standard Purchase Orders can be issued at a later date referencing such Contracts.
Purchasing Cycle
Purchasing Cycle:
Requisitions: Requisitions generated by various departments of your organization. They basically say that ‘I WANT THIS ITEM’ mentioning the item quantity and required date
Request for Quotation: The purchasing person sends the requirement to various suppliers giving details of the item and can also specify own terms and conditions such as payment terms, price etc.
Quotations: The Supplier responds to the RFQ and sends their quotations mentioning details of the item and all their terms and conditions regarding payment terms, discount, delivery schedules, etc.
Purchase Orders: The quotations received from various suppliers are compared and PO made for them in which all the terms and conditions of the firm are mentioned as regards to Payment, price, etc.
Receiving Goods: Suppliers ship the goods, which are received in your organization
Payments: After clearance from the receiving department about the receipt of goods, payments are made to the suppliers.
Close the PO: After the items are received, payments made you can close the PO.
Purchasing Requirements
• Item
• Quantity
• Ship to Address
• Bill to Address
• Delivery Schedules
• Terms and Conditions
• PO Numbering
• Approval Authority
• Supplier
• Accounts
Tuesday, April 28, 2009
E-Business Suite Implementation Stages
Whatever is the nature of the project we have different teams working towards a same goal (question of who is doing what). Each project goes through several stages: from gathering business requirements to production go live (question of when). In this process we go through a number of testing cycles to keep the progress in check.
These questions of who, what and when drives the demand for number of instances in eBusiness Suite and when they are needed. Typically go through the following process (Simplified) before we go live.
These questions of who, what and when drives the demand for number of instances in eBusiness Suite and when they are needed. Typically go through the following process (Simplified) before we go live.
Wednesday, April 22, 2009
Multi-Org Functionality
Introduced as Standard functionality in Release 10.7, Multi-Org is a key component of Oracle E-Business Suite:
1. Provides Secure access to different organizations of the enterprise
2. Supports multiple organizations of the enterprise structure in a single database.
In Release 11i, an individual Operating Unit is assigned to an
individual application Responsibility.
To see and work with data that is relevant to a specific
Operating Unit, users choose the appropriate Responsibility
after logging on to Oracle Applications.
Operating Unit
In the applications of the E-Business Suite that use Multi-Org
functionality, an Operating Unit is the primary organization unit
through which you secure transaction data, but also create, process,
and report on financial applications data.
An Operating Unit can be used to model an autonomous business unit
that performs one or more business activities and creates transactions
with financial impact.
Organizations
In general, an organization can be a company, department, division,
cost center, or virtually any other organizational unit within a business.
The organizational units relevant to Multi-Org in the E-Business Suite
are defined and stored using the Oracle Human Resources (HR) application.
Organizations are assigned classifications that determine their type and use.
These classifications include "Business Group", "GRE/Legal Entity",
"Operating Unit", "Inventory Organization", and "HR Organization".
The organizations described below are the cornerstones for securing
transactions and modeling an enterprise in the Oracle E-Business Suite.
How the user assembles these building blocks to logically model the
enterprise dictates the permitted interaction of the organizational
units and the flow of transactions between them.
Business Group
The purpose of the Business Group is to partition human resource
information.
The Business Group is the highest level in an organization structure
hierarchy in the E-Business Suite.
You can use the Business Group to model the consolidated enterprise
or a major division of a company that is an employer.
HR Organization, GRE/Legal Entity in Oracle Human Resources
The HR Organization classification is applied to the organizations to
which the user assigns employees.
This includes Business Groups, and in the United States it is also
applied to organizations of type "GRE"(Government Reporting Entities)
The GRE in the Oracle Human Resources products is the same organization
as the Legal Entity that appears in the Oracle Financials products.
The GRE represents the real-world legal entity that pays employees,
withholds their taxes, and provides reports on various matters
concerning them to government agencies.
In the Financial Applications of the E-Business Suite the Legal
Entity appears as GRE/Legal Entity when the Oracle Human Resources
application is installed.
Legal Entity in Oracle Financials
The Legal Entity represents a legal company for which the user
prepares fiscal or tax reports.
Tax identifiers and other relevant information are assigned to
this entity.
The GRE/Legal Entity organization classification in the financial
applications is used primarily for Cross-Organization Reporting for
selected reports in Release 11i of the E-Business Suite.
Operating Unit
The Operating Unit is the organization unit through which you create,
process, report on, and secure financial applications data.
Inventory Organization
The Inventory Organization is an organization for which you track
inventory transactions and balances.
Set of Books
In the E-Business Suite, a Set of Books is the financial reporting
entity that secures journal entries and account balances within the
Oracle General Ledger application.
It is neither an organization nor an organization classification in
the context of Multi-Org.
Generally, a Set of Books is used to represent a legal entity or a
group of legal entities.
Each Set of Books may have a different chart of accounts structure,
calendar and functional currency.
Organization Structure in Oracle Applications
It is the relationship of a Set of Books, Legal Entity, Operating Unit
and Inventory Organization that defines what is referred to as a Financial Organization Hierarchy in the Oracle E-Business Suite.
Points to be taken care:-
1. Business Group is the highest level of the structure and has no
accounting impact.
Legal Entities,Operating Units and Inventory Organization belong
to a single Business Group.
The Business Group also determines which employees will be available
to the Set of Books and Operating Units related to the Business
Group.
2. A Set of Books is the highest level that impacts Accounting.
A Set of books is associated with a single Business Group, but
mutliple Set of Books may be associated with a single Business
Group.
3. Legal Entities are associated with a Set of Books.
One or more Legal Entities may be associated with a single
Set of Books, and multiple Legal Entities may be associated
with a single Business Group.
4. Operating Units belong to a Legal Entity. One or more
Operating Units may be associated with a single Legal Entity.
5. Inventory Organizations belong to an Operating Unit.
An Inventory Organization can serve multiple Operating Units
within the same Set of Books. Inventory Organizations can be
associated with any Operating Unit(s) within the same Set of
Books. The relationship between Inventory Organizations and
a Set of Books is financial (creation of requisitions and
replenishment of supplies). For example, requisition transactions
are created against an Inventory Organization, which then have a
financial impact in the Set of Books.
MULTI-ORG
The following are the summarized steps for implementing Multi-Org
in Oracle Applications or when converting from a Non Multi-Org
environment to a Multi-Org environment.
Step-1.Develop an Organization Structure.
A successful implementation of Multi-Org begins with defining
your organizational structure in the multi-level hierarchy used
in Oracle Applications. The levels include:
• Business Group
• Set of Books
• Legal Entity
• Operating Unit
• Inventory Organizations
Step-2.Define Set of Books.
After determining your accounting calendar, currency and chart
of accounts structure, define all necessary Sets of Books.
If your enterprise structure will require multiple Business Groups,
you should define each Set of Books before Business Groups.
Step-3.Define Locations.
After determining your accounting calendar, currency and
chart of accounts structure, define all necessary Sets of Books.
If your enterprise structure will require multiple Business
Groups, you should define each Set of Books before Business Groups.
Step-4.Define Business Group(Optional)
You should define all your Business Groups before defining
any other type of organization. You must have at least
one Business Group. For fresh installations, Oracle Applications
provide one pre-seeded Business Group, "Setup Business
Group".
You can define additional Business Groups as needed for your
enterprise. We recommend that you modify the pre-defined Business
Group instead of creating a new one. If you decide to define a new
Business Group, instead of modifying the pre-defined Business Group,
then you need to set the "HR: Business Group" profile option at the
Responsibility level for the new Business Group. Oracle Human
Resources automatically creates a security profile with the Business
Group name when you define a new Business Group.
Step-5.Associate Responsibilities with Business Groups(Optional)
If you have multiple Business Groups, or if you do not choose to
use the default Business Group provided by Oracle Applications,
you must associate each Responsibility to one and only one Business
Group. If you are upgrading to Multi-Org, you must also associate
previously created Responsibilities to the appropriate Business Group.
You associate a Business Group with a Responsibility via the
"HR: Business Group" system profile option.
Step-6.Define Organizations
Define all your other organizations, i.e. Legal Entities, Operating
Units, and Inventory Organizations.
You can perform this step and the next step
(Define Organization Relationships) at the same time. The steps
are presented separately to emphasize the difference
between the organizational entity and the role it plays in your
organizational structure.
Step-7.Define Organization Relationships
Define your organization relationships by assigning classifications
to each organization.
Attributes of certain classifications relate organizations and the
roles they play.
You can classify an organization as any combination of Legal Entity,
Operating Unit, and Inventory Organization.
Specify your organization classifications in the following order:
1. Legal entities. Attach the Legal Entity to a Set of Books.
2. Operating units. Attach the Operating Unit to the correct Legal
Entity and Set of Books.
3. Inventory organizations. Attach the Inventory Organization to the
correct Operating Unit, Legal Entity and Set of Books.
If you have more than one Business Group, change to the Responsibility
associated with the desired Business Group and continues defining your
organization classification.
Step-8.Define Responsibilities
Define your Responsibilities for each Operating Unit by application.
Carefully consider your naming conventions for the Responsibility
names in a Multi-Org environment. It is a good idea to use
abbreviations of the business function and the organization
name to uniquely identify the purpose of the Responsibility.
Examples of naming conventions are Payables Manager IND
or IND Receivables Super User.
Step-9.Set MO: Operating Unit Profile Option
Set the Oracle Applications system profile option "MO: Operating Unit"
to link each Operating Unit to a Responsibility.
You must also define the default Operating Unit by setting the
"MO: Operating Unit" profile option at the site level in the system
profile option hierarchy. If this is a fresh installation, the
default Operating Unit can be any Operating Unit you have
defined. If this is an existing installation, you should assign
as the default Operating Unit the Operating Unit to which all
existing data should belong.
Step-10.Convert to Multi-Org Architecture
One of the options in adadmin is to convert to Multi-Org
architecture. Choosing this option will enable the Multi-Org
Support feature as well as add Operating Unit context to all
existing data. This process will also replicate seed data to all
Operating Units that have been defined.
Before your database administrator runs this step, you must have
defined an Operating Unit and set the site-level profile option
"MO: Operating Unit" to use your new Operating Unit. This profile
option tells adadmin what Operating Unit it should use when
converting your existing data. If you define additional Operating
Units, the seed data will be replicated for all Operating Units.
Once you have converted to Multi-Org Architecture, the Convert to
Multiple Organization Architecture option does not display on the
menu as you have already Multi-Org installed in your database.
Step-11.Verify Order Management System Parameters
If you have different item validation organizations for your Operating
Units, use Order Management "System Options" window to set the necessary characteristics for each Operating Unit. This allows Order
Management and Shipping Execution to default the tax code and
revenue account information correctly. The "Item Validation
Organization" setting indicates the Oracle Manufacturing
organizations that items are validated against. All transactable
items must be defined in this organization. This setting was
previously controlled through the profile option "OM: Item
Validation Organization".
Step-12.Set Profile Options specific to Operating Unit
Some profile options, including "AR: Receipt Batch Source" and
"AR: Transaction Batch Source", reference data that is secured
by Operating Unit. You must set these profile options at the
Responsibility level. You should choose a value corresponding
to the Operating Unit of the Responsibility.
Step-13.Define Inventory Organization Security
With Inventory Organization security you can restrict Inventory
Organization access to specific Responsibilities. You may want
to restrict your manufacturing users to certain organizations
according to your organizational hierarchy.
Step-14.Implement the Application
After the steps above are complete, go into each Operating Unit
and set up the Oracle Applications products. The following products
must be set up for each Operating Unit in which you intend to
perform the functions:
• Oracle Cash Management
• Oracle Order Management and Shipping Execution
• Oracle Payables
• Oracle Projects
• Oracle Purchasing
• Oracle Property Manager
• Oracle Receivables
• Oracle Release Accounting
• Oracle Sales Compensation
• Oracle Sales and Marketing
• Oracle Service
• European Localizations
• Latin America Localizations
• Regional Localizations
Oracle Fixed Assets, Oracle General Ledger, Oracle Inventory,
and the rest of the Oracle Manufacturing products need to be
set up only once for the installation, not once for each
Operating Unit.
Step-15.Secure Balancing Segment Values by Legal Entity(Optional)
Create your security rules to secure data entry and inquiry for
balancing segment values in each Legal Entity.
Assign your security rule(s) to all Responsibilities associated
with the Legal Entity’s Operating Units. If you need to further
secure balancing segment values for each Operating Unit of a Legal
Entity, you can define additional rules and assign them to
all Responsibilities associated with the relevant Operating Units.
Step-16.Run the Multi-Org Validation Report(Recommended)
After you have implemented Multi-Org, run the Setup Validation
Report to identify any setup problems. Some of the error conditions
that the report finds may be optionally deleted by running this
report, while others require that you change your setup. All
suggested changes can be optionally confirmed so that you may retain
your implementation even if it fails validation.
Optional Steps
After you have implemented Multi-Org and run the Setup
Validation Report, you have the option to set up the
following data that may be necessary depending on
your business and regulatory requirements:
• Document sequencing rules
• Intercompany Selling/Shipping relationships
• Cross-Organization Reporting infrastructure.
You also may need to set up Domain Conflicts to maximize the
concurrency of programs.
Relationship between the Organizational units of E-Business
Enterprises:
Multi-Org
1. Provides Secure access to different organizations of the enterprise
2. Supports multiple organizations of the enterprise structure in a single database.
In Release 11i, an individual Operating Unit is assigned to an
individual application Responsibility.
To see and work with data that is relevant to a specific
Operating Unit, users choose the appropriate Responsibility
after logging on to Oracle Applications.
Operating Unit
In the applications of the E-Business Suite that use Multi-Org
functionality, an Operating Unit is the primary organization unit
through which you secure transaction data, but also create, process,
and report on financial applications data.
An Operating Unit can be used to model an autonomous business unit
that performs one or more business activities and creates transactions
with financial impact.
Organizations
In general, an organization can be a company, department, division,
cost center, or virtually any other organizational unit within a business.
The organizational units relevant to Multi-Org in the E-Business Suite
are defined and stored using the Oracle Human Resources (HR) application.
Organizations are assigned classifications that determine their type and use.
These classifications include "Business Group", "GRE/Legal Entity",
"Operating Unit", "Inventory Organization", and "HR Organization".
The organizations described below are the cornerstones for securing
transactions and modeling an enterprise in the Oracle E-Business Suite.
How the user assembles these building blocks to logically model the
enterprise dictates the permitted interaction of the organizational
units and the flow of transactions between them.
Business Group
The purpose of the Business Group is to partition human resource
information.
The Business Group is the highest level in an organization structure
hierarchy in the E-Business Suite.
You can use the Business Group to model the consolidated enterprise
or a major division of a company that is an employer.
HR Organization, GRE/Legal Entity in Oracle Human Resources
The HR Organization classification is applied to the organizations to
which the user assigns employees.
This includes Business Groups, and in the United States it is also
applied to organizations of type "GRE"(Government Reporting Entities)
The GRE in the Oracle Human Resources products is the same organization
as the Legal Entity that appears in the Oracle Financials products.
The GRE represents the real-world legal entity that pays employees,
withholds their taxes, and provides reports on various matters
concerning them to government agencies.
In the Financial Applications of the E-Business Suite the Legal
Entity appears as GRE/Legal Entity when the Oracle Human Resources
application is installed.
Legal Entity in Oracle Financials
The Legal Entity represents a legal company for which the user
prepares fiscal or tax reports.
Tax identifiers and other relevant information are assigned to
this entity.
The GRE/Legal Entity organization classification in the financial
applications is used primarily for Cross-Organization Reporting for
selected reports in Release 11i of the E-Business Suite.
Operating Unit
The Operating Unit is the organization unit through which you create,
process, report on, and secure financial applications data.
Inventory Organization
The Inventory Organization is an organization for which you track
inventory transactions and balances.
Set of Books
In the E-Business Suite, a Set of Books is the financial reporting
entity that secures journal entries and account balances within the
Oracle General Ledger application.
It is neither an organization nor an organization classification in
the context of Multi-Org.
Generally, a Set of Books is used to represent a legal entity or a
group of legal entities.
Each Set of Books may have a different chart of accounts structure,
calendar and functional currency.
Organization Structure in Oracle Applications
It is the relationship of a Set of Books, Legal Entity, Operating Unit
and Inventory Organization that defines what is referred to as a Financial Organization Hierarchy in the Oracle E-Business Suite.
Points to be taken care:-
1. Business Group is the highest level of the structure and has no
accounting impact.
Legal Entities,Operating Units and Inventory Organization belong
to a single Business Group.
The Business Group also determines which employees will be available
to the Set of Books and Operating Units related to the Business
Group.
2. A Set of Books is the highest level that impacts Accounting.
A Set of books is associated with a single Business Group, but
mutliple Set of Books may be associated with a single Business
Group.
3. Legal Entities are associated with a Set of Books.
One or more Legal Entities may be associated with a single
Set of Books, and multiple Legal Entities may be associated
with a single Business Group.
4. Operating Units belong to a Legal Entity. One or more
Operating Units may be associated with a single Legal Entity.
5. Inventory Organizations belong to an Operating Unit.
An Inventory Organization can serve multiple Operating Units
within the same Set of Books. Inventory Organizations can be
associated with any Operating Unit(s) within the same Set of
Books. The relationship between Inventory Organizations and
a Set of Books is financial (creation of requisitions and
replenishment of supplies). For example, requisition transactions
are created against an Inventory Organization, which then have a
financial impact in the Set of Books.
MULTI-ORG
The following are the summarized steps for implementing Multi-Org
in Oracle Applications or when converting from a Non Multi-Org
environment to a Multi-Org environment.
Step-1.Develop an Organization Structure.
A successful implementation of Multi-Org begins with defining
your organizational structure in the multi-level hierarchy used
in Oracle Applications. The levels include:
• Business Group
• Set of Books
• Legal Entity
• Operating Unit
• Inventory Organizations
Step-2.Define Set of Books.
After determining your accounting calendar, currency and chart
of accounts structure, define all necessary Sets of Books.
If your enterprise structure will require multiple Business Groups,
you should define each Set of Books before Business Groups.
Step-3.Define Locations.
After determining your accounting calendar, currency and
chart of accounts structure, define all necessary Sets of Books.
If your enterprise structure will require multiple Business
Groups, you should define each Set of Books before Business Groups.
Step-4.Define Business Group(Optional)
You should define all your Business Groups before defining
any other type of organization. You must have at least
one Business Group. For fresh installations, Oracle Applications
provide one pre-seeded Business Group, "Setup Business
Group".
You can define additional Business Groups as needed for your
enterprise. We recommend that you modify the pre-defined Business
Group instead of creating a new one. If you decide to define a new
Business Group, instead of modifying the pre-defined Business Group,
then you need to set the "HR: Business Group" profile option at the
Responsibility level for the new Business Group. Oracle Human
Resources automatically creates a security profile with the Business
Group name when you define a new Business Group.
Step-5.Associate Responsibilities with Business Groups(Optional)
If you have multiple Business Groups, or if you do not choose to
use the default Business Group provided by Oracle Applications,
you must associate each Responsibility to one and only one Business
Group. If you are upgrading to Multi-Org, you must also associate
previously created Responsibilities to the appropriate Business Group.
You associate a Business Group with a Responsibility via the
"HR: Business Group" system profile option.
Step-6.Define Organizations
Define all your other organizations, i.e. Legal Entities, Operating
Units, and Inventory Organizations.
You can perform this step and the next step
(Define Organization Relationships) at the same time. The steps
are presented separately to emphasize the difference
between the organizational entity and the role it plays in your
organizational structure.
Step-7.Define Organization Relationships
Define your organization relationships by assigning classifications
to each organization.
Attributes of certain classifications relate organizations and the
roles they play.
You can classify an organization as any combination of Legal Entity,
Operating Unit, and Inventory Organization.
Specify your organization classifications in the following order:
1. Legal entities. Attach the Legal Entity to a Set of Books.
2. Operating units. Attach the Operating Unit to the correct Legal
Entity and Set of Books.
3. Inventory organizations. Attach the Inventory Organization to the
correct Operating Unit, Legal Entity and Set of Books.
If you have more than one Business Group, change to the Responsibility
associated with the desired Business Group and continues defining your
organization classification.
Step-8.Define Responsibilities
Define your Responsibilities for each Operating Unit by application.
Carefully consider your naming conventions for the Responsibility
names in a Multi-Org environment. It is a good idea to use
abbreviations of the business function and the organization
name to uniquely identify the purpose of the Responsibility.
Examples of naming conventions are Payables Manager IND
or IND Receivables Super User.
Step-9.Set MO: Operating Unit Profile Option
Set the Oracle Applications system profile option "MO: Operating Unit"
to link each Operating Unit to a Responsibility.
You must also define the default Operating Unit by setting the
"MO: Operating Unit" profile option at the site level in the system
profile option hierarchy. If this is a fresh installation, the
default Operating Unit can be any Operating Unit you have
defined. If this is an existing installation, you should assign
as the default Operating Unit the Operating Unit to which all
existing data should belong.
Step-10.Convert to Multi-Org Architecture
One of the options in adadmin is to convert to Multi-Org
architecture. Choosing this option will enable the Multi-Org
Support feature as well as add Operating Unit context to all
existing data. This process will also replicate seed data to all
Operating Units that have been defined.
Before your database administrator runs this step, you must have
defined an Operating Unit and set the site-level profile option
"MO: Operating Unit" to use your new Operating Unit. This profile
option tells adadmin what Operating Unit it should use when
converting your existing data. If you define additional Operating
Units, the seed data will be replicated for all Operating Units.
Once you have converted to Multi-Org Architecture, the Convert to
Multiple Organization Architecture option does not display on the
menu as you have already Multi-Org installed in your database.
Step-11.Verify Order Management System Parameters
If you have different item validation organizations for your Operating
Units, use Order Management "System Options" window to set the necessary characteristics for each Operating Unit. This allows Order
Management and Shipping Execution to default the tax code and
revenue account information correctly. The "Item Validation
Organization" setting indicates the Oracle Manufacturing
organizations that items are validated against. All transactable
items must be defined in this organization. This setting was
previously controlled through the profile option "OM: Item
Validation Organization".
Step-12.Set Profile Options specific to Operating Unit
Some profile options, including "AR: Receipt Batch Source" and
"AR: Transaction Batch Source", reference data that is secured
by Operating Unit. You must set these profile options at the
Responsibility level. You should choose a value corresponding
to the Operating Unit of the Responsibility.
Step-13.Define Inventory Organization Security
With Inventory Organization security you can restrict Inventory
Organization access to specific Responsibilities. You may want
to restrict your manufacturing users to certain organizations
according to your organizational hierarchy.
Step-14.Implement the Application
After the steps above are complete, go into each Operating Unit
and set up the Oracle Applications products. The following products
must be set up for each Operating Unit in which you intend to
perform the functions:
• Oracle Cash Management
• Oracle Order Management and Shipping Execution
• Oracle Payables
• Oracle Projects
• Oracle Purchasing
• Oracle Property Manager
• Oracle Receivables
• Oracle Release Accounting
• Oracle Sales Compensation
• Oracle Sales and Marketing
• Oracle Service
• European Localizations
• Latin America Localizations
• Regional Localizations
Oracle Fixed Assets, Oracle General Ledger, Oracle Inventory,
and the rest of the Oracle Manufacturing products need to be
set up only once for the installation, not once for each
Operating Unit.
Step-15.Secure Balancing Segment Values by Legal Entity(Optional)
Create your security rules to secure data entry and inquiry for
balancing segment values in each Legal Entity.
Assign your security rule(s) to all Responsibilities associated
with the Legal Entity’s Operating Units. If you need to further
secure balancing segment values for each Operating Unit of a Legal
Entity, you can define additional rules and assign them to
all Responsibilities associated with the relevant Operating Units.
Step-16.Run the Multi-Org Validation Report(Recommended)
After you have implemented Multi-Org, run the Setup Validation
Report to identify any setup problems. Some of the error conditions
that the report finds may be optionally deleted by running this
report, while others require that you change your setup. All
suggested changes can be optionally confirmed so that you may retain
your implementation even if it fails validation.
Optional Steps
After you have implemented Multi-Org and run the Setup
Validation Report, you have the option to set up the
following data that may be necessary depending on
your business and regulatory requirements:
• Document sequencing rules
• Intercompany Selling/Shipping relationships
• Cross-Organization Reporting infrastructure.
You also may need to set up Domain Conflicts to maximize the
concurrency of programs.
Relationship between the Organizational units of E-Business
Enterprises:
Multi-Org
Important Profile Options as part of Integration
You must set up the following Profile Options:
1.%HR%USER%TYPE% or HR: User Type
2.%HR%SECURITY%PROFILE% or HR: Security Profile and the
3.%HR%BUSINESS%GROUP% or HR: Business Group
4.%GL%SET%OF%BOOKS% or GL Set of books
5.%MO%OPERATING%UNIT% or MO: Operating Unit
6.%MO%SECURITY%PROFILE% or MO: Security Profile
Switch to SYSTEM ADMINISTRATOR Responsibility and set the above Profile Options.
1.%HR%USER%TYPE% or HR: User Type
2.%HR%SECURITY%PROFILE% or HR: Security Profile and the
3.%HR%BUSINESS%GROUP% or HR: Business Group
4.%GL%SET%OF%BOOKS% or GL Set of books
5.%MO%OPERATING%UNIT% or MO: Operating Unit
6.%MO%SECURITY%PROFILE% or MO: Security Profile
Switch to SYSTEM ADMINISTRATOR Responsibility and set the above Profile Options.
Tuesday, April 21, 2009
Profile Options in Oracle Applications
Profile options provide flexibility to Oracle Apps. They are a key component of Oracle Applications.
For the learners of Oracle Applications, understanding Profile Options is mandatory.
Profile Option
The Profile Option acts like a Global Variable in Oracle.
Why does Oracle Provide Profile Options?
These are provided to keep the application flexible. The business
rules in various countries and various companies can be different.
Hence the profile options are delivered by Oracle in such a manner
avoid hard coding of logic, and to let the implementation team at
site decide the values of those variables.
For the learners of Oracle Applications, understanding Profile Options is mandatory.
Profile Option
The Profile Option acts like a Global Variable in Oracle.
Why does Oracle Provide Profile Options?
These are provided to keep the application flexible. The business
rules in various countries and various companies can be different.
Hence the profile options are delivered by Oracle in such a manner
avoid hard coding of logic, and to let the implementation team at
site decide the values of those variables.
What happens when you login to Apps
Firstly and surely there is a URL for Oracle Applications that is structured possibily in below format, possibly in below format, although it can vary from version of apps.
http://machinename:portnumber/OA_HTML/US/ICXINDEX.htm
http://machinename:portnumber /oa_servlets/AppsLogin
When you join an Oracle Applications development team for an employer, you will first be given URL of the development environment.
In any Oracle Applications Implementation project (assuming it has gone live, there are minimum of three environments, each with three different URL's and different database instances.
These are:-
1.Development Instance
2.Testing Instance
3.Production Instance
As a techie, you will be given URL, User Name and Password of the development environment.
What happens when you login?
1.Your login gets authenticated against the table named fnd_user for
your username and password. This is called user definition screen.
Only System Administrator have access to this. The screen below is
where username and password is defined.
2.As you can see below, this username=MANNAMALAI is attached to
responsibilities. It is this assignment to the responsibility that
controls what a logged in person can do and can't do. In layman's
words, a responsibility is a group of menu.
http://machinename:portnumber/OA_HTML/US/ICXINDEX.htm
http://machinename:portnumber /oa_servlets/AppsLogin
When you join an Oracle Applications development team for an employer, you will first be given URL of the development environment.
In any Oracle Applications Implementation project (assuming it has gone live, there are minimum of three environments, each with three different URL's and different database instances.
These are:-
1.Development Instance
2.Testing Instance
3.Production Instance
As a techie, you will be given URL, User Name and Password of the development environment.
What happens when you login?
1.Your login gets authenticated against the table named fnd_user for
your username and password. This is called user definition screen.
Only System Administrator have access to this. The screen below is
where username and password is defined.
2.As you can see below, this username=MANNAMALAI is attached to
responsibilities. It is this assignment to the responsibility that
controls what a logged in person can do and can't do. In layman's
words, a responsibility is a group of menu.
Thursday, April 16, 2009
My Favorite Author - Robert T. Kiyosaki
Robert T. Kiyosaki
The main reason people struggle financially is because they spent years in school but learned nothing about money. The result is, people learn to work for money... but never learn to have money work for them.
Born and raised in Hawaii, Robert is fourth-generation Japanese American. He comes from a prominent family of educators. His father was the head of education for the State of Hawaii. "After high school, Robert was educated in New York and upon graduation, he joined the U. S. Marine Corps and went to Vietnam as an officer and a helicopter gunship pilot.
Returning from the war, Robert's business career began. In 1977 he founded a company that brought to the market the first nylon and Velcro "surfer" wallets, which grew into a multi-million dollar worldwide product. He and his products were featured in Runner's World, Gentleman's Quarterly, Success Magazine, Newsweek, and even Playboy.
Leaving the business world, he co-founded in 1985, an international education company that operated in seven countries, teaching business and investing to tens of thousands of graduates.
Retiring at age 47, Robert does what he enjoys most... investing. Concerned about the growing gap between the haves and have nots, Robert created the board game CASHFLOW, which teaches the game of money, here before only known by the rich.
Although Robert's business is real estate and developing small cap companies, his true love and passion is teaching. He has shared the speaking stage with such greats as Og Mandino, Zig Ziglar, and Anthony Robbins. Robert Kiyosaki's message is clear. "Take responsibility for your finances or take orders all your life. You're either a master of money or a slave to it." Robert holds classes that last from 1 hour to 3 days teaching people about the secrets of the rich. Although his subjects run from investing for high returns and low risk; to teaching your children to be rich; to starting companies and selling them; he has one solid earth shaking message. And that message is, Awaken The Financial Genius that lies within you. Your genius is waiting to come out.
This is what world famous speaker and author Anthony Robbins says about Robert's work.
"Robert Kiyosaki's work in education is powerful, profound, and life changing. I salute his efforts and recommend him highly."
During this time of great economic change, Robert's message is priceless.
The main reason people struggle financially is because they spent years in school but learned nothing about money. The result is, people learn to work for money... but never learn to have money work for them.
Born and raised in Hawaii, Robert is fourth-generation Japanese American. He comes from a prominent family of educators. His father was the head of education for the State of Hawaii. "After high school, Robert was educated in New York and upon graduation, he joined the U. S. Marine Corps and went to Vietnam as an officer and a helicopter gunship pilot.
Returning from the war, Robert's business career began. In 1977 he founded a company that brought to the market the first nylon and Velcro "surfer" wallets, which grew into a multi-million dollar worldwide product. He and his products were featured in Runner's World, Gentleman's Quarterly, Success Magazine, Newsweek, and even Playboy.
Leaving the business world, he co-founded in 1985, an international education company that operated in seven countries, teaching business and investing to tens of thousands of graduates.
Retiring at age 47, Robert does what he enjoys most... investing. Concerned about the growing gap between the haves and have nots, Robert created the board game CASHFLOW, which teaches the game of money, here before only known by the rich.
Although Robert's business is real estate and developing small cap companies, his true love and passion is teaching. He has shared the speaking stage with such greats as Og Mandino, Zig Ziglar, and Anthony Robbins. Robert Kiyosaki's message is clear. "Take responsibility for your finances or take orders all your life. You're either a master of money or a slave to it." Robert holds classes that last from 1 hour to 3 days teaching people about the secrets of the rich. Although his subjects run from investing for high returns and low risk; to teaching your children to be rich; to starting companies and selling them; he has one solid earth shaking message. And that message is, Awaken The Financial Genius that lies within you. Your genius is waiting to come out.
This is what world famous speaker and author Anthony Robbins says about Robert's work.
"Robert Kiyosaki's work in education is powerful, profound, and life changing. I salute his efforts and recommend him highly."
During this time of great economic change, Robert's message is priceless.
Current Implementation Modules and Business Scenairo
1. Implemented GL,AP,AR,FA,INV,PO,OM,WMS for 2 Locations.
2. Implemented Oracle India Localization for 2 Locations- 1. Delhi 2. Hyderabad
3. As per client and business requirement we had 2 seperate Legal Entities,
Operating Units, Inventory Organization - All falling under one Business Group.
4. Functional Currency is INR which remains same for 2 Locations.
5. Also we had 2 Seperate Set of Books.
6. Primary Currency being USD.
2. Implemented Oracle India Localization for 2 Locations- 1. Delhi 2. Hyderabad
3. As per client and business requirement we had 2 seperate Legal Entities,
Operating Units, Inventory Organization - All falling under one Business Group.
4. Functional Currency is INR which remains same for 2 Locations.
5. Also we had 2 Seperate Set of Books.
6. Primary Currency being USD.
Wednesday, April 15, 2009
Currently working in India Localization (Trading Organization with 2 Operating Units)
Oracle India Localization (Version 11.5.9) and upgrade (Version 11.5.10.2 )
How to check the current India Localization Patchset level installed on the instance
The latest India Localization Patchset is IN60107 (Patch Number = 5498551)If the Patch Number 5498551 is applied, your current India Localization patchset is IN60107. This can be verified by running the below selectselect * from JAI_APPLIED_PATCHES where Patch_number = 5498551/
If the Patch Number 5498551 is not applied, the India Localization Patchset should be IN60106 or below.This can be checked by running the below statement:-select * from JA_IN_INSTALL_CHECK_INFO where name like '601%'/
Check the Current India Localization Patchset level installed on an Instance
India Localization mainly acts based on the Descriptive Flexfields (DFF's)
The DFF's attribute 1 to 5, 14 and 15 will be used by India Localization patch. If we have any data in that field we have to move it manually and check whether the data's were moved safe to other fields and then we can apply the patch. If we have not moved the data's from the appropriate field and if we apply India Localization Patch it will delete all the data in the fields 1 to 5, 14 and 15 and will use for India Localization.
This check is mandatory since India Localization patchset installation scripts will delete any previous registrations of attributes 1 to 5, 14 and 15 with Global Data Elements in the DFF's (AP_INVOICES, AP_INVOICE_DISTRIBUTION, FA_ADDITIONS, FA_MASS_ADDITIONS, FND_COMMON_LOOKUPS, MTL_SYSTEM_ITEMS, PER_ORGANIZATION, RCV_SHIPMENT_HEADERS, PO_LOOKUP_CODES)
How to check the current India Localization Patchset level installed on the instance
The latest India Localization Patchset is IN60107 (Patch Number = 5498551)If the Patch Number 5498551 is applied, your current India Localization patchset is IN60107. This can be verified by running the below selectselect * from JAI_APPLIED_PATCHES where Patch_number = 5498551/
If the Patch Number 5498551 is not applied, the India Localization Patchset should be IN60106 or below.This can be checked by running the below statement:-select * from JA_IN_INSTALL_CHECK_INFO where name like '601%'/
Check the Current India Localization Patchset level installed on an Instance
India Localization mainly acts based on the Descriptive Flexfields (DFF's)
The DFF's attribute 1 to 5, 14 and 15 will be used by India Localization patch. If we have any data in that field we have to move it manually and check whether the data's were moved safe to other fields and then we can apply the patch. If we have not moved the data's from the appropriate field and if we apply India Localization Patch it will delete all the data in the fields 1 to 5, 14 and 15 and will use for India Localization.
This check is mandatory since India Localization patchset installation scripts will delete any previous registrations of attributes 1 to 5, 14 and 15 with Global Data Elements in the DFF's (AP_INVOICES, AP_INVOICE_DISTRIBUTION, FA_ADDITIONS, FA_MASS_ADDITIONS, FND_COMMON_LOOKUPS, MTL_SYSTEM_ITEMS, PER_ORGANIZATION, RCV_SHIPMENT_HEADERS, PO_LOOKUP_CODES)
Subscribe to:
Posts (Atom)
