Results for “inv_organizations”

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

Overview

GMP_BOM_ROUTING_PKG is an Oracle Process Manufacturing (OPM) package in the APPS schema that supports the transfer of OPM formula (bill of material) and routing data to the Advanced Planning and Scheduling (APS) supply chain planning schema. In Release 12, the OPM warehouse concept was removed as part of the convergence of OPM and discrete manufacturing, so the package populates planning staging structures rather than a native OPM warehouse. The transfer proceeds in two phases. The first phase, driven by the extract_effectivities procedure, retrieves OPM formulation data into PL/SQL tables and collections, storing each formula or routing only once and linking effectivities to those records to minimise memory consumption. The second phase exports the gathered data into the APS tables. The package therefore acts as the integration bridge between the OPM formulation and routing tables and the APS/planning staging tables.

Key Procedures and Functions

The 35 documented procedures and functions cluster into distinct functional groups.

• Extraction and export: extract_effectivities orchestrates the two-phase transfer. export_effectivities writes the collected data to the APS tables. write_process_effectivity, write_bom_components, write_routing, and write_routing_operations perform the individual staging-table writes for effectivities, BOM components, routings, and routing operations respectively.
• Validation: check_formula, check_formula_for_organization, validate_formula, validate_formula_for_orgn, and validate_routing confirm that formulas and routings are valid and usable within the relevant organisation before transfer. invalidate_rtg_all_org invalidates routing data across organisations.
• Linking and searching: link_routing and link_override_routing establish routing associations. bsearch_routing and bsearch_setupid provide binary-search lookups over in-memory routing and setup identifier structures. search_operation_leadtime retrieves operation lead-time information.
• Diagnostics and utility: time_stamp, log_message, and gmp_debug_message support tracing and debugging of the extraction run.

Parameter lists are not disclosed in the documented metadata; the above describes purpose only.

Tables Accessed

The package reads source OPM definition data and writes planning staging data. Source tables include GMD_OPERATIONS and GMP_SEQUENCE_TYPES for operation and sequence definitions, and IC_ITEM_MST for item master validation. The staging targets are the MSC_ST_* tables: MSC_ST_BOMS, MSC_ST_BOM_COMPONENTS, MSC_ST_ROUTINGS, MSC_ST_ROUTING_OPERATIONS, MSC_ST_OPERATION_COMPONENTS, MSC_ST_OPERATION_NETWORKS, MSC_ST_OPERATION_RESOURCES, MSC_ST_OPERATION_RESOURCE_SEQS, and MSC_ST_PROCESS_EFFECTIVITY. Configuration and session context are supplied by MSC_APPS_INSTANCES, AD_APPLIED_PATCHES, and DBMS_SESSION.

Usage Notes

Because the user search term was "inv_organizations", it is relevant that the package resolves inventory organisation context through effectivity organisation fields and the APS staging structures rather than through a direct INV_ORGANIZATIONS dependency; organisation-level validation is handled by check_formula_for_organization and validate_formula_for_orgn. The package is referenced by three other packages and is typically invoked from the OPM-to-APS planning data collection flow, often through concurrent programs that stage OPM effectivities for APS consumption. Custom code should call extract_effectivities as the entry point rather than the lower-level write_* procedures, and should ensure that valid formulas and routings exist for the target organisations before execution.