Results for “eam_work_clearance_statuses_vl”

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

Overview

The EAM_WORK_CLEARANCE_STATUSES_VL view is an Oracle E-Business Suite dictionary object owned by the APPS schema and delivered as part of the Enterprise Asset Management (EAM) module. Its documented status in ETRM is VALID for releases 12.1.1 and 12.2.2. The view provides a reporting and integration layer over user-defined work clearance statuses, exposing both the user-defined status value and the corresponding system-defined work clearance status to which it is mapped. In EAM, a work clearance (also referred to as a safety clearance or lockout/tagout permit) governs the isolation of equipment and energy sources before maintenance work proceeds. Because customer sites frequently need terminology and lifecycle steps that differ from the seeded Oracle statuses, EAM permits the definition of user-defined statuses that are mapped back to a fixed set of system statuses used by application logic. This view is the read interface through which those custom definitions and their system mappings are surfaced for reports, extensions, and integration flows.

Underlying Base Objects

The view is defined over three documented objects, all resolved through APPS synonyms:

• EAM_SAFETY_USR_DEF_STATUSES_B — the base table holding the status definitions themselves, including the system status code, enabled and seeded flags, and audit columns. It is the driving table of the view.
• EAM_SAFETY_USR_DEF_STATUSES_TL — the translation table supplying the language-specific user-defined status text, joined on STATUS_ID and ENTITY_TYPE for the session language.
• MFG_LOOKUPS — the Oracle Manufacturing lookups view, restricted to lookup type EAM_WORK_CLEARANCE_STATUS, used to resolve the descriptive meaning of the system status code.

The joins to the translation table and to MFG_LOOKUPS are outer joins, and the base query is filtered to ENTITY_TYPE = 2, isolating the work clearance entity from other safety user-defined status usages.

Key Columns

• ROW_ID — the rowid of the base table row, useful for direct row addressing.
• STATUS_ID — unique identifier of the user-defined status definition.
• SYSTEM_STATUS — the system status code to which the user-defined status is mapped; this is the value consumed by EAM application logic.
• WORK_CLEARANCE_STATUS — the display value of the user-defined status. Where the record is seeded (SEEDED_FLAG = 'Y'), the view substitutes the meaning from MFG_LOOKUPS, falling back to the translated user-defined text.
• SYSTEM_STATUS_DESC — the descriptive meaning of the system status code from MFG_LOOKUPS.
• SEEDED_FLAG and ENABLED_FLAG — indicate whether the row is Oracle-seeded and whether it is currently active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard audit columns supporting change tracking and data lineage.

Common Use Cases and Queries

Typical uses include reporting the configured work clearance status lifecycle, validating mappings prior to data migration, and populating custom concurrent program outputs or integration payloads with status descriptions. Because only enabled lookup meanings are returned, the view is safe for presentation-layer use.

Listing all active status definitions and their system mappings:

SELECT status_id,
       work_clearance_status,
       system_status,
       system_status_desc
FROM   apps.eam_work_clearance_statuses_vl
WHERE  enabled_flag = 'Y'
ORDER  BY system_status, work_clearance_status;

Separating seeded Oracle statuses from customer-defined ones:

SELECT seeded_flag, COUNT(*)
FROM   apps.eam_work_clearance_statuses_vl
GROUP  BY seeded_flag;

Resolving the description for a status referenced by a specific clearance record:

SELECT v.work_clearance_status, v.system_status_desc
FROM   apps.eam_work_clearance_statuses_vl v
WHERE  v.status_id = :status_id;

All queries should run with the APPS schema or an appropriately synonymed account, and results are language-dependent through the session USERENV('LANG') setting.