# Oracle Fusion Inventory Organization Design Worksheet > Source: https://netray.co/tools/oracle-fusion-inventory-organization-design-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Lay out inventory organizations, subinventories and locators with their purpose, ownership and counts before configuring them. ## Category oracle ## Erp Oracle Fusion Cloud SCM ## Audience - Oracle Cloud consultant - Inventory manager - Solution architect ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Inventory org **Key:** org **Type:** text #### Subinventory **Key:** subinv **Type:** text #### Purpose **Key:** purpose **Type:** select **Options:** - Raw material - WIP staging - Finished goods - Quarantine - Scrap - Consignment - Tools and spares #### Nettable **Key:** nettable **Type:** select **Options:** - Yes - No #### Locator control **Key:** locator **Type:** select **Options:** - None - Prespecified - Dynamic #### Locators **Key:** locators **Type:** number #### Active items stocked **Key:** items **Type:** number #### Items per locator **Key:** per_loc **Type:** number **Expr:** items / locators **Format:** decimal #### Owner **Key:** owner **Type:** text **Rows:** **Org:** PLT1 **Subinv:** RM-MAIN **Purpose:** Raw material **Nettable:** Yes **Locator:** Prespecified **Locators:** 420 **Items:** 3100 **Owner:** Stores **Org:** PLT1 **Subinv:** WIP-STG **Purpose:** WIP staging **Nettable:** No **Locator:** None **Locators:** 1 **Items:** 900 **Owner:** Production **Org:** PLT1 **Subinv:** FG-MAIN **Purpose:** Finished goods **Nettable:** Yes **Locator:** Prespecified **Locators:** 260 **Items:** 640 **Owner:** Shipping **Org:** PLT1 **Subinv:** QUAR **Purpose:** Quarantine **Nettable:** No **Locator:** None **Locators:** 1 **Items:** 120 **Owner:** Quality **Org:** PLT1 **Subinv:** SCRAP **Purpose:** Scrap **Nettable:** No **Locator:** None **Locators:** 1 **Items:** 75 **Owner:** Quality **Totals:** #### Total locators **Key:** locators **Agg:** sum **Format:** integer #### Total item stocking records **Key:** items **Agg:** sum **Format:** integer #### Subinventories **Key:** subinv **Agg:** count **Format:** integer **Summary:** #### Average items per locator **Key:** avg_ipl **Expr:** sum_items / sum_locators **Format:** decimal **Notes:** Item counts are stocking records and an item can appear in more than one subinventory. Names and controls must be checked against your own Inventory Management setup. ## Content **Intro:** Inventory structure is hard to change after transactions exist. This worksheet lets the design team agree the organizations, subinventories and locators on paper first and see how dense the storage plan is. **Sections:** #### How to use it **Body:** Add a row for each subinventory you intend to create and tag it with its purpose and its inventory organization. Decide whether it is nettable, meaning on-hand quantity counts as available supply in planning, and whether locators are required. Enter the number of locators and the active items stocked there. The sheet calculates items per locator so you can spot a subinventory that is over or under structured. #### Design principles **Body:** Create a subinventory when the physical, financial or planning treatment differs. Do not create one per shelf, because locators handle that. Keep quarantine, scrap and consignment separate so availability, costing and ownership stay clean. Be deliberate about nettable flags, since a wrongly nettable quarantine area inflates supply and starves purchasing. **Bullets:** - One purpose per subinventory - Locators for position, not purpose - Check the nettable flag against planning - Name owners for count accountability #### Reading the density **Body:** A very high number of items per locator suggests mixed bins and slow picks, while a very low number may mean you are over engineering locators and creating maintenance work. There is no right number, since it depends on part size and handling. Use it to start a conversation with the warehouse team, then adjust. #### Common mistakes **Body:** Copying the legacy ERP stockroom list without questioning it, mixing financial ownership with physical location, and enabling locator control everywhere. Locator control adds a field to every transaction, so only use it where position matters. Also confirm the interaction with costing, since cost organizations and inventory organizations follow business rules. **Cta:** If you are consolidating warehouses from a legacy ERP into Oracle Fusion, we can help analyse stockrooms and transactions to inform this design. **Faq:** #### What is an inventory organization? **Answer:** It is the unit that holds item stock, subinventories and transactions for a physical site or logical grouping, and it links to a business unit, legal entity and location. Its setup affects costing, planning and manufacturing. #### When should a subinventory be non-nettable? **Answer:** When stock there should not count as available supply to planning or order promising, such as quarantine, scrap, or demonstration stock. Make the decision with the planning team, not only the warehouse. #### Do I need locators? **Answer:** Only if you need to know where stock sits inside a subinventory. Large stores with many bins usually do. Small or high turnover areas often do not, and the extra step can slow transactions. #### Can I change the design later? **Answer:** Some attributes can be changed with care, but structural changes after transactions exist are costly and carry audit consequences. Take the time to agree the design before go-live. ## Search terms oracle fusion inventory organization design, oracle cloud subinventory design, oracle fusion inventory org template, warehouse structure design worksheet, oracle fusion locator design, inventory organization setup oracle cloud, oracle fusion storage location planning --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json