RELEASE 12 Upgrade Considerations by Product (FINANCIALS

Applications Release: Author: 12

Financials Product Development

Creation Date: January 22, 2009 Last Updated: File URL: Draft / Version: v6.0 Status: Final March 8, 2010

Table of Contents
Table of Contents ...............................................................................................................2 Introduction ........................................................................................................................3 Oracle Advanced Collections ............................................................................................4 Oracle Advanced Global Intercompany Systems ...........................................................6 Oracle Assets ....................................................................................................................10 Oracle Cash Management ...............................................................................................13 Oracle General Ledger ....................................................................................................16 Oracle Legal Entity Configurator ..................................................................................21 Oracle Payables ................................................................................................................24 Oracle Payments ..............................................................................................................30 Oracle Receivables ...........................................................................................................34 Oracle Subledger Accounting .........................................................................................39 Oracle E-Business Tax.....................................................................................................43


This document is a supplement written by professionals in Oracle’s Product Development organization that provides product level considerations to help you understand the issues that your project team should consider when upgrading to E-Business Suite Release 12. It describes the significant new features available in Release 12 and then gives process changes, configuration changes and considerations as relevant for each product. It should be used in conjunction with the published product specific user and implementation guides for Release 12 when planning your upgrade. Prior to reviewing this document, the reader is advised to be familiar with the following Release 12 documentation: Oracle Financials Concepts Guide Oracle Financials Implementation Guide Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to Release 12.


Oracle Advanced Collections
Release 12 of Oracle Advanced Collections extends transactional and customer data in collection management processes within and across operating units (OUs). New MultiOrg Access Control security profiles manage each collector’s access to operating units to which they are assigned. This provides them with the visibility to customer data and balances within or across OUs on their collector work list and specific screens for a more complete understanding of each customer’s collections situation. Other new features in release 12 Oracle Advanced Collections include: • • •
New Implementation Checklist and Setup Screens

Improved Payment Processing and Customer Funds Capture through integration with Oracle Payments Use of Oracle Territory Management to Define Collections Territory Hierarchies

Finally, the collections workbench in Oracle Receivables has been replaced with functionality from Oracle Advanced Collections. Details on the collections features available in Oracle Receivables and Oracle Advanced Collections are provided in Oracle MetaLink Note 389443.1. Planning Considerations If you have used the Collections Workbench in Oracle Receivables you must upgrade to either Oracle Advanced Collections or the new functionality in Oracle Receivables. Oracle Advanced Collections provides the flexibility and high degree of configurability required by enterprise collections agents and managers responsible for managing delinquent customers and collections-related issues. It includes configurable scoring and strategy management tools, configurable customer metrics, later-stage collections tracking capability, and is directly integrated to a number of other Oracle EBS products including Oracle Territory Manager, Oracle Trade Management, Oracle Leasing and Oracle Loans. The collections functionality available in Oracle Receivables is intended for AR clerks who occasionally perform collections activities. Receivables users who have not purchased a license for Oracle Advanced Collections are not authorized to use the full feature set of this product. Therefore, your planning team should consider the long-term operational requirements of your collections group and upgrade to the appropriate collections management capability that best fits those requirements.


fax or print o Optional dunning calls assigned to collector for follow up Considerations • Collections scoring and collections strategies are not extended to OU level. strategies and work items. • Customer call activity created in Oracle Receivables prior to upgrading to Release 12 can be viewed from the Collections History tab by selecting “Receivables Calls” from the “Type” List of Values. and metrics) in pre-production phases of your upgrade. collections agents will be able to see across operating units and will need to consider this additional information as they review and work with customer accounts. some organizations run their scoring or dunning processes in synch with their billing cycles while others run them more frequently. Highest level for these are still ‘Customer’ • Dunning plan capability is available for both Advanced Collections and Receivables users. For instance. 5 . • Based on MOAC security. collections territories can be created in Oracle Territory Manager to facilitate and manage customer assignment and customer-related work assignment. Then add or adjust those elements as needed. Configurable collections strategy management (which also supports dunning activities) is available in Oracle Advanced Collections. Configuration Change • Start by using the new Collections Implementation Setup tool to create preproduction collections systems for conference room pilots and testing.Process Change • Pay heed to the order and frequency in which the concurrent programs that automate the collections processes are run. • Review and use the pre-configured elements (correspondence templates. • For collections organizations where collectors or collector groups are responsible for managing specific customers. scoring models. • Aging-based dunning plans in R12 (for either Advanced Collections or Receivables users) include: o Configurable dunning letter templates using Oracle BI Publisher o Output as email. See Oracle Advanced Collections Implementation Guide and Oracle Advanced Collections User Guide for more information. your production collections system settings can be easily modified with the Setup Tool when changes are needed. • New collections scoring models and customer metrics in Oracle Advanced Collections are best configured by qualified DBAs. Once you go live. prior to going live with the module. New scoring and metrics are usually created during your upgrade project.

• Support true legal entity for intercompany transactions between legal entities. Process Change • Accounting Setup Manager in Release 12 has a separate setup screen for Intercompany / Intracompany accounts. The key components of the Advanced Global Intercompany System are: • Intercompany Balancing • Manual Intercompany Transactions • Intercompany Invoicing • Intercompany Reconciliation Intercompany Balancing Overview: Intercompany Balancing calculates intercompany accounting when transactions are entered directly in the Advanced Global Intercompany system. Intercompany Balancing uses the same single set of intercompany accounts and rules for consistent accounting treatment throughout Financials. Legal entity configuration is not needed for intracompany balancing between pairs of balancing segment values within the same legal entity. GIS data is upgraded to AGIS.Oracle Advanced Global Intercompany Systems Oracle Advanced Global Intercompany Systems is a new product in Release 12. During the R12 upgrade. • Release 12 supports legal entity integration with intercompany balancing rules for intercompany accounts when two legal entities trade. and also when intercompany transactions occur in Oracle General Ledger and Oracle Subledger Accounting. • Track trading partners in a separate optional intercompany segment. replacing the Global Intercompany System in earlier releases. It allows companies to streamline intercompany processing and facilitates intercompany reconciliation. and you can then use R12 functionality to: • Define all intercompany accounting definitions centrally. • Maintain separate intracompany accounting for transactions between balancing segments in the same legal entity. 6 . • Intercompany balancing supports separate Intercompany Payables and Intercompany Receivables accounts rather than a single intercompany due to/due from account.

It will automatically be populated with the balancing segment value of the trading partner to provide more detail for reporting and reconciliation. GIS data is upgraded to AGIS. currency. map them either to ledgers or balancing segment values. one for one.• You can create an optional intercompany segment in your chart of accounts structure. A user may be given access to many different intercompany trading partners regardless of the responsibility used to log in. you need to setup legal entities for transacting subsidiaries. Auto-Accounting rules in GIS are not upgraded. In some cases the automatic upgrade may not have been able to identify one and only one legal entity to associate to an intercompany organization. • To use intercompany accounting rules. • Maintain intercompany periods to control timing of transactions (eg during period close) and close intercompany periods by transaction type. • Grant user access to multiple subsidiaries from a single responsibility. Configuration Change • The R12 upgrade converts intercompany accounts created in GIS into intracompany balancing accounts and rules. and specify them as intercompany organizations. GIS subsidiaries will be converted to intercompany organizations. In that case the organization will be inactive and must be updated with the correct legal entity before it can be used in transactions. and need to be set up as Account Derivation Rules and compiled with the Transaction Account Builder in Subledger Accounting. As part of the upgrade. During the R12 upgrade. with optional proration of amounts across recipients. Security grants are created for the users based on the subsidiaries assigned to the responsibilities that each user was assigned. calendar). • Optionally create intercompany invoices between subsidiaries automatically • Use Oracle Approvals Manager for intercompany transaction approvals. You need to verify post-upgrade that the correct legal entity has been assigned to the intercompany organization so that it can be used. and you can then use R12 functionality to: • Create Intercompany Batches for transactions to multiple recipients (no restriction on COA. Considerations • See Oracle Advanced Global Intercompany System Release 12 Roadmap Document • See Advanced Global Intercompany System White Paper Manual Intercompany Transactions Overview The Manual Intercompany Transaction window facilitates intercompany transaction processing between different legal entities under one or more ledgers. 7 . • The R12 Grant Based Security Model maps intercompany organizations to users instead of responsibilities.

intercompany function security and data access). • GIS transaction types are upgraded to the new intercompany system transaction types. In order to take advantage of the new invoicing feature in AGIS. you should manually select the Allow Invoicing check box for transaction types where invoicing is required. Intercompany Invoicing Overview Advanced Global Intercompany System interacts with the subledgers to facilitate creation of a physical invoice for an intercompany transaction in both Receivables and Payables. When GIS transaction types are upgraded. the invoice number is then automatically used to create a consistent mirror-image invoice in Oracle Payables. Considerations • See also configuration changes / considerations for Intercompany Balancing – these apply to all intercompany setup (eg setting up legal entities and mapping them to intercompany organizations. Release 12 highlights for Intercompany Invoicing: • Intercompany uses Oracle Receivables to produce invoices for the initiator. • All GIS new and completed transactions are upgraded as AGIS transaction batches. the Allow Invoicing option is set to Not Required. Configuration Change • Setup and assign operating units to ledgers (as part of Accounting Setup Manager) in order to use intercompany invoicing within the subledgers. for each GIS transaction a batch is created.Process Change • New workbench for entering manual intercompany transaction batches. Once the Receivables transaction is completed. • Setup intercompany invoicing options. In order to take advantage of the new invoicing feature in AGIS. the Allow Invoicing option is set to Not Required. you should manually select the Allow Invoicing check box for transaction types where invoicing is required. Generally. 8 . Configuration Change • Approvals Manager setup • Optionally create intercompany calendar / periods to control timing of intercompany transaction entry. When GIS transaction types are upgraded. Process Change • Create intercompany invoices automatically where statutory or business practices require them. creating intercompany accounts and rules.

See Oracle Advanced Global Intercompany User Guide for more information. Process Change • Need to run data extract program to populate XML data before using the intercompany reconciliation report. • View intercompany out-of-balance accounts and drill down to details of the subledger accounting and documents. Map the intercompany organizations that are trading partners to AP Suppliers and AR Customers in TCA. Considerations • Intercompany invoices are only created for manual intercompany transactions (i. Release 12 highlights for Intercompany Reconciliation. 9 . Intercompany Reconciliation Overview Intercompany provides reconciliation tools to sort out any discrepancies in accounting balances between the intercompany organizations. • Optionally download report output to Excel for additional analysis.e.• • Create additional AR customers and AP suppliers to represent your company’s subsidiary legal entities. • BI Publisher technology for reconciliation reporting: the layout is fully customizable and can be downloaded to desktop tools (eg Excel or Word) for further analysis. Configuration Change • Optional – customize BI Publisher report layouts. • Creation of additional customer / supplier records and mapping to intercompany organizations is not done automatically as part of the upgrade. not for intercompany journal entries entered directly in GL).

Automatic Depreciation Rollback o Depreciation is rolled back automatically when any transaction is performed on an asset if the period has not yet been closed. which is the common accounting platform for all E-Business Suite sub ledgers. o Executed only on select assets as required and not on the entire asset book. Automatic Preparation of Mass Additions o Default rules and public APIs can be used to populate expense account.Oracle Assets In release 12. depreciation method. industry or geography requirements concurrently in a single instance through configurable rules. asset category and other required fields to complete the preparation of mass addition lines automatically. bonus rule ceiling name. o Asset life. • Subledger Accounting(SLA) Architecture and Inquiries o Oracle Assets is fully integrated with SLA. o No longer required to run depreciation rollback program manually. Enhanced Mass Additions for Legacy Conversions: o Populate depreciation attributes directly in the FA Mass Additions interface table or via? Web ADI (application desktop integrator). Flexible Reporting using XML Publisher Enhanced Functionality for Energy Industry • • • • • Process Change • Prepare Mass Additions process provided in Release 12 automatically populates all the required information for mass additions lines. This means complete automation of legacy conversions. o It enables you to comply with multiple legislative. resulting in a faster period close. Oracle Assets has introduced several enhancements to improve the efficiency of key Assets processes like mass additions and period end close. prorate convention. depreciation limit are some of the attributes that have been added to the interface table in Release 12. o Could significantly reduce the overhead associated with manual preparation of mass addition lines. rather than accepting default values from the asset category. Mass 10 .

accounting records were not created until after depreciation had run. After the upgrade. you can create custom logic coded in a public API to pre-populate these values. The Create Deferred Depreciation Journal Entries program is now obsolete. During upgrade. Configuration Change • New configurable rules for automatic preparation of mass additions. o In addition. you can run the SLA post-upgrade process to update accounting for past transaction data as needed. Prior to Release12. For example. the key setup steps are: o Compile the Application Accounting Definition in SLA. • Generic Subledger Accounting Architecture configuration has been discussed in a separate section of this document. Please note that the pre-seeded account derivation definitions have been provided for Assets. however. backdated transfers and retirements. Users now need to run Calculate Deferred Depreciation followed by Create Accounting. you would not see any addition accounting lines if depreciation had not been run. The Account Drill Down report has been replaced the Account Analysis report. Post upgrade. these records would appear in the Transaction History form for additions. and the period remains open. You can use the seeded account derivation definitions or modify them as required. Accounting for current period depreciation will be upgraded only if depreciation has already run for the period.• • • • • additions data may be optionally verified before posting the mass additions lines. 11 . default rules populate the asset category based on the clearing account from the asset category setup (if there is a one to one match). o If the default rules do not satisfy your requirements. In summary. o Complete the Accounting Setup flow in Oracle General Ledger. backdated additions. transactions in the current fiscal year in Assets books will have their accounting lines migrated to the Subledger Accounting model. if you added an asset and went to the Transaction History form. Create Journal Entries has been replaced by Create Accounting. The Create Journal Entries and Rollback Journal Entries programs are now obsolete. New SLA Accounting report and online account inquiry provided. o You can use default rules provided by Oracle where the expense account is derived from the clearing account by replacing the natural account segment from the asset category.

etc). 12 . theft. • In Release 12. See Oracle Assets User Guide for more information. sale. However. These accounting rules can be configured in SLA without complex customizations on your part. Oracle continues to support Account Generator functionality for existing asset books.Considerations • You may have to look carefully at the clearing account in your category setups if you are planning to use default rules for automatic preparation of mass addition lines. the default rules will not work effectively. the common SLA platform provides many opportunities to implement complex accounting rules without customizations. If you have been using the same clearing account across different categories. some of our customers have requirements where the retirement account is different based upon the type of retirement (missing. For instance.

the format and content of the Bank Number. Portugal. Denmark. however. Oracle Treasury and Oracle Cash Management are centrally defined and maintained in Oracle Cash Management. Oracle Receivables. • The system supports country specific validations for the bank account and address format. The key new features in Release 12 are: • • • Centralized Internal Bank Account Model Bank Account Transfers Bank Account Balances and Interest Centralized Internal Bank Account Model Overview In Release 12. In Release 12. Any operating unit under the same legal entity can be granted access to the same bank account. you will need to link a bank-counterparty in Treasury to the bank branch in Cash Management. Account Number and Check Digit will vary according to the country specific rules. Internal bank account maintenance. Process Change • Internal bank account usage in Oracle Payables.Oracle Cash Management Oracle Cash Management is an enterprise-wide solution for managing liquidity and controlling cash. Configuration Change • There is new user interface in Oracle Cash Management for bank. The countries that are supported are Austria. using Treasury’s Counterparty Profiles window. Oracle Treasury and Oracle Cash Management does not change in Release 12. Finland. Netherlands. is done differently as described below. When creating new bank accounts. • Bank account reconciliation parameters are now defined at the bank account level. Oracle Payroll. Windows related to internal bank account maintenance in Oracle Payables and Oracle Treasury have been made obsolete. Norway. Oracle Cash Management starts leveraging several architectural cross-product features such as Multi-Org Access Control and Subledger Accounting. Oracle Receivables. Spain. Branch Number. internal bank accounts for use in Oracle Payables. France. • Privileges to maintain bank accounts are granted to a user role by legal entity in the Oracle User Management security wizard. • Internal bank accounts are owned by legal entities. • Before you can enable bank account usage in Oracle Treasury. Belgium. 13 . Oracle Payroll. bank branch and bank account maintenance.

existing internal bank accounts defined in Oracle Payables and Oracle Treasury are migrated one-to-one into the new bank account model in Oracle Cash Management. Bank Account Transfers Overview In Release 12. Luxembourg. Greece. • Accounting configuration for bank account transfers is done in subledger accounting. Italy. Considerations • Bank account transfers can be created in the system automatically if you have zero-balance accounts (ZBAs) with your banks. Iceland. Users can define additional journal line definitions for bank account transfer creation and cancelation. Configuration Change • Privileges to create bank account transfers are granted to a user role by legal entity in the Oracle User Management security wizard. Germany. • Reusable bank account transfer templates can be created for accelerated data entry. • Bank account transfers can be created intra-company (between two bank accounts belonging to the same legal entity) or inter-company (between two bank accounts belonging to two different legal entities). If you previously had to create two separate bank account records to represent the same real life bank account because it was used by two different operating units. • Settlement of bank account transfers is done via Oracle Payments. United Kingdom. Switzerland. Process Change • New user interface is available for capturing and. Considerations • During the upgrade. separately authorizing bank account transfers. you will need to define inter-company accounts in Oracle Advanced Global Intercompany System in order to create proper journal entries. settle them through Oracle Payments and account for them using Oracle Subledger Accounting. Sweden. Ireland. users can create cash transfers between internal bank accounts. after the upgrade you will have the option to disable the duplicate bank account and allow both operating units to use the single bank account. Colombia.Brazil. and United States. This will simplify bank account maintenance and bank reconciliation. • If you plan to create inter-company bank account transfers. Seeded journal line definitions are provided for bank account transfer clearing and un-clearing. 14 . Poland.

15 . The data. you can keep track of multiple balance types: ledger. is replicated between Cash Management and Treasury for bank accounts used in Treasury. however. Oracle Cash Management provides robust functionality for bank account balance reporting. are now a part of the internal bank account definition in Cash Management. 2-day float. Before bank balance interest can be calculated. available. so that the interest accrual and settlement can still be performed in Treasury. • Basis. Interest Rounding. previously defined at the bank account balance level in Treasury. • Projected closing bank account balance can be saved alongside actual bank account balances using the new button in the Cash Position window. Considerations • Interest amount can be calculated for both standalone bank accounts and notional cash pools. are now a part of the interest rate schedules in Oracle Cash Management. Portfolio Code. value dated. In addition. Pricing Model and Limits. Process Change • There is new bank balance maintenance user interface in Oracle Cash Management. It should be noted that the system does not calculate any of these balance types. projected month-todate average. Day Count Basis and Interest Includes parameters. They can be populated manually or from the bank statement. Configuration Change • There is a new user interface to manage interest rate schedules. • For each bank account and balance date. See Oracle Cash Management User Guide for more information. interest rate schedules have to be defined and assigned to bank accounts. Bank balance maintenance in Oracle Treasury is disabled. 1-day float. previously defined at the bank account balance level in Oracle Treasury. and year-to-date average. bank balance interest can be calculated for bank fee or credit verification. both online and via concurrent programs with Oracle BI Publisher.Bank Account Balances and Interest Overview In Release 12.

The upgrade creates a separate accounting setup for each primary ledger that is upgraded from a set of books. You can perform simultaneous accounting for multiple reporting requirements. then they will be associated to a primary ledger in an accounting setup. 16 . charts of accounts and/or calendars. Centralized Accounting Setup Overview: In Release 12. Process Change • Accounting Setup Manager is used to create and maintain accounting setups. Release 12 highlights for Oracle General Ledger include.Oracle General Ledger In Release 12. • Centralized Accounting Setup • Data Access Sets • Ledger / Ledger Set Architecture • Replacement for Disabled Accounts Note: There is also a terminology change between Release 11i and Release 12: Sets of Books are upgraded and renamed to Ledgers – the upgrade retains all 11i settings. o Operating Units: All HR Organizations classified as operating units will be preserved in Release 12. Legal entities can be assigned to a ledger and balancing segment values can optionally be mapped to legal entities to help identify transactions by legal entity. You can also gain processing efficiencies by setting up. the Accounting Setup Manager centralizes the setup and maintenance of common accounting-related setup that is shared across Oracle Financials applications. accessing. and processing data across multiple ledgers and legal entities from a single responsibility. An accounting setup defines the accounting context for one or more legal entities or other business entities. • Secondary ledgers and reporting ledgers to create alternate accounting representations automatically. for example: • Definition of legal entities and associated accounting setup to meet different accounting principles and reporting requirements of multiple countries using different currencies. o Legal Entities: HR Organizations classified as GRE/LEs in Release 11i will be upgraded legal entities in Release 12. Oracle General Ledger is significantly enhanced to support multi-national companies and shared services centers. If operating units are assigned to a set of books.

Payables. Configuration Change • Create legal entities and assign them to accounting setups – either assigned to ledgers or mapped to balancing segment values. Global Accounting Engine. o Secondary Ledgers: Multiple-posting set of books (Global Accounting Engine) will upgrade to secondary ledgers. This 17 . the settings on the reporting currency will automatically be changed to be synchronized with the source ledger. If you modify any of the ledger options for the source ledger after the upgrade. For US Federal customers. Journal entries may have multiple legal entities (each accounting line may be different). The subledger accounting method enables Oracle General Ledger to integrate with Oracle subledgers using Subledger Accounting. • Create primary and secondary ledgers and mappings for alternate accounting representations from single transaction (replacement for the Global Accounting Engine Dual Posting solution in Release 11i). The upgrade will preserve the Release 11i settings. o Subledger Accounting Method: All upgraded ledgers in Release 12 will have a subledger accounting method assigned during the upgrade. Considerations • Sequencing is determined by the ledger. o Reporting Currencies: Multiple Reporting Currency (MRC) reporting sets of books become reporting currencies in Release 12. All upgraded. Assets. but in Release 12 these options cannot be manually updated for reporting currencies because the reporting currency will inherit its settings from its source ledger. so there is no distinct legal entity of the journal header. o Intercompany Accounts: The Release 11i Global Intercompany System (GIS) will be replaced by Advanced Global Intercompany System (AGIS) and GIS features will be migrated to the corresponding features in AGIS. Any reporting currencies assigned to the ledger inherit the subledger accounting method from the source ledger. • You can run the Accounting Setup Manager Pre-Update Diagnosis Report to view your Release 11i setup for Multiple Reporting Currencies. non-publicsector ledgers will have a subledger accounting method assigned called Standard Accrual or Standard Cash. users could change settings for certain options on a primary set of books independently of its reporting set of books. • In Release 11i. all upgraded ledgers will have the US Federal Accounting subledger accounting method assigned to them. General Ledger. and Receivables.o Primary Ledger: Most sets of books in Release 11i will become primary ledgers in Release 12. All upgraded public sector ledgers will have a subledger accounting method assigned called Encumbrance Accrual or Encumbrance Cash.

you must assign a data access set to the GL: Data Access Set profile option at the Site. 18 . • Data access sets work with cross–validation rules and flexfield value security rules. you can limit a user's access to a legal entity's data by creating a data access set that secures read and write access to specific balancing segment values or legal entities. • (Optional) Manually create data access sets to further control read and write access to ledgers. if you have a shared accounting setup where multiple legal entities share the same primary ledger. or read and write access. balancing segment value or management segment value. Application. • Privileges allow you to grant users’ read only or read/write access to specific Balancing segment values within a ledger. or to specific ledgers. • Grant read-only user access. but rather control General Ledger security behind the scenes. or specific balancing segment values or management segment values for a ledger or ledger set. those rules are combined with data access set security. This allows you to: • Secure user access to data by ledger. or portions of data. The system-generated data access sets created for each ledger and reporting currency provide full read and write access to the ledger and all of its balancing segment values and management segment values. ledger identifies potential problem areas where you may want to modify your setup in order to take advantage of new Release 12 functionality. Configuration Change • The General Ledger Accounting Setup Program automatically creates a data access set for each ledger and reporting currency (journal level or subledger level) assigned to a completed accounting setup. Process Change • Process changes do not directly impact users. or Responsibility level. Data Access Sets Overview Data access sets allow users to access multiple ledgers and ledger sets within General Ledger from a single responsibility. For example. If flexfield value security rules are defined that prevent certain responsibilities from accessing certain segment values. • Security allows you to secure users’ access to data. Considerations • All ledgers and ledger sets assigned to a data access set must share the same chart of accounts and accounting calendar/period type combination. • To associate a data access set to a responsibility.

and ledger sets can contain other ledger sets. 19 . You must have at least read access to the data to view it on a report. Considerations • The same ledger can belong to multiple ledger sets. Ledger sets allow grouping of ledgers with the same chart of accounts and calendar / period type. Ledger / Ledger Sets Architecture Overview Sets of books are upgraded to ledgers in Release 12. Flexfield value security rules are still applicable for the other segments of the accounting flexfield. Ledger sets facilitate the following accounting operations across ledgers: • Open / close periods for multiple ledgers simultaneously • Submit concurrent programs for all ledgers in a ledger set • Cross ledger allocations. recurring journals and year-end closing journals • Currency translation for multiple ledgers simultaneously • Financial reporting (FSGs) across ledgers • Account inquiry across ledgers Process Change • Management of multiple ledgers simultaneously by grouping them into ledger sets Configuration Change • Create ledger sets to group ledgers with the same chart of accounts and calendar / period type. The system automatically creates a data access set each time you define a new ledger set. If you have read-only access to a ledger. This allows you to group the primary or secondary ledgers with their associated reporting currencies to reduce maintenance efforts and streamline processing. They do not have to share the same currency. • Assign ledger sets to data access sets for user access and security.• • • Use data access sets instead of flexfield value security rules to secure read and write access to balancing segment values and management segment values. you must assign the ledger set to the profile option GL: Data Access Set. or read and write access only to some of its balancing segment values and management segment values. Before you can begin using the ledgers contained in your ledger set for transaction processing. The system generated data access set provides full read and write access to the ledgers in the ledger set. you will not be able to open and close its accounting periods. FSG report output takes into account data access set security and only shows the data accessible for your responsibility. to allow processing across multiple ledgers simultaneously.

Replacement for Disabled Accounts Overview Prevent errors & reduce manual intervention in the journal import process by defining a replacement account for disabled accounts. Process Change • None Configuration Change • Define alternate accounts when creating GL account combinations. See Oracle General Ledger Implementation Guide. Oracle General Ledger Reference Guide and Oracle General Ledger User Guide for more information. If specified. Both the source ledger and its reporting currency must have the same open periods to prevent problems during posting in the general ledger.• Use a ledger set to combine the source ledger with its reporting currencies (journal and subledger levels) to open and close periods across all ledgers simultaneously. the alternate account is used by the Journal Import process and the Create Accounting program in Subledger Accounting to replace the original account combination if it is disabled or end-dated. 20 .

• The legal entity is determined as follows: o Each transaction exists within an operating unit and that OU has a ledger which will account the transactions. Batch Source Assigning a LE to a transaction type or batch source is optional and only the LE’s mapped to the ledger associated with the OU are available to assign. You will be able to define legal entities to meet different statutory principles and reporting requirements of multiple countries and jurisdictions. If that ledger has more than one legal entity associated with it.Oracle Legal Entity Configurator In Release 12. the user must explicitly provide it during transaction entry. For values to show up in the LOV associated to a default legal context. Transaction Type 2. The Legal Entity architecture allows you to represent the legal organization structure separately from the operational business structure. o If no default legal entity value is found from any other source. o Legal entity can also be defaulted from the default legal context of an operating unit if no other default exists. Oracle E-Business Suite is moving from an implicit definition of legal entities to an explicit one. • Additional information: 21 . This legal entity definition is used in the following business processes: o Payment runs by legal entity o Intercompany (legal entity subsidiaries that trade with each other) o Tax calculations (legal establishments that are registered with a tax authority) o Bank account ownership o Ownership of subledger transactions (eg in Payables or Receivables) o Reporting at the legal entity level Process Change • Subledger transactions are stamped (at header level) with the owning legal entity in addition to an operating unit. Overview The Legal Entity Configurator allows you to define legal entities to meet statutory principles and reporting requirements of multiple countries or legal jurisdictions. then a hierarchy of LE derivation is used to default an LE. an LE must be associated to the ledger that is assigned to the OU. A highlight of Release 12 is the Legal Entity Configurator which guides the user through the LE creation process. For example in AR the legal entity derivation hierarchy for transactions is 1.

• Sequencing on transactions is still by o Release 12: Legal Entity Uptake Configuration Change • Migration of existing data into legal entities (eg GRE/LEs. But after migration there is no link between an HR organization of type 'GRE/LE' and an LE created using the Legal Entity Configurator UIs. • If legal entities differ in any of the 4Cs or require different ledger processing options (like average daily balances. calendar. It may be possible to group multiple ledgers into ledger sets for easier processing if need to setup multiple ledgers for legal reasons. it is possible for them to use the same ledger – depending upon your business needs.o How do I define my Legal Entities? http://davidhaimes. • Use Legal Entity Associations to maintain the association between business constructs (operating units.recommended for easier identification of transactions and for reporting purposes. AP Reporting Entities. HR Organization cannot be used for creating a new LE in Release o Can I assign an operating unit to 2 legal entities? http://davidhaimes. accounting method). You can also assign balancing segment values to legal entities that share the same ledger . inventory organizations.wordpress. • If your legal entities share the same ledger attributes (such as chart of accounts. Brazilian Companies and Global Descriptive Flexfields) • Create legal entities and assign them to accounting setups. separate primary ledgers are required. One way of determining the operating units associated with a 22 • . or sequencing). VAT Reporters. Although it is a source for upgraded legal entities. • Assign legal entities to intercompany organizations (if using AGIS). In Release 12 there is no direct relationship between an operating unit and a legal entity. • Configure existing organizations to be legal entities or establishments as appropriate. inventory locations etc) and legal constructs (legal entities and establishments). Note that balancing segments are required for intercompany accounting between legal entities that share the same ledger.oracleappshub. not by legal entity. Considerations • There is no Legal Entity uptake in Oracle General Ledger or Oracle Assets – instead the ledger or balancing segment value is used. An organization of type GRE/LE is used as a source for creating an LE during the R12 upgrade. journal approval.wordpress.

Release entity is via the ledger associated with both the legal entity and the operating unit. implement. and use this product in Release 12. Note that there may not be a unique relationship between a legal entity and an operating unit. install. See the Oracle Legal Entity Configurator Release 12 Roadmap Document which describes the published information available for Oracle Legal Entity Configurator. Use this document to ensure that you leverage all existing resources to learn about. 23 .

Configuration Change: • When new suppliers are created the system creates a TCA party behind the scenes.Oracle Payables In R12. 24 . • Some payment and tax related information is no longer maintained in the supplier sites tables . accounts etc. Oracle E-business tax). • Managing the attributes specific to particular functional areas such as Oracle was moved to the appropriate product tables (Oracle Payments. It also allows easier cross-product integration. are maintained in the supplier sites tables. Purchasing and Receiving can be controlled with the use of Function Security. Process Change • New user interface presents a clear distinction between the supplier’s company details and terms and controls for the trading relationship. • Addresses can be entered and formatted based on country specification. • Adding new locations or relationships with additional operating units is streamlined. • Supplier Representation in TCA (Trading Community Architecture) • Invoice Lines • Payment Process • AP-AR Netting Supplier Representation in TCA Overview Trading Community Architecture is a data model that allows the deploying company to maintain information about its parties (customers. suppliers. Considerations • Existing suppliers. banks etc) and their relationships with the deploying company in a centralized place. address and contact information. sites or locations and their contact information are automatically created in TCA. • Each supplier is associated with a party and each supplier site is associated with a party site. The parties are created with a party usage of “supplier” • Procurement and Payables specific attributes like terms and conditions. The information that will be stored in TCA includes supplier name and legal information. Oracle Payables has made some significant changes in the following areas. thereby providing a single source of truth.

Hence.• • • • • • • • Existing tables that hold the supplier information are moved to a new set of tables (AP_SUPPLIERS). 25 . a new party site will also be created. • Redesigned matching windows for PO/Receipt matching can be invoked from the Invoice Workbench. • Tax. as well as tax. as well as enhancing the matching function. freight. The new invoice structure also more accurately models Oracle Procurements PO shipment. The contacts are always transferred to the merged supplier site specified in the supplier merge form. freight and other charges. • Users can enter freight at the invoice header and then prorate it across all item lines on the invoice. New views. based on the old supplier table names have been added for backward compatibility. Invoice lines that were generated by matching will generate distributions at the time of match. Invoice Lines Overview The addition of invoice lines allows Oracle Payables to better model the paper or electronic business document by representing the goods or services. the associated party or party site does not change. During the supplier merge process. and miscellaneous type invoice lines can be prorated to all item lines on an invoice. • Freight/miscellaneous lines created automatically via request to the matching process from the matching windows do not automatically generate distributions at line creation time. Supplier or supplier site merge does not affect contacts. a new supplier site must be created. when a supplier site is “copied” from one supplier to a different supplier. • New windows support price/quantity/invoice corrections. as their information would already exist in TCA. When a supplier or supplier site is merged. In a separate window. supplier merge should be performed before initiating the party merge. Process Change • The new Invoice Workbench now contains a multi-record block to represent the invoice lines. Supplier open interface processes are enhanced to support the creation of TCA entities while importing suppliers. The creation of supplier bank accounts is also supported from the supplier open interface. When merging suppliers. users can enter one or more distributions for every invoice line. allowing for improved allocation of charges. Employees that were defined as suppliers in prior releases will not be migrated.

• The standard upgrade process creates one invoice line for every distribution existing in the 11i Payables distribution table. start date and number of periods. the R12 multi-period accounting is realized at the invoice line level. modify. • Charge (tax/freight/miscellaneous) distributions are created at the maximum level of detail to represent detailed allocation information. Considerations • No new setup steps are required for using Invoice Lines. • In prior releases. In this case. • Exchange rate variance (ERV) and invoice price variance (IPV) amounts become separate distributions in the upgrade process and so. Once Subledger Accounting is configured for multiperiod accounting. • Powerful search tools improve online inquiry to invoices that you may want to review. the invoice lines are automatically created.Configuration Change • Users can also do a quick match by entering just the PO number on the invoice header. or remove from a pay run. Later on. • With the new invoice lines model. 26 . a series of accounting records will be generated reflecting the fact that the invoice expense is first recorded in an accrual account then moved into expense account periodically. To invoke this feature. users can specify the deferred accounting period as a parameter for each individual invoice line. are no longer part of the item distributions. The following are some of the new enhancements that were made in this release: • More robust and flexible payment processing engine • Improved visibility into payment processing via the centralized Payments dashboard • Improved pay run automation • Improved pay run management tools: o Enhanced cash management report o Comprehensive selected invoice information o Improved online inquiry of selected invoices • Process payments for multiple operating units from single responsibility Process Change • A new Selected Invoices page displays summary and detail information used to view and analyze invoices selected in a pay run. when the accounting records are created for this invoice line and distribution. Payment Process Enhancements Overview The payment process has been significantly enhanced in Release 12. users check the “Deferred Option” box and specify the deferred period type. the allocations were managed by a charge allocation table which is now obsolete.

A Payment Dashboard empowers your payment manager to monitor all current pay run processing and gives them visibility to payment processes that require attention. users can review selected payments. add or remove scheduled payments or change payment and discount amounts. Payables no longer supports the Wire Payments and Clearing Payments document categories. Usage rules and validations can be set up for a payment method. Users can choose to pause after the invoices are selected. • Custom document categories for payments will not be upgraded. and Clearing). Wire. At this point. For example. the process may be stopped for review. • IMPORTANT: All custom payment formats must be migrated to XML in order to work in R12. or all payments may be rejected in the request if errors exist. Electronic. customers can setup their own payment methods Considerations • Scheduled Payment Selection report cannot be run for historical data. Scheduled Payment Selection report replaces many portions of the Preliminary Payment register report. However. payments with errors can be rejected. If payment batch sets were used as a workaround for doing multi-currency pay runs in 11i then. In Release 12. Configuration Change • All payment related setup has now been moved to the new Oracle Payments module. Here. Pay runs can be stopped at two points. 27 . • Check Payments and the Electronic Payments document categories have been retained in Release 12.• • • • • • • • Users can now view invoices that were not selected due to various reasons (not validated/approved). the user can see the final amounts of each payment and can choose to drop any payments. The second point is after the scheduled payments are built into payments. Validation errors during the payment build process are automatically handled based on the options that are specified on the payment process request. It can be used for reviewing the invoices selected in a pay run. review invoice selection criteria. • In prior releases. In addition a single payment run can process multiple banks that includes both electronic and printed payments The Payment Process Request template enables you to predefine invoice selection criteria. • Disbursement type has been made obsolete and hence. Oracle Payables seeded four payment method types (Check. it has been removed from all reports. determine immediate cash requirements for a pay run etc. consider combining those pay runs into a single pay run. Refer to the Oracle Payments User guide. thereby simplifying payment processing.

The approver name list of values is derived from the customer contact information. Configuration Change • Both customers and suppliers must be setup as a trading partner in TCA. • If the option to include trading partner approval is selected. Considerations • An internal dummy bank account will be seeded which will process receipts generated in Oracle Receivables. 28 . • Submit the netting batch and view the final netting report. submit the netting batch. • Optionally. In this process users can review. Process Change • A netting batch needs to be created using the Receivables responsibility. This feature allows you to optionally give the trading partner the opportunity to review and approve transactions before they are posted. • No netting batch information will be upgraded. • Once the batch has been set up. if the (supplier?) site information is left blank. It also supports foreign currency netting.AP-AR Netting Overview The AP-AR Netting feature allows you to offset balances in both Oracle Payables and Oracle Receivables to reduce the outstanding debt owed either from an internal company or from a customer. • Here are some of the additional steps that are required: o Create a netting agreement. users can review the netting batch. settlement date etc. o Create a netting bank account. It can include various parameters like operating unit. o Create a netting control account in General Ledger as well as exchange rate types if using multi-currency netting. then the system includes all the sites for the trading partner. Users could also run the proposed AP/AR netting report. In the header portion of the screen users will be able to see the total dollar amounts of the AP and AR transactions selected as well as the proposed netting amount. Users can view the Receivables and Payables transactions that were selected for possible netting. netting agreement. only one approver can be selected. remove or add transactions before submitting it. Accounting for netting is handled in the same way as if it had been closed in the subledgers. • Query the netting batch and view the proposed AP/AR netting amounts online. o Establish a paying relationship for the customers in Accounts Receivable. • When creating a netting agreement. o Associate the bank account used in the netting agreement with the AP/AR netting receipt class.

Users must review the migrated netting agreement setup to add or correct upgraded information. 29 . All in-progress netting batches should be closed or completed before upgrade. Transaction data residing in interface tables in 11i is not migrated to Release 12. Agreement name will be created using customer id and customer name. Netting upgrade uses dummy values for certain mandatory information not found in 11i setup. See Oracle Payables Implementation Guide and Oracle Payables User Guide for more information.• • • Netting agreements will be created for every existing customer and supplier relationship that is migrated. Users must change this to valid values.

robust and centralized engine for disbursing and receiving payments. End-to-end electronic payment processing that includes validation. Country-specific payment formats and reporting that meet global payment requirements. and secure transmission of payments to financial institutions and payment systems. From receipt remittance through Receivables to centralized receipt remittance. organizations and bank accounts.Oracle Payments Oracle Payments is a new product introduced in Release 12 that provides a configurable. currencies. formats. Oracle Payments has changed payment processing within Oracle products: • • • • • • From proprietary Oracle reporting technology to standardized formatting using XML. formatting. From payments transmitted by external systems to native transmission capabilities. aggregation. The key components of Oracle Payments are: • Funds Disbursement • Funds Capture Funds Disbursement Overview: The funds disbursement features delivered in Oracle Payments simplifies user procedures for managing complex payment processes that span multiple payment methods. Remittance advice reporting that notifies a payee of the remittance detail when a payment is made. • • • 30 . The major features within funds disbursement are: • Funds Disbursement Dashboard that enables payment administrators to manage every aspect of the process across multiple organizations from a central location in the application. From single operating unit restrictions to cross-operating unit transactions.. From credit card information stored in multiple product entities to a centralized credit card entity within Payments. From bank accounts stored in multiple products to centralized bank account setup.

Payment Methods are now user definable. o Processing Rules: the payment method on a document links it to processing rules configured in Oracle Payments. • Oracle Payments offers flexible setup to configure funds disbursement processing. • All masking of credit cards. and handles additional processing. Some of the key areas of impact are: o Payment Methods: each document to be paid requires a payment method to indicate how it should be handled in the funds disbursement process. Also. formats the files. Oracle Payables. The upgrade seeds payment methods that existed in Oracle Payables and globalizations. such as the payment method and currency. and Oracle Globalizations. • Oracle Payments’ secure electronic payment file and payment message transmission and transmission result processing replaces previously existing electronic transmission features in Oracle iPayment. These setup rules are held in a key entity called the Payment Process Profile. 31 . debit cards and bank accounts is centrally controlled. o Payment Build process first groups documents according to various rules.Process Change: • In Release 12. Setup has moved from the payment document on an internal bank account to the payment method in Oracle Payments. Oracle Payments segregates the process into two major functions: Payment Build process and the Payment process. See Oracle Payments Implementation Guide for more detailed information. o Payment process aggregates payments from multiple document selections and submissions into payment instruction files. • The upgrade uses various data from Oracle Payables to create the new Payment Process Profiles. such as printing and transmission. o Payment System: a payment system holds information about the third party involved in processing payments. setup entities related to payment formats within Oracle Payables are obsolete as they are effectively replaced by the new Oracle Payments setup. Considerations: • Both the Automatic Payment Programs and Payment Formats (AP entities) are obsolete in release 12. Configuration Change: • All payment related setup has been centralized within Oracle Payments. • Future Dated Payments are renamed to Bills Payable in release 12.

• Credit card security setup can be easily completed using the Oracle Payments Payment Administrator responsibility. Paymentech. but it is important for you to understand the new setup and process so you can successfully test the migrated information Considerations • EFT online validation is only offered for United States ACH and not for all payment systems. configurable funds capture processing can be setup by Payee. electronic funds transfers from bank accounts. and formatting of bills receivable. • Oracle Receivables retains the functionality of lockbox processing and electronic upload of remittance messages. and Concord EFS. • Process Change • Oracle Payments has consolidated notification letters from Oracle Globalizations into an Oracle XML Publisher format. such as customers. or Funds Capture Processing Rules.Funds Capture Overview Funds capture supports the processes to electronically receive funds owed deploying companies by debtors. Other payment systems. Supports out-of-the-box integration with leading third party payment systems such as Citibank. and to format bills receivable. Supports multiple payment processing systems operating simultaneously for funds capture transactions. such as VeriSign. Please refer to Oracle Payments Implementation Guide for more details. 32 . The major features within funds capture are: • • • Funds Capture Dashboard provides payment administrators an overview of the payment process status. Configuration Change • Centralized. • Oracle Payments does not support risk management for PINless debit card or bank account transfer transactions. EFT online validation checks whether a bank account exists and that the account is not flagged fraudulent. refunds to credit cards. offer their own out-of-the-box integrations with Oracle Payments. EFT online validation does not reserve funds or check if the account has sufficient funds. Routing Rules. First Data Merchant Services. Supports authorization and settlement of funds against credit cards and PINless debit cards. Oracle Payments works with AR to authorize and capture funds against credit cards. perform electronic funds transfers from bank accounts. • The required setup entities for bank account transfer processing are upgraded for you. process refunds to credit cards.

• Oracle Payments does not automatically reauthorize settlements that are rejected due to expired authorizations. Also see Metalink Note733537. 33 . See Oracle Payments Implementation Guide and Oracle Payments User Guide for more information.1 for more details in the Functional Upgrade Impacts Document for Oracle Payments (FINANCIALS).

etc. customer creditworthiness. Configuration Change • Creation of new accounting rules allows for revenue recognition that meets accounting standards and contractual start and end dates. o Ability to create user defined revenue contingency definitions seeded examples include: cancellation. • New Contingency tab offers the ability to review and manually manage contingencies from the Revenue Adjustment Manager (RAM) wizard. organizations may create their own revenue deferral reasons to ensure revenue is recognized in accordance with applicable revenue recognition policies. • Enhanced event-based revenue management allows users to define revenue deferral reasons and corresponding revenue recognition events specific to their business practices. In Release 12. • New Cost of Goods Sold (COGS) and Revenue Matching feature synchronizes the recognition of revenue with recognition of associated COGS. significant changes were made in the following areas: • Revenue Management • Line Level Cash Application • Redesigned Customer User Interface • Bill Presentment Architecture Revenue Management Enhancements Overview Enhancements in the Revenue Management area include the ability to distribute revenue in a more granular fashion which includes full and partial periods. • New Revenue Manager responsibility that provides the revenue analyst a central location to set up and maintain revenue policies and rule assignments. o Example: Able to create an accounting rule for revenue that will distribute revenue across identified accounting periods that can include a partial period (meaning the period does not start or end on the first or 34 . increasing efficiency and optimizing customer relationships. receipt and customer deduction processes while simultaneously improving cash flow. Process Change • New configurable accounting rules to determine the treatment of revenue allocations for partial periods. • Seeded revenue assignment rules have been replaced by a new window that enables the user to create process specific revenue assignment rules. Additionally.Oracle Receivables Oracle Receivables streamlines the invoice.

Partial Periods 180 295 295 130 Fixed Schedule Variable Schedule 225 225 225 225 180 240 240 240 • Ability to create user defined Revenue Assignment Rules: o Example: New Rule for Acceptance: Matching Criteria (must choose from a seeded choice list): Bill to Customer Condition: equals ABC Customer Revenue Contingency: Explicit Acceptance Result: If a transaction line with Bill to Customer of ABC Customer meets the criteria of this rule -.last day of the accounting period). • No longer necessary to create manual journal entries for revenue & COGS matching.Receivables will assign explicit acceptance as the contingency to the transaction line. o In R12. It only provides the ability to override the accounts defaulted via auto-accounting. GL Date Period Days in Period Daily Revenue Rate. During a partial period. Order Management (OM) provides this capability for invoicing & customer acceptance contingencies. the Contingency Defaulting API runs again and can default additional 35 . the revenue amount will be prorated based upon the number of days in the period. o Once this order is imported into Receivables from Order Management. and the revenue will be deferred until customer acceptance is received. • Provides the capability to default contingencies from feeder systems. The table below provides an example of how the new accounting rules would prorate revenue accordingly. • Uptake of SLA does not impact timing and amounts for revenue recognition. User will assign a contingency at order entry time based on the contingency defaulting API from Receivables. • COGS and Revenue Matching report has been retired. New Application Programming Interface (API) automates revenue & COGS matching. All Periods 180 280 310 130 January 14 February 14 March 14 April 13 • January February March April 18 28 31 13 Daily Revenue Rate.populate_cst_tables) that triggers earning and unearning of COGS when revenue is recognized or unearned. Considerations • Oracle costing calls the new Receivables API (AR_match_rev_cogs_grp.

automated line level application is available via lockbox.contingencies but will not over-ride the invoicing and/or customer acceptance contingency created during initial order entry. freight. • Line Level Cash Application Overview With the introduction of line level cash application. Un-apply and re-apply can be done against an entire transaction or to a specific transaction line. group of lines or tax or freight buckets. • Receipts cannot be applied at the line level against invoices migrated from Release 11i. • The Revenue Policy System Option available in 11i will be obsolete in R12. o The system will automatically apply the credit worthiness contingency. late charges or any combination thereof • Ability to un-apply and re-apply receipts. o The revenue policy data (which is populated for certain customers) will automatically show up in the new revenue policy window. Configuration Change None Considerations • Line level applications apply to manual cash application only. • Receipts can be applied against: o one or more transaction lines o all transaction lines o a specific group of transaction lines o a specific transaction line type such as tax. o Only impacts those systems interfacing to Receivables through AutoInvoice or Invoice API. Process Change • New cash application tree to choose the appropriate application level. as line level balances were not stored prior to R12. receipts can be applied against specific transaction items such as individual lines. debit memos and chargebacks with line details. o However. 36 . • Cannot apply against invoices with installments. The system will check to see if this revenue policy is populated during the initial set up. refund contingency and extended term contingency for all invoices (that either violate the policy or match the credit worthiness criteria). Upgrade script will convert the contingency ID from prior releases to the new contingency removal event code. • Available only for invoices. o SLA can only be used to override the accounts created via autoaccounting. o No User Interface impacts.

business volume and payment cycles. If necessary. • Tight integration with TCA allows users to take advantage of the DQM (Data Quality Management) feature. the cost of maintenance is lowered. it can prevent duplicate entries by determining if the customer that is being created or updated is a potential duplicate. customer account. Customers Standard View. customer account site. • Ability to classify customers based on industry. • By using TCA components. Process Change • Provides functionality to create a new customer. o Ability to set flag on Batch Source window to not store balances at line level in 12. Configuration Change • The new Customer Standard UI replaces the five functions that used to exist in prior releases (Customers Standard. In addition to the advanced search feature. credit worthiness. Considerations • The Customer Standard menu item will launch the new HTML customer form. Customers Summary. • Display of data has been enhanced to represent the TCA model. Balances are now stored at the line level regardless of application. and Customers Quick View). Customers Quick. 37 . o The pages are built using TCA CPUI (Common Party User Interface) components. Data quality management tools allow users to maintain the integrity of customer data.• • • Does not use application rule sets. • No data is affected.1. modify the AR profile option “Always Default Transaction Balance” for Applications profile option. Customer Standard User Interface (UI) Redesign Overview The new HTML based user interface provides a streamlined and intuitive customer data management flow. location. DQM allows the user to perform advanced searches for parties and customer accounts with user defined criteria. and a business purpose for the customer account site. size.

38 . including those external to Oracle Receivables. Enhancements were made to the following features: • Balance Forward Bill Presentment o More appealing and easier to modify bill layouts o Ability to view printed bill exactly as the customer sees it o Rules engine provides the ability to select from unlimited formats • Enhanced Template Assignment o New attributes provide more flexibility in how templates are assigned to customers • Attachment Printing o Ability to print PDF attachments for specified document categories Process Change • Balance Forward Bill Presentment: o Key set up steps include: Register views Select template items Select assignment attributes Create hyperlinks o Utilize balance forward data source for template assignment. like header and footer flexfields (e. Transaction Type or Context Reference Supplementary data sources..Bill Presentment Architecture Overview Bill Presentment Architecture (BPA) allows you to retrieve billing data from multiple sources. Projects interface attributes). Oracle Receivables Implementation Guide and Oracle Receivables User Guide for more information. o Two seeded assignment rules: Default rule for balance forward detail template Default rule for balance forward summary template o Must run the “Generate Balance Forward Bills” program • Enhanced Template Assignment o Templates can now automatically be assigned by: Any attribute in the invoice header Seeded attributes like Batch Source. See Oracle Receivables Reference Guide. • New profile option must be set to take advantage of printing attachments for printed bills o AR:BPA Print Attachment Document Category o Applies to both internal & external templates Considerations • Balance Forward Billing replaces Consolidated Billing.g.

accounting for subledger applications existed within the individual applications. The key upgrade areas impacted by Oracle Subledger Accounting are: • Accounting Rules • Transaction account builder • Standard reports Accounting Rules Overview: Subledger accounting rules define how journal entries can be created from subledger transactions for both the primary and secondary ledgers.Oracle Subledger Accounting Oracle Subledger Accounting (SLA) provides a common accounting engine that replaces the existing accounting processes in the subledger applications. Process Change: • In R11i and prior releases. with a common posting process to Oracle General Ledger. NOTE: Please refer to the Oracle Subledger Accounting Implementation Guide for more detailed information and definitions of the terminology used herein. • If specific requirements are not met by startup accounting definitions. accounting for all subledger applications is unified under SLA. with a common posting process to Oracle General Ledger. 39 . This centralized accounting setup provides greater flexibility as well as supports more simplified and standardized accounting rule creation and maintenance. • Seeded application accounting definitions are provided for all Oracle subledgers. Project Accounting) within SLA. Oracle Subledger Accounting has changed accounting within Oracle applications: • From accounting setups within each Oracle module to a unified accounting definition in Subledger Accounting. The intuitive user interface does not require users to know any programming language or to have developer skills. users can copy and modify the seeded definitions and their assignments. Assets. The SLA upgrade involves migrating existing accounting data between 11i and Release 12 to ensure a continuous business operation. • With Release 12. • From separate Global Accounting Engine functionality to a common standard for all Oracle subledgers (Receivables. Payables.

Configuration Change: • In Release 12. Considerations • Standardize your accounting policies by defining a common chart of accounts and accounting method across the enterprise before creating new accounting rules or replicating your existing rules within the SLA model. will work in conjunction with those rules. and Journal Line Definitions for Actual Accounting. In 11i. determine whether to enter manual subledger adjusting journals exclusively in SLA or GL for easier reconciliation. the accounts on the transaction distributions become the default accounts used by SLA accounting rules. and Accounting Methods Builder (AMB). In Release 12. Deploying companies can seed their own Accounting Class codes and assign them to the different journal lines. Implementation teams now have the option to override. Journal Descriptions. • Accounts that appear on the distributions (either manually entered or generated by account generator mechanisms) of subledger transactions such as Payables or Receivables invoices are not necessarily the final accounts that appear in the SLA and GL journal entries. If users define SLA rules to change the default account. the Accounting Class code is a lookup type owned by Subledger Accounting. • Application Accounting Definitions and Journal Entry Setup: The seed data includes all the Accounting Derivation rules. then the SLA and GL journal entries will not match the account stored on the subledger transaction distribution. the Accounting Class code is similar to the accounting journal line types in 11i. In R12. and Oracle Project Encumbrance Accounting. the accounting journal line types are fixed and can be only modified by development. Users may configure SLA accounting rules to further modify the default account by overriding the values for any of the segments in the account combination. • Account generator mechanisms that existed in 11i still exist and provide the same functionality in R12. • Accounting Class Codes: In R12. modify or use the accounting defined within the subledger applications as the accounting to be transferred to GL. • Review existing manual or adjustment journal entries to see if accounting rules can be configured to generate journals that eliminate the need for manual or adjustment journals. • Test effective-dated changes to accounting rules and verify the impact before the change is implemented. Federal Accounting. delivered within Subledger Accounting. 40 . • As a best practice. each subledger application will maintain its existing accounting rules. Encumbrance Accounting.

and extraction. • If implementation teams decide to create new transaction account definitions. • Dynamic insertion can be enabled for the chart of accounts so that if the combination does not exist. Regardless of which product is used to create accounting. • Implementation teams may use the seeded transaction account definitions. They may also create their own definitions either by copying and modifying seeded definitions. Process Change • Advanced Global Intercompany System (AGIS) has adopted TAB in Release 12 o Additional setup in AGIS is required to use TAB to define default accounting for transactions. while transaction account types and transaction account definitions are introduced by Transaction Account Builder. or by creating new ones from scratch. Standard Reports Overview Subledger Accounting owns tables that store all the subledger journal entries and their associated accounting information. the results are stored in subledger accounting tables. TAB is intended only for applications that allow users to modify the default accounts for a transaction before it is committed. they may need to create new account derivation rules. These rules can be derived by accounting flexfield or by segment and may have a chart of accounts associated with them. o Distributed accounts must be defined for each ledger and are generated as defined in Subledger Accounting Transaction Account Builder (SLA TAB). reporting. Considerations • If the application does not allow modification of the default accounts for a transaction before it is accounted. 41 . This information may then be used by analytical applications for inquiries and/or reporting.Transaction Account Builder (TAB) Overview Transaction Account Builder (TAB) provides a flexible mechanism to derive default accounts for subledger transactions that is fully integrated with Subledger Accounting (SLA). Configuration Change • Sources and account derivation rules are shared with Accounting Methods Builder (AMB). a new code combination can be created. • A common data model is designed for efficient inquiry. the implementation team must use AMB.

• With Release 12. • BI Publisher can save reports in many different formats including XML. See Oracle Subledger Accounting Implementation Guide for more detailed information. and Excel.• Oracle BI Publisher reports and templates offer immediate cost savings. you must create the Open Account Balance Listing Definition. Implementers need to create their own definitions for any new liability accounts they have created. It can also publish reports via printer. to run the Trial Balance Report for a particular liability account. greater efficiency. The upgrade process will create Open Account Balance Listing Definitions for each existing liability account per ledger. or posting to websites or portals. PDF. we’ve made it easier to locate and use reports by classifying them into three main categories: Journal Reporting Trading Partner Reporting Account Analysis Reporting Considerations • Analyze custom reports to map out a plan/approach to migrate existing reports to Oracle BI Publisher. e-mail. Process Change • Oracle BI Publisher is a key reporting tool in Release 12 that enables business users to create financials reports with familiar desktop products like Microsoft Word and Excel. 42 . RTF. • Open Account Balance Listing Definitions: In R12. and improved accuracy and reliability for financial reporting. • Custom reports may need to be modified to extract data from SLA tables rather than subledger distribution tables.

The internal subscription model is based on several key concepts: o Configuration Owner: any Legal Entity or Operating Unit that creates and maintains specific tax setup data. o Option to override GCO tax setup data: a subscribing entity can override the tax setup data to handle specific requirements applicable to that entity only. This is the entity that owns tax setup data that any configuration owner within the enterprise can subscribe to. Alternatively. 43 . o Global Configuration Owner (GCO): enterprise level tax configuration owner. • External subscription model where the Configuration Owner may choose to subscribe to the services of a Tax Service Provider for a given tax regime. Process change • Each entity within an organization can subscribe and use a single common configuration source for all transactions.Oracle E-Business Tax E-Business Tax is a new product introduced in Release 12 that provides a single point solution for managing transaction tax requirements across several E-Business Suite products. that entity can use the common configuration source with overridden tax set up specifically required to meet its own tax regulations. There are two subscription options in Release 12: • Internal (or multi-entity) subscription model to share tax setup across entities. E-Business Tax has changed transaction tax handling within Oracle products: • from fixed rules to user configurable rules • from single product setup to cross product setup • from single organization setup to cross organization setup • from multiple engines to single engine (see caveats in sections below) • from multiple repositories to unique repository (see caveats in sections below) The key components of E-Business Tax are: • Configuration Options and Provider Service Subscriptions • Tax Configuration Manager • Tax Determination Services • Tax Reporting • Tax Simulator Configuration Options and Provider Service Subscriptions Overview The configuration subscription model delivered by E-Business Tax optimizes tax setup and ensures tax rules are consistently applied within the enterprise. with overriding capabilities at the Legal Entity and Operating Unit levels.

In Release 12 that restriction no longer exists: you can choose to integrate with your preferred tax partner.• In Release 11i. This is particularly important when you operate in multiple countries with disparate tax regulations. 44 . See considerations below. Tax Configuration Manager Overview The Tax Configuration Manager component is responsible for creating and maintaining the structural foundation of Tax such as taxes. Considerations • Integration with external tax providers is currently available in the Order-To-Cash business cycle only and restricted to Taxware and Vertex’s product versions that were supported in Release 11i. • If any entity within your enterprise requires special tax handling that differs from the common tax setup. Tax setup is uniformly created in a common User Interface for all Oracle products. under the Global Configuration Owner. and have all your entities subscribing that common tax setup. often times in a shared service model. you can either override the common tax setup that is owned by the GCO or create and maintain specific tax setup for that entity that becomes a Configuration Owner itself. the option to integrate with tax service providers was restricted to Vertex and Taxware. using standard API’s. using Vertex O Series as a pilot. In Release 12 there is an explicit association between tax setup and Legal Entities or Operating Units. o Procure-To-Pay testing not scheduled. Legal entities in each country will be subject to local tax regulations which will impact the entire company. The enforcement of adequate tax rules across Legal Entities or Operating Units within your company ensures that tax is correctly applied to all transactions. tax rates. tax jurisdictions. Tax regulations are defined only once and applied consistently across products. • Testing of standard API’s to integrate with external tax providers in the Order-ToCash and Procure-To-Pay business cycles is not completed at the date of writing this document: o Order-To-Cash testing underway. See Oracle E-Business Tax Implementation Guide and Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide Configuration change • If all entities in your enterprise are subject to the same tax regulations you can setup tax only once. tax rules. • You can optionally subscribe services of external providers to handle tax configuration and tax calculation. fiscal classifications.

Process Change • There is a unique tax setup flow and common user interfaces across products. you can easily scale the existing tax setup to meet those new requirements. o Manually enter your tax setup. Considerations • Cannot update tax exclusiveness at invoice header or invoice line levels. Configuration change • Prior to Release 12. ways. That premise has determined the creation of tax configuration flows totally dedicated to the tax manager. • Instead of creating tax setup in various products. you could define Legal Entities in multiple. See Metalink note 463001. sometimes ambiguous. when you have the time or the need to adopt the new capabilities of E-Business Tax. 45 . If your company expands business to new countries with different tax requirements. • You have multiple options for defining tax setup in Release 12: o Migrate tax setup from Release 11i. like Oracle Payable or Oracle Receivables. See Configuration Options and Provider Service Subscription above. • You have the option to run taxes in Release 12 similarly to how you did it in Release 11i and gradually migrate to the new E-Business Tax model. you create a single tax setup that is applied consistently across products. You no longer need to enter tax setup in multiple product. o Use the Tax Configuration Library with modifications: you can take advantage of this predefined set of tax configuration data that may be used as sample data to guide and expedite the E-Business Tax implementation process. Tax configuration is central to the tax role. See Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to Release 12. There is a clear segregation of User Interface flows for tax managers and for general business users. without modifying the product.Legal and business tax regulations are mapped to flexible tax rules and other components of E-Business Tax.1. • Central setup and maintenance is now performed in new User Interfaces dedicated to your tax personnel. With the new Legal Entity model you now have to explicitly define your legal entities as well as the association with the appropriate tax setup. See bug 6772098. Once you complete the transition to E-Business Tax processes. See Oracle EBusiness Tax Implementation Guide. and gradually adopt the E-Business Tax setup and tax determination processes according to your needs. you can disable the Release 11i migrated solution with no loss of service. • The Tax Rules flow makes it easy for you to change existing tax rules and tax rates and/or create new rules and rates. o Integrate with tax content providers. • Tax setup creation and maintenance is done in new User Interfaces.

• • • There is no support for tax point date in E-Business Tax. Ensures the accuracy of tax calculation for all tax regimes your company is subject to.Oracle Purchasing. Tax reporting configuration is associated with a Legal Entity and Tax Registration Number. Tax reporting configuration not shareable across Legal Entities or Operating Units. Tax Determination Services Overview The Tax Determination Services component calculates transaction taxes based on transaction details and tax setup information. This component carries the following benefits: • Automation of tax processing through a central tax engine. Oracle Services Contracts. Process Change • Instead of disparate tax services provided by multiple products. Oracle Internet Expenses and Oracle Payables o Order to Cash . Oracle Trade Management.Oracle General Ledger Each product only needs to pass the required information to E-Business Tax to get the right tax determination and calculation. Oracle Consigned Inventory. • Covers standard Procure-To-Pay and Order-To-Cash transaction taxes. Oracle Internet Procurement. Oracle Project Accounting and Oracle Receivables o Inter-company invoicing . It is not integrated with the E-Business Tax internal subscription model. with the exception of withholding taxes and those taxes handled by the Latin Tax Engine solution. Oracle Order Management. 46 .Oracle Inter-company invoicing o General Ledger . • The central tax engine uses a common set of tax rules applicable to all your business entities. It improves the operation efficiency of your company and reduces errors. the central tax engine uniformly delivers automated tax services through a single application interface to: o Procure to Pay . • E-Business Tax replaces the following Release 11i tax solutions: o Procure to Pay – Automatic Tax Calculation and Brazilian Payables and Purchasing o Order to Cash – Global Tax Engine o General Ledger – General Ledger Automatic Tax Calculation • Your users no longer have to enter the correct tax code at transaction entry point: E-Business Tax determines the applicable tax or taxes for each transaction and automatically calculates the tax amount(s). Only your authorized users can override calculated tax amounts.Oracle Order Capture/iStore/Quoting.

Process Change • Reference data and transactional data are now available from a central Tax Repository.Configuration change • There are distinct flows for tax setup and for operational activities such as entering transactions. • New reports delivered for Austria. reducing the risk of human errors. The majority of tax reports are converted to XML Publisher. 47 . tax reporting and auditing take advantage of the XML Publisher reporting tool that facilitates output manipulation. • Tax determination and tax calculation are fully automated. tax jurisdictions. retained in Release 12: Payables withholding taxes. • Clerks whose main responsibility is to correctly enter transactions in the system can rely on the product to get the correct taxes applied to transactions. fiscal classifications. You no longer need to search for tax information in multiple products. • Enhanced tax reporting configuration with dedicated User Interfaces where you define all reporting rules for your Reporting Entities. They no longer have to enter the relevant tax codes for each transaction because EBusiness Tax does that for them. Croatia and Israel. tax rules. Prior to Release 12. Tax reporting was largely enhanced with features initially requested by EMEA countries. etc. In addition to the single tax repository.) and transactional data. Considerations • Tax functionality not migrated to the E-Business Tax model. Latin Tax Engine (Receivables). In Release 12 you can run all your tax reports by legal entity. It’s extremely easy to customize existing templates or to create new ones using XML Publisher. Brazilian Withholding Tax Calendar. Tax Reporting Overview Tax Reporting and auditing rely on a single tax repository that stores both reference data (taxes. • Business users can easily update templates delivered in the core product or create new templates without changing code. tax rates. based on tax setup previously defined by the tax manager. Indian transaction taxes and EMEA VAT Reporting. tax reporting was a lot compromised by how you implemented your legal entities. which can be used by countries in other regions with the same type of requirements. Payables Extended Withholdings (Latin America).

You can evaluate results. • A few tax reports were not converted to XML Publisher (still available in rdf). This is a valuable tool for tax managers who can use this interface to verify the tax configuration and to simulate the effect of the introduction of a new rule or incremental setup data. stocks. • Reporting based on a user definable tax reporting date. such as a new tax rate. purchases. preliminary and final reporting.See Oracle E-Business Tax Reporting Guide and Oracle Financials for Europe User Guide. alternative tax dates.. however. import. • Multiple Reporting Currencies support not available in all tax reports. Considerations • Core tax reports run by Invoice Date only. • Tax calendars. such as a Purchase or Sales Invoice. • In order to meet reporting requirements. and re run the simulation with same set of transactions. • Preliminary versions of tax reports to be run in order to support corrections and reallocations prior to finalizing the reports (declarations) to tax authorities • Final reporting • Close tax periods after final reporting to prevent updating or reporting twice transactions already finally reported. • Tax Repository does not store General Ledger tax journals. It allows you to verify if the tax configuration provides the expected results on your entered transactions. update the rules if required. export. services. tax reporting categories (or tax boxes) only used by EMEA VAT Reports. • Definition of reporting categories to report transactions by different business angles: sales. and view the results of the corresponding tax calculation. Configuration change • Ability to run tax reports by Legal Entity and Tax Registration Number. • Tax reporting based on tax calendar that can different from the accounting calendar. some of the EMEA countries have to define multiple tax rate codes with the same tax rate. goods. Tax Simulator Overview Tax Simulator allows you to enter transactions. assets. domestic. In Release 12 you can still run tax reports by Balancing Segment Value. 48 . etc. Oracle expects you to gradually move to tax reporting by legal entity and tax registration number. It also gives you the capability to drill down to the rules that were used in the simulation and to the rules that were not used.

and Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System Implementation Guide for more detailed information. It does not allow simulation of tax amounts to be paid or collected. • Simulation is restricted to the behavior of tax rules. Considerations • Requires manual entry of transactions for simulation – no option for uploading. See Oracle E-Business Tax User Guide. Oracle E-Business Tax User Guide. The Tax Simulator has dedicated User Interfaces where you can test all the tax setup before going live. 49 .Process Change • There is no predecessor for Tax Simulator before Release 12. See Oracle E-Business Tax Implementation Guide. Configuration change • You can test tax setup in Purchase or Sales invoices using the new User Interfaces of the Tax Simulator.

Sign up to vote on this title
UsefulNot useful