Target fields to which the external data can be mapped. Depending on the chosen mapping format, the target fields can be one or more of the following types: Person, organization, attribute, lead, activity, survey.
Note
If the following criteria have been met, you can update the business partner data directly:
The columns containing numbers representing business partners in the external file are mapped to the fields PER_NO and ORG_NO in the target structure.
The data is correct and up-to-date.
In a Business-to-Business (B2B) scenario, the data of the organization and person must be in a single record in the file.
The table below lists details of organization-related and person-related mapping fields.
The column BP Table contains a list of table names where mapped entries are stored during business partner processing.
The fields ORG_ID_NUMBER and PERS_ID_NUMBER contain additional identification numbers of the business partner, such as the social security number or the Dun & Bradstreet number. For more information, see Customizing for Customer Relationship Management and choose
.Category | Mapping Field | Description | BP Table | BP Field |
Organization | ORG_TITLE_KEY | Title of the business partner | BUT000 | TITLE |
ORG_NAME1 | Name 1 of the business partner | BUT000 | NAME_ORG1 | |
ORG_NAME2 | Name 2 of the business partner | BUT000 | NAME_ORG2 | |
ORG_NAME3 | Name 3 of the business partner | BUT000 | NAME_ORG3 | |
ORG_LEGALFORM | BP: Legal form of the business partner | BUT000 | LEGAL_ENTY | |
ORG_FOUND_DATE | Founded on date of the organization | BUT000 | FOUND_DAT | |
ORG_TELEPHONE | Telephone: Dialing code number of the business partner | ADRC | TEL_NUMBER | |
ORG_TEL_EXT | Telephone: Extension of the business partner | ADRC | TEL_EXTENS | |
ORG_FAX | Fax number: Dialing code number of the business partner | ADRC | FAX_NUMBER | |
ORG_FAX_EXT | Fax number: Extension of the business partner | ADRC | FAX_EXTENS | |
ORG_URI | URI, for example, homepage or ftp address of the business partner | ADR12 | URI_SRCH | |
ORG_LANGUAGE | Business partner language | BUT000 | BU_LANGU | |
ORG_URI_TYPE | Indicator for URI type | ADR12 | URI_TYPE | |
Organization address | ORG_CITY | City of the business partner | ADRC | CITY1 |
ORG_POSTL_COD1 | City postal code of the business partner | ADRC | POST_CODE1 | |
ORG_POSTL_COD2 | PO box postal code of the business partner | ADRC | POST_CODE2 | |
ORG_PO_BOX | PO box of the business partner | ADRC | PO_BOX | |
ORG_PO_BOX_CIT | PO box city of the business partner | ADRC | PO_BOX_ LOC | |
ORG_STREET | Street of the business partner | ADRC | STREET | |
ORG_HOUSE_NO | House number of the business partner | ADRC | HOUSE_NUM1 | |
ORG_COUNTRYISO | Country ISO code of the business partner | ADRC | COUNTRY | |
ORG_REGION | Region (state, province, county) of the business partner | ADRC | REGION | |
ORG_ID_NUMBER | Identification number of the business partner | BUT0ID | IDNUMBER | |
ORG_NATION | ID of the international address version of the business partner | ADRC | NATION | |
Person | PERS_TITLE_KEY | Title of the business partner | BUT000 | TITLE |
PERS_FIRSTNAME | First name of business partner | BUT000 | NAME_FIRST | |
PERS_LASTNAME | Last name of business partner | BUT000 | NAME_LAST | |
PERS_INITIAL | Second forename of the person | BUT000 | INITIALS | |
PERS_TITLE_ACA1 | Academic title: Key of the business partner (organization) | BUT000 | TITLE_ACA1 | |
PERS_BIRTHDATE | Date of birth of business partner | BUT000 | BIRTHDT | |
PERS_SEX | Gender of business partner | BUT000 | XSEXM, XSEXF, XSEXU | |
PERS_MARITALSTAT | Marital status of business partner | BUT000 | MARST | |
PERS_TELEPHON | Telephone number: Dialing code number of the business partner | BUT051 (B2B) ADRC (B2C) | TEL_ NUMBER | |
PERS_TEL_EXT | Telephone number: Extension of the business partner | BUT051 (B2B) ADRC (B2C) | TEL_ EXTENS | |
PERS_FAX | Fax number: Dialing code number of the business partner | BUT051 (B2B) ADRC (B2C) | FAX_NUMBER | |
PERS_FAX_EXT | Fax number: Extension of the business partner | BUT051 (B2B) ADRC (B2C) | FAX_EXTENS | |
PERS_E_MAIL | E-mail address of the business partner | BUT051 (B2B) ADR6 (B2C) | SMTP_ADDRESS SMTP_ADDR | |
PERS_PAGER | Pager information stored as telephone number with an SMS indicator | ADR13 | PAGER_NMBR | |
PERS_LANGUAGE | Business partner language | BUT000 | BU_LANGU | |
PERS_LANGU_CORR | Correspondence language of the business partner | BUT000 | LANGU_CORR | |
Person address | PERS_CITY | City of the business partner | ADRC | CITY1 |
PERS_POSTL_COD1 | City postal code of the business partner | ADRC | POST_CODE1 | |
PERS_POSTL_COD2 | PO box postal code of the business partner | ADRC | POST_CODE2 | |
PERS_PO_BOX | PO box of the business partner | ADRC | PO_BOX | |
PERS_PO_BOX_CIT | PO box city of the business partner | ADRC | PO_BOX_LOC | |
PERS_STREET | Street of the business partner | ADRC | STREET | |
PERS_HOUSE_NO | House number of the business partner | ADRC | HOUSE_NUM1 | |
PERS_COUNTRYISO | Country ISO code of the business partner | ADRC | COUNTRY | |
PERS_REGION | Region (state, province, county) of the business partner | ADRC | REGION | |
PERS_ID_NUMBER | Identification number of the business partner | BUT0ID (B2C) | IDNUMBER | |
PERS_NATION | ID of the international address version of the business partner | ADRC | NATION | |
Description of function | CP_FUNCTIONNAME | Function name of the business partner | BUT051 | FNCTN |
CP_FUNCTIONKEY | Function key | BUT051 | PAFKT |
The table below lists details of activity-related mapping fields. The column Activity Table contains a list of table names where mapped entries are stored during business transaction creation.
Category |
Mapping Field |
Description |
Activity Table |
Field |
Activity |
TEMPLATE_ID |
ID of activity template |
CRMD_ORDERADM_H |
OBJECT_ID |
PROCESS_TYPE |
Business transaction type |
CRMD_ORDERADM_H |
PROCESS_TYPE |
|
DESCRIPTION |
Transaction description |
CRMD_ORDERADM_H |
DESCRIPTION |
|
ACTUAL_DATE_FROM |
Actual date from |
SCAPPT |
DATE_FROM |
|
ACTUAL_TIME_FROM |
Actual time from |
SCAPPT |
TIME_FROM |
|
ACTUAL_DATE_TO |
Actual date to |
SCAPPT |
DATE_FROM |
|
ACTUAL_TIME_TO |
Actual time to |
SCAPPT |
TIME_FROM |
|
USER_STATUS |
Object status |
CRM_JEST |
STAT |
|
PRIORITY |
Priority of the activity |
CRMD_ACTIVITY_H |
PRIORITY |
|
CATEGORY |
Category of the activity |
CRMD_ACTIVITY_H |
CATEGORY |
The table below lists details of lead-related mapping fields. The column Lead Table contains a list of table names where mapped entries are stored during business transaction creation.
Category |
Mapping Field |
Description |
Lead Table |
Field |
Lead |
TEMPLATE_ID |
ID of lead template |
CRMD_ORDERADM_H |
OBJECT_ID |
PROCESS_TYPE |
Business transaction type |
CRMD_ORDERADM_H |
PROCESS_TYPE |
|
DESCRIPTION |
Transaction description |
CRMD_ORDERADM_H |
DESCRIPTION |
|
START_DATE |
Lead: Start date |
SCAPPT |
DATE_FROM |
|
EXP_END_DATE |
Lead: Expected end date |
SCAPPT |
DATE_FROM |
|
USER_STATUS |
Object status |
CRM_JEST |
STAT |
|
LEAD_PRIORITY |
Opportunity/lead priority |
CRMD_LEAD_H |
IMPORTANCE |
|
LEAD_GROUP |
Lead group |
CRMD_LEAD_H |
LEAD_TYPE |
|
MANUAL_QUAL_LEV |
Lead qualification level (manual) |
CRMD_LEAD_H |
QUAL_LEVEL_MAN |
|
ORIGIN |
Origin of opportunity/lead |
CRMD_LEAD_H |
SOURCE |
The table below lists details of response-related mapping fields. The column Table contains a list of table names where mapped entries are checked against the tables under Table and the fields under Field during data mapping.
Category |
Mapping Field |
Description |
Table |
Field |
Response |
PERS_RESP_CODE |
CRM Marketing: ICRH - personalized response code - character |
CRMD_IM_ML_ITEM |
PRC |
COUPON_CODE |
Coupon code |
CRMD_MKTPL_COUP |
OFRCODE |
|
CAMPAIGN_ELEMENT |
Campaign element |
CGPL_TASK |
EXTERNAL_ID |
|
ORG_NUMBER |
Business partner number of organization |
BUT000 |
PARTNER |
|
PER_NUMBER |
Business partner number of person |
BUT000 |
PARTNER |
For more information about enhancing structures with appended fields, see Structure Enhancement Using Appended Fields.
For more information about how to create an implementation of the Business Add-In for the appended fields, see User Implementation of BAdI for Appended Fields.
For an example on how to append fields to structures and how to create an implementation of the Business Add-In, see Example: Enhancements for Industry Sector and Industry System.
For more information about External List Management, see External List Management in CRM.