Search Results bmgtstdop_get_stdop

Overview

BOMPASGR is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Oracle Bills of Material routing interface process. Its core purpose is to assign routing data from the BOM open interface tables into the permanent routing definition tables maintained by the Bills of Material module. The package header comment explicitly describes it as containing "functions used to assign routing data in the interface tables," confirming its role as the validation-and-transfer engine that converts staged interface records into live manufacturing routing entities.

The package is classified under ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API, meaning it is an internal, non-public interface rather than a formally published open API. It declares AUTHID CURRENT_USER, so it executes with the privileges of the invoking user. Each function accepts organization-scoped parameters (org_id, all_org) plus a standard concurrent-program context (prog_appid, prog_id, req_id, user_id, login_id), which is characteristic of logic invoked from concurrent managers during the routing interface import.

Key Procedures and Functions

The 13 documented routines fall into two functional groups:

• Assignment routines that transfer interface records into the routing schema: BMARTORG_ASSIGN_RTG_ORGID, BMASRREV_ASSIGN_RTG_REVISION, BMPRTGH_ASSIGN_RTG_HEADER, BMASOPD_ASSIGN_OPERATION_DATA, BMASRSD_ASSIGN_RESOURCE_DATA, BMASOPID_ASSIGN_OP_SEQ_ID, BMASRTGID_ASSIGN_RTG_SEQ_ID, and BMASRITM_ASSIGN_RTG_ITEM_ID. These resolve and stamp the organization, revision, header, operation, resource, sequence, and item identifiers required to create valid routing and operation-sequence records.
• Lookup/inquiry routines that supply reference values during import: BMGRTSQ_GET_ROUTING_SEQUENCE, BMGOPSQ_GET_OP_SEQUENCE, BMGRTIN_GET_RTG_INFO, BMGTDEP_GET_DEPARTMENT, and BMGTSTDOP_GET_STDOP. These retrieve routing sequences, operation sequences, routing details, department information, and standard operation definitions.

Each assignment function returns an INTEGER status code and an err_text output parameter for error reporting, allowing the calling concurrent program to aggregate validation failures.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• Interface staging tables: BOM_OP_ROUTINGS_INTERFACE, BOM_OP_SEQUENCES_INTERFACE, and BOM_OP_RESOURCES_INTERFACE — the source records populated by the user or feeder program.
• Permanent routing tables: BOM_OPERATIONAL_ROUTINGS and BOM_OPERATIONAL_ROUTINGS_S, BOM_OPERATION_SEQUENCES and BOM_OPERATION_SEQUENCES_S (the _S variants hold descriptive/translated columns).
• Reference and setup tables: BOM_DEPARTMENTS, BOM_DEPARTMENT_RESOURCES, BOM_RESOURCES, BOM_STANDARD_OPERATIONS, BOM_STD_OP_RESOURCES, and MTL_RTG_ITEM_REVISIONS.
• Supporting tables: CST_ACTIVITIES and MTL_PARAMETERS (organization parameters).

Usage Notes

BOMPASGR is an internal helper package. It is not intended to be called directly by customers or custom code; it is invoked by the Bills of Material routing open-interface concurrent program, which reads staged rows, calls the lookup functions to resolve and validate reference data, then calls the assignment functions to persist routing headers, operation sequences, and resources. The all_org parameter (1 = all orgs, 2 = only the specified org) controls whether processing spans multiple organizations or is restricted to one, consistent with multi-org routing import behavior in EBS 12.1.1 and 12.2.2. One other package references BOMPASGR, reinforcing its role as a dependent utility rather than an entry point. Because it is not a documented public API, custom integrations should use the standard Bills of Material routing open interface instead of calling these routines directly to preserve upgrade safety.