Search Results get_current_op_seq_num
Overview
MRP_CL_FUNCTION is a value-added PL/SQL package in the APPS schema that serves as a shared utility library for Oracle EBS planning, costing, and supply-chain modules. Its name reflects its role as a common ("CL" / common library) function repository consumed by Material Requirements Planning (MRP), Advanced Supply Chain Planning (ASCP), and related release and rescheduling programs. Rather than exposing a single business transaction, the package aggregates a wide range of cost retrieval, quantity conversion, operation sequence resolution, and supplier and sourcing lookup routines. The package is classified as OTHER in the ETRM metadata, indicating that it is an internal, non-public API used primarily by Oracle's own seeded programs rather than by external integrations.
The dependency trace confirms that MRP_CL_FUNCTION sits at the center of a set of planning packages: it is referenced by MRP_AP_REL_PLAN_PUB, MRP_CL_REFRESH_SNAPSHOT, MRP_PO_RESCHEDULE, and MSC_SRP_RELEASE, and it calls FND_PROFILE itself. This makes it a foundational helper layer for plan release, snapshot refresh, purchase-order rescheduling, and supplier release scheduling.
Key Procedures and Functions
The ETRM documentation lists 46 documented procedures and functions. The most instructive include:
- APPS_INITIALIZE — Standard APPS schema initialization routine that sets the session context required before other package calls.
- DEFAULT_ABC_ASSIGNMENT_GROUP — Returns the default ABC assignment group used in inventory classification during planning.
- MRP_ITEM_COST, MRP_RESOURCE_COST, MRP_ITEM_LIST_PRICE, MRP_ITEM_SUPP_PRICE — Cost and price retrieval routines that surface item cost, resource cost, list price, and supplier price for planning and sourcing calculations.
- MRP_REV_CUM_YIELD, MRP_REV_CUM_YIELD_UNRELEASED, MRP_JD_REV_CUM_YIELD — Return cumulative yield values used in flow and discrete manufacturing to reflect scrap and yield across operation sequences (including unreleased jobs and JD (job) context).
- MRP_DAY_UOM_QTY, GET_PRIMARY_QUANTITY — Quantity conversion helpers that normalize quantities to the primary unit of measure and to a per-day basis.
- GET_RESOURCE_OVERHEAD — Retrieves resource-level overhead information used in cost rollups.
- GET_CURRENT_OP_SEQ_NUM and its variants (GET_CURRENT_JD_OP_SEQ_NUM, GET_CURRENT_JOB_OP_SEQ_NUM, GET_CURRENT_RTNG_OP_SEQ_NUM) — Resolve the current operation sequence number for a work order, job, or routing, keeping operation sequencing consistent across planning contexts.
- GETWFUSER — Returns the workflow user identity associated with a process.
- GET_ROUTING_SEQ_ID — Returns the routing sequence identifier for a given routing.
- GET_PO_ORIG_NEED_BY_DATE, GET_PO_ORIG_QUANTITY — Return the original need-by date and original quantity on a purchase order line, supporting rescheduling and date-shift analysis.
Tables Accessed
The package reads from a broad set of tables through APPS synonyms. Costing access includes CST_ITEM_COSTS, CST_COST_TYPES, CST_DEPARTMENT_OVERHEADS, and CST_RESOURCE_OVERHEADS. Manufacturing and routing access includes BOM_OPERATION_SEQUENCES, EAM_OP_COMPLETION_TXNS, AHL_WORKORDERS, AHL_WORKORDER_OPERATIONS, and CSI_ITEM_INSTANCES. Sourcing and supplier access includes AP_SUPPLIER_SITES_ALL. Reference data access includes FND_DOCUMENTS_LONG_TEXT, FND_PRODUCT_INSTALLATIONS, FND_RESPONSIBILITY, FND_USER, and HR_ALL_ORGANIZATION_UNITS_TL. Together these tables supply the cost, yield, routing, and identity information the routines return to their callers.
Usage Notes
MRP_CL_FUNCTION is not intended to be called directly by end users. It is invoked internally by seeded planning packages — most notably during plan release (MRP_AP_REL_PLAN_PUB, MSC_SRP_RELEASE), snapshot refresh (MRP_CL_REFRESH_SNAPSHOT), and purchase order rescheduling (MRP_PO_RESCHEDULE). Custom code that needs identical cost, yield, quantity, or operation-sequence logic may call these procedures, but doing so requires the APPS schema context established by APPS_INITIALIZE. Because the package is undocumented as a public API, direct dependencies should be treated as unsupported and validated against both 12.1.1 and 12.2.2 before reuse.