Search Results process_org_id_assignments

Overview

APPS.INV_EBI_ITEM_HELPER is a public PL/SQL package in Oracle E-Business Suite (12.1.1 and 12.2.2) that provides the server-side engine for the Item master integration and maintenance flows delivered through the EBI (Enterprise Business Integration) item pages. Its primary role is to service item-related requests initiated from the web-based item user interface, taking an incoming request payload (item identifiers, organization context, attribute selections, and category or revision assignments) and translating it into the appropriate validation, lookup, and DML operations against the Inventory item tables.

The package declares a substantial set of named constants that define item attribute groupings — INVENTORY_ATTRS, BOM_ATTRS, COSTING_ATTRS, PURCHASING_ATTRS, WIP_ATTRS, ORDER_ATTRS, MPSMRP_ATTRS, WEB_OPTION_ATTRS, and others — along with numeric constants (G_TEMPLATE, G_INVENTORY_ITEM, G_ORGANIZATION, G_CATEGORY_SET, G_LIFECYCLE, and similar) used to classify request types. It also defines the record type inv_ebi_name_value_pair_rec (Name/Value pair), which is used to pass attribute name-value data between the UI layer and the package. In effect, the package acts as a facade over the item schema, exposing reusable accessors and validators rather than duplicating logic in each calling form or concurrent program.

Key Procedures and Functions

• VALIDATE_GET_ITEM_REQUEST — Validates an inbound request to retrieve item data (the "get item" request) before processing proceeds, ensuring that the caller has supplied a structurally sound request.
• INITIALIZE_ITEM — Prepares item data structures for a request, establishing the working context for subsequent processing.
• SYNC_ITEM — Synchronizes item information between the incoming request and the database, coordinating the update or creation of item records.
• PROCESS_ITEM_PVT, PROCESS_ITEM_UDA, PROCESS_ORG_ID_ASSIGNMENTS, PROCESS_CATEGORY_ASSIGNMENTS, PROCESS_PART_NUM_ASSOCIATION — Private and supporting processors that handle the discrete work units of an item request: the core item record, user-defined attributes, organization assignments, category assignments, and parts-number or cross-reference associations.
• GET_ITEM_BALANCE, GET_ITEM_ATTRIBUTES, GET_ITEM_ATTRIBUTES_LIST, GET_INVENTORY_ITEM_ID, GET_ITEM_NUM, GET_ORGANIZATION_ID — Accessors that return item balances, item attribute values (singly or as a list), and the key identifiers (inventory item ID, item number, organization ID) used throughout item processing.
• IS_ENGINEERING_ITEM, IS_ITEM_EXISTS, IS_NEW_ITEM_REQUEST_REQD — Boolean-style checks that determine whether an item is an engineering item, whether it already exists, and whether a request should be treated as a new-item request.
• ID_COL_VALUE, VALUE_TO_ID, ID_TO_VALUE — Generic lookup helpers that convert between the internal ID representation and the display value of a given column or lookup, using the name/value pair record.

Tables Accessed

The package reads and writes through APPS synonyms. Item cost and quantity information is drawn from CST_ITEM_COSTS and CST_QUANTITY_LAYERS (used by the balance and cost accessors). Item lifecycle and status context comes from EGO_LCPHASE_ITEM_STATUS. Item definition and assignment data is held in MTL_ITEM_CATEGORIES, MTL_CATEGORIES_KFV, MTL_CATEGORY_SETS_B, MTL_ITEM_CATALOG_GROUPS_KFV, MTL_ITEM_REVISIONS, MTL_ITEM_REVISIONS_B, MTL_CROSS_REFERENCES_B, and MTL_ITEM_TEMPLATES. Setup and reference lookups include FND_LANGUAGES, FND_TIMEZONES_B, HZ_ORIG_SYSTEMS_B, and FND_CONCURRENT_REQUESTS (for concurrent request status and submission).

Usage Notes

INV_EBI_ITEM_HELPER is typically invoked from the EBI item web pages and associated Item forms, and from custom or extension code that needs to validate, retrieve, or synchronize item data using the same rules as the standard item maintenance flow. The documented procedures are marked as an "OTHER" API classification, meaning they are not part of the committed public API set and may change between releases. Because the package is referenced by four other packages within the application stack, customizations should call it only where the standard item integration path requires it, and should rely on the accessor functions (for example GET_ITEM_ATTRIBUTES, GET_INVENTORY_ITEM_ID) rather than reproducing item schema lookups directly.