VDMKAL SAP (Change Document Structure; Generated by RSSCD000) Structure details
Description: Change Document Structure; Generated by RSSCD000
Structure field list including key, data, relationships and ABAP select examples
VDMKAL 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 "Change Document Structure; Generated by RSSCD000" 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_VDMKAL TYPE VDMKAL.
The VDMKAL table consists of various fields, each holding specific information or linking keys about Change Document Structure; Generated by RSSCD000 data available in SAP. These include WERKS (Plant), VERID (Production Version), BDATU (Date validity ends), ADATU (Date for beginning of validity).. 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 VDMKAL 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 |
| WERKS | Plant | WERKS_D | CHAR | 4 | WERKS | WRK | H_T001W_C | ||
| VERID | Production Version | VERID | CHAR | 4 | Assigned to domain | VERID | VER | ||
| BDATU | Date validity ends | BDATU | DATS | 8 | DATUM | ||||
| ADATU | Date for beginning of validity | ADATU | DATS | 8 | DATUM | ADT | |||
| STLAL | Alternative BOM | STALT | CHAR | 2 | ALPHA | ALTNR | |||
| STLAN | BOM Usage | STLAN | CHAR | 1 | Assigned to domain | STLAN | CSV | ||
| PLNTY | Task List Type | PLNTY | CHAR | 1 | PLNTY | PTY | H_TCA01 | ||
| PLNNR | Key for Task List Group | PLNNR | CHAR | 8 | ALPHA | PLNNR | PLN | PLKS | |
| ALNAL | Group Counter | PLNAL | CHAR | 2 | ALPHA | ALTNR | PAL | ||
| BESKZ | Procurement Type | BESKZ | CHAR | 1 | BESKZ | MBS | |||
| SOBSL | Special procurement type | SOBSL | CHAR | 2 | Assigned to domain | SOBSL | |||
| LOSGR | Lot Size for Product Costing | CK_LOSGR | QUAN | 13(3) | MENG13 | ||||
| MDV01 | Production line | MDV01 | CHAR | 8 | Assigned to domain | MDVXX | |||
| MDV02 | Planning identification 2 | MDV02 | CHAR | 8 | Assigned to domain | MDVXX | |||
| TEXT1 | Short text on the production version | VERS_TEXT | CHAR | 40 | TEXT40 | ||||
| EWAHR | Usage Probability with Version Control | CK_EWAHR | DEC | 3 | CK_EWAHR | ||||
| VERTO | Distribution key for quantity produced | SA_VERTO | CHAR | 4 | Assigned to domain | SA_VERTL | |||
| SERKZ | Repetitive manufacturing allowed for version | SA_VERSI | CHAR | 1 | XFELD | ||||
| BSTMI | Minimum Lot Size | BSTMI | QUAN | 13(3) | MENG13 | ||||
| BSTMA | Maximum Lot Size | BSTMA | QUAN | 13(3) | MENG13 | ||||
| RGEKZ | Indicator: backflush for RS header | SA_RGEKZ | CHAR | 1 | CO_RGEKZ | ||||
| ALORT | Receiving storage location for repetitive manufacturing | ALORT | CHAR | 4 | Assigned to domain | LGORT | |||
| PLTYG | Task List Type | PLNTY | CHAR | 1 | PLNTY | PTY | H_TCA01 | ||
| PLNNG | Key for Task List Group | PLNNR | CHAR | 8 | ALPHA | PLNNR | PLN | PLKS | |
| ALNAG | Group Counter | PLNAL | CHAR | 2 | ALPHA | ALTNR | PAL | ||
| PLTYM | Task List Type | PLNTY | CHAR | 1 | PLNTY | PTY | H_TCA01 | ||
| PLNNM | Key for Task List Group | PLNNR | CHAR | 8 | ALPHA | PLNNR | PLN | PLKS | |
| ALNAM | Group Counter | PLNAL | CHAR | 2 | ALPHA | ALTNR | PAL | ||
| CSPLT | Apportionment Structure | CSPLIT | CHAR | 4 | Assigned to domain | CSPLIT | |||
| MATKO | Other material for which BOM and task list are maintained | MKAL_MATKO | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
| ELPRO | Proposed issue storage location for components | SA_ELPRO | CHAR | 4 | Assigned to domain | LGORT | |||
| PRVBE | Default supply area for components | SA_PRVBE | CHAR | 10 | Assigned to domain | PRVBE | PVB | ||
| MKSP | Production version is locked | MKSP | CHAR | 1 | MKSP | ||||
| KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND | ||||
| MARAMEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| T001WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS |
| Key field | Non-key field |
How do I retrieve data from SAP structure VDMKAL using ABAP code?
As VDMKAL 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 VDMKAL as there is no data to select.How to access SAP table VDMKAL
Within an ECC or HANA version of SAP you can also view further information about VDMKAL 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