Skip to main content

BI Apps Financials — Accounts Payable Facts and Aggregates

These are OOB (out of box) OBAW facts and aggregates related to Oracle BI Apps AP (Accounts Payable) Facts and Aggregates. This is just to help you understand which fact and aggregate tables goes where in the BI Apps ocean.
Sourced from Oracle BI Apps Data Model Reference.
DIMENSION/FACTBUSINESS NAMEDESCRIPTION
W_AP_AGING_INVOICE_A 
Fact Table
AP Aging Aggregate Table by Invoice This table stores the accounts payable aging information at the invoice and association dimension levels. Each record in this table indicates the aging information at a particular date in time. The SNAPSHOT_DT_WID column indicates the date when the aging information is recorded 
W_AP_AGING_SUPPLIER_A 
Fact Table
AP Aging Aggregate Table by SupplierThis table stores the accounts payable aging information at the supplier andassociation dimension levels. Each record in this table indicates the aging information at a particular date in time. The SNAPSHOT_DT_WID column indicates the date when the aging information is recorded 
W_AP_BALANCE_F 
Fact Table
Accounts payable balance This table stores account payable balance information for supplier accounts. Only Posted records are considered for calculating the balances and Balance amts can beuse for Financial reporting 
W_AP_INV_DIST_F 
Fact Table
AP Invoice DistributionsFact table stores the AP invoice data at invoice distribution level
W_AP_XACT_F 
Fact Table
AP TransactionThis fact table stores various types of Payables transactions.The types of AP transactions stored in this table are:
  • Payment schedules for various types of invoices
  • Accounting entries for payments
  • Liability accounting entries from various types of invoices
GL Reconciliation records.
The first three types of records are extracted from the source applications (ie. Oracle 11i). The fourth type of record, GL Reconciliation records, are records inserted by the source adapters. These records are the results of the “GL Reconciliation” process.
The DOC_TYPE_WID field in this table is the foreign key to W_XACT_TYPE_D table.
It distinguishes the transaction type of the record.
The DOC_STATUS_WID field is the foreign key to W_STATUS_D table. It helps identify the status of the record, whether it is “Open” or “Cleared”, “Posted” or “Unposted”.
W_AP_XACT_GRPACCT_DAY_A 
Fact Table Aggregate
AP Transaction by Day AggregateThis table is an aggregate table of W_AP_XACT_F at day level and various other dimensions. These dimensions include Company, Supplier, Supplier account, Transaction type, etc.Records from W_AP_XACT_F are aggregated to day level and various other dimensions. For instance, all invoices for supplier A posted on December 23, 2006 are aggregated into one record. The aggregation is based on POSTED_ON_DT_WID field, which is the document’s posting date.
Fields such as XACT_COUNT indicates the transaction count of this particular aggregation record. For instance, for the aggregation record of supplier “A”, for the date December 23, 2006, for the transaction type of “Invoice”, the XACT_COUNT indicates how many invoices from supplier “A”, is posted on December 23, 2006.
W_AP_XACT_GRPACCT_FSCLPRD_A 
Fact Table Aggregate
AP Transaction by Fiscal Period i.e. Month Aggregate(Would it be nice if Oracle names this fact table as W_AP_XACT_GRPACCT_FSCLMONTH_A because this truly represents fiscal month. Well, Oracle might have a better reason why they named it like this) This table is an aggregate table of W_AP_XACT_F at fiscal month level and various other dimensions. These dimensions include Company, Supplier, Supplier account, Transaction type, etc.Records from W_AP_XACT_F are aggregated at fiscal month level and various other dimensions. For instance, all invoices for supplier “A” posted in 3rd fiscal month of fiscal year 2006 are aggregated into one record. The aggregation is based on
POSTED_ON_DT_WID field of W_AP_XACT_F, which is the document’s posting date. The fields POSTED_FROM_DT_WID and POSTED_TO_DT_WID indicates the fiscal month start date and fiscal month end date of this aggregation record.
Fields such as XACT_COUNT indicates the transaction count of this particular aggregation record. For instance, for the aggregation record of supplier “A”, for the 3rd fiscal month of fiscal year 2006, for the transaction type of ?Invoice?, theXACT_COUNT indicates how many invoices from supplier ?A?, is posted in the 3rd fiscal month of fiscal year 2006.
W_AP_XACT_GRPACCT_FSCLQTR_A 
Fact Table Aggregate
AP Transaction by Fiscal Quarter AggregateThis table is an aggregate table of W_AP_XACT_F at fiscal quarter level and various other dimensions. These dimensions include Company, Supplier, Supplier account,Transaction type, etc. Records from W_AP_XACT_F are aggregated at fiscal quarter level and various other dimensions. For instance, all invoices for supplier “A” posted in 3rd fiscal quarter of fiscal year 2006 are aggregated into one record. The aggregation is based on
POSTED_ON_DT_WID field of W_AP_XACT_F, which is the document’s posting date. The fields POSTED_FROM_DT_WID and POSTED_TO_DT_WID indicate the fiscal quarter start date and fiscal quarter end date of this aggregation record.
Fields such as XACT_COUNT indicates the transaction count of this particular aggregation record. For instance, for the aggregation record of supplier “A”, for the 3rd fiscal quarter of fiscal year 2006, for the transaction type of “Invoice”, the XACT_COUNT indicates how many invoices from supplier “A”, is posted in the 3rd fiscal quarter of fiscal year 2006.
W_AP_XACT_GRPACCT_FSCLYR_AAP Transaction by Fiscal Year Aggregate This table is an aggregate table of W_AP_XACT_F at fiscal year level and various other dimensions. These dimensions include Company, Supplier, Supplier account, Transaction type, etc. Records from W_AP_XACT_F are aggregated at fiscal year level and various other dimensions. For instance, all invoices for supplier “A” posted in fiscal year 2006 areaggregated into one record. The aggregation is based on POSTED_ON_DT_WID field of W_AP_XACT_F, which is the document’s posting date. The fields POSTED_FROM_DT_WID and POSTED_TO_DT_WID indicate the fiscal year start date and fiscal year end date of this aggregation record.
Fields such as XACT_COUNT indicates the transaction count of this particular aggregation record. For instance, for the aggregation record of supplier “A”, for the fiscal year 2006, for the transaction type of “Invoice”, the XACT_COUNT indicates how many invoices from supplier “A”, is posted in fiscal year 2006.

Comments

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...