Search Results permit_status

Overview

EAM_PERMIT_STATUSES_VL is an APPS-owned view in Oracle E-Business Suite Enterprise Asset Management (EAM) that presents the set of user-defined work permit statuses together with their mapping to the corresponding system-level permit status. It is defined over EAM_SAFETY_USR_DEF_STATUSES_B, its translation table EAM_SAFETY_USR_DEF_STATUSES_TL, and the MFG_LOOKUPS lookup view, and it exists primarily to support the Work Permit functionality within EAM. The object is a "_VL" (validated language) view, meaning it resolves translated values according to the session language and exposes a single logical row per status for reporting, concurrent program, and integration consumption.

In 12.1.1 and 12.2.2, the view is catalogued as VALID in ETRM. It is not a transactional table; reads are effectively read-only projections of the underlying safety status configuration, which is typically maintained by administrators through the EAM Work Permit setup. Because it is a view rather than a table, no direct DML is expected against it; changes to permit statuses flow through the base EAM_SAFETY_USR_DEF_STATUSES_B and _TL tables.

Underlying Base Objects

The documented base objects driving the view are:

• EAM_SAFETY_USR_DEF_STATUSES_B — the base table holding each user-defined permit status row, including STATUS_ID, SYSTEM_STATUS, ENTITY_TYPE, SEEDED_FLAG and ENABLED_FLAG.
• EAM_SAFETY_USR_DEF_STATUSES_TL — the translation table supplying the language-specific USER_DEFINED_STATUS text for each STATUS_ID and ENTITY_TYPE, joined with the (+) outer-join syntax and constrained to the session language via T.LANGUAGE (+) = USERENV('LANG').
• MFG_LOOKUPS — the common lookup view used to resolve the SYS status meaning through LOOKUP_TYPE = 'EAM_WORK_PERMIT_STATUS' and LOOKUP_CODE = SYSTEM_STATUS.

The join is restricted to B.ENTITY_TYPE = 3, so only the entity type corresponding to work permit statuses is surfaced. Because _B and _TL are synonyms under APPS, the view resolves cleanly for both on-premise and R12.2 online-patching environments.

Key Columns

• STATUS_ID — primary identifier of the user-defined status.
• SYSTEM_STATUS — the system-level status code to which the user-defined status maps.
• PERMIT_STATUS — DECODE expression: for seeded rows (SEEDED_FLAG = 'Y') it returns the translated meaning (or the user-defined text as fallback); for non-seeded rows it returns the user-defined text directly.
• SYSTEM_STATUS_DESC — the lookup meaning for the system status.
• SEEDED_FLAG / ENABLED_FLAG — indicate Oracle-seeded versus customer-defined statuses and whether each status is active.
• ROW_ID — the base row's ROWID, exposed for tooling and update operations.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include listing all active permit statuses for a picklist, reporting the seeded-to-custom mapping, and joining permit data to display status descriptions.

• List enabled permit statuses with their system descriptions:
  SELECT STATUS_ID, PERMIT_STATUS, SYSTEM_STATUS, SYSTEM_STATUS_DESC
FROM APPS.EAM_PERMIT_STATUSES_VL
WHERE ENABLED_FLAG = 'Y';
• Distinguish seeded from user-defined statuses:
  SELECT STATUS_ID, PERMIT_STATUS, SEEDED_FLAG
FROM APPS.EAM_PERMIT_STATUSES_VL
WHERE SEEDED_FLAG = 'N';
• Resolve a single status by ID:
  SELECT PERMIT_STATUS, SYSTEM_STATUS_DESC
FROM APPS.EAM_PERMIT_STATUSES_VL
WHERE STATUS_ID = :status_id;

All three queries should be run with APPS credentials or suitable synonym grants, and results will be language-sensitive due to the _TL join.