Multi - Org Functional Flow
Use a single installation of any Oracle Applications product to support any number of organizations, even if those organizations use different sets of books.
Support any number of legal entities within a single installation
Secure Access: You can assign users to particular organizations. This ensures accurate transactions in the correct operating unit.of Oracle Applications.
You can sell from one legal entity and ship from another, posting to each organization’s set of books.
You can enter purchase orders and assign for receipt any inventory organization that uses the same set of books.
You can support multiple organizations running any Oracle Applications product with a single installation. When you run any Oracle Applications product, you first choose an organization—either
implicitly by choosing a responsibility, or explicitly in a Choose Organization window. Each window and report then displays information for your organization only.
Each legal entity can have one or more balancing entities. An operating unit is associated with a legal entity. Information is secured by operating unit for these applications. Each user sees information only for their operating unit. To run any of these applications, you choose a responsibility associated with an
organization classified as an operating unit.
Legal Entities Post to a Set of Books Each organization classified as a legal entity identifies a set of books to post accounting transactions.
Operating Units Are Part of a Legal Entity Each organization classified as an operating unit is associated with a legal entity.
Inventory Organizations are Part of an Operating Unit Each organization classified as an inventory organization references an operating unit.
Inventory Organization Determines Items Available to Order Management The OM:Item Validation Organization profile option specifies the inventory organization that Order Management uses to validate items. Some inventory item attributes for Receivables and Order Management, including Tax Code and Sales Account, are specific to an operating unit or an accounting flexfield structure. Therefore, you
should define an item validation organization for each operating unit.
Inventory Organization Determines Items Available to Purchasing The inventory organization you specify in the financial options for each operating unit determines the items available in Purchasing. You can only choose an inventory organization that uses the same set of books as your operating unit.
Data Security You can limit users to information relevant to their organization. For example, you can limit access for order administration clerks to sales orders associated exclusively with their sales office.
Inventory Organization Security by Responsibility You can specify which inventory organizations are available to users in each responsibility. The Choose Inventory Organization window automatically limits available inventory organizations to those authorized for the current responsibility.
Responsibility Determines Operating Unit Your responsibility determines which operating unit you access when you use Oracle Applications. When you use Oracle Payables, Receivables, Order Management and Shipping Execution, Purchasing, Projects, and Sales Compensation you see information that is relevant to your operating unit. All transactions you create are automatically assigned to your operating unit.
Purchase and Receive Products Between Organizations Your purchase order operating unit and receiving inventory organization must share the same sets of books to receive against a purchase order.
Automatic Intercompany Sales Recognition Sales orders created and shipped from one legal entity to a different legal entity automatically generate an intercompany invoice to record a sale between the two organizations.
Posting Intercompany Invoices to Different Accounts You can define different accounts for Trade and Intercompany Cost of Goods Sold and Sales Revenue to eliminate intercompany profit.
These are the steps to follow when implementing the Multiple Organization support feature in Oracle Applications.
1. Develop the Organization Structure
2. Define Sets of Books
3. Define Locations
4. Define Business Groups (optional)
5. Associate Responsibilities with Business Groups
6. Define Organizations
7. Define Organization Relationships
8. Define Responsibilities
9. Set MO: Operating Unit Profile Option
10. Convert to Multiple Organization Architecture
11. Change Order Management Profile Option
12. Set Profile Options Specific to Operating Units
13. Define Inventory Organization Security (optional)
14. Implement the Applications Products
15. Secure Balancing Segment Values by Legal Entity (optional)
16. Run the Multi–Org Setup Validation Report (recommended)
17. Implement Document Sequencing (optional)
18. Define Intercompany Relations (optional)
19. Set Top Reporting Level Profile Option (optional)
20. Set Conflict Domains (optional)
Step 1 Develop the Organization Structure A successful implementation of Multiple Organization support in Oracle Applications depends primarily on defining your organizational structure in the multi–level hierarchy used by Oracle Applications. The levels are:
• Business groups
• Accounting sets of books
• Legal entities
• Operating units
• Inventory organizations
If your enterprise structure requires that you define a business group, you should define sets of books before business groups.
Step 3 Define Locations Oracle Applications products use locations for requisitions, receiving, shipping, billing, and employee assignments.
Step 4 Define Business Groups (optional) If you define a new business group instead of modifying the pre–defined business group, you need to set the 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.
You should define all your business groups before defining any other type of organization.
To define additional business groups:
1. Set the responsibility from which you define the organizations in the profile option HR: User Type to HR User, to get access to the Define Organizations window. This profile must be set for all responsibilities that use tables from Oracle Human Resources (for example, responsibilities used to define employees and
organizations).
2. Define all of your business groups at this step from a responsibility. Do not define any new organizations or organization hierarchies until you have associated each business group with a responsibility. You do this by setting the HR: Business Group profile option to the business groups for each responsibility.
3. After you have correctly associated business groups to responsibilities, you enter business group setup information, such as additional organization information and business group classifications, to create the organization structure.
4. After you have correctly associated your business groups with a responsibility, sign off and sign on again using the correct responsibility for the business group you want to define. For example, if you have a U.S. business group and a U.K. business group, select the responsibility attached to the U.S. business group to define the U.S. organization structure.
Note: Oracle Human Resources automatically creates a view all security profile with the business group name. This enables you to view all records for your business group.
Note: Oracle Human Resources allows you to use a single responsibility security model by enabling the Security Group. This allows you to access more than one business group from a responsibility. You should not use the single responsibility model in Multiple Organization products.
Step 5 Associate Responsibilities with Business Groups (optional)
Note: This section applies to you if you have multiple business groups, or if you do not choose to use the default business group provided by Oracle Applications.
If you have multiple business groups, you must associate each responsibility to one and only one business group. You associate a business group with a responsibility via the HR:Business Group system profile option. If you are upgrading to Multiple Organizations, you must also associate previously created responsibilities to the appropriate business group.
Step 6 Define Organizations
Use the Define Organization window to define all your 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.
_ To define legal entities, operating units, and inventory organizations:
1. Log in to the responsibility associated with the business group for which you are defining an organization.
2. Define a legal entity. It is then automatically attached to the correct business group.
3. Define operating units.
4. Define your inventory organizations for each operating unit that will have an inventory organization.
Note: Do not define the inventory parameters at this point.
5. If you have more than one business group, switch to the responsibility associated with the other business group and continue to define your organization structure.
Step 7 Define Organization Relationships Use the Define Organization window to define 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 organizations designated as legal entities to a set of books. You must also specify a location in the Define Organization window. Use the Define Location window to define locations for
your legal entities.
2. Operating units Attach the operating units to the correct set of books and legal entity.
3. Inventory organizations Attach the inventory organizations 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 other business group and continue defining your organization classification.
Classification Information Type Required Attributes
Business Group Business group information if Human Resources is installed. Otherwise, None.
Short Name, Employee/Applicant Numbering, Key Flexfield Structures, Default Legislation Code, and Currency
GRE/Legal Entity Legal Entity Accounting Set of Books, Location
Operating Unit Operating Unit Information Legal Entity, Set of Books
Inventory Organization Accounting Information Set of Books, Legal Entity, Operating Unit
Special Considerations for Inventory Organizations All the inventory organizations in the above chart have been set up with the minimal amount of information to enable them in the Multiple Organization environment. This minimal amount is detailed in the table below. If you plan to implement Oracle Inventory, you need to follow the setup procedures for that product.
For a standalone Oracle Purchasing installation (without Oracle
Inventory), you must specify the following minimum information:
1 Accounting information : Set of books, legal entity, operating unit
2 Receiving information : Three–character organization code,prefix serial (no dummy)
3 Inventory information : All required accounts
You must define the control options and account defaults for one inventory organization, the item master organization. Then you can easily assign items to other inventory organization without recreating all the item information. Use the Organization Parameter window to assign inventory organizations to the item master. The item master organization uses itself as the item master.
There is no functional or technical difference between the item master organization and other inventory organizations. However, we recommend that you limit the item master to just an item definition organization. If you set up new inventory organizations in the future, you can assign the new items to only the item master and the new inventory organization.
Step 8 Define Responsibilities Use the Define Responsibility window to define responsibilities for each operating unit by application. When you sign on to Oracle Applications, the responsibility you choose determines the data, forms, menus, reports, and concurrent programs you can access.
Step 9 Set MO: Operating Unit Profile Option Oracle Applications uses the profile option MO: Operating Unit to link an operating unit to a responsibility. You must set this profile option for
each responsibility.
After you choose your responsibility, there is an initialization routine that reads the values for all profile options assigned to that responsibility,
Support any number of legal entities within a single installation
Secure Access: You can assign users to particular organizations. This ensures accurate transactions in the correct operating unit.of Oracle Applications.
You can sell from one legal entity and ship from another, posting to each organization’s set of books.
You can enter purchase orders and assign for receipt any inventory organization that uses the same set of books.
You can support multiple organizations running any Oracle Applications product with a single installation. When you run any Oracle Applications product, you first choose an organization—either
implicitly by choosing a responsibility, or explicitly in a Choose Organization window. Each window and report then displays information for your organization only.
Each legal entity can have one or more balancing entities. An operating unit is associated with a legal entity. Information is secured by operating unit for these applications. Each user sees information only for their operating unit. To run any of these applications, you choose a responsibility associated with an
organization classified as an operating unit.
Legal Entities Post to a Set of Books Each organization classified as a legal entity identifies a set of books to post accounting transactions.
Operating Units Are Part of a Legal Entity Each organization classified as an operating unit is associated with a legal entity.
Inventory Organizations are Part of an Operating Unit Each organization classified as an inventory organization references an operating unit.
Inventory Organization Determines Items Available to Order Management The OM:Item Validation Organization profile option specifies the inventory organization that Order Management uses to validate items. Some inventory item attributes for Receivables and Order Management, including Tax Code and Sales Account, are specific to an operating unit or an accounting flexfield structure. Therefore, you
should define an item validation organization for each operating unit.
Inventory Organization Determines Items Available to Purchasing The inventory organization you specify in the financial options for each operating unit determines the items available in Purchasing. You can only choose an inventory organization that uses the same set of books as your operating unit.
Data Security You can limit users to information relevant to their organization. For example, you can limit access for order administration clerks to sales orders associated exclusively with their sales office.
Inventory Organization Security by Responsibility You can specify which inventory organizations are available to users in each responsibility. The Choose Inventory Organization window automatically limits available inventory organizations to those authorized for the current responsibility.
Responsibility Determines Operating Unit Your responsibility determines which operating unit you access when you use Oracle Applications. When you use Oracle Payables, Receivables, Order Management and Shipping Execution, Purchasing, Projects, and Sales Compensation you see information that is relevant to your operating unit. All transactions you create are automatically assigned to your operating unit.
Purchase and Receive Products Between Organizations Your purchase order operating unit and receiving inventory organization must share the same sets of books to receive against a purchase order.
Automatic Intercompany Sales Recognition Sales orders created and shipped from one legal entity to a different legal entity automatically generate an intercompany invoice to record a sale between the two organizations.
Posting Intercompany Invoices to Different Accounts You can define different accounts for Trade and Intercompany Cost of Goods Sold and Sales Revenue to eliminate intercompany profit.
These are the steps to follow when implementing the Multiple Organization support feature in Oracle Applications.
1. Develop the Organization Structure
2. Define Sets of Books
3. Define Locations
4. Define Business Groups (optional)
5. Associate Responsibilities with Business Groups
6. Define Organizations
7. Define Organization Relationships
8. Define Responsibilities
9. Set MO: Operating Unit Profile Option
10. Convert to Multiple Organization Architecture
11. Change Order Management Profile Option
12. Set Profile Options Specific to Operating Units
13. Define Inventory Organization Security (optional)
14. Implement the Applications Products
15. Secure Balancing Segment Values by Legal Entity (optional)
16. Run the Multi–Org Setup Validation Report (recommended)
17. Implement Document Sequencing (optional)
18. Define Intercompany Relations (optional)
19. Set Top Reporting Level Profile Option (optional)
20. Set Conflict Domains (optional)
Step 1 Develop the Organization Structure A successful implementation of Multiple Organization support in Oracle Applications depends primarily on defining your organizational structure in the multi–level hierarchy used by Oracle Applications. The levels are:
• Business groups
• Accounting sets of books
• Legal entities
• Operating units
• Inventory organizations
If your enterprise structure requires that you define a business group, you should define sets of books before business groups.
Step 3 Define Locations Oracle Applications products use locations for requisitions, receiving, shipping, billing, and employee assignments.
Step 4 Define Business Groups (optional) If you define a new business group instead of modifying the pre–defined business group, you need to set the 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.
You should define all your business groups before defining any other type of organization.
To define additional business groups:
1. Set the responsibility from which you define the organizations in the profile option HR: User Type to HR User, to get access to the Define Organizations window. This profile must be set for all responsibilities that use tables from Oracle Human Resources (for example, responsibilities used to define employees and
organizations).
2. Define all of your business groups at this step from a responsibility. Do not define any new organizations or organization hierarchies until you have associated each business group with a responsibility. You do this by setting the HR: Business Group profile option to the business groups for each responsibility.
3. After you have correctly associated business groups to responsibilities, you enter business group setup information, such as additional organization information and business group classifications, to create the organization structure.
4. After you have correctly associated your business groups with a responsibility, sign off and sign on again using the correct responsibility for the business group you want to define. For example, if you have a U.S. business group and a U.K. business group, select the responsibility attached to the U.S. business group to define the U.S. organization structure.
Note: Oracle Human Resources automatically creates a view all security profile with the business group name. This enables you to view all records for your business group.
Note: Oracle Human Resources allows you to use a single responsibility security model by enabling the Security Group. This allows you to access more than one business group from a responsibility. You should not use the single responsibility model in Multiple Organization products.
Step 5 Associate Responsibilities with Business Groups (optional)
Note: This section applies to you if you have multiple business groups, or if you do not choose to use the default business group provided by Oracle Applications.
If you have multiple business groups, you must associate each responsibility to one and only one business group. You associate a business group with a responsibility via the HR:Business Group system profile option. If you are upgrading to Multiple Organizations, you must also associate previously created responsibilities to the appropriate business group.
Step 6 Define Organizations
Use the Define Organization window to define all your 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.
_ To define legal entities, operating units, and inventory organizations:
1. Log in to the responsibility associated with the business group for which you are defining an organization.
2. Define a legal entity. It is then automatically attached to the correct business group.
3. Define operating units.
4. Define your inventory organizations for each operating unit that will have an inventory organization.
Note: Do not define the inventory parameters at this point.
5. If you have more than one business group, switch to the responsibility associated with the other business group and continue to define your organization structure.
Step 7 Define Organization Relationships Use the Define Organization window to define 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 organizations designated as legal entities to a set of books. You must also specify a location in the Define Organization window. Use the Define Location window to define locations for
your legal entities.
2. Operating units Attach the operating units to the correct set of books and legal entity.
3. Inventory organizations Attach the inventory organizations 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 other business group and continue defining your organization classification.
Classification Information Type Required Attributes
Business Group Business group information if Human Resources is installed. Otherwise, None.
Short Name, Employee/Applicant Numbering, Key Flexfield Structures, Default Legislation Code, and Currency
GRE/Legal Entity Legal Entity Accounting Set of Books, Location
Operating Unit Operating Unit Information Legal Entity, Set of Books
Inventory Organization Accounting Information Set of Books, Legal Entity, Operating Unit
Special Considerations for Inventory Organizations All the inventory organizations in the above chart have been set up with the minimal amount of information to enable them in the Multiple Organization environment. This minimal amount is detailed in the table below. If you plan to implement Oracle Inventory, you need to follow the setup procedures for that product.
For a standalone Oracle Purchasing installation (without Oracle
Inventory), you must specify the following minimum information:
1 Accounting information : Set of books, legal entity, operating unit
2 Receiving information : Three–character organization code,prefix serial (no dummy)
3 Inventory information : All required accounts
You must define the control options and account defaults for one inventory organization, the item master organization. Then you can easily assign items to other inventory organization without recreating all the item information. Use the Organization Parameter window to assign inventory organizations to the item master. The item master organization uses itself as the item master.
There is no functional or technical difference between the item master organization and other inventory organizations. However, we recommend that you limit the item master to just an item definition organization. If you set up new inventory organizations in the future, you can assign the new items to only the item master and the new inventory organization.
Step 8 Define Responsibilities Use the Define Responsibility window to define responsibilities for each operating unit by application. When you sign on to Oracle Applications, the responsibility you choose determines the data, forms, menus, reports, and concurrent programs you can access.
Step 9 Set MO: Operating Unit Profile Option Oracle Applications uses the profile option MO: Operating Unit to link an operating unit to a responsibility. You must set this profile option for
each responsibility.
After you choose your responsibility, there is an initialization routine that reads the values for all profile options assigned to that responsibility,
Period Clossing In AP
Period closing Process for Payables
Period closing Process for Payables
You cannot close a period in Payables if any of the following conditions exist:
o Outstanding payment batches. Confirm or cancel all incomplete payment batches.
o Future dated payments for which the Maturity Date is within the period but that still have a status of Issued.
o Unaccounted transactions. Submit the Payables Accounting Process to account for transactions, or submit the Unaccounted Transaction Sweep to move any remaining unaccounted transactions from one period to another.
o Accounted transactions that have not been transferred to general ledger. Submit the Payables Transfer to General Ledger process to transfer accounting entries.
To complete the close process in Payables:
1. Validate all invoices.
Run Invoice Validation Concurrent program.
2. Confirm or cancel all incomplete payment batches.
3. If you use future dated payments, submit the Update Matured Future Dated Payment Status Program. This will update the status of matured future dated payments to Negotiable so you can account for them.
4. Resolve all unaccounted transactions.
Submit the Payables Accounting Process to account for all unaccounted transactions. Review the Unaccounted Transactions Report. Review any unaccounted transactions and correct data as necessary.
Then resubmit the Payables Accounting Process to account for transactions you corrected. Or move any unresolved accounting transaction exceptions to another period (optional).
o Payables Accounting Process.
o Submit the Unaccounted Transactions Sweep Program.
5. Transfer invoices and payments to the General Ledger and resolve any problems you see on the output report:
o Payables Transfer to General Ledger Program.
6. In the Control Payables Periods window, close the period in Payables.
o Controlling the Status of Payables Periods.
7. Reconcile Payables activity for the period. You will need the following reports:
o Accounts Payable Trial Balance Report (this period and last period).
o Posted Invoice Register.
o Posted Payment Register.
8. If you use Oracle Purchasing, accrue uninvoiced receipts.
9. If you use Oracle Assets, run the Mass Additions Create Program transfer capital invoice line distributions from Oracle Payables to Oracle Assets.
10. Post journal entries to the general ledger and reconcile the trial balance to the General Ledger.
GL Topices
Journal source and categories is used to differentiate journal entries and to enhance your audit trail.
Journal entry source indicates where your journal entries originate
Journal categories help you differentiate entries by purchase or type.
Examples for Sources:
Assets
Purchasing
Payables
Manual
Budget …...Etc.
Examples For Categories:
Accruals
Adjustment
Receipts
Revaluation
Payments..Etc..
Oracle applications provided required source and categories with default. But you can define with your sauce and categories by using the following navigation:
GL:Setup->Journal->Source
Setup->journal-.Categories
With Journal Source you can:
Define inter company and suspense accounts for specific sources.
Run auto post program for specific source
Import journals by source
Freeze journals imported from sub ledgers to prevent users from making changes.
If you have journal approval enabled for your set of books, you can use journal source to enforce management approval of journal before they are posted.
With Journal Categories you can:
Define inter company and suspense accounts for specific category.
Use document sequence to sequentially number journals by categories.
Journal entry source indicates where your journal entries originate
Journal categories help you differentiate entries by purchase or type.
Examples for Sources:
Assets
Purchasing
Payables
Manual
Budget …...Etc.
Examples For Categories:
Accruals
Adjustment
Receipts
Revaluation
Payments..Etc..
Oracle applications provided required source and categories with default. But you can define with your sauce and categories by using the following navigation:
GL:Setup->Journal->Source
Setup->journal-.Categories
With Journal Source you can:
Define inter company and suspense accounts for specific sources.
Run auto post program for specific source
Import journals by source
Freeze journals imported from sub ledgers to prevent users from making changes.
If you have journal approval enabled for your set of books, you can use journal source to enforce management approval of journal before they are posted.
With Journal Categories you can:
Define inter company and suspense accounts for specific category.
Use document sequence to sequentially number journals by categories.
If you enter an invoice for expenses or asset purchases for more than one balancing segment, you might want to use automatic offset method to keep your payables transaction accounting entries balanced.
If we enable balancing as a automatic offset, payable builds the offset GL account by taking the balancing segment value from the invoice distribution and overlaying it on to the appropriate GL account, i.e liability account from the supplier site.
If we enable account as automatic offset, it takes the opposite approach with one segment being retained from the default GL account and all other segments being retained from the invoice distribution
If we enable balancing as a automatic offset, payable builds the offset GL account by taking the balancing segment value from the invoice distribution and overlaying it on to the appropriate GL account, i.e liability account from the supplier site.
If we enable account as automatic offset, it takes the opposite approach with one segment being retained from the default GL account and all other segments being retained from the invoice distribution
Author: Sreenivas.Bandi
Secondary Tracking Segment is a Flex field qualified added in the 11.5.10 release. The secondary tracking segment is used in the revaluation, translation, and fiscal year-end close processes. The system will automatically maintain unrealized gain/loss, retained earnings, and cumulative translation adjustments by unique pairs of balancing segment and secondary tracking segment values. you can assign Secondary tracking segment flex field qualifier to an segment which haven’t assigned Natural account, balensing Segment and inter company.
Oracle Implementation Methodalagy
SUMMARY NOTES ON AIM
Application Implementation Method is a provan approach, which specifies all the activities which are required to implement oracle applications successfully.
The scope of the AIM is enterprise wide.
There are eleven processes of implementation.
1. Business Process Architecture[BP]
This phase explains
Existing business practices
Catalog change practices
Leading practices
Future practices
2. Business Requirement Definition[RD]
This phase explains about the
Base line questionnaire and
The gathering of information.
3. Business Requirement Mapping[BR]
In this phase we can match all the requirements of business with the standard functionality of the oracle applications.
If all the requirements match with oracle standard (with out customization) functionality then, it is called as vanilla implementation).
4. Application and Technical Architecture [TA]
Explains the infrastructure requirements to implement oracle applications.
For example:
desktops
software
hardware
people...etc
5. Build and Module Design[MD]
In this phase concentrate on developing the new functionality which is required by the client.
This is called customization.
In this phase explains how to design a forms, database and reports...
6. Data Conversion:[CV]
Is the process of converting or transferring the data from legacy system to oracle applications? This is called as data migration.
Ex: transferring the closing balances of the previous year as an opening balances to next year.
7. Documentation:[DO]
I
n this phase we have to prepare module wise user guides and implementation manuals which helps in the implementation.
8. Business System Testing:[TE]
A process of validating the setup’s and the functionality by a tester to certify its status is allied business system testing. It is done by a functional consultant.
9. Performance Testing:[PT]
Performance testing means evaluation of transaction saving time, transaction retrieval times. It is done by a technical team.
10; Adoption and Learning.[AP]
This phase explains about the removal of the legacy system of the client. The entire user should be trained with new oracle applications. In this phase we have to prepare user manuals.
11. Production Migration[PM]
A process of decommissioning of legacy system and the usage of new oracle application system begins in this phase.
AR Accounting Entries
Invoices:
When you enter a regular invoice through the Transactions window, Receivables creates the following journal entry:
DEBIT Receivables
CREDIT Revenue
CREDIT Tax (if you charge tax)
CREDIT Freight (if you charge freight)
If you enter an invoice with a Bill in Arrears invoicing rule with a three month fixed duration accounting rule, Receivables creates the following journal entries:
In the first period of the rule:
DEBIT Unbilled Receivables
CREDIT Revenue
In the second period of the rule:
DEBIT Unbilled Receivables
CREDIT Revenue
In the third and final period of the rule:
DEBIT Unbilled Receivables
CREDIT Revenue
DEBIT Receivables
CREDIT Unbilled Receivables
CREDIT Tax (if you charge tax)
CREDIT Freight (if you charge freight)
If you enter an invoice with a Bill in Advance invoicing rule, Receivables creates the followingjournal entries:
In the first period of the rule:
DEBIT Receivables
CREDIT Unearned Revenue
CREDIT Tax (if you charge tax)
CREDIT Freight (if you charge freight)
DEBIT Unearned Revenue
CREDIT Revenue
In all periods of the rule for the portion that is recognized.
DEBIT Unearned Revenue
CREDIT Revenue
Credit Memos:
When you credit an invoice, debit memo, or chargeback through the Credit Transactions window, Receivables creates the following journal entry:
DEBIT Revenue
DEBIT Tax (if you credit tax)
DEBIT Freight (if you credit freight)
CREDIT Receivables (Credit Memo)
DEBIT Receivables (Credit Memo)
CREDIT Receivables (Invoice)
When you credit a commitment, Receivables creates the following journal entries:
DEBIT Revenue
CREDIT Receivables
When you enter a credit memo against an installment, Receivables lets you choose between the following methods: LIFO, FIFO, and Prorate. When you enter a credit memo against an invoice with invoicing and accounting rules, Receivables lets you choose between the following methods: LIFO, Prorate, and Unit.
If the profile option AR: Use Invoice Accounting for Credit Memos is set to Yes, Receivables credits the accounts of the original transaction. If this profile option is set to No, Receivables uses AutoAccounting to determine the Freight, Receivables, Revenue, and Tax accounts. Receivables uses the account information for on-account credits that you specified in your AutoAccounting structure to create your journal entries.
Receivables lets you update accounting information for your credit memo after it has posted to your general ledger. Receivables keeps the original accounting information as an audit trail while it creates an offsetting entry and the new entry.
Commitments:
When you enter a deposit, Receivables creates the following journal entry:
DEBIT Receivables (Deposit)
CREDIT Offset Account
Use the AR: Deposit Offset Account Source profile option to determine how Receivables derives the Offset Account to credit for this deposit.
When you enter an invoice against this deposit, Receivables creates the following journal entries:
DEBIT Receivables (Invoice)
CREDIT Revenue
CREDIT Tax (if you charge tax)
CREDIT Freight (if you charge freight)
DEBIT Offset Account (such as Unearned Revenue)
CREDIT Receivables (Invoice)
When you apply an invoice to a deposit, Receivables creates a receivable adjustment against the invoice. Receivables uses the account information that you specified in your AutoAccounting structure to create these entries.
When cash is received against this deposit, Receivables creates the following journal entry:
DEBIT Cash
CREDIT Receivables (Deposit)
When you enter a guarantee, Receivables creates the following journal entry:
DEBIT Receivables
CREDIT Revenue
Receivables uses the Receivable Account and Revenue Account fields on this guarantee's transaction type to obtain the accounting flexfields for the Unbilled Receivables and Unearned Revenue accounts, respectively.
When you enter an invoice against this guarantee, Receivables creates the following journal entry:
DEBIT Receivables (Invoice)
CREDIT Revenue
CREDIT Tax (if you charge tax)
CREDIT Freight (if you charge freight)
DEBIT Revenue
CREDIT Receivables
When you apply an invoice to a guarantee, Receivables creates a receivable adjustment against the guarantee. Receivables uses the account information you specified in your AutoAccounting structure to create these entries.
When cash is received against this guarantee, Receivables creates the following journal entry:
DEBIT Cash
CREDIT Receivables (Invoice)
Receipts:
When you enter a receipt, Receivables creates the following journal entries:
DEBIT Cash
CREDIT Receivables
When you fully apply a receipt to an invoice, Receivables creates the following journal entry:
DEBIT Cash
DEBIT Unapplied Cash
CREDIT Unapplied Cash
CREDIT Receivables
Note: These examples assume that the receipt has a Remittance Method of No Remittance and a Clearance Method of Directly.
When you enter an unidentified receipt, Receivables creates the following journal entry:
DEBIT Cash
CREDIT Unidentified
When you enter an on-account receipt, Receivables creates the following journal entry:
DEBIT Cash
CREDIT Unapplied
DEBIT Unapplied
CREDIT On-Account
When your receipt includes a discount, Receivables creates the following journal entry:
DEBIT Receivables
CREDIT Revenue
DEBIT Cash
CREDIT Receivables
DEBIT Earned/Unearned Discount
CREDIT Receivables
Receivables uses the default Cash, Unapplied, Unidentified, On-Account, Unearned, and Earned accounts that you specified in the Remittance Banks window for this receipt class.
When you enter a receipt and combine it with an on-account credit (which increases the balance of the receipt), Receivables creates the following journal entry:
DEBIT Cash
CREDIT Unapplied Cash
To close the receivable on the credit memo and increase the unapplied cash balance, Receivables creates the following journal entry:
DEBIT Receivables
CREDIT Unapplied Cash
When you enter a receipt and combine it with a negative adjustment, Receivables creates the following journal entries:
DEBIT Cash
CREDIT Receivables (Invoice)
DEBIT Write-Off
CREDIT Receivables (Invoice)
You set up a Write-Off account when defining your Receivables Activity.
When you enter a receipt and combine it with a positive adjustment, Receivables creates the following journal entries:
DEBIT Cash
CREDIT Receivables (Invoice)
DEBIT Receivables (Invoice)
CREDIT Write-Off
When you enter a receipt and combine it with a Chargeback, Receivables creates the followingjournal entries:
DEBIT Cash
CREDIT Receivables (Invoice)
DEBIT Receivables (Chargeback)
CREDIT Chargeback (Activity)
DEBIT Chargeback (Activity)
CREDIT Receivables (Invoice)
You set up a Chargeback account when defining your Receivables Activity.
Remittances:
When you create a receipt that requires remittance to your bank, Receivables debits the Confirmation account instead of Cash. An example of a receipt requiring remittance would be a check before it was cashed. Receivables creates the following journal entry when you enter such a receipt:
DEBIT Confirmation
CREDIT Receivables
You can then remit the receipt to your remittance bank using one of the two remittance methods: Standard or Factoring. If you remit your receipt using the standard method of remittance, Receivables creates the following journal entry:
DEBIT Remittance
CREDIT Confirmation
When you clear the receipt, Receivables creates the following journal entry:
DEBIT Cash
DEBIT Bank Charges
CREDIT Remittance
If you remit your receipt using the factoring remittance method, Receivables creates the following journal entry:
DEBIT Factor
CREDIT Confirmation
When you clear the receipt, Receivables creates a short-term liability for receipts that mature at a future date. The factoring process let you receive cash before the maturity date, and assumes that you are liable for the receipt amount until the customer pays the balance on the maturity date. When you receive payment, Receivables creates the following journal entry:
DEBIT Cash
DEBIT Bank Charges
CREDIT Short-Term Debt
On the maturity date, Receivables reverses the short term liability and creates the followingjournal entry:
DEBIT Short-Term Debt
CREDIT Factor
Adjustments:
When you enter a negative adjustment against an invoice, Receivables creates the followingjournal entry:
DEBIT Write-Off
CREDIT Receivables (Invoice)
When you enter a positive adjustment against an invoice, Receivables creates the following journal entry:
DEBIT Receivables (Invoice)
CREDIT Write-Off
Debit Memos:
When you enter a debit memo in the Transactions window, Receivables creates the following journal entries:
DEBIT Receivables
CREDIT Revenue (if you enter line amounts)
CREDIT Tax (if you charge tax)
CREDIT Freight (if you charge freight)
DEBIT Receivables
CREDIT Finance Charges
On-Account Credits:
When you enter an on-account credit in the Applications window, Receivables creates the following journal entry:
DEBIT Revenue (if you credit line amounts)
DEBIT Tax (if you credit tax)
DEBIT Freight (if you credit freight)
CREDIT Receivables (On-account Credit)
Receivable uses the Freight, Receivable, Revenue, and Tax accounts that you specified in your AutoAccounting structure to create these entries.
Once the on-account credit is applied to an invoice, the following journal entry is created:
DEBIT Receivables (On-account Credit)
CREDIT Receivables (Invoice)
AP/AR Netting in R 12
AP/AR Netting automatically compares Payables to Receivables and creates the appropriate transaction in each system to net supplier invoices and customer invoices. With this functionality, A receivables user can
· View netted receipt details directly from the receipt
· Create Netting Agreements and Netting Batches
With this functionality, there is significant increase in user productivity and effectiveness because of tight integration and automation.
You can access the process via:
You can access the process via:
· Navigation: Receipts > Netting > Netting Batch
· Navigation: Receipts > Netting > Netting Agreement
· Receipts > Receipts > Action Menu : AP/AR Netting
After Querying a netted receipt, the user can see more details about the batch by selecting AP/AR Netting from the Action menu. This launches the AP/AR Netting batch window. Netted Receipts are created automatically by the AP/AR Netting process and cannot be updated by the user from the Receipts Workbench
After Querying a netted receipt, the user can see more details about the batch by selecting AP/AR Netting from the Action menu. This launches the AP/AR Netting batch window. Netted Receipts are created automatically by the AP/AR Netting process and cannot be updated by the user from the Receipts Workbench
As we have seen Contra charging has been replaced by AP/AR Netting, lets take a setup walk though to use this functionality.
1.Define netting control account
1.Define netting control account
Setup>Financials>Flex field>key>values
2.Create bank
Setup>payment>Bank and Bank Branches
You should note ,Payment document is not required for netting bank account.
3.Go to receivables responsibility, receipt class definition form
3.Go to receivables responsibility, receipt class definition form
Setup>Receipts>Receipt class
Query the 'AP/AR Netting' receipt class which is a seeded one.
4. Attach your bank account in this receipt class.
5.Go to system options, transaction and customer tabbed region, there enable 'Allow payment of Unrelated Transactions'check box
6. Create netting agreement
4. Attach your bank account in this receipt class.
5.Go to system options, transaction and customer tabbed region, there enable 'Allow payment of Unrelated Transactions'check box
6. Create netting agreement
Receipts>Netting>Netting Agreement
7. Enter an Invoice in Payables, validate and run create accounting.
8. Enter a transaction in receivables.
9. Create Netting Batch
Receipts >Netting >Netting Batch
10. Query your netting batch and see the status as Complete. also click on view report icon on right side.click on run push button, you can see the final netting report.
11.Go to view>request>find
You can see 3 concurrent request programs
· Create Netting batch
· Settle netting batch
· Netting Data Extract
12.Now go to receipts and query the AP/AR netting receipt.
13.Now Go to Tools >view Accounting, you can see Netting control account (defined in first step a) debited and receivable account credited.
14. Now go to payables and query your invoice number and click the tab view payments. You can see the payment details and copy the document number.
15.Query your copied payment document number.What you can see the payment type as Netting .
16.Click actions button and enable the check box create accounting .
17.Go to tools>view accounting .You can see the accounting entry
13.Now Go to Tools >view Accounting, you can see Netting control account (defined in first step a) debited and receivable account credited.
14. Now go to payables and query your invoice number and click the tab view payments. You can see the payment details and copy the document number.
15.Query your copied payment document number.What you can see the payment type as Netting .
16.Click actions button and enable the check box create accounting .
17.Go to tools>view accounting .You can see the accounting entry
R12 - GL - New Features
R12 – Oracle General Ledger – New and enhanced feature
Lot many emails I was getting since in past few months , asking to share some more information for R12 of General Ledger features, so thought to share in a post.
Here are some of the new feature of General Ledger in R12.
Accounting Setup Manager
The ledger is a basic concept in Release 12. The ledger replaces the 11i concept of a set of books. It represents an accounting representation for one or more legal entities or for a business need such as consolidation or management reporting. Companies can now clearly and efficiently model its legal entities and their accounting representations in Release 12. This seems to be a major area in getting success of the shared service center and single instance initiatives where many or all legal entities of an enterprise are accounted for in a single instance, and data, setup, and processing must be effectively secured but also possibly shared.
Now, legal Entities can be mapped to entire Ledgers or if you account for more than one legal entity within a ledger, you can map a legal entity to balancing segments within a ledger.
While a set of books is defined by 3 C’s,
Here are some of the new feature of General Ledger in R12.
Accounting Setup ManagerThe ledger is a basic concept in Release 12. The ledger replaces the 11i concept of a set of books. It represents an accounting representation for one or more legal entities or for a business need such as consolidation or management reporting. Companies can now clearly and efficiently model its legal entities and their accounting representations in Release 12. This seems to be a major area in getting success of the shared service center and single instance initiatives where many or all legal entities of an enterprise are accounted for in a single instance, and data, setup, and processing must be effectively secured but also possibly shared.
Now, legal Entities can be mapped to entire Ledgers or if you account for more than one legal entity within a ledger, you can map a legal entity to balancing segments within a ledger.
While a set of books is defined by 3 C’s,
1. chart of accounts
2. functional currency
3. accounting calendar,
The addition in this list the ledger is defined by a 4th C: the accounting method,
This 4th C allows you to assign and manage a specific accounting method for each ledger. Therefore, when a legal entity is subject to multiple reporting requirements, separate ledgers can be used to record the accounting information.
Accounting Setup Manager is a new feature that allows you to set up your common financial setup components from a central location.
This 4th C allows you to assign and manage a specific accounting method for each ledger. Therefore, when a legal entity is subject to multiple reporting requirements, separate ledgers can be used to record the accounting information.
Accounting Setup Manager is a new feature that allows you to set up your common financial setup components from a central location.
What is Accounting Setup Manager
Accounting Setup Manager is a new feature that streamlines the setup and implementation of Oracle Financial Applications. The Accounting Setup Manager will facilitate the setup required for simultaneous accounting for multiple reporting requirements.
With the Accounting Setup Manager, you can perform and maintain the following common setup components from a central location:
Accounting Setup Manager is a new feature that streamlines the setup and implementation of Oracle Financial Applications. The Accounting Setup Manager will facilitate the setup required for simultaneous accounting for multiple reporting requirements.
With the Accounting Setup Manager, you can perform and maintain the following common setup components from a central location:
· Legal Entities
· Ledgers, primary and secondary
· Operating Units, which are assigned to primary ledgers
· Reporting Currencies, which is an enhanced feature
· Subledger Accounting Options. This is where you define the accounting methods for each legal entity subledger transaction and associate them to the ledger where the accounting will be stored.
· Intercompany Accounts and Balancing Rules
· Accounting and Reporting Sequencing
· Both Intercompany and Sequencing
Will discuss some more granular details in some other post.
Subledger Accounting (SLA)As discussed in couple of earlier post GL is integrated with SLA to enable a unified process to account for subledger transactions and post data to GL, and to provide a consistent view when drilling down from GL to subledger transactions. You can read here.
Enhanced Foreign Currency Processing by Reporting Made easyGL has added new features and enhanced existing features to support foreign currency processing , they are mainly as:
· In R12, MRC feature is enhanced with a feature call Reporting Currencies. That mean it will now support multiple currency representations of data from any source, including external systems, Oracle or non-Oracle subledgers, and Oracle General Ledger journals and balances.
· The second one is in reporting to view balances view balances that were entered in your ledger currency separate from those balances that were entered and converted to the ledger currency.The change in R12 is that balances entered in the ledger currency are maintained separately from balances converted to the ledger currency for use in Reporting and Analysis.
Here’s an example. Assume we have a ledger and the ledger currency is USD.
I enter and post two journals; one in 1,000 US Dollars, and another in 500 British Pounds that gets converted to 1200 US Dollars.
In Release 11i, I can review the 500 GBP and the 1200 USD that results from converting the 500 GBP, and the total 2200 USD which is the USD balance in the Cash Account. The $2200 is the sum of the $1000 entered in USD and the $1200 converted from the 500 British Pounds. However, I view that a 1000 USD were entered directly in USD.
In Release 12, I can view the 1000 USD by performing an account inquiry on the Cash account for balances entered only in the ledger currency. The amounts entered in foreign currencies that were converted to the ledger currency will not be included in the balance. Of course, if I want to retrieve all balances in USD, both the entered as well and the converted, I can still do that in Release 12.
Creating foreign currency recurring journals
In Release 11i, you could define recurring journals using the functional currency or STAT currency.
Now in Release 12, you can create recurring journals using foreign currencies. This is particularly useful if you need to create foreign currency journals that are recurring in nature. For example, assume a subsidiary that uses a different currency from its parent borrows money from the parent. The subsidiary can now generate a recurring entry to record monthly interest payable to the parent company in the parent’s currency.
Data Access to Multiple Legal Entities and Ledgers
You no longer have to constantly switch responsibilities in order to access the data in a different ledger. You can access multiple ledgers from a single responsibility as long as all ledgers share the same chart of accounts and calendar.
Simultaneous Opening and Closing of Periods for Multiple Ledgers
You no longer have to open and close periods for each ledger separately. You can now open and close periods across multiple ledgers simultaneously by submitting Open and Close Periods programs from the Submit Request form.
Simultaneous Currency Translation of Multiple Ledgers
You can run the Translation program for multiple ledgers simultaneously, if you are managing multiple ledgers.
Financial Reporting for Multiple Ledgers
Now with this feature you can run Financial Statement Generator (FSG) reports for multiple ledgers simultaneously. This is useful if you manage multiple ledgers and want to run a balance sheet or income statement report for all of your ledgers at the same time.
Cross-Ledger and Foreign Currency Allocations
You are able to allocate financial data from one or more ledgers to a different target ledger. This enables you to perform cross-ledger allocations, which is useful for purposes such as allocating corporate or regional expenses to local subsidiaries when each entity has its own ledger
Streamlined Automatic Posting
You can now share AutoPost Criteria sets across multiple ledgers that share the same chart of accounts and calendar and use the AutoPost Criteria sets to post journals across multiple ledgers simultaneously.
Streamlined AutoReversal Criteria Setup Integrated Web-based
AutoReversal Criteria Sets can also be shared across ledgers to reverse journals across multiple ledgers. This is enhanced by integrated Web-based Spreadsheet Interface.
I enter and post two journals; one in 1,000 US Dollars, and another in 500 British Pounds that gets converted to 1200 US Dollars.
In Release 11i, I can review the 500 GBP and the 1200 USD that results from converting the 500 GBP, and the total 2200 USD which is the USD balance in the Cash Account. The $2200 is the sum of the $1000 entered in USD and the $1200 converted from the 500 British Pounds. However, I view that a 1000 USD were entered directly in USD.
In Release 12, I can view the 1000 USD by performing an account inquiry on the Cash account for balances entered only in the ledger currency. The amounts entered in foreign currencies that were converted to the ledger currency will not be included in the balance. Of course, if I want to retrieve all balances in USD, both the entered as well and the converted, I can still do that in Release 12.
Creating foreign currency recurring journals
In Release 11i, you could define recurring journals using the functional currency or STAT currency.
Now in Release 12, you can create recurring journals using foreign currencies. This is particularly useful if you need to create foreign currency journals that are recurring in nature. For example, assume a subsidiary that uses a different currency from its parent borrows money from the parent. The subsidiary can now generate a recurring entry to record monthly interest payable to the parent company in the parent’s currency.
Data Access to Multiple Legal Entities and Ledgers
You no longer have to constantly switch responsibilities in order to access the data in a different ledger. You can access multiple ledgers from a single responsibility as long as all ledgers share the same chart of accounts and calendar.
Simultaneous Opening and Closing of Periods for Multiple Ledgers
You no longer have to open and close periods for each ledger separately. You can now open and close periods across multiple ledgers simultaneously by submitting Open and Close Periods programs from the Submit Request form.
Simultaneous Currency Translation of Multiple LedgersYou can run the Translation program for multiple ledgers simultaneously, if you are managing multiple ledgers.
Financial Reporting for Multiple LedgersNow with this feature you can run Financial Statement Generator (FSG) reports for multiple ledgers simultaneously. This is useful if you manage multiple ledgers and want to run a balance sheet or income statement report for all of your ledgers at the same time.
Cross-Ledger and Foreign Currency AllocationsYou are able to allocate financial data from one or more ledgers to a different target ledger. This enables you to perform cross-ledger allocations, which is useful for purposes such as allocating corporate or regional expenses to local subsidiaries when each entity has its own ledger
Streamlined Automatic PostingYou can now share AutoPost Criteria sets across multiple ledgers that share the same chart of accounts and calendar and use the AutoPost Criteria sets to post journals across multiple ledgers simultaneously.
Streamlined AutoReversal Criteria Setup Integrated Web-based AutoReversal Criteria Sets can also be shared across ledgers to reverse journals across multiple ledgers. This is enhanced by integrated Web-based Spreadsheet Interface.
Journal CopyNow we can now copy entire journal batches. You can copy journal batches with any status. The system will create a new journal batch containing the same journal entries.You may also change the batch name, period, and/or effective date while copying the journal batch. After copying the journal batch, you may modify the unposted journals in the same manner as any manually created journals.
Streamlined Consolidation MappingsYou are able to define Chart of Accounts Mappings (formerly known as Consolidation Mappings) between two charts of accounts. Therefore, if you have multiple Consolidation Definitions for parent and subsidiary ledgers that share the same chart of accounts pair, and their mapping rules are the same, you only have to define a single Chart of Accounts Mapping.
The enhancement in R12 allows you to define mappings between charts of accounts instead of between sets of books, so that they can be shared across multiple Consolidation Definitions.
Therefore, if you have multiple Consolidation Definitions for parent and subsidiary ledgers that share the same chart of accounts pair, and their mapping rules are the same, you only have to define a single Chart of Accounts Mapping.
You can also secure access to chart of accounts mappings using definition access set security. This allows you to secure which users can view, modify, and/or use chart of account mappings in consolidation definitions.
Replacement for Disabled AccountsNormally when an account is disabled, you can prevent transactions that include the account from erroring during journal import by defining a replacement account for the disabled account. Journal import replaces the disabled account with the replacement account and continue the journal import process if the replacement account is valid. This improves processing efficiency by preventing the journal import process from erroring and enabling the successful creation of the journal with minimal user intervention when an account has been disabled.
Data Access Security for Legal Entities and LedgersIn R12, since you can access multiple legal entities and ledgers when you log into Oracle General Ledger using a single responsibility, Oracle General Ledger provides you with flexible ways to secure your data by legal entity, ledger, or even balancing segment values or management segment values. You are able to control whether a user can only view data, or whether they can also enter and modify data for a legal entity, ledger, balancing segment value or management segment value.
Management Reporting and SecurityThis can be best understood as:You can designate any segment (except the natural account segment) of your chart of accounts to be your management segment and use Oracle GL security model to secure the management segment for reporting and entry of management adjustments.
Prevent Reversal of Journals with Frozen SourcesYou can no longer reverse journals from frozen sources defined in the journal sources form.
If the journal is created from a frozen source, the journal cannot be modified even if the source is subsequently unfrozen in the future.
This provides streamlined data reconciliation with subsystems. Not being able to reverse journals that originated in subledgers will ensure that the account balances will always tie out with General Ledger. If you need to reverse a subledger journal, then you should do so in Subledger Accounting or the subledger application.
If the journal is created from a frozen source, the journal cannot be modified even if the source is subsequently unfrozen in the future.
This provides streamlined data reconciliation with subsystems. Not being able to reverse journals that originated in subledgers will ensure that the account balances will always tie out with General Ledger. If you need to reverse a subledger journal, then you should do so in Subledger Accounting or the subledger application.
Prevent Reversal of Unposted Journals
You also can no longer reverse unposted journals. This ensures data integrity and better auditability. In the past when we allowed you to reverse unposted journals, there was a risk that the original journal could be deleted so you could end up reversing something that didn't exist. Now, all reversals can be tied back to the original posted journal.
Integrated Web-based Spreadsheet Interface
Through the integration with Web ADI, users can now leverage spreadsheet functionality in Oracle General Ledger via a web-based interface. The spreadsheet interface can be conveniently launched from a GL responsibility.
Using the Journal Wizard, we can leverage spreadsheet functionality to create actual, budget, or encumbrance journals. You can take advantage of spreadsheet data entry shortcuts such as copying and pasting or dragging and dropping ranges of cells, or even using formulas to calculate journal line amounts. You can then upload your journals to Oracle General Ledger. Before uploading, you can save and distribute your journal worksheets for approval.
We can also import data from text files into spreadsheets, where it can be further modified before uploading to Oracle. This functionality is useful when migrating data from legacy systems, or from any source that can produce delimited files.
Using the Budget Wizard, you can download budget amounts to a spreadsheet, modify the amounts, and then upload them back. You can also choose to download the actual amounts to compare it with the budget amount. Budget Wizard also allows you to plot graphs and do a graphical comparison on the amounts. Budget Wizard also provides budget notes. You can add descriptions to accounts and amounts in your budget and explain your budget within the budget worksheet, avoiding the clutter of external documentation.
Control Accounts
You are able to control data entry to an account by ensuring it only contains data from a specified journal source and to prevent users from entering data for the account either in other journal sources or manually within general ledger.
Security for Definitions
You can secure your setup and definitions by granting specific privileges to users to view, modify, and/or execute a definition. This enables you to control which of your users can view a definition, but not modify or execute it, or execute a definition without modifying it, or vice versa.
Following is a list of definitions that have this security available for:
You also can no longer reverse unposted journals. This ensures data integrity and better auditability. In the past when we allowed you to reverse unposted journals, there was a risk that the original journal could be deleted so you could end up reversing something that didn't exist. Now, all reversals can be tied back to the original posted journal.
Integrated Web-based Spreadsheet Interface
Through the integration with Web ADI, users can now leverage spreadsheet functionality in Oracle General Ledger via a web-based interface. The spreadsheet interface can be conveniently launched from a GL responsibility.
Using the Journal Wizard, we can leverage spreadsheet functionality to create actual, budget, or encumbrance journals. You can take advantage of spreadsheet data entry shortcuts such as copying and pasting or dragging and dropping ranges of cells, or even using formulas to calculate journal line amounts. You can then upload your journals to Oracle General Ledger. Before uploading, you can save and distribute your journal worksheets for approval.
We can also import data from text files into spreadsheets, where it can be further modified before uploading to Oracle. This functionality is useful when migrating data from legacy systems, or from any source that can produce delimited files.
Using the Budget Wizard, you can download budget amounts to a spreadsheet, modify the amounts, and then upload them back. You can also choose to download the actual amounts to compare it with the budget amount. Budget Wizard also allows you to plot graphs and do a graphical comparison on the amounts. Budget Wizard also provides budget notes. You can add descriptions to accounts and amounts in your budget and explain your budget within the budget worksheet, avoiding the clutter of external documentation.
Control Accounts
You are able to control data entry to an account by ensuring it only contains data from a specified journal source and to prevent users from entering data for the account either in other journal sources or manually within general ledger.
Security for DefinitionsYou can secure your setup and definitions by granting specific privileges to users to view, modify, and/or execute a definition. This enables you to control which of your users can view a definition, but not modify or execute it, or execute a definition without modifying it, or vice versa.
Following is a list of definitions that have this security available for:
1. MassAllocation and MassBudget Formulas
2. FSG Reports and Components
3. Accounting Calendars
4. Transaction Calendars
5. AutoPost Criteria Sets
6. AuoReversal Criteria Sets
7. Budget Organizations
8. Chart of Accounts Mappings
9. Consolidation Definitions
10. Consolidation Sets
11. Elimination Sets
12. Ledger Sets
13. Recurring Journals and Budget Formulas
14. Rate Types
15. Revaluations
Sequence for ReportingMaintaining two sequnces have been introduced, accounting and reporting sequencing.
Read my earlier post for more details:
Read my earlier post for more details:
Journal Line ReconciliationJournal Line Reconciliation enables you to reconcile journal lines that should net to zero, such as suspense accounts, or payroll and tax payable accounts for countries, such as Norway, Germany, or France.
In R12, we’ve made many improvements to intercompany accounting. R11i’s Global Intercompany System (GIS) has been replaced with an exciting new product called Advanced Global Intercompany System (AGIS). We also extended intercompany balancing support to include encumbrance journals.
In R12, we’ve made many improvements to intercompany accounting. R11i’s Global Intercompany System (GIS) has been replaced with an exciting new product called Advanced Global Intercompany System (AGIS). We also extended intercompany balancing support to include encumbrance journals.
R12 - AP - New Features
Welcome to R12 Account Payable
As we learnt during Release 12, the E-Business Suite has couple of new products like Subledger Accounting, E-Business Tax thus significant changes have been observed in Account Payable data module as some of functionality is shared by some other products. Thus it is important to understand what is new. I would like to briefly outline the details of some of new changes and underlying impact on the objects. More details can be found in R12 release documents published by Oracle a month ago.
Let’s have a dissection view of R12 payable, with some of its core objects
Supplier
Let’s have a dissection view of R12 payable, with some of its core objects
SupplierWe have seen in 11i
· Suppliers defined in AP.
· Supplier contacts replicated for each supplier site.
Where as in R12
· Supplier becomes as TCA Party.
· Suppliers Sites as TCA Party Site for each distinct address.
· Contacts for each supplier/address , it means Single supplier address and contact can be leveraged by multiple sites, for each OU
· A single change to an address can be seen instantly by all OUs
· No longer need to manually 'push' updates across OUs.This can be best understood by the figure below.
Then the question is what will happen if any one can come from existing financial products. The Impact from upgrade can summarize as:
1. When we upgrade supplier tables replaced with backward compatible views.
2. One party site for each distinct supplier site address
1. When we upgrade supplier tables replaced with backward compatible views.
2. One party site for each distinct supplier site address
Country and address line1 are required, this is because creation of suppliers in Party in TCA data model would requires Country and address information, but it also understood if there is no country or address line 1 specified for a supplier site in cases when upgrades takes place, Payables derives the country based on the most frequently used operating unit of the Supplier's historical transactions.
3. Employee as suppliers: address NOT migrated to party site in TCA remains in Oracle HR for data security reasons.
As we know in 11i employees are part of internal supplier's record in order for Oracle Payables to create payments for their expense reports. Employees defined in Oracle Human Resources and associated with an Oracle Payables supplier record have existing party information. During the upgrade, Oracle Payables updates the existing party information to have a party usage of supplier but it does not migrate the employee address to the party site in TCA, they remain in Oracle Human Resources for data security reasons.
4. Utilize TCA Party relationships for franchise or subsidiary and its parent company.
InvoiceTill 11i version, we have seen invoices:
· Had only distributions line.
· Allocation of freight and special charges are captured at the distribution level only
· Tax and payment and Project accounting Payment was captured through global Descriptive Flexfields.
But in R12,
1. Invoice Lines as a new additional line accommodated in Invoice data model.
Because of introduction of invoice line there is significant improvement of data flow with n other oracle modules like
1. Invoice Lines as a new additional line accommodated in Invoice data model.
Because of introduction of invoice line there is significant improvement of data flow with n other oracle modules like
· Fixed Asset - Asset Tracking
· Business Tax - Tax line
· Payment - Payment
· SubLedger Accounting - Accounting
2. Allocate freight and special charges are captured to the lines on the invoice
3. Invoice distributions created at the maximum level of detail similar to 11i.
4. Core functionality
The impact with Upgrade can be summarized as:
1. One invoice line for every distribution in 11i
2. Sub Ledger Accounting requires that Payables transform the invoice distributions to be stored at the maximum level of detail
3. Global Descriptive Flexfields migrated to named columns.
2. Sub Ledger Accounting requires that Payables transform the invoice distributions to be stored at the maximum level of detail
3. Global Descriptive Flexfields migrated to named columns.
That's means functional testing is more required while upgrade takes place.
Banks and Bank DetailsNow a days corporate treasury role has been greatly enhanced thus picking up a global bank as partner for all banking need is demand of time in global working model. The recent couple of years have seen drastic increase in acquisition and merger of company thus global working as well as global instance get popularity in ERP areana, and this is one of reason of the reason bank data model has been significant changes from 11 to 11i and 11i to R12.
Internal Bank AccountsIn 11i we have seen internal Banks defined in AP and that is shared by AP/AR/CE, Payroll and Treasury and they are bank accounts often replicated in multiple OUs
Where as in R12,
Internal Bank AccountsIn 11i we have seen internal Banks defined in AP and that is shared by AP/AR/CE, Payroll and Treasury and they are bank accounts often replicated in multiple OUs
Where as in R12,
· Bank and Branch become part of TCA Parties.
· Internal Bank Account in Cash Management which is owned by a Legal Entity. Here the Operating units have granted usage rights.
Suppliers Bank Accounts
In 11i
In 11i
· Banks/Branches defined in AP
· Bank accounts often replicated in multiple OUs Before
R12
· Suppliers, Banks and Branches are defined as Parties in TCA
· Supplier (party's) payment information and all payment instruments (Bank Accounts, Credit Cards) moved into Oracle Payments.
The typical data model for bank can be summarized as:
Impact of Upgrade
1. With Upgrade banks and branches migrated to TCA parties
2. Banks merged if the following attributes are all the same:
2. Banks merged if the following attributes are all the same:
· a. Bank Number
b. Institution type
c. Country
d. Bank admin email
e. Bank name alt
f. Tax payer ID
g. Tax reference number
h. Description, Effective dates
b. Institution type
c. Country
d. Bank admin email
e. Bank name alt
f. Tax payer ID
g. Tax reference number
h. Description, Effective dates
3. Bank accounts, bank account uses are migrated into cash management.
4. Transactions are stamped with the bank account uses identifiers as part of the upgrade
4. Transactions are stamped with the bank account uses identifiers as part of the upgrade
Integration with Oracle E-Business TaxIn 11i
· Oracle standard functionality was based out of User which determines tax by assigning Tax Codes at line level of invoice and Tax rules was controlled at underline code.
· There was global descriptive flex fields were captured for country-specific tax attrib
utes.
utes.· More importanta most of the setup performed at OU level.
In R12
· A new module eBusinessTax determines tax based on facts about each transaction, this is reason why Oracle has introduced additional line information at invoice level.
· The module "ebusiness Tax" set and configure Tax rules which can be viewed
· Tax attributes collected in fields on key entities
· Configure tax rules once per regime and share with your legal entities
Impact of Upgrade
1. Payables Tax setup, Tax Code defaulting rules defined per OU are migrated to eBusiness Tax.
2. OUs migrated to tax content owner in R12
3. Tax information in tax codes are transformed to Regime-Rate flow.
4. E-Business Tax takes information from the AP invoice lines and creates summary and detail tax lines in the E-Business Tax repository.
1. Payables Tax setup, Tax Code defaulting rules defined per OU are migrated to eBusiness Tax.
2. OUs migrated to tax content owner in R12
3. Tax information in tax codes are transformed to Regime-Rate flow.
4. E-Business Tax takes information from the AP invoice lines and creates summary and detail tax lines in the E-Business Tax repository.
Multi Org Access ControlMOAC is new enhancement to the Multiple Organizations feature of Oracle Applications.
This feature enables user to access data from one or many Operating Units while within a set given responsibility. Due to this change, all processing and some Reporting in Oracle Payables is available across Operating Units from a single Applications responsibility. Hence you can isolate your transaction data by Operating unit for security and local level compliance while still enabling shared Service centre processing.Data security is maintained using the Multiple Organizations Security Profile, defined in Oracle HRMS, which specifies a list of operating units and determines the data access privileges for a user.
Impact of UpgradeR12 Upgrade does not automatically create security profiles, thus is important if any one want to use Multiple Organizations Access Control, the first things is to define security profiles, then link them to respective responsibilities or users.
This feature enables user to access data from one or many Operating Units while within a set given responsibility. Due to this change, all processing and some Reporting in Oracle Payables is available across Operating Units from a single Applications responsibility. Hence you can isolate your transaction data by Operating unit for security and local level compliance while still enabling shared Service centre processing.Data security is maintained using the Multiple Organizations Security Profile, defined in Oracle HRMS, which specifies a list of operating units and determines the data access privileges for a user.
Impact of UpgradeR12 Upgrade does not automatically create security profiles, thus is important if any one want to use Multiple Organizations Access Control, the first things is to define security profiles, then link them to respective responsibilities or users.
R12-AR-New-Features
Release 12 : What’s New in Oracle Receivables Receivables.
Revenue Recognition
In R12 revenue recognition is based on Rules and Events, and they are:
· Time-Based Revenue Recognition
· Ratably Over Time
· Upon Expiration of Contingencies
· Event-Based Revenue Recognition
· Payment
· Customer Acceptance
· Rule-Based Revenue Recognition
· Payment Term Thresholds
· Refund Policy Thresholds
· Customer Credit worthiness
Lets take a quick look on some of the new changes:
· Daily Revenue Recognition
· Revenue distribution over full as well as partial accounting periods.
· Fulfills stringent accounting standards
· Accuracy to the number of days in the accounting period.
· Enhanced Revenue Contingencies :
· Fully Supports US GAAP and IAS
· User definable contingencies
· User definable defaulting rules for contingencies assignment
· Supports parent-child (e.g. Product and Service) relationship
· Integration with Order Management and Service Contracts
· User Interface as well as Programming Interface (API) support
· Access control through seeded Revenue Managers Responsibility
· Deferred Revenue Management
Event-Based Revenue Management in Oracle Receivables allows users to define revenue deferral reasons or contingencies and corresponding revenue recognition events. In Release 12, revenue contingencies for customer acceptance that are applied to goods sold in Order Management are now applied to services sold to cover those goods. Revenue is deferred for service ordered in both Order Management and Service Contracts. Acceptance contingencies associated with an item instance are automatically applied to service revenue associated with the item instance when it is covered in a Service Contract as a Covered Product. Revenue for services on other covered levels, subscriptions and usage is not impacted by contingencies applied to goods associated with those services.
Global Architecture
As we know, with in global architecture , these new things has been introduced.
· Sub ledger Accounting - Journal Creation takes place prior to GL.
· Bank Model - This unified model enables to park customer Bank as well as Internal bank information into there new model, so that working capital cash flow should be enhanced.
· EBusiness Tax - Oracle E-Business Tax is a new product that uniformly delivers tax services to all Oracle EBusiness Suite business flows. In Release 12, Receivables is enhanced to support
integration with the E-Business Tax product.
integration with the E-Business Tax product.
· Intercompany - This is enhanced by automatic balancing,
MOAC Control
This enhance you by enabling and performing tasks across operating Units (OUs), where you have access to without changing responsibilities.As we know , MOAC enables companies that have implemented a Shared Services operating model to efficiently process business transactions by allowing them to access, process, and report on data for an unlimited number of operating units within a single applications responsibility.In nutshell, once MOAC is enabled, then you can:
· Perform Setups for any OU
· Enter invoices across OUs
· Receive Cash for any OU
· Manage Customer Credit across all OU
· Run reports across OUs
Because of this greatly enhanced Role based security options, the ability to access multiple operating units with a single responsibility can simplify SOX compliance monitoring from finance controller side.
Line Level Cash ApplicationsThe Line Level Cash Applications solution allows the application of receipts to specific transaction items such as individual lines, groups of lines, or tax or freight buckets. From the receipt workbench,you are able choose whether to allocate cash to the entire transaction or to apply amounts against specific items according to the customer remittance.
· Apply to specific lines or groups of lines
· Indicate when tax, freight or finance charges only are paid
· Make changes as needed
· Easily view activity against receipts
· Know what historical activity affects your receipt
· See what prior activity affects a new application
Enhanced Customer Screen We have seen 11i Customer standard forms makes easier by simple navigation. This times there is clearer separation of the party and account layers, which makes a consist ant look and feel.More over full backward compatibility with 11i UI Bill Presentment Architecture has been provided.
The AR Create Customer page in R12 has eliminated the navigation to separate windows. Now, users can specify the following on a single page:
· Customer Information
· Account Details
· Address
· Account Site Details
· Business Purpose
RefundsOracle Receivables is fully integrated with Oracle Payables to deliver a seamless, automated process to generate check and bank account transfer refunds for eligible receipts and credit memos.
Late ChargesAs we know oracle receivables delivers enhanced Late Charges functionality enabling the creation of standard late charge policies that can be assigned to customer accounts or account sites.Flexible policy configurations include multiple interest calculation formulas, transaction and account balance thresholds, and currency-level rate setups. With new changes these are the enhanced functionality:
· Expanded assessment and calculation capabilities
· Tiered charge schedules
· Penalty charge calculation
· Integration with Balance Forward Billing
· Centralized setup and maintenance of late charge policies
· Calculation performed independent of Dunning and Statement processing
AR-AP NettingThe matching of open receivables and open payables is automated.
Balance Forward BillingThis makes easy transaction processing.
Balance Forward Billing is an enhanced version of the existing consolidated billing functionality for industries where customers are billed for all their account activity on a regular, cyclical basis.
Balance Forward Billing provides the ability to setup cycle-based billing at the account or account site levels, enable event based billing, and leverage user configurable billing formats provided by Oracle Bill Presentment Architecture.
A typical case can be best understood as
Balance Forward Billing is an enhanced version of the existing consolidated billing functionality for industries where customers are billed for all their account activity on a regular, cyclical basis.
Balance Forward Billing provides the ability to setup cycle-based billing at the account or account site levels, enable event based billing, and leverage user configurable billing formats provided by Oracle Bill Presentment Architecture.
A typical case can be best understood as
· Payment Term defaults
· from Site profile if Bill Level = Site
· from Account profile if Bill Level = Account
· Billing Date derived from transaction date and billing cycle
· Due Date derived from billing date and payment term
· Optionally select non-Balance Forward term if Override Terms = Yes
AP Interview Quations
1. What are the types of invoices?
2. What is difference between debit memo and credit memo?
3. What is meant by with-holding tax invoice?
4. What are the mandatory setups in AP?
5. What is the difference between PO default and quick match?
6. Use of recurring invoice?
7. Steps for payment batch?
8. Purpose of Payable invoice open interface?
9. Payable open interface import? (Expense Report Import)
10. Multi Currency payments?
11. Can we implement MRC at Payables?
12. Use of Distribution set?
13. Accounting Methods?
14. Use of automatic offset method?
15. What does the Unaccounted Transaction Sweep Report do?
16. What reports should I run before closing the period?
17. What is the program to transfer data from AP to GL?
18. What is meant by void payments?
19. What are the types of journal categories available in the AP?
20. What is meant by matching and what are the types of matchings available?
21. Types of Prepayments? And difference between them?
22. What is a Hold and Release
23. How to approve ‘n’ no. of invoices
24. What is Zero-Payment in AP
25. What is Proxima Payment Terms?
26. What are the tables associated with Invoice?
27. Which interface tables are used for Invoice Import?
28. What is 2 way, 3 way and 4 way matching?
29. What is Interest Invoice and how it can be created?
30. How many key flexfields are there in Payables?
31. Can you cancel the invoice? If yes, explain?
32. What is pay date basis?
33. What is terms date basis?
34. What is the report used to identify duplicate suppliers?
35. Difference between header level tax calculation and line level tax calculation?
36. What is meant by accrual write off?
37. Difference between quick payment and manual payment?
38. Use of Future dated payments?
39. Tell me steps for Period closing Process in AP?
40. Payable And Financial options?
41. What is meant by third party payments?
42. How to transfer funds between your internal banks?
43. Invoice Approval Process?
44. Can I find out which invoices are matched to a PO?
45. What is Intercompany Invoicing?
46. ERS Invoice means?
47. Use of Pay on receipt auto invoice?
48. What is meant by RTS transactions?
49. What are the steps to define a Bank?
50. Payment Methods?
2. What is difference between debit memo and credit memo?
3. What is meant by with-holding tax invoice?
4. What are the mandatory setups in AP?
5. What is the difference between PO default and quick match?
6. Use of recurring invoice?
7. Steps for payment batch?
8. Purpose of Payable invoice open interface?
9. Payable open interface import? (Expense Report Import)
10. Multi Currency payments?
11. Can we implement MRC at Payables?
12. Use of Distribution set?
13. Accounting Methods?
14. Use of automatic offset method?
15. What does the Unaccounted Transaction Sweep Report do?
16. What reports should I run before closing the period?
17. What is the program to transfer data from AP to GL?
18. What is meant by void payments?
19. What are the types of journal categories available in the AP?
20. What is meant by matching and what are the types of matchings available?
21. Types of Prepayments? And difference between them?
22. What is a Hold and Release
23. How to approve ‘n’ no. of invoices
24. What is Zero-Payment in AP
25. What is Proxima Payment Terms?
26. What are the tables associated with Invoice?
27. Which interface tables are used for Invoice Import?
28. What is 2 way, 3 way and 4 way matching?
29. What is Interest Invoice and how it can be created?
30. How many key flexfields are there in Payables?
31. Can you cancel the invoice? If yes, explain?
32. What is pay date basis?
33. What is terms date basis?
34. What is the report used to identify duplicate suppliers?
35. Difference between header level tax calculation and line level tax calculation?
36. What is meant by accrual write off?
37. Difference between quick payment and manual payment?
38. Use of Future dated payments?
39. Tell me steps for Period closing Process in AP?
40. Payable And Financial options?
41. What is meant by third party payments?
42. How to transfer funds between your internal banks?
43. Invoice Approval Process?
44. Can I find out which invoices are matched to a PO?
45. What is Intercompany Invoicing?
46. ERS Invoice means?
47. Use of Pay on receipt auto invoice?
48. What is meant by RTS transactions?
49. What are the steps to define a Bank?
50. Payment Methods?
Fixed Assets Interview Quations
1. What are the different ways of adding assets in FA?
2. How do we depreciate Assets in Oracle Applications?
3. What is the significance of asset books in FA? Types?
4.What is ment by retire asset? How do we retire assets in Oracle applications?
5. What are the various Journal Entries generated through fixed assets
6.At what level FA is implemented?
7.What is the profile used to secure asset register?
8.What are the asset types in FA Module?
9.What are the different calendars used in FA Module?
10.Is FA Supports Multi _org?
11.What is ment by Roll back depreciation?
12.What are the mandatory flexfiels used in FA?
13.What are the depreciation methods used in FA module?
14.What is ment by prorate convention?
15.What is the use of allow amortized changes check box?
16.What is the difference between Quick addition and detail addition?
17.What is ment by projection?
18.What is ment by what-if analysis?
19.What is ment by leased asset?
20.What is ment by depreciation override? Can we override depreciation?
21.What is ment by physical inventory reconciliation?
22.Tell me something about asset insurance?
23.What is ment by asset revaluation?
24.In prepare mass additions window what are available Q names?
25.what is the difference between initial mass copy and periodic mass copy?
26.what is internal retairment?
27.What experience do you have in FA Module Implementation?
28.What do you know about FA to GL cycle?
2. How do we depreciate Assets in Oracle Applications?
3. What is the significance of asset books in FA? Types?
4.What is ment by retire asset? How do we retire assets in Oracle applications?
5. What are the various Journal Entries generated through fixed assets
6.At what level FA is implemented?
7.What is the profile used to secure asset register?
8.What are the asset types in FA Module?
9.What are the different calendars used in FA Module?
10.Is FA Supports Multi _org?
11.What is ment by Roll back depreciation?
12.What are the mandatory flexfiels used in FA?
13.What are the depreciation methods used in FA module?
14.What is ment by prorate convention?
15.What is the use of allow amortized changes check box?
16.What is the difference between Quick addition and detail addition?
17.What is ment by projection?
18.What is ment by what-if analysis?
19.What is ment by leased asset?
20.What is ment by depreciation override? Can we override depreciation?
21.What is ment by physical inventory reconciliation?
22.Tell me something about asset insurance?
23.What is ment by asset revaluation?
24.In prepare mass additions window what are available Q names?
25.what is the difference between initial mass copy and periodic mass copy?
26.what is internal retairment?
27.What experience do you have in FA Module Implementation?
28.What do you know about FA to GL cycle?
AR Interview Quations
1. How many Address’s can have one Customer?
Primary Address, Bill – To – Address, Ship – To – Address
2. Customer Number Always Automatic / Manual?Any thing Either Manual or Automatic
3. What are the Mandatory Address’s you should create a Customer for Communicate him?
Remit – To – Address
4. Can U Merge the Customers? If How?
Using the Merging Customer Window
5. What is Accounting Rules?
It is For Generating Revenue Recognition Programs like Monthly, Quarterly
6. What is Invoicing Rules?
The Invoicing Rules Helps you when you receive data from Outside systems like Auto Invoices how the data should insert and It contains 2 rules Advance Invoice, Arrears Invoice.
7. Where should the customers send the payments of Invoices?
Remittance Banks or Vendor Places
8. What is the Transaction Type?
It describes us Whether you want transfer the Receivables data into General Ledger or not. And also when ever you create an invoice what are the accounts should be effected and also the sign of Transaction also.
9. What is a Transaction Source?
It is For Invoice or Invoice Batch numbers whether automatically or manually
10. How many Transactions we have?
Six, Credit Transactions: Invoice: Debit Memo: Charge back: Guarantee: Deposit
11. How can i reduce the Invoice amount?
Using with Credit Transactions
12. What are the Accounts to be use in Transaction Types (Few)?
Revenue, Receivables, Freight, Tax, Clearing, Unearned, Unbilled
13. How can i Assign a Deposit amount to an Invoice?
In the Invoice Window “Commitment” Region
14. What is the Guarantee?
It is agreement between both sides for goods or services in the future , specific range of periods
15. Give the Navigation for Credit Transactions?
Transactions/Credit Transactions
16. How many ways you can apply the Receipt Amount?
Application: Mass Apply
17. How will you know a Customer Balance Amount?
Using with the Customer Account Overview window
18. Can U Define Customer Agreements using with AR?
No, In the Oracle Order Entry Module
19. What are Aging Buckets?
It is for Outstanding Reports purpose the no of days in various ranges
20. How will U View the Outstanding Balance of a Customer?
Generating the Aging Buckets Report
Its impressive to know something about your note on Oracle apps functional Course. Please do share your articles like this your articles for our awareness. Mostly we do also provide Online Training on Cub training oracle apps functional course.
ReplyDeleteGreat content
ReplyDelete