SAIRT_TSTIO_START SAP (Input/Output Fields for AI Runtime Test Environment) Structure details
Description: Input/Output Fields for AI Runtime Test Environment
Related tables to SAIRT_TSTIO_START
Access table SAIRT_TSTIO_START
Structure field list including key, data, relationships and ABAP select examples
SAIRT_TSTIO_START 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 "Input/Output Fields for AI Runtime Test Environment" 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_SAIRT_TSTIO_START TYPE SAIRT_TSTIO_START.
The SAIRT_TSTIO_START table consists of various fields, each holding specific information or linking keys about Input/Output Fields for AI Runtime Test Environment data available in SAP. These include S_LOCAL (AI Test: Local Process Flow), S_CONFIG (AI Test: Service Selection), S_PAYLOAD (XI: Test Transaction), S_PRXOUT (AI Test: Outbound Proxy).. 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 SAIRT_TSTIO_START 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 |
| S_XMS | AI Test: Process Flow Using XMS | SAIRT_XMS | CHAR | 1 | SYCHAR01 | ||||
| S_LOCAL | AI Test: Local Process Flow | SAIRT_LOCAL | CHAR | 1 | SYCHAR01 | ||||
| S_CONFIG | AI Test: Service Selection | SAIRT_CONFIG | CHAR | 1 | SYCHAR01 | ||||
| S_PAYLOAD | XI: Test Transaction | SAIRT_SNGSRV | CHAR | 1 | SYCHAR01 | ||||
| S_PRXOUT | AI Test: Outbound Proxy | SAIRT_PRXOUT | CHAR | 1 | SYCHAR01 | ||||
| S_PRXIN | AI Test: Inbound Processing | SAIRT_PRXIN | CHAR | 1 | SYCHAR01 | ||||
| S_ROUT | AI Test: Routing | SAIRT_ROUT | CHAR | 1 | SYCHAR01 | ||||
| S_MAPP | AI Test: Mapping | SAIRT_MAPP | CHAR | 1 | SYCHAR01 | ||||
| S_MAPP_MULT | Test Transaction: Multiple Mapping | SAIRT_MAPPMTP | CHAR | 1 | |||||
| S_PREP | AI Test: Service Selection | SAIRT_PREP | CHAR | 1 | SYCHAR01 | ||||
| S_PREROUT | AI Test: Service Selection | SAIRT_PREROUT | CHAR | 1 | SYCHAR01 | ||||
| S_PREROUT_OUT | AI Test: Service Selection | SAIRT_PREROUT | CHAR | 1 | SYCHAR01 | ||||
| S_XXML | Proxy Runtime: Standard/Extended Rendering and Parsing | PRX_XXML | CHAR | 1 | SYCHAR01 | ||||
| S_TECHROUT | CHAR01 data element for SYST | SYCHAR01 | CHAR | 1 | SYCHAR01 | ||||
| S_INTF | AI Test: Interface Determination | SAIRT_INFT | CHAR | 1 | SYCHAR01 | ||||
| S_PID_NORM | XI: Test Transaction, Party Normalization | SAIRT_PIDNORM | CHAR | 1 | SYCHAR01 | ||||
| S_PID_CHNG | Test Transaction: Party Identifier After Service | SAIRT_PIDCHNG | CHAR | 1 | |||||
| S_PID_EXT | XI: Test Transaction, External Party Identifier | SAIRT_PIDEXT | CHAR | 1 | SYCHAR01 | ||||
| S_PLD_INTF | XI: Display Test Transaction Interface Payload | SAIRT_PLDINTF | CHAR | 1 | SYCHAR01 | ||||
| S_PLD_FAULT | XI: Test Transaction | SAIRT_PLDFLT | CHAR | 1 | SYCHAR01 | ||||
| S_INBD_BDG | CHAR01 data element for SYST | SYCHAR01 | CHAR | 1 | SYCHAR01 |
| Key field | Non-key field |
How do I retrieve data from SAP structure SAIRT_TSTIO_START using ABAP code?
As SAIRT_TSTIO_START 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 SAIRT_TSTIO_START as there is no data to select.How to access SAP table SAIRT_TSTIO_START
Within an ECC or HANA version of SAP you can also view further information about SAIRT_TSTIO_START 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