Search Results number_prefix

Overview

APPS.AMW_WORK_TYPES_VL is a multilingual (language-resolved) view in the Oracle E-Business Suite Applications (APPS) schema, registered in FND Design Data as AMW.AMW_WORK_TYPES_VL. It exposes work type definitions used by the Oracle Enterprise Asset Management (eAM) and related maintenance modules, presenting a translated, language-aware projection of work type data for the session's current language. Because it is a _VL view, consumers see only the translated description columns appropriate to their NLS language setting, while the underlying identifiers and attributes remain language-independent.

The view plays a reporting and integration role: it is the standard read interface for work type lookups, used in forms, concurrent programs, Discoverer reports, and interface tables that reference work types by code or ID. In Oracle EBS 12.1.1 and 12.2.2, the view remains VALID and is defined in the AMW (Asset Maintenance Work) product family.

Underlying Base Objects

ETRM metadata for this object records no explicitly documented base tables or referenced objects, so the definitive dependency mapping must be confirmed against the deployed database using ALL_DEPENDENCIES or ALL_VIEWS. By convention in EBS, a _VL view is built on a _TL (translation) table and a _B (base) table, typically joined on the primary key and LANGUAGE. For AMW_WORK_TYPES_VL, the expected pattern is a join between AMW_WORK_TYPES_B (language-independent attributes and foreign keys) and AMW_WORK_TYPES_TL (translated name/description), restricted to the current NLS language, with SOURCE_LANG handling for fallback. The view therefore inherits all Who columns, DFF columns, and operational flags from the base table while resolving language-dependent text at query time.

Key Columns

• WORK_TYPE_ID — Primary key of the work type, used as the foreign key in work order and asset-related tables.
• WORK_TYPE_CODE — Short alphanumeric code (VARCHAR2(30)) used for lookup and interface loading.
• DEFAULT_TYPE_FLAG — The column matched by the searched term "default_type_flag"; indicates whether this work type is the default type applied when none is specified. Values are typically Y/N and drive defaulting logic in work order creation.
• CATEGORY_ID / PROJECT_TYPE_ID — Classification references linking the work type to a category and project type.
• START_DATE / END_DATE — Effective dating window controlling whether the work type is currently active.
• NUMBER_PREFIX / AUTO_NUMBERING_METHOD — Govern automatic numbering of work orders created under the type.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield structure and segment columns for extensibility.
• OBJECT_VERSION_NUMBER — Optimistic locking column; SECURITY_GROUP_ID — hosted/multi-tenant use; ROW_ID — ROWID identifier.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns.

Common Use Cases and Queries

Typical scenarios include validating a work type code during interface import, locating the default work type for a given organization or category, and reporting all active work types with translated descriptions. Note that DEFAULT_TYPE_FLAG is exposed directly on the view, so it can be filtered without joining the base table.

To find the default work type:

• SELECT work_type_id, work_type_code FROM apps.amw_work_types_vl WHERE default_type_flag = 'Y' AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

To list active, current work types with their flexfield segments:

• SELECT work_type_code, attribute1, attribute2, auto_numbering_method FROM apps.amw_work_types_vl WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)) ORDER BY work_type_code;

Because the view is language-resolved, joining it to operational tables (for example, work order headers) yields descriptions in the user's session language, making it the preferred source for multi-language reporting in both 12.1.1 and 12.2.2 environments.