Skip to Content
SAP Integrated Business Planning for Supply Chain

S&OP Landscape Configuration during Implementation


The purpose of this document is to detail the suggested approach for implemenation when using Multiple S&OP Systems.

Pre Requisites

This document assumes a 2 system landscape with production and test S&OP system hosted by SAP Cloud although these guidelines are equalliy applicable for On premise deployments. It is strongly advised that all customers purchase an S&OP Test system. If the customer plans to do any performance testing or maintain a large historical dataset in their test environment it is recomended that the customer pruchase a test system which is the same size as their production system. If the intended use of test does not include either of these cases a standard sized test system of 144 GB should be sufficient.

The S&OP Operations team will provision both production and test systems for the customer. It takes a minimum of 10 business days to prepare the systems. This includes the provisioning of Hana Cloud Integration (HCI) as well as intgration to SAP JAM if a Jam subscription has been purchased.


Test System

  • The test tenant will be provisioned with our standard demo content to support implmentation teamĀ  with jam and HCI configuration. The implmentation team should conduct blueprint workshop using this system.
  • After blueprinting all configuration should me made on the test system and data loaded
  • Implmentation team should then conduct unit testing of the model configuration as well as data load configuration.

Production System

  • In parallel the implementation team should build the production system with JAM and HCI configurations, create necessary users, roles and visibility filters as well as build out necessary Process Templates.
  • Once Unit Tests on Test System configuration are completed migrate configuration from test to production. S&OP Support team can assist with this migration.
  • Load historical data and production data
  • Request SAP Clould Operations team to take a snapshot of production system
  • Conduct all UAT on the Production Environment
  • Once UAT is complete and customer has signed off reset the production system to the earlier snapshot and reset the test system to that same snapshot to build a test environemtnt hat reflects the state of production at Go Live.
  • Go live

No comments