Search Results value_required_rule

Overview

APPS.ECE_RULES_PKG is a PL/SQL package within the Oracle E-Business Suite E-Commerce Gateway (ECE) module. Its principal business function is the evaluation and enforcement of processing rules that govern inbound and outbound electronic data interchange (EDI) transactions and the associated trading partner data. The package provides the validation engine that determines whether a given transaction, column value, or trading partner assignment satisfies the conditions defined by the user through the ECE rules setup. When a rule is violated, the package records the breach in the rule violations structure and communicates the outcome to the calling program. Because ECE is the gateway through which EDI documents enter and leave the E-Business Suite, ECE_RULES_PKG plays a critical role in protecting data integrity, ensuring that inbound interface data conforms to the configured mapping rules before it is processed by downstream applications, and ensuring that trading partner configurations remain internally consistent. The package is classified under the OTHER API category in the ETRM documentation, indicating that it is an internal processing utility rather than a published business API intended for external integration.

Key Procedures and Functions

The package exposes twenty-five documented procedures and functions, which fall into several functional groups.

• Rule validation drivers: VALIDATE_PROCESS_RULES, VALIDATE_TRADING_PARTNER, VALIDATE_TEST_PROD, and VALIDATE_COLUMN_RULES orchestrate the evaluation of a rule set. VALIDATE_PROCESS_RULES evaluates the rules attached to a processing definition, VALIDATE_TRADING_PARTNER evaluates rules that are specific to a trading partner, VALIDATE_TEST_PROD distinguishes test versus production processing conditions, and VALIDATE_COLUMN_RULES evaluates the column-level mapping rules.
• Individual rule evaluators: VALUE_REQUIRED_RULE checks that a mandatory value is present; SIMPLE_LOOKUP_RULE and VALUESET_RULE validate values against lookup codes and value sets respectively; PREDEFINED_LIST_RULE checks a value against a defined list; DATATYPE_CHECKING_RULE verifies that the value matches the expected data type; NULL_DEFAULT_RULE and NULL_DEPENDENCY_RULE handle default substitution and inter-column dependency conditions; and NULL_DEPENDENCY_RULE operates in conjunction with the null dependency detail setup.
• Address validation procedures: 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 evaluate the various address roles and intermediate ship-to configurations used in EDI documents.
• Status maintenance: UPDATE_STATUS records or updates the outcome of a rule evaluation, typically writing to the violations table or updating a processing status flag.

Tables Accessed

The package reads and writes the core ECE rules configuration and staging tables through APPS synonyms. The setup tables include ECE_PROCESS_RULES, ECE_COLUMN_RULES, ECE_MAPPINGS, ECE_INTERFACE_COLUMNS, and ECE_TP_DETAILS, which together define what rules apply to which transaction, column, and trading partner. The supporting rule definition tables include ECE_RULE_LIST and ECE_RULE_LIST_DETAILS for predefined lists, ECE_RULE_NULL_DEFAULT, ECE_RULE_NULL_DEP and ECE_RULE_NULL_DEP_DETAILS for default and dependency logic, ECE_RULE_SIMPLE_LOOKUP for lookup-based validation, and ECE_RULE_VALUESET for value-set validation. Violations are persisted in ECE_RULE_VIOLATIONS and its sequence-backed counterpart ECE_RULE_VIOLATIONS_S. Transaction and staging data are read from ECE_STAGE. These tables collectively support the complete validation cycle from configuration retrieval through value inspection to violation logging.

Usage Notes

ECE_RULES_PKG is invoked internally by other ECE components rather than being called directly by end users. The ETRM dependency metadata shows that ECE_INBOUND and ECE_TRADING_PARTNERS_PUB reference this package, which confirms that it is consumed during inbound EDI processing and during trading partner maintenance. Its own dependencies include EC_UTILS, FND_API, and STANDARD, indicating that it relies on the ECE utility library and the Oracle Application Object Library API framework for message handling and error reporting. The package is executed in the context of the ECE inbound concurrent programs and related forms when rules must be applied to staged interface data. Because rule evaluation can affect whether a transaction is accepted, rejected, or flagged, customizations that extend or bypass this package should be undertaken with caution, and any direct invocation from custom code should respect the validation and status-update conventions established by the standard ECE processing flow.