SAP CRM_GET_QUEUENAME Function Module for

Search SAP Function Modules

CRM_GET_QUEUENAME is a standard crm get queuename 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 crm get queuename FM, simply by entering the name CRM_GET_QUEUENAME into the relevant SAP transaction such as SE37 or SE38.

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

Function CRM_GET_QUEUENAME 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 'CRM_GET_QUEUENAME'"
  EXPORTING
   I_OBJNAME =  "
   I_DWNLOADTYPE =  "
*  I_RFC_QUEUE =  "
*  I_CONSUMER =  "
*  I_BAPICRMDH2 =  "
*  I_MASS_QUEUE =  "
*  I_TRANSFER_DATA =  "
*  I_STSHD =  "

 IMPORTING
   O_Q_OUT_NAME_COMPLETE =  "
   O_Q_OUT_QNAME_ONLY_OBJECT_PRT =  "
   O_Q_IN_NAME_COMPLETE =  "
   O_Q_IN_QNAME_ONLY_OBJECT_PRT =  "
   O_MASS_QUEUE =  "

TABLES
*  TI_BAPIMTCS =  "
*  O_Q_OUT_QNAME_ONLY_OBJ_PRT_TAB =  "
*  O_Q_IN_QNAME_ONLY_OBJ_PRT_TAB =  "

.

IMPORTING Parameters details for CRM_GET_QUEUENAME

I_OBJNAME -

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

I_DWNLOADTYPE -

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

I_RFC_QUEUE -

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

I_CONSUMER -

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

I_BAPICRMDH2 -

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

I_MASS_QUEUE -

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

I_TRANSFER_DATA -

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

I_STSHD -

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

EXPORTING Parameters details for CRM_GET_QUEUENAME

O_Q_OUT_NAME_COMPLETE -

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

O_Q_OUT_QNAME_ONLY_OBJECT_PRT -

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

O_Q_IN_NAME_COMPLETE -

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

O_Q_IN_QNAME_ONLY_OBJECT_PRT -

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

O_MASS_QUEUE -

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

TABLES Parameters details for CRM_GET_QUEUENAME

TI_BAPIMTCS -

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

O_Q_OUT_QNAME_ONLY_OBJ_PRT_TAB -

Data type: CRMQNAM_TAB
Optional: Yes
Call by Reference: Yes

O_Q_IN_QNAME_ONLY_OBJ_PRT_TAB -

Data type: CRMQNAM_TAB
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for CRM_GET_QUEUENAME 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.

ABAP code using 7.40 inline data declarations to call FM CRM_GET_QUEUENAME

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.

Search for further information about these or an SAP related objects