Results for “rep_name”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKS_REPNAME_V is a VALID, APPS-owned database view within the OKS – Service Contracts module of Oracle E-Business Suite, documented identically across 12.1.1 and 12.2.2. As stated in its documented description, the view is "Used for Service Contracts Summary Report." It consolidates contract header, customer party, status, and internal sales-representative data into a single flattened row per contract, enabling the Service Contracts Summary Report to present contract-level facts without navigating the normalized Service Contracts (OKC) and Trading Community (HZ) schemas. The view is a report-serving construct rather than a transactional entity: it exposes no DML surface and is not a base table for downstream processing. Because it joins synonym-backed OKC and HZ objects, it is sensitive to profile-option settings and to the existence of a designated vendor contact role on the contract.
Underlying Base Objects
The documented referenced base objects are: FND_GLOBAL (PACKAGE), FND_PROFILE (PACKAGE), HZ_PARTIES (SYNONYM), OKC_CONTACTS_V (VIEW), OKC_K_HEADERS_B (SYNONYM), OKC_K_PARTY_ROLES_B (SYNONYM), OKC_K_PARTY_ROLES_V (VIEW), OKC_STATUSES_V (VIEW), and OKS_EXTWAR_UTIL_PVT (PACKAGE).
The view text is driven by a core join chain: OKC_K_HEADERS_B K supplies the contract header record; OKC_K_PARTY_ROLES_B PR links the customer role to that header where PR.CLE_ID IS NULL and PR.RLE_CODE = 'CUSTOMER'; HZ_PARTIES PX resolves the customer's identifiers and name; and OKC_STATUSES_V ST translates K.STS_CODE into a user-facing meaning. The REP_NAME column is derived by a scalar subquery against OKC_CONTACTS_V, filtered first by the OKS_VENDOR_CONTACT_ROLE profile option (defaulting to 'SUP_SALES' via FND_PROFILE.VALUE) and then by an inner lookup into OKC_K_PARTY_ROLES_V for a party role with RLE_CODE = 'VENDOR' and CLE_ID IS NULL. The view restricts to contract classes through K.SCS_CODE IN ('SERVICE', 'WARRANTY'). FND_GLOBAL and OKS_EXTWAR_UTIL_PVT are listed as dependencies, with the latter associated with warranty entitlement utility logic. Both REP_NAME subqueries are capped by ROWNUM < 2 to guarantee scalar, single-row returns.
Key Columns
- TOTAL_VALUE — Sourced from K.ESTIMATED_AMOUNT, the monetary value of the contract. This is the column users most commonly search for; it is the estimated amount held on the contract header, not a computed sum of lines or billings.
- CONTRACT_ID / CONTRACT_NUMBER / CONTRACT_MODIFIER — The internal header identifier (K.ID) and the externally visible contract number with its modifier, allowing joins back to OKC_K_HEADERS_B and direct user communication of the contract reference.
- REP_NAME — The sales or vendor representative resolved through the OKS_VENDOR_CONTACT_ROLE profile option, defaulting to SUP_SALES. May be NULL when no matching role or contact exists.
- CUSTOMER_ID / CUSTOMER_NAME / CUSTOMER_NUMBER — Party identifiers, name, and party number from HZ_PARTIES for the CUSTOMER-role party.
- STATUS_CODE / STATUS_MEANING / STATUS_TYPE — The raw status code (K.STS_CODE), its translated meaning (ST.MEANING), and status type (ST.STE_CODE).
- START_DATE / END_DATE — Contract effective period from the header.
- ORG_ID / CURRENCY_CODE / LAST_UPDATE_DATE — Authoring organization, contract currency, and last update timestamp. ORG_ID supports multi-org filtering in reports.
Common Use Cases and Queries
The primary use case is reporting on active service and warranty contracts with their value, customer, and owner. A representative query for retrieving contract value by customer is:
SELECT contract_number, customer_name, total_value, currency_code, status_meaning, start_date, end_date FROM apps.oks_repname_v WHERE org_id = :p_org_id AND total_value > 0 ORDER BY total_value DESC;
To identify contracts lacking an assigned representative:
SELECT contract_id, contract_number, total_value FROM apps.oks_repname_v WHERE rep_name IS NULL;
To aggregate total contract exposure per customer:
SELECT customer_number, customer_name, COUNT(*) contract_count, SUM(total_value) total_value FROM apps.oks_repname_v GROUP BY customer_number, customer_name;
Because TOTAL_VALUE maps to ESTIMATED_AMOUNT on the header, reconciliations between this view and OKC_K_HEADERS_B are direct. Queries should always filter by ORG_ID in multi-organization environments, and applications should treat REP_NAME as optionally NULL.
-
View: OKS_REPNAME_V 12.2.2
This View is Used for Service Contracts Summary Report
APPS.OKS_REPNAME_V·↳ FND_GLOBAL·↳ FND_PROFILE·↳ HZ_PARTIES·Explore OKS module →
-
View: OKS_REPNAME_V 12.1.1
This View is Used for Service Contracts Summary Report
APPS.OKS_REPNAME_V·↳ FND_GLOBAL·↳ FND_PROFILE·↳ HZ_PARTIES·Explore OKS module →
-
VIEW: APPS.CN_SRP_PLAN_LOV_V 12.2.2
-
VIEW: APPS.CN_SRP_PLAN_LOV_V 12.1.1
-
VIEW: APPS.OKS_REPNAME_V 12.2.2
-
VIEW: APPS.OKS_REPNAME_V 12.1.1
-
VIEW: APPS.CN_SRP_PLAN_LOV_V 12.2.2
-
VIEW: APPS.CN_SRP_PLAN_LOV_V 12.1.1
-
Sales Representative View
Not implemented in this database·Explore ICX module →
-
Sales Representative View
Not implemented in this database·Explore ICX module →
-
VIEW: APPS.OKS_REPNAME_V 12.1.1
-
VIEW: APPS.OKS_REPNAME_V 12.2.2
-
PACKAGE: APPS.PAY_MX_TRR_PKG 12.1.1
-
PACKAGE: APPS.PAY_MX_TRR_PKG 12.2.2