SAP SRT_SEQ_DELETE_BGRFC_QUEUES Function Module for delete bgrfc queues remotely









SRT_SEQ_DELETE_BGRFC_QUEUES is a standard srt seq delete bgrfc queues SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for delete bgrfc queues remotely processing and below is the pattern details for this FM, 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 srt seq delete bgrfc queues FM, simply by entering the name SRT_SEQ_DELETE_BGRFC_QUEUES into the relevant SAP transaction such as SE37 or SE38.

Function Group: SRT_SOAP_SEQUENCE_REORG
Program Name: SAPLSRT_SOAP_SEQUENCE_REORG
Main Program: SAPLSRT_SOAP_SEQUENCE_REORG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SRT_SEQ_DELETE_BGRFC_QUEUES 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 'SRT_SEQ_DELETE_BGRFC_QUEUES'"delete bgrfc queues remotely
TABLES
QUEUES = "bgrfc queues that can be deleted because of seq termination

EXCEPTIONS
BGRFC_MONITOR_API_AUTHORITY = 1 BGRFC_MONITOR_API = 2 BGRFC_INVALID_DESTINATION = 3
.



TABLES Parameters details for SRT_SEQ_DELETE_BGRFC_QUEUES

QUEUES - bgrfc queues that can be deleted because of seq termination

Data type: SRT_T_SEQ_DEL_QUE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

BGRFC_MONITOR_API_AUTHORITY - Missing authority for bgRFC queue manipulations

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

BGRFC_MONITOR_API - Emply queue list

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

BGRFC_INVALID_DESTINATION - Invalid destination

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

Copy and paste ABAP code example for SRT_SEQ_DELETE_BGRFC_QUEUES 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_queues  TYPE STANDARD TABLE OF SRT_T_SEQ_DEL_QUE, "   
lv_bgrfc_monitor_api_authority  TYPE SRT_T_SEQ_DEL_QUE, "   
lv_bgrfc_monitor_api  TYPE SRT_T_SEQ_DEL_QUE, "   
lv_bgrfc_invalid_destination  TYPE SRT_T_SEQ_DEL_QUE. "   

  CALL FUNCTION 'SRT_SEQ_DELETE_BGRFC_QUEUES'  "delete bgrfc queues remotely
    TABLES
         QUEUES = lt_queues
    EXCEPTIONS
        BGRFC_MONITOR_API_AUTHORITY = 1
        BGRFC_MONITOR_API = 2
        BGRFC_INVALID_DESTINATION = 3
. " SRT_SEQ_DELETE_BGRFC_QUEUES




ABAP code using 7.40 inline data declarations to call FM SRT_SEQ_DELETE_BGRFC_QUEUES

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



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!