ROS_CAND SAP (Itinerary Candidates) Structure details

Search SAP tables

Structure field list including key, data, relationships and ABAP select examples

ROS_CAND 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 "Itinerary Candidates" 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_ROS_CAND TYPE ROS_CAND.

The ROS_CAND table consists of various fields, each holding specific information or linking keys about Itinerary Candidates data available in SAP. These include GIDATE (Field of type DATS), GITIME (Field of type TIMS), DEDATE (Field of type DATS), DETIME (Field of type TIMS).. 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 ROS_CAND structure fields - Full list of fields found in SAP data dictionary

Key field

Non-key field

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

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

How to access SAP table ROS_CAND

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

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

Search for further information about these or an SAP related objects