Results for “okx_salepers”

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

Overview

APPS.OKC_KEXP_REPORT_V is a reporting view in the Oracle E-Business Suite Contracts (OKC) module that exposes contract expense reporting data, currency, estimated amounts, and associated customer, salesperson, and territory attributes. The view is primarily used in Oracle EBS 12.1.1 and 12.2.2 environments for extracting information related to contract expense reports (identified by the KEXP naming convention, derived from OKC Expense Report). It is a denormalized read-only view that joins core contract tables with territory and party role objects to produce a flat reporting structure suitable for operational queries and downstream integrations.

The "SLA-KPR" search term maps to this object because the view joins OKC_K_PARTY_ROLES_B (KPR) and related service level agreement (SLA) contract headers, exposing customer role assignments attached to contract versions. This makes the view relevant to both SLA-related contract analysis and expense reporting scenarios.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKC_KEXP_REPORT (SYNONYM) — stores contract expense report header records.
• OKC_K_HEADERS_B (SYNONYM) — the base contract headers table (CHRV alias), providing contract_number, currency_code, estimated_amount, start_date, and end_date.
• OKC_K_PARTY_ROLES_B (SYNONYM) — party roles on contracts (KPR), filtered to customer roles.
• OKC_K_VERS_NUMBERS (SYNONYM) — contract version numbering (KVER).
• OKC_CONTACTS (SYNONYM) — contact information used to derive the salesperson (KCON).
• JTF_TERR_ALL, JTF_TERR_QUAL_ALL, JTF_TERR_VALUES_ALL (SYNONYMS) — territory definition, qualification, and value tables from the CRM Foundation, used to resolve territory names.
• OKC_UTIL (PACKAGE) — utility package supplying OKC_UTIL.get_name_from_jtfv for customer name resolution.
• OKC_KEXP_PVT (PACKAGE) — private package supplying OKC_KEXP_PVT.get_salesrep_name for salesperson name resolution.

The central join links OKC_KEXP_REPORT.CONTRACT_HEADER_ROWID to OKC_K_HEADERS_B via ROWID, with additional joins to party roles, contacts, and territory tables through shared IDs and coded lookups such as CRO_CODE = 'SUP_SALES' and JTOT_OBJECT1_CODE = 'OKX_PARTY'.

Key Columns

• CONTRACT_NUMBER — the human-readable contract identifier from OKC_K_HEADERS_B.
• CURRENCY — the contract's currency code.
• AMOUNT — the estimated contract amount.
• START_DATE / END_DATE — effective date range of the contract header.
• CUSTOMER — resolved party name via OKC_UTIL.get_name_from_jtfv, based on KPR party role definition (OKX_PARTY).
• SALESREP — salesperson name resolved via OKC_KEXP_PVT.get_salesrep_name from OKC_CONTACTS where CRO_CODE = 'SUP_SALES'.
• TERRITORY — territory name (JT.NAME) derived through the JTF_TERR hierarchy.
• REPORT_ID — identifier of the expense report row from OKC_KEXP_REPORT.
• LAST_UPDATE_DATE — version timestamp from OKC_K_VERS_NUMBERS.

Common Use Cases and Queries

Typical uses include contract expense reporting, SLA customer/territory analysis, and sales pipeline reporting by salesperson and territory. The view excludes renewed contract headers via the CHRV.CHR_ID_RENEWED IS NULL predicate, restricting output to active (non-renewed) contract versions.

Example query to list all expense reports by territory:

• SELECT contract_number, customer, salesrep, territory, amount, currency FROM apps.okc_kexp_report_v WHERE territory = :p_territory ORDER BY contract_number;

Example query for a specific salesperson's contract expense pipeline:

• SELECT contract_number, customer, amount, start_date, end_date FROM apps.okc_kexp_report_v WHERE salesrep = :p_salesrep;

Example query joining to retrieve the latest updated reports:

• SELECT report_id, contract_number, last_update_date FROM apps.okc_kexp_report_v WHERE last_update_date >= :p_from_date;

Because the view performs multiple outer joins and invokes PL/SQL package functions, it should be used with selective predicates—especially on TERRITORY, CUSTOMER, or SALESREP—to maintain acceptable performance on large contracts datasets.