PUBLIC

SAP Returnable Packaging Management

2022-02-28

SAP Returnable Packaging Management -

Integration Guide (File-Based Integration)
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Integration Flow Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Error Mail Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 SFTP Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Steps in SAP Returnable Packaging Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 CSV File Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1 Deployment of Credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Deploy Certificates in Keystore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Deploy known_hosts File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Open Firewall Request at SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Deploy Technical Communication User Data with a Credential Artifact. . . . . . . . . . . . . . . . . . . . 18
3.2 Configuration and Deployment of Integration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Create a Copy of the Pre-Packaged Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuration of Integration Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3 Order of File Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Deployment of Integration Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4 Troubleshooting and Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5 Scheduled System Downtimes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

5.1 Downtime of SAP Returnable Packaging Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2 SAP Cloud Integration Downtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

7 Components for Customer Incidents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

2 PUBLIC Content
1 Purpose

This guide covers the integration between SAP Returnable Packaging Management and CSV file-based data.
The purpose of this document is to describe the general configuration steps required to set up the system
landscape that has been installed using the corresponding installation or configuration guides.

1.1 Overview

The integration package SAP Returnable Packaging Management Integration with File Based Master Data Load
implements the integration of CSV file-based data into SAP Returnable Packaging Management. This allows
you to create, update, or delete entries in your SAP Returnable Packaging Management tenant.

This integration package runs on the SAP Cloud Integration service tenant and connects to the SAP Returnable
Packaging Management via OData services and REST services. The CSV files are loaded using an SFTP server
to SAP Cloud Integration.

1.2 Integration Flow Templates

The following integration flows serve as templates that can be copied to a customer’s tenant and configured to
individual requirements:

• Address Replication to SAP Returnable Packaging Management

• Address Deletion from SAP Returnable Packaging Management
• CompanyCode Replication to SAP Returnable Packaging Management
• Company Code Deletion from SAP Returnable Packaging Management
• Plant Replication to SAP Returnable Packaging Management
• Plant Deletion from SAP Returnable Packaging Management
• Storage Location Replication to SAP Returnable Packaging Management
• Storage Location Deletion from SAP Returnable Packaging Management
• Sales Organization Replication to SAP Returnable Packaging Management
• Sales Organization Deletion from SAP Returnable Packaging Management
• Distribution Channel Replication to SAP Returnable Packaging Management
• Distribution Channel Deletion from SAP Returnable Packaging Management
• Sales Division Replication to SAP Returnable Packaging Management
• Sales Division Deletion from SAP Returnable Packaging Management
• Material Master General Data Replication to SAP Returnable Packaging Management

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Purpose PUBLIC 3
• Material Master General Data Description Replication to SAP Returnable Packaging Management
• Material Master General Data Deletion from SAP Returnable Packaging Management
• Material Master Plant Data Replication to SAP Returnable Packaging Management
• Material Master Plant Data Deletion from SAP Returnable Packaging Management
• Material Master Sales Data Replication to SAP Returnable Packaging Management
• Material Master Sales Data Deletion from SAP Returnable Packaging Management
• Business Partner Replication to SAP Returnable Packaging Management
• Business Partner Deletion from SAP Returnable Packaging Management
• Material Serial Number Replication to SAP Returnable Packaging Management
• Material Serial Number Delete from SAP Returnable Packaging Management

1.3 Error Mail Notification

All integration flows in this integration package provide the facility of sending error mail notifications for
errors that occur during processing in the SAP Cloud Integration tenant, or in SAP Returnable Packaging
Management system.

For this, the SMTP server to be used as well as the email IDs from and to which the error message is to be sent
can be configured in the mail adapter connected to the exception sub-process present in each integration flow
in the package.

 Note

Only if a user subscribes to receiving notifications, they will receive emails.

1.4 SFTP Connection

The CSV files are stored on the SFTP server in specific directories referred to as mailboxes. For each mailbox, a
user is specified to control access to the data.

Before the integration content can be configured and used in your SAP Cloud Integration tenant, the SFTP
server needs to be available. SAP Cloud Integration tenant acts as a client and collects the data from the SFTP
mailbox on the SFTP server.

Public keys of all connected SFTP servers need to be stored in the known_hosts file on the SAP Cloud
Integration side. Integration flows in this package support username/password form of authentication for the
SFTP adapter. Therefore, the corresponding credentials need to be deployed in the security artifacts tile of the
Monitor tab, and subsequently be used in the SFTP adapter in each integration flow.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

4 PUBLIC Purpose
2 Preparation

2.1 Steps in SAP Returnable Packaging Management

For communication with the OData services or REST web services, a technical user needs to be enabled in the
SAP Returnable Packaging Management system. This user is enabled while onboarding the SAP Returnable
Packaging Management application; refer to the Subscription via SAP Store section in SAP Returnable
Packaging Management - Administrator's Guide. This user gets access to the authentication URL as well as
client credentials (client_id and client_secret). These are required to fetch OAuth token to establish connection
to the SAP Returnable Packaging Management services.

To get access to authentication URL and client credentials, execute command cf service-key <service-
instance-name> <service-key-name>. You should use the service name and service key created during
onboarding of SAP Returnable Packaging Management. To know the created service name, execute command
cf s. To know the created service key, execute command cf service-keys.

Alternatively, you can request the administrator of SAP Returnable Packaging Management to provide you with
the authentication URL and client credentials.

Related Information

Subscription via SAP Store

2.2 CSV File Preparation

 Note

To refer to the sample CSV files, see the SAP Note 3068702 .

For File-Based Load

Consider the following input information and data restrictions (for example, file format required) for CSV files.
These CSV files need to be then stored in the dedicated SFTP folder, so that these are collected from the server
by the SAP Cloud Integration client.

Note that execution will stop and send a mail with error content if the values entered in fields exceed character
limit.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Preparation PUBLIC 5
  Note

• If there's no input required for any field with data type String, then you may leave those fields empty.
The default value for fields with data type String is empty or blank. However, for all numerical fields
such as Integer and Decimal, the default value is 0.
• There are some fields that accept alpha-numeric characters as input. And as an exception, these fields
also accept hyphen (-) as an input, along with alpha-numeric characters.

CSV File Contents for File-Based Load

Entity Field Description Type Mandatory

Address Address ID Key for identifying the String (10) Yes

address

Street Name of the street, String (60) No

which is a part of the
address data

House number House number, which String (10) No

is a part of address
data

Address Line 1 Address line 1, which is String (60) No

a part of address data

Address Line 2 Address line 2, which is String (60) No

a part of address data

Address Line 3 Address line 3, which is String (60) No

a part of address data

Postal Code Postal code, which is String (10) No

a part of the address
data

City City name, which is String (40) Yes

a part of the address
data

Country Key ISO country code, String (3) Yes

which is a part of the
address data

PO Box PO box number, which String (10) No

is a part of the address
data

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

6 PUBLIC Preparation
 Entity Field Description Type Mandatory

Mobile Mobile telephone num­ String (30) No

ber (consisting of dial­
ing code and number),
which is a part of the
address data

Telephone Telephone number String (30) No

(consisting of dialing
code and number),
which is a part of the
address data

Extension Telephone extension String (10) No

number, which is a part
of the address data

Fax Number Fax number (consist­ String (31) No

ing of dialing code and
number), which is a
part of the address
data

E-mail E-mail address, which String (241) No

is a part of the address
data

Contact Person Contact person, which String (60) No

is a part of the address
data

Company Code Company Code Key used to represent String (4) Yes
the company code

Company Code Name Description for the String (25) Yes

company code

Country Key ISO code to represent String (3) Yes

the country

Address ID Key used to identify String (10) Yes

the address

Currency Medium of currency String (5) Yes

that is currently in
use within a particular
country

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Preparation PUBLIC 7
Entity Field Description Type Mandatory

Plant Plant Key used to identify String (4) Yes

plant

Plant Name Name of the plant String (25) No

Plant Name Extn. Plant name extension, String (40) No

which is a part of the
plant entity

Company Code Key used to represent String (4) Yes

company code

Customer No of Plant Customer number of String (10) No

the plant if plant is
used a customer in lo­
gistics process

Supplier No of Plant Supplier number of the String (10) No

plant if plant is used
a customer in logistics
process

Address ID Key used to identify String (10) Yes

address

Factory Calendar Key used to identify String (2) No

the factory calendar
that is valid for the
plant.

Storage Location Storage Location Key used to represent String (4) Yes
the storage location

Storage Location Name of the storage String (25) Yes

Name location

Plant Code Key used to identify a String (4) Yes

plant

Sales Organization Sales Organization Key used to represent String (4) Yes
the storage location

Sales Organization Name of the sales or­ String (25) Yes

Name ganization

Company Code Key used to represent String (4) Yes

company code

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

8 PUBLIC Preparation
 Entity Field Description Type Mandatory

Distribution Channel Distribution Channel Key used to represent String (2) Yes
the distribution chan­
nel

Distribution Channel Name of the distribu­ String (20) Yes

Name tion channel

Sales Organization Key used to represent String (4) Yes

the sales organization

Division Sales Division Key used to o repre­ String (2) Yes

sent the sales division

Sales Division Name Name of sales division String (20) Yes

Sales Organization Key used to represent String (4) Yes

the sales organization

Material Master Gen­ Material Code Key used to identify String (40) Yes
eral Data
the returnable packag­
ing material

Material Description Text that describes the String (40) Yes

material in more detail

Material Type Key used to represent String (4) Yes

a material type, for ex­
ample, group of mate­
rials such as raw mate­
rials, returnable pack­
aging materials

Material Group Key used to represent String (9) No

a material group

Division Key used to represent String (2) No

a division

Plant Material Status Key used to restrict the String (2) No

usability of material for
all plants

Valid From Date from which the String (10) No

cross-plant material
status is valid. Date
should be provided
in "YYYY-MM-DD" for­
mat.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Preparation PUBLIC 9
Entity Field Description Type Mandatory

Gross Weight Gross weight ex­ Decimal (13,3) No

pressed in the unit of
weight specified in the
Unit of weight field.

Net Weight Net weight expressed Decimal (13,3) No

in the unit of weight
specified in the Unit of
weight field.

Volume Space that the mate­ Decimal (13,3) No

rial occupies per unit
of volume

Size/Dimensions Text field that you can String (32) No

use to record the size
or dimensions of the
material

EAN/UPC International Article String (18) No

Number (EAN/UPC)

EAN Category Category of Interna­ String (2) No

tional Article Number
(EAN)

Product Composition Indicator to define if String (1) No

Indicator product composition is
printed on packaging

Packaging Material Key used to represent String (4) No

Group the packaging material
group

Base Unit of Measure Unit of measure in String (3) Yes

which stocks of the
material are managed

Weight Unit Unit referring to the String (4) No

gross weight or net
weight of the material.

Voume Unit Unit referring to the String (4) No

gross volume or net
volume of the material.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

10 PUBLIC Preparation
 Entity Field Description Type Mandatory

Material Serial Man­ Key that is used to in­ Integer Yes

aged Status
dicate if the material
is serially managed or
not. The values of this
field are:

1 - Serially managed

2 - Not serially man­

aged

Material Master Plant Material Code Key used to identify String (40) No
Data
the returnable packag­
ing material

Plant Key used to identify String (4) Yes

the plant

Serial Number Profile Key used to identify String (4) No

the serial number pro­
file

Reorder Point If the stock falls be­ String (13) No

low this quantity, reor­
der or replenishment
of the material should
be planned

MRP Type Key that determines String (3) No

whether and how the
material is planned

Pricing Indicator Indicator that repre­ String (1) No

sents the price control
(Standard or Moving
Average Price) used to
valuate the stock of a
material

Gross Weight Gross weight ex­ Decimal (13,3) No

pressed in the unit of
weight in the Unit of
weight field

Standard Price Standard price of a String (15) No

material

Moving Average Price Moving average price String (15) No

of a material

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Preparation PUBLIC 11
Entity Field Description Type Mandatory

Material Master Sales Material Code Key used to represent String (40) Yes
Data
the returnable packag­
ing material

Sales Organization Key used to represent String (4) Yes

the sales organization

Distribution Channel Key used to represent String (2) Yes

the distribution chan­
nel

Business partner Business Partner Key used to identify a String (10) Yes
Number business partner

Vendor Code Key used to repre­ String (10) No

sent vendor code as­
sociated with business
partner

Customer Code Key used to represent String (10) No

the customer code as­
sociated with business
partner

BP Name 1 First name of the busi­ String (40) Yes

ness partner

BP Name 2 Second name of the String (40) No

business partner

Address ID Key used to identify String (4) Yes

address

MaterialMasterGener­ Material Code Key used to identify String (40) Yes

alDataText
a returnable packaging
material

Material description Text that describes the String (40) Yes

material in more detail

Language Key Key used to identify String (14) Yes

the language in which
the material descrip­
tion is maintained

Business User Business User ID User ID of the business String (100) Yes
user

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

12 PUBLIC Preparation
 Entity Field Description Type Mandatory

First Name First name of the busi­ String (50) Yes

ness user

Last Name Last name of the busi­ String (50) Yes

ness user

Contact Number Contact number of String (100) No

business user

Email Email address of the String (50) No

business user

Address Address of the busi­ String (50) No

ness user

Logon Name Logon name of the String (100) Yes

business user

Role Role associated with String (2) Yes

the business user

Material Serial Number Material Code Alphanumeric key that String (40) Yes
uniquely identifies the
returnable packaging
material

Serial Number A unique identifier that String(20) Yes

is assigned to a return­
able material. The pur­
pose of serial numbers
is to manage, moni­
tor, and track individ­
ual returnable packag­
ing materials.

Equipment Number Unique identifier of String(20) No

an equipment. The re­
turnable material, its
serial number (along
with other details) are
assigned to an equip­
ment. The equipment
can be used to moni­
tor, track, and manage
maintenance activities
performed for this ma­
terial.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Preparation PUBLIC 13
Entity Field Description Type Mandatory

Asset Number Uniquely identifies an String(20) No

asset in the system.
The equipment num­
ber (containing the re­
turnable material num­
ber and its serial num­
ber) along with other
details are linked to
an asset. An asset is
an independent object
that is used to track
the expenditure and
use of a material.

Status Code Key that is used to in­ Integer No

dicate the status of se­

rially managed return­
able packaging mate­
rial. The values of this
field are:

1 - In Stock

2 - Issued

Ownership Type Key that is used to in­ Integer No

dicate the ownership
type. The values of this
field are:

1 - Customer Owned

3 - Vendor Owned

4 - Self Owned (Com­

pany Owned)

Ownership Code Key that identifies the String(10) No

owner of a returnable
packaging material

IMEI Number Key that identifies the String(20) No

IMEI number of an IoT
device that is associ­
ated with a returnable
packaging material

Bar Code Key of the bar code as­ String(48) No

sociated with a return­
able packaging mate­
rial

RFID Key of the RFID associ­ String(40) No

ated with a returnable
packaging material

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

14 PUBLIC Preparation
 Entity Field Description Type Mandatory

Colour Identifes the colour of String(20) No

a returnable packing
material

For File Based Delete

CSV File Contents for File-Based Delete

Entity Field Description Field Type Mandatory

Address Address ID Key used to identify the address String (10) Yes

Company Code Company Company code key String (4) Yes

Code

Plant Plant Key used to identify a plant String (4) Yes

Storage Location Storage Loca­ Key used to represent the stor­ String (4) Yes
tion age location

Plant Code Key used to identify a plant String (4) Yes

Sales Organization Sales Organi­ Key used to represent a sales or­ String (4) Yes
zation ganization

Distribution Chan­ Distribution Key used to represent distribu­ String (2) Yes
nel Channel tion channel

Sales Organi­ Key used to represent sales or­ String (4) Yes
zation ganization

Division Sales Division Key used to represent sales divi­ String (2) Yes
sion

Sales Organi­ Key used to represent sales or­ String (4) Yes
zation ganization

Material Master Material Code Key used to identify returnable String (40) Yes
General Data
packaging material

Material Master Material Code Key used to identify returnable String (40) Yes
Plant Data
packaging material

Plant Key used to identify a plant String (4) Yes

Material Master Material Code Key used to identify returnable String (40) Yes
Sales Data
packaging material

Sales Organi­ Key used to represent the stor­ String (4) Yes
zation age location

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Preparation PUBLIC 15
Entity Field Description Field Type Mandatory

Distribution Key used to represent the distri­ String (2) Yes

Channel bution channel

Business Partner Business Part­ Key used to represent a busi­ String (10) Yes
ner Number ness partner

Material Master Material Key that uniquely identifies a re­ String (40) Yes
GeneralData Text
turnable packaging material

Language Key Key to identify the language in String (3) Yes

which the material description is
maintained

Business User Business User User ID of the business user String (100) Yes
ID

MaterialSerial­ Material Code Alphanumeric key that uniquely String (40) Yes
NumberDelete identifies the returnable packag­
ing material

Serial Number A unique identifier that is as­ String (20) Yes

signed to a returnable material.
The purpose of serial numbers
is to manage, monitor, and track
individual returnable packaging
materials.

For more information, see SAP Business Accelerator Hub .

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

16 PUBLIC Preparation
3 Configuration

The pre-packaged integration scenario contains integration flows for each separate object, which can be
loaded to SAP Returnable Packaging Management. For each integration flow, the SFTP connection, the receiver
HTTP channel and the receiver SMTP connection need to be configured.

The configuration is structured in the following order:

1. Deployment of credentials
2. Configuration and deployment of the integration flows

3.1 Deployment of Credentials

To establish the communication with the source SFTP system and the SAP Returnable Packaging
Management., it is required to deploy the requisite credentials. Some firewall ports also need to be opened.

3.1.1 Deploy Certificates in Keystore

For connecting sender or receiver systems, the tenant administrator needs to maintain keys and certificates
in different systems, sender, receiver, and the Cloud integration tenant. The Keystore Monitor available in the
Cloud integration tenant can be used for this purpose.

The monitor is available in Operations View on the web. In the section Manage Security, you find the Keystore
tile, which directly informs you about the number of keys and certificates available in the tenant keystore.

In the keystore, certificates of all relevant end-points need to be uploaded.

For more information, refer to this blog :

3.1.2 Deploy known_hosts File

The known_hosts file contains the SSH server host key of your SFTP server. Each entry in known_hosts is one
line with three or more white space-separated fields as follows:

1. One or more server names or IP Addresses, joined together by commas

2. The type of key
3. The public key data itself encoded to stay within the ASCII range
4. Any optional comment data

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Configuration PUBLIC 17
The deployment of the known_hosts file can be done in the Security Material tab of the Monitor tab of SAP
Cloud Integration. For further details, see the Operations Guide for SAP Cloud Integration (Connecting a
Customer System to Cloud Integration).

For more information, refer to this blog .

3.1.3 Open Firewall Request at SAP

When connecting to an SFTP server from SAP Cloud Integration, the firewall needs to be opened at SAP Cloud
Support. The request needs to be addressed through an SAP incident on component LOD-HCI-PI-OPS.

You will need to provide the following information in the ticket:

• Port number
• Destination address
• Destination IP
• Brief description of the purpose
• Affected customer
• Tenant ID
• Name of requesting SAP department
• Persons responsible for the request (at least two)
• Company name and address of where the SFTP server resides
• Estimated project duration

 Note

Also make sure to open the Firewall at your (Customer) side to be able to accept SFTP adapter calls from
SAP CPI (Port 22).

3.1.4 Deploy Technical Communication User Data with a

Credential Artifact

User credentials of the technical user of your SAP Returnable Packaging Management application needs to be
deployed in your SAP Cloud Integration tenant.

1. Open your SAP Cloud Integration tenant’s web UI.

2. On the Tenant menu, choose Monitor.
3. Select the Security Material tile in the Manage Security Material section.
4. Choose Add.
5. Select User Credentials.
6. Enter the following values in the Add User Credential dialog box:
• Name: <credential_name>
• Description (optional)

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

18 PUBLIC Configuration
 • User: <Client_ID>
• Password: <Client_Secret>
7. Choose OK to save the user credentials.

3.2 Configuration and Deployment of Integration Package

To work with the integration flows of this package, the pre-packaged integration flow scenario must be copied
to your workspace. Constituent integration flows need to be configured next. Finally, to activate the integration
flows, they must be deployed. The configuration and deployment must be processed for each integration flow.

3.2.1 Create a Copy of the Pre-Packaged Integration Scenario

To create a copy of the pre-packaged integration scenario, proceed as follows:

1. In your preferred web browser, open the web UI of your SAP Cloud Integration tenant: <https://
your_tenant_URL/itspaces>.
2. On the Discover page, select All to navigate through the available pre-packaged integration scenarios.
3. Enter <File Based Master Data Load> in the Search field and choose Enter.
4. To copy the integration package from the catalog to your customer workspace, move your cursor over the
integration package tile and choose Copy to workspace.
The message Integration package copied confirms that the package was copied to your workspace.

 Note

In case the integration scenario is already available in the workspace, a copy with a different name
can be created, or the existing package can be overwritten. In case of overwriting, all previous
configurations will be lost.

5. Select the pen icon to open the Design page. You can now work with the copied package and it's integration
flows.

3.2.2 Configuration of Integration Flows

..

1. On the Design page, select the package SAP Returnable Packaging Management Integration with File Based
Master Data Load, which contains the integration content.
An overview of the artifacts available in the selected integration package is shown.
2. To configure an integration flow, choose Configure in the Actions column for the integration flow.

Configuration of File-Based Load Integration Flows

A integration flow has a configuration part for the sender and another one for the receiver.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Configuration PUBLIC 19
Provide the relevant details on the Sender tab page:

Field Value

Directory <sftp_directory>

File Name <file_name>

Regular expressions, such as ab*, a.*, *a*, ?b, and so on, are
supported.

Address <sftp_system_host:port>

Proxy Type Specify a proxy type value.

Location ID Specify tenant space technical name.

Authentication User name and password

Credential Name <sftp_credentials>

Timeout <Timeout (in ms)>

Sender Tab

All integration flows are configured to poll the SFTP server every 10 seconds by default. If required, the polling
interval can also be configured on this Sender tab page.

Provide the relevant details on the Receiver tab page as follows:

1. In Receiver field, select either Mail_Success, Mail_Exception, or Mail_Error. All three options are configured
with the same mailing parameters.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

20 PUBLIC Configuration
 Adapter Type - MAIL

Field Value

Address <smtp_address>

Timeout <Timeout in (ms)>

Credential Name <credential_name>

From <from@mail.com>

To <to@mail.com>

Subject Enter the subject line as required in the mails

Other Fields Enter the text as required in the mails

Receiver Tab - Mail_Error

2. In Receiver field, select Returnable_Packaging_Receiver and configure the following:

Adapter Type - HTTP

Field Value

Application URL Host <Service URL>

Proxy Type Internet

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Configuration PUBLIC 21
 Field Value

Authentication OAuth2 Client Credentials

Credential Name Specify OAuth2 Client Credentials

Timeout (in ms) <Timeout (in ms)> example: 600000 ms which is equals
to 10 min>

Receiver Tab - Returnable_Packaging_Receiver

3. In Receiver field, select SFTPServer_ErrorLog and configure the following:

Adapter Type - SFTP Receiver

Field Value

Directory <sftp_directory>

File Name <file_name>

Regular expressions, such as ab*, a.*, *a*, ?b, and so on,

are supported.

SFTP file name for error log <file_name_of_error_log>

Address <sftp_system_host:port>

Proxy Type Specify a proxy type value.

Location ID Specify tenant space technical name.

Credential Name <sftp_credentials>

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

22 PUBLIC Configuration
 Field Value

Timeout <Timeout (in ms)>

Receiver Tab - SFTPServer_ErrorLog

4. In the More tab, enter the relevant details. If you want to receive email notifications, choose True in the
Email Notification field. To stop getting email notifications, choose False in the Email Notification field.

Fields in More Tab

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Configuration PUBLIC 23
3.3 Order of File Upload

Files need to be uploaded to SAP Cloud Integration in the following specific order:

1. Address
2. CompanyCode
3. BusinessPartner
4. Plant
5. StorageLocation
6. SalesOrganization
7. DistributionChannel
8. Division
9. MaterialMasterGeneralData
10. MaterialMasterGeneralDataDescription
11. MaterialMasterPlantData
12. MaterialMasterSalesData
13. MaterialSerialNumber

3.3.1 Deployment of Integration Flows

Before an integration flow can be deployed, the configuration for this integration flow must be completed.

Procedure

1. On the Design page, select the SAP Returnable Packaging Management Integration with File Based Master
Data Load package that contains the integration content
2. In the Actions column for the integration flow, choose Deploy.
A message confirms that the integration flow was deployed.
3. Choose Monitor on the tenant page.
4. Select the All tile in the Manage Integration Content section.
The integration flow should have the started status in the Status column.
In case of errors, check whether you have set up the sender and receiver parameters properly in
Configuration of the Integration Flows.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

24 PUBLIC Configuration
4 Troubleshooting and Log

In the SAP Cloud Integration web UI, you can analyze the deployed integration flows in the Monitoring section
as follows:

1. To carry out the activity, open your SAP Cloud Integration tenant web UI, for example, https://<your
SAP Cloud Integration tenant URL>/itspaces
2. On the tenant web UI, choose Monitor, then Monitor Message Processing.
On the Overview screen, choose the tile with the message status you wish to analyze.
3. On the left, select the integration flow you wish to analyze.
4. Access the Message Processing Log from the Log tabs.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Troubleshooting and Log PUBLIC 25
5 Scheduled System Downtimes

During the scheduled system downtime of SAP Returnable Packaging Management, you should prevent files
from being transferred in advance to avoid Failed messages.

In case of downtime of SAP Returnable Packaging Management, all file-based load artifacts are affected.

5.1 Downtime of SAP Returnable Packaging Management

The files are picked up from the SFTP server according to the schedule of the corresponding integration flow.
To stop the file transfer during the downtime, adapt the schedule of the integration flows accordingly. A second
option to prevent Failed messages is to not place any file on the SFTP server during the downtime.

5.2 SAP Cloud Integration Downtime

During the scheduled downtime of SAP Cloud Integration system, no files will be fetched from the SFTP server.
In that case, you should consider that all files will remain on the SFTP server as long as the system is down.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

26 PUBLIC Scheduled System Downtimes
6 Data Protection and Privacy

Data protection is associated with numerous legal requirements and privacy concerns. In addition to
compliance with general data privacy regulation, it is necessary to consider compliance with industry-specific
legislation in different country/region. SAP provides specific features and functions to support compliance with
regards to relevant legal requirements, including data protection. SAP does not give any advice on whether
these features and functions are the best method to support company, industry, regional, or country-specific
requirements. Furthermore, this information does not give any advice or recommendation in regards to
additional features that would be required in particular IT environments; decisions related to data protection
must be made on a case-by-case basis, under consideration of the given system landscape and the applicable
legal requirements.

 Note

In most cases, compliance with applicable data protection and privacy laws will not be covered by a product
feature. SAP software supports data protection compliance by providing security features and specific
data protection-relevant functions, such as simplified blocking and deletion of personal data. SAP does not
provide legal advice in any form. Definitions and other terms used in this document are not taken from any
given legal source.

Data Protection and Privacy in Integration with SAP Returnable Packaging

Management

The SAP Returnable Packaging Management application works with personal data of business partners and
business users. This data can be uploaded to SAP Returnable Packaging Management, changed using the
integration flows for business partners and business users, and deleted using the file-based delete integration
flows.

• Consent
As no explicit consent from the users is managed, users have to manually verify and validate the data
issues.
• Deletion
The file-based delete integration flows allow you to delete personal information of business partners and
business users completely from the SAP Returnable Packaging Management system. These deletions are
also logged in the application's Audit Log.
• Change Logging
All changes made in SAP Returnable Packaging Management using the file-based integration flows are
recorded in the application's Audit Log.

For more information, refer theSAP Returnable Packaging Management - Administrator's Guide.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Data Protection and Privacy PUBLIC 27
7 Components for Customer Incidents

In case if any errors occur during the execution of integration flows (iFlow) that are delivered, open a ticket
using component LO-RL. For more information, see Components for Incidents.

In case of any CPI tenant platform related issues, open a ticket using component LOD-HCI-PI-OPS.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

28 PUBLIC Components for Customer Incidents
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

SAP Returnable Packaging Management - Integration Guide (File-Based Integration)

Important Disclaimers and Legal Information PUBLIC 29
www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN