During Cloud Inventory implementation your customer requires you to enable the Oracle Transactional Business Intelligence (OTBI) KPI to review the list of standard reports which is useful for their…

Question

Options

• ALogistics Business Intelligence Analytics is enabled.
• BLogistics Business Intelligence Analytics is not implemented.
• COrganization is not enabled for warehousing.
• DData permissions for the organization being referenced are not set up.
• ESupply Chain and Order Management Business Intelligence Analytics is not enabled.

Explanation

C and D are the two correct answers.

Why C is correct: If the organization is not enabled for warehousing in Oracle Cloud Inventory setup, the warehouse dashboard has no valid warehouse context to pull KPI data from - the watchlist simply won't appear because the system doesn't recognize the org as a warehousing entity.

Why D is correct: Even if the org is properly enabled, OTBI KPI watchlists are data-security-driven. Without data permissions configured for that specific organization, the user has no access to the underlying inventory data the KPIs depend on, resulting in a blank watchlist.

Why the distractors are wrong:

• A is wrong because Logistics BI Analytics being enabled is a positive condition, not a cause of failure.
• B (Logistics BI Analytics not implemented) is a plausible trap, but the question is specifically about OTBI KPIs and warehouse dashboard visibility - a missing Logistics BI module doesn't directly control whether OTBI watchlists render.
• E (Supply Chain and Order Management BI not enabled) refers to a separate analytics module that doesn't govern the warehouse dashboard KPI watchlist display.

Memory tip: Think "setup before data" - the org must be structurally enabled for warehousing (C) and permissioned for data access (D). Both are prerequisites at different layers (configuration vs. security) before any KPI watchlist can render.

No community discussion yet for this question.