Oracle SCM Cloud: Planning Foundation — Lesson 2: Items, Organizations, Calendars, Measures, and Hierarchies

Technical Scope

• items, item organizations, categories, catalogs, lifecycle, and planning attributes
• organization networks, suppliers, customers, locations, and sourcing relationships
• calendars, time levels, hierarchies, measures, aggregation, and disaggregation
• data-security context, missing members, inconsistent hierarchies, and correction

Instructor Demonstration

The instructor models items, item organizations, categories, catalogs, lifecycle, and planning attributes, then connects it to organization networks, suppliers, customers, locations, and sourcing relationships. The demonstration captures the exact configuration, transaction, command, query, log, or screen evidence needed to prove intended behavior and the applicable control boundary.

Applied Workshop

Learners execute a guided lab focused on organization networks, suppliers, customers, locations, and sourcing relationships and calendars, time levels, hierarchies, measures, aggregation, and disaggregation. The exercise introduces a realistic exception related to data-security context, missing members, inconsistent hierarchies, and correction and requires a reversible correction supported by before-and-after evidence.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration or analysis and record exact steps.
3. Validate functional behavior, security, data integrity, and operational observability.
4. Introduce the defined failure condition, diagnose the cause, and apply a safe correction.
5. Document rollback, acceptance evidence, unresolved risk, and ownership.

Validation Standard

Acceptance requires accurate handling of calendars, time levels, hierarchies, measures, aggregation, and disaggregation, traceable proof for items, item organizations, categories, catalogs, lifecycle, and planning attributes, and a repeatable recovery path for data-security context, missing members, inconsistent hierarchies, and correction. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when data-security context, missing members, inconsistent hierarchies, and correction occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested items, organizations, calendars, measures, and hierarchies implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.