Search Results ret_code

Overview

BOMPAVRT is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Bills of Material (BOM) module and is classified under the ETRM "OTHER" API category, meaning it is not exposed as a formally published public interface. Its stated purpose, per the embedded header comment, is to serve as "the main package used to assign and verify routing data." The package therefore sits in the routing maintenance layer of the manufacturing foundation, coordinating the association of routing records with organizations, revisions, and related attributes.

The header defines a consistent parameter contract used across the package: org_id (organization identifier), all_org (a flag where 1 processes all organizations and 2 processes only the supplied org_id), prog_appid, prog_id, request_id, user_id, and login_id. These are the standard concurrent-program context values used throughout EBS to record WHO columns and support restartability. The documented return contract is equally important to the user searching on "ret_code": functions return 1 on success and SQLCODE on failure, and the err_text OUT parameter carries the failure detail.

Key Procedures and Functions

ETRM documents two public units in this package:

• BMASRTG_ASSIGN_RTG_DATA — the assignment routine. Based on the source excerpt, it is a function returning INTEGER that orchestrates several subordinate steps in sequence. It first calls BOMPASGR.bmartorg_assign_rtg_orgid to associate routing data with the appropriate organization, then calls BOMPASGR.bmasrrev_assign_rtg_revision to assign routing revisions, and continues into further BOMPASGR routines. Each step is checked against ret_code; on a non-zero value the transaction is rolled back, the failing routine name is prefixed to the error message via substrb(err_msg,1,100), and control transfers to an error label. A COMMIT follows each successful step.
• BMVRRTG_VERIFY_RTG_DATA — the verification counterpart. Its naming ("VR" for verify) indicates it validates existing routing data rather than creating it, following the same return convention of 1 for success and SQLCODE for failure.

Tables Accessed

The ETRM metadata records no direct table references for BOMPAVRT through APPS synonyms. All persistence is delegated to the BOMPASGR package, whose routines read and write the BOM routing base tables — principally BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_ROUTING_REVISIONS, and their organization-association counterparts. BOMPAVRT itself acts as the coordination layer: it sequences organization assignment, revision assignment, and validation, and manages transaction boundaries rather than issuing DML directly.

Usage Notes

BOMPAVRT is not referenced by any other documented package (ETRM reports zero referencing packages), which is consistent with an internal utility invoked from the routing concurrent programs and forms of the Bills of Material module. The presence of request_id, prog_appid, and prog_id confirms the intended entry point is a concurrent program launched from the Routing form or the Assign Routing concurrent request. The package predates the modern JAVA/PLSQL API standards — its header carries a 1993 copyright and a 1999 revision stamp — so it should be treated as an internal, version-sensitive interface. Custom code should not call it directly; instead, invoke the supported routing assignment concurrent programs. When diagnosing failures, the returned ret_code and the err_text value, which names the specific BOMPASGR routine that failed, are the primary troubleshooting signals.