Skip to Content

As part of majority of SAP Implementations, the customer master is one of the key master data objects to be loaded from Legacy system into SAP system.

The customer master data is very important in clients business, and the fields of the same should not be compromised during migration.

One of the main attributes of the customer master data is the dunning data, which will appraise the business with the status (riskiness for the item to be realized) of the open items.


Dunning data for customer open items is captured at two places as mentioned below:

1. Customer master data is updated with highest level of dunning irrespective of the Dunning level of

    individual line items.

2. While migrating customer open items, the last dunning date and dunning level of each individual open

    item is also migrated as part of the open items migrated to the new system

With the above explanation and understanding, we will now see why we require migration of Dunning information only at line item level but do not require at the Customer master data level.

For Example Customer account number 172110290 in legacy system was last dunned on 28.02.2014 and Dunning level as 2

/wp-content/uploads/2014/03/q_416445.png

Note: Dunning Procedure should be migrated.


Open line items of the same customer were also migrated with Dunning information as shown below.

/wp-content/uploads/2014/03/q_416445.png

When Dunning run is carried out for the same Customer in new SAP system, Customer open line item (If considered by Dunning run) will be updated with the next Dunning level and the Customer master data will always get updated with highest Dunning level of all the open items.

/wp-content/uploads/2014/03/q_416445.png

/wp-content/uploads/2014/03/q_416445.png

Customer line items reach the next Dunning level.

/wp-content/uploads/2014/03/q_416445.png

Customer master data gets updated with highest Dunning level 3

/wp-content/uploads/2014/03/q_416445.png

This situation would have been same in case Last Dunned date and Dunning level were not migrated while migrating customer master data. So, in a nutshell, MADAT-KNB5 (Last Dunned date) and MAHNS-KNB5 (Dunning level) fields can be excluded from Customer Master data migration strategy and rest of the other important data fields can be focused for successful migration of customer master data.

To report this post you need to login first.

2 Comments

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

  1. Warren Nash

    Nice bit of information.  I tested this same situation on a project a while ago.

    (0) 
  2. M. ten Hove

    Both fields: KNB5-MADAT and KNB5-MAHNS also can play a role in Customer Credit management (FD32).:Based on the value of the dunning level the customer could be refused to place a new order:

    Maximum Number of Dunning Levels Allowed

    The customer’s dunning level may only reach a specified maximum value exceeding which the item may be blocked if so configured.

    (0) 

Leave a Reply