
After completing this lesson, you will be able to:
Data needs to be replicated regularly from a source system such as SAP S/4HANA or SAP ECC to SAP Responsible Design and Production. The following object types need to be replicated:
All the public interfaces can be found on the SAP API Hub Responsible Design and Production
SAP API Hub Responsible Design and Production
What needs to be done?
For the replication documentation, refer to the following SAP help pages:
Push Replication See help documentation for sending packaging data from SAP S/4HANA to RDP.
Setting up the replication services in BTP Cloud Cockpit
Follow these steps to set up the replication services
The clientId and the clientSecret that are received from the cloud service need to be used on the sender side to establish the connection.
Setting up the replication services in SAP S/4HANA
Follow these steps to set up the replication destinations.
To establish the connection, use the above retrieved clientId and clientSecret.
Documentation for the REST interfaces can be found here: SAP API Hub Responsible Design and Production
To replicate data using the Push interfaces data has to be extracted and send to RDP through REST.
For objects that are needed for the calculations and analytics in RDP, there are no standard extractors provided by SAP RDP. SAP Value Prototype team offers some extractors that can be transported into an ECC or S4 system for releases prior to S/4 2021 FPS1. These extractors offer an easy way to send the data from an SAP system to RDP.
For those who do not want to leverage the provided extractors or who need to integrate a non SAP system, SAP offers an API to implement own extractors.
The API interfaces are described here.
The mapping of the ECC / S4 data to the RDP properties is described here.
The provided Acceleration Package offers extractors for all needed business objects. The offered filters can be used to limit the amount of replicated data and to tailor the data to your needs. Test run and delta replication are also part of the offered solution - see the figure, Extracting Master and Transactional Data.
For packaging data SAP provides extractors for packaging data that is stored in PLM and/or in Recipe Management (RM). SAP has defined the way how the packaging data shall be structured as characteristics in PLM so it can be consumed easily by the provided extractors.
Nevertheless, as a standard entity for packaging elements and packaging composition is missing, the customer has to adapt the mapping of the S/4 data to the API. A detail description is provided with the BAdIs for each extractor.
The default extractors for extracting packaging data are shipped first with S/4 2021 FPS1.
For customers that need extractors for earlier releases, SAP Value Prototype team offers extractors that can be transported into an ECC or S4 system for releases prior to S/4 2021 FPS1. These extractors offer an easy way to send the data from an SAP system to RDP.
SAP provides for this a report and a BAdI. Documentation is given here:
The documentation of the BAdI can be found as technical documentation within the S/4 system
SAP provides for this a report and a BAdI. Documentation is given here:
The documentation of the BAdI can be found as technical documentation within the S/4 system.
SAP provides for this a report and a BAdI. Documentation is given here:
For more information, see Setting up System and Replication.