Results for “phase_change_flag”

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

Overview

OE_ORD_SAL_CRDT_HIST_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ONT (Order Management) product family. Its purpose is to expose the header-level audit history of sales credit assignments applied to order headers. The view flattens the historical record of changes made to sales credit allocations so that reporting tools, concurrent programs, and integration layers can query a stable, denormalized projection without directly joining the underlying transactional tables.

The view carries status VALID in the ETRM dictionary for 12.1.1 and 12.2.2. Because it is a view rather than a table, it introduces no storage of its own and always reflects the current committed state of the base rows at query time. This makes it suitable for audit reporting, credit reallocation analysis, and reconciliation of salesperson compensation against order activity.

Underlying Base Objects

The documented view text joins two base objects through APPS synonyms:

• OE_SALES_CREDIT_HISTORY (OSCH) — the history table that stores each version of a sales credit record, including the audit, version, and phase-change indicators that drive historical analysis.
• OE_ORDER_HEADERS_ALL (OH) — the order header table supplying header context such as order number, order type, and the sold-to organization.

The join is OH.HEADER_ID = OSCH.HEADER_ID, constrained by the predicate OSCH.LINE_ID IS NULL. That predicate is significant: it restricts the result set to sales credits attached at the header level, excluding line-level credit history. Consumers seeking line-level history must query the history table directly or use a corresponding line-level view.

Key Columns

• HEADER_ID — foreign key to the order header; the primary correlation point with OE_ORDER_HEADERS_ALL.
• ORDER_NUMBER, ORDER_TYPE_ID, SOLD_TO_ORG_ID — order identification and customer context inherited from the header table.
• SALES_CREDIT_ID — identifies the sales credit assignment being versioned.
• SALESREP_ID, PERCENT, SALES_CREDIT_TYPE_ID — the salesperson, quota percentage, and credit type for each historical version.
• HIST_TYPE_CODE, REASON_CODE, REASON_ID, HIST_COMMENTS — the classification, reason, and free-text commentary describing why the credit record changed.
• HIST_CREATED_BY, RESPONSIBILITY_ID, HIST_CREATION_DATE — the user, responsibility, and timestamp of the historical action.
• AUDIT_FLAG — the column targeted by the searched term; indicates whether the historical row was produced by an audited change, allowing filtering of genuine audit-driven records.
• VERSION_FLAG, VERSION_NUMBER, PHASE_CHANGE_FLAG — versioning metadata distinguishing the current record from prior versions and phase-driven transitions.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO columns for row-level traceability.

Common Use Cases and Queries

Typical scenarios include auditing sales credit changes on a given order, reconstructing the sequence of salesperson percentage changes, and isolating records flagged for audit review. A representative query filtering on the audit indicator is:

SELECT order_number, salesrep_id, percent, hist_type_code, reason_code, audit_flag, version_number, hist_creation_date FROM oe_ord_sal_crdt_hist_v WHERE audit_flag = 'Y' AND order_number = :p_order_number ORDER BY hist_creation_date;

For version tracking on a single credit assignment:

SELECT sales_credit_id, version_number, version_flag, percent, last_update_date FROM oe_ord_sal_crdt_hist_v WHERE header_id = :p_header_id ORDER BY version_number;

Because the view enforces LINE_ID IS NULL, it should be treated strictly as a header-level audit source. Performance depends on the indexes supporting OE_SALES_CREDIT_HISTORY and OE_ORDER_HEADERS_ALL, so queries should always constrain HEADER_ID or ORDER_NUMBER where possible.