Results for “rejected_update_status”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.AHL_GENERIC_APRV_PVT is a private PL/SQL package body within the Oracle E-Business Suite Advanced Product Catalog (AHL) application. It implements the generic approval workflow engine that governs approval routing, notification, and status transitions for AHL business objects. The package encapsulates the Workflow-backed approval logic surfaced through the AHL approval framework, starting Oracle Workflow processes, tracking approver responses, and applying resulting status changes to the underlying objects.
Because the package is classified as PVT (private), it is not a supported public API. It is intended for internal consumption by other AHL packages and the approval framework, and it is documented as being referenced by twenty-two other packages. Customers and integrators should treat it as an implementation detail rather than a callable interface, and should not bind directly to its procedures.
Key Procedures and Functions
The package exposes twenty documented procedures and functions. The workflow lifecycle is driven primarily by START_WF_PROCESS, which launches the Workflow process for a given object, activity, approval type, and object version. SET_ACTIVITY_DETAILS and PREPARE_DOC supply the Workflow item attributes, while SET_APPROVER_DETAILS and SET_FURTHER_APPROVAL maintain approver assignments and multi-stage routing.
Notification handlers deliver the messages generated during approval: NTF_APPROVAL, NTF_APPROVAL_REMINDER, NTF_FORWARD_FYI, NTF_APPROVED_FYI, NTF_REJECTED_FYI, NTF_FINAL_APPROVAL_FYI, and NTF_ERROR_ACT. Status management is handled by UPDATE_STATUS, REVERT_STATUS, APPROVED_UPDATE_STATUS, and REJECTED_UPDATE_STATUS, which persist the outcome of an approval decision.
Inquiry and resolution procedures include GET_APPROVAL_DETAILS, GET_APPROVER_INFO, GET_API_NAME, and HANDLE_ERROR. GET_API_NAME, the term referenced in the user search, is the documented internal helper that returns the name of the API associated with a given approval context or object. The remaining procedures, including GET_USER_ROLE, CHECK_APPROVAL_REQUIRED, and CHECK_APPL_USG_CODE, support role resolution and approval-required determination.
Tables Accessed
The package operates against five tables through APPS synonyms:
- AHL_APPROVAL_API — resolves approval API definitions used when applying decisions.
- AHL_APPROVAL_RULES_B — determines whether approval is required and at which sequence stage.
- AHL_APPROVERS — stores approver assignments and related details.
- JTF_RS_ROLES_B and JTF_RS_ROLE_RELATIONS — resolve the resource role and reporting hierarchy used for approver determination.
These tables supply the routing data that the Workflow process consumes, and the package reads them to build notifications and to validate approval requirements.
Usage Notes
AHL_GENERIC_APRV_PVT is invoked when an AHL business object enters an approval-required lifecycle state. Oracle Forms or the AHL approval framework call the package to start the Workflow process, generate notifications, and apply approved or rejected status updates. It is not registered as a concurrent program interface and is not intended for direct invocation from custom code. Because it is a private package with no documented public contract, any dependency on its procedures carries upgrade risk; customizations should instead use the supported AHL public APIs that this package backs.