TP_CHECK_TICKET_ELEMENT SAP Function module

TP_CHECK_TICKET_ELEMENT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name TP_CHECK_TICKET_ELEMENT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FITP_GEN
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM TP_CHECK_TICKET_ELEMENT - TP CHECK TICKET ELEMENT

CALL FUNCTION 'TP_CHECK_TICKET_ELEMENT' "
  EXPORTING
    provider =                  " ta20ba-res_system  Context
    variant =                   " ftpt_variant  Travel Plan Variant
    variant_status =            " ftpt_variant-status  Variant Status
  IMPORTING
    ticket_element =            " char1
  EXCEPTIONS
    INVALID_SYSTEM = 1          "
    INVALID_CONTEXT = 2         "               Invalid context
    CONNECTION_ERROR = 3        "
    .  "  TP_CHECK_TICKET_ELEMENT

ABAP code example for Function Module TP_CHECK_TICKET_ELEMENT

The ABAP code below is a full code listing to execute function module TP_CHECK_TICKET_ELEMENT including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_ticket_element  
 
 TYPE CHAR1
.

 

SELECT single RES_SYSTEM 
  FROM TA20BA 
  INTO @DATA(ld_provider).


DATA(ld_variant) = 'Check type of data required'.
 

SELECT single STATUS 
  FROM FTPT_VARIANT 
  INTO @DATA(ld_variant_status).

.

CALL FUNCTION 'TP_CHECK_TICKET_ELEMENT'
  EXPORTING
    provider =                   ld_provider
    variant =                    ld_variant
    variant_status =             ld_variant_status
  IMPORTING
    ticket_element =             ld_ticket_element
  EXCEPTIONS
    INVALID_SYSTEM =             1
    INVALID_CONTEXT =            2
    CONNECTION_ERROR =           3
    .  "  TP_CHECK_TICKET_ELEMENT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ticket_element
 
 TYPE CHAR1 ,
ld_provider
 
 TYPE TA20BA-RES_SYSTEM ,
ld_variant
 
 TYPE FTPT_VARIANT ,
ld_variant_status
 
 TYPE FTPT_VARIANT-STATUS .



SELECT single RES_SYSTEM 
  FROM TA20BA 
  INTO ld_provider.

ld_variant = 'Check type of data required'.

SELECT single STATUS 
  FROM FTPT_VARIANT 
  INTO ld_variant_status.