Search Results dw_update_advice_flag




Overview

ASO_I_OE_SALES_CREDITS_V is an APPS-owned database view in Oracle E-Business Suite, registered as a VALID object within the ASO (Order Capture) product family. Its documented purpose is to retrieve sales credit information from Order Management. In practice, the view serves as a stable, interface-oriented projection of the sales credit records that Order Management maintains, allowing downstream components — order capture, quoting, integrations, and reporting layers — to consume sales credit data through a pre-defined column list rather than querying the transactional base table directly.

Because the view is catalogued under ASO but sources its data entirely from Order Management structures, it functions as a cross-module bridge. The "I" convention in the object name indicates an interface view, commonly used by concurrent programs, APIs, and data-extraction routines that require a consistent representation of sales credits for processing or replication into other systems. It is exposed in both EBS 12.1.1 and 12.2.2 with identical documented structure.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: OE_SALES_CREDITS, accessed through a SYNONYM. The view is a straightforward, non-joining projection — the view text is a direct SELECT of named columns FROM OE_SALES_CREDITS, without aggregations, filters, or joins. Consequently, each row in the view corresponds one-to-one with a row in OE_SALES_CREDITS.

OE_SALES_CREDITS is the Order Management table that stores sales credit assignments, allocating a percentage of an order or order line to one or more salespersons. Because the view merely renames and re-exposes that table under an ASO-facing name, it inherits the transaction context of Order Management, including header-level and line-level associations, multi-org operating unit implications, and the standard EBS audit and descriptive flexfield columns.

Key Columns

  • SALES_CREDIT_ID — Primary key uniquely identifying each sales credit record.
  • HEADER_ID — Foreign key to the order or quote header owning the credit.
  • LINE_ID — Optional foreign key to the specific order line; when null, the credit applies at header level.
  • SALESREP_ID — Identifier of the salesperson receiving credit.
  • PERCENT — Percentage of the associated amount allocated to that salesperson.
  • SALES_CREDIT_TYPE_ID — References the sales credit type, distinguishing roles such as quota or non-quota credit.
  • ORIG_SYS_CREDIT_REF — Reference to the originating system's credit record, supporting external or legacy integration.
  • DW_UPDATE_ADVICE_FLAG, WH_UPDATE_DATE — Warehouse/update-advice control columns used by data-warehouse extraction.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns.
  • CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segment columns.

Common Use Cases and Queries

Typical scenarios include determining the sales representatives credited on an order, computing quota-eligible credit splits, extracting credit data to a warehouse, and validating credit allocation during order import or integration.

Retrieve all credits for a given order header:

SELECT sales_credit_id, header_id, line_id, salesrep_id, percent
FROM   aso_i_oe_sales_credits_v
WHERE  header_id = :p_header_id;

Summarise credit allocation per salesperson across an order:

SELECT salesrep_id, SUM(percent) total_percent
FROM   aso_i_oe_sales_credits_v
WHERE  header_id = :p_header_id
GROUP  BY salesrep_id;

Extract line-level credits assigned to a specific sales representative:

SELECT header_id, line_id, percent, sales_credit_type_id
FROM   aso_i_oe_sales_credits_v
WHERE  salesrep_id = :p_salesrep_id
AND    line_id IS NOT NULL;

Because the view performs no filtering, all predicates, joins to order headers, lines, or salesperson tables, and multi-org restrictions must be supplied by the calling query. This keeps the object lightweight and predictable for both interactive reporting and bulk integration processing.