Search Results bmvrrtg_verify_rtg_data

Overview

BOMPAVRT is a public PL/SQL package owned by APPS in the Oracle E-Business Suite environment. Its declared purpose, as recorded in the package header, is to provide functions that validate routing data residing in the Oracle Bills of Material interface tables. Routing information, which defines the sequence of operations performed to manufacture an assembly, is frequently loaded into EBS from external manufacturing, CAD, or legacy systems. Before this data can be applied to the production routing tables, it must be checked for referential and structural integrity. BOMPAVRT centralizes that validation logic so that concurrent processing and programmatic loads share a single, consistent set of rules.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking schema rather than the definer. In practice, this package is most often called from within the APPS schema, where synonyms and grants make the interface and base tables accessible. The parameter conventions documented in the header also reveal the package's integration with the concurrent manager: it accepts organization, program, request, user, and login identifiers, all of which are standard arguments passed by request-driven processing.

Key Procedures and Functions

The documented interface exposes two functions:

• BMASRTG_ASSIGN_RTG_DATA — The assignment routine. Its role is to move validated routing data from the interface tables into the destination routing structures for the specified organization. It participates in the standard two-phase pattern used throughout Oracle manufacturing interfaces: validate first, then assign.
• BMVRRTG_VERIFY_RTG_DATA — The verification routine, which corresponds directly to the user search term bmvrrtg_verify_rtg_data. This function performs the validation of routing data held in the interface tables for a given organization and returns an integer status. An OUT parameter named err_text conveys diagnostic text when validation fails, allowing callers to report specific errors to users or to the concurrent request log.

Both functions accept an all_org flag that controls processing scope: a value of 1 signals that all organizations should be processed, while a value of 2 restricts processing to the single org_id supplied. Neither the verification nor the assignment function is documented as returning a result set; instead they return an integer status code, consistent with Oracle's convention of 0 for success and non-zero for error conditions.

Tables Accessed

The ETRM metadata for this object records no tables referenced through APPS synonyms. This is unsurprising for a validation package of this vintage, because the routing interface routines access the routing interface and base tables dynamically or through unqualified names resolved at runtime under AUTHID CURRENT_USER. Functionally, the package operates against the routing interface tables (the BOM routing interface family) and the production routing tables that receive the assigned data. Because no explicit table list is documented, implementers should determine the precise data footprint by tracing execution in a test instance rather than relying on the package header alone.

Usage Notes

BOMPAVRT is not intended for direct end-user invocation. It is typically called by concurrent programs that load routing data, by forms-based interfaces when a user submits a routing interface request, and by custom PL/SQL code that programmatically loads routings from external systems. The standard invocation sequence is to call BMVRRTG_VERIFY_RTG_DATA first to validate the interface rows, correct any errors reported through err_text, and then call BMASRTG_ASSIGN_RTG_DATA to transfer the rows into the production routing tables.

Because the package is documented as referenced by zero other packages in the ETRM inventory, its callers are expected to be forms, concurrent programs, or custom extensions rather than other shipped PL/SQL APIs. Developers should wrap calls in exception handlers, inspect both the returned integer and the err_text output, and test thoroughly in a non-production instance before using the package to load routing data in a live environment.