MEV_S_AD_ITEM_SD_WORK_DATA SAP (Period-End Valuation: Work Structure for MEV_D_AD_ITEM_SD) Structure details
Description: Period-End Valuation: Work Structure for MEV_D_AD_ITEM_SD
Related tables to MEV_S_AD_ITEM_SD_WORK_DATA
Access table MEV_S_AD_ITEM_SD_WORK_DATA
Structure field list including key, data, relationships and ABAP select examples
MEV_S_AD_ITEM_SD_WORK_DATA 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 "Period-End Valuation: Work Structure for MEV_D_AD_ITEM_SD" 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_MEV_S_AD_ITEM_SD_WORK_DATA TYPE MEV_S_AD_ITEM_SD_WORK_DATA.
The MEV_S_AD_ITEM_SD_WORK_DATA table consists of various fields, each holding specific information or linking keys about Period-End Valuation: Work Structure for MEV_D_AD_ITEM_SD data available in SAP. These include VBELN_POST (Posting Billing Document), POSNR_POST (Posting Billing Document Item), POSNR_POST_2 (Differential Billing: Item Number of the 2nd Item in a Pair), VBELN_RESET (Resetting Billing Document).. 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 MEV_S_AD_ITEM_SD_WORK_DATA 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 |
VBELN_POST | Posting Billing Document | VBELN_VF_MEV_POST | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
POSNR_POST | Posting Billing Document Item | POSNR_VF_MEV_POST | NUMC | 6 | Assigned to domain | POSNR | |||
POSNR_POST_2 | Differential Billing: Item Number of the 2nd Item in a Pair | POSNR_VF_BILL_DIFF_2 | NUMC | 6 | Assigned to domain | POSNR | |||
VBELN_RESET | Resetting Billing Document | VBELN_VF_MEV_RESET | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
POSNR_RESET | Resetting Billing Document Item | POSNR_VF_MEV_RESET | NUMC | 6 | Assigned to domain | POSNR | |||
POSNR_RESET_2 | Differential Billing: Item Number of the 2nd Item in a Pair | POSNR_VF_BILL_DIFF_2 | NUMC | 6 | Assigned to domain | POSNR | |||
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 | |
VKGRP | Sales Group | VKGRP | CHAR | 3 | Assigned to domain | VKGRP | VKG | ||
VKBUR | Sales Office | VKBUR | CHAR | 4 | Assigned to domain | VKBUR | VKB | ||
KUNAG | Sold-to party | KUNAG | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | VAG | |
VBTYP_OBJ | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
NAME1 | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
KNUMV | Number of the document condition | KNUMV | CHAR | 10 | KNUMV | ||||
VBTYP_POST | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
VBTYP_RESET | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
FKART_POST | Billing Type | FKART | CHAR | 4 | Assigned to domain | FKART |
Key field | Non-key field |
How do I retrieve data from SAP structure MEV_S_AD_ITEM_SD_WORK_DATA using ABAP code?
As MEV_S_AD_ITEM_SD_WORK_DATA 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 MEV_S_AD_ITEM_SD_WORK_DATA as there is no data to select.How to access SAP table MEV_S_AD_ITEM_SD_WORK_DATA
Within an ECC or HANA version of SAP you can also view further information about MEV_S_AD_ITEM_SD_WORK_DATA 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