BAPIMEDCM_ALLVERSIONS SAP (Version Management - All Version Data) Structure details
Description: Version Management - All Version Data
Related tables to BAPIMEDCM_ALLVERSIONS
Access table BAPIMEDCM_ALLVERSIONS
Structure field list including key, data, relationships and ABAP select examples
BAPIMEDCM_ALLVERSIONS 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 "Version Management - All Version Data" 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_BAPIMEDCM_ALLVERSIONS TYPE BAPIMEDCM_ALLVERSIONS.
The BAPIMEDCM_ALLVERSIONS table consists of various fields, each holding specific information or linking keys about Version Management - All Version Data data available in SAP. These include DOC_NUMBER (Object Number in Purchasing), ITEM_NUMBER (Purchasing object: item), VERSION (Version number in Purchasing), CREATED_BY (Name of Person who Created the Object).. 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: Cannot Be Enhanced
SAP BAPIMEDCM_ALLVERSIONS 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 |
| DOC_TYPE | Purchasing Document Category | BSTYP_DCM | CHAR | 1 | BSTYP_DCM | ||||
| DOC_NUMBER | Object Number in Purchasing | EDOKN | CHAR | 10 | ALPHA | EDOKN | |||
| ITEM_NUMBER | Purchasing object: item | EDOKP | NUMC | 5 | Assigned to domain | EBELP | |||
| VERSION | Version number in Purchasing | REVNO | CHAR | 8 | ALPHA | REVNO | |||
| CREATED_BY | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| CR_ON | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| REC_TIME | Entry time | ERZET | TIMS | 6 | UZEIT | ||||
| RELEASED_BY | Name of person effecting release | FGNAM | CHAR | 12 | USNAM | ||||
| RELEASE_DATE | Date of release | FGDAT | DATS | 8 | DATUM | ||||
| RELEASE_TIME | Time of release | FGUHR | TIMS | 6 | UZEIT | ||||
| RELEASEBY_PUR | Name of approving buyer | OKNAM | CHAR | 12 | USNAM | ||||
| RELEASEDATE_PUR | Date of buyer approval | OKDAT | DATS | 8 | DATUM | ||||
| RELEASETIME_PUR | Time of buyer approval | OKUHR | TIMS | 6 | UZEIT | ||||
| REASON | Reason for change | RSCOD | CHAR | 4 | Assigned to domain | RSCOD | |||
| DESCRIPTION | Description of version | TXZ01_DCM | CHAR | 60 | TEXT60 | ||||
| REQ_BY_EXT | External Change Number of Version | DCM_EXTNR | CHAR | 20 | CHAR20 | ||||
| REQ_BY | Person requesting change | DCM_AFNAM | CHAR | 12 | AFNAM | ||||
| NET_VALUE | Net Order Value in PO Currency | BWERT | CURR | 13(2) | WERT7 | ||||
| VALUE_CHANGED | Value change due to version | DCM_DIFWR | CURR | 13(2) | WERTV7 | ||||
| CURRENCY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| CURRENCY_ISO | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
| POST_DATE | Posting date of version | DCM_BUDAT | DATS | 8 | DATUM | ||||
| COMPLETED | Status 'version completed' | DCM_REVOK | CHAR | 1 | XFELD | ||||
| STATUS | Version status | STREV | CHAR | 1 | STREV | ||||
| DELETE_IND | Deletion Indicator in Purchasing Document | ELOEK | CHAR | 1 | ELOEK | ||||
| STATUS_DOC_OLD | Old processing state in purchasing document before version | BANPR_OLD | CHAR | 2 | BANPR |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPIMEDCM_ALLVERSIONS using ABAP code?
As BAPIMEDCM_ALLVERSIONS 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 BAPIMEDCM_ALLVERSIONS as there is no data to select.How to access SAP table BAPIMEDCM_ALLVERSIONS
Within an ECC or HANA version of SAP you can also view further information about BAPIMEDCM_ALLVERSIONS 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