BAPI_ERC_MD_EXT SAP (External Candidate's Application Data (AE)) Structure details
Description: External Candidate's Application Data (AE)
Related tables to BAPI_ERC_MD_EXT
Access table BAPI_ERC_MD_EXT
Structure field list including key, data, relationships and ABAP select examples
BAPI_ERC_MD_EXT 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 "External Candidate's Application Data (AE)" 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_BAPI_ERC_MD_EXT TYPE BAPI_ERC_MD_EXT.
The BAPI_ERC_MD_EXT table consists of various fields, each holding specific information or linking keys about External Candidate's Application Data (AE) data available in SAP. These include FIRSTNAME (First name of business partner (person)), MIDDLENAME (Middle name or second forename of a person), LASTNAME (Last name of business partner (person)), SEX (Sex of business partner (person)).. 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: Cannot Be Enhanced
SAP BAPI_ERC_MD_EXT 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 |
TITLE_KEY | Form-of-Address Key | AD_TITLE | CHAR | 4 | Assigned to domain | AD_TITLE | |||
FIRSTNAME | First name of business partner (person) | BU_NAMEP_F | CHAR | 40 | BU_NAME | ||||
MIDDLENAME | Middle name or second forename of a person | BU_NAMEMID | CHAR | 40 | BU_NAME | ||||
LASTNAME | Last name of business partner (person) | BU_NAMEP_L | CHAR | 40 | BU_NAME | ||||
SEX | Sex of business partner (person) | BU_SEXID | CHAR | 1 | BU_SEXID | ||||
BIRTHDATE | Date of Birth of Business Partner | BU_BIRTHDT | DATS | 8 | DATUM | ||||
INITIALS | 'Middle Initial' or personal initials | AD_INITS | CHAR | 10 | CHAR10 | ||||
TITLE_ACA1 | Academic Title: Key | AD_TITLE1 | CHAR | 4 | Assigned to domain | AD_TITLE1 | AD_TITLE1 | ||
TITLE_ACA2 | Second academic title (key) | AD_TITLE2 | CHAR | 4 | Assigned to domain | AD_TITLE1 | |||
TITLE_SPPL | Name supplement, e.g. noble title (key) | AD_TITLES | CHAR | 4 | Assigned to domain | AD_TITLES | |||
PREFIX1 | Name Prefix (Key) | AD_PREFIX | CHAR | 4 | Assigned to domain | AD_PREFIX | |||
ADDR_CHANNEL | Communication Channel | RCF_COMM_CHANNEL | NUMC | 2 | Assigned to domain | RCF_COMM_CHANNEL | |||
STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
STR_SUPPL1 | Street 2 | AD_STRSPP1 | CHAR | 40 | TEXT40 | ||||
COUNTRY | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
REGION | STATE (State, Province, County) | REGIO | CHAR | 3 | Assigned to domain | REGIO | |||
CITY | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
POSTL_COD1 | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
PHONE_CHANNEL | Communication Channel | RCF_COMM_CHANNEL | NUMC | 2 | Assigned to domain | RCF_COMM_CHANNEL | |||
TELEPHONE | Telephone no.: dialling code+number | AD_TLNMBR | CHAR | 30 | CHAR30 | ||||
E_MAIL | E-Mail Address | AD_SMTPADR | CHAR | 241 | SXIDN | AD_SMTPADR | |||
CORRESPONDLANGUAGE | Business Partner: Correspondence Language | BU_LANGU_CORR | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
INTEREST_GRP | Interest Group | RCF_TARGET_GRP | NUMC | 4 | Assigned to domain | RCF_TARGET_GRP | H_RCF_TARGET_GRP | ||
REFERENCE_CODE | Reference Code of Posting | RCF_EXTERNAL_CODE | CHAR | 40 | TEXT40 | RCF_REFCODE | |||
APPLICATIONDATE | Application Date | RCF_APPLICATION_DATE | DATS | 8 | DATUM | ||||
APPLICATION_STATUS | Application Status | RCF_APPLICATION_STATUS | NUMC | 1 | RCF_APPLICATION_STATUS | ||||
REASON_CODE | Status Reason | RCF_REASON_CODE | NUMC | 2 | Assigned to domain | RCF_REASON_CODE | |||
REL_OBJ_TY | Type of Related Object | SCLAS | CHAR | 2 | Assigned to domain | OTYPE | |||
SOBID | ID of Related Object | SOBID | CHAR | 45 | CHAR45 | ||||
APPL_SOURCE | Source of Candidate's Application | RCF_APPL_SOURCE | NUMC | 4 | Assigned to domain | RCF_APPL_SOURCE | |||
APPL_SOURCE_INFO | Freeform Text for Application Source | RCF_APPL_SOURCE_INFO | CHAR | 80 | TEXT80 | ||||
TECH_APPL_SOURCE | Technical Application Source | RCF_TECH_APPL_SOURCE | CHAR | 1 | RCF_TECH_APPL_SOURCE |
Key field | Non-key field |
How do I retrieve data from SAP structure BAPI_ERC_MD_EXT using ABAP code?
As BAPI_ERC_MD_EXT 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 BAPI_ERC_MD_EXT as there is no data to select.How to access SAP table BAPI_ERC_MD_EXT
Within an ECC or HANA version of SAP you can also view further information about BAPI_ERC_MD_EXT 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