LCMS_UI_CONTACTS SAP (Contact Person for LCM) Structure details
Dictionary Type: Structure
Description: Contact Person for LCM
Description: Contact Person for LCM
ABAP Code to SELECT data from LCMS_UI_CONTACTS
Related tables to LCMS_UI_CONTACTS
Access table LCMS_UI_CONTACTS
Related tables to LCMS_UI_CONTACTS
Access table LCMS_UI_CONTACTS
Structure field list including key, data, relationships and ABAP select examples
LCMS_UI_CONTACTS is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Contact Person for LCM" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_LCMS_UI_CONTACTS TYPE LCMS_UI_CONTACTS.
The LCMS_UI_CONTACTS table consists of various fields, each holding specific information or linking keys about Contact Person for LCM data available in SAP. These include ABTNR (Contact person department), UEPAR (Higher-level partner), PAFKT (Contact person function), PARVO (Partner's Authority).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can Be Enhanced (Deep)
SAP LCMS_UI_CONTACTS structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| PARNR | Number of contact person | PARNR | NUMC | 10 | PARNR | VPA | |||
| ABTNR | Contact person department | ABTNR_PA | CHAR | 4 | Assigned to domain | ABTNR | |||
| UEPAR | Higher-level partner | UEPAR | NUMC | 10 | PARNR | ||||
| PAFKT | Contact person function | PAFKT | CHAR | 2 | Assigned to domain | PAFKT | |||
| PARVO | Partner's Authority | PARVO | CHAR | 1 | Assigned to domain | PARVO | |||
| PAVIP | VIP Partner | PAVIP | CHAR | 1 | Assigned to domain | PAVIP | |||
| PARGE | Partner's gender | PARGE | CHAR | 1 | GESCH | ||||
| GBDAT | Date of Birth | GBDAT | DATS | 8 | PDATE | GBDAT | |||
| VRTNR | Representative number | VTRNR | NUMC | 10 | VTRNR | ||||
| BRYTH | Call frequency | BRYTH | CHAR | 4 | Assigned to domain | BRYTH | |||
| AKVER | Buying habits | AKVER | CHAR | 2 | Assigned to domain | AKVER | |||
| NMAIL | Advertising material indicator | NMAIL | CHAR | 1 | XFELD | ||||
| PARAU | Notes about contact person | PARAU | CHAR | 40 | TEXT40 | ||||
| PARH1 | Contact person: Attribute 1 | PAAT1 | CHAR | 2 | Assigned to domain | PARHO | |||
| PARH2 | Contact person: Attribute 2 | PAAT2 | CHAR | 2 | Assigned to domain | PAAT2 | |||
| PARH3 | Contact person: Attribute 3 | PAAT3 | CHAR | 2 | Assigned to domain | PAAT3 | |||
| PARH4 | Contact person: Attribute 4 | PAAT4 | CHAR | 2 | Assigned to domain | PAAT4 | |||
| PARH5 | Contact person: Attribute 5 | PAAT5 | CHAR | 2 | Assigned to domain | PAAT5 | |||
| MOAB1 | Contact person's visiting hours: Monday morning from ... | BEMOAB1 | TIMS | 6 | UHRZT | ||||
| MOBI1 | Contact person's visiting hours: Monday morning until ... | BEMOBI1 | TIMS | 6 | UHRZT | ||||
| MOAB2 | Contact person's visiting hours: Monday afternoon from ... | BEMOAB2 | TIMS | 6 | UHRZT | ||||
| MOBI2 | Contact person's visiting hours: Monday afternoon until ... | BEMOBI2 | TIMS | 6 | UHRZT | ||||
| DIAB1 | Contact person's visiting hours: Tuesday morning from... | BEDIAB1 | TIMS | 6 | UHRZT | ||||
| DIBI1 | Contact person's visiting hours: Tuesday morning until ... | BEDIBI1 | TIMS | 6 | UHRZT | ||||
| DIAB2 | Contact person's visiting hours: Tuesday afternoon from.. | BEDIAB2 | TIMS | 6 | UHRZT | ||||
| DIBI2 | Contact person's visiting hours: Tuesday afternoon until ... | BEDIBI2 | TIMS | 6 | UHRZT | ||||
| MIAB1 | Contact person's visiting hours: Wednesday morning from... | BEMIAB1 | TIMS | 6 | UHRZT | ||||
| MIBI1 | Contact person's visiting hours: Wednesday morning until ... | BEMIBI1 | TIMS | 6 | UHRZT | ||||
| MIAB2 | Contact person's visiting hours: Wednesday afternoon from .. | BEMIAB2 | TIMS | 6 | UHRZT | ||||
| MIBI2 | Contact person's visiting hours: Wednesday afternoon until.. | BEMIBI2 | TIMS | 6 | UHRZT | ||||
| DOAB1 | Contact person's visiting hours: Thursday morning from .... | BEDOAB1 | TIMS | 6 | UHRZT | ||||
| DOBI1 | Contact person's visiting hours: Thursday morning until .... | BEDOBI1 | TIMS | 6 | UHRZT | ||||
| DOAB2 | Contact person's visiting hours: Thursday afternoon from... | BEDOAB2 | TIMS | 6 | UHRZT | ||||
| DOBI2 | Contact person's visiting hours: Thursday afternoon until .. | BEDOBI2 | TIMS | 6 | UHRZT | ||||
| FRAB1 | Contact person's visiting hours: Friday morning from ... | BEFRAB1 | TIMS | 6 | UHRZT | ||||
| FRBI1 | Contact person's visiting hours: Friday morning until ... | BEFRBI1 | TIMS | 6 | UHRZT | ||||
| FRAB2 | Contact person's visiting hours: Friday afternoon from ... | BEFRAB2 | TIMS | 6 | UHRZT | ||||
| FRBI2 | Contact person's visiting hours: Friday afternoon until ... | BEFRBI2 | TIMS | 6 | UHRZT | ||||
| SAAB1 | Contact person's visiting hours: Saturday morning from ... | BESAAB1 | TIMS | 6 | UHRZT | ||||
| SABI1 | Contact person's visiting hours: Saturday morning until ... | BESABI1 | TIMS | 6 | UHRZT | ||||
| SAAB2 | Contact person's visiting hours: Saturday afternoon from ... | BESAAB2 | TIMS | 6 | UHRZT | ||||
| SABI2 | Contact person's visiting hours: Saturday afternoon until .. | BESABI2 | TIMS | 6 | UHRZT | ||||
| SOAB1 | Contact person's visiting hours: Sunday morning from ... | BESOAB1 | TIMS | 6 | UHRZT | ||||
| SOBI1 | Contact person's visiting hours: Sunday morning until ... | BESOBI1 | TIMS | 6 | UHRZT | ||||
| SOAB2 | Contact person's visiting hours: Sunday afternoon from ... | BESOAB2 | TIMS | 6 | UHRZT | ||||
| SOBI2 | Contact person's visiting hours: Sunday afternoon until ... | BESOBI2 | TIMS | 6 | UHRZT | ||||
| PAKN1 | Contact person: Attribute 6 | PAAT6 | CHAR | 3 | Assigned to domain | PAAT6 | |||
| PAKN2 | Contact person: Attribute 7 | PAAT7 | CHAR | 3 | Assigned to domain | PAAT7 | |||
| PAKN3 | Contact person: Attribute 8 | PAAT8 | CHAR | 3 | Assigned to domain | PAAT8 | |||
| PAKN4 | Contact person: Attribute 9 | PAAT9 | CHAR | 3 | Assigned to domain | PAAT9 | |||
| PAKN5 | Contact person: Attribute 10 | PAAT0 | CHAR | 3 | Assigned to domain | PAAT0 | |||
| SORTL | Sort field | SORTL | CHAR | 10 | CHAR10 | ||||
| FAMST | Marital Status Key | FAMST | CHAR | 1 | Assigned to domain | FAMST | |||
| ADDR_VERS | Version ID for International Addresses | AD_NATION | CHAR | 1 | TSADV | AD_NATION | ADDRESS_NATION | ||
| FROM_DATE | Valid-from date - in current Release only 00010101 possible | AD_DATE_FR | DATS | 8 | DATUM | ||||
| TO_DATE | Valid-to date in current Release only 99991231 possible | AD_DATE_TO | DATS | 8 | DATUM | ||||
| TITLE_P | Form-of-Address Key | AD_TITLE | CHAR | 4 | TSAD3 | AD_TITLE | |||
| FIRSTNAME | First name | AD_NAMEFIR | CHAR | 40 | TEXT40 | ||||
| LASTNAME | Last name | AD_NAMELAS | CHAR | 40 | TEXT40 | ||||
| BIRTH_NAME | Name of person at birth | AD_NAME2_P | CHAR | 40 | TEXT40 | ||||
| MIDDLENAME | Middle name or second forename of a person | AD_NAMEMID | CHAR | 40 | TEXT40 | ||||
| SECONDNAME | Second surname of a person | AD_NAMLAS2 | CHAR | 40 | TEXT40 | ||||
| FULLNAME | Full Name of Person | AD_NAMTEXT | CHAR | 80 | TEXT80 | ||||
| FULLNAME_X | Status of Field 'Full Name' NAME_TEXT | AD_NAMCONV | CHAR | 1 | AD_NAMCONV | ||||
| TITLE_ACA1 | Academic Title: Key | AD_TITLE1 | CHAR | 4 | TSAD2 | AD_TITLE1 | AD_TITLE1 | ||
| TITLE_ACA2 | Second academic title (key) | AD_TITLE2 | CHAR | 4 | TSAD2 | AD_TITLE1 | |||
| PREFIX1 | Name Prefix (Key) | AD_PREFIX | CHAR | 4 | TSAD4 | AD_PREFIX | |||
| PREFIX2 | 2nd name prefix (key) | AD_PREFIX2 | CHAR | 4 | TSAD4 | AD_PREFIX | |||
| TITLE_SPPL | Name supplement, e.g. noble title (key) | AD_TITLES | CHAR | 4 | TSAD5 | AD_TITLES | |||
| NICKNAME | Nickname or name used | AD_NICKNAM | CHAR | 40 | TEXT40 | ||||
| INITIALS | 'Middle Initial' or personal initials | AD_INITS | CHAR | 10 | CHAR10 | ||||
| NAMEFORMAT | Name format | AD_FORMAT | CHAR | 2 | T005N | AD_NAMFORM | |||
| NAMCOUNTRY | Country for name format rule | AD_NAMCTRY | CHAR | 3 | T005 | LAND1 | |||
| NAMCTRYISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| PROFESSION | Profession | AD_PROFESS | CHAR | 40 | TEXT40 | ||||
| SEX | Gender key | AD_SEX | CHAR | 1 | AD_SEX | ||||
| LANGU_P | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
| LANGUP_ISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
| SORT1_P | Search Term 1 | AD_SORT1 | CHAR | 20 | CHAR20 | ||||
| SORT2_P | Search Term 2 | AD_SORT2 | CHAR | 20 | CHAR20 | ||||
| LANGU_CR_P | Address record creation original language | AD_LANGUCR | LANG | 1 | T002 | ISOLA | SPRAS | ||
| LANGUCPISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
| DEPARTMENT | Department | AD_DPRTMNT | CHAR | 40 | TEXT40 | ||||
| FUNCTION | Function | AD_FNCTN | CHAR | 40 | TEXT40 | ||||
| BUILDING_P | Building (number or code) | AD_BLDNG_P | CHAR | 10 | TEXT10 | ||||
| FLOOR_P | Floor in building | AD_FLOOR | CHAR | 10 | TEXT10 | ||||
| ROOM_NO_P | Room or Appartment Number | AD_ROOMNUM | CHAR | 10 | TEXT10 | ||||
| INITS_SIG | Short name for correspondence | AD_ID_CODE | CHAR | 10 | TEXT10 | ||||
| INHOUSE_ML | Int. mail postal code | AD_IH_MAIL | CHAR | 10 | TEXT10 | ||||
| COMM_TYPE | Communication Method (Key) (Business Address Services) | AD_COMM | CHAR | 3 | TSAC | AD_COMM | |||
| PERS_GROUP | Person Group (Key) (Business Address Services) | AD_GROUP_P | CHAR | 4 | TSAD8 | AD_GROUP_P | |||
| TELEPHONE | Telephone no.: dialling code+number | AD_TLNMBR | CHAR | 30 | CHAR30 | ||||
| TELEXTENSION | Telephone no.: Extension | AD_TLXTNS | CHAR | 10 | CHAR10 | ||||
| FAX | Fax number: dialling code+number | AD_FXNMBR | CHAR | 30 | CHAR30 | ||||
| FAXEXTENSION | Fax no.: Extension | AD_FXXTNS | CHAR | 10 | CHAR10 | ||||
| E_MAIL | E-Mail Address | AD_SMTPADR | CHAR | 241 | SXIDN | AD_SMTPADR | |||
| ABTNR_TEXT | Description | VTEXT | CHAR | 20 | TEXT20 | ||||
| PAFKT_TEXT | Description | VTEXT | CHAR | 20 | TEXT20 | ||||
| MAIL_TO | String | LCM_STRING | STRG | 0 | |||||
| TELCOUNTRYISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| FAXCOUNTRYISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| MOBILE | Telephone no.: dialling code+number | AD_TLNMBR | CHAR | 30 | CHAR30 | ||||
| MOBCOUNTRYISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA |
| Key field | Non-key field |
How do I retrieve data from SAP structure LCMS_UI_CONTACTS using ABAP code?
As LCMS_UI_CONTACTS is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on LCMS_UI_CONTACTS as there is no data to select.How to access SAP table LCMS_UI_CONTACTS
Within an ECC or HANA version of SAP you can also view further information about LCMS_UI_CONTACTS and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects