DISER02 SAP (Internal Structure SER02) Structure details
Description: Internal Structure SER02
Structure field list including key, data, relationships and ABAP select examples
DISER02 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 "Internal Structure SER02" 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_DISER02 TYPE DISER02.
The DISER02 table consists of various fields, each holding specific information or linking keys about Internal Structure SER02 data available in SAP. These include MANDT (Client), OBKNR (Object list number), SDAUFNR (Sales Document), POSNR (Sales Document Item).. 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: Not classified
SAP DISER02 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 | T000 | MANDT | |||
OBKNR | Object list number | OBJKNR | INT4 | 10 | SER00 | OBJKN | |||
SDAUFNR | Sales Document | VBELN_VA | CHAR | 10 | VBUK | ALPHA | VBELN | AUN | |
POSNR | Sales Document Item | POSNR_VA | NUMC | 6 | VBUP | POSNR | APO | ||
DATUM | Date | DATUM | DATS | 8 | DATUM | ||||
LETZNR | Counter key | OBZAE | NUMC | 4 | NUM4 | ||||
KUNDE | Partner number (KUNNR, LIFNR, or PERNR) | KUNDE_D | CHAR | 10 | ALPHA | KUNDE | |||
ANZSN | Number of serial numbers | ANZSN | INT4 | 10 | INT4 | ||||
VORGANG | Serialization Procedure for Serial Number Management | BELEG | CHAR | 4 | T377X | BELEG | |||
VBTYP | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
SD_AUART | Sales Document Type | AUART | CHAR | 4 | Assigned to domain | AUART | AUART | AAT | |
SD_POSTYP | Sales document item category | PSTYV | CHAR | 4 | Assigned to domain | PSTYV | |||
.INCLU--AP | 0 | ||||||||
BUMP | High tech bump indicator | /SAPHT/SW_BUMP | CHAR | 1 | /SAPHT/SW_BUMP | ||||
VCPOSNR | Return item number of the SD document for version change | /SAPHT/SW_VCPOSNR | NUMC | 6 | Assigned to domain | POSNR | |||
.INCLU--AP | 0 | ||||||||
VKORG | Sales Organization | VKORG | CHAR | 4 | Assigned to domain | VKORG | VKO | C_VKORG | |
VTWEG | Distribution Channel | VTWEG | CHAR | 2 | Assigned to domain | VTWEG | VTW | C_VTWEG | |
SPART | Division | SPART | CHAR | 2 | Assigned to domain | SPART | SPA | C_SPART | |
LTSPS | Indicator : stockable type switched into standard product | /SAPHT/SW_LTSPS | CHAR | 1 | /SAPHT/SW_LTSPS |
Key field | Non-key field |
How do I retrieve data from SAP structure DISER02 using ABAP code?
As DISER02 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 DISER02 as there is no data to select.How to access SAP table DISER02
Within an ECC or HANA version of SAP you can also view further information about DISER02 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