Search Results ego_import_batch_status

Overview

APPS.EGO_IMPORT_BATCH_DETAILS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes import batch records used by the EGO (Item Management / Product Information Management) schema. The view consolidates batch header data from the import batches entity with descriptive lookup translations, user name resolution, and default matching rule attributes, presenting a denormalized result set suitable for operational reporting, concurrent program validation, and external system integration.

The view is central to questions about import batch status. Its BATCH_STATUS column stores the raw lookup code, while BATCH_STATUS_MEANING exposes the translated, user-facing description derived through EGO_ITEM_UTIL_PVT.GET_LOOKUP_MEANING against lookup type EGO_IMPORT_BATCH_STATUS. This dual exposure of coded value and meaning is the primary reason the view is frequently queried when users search for "ego_import_batch_status" within ETRM documentation.

Underlying Base Objects

The view is owned by APPS and is defined over a combination of synonyms, views, and a PL/SQL package. Its principal driving object is EGO_IMPORT_BATCHES_VL, from which batch identity, organization, source system, status, assignee, and audit columns are sourced. Descriptive enrichment is supplied by HZ_ORIG_SYSTEMS_TL for source system names and FND_OBJECTS_VL for batch type display names, each restricted by USERENV('LANG') to honor the session language.

Default match rule data originates from the EGO_IMPORT_OPTION_SETS synonym, with the customization definition resolved from AK_CUSTOMIZATIONS_TL. Lookup decoding is performed by the EGO_ITEM_UTIL_PVT package, which supplies GET_LOOKUP_MEANING and GET_USER_NAME calls. Additional documented references include BOM_GLOBALS and BOM_STRUCTURE_TYPES_TL, BOM_ALTERNATE_DESIGNATORS_TL, ENG_CHANGE_ORDER_TYPES and its translation table, FND_CONCURRENT_REQUESTS for request identifiers, and MFG_LOOKUPS. Because the view resolves names at runtime, code and meaning remain synchronized with current lookup definitions and translations.

Key Columns

• BATCH_ID, ORGANIZATION_ID, SOURCE_SYSTEM_ID / SOURCE_SYSTEM_NAME — Unique batch identifier, owning inventory organization, and the originating external system with its translated name.
• BATCH_TYPE / BATCH_TYPE_MEANING — Import batch category code and its display name from FND_OBJECTS_VL.
• BATCH_STATUS / BATCH_STATUS_MEANING — Lookup code from EGO_IMPORT_BATCH_STATUS and its translated meaning; the most widely referenced columns of this view.
• ASSIGNEE / ASSIGNEE_NAME and CREATED_BY / CREATOR_NAME — User IDs resolved to display names via EGO_ITEM_UTIL_PVT.GET_USER_NAME.
• BATCH_NAME, BATCH_DESCRIPTION, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Descriptive and standard audit attributes.
• LAST_MATCH_REQUEST_ID, LAST_IMPORT_REQUEST_ID — Concurrent request IDs for the most recent match and import runs, joinable to FND_CONCURRENT_REQUESTS.
• DEF_MATCH_RULE_CUST_APP_ID, DEF_MATCH_RULE_CUST_CODE, DEF_MATCH_RULE_RN_APP_ID, DEF_MATCH_RULE_RN_CODE, DEFAULT_MATCH_RULE_MEANING — Definition of the default match rule, resolved to a readable name through AK_CUSTOMIZATIONS_TL.
• OPTION_SET_ID, APPLY_DEF_MATCH_RULE_ALL, APPLY_DEFMATCHRULEALL_MEANING, MATCH_ON_DATA_LOAD — Option set linkage and yes/no flags decoded through the EGO_YES_NO lookup.

Common Use Cases and Queries

The view supports monitoring of import batch progress, troubleshooting stalled or failed batches, and feeding status information to downstream systems. A typical status inquiry is:

• SELECT batch_id, batch_name, batch_status_meaning, assignee_name, creation_date FROM ego_import_batch_details_v WHERE batch_status = 'NEW';
• SELECT batch_status_meaning, COUNT(*) FROM ego_import_batch_details_v GROUP BY batch_status_meaning;
• SELECT batch_id, batch_name, last_import_request_id, last_match_request_id FROM ego_import_batch_details_v WHERE organization_id = :org_id;
• SELECT b.batch_id, b.batch_name, r.phase_code, r.status_code FROM ego_import_batch_details_v b, fnd_concurrent_requests r WHERE r.request_id = b.last_import_request_id;

Because status and type meanings are translated at query time, reports built on this view automatically reflect the session language, making it suitable for both localized operational dashboards and integration extracts.