SCI_DYSO SAP (Code Inspector: Structure for Screen) Structure details
Description: Code Inspector: Structure for Screen
Structure field list including key, data, relationships and ABAP select examples
SCI_DYSO 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 "Code Inspector: Structure for Screen" 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_SCI_DYSO TYPE SCI_DYSO.
The SCI_DYSO table consists of various fields, each holding specific information or linking keys about Code Inspector: Structure for Screen data available in SAP. These include O_TADIR_C (Software Component), O_TADIR_T (Transport Layer in ABAP Workbench), O_TADIR_P (Package), O_TADIR_S (Original System of Object).. 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 SCI_DYSO 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 |
O_TADIR_A | Application component ID | UFPS_POSID | CHAR | 24 | UFPS_POSID | ||||
O_TADIR_C | Software Component | DLVUNIT | CHAR | 30 | Assigned to domain | DLVUNIT | H_CVERS | ||
O_TADIR_T | Transport Layer in ABAP Workbench | DEVLAYER | CHAR | 4 | DEVLAYER | TCE_TRANSPORT_LAYERS | |||
O_TADIR_P | Package | DEVCLASS | CHAR | 30 | Assigned to domain | DEVCLASS | DVC | DEVCLASS | |
O_TADIR_S | Original System of Object | SRCSYSTEM | CHAR | 10 | SYSNAME | ||||
O_TADIR_R | Person Responsible for a Repository Object | RESPONSIBL | CHAR | 12 | AS4USER | USER_ADDR | |||
O_TA_1 | Object Name in Object Directory | SOBJ_NAME | CHAR | 40 | SOBJ_NAME | ||||
O_TA_2 | Object Name in Object Directory | SOBJ_NAME | CHAR | 40 | SOBJ_NAME | ||||
O_PRG_N | ABAP Program Name | PROGRAMM | CHAR | 40 | Assigned to domain | PROGRAMM | RID | ||
O_PRG_T | Program type | SUBC | CHAR | 1 | SUBC | ||||
O_PRG_S | Status | RDIR_RSTAT | CHAR | 1 | RSTAT | ||||
O_PRG_A | Author | CNAM | CHAR | 12 | SYCHAR12 | ||||
O_CLAS | Object Type Name | SEOCLSNAME | CHAR | 30 | SEOCLSNAME | CLASS | |||
O_FUGR | Function group, to which the function module belongs | RS38L_AREA | CHAR | 26 | Assigned to domain | AREA | |||
O_REPO | Program/Transaction in SQL Trace Evaluation | SCI_REPO | CHAR | 40 | Assigned to domain | PROGRAMM | RID | ||
O_WDYN | Web Dynpro: Component Name | WDY_COMPONENT_NAME | CHAR | 30 | WD_COMPONENT | ||||
O_DDIC | Code Inspector: Dictionary Type | SCI_DDIC | CHAR | 30 | TABNAME | ||||
O_DDTY | Type Group | TYPEGROUP | CHAR | 5 | TYPEGROUP | DOB | |||
F_OBJT | Code Inspektor: Copy of TROBJTYPE (R3TR Only) | SCI_TROBJ | CHAR | 4 | OBJECT | SCI_TROBJ | |||
F_OBJ | Object Name in Object Directory | SOBJ_NAME | CHAR | 40 | SOBJ_NAME | ||||
F_DEVC | Package | DEVCLASS | CHAR | 30 | Assigned to domain | DEVCLASS | DVC | DEVCLASS | |
F_RESP | Person Responsible for a Repository Object | RESPONSIBL | CHAR | 12 | AS4USER | USER_ADDR | |||
F_ERRTY | Code Inspector: Message Type (Info, Warning, ...)) | SCI_ERRTY | CHAR | 1 | SCI_ERRTY | ||||
F_ERRC | Code Inspector: ID for Message Code | SCI_ERRC | CHAR | 10 | CHAR10 |
Key field | Non-key field |
How do I retrieve data from SAP structure SCI_DYSO using ABAP code?
As SCI_DYSO 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 SCI_DYSO as there is no data to select.How to access SAP table SCI_DYSO
Within an ECC or HANA version of SAP you can also view further information about SCI_DYSO 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