TSQACCESS_INPUT SAP (Proxy Structure (generated)) Structure details
Description: Proxy Structure (generated)
Related tables to TSQACCESS_INPUT
Access table TSQACCESS_INPUT
Structure field list including key, data, relationships and ABAP select examples
TSQACCESS_INPUT 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 "Proxy Structure (generated)" 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_TSQACCESS_INPUT TYPE TSQACCESS_INPUT.
The TSQACCESS_INPUT table consists of various fields, each holding specific information or linking keys about Proxy Structure (generated) data available in SAP. These include POS (), CONTROLLER (), SOURCE (), CONTROLLER ().. 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 (Deep)
SAP TSQACCESS_INPUT 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 |
CONTROLLER | 0 | ||||||||
POS | 0 | ||||||||
CONTROLLER | 0 | ||||||||
SOURCE | 0 | ||||||||
CONTROLLER | 0 | ||||||||
REQUESTOR_ID | 0 | ||||||||
CONTROLLER | 0 | ||||||||
COMPANY_NAME | 0 | ||||||||
CONTROLLER | 0 | ||||||||
COMPANY_SHORT_NAME | 0 | ||||||||
TRAVEL_SECTOR | 0 | ||||||||
CODE | 0 | ||||||||
CODE_CONTEXT | Identifies the context of the identifying code, | 0 | |||||||
CONTENT | 0 | ||||||||
URL | URL that identifies the location associated with the record | 0 | |||||||
TYPE | The type of booking channel (e.g. Global Distribution System | 0 | |||||||
INSTANCE | The identification of a record as it exists at a point in ti | 0 | |||||||
ID | A unique identifying value assigned by the creating system. | 0 | |||||||
ID_CONTEXT | Used to identify the source of the identifier (e.g. IATA, AB | 0 | |||||||
POSITION | 0 | ||||||||
CONTROLLER | 0 | ||||||||
LATITUDE | 0 | ||||||||
LONGITUDE | 0 | ||||||||
ALTITUDE | 0 | ||||||||
BOOKING_CHANNEL | 0 | ||||||||
CONTROLLER | 0 | ||||||||
COMPANY_NAME | 0 | ||||||||
CONTROLLER | 0 | ||||||||
COMPANY_SHORT_NAME | 0 | ||||||||
TRAVEL_SECTOR | 0 | ||||||||
CODE | 0 | ||||||||
CODE_CONTEXT | Identifies the context of the identifying code, | 0 | |||||||
CONTENT | 0 | ||||||||
TYPE | The type of booking channel (e.g. Global Distribution System | 0 | |||||||
PRIMARY | XSD Truth Value: True/False [ext.] | XSDBOOLEAN | CHAR | 1 | XSDBOOLEAN | ||||
AGENT_SINE | Identifies the party within the requesting entity. | 0 | |||||||
PSEUDO_CITY_CODE | An identification code assigned to an office/agency by a res | 0 | |||||||
ISOCOUNTRY | The country code of the requesting party. | 0 | |||||||
ISOCURRENCY | The currency code in which the reservation will be ticketed. | 0 | |||||||
AGENT_DUTY_CODE | An authority code assigned to a requestor. | 0 | |||||||
AIRLINE_VENDOR_ID | The IATA assigned airline code. | 0 | |||||||
AIRPORT_CODE | The IATA assigned airport code. | 0 | |||||||
FIRST_DEPART_POINT | The point of first departure in a trip. | 0 | |||||||
ERSP_USER_ID | Electronic Reservation Service Provider (ERSP) assigned iden | 0 | |||||||
TPA_EXTENSIONS | 0 | ||||||||
CONTROLLER | 0 | ||||||||
MESSAGING_DETAILS | 0 | ||||||||
CONTROLLER | 0 | ||||||||
MDRSUBSET | 0 | ||||||||
CONTROLLER | 0 | ||||||||
CODE | 0 | ||||||||
QUEUE_IDENTIFIER | 0 | ||||||||
CONTROLLER | 0 | ||||||||
LIST | 0 | ||||||||
CONTROLLER | 0 | ||||||||
IND | XSD Truth Value: True/False [ext.] | XSDBOOLEAN | CHAR | 1 | XSDBOOLEAN | ||||
PSEUDO_CITY_CODE | An identification code assigned to an office/agency by a res | 0 | |||||||
NAME | 0 | ||||||||
NUMBER | 0 | ||||||||
NAVIGATION | 0 | ||||||||
CONTROLLER | 0 | ||||||||
DIRECTION | 0 | ||||||||
CONTROLLER | 0 | ||||||||
ACTION | 0 | ||||||||
PLUS | 0 | ||||||||
MINUS | 0 | ||||||||
ACTION | 0 | ||||||||
SELECTION1 | 0 | ||||||||
CONTROLLER | 0 | ||||||||
FUNCTION | 0 | ||||||||
CRITERIA | 0 | ||||||||
ECHO_TOKEN | A sequence number for additional message identification, ass | 0 | |||||||
TIME_STAMP | Indicates the creation date and time of the message in UTC u | 0 | |||||||
TARGET | Used to indicate whether the request is for the Test or Prod | 0 | |||||||
VERSION | For all OTA versioned messages, the version of the message i | 0 | |||||||
SEQUENCE_NMBR | Used to identify the sequence number of the transaction as a | 0 | |||||||
PRIMARY_LANG_ID | Identifes the primary language preference for the form of tr | 0 | |||||||
ALT_LANG_ID | Identifes the primary language preference for the form of tr | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure TSQACCESS_INPUT using ABAP code?
As TSQACCESS_INPUT 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 TSQACCESS_INPUT as there is no data to select.How to access SAP table TSQACCESS_INPUT
Within an ECC or HANA version of SAP you can also view further information about TSQACCESS_INPUT 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