Business Partner Approach in SAP S/4HANA

As part of the SAP S/4HANA Business Partner (Central Master Data) development team, we come across many concerns during the migration from ERP to SAP S/4HANA. It is vital to understand the business partner approach before migrating to SAP S/4HANA. This blog attempts to give you the latest information on business partner approach, customer/supplier integration, and conversion process. This blog is also inspired from the top simplification list items.

Business Partner Approach

In SAP S/4HANA, Business Partner is the leading object and single point of entry to maintain Business Partner, Customer, and Supplier (formerly known as Vendor) master data.

This is to ensure the ease of master data maintenance and to achieve harmonization between them. Compared to classical ERP transactions, maintenance of Customer and Supplier master data via Business Partner has many advantages:

• A legal entity is represented with one Business Partner.
• Business Partner allows maintenance of multiple addresses with corresponding address usages.
• In classical transactions, one customer can only be associated to one account group. But in Business Partner, multiple roles can be associated to the same Business Partner.
• Maximal data sharing and reuse of data which lead to an easier data consolidation.
• General Data available for all different Business Partner roles, specific data is stored for each role.
• Maintenance of multiple relationships to the same Business Partner.
• Maintenance of Time Dependency at different sub-entities roles, address, relationship, bank data etc.

Customer Supplier Integration (CVI)

There are redundant object models in the traditional ERP system. Here the vendor (now, supplier) master and customer master is used. The (mandatory) target approach in SAP S/4HANA is the Business Partner Approach. Customer Supplier Integration is a perquisite to move to SAP S/4HANA.

Business Partner is now capable of centrally managing master data for business partners, customers, and suppliers. With current development, BP is the single point of entry to create, edit, and display master data for business partners, customers, and suppliers.
It is planned to check the introduction of the CVI in the pre-checks and the technical Conversion procedure of SAP S/4HANA on-premise edition 1511, 1610, and 1709. A system where the customer/supplier integration is not in place will be declined for the transition.

Changes in Business Process 

Only SAP Business Suite customer with Customer/Supplier integration in place can move to SAP S/4HANA, on-premise(Conversion approach). It is recommended but not mandatory that BuPa ID and Customer ID/Vendor ID are the same.
The user interface for SAP S/4HANA is transaction BP. There is no specific user interface for customer/supplier like known from SAP Business Suite (the specific SAP GUI transactions like XD01, XD02, XD03 or VD01, VD02, VD03/XK01, XK02, XK03 or MK01, MK02, MK03 etc. are not available in SAP S/4HANA on-premise)

Transaction not available in SAP S/4HANA on-premise edition

FD01, FD02, FD03, FD06, FD0 FK01, FK02, FK03, FK06 MAP1, MAP2, MAP3 MK01, MK02, MK03, MK06, MK12, MK18, MK19, V-03, V-04, V-05, V-06, V-07, V-08, V-09, V-11, V+21, V+22, V+23 VAP1, VAP2, VAP3 VD01, VD02, VD03, VD06 XD01, XD02, XD03, XD06, XD07 XK01, XK02, XK03, XK06, XK07

For further information on the modified functionalities and features, refer to SAP S/4HANA Product Assistance > Cross Components > Central Master Data > SAP Business Partner.

Activities

1. Whether the Business Partner ID and Customer-ID /Vendor ID should be the same in the S/4HANA System?  The keys for a smooth synchronization of the ERP customer/vendor into the SAP S/4HANA system with the business partner as the leading object are beside Business Partner Know-How also consistent customer/supplier data and valid and consistent customer/supplier and Business Partner customizing entries. For this reason, the customer/supplier data has to be cleaned up before it can be converted into the SAP S/4HANA Business Partner.
   
   
2. Preparation Pre-Checks and clean-up customer/vendor data in the ERP System (SAP Notes: 2211312, 2210486, 2216176)
   
   
3. Synchronization Done via Synchronization Cockpit. Open SAP Note 2265093 and refer to the attached BP_Conversion Document.pdf > Chapter 4. Convert Customer/Supplier Data into Business Partner . 
4. Conversion Conversion Process must be triggered according to the BP_Conversion Document.pdf that is attached to SAP Note 2265093.
5. Business Partner Post Processing  The customer/supplier transformation is bidirectional. After successful S/4HANA conversion process, you have to activate the post processing from direction Business Partner to Customer /Supplier.

Industry Specific Actions

IS-OIL Specific Actions:

• In S/4HANA all the IS-OIL specific fields (including customer BDRP data fields) have been adapted as per the new Framework of BP.
• The IS-OIL Fields related to Vendor and Customer now have been moved to BP under the roles FLCU01 (Customer), FLVN01 (Vendor).

Retail Sites Specific Action:

• Customers and vendors assigned to Retail sites are not handled by CVI synchronization (MDS_LOAD_COCKPIT) on SAP ERP as described in this note, but by a specific migration process during SAP S/4HANA conversion. See SAP Note 2310884 for more information.

Finance:

• Refer to the blog Business Partner approach: Customer Vendor Integration to Business Partners (CVI)

Additional Information

• SAP Note 2265093 – Business Partner Approach
• SAP Note 1923393 – Contact Person Synchronization
• SAP Note 2399368 – Cockpit Excel Upload
• SAP Note 2363892 – Business Partner as one legal entity
• SAP Note 2336018 – BP S4HANA : Suppress Mandatory BP field
• SAP Note 2345087 – Missing values in required entry fields cause posting termination
• SAP Note 2400445 – Customer Company Data – Deletion/archiving/block not visible in BP transaction
• SAP Note 2349671 – Supplier Company Data – Deletion/archiving/block not visible in BP transaction

Source: https://blogs.sap.com/2018/01/18/business-partner-approach-in-sap-s4hana/

Business Partner CVI – Master Data Consistency Checks supporting the SAP S/4HANA MOVE

Value Proposition:

Proactive listing and correction of the customer / vendor master data eases the synchronization (BP/CVI) process, thereby enabling a smooth migration from SAP ECC to SAP S/4HANA.

Business Context / Motivation:

In SAP S/4HANA, Business Partner is the leading object and single entry point to maintain business partner, customer and supplier master data. As part of the conversion from SAP ECC to SAP S/4HANA, customers have to first synchronize their existing customer & vendor data records to the Business Partner. High volume of master data errors during Customer/Vendor to BP Synchronization phase results in laborious iterations of the synchronization cockpit to fix the errors.

Solution:

As of ECC EhP8 SP12^(*), SAP has delivered a standard Master data consistency check report that can be run pretty early in the conversion process (as part of the Preparation phase) that provides an exhaustive listing of the errors / inconsistencies in the existing customer & vendor master data records (with respect to BP data model).

Benefits:

• The report gives the flexibility to identify the errors for a range of customer / vendor records
• To overcome performance issues in case there are millions of customer / vendor records, there is also the possibility to additionally filter by account groups and execute the checks
• The report provides options to choose from a list of business checks or execute all checks
• Forward navigation to XD02/XK02 is possible to fix errors for one-off customer / vendor records
• Outlook: As part of the future roadmap, there is a planned development to perform mass correction with direct / inline navigation from the error log to the respective customer / vendor mass maintenance transactions

(*) The report is also made available for customers in lower releases (until ECC6.0) via NOTE (2743494)

Details:

Report: CVI_MIGRATION_PRECHK
Transaction: CVI_PRECHK


Steps:

• Launch the Master data consistency check report via transaction CVI_PRECHK
• You can execute the checks for Customer / Vendor (one at a time)
• Specify other details:
  • Customer Number Range
  • Account Group
• Select the relevant business checks to be executed (Select-All if all checks are relevant)
• In order to ensure faster processing, specify a Server Group (as defined by your Technical / System Administrator)
• Specify a description for the run; The description also serves as a reference to check the log at a later point in time
• Execute the report by clicking on the “Execute” button at the top
• A new RUN ID would be created which can be seen at the bottom section “Run History”. Click on Refresh until the run is finished
• You can then view the log by clicking on the “Run ID” hyper-link
• As the name suggests, the “Run History” shows history of all the previously executed Runs

Log:

• The log gives the details of the Run with respect to the Object (Customer / Vendor), #records processed & #records in error
• The ALV result table could be filtered / sorted by the Business check / Object ID to see all errors per Object ID or all Object IDs per Error category
• There is a possibility to navigate to the Object Details by clicking on the Object-ID (hotspot) which will navigate to the maintenance screen of the Customer / Vendor
• There is also the possibility to download all errors into an excel / spreadsheet and carry out a mass maintenance via XD99 / XK99

Summary:
With the Master data consistency check report, you can get a quick overview or summary of all errors at a very early stage of the conversion from ECC to SAP S/4HANA. Fixing the errors at this stage will enable a smooth conversion by eliminating the errors to be identified at a much later stage during synchronization to BP.

Watch this space for more updates.


Source: https://blogs.sap.com/2019/07/22/business-partner-cvi-master-data-consistency-checks-supporting-the-sap-s4hana-move/

S/4 HANA: Between Migration and New Implementation

Based on SAP announcement to prolong mainstream maintenance until the end of 2025 for SAP Business Suite 7 core application releases including SAP ERP 6.0, SAP Customer.
“https://news.sap.com/2014/10/sap-committed-innovation-choice-sap-business-suite/”
This make moving to SAP S/4 HANA is only a matter of time.

SAP provides three options to have S/4 HANA system:
1- Conversion / Migration
2- New Implementation / Greenfield
3- Central finance implementation

This blog post helps to getting better decision for moving to S/4 HANA using one of first two options.

In order to provide appropriate recommendation for which method to use, we need to:

• First : Discuss , Explain and Get answers for predefined questions:

Here are Questions in more details:

1. Do you want to keep your solution enhancements (ABAP Code for Non-standard solutions / Functions)?
2. Do you want to keep your transaction data history (Not only open items or balances but full SAP ECC historical data)?
3. Do you need a phased business roll out (Ex. Introduce some firori apps as starting phase, not all S/4 HANA capabilities at once)?
4. Does your system fulfill all conversion prerequisites? (Like Update to latest version of ECC6 Enhancement package .There are several tools that can be used to check the prerequisites for moving to Suite on HANA or S/4HANA from ECC 6 Any DB)
5. Do You Perceive your current system as Key Asset (Percentage of Current system satisfaction is important key here)?

• Second : Answers analysis

 
If Answers for all previous questions or majority are YES, we recommend Migration option as it going provide following benefits:

Faster move to SAP S/4HANA: Conversion mainly takes much less time than new implementation as SAP ECC system is up and running with all functions , Integrations and authorization
Preserve historic data: All Historical data will be migrated and still reachable on current system (Note: Un-needed Historical data recommended to be archived to reduce migrated documents size)
Investment protection: S/4 HANA migration will contribute to client new investment, will not start from beginning to start a new implementation
Limit change management: Change management for migration and tracking delta are less than new implementation
Prepare for business innovations: Massive innovation capabilities for S/4 HANA with new industry specific business processes and integration to the Cloud, SaaS applications, IoT and beyond.
No initial load of data: All ECC system data will be migrated that’s why no more data upload needed either master data nor beginning balances

However, if the answers or Majority of them are NO, We need to ask following direct question:

1. Do you need a renewal of your complete ERP solution? If answer is YES

Hence, Going with Fresh S/4 HANA new implementation Option is recommended, with all new implementations considerations.

Source: https://blogs.sap.com/2019/07/22/s4-hana-between-migration-and-new-implementation/#

SAP S/4 HANA Migration Cockpit (LTMC) – Activity Type Master Data Upload Step by Step Process

       

7 Likes 1,221 View 6 Comments

Hello Friends,
This blog briefs about Master Data Upload through SAP S/4 HANA Migration Cockpit (LTMC).
We can upload all Master Data e.g. BOM, Work Center, Routing, Activity Type Master and Activity Price, through LTMC.
Data Upload Procedure in LTMC is common for all kind of Master Data.
For explanation purpose, I am taking the Activity Type Data Upload through LTMC in 1709 SAP system.

How to login into LTMC and to download the LTMC template

In LTMC, We can download the Master Data Template, Please refer below Steps to download the Master Data Template in SAP system.
Step1: Enter LTMC Transaction Code

Step2: Enter User Name & Password in the SAP Netweaver

Step3: Create or Select your already created Migration Project
 
Step4: Select required Object e.g. Activity type, to be uploaded 
Note Here I already uploaded some Activity Type, So that It is showing Migration Status as Finished. Normally it will show as Migration Status as Not Started

Step5: Download the template by clicking Download Template ICON 

Step6: In the Template (.XML file), Enter the All Mandatory fields in the template
In the Activity Type Template, three sheets will be available

1. Introduction  – Introduction to Data Migration Templates

Read the  details about Data Migration Templates

2. Field List – Field List for Migration Object : Activity Type
Here we can see the Mandatory Fields, Type and Length details
If required, we can change the Mandatory Fields into Non-Mandatory fields

3. Activity Master – Source Data for Migration Object : Activity Type
Here we can update all required data about Activity Type and Save the XML file.

How to upload the Data through LTMC template

Please follow the above mentioned Step1 to Step 4
Step1: Enter LTMC Transaction Code
Step2: Enter User Name & Password in the SAP Netweaver
Step3: Create or Select your already created Migration Project
Step4: Select required Object e.g. Activity type, to be uploaded 
Step5: Upload filled Data Template (XML file)

Step6: Select the line and Click Activate for the Object 

Step7: Click start transfer button

Step8: Click OK button 

Step9: After completing, click close

Step10: Validate data completed click next
If any data issue exist in the XML template, we may get the error message.
Based on the error message, we have to rectify and try once again the same steps.

Step11: Complete confirm mapping values
In the drop down, we have options to correct the mapping values.


Step12: Convert Value Stage completed, Click Next for Simulate Import

Step13: Click close to complete Simulate Import

Step14: Simulate Import completed, Click close to complete Execute Import

Step15: Click Close to complete Execute Import


Step16: Click Finish to Complete Migration 

Conclusion

By this way, We can upload the Activity Type Master Data through LTMC in SAP S/4 HANA system.
In this similar way, We can upload all Master Data through LTMC, since Data Upload Procedure is same in LTMC for all Master Data.
Kindly give me your valuable feedback / suggestions to make this blog as more useful.

Thanks & Regards,
Ramkumar RV.


Source: https://blogs.sap.com/2019/05/13/sap-s4-hana-migration-cockpit-ltmc-activity-type-master-data-upload-step-by-step-process/

LTMC for Master Data Step by Step Process

Dear All,
When We are Implementing SAP S/4HANA solution, We can migrate our master data and business data from SAP systems or non-SAP systems to SAP S/4HANA. By using  SAP S/4HANA migration cockpit.
The SAP S/4HANA migration cockpit uses migration objects to identify and transfer the relevant data. A migration object describes how to migrate data for a specific business object to SAP S/4HANA. It contains information about the relevant source and target structures, as well as the relationships between these structures. It also contains mapping information for the relevant fields, as well as any rules used to convert values that are migrated from source fields to target fields. SAP provides predefined migration objects that you can use to transfer your data.
The Tool used to perform Migration is LTMC – (Legacy Transfer Migration Cockpit)
You can access the SAP S/4HANA migration cockpit by using transaction LTMC.
Note the following considerations when deciding on the most suitable approach for your project:

Consideration	Files	Staging Tables
Size Limit	200MB limit for SAP S/4HANA Migration Cockpit .*	No Limit.
System Considerations	None.	Staging system uses an SAP HANA database.
Data Provisioning	Enter data manually in each Microsoft Excel XML file.	Fill tables manually or by using preferred tools (for example SAP Agile Data Preparation).

* For on-premise systems, parameter icm/HTTP/max_request_size_KB controls the size of the http request. The value of this parameter is the maximum size (in KB) of an HTTP request. This parameter has the standard value 102400 kb (100MB) but can be changed if required. For more information, see
https://help.sap.com/viewer/fe1dfb6e6c551014b6f1befabc903d5d/7.02.19/en-US/483e87b3ca6b72d0e10000000a42189c.html

Steps to Use LTMC

1. Enter LTMC T.Code

2. LTMC Web page / Fiori App will get opened

3. Click on Create for Starting New Migration Project


4. Provide Project Title & Data Retention Time and hit Create
5. In the Search bar, we can look for an object which we want to use and upload data

6. Select Required Object and click open


It’s just an information  and press ok

7.  Click on Download Template so XML file will be downloaded

8. A pre-filled Template with detailed of each field and business is available

9. In Field, List Sheet will find each sheet which and all are mandatory  based on that we will fill data and upload

10. In Basic Data Sheet highlighted column is mandatory and fill the remaining fields and sheets as per requirement.

11. In the last Sheet, “Maintenance Status Settings” Sheet will be activating which screens are required as per business.

12. Once the template is ready with all required data need to follow below Steps

A. Upload File

B. Activate

C. Start Transfer

D. Data Validate

E. Convert values

F. Simulate

G. Execute Import

13. Click Activate

14. Click Start Transfer

15. Data will get Transferred once its done Close button will get enabled

16. If any error or data is missing will get error hear if all data in templet is good we can proceed further
17. Click next

18. When we are executing for the first time particular object in a project we need to Map fields.

19. Click  each line item and do Mapping  of Values

20. Select Line Item and Click check once status turns in to Green Light click save so next time system will do the mapping automatically

21. Once all the mapping is completed and no open items click next to simulate Import

22. Similar to upload once its completed click close to proceeding further

23. Backed  Program  will execute and data gets simulated if any missing data of mandatory fields and fields Mapping is wrong
24. If any error go back and fix and  repeat same if no error click Next

25. If all the steps are completed without any error will get above message then click finish.

Migration Status is now Finish

1. Now Check whether Material is created or not

2. Go to Display Material Fiori App and Search with the Material Number which you created


3. Select required Fields

4. Material with all the fields got updated with Screens.

For uploading data without any error try with one material and will get a lot of errors when doing initially do trial and error so will get masters in LTMC.

 Source: https://blogs.sap.com/2019/04/26/ltmc-for-master-data-step-by-step-process/