Search Results customer_acceptance

Overview

APPS.OE_SALES_CONTINGENCY_RM_V is a reporting and integration view in Oracle E-Business Suite that consolidates Order Management sales credit assignments into a uniform "document sub-line" structure. It is designed primarily for Revenue Management and related revenue-recognition reporting, presenting sales credit and contingency information in a shape that downstream revenue engines and reporting layers can consume consistently. The view unifies two logical categories of data — sales credits associated with order lines, and contingency records — into a single result set distinguished by the DOC_SUB_LINE_TYPE column (values include 'SALESCREDITS' and 'CONTINGENCIES'). For users searching on "salesrep_name," this view is directly relevant because it exposes the JTF.NAME column aliased as SALESREP_NAME, giving a human-readable sales representative name alongside the numeric SALESREP_ID sourced from the sales credit records.

Underlying Base Objects

The view is defined over the following documented base objects, accessed via APPS synonyms:

• OE_SALES_CREDITS — the primary driving table (aliased OESC), supplying sales credit identifiers, sales rep IDs, percent splits, sales credit type, creation and update dates, and header/line foreign keys.
• JTF_RS_SALESREPS (alias jtf) — the resource/sales rep repository, joined on SALESREP_ID to resolve the rep name (JTF.NAME) and the revenue general ledger code combination (JTF.GL_ID_REV).
• OE_ORDER_LINES_ALL (alias OEL) — the order line table, joined on HEADER_ID and LINE_ID to bring ORG_ID and to enforce multi-org alignment via jtf.org_id = OEL.org_id.
• AR_DEFERRAL_REASONS — listed as a referenced base object supporting the revenue/contingency (deferral) semantics of the view even though it does not appear in the excerpted top-level join text.

The body is a three-branch UNION ALL. The first branch captures sales credits where LINE_ID is not null (line-level credits). The second branch captures header-level credits (LINE_ID null) where the order line does not itself carry a line-level sales credit. The third branch addresses contingency records. Because of this structure, callers should expect the contingency-specific columns to be populated only for the CONTINGENCIES branch and null for sales credit rows.

Key Columns

• SALESREP_NAME — the sales representative name from JTF_RS_SALESREPS, the column most frequently queried by users.
• SALESREP_ID — the numeric identifier linking the credit to a resource.
• REVENUE_PERCENT_SPLIT — the percentage of the revenue attribution assigned to that sales rep.
• CODE_COMBINATION_ID — the revenue account code combination from the sales rep resource.
• DOC_SUB_LINE_TYPE / DOC_SUB_LINE_LEVEL — classify the record (e.g., SALESCREDITS, level 'L').
• DOC_SUB_LINE_ID_INT_1, DOC_SUB_LINE_ID_INT_2, DOC_LINE_ID_INT_1, DOC_ID_INT_1 — surrogate identifiers for sub-line, line, and header used by the revenue engine.
• ORG_ID, SUB_LINE_CREATION_DATE, SUB_LINE_LAST_UPDATE_DATE — organization and audit context.

Common Use Cases and Queries

Typical usage includes reporting sales credit splits by representative, verifying revenue account assignments, and feeding revenue-recognition processing. A representative query resolving sales rep names for an order is:

• SELECT salesrep_name, revenue_percent_split, doc_line_id_int_1, org_id FROM apps.oe_sales_contingency_rm_v WHERE doc_sub_line_type = 'SALESCREDITS' AND doc_id_int_1 = :header_id;
• SELECT DISTINCT salesrep_name FROM apps.oe_sales_contingency_rm_v WHERE doc_line_id_int_1 = :line_id ORDER BY salesrep_name;

Filtering on DOC_SUB_LINE_TYPE is recommended to isolate sales credits from contingency rows and to avoid interpreting null contingency columns.