Search Results ahl_wf_mapping_u1

Overview

AHL.AHL_WF_MAPPING is a seed-data configuration table in the Oracle E-Business Suite Application Object Library and Oracle Approvals Management / Approval Management Engine (AME) subsystem, owned by the AHL schema (Oracle Quality / Audit, Health, and Logistics schema used by Oracle Process Manufacturing and Oracle Approvals). The table stores workflow process mapping information that associates different AHL business objects with their corresponding Oracle Workflow process definitions, approval routing objects, and item types. In practice it acts as a lookup driving the selection of the correct workflow process when an AHL object enters an approval cycle, ensuring that the appropriate Workflow item type and process name are invoked for a given approval object and application usage context.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone, meaning no explicit parent or child relationships are enforced through the documented dependencies. This suggests that, if modeled under Data Vault conventions, AHL_WF_MAPPING would best be treated as a reference satellite or an independent reference hub rather than as a link table joining two hubs, since it carries its own surrogate identifier and business attributes without documented FK references to other entities.

Key Information Stored

The table contains thirteen documented columns. The most significant are:

• WF_MAPPING_ID — NUMBER, the primary key (AHL_WF_MAPPING_PK) and unique identifier for each workflow mapping row.
• OBJECT_VERSION_NUMBER — NUMBER, the locking sequence number used by the Oracle EBS optimistic locking framework to detect concurrent updates.
• ACTIVE_FLAG — VARCHAR2, indicates whether the mapping is currently enabled for use in approval processing.
• WF_PROCESS_NAME — VARCHAR2(30), the Oracle Workflow process name to be launched for the associated object.
• APPROVAL_OBJECT — VARCHAR2(30), identifies the approval object to which the workflow mapping applies.
• ITEM_TYPE — VARCHAR2, the Workflow item type used by the process.
• APPLICATION_USG_CODE — VARCHAR2(30), the application usage code that qualifies the mapping context.
• ZD_EDITION_NAME — VARCHAR2(30), the editioning column that participates in the unique business key and supports Online Patching / edition-based redefinition in EBS 12.2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

The unique index AHL_WF_MAPPING_U1 spans (WF_MAPPING_ID, ZD_EDITION_NAME), establishing the business-key candidate alongside the single-column primary key on WF_MAPPING_ID.

Common Use Cases and Queries

Typical usage centers on troubleshooting approval routing and on verifying which Workflow process will fire for a given object. A common diagnostic query retrieves all active mappings:

SELECT WF_MAPPING_ID, WF_PROCESS_NAME, APPROVAL_OBJECT, ITEM_TYPE, APPLICATION_USG_CODE
FROM AHL.AHL_WF_MAPPING
WHERE ACTIVE_FLAG = 'Y';

Administrators use the table to confirm or override the process name associated with an approval object before raising a bug or extending approval logic. Reporting use cases include auditing seed data across environments and comparing edition-specific rows via ZD_EDITION_NAME in a 12.2 multi-edition deployment.

Related Objects

The documented dependency metadata states that AHL_WF_MAPPING does not reference any database object and is referenced only by AHL_WF_MAPPING# (the editioning view / internal synonym). Because no valid foreign keys are documented, the most relevant related objects are conceptual rather than enforced:

• AHL.AHL_WF_MAPPING# — the underlying editioning object referencing the base table.
• WF_ITEM_TYPES and WF_PROCESS_ACTIVITIES — Oracle Workflow definitions joined via ITEM_TYPE and WF_PROCESS_NAME.
• FND_APPLICATION — provides the application context for APPLICATION_USG_CODE.
• AME_* approval configuration tables where approval objects are defined.

Because the object is classified as standalone, joins to these tables are performed by matching descriptive business columns rather than by documented FK constraints.