Results for “ci_attribute_value”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
INV_CUSTOMER_ITEM_GRP is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and classified by ETRM as a group (GRP) API. The package encapsulates the business logic that governs the relationship between customer-defined item information and the master inventory item definition in Oracle Inventory. Its central purpose is to resolve and return attribute values that belong to a customer item — the customer-facing representation of an inventory item, including customer item numbers, cross-references, container and commodity attributes, planning flags, tolerance values, and descriptive flexfield segments.
In Oracle Inventory, a single inventory item may be known to different customers by different numbers and may be associated with distinct packaging, planning, and ordering attributes at the customer, customer site, or customer category level. INV_CUSTOMER_ITEM_GRP provides the retrieval layer that allows applications and concurrent processes to obtain these values programmatically rather than re-implementing the lookup logic. Because the package is a group API rather than a public interface, it functions primarily as an internal service invoked by other Inventory, Order Management, and Advanced Supply Chain Planning components.
Key Procedures and Functions
- CI_ATTRIBUTE_VALUE — Returns the value of a specified customer item attribute. The procedure accepts a set of optional identifying keys (customer item, customer, customer category code, address, customer item number, inventory item, organization, and line category code) and an attribute name, and returns the resolved attribute value together with standard error code, error flag, and error message outputs. This is the primary entry point for callers that need a single attribute — for example, a customer item number, description, planning flag, or flexfield segment — resolved against the caller-supplied context.
- FETCH_ATTRIBUTES — Retrieves the set of attributes associated with a customer item. Whereas CI_ATTRIBUTE_VALUE targets one named attribute, FETCH_ATTRIBUTES supports the broader retrieval of customer item attribute data in a single call, making it suitable for callers that must obtain multiple attributes for a customer item context.
The header comment ($Header: INVICSDB.pls 120.6.12020000.3 2012/08/03) indicates maintenance through the 12.1.1 and 12.2.x release lines, consistent with a shared code base across EBS 12.1.1 and 12.2.2.
Tables Accessed
- MTL_CUSTOMER_ITEMS — The core customer item definition table. It holds customer-specific item numbers and their link to inventory items, and supplies most of the attribute values returned by the package.
- MTL_CUSTOMER_ITEM_XREFS — Stores cross-references between customer items and inventory items. This table is the mechanism behind cross-reference resolution and is directly relevant to searches for "get_cross_reference" functionality.
- MTL_SYSTEM_ITEMS — The master item definition, joined to validate the inventory item and retrieve organization-level item attributes.
- MTL_PARAMETERS — Organization parameters, used to confirm the operating context (for example defaulting and validation of the organization) before attributes are returned.
- HZ_CUST_ACCT_SITES_ALL — The Trading Community Architecture customer account site table, used to validate the customer and address context supplied by the caller.
Usage Notes
INV_CUSTOMER_ITEM_GRP is typically invoked from Oracle Inventory and Order Management forms, from concurrent programs that process customer item data, and from custom PL/SQL that needs to resolve a customer item attribute or cross-reference without duplicating the underlying query logic. ETRM records that the package is referenced by six other packages, confirming its role as a shared internal utility rather than a standalone interface. When implementing cross-reference lookups, developers should call this package (or the underlying MTL_CUSTOMER_ITEM_XREFS query pattern) instead of reading the tables directly, so that validation and error handling remain consistent. Callers must supply at least one valid identifying key and should inspect the returned Error_Flag and Error_Code before using the attribute value.