Search Results batch_type_meaning

Overview

EGO_IMPORT_BATCH_DETAILS_V is a reporting and integration view in the APPS schema belonging to the EGO — Advanced Product Catalog product family. Its documented purpose is to present all details of an import batch, consolidating identity, ownership, status, assignment, and match-rule information held across the EGO import batch tables into a single, denormalized read model. In Oracle EBS 12.1.1 and 12.2.2, the view functions as the primary lens through which import batches are inspected by concurrent programs, personalizations, and custom reports that need meaningful display values rather than raw coded identifiers.

A defining characteristic of the view is its heavy reliance on inline scalar subqueries and calls to the EGO_ITEM_UTIL_PVT package to resolve translations and lookups at query time. Source system names, batch type meanings, assignee names, creator names, status meanings, and default match rule descriptions are all resolved dynamically, ensuring the view returns user-facing text consistent with the session language. Because of this, the view is best regarded as a query tool rather than a high-volume transactional source.

Underlying Base Objects

The view is built primarily on EGO_IMPORT_BATCHES_VL, the base batch entity view, from which most driving columns such as BATCH_ID, ORGANIZATION_ID, SOURCE_SYSTEM_ID, BATCH_TYPE, BATCH_STATUS, NAME, and the standard WHO columns are drawn. Option-set attributes (default match rule application and region identifiers, option set identifier, and the flag controlling application of the default match rule to all items) derive from EGO_IMPORT_OPTION_SETS.

Translation and lookup resolution depends on several reference objects. HZ_ORIG_SYSTEMS_TL supplies the source system name; FND_OBJECTS_VL supplies the batch type display name; and AK_CUSTOMIZATIONS_TL supplies the default match rule meaning, keyed by customization and region application/code pairs. Lookup meanings are obtained through EGO_ITEM_UTIL_PVT.GET_LOOKUP_MEANING. The documented referenced base objects also include BOM_ALTERNATE_DESIGNATORS_TL, BOM_STRUCTURE_TYPES_TL, ENG_CHANGE_ORDER_TYPES, ENG_CHANGE_ORDER_TYPES_TL, ENG_CHANGE_ORDER_TYPES_TL, FND_CONCURRENT_REQUESTS, BOM_GLOBALS, and MFG_LOOKUPS, which support the batch type domain (including change order types), request context, and structural classification of imported items. Notably, ENG_CHANGE_ORDER_TYPES_TL is among these referenced objects, reflecting that import batches may carry engineering change order context resolved through the change order type translations.

Key Columns

• BATCH_ID, ORGANIZATION_ID, SOURCE_SYSTEM_ID, SOURCE_SYSTEM_NAME — batch identity, owning inventory organization, and the translated source system label.
• BATCH_TYPE, BATCH_TYPE_MEANING — the coded object name and its display name from FND_OBJECTS_VL.
• BATCH_STATUS, BATCH_STATUS_MEANING — status code and lookup meaning from the EGO_IMPORT_BATCH_STATUS lookup.
• ASSIGNEE, ASSIGNEE_NAME, CREATED_BY, CREATOR_NAME — user identifiers resolved to user names via EGO_ITEM_UTIL_PVT.GET_USER_NAME.
• BATCH_NAME, BATCH_DESCRIPTION — user-supplied batch label and description.
• LAST_MATCH_REQUEST_ID, LAST_IMPORT_REQUEST_ID — concurrent request identifiers for the most recent match and import executions.
• 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 — default match rule identity and translated description.
• OPTION_SET_ID, APPLY_DEF_MATCH_RULE_ALL — option set reference and the flag governing default match rule scope.
• CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns.

Common Use Cases and Queries

Typical uses include monitoring batch progress, resolving request identifiers to concurrent requests, and driving personalized batch dashboards. Example query listing active batches with owner and status:

SELECT batch_id, batch_name, organization_id,
       source_system_name, batch_type_meaning,
       batch_status_meaning, assignee_name, creation_date
FROM   apps.ego_import_batch_details_v
WHERE  batch_status_meaning NOT IN ('Complete','Cancelled');

To reconcile batch activity against concurrent requests or to inspect default match rule configuration for a given option set, the LAST_MATCH_REQUEST_ID, LAST_IMPORT_REQUEST_ID, OPTION_SET_ID, and DEFAULT_MATCH_RULE_MEANING columns are joined to FND_CONCURRENT_REQUESTS and EGO_IMPORT_OPTION_SETS respectively. Because translations are resolved with USERENV('LANG'), results reflect the querying session's language, so report definitions should set NLS appropriately for consistent output.