Search Results party_name_txt

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

Overview

OKC_REP_IMP_PARTIES_T is a temporary (staging) table owned by the OKC schema within the Contracts Core module of Oracle E-Business Suite, and is available in both 12.1.1 and 12.2.2. Its documented purpose is to store the attributes of an imported contract party while the import process runs. Specifically, it holds raw party records extracted from a source file or interface, supports validation of those party records, prepares the party data for insertion into the Contracts Repository schema, and serves as the source for error messages generated when an imported party fails validation. The table therefore sits at the front end of the contract import pipeline rather than in the production contract repository itself, and its rows are conventionally transient — populated, validated, consumed, and purged by the import program.

From a data modeling perspective, the ETRM metadata classifies this object heuristically as standalone under the Data Vault classification scheme. That classification should be treated as a modeling suggestion only: because the table is a flattened staging structure with a single documented foreign key out to OKC_REP_IMP_CONTRACTS_T, it does not function as a true hub, link, or satellite. It is best understood as a staging entity whose natural parent is the imported contract header.

Key Information Stored

The table is documented with 18 columns. The most significant are the following.

• IMP_PARTY_ID — the surrogate primary key, enforced by unique index/constraint OKC_REP_IMP_PARTIES_T_PK1 and also carried by unique index OKC_REP_IMP_PARTIES_T_U1, making it the primary business-key candidate for the staging row.
• IMP_CONTRACT_ID — foreign key to OKC_REP_IMP_CONTRACTS_T, tying each staged party to the staged contract header being imported.
• CONTRACT_ID — the target contract identifier once the party is resolved against the Contracts Repository.
• CONTRACT_PARTY_ID — the resulting party identifier in the repository, populated as part of the import resolution.
• PARTY_ID — the identifier of the party (for example, a customer, supplier, or contact) referenced by the imported contract.
• PARTY_ROLE_CODE — the coded role the party plays on the contract, used for validation against role setup.
• PARTY_NAME_TXT and PARTY_ROLE_TXT — free-text name and role captured from the import source, typically retained for validation and error reporting.
• SIGNED_BY_TXT and SIGNED_DATE — the signatory and signature date for the party on the contract.
• VALID_FLAG — the validation outcome indicator, driving whether the row proceeds to repository load or is reported as an error.
• PARTY_INDEX — the ordinal position of the party within the imported contract.
• Audit and run context columns — CREATION_DATE, PROGRAM_ID, PROGRAM_LOGIN_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, and RUN_ID, which record who or which concurrent request loaded each staging row.

Common Use Cases and Queries

Typical use is diagnostic and reconciliation work around contract imports. The most common pattern is to list the parties staged for a given imported contract and inspect their validation status:

• SELECT imp_party_id, party_id, party_role_code, party_name_txt, valid_flag FROM okc.okc_rep_imp_parties_t WHERE imp_contract_id = :p_imp_contract_id ORDER BY party_index;
• SELECT party_role_code, COUNT(*) FROM okc.okc_rep_imp_parties_t WHERE valid_flag = 'N' GROUP BY party_role_code; — to identify which roles most frequently fail validation.
• A join to OKC_REP_IMP_CONTRACTS_T on IMP_CONTRACT_ID to correlate party errors with the parent contract record.
• A join to OKC_REP_IMP_CONTACTS_T on IMP_PARTY_ID to see the contacts staged against each party.
• Audit-style queries restricted by REQUEST_ID or RUN_ID to isolate the rows produced by one import run, and queries against CREATION_DATE to track import volumes over time.

Because the table is temporary in nature, queries should be scoped to the current or most recent import run; historical rows are not guaranteed to persist.

Related Objects

• OKC_REP_IMP_CONTRACTS_T — parent staging table; joined via OKC_REP_IMP_PARTIES_T.IMP_CONTRACT_ID → OKC_REP_IMP_CONTRACTS_T.
• OKC_REP_IMP_CONTACTS_T — child staging table; references this table through OKC_REP_IMP_CONTACTS_T.IMP_PARTY_ID → OKC_REP_IMP_PARTIES_T.
• Contract import concurrent program(s) in the OKC module that populate, validate, and consume these staging rows, writing errors for records whose VALID_FLAG is not set.
• Contracts Repository party entities (contract parties / contract party roles) that represent the final destination of validated rows, with CONTRACT_ID, CONTRACT_PARTY_ID, and PARTY_ID recorded here for traceability.
• OKC party and role setup objects used to validate PARTY_ROLE_CODE during the import.