MCEKPVB SAP (PURCHIS Communication Structure for EKPV) Structure details
Description: PURCHIS Communication Structure for EKPV
Structure field list including key, data, relationships and ABAP select examples
MCEKPVB 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 "PURCHIS Communication Structure for EKPV" 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_MCEKPVB TYPE MCEKPVB.
The MCEKPVB table consists of various fields, each holding specific information or linking keys about PURCHIS Communication Structure for EKPV data available in SAP. These include MANDT (Client), EBELN (Purchasing Document Number), EBELP (Item Number of Purchasing Document), VSTEL (Shipping Point/Receiving Point).. 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 MCEKPVB 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 |
SUPKZ | Statistics update indicator (post in/post out) | SUPKZ | CHAR | 1 | SUPKZ | ||||
MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
EBELN | Purchasing Document Number | EBELN | CHAR | 10 | EKKO | ALPHA | EBELN | BES | MEKK_C |
EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | EKPO | EBELP | BSP | ||
VSTEL | Shipping Point/Receiving Point | VSTEL | CHAR | 4 | TVST | VSTEL | VST | ||
LPRIO | Delivery Priority | LPRIO | NUMC | 2 | TPRIO | LPRIO | |||
ROUTE | Route | ROUTE | CHAR | 6 | TVRO | ROUTE | |||
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | C_KUNNR |
KUNAG | Sold-to party | KUNAG | CHAR | 10 | KNA1 | ALPHA | KUNNR | VAG | |
SPDNR | Forwarding agent | SPDNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
VKORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
VTWEG | Distribution Channel | VTWEG | CHAR | 2 | TVTW | VTWEG | VTW | C_VTWEG | |
SPART | Division | SPART | CHAR | 2 | TSPA | SPART | SPA | C_SPART | |
LEDAT | Delivery Creation Date | LEDAT | DATS | 8 | DATUM | ||||
PLIFZ | Planned Delivery Time in Days | PLIFZ | DEC | 3 | DEC3 | ||||
SPRAS | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
VSBED | Shipping Conditions | VSBED | CHAR | 2 | TVSB | VSBED | |||
LADGR | Loading Group | LADGR | CHAR | 4 | TLGR | LADGR | |||
TRAGR | Transportation Group | TRAGR | CHAR | 4 | TTGR | TRAGR | |||
ABLAD | Unloading Point | ABLAD | CHAR | 25 | TEXT25 | ||||
KZAZU | Order Combination Indicator | KZAZU_D | CHAR | 1 | XFELD | ||||
TZONIS | Time zone of delivering location | TSEGZONISS | CHAR | 6 | Assigned to domain | TZNZONE | |||
SPE_AUTH_NUMBER | Return Material Authorization Number | /SPE/RET_RMA | CHAR | 20 | ALPHA | /SPE/RET_RMA | |||
SPE_SRC_DLV_NO | Source delivery number | /SPE/RET_SRC_DLV_NO | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
SPE_SRC_EXIDV | Source/Target handling unit (external ID) | /SPE/RET_SRC_EXIDV | CHAR | 20 | ALPHA | EXIDV | |||
SPE_INSPOUT_GUID | Inspections: Inspection outcome GUID set by EWM | /SPE/INSP_OUT_GUID_16 | RAW | 16 | /SPE/RET_GUID16 | ||||
SPE_FOLLOW_UP | Default Follow-Up Activity Code | /SPE/RET_FOLLOW_UP | CHAR | 4 | /SPE/RET_FOLLOW_UP | ||||
SPE_EXT_ID | External Delivery Number | /SPE/VBELN_EXT | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
SPE_EXT_ID_ITEM | External Delivery Item Number | /SPE/VBELN_EXT_ITEM | NUMC | 6 | Assigned to domain | POSNR | |||
PLGTYP | Planned picking storage type | MCL_PLGTYP | CHAR | 3 | T301 | LGTYP | LGT | ||
PKOBER | Planned picking area | MCL_PKOBER | CHAR | 3 | Assigned to domain | KOBER | |||
DUMMY | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY |
Key field | Non-key field |
How do I retrieve data from SAP structure MCEKPVB using ABAP code?
As MCEKPVB 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 MCEKPVB as there is no data to select.How to access SAP table MCEKPVB
Within an ECC or HANA version of SAP you can also view further information about MCEKPVB 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