CKBLK_USER 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
CKBLK_USER 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_CKBLK_USER TYPE CKBLK_USER.
The CKBLK_USER 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), DOCCLASS (Document class for table KBLK_USER), BUKRS (Company Code), BELNR (Document number for KBLK_USER).. 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 CKBLK_USER 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 | |||
DOCCLASS | Document class for table KBLK_USER | KBLKUSERCL | CHAR | 4 | KBLKUSERCL | ||||
BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
BELNR | Document number for KBLK_USER | KBLKUSERDO | CHAR | 10 | Assigned to domain | ALPHA | KBLKUSERDO | ||
GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
.INCLU--AP | 0 | ||||||||
LOCSYS | Specification from local system | LOCSYS | CHAR | 20 | CHAR20 | ||||
LOCSYSNSIC | Local non-SIC system | LOCSYSNSIC | CHAR | 20 | CHAR20 | ||||
PAYSC | Link to payment plan | PAYSC | CHAR | 10 | CHAR10 | ||||
FDUDT | Last payment due date | FDUDT | DATS | 8 | DATUM | ||||
BUDEX | Commitment budget overruns permitted | BUDEX | CHAR | 1 | CHAR1 | ||||
ONACCKZ | Partial payment number required for reduction | ONACCKZ | CHAR | 1 | CHAR1_X | ||||
ATEXT1 | Additional reference | ATEXT1 | CHAR | 50 | TEXT50 | ||||
REFAO | User reference | REFAO | CHAR | 20 | CHAR20 | ||||
PERSCH | Person responsible | PERSCH | CHAR | 12 | USNAM | ||||
LOCMANAG | Person responsible locally | FMLOCMANAG | CHAR | 12 | USNAM | ||||
GROUPNR | Group key | GROUPNR | CHAR | 10 | CHAR10 | ||||
VERSION | Version | FMEUVERS | CHAR | 10 | CHAR10 | ||||
CONTKZ | Contract signed | CONTKZ | CHAR | 1 | CHAR1 | ||||
CONTDAT | Contract signed on: | CONTDAT | DATS | 8 | DATUM | ||||
CONTREG | Contract entered on: | CONTREG | DATS | 8 | DATUM | ||||
PERSARC | Person responsible for accompanying documents | PERSARC | CHAR | 12 | USNAM | ||||
INVCNR | Reference to invoice number | INVCNR | CHAR | 25 | TEXT25 | ||||
INVCDT | Invoice reference: date | INVCDT | DATS | 8 | DATUM | ||||
INVCLC | Invoice reference: location | INVCLOC | CHAR | 25 | TEXT25 | ||||
PURONR | Reference to purchase order | PURONR | CHAR | 25 | TEXT25 | ||||
PURODT | Purchase order reference: date | PURODT | DATS | 8 | DATUM | ||||
PUROLC | Purchase order reference: location | PUROLOC | CHAR | 25 | TEXT25 | ||||
CONTNR | Reference to contract | CONTNR | CHAR | 25 | TEXT25 | ||||
CONTDT | Contract ref.: Date | CONTDT | DATS | 8 | DATUM | ||||
CONTLC | Contract ref.: Location | CONTLOC | CHAR | 25 | TEXT25 | ||||
DEMNR | Reference to contract change | DEMNR | CHAR | 25 | TEXT25 | ||||
DEMDT | Contract changed on: | DEMDT | DATS | 8 | DATUM | ||||
DEMLC | Contract change: Location | DEMLOC | CHAR | 25 | TEXT25 | ||||
FREPNR | Reference to closing check | FREPNR | CHAR | 25 | TEXT25 | ||||
FREPDT | Closing check: date | FREPDT | DATS | 8 | DATUM | ||||
FREPLC | Closing check: location | FREPLOC | CHAR | 25 | TEXT25 | ||||
REGLNR | Reference to rule | REGLNR | CHAR | 25 | TEXT25 | ||||
REGLDT | Rule: date | REGLDT | DATS | 8 | DATUM | ||||
REGLLC | Rule: location | REGLLOC | CHAR | 25 | TEXT25 | ||||
AVISNR | Reference to expert opinion | AVISNR | CHAR | 25 | TEXT25 | ||||
AVISDT | Opinion: Date | AVISDT | DATS | 8 | DATUM | ||||
AVISLC | Opinion: Location | AVISLOC | CHAR | 25 | TEXT25 | ||||
OTHERNR | Reference to further data 1 | OTHERNR1 | CHAR | 25 | TEXT25 | ||||
OTHERDT | Further data 1: date | OTHERDT1 | DATS | 8 | DATUM | ||||
OTHERLC | Further data 1: location | OTHERLOC1 | CHAR | 25 | TEXT25 | ||||
OTHERNR2 | Reference to further data 2 | OTHERNR2 | CHAR | 25 | TEXT25 | ||||
OTHERDT2 | Further data 2: date | OTHERDT2 | DATS | 8 | DATUM | ||||
OTHERLC2 | Further data 2: location | OTHERLOC2 | CHAR | 25 | TEXT25 | ||||
CHANGINVOI | Reason for changing baseline date for payment in invoice | CHANGINVOI | CHAR | 80 | TEXT80 | ||||
XBRIEF | Accompanying letter required | PRQ_XBRIEF | CHAR | 1 | X | ||||
XPAPER | Paper printout required | PRQ_XPAPER | CHAR | 1 | X | ||||
GEST_GRP | User Group | PRQ_GRP | CHAR | 5 | CHAR5 | ||||
HBKID | Short Key for a House Bank | HBKID | CHAR | 5 | Assigned to domain | HBKID | |||
HKTID | ID for account details | HKTID | CHAR | 5 | Assigned to domain | HKTID | |||
REASON | Reason for transaction | FMPRREASON | CHAR | 240 | TEXT240 | ||||
KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
Key field | Non-key field |
How do I retrieve data from SAP structure CKBLK_USER using ABAP code?
As CKBLK_USER 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 CKBLK_USER as there is no data to select.How to access SAP table CKBLK_USER
Within an ECC or HANA version of SAP you can also view further information about CKBLK_USER 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