Search Results amw_work_types_b_pk

Overview

AMW_WORK_TYPES_B is a core configuration table in the Oracle E-Business Suite module AMW — Internal Controls Manager (ICM). It stores the definition of work types, which are the operational classifications used throughout ICM to categorize and govern the various kinds of work items, audits, assessments, and remediation activities that flow through the controls and compliance lifecycle. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the AMW schema and is registered as a valid, seeded object maintained by the application.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as a standalone structure. That classification suggests the table behaves as a hub-like reference entity: it holds the durable business identity of each work type and is not a transaction link or a dependent satellite. Because the table carries descriptive and attribute columns alongside its identity key, a strict Data Vault implementation would separate the hub (work type identity) from the satellite (descriptive attributes such as dates, flags, and descriptive flexfields). The standalone designation indicates that no upstream dependency chain is modelled for it within this documentation set.

Key Information Stored

The table contains 33 documented columns. The most significant are:

• WORK_TYPE_ID — surrogate primary key, enforced by constraint AMW_WORK_TYPES_B_PK. This is the internal identifier referenced by dependent ICM entities.
• WORK_TYPE_CODE — the human-readable business key used in user interfaces, reports, and integrations. This is the primary business-key candidate for the work type.
• START_DATE / END_DATE — effective-dating columns defining the active life of the work type definition.
• CATEGORY_ID — foreign reference to the category that groups this work type for reporting and filtering.
• PROJECT_TYPE_ID — associates the work type with a project type, linking ICM configuration to project-centric processing.
• DEFAULT_TYPE_FLAG — indicates whether this work type is the default for its category or process.
• NUMBER_PREFIX and AUTO_NUMBERING_METHOD — control how work items of this type are automatically numbered (prefix text and numbering algorithm).
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-tenant style data segregation across operating units or security partitions.
• OBJECT_ID and OBJECT_VERSION_NUMBER — support the OAF/BC4J object model, providing the row identifier and optimistic-locking version used by the middle tier.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns, allowing customer-specific extensions without schema changes.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — the standard "who/when" stamping present on nearly all EBS transaction tables.

Common Use Cases and Queries

Typical usage centers on configuration reporting, validation of setup completeness, and lookups that translate WORK_TYPE_ID into WORK_TYPE_CODE for downstream reports. A common pattern joins the table to FND_SECURITY_GROUPS to confirm the security context of each work type:

• Listing active work types: SELECT work_type_id, work_type_code FROM amw_work_types_b WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);
• Resolving the default work type per category: SELECT category_id, work_type_id, work_type_code FROM amw_work_types_b WHERE default_type_flag = 'Y';
• Checking numbering configuration: SELECT work_type_code, number_prefix, auto_numbering_method FROM amw_work_types_b ORDER BY work_type_code;
• Security-scoped extracts: SELECT a.work_type_code, s.security_group_name FROM amw_work_types_b a, fnd_security_groups s WHERE a.security_group_id = s.security_group_id;
• Flexfield-aware reporting: SELECT work_type_code, attribute_category, attribute1 FROM amw_work_types_b;

Because row volume is normally small and largely static, these queries are inexpensive and are frequently embedded in BI Publisher reports, OTBI extracts, and setup validation scripts during implementations and upgrades.

Related Objects

The most significant related objects follow from the documented key and foreign-key relationships:

• AMW_WORK_TYPES_B_PK — the primary-key constraint on WORK_TYPE_ID, referenced by child tables throughout ICM.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; the standard EBS security partition definition table.
• AMW_CATEGORIES (via CATEGORY_ID) — the assumed parent of the work-type grouping, though not listed as a documented FK here.
• AMW_PROJECT_TYPES or equivalent project-type reference (via PROJECT_TYPE_ID) — links work types to project configuration.
• AMW_WORK_TYPES_TL — where multilanguage installations exist, the translation table supplying user-facing names and descriptions for each work type, joined on WORK_TYPE_ID and LANGUAGE.
• Work item / audit transaction tables in the AMW schema — the operational tables that consume WORK_TYPE_ID as a foreign key and drive the compliance lifecycle.

Together these dependencies position AMW_WORK_TYPES_B as a foundational reference table whose identity and configuration propagate throughout Internal Controls Manager.