nerdexam
Oracle

1Z0-900 · Question #133

As part of implementing Oracle Cloud for your customer, you defined multiple Business Units. The customer wants you to define an Inventory Organization that is associated with all the business units…

The correct answer is D. It is not possible to define an Inventory Organization that is associated with more than one. In Oracle Cloud, every Inventory Organization must be associated with exactly one Business Unit - this is a fundamental architectural constraint of the data model, not a configuration choice. There is no mechanism to link a single Inventory Organization to multiple Business…

Understand Java EE Architecture

Question

As part of implementing Oracle Cloud for your customer, you defined multiple Business Units. The customer wants you to define an Inventory Organization that is associated with all the business units and not just one particular business unit. How do you achieve this?

Options

  • ADefine the Inventory Organization without associating it with any location.
  • BLeave the Management Business Unit field blank in the Inventory Organization definition.
  • CLeave the Profit Center Business Unit field blank in the Inventory Organization definition.
  • DIt is not possible to define an Inventory Organization that is associated with more than one

How the community answered

(46 responses)
  • A
    4% (2)
  • B
    2% (1)
  • D
    93% (43)

Explanation

In Oracle Cloud, every Inventory Organization must be associated with exactly one Business Unit - this is a fundamental architectural constraint of the data model, not a configuration choice. There is no mechanism to link a single Inventory Organization to multiple Business Units simultaneously; if you need items/inventory accessible across multiple Business Units, the standard approach is to define separate Inventory Organizations per Business Unit or use cross-referencing features.

Why the distractors are wrong:

  • A is wrong because location association is independent of Business Unit association - omitting a location doesn't change the one-to-one BU constraint.
  • B is wrong because the Management Business Unit field serves a specific ledger/reporting purpose; leaving it blank doesn't make the org available to all BUs, it simply leaves a required or functional field empty, which may cause setup errors.
  • C is wrong because the Profit Center Business Unit drives financial reporting (P&L), not the org's availability to multiple BUs - blanking it affects costing/reporting, not multi-BU access.

Memory tip: Think of an Inventory Organization as a physical warehouse - a warehouse belongs to one company division (Business Unit). You wouldn't say a warehouse belongs to "all divisions at once"; instead, you'd create separate warehouses per division. One Org = One BU, always.

Topics

#Oracle Cloud#Inventory Organization#Business Units#System Constraints

Community Discussion

No community discussion yet for this question.

Full 1Z0-900 Practice