Search Results valid_locator

Overview

WIP_COMPONENT is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM metadata as an "OTHER" API rather than a formal public interface. It resides in the Work in Process (WIP) module and provides supporting logic for validating and resolving component-level attributes during manufacturing transactions. Its status is VALID in both 12.1.1 and 12.2.2, indicating it is a compiled, active object within the application tier.

The package is not a standalone business API; instead it supplies utility routines consumed by other WIP processing units. Dependency metadata shows that APPS.WIP_COMPONENT references SYS.STANDARD and that it is referenced by the WIP_COMPONENT package and by WIP_POPULATE_TEMP. This confirms its role as a helper layer used during the population and validation of WIP component data prior to transaction processing, such as material issue, backflush, and completion activities.

Key Procedures and Functions

• IS_VALID — Determines whether a component or its supplied attributes constitute a valid entry within the WIP transaction context. It acts as a boolean-style validation gate returning the outcome of the validity test.
• MEETS_CRITERIA — Evaluates whether a given component record satisfies the configured criteria required for it to participate in the transaction being processed. This supports selective inclusion or exclusion of components.
• DETERMINE_TXN_QUANTITY — Derives or computes the transaction quantity applicable to a component, typically used to establish the quantity to be issued, backflushed, or consumed based on the component's setup and demand.
• VALID_LOCATOR — Verifies that a specified locator is valid for the component's inventory organization, including secondary locator considerations where enabled.

Tables Accessed

• MTL_SECONDARY_LOCATORS — Read to resolve and validate secondary locator information, supporting warehouses that use dual-unit locator tracking.
• MTL_SYSTEM_ITEMS — Read to obtain item-level attributes that determine validity, criteria, and quantity behavior for the component.
• DUAL — Referenced for simple single-row evaluations and standard PL/SQL expression checks.

All tables are accessed through APPS synonyms, reflecting standard EBS schema indirection.

Usage Notes

WIP_COMPONENT is an internal support package and is not intended as a public, callable API for customer extensions. It is invoked indirectly by other WIP objects—most notably WIP_COMPONENT itself and WIP_POPULATE_TEMP—during the routine execution of component population and transaction validation logic. Because it is consumed by WIP_POPULATE_TEMP, it is typically reached during the processing that assembles temporary component data ahead of a WIP material transaction.

Customers should treat these routines as private implementation details. Direct calls from custom forms, concurrent programs, or custom PL/SQL are discouraged because signatures and behavior are subject to change across patches and releases without notice. When customization is required, the supported approach is to use documented WIP public APIs (such as the WIP transaction and move APIs) rather than referencing this internal package.