Search Results inv_ebi

Overview

INV_EBI_ITEM_HELPER is an Oracle E-Business Suite application-level PL/SQL package body owned by the APPS schema. It sits within the Inventory (INV) module and provides a library of helper routines that support the EBI (Enterprise Business Intelligence/Integration) item-processing interface. Its primary role is to mediate between external or batch item requests and the underlying Oracle Inventory data model: it validates requests, resolves identifiers and descriptive values, drives item creation and synchronization, manages organization, category, and UDA assignments, and assembles user-facing diagnostic messages. The package is not a public concurrent program or form module itself, but a programmatic utility layer invoked by other EBI programs and by four other packages that reference it. In Oracle EBS 12.1.1 and 12.2.2 deployments the source shipped is INVEIHITB.pls (last revision 120.35.12010000.9), confirming its long-standing stability across the 11i-to-12.x release line. The ETRM classification is OTHER, reflecting that it exposes a utility API surface rather than a single business transaction API.

Key Procedures and Functions

ETRM documents 30 callable units. Representative public routines include the following.

• POPULATE_ERR_MSG — Builds a consolidated error text from organization, item, and message fragments. It appends org identity (code or ID) and item identity (name or inventory item ID) to a caller-supplied message, guards against the 32000-byte PL/SQL string limit by inserting a truncation ellipsis, and swallows exceptions internally so message construction never fails the calling transaction.
• ID_COL_VALUE, VALUE_TO_ID, ID_TO_VALUE — Generic key/value translation helpers used to convert between internal IDs and descriptive column values, typically for lookup-driven attributes.
• INITIALIZE_ITEM, SYNC_ITEM, PROCESS_ITEM_PVT — Core orchestration routines: initialize a new item staging record, synchronize item data, and execute the private item-processing driver.
• PROCESS_ITEM_UDA, PROCESS_ORG_ID_ASSIGNMENTS, PROCESS_CATEGORY_ASSIGNMENTS, PROCESS_PART_NUM_ASSOCIATION — Assignment processors for descriptive flexfield (UDA) values, organization assignments, category memberships, and manufacturer part-number cross-references.
• GET_ITEM_BALANCE, GET_ITEM_ATTRIBUTES, GET_ITEM_ATTRIBUTES_LIST, GET_INVENTORY_ITEM_ID, GET_ITEM_NUM, GET_ORGANIZATION_ID — Retrieval functions returning balances, attribute collections, and identifier resolution results.
• VALIDATE_GET_ITEM_REQUEST, IS_ENGINEERING_ITEM, IS_ITEM_EXISTS, IS_NEW_ITEM_REQUEST_REQD — Validation and predicate functions that determine whether a request is well-formed and whether a new item record must be created.

Tables Accessed

The package reads and writes through APPS synonyms. Item master and revision data is handled via MTL_ITEM_REVISIONS and MTL_ITEM_REVISIONS_B; category structures via MTL_CATEGORIES_KFV, MTL_CATEGORY_SETS_B, MTL_ITEM_CATALOG_GROUPS_KFV, and MTL_ITEM_CATEGORIES; and templates via MTL_ITEM_TEMPLATES. Cross-reference and origin data flow through MTL_CROSS_REFERENCES_B and HZ_ORIG_SYSTEMS_B. Costing and quantity information is drawn from CST_ITEM_COSTS and CST_QUANTITY_LAYERS, supporting balance and valuation retrieval. Lifecycle and status logic references EGO_LCPHASE_ITEM_STATUS. Concurrent request details (for tracking long-running item loads) come from FND_CONCURRENT_REQUESTS, while FND_LANGUAGES and FND_TIMEZONES_B supply localization and time-zone context for message and date rendering.

Usage Notes

INV_EBI_ITEM_HELPER is normally invoked indirectly. EBI item-import and item-maintenance processes call the INITIALIZE_ITEM / SYNC_ITEM / PROCESS_ITEM_PVT chain to stage and commit item records, while assignment and validation functions are called as sub-steps during that orchestration. Because the package is referenced by four other packages, extensions and custom concurrent programs commonly call its retrieval and translation helpers rather than reimplementing ID/value conversion or error formatting. The POPULATE_ERR_MSG pattern is intended for error-collection loops where many failures are accumulated into a single bounded string. Custom code should note that exceptions inside POPULATE_ERR_MSG are suppressed, so it must not be used as a validation gate; call VALIDATE_GET_ITEM_REQUEST and IS_ITEM_EXISTS for that purpose. When targeting 12.2.2, ensure APPS synonyms for the underlying MTL, CST, and EGO tables are valid, as the helper layer depends entirely on those synonyms.