Search Results ic_allc_cls_pk

Overview

IC_ALLC_CLS is a GMI (Process Manufacturing Inventory) reference table that defines Automatic Allocation Classes within Oracle E-Business Suite releases 12.1.1 and 12.2.2. In the Process Manufacturing inventory model, automatic allocation classes serve as classification codes that determine how on-hand inventory is automatically reserved, released, or distributed across lots during allocation processing. The table acts as a master list of permitted allocation class values that are subsequently referenced by lot-level and item-level master data.

The ETRM metadata indicates this object is "Not implemented in this database," meaning the table exists as shipped metadata but is populated or activated only when the corresponding GMI allocation functionality is licensed and configured. Its primary key is IC_ALLC_CLS_PK, defined on the ALLOC_CLASS column. From a Data Vault modeling perspective, the heuristic classification is hub-leaning. This suggests the table is best modeled as a hub entity: it holds a stable, unique business key (ALLOC_CLASS) with minimal descriptive attributes, surrounded by the transactional or attribute-bearing objects that reference it.

Key Information Stored

The documented metadata reveals a deliberately narrow table. The essential columns are:

• ALLOC_CLASS — The allocation class code. This is both the primary key (IC_ALLC_CLS_PK) and the natural business-key candidate. It uniquely identifies each valid allocation class definition in the Process Manufacturing inventory domain.
• TEXT_CODE — A foreign key to IC_TEXT_HDR, linking the allocation class to the Oracle text/comment header infrastructure. This associates descriptive text or multilingual documentation with each class.

Additional descriptive columns (such as class descriptions or status flags) are not enumerated in the provided excerpt. Where the documentation is silent, the practical observation is that the table's value derives primarily from the ALLOC_CLASS identifier itself, which is consumed as a foreign key by lot parameters and item master records.

Common Use Cases and Queries

The most frequent operational need is to validate the set of allocation classes available for assignment to items or lots, and to join those classes to their descriptive text. A representative query is:

• List all allocation classes with their text descriptions: SELECT a.ALLOC_CLASS, t.TEXT_CODE FROM IC_ALLC_CLS a, IC_TEXT_HDR t WHERE a.TEXT_CODE = t.TEXT_CODE;
• Find items assigned to a given class: SELECT m.ITEM_ID, m.ALLOC_CLASS FROM IC_ITEM_MST m WHERE m.ALLOC_CLASS = :alloc_class;
• Find lot parameters tied to an allocation class: SELECT p.ALLOC_CLASS, p.LOT_ID FROM IC_ALOT_PRM p WHERE p.ALLOC_CLASS = :alloc_class;

Reporting scenarios include allocation class usage audits, item-to-class assignment reviews, and validation of lot parameter configurations before running allocation programs. Because the table functions as a domain list, reports are typically value-set lookups rather than transaction summaries.

Related Objects

The FK relationships documented for IC_ALLC_CLS position it as a central reference point between text metadata and inventory master data:

• IC_TEXT_HDR — referenced by IC_ALLC_CLS.TEXT_CODE, supplying descriptive text for the class.
• IC_ALOT_PRM — references this table via ALLOC_CLASS, storing lot parameter configurations tied to an allocation class.
• IC_ITEM_MST — references this table via ALLOC_CLASS, indicating which allocation class applies to each inventory item.

Together these three dependent objects form the primary surface through which automatic allocation classes influence GMI inventory behavior: item master defaults, lot parameter rules, and supporting descriptive documentation. Administrators maintaining GMI allocation functionality should treat IC_ALLC_CLS as the authoritative source of valid ALLOC_CLASS values before modifying any dependent master or parameter records.