Results for “entered_by_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMW_CONSTRAINTS_B is a core table within the AMW (Internal Controls Manager) product module of Oracle E-Business Suite, holding information about Segregation of Duties (SoD) constraints. It is maintained by the AMW schema and is documented as VALID in ETRM releases 12.1.1 and 12.2.2. In the context of internal controls and compliance, this table defines and tracks the constraints that govern which combinations of responsibilities, roles, or privileges are incompatible, thereby allowing organizations to detect and prevent SoD violations.

From a Data Vault modeling perspective, the mined foreign-key structure suggests that AMW_CONSTRAINTS_B is hub-leaning. Its primary key, CONSTRAINT_REV_ID, is referenced by two dependent tables (AMW_CONSTRAINT_ENTRIES and AMW_VIOLATIONS), which is characteristic of a hub entity that anchors business keys and connects to related detail and outcome data. This classification is a heuristic modeling suggestion rather than a formal EBS construct.

Key Information Stored

The table contains 34 documented columns in the 12.1.1 schema. The most significant columns are:

• CONSTRAINT_REV_ID — The primary key (AMW_CONSTRAINTS_B_PK) and also the business-key candidate surfaced through the unique index AMW_CONSTRAINTS_B_U1. It uniquely identifies a specific revision of a constraint.
• CONSTRAINT_ID — Groups the revisions belonging to a logical constraint, distinguishing the constraint identity from its revision.
• START_DATE / END_DATE — Define the effective date range during which the constraint revision is active.
• TYPE_CODE — Indicates the category or kind of segregation-of-duties constraint.
• RISK_ID — Associates the constraint with an identified risk.
• CONTROL_ID — Links the constraint to an internal control designed to mitigate the associated risk.
• APPROVAL_STATUS — Tracks the workflow or approval state of the constraint revision.
• CLASSIFICATION — Records the classification applied to the constraint.
• OBJECTIVE_CODE — Captures the control objective the constraint supports.
• ENTERED_BY_ID — Identifies the user who entered the constraint.
• SECURITY_GROUP_ID / OBJECT_VERSION_NUMBER — Standard EBS multitenancy and optimistic locking columns.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, plus 15 ATTRIBUTE columns and ATTRIBUTE_CATEGORY, providing audit and extensibility support.

Common Use Cases and Queries

Typical usage centers on compliance reporting, SoD analysis, and constraint maintenance. Because the table is revision-based, queries frequently join to entries or violations using CONSTRAINT_REV_ID. A representative query to list active constraints with their risk and control context might resemble:

SELECT c.CONSTRAINT_ID, c.CONSTRAINT_REV_ID, c.TYPE_CODE, c.RISK_ID, c.CONTROL_ID, c.APPROVAL_STATUS FROM AMW_CONSTRAINTS_B c WHERE SYSDATE BETWEEN c.START_DATE AND c.END_DATE;

Analysts may also aggregate revisions per logical constraint, audit approval statuses pending action, or reconcile constraints against AMW_VIOLATIONS to measure SoD exposure. Reporting use cases include control-effectiveness dashboards, audit trails of constraint changes, and regulatory compliance extracts.

Related Objects

• AMW_CONSTRAINT_ENTRIES — References AMW_CONSTRAINTS_B via AMW_CONSTRAINT_ENTRIES.CONSTRAINT_REV_ID, holding the individual entries that compose each constraint revision.
• AMW_VIOLATIONS — References AMW_CONSTRAINTS_B via AMW_VIOLATIONS.CONSTRAINT_REV_ID, recording detected instances where a constraint has been breached.
• Related lookup and reference objects keyed by RISK_ID, CONTROL_ID, and OBJECTIVE_CODE support risk, control, and objective definitions.
• Standard EBS WHO columns relate to FND_USER for the CREATED_BY, LAST_UPDATED_BY, and ENTERED_BY_ID identifiers.