Search Results update_line_operation

Overview

WIP_SFCB_UTILITIES is a PL/SQL package owned by the APPS schema that supports Oracle EBS Work in Process shop floor control and flow manufacturing reporting. Rather than exposing a public API for transaction entry, the package functions primarily as an internal helper library: its procedures and functions compute the derived values — efficiency, utilization, productivity, resource load, and line load — that drive the Flow Manufacturing and shop floor scheduling views. Because several of these views (WIP_FLOW_ASSEMBLIES_V, WIP_FLOW_LINE_LINEARITY_V, WIP_FLOW_MIX_LINEARITY_V, WIP_OPEN_FLOW_SCHEDULES_V, and their PCB counterparts) reference the package directly in their SQL definitions, WIP_SFCB_UTILITIES is embedded in the query path of flow schedule inquiry and reporting rather than being invoked explicitly by end users. The package is classified as OTHER in ETRM, reflecting that it is not a formally published open interface.

Key Procedures and Functions

The documented interface comprises thirty-one procedures and functions, which fall into several functional groups:

• Metric computation: POPULATE_EFFICIENCY, POPULATE_UTILIZATION, POPULATE_PRODUCTIVITY, POPULATE_RESOURCE_LOAD, and POPULATE_LINE_LOAD calculate and populate performance and capacity metrics for a reporting context.
• Line and schedule context: SET_ORGANIZATION, SET_LINE, GET_ORGANIZATION, and GET_LINE establish or return the current organization and flow line under evaluation; SET_LINEARITY_DATES, GET_LINEARITY_FROM_DATE, and GET_LINEARITY_TO_DATE manage the date window used for linearity calculations; DISPLAYDATE_TO_DISPLAYDT performs date presentation conversion.
• Routing and operation analysis: GET_ALL_LINE_OPS, CHECK_LAST_LINE_OP, LINE_OP_IS_PENDING, UPDATE_LINE_OPERATION, and POPULATE_LINE_RESOURCE_LOAD interrogate operational routings and resource assignments to determine line operation status and loading.
• Resource and calendar calculation: RESOURCE_TXN and GET_WORKDAY_FACTOR derive resource transaction data and the working-day factor used in capacity and linearity math.

Parameter lists are not documented in the ETRM metadata and therefore are not reproduced here; consumers should treat these routines as internal and validate signatures against the deployed package before calling them from custom code.

Tables Accessed

The package reads and writes through APPS synonyms. Work definition data comes from BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_OPERATION_RESOURCES, BOM_RESOURCES, BOM_STANDARD_OPERATIONS, and BOM_DEPARTMENTS. Capacity and scheduling data is drawn from BOM_CALENDAR_DATES and MRP_NET_RESOURCE_AVAIL, the latter supplying net resource availability used in load computations. Flow and discrete execution data comes from WIP_FLOW_SCHEDULES, WIP_DISCRETE_JOBS, and WIP_LINES. Organization defaults are obtained from MTL_PARAMETERS, deliverables from OKE_K_DELIVERABLES_B, and intermediate metric results are staged in WIP_INDICATORS_TEMP and WIP_INDICATORS_TEMP_S.

Usage Notes

WIP_SFCB_UTILITIES is referenced by seven other packages and by the flow scheduling views listed in the dependency information, and in turn it depends only on SYS.STANDARD. This places it low in the call stack, suitable for invocation from view SQL and from callers such as WPS_GANTT_UTILITIES that render Gantt and shop floor scheduling displays. It is not intended for direct invocation from Oracle Forms or concurrent programs in a supported customization. When extending flow manufacturing reporting, the recommended approach is to query the dependent views rather than call package routines directly, since internal signatures and the temp indicator tables may change between releases.