Results for “err_reason”

50+ results




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

Overview

DDR_ODI is a PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the Oracle Data Dictionary Reference (DDR) family of packages, which supports the Enterprise Tax and Regulatory Management (ETRM) product line and related data-conversion or data-loading operations. The package is declared with AUTHID CURRENT_USER, meaning all SQL statements it executes are parsed and privilege-checked against the invoker's schema rather than the package owner. This design is characteristic of generic, reusable validation and error-handling utilities that must operate on arbitrary caller-supplied tables.

The name "DDR_ODI" reflects its role as a Data Dictionary Reference utility oriented toward Oracle Data Integrator (ODI) or similar ETL-driven staging loads. The core business function is to provide a standard error-detection and error-management framework for bulk data interfaces: it checks incoming staged rows for duplicates and nulls, validates column values against reference targets, captures rejected rows into error tables, and moves clean rows into destination tables. The user search term "target ddi" most likely corresponds to references in ETRM setup or ODI mappings where destination (target) DDR interface or staging entities are configured.

Key Procedures and Functions

The package exposes a small, cohesive set of reusable routines:

  • DUP_CHECK — Performs duplicate detection against a source table using a caller-supplied list of key columns, recording failures to an error table for a given load identifier.
  • MOVE_ERRORS — Overloaded procedure that relocates rejected rows from a source or error table into a target table. One variant accepts a filter predicate to restrict which records are moved.
  • GET_ERROR — Function that returns the human-readable error message text associated with a supplied error code.
  • IS_VALID — General-purpose validation routine that compares a source column against a target table/column, with optional null checking and optional WHERE and error-column lists.
  • NULL_CHECK — Dedicated null-validation routine for a single source column, logging failures with an error code and load identifier.
  • ALLOC_MOVE_ERR — Handles allocation-specific error movement, using a run-type indicator and generic error message to classify and relocate failed allocation rows.
  • PARSE_PAD_ACCOUNTS — Parses padded accounting flexfield account strings, accepting a maximum segment level (defaulting to 10).
  • TRUNC_TABLE — Utility that truncates a specified staging or error table.

The package also declares two collection types: code_type (a VARCHAR2(10000) associative array) and account_array (a VARCHAR2(30) associative array), used internally to hold codes and account strings.

Tables Accessed

The documented reference list identifies three objects accessed through APPS synonyms. DDR_R_ORG_BSNS_ENT holds organization and business entity reference data used when validating or parsing organizational identifiers. ALL_TAB_COLUMNS is the Oracle data dictionary view used to introspect column definitions of caller-supplied tables at runtime, enabling the generic validation and parsing logic. PLITBLM is the standard Oracle PL/SQL integer table used for array/collection manipulation. Because the package is generic and AUTHID CURRENT_USER, most of its actual reads and writes occur against dynamically named source, error, and target tables passed at invocation time.

Usage Notes

DDR_ODI is not exposed through its own concurrent program or form; it is a backend utility invoked by other PL/SQL packages, ODI interfaces, or custom interfaces that stage data into ETRM or related modules. Typical invocation patterns follow a validate-then-move cycle: call DUP_CHECK and NULL_CHECK or IS_VALID to flag bad rows, use GET_ERROR to retrieve messages, then MOVE_ERRORS or ALLOC_MOVE_ERR to separate rejects, and finally TRUNC_TABLE to clean staging objects before the next load. The metadata records zero referencing packages, indicating the callers are external to the tracked ETRM package dependency graph—likely ODI mappings, SQL*Loader control scripts, or bespoke conversion programs. Because it relies on dictionary lookup and dynamic SQL, callers must ensure appropriate object privileges on all referenced tables.