CEKKO SAP (Communication Release Strategy Determination Purch. Document) Structure details
Description: Communication Release Strategy Determination Purch. Document
Structure field list including key, data, relationships and ABAP select examples
CEKKO 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 "Communication Release Strategy Determination Purch. Document" 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_CEKKO TYPE CEKKO.
The CEKKO table consists of various fields, each holding specific information or linking keys about Communication Release Strategy Determination Purch. Document data available in SAP. These include BSTYP (Purchasing Document Category), BSART (Order Type (Purchasing)), BSAKZ (Control indicator for purchasing document type), LIFNR (Vendor Account Number).. 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 CEKKO 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 |
BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
BSTYP | Purchasing Document Category | BSTYP | CHAR | 1 | BSTYP | ||||
BSART | Order Type (Purchasing) | BSART | CHAR | 4 | Assigned to domain | BSART | BSA | ||
BSAKZ | Control indicator for purchasing document type | BSAKZ | CHAR | 1 | BSAKZ | ||||
LIFNR | Vendor Account Number | ELIFN | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
SPRAS | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
EKGRP | Purchasing Group | BKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
BEDAT | Purchase Order Date | BEDAT | DATS | 8 | DATUM | ||||
LLIEF | Supplying Vendor | LLIEF | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LLI | |
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
RESWK | Supplying (Issuing) Plant in Stock Transport Order | RESWK | CHAR | 4 | Assigned to domain | WERKS | |||
LBLIF | Field not used | LBLIF | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | |
INCO1 | Incoterms (Part 1) | INCO1 | CHAR | 3 | Assigned to domain | INCO1 | |||
KTWRT | Target Value for Header Area per Distribution | KTWRT | CURR | 15(2) | WERT15 | ||||
LIFRE | Different Invoicing Party | LIFRE | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LRE | |
WERKS | Plant | EWERK | CHAR | 4 | Assigned to domain | WERKS | WRK | ||
MATKL | Material Group | MATKL | CHAR | 9 | Assigned to domain | MATKL | MKL | S_WBWG | |
LTSNR | Vendor Subrange | LTSNR | CHAR | 6 | Assigned to domain | LTSNR | |||
USRC1 | User field format character for release strategy | USRC1 | CHAR | 20 | CHAR20 | ||||
USRC2 | User field format character for release strategy | USRC1 | CHAR | 20 | CHAR20 | ||||
USRN1 | User field numeric for release strategy | USRN1 | NUMC | 10 | NUM10 | ||||
USRN2 | User field numeric for release strategy | USRN1 | NUMC | 10 | NUM10 | ||||
GNETW | Total net order value | GNETW | CURR | 15(2) | WERT15 | ||||
SUBMI | Collective Number | SUBMI | CHAR | 10 | CHAR10 | ||||
MEMORY | Purchase order not yet complete | MEMER | CHAR | 1 | XFELD | ||||
KONNR | Number of Principal Purchase Agreement | KONNR | CHAR | 10 | Assigned to domain | ALPHA | EBELN | KTR | |
REVNO | Version number in Purchasing | REVNO | CHAR | 8 | ALPHA | REVNO | |||
PDUMMY | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY |
Key field | Non-key field |
How do I retrieve data from SAP structure CEKKO using ABAP code?
As CEKKO 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 CEKKO as there is no data to select.How to access SAP table CEKKO
Within an ECC or HANA version of SAP you can also view further information about CEKKO 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