Search Results find_wip_or_inv_spec

Overview

GMD_SPEC_MATCH_MIG_GRP is a group-layer PL/SQL package in the Oracle E-Business Suite Process Manufacturing (OPM) product family. Its business purpose is to provide specification matching services specifically for migration scenarios. Specification matching determines whether an inventory lot, customer order line, WIP entity, or supplier lot satisfies the quality specification defined for a given item, grade, organization, and effective date. The standard Quality Management (QM) matching logic applies a spec_status filter in its WHERE clauses; this migration-specific group layer deliberately removes those spec_status conditions so that legacy or historical specification data can be matched regardless of the specification's current lifecycle status. Apart from that single difference, the matching semantics mirror those used by QM.

The package header carries the source file identifier GMDGSMMS.pls (version 120.0) and records its creation by B. Stone on 13-Oct-2004 under Bug 3934121. The revision history notes that find_location_spec and find_resource_spec were intentionally removed because migration processing does not require them. The type definitions also reflect a production-specific extension: an INVENTORY_SPEC_REC_TYPE record includes a test_id attribute described as supporting a production requirement, passed only by the production team.

Key Procedures and Functions

The ETRM metadata documents eight public program units in the package:

• FIND_INVENTORY_SPEC — Locates the inventory specification applicable to a given item, lot, sublot, organization, warehouse, and effective date, returning the matching specification and result information.
• FIND_CUSTOMER_SPEC — Resolves the customer specification that applies to a sales order line for a specified customer, ship-to site, item, and effective date.
• FIND_CUST_OR_INV_SPEC — Combines customer-oriented and inventory-oriented matching, returning whichever applicable specification is resolved first according to the internal precedence rules.
• FIND_WIP_SPEC — Identifies the WIP (work-in-process) specification relevant to a batch or routing step context.
• FIND_WIP_OR_INV_SPEC — Extends WIP matching by falling back to inventory specification matching when no WIP specification is found.
• FIND_SUPPLIER_SPEC — Returns the supplier specification applicable to a given supplier lot or receipt context; this is the procedure most commonly targeted by searches for supplier specification resolution in migration.
• FIND_SUPPLIER_OR_INV_SPEC — Resolves a supplier specification and, when none applies, falls back to the inventory specification.
• GET_RESULT_MATCH_FOR_SPEC — Given a resolved specification, evaluates the test results and returns the match outcome used by the migration process.

Parameter lists are not reproduced here; callers should consult the package specification in the database. Each routine accepts a typed record (for example INVENTORY_SPEC_REC_TYPE or CUSTOMER_SPEC_REC_TYPE) plus output parameters carrying the matched specification and status.

Tables Accessed

The package operates exclusively against APPS synonyms for OPM and Quality tables. Specification version tables supply the match source data: GMD_INVENTORY_SPEC_VRS, GMD_CUSTOMER_SPEC_VRS, GMD_WIP_SPEC_VRS, and GMD_SUPPLIER_SPEC_VRS. Master specification definitions and test definitions come from GMD_SPECIFICATIONS_B and GMD_SPEC_TESTS_B. Actual analytical values and sample linkage are read from GMD_RESULTS, GMD_SAMPLES, and GMD_SAMPLE_SPEC_DISP. Manufacturing context is retrieved from GMD_RECIPES_B, GMD_ROUTINGS_B, GMD_OPERATIONS_B, GME_BATCH_STEPS, FM_FORM_MST_B, and FM_ROUT_DTL, which support WIP and formula/routing specification resolution. The package is not documented as writing to these tables; its role is read-oriented matching for migration.

Usage Notes

GMD_SPEC_MATCH_MIG_GRP is invoked by migration and conversion routines rather than by interactive forms or standard concurrent programs. ETRM records zero packages referencing it, indicating it is called directly from migration scripts or data-loading utilities, principally during upgrades or legacy data conversions into OPM Quality. Because the spec_status filter is omitted, callers must understand that inactive or historical specifications may be returned; this behavior is intentional for migration but generally unsuitable for transactional, day-to-day quality checks, which should use the standard QM specification matching APIs instead. The package should be treated as a specialized, migration-only utility and used accordingly in custom code.