Results for “responsibility”

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

Overview

AMW_VIOLATION_RESP is a table within the AMW (Internal Controls Manager) module of Oracle E-Business Suite. It is documented as obsolete and is not implemented in the current database environment referenced by the ETRM metadata. The table stores information about responsibility-level violations associated with a constraint violation, providing the granular attribution of a compliance breach down to a specific Oracle EBS responsibility or application role. In the broader EBS governance, risk, and compliance (GRC) context, this object supported the segregation-of-duties and access-control enforcement logic that Internal Controls Manager delivered before its functional retirement.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This suggests the table behaves primarily as a descriptive satellite: it hangs off a parent key (the violation) and records the changing attributes of that violation as it pertains to a particular responsibility. Analysts designing a warehouse layer over legacy AMW data should treat RESP_VIOLATION_ID as the satellite's own surrogate hash or sequence key, with VIOLATION_ID acting as the parent hub/link reference.

Key Information Stored

The table is documented with 13 columns. The most significant are summarized below; note that the primary key is the surrogate RESP_VIOLATION_ID, not a natural business key.

• RESP_VIOLATION_ID — Surrogate primary key (AMW_VIOLATION_RESP_PK); uniquely identifies each responsibility-violation record. This is the value users typically search for under the term "resp_violation_id."
• VIOLATION_ID — Foreign key to AMW_VIOLATIONS; ties the responsibility-level record to its parent constraint violation.
• RESPONSIBILITY_ID — The Oracle EBS responsibility implicated in the violation.
• APPLICATION_ID — The application context (typically FND_APPLICATION) under which the responsibility operates.
• ROLE_NAME — The role associated with the violation, where role-based access is defined.
• WAIVED_FLAG — Indicates whether the violation has been formally waived, permitting the assignment to persist despite the conflict.
• CORRECTED_FLAG — Indicates whether the violation has been remediated.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS; enforces multi-tenant or operating-unit data segregation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard EBS audit Who columns capturing record lifecycle.

Common Use Cases and Queries

Typical usage centers on compliance reporting and remediation tracking. A frequent pattern joins the responsibility violation to its parent violation and responsibility master data:

• Listing all open (non-waived, non-corrected) responsibility violations for a given responsibility.
• Counting violations by application or role to identify high-risk access assignments.
• Audit reporting on who last touched a remediation record, using the Who columns.

Illustrative SQL:

SELECT r.RESP_VIOLATION_ID, r.VIOLATION_ID, r.RESPONSIBILITY_ID, r.ROLE_NAME, r.WAIVED_FLAG, r.CORRECTED_FLAG FROM AMW_VIOLATION_RESP r WHERE r.RESPONSIBILITY_ID = :resp_id AND r.WAIVED_FLAG = 'N' AND r.CORRECTED_FLAG = 'N';

Because the object is obsolete and not implemented, live queries against it will fail; such SQL is relevant only for historical data migration or archival analysis.

Related Objects

• AMW_VIOLATIONS — Parent violation table; joined via AMW_VIOLATION_RESP.VIOLATION_ID = AMW_VIOLATIONS.VIOLATION_ID.
• AMW_VIOLAT_RESP_ENTRIES — Child detail table; references this table via AMW_VIOLAT_RESP_ENTRIES.RESP_VIOLATION_ID.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for data segregation.
• FND_RESPONSIBILITY — Master of the RESPONSIBILITY_ID business entity.
• FND_APPLICATION — Master of the APPLICATION_ID context.