12/4/2023

User Guide
Generated on: 2023-12-04 05:01:03 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

Data Import Through File Upload

Provide the following data by lling out the respective spreadsheets and upload them in the order shown below to work with
SAP Responsible Design and Production.

To download template les, go to the Import Data application and choose Upload File. A dialog opens where a download link is
available per object type.

 Tip
When you upload a le, it is validated, and log messages provide information about detected data issues. To be able to
generate a correct report, these issues need to be resolved in your source system or in the upload les.

An ID is provided at the top of the log. If you cannot resolve an issue yourself, create a ticket on the SUS-RDP component by
using your support launchpad and provide the ID in the ticket: https://launchpad.support.sap.com/ .

The log is limited to 1.000 messages. If you receive such a high number of errors, try the following actions:

Make sure to download the templates from the Import Data application.

Consider the steps in the checklist: Checklist for the File Upload.

Rebuild your upload le from scratch.

Files should be uploaded in the sequence listed below to avoid issues with the data.

1. Con guration data (Template: ConfigurationData_Template.xlsx). Use this template to import basic
con gurational data. The data that is entered in this le is a prerequisite for the following les during data load. For
example, only units of measure that are de ned here, can be used in the load les.

2. Organization data (Template: OrganizationData_Template.xlsx). Use this template to import data about the
company structure.

3. Customers and customer extensions (Templates: Customer_Template.xlsx and

CustomerExtension_Template.xlsx). Use this template to import customer data.

4. Suppliers (Template: Supplier_Template.xlsx). Use this template to provide information about suppliers.

5. Products and product extensions (Templates: Product_Template.xlsx and

ProductExtension_Template.xlsx). Every unit of measure that is used in your product data must be provided in
this le. There are two elds for this purpose, Base Unit of Measure in the Product sheet and Alternative
Unit of Measure in the ProductUoM sheet. The Base Unit of Measure must also be listed in the ProductUoM
sheet with value 1 for both Quantity Numerator and Quantity Denominator.

6. Deliveries (Template: Delivery_Template.xlsx). Use this template to provide information about deliveries.

 Note
Make sure that the deliveries that you import are outbound only and re ect sales activities for customers.

7. Material documents (Template: MaterialDocument_Template.xlsx). Use this template to provide information

about material documents. The material documents are classi ed for speci c logistic processes. Each sheet represents
a different logistic process. The attributes in all sheets are identical.

Use this template exclusively for low volumes of data. For all other cases, use the push data replication.

8. Inventory (Template: Inventory_Template.xlsx)

9. Packaging elements (Template: PackagingElement_Template.xlsx). Use this template to provide data for
packaging elements that that can be assigned to a packaging composition.

This is custom documentation. For more information, please visit the SAP Help Portal 2
 12/4/2023
10. Packaging compositions (Template: PackagingComposition_Template.xlsx). You can also maintain the packaging
compositions manually in the Packaging Compositions application. Use this template to provide the packaging
information of your product.

 Note
The behavior of the data import for packaging elements is different for packaging elements that have been manually
added to a packaging composition in the Packaging Compositions application. These packaging elements are not
deleted by the data import, but updated in the packaging composition. See also Behavior of the Data Import.

11. Batches (Template: Batch_Template.xlsx)

12. Incoterms (Template: Incoterms_Template.xlsx)

13. Packaging Composition - Additional Items (Template: PackagingCompositionItems_Template.xlsx)

Related Information
Behavior of the Data Import
Spreadsheets
Format
Common Elements
Checklist for the File Upload

Behavior of the Data Import

If data already exists in the system, the system handles con guration and organization data differently from the other object
types.

For con guration and organization data, a new import will overwrite and delete the existing data.

Data replication has priority over data import. Data import has priority over manual maintenance in SAP Responsible
Design and Production applications.

If the source of an ID is data replication, the data import will fail for this ID because data replication has priority
over data import.

If the source of an ID is manual maintenance or data import, all existing data for this ID will be deleted and
replaced by the data in the import le.

For packaging compositions, an exception exists. See Packaging Compositions

 Note
The calculated report data and the packaging fees are rounded using three decimal places for each basic material fraction.
However, the data inserted in the spreadsheet is rounded using four decimal places. The different rounding rules can cause
differences in the calculated data and the data entered in the spreadsheet.

Spreadsheets
Consider the following conditions and limitations:

The le format is Microsoft Excel (XLSX).

Note: Make sure to not change the cell format. If you need to copy and paste, then we suggest pasting values only.

Note: Don't change the ve header lines.

Note: Some of the les contain code lists. Don't change the code lists. If you require customized codes, please get in
touch with your SAP contact.

This is custom documentation. For more information, please visit the SAP Help Portal 3
 12/4/2023
Note: The maximum le size for a le that is to be uploaded is 25 MB. In case you need to split your le, make sure that
the split is done at the correct rows for all related tabs accordingly. For example, when you load more than one le for
deliveries, make sure to do the split in both tabs (Delivery and DeliveryItem) at the same place, at the same
delivery ID. When you need to split the le for products, make the split in each tab at the same product ID.

Column B:

The system can handle empty rows as described below but it is not recommended to have a higher number of
empty rows in the les.

Rows that only contain spaces are interpreted as empty and are skipped. That means, that the system goes to
the next row in this case. This is applied for sequences of less than 10 empty rows.

10 empty rows in sequence are interpreted as table end. If 10 empty rows are detected, the system stops reading
and goes to the next sheet.

The overall number of empty rows that were detected is prompted in the log messages. For example, if there are
5 empty rows in different places in the le, then all of them are skipped and summed up in the log message.

Format
Dates: Dates are converted to text when the le is uploaded. Different formats are supported:

MM-DD-YYYY. Example: 12-21-2020.

Day, Month, DD YY. Example: Wednesday, April 19, 2023

Time: HH24:MI:SS

Numbers: Numbers are converted to text when the le is uploaded.

Separators: The decimal separator is a period (.), for example 1122.33.

Booleans: true, false, or empty (=NULL)

Common Elements
This section describes the common characteristics of the templates.

Example template

Rows
Description: Identi es the column

Internal name: The name of the object that is used by SAP Responsible Design and Production

Data Type: De nes the expected data type and maximum eld length

Mandatory: De nes whether the column must be lled or is optional for the data load. Note: For some EPR reports
optional elds might be required

SAP S/4HANA Attribute: The name of the table eld in SAP S/4HANA that supplies the information

Sample Value, remove: A sample value. Remove the sample value before you ll in your own data

Color Codes
Orange: Key elds are marked in orange color. They are always mandatory. Data must be provided here to have valid
import

Grey: Grey elds can be optional or mandatory

This is custom documentation. For more information, please visit the SAP Help Portal 4
 12/4/2023
Blue: Marks the eld in SAP S/4HANA that provides the attribute value for the column

White: The elds where you enter the data

Checklist for the File Upload

Before you upload les to SAP Responsible Design and Production, check if the conditions in this list are ful lled. If one of the
conditions is not ful lled, the import will fail.

Adhere to the proper upload order. See Data Import Through File Upload.

The le size does not exceed 25 MB.

In case you need to split your le, make sure that the split is done at the correct rows for all related tabs accordingly. For
example, when you load more than one le for deliveries make sure to do the split in both tabs (Delivery and
DeliveryItem) at the same place, at the same delivery ID. When you need to split the le for products make the split
in each tab at the same product ID.

The le format is XLSX. CSV les cannot be imported.

No sheets from the template les were removed. Additional sheets can be added. Additional sheets are disregarded
during the import.

No sheet names were changed and are matching the template les.

The ve header lines in column A were not changed and are matching the template les. See Common Elements.

No additional columns were inserted. In case you want to add a comment, use the “Your Remarks” column.

The correct SAP S/4HANA attribute was exported for every eld. The proper SAP S/4HANA attribute is listed in the le
templates for every column.

The mandatory elds are lled. See Common Elements.

The eld length does not exceed the maximum eld length.

The data type of every eld is correct.

The row with sample values is removed.

Adhere to the correct data and time format and use the correct decimal separator. See Format.

Values from code lists are used. For some elds, only values from a code list are allowed. Make sure to use values from
the code list for those elds. The code lists are part of the templates.

Related values exist. Some eld values must match a corresponding value from a related sheet or le. That means, a
value must match another value in a different le or sheet that you need to import, too. Make sure to use values that
exist in the related sheet or le.

No blank line items or blank elds are left in column B. If an empty eld is encountered in column B, then this is regarded
as the end of the table. Only the data that was read until this point is imported.

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