Results for “okc_rep_imp_parties_t_u1”

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

Overview

OKC.OKC_REP_IMP_PARTIES_T is a temporary staging table in the Oracle E-Business Suite Contracts (OKC) schema that holds the party-level attributes of contracts being loaded through the Contracts Repository import process. It functions as an interface table: rows are inserted from an external source (typically a CSV file processed by the concurrent import program), validated against existing party and party-role definitions, and then either promoted into the production contract tables or flagged for correction. The data is deleted after each import process completes, so the table is transient by design and resides in the APPS_TS_INTERFACE tablespace with a PCT Free of 10.

From a modeling perspective, the heuristic Data Vault classification for this object is standalone. No parent hub or link relationship beyond its staging foreign key to OKC_REP_IMP_CONTRACTS_T was mined, so it is best treated as a transient staging entity rather than a durable hub, link, or satellite. Where it is retained for audit or reconciliation, a satellite-style treatment keyed on the import party identifier would be the natural extension.

Key Information Stored

The table is defined with 18 documented columns. The most operationally significant are:

• IMP_PARTY_ID — surrogate primary key (OKC_REP_IMP_PARTIES_T_PK1), generated from sequence OKC_REP_IMP_PARTIES_T_S. It is also the column behind the unique index OKC_REP_IMP_PARTIES_T_U1, making it both the surrogate key and the documented business-key candidate.
• IMP_CONTRACT_ID — foreign key to OKC_REP_IMP_CONTRACTS_T.imp_contract_id, tying the party row to its parent staged contract.
• CONTRACT_ID — identifier of the target contract in OKC_REP_CONTRACTS_ALL once the import is committed.
• CONTRACT_PARTY_ID — primary key value destined for insertion into the production contract-party table, generated from OKC_REP_CONTRACT_PARTIES_S.
• PARTY_INDEX — ordinal position of the party within the source CSV file (1 for the first party, 2 for the second, and so on).
• PARTY_ID — the resolved primary key of the party, which may point to HR_ALL_ORGANIZATION_UNITS, HZ_PARTIES, or PO_VENDORS depending on the party role.
• PARTY_NAME_TXT — the user-entered party name that must resolve to a record in HZ_PARTIES, PO_VENDORS, or HR_ALL_ORGANIZATION_UNITS.
• PARTY_ROLE_CODE — the party role derived from OKC_DEL_RESP_PARTIES_B.resp_party_code.
• PARTY_ROLE_TXT — the literal role text supplied by the user and validated against the defined party roles.
• SIGNED_BY_TXT and SIGNED_DATE — signatory name and signing date captured as text during import.
• VALID_FLAG — indicates whether the staged party row passed validation.
• REQUEST_ID, PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, and RUN_ID — concurrent-program and run identifiers used to isolate a single import execution; REQUEST_ID is indexed by OKC_REP_IMP_PARTIES_T_N1.

Common Use Cases and Queries

Typical usage centers on monitoring, troubleshooting, and reconciling a contract import. A frequent query retrieves all staged parties for a given concurrent request:

• SELECT imp_party_id, imp_contract_id, party_name_txt, party_role_txt, valid_flag FROM okc.okc_rep_imp_parties_t WHERE request_id = :request_id ORDER BY imp_contract_id, party_index;
• Identifying rows that failed validation before the run is purged: SELECT * FROM okc.okc_rep_imp_parties_t WHERE valid_flag = 'N' AND request_id = :request_id;
• Joining to the parent staged contract to report parties per imported contract: SELECT c.imp_contract_id, p.party_name_txt, p.party_role_txt FROM okc.okc_rep_imp_parties_t p JOIN okc.okc_rep_imp_contracts_t c ON c.imp_contract_id = p.imp_contract_id WHERE p.request_id = :request_id;

Because rows are deleted after each import, these queries are meaningful only while the run is in flight or before the cleanup step. The table should not be used as a long-term reporting source.

Related Objects

• OKC.OKC_REP_IMP_CONTRACTS_T — parent staging table; joined on imp_contract_id.
• OKC.OKC_REP_IMP_CONTACTS_T — child staging table referencing this table via imp_party_id.
• OKC.OKC_REP_IMP_ERRORS_T — error repository referenced in the ETRM documentation for invalid party attributes.
• OKC.OKC_REP_CONTRACTS_ALL — production contract table receiving the promoted contract_id.
• OKC.OKC_REP_CONTRACT_PARTIES_S — sequence supplying contract_party_id for production inserts.
• OKC.OKC_DEL_RESP_PARTIES_B — source of valid party role codes used for validation.
• HZ.HZ_PARTIES, PO.PO_VENDORS, and HR.HR_ALL_ORGANIZATION_UNITS — party master sources against which party_id and party_name_txt resolve.