!--a11y-->
Data Model 
The data in the address lists is stored in the following master data objects.
An address list consists of administrative data (header data) and the actual addresses (item data).
The administrative data for the address lists is saved in this master data object.
|
HEX |
16 |
GUID for an address list |
|
|
CHAR |
28 |
ID for an address list |
|
|
CHAR |
10 |
Logical system in which the list was created |
|
|
CHAR |
6 |
Origin of an address list |
|
|
CHAR |
2 |
Type of an address list |
|
|
CURR |
9 |
Costs of an address list |
|
|
CUKY |
5 |
Currency of the costs |
|
|
NUMC |
4 |
Allowed usage number |
|
|
0ELM_MUDATE |
DATS |
8 |
Allowed maximum usage date |
|
DATS |
8 |
Recommended maximum usage date |
|
|
INT |
4 |
Gross number |
|
|
CHAR |
1 |
Indicator that an address list has been deleted |
|
|
DATS |
8 |
Creation date of the address list |
|
|
0CRM_CRD_BY |
CHAR |
12 |
User who created the address list |
|
DATS |
8 |
Last change date of the address list |
|
|
CHAR |
12 |
User who last changed the address list |
|
|
CHAR |
1 |
Addresses loaded |
The addresses are stored in these master data objects.
|
HEX |
16 |
GUID for an item in an address list |
|
|
HEX |
16 |
GUID for an address list |
|
|
CHAR |
28 |
ID for an address list |
|
|
CHAR |
10 |
ID of a business partner |
|
|
CHAR |
1 |
Filled business partner |
|
|
CHAR |
1 |
Indicator that the postal information for an address is incorrect |
|
|
CHAR |
1 |
Indicator that an address is duplicated |
|
|
CHAR |
1 |
Indicator that an address has reacted positively |
|
|
CHAR |
1 |
Indicator that an address has been won as a customer |
|
|
|
|
|
|
|
0COUNTRYISO |
CHAR |
2 |
Address - country key in ISO format |
|
CHAR |
3 |
Address - country key |
|
|
CHAR |
3 |
Address - region |
|
|
0CITY_1 |
CHAR |
40 |
Address - city |
|
0POSTALCODE |
CHAR |
10 |
Address - city ZIP code |
|
0STREET60 |
CHAR |
60 |
Address - street |
|
0HOUSE_NUM1 |
CHAR |
10 |
Address - house number |
|
0POBOX |
CHAR |
10 |
Address - PO box |
|
0POBOX_LOC |
CHAR |
40 |
Address - location of PO box |
|
0POSTCD_BOX |
CHAR |
10 |
Address - ZIP code of PO box |
|
CHAR |
1 |
Address - indicator for international address version |
|
|
|
|
|
|
|
0BP_ID_NUM |
CHAR |
60 |
Identification number for an address / a business partner (e.g. social security number) |
|
|
|
|
|
|
CHAR |
4 |
Organization - form of address key |
|
|
0NAME_ORG1 |
CHAR |
40 |
Organization - name 1 |
|
0NAME_ORG2 |
CHAR |
40 |
Organization - name 2 |
|
0NAME_ORG3 |
CHAR |
40 |
Organization - name 3 |
|
DATS |
8 |
Organization - foundation date |
|
|
0LEGALFORM |
CHAR |
2 |
Organization - legal form |
|
CHAR |
60 |
Organization - website |
|
|
0TEL_NUMBER |
CHAR |
30 |
Organization - telephone number (area code + extension) |
|
0TEL_EXTENS |
CHAR |
10 |
Organization - telephone number (extension) |
|
0FAX_NUMBER |
CHAR |
30 |
Organization - fax number (area code + extension) |
|
0FAX_EXTENS |
CHAR |
10 |
Organization - fax number (extension) |
|
|
|
|
|
|
CHAR |
4 |
Person - form of address key |
|
|
0BP_ACTITL1 |
CHAR |
4 |
Person - academic title (key) |
|
0BP_FSTNAME |
CHAR |
40 |
Person - first name |
|
0BP_MDLNAME |
CHAR |
40 |
Person - middle name |
|
0BP_LSTNAME |
CHAR |
40 |
Person - last name |
|
0BIRTHDAY |
DATS |
8 |
Person - birth date |
|
0GENDER |
CHAR |
1 |
Person - gender |
|
0BP_MAR_STA |
CHAR |
1 |
Person - marital status |
|
CHAR |
30 |
Person - telephone number (area code + extension) |
|
|
CHAR |
10 |
Person - telephone number (extension) |
|
|
CHAR |
30 |
Person - fax number (area code + extension) |
|
|
CHAR |
10 |
Person - fax number (extension) |
|
|
0EMAIL_ADDR |
CHAR |
60 |
Person - e-mail address |
|
CHAR |
30 |
Person - pager number (e.g. mobile telephone) |
|
|
CHAR |
40 |
Person - function description, if person is contact person for the organization |
|
|
INT |
4 |
Net number addresses |
If you change the master data objects (e.g. by adding further attributes), you must inform the following functions of these fields:
· Interface and API’s
Create your own implementation of Business Add-In (BadI) ELM_MAPPING. In the SAP standard, a default implementation is used, in which the fields can be mapped from the master data objects to the internal structures (and vice versa).
· Postal check
Create your own implementation of Business Add-In (BadI) ELM_MAPPING. In the SAP standard, a default implementation is used, in which the fields can be mapped from the master data objects to the internal structures (and vice versa).
If you want to use the new fields in the check, you must create your own implementation for das Business Add-In ELM_CHECK.
· Duplicate check
Create your own implementation of Business Add-In (BadI) ELM_MAPPING. In the SAP standard, a default implementation is used, in which the fields can be mapped from the master data objects to the internal structures (and vice versa).
If you want to use teh new fields in the check, you must create your own implementation for das Business Add-In ELM_CHECK.
· Delete
Create your own implementation of Business Add-In (BadI) ELM_MAPPING. In the SAP standard, a default implementation is used, in which the fields can be mapped from the master data objects to the internal structures (and vice versa).
· InfoSet ELM_INFOSET
Copy InfoSet ELM_INFOSET and maintain the coding of the read program accordingly, so that the new fields can be read.
In the SAP CRM system, you must create your own implentation for Business Add-In CRM_MKTLIST_BW_FIELD.