Search Results db_flag




Overview
Explore in AI Chat

Overview

APPS.OE_AK_HEADER_SCREDITS_V is an internal Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data container ONT.OE_AK_HEADER_SCREDITS_V. It exposes sales credit assignment data associated with order headers in the Order Management (ONT) application. The view carries a documented status of VALID in Oracle EBS 12.1.1 and 12.2.2. Oracle explicitly marks this object as "Oracle Internal Use Only," meaning it is not supported for direct customer access and is intended to be consumed only by standard Oracle Applications programs. Its presence in the database reflects the historical Oracle Forms-based "AK" (Administrative Knowledge/attribute framework) region constructs, where header-level sales credits are surfaced for display or integration purposes.

The view presents one row per header-level sales credit record, including the salesrep assignment, the percentage or quota credited, the credit type, and the descriptive flexfield context and attribute segments. It is therefore a read-oriented projection that flattens the header sales credit relationship rather than a transactional entity in its own right.

Underlying Base Objects

According to the documented view metadata (ETRM 12.2.2), OE_AK_HEADER_SCREDITS_V is defined over a single referenced base object: OE_SALES_CREDITS, resolved through a synonym in the APPS schema. OE_SALES_CREDITS is the Order Management table that stores sales credit information for both order headers and order lines. The view filters and shapes that table's content so that only header-scoped sales credit rows are presented, adding the attribute and context columns used by the AK framework.

Dependency metadata further records that OE_AK_HEADER_SCREDITS_V is referenced by APPS.OE_5PC1_ORDER_AHL, indicating it participates in internal Order Management form or program logic rather than standalone reporting. Because the view reads directly from OE_SALES_CREDITS, any DML performed against the base table is immediately visible through the view; the view itself is not a materialized snapshot.

Key Columns

  • HEADER_ID – The order header identifier linking the sales credit to a specific order.
  • LINE_ID – Null for header-level credits; distinguishes header credits from line-level counterparts.
  • SALES_CREDIT_ID – Primary identifier of the sales credit record.
  • SALESREP_ID – The sales representative receiving credit.
  • SALES_CREDIT_TYPE_ID – The credit type (for example, quota or non-quota sales credit).
  • PERCENT – The credit percentage allocated to the salesperson.
  • CONTEXT and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield context and segment values associated with the credit record.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns.
  • DB_FLAG, OPERATION, RETURN_STATUS, DW_UPDATE_ADVICE_FLAG – Internal processing flags used by the application and integration logic, notably tied to the attribute framework and downstream update advice processing.
  • WH_UPDATE_DATE – Warehouse update timestamp supporting data extraction and refresh cycles.

The DB_FLAG and OPERATION columns, surfaced by the user's search term, carry internal state used by Oracle's AK processing and are not intended for external reporting semantics.

Common Use Cases and Queries

Because the object is documented as Oracle Internal Use Only, the principal supported use case is indirect: interpretation of internal Order Management form behavior and diagnostics. Customers and integrators who nonetheless query it typically do so for ad hoc analysis of header-level sales credit distribution. A representative query follows:

SELECT header_id
     , salesrep_id
     , sales_credit_type_id
     , percent
FROM   apps.oe_ak_header_scredits_v
WHERE  header_id = :p_header_id;

For integration and reconciliation, the DB_FLAG and RETURN_STATUS columns may be inspected to identify records pending downstream processing, though Oracle does not guarantee their meaning across patches. In practice, organizations seeking supported access to header sales credit data should query OE_SALES_CREDITS directly, applying an appropriate header-versus-line filter, and reserve OE_AK_HEADER_SCREDITS_V for internal troubleshooting where no supported alternative exists.