Results for “create_routing_history_bp”

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

Overview

PQH_ROUTING_HISTORY_API is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as an API. It belongs to the Public Sector/Public Sector Human Resources (PQH) product family and supports the routing history infrastructure used by the Oracle Approval Management and routing engine. Within Oracle EBS, approval routing records the path that a transaction — such as a position, assignment, or requisition change — travels through a defined hierarchy of approvers. This package provides the programmatic interface for creating, maintaining, and removing those routing history records and their associated attribute rows. The package is documented as VALID in ETRM for both 12.1.1 and 12.2.2, and it is classified as an API, meaning it is intended for controlled use by other application modules and by customer extensions rather than as an internal utility. It is a dependency of PQH_WF, the workflow integration package for the PQH product, which confirms its role in supporting approval workflow processing.

Key Procedures and Functions

The ETRM metadata documents four callable program units within this package:

• CREATE_ROUTING_HISTORY — Inserts a new routing history record, establishing the linkage between a routed transaction and the history it generates during the approval process.
• CREATE_ROUTING_HISTORY_BP — The business process variant of the create operation, providing the same logical insert behavior with the additional processing conventions Oracle applies to _BP entry points in HR-family APIs (for example, supplemental processing hooks, message handling, or business-group context).
• UPDATE_ROUTING_HISTORY — Modifies an existing routing history record, typically as the routing progresses or as attribute values change.
• DELETE_ROUTING_HISTORY — Removes a routing history record, used when routing data is purged or a routing event is reversed.

No parameter lists are published in the available metadata; callers should obtain exact signatures from the package specification (via the ETRM dependent-code viewer or by describing the package in the database) before coding against it.

Tables Accessed

The package operates against the following documented tables, accessed through APPS synonyms:

• PQH_ROUTING_HISTORY — The primary routing history entity table, holding the header-level routing records created and maintained by the CREATE, UPDATE, and DELETE procedures.
• PQH_ROUTING_HIST_ATTRIBS — The attribute (detail) table that stores qualifying values belonging to each routing history record; it appears both as a referenced table and as a dependency of the package body.
• PLITBLM — The standard Oracle Applications PL/SQL table used by the HR API framework for message/error handling across multi-row DML operations.

The package declares dependencies on HR_API and STANDARD, consistent with APIs built on the Oracle HRMS API framework, which supplies shared validation, message, and error-stack utilities.

Usage Notes

PQH_ROUTING_HISTORY_API is normally invoked indirectly. The workflow package PQH_WF references it, so routing history records are generated and updated automatically as approval workflow activities execute. Direct calls are appropriate when custom code, a concurrent program, or a Forms-based extension must seed or correct routing history outside the standard workflow path. Because this is a documented public API, custom callers should invoke the procedures rather than performing DML against PQH_ROUTING_HISTORY or PQH_ROUTING_HIST_ATTRIBS directly, ensuring that attribute rows, messages, and any framework-side validation remain consistent. The existence of the _BP variant indicates that the business-process entry point should be used where the calling context expects the full API processing model. As with all APPS APIs, callers must adhere to the standard initialization and commit/rollback conventions of the HR API framework, and should review the package body for the precise parameter contracts and validation behavior before deployment in either 12.1.1 or 12.2.2.