What is the Blue Yonder Enterprise Knowledge Base (EKB)?

The Blue Yonder Enterprise Knowledge Base (EKB)—historically known as the SCPO Database or SCPO Schema—is the centralized relational database and data management layer that serves as the "Single Source of Truth" for the core Supply Chain Planning applications (Demand, Fulfillment, and Master Planning), storing all master data, transaction history, and planning hierarchies in a unified structure.

While the Category Knowledge Base (CKB) powers the retail side (Planograms), the Enterprise Knowledge Base (EKB) powers the industrial side (Supply Chain). It is the backbone of the SCPO (Supply Chain Planning & Optimization) suite. It is not just a storage bucket; it is a sophisticated logic engine that understands the complex relationships between products, locations, and time. It ensures that when the "Demand Planner" forecasts a sale in Cases, the "Fulfillment Planner" instantly sees the requirement in Pallets, handling the conversion and synchronization automatically.

Why It Matters: The "Rosetta Stone" of Planning

Supply chains speak many languages. The ERP speaks "Finance," the Warehouse speaks "Logistics," and Sales speaks "Revenue." The EKB translates them all.

• Hierarchy Management: It is the master of "Roll-ups." It understands that SKU A belongs to Brand B, which belongs to Category C. If you change the hierarchy (e.g., move a product to a new brand), the EKB automatically restates history so you can compare "Apples to Apples" year-over-year.
• Data Integrity: It enforces rules. You cannot plan a shipment for a product that doesn't exist. The EKB rejects "dirty data" from the ERP before it corrupts the plan, ensuring the planners are working with clean numbers.
• Scenario Partitioning: It allows for "What-If" planning. The EKB can store multiple versions of the truth simultaneously—Live Plan, Optimistic Plan, Pessimistic Plan—without them overwriting each other, allowing executives to compare scenarios side-by-side.

Key Capabilities

1. Unified Data Model (UDM): The schema is pre-built for supply chain. It has standard tables for SKU, Loc, Sourcing Network, Calendar, and Price. You don't have to build the database from scratch; you populate the standard tables, and the applications (Demand, Fulfillment) automatically know how to read them.
2. Mass Maintenance: It includes tools for bulk editing. A planner can execute a query to "Increase safety stock by 5% for all hazardous materials in the Northeast Region," and the EKB updates thousands of records instantly.
3. Integration Staging (OINT): It features a dedicated "Staging Layer" for incoming data. Data from SAP or Oracle lands here first, is validated/cleansed, and then promoted to the live tables, protecting the active plan from bad integration loads.
4. Security & Permissions: It manages "Who sees What." It ensures that the European Planner can only read/write data for European locations, even though the database holds the global dataset.

The Blue Yonder Difference

Blue Yonder differentiates the EKB through its Performance at Scale. Supply chain data is massive (Billions of rows: Every SKU x Every Store x Every Day). General-purpose databases often choke on this volume during complex calculations. The EKB is indexed and tuned specifically for Time-Series and Matrix operations, allowing it to aggregate millions of forecast records in seconds to support real-time planning sessions.