Search Results create_wf_mapping

Overview

APPS.AHL_WF_MAPPING_PVT is a private PL/SQL package body belonging to the Oracle E-Business Suite product family for Oracle Enterprise Asset Management and Depot Repair (AHL — the Application Object Library prefix associated with Oracle Enterprise Asset Management and the eAM/Depot Repair module set). Its specific business purpose is to maintain and validate the mapping between Oracle Workflow (WF) process definitions and the functional usage contexts in which those workflows may be launched, such as within Depot Repair or field service transactions. The package encapsulates the create, update, delete, and validation logic required by the public API layer that sits above it, ensuring data integrity, uniqueness, and business-rule compliance for records held in the AHL_WF_MAPPING base table.

The package is classified as PVT (private) in the ETRM 12.2.2 metadata, meaning it is not intended for direct invocation by customers or third-party developers. Only one other package references it, confirming its role as a supporting implementation unit behind a public API. The source header, dated 2006, indicates a long-lived, stable component carried forward across releases, including 12.1.1 and 12.2.2.

Key Procedures and Functions

Seven documented procedures and functions form the working surface of this package:

• PROCESS_WF_MAPPING — The main driver that routes a request to the appropriate internal handler based on the requested DML action.
• CREATE_WF_MAPPING — Inserts a new workflow-to-usage mapping record after validation.
• UPDATE_WF_MAPPING — Modifies an existing mapping record, re-validating affected attributes.
• DELETE_WF_MAPPING — Removes an existing mapping record, subject to any referential checks.
• VALIDATE_WF_MAPPING — Orchestrates the validation routines, coordinating required-item checks, uniqueness checks, process-name checks, and default checks.
• CHECK_WF_MAPPING_ITEMS — Confirms that mandatory attributes are populated and that uniqueness constraints on the mapping are not violated.
• COMPLETE_WF_MAPPING_REC — Populates any derived or defaulted columns before persistence, ensuring the record is complete and internally consistent.

Notably, the source excerpt explicitly documents the internal validator Check_Appl_Usg_Code, which is the routine directly associated with the user's search term. This procedure validates the application usage code supplied on the mapping record — the field that designates which functional usage context the workflow serves — ensuring the value is legitimate before the record is accepted. Other internal validators include Check_Wf_Mapping_Req_Items, Check_Wf_Mapping_UK_Items (uniqueness key), Check_Process_Name (used when the process name is typed rather than selected from an LOV), and Check_Default (enforcing that only one default mapping can exist for a given context).

Tables Accessed

The package operates against the following objects, referenced through APPS synonyms:

• AHL_WF_MAPPING — The primary base table holding workflow-to-usage mapping definitions; the target of create, update, and delete operations.
• AHL_WF_MAPPING_S — The sequence used to generate primary keys for new mapping records.
• WF_ACTIVITIES and WF_ACTIVITIES_TL — Oracle Workflow activity definition tables, joined to validate workflow item types, process names, and their translated display names.
• DUAL — Used for singleton lookups and simple existence checks.
• PLITBLM — The PL/SQL index-by table used by the JTF validation framework, reflecting the package's use of standard EBS error-handling and validation infrastructure (Jtf_Plsql_Api).

Usage Notes

Because AHL_WF_MAPPING_PVT is a private package, it is never called directly from a client form or custom script. It is invoked in the following ways:

• Indirectly through the public AHL_WF_MAPPING API, which delegates all DML to the PROCESS_WF_MAPPING entry point.
• From the Oracle EBS setup form for workflow mapping configuration, used by implementers defining which workflows apply to which usage codes.
• From concurrent or batch processes that load or refresh mapping definitions, again via the public API.

Developers searching for check_appl_usg_code should recognize it as an internal validation step. Custom code must not call it directly; instead, rely on the public wrapper exposed by the AHL_WF_MAPPING API, and expect the usage-code validation to occur automatically during any create or update operation. Because the package uses NOCOPY OUT parameters and the JTF validation framework, exceptions are returned through x_return_status rather than propagated as unhandled errors.