oracle r12 changes tech and functional
DESCRIPTION
oracleTRANSCRIPT
Migrating Custom 11i Reports to Release 12
Paul [email protected]
Director, Product ManagementNoetix Corporation
What To Expect
• Emphasis on “porting” custom 11i queries• Focus on Oracle Financials subject areas• More technical than functional• What we see companies doing about
reporting
About Noetix
• BI solutions experts since 1994
• Offices in North America, Europe and South Asia
• Certified with all leading BI Platforms
• 2007 Product Awards: KMWorld, eWEEK, DMReview
• 1400+ customers globally
PARTNERSHIPS
Industry Recognition
• 100 Companies that Matter in Knowledge Management, KMWorld
• Codie Award for Best Business Intelligence or Knowledge Management Solution, SIIA
• Top 100 Companies in the Business Intelligence Industry, DM Review
• Trend Setting Products 2007, KMWorld
• Finalist, Excellence Award – Analytics and Reporting, eWeek
• Top 100 Private Companies Award, Red Herring
• Washington Technology Fast 50, Deloitte and Touche
• Washington’s Best 100 Companies to Work For, Washington CEO Magazine
AWARDS
Oracle Reporting Experts
Oracle E-Business Suite
Siebel CRMPeopleSoft
NoetixViewsNoetixAnswers
Noetix PlatformOracle DatabaseOracle Discoverer
Cognos BIBusiness ObjectsOracle Business Intelligence EE
Everything Starts with a Query
• ETL routines– To replicate the data, to transform it into a
different model, and usually to create stored aggregations
• Reporting tool’s repository– Discoverer EUL, OBI EE Repository, BO Universe,
Cognos Framework Mgr. Model, …• Database views
– Virtual transformation of data into a denormalized model without replicating the data
– For direct access• The information in this presentation is applicable to
all approaches
E-Business SuiteOLTP Tables
BI Suite Cognos 8 BIDiscoverer /BI Suite EE
Crystal ReportsWeb Intelligence
Reporting Tool Repositories
Topics Models / PkgsEnd User Layer/Repository
Business ViewsUniverse
Master FileMetadata
BI Suite Cognos 8 BIDiscoverer /BI Suite EE
Crystal ReportsWeb Intelligence
Common Data Access Layer
EBS Tables
Database Views
End User Layer/Repository Topics Models / Pkgs Business Views
UniverseMaster FileMetadata
Common business terminology
Reuse complex SQL logic
Improved maintainability
Improved “time to query”
Subject Areas
Funds Disbursement via new Payments applicationSuppliers & Trading Community ArchitectureBanks & Trading Community ArchitectureSubledger AccountingAlso…Collections & customer correspondence via
Collections application Tax Calculations via the new E-Business Tax appl.XML Publisher
Impact of Release 12 to your 11i queries: Very little complete rewrite
Funds Disbursement
Funds Disbursement
• Moved from Payables to new Payment module
– Creation & validation of payments– Aggregation of payments into files– Format & transmission of files
• Selection & approval of invoices remains in Payables
Funds Disbursement Changes
• Invoice payments IBY_DOCS_PAYABLE_ALLAP_INVOICES_ALLAP_PAYMENT_SCHEDULES_ALL
Release 1211i
• Payments IBY_PAYMENTS_ALLAP_CHECKS_ALL
• Banks CE_BANK_ACCT_USES_ALLAP_BANK_ACCOUNT_USES_ALL
Co-existing Tables
Obsolete Tables
• Instructions, batchesIBY_DOCS_PAYABLE_ALLIBY_PAY_SERVICE_REQUESTSIBY_PAY_INSTRUCTIONS_ALL
AP_INV_SELECTION_CRITERIA_ALL
• Payment documents CE_PAYMENT_DOCUMENTSAP_CHECK_STOCKS_ALL
• Supplier & customer bank accounts
IBY_EXTERNAL_PAYEES_ALLIBY_EXT_BANK_ACCOUNTS IBY_PMT_INSTR_USES_ALL
AP_BANK_ACCOUNTS_ALL
Suppliers & Trading Community Architecture
Suppliers & TCA
• Supplier, supplier site, & supplier contact information migrated to TCA tables
• Three new AP tables containing supplier-unique data, with links to TCA tables
AP_SUPPLIERSAP_SUPPLIER_SITES_ALLAP_SUPPLIER_CONTACTS
• Three old PO Vendors tables obsolete– Views provided for backward compatibility
Supplier Changes
HZ_PARTIESAP_SUPPLIERS
Release 12 TCARelease 12 Payables
HZ_PARTY_SITESHZ_LOCATIONSAP_SUPPLIER_SITES_ALL
• SuppliersRelease 1211i
AP_SUPPLIERSPO_VENDORS
Co-existing Tables
Obsolete Tables
HZ_PARTIESHZ_PARTY_SITESHZ_RELATIONSHIPSHZ_ORG_CONTACTS
AP_SUPPLIER_CONTACTS
• Supplier sites AP_SUPPLIER_SITES_ALLPO_VENDOR_SITES_ALL
• Supplier contacts AP_SUPPLIER_CONTACTSPO_VENDOR_CONTACTS
• Suppliers
• Supplier sites
• Supplier contacts
Oracle’s Supplier / TCA Model
Supplier Contacts
• Single occurrence of each supplier contact
• Supplier contacts now shared across operating units
Banks & Trading Community Architecture
Banks Data in R12
• Setup in Cash Management (CE)– Bank, bank account setup– Shared with Payables, Receivables, Treasury, &
Payroll• Banks & bank branches now represented as TCA
parties– 11i AP bank data moved to TCA HZ_PARTIES table
• Three key CE tables– CE_BANK_ACCOUNTS for bank accounts– CE_BANK_ACCT_USES_ALL for account uses by
Operating Units & Legal Entities– CE_GL_ACCOUNTS_CCID for bank account use
accounting data
Bank Data in TCA
HZ_PARTIES
Release 12 TCA
HZ_PARTY_SITESHZ_LOCATIONS
• Bank, bank branch, account attributes, contact persons
• Bank sites & locations
HZ_ORGANIZATION_PROFILES• Change history & additional attributes
HZ_CONTACT_POINTS• Contact details & methods
HZ_ORG_CONTACT• Contact titles
HZ_ORG_CONTACT_ROLES• Contact purpose or role
Subledger Accounting
Subledger Accounting
• All accounting performed before transfer to the GL
• User-definable accounting rules• At the data level, it’s a big change for all the
subledgers, though there is a first generation in 11i Payables “Accounting Events”
Oracle’s Slide on SLA 1 of 3
Oracle’s Slide on SLA 2 of 3
Oracle’s Slide on SLA 3 of 3
Receivables Accounting in 11i
• Final accounting data not generated prior to transfer to GL
– Distribution level information GL• Three distinct distributions tables
– Customer transactions• Invoices / Credit Memos / Debit Memos / …• Accounting class & amounts, but not debits & credits
– Receipts & Adjustments• Unapplied, applied• Both debits & credits
– Misc. Cash Receipts• Both debits & credits
• “View Accounting” is a report against distributions
11i AR Database
ra_cust_trx_line_gl_dist_all
ar_distributions
misc_cash_distributions
gl_interfacesTransfer
to GL
Receivables
GL
Cross-functional Views
•Adjustment distributions•Customer transaction distributions
•Miscellaneous receipt distributions•Standard receipt distributions
Payables Accounting in 11i
• Accounting data generated and stored in “Accounting Events” tables prior to transfer to GL
– Run “Create Accounting” to populate accounting events tables
– Accounting event tables GL
11i AP Database
gl_interfacesTransferto GL
invoices
invoice_distributions
CreateAccounting
ae_events
ae_headers
ae_lines
Payables GL
Cross-functional Views
•Invoice distributions •Payment distributions
Subledger to Ledger Reporting in 11i
• Complete, final accounting only available in the GL
– All debits and credits– All journal entries– All balances
• Challenge: Difficult to link summarized accounting data with source details
Release 12 Subledger Accounting
• All subledger accounting data generated and stored in shared SLA tables prior to transfer to GL
– Run “Create Accounting” to populate SLA tables
• User can “View Accounting” only after “Create Accounting” is run
The Create Accounting processTools Create Accounting
From Distributions to SLA
SLA Events,Headers,& Lines
CreateAccountingDistributions
• Create Accounting process– Applies accounting rules– Loads SLA tables, GL tables– Creates detailed data per accounting rules,
stores in SLA “distribution links” table
SLA Distributions Links
• SLA Distribution Links Table– Holds distribution details…finest granularity of
accounting data– Must join through to get true Distribution SLA
journals matches– Multiple distributions may be aggregated into a few
SLA journal lines
SLA Events,Headers,& Lines
DistributionsSLA
DistributionLinks
R12 Accounting Structures
gl_interfacesTransferto GL
CreateAccounting
VariousSubledger
DistributionsTables
Subledgers GLSLA
xla_events
xla_headers
xla_lines
xla_distribution_links
Distribution Links Sample Data
0Round24718CAD11984
158.2Rec12833CAD11984
1.2Tax18170CAD1.23Tax11984
6Tax18170CAD63Tax11984
0.4Tax18170CAD0.42Tax11984
2Tax18170CAD22Tax11984
20Rev12871CAD202Line11984
0.6Tax18170CAD0.61Tax11984
3Tax18170CAD31Tax11984
5Freight13053CAD51Freight11984
20Freight13053CAD201Freight11984
100Rev12871CAD1001Line11984
AmtAcct.Class
CCIDCurrencyExtAmt
Line #Line Type
Trx #
123.93158.2Receivable1305311984
0.010Rounding1283311984
94.01120Revenue1287111984
19.5925Freight2471811984
10.3413.2Tax1817011984
Acct. CR
Acct. DR
Entered CR
Entered DR
Acct. ClassCCIDTrx #
SLA Je LinesDistributions
DistributionLinks
2.35310.3413.2CADTax1817011984
1.57210.3413.2CADTax1817011984
4.7610.3413.2CADTax1817011984
0.470.610.3413.2CADTax1817011984
0.31.0410.3413.2CADTax1817011984
0.941.210.3413.2CADTax1817011984
0.0100.010CADRounding2471811984
78.3412094.01120CADRevenue1287111984
15.672094.01120CADRevenue1287111984
123.93158.2123.93158.2CADReceivable1283311984
15.672019.5925CADFreight1305311984
3.92519.5925CADFreight1305311984
UnroundedAcct. DR
UnroundedAcct. DR
UnroundedEnteredCR
UnroundedEnteredDR
SLAAcct.CR
SLAAcct.DR
SLAEnteredCR
SLAEnteredDR
CurrAcct.Class
CCIDTrx #
View Accounting reportTools View Accounting
Tie It All Together
• Data flows from distributions, thru distribution links and SLA tables, to GL
• Three key stages– Distributions (before accounting applied)– SLA (in draft or final form)– GL
• Three key views of the data– Distributions only– Tie distributions to SLA to GL– Tie GL back to distributions
AR_Tran_Dist_SLA_GL_JeGL_Je_SLA_AR_Tran_DistReceivables transactions (all)
AR_Std_Rcpt_SLA_GL_JeGL_Je_SLA_AR_Std_Rcpt_DistReceivables standard receipts
AR_Misc_Rcpt_Dist_SLA_GL_JeGL_Je_SLA_AR_Misc_Rcpt_Dist
Receivables miscellaneous receipts
AR_Adj_Dist_SLA_GL_JeGL_Je_SLA_AR_Adj_DistReceivables adjustments
AP_Pmt_Dist_SLA_GL_JeGL_Je_SLA_AP_Pmt_DistPayables invoice payments
AP_Inv_Dist_SLA_GL_JeGL_Je_SLA_AP_Inv_DistPayables invoices
Subledger GLCross-Functional View(Final and draft accounting data)
GL SubledgerCross-Functional View(Final accounting data only)
Accounting Subject Area
Noetix Support for Oracle SLAPayables & Receivables
The Impact?
• Some 11i queries will easily migrate to Rel. 12– Some with no changes at all– Some will need table name changes
• Some 11i queries will need moderate attention
– Data moved to TCA will require query re-writes, but the basic reports can remain the same
• Some 11i queries won’t migrate 1:1 to Rel. 12– SLA may require new reports, queries &
ETL routines
Report Strategies
• Best practice: Establish a common data access layer between queries and OLTP tables
– Use common business terms for query objects, data elements, and the descriptions of both
– Persist this “business metadata” between database upgrades
– Remap the “technical metadata” (SQL)• OLTP database views
– Common data access layer– Usable by reporting & query tools, & ETL
• Reporting tools’ metadata repositories– Map to data access layer in the OLTP database