EKUNUPD SAP (BP: IS-U-Specific Data (Update)) Structure details
Description: BP: IS-U-Specific Data (Update)
Structure field list including key, data, relationships and ABAP select examples
EKUNUPD 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 "BP: IS-U-Specific Data (Update)" 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_EKUNUPD TYPE EKUNUPD.
The EKUNUPD table consists of various fields, each holding specific information or linking keys about BP: IS-U-Specific Data (Update) data available in SAP. These include MANDT (Client), PARTNER (Business Partner Number), MUSTER_KUN (Reference for creating a standard customer for bus. partner), WAKLASS (Employee classification).. 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 (character-type or numeric)
SAP EKUNUPD 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 |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
PARTNER | Business Partner Number | BU_PARTNER | CHAR | 10 | BUT000 | ALPHA | BU_PARTNER | BPA | BUPA |
MUSTER_KUN | Reference for creating a standard customer for bus. partner | MUSTER_KUN | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
WAKLASS | Employee classification | WAKLASS | CHAR | 4 | TE697 | E_WAKLASS | |||
FIRMART | Type of installation company | FIRMART | CHAR | 2 | TE183 | FIRMART | |||
ARBFELD | Company work field | ARBFELD | CHAR | 2 | TE185 | ARBFELD | |||
MITGLIED | Membership of installer | MITGLIED | CHAR | 1 | MITGLIED | ||||
SPZULASS | Division license of installer | SPZULASS | CHAR | 20 | SPZULASS | ||||
ARTZULASS | Installer license type | ARTZULASS | CHAR | 2 | TE189 | ARTZULASS | |||
AUSWANZ | Number of identifications | AUSWANZ | NUMC | 2 | AUSWANZ | ||||
PLOMBENZ | Sealing pliers number | PLOMBENZ | CHAR | 10 | PLOMBENZ | ||||
FREMDEVU | Main utility company | FREMDEVU | CHAR | 3 | TE187 | EVU | |||
STATINS | Valid status of installer in supply area | STATINS | CHAR | 2 | TE061 | STATINS | |||
STATDATUM | Date on which status of installer comes into effect | STATDATUM | DATS | 8 | STATDATUM | ||||
ERSTZUL | Date of initial license of installer | ERSTZUL | DATS | 8 | ERSTZUL | ||||
WERKSTATT | Date of workshop inspection | WERKSTATT | DATS | 8 | WERKSTATT | ||||
VERLZUL | Date of license renewal | VERLZUL | DATS | 8 | VERLZUL | ||||
ENDEZUL | Date until which license is renewed | ENDEZUL | DATS | 8 | ENDEZUL | ||||
ANZEVU | Number of utility companies | ANZEVU | NUMC | 2 | ANZEVU | ||||
ANZFIL | Number of branches supported by an installionr company | ANZFIL | NUMC | 2 | ANZFIL | ||||
AUSW_INST | Identification number for installer license | AUSW_INST | CHAR | 10 | AUSW_INST | ||||
DR_LICENSE_LAND1 | Country in which driver's license was acquired | DR_LICENSE_LAND1 | CHAR | 3 | T005 | LAND1 | |||
DR_LICENSE_REGIO | Region in which driver's license was acquired | DR_LICENSE_REGIO | CHAR | 3 | T005S | REGIO | |||
DR_LICENSE | Driver's license number | DR_LICENSE | CHAR | 20 | DR_LICENSE | ||||
SOC_SECURE | Social Insurance Number | E_SOC_SECU | CHAR | 12 | E_SOC_SECU | ||||
WELFARE | Welfare office | WELFARE | CHAR | 9 | WELFARE | ||||
PLACE_EMPL | Work center | PLACE_EMPL | CHAR | 40 | CHAR40 | ||||
KTOKLASSE | Account class | KTOKLASSE | CHAR | 4 | KONTOKLASSE | KTOKLASSE | |||
BUPINFOREL | Information release for business partner data | BUPINFOREL | CHAR | 2 | TEBUPINFOREL | ALPHA | BUPINFOREL | ||
CLERK_ID | Business partner-specific criteria for agent determination | E_CLERK_ID | CHAR | 8 | TECLERK_ID | E_CLERK_ID | |||
RECPTYPE | Category for Alternate Payee | E_RECPTYPE | CHAR | 1 | E_RECPTYPE | ||||
PYMET | Payment method for donations/fund payments | E_PYMET_DON | CHAR | 1 | TFK042Z | PYMET_KK | |||
EMBVT | Bank details ID for donations/fund payments | E_EMBVT_DON | CHAR | 4 | CHAR4 | ||||
HKONT | G/L accounts for donations/fund payments | E_HKONT_DON | CHAR | 10 | SKA1 | ALPHA | SAKNR | ||
CLASSIFICATION | Classification of Business Partner | E_CLASSIFICATION | CHAR | 4 | TE181 | CHAR4 | |||
VIP | Indicate Very Important Business Partner | E_VIP | CHAR | 1 | KENNZX | ||||
IDENT_INST | Identification Number for Installer License | IDENT_INST | CHAR | 18 | IDENT_INST | ||||
UPD_MODE | Data: Processing status | DAMODUS | CHAR | 1 | DAMODUS |
Key field | Non-key field |
How do I retrieve data from SAP structure EKUNUPD using ABAP code?
As EKUNUPD 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 EKUNUPD as there is no data to select.How to access SAP table EKUNUPD
Within an ECC or HANA version of SAP you can also view further information about EKUNUPD 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