Search Results ece_rule_violations_s

Overview

APPS.ECE_RULES_PKG is the core validation engine of the Oracle E-Business Suite E-Commerce Gateway (ECE). Its business purpose is to enforce the configurable rule set that governs inbound and outbound electronic commerce transactions—such as EDI purchase orders, invoices, advance ship notices, and remittance advices—before those transactions are staged and processed by the gateway. The package evaluates trading partner profiles, mapped interface columns, and predefined validation rules against incoming or outgoing data, and records any breach as a rule violation. Because ECE is the entry point through which external trading partner data enters the EBS transaction tables, the integrity checks performed by ECE_RULES_PKG are fundamental to preventing invalid or non-compliant data from propagating into Order Management, Purchasing, Receivables, and Payables. The package body is valid in the APPS schema and is classified as an OTHER-type API rather than a public open interface API; it is therefore invoked internally by the gateway validation flow rather than being called directly by customers.

Key Procedures and Functions

The package exposes 25 documented procedures and functions that fall into three functional clusters:

• Rule type validators — VALUE_REQUIRED_RULE, SIMPLE_LOOKUP_RULE, VALUESET_RULE, NULL_DEPENDENCY_RULE, PREDEFINED_LIST_RULE, NULL_DEFAULT_RULE, and DATATYPE_CHECKING_RULE each implement one configurable rule category, checking source values against the corresponding rule metadata.
• Scope-level validators — VALIDATE_PROCESS_RULES, VALIDATE_TRADING_PARTNER, VALIDATE_TEST_PROD, and VALIDATE_COLUMN_RULES orchestrate validation at the process, trading partner, test/production, and column levels respectively.
• Address validators — VALIDATE_GET_ADDRESS_INFO, VALIDATE_SHIP_TO_ADDRESS, VALIDATE_BILL_TO_ADDRESS, VALIDATE_SOLD_TO_ADDRESS, VALIDATE_SHIP_FROM_ADDRESS, VALIDATE_BILL_FROM_ADDRESS, VALIDATE_SHIP_TO_INT_ADDRESS, and VALIDATE_SHIP_TO_INTRMD_ADD verify party-site addresses against the master data held in HR, HZ, and PO structures.
• Status maintenance — UPDATE_STATUS records the outcome of validation processing.

Tables Accessed

The package reads its rule definitions and writes its results through APPS synonyms. The ECE_RULE_* family (ECE_RULE_LIST, ECE_RULE_LIST_DETAILS, ECE_RULE_NULL_DEFAULT, ECE_RULE_NULL_DEP, ECE_RULE_NULL_DEP_DETAILS, ECE_RULE_SIMPLE_LOOKUP, ECE_RULE_VALUESET) supplies the configured rule metadata. ECE_COLUMN_RULES and ECE_INTERFACE_COLUMNS define which mapped columns are subject to which checks, while ECE_MAPPINGS, ECE_PROCESS_RULES, and ECE_TP_DETAILS establish the trading partner and process context. ECE_STAGE holds the transaction data under validation. Violations are persisted to ECE_RULE_VIOLATIONS and, notably, to the sequence-backed table ECE_RULE_VIOLATIONS_S, which the user search term references; this table carries the surrogate key that uniquely identifies each violation record. Master-data lookups against CE_BANK_BRANCHES_V, FND_FLEX_VALUE_SETS, FND_VSET, HR_LOCATIONS, HZ_CONTACT_POINTS, HZ_CUST_ACCT_SITES_ALL, and PO_VENDOR_SITES_ALL support the address and value-set validations.

Usage Notes

ECE_RULES_PKG is invoked automatically during ECE inbound and outbound processing, typically from the gateway's transaction validation and staging programs and from the ECE transaction forms. It is not intended for direct customer invocation, and no public API contract is documented for it. Customers who need to influence behavior should configure rules through the ECE Rule setup forms rather than modify this package, since changes would be overwritten by patching. When diagnosing failed transactions, DBAs and analysts commonly query ECE_RULE_VIOLATIONS_S and ECE_RULE_VIOLATIONS to identify the specific rule breaches recorded by this package. ETRM records the object as VALID in 12.1.1 and 12.2.2, with two dependent packages referencing it.