Search Results amw_work_categories_b_pk

Overview

AMW_WORK_CATEGORIES_B is a foundational table within the Oracle E-Business Suite Internal Controls Manager (AMW) module, which is part of the Governance, Risk, and Compliance (GRC) product family. As described in the ETRM metadata, this table "contains information about extensible attributes categories." In practical terms, it serves as the master definition repository for the attribute categories that govern how extensible (flexfield-style) descriptive attributes are grouped and applied to records managed within the Internal Controls Manager application. These categories allow organizations to extend core AMW entities — such as controls, processes, risks, and test plans — with customer-specific or compliance-specific metadata without altering the underlying schema.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as standalone under the Data Vault methodology, meaning the FK mining process did not surface inbound or outbound foreign-key relationships that would position it as a hub or link. In Data Vault terms, this suggests treating AMW_WORK_CATEGORIES_B as a reference or descriptive entity — effectively a satellite-like lookup — that supplies category definitions consumed by other AMW tables, rather than as a transactional or associative structure.

Key Information Stored

The table is owned by the AMW schema and comprises 29 documented columns in the 12.1.1 physical schema. The most important columns are:

• CATEGORY_ID — The surrogate primary key, enforced by the AMW_WORK_CATEGORIES_B_PK constraint. It uniquely identifies each extensible attribute category record.
• CATEGORY_CODE — The business-key candidate: the human-readable, user-facing code that uniquely identifies a category. Application logic and integrations typically resolve category references through this value.
• START_DATE / END_DATE — Effective-dating columns that define the active life of a category definition, supporting date-tracked (versioned) reference data.
• OBJ_NAME — Identifies the AMW object (for example, control or process) to which the category applies.
• ATTR_GROUP_TYPE — Classifies the attribute grouping behavior associated with the category.
• ATTRIBUTE_CATEGORY — The descriptive-flexfield context that ties the category to the standard Oracle attribute framework.
• ATTRIBUTE1 through ATTRIBUTE15 — The fifteen standard descriptive-flexfield columns holding the extensible attribute values defined by each category.
• SECURITY_GROUP_ID — The multi-tenant / operating-unit security discriminator used to isolate category data by security group.
• OBJECT_VERSION_NUMBER — The optimistic-locking version token used by the AMW framework to detect concurrent updates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — The standard Oracle who-columns that provide audit traceability.

The _B suffix in the table name conventionally indicates the base (non-translated) table; a corresponding _TL table typically holds translated name or description columns, joined on CATEGORY_ID.

Common Use Cases and Queries

Typical uses include reporting on category definitions, validating category codes during integrations, and joining category data to transactional AMW records to label or filter flexible attributes.

• Retrieve currently effective categories: SELECT CATEGORY_ID, CATEGORY_CODE, OBJ_NAME FROM AMW_WORK_CATEGORIES_B WHERE SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE);
• Look up a category by business key: WHERE CATEGORY_CODE = :code to resolve the surrogate CATEGORY_ID.
• Security-scoped reporting: filter results by SECURITY_GROUP_ID to restrict output to the caller's security group.
• Extensible attribute reporting: select the relevant ATTRIBUTEn columns alongside CATEGORY_CODE to produce customer-specific attribute reports.

Related Objects

Given the standalone classification, related objects are primarily consumers of the category definitions through the CATEGORY_ID key rather than enforced FK dependents. Significant related objects include:

• AMW_WORK_CATEGORIES_TL (or equivalent translation table) — joins on CATEGORY_ID to supply translated category names and descriptions.
• AMW_WORK_CATEGORIES_V — a view layer presenting category definitions with translated and effective-dated values.
• Other AMW GRC tables that store CATEGORY_ID or ATTRIBUTE_CATEGORY references — including control, process, risk, and test-related tables that consume these attribute categories.
• The AMW Internal Controls Manager concurrent programs and Oracle Forms / OAF pages that create, update, and version categories through the AMW schema APIs.

Consumers should always join back to AMW_WORK_CATEGORIES_B on CATEGORY_ID and respect START_DATE/END_DATE and SECURITY_GROUP_ID filtering to obtain accurate, in-scope results.