SAP RSC1_TRFC_QUEUE_GET_CALLIDS Function Module for









RSC1_TRFC_QUEUE_GET_CALLIDS is a standard rsc1 trfc queue get callids SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for rsc1 trfc queue get callids FM, simply by entering the name RSC1_TRFC_QUEUE_GET_CALLIDS into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSC1
Program Name: SAPLRSC1
Main Program: SAPLRSC1
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RSC1_TRFC_QUEUE_GET_CALLIDS pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'RSC1_TRFC_QUEUE_GET_CALLIDS'"
EXPORTING
I_OLTPSOURCE = "

TABLES
* E_T_CALLID = "

EXCEPTIONS
NAME_TOO_LONG = 1
.



IMPORTING Parameters details for RSC1_TRFC_QUEUE_GET_CALLIDS

I_OLTPSOURCE -

Data type: ROOSOURCE-OLTPSOURCE
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RSC1_TRFC_QUEUE_GET_CALLIDS

E_T_CALLID -

Data type: ARFCCALLID
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NAME_TOO_LONG -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RSC1_TRFC_QUEUE_GET_CALLIDS Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lt_e_t_callid  TYPE STANDARD TABLE OF ARFCCALLID, "   
lv_i_oltpsource  TYPE ROOSOURCE-OLTPSOURCE, "   
lv_name_too_long  TYPE ROOSOURCE. "   

  CALL FUNCTION 'RSC1_TRFC_QUEUE_GET_CALLIDS'  "
    EXPORTING
         I_OLTPSOURCE = lv_i_oltpsource
    TABLES
         E_T_CALLID = lt_e_t_callid
    EXCEPTIONS
        NAME_TOO_LONG = 1
. " RSC1_TRFC_QUEUE_GET_CALLIDS




ABAP code using 7.40 inline data declarations to call FM RSC1_TRFC_QUEUE_GET_CALLIDS

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single OLTPSOURCE FROM ROOSOURCE INTO @DATA(ld_i_oltpsource).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!