SAP BCOM_R_SCENARIO_SET Function Module for









BCOM_R_SCENARIO_SET is a standard bcom r scenario set 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 bcom r scenario set FM, simply by entering the name BCOM_R_SCENARIO_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function BCOM_R_SCENARIO_SET 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 'BCOM_R_SCENARIO_SET'"
  EXPORTING
   SCENARIO_ID =  "Routing Scenario ID
   DESCRIPTION =  "SAPphone: Description
   VALID_FROM =  "Start of Validity Period of a Scenario
   VALID_UNTIL =  "End of Validity Period of a Scenario
   TIMESTAMP =  "
   DESTINATION_LIST =  "Table Type: Type (INT, FAX, TEL..) and Content of an Address
   ATTRIBUTE_LIST =  "Table Type: Routing Attribute with Priority
   RESPONSIBILITY_LIST =  "Table: Agent Group and Assigned Attribute Values
   SERVER =  "BCOM Routing Server

EXCEPTIONS
   SERVER_NOT_READY = 1    RFC_ERROR = 2
.



IMPORTING Parameters details for BCOM_R_SCENARIO_SET

SCENARIO_ID - Routing Scenario ID

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

DESCRIPTION - SAPphone: Description

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

VALID_FROM - Start of Validity Period of a Scenario

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

VALID_UNTIL - End of Validity Period of a Scenario

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

TIMESTAMP -

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

DESTINATION_LIST - Table Type: Type (INT, FAX, TEL..) and Content of an Address

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

ATTRIBUTE_LIST - Table Type: Routing Attribute with Priority

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

RESPONSIBILITY_LIST - Table: Agent Group and Assigned Attribute Values

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

SERVER - BCOM Routing Server

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

EXCEPTIONS details

SERVER_NOT_READY -

Data type:
Optional: No
Call by Reference: Yes

RFC_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BCOM_R_SCENARIO_SET 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:
lv_scenario_id  TYPE SR_SCNID, "   
lv_server_not_ready  TYPE SR_SCNID, "   
lv_rfc_error  TYPE SR_SCNID, "   
lv_description  TYPE SP_DESCRPT, "   
lv_valid_from  TYPE SR_VALFROM, "   
lv_valid_until  TYPE SR_VALTO, "   
lv_timestamp  TYPE SRTSK, "   
lv_destination_list  TYPE SRADDRESST, "   
lv_attribute_list  TYPE SRATTRIBT, "   
lv_responsibility_list  TYPE SRAGPRSPT, "   
lv_server  TYPE CL_BCOM_R_SERVER. "   

  CALL FUNCTION 'BCOM_R_SCENARIO_SET'  "
    EXPORTING
         SCENARIO_ID = lv_scenario_id
         DESCRIPTION = lv_description
         VALID_FROM = lv_valid_from
         VALID_UNTIL = lv_valid_until
         TIMESTAMP = lv_timestamp
         DESTINATION_LIST = lv_destination_list
         ATTRIBUTE_LIST = lv_attribute_list
         RESPONSIBILITY_LIST = lv_responsibility_list
         SERVER = lv_server
    EXCEPTIONS
        SERVER_NOT_READY = 1
        RFC_ERROR = 2
. " BCOM_R_SCENARIO_SET




ABAP code using 7.40 inline data declarations to call FM BCOM_R_SCENARIO_SET

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!