Search Results get_uncommitted

Overview

MSC_X_PEGGING_FUNC is an Oracle Advanced Supply Chain Planning (ASCP) PL/SQL package owned by the APPS schema. It supplies pegging-related calculation and display logic used by the planning engine and its diagnostic user interfaces. Pegging in Oracle EBS establishes the vertical dependency chain that links a demand (typically a sales order or forecast) to its supplying sources, such as on-hand inventory, work orders, purchase orders, and internal requisitions. The package exposes scalar functions that, given a transaction identifier (arg_transid), return derived attributes of the pegged record, including receipt timing, lateness, quantity breakdowns, child relationships, and exception status.

The header comment identifies the source file as MSCXPEGS.pls, version 120.1, last modified June 7, 2005 — a lineage that underscores the package's stability across the 12.1.1 and 12.2.2 releases. The functions are designed for row-level, single-transaction evaluation and are therefore well suited to form-level field derivations, reports, and custom diagnostic queries rather than set-based batch processing.

Key Procedures and Functions

The package exposes twenty documented functions, all returning scalar values:

• GET_RECEIPT_DATE — returns the DATE on which the pegged supply is expected to be received, based on the supply transaction.
• GET_DAYS_LATE — returns the NUMBER of days by which the supply is late relative to its demand.
• GET_MAX_LATE — returns the NUMBER representing the maximum lateness across the pegged chain.
• GET_QTY_ONTIME — returns the quantity portion arriving on time.
• GET_QTY_LATE — returns the quantity portion arriving late.
• GET_INTRANSIT — returns the in-transit quantity for the pegged supply.
• GET_UNCOMMITTED — returns the uncommitted quantity associated with the transaction.
• GET_CHILD_NUM — returns the child (dependent) number identifying the downstream node in the pegging hierarchy.
• GET_TRANSIDS — returns a VARCHAR2 string containing related transaction identifiers, optionally filtered by a binder value.
• GET_IMMEDIATE_PO — returns the immediate purchase-order reference for the transaction, qualified by order type.
• GET_DATE_EXCEP — returns a VARCHAR2 describing the date exception for the pegged record.
• GET_DATE_EXCEP_SHORT — returns a condensed VARCHAR2 form of the date exception.
• GET_DISPLAY_DATE — returns a DATE formatted for display at a specified position in the visual pegging list.
• GET_GRAPH_VALUE — returns a VARCHAR2 value used to populate the graphical pegging chart at a given position and field.
• GET_SCHEDULED_QTY — returns the scheduled quantity as a VARCHAR2.
• GET_EXCEP — returns a VARCHAR2 exception description qualified by order type, exception order, and exception type.
• GET_STATUS — returns a VARCHAR2 status indicator for the pegged transaction.

Only GET_RECEIPT_DATE is explicitly singled out by the user's search; it is central to lateness and on-time analysis.

Tables Accessed

Two tables are referenced through APPS synonyms. MSC_SUP_DEM_ENTRIES is the primary supply/demand detail table in the ASCP schema; the functions query it to resolve quantities, dates, and exception flags for a given transaction. PLITBLM is a legacy PL/SQL table structure used here as an internal lookup or temporary storage mechanism supporting the pegging computations. No other tables are documented.

Usage Notes

MSC_X_PEGGING_FUNC is not documented as referenced by other packages, indicating it is consumed by external callers rather than internal ASCP code. Typical invocation paths include the ASCP pegging and exception diagnostic forms, concurrent programs that render pegging reports and exception summaries, and custom extensions or SQL reports that need transaction-level pegging attributes. The functions are designed for single-row calls and should not be used within high-volume set-based SQL without performance evaluation. Because the package is not a public open interface, customizations should treat its signatures as internal and validate behavior after upgrades between 12.1.1 and 12.2.2.