Search Results doc_sub_line_id_int_2

Overview

The OE_SALES_CONTINGENCY_RM_V view is an Order Management (ONT) reporting and integration object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name and structure indicate its purpose: it exposes sales contingency information — specifically sales credit allocations and related contingency data — in a denomination-agnostic, record-manager style format. The "_RM_V" suffix denotes a view intended for consumption by Oracle's Record Manager framework and by downstream reporting or integration layers that require a normalized sub-line representation of sales credit data.

Rather than presenting raw transactional rows, the view shapes data into a consistent set of DOC_* columns such as DOC_SUB_LINE_TYPE, DOC_SUB_LINE_LEVEL, DOC_SUB_LINE_ID_INT_1, DOC_LINE_ID_INT_1, and DOC_ID_INT_1. This structure supports tools that treat contingencies and sales credits as subordinate document lines tied to an order header and line. The view also carries contingency-related columns such as CONTINGENCY_NAME, CONTINGENCY_ID, EXPIRATION_DATE, and EXPIRED_FLAG, which are populated in the contingency portion of the definition and left NULL in the sales-credit portion.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view references four base objects through APPS synonyms:

• OE_SALES_CREDITS — the primary source of sales credit allocations, providing SALES_CREDIT_ID, SALESREP_ID, PERCENT, SALES_CREDIT_TYPE_ID, and the header/line foreign keys.
• OE_ORDER_LINES_ALL — supplies the associated order line context, including LINE_ID, HEADER_ID, and ORG_ID.
• JTF_RS_SALESREPS — the sales representative resource table, providing the salesrep name and the GL_ID_REV value surfaced as CODE_COMBINATION_ID.
• AR_DEFERRAL_REASONS — referenced for contingency/deferral reason logic within the full view definition.

The visible view text joins OE_SALES_CREDITS to JTF_RS_SALESREPS on SALESREP_ID and to OE_ORDER_LINES_ALL on both HEADER_ID and LINE_ID, with an additional organization match on ORG_ID.

Key Columns

• DOC_SUB_LINE_TYPE — identifies the sub-line category; the excerpt shows the literal value 'SALESCREDITS'.
• DOC_SUB_LINE_LEVEL — indicates the level of the sub-line; the excerpt uses 'L' for line level.
• DOC_SUB_LINE_ID_INT_1 / DOC_SUB_LINE_ID_INT_2 — surrogate keys for the sub-line, populated with SALES_CREDIT_ID and LINE_ID.
• DOC_LINE_ID_INT_1 / DOC_ID_INT_1 — the associated order line and order header identifiers.
• CODE_COMBINATION_ID — the revenue accounting flexfield from JTF_RS_SALESREPS.GL_ID_REV.
• SALESREP_ID / SALESREP_NAME — the sales representative and their descriptive name.
• REVENUE_PERCENT_SPLIT — the percentage of revenue credited, sourced from OE_SALES_CREDITS.PERCENT.
• ORG_ID — the operating unit context.
• Contingency columns — CONTINGENCY_NAME, CONTINGENCY_ID, EXPIRATION_DATE, EXPIRATION_DAYS, EXPIRED_FLAG, EXPIRATION_EVENT_DATE, and EXPIRED_BY.

Common Use Cases and Queries

Typical use cases include revenue-credit reporting by salesrep, contingency expiration monitoring, and integration into a Record Manager or order-contingency feed. A representative query retrieves sales credit lines for an order:

SELECT doc_id_int_1,
       doc_line_id_int_1,
       salesrep_name,
       revenue_percent_split,
       code_combination_id
FROM   apps.oe_sales_contingency_rm_v
WHERE  doc_sub_line_type = 'SALESCREDITS'
AND    org_id = :p_org_id
ORDER  BY doc_id_int_1, doc_line_id_int_1;

For contingency review, filtering on EXPIRED_FLAG or EXPIRATION_DATE highlights credits approaching expiration. Because the view normalizes both header-level and line-level sales credits through a UNION, it should be treated as a read-only reporting source rather than an update target.