/BOFU/S_CDC_CHANGE_HDR_K SAP (Document change number per BO instance) Structure details
Description: Document change number per BO instance
Related tables to /BOFU/S_CDC_CHANGE_HDR_K
Access table /BOFU/S_CDC_CHANGE_HDR_K
Structure field list including key, data, relationships and ABAP select examples
/BOFU/S_CDC_CHANGE_HDR_K 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 "Document change number per BO instance" 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_/BOFU/S_CDC_CHANGE_HDR_K TYPE /BOFU/S_CDC_CHANGE_HDR_K.
The /BOFU/S_CDC_CHANGE_HDR_K table consists of various fields, each holding specific information or linking keys about Document change number per BO instance data available in SAP. These include KEY (NodeID), PARENT_KEY (NodeID), ROOT_KEY (NodeID), MANDANT (Client).. 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 (Deep)
SAP /BOFU/S_CDC_CHANGE_HDR_K 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 |
| KEY | NodeID | /BOBF/CONF_KEY | RAW | 16 | /BOBF/CONF_KEY | ||||
| PARENT_KEY | NodeID | /BOBF/CONF_KEY | RAW | 16 | /BOBF/CONF_KEY | ||||
| ROOT_KEY | NodeID | /BOBF/CONF_KEY | RAW | 16 | /BOBF/CONF_KEY | ||||
| MANDANT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| OBJECTCLAS | Object class | CDOBJECTCL | CHAR | 15 | ALPHA | OBJECTCL | |||
| OBJECTID | Object value | CDOBJECTV | CHAR | 90 | CHAR90 | ||||
| CHANGENR | Document change number | CDCHANGENR | CHAR | 10 | ALPHA | CDCHANGENR | |||
| USERNAME | User name of the person responsible in change document | CDUSERNAME | CHAR | 12 | CHAR12 | ||||
| UDATE | Creation date of the change document | CDDATUM | DATS | 8 | DATUM | ||||
| UTIME | Time changed | CDUZEIT | TIMS | 6 | UZEIT | ||||
| TCODE | Transaction in which a change was made | CDTCODE | CHAR | 20 | TSTC | TCODE | |||
| PLANCHNGNR | Planned change number | PLANCHNGNR | CHAR | 12 | ALPHA | PLANCHNGNR | AEN | ||
| ACT_CHNGNO | Change number of the document created by this change | CD_CHNGNO | CHAR | 10 | ALPHA | CDCHANGENR | |||
| WAS_PLANND | Flag that changes were generated from planned changes | CD_PLANNED | CHAR | 1 | XFLAG | ||||
| CHANGE_IND | Application object change type (U, I, E, D) | CDCHNGINDH | CHAR | 1 | CDCHNGIND | ||||
| LANGU | Language Key | LANGU | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
| VERSION | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| CHANGE_TIME | Changed On | /BOFU/TSTMP_CHANGED_TIME | DEC | 15 | TSTLC | /BOFU/TSTMP | |||
| CHANGED_BY | Full name of the user | /BOFU/CHANGED_BY | CHAR | 80 |
| Key field | Non-key field |
How do I retrieve data from SAP structure /BOFU/S_CDC_CHANGE_HDR_K using ABAP code?
As /BOFU/S_CDC_CHANGE_HDR_K 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 /BOFU/S_CDC_CHANGE_HDR_K as there is no data to select.How to access SAP table /BOFU/S_CDC_CHANGE_HDR_K
Within an ECC or HANA version of SAP you can also view further information about /BOFU/S_CDC_CHANGE_HDR_K 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