12/4/2023

User Guide
Generated on: 2023-12-04 05:01:59 GMT+0000

SAP Responsible Design and Production | latest

PUBLIC

Original content: https://help.sap.com/docs/SAP_RESPONSIBLE_DESIGN_AND_PRODUCTION/01d581e7150c42f59b5234a76f5e8d2d?

locale=en-US&state=PRODUCTION&version=latest

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product documentation. The
information included in custom documentation may not re ect the arrangement of topics in the SAP Help Portal, and may be missing important
aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 12/4/2023

Push Replication
SAP Responsible Design and Production provides a public API for data replication. To be able to push data from your system, you need to get the
credentials, access the API, and con gure the replication in SAP Responsible Design and Production. The instructions below apply if you want to
replicate packaging elements or packaging compositions from an SAP S/4HANA system.

Prerequisites
The getting started prerequisites are ful lled and you are subscribed to the service SAP Responsible Design and Production. A service
instance is created with the scope data-replicate. See Initial Setup.

The source system has REST capability.

Standard integration is provided for SAP S/4HANA 2021 SP01 or higher. See also Overview: Supported Integration Features

Overview
To be able to push data to SAP Responsible Design and Production, all of the following tasks must be done:

1. Setting Up Replication Services

2. Setting Up SAP S/4HANA Destinations

3. Setting Up System and Replication

4. Preparing and Sending Data in SAP S/4HANA

Restrictions

 Restriction
Maximum 2000 Data Records per Package

If many data records are sent via the push API to SAP Responsible Design and Production, the processing must be done in packages (batch
requests) until all data records are transferred. You con gure how many data records are include in a single package. The maximum data
records in a package is 2000. This is true for each object type, for example packaging compositions, material documents, and so on.

Example: You have de ned a package (batch request) size of 1000 and in a replication execution 5500 data records shall be replicated. The
data records are organized in packages and 6 packages are sent to cover the 5500 data records.

 Restriction
Uncompressed request payload size not more than 50 MB

For uncompressed requests the payload size limit is 50 MB. For compressed requests the limit is not more than 50 MB of payload size after
the extraction.

Recommendation

For deliveries it is recommended to send not more than 1000 objects per batch.

For products it is recommended to send not more than 500 objects per batch.

 Note
It is possible that data that is pushed is not immediately visible in the applications. Push replication is an asynchronous process.

Setting Up Replication Services

SAP Responsible Design and Production provides a public API for data replication. To be able to push data from your system, you need to get the
credentials, access the API, and con gure the replication in SAP Responsible Design and Production. Make sure the setup is done according to

This is custom documentation. For more information, please visit the SAP Help Portal 2
 12/4/2023
the instructions. See Initial Setup.

API Documentation
To access the API documentation, go to SAP Business Accelerator Hub .

For more information on the API elements, see Data Structure.

Setting Up SAP S/4HANA Destinations

Setup the authentication and the RFC destinations in SAP S/4HANA. For instructions, see Con guring Authentication and RFC Destination.

Prerequisites
Authorizations for the following transactions:

SM59 to create an RFC destination

OA2C_CONFIG to con gure the OAuth 2.0 client

Authorizations to de ne and use an OAuth 2.0 con guration. Adhere to the prerequisites listed here:
https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_752/916a7da9481e4265809f28010a113a6a/6f679081b5444f91bf68e600025c2cf6.html.

S_DEVELOP and S_OA2C_ADM for the de nition

S_OA2C_USE for the use

Credentials of the SAP BTP tenant of the SAP Responsible Design and Production API. You need the clientid, the clientsecret, and the
url.

Prepare Con guration Values

Using the credentials that you received when you followed the getting started instructions, you can derive token endpoint, authorization
endpoint, and target host. For examples, see the table below.

Example

Parameters Example Values

Client ID sb-x0000000-0x00-0000-x000-
xxxxxxxxxxxxxxxxxxx|smrdp!b3480

Client secret xxxxxxxxxxxxxxxxxxxxxxxxxxxx

URL https://<subaccount-subdomain>.eu20.hana.ondemand.com

Token endpoint <subaccount-

subdomain>.eu20.hana.ondemand.com/oauth/token

Authorization endpoint <subaccount-

subdomain>.eu20.hana.ondemand.com/oauth/token/authorize

Target host <subaccount-subdomain>.eu20.ce.sustainability.cloud.sap

Port 443

Path pre x /api/replication/v1

Create and Con gure the OAuth 2.0 Client

Con gure your OAuth 2.0 client.

1. To create an OAuth 2.0 Client Pro le in the customer namespace, open transaction SE80.

2. In the context menu of a package where you are authorized to create new development objects, choose Create > Others > OAuth 2.0
Client Pro le. Enter the following values:
This is custom documentation. For more information, please visit the SAP Help Portal 3
 12/4/2023
Name: ZSURDP_REPL_API

Type: DEFAULT

3. Choose Save.

4. Start transaction OA2C_CONFIG (OAuth 2.0 Client Con guration).

5. Choose Create and enter the following values:

OAuth 2.0 Client Pro le: ZSURDP_REPL_API

Con guration Name: RDP_REPL_API_INTEG_S4

OAuth 2.0 Client ID: Enter the clientid.

Choose OK.

6. On the Administration tab, enter the clientsecret.

7. Under Authorization Server Settings, enter the URL for the token endpoint. For example, <authorization endpoint
URL>/oauth/token/authorize and <token endpoint URL>/oauth/token.

8. Under Access Settings, select the following data:

Client Authentication: Basic

Resource Access Authentication: Header Field

Selected Grant Type: Client Credentials

Note that the proxy settings must be con gured beforehand.

9. Save your entries.

Open this video in a new window

Con gure the RFC Destination

To create a new RFC destination, carry out the following steps:

1. Open transaction SM59

2. Choose Create.

3. Enter a name for the RFC destination. As default use RDP_REPL_API

4. Select connection type G (HTTP Connection to External Server).

5. On the Technical Settings tab, enter the following data:

Target Host: The application endpoint URL. The target host looks like this: <subaccount-
subdomain>.eu20.ce.sustainability.cloud.sap

Port: 443

This is custom documentation. For more information, please visit the SAP Help Portal 4
 12/4/2023
Path Pre x: /api/replication/v1

Don't use a trailing / when entering the path pre x.

6. On the Logon & Security tab

Set Do not use a user.

Set SSL to Active.

Set Do Not Use Certi cate for Logon.

7. Select OAuth Settings.

8. Con guration: RDP_REPL_API_INTEG_S4

9. Save your entries.

Open this video in a new window

Setting Up System and Replication

Follow the instructions below to con gure the source systems and object types for the data replication.

1. Go to the SAP Fiori launchpad and choose the Con guration Cockpit.

2. Go to the Source Systems tab and create the source systems.

 Note
You cannot delete or edit source systems after you created them.

3. Go to the Replications tab and con gure the replications.

 Note
Only one replication con guration can be created for the object types con guration data, organization data, packaging composition,
and packaging element. There is no restriction for the other object types.

4. In the Replications tab, you can monitor the status of the replication.

This is custom documentation. For more information, please visit the SAP Help Portal 5
 12/4/2023

Open this video in a new window

Preparing and Sending Data in SAP S/4HANA

There are different use cases for the upload of packaging elements and packaging compositions from SAP S/4HANA. For instructions, see the
links below.

Uploading Packaging Elements from Product Lifecycle Management

Uploading Packaging Compositions from Product Lifecycle Management

Uploading Packaging Compositions from Recipe Management

Uploading Packaging Compositions from Bills of Material

This is custom documentation. For more information, please visit the SAP Help Portal 6