8/12/2019 384462 - Master Data and Addresses

http://slidepdf.com/reader/full/384462-master-data-and-addresses 1/4

SAP Note 

Header Data

Symptom 

You want to change, import address data for customers, vendors and contact persons or distribute thedata 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 makeall address fields available.

Other Terms 

RFBIDE10, RFBIDE20, RFBIKR10, RFBIKR20, batch input, master data, vendors, customers, LFA1, KNA1,KNVKBAS_ALEBAS_BAPISBAS_BDCBAS_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 isgrouped in one common function and was therefore standardized.In the dialog maintenance, the previous address screen for the company address was replaced by a newscreen 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 assignedaddress data from the BAS.The tables of the BAS allow to store considerably more address information as it was possible in theold 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, isstored redundantly in these tables.

Solution 

ALE distribution 

Addresses are assigned to separate message types and are distributed as separate objects.So that theaddresses are only transferred to the systems to which also the master objects should betransferred, dependencies between the method for the address object and the master object messagetypes 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 duringthe distribution of the master objects.So that the master objects and their respective addresses are transferred 'together' to the targetsystem, the option of serialization provided by ALE was used.SAP delivers the two serializationgroups GRP_DEBMAS_ADR (for the customer master) and GRP_CREMAS_ADR (for the vendor master) for thisin the standard system.However, in ALE Customizing, it is still necessary, at least in the receiving system, that you makesettings for the inbound processing of the message types within one serialization group.As you haveto specify the logical name of the sending system among other things, SAP is not able to make anydefault settings in the standard systems.When you use the serialization groups delivered as a standard by SAP, the address objects areimported before the master objects.Thus the sequence address data before master objects must only beadhered 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 theCustomizing of the customer or vendor master.

l For your customers, contact persons exist to which a private address or a different businessaddress is assigned.

If posting the address data should fail for some reason, this does not mean, that the master objectsare also not created automatically.In this situation, the master objects and their addresses arecreated 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 areset as required fields which are only made available by the BAS).The addresses created are indeedconsistent but, in general, not complete;however, the subsequent posting of the address IDoccompletes the address data.

384462 - Master data and addresses 

Version  11 Validity: 28.07.2003 - active Language  English

Released On  30.07.2003 08:24:17

Release Status Released for Customer

Component  LO-MD-BP Business Partners

Priority  Recommendations / Additional InfoCategory  Consulting

8/12/2019 384462 - Master Data and Addresses

http://slidepdf.com/reader/full/384462-master-data-and-addresses 2/4

In order to simplify the maintenance of the distribution model, the system offers a report in theALE Customizing which generates the proposal for the distribution model.You will find thecorresponding activity under point 'Proposal for the distribution model:customer and vendor master'.The corresponding activity is available under point " Proposal for distribution model: Customer andvendor masters" in the ALE Customizing. Also read the respective IMG documentation; it containsadditional information on the distribution of addresses and their master objects.When directly sending customer and vendor masters, the direct sending of the respective addresses isalso automatically triggered internally so that the master objects and their addresses aredistributed in the target system when the Customizing settings are correct (distribution model,partner profiles).It is recommended that you execute a serialized distribution via message types in the sending systemfor the distribution via change pointer.If you work with the standard message types delivered bySAP, you can also use the serialization groups GRP_DEBMAS_ADR (for the customer master) orGRP_CREMAS_ADR (for the vendor master) delivered in the standard system.A corresponding activity forthe serialized distribution via message types cannot be found in the ALE Customizing.

Batch input 

In general, using the standard batch input programs for the customer and vendor master (RFBIDE00 andRFBIKR00), only the address data can be imported which is available in tables KNA1, LFA1 and KNVK.Asthe information is kept redundant in these fields, they were not adjusted by length to thecorresponding fields of the BAS.If new address fields which do not exist on the old address screens are to be transferred or thedata is to be transferred in the BAS format for the corresponding fields, a separate addresstransfer run is to be executed for this data.In Note 306275, you will find information on theoptions made available by BAS for this.transfer of the address data should occur before the transferof the customer or vendor masters.This way, you avoid the problems of the required entry fieldcontrol and of the contact persons specified below.So that batch input sessions can still be imported which were created before the conversion to BAS,an indicator was included in the initial screens of the customer master and vendor master (usecentral address management;screen name of the indicator is 'USE_ZAV') which shows whether BusinessAddress Services should be used for processing.If the indicator is set (that is, filled with 'X'),the new address screens are processed;if the indicator is not set, the old address screens areprocessed.The standard batch input programs set the indicator.If you use user-defined batch input programs, we highly recommend that you adjust them to the newaddress screens and set the indicator correspondingly.If you create a user-defined batch input program for the maintenance of customers or vendors usingthe transaction recorder, it is also important that the indicator is set on the initial screen ofthe corresponding maintenance dialog.The indicator must be set as the options of BAS are onlyavailable in the batch input mode when the indicator is set.Note that this indicator can only be seen if you work in the batch input mode. In the normal onlinedialog, the flag is hidden.There, you can and should only work with the new address screens.On account of the separate transfer of address information and master data, calculating the masterobject key in advance is possibly required when master data is created.When you create an address,the corresponding module must be informed of the master object to which the address belongs.However,the advance calculation of the master object key is only necessary if the creation of the masterobject is executed with internal number assignment.So that address and master object can be combinedlater, the master object key must also be entered for the batch input run of the master object, evenif the master object uses internal number assignment.master objects had to be adjusted so thatduring the batch input and the internal number assignment a possibly assigned master object key is

transferred.The following BAPIs are available for calculating the keys in advance:

l BAPI_VENDOR_GETINTNUMBER (vendor number)

l BAPI_CUSTOMER_GETINTNUMBER (customer number)

l BAPI_PARTNEREMPLOYEE_GETINTNUMBER (contact person number)

When setting up of the master object data to be imported you have to ensure that the values of theaddress fields, for which there is a corresponding field in BAS, agree with the values of theseparate address transfer run.'Agree' in this case means that the values to be imported correspondto the values from the corresponding BAS fields under consideration of the length adjustment andother special features (for example, concatenation of two fields from the BAS into a field of themaster object table as it is the case for street and house number).If this is not the case, the

values existing in the BAS tables are overwritten by the values of the corresponding fields of themaster object.A possibility to avoid this problem is that the transfer of these address fields isonly executed by the separate address transfer run and is set in the transfer run of the masterobjects for the corresponding fields of the NODATA indicator.However, in this situation it isrequired that the transfer run of the address data occurs before the transfer run of the masterobjects.Otherwise, the corresponding fields of the master objects would not be filled with thecorrect 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 inputprograms RFBIDE00 (Customer master record) or RFBIKR00 (Vendor master) that are provided as astandard, as well as the ALE incoming interface with message categories DEBMAS (Customer master) orCREMAS (Vendor master).The maintenance of address data which exceeds the information available inthe master data must be executed via the BAS interfaces (--> Note 306275).If fields are concerned when you change or import the address data via the BAS interfaces for whichthere are corresponding fields in the master object tables, you must also carry out a data transfer

for the master object.Without it, the current address values are not available in the master objecttables.

List of corresponding fields 

In the following, there is a list of address fields to which there are no corresponding fields inthe master data tables and the values of which are stored there redundantly.The length of the masterdata fields was not adjusted so that the information, which is stored redundantly in the mastertables, is possibly reduced.Field from KNA1 / LFA1 Field from BAS ADRNR ADRC-ADDRNUMBER

8/12/2019 384462 - Master Data and Addresses

http://slidepdf.com/reader/full/384462-master-data-and-addresses 3/4

ANRED ADRC-TITLEDATLT ADRC-EXTENSION1KNURL / LFURL Tabelle ADR12 LAND1 ADRC-COUNTRYLZONE ADRC-TRANSPZONENAME1 ADRC-NAME1NAME2 ADRC-NAME2NAME3 ADRC-NAME3NAME4 ADRC-NAME4ORT01 ADRC-CITY1ORT02 ADRC-CITY2PFACH ADRC-PO_BOXPFORT ADRC-PO_BOX_LOCPSTL2 ADRC-POST_CODE2PSTLZ ADRC-POST_CODE1REGIO ADRC-REGIONSORTL ADRC-SORT1SPRAS ADRC-LANGUSTRAS ADRC-STREETLINETELBX ADRC-EXTENSION2TELF1 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-DEPARTMENTANRED ADRP-TITLENAME1 ADRP-NAME_LASTNAMEV ADRP-NAME_FIRSTPARGE ADRP-SEXPARLA ADRP-LANGU_P

SORTL ADRP-SORT1_PSPNAM ADRP-NICKNAMETELF1 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 isdefined in the BAS Customizing. However, the form of address text is stored in the assigned mastertable fields.For the communication data marked with (*) it is true to say that one field is alwaysavailable in table ADRC or ADRP in which the number selected as standard is also defined.These arethe fields ADRC-TEL_NUMBER, ADRC-TEL_EXTENS, ADRC-FAX_NUMBER, ADRC-FAX_EXTENS, ADRP-TEL_NUMBER,ADRP-TEL_EXTENS.

Special features 

As the telephone and fax numbers of the BAS are longer as the ones of the master tables, it mightoccur that not the complete number fits into the corresponding master table field when you enterlong telephone and fax numbers.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, the last threedigits of the telephone or fax numbers are filled with '...'. filled.This is particularly interesting if you import data with user-defined batch input programs which arenot yet changed to BAS.Then these two communication types might also be updated in the tables of theBAS with the incomplete numbers and the actual numbers are lost.

In the Customizing settings for the field status control of the customer master, the fields forlanguage and country are no longer supported.The fields are regarded as required entry fields whichcannot be changed as nearly every subsequent process requires these two sets of data at least (seealso Note 205209).For the vendor master, this was restricted to the country;the language is furthermore supported (seealso Note 301362).

In the customer and vendor master, you can no longer set the postal code field as required entryfield via Customizing.A general control of the postal code field as a required entry field is nolonger planned (see also Note 153264).

Additional documentation 

You will find information on the use of the Business Address Services in the customer master andvendor master area

l In the documentation of batch input programs RRBIDE00 and RFBIKR00 delivered with the standardsystem

l In the release notes for Release 4.5 under path

--> Logistics Basic DataLogistics - 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.

Validity

This document is not restricted to a software component or software component version

8/12/2019 384462 - Master Data and Addresses

http://slidepdf.com/reader/full/384462-master-data-and-addresses 4/4

 

References

This document refers to:

SAP Notes 

This document is referenced by:

SAP Notes (7) 

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, Vendors 

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, Customers, Vendors