Search Results oki_k_salesreps

Overview

OKI_K_SALESREPS is a Contracts Intelligence table in the OKI product/module, historically used to store the sales representatives associated with contracts. Contracts Intelligence (OKI) was an Oracle E-Business Suite module positioned around contract analytics, reporting, and related data extraction from the core Contracts (OKC) and Order Management schema. In the documented ETRM metadata the product is explicitly flagged as Obsolete, and the implementation note states "Not implemented in this database," meaning the table is a legacy artifact retained for reference and historical upgrade purposes rather than an active transactional object in Oracle EBS 12.1.1 or 12.2.2.

Despite its obsolete status, the object carries a fully documented physical definition: the OKI owner schema, 25 columns in the 12.1.1 baseline, a primary key OKI_K_SALESREPS_PK defined on PARTY_CONTACT_ID, and a unique index OKI_K_SALESREPS_U1 on PARTY_CONTACT_ID. Its role in EBS was to hold the denormalized salesrep association details needed by Contracts Intelligence reporting, relating a contract to the party/contact that acts as the sales representative. The heuristic Data Vault classification mined from the FK structure is standalone; in Data Vault modeling terms this suggests treating the object as an independent structure rather than a dependent satellite — a hub- or link-like pattern centered on the PARTY_CONTACT_ID business key, without strong downstream FK dependency chains to wrap it as a satellite.

Key Information Stored

The table stores a compact set of contract-to-salesrep attribution attributes. The most significant documented columns are:

• PARTY_CONTACT_ID — the primary key column of OKI_K_SALESREPS_PK and also the sole column of the unique index OKI_K_SALESREPS_U1, making it the principal business-key candidate for the row.
• CONTRACT_ID — identifies the contract to which the salesrep assignment belongs.
• PARTY_ROLE_ID — the party role context under which the salesrep participates.
• CONTACT_ID — the contact record representing the individual salesrep.
• CONTACT_ROLE_CODE — the role classification of the contact.
• SALESREP_NAME — the denormalized display name of the sales representative.
• CREATION_DATE / LAST_UPDATE_DATE — standard audit columns capturing row creation and last modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) column set, preserved for extensible customer-defined attributes.
• SECURITY_GROUP_ID — the multi-tenant/security grouping column, which is also the only referenced FK target documented (to FND_SECURITY_GROUPS).

The distinction between the surrogate primary key and business-key candidates is minimal here: PARTY_CONTACT_ID serves both roles, appearing as the PK column and as the unique index column, which simplifies the identifier model but also means the object has a single, narrow identity anchor.

Common Use Cases and Queries

Because the table is obsolete and not implemented in the current database, practical use is confined to legacy reporting, migration validation, and gap analysis during upgrades from earlier OKI-enabled instances. Typical patterns include verifying surviving salesrep attribution after data conversion, reconciling contract-to-salesrep mappings against OKC contract data, and auditing the DFF attribute columns for customer extensions. Representative SQL patterns include:

• Retrieve all salesreps for a contract: SELECT party_contact_id, contract_id, contact_id, salesrep_name FROM oki_k_salesreps WHERE contract_id = :contract_id;
• Look up a single assignment by its unique key: SELECT * FROM oki_k_salesreps WHERE party_contact_id = :party_contact_id;
• Security-scoped reporting: SELECT s.* FROM oki_k_salesreps s, fnd_security_groups g WHERE s.security_group_id = g.security_group_id;
• Utilization audit of the DFF attributes: SELECT attribute_category, COUNT(*) FROM oki_k_salesreps GROUP BY attribute_category;

Any such query should be preceded by confirming object existence, since the ETRM metadata records the table as not implemented in the target database.

Related Objects

The documented foreign key relationship is limited, but the following objects are the most significant related structures:

• FND_SECURITY_GROUPS — the only documented FK target, joined on OKI_K_SALESREPS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID, governing row-level security visibility.
• OKC_K_HEADERS / OKC_CONTRACTS — the core Contracts headers that provide the CONTRACT_ID context for salesrep assignments.
• HZ_PARTIES / HZ_RELATIONSHIPS — source of party and contact identities underlying PARTY_CONTACT_ID and CONTACT_ID.
• JTF_RS_SALESREPS — the salesrep resource definition against which SALESREP_NAME attributes typically align.
• OKI_K_CONTRACTS and other OKI_K_* staging tables — sibling Contracts Intelligence extracts sharing the CONTRACT_ID and SECURITY_GROUP_ID conventions.

These relationships should be validated against the actual installed schema, as the obsolete OKI objects may exist only in historical references.