Search Results convert_comop_to_rtgop




Overview
Explore in AI Chat

Overview

APPS.BOM_RTG_PUB is a public PL/SQL package in Oracle E-Business Suite that provides the programmatic interface for converting between Routing business object entities and Engineering Change Order (ECO) business object entities within Oracle Bills of Material and Oracle Engineering. The package body (BOMBRTGB.pls) was created to support the integration of routing structures with the ECO framework, allowing routing and routing resource definitions to be represented as engineering change artifacts and, conversely, allowing approved engineering changes to be applied back to routings.

The header comment documents two primary conversion flows: conversion from Routing BO Entity to ECO BO Entity, and conversion from ECO BO Entity to Routing BO Entity. Because the record structures defined for ECO operations and routing operations differ, the package performs conversion on a field-by-field basis rather than by direct record assignment. This design isolates the mapping logic in a single maintained API surface, ensuring that engineering changes can be created or applied consistently without exposing callers to the underlying column-level differences between the two entity models.

Key Procedures and Functions

  • CONVERT_RTGOP_TO_COMOP — Converts a routing operation entity into the common operation entity. The header comment states that the procedure copies values from the routing operation exposed and unexposed records into the common operation records on a field-by-field basis. For example, Organization_Code and Assembly_Item_Name are mapped to the corresponding common operation fields, while ECO-specific attributes such as Eco_Name are initialized to NULL.
  • CONVERT_COMOP_TO_RTGOP — Performs the reverse mapping, translating the common operation entity back into the routing operation exposed and unexposed record structures.
  • CONVERT_ECOOP_TO_COMOP — Converts an ECO operation entity into the common operation entity, providing the ECO-side counterpart to the routing operation conversion.
  • CONVERT_COMOP_TO_ECOOP — Converts the common operation entity into an ECO operation entity.
  • CONVERT_RTGRES_TO_ECORES — Converts routing resource entity data into ECO resource entity data. This is the counterpart procedure to the one referenced in the user's search and supports the routing-to-ECO direction of the resource conversion.
  • CONVERT_ECORES_TO_RTGRES — Converts ECO resource entity data into routing resource entity data. This is the procedure most directly associated with the search term "convert_ecores_to_rtgres," and it is invoked when engineering change resource information must be reflected back onto the routing resource structure.
  • CONVERT_RTGSUBRES_TO_ECOSUBRES — Converts routing sub-resource entity data into ECO sub-resource entity data.
  • CONVERT_ECOSUBRES_TO_RTGSUBRES — Converts ECO sub-resource entity data into routing sub-resource entity data, completing the sub-resource pair of conversion procedures.
  • PROCESS_RTG — The primary processing driver of the package, orchestrating the conversion routines against routing data rather than acting as a simple field mapper.

Tables Accessed

The documented metadata identifies PLITBLM as a referenced table via APPS synonyms. PLITBLM is the standard Oracle EBS table used to store translated or descriptive text segments associated with structured entities, and its presence indicates that the package may resolve or persist textual descriptions during conversion processing. The package is referenced by 51 other packages, confirming that it occupies a central position in the routing and ECO conversion call graph; dependent packages rely on it as the authoritative conversion layer rather than re-implementing field mapping independently.

Usage Notes

BOM_RTG_PUB is classified as a PUB (public) API in the ETRM repository, indicating that it is a supported interface intended for external invocation rather than a private implementation detail. In Oracle EBS 12.1.1 and 12.2.2, it is typically invoked from Oracle Engineering and Oracle Bills of Material forms, from concurrent programs that create or apply engineering change orders affecting routings, and from custom extensions that need to synchronize routing operations, resources, and sub-resources with ECO entities. Because conversion is performed field by field, callers must supply fully populated exposed and unexposed record structures for the source entity and provide the corresponding target record structures for output. The presence of IN OUT NOCOPY parameters in the conversion procedures supports in-place modification of the common operation records, which is efficient for high-volume processing. Custom code should call the package through its published specification and avoid direct manipulation of the underlying routing and ECO tables to preserve data integrity and upgrade safety.