SXPCKLSTI1 SAP (SAPconnect: RFC - packet list) Structure details
Description: SAPconnect: RFC - packet list
Structure field list including key, data, relationships and ABAP select examples
SXPCKLSTI1 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 "SAPconnect: RFC - packet list" 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_SXPCKLSTI1 TYPE SXPCKLSTI1.
The SXPCKLSTI1 table consists of various fields, each holding specific information or linking keys about SAPconnect: RFC - packet list data available in SAP. These include TRANSF_BIN (Flag for indicating an obj. to be transported in binary form), HEAD_START (Start line of object header in transport packet), HEAD_NUM (Number of lines of an object header in object packet), BODY_START (Start line of object contents in an object packet).. 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: Not classified
SAP SXPCKLSTI1 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 |
TRANSF_BIN | Flag for indicating an obj. to be transported in binary form | SO_TRANBIN | CHAR | 1 | SO_FLAG | ||||
HEAD_START | Start line of object header in transport packet | SO_HD_STRT | NUMC | 15 | SO_PCKLINE | ||||
HEAD_NUM | Number of lines of an object header in object packet | SO_HD_NUM | NUMC | 15 | SO_PCKLINE | ||||
BODY_START | Start line of object contents in an object packet | SO_BD_STRT | NUMC | 15 | SO_PCKLINE | ||||
BODY_NUM | Number of lines of the object contents in an object packet | SO_BD_NUM | NUMC | 15 | SO_PCKLINE | ||||
DOC_TYPE | Code for document class | SO_OBJ_TP | CHAR | 3 | Assigned to domain | SO_OBJ_TP | |||
OBJ_NAME | Name of document, folder or distribution list | SO_OBJ_NAM | CHAR | 12 | SO_OBJ_NAM | ||||
OBJ_DESCR | Short description of contents | SO_OBJ_DES | CHAR | 50 | SO_OBJ_DES | ||||
OBJ_LANGU | Language in Which Document Is Created | SO_OBJ_LA | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
DOC_SIZE | Size of SAPoffice Document (for API1) | SO_DOC_SIZ | CHAR | 12 | SO_DOC_SIZ | ||||
MESS_TYPE | Type of message | SO_MESS_TP | CHAR | 4 | CHAR4 | ||||
ISO_LANGU | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO |
Key field | Non-key field |
How do I retrieve data from SAP structure SXPCKLSTI1 using ABAP code?
As SXPCKLSTI1 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 SXPCKLSTI1 as there is no data to select.How to access SAP table SXPCKLSTI1
Within an ECC or HANA version of SAP you can also view further information about SXPCKLSTI1 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