Results for “cust_tax_round”

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

Overview

The EDW_TPRT_TPARTNER_LOC_LSTG table is a warehouse staging object owned by the POA schema, which corresponds to the Purchasing Intelligence (Purchasing Analytics) module in Oracle EBS 12.1.1 and 12.2.2. It stores trade partner and trade partner location records extracted from source Purchasing and Order Management tables and loaded into the POA analytics infrastructure. The prefix EDW_ indicates it is part of the Enterprise Data Warehouse extraction layer that feeds the POA star schemas and dimensional aggregates used for spend analysis and supplier performance reporting.

The _LSTG suffix denotes a staging or landing table. Records are staged here before being validated, transformed, and propagated to downstream dimension tables. The COLLECTION_STATUS, OPERATION_CODE, ERROR_CODE, REQUEST_ID, and INSTANCE columns confirm this staging role, supporting incremental collection runs across multiple EBS instances.

The documented foreign key relationship is ROW_ID → CS_SYSTEMS_ALL_B_TEMP, and the Data Vault classification mined from the FK structure is standalone. This suggests the table is best modeled as an independent staging entity rather than a classic hub, link, or satellite, though its business key structure (trade partner and location) would naturally support a hub-and-satellite design in a consolidated warehouse.

Key Information Stored

The table contains 59 columns covering trade partner identity, location addressing, and supplier/customer attributes. The most significant columns are:

• TPARTNER_LOC_PK — the primary surrogate key identifying each trade partner location record.
• ROW_ID — unique row identifier; also the FK column joining to CS_SYSTEMS_ALL_B_TEMP.
• TRADE_PARTNER_FK and TRADE_PARTNER_FK_KEY — business key components linking the location to its parent trade partner (supplier or customer).
• BUSINESS_TYPE — distinguishes supplier (VNDR) versus customer (CUST) trade partners, which governs which attribute columns are populated.
• NAME — trade partner or location descriptive name.
• ADDRESS_LINE1 through ADDRESS_LINE4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — address components used for geographic reporting and country-specific analysis such as Italy.
• DATE_FROM, DATE_TO — effective dating for the location record.
• VNDR_PURCH_SITE, VNDR_RFQ_ONLY, VNDR_PAY_SITE, VNDR_PAY_TERMS — supplier-specific site and payment attributes.
• CUST_SITE_USE, CUST_LOCATION, CUST_PRIMARY_FLAG, CUST_STATUS, CUST_PAY_TERMS — customer-specific site and status attributes.
• COLLECTION_STATUS, OPERATION_CODE, ERROR_CODE, REQUEST_ID — staging control columns used by the collection program.
• INSTANCE — identifies the source EBS instance, essential in multi-instance deployments.
• LAST_UPDATE_DATE, CREATION_DATE — audit timestamps for incremental loading.

The surrogate key is TPARTNER_LOC_PK, while TRADE_PARTNER_FK_KEY combined with the location attributes serves as the business-key candidate for deduplication and upserts.

Common Use Cases and Queries

Typical use cases include supplier and customer spend analysis, geographic reporting (for example, filtering to Italy via COUNTRY), and supplier consolidation by parent trade partner. A representative query joins the staging table to the system instance table and filters by business type and country:

SELECT t.NAME, t.CITY, t.COUNTRY, t.BUSINESS_TYPE FROM POA.EDW_TPRT_TPARTNER_LOC_LSTG t WHERE t.COUNTRY = 'IT' AND t.COLLECTION_STATUS = 'COMPLETE';

A second pattern identifies collection errors during load runs: SELECT REQUEST_ID, ERROR_CODE, COUNT(*) FROM POA.EDW_TPRT_TPARTNER_LOC_LSTG WHERE ERROR_CODE IS NOT NULL GROUP BY REQUEST_ID, ERROR_CODE;

A third pattern joins supplier attributes to spend facts to reconcile purchasing sites: SELECT VNDR_PURCH_SITE, VNDR_PAY_TERMS FROM POA.EDW_TPRT_TPARTNER_LOC_LSTG WHERE BUSINESS_TYPE = 'VNDR' AND DATE_TO IS NULL;

Related Objects

• CS_SYSTEMS_ALL_B_TEMP — referenced through ROW_ID; provides the source system instance context for the staged rows.
• POA_TPARTNER_LOC_LSTG (or equivalent EDW dimension target) — the downstream load target for validated records.
• EDW_TPRT_TPARTNER_LSTG — the parent trade partner staging table, joined via TRADE_PARTNER_FK.
• POA spend fact tables (for example, EDW_PA_SPEND_F) — join on trade partner and location keys for spend analytics.
• FND request tables (FND_CONCURRENT_REQUESTS) — correlate REQUEST_ID to collection program runs.

These relationships anchor the staging table within the broader POA extract-transform-load pipeline.