Results for “stage_id”

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

Overview

ECE_RULE_VIOLATIONS is a table in the EC (e-Commerce Gateway) schema of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. The table stores information about rule violations detected during the processing of inbound and outbound e-Commerce Gateway transactions. When the gateway validates translated or staged interface data against user-defined rules, any breach of those rules is persisted here, providing a durable audit trail of every transaction that failed a gateway validation check.

The physical schema documented in ETRM 12.2.2 records 19 columns owned by EC, with a single-column primary key constraint, ECE_RULE_VIOLATIONS_PK, defined on VIOLATION_ID. The object is an intersection of transactional staging data and rule definitions; each row records a specific interface column within a specific staged document that violated a specific rule. No unique business-key index is documented beyond the primary key, so VIOLATION_ID is the only surrogate identifier; business-key candidates would logically be the composite of STAGE_ID, RULE_ID, and INTERFACE_COLUMN_ID, which represent the natural grain of a violation.

Under the heuristic Data Vault classification supplied in the metadata, this table is classified as standalone. As a modeling suggestion, the table behaves as a satellite-like structure: it records descriptive, time-stamped attributes (severity, message text, ignore flag) about a business event keyed to a staged document, rather than acting as a hub of business entities or a pure link between hubs. The presence of standard audit columns reinforces its event-capture role.

Key Information Stored

The most significant columns fall into three groups. Identity and relationships are carried by VIOLATION_ID (surrogate primary key), STAGE_ID (foreign key to ECE_STAGE), DOCUMENT_ID, INTERFACE_COLUMN_ID, and RULE_ID, which together identify which staged document, which interface column, and which rule definition produced the violation. Classification attributes include VIOLATION_LEVEL, TRANSACTION_TYPE, and DOCUMENT_NUMBER, allowing violations to be categorized by severity and by the transaction type and document number under evaluation.

Descriptive and resolution attributes include IGNORE_FLAG, which allows a user or process to suppress a known-acceptable violation, and MESSAGE_TEXT, the human-readable explanation of the failure. The standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — record who or which concurrent program created and last modified the row. These are particularly valuable for tracing which gateway program run produced the violation.

Common Use Cases and Queries

Typical uses include diagnosing failed gateway transactions, reporting on rule failures by severity, and clearing or ignoring known exceptions before reprocessing. A query to list open violations for a staged document might be:

• SELECT v.VIOLATION_ID, v.STAGE_ID, v.RULE_ID, v.VIOLATION_LEVEL, v.MESSAGE_TEXT FROM EC.ECE_RULE_VIOLATIONS v WHERE v.IGNORE_FLAG = 'N' AND v.TRANSACTION_TYPE = :transaction_type ORDER BY v.VIOLATION_LEVEL, v.CREATION_DATE;
• Joining to the staging table: SELECT v.*, s.* FROM EC.ECE_RULE_VIOLATIONS v, EC.ECE_STAGE s WHERE v.STAGE_ID = s.STAGE_ID AND v.DOCUMENT_NUMBER = :doc_number;
• Auditing by program run: SELECT PROGRAM_ID, REQUEST_ID, COUNT(*) FROM EC.ECE_RULE_VIOLATIONS GROUP BY PROGRAM_ID, REQUEST_ID;

These patterns support operational troubleshooting, exception dashboards, and periodic compliance reporting on gateway data quality.

Related Objects

The most significant relationship is the foreign key from STAGE_ID to ECE_STAGE, which anchors each violation to its staged document. ECE_RULE_VIOLATIONS_PK on VIOLATION_ID governs parent-child references. Related rule-definition and interface objects referenced by RULE_ID and INTERFACE_COLUMN_ID, along with the ECE_STAGE staging hierarchy and the concurrent program definitions identified by PROGRAM_ID and REQUEST_ID, complete the dependency set. Reporting typically joins ECE_RULE_VIOLATIONS with ECE_STAGE through STAGE_ID and with rule metadata through RULE_ID.