Results for “amount_financed_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

POA_API_BS_J_MV is an Oracle E-Business Suite table owned by the APPS schema in the FND — Application Object Library product family. The object name suffix "MV" indicates a materialized view, and the "_BS_J_" segment identifies it as a balance-sheet journal structure within the Procurement Operations Analysis (POA) analytical layer. In Oracle EBS 12.1.1 and 12.2.2, this object serves as a pre-aggregated repository for procurement and financial commitment activity, exposing dimensions across supplier, commodity, category, cost center, and enterprise calendar hierarchies alongside paired amount measures. It functions as the reporting substrate for procurement spend analysis, financing exposure, and commitment lifecycle tracking rather than as an operational transaction table.

Mining of the foreign-key structure yields a heuristic Data Vault classification of standalone, meaning the object does not cleanly resolve into a pure hub, link, or satellite pattern. In practice it behaves most like a presentation-layer bridge that joins multiple business-key references to a central fact grain, and it should be modeled as a denormalized reporting entity rather than as an audited raw-data-vault artifact.

Key Information Stored

The documented physical schema contains 35 columns. The most significant include:

• ORG_ID — operating unit discriminator, essential for multi-org security and partitioning in R12.
• SUPPLIER_ID and SUPPLIER_SITE_ID — vendor and vendor-site identifiers.
• COMMODITY_ID — foreign key to PO_COMMODITIES_B.
• COMPANY_ID — foreign key to PN_COMPANIES_ALL, tying activity to the company hierarchy.
• CATEGORY_ID and PO_ITEM_ID — purchasing category and item dimensions.
• BUYER_ID — purchasing agent responsible for the activity.
• COST_CENTER_ID and SHIP_TO_ORG_ID — organizational and delivery dimensions.
• BASE_UOM — unit of measure applied to the measures.
• ENT_YEAR_ID, ENT_QTR_ID, ENT_PERIOD_ID, WEEK_ID, DAY_ID — enterprise calendar hierarchy enabling roll-up reporting.
• AMOUNT_B, AMOUNT_G, AMOUNT_SG, together with the parallel FINANCED and RECOUPED measure families (AMOUNT_FINANCED_B/G/SG, AMOUNT_RECOUPED_B/G/SG) — committed, financed, and recovered balances across base, group, and sub-group currency bases.
• APPROVED_FLAG, INVOICE_TYPE, and LINE_TYPE_LOOKUP_CODE — status and classification attributes for filtering.

The identifier columns FRID, POFRID, COMRID, CRID, and MRID are surrogate key candidates typical of POA fact structures, while the business-key candidates are the composite of ORG_ID with SUPPLIER_ID, COMMODITY_ID, and the enterprise calendar identifiers. INV_D_CREATED_BY records the creating user identifier.

Common Use Cases and Queries

Typical reporting scenarios include approved-spend analysis by commodity and supplier, financing versus recoupment reconciliation, and period-over-period commitment trending. A representative query aggregates the base amount over the enterprise year and period:

SELECT ent_year_id, ent_period_id, commodity_id,
       SUM(amount_b) total_amount,
       SUM(amount_financed_b) financed,
       SUM(amount_recouped_b) recouped
FROM   apps.poa_api_bs_j_mv
WHERE  org_id = :p_org_id
AND    approved_flag = 'Y'
GROUP BY ent_year_id, ent_period_id, commodity_id;

Because the object is a materialized view, results reflect the last refresh cycle; users should confirm the refresh schedule before relying on the data for near-real-time decisions. Join the commodity and company dimensions to enrich output with names:

SELECT c.commodity_name, b.amount_b
FROM   apps.poa_api_bs_j_mv b,
       apps.po_commodities_v c
WHERE  b.commodity_id = c.commodity_id;

Related Objects

• PO_COMMODITIES_B — referenced through COMMODITY_ID; supplies commodity definition and description.
• PN_COMPANIES_ALL — referenced through COMPANY_ID; provides the legal company hierarchy.
• PO_VENDORS / POZ_SUPPLIERS — supplier master linkage via SUPPLIER_ID and SUPPLIER_SITE_ID.
• PO_CATEGORIES_B — category dimension via CATEGORY_ID.
• PER_ALL_PEOPLE_F — resolves BUYER_ID to a purchasing agent.
• HR_ALL_ORGANIZATION_UNITS — resolves SHIP_TO_ORG_ID and COST_CENTER_ID.
• FND_LOOKUP_VALUES — decodes LINE_TYPE_LOOKUP_CODE and INVOICE_TYPE.
• GL_DAILY_CONVERSION_TYPES and standard AP/PO finance views — support reconciliation of the AMOUNT_* measure families against general ledger balances.

Because the object is standalone in the mined relationship model, no child tables depend on it; it is consumed exclusively through joins to the dimensional masters listed above.