Search Results update_wf_mapping

Overview

APPS.AHL_WF_MAPPING_PVT is a private PL/SQL API within the Oracle E-Business Suite Advanced Services (Advanced Service Online) module. Its principal business function is to manage Workflow Mapping information, which associates Oracle Workflow process definitions with Approval Objects and Application Usage codes used by Advanced Services Online. The package is declared with AUTHID CURRENT_USER and resides under the APPS schema, exposing a controlled set of procedures and PL/SQL record and table types that model the AHL_WF_MAPPING entity. By centralizing create, update, delete, and validation logic, the package ensures that workflow mapping data consumed by the Advanced Services Online application remains consistent, auditable, and validated against the underlying Workflow definitions.

Workflow mappings are the connective tissue between the service business objects and the Oracle Workflow engine. Because the package is classified as a private API (PVT), it is intended for consumption by other Oracle-developed packages and internal components rather than as a public extension point for customer code. The header history indicates the package was originally created in January 2002, and the current source revision dates from May 2005, confirming its stability across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The ETRM documentation lists seven documented procedures and functions, each serving a specific role in the workflow mapping lifecycle:

• PROCESS_WF_MAPPING — Accepts a table of workflow mapping records (Wf_Mapping_Tbl) and processes them as a unit of work. It acts as the entry point that routes records to the appropriate create, update, or delete logic based on the operation flag carried on each record.
• CREATE_WF_MAPPING — Inserts a new workflow mapping record into the underlying AHL_WF_MAPPING tables, populating the identifying columns such as WF_PROCESS_NAME, WF_DISPLAY_NAME, APPROVAL_OBJECT, ITEM_TYPE, and APPLICATION_USG_CODE.
• UPDATE_WF_MAPPING — Modifies an existing workflow mapping record. This is the procedure referenced by the search term "update_wf_mapping" and is invoked when the attributes of an existing mapping, such as the display name or active flag, must be revised.
• DELETE_WF_MAPPING — Removes a workflow mapping record, logically or physically, from the mapping store.
• VALIDATE_WF_MAPPING — Performs validation of a mapping record prior to persistence, ensuring that required attributes are present and that the referenced workflow definitions are valid.
• CHECK_WF_MAPPING_ITEMS — Verifies the workflow mapping items associated with a record, confirming the integrity of the relationship between the mapping and the underlying Workflow item types.
• COMPLETE_WF_MAPPING_REC — Populates defaulted and derived attributes on a mapping record, completing the record structure so that all mandatory columns are set before DML operations are performed.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

• AHL_WF_MAPPING and AHL_WF_MAPPING_S — the primary table and its corresponding sequence, holding the workflow mapping definitions and generating the WF_MAPPING_ID primary key.
• WF_ACTIVITIES and WF_ACTIVITIES_TL — the Oracle Workflow activity definition tables, consulted to validate and resolve the workflow process names and display names referenced by a mapping.
• DUAL — used for single-row queries, typically for sequence lookups or constant evaluations.
• PLITBLM — the standard PL/SQL indexed table manipulation utility used by the PL/SQL table APIs generated by Oracle Forms, supporting the bulk-processing pattern of the Wf_Mapping_Tbl records.

Usage Notes

Because it is a private API, AHL_WF_MAPPING_PVT is not intended for direct invocation by customers. It is typically called by Oracle Advanced Services Online forms or by other internal packages when a user creates or maintains a workflow mapping configuration within the application. The ETRM metadata records that the package is referenced by one other package, reflecting its role as a lower-level implementation detail behind a public API surface. Developers performing upgrade or diagnostic work in 12.1.1 or 12.2.2 should inspect callers rather than invoking the procedures directly. Any custom code extending workflow mapping behavior should target the supported public API; direct calls to UPDATE_WF_MAPPING or its siblings bypass the documented public contract and may be affected by patching.