10Steps2S4

Logistic Preparation Activities

Activity Document

Installed Base Conversion

March 2020
10Steps2S4 – [ACT] Logistic Preparation Activities

1. Introduction
2. Precheck
3. CVI Synchronization – Preparation
4. CVI Synchronization – Check Reports
5. CVI Synchronization – CVI Mapping
6. CVI Synchronization
7. CVI Synchronization
8. CVI Synchronization
9. Check Report after converting Customers/Vendors
10. Check item “SI22: GENERIC_CHECKS”
11. Check item "SI2: Logistics_PP-MRP"
12. Check item "SI5: MasterData_PM"
13. Check item “SI3: HR_LEARN”

2
10Steps2S4 – [ACT] Logistic Preparation Activities

1 Introduction
The activities described in this document should be executed in your system in order to successfully
complete this work package.

2 Precheck
2.1. Run T Code CVI_PRECHK

Select customer or vendor

Choose Server Group = PUBLIC

Enter a description

Execute

You should see an entry under Run History. Click on the Run ID

3
10Steps2S4 – [ACT] Logistic Preparation Activities

Once you click on Run IDs, you should see no error for customers and one error for vendors as below

Now run transaction XK02 and check the error. Entry in Tax Number 5 field is not allowed for China.
Remove the entry from this field or move the value to the appropriate field and save the vendor.

Rerun the Pre-validation report using transaction CVI_PRECHK. You should not see any errors.

2.2. Run CVI Customizing Check report CVI_UPGRADE_CHECK_RESOLVE

4
10Steps2S4 – [ACT] Logistic Preparation Activities

Use transaction SE38 to execute this report

Select each option and execute (click on Check and Display Results) to see the results

5
10Steps2S4 – [ACT] Logistic Preparation Activities

6
10Steps2S4 – [ACT] Logistic Preparation Activities

3 CVI Synchronization – Preparation

3.1. SI Check Error: SI2: MasterData_BP

Use transaction SE38 to execute SI Check report

/SDF/RC_START_CHECK

3.2. Configuration Steps

1. Activate the PPO Request for the synchronization object Business Partner

IMG -> Cross-Application Components -> Master Data Synchronization -> Synchronization
Control -> Synchronization Control-> Activate PPO Requests for Platform Objects in the Dialog

2. Activate Synchronization between Customer/Vendor and BP

IMG -> Cross-Application Components -> Master Data Synchronization -> Synchronization
Control -> Synchronization Control-> Activate Synchronization Options

7
10Steps2S4 – [ACT] Logistic Preparation Activities

Only Customer to BP and Vendor to BP should be activated as shown in the screenshot

3. Activate Creation of Post Processing Orders (PPO) for component AP-MD

IMG -> Cross-Application Components -> General Application Functions -> Postprocessing Office
-> Business Processes->Activate Creation of Postprocessing Orders

4. Number Range Assignment

Please follow the menu path below and review the number range assignments for customer and
vendor

IMG -> Logistics - General -> Business Partner -> Customers -> Control-> Define and
Assign Customer Number Ranges

IMG -> Logistics - General -> Business Partner -> Vendor -> Control-> Define Number
Ranges for Vendor Master Records

Based on the number ranges used for customer and vendor the number ranges may be created
for BP following the menu path as shown in the table below. This table is only a suggestion, you
could choose your own approach.

IMG -> Cross-Application Components -> SAP Business Partner -> Business Partner->
Basic Settings -> Number Ranges and Groupings -> Define Number Ranges

From To External/Internal

B1 100000 199999 Ext

B2 200000 299999 Ext

B3 300000 399999 Ext

B4 400000 499999 Ext

8
10Steps2S4 – [ACT] Logistic Preparation Activities

B5 500000 599999 Int

B6 600000 699999 Int

AB A ZZZZZZZZZZ Ext

01 9000000 9999999 Int

5. In this step you should create BP Groupings and assign number ranges. You may check the
embedded excel files for reference. Again, the settings shown in the screenshot are suggestions
and you may choose your own approach.

Customer Number Vendor Number

Range.xlsx Range.xlsx

9
10Steps2S4 – [ACT] Logistic Preparation Activities

IMG -> Cross-Application Components -> SAP Business Partner -> Business Partner->Basic
Settings -> Number Ranges and Groupings -> Define Groupings and Assign Number Ranges

6. The next step is to link the customer account group to BP Grouping

IMG -> Cross-Application Components -> Master Data Synchronization -> Customer/Vendor
Integration -> Business Partner Settings -> Settings for Customer Integration -> Field Assignment
for Customer Integration -> Assign Keys -> Define Number Assignment for Direction Customer to
BP

7. Repeat the previous step for vendor account group

10
10Steps2S4 – [ACT] Logistic Preparation Activities

IMG -> Cross-Application Components -> Master Data Synchronization -> Customer/Vendor
Integration -> Business Partner Settings -> Settings for Vendor Integration -> Field Assignment
for Vendor Integration -> Assign Keys -> Define Number Assignment for Direction Vendor to BP

8. Assign BP roles to customer account groups

IMG -> Cross-Application Components -> Master Data Synchronization -> Customer/Vendor
Integration -> Business Partner Settings -> Settings for Customer Integration -> Define BP Role
for Direction Customer to BP

9. Assign BP roles to vendor account groups

IMG -> Cross-Application Components -> Master Data Synchronization -> Customer/Vendor
Integration -> Business Partner Settings -> Settings for Vendor Integration -> Define BP Role for
Direction Vendor to BP

11
10Steps2S4 – [ACT] Logistic Preparation Activities

4 CVI Synchronization – Check Reports

4.1. Run CVI Customizing Check report CVI_UPGRADE_CHECK_RESOLVE and confirm that there are
no customizing errors for all three selections shown in the screenshot

12
10Steps2S4 – [ACT] Logistic Preparation Activities

13
10Steps2S4 – [ACT] Logistic Preparation Activities

4.2. Run pre-check report PRECHECK_UPGRADATION_REPORT using transaction SE38

(By default, the bottom three checkboxes are checked)

14
10Steps2S4 – [ACT] Logistic Preparation Activities

Click on Customer value mapping (Red flag)

These are three errors in this system. If you complete Section 5.1 and 5.3, these errors will be
cleared. If you clear these errors, you can proceed to section 6 (CVI Synchronization).

However, the following section (5. CVI Synchronization – CVI Mapping) shows complete mapping
activities that may be necessary depending on the data in a real customer system.

5 CVI Synchronization – CVI Mapping

Complete the following mapping activities in IMG

15
10Steps2S4 – [ACT] Logistic Preparation Activities

1. Activate the Assignment of Contact Person

2. Assign Department Numbers for Contact Person

IMG → Cross-Application Components → Master Data Synchronization → Customer/Vendor

Integration → Business Partner Settings → Settings for Customer Integration → Field
Assignment for Customer Integration → Assign Attributes → Contact Persons → Assign
Department Numbers for Contact Person

Add the following entries

16
10Steps2S4 – [ACT] Logistic Preparation Activities

3. Assign Functions of Contact Person

IMG → Cross-Application Components → Master Data Synchronization → Customer/Vendor
Integration → Business Partner Settings → Settings for Customer Integration → Field
Assignment for Customer Integration → Assign Attributes → Contact Persons → Assign
Functions of Contact Person

4. Assign Authority of Contact Person

IMG → Cross-Application Components → Master Data Synchronization → Customer/Vendor

Integration → Business Partner Settings → Settings for Customer Integration → Field
Assignment for Customer Integration → Assign Attributes → Assign Authority of Contact
Person

17
10Steps2S4 – [ACT] Logistic Preparation Activities

5. Assign VIP Indicator for Contact Person

IMG → Cross-Application Components → Master Data Synchronization → Customer/Vendor

Integration → Business Partner Settings → Settings for Customer Integration → Field
Assignment for Customer Integration → Assign Attributes → Assign VIP Indicator for Contact
Person

6. Assign Marital Statuses

IMG → Cross-Application Components → Master Data Synchronization → Customer/Vendor

Integration → Business Partner Settings → Settings for Customer Integration → Field
Assignment for Customer Integration → Assign Attributes → Assign Marital Statuses

7. Assign Legal Form to Legal Status

IMG → Cross-Application Components → Master Data Synchronization → Customer/Vendor

Integration → Business Partner Settings → Settings for Customer Integration → Field
Assignment for Customer Integration → Assign Attributes → Assign Legal Form to Legal
Status

Add the following entries:

18
10Steps2S4 – [ACT] Logistic Preparation Activities

8. Assign Payment Cards

IMG → Cross-Application Components → Master Data Synchronization → Customer/Vendor

Integration → Business Partner Settings → Settings for Customer Integration → Field
Assignment for Customer Integration → Assign Attributes → Assign Payment Cards

9. Assign Industries

IMG → Cross-Application Components → Master Data Synchronization → Customer/Vendor

Integration → Business Partner Settings → Settings for Customer Integration → Field
Assignment for Customer Integration → Assign Attributes → Assign Industries

Assign both Outgoing and Incoming Industry Mapping for all Industries

Note: Ii industries are not defined already in the system, industries may have to be defined
before assigning. (IMG → Logistics - General → Business Partner → Vendors → Control
→ Define Industries)

19
10Steps2S4 – [ACT] Logistic Preparation Activities

6 CVI Synchronization
1. Now you are ready to perform the migration using Synchronization Cockpit

Important: Before you start this step, please check Customer 100012 and Vendor 300013.
These two are an example of one legal entity but created as customer and vendor in the ERP
system. After running the synchronization process you will find that this customer and vendor are
combined into one BP

1. Run transaction MDS_LOAD_COCKPIT

2. Double click the desired synchronization Process
a. Customer → Business Partner or
Vendor → Business Partner
b. Uncheck background processing
3. Filter the customer/vendor by account group or by numbers. To facilitate error analysis,
run a small batch initially by selecting a few customers or vendors.
4. There is one example data for customer and vendor representing a single legal entity.
• Run the report MDS_LOAD_COCKPIT for Customer 100012 and then vendor
300013.
• When you run the report for vendor 300013 you will see an error about data
consistency in the Monitor tab.
• Use transaction XK02 and update the address city “Houston” for vendor 300013
• Then run the report again for vendor 300013. There should not be any error this
time
• Then check the Business Partner created using transaction BP. You should see
BP 100012 with both customer and vendor roles assigned
5. Execute the report. It creates a corresponding BP for the customer, vendor and contact
person.

a. Check the execution result in the tab Monitor

20
10Steps2S4 – [ACT] Logistic Preparation Activities

2. If there are errors, select the monitor tab, and click the Call PPO icon

1. PPO screen is displayed with the master data error list

2. You could resolve the master data errors from the PPO screen or fix the errors outside PPO.
See Synchronization Cockpit help document for more information.
3. Correct all master data errors and re-run the report to complete the conversion of
customers/vendors/contact persons.

21
10Steps2S4 – [ACT] Logistic Preparation Activities

7 Check Report after converting Customers/Vendors

7.1. Run report PRECHECK_UPGRADATION_REPORT

Select all checkboxes and run. If all the customers/vendors/contact persons are synchronized, you
should get green in all items except Bp -> Customer/Vendor which will be addressed after converting
the system to S/4HANA.

7.2. Run CVI Customizing Check report CVI_UPGRADE_CHECK_RESOLVE and confirm that all the
customer/vendors/contact persons are synchronized to BP

22
10Steps2S4 – [ACT] Logistic Preparation Activities

7.3. Now that the synchronization is completed check the result of Customer 100012 and Vendor 300013
and confirm if one BP is created for both. The customer and vendor are linked.

7.4. Now run the SI Check report /SDF/RC_START_CHECK using transaction SE38

Select Display Last Check Result and execute

Now you should not see the error SI2: MasterData_BP

23
10Steps2S4 – [ACT] Logistic Preparation Activities

24
10Steps2S4 – [ACT] Logistic Preparation Activities

8 Check item “SI22: GENERIC_CHECKS”

Check Sub-ID:"TABLE_SCRAP_CHECK_TNIW5", return code = 8

Table entries (Table TNIW5)

Run report RS4SIC_TNIW5CORR (Test run checked)

25
10Steps2S4 – [ACT] Logistic Preparation Activities

Run report RS4SIC_TNIW5CORR (Test run unchecked)

26
10Steps2S4 – [ACT] Logistic Preparation Activities

9 Check item "SI2: Logistics_PP-MRP"

27
10Steps2S4 – [ACT] Logistic Preparation Activities

1. Run report MRP_AREA_STORAGE_LOC_MIGRATION from transaction SE38.

28
10Steps2S4 – [ACT] Logistic Preparation Activities

2. The first item in the above report is to activate MRP for MRP Areas.
To activate MRP for MRP areas, you firstly must have converted the existing planning file entries
at plant level into planning file entries at MRP area level. To carry out the conversion, use a
report that you start in the IMG activity Convert planning file entries for MRP areas.
This activity is explained in Chapter 9.1.1 below
3. The following chapters describe the solution for the different issues/activities reported in the
report MRP_AREA_STORAGE_LOC_MIGRATION

9.1.1 Transaction OM0F: Convert Planning file entries for MRP Areas
1. Call transaction OM0F
2. Set the conversion field to X
3. Click on execute
4. Check the result

29
10Steps2S4 – [ACT] Logistic Preparation Activities

9.1.2 Activate MRP for MRP Area

1. Call transaction SPRO and select “SAP Reference IMG”
2. Go to IMG → Materials Management → Consumption-Based Planning → Master Data → MRP
Areas → Activate MRP for MRP Areas
3. Select New Entries, check MRP Area Active and save
4. If you get any errors, logout and log back in and complete this step

9.1.3 Special Procurement Key

1. Go to IMG → Materials Management → Consumption-Based Planning → Plant Parameters →

Carry Out Overall Maintenance of Plant Parameters
2. Select Maintain Button
3. Select plant 1000
4. Select Maintain

30
10Steps2S4 – [ACT] Logistic Preparation Activities

5. Select Special Procurement

31
10Steps2S4 – [ACT] Logistic Preparation Activities

6. Create a new entry with the following details

7. You can ignore the warning “The production/stock transfer plant corresponds to the ordering
plant” by pressing Enter
8. Save and check the new entry in the main screen

9. Go back to the initial screen, click Maintain button, enter Plant 1100 and click Maintain
10. Select Special Procurement
11. Create a new entry with the following details

32
10Steps2S4 – [ACT] Logistic Preparation Activities

12. Save and check the new entry in the main screen

9.1.4 Define MRP Areas

1. Go to IMG → Materials Management → Consumption-Based Planning → Master Data → MRP

Areas → Define MRP Areas
2. Press “New Entries” to create a new MRP Area
3. Create a new MRP Area for Plant 1000 / Storage Location 1060 with the following data

33
10Steps2S4 – [ACT] Logistic Preparation Activities

4. Create another new MRP area for Plant 1100 / Storage Location 1160 with the following data

9.1.5 Final step and result

1. Execute again the report “MRP_AREA_STORAGE_LOC_MIGRATION” from transaction SE38.

2. If the report is executed successfully it does not return any message and gets directly back to the
execution screen (SE38).

Now the report MRP_AREA_STORAGE_LOC_MIGRATION should not return any message and in the SI
Check error should be cleared

34
10Steps2S4 – [ACT] Logistic Preparation Activities

9.1.6 SI Check

Run SI Check /SDF/RC_START_CHECK using transaction SE38 and validate that the error is
cleared for SI2: Logistics_PP-MRP

10 Check item "SI5: MasterData_PM"

This step addresses the following error message from the pre-checks report.

35
10Steps2S4 – [ACT] Logistic Preparation Activities

Following is the explanation of the issue from note 2330063.

In SAP S/4HANA, the table type of the table T130F has been changed so that the entries delivered by
SAP can no longer be changed in a customer system without a modification. It is simply possible to
create new, customer-specific entries in customer namespaces predefined especially for the purpose.
However, since some of the fields in T130F control the copy behavior during the creation of products, and
in Retail also when you change them, these settings should be retained during a migration. For this
purpose, the relevant fields of T130F must be copied beforehand to a new Customizing table T130F_C so
that these settings can continue to be defined customer-specifically.

NOTE: Execute the following activities also if the error does not appear in pre transition checks because if
not before it will appear during the SUM execution.

1. SAP Notes 2323185 and 2324325 have been already implemented on the system
2. Read note 2330063
3. Run report NOTE_2323185 by selecting option “Update & Activate” to create the new table
T130F_C

36
10Steps2S4 – [ACT] Logistic Preparation Activities

NOTE: If you see a message with text “The necessary changes already came via support
package. Report execution not required anymore”, that means all the required changes have
been already included in the system.

4. Now to migrate data from table T130F to the newly created table T130F_C run report
RMMT130F_CPY

NOTE: Report has to be run for each client

a. First run the report in TEST mode (TEST flag checked) for client 100

b. Check the result and note the number of records that will be created

37
10Steps2S4 – [ACT] Logistic Preparation Activities

c. Run the report again with OVERWRT checked for client 100

d. Now check the number of entries in table T130F_C using transaction SE16

e. Execute the same report again for client 000

38
10Steps2S4 – [ACT] Logistic Preparation Activities

5. Run SI Check /SDF/RC_START_CHECK using transaction SE38 and validate that the error is
cleared for SI5: MasterData_PM

11 Check item “SI3: HR_LEARN”

This step addresses the following error message from the pre-checks report.

39
10Steps2S4 – [ACT] Logistic Preparation Activities

The error is to inform that the “SAP Learning Solution” currently activated in the system is not available in
S/4HANA. Not even in the Compatibility Scope that contains SAP-HR and EA-HR.

Note 2383837 - S4TWL - SAP Learning Solution not available in Compatibility Mode describes possible
alternative solutions to address the same requirements.

Since there is no resolution for this error we have to “Apply Exemption” for this error in SI Check report

1. Go to SI Check report
2. Select the item “SI3: HR_LEARN”
3. Click the button “Apply/Revoke Exemption”

4. Confirm the pop-up message with “Yes”

40
10Steps2S4 – [ACT] Logistic Preparation Activities

5. Now if you execute again a “Check Consistency for ALL” the message related to this item will be
yellow instead of red and the error is cleared.

41