Commodity hierarchy for Commodity Domain (Custom): parent (level 2-4) has only partially correct hierarchy

1. Ensure correct pre-conditions:

a. No Commodity Code has

(1) duplicate Commodity Code or

(2) duplicate Commodity Name.

b. Commodity Code Status: ensure Commodity Code in Status (Inactive) is clearly differentiated from Commodity Code in Status (Active).

Example for Commodity Code in Status (Inactive):

Name:

legacy

Do not Use

Used until Date DD-MM-YYYY

2. See the levels and hierarchy available of Commodity Code in menu on Realm level (S4):

Administration -> Reporting Manager -> Facts and Dimensions -> Dimensions -> Commodity

3. ALL Commodity Codes for deployed Custom Commodity Domain has highest class (All), i.e. all Commodity Codes roll up to ultimate top level.

4. Ensure correct hierarchy mapping for all Commodity Codes:

1. All Commodity Codes must have parent Commodity Code.
2. Ensure hierarchy levels are consistently mapped for each level applied in the Custom Commodity Domain.

Example for total hierarchy Levels (3):

Level 1: Commodity ID (A)' -> has Parent ID (B)

Level 2: Commodity ID (B) -> has Parent ID (C)

Level 3: Commodity ID (C) -> has Parent ID (All)

5. Catalog Reporting for Part ID/Name applied for Operational Procurement Facts (Requisition, PO, Invoice):

Ensure applied Commodity Domain (Custom) is mapped consistently to standard Commodity Domain (UNSPSC) as applied by Supplier for the particular Part ID.

Transaction Module:

Menu: Commodity Code Manager

Invoicing > Analysis Reporting for Invoicing
Spend Visibility
Strategic Contracts > Analysis Reporting for Strategic Contracts
Strategic Sourcing > Analysis Reporting for Strategic Sourcing
Supplier Lifecycle & Performance > Analysis Reporting for SLPM