Skip to Content
Personal Insights

Customer Master creation and extension in S/4 using Migration cockpit (LTMC)

There are two migration objects in S/4 delivered in 1909 for Customer Master.

  • Customer
  • Customer – extend existing record by new org levels

Customer object is used when a customer is created first time. Business Partner (BP) is created at the same time. This additional business partner creation adds complexity to customer data load in S/4 especially during initial data loads.

Extension to a different sales area or company code is done by another object – Customer – extend existing record by new org levels.

This document gives some tips that will help you fill up the templates and load these objects in S/4.

Customer

This object is used when a customer is created for the first time.

Use LTMC t-code to start the migration cockpit in the backend system.

TIP: If you do not get the Migrate Your Data screen, then your system is not set up Web Dynpro Application. Contact your Basis team.

Migrate%20your%20data

Migrate your data

You can create a new project or double click an existing one.

Select Customer to create customer first time.

Customer

Customer

Double click customer.

Migration%20Object%20Customer

Migration Object Customer

 

In here many actions are possible.

Download Template – This will download XML file.

TIP: Open this in Excel. This will show up as multiple tabs.

Upload file – After file is filled, upload here.

Activate – Activate file.

Start Transfer – To load the file. Now system will do multiple checks.

TIP: You can deactivate and delete a file if you do not want to load data.

There is a blog that covers the customer master creation in an earlier release.

https://blogs.sap.com/2018/11/14/business-partner-customer-upload-via-ltmc/

This blog is focused on changes in 1909 and tips that will help users to prepare the customer master load sheets. Data migration for customer extension object screens are included in this blog also.

 

BP Roles Tab

Add the BP roles you want to create. You can create Fin. Accounting and Sales in one file if needed.

The standard role FLCU00 Customer (Fin.Accounting) will create customer at Company Code.

The standard role FLCU01 Customer will create customer Sales views.

TIP: Do not add role 000000 Business Partner General. As long as one of company code or sales view is selected, Business Partner is created.

Customer%20-%20Roles

Customer – Roles

TIP: The template for customer number expects an external number. So you have to start with a number even if you are using internal number in BP.

Customer – Sales

For role FLCU01 Customer, typically the following tabs in load file are filled in.

  • General Data
  • Sales Data
  • Sales Partner
  • Tax Classification

General Data

Customer%20-%20General%20Data

Customer – General Data

Sales Data

Customer%20-%20Sales%20Data

Customer – Sales Data

Sales Partner

TIP: Use partner function in German not local language.

Customer%20-%20Sales%20Partner

Customer – Sales Partner

Tax Classification

Customer%20Sales%20Classification

Customer Sales Classification

Customer – Fin. Accounting (Company Code)

For role FLCU00 Customer Fin Accounting, typically the following tabs in load file are filled in.

  • General Data
  • Company Data

General data is covered earlier.

Company Data

Customer-%20Company%20Data

Customer- Company Data

Internal Number Scheme for BP

When you want to use internal number range for business partners, the migration spreadsheet is expecting customer number to be filled in. During processing in CoNvert Values, there is a mapping that will ask customer number range. If you are using internal numbers. Filling this one way or other is not going to create business partners or customers. The number range in BP has to be set correctly. See BUC2.

Customer%20-%20Numbering

Customer – Numbering

TIP: You have to convert number range to External range during dats migration.

T-code BUC2

After migration, you change to internal number range.

Customer%20-%20BP%20Group%20number%20range

Customer – BP Group number range

 

—————————————————————————————————————————-

 

Customer Master Extension

After a customer master is created, use object Customer – extend existing record by new org levels, to extend to different sales org or company code.

Customer%20Ext%20-%20Project

Customer Ext – Project

Extend Customer – BP roles

BP role(s) can be created only once. They are created with Customer object initially.

TIP: BP roles – leave blank if they are created in Customer migration object. These are not needed for customer extension.

Customer%20Ext%20-%20BP%20roles

Customer Ext – BP roles

Extend Customer Sales

Here a customer created for one sales organization can be extended to additional sales orgs.

Typically the following tabs in load file are filled in.

  • General Data
  • Sales Data
  • Sales Partner
  • Tax Classification

General Data

The data in this tab is very different than customer. Additional linkages like vendor, contact person can be made here.

Customer%20Ext%20-%20General%20Data

Customer Ext – General Data

Sales Data

Customer%20Ext%20-%20Sales%20Data

Customer Ext – Sales Data

Sales Partner

TIP: As in customer use partner function in German language

Customer%20Ext%20-%20Sales%20Partner

Customer Ext – Sales Partner

Tax Classification

If the country is loaded already with Customer object, data will be filled in automatically.

TIP: Fill this only when a new country is involved with the extension. Otherwise leave it blank.

Customer%20Ext%20-%20Tax%20Classification

Customer Ext – Tax Classification

 

Customer – Fin. Accounting (Company Code)

To extend to a new company code, typically the following tabs in load file are filled in.

  • General Data
  • Company Data

General data is covered earlier.

Company Data

Fill with data for additional company code.

Customer%20Ext%20-%20Company%20Data

Customer Ext – Company Data

 

 

 

2 Comments
You must be Logged on to comment or reply to a post.