Results for “effective_date”

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

Overview

WSMPUTIL (source file WSMUTILS.pls, version 120.1.12010000.3) is a shared utility package owned by APPS that underpins Oracle EBS Work in Process and Bills of Material routing logic, with particular emphasis on the Oracle Enterprise Asset Management (eAM) / Shop Floor Manufacturing (WSM) family of modules. The package is classified under ETRM as "OTHER" rather than as a published open interface, which reflects its role as an internal helper library rather than a formalized API surface. Its procedures and functions resolve routing start and end points, evaluate operation effectiveness, validate co-product and by-product relationships, determine default accounting classes and completion subinventories, and expose a number of override hooks (marked "overridden" in the header) that WSM consumers replace to suit specific manufacturing environments.

Key Procedures and Functions

The documented surface contains 64 procedures and functions. The most frequently referenced include:

• CHECK_WSM_ORG and CHECK_IF_ORG_IS_VALID — confirm that a given organization is enabled for WSM processing and is a valid inventory/ manufacturing organization.
• FIND_ROUTING_START, FIND_ROUTING_END, GET_ROUTING_START, GET_ROUTING_END, and FIND_COMMON_ROUTING — overridable routines that determine the effective start and end operations of a routing and identify shared routing segments.
• GET_SCHEDULED_DATE — returns the scheduled date for an operation, honoring the manufacturing calendar.
• GET_DEF_ACCT_CLASS_CODE — supplies the default WIP accounting class code.
• GET_DEFAULT_SUB_LOC and UPDATE_SUB_LOC — retrieve and maintain default subinventory locations for completion and component transactions.
• GET_DEF_COMPLETION_SUB_DTLS — returns default completion subinventory detail; documented as overridden.
• PRIMARY_LOOP_TEST — detects primary routing loops.
• CHECK_COPROD_RELATION, CHECK_COPROD_COMP_RELATION, and CHECK_100_PERCENT — validate co-product and by-product relationships and confirm that yield allocations reconcile to 100 percent.
• AUTONOMOUS_TXN — commits a transaction in an autonomous transaction context.
• OPERATION_IS_STANDARD_REPEATS and VALIDATE_NON_STD_REFERENCES — overridable validation of standard operation repetition and non-standard operation references.
• WSM_ESA_ENABLED and WSM_CHANGE_ESA_FLAG — read and toggle the Enterprise Scheduling and Allocation flag.

Additional helpers such as OPERATION_IS_STANDARD_REPEATS, NETWORK_WITH_DISABLED_OP, EFFECTIVE_NEXT_OP_EXISTS, REPLACEMENT_OP_SEQ_ID, and the CHECK_WMTI / CHECK_WSMT / CHECK_WSMTI family perform related network and work-order validations; the metadata lists their names without parameter signatures, so callers should reference the installed package specification.

Tables Accessed

WSMPUTIL reads and writes through APPS synonyms. Routing and operation data is drawn from BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_NETWORKS, BOM_OPERATION_SEQUENCES, BOM_OPERATION_RESOURCES, BOM_STANDARD_OPERATIONS, and BOM_STD_OP_RESOURCES. Calendar-based scheduling uses BOM_CALENDAR_DATES. Inventory and item data is sourced from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_PARAMETERS, and MTL_SECONDARY_INVENTORIES. Transaction and costing references include MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_TEMP, WIP_ACCOUNTING_CLASSES, and WIP_COST_TXN_INTERFACE. Writes typically target interface and staging tables (notably the WIP accounting interface and temporary material transaction structures) rather than the live transaction tables.

Usage Notes

WSMPUTIL is an internal dependency: the metadata records that it is referenced by 28 other packages. It is invoked indirectly through WSM/ eAM forms, shop-floor transactions, and WIP completion processes rather than being called directly from end-user screens. Because several routines are explicitly documented as "overridden," implementers should be aware that behavior may be replaced by customer-specific extensions; any custom code calling WSMPUTIL must account for that variability. Direct invocation should be limited to controlled customizations, ideally after reviewing the installed package specification, since the public parameter signatures are not enumerated in the ETRM extract and the package falls outside the supported open-interface set.