MGVEXTINFOS SAP (Information for copyting/referencing external objects) Structure details
Description: Information for copyting/referencing external objects
Structure field list including key, data, relationships and ABAP select examples
MGVEXTINFOS 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 "Information for copyting/referencing external objects" 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_MGVEXTINFOS TYPE MGVEXTINFOS.
The MGVEXTINFOS table consists of various fields, each holding specific information or linking keys about Information for copyting/referencing external objects data available in SAP. These include MATNR (Material Number), WERKS (Plant), LGORT (Storage Location), BUKRS (Company Code).. 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)
SAP MGVEXTINFOS 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 |
MATNR | Material Number | MATNR | CHAR | 18 | MARA | MATN1 | MATNR | MAT | S_MAT1 |
WERKS | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
LGORT | Storage Location | LGORT_D | CHAR | 4 | T001L | LGORT | LAG | ||
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
BWKEY | Valuation Area | BWKEY | CHAR | 4 | T001K | BWKEY | BWK | ||
BWTAR | Valuation type | BWTAA | CHAR | 10 | BWTAA | BWT | |||
VKORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
VTWEG | Distribution Channel | VTWEG | CHAR | 2 | TVTW | VTWEG | VTW | C_VTWEG | |
LGNUM | Warehouse Number / Warehouse Complex | LGNUM | CHAR | 3 | T300 | LGNUM | LGN | ||
LGTYP | Storage Type | LGTYP | CHAR | 3 | T301 | LGTYP | LGT | H_T301 | |
MYKEY | LIFO valuation level | MYKEY | CHAR | 4 | T001Y | MYKEY | MYL | ||
SPRAS | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
BUKRS_VKO | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
MBRSH | Industry sector | MBRSH | CHAR | 1 | T137 | MBRSH | MTP | ||
MTART | Material Type | MTART | CHAR | 4 | T134 | MTART | MTA | ||
DISPR | Material: MRP profile | DISPR | CHAR | 4 | MDIP | DISPR | DPR | ||
PROPR | Forecast profile | PROPR | CHAR | 4 | MPRP | PROPR | PPR | ||
KZEXI | Ind.: the corresponding entry has already been maintained | KZEXIST | CHAR | 1 | XFELD | ||||
AENNR | Change Number | AENNR | CHAR | 12 | Assigned to domain | AENNR | AENNR | AEN | |
AEDAT | Date for which the change is scheduled | DAT_CHPL | DATS | 8 | DATUM | ||||
CHANGENR | Document change number | CDCHANGENR | CHAR | 10 | ALPHA | CDCHANGENR | |||
DLINE | Key date | DEADLINE | DATS | 8 | DATUM | STICH | |||
BERID | MRP Area | BERID | CHAR | 10 | Assigned to domain | BERID | BERID | ||
BERTY | Type of MRP area | BERTY | NUMC | 2 | BERTY | ||||
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | C_KUNNR |
.INCLU--AP | 0 | ||||||||
MSBOOKPARTNO | Manufacturer Book Part Number | /SAPHT/DRM_MSBOOKPART | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT1 | |
.INCLU--AP | 0 | ||||||||
VTYPE | Version Category | VERSIONTYPE | CHAR | 10 | MGVTYPE | VERSIONTYPE | |||
VCHNR | Change number material versions | MGV_VCHNR | CHAR | 12 | AENR | AENNR | AENNR | AEN | |
EVVAL | Material is Always Valid | MGV_EVER_VALID | CHAR | 1 | XFELD | ||||
DVERS | Default Version | MGV_MATNR_VALID_DEFAULT | CHAR | 18 | Assigned to domain | MATN1 | MATNR |
Key field | Non-key field |
How do I retrieve data from SAP structure MGVEXTINFOS using ABAP code?
As MGVEXTINFOS 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 MGVEXTINFOS as there is no data to select.How to access SAP table MGVEXTINFOS
Within an ECC or HANA version of SAP you can also view further information about MGVEXTINFOS 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