Results for “application_usg_code”

50+ results




Overview
Explore in AI Chat

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

Overview

The AHL_WF_MAPPING table is a core configuration object within the Oracle E-Business Suite product AHL — Complex Maintenance Repair and Overhaul (CMRO). It resides in the AHL schema and stores the mapping between AHL business objects and the Oracle Workflow process definitions that govern their lifecycle. In practical terms, the table answers the question: "For a given AHL object and usage context, which workflow process, item type, and approval object should be instantiated?" This makes it a foundational lookup table for any CMRO feature that routes maintenance, repair, or overhaul transactions through approval and notification logic.

In Oracle EBS 12.1.1 and 12.2.2 the table is documented as VALID and carries 13 columns. The ETRM metadata classifies AHL_WF_MAPPING heuristically as standalone from a Data Vault perspective — a modeling suggestion indicating no outbound foreign-key relationships to other hubs were mined. In Data Vault terms this behaves most like a reference satellite or a small standalone reference table: it holds descriptive attributes keyed by its own surrogate identifier rather than participating in a hub-and-link network. The presence of ZD_EDITION_NAME reflects the edition-based redefinition (EBR) architecture introduced in 12.2, which supports online patching.

Key Information Stored

The table is anchored by the surrogate primary key WF_MAPPING_ID (constraint AHL_WF_MAPPING_PK). A unique index, AHL_WF_MAPPING_U1, covers WF_MAPPING_ID together with ZD_EDITION_NAME; this composite is the documented business-key candidate and is consistent with the EBR pattern in which the edition name qualifies the logical uniqueness of each row.

The most significant descriptive columns are:

  • WF_PROCESS_NAME — the Oracle Workflow process (activity) invoked for the mapped object.
  • APPROVAL_OBJECT — identifies the object type subject to approval routing.
  • ITEM_TYPE — the Workflow item type under which the process is defined.
  • APPLICATION_USG_CODE — the application usage code that scopes the mapping to a particular functional context.
  • ACTIVE_FLAG — enables or disables a mapping row without deleting it.

Standard EBS WHO columns are also present: OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. These support concurrency control, audit trails, and the 12.2 online-patching model.

Common Use Cases and Queries

Administrators and developers query this table to verify which workflow is wired to a given object, to troubleshoot approval routing failures, and to confirm that only one active mapping exists per object and usage code. A typical validation query is:

SELECT wf_mapping_id, wf_process_name, item_type, approval_object, application_usg_code
FROM   ahl.ahl_wf_mapping
WHERE  active_flag = 'Y'
AND    application_usg_code = :usage_code;

For a specific mapping lookup during diagnostics:

SELECT m.wf_process_name, m.item_type
FROM   ahl.ahl_wf_mapping m
WHERE  m.approval_object = :object_name
AND    m.active_flag = 'Y'
AND    m.zd_edition_name = 'SET2';

Reporting use cases include auditing active versus inactive workflow mappings, tracking mappings modified by a given user or after a specific date using the WHO columns, and documenting the workflow configuration during an upgrade from 12.1.1 to 12.2.2, where the addition of ZD_EDITION_NAME changes the uniqueness semantics.

Related Objects

Because the metadata classifies this table as standalone, no foreign keys are documented. The relationships that matter are therefore functional rather than declarative. The most significant dependent and referencing objects are:

  • Oracle Workflow runtime tables — WF_ITEM_TYPES and WF_PROCESSES — joined on ITEM_TYPE and WF_PROCESS_NAME.
  • WF_ITEM_ATTRIBUTE_VALUES and WF_ITEMS, which store instances launched using the mapped item type.
  • AHL CMRO transaction and work order tables that resolve their workflow at runtime via APPROVAL_OBJECT and APPLICATION_USG_CODE.
  • Standard EBS audit views and the FND_ lookup family used to decode ACTIVE_FLAG and usage codes.
  • AHL public APIs or concurrent programs that load and validate workflow mappings during CMRO setup.

Together these objects form the configuration and runtime chain through which CMRO operations acquire their approval and notification behavior.