Search Results delete_error

Overview

EGO_CHANGE_PEOPLE_IMPORT_PKG is a PL/SQL package owned by the APPS schema that supports the Change People Import process within Oracle Engineering (EGO). The package provides the programmatic backbone for loading, validating, and purging interface records that describe changes to people and role assignments associated with engineering changes. In an EBS 12.1.1 or 12.2.2 environment, this functionality allows organizations to bulk-import updates to the people, roles, and access privileges attached to engineering change objects, rather than maintaining each change manually through the Engineering Change Management forms.

The specification declares AUTHID CURRENT_USER, so the package executes with the privileges of the calling schema. It exposes a set of constants that drive concurrent program behavior and interface purge semantics. The RETCODE values (RETCODE_SUCCESS, RETCODE_WARNING, RETCODE_ERROR) follow the standard concurrent manager convention. The DELETE_LINES constants define which interface rows are removed after processing: DELETE_NONE, DELETE_ALL, DELETE_ERROR, and DELETE_SUCCESS. The LOG_MODE constants govern whether errors are written to a file, a table, or both, while the ORDER_BY constants control the sequence in which interface rows are created, updated, deleted, or synchronized.

Key Procedures and Functions

• GET_CURR_DATASET_ID — Returns the current dataset identifier used to track a batch of interface records loaded through SQL*Loader. This value is generated from the ENG_CPI_DATASET_ID_S sequence and consumed by downstream processing to isolate one import run from another.
• LOAD_INTERFACE_LINES — Reads rows staged in the change people interface table and applies them against the engineering change, role, and access structures. It is the core routine that transforms staged interface data into the target engineering change records.
• PURGE_INTERFACE_LINES — Removes processed rows from the interface table according to the purge mode selected. When invoked with DELETE_ERROR, only rows that failed validation are removed; DELETE_SUCCESS removes successfully processed rows; DELETE_ALL clears the entire set; DELETE_NONE leaves everything intact for review.

Tables Accessed

The package reads and writes ENG_CHANGE_PEOPLE_INTF, the central staging table for change people import records, and ENG_CPI_DATASET_ID_S, the sequence supplying dataset identifiers. It references ENG_CHANGE_ROLES_TEMP for intermediate role data, ENG_ENGINEERING_CHANGES for the parent change objects, and ENG_LOGIN_ACCESS_CHANGES for login/access modifications. Security-related structures are touched through FND_USER, FND_GRANTS, FND_MENUS, FND_MENUS_TL, FND_MENU_ENTRIES, FND_OBJECTS, and FND_FORM_FUNCTIONS. Party information is sourced from HZ_PARTIES, and processing errors are recorded in MTL_INTERFACE_ERRORS. UTL_FILE is used as the database file I/O package for log output.

Usage Notes

This package is typically invoked from the concurrent program that drives Change People Import, where the DELETE_LINES and LOG_MODE parameters are passed to control purge and logging behavior. Administrators commonly search for "delete_error" to locate the DELETE_ERROR constant that purges only failed interface rows while preserving successful ones. The package is not referenced by any other documented package, so it is intended to be called directly by the concurrent manager or by custom code that wraps the import process. Because it relies on APPS synonyms for all base tables, it must be invoked from a schema with the appropriate EXECUTE grant and synonym access. When debugging failed imports, LOG_INTO_FILE_AND_TABLE is the recommended mode, as it captures diagnostics in both the concurrent output file and MTL_INTERFACE_ERRORS for later querying.