SAP E1CSKTM Master cost center texts (CSKT) Table data and field list

E1CSKTM is a standard SAP Structure which is used to define the field attributes of IDoc segment E1CSKTM. The segment is used within the below IDoc to send Master cost center texts (CSKT) information via the IDoc send process

COSMAS01

Below is the standard documentation available and a few details of the fields which make up this IDoc segment structure. To view further details checkout the IDoc links above or use relevant transactions such as WE30(IDoc development), WE31 (segment development)...Also check here for more IDoc related development help, or you can obviously also use standard dictionary object dev tcodes such as SE11, SE80 etc...

E1CSKTM idoc segment structure Technical Details:

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced


SAP E1CSKTM idoc segment structure fields - Full list of fields found in SAP data dictionary

Looking for S/4HANA specific information? Click here to explore the details, fields and extensibility available for this table in the SAP S/4HANA version of the E1CSKTM table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.
Field Description Data Element Data Type length (Dec) Check table Conversion Routine Domain Name MemoryID SHLP
MSGFNFunction MSGFNCHAR3MSGFN
SPRASCharacter field of length 1 CHAR_LG_01CHAR1CHAR_LG_01
KTEXTGeneral Name KTEXTCHAR20TEXT20
LTEXTDescription KLTXTCHAR40TEXT40
SPRAS_ISO 0

Key field Non-key field



How do I retrieve data from SAP structure E1CSKTM using ABAP code?

As E1CSKTM 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 E1CSKTM as there is no data to select.

How to access SAP table E1CSKTM

Within an ECC or HANA version of SAP you can also view further information about E1CSKTM and the data within it using relevant transactions such as

SE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).