Search Results amw_obj_classification_v




Overview
Explore in AI Chat

Overview

AMW_OBJ_CLASSIFICATION_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the AMW – Internal Controls Manager product. Its documented purpose is to present a consolidated, filterable list of all valid classifications that are applicable to object work types. The view returns the identifier and name of each qualifying work type together with the category code assigned to it, providing a single read-only source that joins work type definitions to their governing categories.

In Oracle EBS 12.1.1 and 12.2.2, views of this type are typically consumed by application logic, concurrent programs, and reporting layers rather than being maintained directly. They shield callers from the underlying multi-table structure and from the translation (VL) mechanics used by work type definitions. Because the view applies effective-dating and project-type filters internally, callers receive only classification rows that are currently active and non-project-specific, which makes it suitable for integration and ad hoc reporting where consistent, current data is required.

Underlying Base Objects

The view is defined over two documented base objects joined in a single SELECT statement:

  • AMW_WORK_TYPES_VL — aliased as TYPES; supplies the work type identifier and name. The VL suffix indicates a translated view that resolves the work type name according to the session language.
  • AMW_WORK_CATEGORIES_B — aliased as CAT; supplies the category code associated with each work type.

The join condition is TYPES.CATEGORY_ID = CAT.CATEGORY_ID. Three predicates restrict the result set: TYPES.PROJECT_TYPE_ID IS NULL excludes work types tied to a specific project type, and the effective-dating pair TYPES.START_DATE <= SYSDATE plus (TYPES.END_DATE > SYSDATE OR TYPES.END_DATE IS NULL) limits output to currently active rows with no end date or a future end date. The documented ETRM metadata does not enumerate referenced base objects beyond these, so any additional derivation is not documented.

Key Columns

The view exposes three columns:

  • WORK_TYPE_ID — numeric identifier of the work type, sourced from TYPES.WORK_TYPE_ID. This is the primary join key back to the work type definition and is used by downstream AMW processing.
  • WORK_TYPE_NAME — the descriptive, language-resolved name of the work type, sourced from TYPES.WORK_TYPE_NAME. This is the column users most commonly filter on when searching for a classification by name.
  • CATEGORY_CODE — the category code of the associated work category, sourced from CAT.CATEGORY_CODE. It groups work types into their classification category and supports category-level rollups and filtering.

Common Use Cases and Queries

The view is used to validate and report on active classifications, to populate selection lists, and to resolve a work type name from its identifier. A representative retrieval of all current classifications follows:

SELECT work_type_id, work_type_name, category_code FROM apps.amw_obj_classification_v ORDER BY category_code, work_type_name;

To find a classification by its name, as implied by the "work_type_name" search term:

SELECT work_type_id, category_code FROM apps.amw_obj_classification_v WHERE work_type_name = :p_name;

To list all work types belonging to a given category:

SELECT work_type_id, work_type_name FROM apps.amw_obj_classification_v WHERE category_code = :p_category ORDER BY work_type_name;

Because the view enforces SYSDATE-based effective dating, results automatically reflect only currently valid classifications; callers need not add date predicates themselves. This makes the view a dependable foundation for integration extracts and reports against Oracle EBS 12.1.1 and 12.2.2.