I keep coming again and again to understand these new features and how to apply with new implementation clients. Though they look straight forward , but it is difficult to unlearn old 11i concept.
here putting again so you can again think why we should have a fresh thought process for R12 Implementation Projects and using these feature as starting point.
Data migration is the first step when moving your mission critical data to an Oracle database. The initial data loading is traditionally done using Oracle SQL Loader. As data volumes have increased and data quality has become an issue, Oracle Data Warehouse and Oracle Data Integrator have become more important, because of their capabilities to connect directly to source data stores, provide data cleansing and profiling support, and graphical drag and drop development.
Here i touching SQL Loader, External Table concept and ODI ( Oracle Data Integrator ) in this context. Not covering OWB -Oracle Warehouse builder as my knowledge is limited in that.
SQL LOADER – SQL Loader is the primary method for quickly populating Oracle tables with data from external files. SQL Loader is typically used in ‘fat file’ mode. This means the data is exported into a command-delimited fat file from the source database or arrives in an ASCII fat file. With the growth of data volumes, using SQL Loader with named pipes has become common practice.
External Table : The external tables feature is a complement to the existing SQL Loader functionality. It enables you to access data in external sources as if it were in a table in the database. Therefore, standard SQL or Oracle PL/SQL can be used to load the external file (defined as an external table) into an Oracle database table.
if you know SQL well, then it is easier to code the external table load SQL than SQL Loader control files and load scripts.
Oracle Data Integrator (ODI) –Oracle Data Integrator (ODI) is a product that Oracle acquired from Sunopsis SA in 2006.
ODI is a data migration and integration software product, providing a declarative design approach to defining data transformation and integration processes, resulting in faster and simpler development and maintenance. Based on an Extract-Load- Transform (E-L-T) architecture, Oracle Data Integrator, unlike traditional Extract- Transform-Load (E-T-L) products, loads the data into the target database and then does the transformation processing.
By combining data, event-based, and service-based integration, ODI is able to address varying needs from legacy data migration, data warehousing, and business intelligence to Master Data Management, Service Oriented Architecture, and others (such as cloud computing).
The most likely instances or use cases when ODI would be the Oracle product or tool selected are:
Now a day, more and more projects are using ODI and moving away from SQLLOADER, do reach me out for any questions around ODI.
In release 12: 11i Trial Balance is known as the Accounts Payable Trial Balance Report report in R12. It runs based on the Open Account Balances Listing Definition that you define. You can define the Listing Definition at a Ledger or Ledger Set level
A New concept “Open Account Balances Listing Definition” , what is it ? –> The Open Account Balances Listing identifies General Ledger accounts with outstanding balances and displays the subledger transactions that contribute to that balance
Define the report definitions either by Accounting Flexfield or by Accounting Flexfield segments. Associate each definition with a single ledger, which indicates the chart of accounts. The chart of accounts sets the context for the following information in the definition details region:
Define as many definitions as necessary. If defining a report definition by segment, indicate a single segment value, a range of segment values, or a combination of individual values and ranges for different Accounting Flexfield segments. If defining a report by Accounting Flexfield, include one or more entire General Ledger accounts.
The Open Account Balances Data Manager maintains reportable information for all enabled open account balance listing definitions. This program is submitted automatically after a successful transfer to General Ledger for the same ledger or manually by running the Open Account Balances Data Manager program. When changes are applied to a Open Account Balances Listing Definition, the Open Account Balances Data Manager program is automatically submitted for the changed definition.
Open Account Balances Data Manager :- This program processes subledger journal entries that are transferred to General Ledger and also final accounted journal entries that are flagged as No Transfer because these entries are already represented in General Ledger.
Use the Accounts Payable Trial Balance Report to verify that total accounts payable liabilities in Payables equal those in the general ledger. To reconcile these balances you can compare the cumulative total liability provided by this report with the total liability provided by your general ledger.
The Accounts Payable Trial Balance report is a Payables-specific version of the Open Account Balances Listing report. By running this report from Payables, you can run this report for a specific operating unit.
Latest R12 Accounts Payable Trial Balance (post-patch 9162536) has 2 templates available that control the output that is displayed. The two templates available are:
Accounts Payable Trial Balance – Group by Account
Accounts Payable Trial Balance – Group by Third Party
How to integrate Oracle AP Supplier Invoices to get Charge to PROJECTs:
Interfacing Supplier Invoice From Oracle Payables To Oracle Projects:
This process involves :
Important Project Related Fields in AP:
Once all the requisite information has been entered and the invoice distribution saved, the system checks whether the values given in the Project, Task, Expenditure Type and Expenditure Organization fields are active as of the Expenditure Item Date.
The following columns in the AP_INVOICE_DISTRIBUTIONS_ALL table are relevant for project-related supplier invoices:
To avoid the same invoice distribution being interfaced to both Projects and Fixed Assets, you must interface any project-related invoice distribution to Oracle Projects before you interface it to Oracle Assets.
PA_ADDITION_FLAG – The PA_ADDITION_FLAG tracks the status of project-related supplier invoice distribution lines and expense report distribution lines. For supplier invoice distributions entered via Oracle Payables, the PA_ADDITION_FLAG is set to N if the distribution is project-related, otherwise it is set to E and it is updated by Oracle Projects when the distribution is processed by the Oracle Projects Interface Supplier Invoice process. Oracle Projects sets the PA_ADDITION_FLAG to Y or Z after the item is successfully processed, or may be set to a rejection code if the line is rejected during transfer to Projects. For supplier invoice adjustment lines interfaced from Projects to Payables (which must net to zero with another line), the value for the PA_ADDITION_FLAG is set to T. Listed below are the Quick Codes available for the PA_ADDITION_FLAG:
If an item is rejected, you must correct the rejection reason and re-run the interface process.Once the Invoice is interfaced to Projects, the following tables are populated with appropriate values:
ABOUT THE ORACLE® UNIFIED METHOD (OUM)
Oracle is evolving the Oracle® Unified Method (OUM) to achieve the vision of supporting the entire Enterprise IT Lifecycle, including support for the successful implementation of every Oracle product. OUM replaces the Legacy Methods, such as AIM Advantage, AIM for Business Flows, EMM Advantage, PeopleSoft’s Compass, and Siebel’s Results Roadmap. Oracle PartnerNetwork (OPN) Diamond, Platinum, and Gold Partners are encouraged to transition to OUM.
This release features:
OPN Diamond, Platinum, and Gold Partners are able to access the OUM method pack, training courses, and collateral from the OPN Portal at no additional cost:
Lot of us are involve in Upgrade projects or something where we need to know what are the database level object changes happens between one version to another. Oracle provides something to start our work in that context ;
Refer Oracle support note :
|EBS Data Model Comparison Report Overview [ID 1290886.1]|
The EBS data model comparison report provides the static database object definition changes between two EBS releases to help users to preview the database object definition changes before upgrading their instances from one release to another and understand the impact of the database object changes that may affect the customization or business flows.
Users can select a product and navigate the database object definition differences for each supported database object type.
Here is the list of additional prefixes known to products that are considered for comparison in addition to their own product short code.
|Product Short Name||Additional Prefixes|
|AR||HZ, OCM, RA, TAX|
|EDW||EDW (from all product schema including the common schema, e.g. APPS)|
|FND||WF, UMX, FWK, OAM|
|JTF||JTY, JTO, CAC, JTH, JTA|