SAP Note 384462 - Master data and addresses Version 11 Validity: 28.07.2003 - active Language English Header Data Released On 30.07.2003 08:24:17 Release Status Released for Customer Component LO-MD-BP Business Partners Priority Recommendations / Additional Info Category Consulting Symptom You want to change, import address data for customers, vendors and contact persons or distribute the data between systems.Both, the batch input programs (RFBIDE00 or RFBIKR00) and the message types (DEBMAS or CREMAS) which are all delivered in the standard system for ALE distribution do not make all address fields available. Other Terms RFBIDE10, RFBIDE20, RFBIKR10, RFBIKR20, batch input, master data, vendors, customers, LFA1, KNA1, KNVK BAS_ALE BAS_BAPIS BAS_BDC BAS_DOCUMENTATION Reason and Prerequisites For Release 4.5, the address data was converted in different master objects (customer, vendor, contact person) to the Business Address Services (BAS, also known as central address management). With the implementation of the Business Address Services, the maintenance of the addresses is grouped in one common function and was therefore standardized. In the dialog maintenance, the previous address screen for the company address was replaced by a new screen in which the BAS subscreens are included.From a technical point of view, the database stores the addresses in separate tables;the tables of the master objects contain pointers to their assigned address data from the BAS. The tables of the BAS allow to store considerably more address information as it was possible in the old customer, vendor and contact person tables (KNA1, LFA1 and KNVK). Information from the BAS for which no corresponding field exists in the master object tables, is stored redundantly in these tables. Solution ALE distribution Addresses are assigned to separate message types and are distributed as separate objects.So that the addresses are only transferred to the systems to which also the master objects should be transferred, dependencies between the method for the address object and the master object message types were defined. These ensure that distribution criteria are also used on the level of the master object for the address object.Read Note 354107 if you filter via user-defined filter objects during the distribution of the master objects. So that the master objects and their respective addresses are transferred 'together' to the target system, the option of serialization provided by ALE was used.SAP delivers the two serialization groups GRP_DEBMAS_ADR (for the customer master) and GRP_CREMAS_ADR (for the vendor master) for this in the standard system. However, in ALE Customizing, it is still necessary, at least in the receiving system, that you make settings for the inbound processing of the message types within one serialization group.As you have to specify the logical name of the sending system among other things, SAP is not able to make any default settings in the standard systems. When you use the serialization groups delivered as a standard by SAP, the address objects are imported before the master objects.Thus the sequence address data before master objects must only be adhered to if one of the following points applies to your application: l Such fields are set as required entry fields that are only provided by the BAS in the Customizing of the customer or vendor master. For your customers, contact persons exist to which a private address or a different business address is assigned. l If posting the address data should fail for some reason, this does not mean, that the master objects are also not created automatically.In this situation, the master objects and their addresses are created with address information which redundantly exists in master data tables KNA1, LFA1 and KNVK (however, this only works if, in Customizing of the customer master or vendor master, no fields are set as required fields which are only made available by the BAS).The addresses created are indeed consistent but, in general, not complete;however, the subsequent posting of the address IDoc completes the address data. the master object key must also be entered for the batch input run of the master object.In order to simplify the maintenance of the distribution model.Without it.The maintenance of address data which exceeds the information available in the master data must be executed via the BAS interfaces (--> Note 306275). is possibly reduced.A possibility to avoid this problem is that the transfer of these address fields is only executed by the separate address transfer run and is set in the transfer run of the master objects for the corresponding fields of the NODATA indicator. the old address screens are processed. the new address screens are processed.However. it contains additional information on the distribution of addresses and their master objects.transfer of the address data should occur before the transfer of the customer or vendor masters. If you use user-defined batch input programs. LFA1 and KNVK. using the standard batch input programs for the customer and vendor master (RFBIDE00 and RFBIKR00).In Note 306275. you avoid the problems of the required entry field control and of the contact persons specified below.When you create an address. the corresponding fields of the master objects would not be filled with the correct values. Which means are available for changing or importing customer and vendor master data? As an interface for the changing or the importing of the master data you can use batch input programs RFBIDE00 (Customer master record) or RFBIKR00 (Vendor master) that are provided as a standard.The length of the master data fields was not adjusted so that the information. partner profiles). which is stored redundantly in the master tables.screen name of the indicator is 'USE_ZAV') which shows whether Business Address Services should be used for processing.If the indicator is set (that is. they were not adjusted by length to the corresponding fields of the BAS. concatenation of two fields from the BAS into a field of the master object table as it is the case for street and house number). agree with the values of the separate address transfer run. it is also important that the indicator is set on the initial screen of the corresponding maintenance dialog. Also read the respective IMG documentation. Field from KNA1 / LFA1 Field from BAS ADRNR ADRC-ADDRNUMBER .'Agree' in this case means that the values to be imported correspond to the values from the corresponding BAS fields under consideration of the length adjustment and other special features (for example. Batch input In general. you can and should only work with the new address screens. calculating the master object key in advance is possibly required when master data is created.If this is not the case. Note that this indicator can only be seen if you work in the batch input mode. The following BAPIs are available for calculating the keys in advance: l BAPI_VENDOR_GETINTNUMBER (vendor number) BAPI_CUSTOMER_GETINTNUMBER (customer number) BAPI_PARTNEREMPLOYEE_GETINTNUMBER (contact person number) l l When setting up of the master object data to be imported you have to ensure that the values of the address fields.if the indicator is not set. the current address values are not available in the master object tables.However. the values existing in the BAS tables are overwritten by the values of the corresponding fields of the master object. If you create a user-defined batch input program for the maintenance of customers or vendors using the transaction recorder.This way. the advance calculation of the master object key is only necessary if the creation of the master object is executed with internal number assignment. the flag is hidden.There. So that batch input sessions can still be imported which were created before the conversion to BAS. you will find information on the options made available by BAS for this. the system offers a report in the ALE Customizing which generates the proposal for the distribution model. you can also use the serialization groups GRP_DEBMAS_ADR (for the customer master) or GRP_CREMAS_ADR (for the vendor master) delivered in the standard system.As the information is kept redundant in these fields. In the normal online dialog. If new address fields which do not exist on the old address screens are to be transferred or the data is to be transferred in the BAS format for the corresponding fields. there is a list of address fields to which there are no corresponding fields in the master data tables and the values of which are stored there redundantly. When directly sending customer and vendor masters. as well as the ALE incoming interface with message categories DEBMAS (Customer master) or CREMAS (Vendor master). The corresponding activity is available under point " Proposal for distribution model: Customer and vendor masters" in the ALE Customizing. filled with 'X'). you must also carry out a data transfer for the master object.The indicator must be set as the options of BAS are only available in the batch input mode when the indicator is set. the corresponding module must be informed of the master object to which the address belongs.The standard batch input programs set the indicator. the direct sending of the respective addresses is also automatically triggered internally so that the master objects and their addresses are distributed in the target system when the Customizing settings are correct (distribution model.master objects had to be adjusted so that during the batch input and the internal number assignment a possibly assigned master object key is transferred. It is recommended that you execute a serialized distribution via message types in the sending system for the distribution via change pointer. List of corresponding fields In the following.You will find the corresponding activity under point 'Proposal for the distribution model:customer and vendor master'.If you work with the standard message types delivered by SAP.So that address and master object can be combined later. in this situation it is required that the transfer run of the address data occurs before the transfer run of the master objects. If fields are concerned when you change or import the address data via the BAS interfaces for which there are corresponding fields in the master object tables. On account of the separate transfer of address information and master data. even if the master object uses internal number assignment.Otherwise. an indicator was included in the initial screens of the customer master and vendor master (use central address management. for which there is a corresponding field in BAS. only the address data can be imported which is available in tables KNA1. a separate address transfer run is to be executed for this data. we highly recommend that you adjust them to the new address screens and set the indicator correspondingly.A corresponding activity for the serialized distribution via message types cannot be found in the ALE Customizing. you can no longer set the postal code field as required entry field via Customizing. However. Special features As the telephone and fax numbers of the BAS are longer as the ones of the master tables. this also Note 301362).In order to mark this and let a possible user of these communication types know that when he dials this number an incorrect connection is established.For the communication data marked with (*) it is true to say that one field is always available in table ADRC or ADRP in which the number selected as standard is also defined. ADRC-FAX_NUMBER.. the form of address text is stored in the assigned master table fields. ADRP-TEL_EXTENS.General --> Business Partners --> Customer Master -->Customer Master and Vendor Master:Central address management You will find information on the Business Address Services via Note 383362.The fields are regarded as required entry fields which every subsequent process requires these two sets of data at least (see was restricted to the country.ANRED ADRC-TITLE DATLT ADRC-EXTENSION1 KNURL / LFURL Tabelle ADR12 LAND1 ADRC-COUNTRY LZONE ADRC-TRANSPZONE NAME1 ADRC-NAME1 NAME2 ADRC-NAME2 NAME3 ADRC-NAME3 NAME4 ADRC-NAME4 ORT01 ADRC-CITY1 ORT02 ADRC-CITY2 PFACH ADRC-PO_BOX PFORT ADRC-PO_BOX_LOC PSTL2 ADRC-POST_CODE2 PSTLZ ADRC-POST_CODE1 REGIO ADRC-REGION SORTL ADRC-SORT1 SPRAS ADRC-LANGU STRAS ADRC-STREETLINE TELBX ADRC-EXTENSION2 TELF1 Tabelle ADR2 (*) TELF2 Tabelle ADR2 TELFX Tabelle ADR3 (*) TELTX Tabelle ADR4 TELX1 Tabelle ADR5 TXJCD ADRC-TAXJURCODE Field from KNVK Field from BAS ABTPA ADCP-DEPARTMENT ANRED ADRP-TITLE NAME1 ADRP-NAME_LAST NAMEV ADRP-NAME_FIRST PARGE ADRP-SEX PARLA ADRP-LANGU_P SORTL ADRP-SORT1_P SPNAM ADRP-NICKNAME TELF1 Tabelle ADR2 (*) TITEL_AP ADCP-FUNCTION In fields ADRC-TITLE or ADRP-TITLE only the key is stored under which the form of address text is defined in the BAS Customizing.These are the fields ADRC-TEL_NUMBER. it might occur that not the complete number fits into the corresponding master table field when you enter long telephone and fax numbers. ADRC-TEL_EXTENS. Additional documentation You will find information on the use of the Business Address Services in the customer master and vendor master area l In the documentation of batch input programs RRBIDE00 and RFBIKR00 delivered with the standard system In the release notes for Release 4.. This is particularly interesting if you import data with user-defined batch input programs which are not yet changed to BAS. In the Customizing settings language and country are no cannot be changed as nearly also Note 205209).the language is furthermore supported (see In the customer and vendor master.A general control of the postal code field as a required entry field is no longer planned (see also Note 153264). Validity This document is not restricted to a software component or software component version .5 under path l --> Logistics Basic Data Logistics . ADRP-TEL_NUMBER. ADRC-FAX_EXTENS.Then these two communication types might also be updated in the tables of the BAS with the incomplete numbers and the actual numbers are lost. For the vendor master. for the field status control of the customer master. filled. the last three digits of the telephone or fax numbers are filled with '. the fields for longer supported.'. References This document refers to: SAP Notes 1421692 Recommendations for modifying BP exchange from CRM to ERP 306275 Transferring address data 573396 HR customer/vendor determination: New search term 904493 Vendor monitor: Vendor update with XML and IDoc 1052964 MDM: Distribution of Business Partners. Customers. Customers. Vendors This document is referenced by: SAP Notes (7) 573396 HR customer/vendor determination: New search term 306275 Transferring address data 881094 SAPMF02D / SAPMF02K: PO box and company postal code 883532 RFBIDE00/RFBIKR00: Account number with intnl no assignment 904493 Vendor monitor: Vendor update with XML and IDoc 1421692 Recommendations for modifying BP exchange from CRM to ERP 1052964 MDM: Distribution of Business Partners. Vendors .