VDFKKORDER 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
VDFKKORDER 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_VDFKKORDER TYPE VDFKKORDER.
The VDFKKORDER 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 MANDT (Client), ORDNR (Request Number), ORDCLS (Request Class), ORDTYP (Request Category).. 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 VDFKKORDER 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 |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
ORDNR | Request Number | ORDNR_KK | CHAR | 12 | ALPHA | ORDNR_KK | |||
ORDCLS | Request Class | ORDCLS_KK | CHAR | 1 | ORDCLS_KK | ||||
ORDTYP | Request Category | ORDTYP_KK | CHAR | 1 | Assigned to domain | ORDTYP_KK | |||
FIKEY | Reconciliation Key for General Ledger | FIKEY_KK | CHAR | 12 | Assigned to domain | FIKEY_KK | FKFI1 | ||
APPLK | Application area | APPLK_KK | CHAR | 1 | APPLK_KK | ||||
DOC_DATE | Document Date in Document | BLDAT | DATS | 8 | DATUM | ||||
OPBEL | Number of Contract Accts Rec. & Payable Doc. | OPBEL_KK | CHAR | 12 | Assigned to domain | ALPHA | OPBEL_KK | 80B | |
POST_DATE | Posting Date in the Document | BUDAT_KK | DATS | 8 | DATUM | ||||
BLART | Document Type | BLART | CHAR | 2 | Assigned to domain | BLART | BAR | ||
APPROVED | Approved | APPROVED_KK | CHAR | 1 | APPROVED_KK | ||||
CURRENCY | Transaction Currency | BLWAE_KK | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
TRANS_DATE | Translation Date | WWERT_D | DATS | 8 | DATUM | ||||
REVID | Request Status | REVID_KK | CHAR | 1 | REVID_KK | ||||
REVERSEDNR | Number of Transferred Request | REVERSEDNR_KK | CHAR | 12 | REVERSEDNR_KK | ||||
REVERSALNR | Number of Transfer Request | REVERSALNR_KK | CHAR | 12 | REVERSALNR_KK | ||||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
CPUDT | Day On Which Accounting Document Was Entered | CPUDT | DATS | 8 | DATUM | ||||
CPUTM | Time of Entry | CPUTM | TIMS | 6 | UZEIT | ||||
REFDOCNR | Reference document number | XBLNR_KK | CHAR | 16 | ALPHA | XBLNR_KK | |||
AWTYP | Reference Transaction | AWTYP | CHAR | 5 | Assigned to domain | AWTYP | |||
AWKEY | Reference Key | AWKEY | CHAR | 20 | AWKEY | ||||
AWSYS | Logical system of source document | AWSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
AENAM | Name of Person Responsible for Changing Object | AENAM_REQ_KK | CHAR | 12 | USNAM | ||||
AEDAT | Date of Last Change | AEDAT_KK | DATS | 8 | DATUM | ||||
AETIM | Time at Which the Object Was Last Changed | AETIM_KK | TIMS | 6 | UZEIT | ||||
XMULTIDOC | Generate Document for each Request Item | XMULTIDOC_KK | CHAR | 1 | XFELD | ||||
NO_DIALOG | External Call Without Dialog | X_NO_DIALOG_KK | CHAR | 1 | XFELD | ||||
REVID_NEXT | Request Status | REVID_KK | CHAR | 1 | REVID_KK | ||||
WNPER | Requested Special Period for Transfer to General Ledger | WNPER_KK | NUMC | 2 | MONAT | ||||
KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
Key field | Non-key field |
How do I retrieve data from SAP structure VDFKKORDER using ABAP code?
As VDFKKORDER 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 VDFKKORDER as there is no data to select.How to access SAP table VDFKKORDER
Within an ECC or HANA version of SAP you can also view further information about VDFKKORDER 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