UKM_S_SEARCH_ID_RESPONSE SAP (Results of the ID Search) Structure details
Description: Results of the ID Search
Related tables to UKM_S_SEARCH_ID_RESPONSE
Access table UKM_S_SEARCH_ID_RESPONSE
Structure field list including key, data, relationships and ABAP select examples
UKM_S_SEARCH_ID_RESPONSE 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 "Results of the ID Search" 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_UKM_S_SEARCH_ID_RESPONSE TYPE UKM_S_SEARCH_ID_RESPONSE.
The UKM_S_SEARCH_ID_RESPONSE table consists of various fields, each holding specific information or linking keys about Results of the ID Search data available in SAP. These include GRADE_METHOD (External Provider), BP_EXT_ID_TYPE (Identification Type), BP_EXT_ID (ID of Business Partner at Information Provider), SEARCH_RESPONSE ().. 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 UKM_S_SEARCH_ID_RESPONSE 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 |
GRADE_METHOD | External Provider | UKM_PROVIDER_EXT | CHAR | 10 | TPZ21 | BP_GRADE_METHOD | |||
BP_EXT_ID_TYPE | Identification Type | BU_ID_TYPE | CHAR | 6 | TB039A | BU_ID_TYPE | |||
BP_EXT_ID | ID of Business Partner at Information Provider | UKM_BP_EXT_ID | CHAR | 60 | CHAR60 | UMK_BP | |||
SEARCH_RESPONSE | 0 | ||||||||
MATCH_GRADE | Degree of Matching | UKM_SEARCH_ID_MATCH_GRADE | NUMC | 4 | |||||
SEARCH_RANK | Degree of Matching at Provider | UKM_SEARCH_ID_SEARCH_RANK | INT4 | 10 | INT4 | ||||
COMPANY | 0 | ||||||||
BUSINESS_NAME | Business Name | UKM_SEARCHID_BUSINESS_NAME | CHAR | 40 | BU_NAME | ||||
LEGAL_ENTITY | BP: Legal form of organization | BU_LEGENTY | CHAR | 2 | BU_LEGENTY | H_TB019 | |||
FOUNDATION_DATE | Date organization founded | BU_FOUND_DAT | DATS | 8 | DATUM | ||||
PERSON | 0 | ||||||||
NAME_LAST | Last name of business partner (person) | BU_NAMEP_L | CHAR | 40 | BU_NAME | ||||
NAME_FIRST | First name of business partner (person) | BU_NAMEP_F | CHAR | 40 | BU_NAME | ||||
NAME_BIRTH | Name at birth of business partner | BU_BIRTHNM | CHAR | 40 | BU_NAME | ||||
BIRTH_DATE | Date of Birth of Business Partner | BU_BIRTHDT | DATS | 8 | DATUM | ||||
BIRTH_PLACE | Birthplace of business partner | BU_BIRTHPL | CHAR | 40 | TEXT40 | ||||
BIRTH_COUNTRY | Country Key | LAND1 | CHAR | 3 | LAND1 | LND | |||
MARITAL_STATUS | Marital Status of Business Partner | BU_MARST | CHAR | 1 | BU_MARST | ||||
SEX | Gender | UKM_SEARCHID_SEX | CHAR | 1 | UKM_SEARCHID_SEX | ||||
NATIONALITY | Nationality | BU_NATIO | CHAR | 3 | LAND1 | ||||
ADDRESS | 0 | ||||||||
HOUSE_NUMBER | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
CITY | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
TOWN | District | AD_CITY2 | CHAR | 40 | TEXT40 | CITY_PART | |||
STATE | STATE (State, Province, County) | REGIO | CHAR | 3 | REGIO | ||||
COUNTRY | Country Key | LAND1 | CHAR | 3 | LAND1 | LND | |||
POST_CODE | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
COMMUNICATION | 0 | ||||||||
PHONE | First telephone no.: dialling code+number | AD_TLNMBR1 | CHAR | 30 | CHAR30 | ||||
PHONE_COUNTRY | Country for telephone/fax number | AD_COMCTRY | CHAR | 3 | LAND1 | LND | |||
PHONE_EXTENSION | First Telephone No.: Extension | AD_TLXTNS1 | CHAR | 10 | CHAR10 | ||||
MOBILE | First Mobile Telephone No.: Dialing Code + Number | AD_MBNMBR1 | CHAR | 30 | CHAR30 | ||||
MOBILE_COUNTRY | Country for telephone/fax number | AD_COMCTRY | CHAR | 3 | LAND1 | LND | |||
FAX | First fax no.: dialling code+number | AD_FXNMBR1 | CHAR | 30 | CHAR30 | ||||
FAX_COUNTRY | Country for telephone/fax number | AD_COMCTRY | CHAR | 3 | LAND1 | LND | |||
FAX_EXTENSION | First fax no.: extension | AD_FXXTNS1 | CHAR | 10 | CHAR10 | ||||
E_MAIL | E-Mail Address | AD_SMTPADR | CHAR | 241 | SXIDN | AD_SMTPADR | |||
IDS | 0 | ||||||||
ID_TYPE | Identification Type | BU_ID_TYPE | CHAR | 6 | BU_ID_TYPE | ||||
ID | Identification Number | BU_ID_NUMBER | CHAR | 60 | CHAR60 | ||||
TAX | 0 | ||||||||
TAX_TYPE | Tax Number Category | BPTAXTYPE | CHAR | 4 | BPTAXTYPE | ||||
TAX_NUMBER | Business Partner Tax Number | BPTAXNUM | CHAR | 20 | BPTAXNUM | ||||
POBOX | 0 | ||||||||
POBOX | PO Box | AD_POBX | CHAR | 10 | CHAR10 | ||||
POST_CODE_POBOX | PO Box Postal Code | AD_PSTCD2 | CHAR | 10 | CHAR10 | ||||
POST_CODE_COMPANY | Company Postal Code (for Large Customers) | AD_PSTCD3 | CHAR | 10 | CHAR10 | ||||
RELATI | 0 | ||||||||
R_NAME_LAST | Last Name of Spouse | UKM_SEARCH_ID_RELA_NAME_L | CHAR | 40 | BU_NAME | ||||
R_NAME_FIRST | First Name of Spouse | UKM_SEARCH_ID_RELA_NAMEP_F | CHAR | 40 | BU_NAME | ||||
R_NAME_BIRTH | Name of Spouse at Birth | UKM_SEARCH_ID_RELA_BIRTHNM | CHAR | 40 | BU_NAME | ||||
R_BIRTH_DATE | Date of Birth of Spouse | UKM_SEARCH_ID_RELA_BIRTHDT | DATS | 8 | DATUM | ||||
R_BIRTH_PLACE | Place of Birth of Spouse | UKM_SEARCH_ID_RELA_BIRTHPL | CHAR | 40 | TEXT40 | ||||
R_BIRTH_COUNTRY | Country Key | LAND1 | CHAR | 3 | LAND1 | LND | |||
R_MARITAL_STATUS | Marital Status | UKM_SEARCH_ID_RELA_MARST | CHAR | 1 | BU_MARST | ||||
R_SEX | Gender of Spouse | UKM_SEARCH_ID_RELA_SEX | CHAR | 1 | UKM_SEARCHID_SEX |
Key field | Non-key field |
How do I retrieve data from SAP structure UKM_S_SEARCH_ID_RESPONSE using ABAP code?
As UKM_S_SEARCH_ID_RESPONSE 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 UKM_S_SEARCH_ID_RESPONSE as there is no data to select.How to access SAP table UKM_S_SEARCH_ID_RESPONSE
Within an ECC or HANA version of SAP you can also view further information about UKM_S_SEARCH_ID_RESPONSE 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