Results for “sic_code”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The EDW_TPRT_P4_TPARTNER_LSTG object is a staging and extract table within the Oracle EBS Business Intelligence System (BIS) product family, owned by the POA schema. It is a denormalized, 36-column structure designed to hold third-party partner listing data — trading partner records that describe vendor, supplier, and business partner entities used across procurement, payables, and supply chain modules. The _LSTG suffix indicates its role as a list/staging table that feeds downstream ETL processes, data warehouse extracts, or interface programs rather than serving as a transactional master. The P4 segment reflects an internal processing-stage naming convention typical of publicly sector-oriented BIS extracts.
Based on the documented foreign key relationship — ROW_ID referencing CS_SYSTEMS_ALL_B_TEMP — the metadata suggests a standalone Data Vault classification (heuristic, mined from FK structure). In practice this means the table functions largely as an isolated staging surface rather than a true hub, link, or satellite. If modeled into a Data Vault, the surrogate ROW_ID and business identifiers (TPARTNER_PK, VENDOR_NUMBER) would most naturally form a hub, with descriptive attributes treated as satellite content. The ETRM documentation notes this object is "Not implemented in this database" in the reference environment, confirming it is a design-time artifact rather than an active runtime table in every deployment.
Key Information Stored
The table's columns fall into identity, classification, and lifecycle groupings. The most significant are:
TPARTNER_PK— the primary identifier for the third-party partner record, the principal business-key candidate.ROW_ID— the surrogate/technical key, also serving as the documented foreign key toCS_SYSTEMS_ALL_B_TEMP.PARENT_TPARTNER_FKandPARENT_TPARTNER_FK_KEY— self-referencing hierarchy columns supporting parent/child partner structures.NAME,ALTERNATE_NAME,TPARTNER_DP— partner descriptive and display attributes.VENDOR_NUMBERandVENDOR_TYPE— the vendor linkage that ties the partner to supplier master data.START_ACTIVE_DATEandEND_ACTIVE_DATE— effectivity window for the partner record.TAX_REG_NUM,TAXPAYER_ID,SIC_CODE— regulatory and classification identifiers.PAYMENT_TERMS— default payment terms associated with the partner.- Diversity/status flags —
MINORITY_GROUP,WOMEN_OWNED,SMALL_BUSINESS,ONE_TIME_FLAG,HOLD_FLAG. - Receiving controls —
INSPECT_REQUIRED,RECEIPT_REQUIRED,ALLOW_SUB_RECEIPT,ALLOW_UNORDER_RCV. - ETL audit columns —
REQUEST_ID,OPERATION_CODE,ERROR_CODE,COLLECTION_STATUS,LAST_UPDATE_DATE,CREATION_DATE, plus fiveUSER_ATTRIBUTEflex fields.
Common Use Cases and Queries
Because the table is a staging surface, typical usage centers on extraction, reconciliation, and partner-master validation. A common pattern filters active partners by effectivity window:
SELECT TPARTNER_PK, NAME, VENDOR_NUMBER, VENDOR_TYPE, PAYMENT_TERMS FROM POA.EDW_TPRT_P4_TPARTNER_LSTG WHERE START_ACTIVE_DATE <= SYSDATE AND (END_ACTIVE_DATE IS NULL OR END_ACTIVE_DATE >= SYSDATE);
Small-business and diversity reporting relies on the flag columns to produce spend analyses:
SELECT VENDOR_TYPE, SMALL_BUSINESS, WOMEN_OWNED, MINORITY_GROUP, COUNT(*) FROM POA.EDW_TPRT_P4_TPARTNER_LSTG GROUP BY VENDOR_TYPE, SMALL_BUSINESS, WOMEN_OWNED, MINORITY_GROUP;
Error reconciliation examines ERROR_CODE, OPERATION_CODE, and COLLECTION_STATUS to identify failed or pending ETL loads, while hierarchy traversal joins PARENT_TPARTNER_FK back to TPARTNER_PK for parent/child reporting.
Related Objects
The documented relationship links this table to CS_SYSTEMS_ALL_B_TEMP via ROW_ID, indicating a staging-chain dependency. In EBS practice, related objects include:
CS_SYSTEMS_ALL_B_TEMP— temp staging parent (join onROW_ID).PO_VENDORS/PO_VENDOR_SITES_ALL— supplier master tied viaVENDOR_NUMBER.AP_SUPPLIERS— payables supplier representation.AP_TERMS— resolution target forPAYMENT_TERMS.RCV_SHIPMENT_HEADERS— receiving logic influenced by the receipt/inspection flags.POA_TPARTNER-family views and BIS ETL programs that populate and consume this list-staging table.
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →