VBBPD_CM_IPOCAMAP SAP (Change Document Structure; Generated by RSSCD000) Structure details
Description: Change Document Structure; Generated by RSSCD000
Related tables to VBBPD_CM_IPOCAMAP
Access table VBBPD_CM_IPOCAMAP
Structure field list including key, data, relationships and ABAP select examples
VBBPD_CM_IPOCAMAP 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_VBBPD_CM_IPOCAMAP TYPE VBBPD_CM_IPOCAMAP.
The VBBPD_CM_IPOCAMAP 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 CM_MANDT (Client), CM_POCA_GUID (Unique Identifier), CM_INIT_GUID (Unique Identifier), CM_ALLOC_SPEND (Planned Spending Value).. 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 VBBPD_CM_IPOCAMAP 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 |
| CM_MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| CM_POCA_GUID | Unique Identifier | BBP_CM_GUID | RAW | 16 | SYSUUID | ||||
| CM_INIT_GUID | Unique Identifier | BBP_CM_GUID | RAW | 16 | SYSUUID | ||||
| CM_ALLOC_SPEND | Planned Spending Value | BBP_CM_ALLOC_SPEND | CURR | 15(2) | WERT8 | ||||
| CM_ALLOC_OBJTV | Objective Breakdown | BBP_CM_ALLOC_OBJTV | CURR | 15(2) | WERT8 | ||||
| CM_NEGO_OBJTV | Objective Breakdown | BBP_CM_ALLOC_OBJTV | CURR | 15(2) | WERT8 | ||||
| CM_ACTU_OBJTV | Objective Breakdown | BBP_CM_ALLOC_OBJTV | CURR | 15(2) | WERT8 | ||||
| CM_CURRENCY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| CM_OBJ_DESC | Description | BBP_CM_DESC | CHAR | 255 | BBP_CM_DESCRIPTION | ||||
| CM_OBJ_INVST | Objective Breakdown | BBP_CM_ALLOC_OBJTV | CURR | 15(2) | WERT8 | ||||
| CM_OBJ_RES_REQ | Description | BBP_CM_DESC | CHAR | 255 | BBP_CM_DESCRIPTION | ||||
| CM_ORG_SEQ_NUM | Sequence Number | BBP_CM_SEQ_NUM | NUMC | 3 | BBP_CM_SEQ_NUM | ||||
| KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
| Key field | Non-key field |
How do I retrieve data from SAP structure VBBPD_CM_IPOCAMAP using ABAP code?
As VBBPD_CM_IPOCAMAP 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 VBBPD_CM_IPOCAMAP as there is no data to select.How to access SAP table VBBPD_CM_IPOCAMAP
Within an ECC or HANA version of SAP you can also view further information about VBBPD_CM_IPOCAMAP 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