PRD Instructions

SAP Variant Configuration
PDR User Instruction
PRODUCT DATA REPLICATION TOOL PDR INSTRUCTIONS
INTRODUCTION...........................................................................................................................................................2
CONCEPTS AND NAMING CONVENTIONS..........................................................................................................2
TRANSACTIONS AND SETTINGS............................................................................................................................4

3.1
3.2
3.3
PRE-SETTINGS IN SAP...............................................................................................................................................4
TRANSACTIONS IN THE SENDING SYSTEM.................................................................................................................5
TRANSACTIONS IN THE TARGET SYSTEM...................................................................................................................6
USING PDR.....................................................................................................................................................................7
4.1
OPTION 1: PHASE BY PHASE......................................................................................................................................7
4.1.1
Configuration folder settings............................................................................................................................7
4.1.2
Creation of a baseline.....................................................................................................................................10
4.1.3
Baseline explosion..........................................................................................................................................12
4.1.4
Creation of a distribution order......................................................................................................................16
4.1.5
Starting the distribution..................................................................................................................................17
4.1.6
Sending the ALE distribution package...........................................................................................................18
4.1.7
Sending the IDocs to the target system...........................................................................................................21
4.1.8
Posting the UPS package in the target system...............................................................................................24
4.2
OPTION 2: ADVANCED (RECOMMENDED).................................................................................................................28
4.3
GOOD HOUSEKEEPING OF PRODUCT CHANGES........................................................................................................31
PROBLEMATIC SITUATIONS.................................................................................................................................32
5.1
5.2
IDOCS IN ERROR STATUS..........................................................................................................................................32

CREATION OF A CORRECTION PACKAGE...................................................................................................................35
APPROVALS AND VERSION HISTORY.................................................................................................................38
TA-xx.xx.xxx
2011 KONE Corporation

All rights reserved.
1 ( 38 )
(-) 2011-10-11

INTRODUCTION
Product Data Replication tool (later PDR) is SAP standard way to transport Product data (including
materials, bills of material, documents, classes, characteristics, classifications, and the configuration
model) between different systems. It is relatively easy to use and does lots of phases automatically
compared to previous customized transactions used in KONE (ZAL1). We will still have the individual
object ALE transactions (for example CLD2 to transport Object dependencies) and those transactions
can be used for minor changes as we are doing today.
CONCEPTS AND NAMING CONVENTIONS

Icon
Description
Explanation
Configuration Definition
Frame in which all configurations of

a product or project throughout all
the phases of a life cycle are
cumulated. You can group together
several related configuration
folders in a Configuration
Definition.
Configuration folder
In a configuration folder, you define

the product to be distributed and
recipient systems.
Baseline
In a baseline, you group together

the objects that are to be
distributed. A function for explosion
of the product structure supports
you here.
Distribution order
You use a distribution order to

control the distribution of product
data to one or more recipients. A
distribution order can contain
several distribution packages.
Distribution package
A distribution package controls the

distribution of baselines to a
specific logical system or the
distribution of documents to a
specific recipient. By doubleclicking on a distribution packet for
a logical system, you display the
ALE distribution unit.
Configuration definition is always CD_PDR.
TA-xx.xx.xxx

2 ( 38 )
(-) 2011-10-11

Configuration folders are created for each material and for each transferring scenario, naming
convention is CF_MATERIAL CODE_TARGET SYSTEM(_2nd TARGET SYSTEM), for example
CF_KM806402_S03C007. When you are transferring material KM806402 to system S03/007, you will
use this same folder each time.
You will create a baseline for each job. Naming convention is BL_MATERIAL CODE_YYYYMMDD, for
example BL_KM806402_20120930. This is a baseline for material KM806402 created 30.9.2012.
Distribution order and Distribution package are created automatically by the system.
Here is the overview of the PDR structure:
We have only one:
CD_PRD
Configuration
Definition
Configuration
Folder
Baseline
Are predefined for each material

and each transportation path.
Create for each transport
Distribution Order
Created automatically during

the transportation process for
each transport
Distribution Package
TA-xx.xx.xxx

Created automatically during

the transportation process
for each transport
3 ( 38 )
(-) 2011-10-11

TRANSACTIONS AND SETTINGS
3.1
Pre-settings in SAP
It is strongly recommended to change SAP GUI SETTINGS as described here below:
Press 'Customize Local Button'-button
and choose Options:
Go to Expert-sheet and choose 'Show keys in All Dropdown lists' and 'Sort by Key':
TA-xx.xx.xxx

4 ( 38 )
(-) 2011-10-11

Press OK.
The reason to use this setting is that it is much easier to use sorting in PDR.
NOTE! This will change also settings also in other transactions and you will see technical keys in front
of some items. You can choose yourself whether you want to use it or not.
3.2
Transactions in the sending system

You can find Product Data Replication Workbench (CRWBD) in SAP menu:
This transaction is used to create data package which contains all needed VC data for releasing VC
objects in the target system.
You may need to check job overviews with SM37.
IDocs will be sent with BD87 as usual at this point (later they will be sent automatically, see chapter
4.1.7)
TA-xx.xx.xxx

5 ( 38 )
(-) 2011-10-11

3.3
Transactions in the target system

In the target system you will receive IDocs with BD87 (later they will be processed automatically, see
chapter 4.1.7)
In the target system all you need is transaction UPS to updload IDOCs.
TA-xx.xx.xxx

6 ( 38 )
(-) 2011-10-11

USING PDR
4.1
Option 1: Phase by phase
4.1.1
Configuration folder settings

Open transaction CRWBD
Select CD_PDR as a configuration definition:
Press ENTER. The Replication Workbench and the product structure overview tree will open:
TA-xx.xx.xxx

7 ( 38 )
(-) 2011-10-11

From the dropdown arrow in branch Replication you can open the selection of configuration folders.
Configuration folders are predefined in each system for each material and each ALE path. If you cant
find a proper folder, please contact your key user.
You can use the same folder each time you need to transfer data. For example if you need to transfer
material KM806402 from S01/145 to S03/007, in client S01/145 you use always folder
CF_KM806402_S03C007.
When you double click the folder icon
, you can specify needed BOM level explosion:
TA-xx.xx.xxx

8 ( 38 )
(-) 2011-10-11

Possible BOM explosion levels are:

1. Only one BOM level
2. Full BOM explosion (all BOM levels)
3. No BOM
After you have defined BOM explosion level and checked that Material ID is correct, press
NOTE! You can always see the information from previous transfer in the beginning and you must
remember to change BOM level and material ID according to your needs!
You can also include several materials to one transfer, but this is not recommended, because we
should have a folder per each material. If you want to use it for some reason, select sheet Structure
in the configuration folder and specify materials in the Material column:
NOTE! If you select full BOM explosion, the whole structure will be included to the transport and you
dont need to specify all materials here.
TA-xx.xx.xxx

9 ( 38 )
(-) 2011-10-11

4.1.2
Creation of a baseline
If you create a baseline in an already existing configuration folder (as we usually do) you can open the
configuration folder directly from the replication workbench entry screen:
By clicking
next to the Configuration Folder entry field you can see the current selection of folders
and select the correct one:
When you have selected the correct folder, press Enter and the overview tree will open.
TA-xx.xx.xxx

10 ( 38 )
(-) 2011-10-11

Right-click on the configuration folder in the product structure overview tree, select Create Baseline:
Enter baseline name, description and baseline date (=current date).

NOTE! DO NOT SELECT Explode and FIX immediately!!!! It will corrupt BOM.
Enter also Explode to date. You can use always date 31129999.
DO NOT SELECT!!!
Press green arrow
to create the baseline.
TA-xx.xx.xxx

11 ( 38 )
(-) 2011-10-11

Result: Baseline appear in the overview tree:
4.1.3
Baseline explosion
The baseline is not yet exploded, i.e. all the VC objects which are part of the VC model have not yet
been collected. This is done by the so called FOX during the baseline explosion.
You recognize the missing explosion when you double-click the baseline and look to the workbench
view the lower left. The header symbol (material number) is not yet expanded to the explosion node:
TA-xx.xx.xxx

12 ( 38 )
(-) 2011-10-11

To explode the baseline right-click on the baseline, select Backgroud processing -> Expand Baseline:
No drop down arrow yet

Start job immediately:
You might check the job execution in transaction SM37.
TA-xx.xx.xxx

13 ( 38 )
(-) 2011-10-11

When the baseline explosion job is finished (usually it takes less than a minute), click the refresh
button
, double-click on the baseline and you will see if the explosion was successful: A drop
down arrow appears in front of the material number in the lower half of the overview screen. You can
now expand the drop down menus below the material ID:
You can check the explosion result by right-clicking the explosion data id:
TA-xx.xx.xxx

14 ( 38 )
(-) 2011-10-11

You should get a list of exploded VC objects:
By double-clicking on the Object type (for example Characteristic) you will see the list of all objects
(characteristics).
The buttons aloe other useful presentation og the FOX result. For example, the Display Explosion
shows a complete hierarchical structure of the VC model. If you place the cursor on any object,
the button Show path up to Top Object
shows the direct path from the root material to this object.
NOTE! Material masters are also listed here in FOX explosion but they are not included to the final
data transferring!!!
Return to the Replication workbench with green arrow
TA-xx.xx.xxx

15 ( 38 )
(-) 2011-10-11

4.1.4
Creation of a distribution order

Now when the baseline is successfully exploded, it is time to create a distribution order for the
package.
Right-click the baseline icon and select Create distribution order
Result: the distribution order appears in the overview screen below the baseline:
It already ha a preliminary distribution order package below (white box). However it is still empty
(recognizable by the white package icon). It will be filled in the next step.
TA-xx.xx.xxx

16 ( 38 )
(-) 2011-10-11

4.1.5
Starting the distribution

Double-click the distribution order. After that right-click on the distribution order and select Start
distribution:
Result: Status of changes to Distribution is running:
TA-xx.xx.xxx

17 ( 38 )
(-) 2011-10-11

Wait a few moments (typically some seconds). Click the refresh button
and double click the blue
distribution package icon. The status of the distribution package is changed to Saved (the red icon
does not indicate an error) and an object list will be opened:
On the object list tab you can:
4.1.6
Delete single objects
Sort the object list with button
Navigate to the objects: double-click on the object ID (you can even navigate to dependency
source code)
Sending the ALE distribution package

Change the package status from Saved to Released:
TA-xx.xx.xxx

18 ( 38 )
(-) 2011-10-11

NOTE! If you get a popup: Missing object serialization, select Yes. You have to release again after
confirmation of this popup
Status is changed to Released. If it is not updated automatically, refresh and save.
Click Send packets:
TA-xx.xx.xxx

19 ( 38 )
(-) 2011-10-11

Start job immediately:
If you want, you can check the running job in SM37.

Now the IDocs are generated. You can check that in BD87
NOTE!!! Please notice that you keep the Replication workbench in Display mode (this is done
automatically, please dont change the status!):
NOT in change mode:
Otherwise it can create some problems when creating UPSRCP-IDocs. Then the status will be
Partially sent.
TA-xx.xx.xxx

20 ( 38 )
(-) 2011-10-11

Check from CRWBD that package status is now Received
4.1.7
Sending the IDocs to the target system

NOTE!!! THIS IS A TEMPORARY STEP!!! In the future IDocs will be sent automatically but this
functionality is not available before ZAL1 is terminated.
Go to transaction BD87 and choose the target system as a partner system:
Process IDocs which are in outbound processing status IDoc ready for dispatch (ALE service):
TA-xx.xx.xxx

21 ( 38 )
(-) 2011-10-11

Log in to the target system and select sending system as a partner:
TA-xx.xx.xxx

22 ( 38 )
(-) 2011-10-11

Process the IDocs which are in status IDoc ready to be transferred to application:
IDocs will go to error status Posting only possible via ALE distribution unit Q000000XX:
TA-xx.xx.xxx

23 ( 38 )
(-) 2011-10-11

This is how it should go so dont be afraid of red colour. IDocs will be processed in correct sequence
in the next phase.
4.1.8
Posting the UPS package in the target system

Before UPS package can be posted in the target system, be sure that everything went right:
In the sending system:
o
Ensure that all IDocs have been successfully sent (all IDocs in Data passed to port OK
with status 03)
Package status in CRWBD is Received
In the target system:

o
All received inbound IDocs are in Application document not posted in status 51
Status message: Posting only possible with ALE distribution unit Q000000000000000xxx
Open transaction UPS in the target system.

Insert the number of the distribution package you just sent. To find out the correct distribution
package, check Unit of distribution package that you just sent (CRWBD in sending system):
TA-xx.xx.xxx

24 ( 38 )
(-) 2011-10-11

And enter the package name in the target system:
Or you can leave fields empty, click Execute

Received:
and select from the list the package in status
You need to enter to the UPS cockpit in change mode so press Change-icon (pen).
Set the status of package to Approve package:
TA-xx.xx.xxx

25 ( 38 )
(-) 2011-10-11

If you get a popup asking about the identification of the objects, confirm this popup and once again
click the button next to the status to approve the package.
Result:
Start posting of IDocs: Click button Post:
Start job immediately and be sure to check Complete Posting!!!
TA-xx.xx.xxx

26 ( 38 )
(-) 2011-10-11

The UPS cockpit changes to display mode. When the job s finished the IDocs in the package have
been posted.
If all IDocs are posted successfully the status of the package is changed to Updated. You need to
push Refresh
Check in BD87 that finally all IDocs are in Application document posted in status 53.
Errors may occur like in normal ALE IDoc processing. This situation is described in chapter 5.1. If the
error is that kind that you cant correct the root cause, you have to create a correction package. This
is described in the chapter 5.
TA-xx.xx.xxx

27 ( 38 )
(-) 2011-10-11

4.2
Option 2: Advanced (recommended)

When you understand the logic and structure behind the PDR process, you can start to use more
advanced and faster way of sending distribution packages. This instruction regards phases in the
sending system; the process in the target system will be as described in chapter 4.1.7.
Go to Replication workbench CRWBD and enter the configuration folder to the Folder-sheet:
Then check the correct material number and enter BOM level explosion according to your needs:
Press Save
TA-xx.xx.xxx

28 ( 38 )
(-) 2011-10-11

Right-click the configuration folder, select Background processing and Distribute completely:
This functionality creates the baseline, explodes it and creates a distribution unit all at once. You have
now give baseline information like in chapter 4.1.2:
Press then Create CM object-button
TA-xx.xx.xxx

29 ( 38 )
(-) 2011-10-11

Open baselines in the overview tree:
Click Refresh-button as long as you can see the baseline you just created:
Double click the baseline and you can see that FOX is run from the lower half of the screen. Open the
collapse tree from the baseline and you can see that distribution package is created and saved:
By double-clicking the package you can see the object list and proceed forward as described in
chapters 4.1.6 and 4.1.7.
TA-xx.xx.xxx

30 ( 38 )
(-) 2011-10-11

4.3
Good housekeeping of product changes

For good housekeeping of product changes no packages can be left to error status or not processed.
The status should always be Rejected or Updated.
If you have created a package in sending system and released it to target system, but you recognize
that you shouldnt implement the change, you can reject it before processing simply changing status to Rejected
in UPS:
The package will be rejected and no changes have been made to the VC objects in the target system.
If there are some terminal errors in the package after processing it, you can create a correction
package. This is described in chapter 5.2.
TA-xx.xx.xxx

31 ( 38 )
(-) 2011-10-11

PROBLEMATIC SITUATIONS
5.1
IDocs in error status

If something is missing from the target system or there is a conflict between some objects, status in
UPS Cockpit will change to Incorrect:
The first approach must be fixing the root cause of the problem as it is in current ALE process.
IDocs that are in error status are having a red icon in front of them:
You can sort those with buttons:
TA-xx.xx.xxx

32 ( 38 )
(-) 2011-10-11

Or you can use filter button
. Filter with IDoc status 51:
Select incorrect IDocs:
And press Call log-button:
TA-xx.xx.xxx

33 ( 38 )
(-) 2011-10-11

Here you have the error log:
Double-click the error and you can see the root cause:
Act as it is said in the error log. In this case, material master is missing from the target system, create
it first and then continue going through all errors.
Go Back to UPS cockpit with green arrow
Change UPS cockpit to change mode
Post IDocs again:
Click Yes to Existing job will be overwritten-popup
TA-xx.xx.xxx

34 ( 38 )
(-) 2011-10-11

Refresh the screen until the job is finished. Either there will be some inconsistencies left (then
proceed as described above again) or if everything is ok, status will change to Updated and all IDocs
are successfully posted:
If the root cause cant be corrected, (for example a material is expired etc.) please see instructions
how to make a correction package in chapter 5.2.
5.2
Creation of a correction package

It is very important for good housekeeping of product changes that all packages are processed and
the status is either Rejected or Updated. It is not allowed to leave packages to error status or
not processed status!!! If you create and send a distribution package you have to process it or
reject it in the target system!
If you encounter that kind of an error in PDR process that it is not possible to solve the root cause of
it, you have to create a correction package:
a. In the sender system, open package in CRWBD in change mode, and in menu: Edit -> Create
Correction
TA-xx.xx.xxx

35 ( 38 )
(-) 2011-10-11

b. a strict naming for the correction package is recommended: C_Qnnnn_01 for the first
correction of package Qnnnn (with nnnn the last 4 digits of the long package number),
C_Qnnnn_02 the second one etc. Enter name and description (e.g. Delete objects with error)
c.
Enter
d. Now the object list appears. You can also filter the error IDocs with status 53:
For the ones that have the posting error in the target, tick the Del check box.
TA-xx.xx.xxx

36 ( 38 )
(-) 2011-10-11

e. Press Save, then set status to Released and send the correction package.
f.
Process IDocs in BD87 both in sending and receiving system. NOTE! This part of the process
is valid only until ZAL1 is terminated. After that the system does this automatically!
g. In the target process the correction as normal: Approve and post.
h. Now your distribution unit should get the black-white flag and status Updated
TA-xx.xx.xxx

37 ( 38 )
(-) 2011-10-11

APPROVALS AND VERSION HISTORY

Compiled by:
Checked by:
Approved by:
Issue
A
B
VC Engineer/PDR Key User

Job Title
Job Title
Date
2011-11-11
Description of Change
Document created
Ref CR
Approved By
TA-xx.xx.xxx

Virpi Turunen
Name
Name
38 ( 38 )
(-) 2011-10-11

PRD Instructions

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

PRD Instructions

Transféré par

Droits d'auteur :

Formats disponibles

SAP Variant Configuration

PDR User Instruction

PRODUCT DATA REPLICATION TOOL PDR INSTRUCTIONS

CONCEPTS AND NAMING CONVENTIONS..........................................................................................................2

TRANSACTIONS AND SETTINGS............................................................................................................................4

IDOCS IN ERROR STATUS..........................................................................................................................................32

APPROVALS AND VERSION HISTORY.................................................................................................................38

2011 KONE Corporation

SAP Variant Configuration

CONCEPTS AND NAMING CONVENTIONS

Frame in which all configurations of

In a configuration folder, you define

In a baseline, you group together

You use a distribution order to

A distribution package controls the

Configuration definition is always CD_PDR.

2011 KONE Corporation

SAP Variant Configuration

Are predefined for each material

Create for each transport

Created automatically during

2011 KONE Corporation

Created automatically during

SAP Variant Configuration

TRANSACTIONS AND SETTINGS

and choose Options:

2011 KONE Corporation

SAP Variant Configuration

Transactions in the sending system

2011 KONE Corporation

SAP Variant Configuration

Transactions in the target system

2011 KONE Corporation

SAP Variant Configuration

Option 1: Phase by phase

Configuration folder settings

2011 KONE Corporation

SAP Variant Configuration

When you double click the folder icon

, you can specify needed BOM level explosion:

2011 KONE Corporation

SAP Variant Configuration

Possible BOM explosion levels are:

2011 KONE Corporation

SAP Variant Configuration

2011 KONE Corporation

SAP Variant Configuration

Enter baseline name, description and baseline date (=current date).

Press green arrow

to create the baseline.

2011 KONE Corporation

SAP Variant Configuration

Result: Baseline appear in the overview tree:

2011 KONE Corporation

SAP Variant Configuration

No drop down arrow yet

You might check the job execution in transaction SM37.

2011 KONE Corporation

SAP Variant Configuration

2011 KONE Corporation

SAP Variant Configuration

You should get a list of exploded VC objects:

2011 KONE Corporation

SAP Variant Configuration