A Handy Guide on Getting Started
Using SDI to load Master and Transactional data from SAP S/4 Hana or SAP ERP to IBP Order-Based Planning is still a relatively new concept that not many companies have implemented yet. So, for those attempting to walk down this path, here are a few tips and checks that may guide you. For the sake of this blog we are going to assume the source is SAP ERP, however the same tips/checks apply to S/4 Hana also.
First tip when starting IBP Order-Based Project is to figure out what IBP version to use (either the current IBP version or an upcoming new release of IBP). The IBP version you decide upon will determine the SAP ERP Supply Chain Integration IBP Add-on version that needs to be installed in the source system. For instance, using IBP version 2002 requires the SAP ERP Supply Chain Integration Add-on for IBP 1.1 SP12 version to be installed in the source SAP ERP system. Installing the IBP Add-on is not always sufficient as there are also recent SAP Notes that may need to be applied (see SAP Help for further details).
Second tip, if you encounter any authorization errors when trying to access any of the IBP Integration Model Transaction Codes, it’s always a good idea to check in case you are missing some SAP Notes that need to be applied as I found out. (Applying SAP Note 2746103 and SAP Note 2727275 did the trick for us). This is typically performed by the Basis team/resource but doesn’t hurt to have some knowledge of this also.
Next tip, I found out the hard way through a process of trial and error that deleting/purging Master and Transactional data within Order-Based Planning Area actually requires you to first delete/purge those same records from the Source System (in our case SAP ERP) IBP staging tables beforehand. This is a result of the tight coupling that exists between OBP and the IBP staging tables. To delete all the Master and Transactional Data from the IBP staging table in SAP ERP, run Transaction Code IBP/ECC_DEL_ALL with Deletion Mode selected for all the objects across the 3 different tabs for Location, Work Center and Material-Dependent Objects.
Also, do not dismiss SAP’s recommendation to create a separate Integration Profile for use within Order-Based Planning Area.
The Integration Profile as depicted in the IBP Order Series Integration Flow diagram above is assigned/associated with the Master Data Type and Order Based Planning Area as part of the configuration steps for loading data from one or more Source Systems.
If you need to use the File Adapter to load data from a Non-SAP Source to OBP, watch out for Master and Transactional Attribute strict format checks. Attributes that are numeric/decimal format are required to have a default value of 0. The Geolocation Latitude and Longitude attributes of the Location file (IBP_LOCATION__XX1.csv) need to have a format type example: 20.000000000000. (Refer to the SAP Help Guide for a list of mandatory attributes for Master and Transactional DataTypes).
The ABAP Adapter handles a lot of the attribute checks for you and any data related errors that appear via the Application Log in IBP are easy to decipher. Attribute check related errors can be resolved with the use of a custom BAdI which are specific according to the Master or Transactional Data Type in Source SAP ERP or S/4 Hana System. In our case the attribute NodeType in the /IBP/LOC_EXT table had invalid entries (SAP requires ‘PL’ or Plant, ’DC’ for Distribution Center or blank for Customers only). Applying ABAP code to the custom BAdI – /IBP/ECC_SAVE_LOCATION so the invalid entries could be modified to valid entries before being loaded to the /IBP/LOC_EXT Location Staging table resolved this issue.
My key takeaway from integrating data using SDI from the Source System into Order-Based Planning System is to not underestimate the tight coupling between the systems as designed by SAP to ensure data integrity and conformity.