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

Oracle Subledger Accounting (SLA) Tables, Views

Oracle Subledger Accounting (SLA) Tables, Views Oracle Subledger Accounting Tables: TABLE NAME DESCRIPTION XLA_AAD_GROUPS The XLA_AAD_GROUPS table stores the merge dependencies analyzed during the merge analysis.  All application accounting definitions with the same GROUP_NUM must be merged together. XLA_AAD_HDR_ACCT_ATTRS The XLA_AAD_HDR_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the AAD level. XLA_AAD_HEADER_AC_ASSGNS Store the analytical criteria for the application accounting definitions. XLA_AAD_LINE_DEFN_ASSGNS This table stores the journal lines definitions for the application accounting definitions. XLA_AAD_LOADER_DEFNS_T The XLA_AAD_LOADER_DEFNS_T table is the interface table that facilitates the data transfer from data files and the database. XLA_AAD_LOADER_LOGS The XLA_AAD_LOADER_LOGS table stores the errors and logs generated by the application accounting definitions loader. XLA_AAD_SOURCES XLA_AAD_SOURCES table stores a...

Oracle Fusion Cloud: Supplier Import Process using File Based Data Import (FBDI)

 Supplier Data Migration or Upload to Oracle Fusion environment File-Based Data Import for Oracle Procurement Cloud Supplier import in oracle fusion   In this post , We will discuss about Supplier import in oracle fusion. Oracle has provided the FBDI tool to import suppliers from External  Source  to the Oracle fusion. Supplier Import in Oracle fusion we first need to  Download  the Supplier Import FDBI  templates  given by the Oracle fusion to import suppliers. Oracle has given 5 Different FBDI templates to Import supplier in Fusion. Here in this post , I will share the Complete steps for Supplier import in oracle fusion. You can refer this post for Supplier Import.   Steps for Supplier import in oracle fusion     Step1- First we need to download Supplier Data  Template  from Oracle Repository. Go to this path for Oracle Repository. ( select Based on your Cloud version) https://docs.oracle.com/en/...

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects Introduction When it comes to contractual billing, invoice and revenue generation are two separate processes, which during the lifespan of a project may or may not always coincide with each other and so do the balances in revenue and receivables accounts.  This interim difference between revenue and invoice account balances is bridged using Unbilled Receivables (UBR) and Unearned Revenue (UER) Accounts. Unearned Revenue (UER) Unearned Revenue (also termed as deferred revenue or UER) signifies money received for the goods or services, which are yet to be delivered.  As per the principles of Revenue Recognition, UER is recorded as on the balance sheet unless it is converted to Revenue upon delivery of goods or services For Example XYZ Consulting Ltd. receives an annual maintenance contract of $ 12,000 on Dec 31, 2014 for the period of Jan 01, 2015 to Dec 31, 2015. At the start of the contract as of Dec 31, 2...