Results for “status_ind”

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

Overview

OP_PRSL_AUD is a table owned by the GML schema (Process Manufacturing Logistics) within Oracle E-Business Suite. The ETRM documentation notes explicitly that this table is not used in 11i, meaning its functionality is specific to the 12.1.1 and 12.2.2 release streams where the Process Manufacturing Logistics pricing and presales audit model was introduced or extended. The table appears to serve as an audit or change-history store for presales order line pricing recommendations, capturing the lineage of price reason changes applied to presales order lines.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. Because no inbound or outbound FK relationships were detected, the object is best modeled as an isolated satellite-like structure rather than a conformed hub or link. Its three unique indexes — OP_PRSL_AUDI1, OP_PRSL_AUD_PK, and OP_PRSL_AUD_UK — suggest a composite business key formed around CHANGEPRSL_ID, CHANGEPRSL_LINE_ID, and PRESALES_ORDLINE_ID, indicating that audit records are keyed by both the change event and the presales line it affects.

Key Information Stored

The 27 documented columns describe a pricing-change audit record. The most significant are:

• CHANGEPRSL_ID — the change header identifier; the single-column unique index OP_PRSL_AUDI1 is built on this column.
• CHANGEPRSL_LINE_ID — the change line identifier returned by the user's search term; the OP_PRSL_AUD_PK unique index is defined on it, making it the closest candidate for a surrogate row key.
• PRESALES_ORDLINE_ID — the presales order line affected; combined with CHANGEPRSL_ID in the OP_PRSL_AUD_UK business-key candidate.
• PRICEREAS_CODE — the price reason code driving the change.
• NET_PRICE — the resulting net price after the change.
• CHANGE_COMMENT — free-text justification or note attached to the change.
• ORDER_QTY1, ORDER_UM1 — ordered quantity and unit of measure in the primary UOM.
• BSO_MINTOTALQTY1, BSO_MAXTOTALQTY1, BSO_MINTOTALVALUE, BSO_MAXTOTALVALUE — buy-side offer quantity and value boundaries that constrain the pricing.
• AVAILABILITY_LEADTIME, TRANSIT_LEADTIME — scheduling lead times referenced when the price change was evaluated.
• QC_GRADE_WANTED, SHIPPER_CODE, SHIPCUST_ID, SHIPADDR_ID, TO_WHSE, FROM_WHSE — sourcing and quality context for the affected line.
• STATUS_IND — status flag for the audit row.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and DELETE_MARK support audit tracking and logical deletion.

Common Use Cases and Queries

Because the table records pricing change history, typical reporting revolves around reconstructing why a presales line's price changed. A representative query traces a single change line:

• SELECT CHANGEPRSL_ID, CHANGEPRSL_LINE_ID, PRESALES_ORDLINE_ID, PRICEREAS_CODE, NET_PRICE, CHANGE_COMMENT FROM GML.OP_PRSL_AUD WHERE CHANGEPRSL_LINE_ID = :line_id;
• SELECT * FROM GML.OP_PRSL_AUD WHERE PRESALES_ORDLINE_ID = :ordline AND CHANGEPRSL_ID = :chgid; — uses the OP_PRSL_AUD_UK business key.
• Aggregate reporting by PRICEREAS_CODE to analyse price-reason frequency, or by SHIPCUST_ID and TO_WHSE to profile change behaviour across customers and warehouses.
• Audit extraction filtering on CREATION_DATE / LAST_UPDATE_DATE windows, and excluding logically deleted rows via DELETE_MARK = 0.

Related Objects

The metadata identifies no enforced foreign keys; the classification is standalone. Nonetheless, the columns imply functional joins to the following objects:

• Presales order line tables in GML, joined via PRESALES_ORDLINE_ID.
• Price reason / change reason setup referenced by PRICEREAS_CODE.
• Customer and address entities via SHIPCUST_ID and SHIPADDR_ID.
• Warehouse/inventory organization tables via TO_WHSE and FROM_WHSE.
• Unit of measure definitions via ORDER_UM1.
• Shipper/carrier definitions via SHIPPER_CODE.

Because no FK columns are formally documented, joins should be validated against the actual ETRM dictionary before being embedded in reports or interfaces.