TP_1A_GET_QUEUE_COUNT SAP Function module

TP_1A_GET_QUEUE_COUNT 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_1A_GET_QUEUE_COUNT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM TP_1A_GET_QUEUE_COUNT - TP 1A GET QUEUE COUNT

CALL FUNCTION 'TP_1A_GET_QUEUE_COUNT' "
  EXPORTING
    variant =                   " ftpt_variant-variant  Plan Variant Number (Sequential Number)
    office_id =                 " ftps_api-office_id  Sales office code
    queue_number =              " ftps_api-int2
    queue_category =            " ftps_api-int2
  IMPORTING
    pnr_counter =               " ftps_api-int2
  EXCEPTIONS
    NO_DESTINATION = 1          "
    INVALID_VARIANT = 2         "
    CONNECTION_ERROR = 3        "
    RFC_ERROR = 4               "
    APPLICATION_API_ERROR = 5   "
    GENERAL_API_ERROR = 6       "
    .  "  TP_1A_GET_QUEUE_COUNT

ABAP code example for Function Module TP_1A_GET_QUEUE_COUNT

The ABAP code below is a full code listing to execute function module TP_1A_GET_QUEUE_COUNT 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_pnr_counter  
 
 TYPE FTPS_API-INT2
.

 

SELECT single VARIANT 
  FROM FTPT_VARIANT 
  INTO @DATA(ld_variant).



DATA(ld_office_id) = some text here


DATA(ld_queue_number) = 123 


DATA(ld_queue_category) = 123 
.

CALL FUNCTION 'TP_1A_GET_QUEUE_COUNT'
  EXPORTING
    variant =                    ld_variant
    office_id =                  ld_office_id
    queue_number =               ld_queue_number
    queue_category =             ld_queue_category
  IMPORTING
    pnr_counter =                ld_pnr_counter
  EXCEPTIONS
    NO_DESTINATION =             1
    INVALID_VARIANT =            2
    CONNECTION_ERROR =           3
    RFC_ERROR =                  4
    APPLICATION_API_ERROR =      5
    GENERAL_API_ERROR =          6
    .  "  TP_1A_GET_QUEUE_COUNT

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
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "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_pnr_counter
 
 TYPE FTPS_API-INT2 ,
ld_variant
 
 TYPE FTPT_VARIANT-VARIANT ,
ld_office_id
 
 TYPE FTPS_API-OFFICE_ID ,
ld_queue_number
 
 TYPE FTPS_API-INT2 ,
ld_queue_category
 
 TYPE FTPS_API-INT2 .



SELECT single VARIANT 
  FROM FTPT_VARIANT 
  INTO ld_variant.


ld_office_id = some text here

ld_queue_number = 123 

ld_queue_category = 123