Search Results common_ag_validations

Overview

EGO_AG_BULKLOAD_PVT is a private (PVT) PL/SQL package owned by the APPS schema within the Oracle E-Business Suite Item Management (EGO / EGO_ITEMMGMT_GROUP) product family. Its purpose is to support the high-volume, set-based import of Attribute Group definitions — the descriptive flexfield-style structures that attach configurable attributes to items in Oracle Product Information Management. The package implements the bulk-loading pipeline that translates staged rows from the EGO interface tables (EGO_ATTR_GROUPS_INTERFACE, EGO_ATTR_GROUPS_DL_INTERFACE, and EGO_ATTR_GROUP_COLS_INTF) into the permanent Attribute Group and Data Level base records used throughout EGO. It is a companion to the interface-reconciliation machinery in EGO and is normally orchestrated by a concurrent program rather than called directly by end users.

The package declares the standard EBS API contract conventions — the operation constants G_OPR_CREATE, G_OPR_UPDATE, G_OPR_DELETE, and G_OPR_SYNC, and the FND_API return statuses (G_RET_STS_SUCCESS, ERROR, UNEXP_ERROR) — along with process-status markers (G_PROCESS_RECORD, G_ERROR_RECORD, G_SUCCESS_RECORD) and counters for attribute groups, data levels, and attributes. These constants govern transactional behaviour and status reporting during bulk import.

Key Procedures and Functions

The 39 documented units divide into several functional clusters. INITIALIZE and VALIDATE_TRANSACTION_TYPE seed working globals (request ID, user, login, application) and confirm that an inbound transaction is one of the supported operation types.

• Identifier resolution: VALUE_TO_ID_AG, VALUE_TO_ID_DL, VALUE_TO_ID_ATTR and their table-oriented variants (VALUE_TO_ID_AG_TBL, VALUE_TO_ID_DL_TBL, VALUE_TO_ID_ATTR_TBL) translate external interface keys (attribute group, data level, and attribute names) into their internal surrogate identifiers, using the relevant EGO and FND descriptive-flex definitions.
• Record construction: CONSTRUCT_ATTR_GROUPS, CONSTRUCT_AG_DATA_LEVEL, and CONSTRUCT_ATTRIBUTE populate the in-memory or interface structures for each entity type from the staged columns.
• Validation: BULK_VALIDATE_ATTR_GROUPS and BULK_VALIDATE_ATTRIBUTE perform set-based checks; ADDITIONAL_AGDL_VALIDATIONS and ADDITIONAL_ATTR_VALIDATIONS apply entity-specific rules; COMMON_AG_VALIDATIONS, COMMON_DL_VALIDATIONS, and COMMON_ATTR_VALIDATIONS centralise reusable checks across all three entity types.
• Execution: IMPORT_AG_INTF and PROCESS_ATTR_GROUPS drive the actual interface-to-base load, committing per G_COMMIT and recording per-record status (success, error) via the G_MESSAGE_NAME / G_MESSAGE_TEXT error-handler globals.

The user's search term get_attr_changes_b_table does not appear among the documented procedures; it is not a public entry point of this package and likely refers to change-detection logic implemented elsewhere in the EGO attribute-group stack.

Tables Accessed

The package reads and writes through APPS synonyms. The three interface tables — EGO_ATTR_GROUPS_INTERFACE, EGO_ATTR_GROUPS_DL_INTERFACE, and EGO_ATTR_GROUP_COLS_INTF — are the staging sources and are consumed during import. The base and extension tables EGO_ATTR_GROUP_DL, EGO_DATA_LEVEL_B, EGO_OBJ_AG_ASSOCS_B, EGO_FND_DF_COL_USGS_EXT, and EGO_FND_DSC_FLX_CTX_EXT receive or are validated against the loaded data. Descriptive flexfield metadata is resolved from FND_DESCRIPTIVE_FLEXS, FND_DESCR_FLEX_CONTEXTS_TL, FND_DESCR_FLEX_COLUMN_USAGES, FND_FLEX_VALUE_SETS, FND_COLUMNS, FND_APPLICATION, and FND_FORM_FUNCTIONS, providing the column, context, and valueset definitions required to validate attribute definitions before they are committed.

Usage Notes

EGO_AG_BULKLOAD_PVT is an internal (PVT) API: it is invoked by the Attribute Group bulk-import concurrent program or by other EGO packages — the metadata notes it is referenced by one other package — and is not intended for direct custom calls. Customers who need to load attribute groups programmatically should use the supported public interface tables and the associated concurrent program rather than calling this private package, because the API classification offers no upgrade guarantee. When debugging imports, DBAs should trace the concurrent request logged in G_REQUEST_ID and inspect the EGO interface tables for rows left in an error state.