Search Results number_prefix

Overview

AMW_WORK_TYPES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the AMW product, the Internal Controls Manager module, and exposes the definitional attributes of "work types" used to classify and drive the workflow of certification and control activities. In EBS multi-language ("_VL") naming convention, the suffix indicates a view that joins a base table (_B) to its translation table (_TL) and returns the row in the session's current language only. As a result, AMW_WORK_TYPES_VL is the standard read interface consumed by reports, concurrent programs, OA Framework pages, and integration extracts: any consumer requiring the display name, tab caption, or description of a work type joins through this view rather than querying the underlying tables directly.

Underlying Base Objects

The view is defined over two documented base tables, AMW_WORK_TYPES_B (alias B) and AMW_WORK_TYPES_TL (alias TL), joined on WORK_TYPE_ID. The WHERE clause additionally filters the translation row with TL.LANGUAGE = USERENV('LANG'), so only the session-language translation is returned. The view projects every column of the _B table except the flexfield structure reference, and appends the translated columns WORK_TYPE_NAME, TAB_TEXT, and DESCRIPTION from the _TL table. Although the ETRM metadata records "Referenced base objects: none documented," the view text itself confirms the _B/_TL relationship, and this join pattern is the authoritative source for the object's structure.

Key Columns

• WORK_TYPE_CODE — the user-defined, language-independent short code that uniquely identifies a work type. This is the primary search key referenced by the user's query and is typically the value stored in related application tables and used in integration payloads.
• WORK_TYPE_ID — the surrogate primary key of the work type; the join key to both the _B and _TL tables.
• WORK_TYPE_NAME — the translated, user-facing name of the work type; this column is absent from the _B table and comes from _TL.
• TAB_TEXT and DESCRIPTION — translated tab caption and free-text description sourced from AMW_WORK_TYPES_TL.
• START_DATE / END_DATE — effective dating for the work type definition.
• CATEGORY_ID — the category to which the work type is assigned.
• DEFAULT_TYPE_FLAG, NUMBER_PREFIX, AUTO_NUMBERING_METHOD, PROJECT_TYPE_ID — control how instances of the work type are created and automatically numbered.
• SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER — ADO/MLS infrastructure columns supporting security and optimistic locking.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the DFF (descriptive flexfield) context and segment columns.
• ROW_ID — the ROWID of the _B row, projected under this alias.

Common Use Cases and Queries

The view is primarily used to resolve a work type code to its translated name, to list selectable work types in validation or LOV queries, and to supply work type labels in certification reporting.

Lookup by code:

SELECT work_type_id, work_type_code, work_type_name, description
FROM   apps.amw_work_types_vl
WHERE  work_type_code = :p_work_type_code;

Dropdown population restricted to active work types for the current date:

SELECT work_type_code, work_type_name
FROM   apps.amw_work_types_vl
WHERE  SYSDATE BETWEEN NVL(start_date, SYSDATE) AND NVL(end_date, SYSDATE)
ORDER  BY work_type_name;

Joining to a transaction or control table to return a translated work type name is the most frequent integration pattern. Because AMW_WORK_TYPES_VL is a simple join view with no documented INSTEAD OF triggers and is seeded as VALID, it should be treated strictly as read-only; all DML is performed against the _B and _TL tables through the appropriate AMW APIs.