Search Results wip_move

Overview

WIP_FLOWRESCHARGE is an Oracle E-Business Suite package owned by APPS that supports flow manufacturing and work-orderless completion transactions. Its principal business function is to calculate and charge resource and overhead costs against a work-in-process transaction generated during flow completion or work orderless completion. The package derives its costing logic from the bills of material definition, ensuring that resource charges and item or lot overheads are applied consistently with the routing, operation sequence, and resource configuration established for the manufactured item.

Because flow manufacturing does not rely on traditional discrete work orders in the same manner, the resource charging logic must be driven directly from the BOM and routing definitions. WIP_FLOWRESCHARGE provides this bridge, applying overhead and resource charges based on the characteristics of each operation sequence and resource rather than on a manually maintained work order routing. This is particularly relevant for users searching on the "wip_move" reference, since the package's autocharge logic includes special handling for resources whose autocharge type is WIP_MOVE.

Key Procedures and Functions

The documented package exposes a single public procedure:

• CHARGE_RESOURCEANDOVERHEAD — The sole documented entry point, this procedure is invoked by flow completion or work orderless completion to charge resources and item/lot overhead. It receives a transaction temporary identifier referencing the record in the material transaction temporary table (MTL_MATERIAL_TRANSACTIONS_TEMP, abbreviated MMTT) and returns a status value indicating the outcome of the charging operation. The procedure encapsulates all of the charging rules documented in the package header, including the treatment of autocharge flags, lot-based charging, manually charged resources, and the distinction between overhead and ordinary resource cost elements.

Tables Accessed

The package reads and writes a defined set of BOM, WIP, and inventory tables, referenced through APPS synonyms:

• BOM_OPERATION_SEQUENCES — Provides the count_point_type that determines whether a resource is auto-charged, not auto-charged, or not directly charged.
• BOM_RESOURCES — Supplies the basis_type (Item, Lot, Resource Unit, Resource Value, Total Value, or Activity) and the cost_element_id used to distinguish material, material overhead, resource, outside processing, and overhead charges.
• BOM_OPERATION_RESOURCES — Supplies the autocharge_type, including the WIP_MOVE value that indicates the standard rate is stored and must be charged even for outside processing resources.
• BOM_OPERATIONAL_ROUTINGS and BOM_DEPARTMENTS — Provide routing and departmental context for the operation being charged.
• MTL_MATERIAL_TRANSACTIONS_TEMP — Holds the temporary transaction record identified by the incoming transaction temporary ID.
• WIP_COST_TXN_INTERFACE — Receives or references the cost transaction interface records produced by the charge operation.
• WIP_FLOW_SCHEDULES — Provides the flow schedule context for the completion event.
• MTL_PARAMETERS — Supplies inventory organization-level parameters consulted during processing.
• PLITBLM — A standard Oracle PL/SQL table type used within the package's internal processing.

Usage Notes

WIP_FLOWRESCHARGE is not intended for direct invocation by end users. It is called internally by flow completion and work orderless completion processing, typically triggered from the relevant WIP transaction forms or from concurrent processing that executes completion logic. The package is also referenced by one other package within the APPS schema, indicating that at least one higher-level program depends on its charging routine.

Custom code integrations should treat CHARGE_RESOURCEANDOVERHEAD as an internal API and invoke it only when replicating flow completion behavior, passing a valid transaction temporary identifier from the MMTT and interpreting the returned status value to detect errors. Because the procedure relies on BOM and routing setup for its charging decisions, correct configuration of count_point_type, basis_type, autocharge_type, and cost_element_id is essential. In particular, resources flagged with the WIP_MOVE autocharge type are still charged even when categorized as outside processing, and manually charged resources are deliberately excluded from automatic charging.