Administration Guide | PUBLIC

Document Version: 1.0 – 2024-06-28

SAP Replenishment Planning 5.0 SPS07

Administration Guide
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Security Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Security Aspects of Data, Data Flow and Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 User Administration and Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Back-End Roles and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Database Roles and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Authorizations for Transfer of Order Plan Items to Source Master Data System. . . . . . . . . . . . . . 15
2.4 Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.5 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Information Retrieval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Deletion of Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.6 Data Storage Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7 Security-Relevant Logging and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.8 Services for Security Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3 Configuration Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.1 Ensure a Suitable Configuration of the Enqueue Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2 Configure SAP Replenishment Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3 How to Set Up SAP Fiori Apps for SAP Replenishment Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.4 External Review of Order Plan Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.5 Provision of Customer-Specific Stock Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.6 Configure Purchase Order Creation Based on Order Plan Items. . . . . . . . . . . . . . . . . . . . . . . . . . . .36
3.7 Define the Parameterization Profiles and the Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.8 Configure Exception Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.9 Configure Process Packaging and Parallelization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.10 Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Optimize Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Performance Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
How to Integrate Performance Monitoring in Customer-Specific Processes. . . . . . . . . . . . . . . . . 51
3.11 Partition Tables for SAP Replenishment Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4 Operation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.1 Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.2 Display of Data with Tools Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

SAP Replenishment Planning 5.0 SPS07 Administration Guide

2 PUBLIC Content
4.3 Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.4 High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.5 Software Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.6 Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Content PUBLIC 3
1 Getting Started

SAP Replenishment Planning is a highly automated solution that significantly speeds up replenishment
planning for retail and makes ordering more cost effective. It supports replenishment planners in meeting
replenishment targets while minimizing overall costs.

About This Document

This guide provides information about how to securely configure, operate, and optimize the SAP
Replenishment Planning application.

Setting Up SAP Replenishment Planning

For information about how to set up SAP Replenishment Planning, see one of the following guides:

• For new installations, see SAP Replenishment Planning in the Common Installation Guide at https://
help.sap.com/viewer/p/CARAB.
• For upgrade scenarios, see SAP Replenishment Planning in the Common Upgrade Guide at https://
help.sap.com/viewer/p/CARAB.

Related Information

For more information about implementation topics not covered in this guide, see the following content:

Content Location

Performance (in general) and scalability https://www.sap.com/about/benchmark/sizing/perform-

ance.html

SAP Security Optimization Services Portfolio https://support.sap.com/en/offerings-programs/support-

services/security-optimization-services-portfolio.html

Sizing (sizing guidelines, Quick Sizer tool, calculation of https://www.sap.com/about/benchmark/sizing.html

hardware requirements, such as CPU, disk, and memory re-
source)

SAP Support Package Stacks https://support.sap.com/en/my-support/software-down-

loads/support-package-stacks.html

SAP Replenishment Planning 5.0 SPS07 Administration Guide

4 PUBLIC Getting Started
Further Useful Links

The following table lists further useful links:

Content Location

SAP Notes search https://support.sap.com/notes

SAP Software Download Center (software download and or- https://support.sap.com/swdc

dering of software)

Early Knowledge Transfer https://support.sap.com/en/offerings-programs/get-in-

volved-early.html

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Getting Started PUBLIC 5
2 Security Information

Security Aspects of Data, Data Flow and Processes [page 6]

User Administration and Authentication [page 7]

SAP Replenishment Planning uses the user management and authentication mechanisms provided
with the SAP NetWeaver platform, in particular the Application Server (AS) ABAP.

Authorizations [page 9]
SAP Replenishment Planning uses the authorization concept provided by SAP NetWeaver AS ABAP.
Therefore, the recommendations and guidelines for authorization as described in the SAP NetWeaver
AS Security Guide ABAP also apply to SAP Replenishment Planning.

Network and Communication Security [page 17]

Data Protection and Privacy [page 17]

Data Storage Security [page 22]

Security-Relevant Logging and Tracing [page 22]

SAP Replenishment Planning does not provide additional security logging and tracing above those
available within SAP NetWeaver. For more information, see the references for the following aspects:

Services for Security Lifecycle Management [page 23]

There are services available from Active Global Support to assist you in maintaining security in your
SAP systems on an ongoing basis.

2.1 Security Aspects of Data, Data Flow and Processes

The concepts for data storage, exchange, and processing applied in SAP Replenishment Planning follow the
principles and frameworks outlined in section Security Aspects of Data, Data Flow and Processes of the SAP
Customer Activity Repository Administration Guide.

The following data flows are required to operate SAP Replenishment Planning:

Step Description Security Measure

Master/transaction data inbound flow The master and transaction data im- SAP Communication User with neces-
sary authorizations, RFC
port is used as provided by the Demand
Data Foundation (DDF) module.

Order plan outbound flow The calculated order plan entries are SAP Communication User with neces-
sary authorizations, RFC
transferred back to the SAP Retail or
SAP S/4HANA Retail system in order to
be processed into operative orders.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

6 PUBLIC Security Information
 Step Description Security Measure

Real-time inventory data inbound flow This is only relevant if the use of real- SLT replication (SAP system user with
necessary authorizations to set up rep-
from SAP ERP time inventory data (RTI stock) is acti-
lication, SAP technical user(s) with nec-
vated.
essary authorizations for replication of
Data replication from SAP ERP. target schema)

 Note
Replication is not required in cases
of Multiple Components in One Da-
tabase (MCOD) co-deployment of
SAP Customer Activity Repository
and SAP ERP.

Real-time inventory data inbound flow This is only relevant if the use of real- SLT replication (SAP system user with
from SAP S/4HANA necessary authorizations to set up rep-
time inventory data (RTI stock) is acti-
lication, SAP technical user(s) with nec-
vated.
essary authorizations for replication of
Data replication from SAP S/4HANA target schema)

2.2 User Administration and Authentication

SAP Replenishment Planning uses the user management and authentication mechanisms provided with the
SAP NetWeaver platform, in particular the Application Server (AS) ABAP.

Therefore, the security recommendations and guidelines for user administration and authentication as
described in the SAP NetWeaver Application Server ABAP Security Guide also apply to SAP Replenishment
Planning.

In addition to these guidelines, we include the following information about user administration and
authentication that specifically applies to SAP Replenishment Planning.

User Management

User management for SAP Replenishment Planning uses the user management and authentication
mechanisms provided with the SAP NetWeaver platform, in particular the AS ABAP, for example, tools, user
types, and password policies.

Similarly, other components of the technical system landscape for SAP Replenishment Planning, such as SAP
ERP Central Component (ECC) and/or SAP NetWeaver Process Integration (PI), also use the mechanisms
provided with the SAP NetWeaver AS ABAP. For an overview of how these mechanisms apply for SAP
Replenishment Planning, see the sections below.

User Administration Tools

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Security Information PUBLIC 7
The table below shows the tools to use for user management and user administration with SAP Replenishment
Planning.

Tool Description Requirements

User and role maintenance with SAP For more information, see: SAP NetWeaver Application Server
NetWeaver AS ABAP (transactions ABAP should be running.
• AS ABAP Authorization Concept
SU01, PFCG) in the SAP NetWeaver Application
Server ABAP Security Guide
• SAP Library for SAP Net-
Weaver on SAP Help
Portal at https://help.sap.com/
viewer/product/SAP_NETWEA-

VER_750 Application Help

Function-Oriented View Solution

Life Cycle Management Security

and User Administration

User Types

It is often necessary to specify different security policies for different types of users. For example, your policy
may specify that individual users who perform tasks interactively have to change their passwords on a regular
basis, but not those users under which background processing jobs run.

The user types that are required for SAP Replenishment Planning include:

• Individual users:
• Dialog users are used for interactive system access, such as SAP GUI for Windows or RFC connections.
• Internet users are used for internet connections. The same policies apply as for dialog users, but used
for Internet connections.
• Technical users:
• Communication users are used for dialog-free communication through external RFC calls.
• Background users are used for background processing and communication within the system, such
as, running scheduled inbound/outbound dispatcher jobs.

For more information on these user types, see User Types in the SAP NetWeaver Application Server ABAP
Security Guide.

Standard Users

SAP Replenishment Planning does not require specialized standard users.

For more information about SAP NetWeaver standard users, see Protecting Standard Users in the SAP
NetWeaver Application Server ABAP Security Guide.

 Recommendation

We recommend changing the user IDs and passwords for any users that are automatically created during
installation.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

8 PUBLIC Security Information
User Data Synchronization

The application does not deliver additional user data synchronization related features in addition to those
available in the SAP NetWeaver platform. It also does not impose any special needs or restrictions, which would
limit the usage of related SAP NetWeaver tools.

 Recommendation

For any scenarios where system inter-connectedness at the user level is a requirement, it is recommended
that the same users exist throughout all the pertinent connected systems in the landscape.

Integration into Single Sign-On Environments

SAP Replenishment Planning supports the Single Sign-On (SSO) mechanisms provided by the SAP NetWeaver
AS ABAP. Therefore, the security recommendations and guidelines for user administration and authentication
as described in the SAP NetWeaver Security Guide also apply to SAP Replenishment Planning.

For more information about the available authentication mechanisms, see the User Authentication and Single
Sign-On section in the SAP NetWeaver Library.

More Information

You can find the product documentation for SAP NetWeaver on SAP Help Portal at https://help.sap.com/
viewer/p/SAP_NETWEAVER.

2.3 Authorizations

SAP Replenishment Planning uses the authorization concept provided by SAP NetWeaver AS ABAP. Therefore,
the recommendations and guidelines for authorization as described in the SAP NetWeaver AS Security Guide
ABAP also apply to SAP Replenishment Planning.

The SAP NetWeaver authorization concept is based on assigning authorizations to users based on roles. For
role maintenance, use the profile generator (transaction PFCG) on the Application Server ABAP.

For more information, see https://help.sap.com/viewer/product/SAP_NETWEAVER/ALL/en-US and select

your SAP NetWeaver version. Choose Security SAP NetWeaver Security Guide .

 Note

For information about how to create roles, see https://help.sap.com/viewer/product/

SAP_NETWEAVER/ALL/en-US and select your SAP NetWeaver version. Choose Application Help SAP
NetWeaver Library: Function-oriented View and search for Role Administration.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Security Information PUBLIC 9
For each user role, such as replenishment planner, you must create the necessary user(s) and roles with
suitable authorizations for the back-end and database as described in the following subsections.

2.3.1 Back-End Roles and Authorizations

To access the relevant Customizing activities and core SAP Replenishment Planning application functionality,
you must have a user on the ABAP back-end server.

Create roles with the suitable authorization objects according to your demand and based on the segregation of
duties. Then assign the roles to the users depending on their tasks.

Example

Users who are responsible for the parameter maintenance receive a role that contains only the authorization
object for the parameter maintenance. Users who are responsible for running the operative replenishment
process receive a role that contains only the authorization objects for executing the replenishment calculation
and transferring order plan items.

Standard Authorization Objects

The following table shows the security-relevant authorization objects that are used by SAP Replenishment
Planning.

Authorization Object Authorization Object Field Value Field Description

Description

/DMF/ALERT Authorization for ACTVT Add Activity

generating alerts
Create
with the Generate
Alerts (/DMF/
GENERATE_ALERTS)
report.

/DMF/AOP Authorization to exe- ACTVT Execute Activity

cute a remote function
call /DMF/
AGGR_ORDER_PLAN_R
EAD for the aggregated
order plan.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

10 PUBLIC Security Information
 Authorization Object Authorization Object Field Value Field Description
Description

/DMF/DPL Authorization to do the ACTVT Execute Activity

following:

• Create forecast
corrections in the
Adjust Forecast
app.
• Create demand
influencing fac-
tors assignments
in the
Manage Demand
Influencing
Factors app.
• Filter for prod-
uct and prod-
uct hierarchy in
the apps for de-
mand forecasting
(Analyze Forecast,
Adjust Forecast,
Manage Demand
Influencing
Factors) and SAP
Replenishment
Planning (Review
Order Plan
Items, Simulate
Replenishment).
• Filter for loca-
tion and loca-
tion hierarchy in
the apps for de-
mand forecasting
(Analyze Forecast,
Adjust Forecast,
Manage Demand
Influencing
Factors) and SAP
Replenishment
Planning (Review
Order Plan
Items, Simulate
Replenishment).

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Security Information PUBLIC 11
Authorization Object Authorization Object Field Value Field Description
Description

• Use/display the
chart component
consisting of time
series chart, de-
composition chart
and table view in
the apps for de-
mand forecasting
(Analyze Forecast,
Adjust Forecast,
Manage Demand
Influencing
Factors).

/DMF/MPSCH Authorization to dis- ACTVT Display Activity

play and maintain
Maintain
procurement sched-
ules by using the
Manage Procurement
Schedules app.

/DMF/MCASG Authorization to dis- ACTVT Display Activity

play and maintain
Maintain
configuration assign-
ments by using the
Manage Configuration
Assignments app.

/DMF/MNGAT Authorization to dis- ACTVT Display Activity

play and review alerts
Maintain
by using the Manage
Alerts app.

/DMF/OP4AP Authorization for purg- ACTVT Execute Activity

ing order plan items for
aggregation with the
Purge Order Plan Items
for Aggregation (/DMF/
ORDERPLAN_4_AGG_P
URGE) report.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

12 PUBLIC Security Information
 Authorization Object Authorization Object Field Value Field Description
Description

/DMF/OPPRG Authorization for purg- ACTVT Execute Activity

ing order plan items
with Purge Order
Plan Items (/DMF/
ORDERPLAN_PURGE)
report.

/DMF/PCPWL Authorization to exe- ACTVT Execute Activity

cute parallel process-

Display
ing and to display and
change workloads in Change
the Manage Workloads
Delete
app.

/DMF/PERFM Authorization to purge ACTVT Display Activity

performance monitor-
ing data using the Delete
Purging of
Performance
Monitoring
Measurements (/DMF/
PERFORMANCE_MONIT
OR_PURGE) report.

/DMF/PMCNF Authorization to ACTVT Change Activity

display or main-
tain settings for Display
the Performance
Monitoring
Configuration.

/DMF/PRFLM Authorization to dis- ACTVT Display Activity

play and maintain pa-
Maintain
rameter profiles by
using the Manage
Cost profiles, Manage
Constraint Profiles,
Manage Shelf Cost
Profiles, Manage
Exception Profiles, and
Manage Alert Profiles
apps.

/DMF/PRGAT Authorization for ACTVT Delete Activity

purging alerts
with the Purging
of Alerts (/DMF/
PURGE_ALERTS) re-
port.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Security Information PUBLIC 13
Authorization Object Authorization Object Field Value Field Description
Description

/XRP/EXTRV Authorization to dis- ACTVT Change Activity

play and change order
plan items externally. Display

/XRP/OPANA Authorization to fetch ACTVT Execute Activity

the aggregated sched-
ule line quantities of
the purchase order
items with the Store
Order Plan Information
for Analytics (/XRP/
OPI_PO_DATA_UPD)
report.

/XRP/OPOUT Authorization to trans- ACTVT Execute Activity

fer order plan items
into an ERP system
with the Order Plan
Outbound Processing
(/XRP/
ORDERPLAN_OUTBOUN
D) report.

/XRP/OPUST Authorization to adapt ACTVT Execute Activity

the status of order plan
items with the Adapt
Status of Order Plan
Items (/XRP/
ORDERPLAN_ADAPT_S
TATUS) report.

/XRP/REPL Authorization to exe- ACTVT Execute Activity

cute the replenishment
calculation with the
Replenishment
Calculation (/XRP/
REPLENISHMENT_CAL
C) report.

/XRP/ROPI Authorization to dis- ACTVT Display Activity

play and change order
plan items by using Change
the Review Order Plan
Items app.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

14 PUBLIC Security Information
 Authorization Object Authorization Object Field Value Field Description
Description

/XRP/SIM Authorization to exe- ACTVT Execute Activity

cute the Simulate
Replenishment app
and the replenishment
simulation with the
Replenishment
Simulation (/XRP/
REPLENISHMENT_SIM
) report.

There are further applications and funtionalities in SAP Replenishment Planning that require special
authorizations. For more information about this objects and corresponding authorization objects, see Display
of Data with Tools Reports [page 59].

2.3.2 Database Roles and Authorizations

Make sure that the SELECT privilege on the SAP_ECC or SAP_S4H schema and the
AFL__SYS_AFL_XRP_EXECUTE role are granted to the SAPHANADB user. This is mandatory because the
SELECT privilege and this role are required for the successful execution of SAP Replenishment Planning.

For more information about granting this role, see Set Up Database Roles and Authorizations in the Common
Installation Guide.

2.3.3 Authorizations for Transfer of Order Plan Items to

Source Master Data System

For the transfer of order plan items from SAP Customer Activity Repository to SAP ERP or SAP S/4HANA
through Remote Function Call (RFC), the user must have certain authorizations.

The user who wants to transfer order plan items from SAP Customer Activity Repository to SAP ERP or SAP
S/4HANA needs a role with the following authorization objects in the source master data system:

Authorization Object Authorization Object Field Value Field Description

Description

M_BEST_BSA Document Type in Or- ACTVT • Create or gener- Activity

der ate
• Change
• Display change
documents
• Display prices

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Security Information PUBLIC 15
Authorization Object Authorization Object Field Value Field Description
Description

BSART Type of purchasing Purchasing document

document to be cre- type
ated. The type can
be NB (Standard
purchase order), UB
(Stock transport or-
der), or customized.

M_BEST_EKG Purchasing Group in ACTVT • Create or gener- Activity

Purchase Order ate
• Change
• Display change
documents
• Display prices

EKGRP Purchasing group for Purchasing group

which purchase orders
may be processed

M_BEST_EKO Purchasing Organiza- ACTVT • Create or gener- Activity

tion in Purchase Order ate
• Change
• Display change
documents
• Display prices

EKORG Purchase organization Purchasing organiza-

for which purchase or- tion
ders may be processed

M_BEST_WRK Plant (location) in Pur- ACTVT • Create or gener- Activity

chase Order ate
• Change
• Display change
documents
• Display prices

WERKS Plants (locations) for Plant (location)

which purchase orders
may be processed

SAP Replenishment Planning 5.0 SPS07 Administration Guide

16 PUBLIC Security Information
2.4 Network and Communication Security

Your network infrastructure is extremely important in protecting your system. Your network must support the
communication necessary for your business needs without allowing unauthorized access.

The network topology for SAP Replenishment Planning is based on the topology used by the SAP NetWeaver
platform. Therefore, the security guidelines and recommendations described in the SAP NetWeaver Security
Guide also apply to SAP Replenishment Planning. The details that specifically apply to SAP Replenishment
Planning are similar to the specific details for SAP Customer Activity Repository. For more information about
the specific details for SAP Customer Activity Repository, see section Network and Communication Security in
the SAP Customer Activity Repository Administration Guide. The specializations compared to SAP Customer
Activity Repository are described here.

Communication Channel Security

The following table shows the communication paths used by SAP Replenishment Planning and the protocol
used for the connection. This is a subset of the communication paths used by SAP Customer Activity
Repository.

Communication Paths

Communication Path Protocol Used

Front-end client using SAP GUI for Windows to application DIAG

server

Application server to application server RFC

2.5 Data Protection and Privacy

Introduction [page 17]

Glossary [page 18]

Information Retrieval [page 21]

Deletion of Personal Data [page 21]

2.5.1 Introduction

Data protection is associated with numerous legal requirements and privacy concerns. In addition to
compliance with general data protection and privacy acts, it is necessary to consider compliance with industry-

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Security Information PUBLIC 17
specific legislation in different countries. SAP provides specific features and functions to support compliance
with regard to relevant legal requirements, including data protection, which are documented in these templates
along with the assumptions that have been guiding the implementation in the software. By nature of legal
requirements the conclusion whether these features are covering customer specific demands as well as the
conclusion whether additional measures have to be taken is solely with the customer.

 Note

SAP does not provide legal advice in any form. 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. In many cases, compliance with applicable data protection and privacy laws will
not be covered by a product feature. Definitions and other terms used in this document are not taken from
a particular legal source.

 Caution

The extent to which data protection is supported by technical means depends on secure system operation.
Network security, security note implementation, adequate logging of system changes, and appropriate
usage of the system are the basic technical requirements for compliance with data privacy legislation and
other legislation.

 Note

For upgrade recommendations to support General Data Protection Regulation (GDPR) compliance, see
SAP Note 2590321 .

For more information on GDPR compliance, see https://discover.sap.com/gdpr/en-us/index.html .

Generic Fields

You need to make sure that no personal data enters the system in an uncontrolled or non-purpose related way,
for example, in free-text fields, through APIs, or customer extensions. Note that these are not subject to the
read access logging (RAL) example configuration.

2.5.2 Glossary

The following terms are general to SAP products. Not all terms may be relevant for this SAP product.

Term Definition

Blocking A method of restricting access to data for which the primary

business purpose has ended.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

18 PUBLIC Security Information
 Term Definition

Business Purpose The legal, contractual, or in other form justified reason for
the processing of personal data to complete an end-to-end
business process. The personal data used to complete the
process is predefined in a purpose, which is defined by the
data controller. The process must be defined before the per-
sonal data required to fulfill the purpose can be determined.

Consent The action of the data subject confirming that the usage
of his or her personal data shall be allowed for a given pur-
pose. A consent functionality allows the storage of a consent
record in relation to a specific purpose and shows if a data
subject has granted, withdrawn, or denied consent.

Data Subject Any information relating to an identified or identifiable natu-

ral person ("data subject"). An identifiable natural person is
one who can be identified, directly or indirectly, in particular
by reference to an identifier such as a name, an identifica-
tion number, location data, an online identifier, or to one or
more factors specific to the physical, physiological, genetic,
mental, economic, cultural, or social identity of that natural
person.

Deletion Deletion of personal data so that the data is no longer avail-

able.

End of business Defines the end of active business and the start of residence
time and retention period.

End of Purpose (EoP) The point in time when the processing of a set of personal
data is no longer required for the primary business purpose,
for example, when a contract is fulfilled. After the EoP has
been reached, the data is blocked and can only be accessed
by users with special authorizations (for example, tax audi-
tors).

End of Purpose (EoP) check A method of identifying the point in time for a data set when
the processing of personal data is no longer required for the
primary business purpose. After the EoP has been reached,
the data is blocked and can only be accessed by users with
special authorization, for example, tax auditors.

Personal Data Any information relating to an identified or identifiable natu-

ral person ("data subject"). An identifiable natural person is
one who can be identified, directly or indirectly, in particular
by reference to an identifier such as a name, an identifica-
tion number, location data, an online identifier, or to one or
more factors specific to the physical, physiological, genetic,
mental, economic, cultural, or social identity of that natural
person.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Security Information PUBLIC 19
Term Definition

Purpose The information that specifies the reason and the goal for
the processing of a specific set of personal data. As a rule,
the purpose references the relevant legal basis for the proc-
essing of personal data.

Residence Period The period of time between the end of business and the
end of purpose (EoP) for a data set during which the data
remains in the database and can be used in case of sub-
sequent processes related to the original purpose. At the
end of the longest configured residence period, the data is
blocked or deleted. The residence period is part of the over-
all retention period.

Retention Period The period of time between the end of the last business
activity involving a specific object (for example, a business
partner) and the deletion of the corresponding data, subject
to applicable laws. The retention period is a combination of
the residence period and the blocking period.

Sensitive Personal Data A category of personal data that usually includes the follow-
ing type of information:

• Special categories of personal data such as data reveal-

ing racial or ethnic origin, political opinions, religious or
philosophical beliefs, or trade union membership and
the processing of genetic data, biometric data, data
concerning health, sex life or sexual orientation or per-
sonal data concerning bank and credit accounts
• Personal data subject to professional secrecy
• Personal data relating to criminal or administrative of-
fenses
• Personal data concerning insurances and bank or credit
card accounts

Technical and Organizational Measures (TOM) Some basic requirements that support data protection and
privacy are often referred to as technical and organizational
measures (TOM). The following topics are related to data
protection and privacy and require appropriate TOMs, for
example:

• Access control Authentication features

• Authorizations Authorization concept
• Read access logging
• Transmission control/communication security
• Input control/change logging
• Availability control
• Separation by purpose Subject to the organizational
model implemented and must be applied as part of the
authorization concept.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

20 PUBLIC Security Information
2.5.3 Information Retrieval

Data subjects have the right to receive information regarding their personal data that is being processed. The
information retrieval feature supports you in complying with the relevant legal requirements for data protection
by allowing you to search for and retrieve all personal data for a specified data subject. The search results
are displayed in a comprehensive and structured list containing all personal data of the data subject specified,
organized according to the purpose for which the data was collected and processed.

To see where personal information is used, you must use the Demand Data Foundation (DDF) feature that
provides this information. For more information, see the Information Retrieval subsection of the SAP Customer
Activity Repository Administration Guide.

2.5.4 Deletion of Personal Data

Simplified Blocking and Deletion

The processing of personal data is subject to applicable laws related to the deletion of this data when the
specified, explicit, and legitimate purpose for processing this personal data has expired. If there is no longer
a legitimate purpose, that requires the retention and use of personal data, it must be deleted irrecoverably.
Blocking is necessary when the original retention period has expired but additional applicable extended and
overruling (mandated by law) retention periods are still in place. After the expiration of the longest retention
period, the data must be deleted.

Deletion of Personal Data

When considering compliance with data protection regulations, it is also necessary to consider compliance
with industry-specific legislation in different countries. A typical potential scenario in certain countries is
that personal data shall be deleted after the specified, explicit, and legitimate purpose for the processing
of personal data has ended, but only if no other retention periods are defined in legislation, for example,
retention periods for financial documents. Legal requirements in certain scenarios or countries also often
require blocking of data in cases where the specified, explicit, and legitimate purposes for the processing of
this data have ended, however, the data still has to be retained in the database due to other legally mandated
retention periods. Sometimes, transactional data are personal data with relation to a master data object, e.g.
a sales order with reference to a business partner. Therefore, the challenge for deletion and blocking is first to
handle transactional data and finally other data, such as business partner data.

This SAP product might process data (personal data) that is subject to the data protection laws applicable in
specific countries as described in SAP Note 1825544 .

For information, see SAP Customer Activity Repository Administration Guide Security Information Data
Protection and Privacy Deletion of Personal Data Expected Behavior Within Demand Data Foundation
(DDF) .

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Security Information PUBLIC 21
Deletion or Blocking of Customer or Business Partner Instances

No special processing is applied with respect to deletion of records from customers, vendors, or business
partners. If a vendor which is to be deleted is linked to one or more existing order plan items, the respective
records will still be present in the according tables and visible in the visualization tools. However, the outbound
processing of order plan items will not be able to transfer these records and issues a corresponding message.

Once a vendor is deleted, the creation of new order plan items with such a deleted vendor is no longer possible.

Deletion of Users

User information may be attached to several business or technical entities, depicting the author or editor of
the object. If the user wants or needs to be deleted, the respective user information needs to be removed from
these entities as well. There is a transaction in DDF (/DMF/PURGE_USER_ID) which takes care of the deletion,
including also the user information persisted in SAP Replenishment Planning.

2.6 Data Storage Security

SAP Replenishment Planning saves data in the SAP HANA database of the SAP system. It relies on the
underlying security features available in HANA for data protection.

For more information, see the SAP HANA Administration Guide.

2.7 Security-Relevant Logging and Tracing

SAP Replenishment Planning does not provide additional security logging and tracing above those available
within SAP NetWeaver. For more information, see the references for the following aspects:

• Regarding Logging and Tracing for ABAP, see subsection Auditing and Logging in the SAP NetWeaver
Security Guide.
• Regarding Logging and Tracing for customizing changes, use the SCU3 transaction to activate the logging
of changes to the table data.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

22 PUBLIC Security Information
2.8 Services for Security Lifecycle Management

There are services available from Active Global Support to assist you in maintaining security in your SAP
systems on an ongoing basis.

For more information about these services, see section Services for Security Lifecycle Management in the SAP
Customer Activity Repository Administration Guide.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Security Information PUBLIC 23
3 Configuration Information

Ensure a Suitable Configuration of the Enqueue Server [page 25]

To ensure the smooth operation of the replenishment calculation or order plan outbound processing,
configure the enqueue server in a suitable manner regarding the maximum number of locks.

Configure SAP Replenishment Planning [page 26]

To configure automated replenishment processes in SAP Replenishment Planning according to your
business needs, set up Customizing activities and use Business Add-Ins (BAdIs).

How to Set Up SAP Fiori Apps for SAP Replenishment Planning [page 30]
SAP Replenishment Planning includes multiple apps. See which apps are included and find out how to
set them up.

External Review of Order Plan Items [page 31]

Order plan items proposed based on the replenishment calculation can be reviewed and changed to
best meet replenishment targets and support cost-optimized ordering.

Provision of Customer-Specific Stock Parameters [page 35]

During the replenishment calculation, SAP Replenishment Planning considers stock parameters
(minimum and maximum stock) to determine the order quantity of a product for an order plan item
considering the seasonal presentation.

Configure Purchase Order Creation Based on Order Plan Items [page 36]
Order plan items calculated by SAP Replenishment Planning can be transferred to an ERP system
(SAP ERP or SAP S/4HANA) where they are grouped to be used as input for purchase orders that are
created in the ERP system.

Define the Parameterization Profiles and the Assignments [page 39]

This section provides an overview of the configuration steps for creating configuration objects and
assignments that are valid for every product location that is supposed to be processed by the
replenishment calculation.

Configure Exception Management [page 41]

Standard settings for exception management are delivered so that nothing is missing from a functional
point of view. This includes that all exceptions specific for SAP Replenishment Planning are switched
on. If necessary, you can then adjust the settings to meet the needs of your specific business
processes.

Configure Process Packaging and Parallelization [page 42]

This section provides information necessary to configure Process Packaging and Parallelization and
some recommendations for its optimum usage.

Performance [page 44]

Partition Tables for SAP Replenishment Planning [page 54]

If your replenishment scenario involves large numbers of products and locations, the relevant SAP
Replenishment Planning, Unified Demand Forecast (UDF), and Demand Data Foundation (DDF) tables
can become very large. To improve standard database operations (such as inserting, updating,
deleting, and reading) and mass operations (such as archiving or index merging), we recommend to
partition those tables. Partitioning help is available for single-host systems only, the use of multi-node
systems is currently not recommended.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

24 PUBLIC Configuration Information
3.1 Ensure a Suitable Configuration of the Enqueue Server

To ensure the smooth operation of the replenishment calculation or order plan outbound processing, configure
the enqueue server in a suitable manner regarding the maximum number of locks.

Order plan items are secured against concurrent updates via locking by means of the enqueue server. The
process steps making use of this mechanism include:

• Replenishment calculation: Obtains locks at the level of the processed product locations
• Reviewing of order plan items: Obtains locks at the level of single order plan items being adjusted
• Outbound processing of order plan items: Obtains locks at the level of order plan items that are selected
for the transfer to SAP ERP or SAP S/4HANA
• Purging of obsolete order plan items: Obtains locks at the level of order plan items that are selected for
purging with a status that allows operative processing

The number of locks managed within an SAP NetWeaver system at any single point of time is subject to an
upper limit. Therefore, this upper limit should allow for all processes running concurrently to be able to retrieve
the locks they require.

Procedure

1. Determine the maximum number of locks needed concurrently

For each of the process steps mentioned above, determine the number of locks needed at maximum. In a
parallel scenario, you can determine this number by multiplying the number of locks needed within one job
by the number of jobs being run in parallel. Please note that the number of locks heavily depends on the
selections being applied.
Example:
If a typical job size for the replenishment calculation is 2000 product location combinations and the
calculation is performed in 50 parallel jobs, the maximum total number of locks required for this process
at any point in time is roughly 2000 * 50 = 100,000. Check which of the processes might run concurrently
(for example, replenishment calculation and outbound processing of order plan items running at the same
time for different selections), and determine an upper limit that covers even peak loads.

 Tip

If you use the Process Packaging and Parallelization framework, you can derive the number of locks
from the configured task size and maximum number of work processes.

2. Check and adapt the maximum number of locks (if necessary)

Configure the parameter enq/server/schema in transaction SMENQ.
For more information on managing and configuring the enqueue server, see Administration of Application
Server ABAP. Choose Monitoring and Administration Tools for AS ABAP Managing Lock Entries using
SMENQ .

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 25
3.2 Configure SAP Replenishment Planning

To configure automated replenishment processes in SAP Replenishment Planning according to your business
needs, set up Customizing activities and use Business Add-Ins (BAdIs).

SAP Replenishment Planning is a consuming application of the Demand Data Foundation module. Therefore,
to set up SAP Replenishment Planning, in addition to make application-specific settings, you also need to
make settings in Customizing in transaction SPRO under Cross-Application Components Demand Data
Foundation . The DDF Customizing activities that are mandatory for SAP Replenishment Planning can be
found in Customizing for Replenishment Planning. Which additional DDF Customizing activities are relevant for
SAP Replenishment Planning can be found in the organizational activities in Customizing for Replenishment
Planning.

 Note

Depending on your existing settings and your business requirements, you might not need to make settings
for all activities; however, we recommend that you check all relevant DDF settings during the initial setup of
SAP Replenishment Planning.

 Note

For alert statuses, you need to ensure that the data from client 000 is cascaded to other relevant clients.

Use the following Customizing activities and Business Add-Ins in transaction SPRO under Cross-Application
Components Replenishment Planning to set up and customize SAP Replenishment Planning:

 Note

For details about a Customizing activity, read the respective Customizing activity documentation in the
system.

Mandatory Customizing Activities

Basic Settings

Customizing path: Cross-Application Components Replenishment Planning Basic Settings

• Maintain RFC Mapping

With this Customizing activity, you specify an RFC destination for each master data system to which you
want to transfer order plan items for purchase order creation.
• Define Replenishment Types Relevant for Replenishment Planning
With this Customizing activity, you define whether a product location is considered in replenishment
planning by defining replenishment types relevant for replenishment planning.

Replenishment Calculation

Customizing path: Cross-Application Components Replenishment Planning Replenishment Calculation

SAP Replenishment Planning 5.0 SPS07 Administration Guide

26 PUBLIC Configuration Information
 • Maintain Number Range for Replenishment Run ID
Use this Customizing activity to maintain the number range for the replenishment run ID.

Optional Customizing Activities and Business Add-Ins

Stock Determination

Customizing path: Cross-Application Components Replenishment Planning Stock Determination

• BAdI: Determination of Customer-Specific Stock

You can use this BAdI to determine a customer-specific stock quantity for each product location that is
considered in the replenishment planning process.
• BAdI: Adaptation of Customer-Specific Stock
You can use this BAdI to adapt the stock quantity for each product location that is considered in the
replenishment planning process.

Source of Supply Determination

Customizing path: Cross-Application Components Replenishment Planning Source of Supply

Determination

 Note

If you want internal sources of supply to be considered in the source of supply determination, you need
to include Supplying Site transportation lanes in the transfer of transportation lanes from the ERP source
system to SAP Customer Activity Repository. You can access the relevant Customizing activity in the ERP
system in transaction SPRO under Logistics General Merchandise Lifecycle Optimization Outbound
Handling of Control Parameters Maintain Control Parameters for Source of Supply .

• Define Client-Specific Settings for Source of Supply Determination

With this Customizing activity, you can activate an optional listing check for a product at a receiving
location. If the listing check is activated, the listing is considered as ranking criterion for the selection of the
preferred source of supply.
• BAdI: Determination of Valid Transportation Lanes
You can use this BAdI to implement your own logic for identifying valid transportation lanes during source
of supply determination.
• BAdI: Adaptation of Valid Transportation Lanes
You can use this BAdI to implement your own logic to add new valid transportation lanes and to change or
remove existing transportation lanes during source of supply determination.
• BAdI: Selection of Preferred Transportation Lanes
You can use this BAdI to implement your own logic for selecting preferred transportation lanes during
source of supply determination.

Scheduling

Customizing path: Cross-Application Components Replenishment Planning Scheduling

• Define Client-Specific Settings for Scheduling

With this Customizing activity, you can define whether the staging date and time of a product location are
to be calculated if they are not provided in a procurement schedule and also define if the replenishment

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 27
 block and its start date defined for a product location are considered in the replenishment calculation.
You can also enable the use of scheduling information from SAP Order and Delivery Scheduling by SAP
Replenishment Planning.
• BAdI: Adaptation of Replenishment Schedule
You can use this BAdI to adapt the replenishment schedule that was calculated by the system.
• BAdI: Deactivation of Listing Check for Schedule Items
You can use this BAdI to deactivate the listing check on procurement schedule items that are used as a
basis for calculating replenishment schedules.

Open Goods Movements

Customizing path: Cross-Application Components Replenishment Planning Open Goods Movements

• Define Purchase Order Document Types for Promotion Quantity Reservation

With this Customizing activity, you can define which purchase order document types are considered for
the promotion quantity reservation.
• BAdI: Adaptation of Open Goods Movements Based on Order Plan
You can use this BAdI to adapt open goods movements that have been derived from order plan items.
• BAdI: Adaptation of Open Goods Movements Based on Purchase Orders
You can use this BAdI to adapt open goods movements that have been derived from purchase orders.

Replenishment Calculation
Customizing path: Cross-Application Components Replenishment Planning Replenishment Calculation

• Define Client-Specific Settings for Order Units and Rounding

With this Customizing activity, you can define client-specific settings that control if multiple order units are
to be allowed and how rounding rules are applied for the replenishment calculation.
• Define Client-Specific Settings for Minimum Order Quantity
With this Customizing activity, you can control whether the minimum order quantity defined for a product
location is considered in the replenishment calculation.
• BAdI: Adaptation of Non-Listing Periods for Replenishment Calculation
You can use this BAdI to adapt the non-listing periods that were determined by the system for use in the
replenishment calculation.
• BAdI: Reduce Worklist for Replenishment Calculation
You can use this BAdI to reduce the worklist of the replenishment calculation by excluding product
locations from being processed by removing them from the worklist.
• BAdI: Adaptation of Calculated Order Quantity and Unit
You can use this BAdI to adapt the order quantity and/or order units of operative and fallback order plan
items calculated by the replenishment calculation before they are stored to the database.

Replenishment Configuration
Customizing path: Cross-Application Components Replenishment Planning Replenishment
Configuration

• BAdI: Modification of Control Paramter Values

You can use this BAdI to change the values of control parameters of configuration objects assigned to
product locations that are considered in the replenishment planning process.

Order Plan Processing

Customizing path: Cross-Application Components Replenishment Planning Order Plan Processing

SAP Replenishment Planning 5.0 SPS07 Administration Guide

28 PUBLIC Configuration Information
 • Define Change Reasons for Order Plan Items
With this Customizing activity, you can define reasons for manual changes of order plan items.
• Configure Order Plan Item Change History
With this Customizing activity, you can enable and configure the order plan item change history.
• BAdI: Order Plan Outbound - Selection of Order Plan Items
You can use this BAdI to implement your own logic to select order plan items for the order plan outbound
processing.
• BAdI: Order Plan Outbound - Adaptation of Order Plan Items
You can use this BAdI to implement your own logic to add new order plan items and to change or remove
existing order plan items for the order plan outbound processing.
• BAdI: Aggregation of Order Plan Items - Definition of Order Horizon Start
You can use this BAdI to implement your own logic to define which order plan items that have not yet been
used for the creation of purchase orders should be excluded from the aggregation process.
• BAdI: Aggregation of Order Plan Items - Definition of Excluded Document Types
You can use this BAdI to implement your own logic to exclude open stock transport orders from the
aggregation process based on their document type.

Performance Monitoring

Customizing path: Cross-Application Components Replenishment Planning Performance Monitoring

• Define Measured Units for Performance Monitoring

With this Customizing activity, you can define measured units that you want to be available for
performance monitoring.
• Define Reference Key Figure Types for Performance Monitoring
With this Customizing activity, you can define reference key figure types that you want to use in the
performance monitoring.
• Define Characteristic Types for Performance Monitoring
With this Customizing activity, you can define characteristic types that you want to use in performance
monitoring.
• BAdI: Definition of Additional Characteristics for Performance Measurements
You can use this BAdI to add characteristics relevant for later analysis to a performance measurement.

Analytics

Customizing path: Cross-Application Components Replenishment Planning Analytics

• Define Client-Specific Settings for Analytics

With this Customizing activity, you can define whether the adapted order quantity of a purchase order item
is to be stored in the order plan item based on which the purchase order item was created in addition to the
order quantity proposed in the order plan item .
Furthermore, you can define whether additional order plan item for aggregation data is calculated for
analytical evaluations.

Alert and Exception Management

Customizing path: Cross-Application Components Replenishment Planning Alert and Exception

Management

• Maintain Configuration Data for High Level Exceptions

With this Customizing activity, you can change configuration settings for high level exceptions. For more
information, see Configure Exception Management [page 41].

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 29
• Maintain Configuration Data for Low Level Exceptions
With this Customizing activity, you can change configuration settings for low level exceptions. For more
information, see Configure Exception Management [page 41]
• Define Alert Statuses
With this Customizing activity, you can define alert statuses for the Manage Alerts app.

 Note

If you want to add several custom statuses based on your scenario, you must define them using
this Customizing activity. For more information on how to access this Customizing, see the SAP
Replenishment Planning application help and search for Alert Management.

• Maintain Alert Key Figures

With this Customizing activity, you can manage key figures for alerts.
• Define Alert Types and Key Figure Assignments
With this Customizing activity, you can manage alert types and assign key figures to them. You can
maintain key figures and weighting factors for each of the alert types based on your business scenario.
• BAdI: Adaptation of Alert Scoring
You can use this BAdI to implement your own scoring logic for the alert types.
• BAdI: Adaptation of Alerts
You can use this BAdI to implement your own logic to generate alerts for the new custom alerts.

Process Packaging and Parallelization

Customizing path: Cross-Application Components Replenishment Planning Process Packaging and

Parallelization

• Maintain Basic Settings

With this Customizing activity, you can maintain basic settings for process packaging and parallelization.
• Define Parameters for Workload Types
With this Customizing activity, you can maintain parameters related to predefined workload types.
• BAdI: Set Preconditions for Processing
You can use this BAdI to set preconditions for processing of workloads in process packaging and
parallelization.

3.3 How to Set Up SAP Fiori Apps for SAP Replenishment

Planning

SAP Replenishment Planning includes multiple apps. See which apps are included and find out how to set them
up.

• For a list of the apps, see the Getting Started with SAP Replenishment Planning section in the application
help for SAP Replenishment Planning at https://help.sap.com/viewer/p/CARAB.
• For setup instructions for the apps, see the Set Up SAP Fiori Apps for SAP Replenishment Planning
section of the Common Installation Guide at https://help.sap.com/viewer/product/CARAB/latest/en-US?
task=implement_task.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

30 PUBLIC Configuration Information
3.4 External Review of Order Plan Items

Order plan items proposed based on the replenishment calculation can be reviewed and changed to best meet
replenishment targets and support cost-optimized ordering.

In general, order plan items are reviewed with the Review Order Plan Items app by central replenishment
planners who are responsible for the replenishment in multiple locations. If the order plan items are to be
reviewed or changed externally by the store personnel in separate store systems, these store systems must be
integrated in the order plan management process.

SAP Replenishment Planning provides an Application Programming Interface (API) to suppport the integration
of external store systems for reviewing order plan items.

The API supports the following use cases:

• Retrieve order plan items for display

• Change order plan items for approval (set the corresponding order plan item status without changing the
item itself)
• Change the order quantity and/or order unit of an order plan item
• Delete order plan items logically

Integrate External Review

If you want to integrate processes to review and change order plan items externally, you must implement the
External Review API to setup the retrieval and update of data.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 31
Retrieve Data for External Review
Perform the following steps to select and retrieve order plan items:

1. Create an instance of the External Review API with the method /XRP/
CL_ORDERPLAN_4_EXTREVIEW>GET_RETRIEVAL_INSTANCE.
The instance provides the methods of the interface /XRP/IF_GET_ORDPLN_4_EXTREVIEW.
Besides the order plan item data, the interface allows the retrieval of metadata required to interpret and
change order plan items:
• Order Plan Item Status: List of available values with language-dependent descriptions.
• Changeable Fields: List of fields you can change with language-dependent descriptions. Only the fields
available in this list can be changed.
• Change Reason: List of available change reasons with language-dependent descriptions. Only change
reasons available in this list can be used.
2. Optional: If you want to measure the performance of the retrieval process, you must enable performance
monitoring for your process to allow the measurements. For more information, see How to Integrate
Performance Monitoring in Customer-Specific Processes [page 51]. If performance monitoring has been
enabled for the retrieval process, hand over an instance for performance monitoring.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

32 PUBLIC Configuration Information
 3. Optional: If you want to gather information from multiple retrieval processes in one central application
log, hand over an instance for application log handling. If you do not hand over an instance, each retrieval
process writes an own application log (object /XRP, subobject /XRP/ORDPLN_EXTRVW).
4. Select order plan items for the retrieval.

 Note

To select order plan items for retrieval, you need the authorization object /XRP/EXTRV with activity
Display (02).

Depending on your logic, you can select order plan items either by a list of internal identifiers (UUIDs) or by
external identifiers with additional selection criteria, for example, the scheduling group. Besides this, you
can define additional parameters to restrict or enlarge the selection of order plan items:
• By default, only order plan items that can be changed are retrieved. If you want to retrieve all
available order plan items, including items that cannot be changed, set the import parameter
IV_INCLUDE_READ_ONLY_ITEMS.
• By default, only order plan items with an order quantity unequal to zero are retrieved. If you want
to retrieve all available order plan items, including items with the order quantity zero, set the import
parameter IV_INCLUDE_0_QUAN_ITEMS.
• By default, only operational order plan items are retrieved. If you want to retrieve operational and
fallback order plan items, set the import parameter IV_INCLUDE_FALLBACK_ITEMS.

The interface returns the selected order plan items with internal and external identifiers of the product, the
supplying location, the receiving location, and the internal identifiers of the order plan items. In case that the
application that retrieves the order plan items is not able to handle the provided structure of the items, it might
be required to implement a customer-specific buffering of the retrieved order plan item data.

Update Data from External Review

Perform the following steps to change order plan items and persist the changes:

1. Create an instance of the External Review API with the method /XRP/
CL_ORDERPLAN_4_EXTREVIEW>GET_UPDATE_INSTANCE.
The instance provides the methods of the interface /XRP/IF_UPD_ORDPLN_FROM_EXTREV.
2. Optional: If you want to measure the performance of the update process, you must enable performance
monitoring for your process to allow the measurements. For more information, see How to Integrate
Performance Monitoring in Customer-Specific Processes [page 51]. If performance monitoring has been
enabled for the update process, hand over an instance for performance monitoring.
3. Optional: If you want to gather information from multiple updates in one central application log, hand over
an instance for application log handling. If you do not hand over an instance, each update writes an own
application log (object /XRP, subobject /XRP/ORDPLN_EXTRVW).
4. Optional: If you want to gather exceptions from multiple updates before they are persisted centrally, hand
over an instance for the Demand Data Foundation (DDF) exception handling. If you do not hand over an
instance, each update persists the DDF exceptions by itself.
5. Display or change the order plan items depending on your use case.

 Note

To select order plan items for retrieval, you need the authorization object /XRP/EXTRV with activity
Change (03).

You can define parameters that influence the logic for the update of order plan items:

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 33
 • By default, only unchanged order plan items are updated. If you want to update all available order
plan items, including items that have been changed since the last retrieval, set the import parameter
IV_OVERWRITE_CHANGES.
• By default, the current system user is used for the update. If you provide a user with the import
parameter IV_USER, the updates from the external review are performed by the imported user instead
of the current user. The imported user also needs the authorization to change order plan items.

The interface performs consistency checks. Therefore, the order plan items must be imported completely as
they were provided by the retrieval. In the following cases, the update of an order plan item is rejected:

The order plan item cannot be updated.

The order plan item cannot be updated for the following reasons:

• The order plan item cannot be locked against changes from other processes.
• The order plan item status does not allow a change of the order plan item.
• The delivery date and time of the order plan item are in the past.
• The order plan item has been changed in the backend since the last retrieval and the parameter
IV_OVERWRITE_CHANGES has not been set.

The update is invalid.

The update can be invalid for the following reasons:

• An unchangeable field has been changed.

• The change reason of the order plan item is not available in Customizing.
• Multiple update entries exist for an order plan item.
• A new order plan item has been created.
• The changed order quantity and/or order unitis not valid.
• The order plan item has been deleted logically but a field has been changed.
• A field of an order plan item has been changed, but the target status does not allow a change.
• The order plan item status cannot be set to Changed Manually.

If the update of an order plan item is rejected, a high-level exception is added to the DDF exception handling.
The assigned low-level exceptions allow you an analysis of the underlying root cause.

More Information

For detailed information about the implementation of the External Review API, see the documentation in the
backend system for the following objects:

• Interface /XRP/IF_GET_ORDPLN_4_EXTREVIEW and all corresponding interface methods

• Interface /XRP/IF_UPD_ORDPLN_FROM_EXTREV and all corresponding interface methods
• Class /XRP/CL_ORDERPLAN_4_EXTREVIEW and all corresponding class methods

SAP Replenishment Planning 5.0 SPS07 Administration Guide

34 PUBLIC Configuration Information
3.5 Provision of Customer-Specific Stock Parameters

During the replenishment calculation, SAP Replenishment Planning considers stock parameters (minimum
and maximum stock) to determine the order quantity of a product for an order plan item considering the
seasonal presentation.

In general, stock parameter information that is not time-dependent (/DMF/PRODLOC-MIN_STOCK and /DMF/
PRODLOC-MAX_STOCK) is replicated from the product location master data (MARC-EISLO and MARC-MABST) in
the ERP system into Demand Data Foundation (DDF).

SAP Replenishment Planning provides an Application Programming Interface (API) (/DMF/

IF_CUST_TD_MINMAX_STOCK) to support the use of customer-specific time-dependent stock parameter
information for the calculation of order plan items.

Provide and Delete Customer-Specific Stock Parameter Data

If you want to use your customer-specific time-dependent minimum and maximum stock information, you
must implement the API to provide, update, or delete time-dependent minimum and maximum stock data.

 Note

The customer-specific time-dependent minimum and maximum stock data can be provided separately, so
it is possible to provide values only for one of the stock parameters.

Provide or Update Customer Specific Data

Perform the following steps to provide customer-specific time-dependent minimum and maximum stock data
by updating existing data:

1. Create an instance of the API with the method /DMF/CL_CUST_TD_MINMAX_STOCK>GET_INSTANCE.

The instance provides the methods of the interface /DMF/IF_CUST_TD_MINMAX_STOCK.
2. Use the method M_UPDATE_CUST_TD_MINMAX_STOCK and select product locations for which you want to
provide or update customer-specific time-dependent stock parameters. You select the product locations
by a list of internal identifiers (UUIDs).
Before the data can be provided or updated, the system performs consistency checks. In the following
cases, the update is rejected:
• The product locations cannot be locked
• The imported product locations are marked for deletion
• The imported validity periods are not defined correctly
• The imported validity periods overlap

The interface method updates the existing stock parameter data as a block, which means that existing
data for the imported product locations is replaced by the imported customer-specific time-dependent stock
parameter data of the product locations.

Delete Customer-Specific Data

1. Create an instance of the API with the method /DMF/CL_CUST_TD_MINMAX_STOCK>GET_INSTANCE.
The instance provides the methods of the interface /DMF/IF_CUST_TD_MINMAX_STOCK.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 35
2. Use the method M_DELETE_CUST_TD_MINMAX_STOCK and select product locations for which you want to
delete the stock parameter data. You select the product locations by a list of UUIDs.

The interface method deletes the customer-specific time-dependent stock parameter for the imported product
locations.

More Information

For detailed information about the implementation of the API, see the documentation in the backend system of
the class /DMF/CL_CUST_TD_MINMAX_STOCK and all corresponding class methods.
For more information about the use of customer-specific stock parameters and their determination as part
of the replenishment calculation, see the sections Customer-Specific Stock Parameters and Stock Parameter
Determination in the SAP Replenishment Planning Application Help.

3.6 Configure Purchase Order Creation Based on Order

Plan Items

Order plan items calculated by SAP Replenishment Planning can be transferred to an ERP system (SAP ERP
or SAP S/4HANA) where they are grouped to be used as input for purchase orders that are created in the ERP
system.

To create purchase orders based on order plan items, SAP Replenishment Planning makes use of the Grouping
of Order List Items into Purchase Orders function provided in the ERP system. You must configure the function
by making the relevant Customizing settings in Customizing for Materials Management under Purchasing
Order Optimizing Grouping of Order List Items into Purchase Orders .

After having configured the grouping, you can create purchase orders based on order plan items with the
Process Order List Items (R_MMPUR_RPO_START_PROCESSING) report.

Prerequisites

To use the Grouping of Order List Items into Purchase Orders function, you need to ensure that the following
Customizing settings have been made in Customizing for Materials Management under Purchasing
Purchase Order .

Define Document Types

Purchase orders are managed as documents. With this Customizing activity, you define purchasing document
types relevant for replenishment planning. By default, SAP Replenishment Planning relies on the following
standard document types:

• Standard Purchase Order (NB)

SAP Replenishment Planning 5.0 SPS07 Administration Guide

36 PUBLIC Configuration Information
 • Stock Transport Order (UB)

Depending on the business scenario, the system determines the assigned purchasing document type. By
default, the following assignment is applied:

Business Scenario Assigned Document Type

Internal Replenishment Stock Transport Order (UB)

Internal Replenishment Cross Company Standard Purchase Order (NB)

External Replenishment Standard Purchase Order (NB)

If you want to assign other document types than the default assignment, you can implement the Business Add-
In (BAdI) BAdI: Enhancement of Business Logic Grouping API in Customizing for Materials Management under
Purchasing Order Optimizing Grouping of Order List Items into Purchase Orders Business Add-Ins .

 Note

You can use the document types as a filter criteria in SAP Customer Activity Repository to determine
which purchase orders should be provided to the ERP system. For this, you can implement the BAdI BAdI:
Aggregation of Order Plan Items - Definition of Excluded Document Types in Customizing in transaction
SPRO under Cross-Application Components Replenishment Planning Order Plan Processing .

Configuration Steps

To group order plan items into purchase orders, make the following Customizing settings in Customizing for
Materials Management under Purchasing Order Optimizing Grouping of Order List Items into Purchase
Orders :

1. Edit Purchasing Document Types and Grouping Criteria

With this Customizing activity, you maintain all defined purchasing document types that you want to use
in the Grouping of Order List Items into Purchase Orders function and assign them to a location type (store
and/or distribution center) based on your supported business scenario.
By default, order list items are grouped by the following criteria:
• BSART: Purchasing Document Type
• BUKRS: Company Code
• EKGRP: Purchasing Group
• EKORG: Purchasing Organization
• LIFNR: Supplier Account Number
• WAEHR: Currency
You can also define additional grouping criteria for each purchasing document type that are used to split
order plan items into multiple purchase orders.

 Note

You must at least define the Ordering Time (UTC Time Stamp in Long Form) as additional grouping
criterion to define whether multiple purchase orders can be created for a product per day.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 37
2. Define Status Control
The Grouping of Order List Items into Purchase Orders function supports a specific release procedure for
purchase orders that can overrule the general release procedure for purchase orders that can be defined
in Customizing for Materials Management under Purchasing Purchase Orders Release Procedure for
Purchase Orders .
With the Customizing activity Define Status Control, you define the Status Determination Code for grouping
that specifies how the status of a purchase order is set depending on whether the purchase order is
relevant for the predefined release procedure or not. How many status determination codes you must
define, depends on the purchasing document types you previously defined.

 Note

If you want to determine or change the currently selected release strategy, use the function module
ME_REL_STRATEGIE_EKKO.

• Set the Release Strategy-Relevant (Rel.-Relv.) flag if the purchase order is relevant for the selected
release procedure according to the assigned purchasing document type and the corresponding
definition of the release strategy.
• Set the Release Type to Automatic release.
The Release Type defines how the purchase order Category of Incompleteness is set after the order
time has passed.
• Make sure that the Not Grouping-Relevant (No Grp.) flag is not set.
• Set the Category of Incompleteness to Document Parked or Document on Hold.
The status determination code you defined will be assigned to control characteristics (control codes).
Depending on the selected release strategy for purchase orders, the system ensures that the right status
determination code is assigned.
3. Define Control Characteristics
With this Customizing activity you define a control code that consists of settings for processing order list
items into purchase orders:
• Set the Write Preference to Not specified
This setting is not relevant for replenishment planning as incoming order plan items do not overwrite
exisitng items.
• Select a predefined Status Determination Code.
• Set Obsolete OLI accepted to Customer specific logic
Order plan items whose order date and time is before the current date and time plus the additional
order time buffer are obsolete per definition and not considered for purchase order creation. This
setting ensures that obsolete order plan items are considered for purchase order creation.

 Note

To enable the consideration of obsolete order plan items, you must implement the BAdI BAdI:
Enhancement of Business Logic in Processing API (BADI_MMPUR_RPO_PROC)

• Set Validate Obsolete OLI to Validation done by Data Transfer.

This setting causes the system to validate already while transferring order plan items from SAP
Customer Activity Repository to the ERP system if the order plan item can be considered for purchase
order creation.
• Define a Order Time Buffer (Ord. Buf.) in minutes.
This order time buffer depends on the job frequency of the report Process Order List Items. By adding
the time buffer to the ordering date of an order list item, the release time of a purchase order is

SAP Replenishment Planning 5.0 SPS07 Administration Guide

38 PUBLIC Configuration Information
 postponed. Every order list item that is being processed after this time buffer is not considered for the
creation of purchase orders.
• Set the Partially Save (Prtly Save) flag.
This setting specifies that a purchase order can be saved including erroneous data. This means that a
purchase order is created although the regular checks for the creation have failed. The erroneous data
must be corrected manually before the purchase order can be released.
4. Assign Control Code to Document Types
With this Customizing activity, you assign control codes that you have previously defined to the according
purchasing document types.
5. Activate Grouping
With this Customizing activity, you activate the Grouping of Order List Items into Purchase Orders function.
This needs to be done to create purchase orders based on order plan items.

Integration

You can review purchase orders or create new purchase orders for a product with the Order Products app
provided in the ERP system. The app allows you to see detailed information about open order quantities,
available stock, promotion periods, and historical sales data.

If you want to review purchase orders created based on order plan items with the Order Products app,
you need to make the following settings in Customizing for Logistics - General under Store Operations
In-Store Merchandise and Inventory Management - UI5 Apps Order Products Define Basic Settings for Order
Products Order Products Basic Customizing Settings :

• Set the Order Document Type to 002 Purchase Order (on hold).
• Set the Description to Standard.
• Set the Is Standard flag.
• Make sure that the flags Exception Enabled (Exc Enabld) and Range of Coverage Enabled (RCov Enbld) are
not set.

3.7 Define the Parameterization Profiles and the

Assignments

This section provides an overview of the configuration steps for creating configuration objects and
assignments that are valid for every product location that is supposed to be processed by the replenishment
calculation.

The configuration objects comprise of single control parameters, groups of parameters (so-called profiles),
as well as other structured objects (such as an entire procurement schedule). For a comprehensive list of
the configuration objects, see the subsection Replenishment Configuration in the Application Help for SAP
Replenishment Planning at https://help.sap.com/viewer/product/CARAB/latest/en-US?task=use_task.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 39
Prerequisites

1. You are familiar with the configuration concept, especially with the various configuration objects and the
ways to assign them to product locations. For information about the configuration concept, see subsection
Replenishment Configuration in the application help.
2. You are familiar with the various use cases. The configuration hints therein will help you to find the right
parameterization matching to your specific business requirements. As an entry point, you can use the
use case Use Basic Cost-Optimized Ordering and refine your configuration with further use cases. For
information about the use cases, see subsection Use Cases in the application help.

Create and Assign Configuration Objects

1. Create or import procurement schedules. For more information about the maintenance of the
procurement schedules using an app, see the section Manage Procurement Schedules in the
application help. For more information about importing procurement schedules from another system
(inbound processing of procurement schedules), see the documentation of the function module /DMF/
MDIF_PRCSCHD_INBOUND in the system.
2. Configure the parameters in profiles according to your business requirements. For more information about
the configuration of the parameters using apps, see the following sections in the application help:
• Manage Cost Profiles
• Manage Shelf Cost Profiles
• Manage Constraint Profiles
• Manage Exception Profiles
3. You can assign configuration objects to the product locations based on product hierarchy nodes and
location hierarchy nodes. For uniqueness and unambiguity, these assignments can only use hierarchy
nodes from one product hierarchy and one location hierarchy. In turn, these hierarchies must contain all
the nodes relevant for assignments. You have to select these hierarchies prior to creating assignments.
To select these hierarchies, use the transaction /DMF/CONFIGHIER_SET in your ABAP back-end system
according to the following steps:
• You can access the Define Hierarchies for Configuration Assignments transaction either in the
system on the SAP Easy Access screen (transaction /DMF/CONFIGHIER_SET) or from the SAP Fiori
Launchpad ( Define Hierarchies Configuration Assignments) tile.
• Ensure that one record exists for each connected master data system which hosts product locations
that are subject to SAP Replenishment Planning. Within these records, specify the product and
location hierarchies that should be used for assignments of configuration objects to product locations
originating from the respective master data system.
4. Assign the parameters and profiles to the product locations. We recommend that you assign them on
global level initially so that they are valid for all product locations without corresponding parameter or
profile assignments on any lower level. Depending on your business requirements, you can create more
specific assignments.
The alert generation process can read (using extension concept) the configuration objects (alert profiles)
assigned within the manage configuration assignment application and use them for the alert generation.
You must configure the configuration objects for every product that you want to be used in the alert
generation process. Hence, it is recommended that you provide alert profiles on the product hierarchy level
and provide a more specific alert profile on the product level. Configure the thresholds in alert profiles

SAP Replenishment Planning 5.0 SPS07 Administration Guide

40 PUBLIC Configuration Information
 according to your business requirements. Use Manage Alert Profiles app for creating alert profiles. For
more information, see section Manage Configuration Assignments in the application help.
5. Assign procurement schedules to product locations depending on your business requirements. Common
procurement schedules are usually applicable for groups of product locations based on special
characteristics. You have to create the assignments accordingly. If, for example, all products in a location
which share the same scheduling group should share the same procurement schedule, you would have to
create assignments specifying the procurement schedule on the assignment level Location, with specific
conditions based on the Scheduling Group attribute. Unlike for the parameters, it is rather unusual
that there is one procurement schedule which can be assigned on global level as a fallback. For more
information, see section Manage Configuration Assignments in the application help.

3.8 Configure Exception Management

Standard settings for exception management are delivered so that nothing is missing from a functional point of
view. This includes that all exceptions specific for SAP Replenishment Planning are switched on. If necessary,
you can then adjust the settings to meet the needs of your specific business processes.

We recommend that you check especially the settings for high-level exceptions.

Settings for High-Level exceptions

You can change the settings for high-level exceptions using the Customizing activity Maintain Configuration
Data for High Level Exceptions in Customizing for Cross-Application Components under Replenishment
Planning Alert and Exception Management .

We recommend that you check especially the following settings:

Assignment to Business Areas

Exceptions that might occur during the replenishment calculation or the order plan transfer are assigned to
one or two of the following business areas by default:

• 61 Replenishment Order Plan Transfer

• 62 Replenishment Review Order Plan Items
• 63 Replenishment Calculation
• 64 Replenishment Review Order Plan Items externally

You can change the assignments according to your needs. Further business areas are relevant for
SAP Replenishment Planning. For more information, see the subsection Exception Management of the
Application Help for SAP Replenishment Planning at https://help.sap.com/viewer/product/CARAB/5.latest/
en-US?task=use_task.

Validity Period
You can set the validity period (maximum number of days that an exception object is stored) until the exception
can be deleted by the Purging Exceptions from the Database report. You can access this report in the system
on the SAP Easy Access screen (transaction /DMF/PURGE_EWB_MSG). For more information about purging

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 41
exceptions, see subsection Monitor Exceptions in the application help for SAP Customer Activity Repository at
https://help.sap.com/viewer/product/CARAB/latest/en-US?task=use_task.

Priority
You can adjust the priority for each exception. Exceptions that are not relevant are switched off; that is, they are
not generated during runtime.

Settings for Low-Level exceptions

You can change the settings for low-level exceptions using the Customizing activity Maintain Configuration Data
for Low Level Exceptions in Customizing for Cross-Application Components under Replenishment Planning
Alert and Exception Management .

We recommend that you check especially the following setting:

Default Priority
You can adjust the default priority for each exception. Exceptions that are not relevant are switched off; that is,
they are not generated during runtime.

Relevant DDF settings

We also recommend that you check all relevant DDF settings during the initial setup of SAP Replenishment
Planning.

This includes the following optional settings:

• You can replace standard exception texts by user-defined texts using the Customizing activity Define
Customer-Specific Replacement Messages.
• You can create custom statuses for exception messages using the Customizing activity Define
Customizable Message Status.

For more information about these settings, see the organizational Customizing activity Alert and Exception
Management (DDF) in Customizing for Cross-Application Components under Replenishment Planning Alert
and Exception Management .

3.9 Configure Process Packaging and Parallelization

This section provides information necessary to configure Process Packaging and Parallelization and some
recommendations for its optimum usage.

Process Packaging and Parallelization (PPP) focuses on creating well-defined work packages and executing
them as parallel tasks to optimize the utilization of your computational resources and timely completion of
your time-critical processes in SAP Replenishment Planning.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

42 PUBLIC Configuration Information
For more information, see the section Process Packaging and Parallelization in the application help for SAP
Customer Activity Repository at https://help.sap.com/viewer/product/CARAB/latest/en-US?task=use_task.

Process Packaging and Parallelization supports the following replenishment planning processes:

Process Workload Type

Replenishment calculation Replenishment Calculation

Replenishment calculation for aggregation

Order plan transfer Order Plan Outbound

For more information about monitoring and managing these processes, see Monitoring [page 55] and
Management [page 65].

Customizing Settings

Customizing path: Cross-Application Components Replenishment Planning Process Packaging and

Parallelization

• Maintain Basic Settings

With this Customizing activity, you can maintain basic settings for process packaging and parallelization.

 Note

To use the Dispatcher Daemon for processing of workloads, you must

execute the one-time report Set up Start Up Configuration (transaction /DMF/
PCP_DISP_START) in the system. For information on ABAP Daemons,
see https://help.sap.com/docs/ABAP_PLATFORM_NEW/753088fc00704d0a80e7fbd6803c8adb/
311af9b769d84fffa7b7384bae27109c.html?version=202009.001.

• Define Parameters for Workload Types

 Note

The workload type you wish to configure must be available and the data from client 000 must be
cascaded to other relevant clients.

With this Customizing activity, you maintain the size of each workload task (Task Size) and the maximum
work processes (Max WP) you wish to run in parallel for Replenishment Calculation and Order Plan
Outbound, the predefined workload types for replenishment planning.
• BAdI: Set Preconditions for Processing
You can use this BAdI to set preconditions for processing of workloads in process packaging and
parallelization.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 43
Recommendations for Scheduling

For optimum use of Process Packaging and Parallelization in the supported replenishment planning processes,
we have the following recommendations:

• If you plan to create workloads on a periodic basis, use the Application Job app.
• If you plan to create workloads as a one-time activity, use the Manage Workloads app.
• Select the Use Parallel Processing option in the Replenishment Calculation (/XRP/REPLENISHMENT_CALC)
and the Order Plan Outbound Processing (/XRP/ORDERPLAN_OUTBOUND) reports for the creation of
workloads only as an alternative option to the Manage Workloads and Application Job apps but not as
a standard practice.

3.10 Performance

Optimize Performance [page 44]

Get recommendations on how to optimize the performance of your replenishment-related processes.
As the application function library (SAP XRP AFL) runs directly in the SAP HANA database,
performance considerations for SAP HANA are also relevant, and included here.

Performance Monitoring [page 47]

To ensure an efficient performance by detecting possible performance issues early on in all phases of
the software lifecycle, such as implementation, or production, SAP Replenishment Planning provides a
framework to integrate performance monitoring in the central replenishment processes. Performance
monitoring collects data about the used runtime of a process or process step.

How to Integrate Performance Monitoring in Customer-Specific Processes [page 51]

In addition to the standard implementation of the performance monitoring in the central replenishment
processes, you can integrate performance monitoring in the coding of your own processes.

3.10.1 Optimize Performance

Get recommendations on how to optimize the performance of your replenishment-related processes. As

the application function library (SAP XRP AFL) runs directly in the SAP HANA database, performance
considerations for SAP HANA are also relevant, and included here.

Get Performance Tips for Different Scenarios in SAP Customer Activity

Repository applications bundle

An SAP Note is available that points you to performance tips for different scenarios and consuming
applications. You can use this note as your main entry point to performance information for SAP Customer
Activity Repository applications bundle.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

44 PUBLIC Configuration Information
Procedure

1. See SAP Note 2958143 Performance recommendations for SAP Customer Activity Repository
applications bundle 5.0.

 Note

You can also access this SAP Note directly from SAP Help Portal. See https://help.sap.com/viewer/p/
CARAB under Implement.

Check SAP Notes for Latest Performance Corrections

Since your version of SAP Customer Activity Repository applications bundle was released, new performance
enhancements and corrections might have become available.

Procedure
1. For up-to-date information, see SAP Help Portal at https://help.sap.com/viewer/p/CARAB and select your
version from the dropdown.
2. Under Implement, see the two release information notes (RINs). The RINs are release-specific. There is
always one RIN listing the latest back-end corrections, and one RIN listing the latest front-end corrections.
3. Under Performance, see the overall performance note for SAP Customer Activity Repository applications
bundle.
4. Implement any enhancements and corrections applicable to your scenario.

Install Latest AFL Patch (Component SAP XRP AFL)

A new AFL patch may contain performance improvements. Therefore, it is highly recommended to install
the latest patch. The application function library for SAP Replenishment Planning is delivered in software
component SAP XRP AFL. Check if a new patch of the component is available on the SAP Support Portal. If so,
install the patch in your SAP HANA system.

 Note

The revision of SAP XRP AFL must always be compatible with the revision of the SAP HANA database.
Within the same revision, however, you can still upgrade the AFL to a newer patch.

Example

• Your current revision of SAP XRP AFL is:

Revision 44.200 for SAP HANA Platform 2.0 SPS04 Revision 44.02
• A new patch of SAP XRP AFL might be:
Revision 44.201 for SAP HANA Platform 2.0 SPS04 Revision 44.02

For download and installation instructions, see the Download and Install SAP XRP AFL (Only for SAP
Replenishment Planning) section in the Common Upgrade Guide or Common Installation Guide.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 45
Configure SAP HANA Workload Management (Recommended)

We highly recommend that you use SAP HANA workload management to control how much system resources
should be assigned to the replenishment-related calculations. This is an important measure to ensure the
stability of your system. Without workload management, SAP HANA can use so many resources (CPU and
memory) that your system may become unresponsive when running load-intensive jobs.

Procedure
1. Familiarize yourself with SAP HANA workload management:
• See the SAP HANA Administration Guide for SAP HANA Platform at https://help.sap.com/viewer/p/
SAP_HANA_PLATFORM. Search for section Workload Management and consult also the subsections.
• See SAP Note 2222250 (FAQ: SAP HANA Workload Management). In particular, read the following
sections:
• 4. How can workload management be configured for memory?
• 5. How can workload management be configured for CPU and threads?
• 8. How can workload classes be mapped to users and applications?
2. Configure SAP HANA workload management as required for your scenario.

Optimize SAP HANA Performance

The application function library SAP XRP AFL runs directly in the SAP HANA database.

Optimizing the performance of your SAP HANA system is therefore also of interest for the replenishment-
related processes.

Procedure
1. Compare your current SAP HANA parameter settings against the latest parameter recommendations.
Adjust your settings where required, based on the following references:
• SAP Note 1969700 (SQL Statement Collection for SAP HANA)
• SAP Note 2186744 (FAQ: SAP HANA Parameters)

 Note

Perform this check on a regular basis, in particular, after upgrading your SAP HANA system. Also, both
SAP Notes are regularly updated as recommendations change or new ones are added.

2. Consult the latest performance recommendations for SAP HANA Platform:

Your main references are as follows:
• SAP HANA Troubleshooting and Performance Analysis Guide for your SAP HANA Platform revision at
https://help.sap.com/viewer/p/SAP_HANA_PLATFORM
In particular, search for section Analyzing Generic Symptoms.
• SAP Note 2000000 (FAQ: SAP HANA Performance Optimization)
This is your entry note to detailed performance information for SAP HANA.
Helpful additional references:
• SAP Note 2600030 (Parameter Recommendations in SAP HANA Environments)

SAP Replenishment Planning 5.0 SPS07 Administration Guide

46 PUBLIC Configuration Information
 • SAP Note 2081591 (FAQ: SAP HANA Table Distribution)
• SAP Note 2100040 (FAQ: SAP HANA CPU)
• SAP Note 1999997 (FAQ: SAP HANA Memory)
• SAP Note 2000002 (FAQ: SAP HANA SQL Optimization)
• SAP Note 2222217 (How-To: Troubleshooting SAP HANA Startup Times)
• SAP Note 2222200 (FAQ: SAP HANA Network)
• SAP Note 2380176 (FAQ: SAP HANA Database Trace)
• SAP Note 2220627 (FAQ: SAP HANA LOBs (large objects))

Optimize the Runtime of the Replenishment Calculation

SAP Replenishment Planning contains several configuration parameters that may impact the runtime of an
replenishment calculation run. Therefore, we highly recommend to set these parameters as follows:

• Always define a maximum range of coverage and chose an appropriate value which is as small as possible.
The smaller the value, the lower the calculation effort for your order proposals. For more information
about the use case, see subsection Limit Range of Coverage in the Application Help for SAP Replenishment
Planning at https://help.sap.com/viewer/p/CARAB under Use.
• When scheduling your SAP Replenishment Planning runs, define the planning horizon as short as possible.
The shorter the planning horizon, the less order proposals will be calculated, which in turn reduces the
calculation effort. For more information about the planning horizon see subsection Demand Plan in the
Application Help for SAP Replenishment Planning.
• SAP Replenishment Planning aims to consider different points in time during the calculation. The further in
the future these points in time, the more the calculation time increases. Because of that, try to specify as
less as possible points in time and as near in the future as possible. The following data is used to generate
such points in time:
• Shelf life end
• Open goods movements
• If you want to process only product locations that are calculated using non-cost-based settings, you can
profit from the performance optimization of the replenishment calculation by making sure that all cost
factors in the cost profile are set to 0 and the cost profile parameter Use Basic Cost Components has the
value No.

3.10.2 Performance Monitoring

To ensure an efficient performance by detecting possible performance issues early on in all phases of the
software lifecycle, such as implementation, or production, SAP Replenishment Planning provides a framework
to integrate performance monitoring in the central replenishment processes. Performance monitoring collects
data about the used runtime of a process or process step.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 47
Prerequisites

By default, performance monitoring is disabled. You need to explicitly enable the collection of performance
data for each process or process step whose performance you want to measure in the Performance Monitoring
Configuration.

You can access the configuration either in the system on the SAP Easy Access screen (transaction /DMF/
PERFMON_CONFIG) from the SAP menu under Cross-Application Components Replenishment Planning
or from the SAP Fiori launchpad (Configure Performance Monitoring tile).

Enable Performance Monitoring

In the Performance Monitoring Configuration, you enable the collection of performance data by defining a
logging level for each process whose performance you want to measure.

By default, no logging level is defined for a process and no performance data is collected. You enable the
collection of performance data by setting one of the following logging levels:

• Process: Performance data for a whole process is collected in one measurement.

• Process Step: Performance data for a whole process and all underlying process steps within this process
is collected in seperate measurements. This can include measurements for subprocesses, for example, in
case of parallelization.
• Process Step with Additional Process Detail Measurements: In addition to the performance data collected
on logging level Process Step, process-specific performance data is collected in seperate measurements.
Since the additional measurements have a significant impact on the runtime of a process, this logging level
should only be used in test scenarios or for error handling.

Example

The order plan outbound is a process whose performance can be measured. It consists of different process
steps, such as the selection of order plan items, or the transfer of order plan items.

Measurement Measured Unit Parent Measurement

Process Order Plan Outbound

Process Step Selection of Order Plan Items Order Plan Outbound

Process Step Locking of Order Plan Items Order Plan Outbound

Process Step Transfer of Order Plan Items Order Plan Outbound

Process Step Update of Order Plan Item Status Order Plan Outbound

Process Step Unlocking of Order Plan Items Order Plan Outbound

• If you enable performance monitoring for the order plan outbound on logging level Process, the
performance of the order plan outbound is measured as a whole and stored to the database in one
measurement.
• If you enable performance monitoring for the order plan outbound on logging level Process Step, the
performance of the order plan outbound as a whole, and the performance of each underlying process step
is measured and stored to the database in separate measurements. In this case, six measurements would
be stored to the database.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

48 PUBLIC Configuration Information
Define Retention Period for Performance Data
Besides the logging level, you can define a retention period for each process for which you enabled the
performance monitoring. The retention period defines how long the performance data for a process is to be
retained in the system before it can be deleted:

• Retention period for processes: All process measurements will be deleted completely, including the
measurements of its subprocesses and process steps.
• Retention period for process steps: All subprocess and process step measurements will be deleted. The
measurement of the superordinate process will not be deleted. You can specify a retention period for
process steps if you want to keep the overall runtime measurement longer than the details.

For more information about the deletion of performance data, see the section Purging of Performance Data.

Performance Monitoring Measurements

If performance monitoring has been enabled for a process, the system measures the runtime of the process,
and if configured it measures the process steps to analyze the performance behavior. In addition to the
used runtime, the performance monitoring collects data about a reference key figure, such as the number of
processed product locations to be able to compare the runtimes of multiple performance measurements of
the same process or process step. To gather more information for later analysis, additional characteristics of
a measurement can be collected for an individual performance measurement, such as timestamps, or defined
Customizing settings.

You can display the results of the performance monitoring with the Display Performance Monitoring
Measurements (transaction /DMF/PERFMON_DISP) report. The report displays performance measurements
of selected measured units.

You can extend the results and display all subordinate measurements of the selected measurements by
selecting the Show All Measurements checkbox in the selection criteria of the report. This enables you to see
the interdependencies of the measurements and measured units within a complete process measurement.

In case the Additional Characteristics column is filled on the result screen of the report, you can display
additional information about the measurement by double-clicking the measurement. The table control also
allows different calculations of numeric values.

Performance Monitoring Hierarchy

The following image shows the relation between measured units, reference key figure types, and characteristic
types using the example of the replenishment calculation as process whose performance is measured.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 49
Purging of Performance Data

You can delete performance data which is no longer required by using the Purging of Performance
Measurements report. You can access the report either on the SAP Easy Access screen (transaction /DMF/
PERFMON_PURGE) from the SAP menu under Cross-Application Components Replenishment Planning or
from the SAP Fiori launchpad (Purge Performance Data tile).

You can choose how the measurements that you want to delete are determined by selecting one of the
following options:

• As Defined in Configuration: By selecting this option, you delete performance measurements based on the
retention period you defined in the Performance Monitoring Configuration. The retention period refers to
the start date and time of a process measurement.
• As Defined in Selection: By selecting this option, you delete performance measurements based on the
selection criteria of the report. You can only delete measurements of measured units that are maintained in
the Performance Monitoring Configuration.

In addition, you can delete all process measurements that are not maintained in the configuration any longer by
selecting the option Delete Obsolete Performance Measurements.

The number of the deleted measurements is shown in the Application Log. For more information about the set
up of the Application Log function, see the Detailed Monitoring section under Monitoring [page 55].

SAP Replenishment Planning 5.0 SPS07 Administration Guide

50 PUBLIC Configuration Information
Extensibility

You can enhance performance monitoring based on your business needs in Customizing for Cross-Application
Components under Replenishment Planning Performance Monitoring by using the Business Add-In BAdI:
Addition of Characteristics for Performance Measurements to add characteristics that are relevant for later
analysis of performance measurements.

Further Information

In addition to the processes of the standard implementation, you can use performance monitoring in your own
processes. For more information about how to setup/integrate performance monitoring in your own processes,
see How to Integrate Performance Monitoring in Customer-Specific Processes [page 51].

3.10.3 How to Integrate Performance Monitoring in

Customer-Specific Processes

In addition to the standard implementation of the performance monitoring in the central replenishment
processes, you can integrate performance monitoring in the coding of your own processes.

Setup Performance Monitoring Configuration

To setup the collection of performance data for a process in your application, perform the following tasks
in transaction SM30 or in Customizing for Cross-Application Components under Replenishment Planning
Performance Monitoring :

1. Define measured units (/DMF/VPF_MS_UNIT)

You must define code sections (processes and/or process steps) as measured units for which you want
to collect performance data. Set the Process Indicator for processes that you want to be available in the
Performance Monitoring Configuration for enabling performance monitoring. Each code section whose
performance you want to measure must be defined as separate measured unit.

 Note

Do not reuse measured units that are not completely equivalent. For example, the workload
determination of the replenishment calculation and the workload determination of the order plan
outbound must be defined as separate measured units. This is required because the runtime of
different measurements of the same measured unit shall be comparable.

2. Define reference key figure types (/DMF/VPF_REFKEY)

You must define reference key figure types for your measurement which specify the object that is used to
standardize the runtimes of multiple performance measurements. You can also reuse existing reference
key figure types if they fit to your requirement.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 51
3. Define Characteristic Types (/DMF/VPF_CHARTYP)
You can define characteristic types which defines a type of additional information that can be stored
for a measurement. Optionally, you can define additional characteristics that help to understand a
measurement when closing a measurement via the parameter IV_ADDITIONAL_INFO.
4. Enable the performance monitoring for your process to test the implementation by selecting the process
you want to test and setting the logging level for the performance monitoring in the Performance
Monitoring Configuration.
You can access the configuration either in the system on the SAP Easy Access screen (transaction /DMF/
PERFMON_CONFIG) from the SAP menu under Cross-Application Components Replenishment
Planning or from the SAP Fiori launchpad (Configure Performance Monitoring tile).

Integrate Performance Monitoring

If you want to integrate performance monitoring in the coding of your own application, you must implement the
performance monitoring Application Programming Interface (API) to setup performance measurements.

Depending on the type of your application, you choose one of the provided interfaces.

Application Description Interface

Process The performance of a whole process is /DMF/IF_PERFMON_PROCESS

measured, for example a report. A proc-
ess measurement can have subordinate
performance measurements.

Subprocess The performance of a task that can be /DMF/IF_PERFMON_SUBPROCESS

started as subprocess out of an already
running process is measured in an own
measurement, for example, a Remote
Function Call. A subprocess measure-
ment can have subordinate perform-
ance measurements.

Process Step The performance of a part of a proc- /DMF/IF_PERFMON_PROCESSSTEP

ess or subprocess that is implemented
independent of the process or subpro-
cess is measured in an own measure-
ment, for example, a class with sepa-
rate measurement points inside.

Integrate Process Measurements

1. Create an instance of the performance monitoring API with the method /DMF/CL_PERF_MONITORING
> GET_PROCESS_INSTANCE and hand over the measured unit that you defined as the process whose
performance you want to measure to the instance.
If you want to deactivate performance monitoring for a process although it has been activated in
Customizing, for example, in simulation runs, you can set the import parameter IV_LOGGING_LEVEL_OFF.
2. Store the instance in a global variable of type /DMF/IF_PERFMON_PROCESS.
3. Open the process measurement with the method PROCESS_OPEN.
4. Optional: If you want to measure the performance of process steps that are part of the measured process
in separate measurements, open a process step measurement with the method PROCESS_STEP_OPEN

SAP Replenishment Planning 5.0 SPS07 Administration Guide

52 PUBLIC Configuration Information
 and hand over the measured unit. After the process step measurement has finished processing, close the
measurement with the method PROCESS_STEP_CLOSE.
5. Optional: If you want to measure the performance of parallel tasks that are started as subprocesses
by the actual process, retrieve information about the current process measurement with the method
GET_MEASUREMENT_INFORMATION and hand it over to the subprocess. This is required to properly assign
the measured data.
For more information, see Integrate Subprocess Measurements.
6. Close the process measurement with the method PROCESS_CLOSE. Hand over the reference key figure
type and, if required, additional characteristics.

Integrate Subprocess Measurements

If you want to measure the performance of a parallel task that is started as subprocess out of the actual
process and you want to have an overall overview of the process runtime, you can integrate subprocess
measurements.

A subprocess must import information about the current process measurement. Use an import parameter of
type /DMF/PERFMON_MEASUREMENT_STY and perform the following steps:

1. Create an instance of the performance monitoring API with the method /DMF/CL_PERF_MONITORING >
GET_SUBPROCESS_INSTANCE and hand over the imported process measurement information.
The imported measurement information is evaluated to derive whether performance monitoring is
active or not. If no process measurement information can be imported, no subprocess measurement is
performed.
2. Store the instance in a global variable of type /DMF/IF_PERFMON_SUBPROCESS.
3. Open the subprocess measurement with the method SUBPROCESS_OPEN.
4. Optional: If you want to measure the performance of process steps that are part of the measured
subprocess in separate measurements, open a process step measurement with the method
PROCESS_STEP_OPEN and hand over the measured unit. After the process step measurement has finished
processing, close the measurement with the method PROCESS_STEP_CLOSE.
5. Close the subprocess measurement with the method SUBPROCESS_CLOSE. Hand over the reference key
figure type and, if required, additional characteristics. This is required to enable the comparison of different
measurements of the same measured unit.

The subprocess measurement is persisted to the database with reference to the leading process
measurement.

Integrate Process Step Measurements

You can prepare a code artifact, for example, a class for performance measurements independent of the
leading process.

To perform measurements, you need to import the performance monitoring instance from the leading process.
Process step measurements can only be performed if a leading process or subprocess measurement is
available. The API for process step measurements allows a preparation for measurements in a way that you
don’t need to check whether the calling applications uses performance monitoring or not, if you perform the
following steps:

1. Create an instance of the performance monitoring API for the process step with the method /DMF/
CL_PERF_MONITORING > GET_PROCESSSTEP_INSTANCE. You can use the returned instance to start
and stop your process step measurements. You need to import the performance instance of the calling
application. Independent of the interface used in the calling application, you can import the instance as
type /DMF/IF_PERFMON_PROCESSSTEP, so the instance /DMF/CL_PERF_MONITORING is downcasted to
the needed interface. The instance can be stored as class attribute.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Configuration Information PUBLIC 53
2. Start the process step measurement with the method PROCESS_STEP_OPEN and hand over the measured
unit. After the process step measurement has finished processing, close the measurement with the
method PROCESS_STEP_CLOSE.

3.11 Partition Tables for SAP Replenishment Planning

If your replenishment scenario involves large numbers of products and locations, the relevant SAP
Replenishment Planning, Unified Demand Forecast (UDF), and Demand Data Foundation (DDF) tables can
become very large. To improve standard database operations (such as inserting, updating, deleting, and
reading) and mass operations (such as archiving or index merging), we recommend to partition those tables.
Partitioning help is available for single-host systems only, the use of multi-node systems is currently not
recommended.

Carefully read the information in section Partition Tables for UDF and DDF of the SAP Customer
Activity Repository Administration Guide at https://help.sap.com/viewer/p/CARAB and follow the mentioned
instructions.

In addition, see SAP Note 3051343 (Table Partitioning for SAP Replenishment Planning (for Single-Host
Scenarios) and follow the instructions therein.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

54 PUBLIC Configuration Information
4 Operation Information

Monitoring [page 55]

Monitoring is an essential task in managing SAP Technology. Monitoring allows you to detect any
irregularities or deviations from the ideal business process flow. It also allows you to detect error
situations concerning core business processes at an early stage.

Display of Data with Tools Reports [page 59]

You can use tools reports provided by SAP Replenishment Planning to display data or the result
of processing steps of replenishment planning, for example, the source of supply determination or
determination of scheduling information.

Management [page 65]

SAP provides you with an infrastructure to help your technical support consultants and system
administrators effectively manage all SAP components and complete all tasks related to technical
administration and operation.

High Availability [page 74]

SAP Replenishment Planning is based on SAP HANA and SAP NetWeaver technology. All high
availability considerations that apply to SAP HANA and SAP NetWeaver, such as increasing
system availability, improving performance, and eliminating unplanned downtime, also apply to SAP
Replenishment Planning.

Software Change Management [page 75]

Software Change Management standardizes and automates software distribution, maintenance, and
testing procedures for complex software landscapes and multiple software development platforms.
These functions support your project teams, development teams, and application support teams.

Support Desk Management [page 77]

Support Desk Management enables you to set up an efficient internal support desk for your support
organization that seamlessly integrates your end users, internal support employees, partners, and SAP
Active Global Support specialists with an efficient problem resolution procedure.

4.1 Monitoring

Monitoring is an essential task in managing SAP Technology. Monitoring allows you to detect any irregularities
or deviations from the ideal business process flow. It also allows you to detect error situations concerning core
business processes at an early stage.

SAP Replenishment Planning uses frameworks developed in Demand Data Foundation (DDF) for its monitoring
purposes as most of the master and transaction data comes from DDF.

SAP Replenishment Planning does not have any specific monitoring implemented unless specified in
this guide. Demand Data Foundation internally uses the Foundation on SAP NetWeaver AS for ABAP,
version for SAP HANA (SAP NetWeaver) standard functionality for monitoring. For more information
about this functionality, see SAP NetWeaver Application Server for ABAP 7.52 https://help.sap.com/viewer/

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 55
product/SAP_NETWEAVER_AS_ABAP_752 and search for Search and Operational Analytics. In the Search
and Operational Analytics guide navigate to Managing Search and Operational Analytics Technical
Operations Manual Monitoring . For more information, see also the section Operation Information in
the SAP Customer Activity Repository Administration Guide at http://help.sap.com/viewer/product/CARAB
<Version> Administration .

Alert Monitoring (SAP System Environment)

SAP provides you with the infrastructure and recommendations to set up your alert monitor in such a way that
critical situations are identified as quickly as possible.

Exception Monitoring

You can use the Monitor Exceptions service to review and process exceptions.

To access this service from your SAP Easy Access screen, execute transaction nwbc and choose Services
Monitor Exceptions .

You can do the following:

• Get an overview of the number of exceptions

• Filter the exceptions based on different criteria including business area, context type, or context instance
(value)
• Display the selected exceptions in a table
• Display the detailed information on the exception
• Display all low-level exceptions assigned to a selected high-level exception

If you want to filter the exceptions by business area, you can use the following list of business areas that are
most relevant for the overall SAP Replenishment Planning business process:

• 01 Inbound Processing
• 02 Master Data Management
• 04 Modeling
• 05 Forecasting
• 64 Replenishment Review Order Plan Items Externally
• 63 Replenishment Calculation
• 62 Replenishment Review Order Plan Items
• 61 Replenishment Order Plan Transfer

For more information about this service, see Monitor Exceptions in the application help of SAP Customer
Activity Repository.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

56 PUBLIC Operation Information
Performance Monitoring

To ensure an efficient performance by detecting possible performance issues early onSAP Replenishment
Planning provides a framework to enable performance monitoring for the central replenishment processes
or customer-specific processes. For more information, see Performance Monitoring [page 47] and How to
Integrate Performance Monitoring in Customer-Specific Processes [page 51].

Component-Specific Monitoring

Specific CCMS monitoring for SAP Replenishment Planning is not available.

Detailed Monitoring

Application Log
The Application Log function collects messages, exceptions, and errors and displays them in a log. You can call
up the log using transaction SLG1. The log provides you with the following:

• Basic header information on the events that have occurred

• Event details
• Technical information
• Message short and long texts
• Performance and runtime information on various process steps (for example, reading input data and order
plan determination) through timestamps in the log

The following functionalities in SAP Replenishment Planning use the Application Log function:

Functionality System Log Object Log Sub-Object

Creation of Purchase Orders SAP ERP or SAP S/4HANA MMPUR_RPO

Based on Order Plan Items

Order Plan Item Processing SAP ERP or SAP S/4HANA RFM_XRP_ORDERPLAN

Order Plan Outbound Proc- SAP Customer Activity /XRP/ /XRP/ORDPLN_OUTBOUND

essing Repository

Replenishment Calculation SAP Customer Activity /XRP/ /XRP/REPL_CALC

Repository

Replenishment Calculation SAP Customer Activity /XRP/ /XRP/OP4A_CALC

for Aggregation Repository

Process Workloads in Proc- SAP Customer Activity /DMF/PCP /DMF/PCP_PROCESWRKLD

ess Packaging and Paralleli- Repository
zation

Create Workloads for Proc- SAP Customer Activity /DMF/PCP /DMF/PCP_CREATEWRKLD

ess Packaging and Paralleli- Repository
zation

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 57
Functionality System Log Object Log Sub-Object

Dispatch Workloads for Proc- SAP Customer Activity /DMF/PCP /DMF/PCP_DSPTCHWRKLD

ess Packaging and Paralleli- Repository
zation

Purge Workloads for Process SAP Customer Activity /DMF/PCP /DMF/PCP_PURGEWRKLD

Packaging and Parallelization Repository

Replenishment Simulation SAP Customer Activity /XRP/ /XRP/REPL_SIM

Repository

External Review of Order Plan SAP Customer Activity /XRP/ /XRP/ORDPLN_EXTRVW

Items Repository

Purging of Order Plan Items SAP Customer Activity /DMF/APPL /DMF/ORDPLN_PURGE

Repository

Purging of Order Plan Items SAP Customer Activity /DMF/APPL /DMF/OPI4A_PURGE

for Aggregation Repository

Purging of Traceability Data SAP Customer Activity /DMF/APPL /DMF/ORDPLN_PURGE

Repository

Purging of Procurement SAP Customer Activity /DMF/APPL /DMF/PRCSCHD_PURGE

Schedules Repository

Generation of Alerts SAP Customer Activity /DMF/APPL /DMF/ALERTS_GEN

Repository

Purging of Alerts SAP Customer Activity /DMF/APPL /DMF/ALERTS_PURGE

Repository

Purging of Performance Mon- SAP Customer Activity /DMF/APPL /DMF/PERFMON_PURGE

itoring Data Repository

Replicate Scheduling Groups SAP Customer Activity /DMF/ODS_INT /DMF/ODS_REPL

from SAP Order and Delivery Repository
Scheduling

Replicate Order and Delivery SAP Customer Activity /DMF/ODS_INT /DMF/ODS_REPL

Schedules from SAP ODS Repository

Purge Data Replicated from SAP Customer Activity /DMF/ODS_INT /DMF/ODS_PURGE

SAP Order and Delivery Repository
Scheduling

For more information on the Application Log function, see SAP Help Portal for SAP NetWeaver at http://
help.sap.com/viewer/product/SAP_NETWEAVER. Choose a release. Under Application Help, choose SAP
NetWeaver Library: Function-Oriented View Application Server ABAP Other Services Services for Business
Users Application Log - User Guidelines (BC-SRV-BAL) .

If you use the Process Packaging and Parallelization framework for executing the replenishment calculation,
you do the calculation by using the Replenishment Calculation job template in the Application Job app or in
the system using the Create Workloads report (transaction /DMF/PCP_WRKLD_GEN) or by using the Manage
Workloads app. In either case, in the Application Log app, you use /DMF/PCP as the Category and /DMF/
PCP_PROCESWRKLD as the Subcategory to monitor application log entries. In the Manage Workloads app,
when analyzing workload tasks, you can choose View Log to monitor the corresponding application log entries
in the Application Log app. For more information, see the sections Process Packaging and Parallelization

SAP Replenishment Planning 5.0 SPS07 Administration Guide

58 PUBLIC Operation Information
and Manage Workloads in the application help for SAP Customer Activity Repository at https://help.sap.com/
viewer/product/CARAB/latest/en-US?task=use_task.

SAP HANA Monitoring

SAP Replenishment Planning uses standard SAP HANA Monitoring tools for monitoring SAP HANA. For more
information, see the SAP HANA Administration Guide for SAP HANA Platform at http://help.sap.com/viewer/
product/SAP_HANA_PLATFORM and choose a version. Choose Administration SAP HANA Administration
Guide for SAP HANA Platform .

SAP Fiori and SAP Gateway Monitoring

SAP Replenishment Planning uses standard SAP Gateway Monitoring tools for monitoring the SAP Fiori
applications and OData services.

For more information about monitoring SAP Fiori apps, see SAP Library on SAP Help Portal at http://
help.sap.com/viewer/p/FIORI_IMPLEMENTATION. Choose Operations SAP Fiori: Operations Monitoring
SAP Fiori Apps .

For more information about SAP Gateway Monitoring, see the SAP Gateway Technical Operations Guide
on SAP Help Portal at http://help.sap.com/viewer/p/SAP_GATEWAY. Choose Operations Technical
Operations Guide .

4.2 Display of Data with Tools Reports

You can use tools reports provided by SAP Replenishment Planning to display data or the result of processing
steps of replenishment planning, for example, the source of supply determination or determination of
scheduling information.

Tools reports typically show information on a more technical level, such as internal IDs (UUIDs) of objects. They
are meant to be used for analytical tasks, for example, in support cases or for a technical analysis of data.
Some of the tools reports offer different display options.

You can access the tools reports in the system by using the corresponding transactions. To use the reports,
you must have an authorized user on the ABAP back-end server. Therefore, create roles with the suitable
authorization objects.

SAP Replenishment Planning provides the following tools reports:

Tools Report Transaction Description Authorization Object

Display Procurement Sched- /DMF/PROCSCHED_DISP This tools report displays /DMF/PSGET

procurement schedule items
ule Information
for a combination of selected
(/DMF/ procurement schedules and
TOOLS_PROC_SCHEDULE) a specified order date and
time range.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 59
Tools Report Transaction Description Authorization Object

Display of Replenishment /XRP/RPLSCHED_DET This tools report displays re- /XRP/SHGET

Schedules for Product Loca- plenishment schedule items

tions as a result of the schedul-
ing service for a combination
(/XRP/
of selected product locations
TOOLS_GET_SCHEDULING)
and a specified order date
and time range.

The report also displays ex-

ceptions that occurred dur-
ing the determination of
scheduling information.

It provides the option to over-

ride assigned procurement
schedules.

Display of SoS Determination /DMF/SOS_DET This tools reports displays /DMF/SOSGT

Results for Product Locations the preferred source of sup-

ply as result of the source
(/DMF/
of supply determination for
TOOLS_SOS_PROD_TARGETL
a combination of selected
OC)
product locations and a
specified delivery date and
time range.

The report provides the op-

tion to display all valid sour-
ces of supply instead of the
preferred one.

It also displays the excep-

tions that occurred during
the source of supply determi-
nation.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

60 PUBLIC Operation Information
 Tools Report Transaction Description Authorization Object

Display of Stock Levels for /XRP/STOCK_DET This tools report displays the /DMF/STGET

Product Locations current stock for selected

product locations.
(/XRP/TOOLS_READ_STOCK)
By default, the reports dis-
plays stock data for the stock
source, which has been as-
signed to the selected prod-
uct location in the configu-
ration assignments. It pro-
vides the option to select the
source for which the stock in-
formation is to be displayed.
You can display real-time in-
ventory information, or the
DDF stock information.

In case only DDF stock in-

formation is displayed, disag-
gregated DDF stock informa-
tion is also displayed.

The report also displays ex-

ceptions that occurred dur-
ing the stock determination.

Display Order Units and /XRP/UOM_DET This tools report displays al- /XRP/UMGET
lowed order units and po-
Rounding Rules
tential rounding rules for se-
/XRP/ lected product locations and
TOOLS_GET_ORD_RNDNG_UN a specific time range.

IT The report provides the op-

tion to select a Unit of
Measure for Simulation. The
report then displays the con-
version factors for the se-
lected unit without checking
if it is an allowed unit.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 61
Tools Report Transaction Description Authorization Object

Display Parameter Values for /XRP/CONFIG_DET This tools reports displays /XRP/PVGET
effective parameter assign-
Product Locations
ments for the selected prod-
(/XRP/ uct locations and parame-
TOOLS_DISPLAY_PARAM_VA ter scope. You can restrict
the result by specifying fur-
LUE)
ther selection criteria, such
as the validation date and
time, either as individual date
and time or date and time
range. In case of a date and
time range, you can specify
whether to display existing
parameter assignments or
time periods with missing as-
signments.

Display of Open Goods Move- /XRP/OGM_DET This tools report displays /XRP/OGGET

ments for Product Locations open goods movements for

the selected product loca-
(/XRP/
tions starting at a specified
TOOLS_GET_OPENGOODSMOV
date and time.
MNT)
Besides the display of open
goods movements from
both, purchase orders and
order plan items, the report
provides the option to either
display open goods move-
ments from order plan items
or from purchase orders only.

It also shows exceptions that

occurred during the determi-
nation of open goods move-
ments.

Display Order Plan Items /DMF/OPI_DISP This tools report displays or- /DMF/OPGET
der plan items and change
(/DMF/ history data for different se-
TOOLS_GET_ORDERPLAN_IT lection criteria. It provides
EMS) different selection criteria re-
ferring to order plan items
and the option to select a
time zone into which the date
and time information of the
order plan items is converted
to for display.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

62 PUBLIC Operation Information
 Tools Report Transaction Description Authorization Object

Display Order Plan Items for /DMF/OPI4A_DISP This tools reports displays /DMF/OP4AG

Aggregation order plan items for aggre-

gation and corresponding
(/DMF/
traceability data for different
TOOLS_GET_OP4A_ITEMS)
selection criteria.

It provides different selection

criteria referring to order
plan items for aggregation
and the option to select a
time zone into which the date
and time information of the
order plan items is converted
to for display.

The report displays excep-

tions that occurred during
the calculation of order plan
items for aggregation.

Instead of order plan items

for aggregation, the end of
horizon information stored
for the selected product loca-
tions can be displayed.

Display Performance Moni- /DMF/PERFMON_DISP This tools report displays /DMF/PERFM

toring Measurements performance monitoring

measurements for selected
(/DMF/
measured units.
TOOLS_GET_PERFMON)
You can restrict the result by
specifying further selection
criteria, such as the user who
started a performance meas-
urement, a date and time
range or a particular meas-
urement UUID.

The report provides the op-

tion to display all subordinate
measurements related to the
selected measurements.

It indicates the hierarchical

relations of single measure-
ments and shows additional
characteristics of each meas-
urement.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 63
Tools Report Transaction Description Authorization Object

Display of Results for Aggre- /DMF/AOP_DET This tools report displays ag- /DMF/AOP_T
gated Order Plan Functional- gregated order plans as the
ity result for the provided test  Note
input data. Furthermore, it Additional authorization
(/DMF/TOOLS_AOP_TEST)
can display information on object required only
the process’s performance for the external
as well as messages created call: /DMF/AOP
during the run.

You can restrict the results by

specifying the call variant of
the order plan aggregation.

The report provides the op-

tion to display either the ag-
gregation results, the warn-
ings and errors created dur-
ing the run, the application
log messages, or the per-
formance of the report ex-
ecution. Note that this re-
port only shows the applica-
tion log for the internal call
variant. To display the appli-
cation log for the external
call variant, use transaction
SLG1.

For further information on the individual tools reports, see the system documentation of the reports in the
back-end system.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

64 PUBLIC Operation Information
4.3 Management

SAP provides you with an infrastructure to help your technical support consultants and system administrators
effectively manage all SAP components and complete all tasks related to technical administration and
operation.

Starting and Stopping

Start and Stop Sequences and Tools

Action and Component Sequence Tool Detailed Description

Start SAP HANA database 1 sapstartsrv See the information about

starting and stopping SAP
HANA systems in the uses
the standard SAP NetWea-
ver administration tools. For
more information, see SAP
Help Portal for SAP NetWea-
ver atSAP HANA Administra-
tion Guide.

Start SAP Systems and In- 2 STARTSAP (for UNIX) uses the standard SAP
stances NetWeaverSee the informa-
tion about starting and
stopping SAP systems
based on SAP NetWea-
ver at http://help.sap.com/
viewer/p/SAP_NETWEA-
VER_AS_ABAP_752
Application Help SAP
NetWeaver Library: Function-
Oriented View Solution
Lifecycle Management
Starting and Stopping SAP
Systems Based on SAP
NetWeaver .

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 65
Action and Component Sequence Tool Detailed Description

Stop SAP Systems and In- 3 STOPSAP (for UNIX) See the information
stances about starting and
stopping SAP systems
based on SAP NetWea-
ver at http://help.sap.com/
viewer/p/SAP_NETWEA-
VER_AS_ABAP_752
Application Help SAP
NetWeaver Library: Function-
Oriented View Solution
Lifecycle Management
Starting and Stopping SAP
Systems Based on SAP
NetWeaver .

Stop SAP HANA database 4 sapstartsrv See the information about

starting and stopping SAP
HANA systems in the SAP
HANA Administration Guide.

Administration Tools

There is no specific administration tool for SAP Replenishment Planning.

SAP Replenishment Planning http://help.sap.com/viewer/product/SAP_NETWEAVER. Choose SAP

NetWeaver Platform <Your Platform> Operations Technical Operations for SAP NetWeaver
Administration of SAP NetWeaver systems and components .

SAP Replenishment Planning also uses the administration tools available with SAP HANA. For more
information, see SAP Help Portal for SAP HANA platform at http://help.sap.com/viewer/product/
SAP_HANA_PLATFORM. Choose an SAP HANA platform version. Choose Administration SAP HANA
Administration Guide for SAP HANA Platform .

Backup and Restore

You must back up your system landscape regularly to ensure that you can restore and recover it in case of
failure. The backup and restore strategy for your system landscape must not only include your strategy for your
SAP system, but it must also be included in your company's overall business requirements and incorporated
into your entire process flow.

In addition, the backup and restore strategy must cover disaster recovery processes, such as how to recover
from the loss of data center due to a fire. It is important that your strategy specifies that normal data and
backup data are stored in separate physical locations, so that both types of data are not lost in case of a
disaster. SAP Replenishment Planning is based on SAP NetWeaver technology; therefore, the SAP NetWeaver
backup procedures can also be used for SAP Replenishment Planning.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

66 PUBLIC Operation Information
 Subject Path

Backup and recovery processes for ABAP or Process Integra- See the Technical Operations documentation for SAP Net-
tion Weaver at http://help.sap.com/viewer/product/SAP_NET-
WEAVER. Choose SAP NetWeaver Platform <Your
Platform> Operations Technical Operations for SAP
NetWeaver .

Backup and recover the SAP HANA database See SAP Help Portal for SAP HANA platform
at http://help.sap.com/viewer/product/SAP_HANA_PLAT-
FORM. Choose Administration SAP HANA
Administration Guide for SAP HANA Platform .

Backup and restore for Demand Data Foundation See the SAP Customer Activity Repository Administration
Guide at https://help.sap.com/viewer/product/CARAB and
search for Backup and Restore.

Periodic Tasks

This section describes the tasks required to run to keep the application running smoothly over time. It is
important that you monitor the successful execution of these tasks on a regular basis.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 67
Periodic Tasks
Recommended Frequency and
Program Name/Task Method Detailed Description

DRFOUT (for master data replication) Frequency: Perform this task in SAP ERP or
SAP S/4HANA to replicate the needed
• Initial setup of the system
master data to the system for
• Whenever master data changes SAP Replenishment Planning. SAP
Replenishment Planning needs the fol-
Method: Manual task
lowing outbound implementations:

• PPLT (Plant/Location)
• PMAT (Material/Product)
• PMPL (Material an Plant/Product
Location)
• PINV (Inventory/Stock)
• PSOS (Source of Supply)
• PVEN (Vendor/Supplier)

For more information about the relevant

DRF outbound implementations, see
SAP Note 2774819 .

For more information, see the section

Configure Demand Data Foundation in
the Common Installation Guide and sec-
tion Configure Data Replication from
SAP ERP and SAP S/4HANA to DDF in
the SAP Customer Activity Repository
Administration Guide.

DRFOUT (for transaction data replica- Frequency: On a regular basis Perform this task in SAP ERP or
tion) SAP S/4HANA to replicate the needed
transaction data to the system for
SAP Replenishment Planning. SAP
Replenishment Planning needs the fol-
lowing outbound implementation:

• PURCH_ORDR (Purchase Order)

 Note
If you enabled the use of real-time
inventory for the stock determina-
tion, make sure that the purchase
order information replicated via
DRF outbound is up to date. Only
if the information is up to date, the
current state of purchase orders is
in sync with the stock information.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

68 PUBLIC Operation Information
 Recommended Frequency and
Program Name/Task Method Detailed Description

Purging of Master Data Frequency: On a regular basis Perform this task in the SAP Customer
Activity Repository to delete obsolete
master data by using the Where
Used Framework for Purging (/DMF/
PURGE_AGENT) report.

Unified Demand Forecast (UDF) Model- Frequency: Perform this task in SAP Customer
ing and Forecasting Activity Repository to create demand
• On a regular basis forecasts based on up-to-date sales in-
• Daily to weekly formation and demand influencing fac-
tors.

For more information on scheduling

UDF, see the application help for
SAP Customer Activity Repository
and search for Schedule Model and
Forecast.

For more information on configur-

ing UDF, see the SAP Customer
Activity Repository Administration

Guide and navigate to Configuration

Configure Unified Demand Forecast

(UDF) .

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 69
 Recommended Frequency and
Program Name/Task Method Detailed Description

Replenishment Calculation Frequency: Depending on your business Perform this task in SAP Customer
needs, for example, the procurement Activity Repository to calculate order
rhythm of a product location. plan items based on up-to-date stock,
goods movements, and demand infor-
• Whenever new order plan items mation.
are required
Group the product locations concerned
• Subdaily to weekly
based on similar procurement sched-
ules and configure the planning horizon.

For more information, see

the documentation of the
Replenishment Calculation report
(/XRP/REPLENISHMENT_CALC).

 Tip
The replenishment calculation can
also be executed in parallel using
the Process Packaging and Paral-
lelization framework. You can ac-
tivate parallel processing by us-
ing the Generate Workload for
Replenishment Calculation job tem-
plate in the Application Job app.
Alternatively, you can use the
Replenishment Calculation report
(transaction /XRP/RPL_CALC) or
the Manage Workloads app. The
same recommended frequency and
method apply. For more informa-
tion, see the sections Process Pack-
aging and Parallelization and Man-
age Workloads in the application
help for SAP Customer Activity Re-
pository at https://help.sap.com/
viewer/product/CARAB/latest/en-
US?task=use_task.

Make sure that the enqueue server

is configured in a suitable manner
regarding the maximum number of
locks to ensure the smooth oper-
ation of the replenishment calcula-
tion. For more information, see En-
sure a Suitable Configuration of the
Enqueue Server [page 25].

SAP Replenishment Planning 5.0 SPS07 Administration Guide

70 PUBLIC Operation Information
 Recommended Frequency and
Program Name/Task Method Detailed Description

Replenishment Calculation for Aggrega- Frequency: Depending on your business Perform this task in SAP Customer
tion needs, for example, the procurement Activity Repository to calculate order
rhythm of a product in your distribution plan items for aggregation based on up-
center. to-date stock, goods movements, and
demand information.
• Whenever new order plan items
are required for your distribution Group the product locations concerned
center. based on similar procurement sched-
• Weekly to monthly ules and configure the planning horizon.

To calculate order plan items for

 Note aggregation, run the Replenishment
Calculation report in Order Plan for
The replenishment calculation for
Aggregation mode. For more infor-
aggregation should be processed mation, see the documentation of
after the regular replenishment cal- the Replenishment Calculation report
culation. (/XRP/REPLENISHMENT_CALC).

 Tip
The replenishment calculation can
also be executed in parallel using
the Process Packaging and Paral-
lelization framework. You can ac-
tivate parallel processing by us-
ing the Generate Workload for
Replenishment Calculation job tem-
plate in the Application Job app.
Alternatively, you can use the
Replenishment Calculation report
(transaction /XRP/RPL_CALC) or
the Manage Workloads app. The
same recommended frequency and
method apply. For more informa-
tion, see the sections Process Pack-
aging and Parallelization and Man-
age Workloads in the application
help for SAP Customer Activity Re-
pository at https://help.sap.com/
viewer/product/CARAB/latest/en-
US?task=use_task.

Make sure that the enqueue server

is configured in a suitable manner
regarding the maximum number of
locks to ensure the smooth oper-
ation of the replenishment calcula-
tion. For more information, see En-

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 71
 Recommended Frequency and
Program Name/Task Method Detailed Description

sure a Suitable Configuration of the

Enqueue Server [page 25].

Order Plan Transfer Frequency: Depending on your business Perform this task in SAP Customer
needs, for example, the procurement Activity Repository to transfer order
rhythm of a product location. plan data to SAP ERP or SAP S/
4HANA.
• On a regular basis
• Subdaily to weekly For more information, see the
documentation of the Order Plan
Outbound Processing report (/XRP/
ORDERPLAN_OUTBOUND).

 Tip
Order plan outbound processing
can also be executed in parallel
using the Process Packaging and
Parallelization framework. You can
activate parallel processing by us-
ing the OP Outbound Processing
job template in the Application
Job app. Alternatively, you can
use the Order Plan Outbound
Processing report (transac-
tion /XRP/ORDERPLAN_OUTBOUND)
or the Manage Workloads app. The
same recommended frequency and
method apply. For more informa-
tion, see the sections Process Pack-
aging and Parallelization and Man-
age Workloads in the application
help for SAP Customer Activity Re-
pository at https://help.sap.com/
viewer/product/CARAB/latest/en-
US?task=use_task.

Make sure that the enqueue server

is configured in a suitable manner
regarding the maximum number of
locks to ensure the smooth oper-
ation of the order plan transfer.
For more information, see Ensure
a Suitable Configuration of the En-
queue Server [page 25].

SAP Replenishment Planning 5.0 SPS07 Administration Guide

72 PUBLIC Operation Information
 Recommended Frequency and
Program Name/Task Method Detailed Description

Create Purchase Orders Based on Or- Frequency: Depending on your business Perform this taks in SAP ERP or
der Plan Items needs, but at least after each transfer SAP S/4HANA to create purchase
of order plan items from SAP Customer orders based on order plan items
Activity Repository to the ERP system. by using the Grouping of Order
List Items into Purchase Orders
(R_MMPUR_RPO_START_PROCESSING)
function. For more information, see
Configure Purchase Order Creation
Based on Order Plan Items [page 36].

Purging of Order Plan Items Frequency: On a regular basis Perform this task in the SAP Customer
Activity Repository to delete obsolete
order plan items.

For more information, see the

documentation of the Purging of
Order Plan Items report (/DMF/
ORDERPLAN_PURGE).

Purging of Order Plan Items for Aggre- Frequency: On a regular basis Perform this task in the SAP Customer
gation Activity Repository to delete obsolete
order plan items for aggregation.

For more information, see the docu-

mentation of the Purging of Order Plan
Items for Aggregation report (/DMF/
OPI4A_PURGE).

Purging of Traceability Data Frequency: On a regular basis Perform this task in the SAP Customer
Activity Repository to delete obsolete
traceability data. For more information,
see the Purging section in the Lifecy-
cle of Order Plan Items topic in the
SAP Replenishment Planning applica-
tion help.

Purging of Performance Monitoring Frequency: On a regular basis Perform this task in the SAP Customer
Data Activity Repository to delete obsolete
performance monitoring data. You can
access the Purging of Performance
Measurements report either in the sys-
tem on the SAP Easy Access screen
(transaction /DMF/PERFMON_PURGE)
or from the SAP Fiori Launchpad (Purge
Performance Data tile).

Creation of Alerts Frequency: Ideally immediately after Perform this task in SAP Customer
having performed the UDF Modeling Activity Repository to generate alerts
and Forecasting tasks and / or the re- based on the underlying exceptions.
plenishment calculation as they are the You can access the Generate Alerts re-
base for the alerts. port either in the system on the SAP
Easy Access screen (transaction /DMF/
ALERTS_GEN) or from the SAP Fiori
Launchpad (Generate Alerts tile).

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 73
 Recommended Frequency and
Program Name/Task Method Detailed Description

Purging of Alerts Frequency: On a regular basis Perform this task in SAP Customer
Activity Repository to delete obsolete
alerts. You can access the Purging of
Alerts report either in the system on
the SAP Easy Access screen (transac-
tion /DMF/ALERTS_PURGE) or from the
SAP Fiori Launchpad (Purge Alerts tile).

Purging of Exceptions Frequency: On a regular basis Perform this task in SAP Customer
Activity Repository to delete obso-
lete exception message data with the
Purging Exceptions From the Database
(/DMF/PURGE_EWB_MESSAGES) report.

You do not need to specify parameters

for this report. You can either execute it
directly or schedule it for execution.

Purging of scheduling data replicated Frequency: Depending on your business Perform this task in SAP Customer
from SAP Order and Delivery Schedul- needs. Activity Repository to delete obsolete
ing. scheduling data replicated from SAP
Order and Delivery Scheduling with
the Purge Data Replicated from SAP
Order and Delivery Scheduling (/DMF/
ODS_PURGE_HDR_ITEMS) report.

For more information about scheduled periodic tasks for SAP NetWeaver Application Server for ABAP 7.52,
see https://help.sap.com/viewer/p/SAP_NETWEAVER_AS_ABAP_752 Application Help SAP NetWeaver
Library: Function-Oriented View Search and Operational Analytics Managing Search and Operational
Analytics Technical Operations Manual Administration Periodic Tasks Scheduled Periodic Tasks .

4.4 High Availability

SAP Replenishment Planning is based on SAP HANA and SAP NetWeaver technology. All high availability
considerations that apply to SAP HANA and SAP NetWeaver, such as increasing system availability, improving
performance, and eliminating unplanned downtime, also apply to SAP Replenishment Planning.

Additional Information on High Availability

Topic Path

General information on high availability strategies for SAP See SAP Help Portal for SAP NetWeaver at http://
NetWeaver-based systems help.sap.com/viewer/product/SAP_NETWEAVER. Choose
SAP NetWeaver Platform <Your Platform> . Under
Application Help, choose SAP NetWeaver Library:
Function-Oriented View Solution Lifecycle Management
SAP Business Continuity .

SAP Replenishment Planning 5.0 SPS07 Administration Guide

74 PUBLIC Operation Information
 Topic Path

General information in high availability strategies for SAP See SAP Help Portal for SAP HANA Platform
HANA-based systems at http://help.sap.com/viewer/product/SAP_HANA__PLAT-
FORM. Choose a SAP HANA platform version. Choose
Administration SAP HANA Administration Guide for
SAP HANA Platform .

4.5 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and testing
procedures for complex software landscapes and multiple software development platforms. These functions
support your project teams, development teams, and application support teams.

The goal of Software Change Management is to establish consistent, solution-wide change management that
allows for specific maintenance procedures, global rollouts (including localizations), and open integration with
third-party products.

Transport and Change Management

SAP Replenishment Planning uses the infrastructure of SAP NetWeaver Application Server for ABAP.

For more information about how to download and install the application function library SAP XRP AFL, see
the SAP Replenishment Planning Setup Guide and choose Set Up SAP SAP Replenishment Planning
Download and Install the Application Function Library SAP XRP AFL .

For information about change management for SAP NetWeaver Application Server for ABAP 7.52,
see https://help.sap.com/viewer/p/SAP_NETWEAVER_AS_ABAP_752 Application Help SAP NetWeaver
Library: Function-Oriented View Search and Operational Analytics Managing Search and Operational
Analytics Technical Operations Manual Change Management .

Development Requests and Development Release Management

You use the standard tools and procedures of SAP NetWeaver to transport SAP Replenishment Planning
code extensions or customizing changes. All such changes are captured by the transport system and are
transportable.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 75
Additional Information on Development Requests and Development Release Management
Topic Path

Change and Transport System See SAP Help Portal for SAP NetWea-
ver at http://help.sap.com/viewer/product/SAP_NETWEA-
VER/ALL. Choose a SAP NetWeaver Platform (release).
Under Operations, choose Technical Operations for SAP
NetWeaver Administration of Application Server ABAP .

Change Management for SAP HANA-based systems See SAP Help Portal for SAP HANA plat-
form at https://help.sap.com/viewer/product/DRAFT/
SAP_HANA_PLATFORM/2.0.05. Under Administration,
choose SAP HANA Administration Guide for SAP HANA
Platform.

Support Packages and Patch Implementation

We recommend that you implement SAP NetWeaver, SAP HANA, and SAP Replenishment Planning support
package stacks. These support package stacks are sets of support packages and patches for the respective
product version that must be used in the given combination. The technology for applying support packages
and patches will not change.

Before you apply any support packages or patches of the selected support package stack, see the
corresponding release information notes (RINs) for up-to-date information on the current release:

1. Navigate to SAP Help Portal for SAP Customer Activity Repository applications bundle at https://
help.sap.com/viewer/p/CARAB and select your version at the top right.
2. Under Installation and Upgrade, see the release information notes (one for the back-end and one for the
front end).

More Information
For more information about software change management, see the following:

Topic Path

Maintenance Planner https://support.sap.com/en/alm/solution-manager/proc-

esses-72/maintenance-planner.html

Support Package Stacks https://support.sap.com My Support Software

Downloads Support Package Stacks

SAP Replenishment Planning 5.0 SPS07 Administration Guide

76 PUBLIC Operation Information
4.6 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support
organization that seamlessly integrates your end users, internal support employees, partners, and SAP Active
Global Support specialists with an efficient problem resolution procedure.

For support desk management, you need the methodology, management procedures, and tools infrastructure
to run your internal support organization efficiently.

Remote Support Setup

If you want to use SAP remote services (for example, SAP EarlyWatch for Remote Consulting), or if you would
like to permit an SAP support consultant to work directly in your system to make a more precise problem
diagnosis, set up a remote service connection.

Additionally, there exists an ABAP role for read-only access for remote support that is also relevant. This role
(SAP_RCA_SAT_DISP for ABAP) is available in the STOP plug-in and is generated when a managed system is
connected to SAP Solution Manager.

Should any additional application-specific functionality be necessary for use by an SAP support consultant,
then an applicable role should be defined providing the appropriate authorizations and assigned to the SAP
support consultant's user logon.

Problem Message Handover

If you need to report an incident (that is, create an SAP support message) for your installation, you must
specify an application component. The most relevant components for SAP Replenishment Planning are as
follows:

• CA-RT-XRP: for general issues with SAP Replenishment Planning

• CA-RT-XRP-CLC: for the replenishment calculation process
• CA-RT-XRP-SIM: for the Simulate Replenishment app and the Purge Simulation Data report
• CA-RT-XRP-OPO: for the order plan outbound process
• CA-RT-XRP-ROP: for the Review Order Plan Items app
• CA-DDF-RT: for general issues with the components in the Demand Data Foundation (DDF) layer used by
SAP Replenishment Planning
• CA-DDF-RT-MD: for the master data component
• CA-DDF-RT-IF: for the inbound process
• CA-DDF-RT-DRF: for the data replication
• CA-DDF-RT-UDF: for modeling and forecasting with the Unified Demand Forecast (UDF) module and
the apps for demand forecasting (Analyze Forecast, Adjust Forecast, and Manage Demand Influencing
Factors)
• CA-DDF-RT-WUF: for issues with the Purge Business Objects functionality (Where Used Framework for
Purging)

SAP Replenishment Planning 5.0 SPS07 Administration Guide

Operation Information PUBLIC 77
 • CA-DDF-RT-EWB: for issues with the Monitor Exceptions service and the exception management
framework
• CA-DDF-RT-PCP: for process packaging and parallelization
• CA-DDF-RT-ANA: for the retail analytical views
• CA-DDF-RT-ALR: for alert management (including the apps Manage Alerts and Manage Alert Profiles
as well as the reports Generate Alerts and Purging of Alerts)
• CA-DDF-RT-CFG: for the apps for configuration management (Manage Procurement Schedules,
Manage Cost Profiles, Manage Shelf Cost Profiles, Manage Constraint Profiles, Manage Configuration
Assignments, and Manage Exception Profiles)
• CA-DDF-RT-OPM: for general order plan management issues including status handling, change history,
external review, and purging
• CA-DDF-RT-PFM: for performance monitoring
• CA-DDF-RT-PSC: for procurement scheduling

For more information about reporting incidents for SAP Customer Activity Repository, see the Support Desk
Management section of the SAP Customer Activity Repository Administration Guide at https://help.sap.com/
viewer/product/CARAB.

SAP Replenishment Planning 5.0 SPS07 Administration Guide

78 PUBLIC Operation Information
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 Replenishment Planning 5.0 SPS07 Administration Guide

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

© 2024 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