Explain Item Master and Organization Structure in EBS in Oracle Applications

10 / 60

EBSintermediate

Item Master and Organization Structure in EBS

Explain how items and inventory organizations are structured to support multi-org manufacturing and distribution

Items are defined once and used in many organisations. The structure that makes that work is the master and child model.

The Item Master is like a central product catalog for a retail chain — head office defines the base product (description, UPC code), but each individual store (inventory org) can set its own local price, shelf location, or reorder point.

Key Concepts

The organisation hierarchy.

    Business Group        HR boundary -- employees, positions
      Legal Entity        the legal company that signs contracts
        Operating Unit    the subledger boundary -- AP, AR, PO, OM
          Inventory Org   a physical place: a warehouse, a plant

Each level means something specific. The Operating Unit is what MOAC secures on. The Inventory Organization is what holds on-hand quantities.

One Operating Unit can have several Inventory Organizations — three warehouses under one selling entity, each tracking its own stock.

The item master is itself an inventory organization, conventionally a dedicated one holding no stock. Items are defined there and assigned to the organisations that use them.

    Master Org  item ABC123 defined -- description, UOM, category
      -> assigned to Warehouse Mumbai   (own status, own cost)
      -> assigned to Warehouse Chennai  (own status, own cost)

Which brings the subtlety that catches people: attribute control level. Every item attribute is controlled either at master level or at organisation level.

    Master level   change it once, it applies everywhere
    Org level      each organisation has its own value

Change an org-level attribute in the master organisation and the child organisations keep their own values. The change appears to have been made and nothing downstream sees it.

That control level is set per attribute and is not obvious from the form, which is why "I changed it and nothing happened" is a recurring EBS item question.

Item templates pre-populate the dozens of attributes across purchasing, inventory, order management and costing. Creating an item without one means setting them by hand and getting some wrong, which surfaces later as an item that cannot be purchased or cannot be sold.

Categories and category sets group items for reporting, costing and rules. An item belongs to one category within each category set, and different functions use different sets — so the same item is in a purchasing category and an inventory category simultaneously.

Why the structure is decided first. Organisation structure determines what MOAC secures, how costing rolls up, which HR rules apply, and how inventory is tracked. Changing it after transactions exist means migrating data across boundaries, which is why it is designed up front and rarely revisited.

What the interviewer is probing.1. "What is the organisation hierarchy in inventory?" Probing: the structure. Stalls: "Warehouses." Moves up: business group, ledger, legal entity, operating unit and inventory organisation — with the item master organisation defining items centrally.

2. "What is the item master organisation?" Probing: the key concept. Stalls: "The main warehouse." Moves up: the one where items are defined and from which they are assigned to other organisations — it typically holds no stock.

3. "What are item attributes controlled at?" Probing: the detail. Stalls: "The item." *Moves up:* master or organisation level depending on the attribute, which is why an item can be purchasable in one org and not another.

4. "What is an item template for?" Probing: the practical answer. Stalls: "Nothing." *Moves up:* applying a consistent set of attributes on creation, so item setup is repeatable rather than manual.