Ansicht
Dokumentation

EDI_V_KNADDR_EDMAP - Enter Customer Number Mapping Resulting from Customer Master Data Migration

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Enter the mapping between old customer numbers and the combinations of new customer number and address number. This mapping results from the migration of customer master data records that you should usually perform when you enable multiple address handling for SD documents.

In the Customizing activity Convert External to Internal Partner Numbers, you define the mapping used for the conversion between external partner numbers and internal partner numbers.

As soon as multiple address handling for SD documents is active, you need a different conversion for the partner functions of type 'KU' (customer) for those customer numbers that have been consolidated into 'golden' business partner records.

The old and the new conversion cannot be active at the same time.

The additional mapping in this Customizing activity allows you to adjust the conversion before multiple address handling for SD documents is activated. For inbound processing, the additional mapping enables the system to derive the old conversion rule from the new conversion rule as long as multiple address handling for SD documents has not yet been activated.

For outbound processing that takes place after the activation of multiple address handling for SD documents, the additional mapping enables the system to derive the new conversion rule from the old internal number that is still used in SD documents that were created before the activation.

Before you enter the mapping, you must have done the following:

• Activated multiple address handling for your customer master data

• Migrated affected customer master records to the respective single business partner records (that is, 'Golden Records')

Note that any entries that you make in the current Customizing activity in, for example, the quality system, cannot be transported to the production system. Therefore, you must make the required entries manually using the actual business data in the production system.

The system can apply the mappings in this Customizing activity to different scenarios. The following example illustrates one of these scenarios:

Before enabling multiple address handling for customer master data, you maintained the following entries in the Customizing activity Convert External to Internal Partner Numbers.
For partner functions of type 'KU' (Customer) such as ship-to party, bill-to party, and so on, the internal number is the customer number.

Customer	Partner Function	External Partner	Internal Number
ABC	SH (Ship-to Party)	1010	10100080
ABC	SH (Ship-to Party)	1011	10100081
ABC	SH (Ship-to Party)	1012	10100082

You now enable multiple address handling for customer master data.

You then consolidate the customers 10100080, 10100081, and 10100082 into a single business partner record with multiple addresses, with customer number 10100083.

Next, you maintain the result of the consolidation in the current Customizing activity as follows:

Old Customer	New Customer	Address No.	Address
10100080	10100083	41000	Los Angeles
10100081	10100083	41001	Dallas
10100082	10100083	41002	New York

Now you are ready to also adjust the mapping in the Customizing activity Convert External to Internal Partner Numbers:

Customer	Partner Function	External Partner	Internal Number	Address No.	Address

ABC	SH (Ship-to Party)	1010	10100083	41000	Los Angeles
ABC	SH (Ship-to Party)	1011	10100083	41001	Dallas
ABC	SH (Ship-to Party)	1012	10100083	41002	New York

This mapping is now ready to be used after the activation of multiple address handling for SD documents.

Before you activate multiple address handling for SD documents, you may receive additional inbound EDI messages from customer ABC for sales order creation.
The conversion of external partner numbers to internal partner numbers leads to the single ('golden') business partner record (10100083) with one of the multiple addresses.

As you have not yet enabled multiple address handling for SD documents, the single business partner record with one of the multiple addresses is not yet relevant for the system. SD documents (such as sales orders) still work with the old customer numbers.

To find out the correct customer number for the sales order, the system uses the mapping defined in the current Customizing activity.

Note that the app Manage Migrations - Business Partner Multiple Addressesalso populates the mapping in the current Customizing activity if there are entries defined in Customizing activity Convert External to Internal Partner Numbersfor the old customer number.

CL_GUI_FRONTEND_SERVICES - Frontend Services   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 7202 Date: 20240523 Time: 182227     sap01-206 ( 128 ms )