Be aware of R12 Data Model changes to properly assess R12 upgrade rework
Any entity upgrading to R12 should sufficiently understand the data model changes between 11i and R12. Based on an entities’ dependence on the existing 11i data models that change, there can be a significant level of rework required to ensure that existing custom RDF/BI Pubisher Reports, Discoverer Reports, outbound interfaces, custom views, custom SQL & PL/SQL, etc. will function properly in the R12 environment. Analysis of custom objects relative to the data model changes can’t just be limited to whether objects will compile or run in R12, but should also include analysis of whether the proper data is returned from both upgraded 11i transactions and new transactions generated in R12. To properly plan and allocate resources to an R12 upgrade project, the impact of these changes to an entity should be thoroughly analyzed.
For example, in my years working in the Federal Financials space, I’ve seen a fairly heavy reliance on the gl_je_lines.referenceX (journal import references) columns for creating custom reports that provide subsidiary information (e.g. PO Number, Vendor, etc.) and gl information together. I’ve seen reports/interfaces often built from gl_je_lines up to best ensure the detail reports balance with trial balance amounts. In R12, the gl_je_lines.referenceX columns are no longer populated or are populated in a different manner. Thus any custom report, interface, etc. that leverages these fields will likely have to be reworked (or overall approach addressed) to continue to meet end-user requirements. The R12 GL -> Subsidiary drilldown path now runs through gl_import_references and a new suite of XLA tables as shown in this diagram.
An additional problem that confronts Federal Financials customers with this change is (more…)
Read Full Post | Make a Comment ( 2 so far )gl_je_lines import references for Treasury Confirmation journals
The other day I was dealing with needing to get some additional subsidiary detail for some Payables – Treasury Confirmation journal lines and since the relationships aren’t well documented, I’ll post them here.
For journal source = ‘Payables, journal category = ‘Treasury Confirmation’, the following are what the gl.gl_je_lines reference columns include:
reference_1 = fv.fv_treasury_confirmations.treasury_confirmation_id
reference_3 = ap.ap_checks_all.check_id
reference_4 = ap.invoices_all.invoice_id
reference_5 = hr.hr_all_organization_units.organization_id
I, along with others, have run into some situations where it would have been nice to have a link to invoice_distribution_id to support detail level gl to subsidiary module reconciliation efforts, but if I remember correctly, the confirmation journal entries aren’t necessarily at that lowest level of detail.
Read Full Post | Make a Comment ( 3 so far )
Oracle Federal Applications 