SAP RFC_F_SCMA_RFC Function Module for Schedul Manager: Start Job or Tcode in Satellite









RFC_F_SCMA_RFC is a standard rfc f scma rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Schedul Manager: Start Job or Tcode in Satellite 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 rfc f scma rfc FM, simply by entering the name RFC_F_SCMA_RFC into the relevant SAP transaction such as SE37 or SE38.

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



Function RFC_F_SCMA_RFC 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 'RFC_F_SCMA_RFC'"Schedul Manager: Start Job or Tcode in Satellite
  EXPORTING
*  I_REPORT =  "Report to be started
*  I_VARIANT =  "Variant of report to be started
*  I_EXTERN_RFCDEST_C =  "Destination of Central system (Caller)
*  I_EXTERN_CALLER_ID =  "ID of calling job in Schedule Manager
*  I_EXTERN_RFCDEST_S =  "Destination of satellite system
*  I_EXTERN_UNAME =  "User Name to start the job
*  I_EXTERN_RFCDIA_C =  "Dialog-Destination of central system
*  I_EXTERN_RFCDIA_S =  "Dialog-Destination of satellite system
*  I_TCODE =  "Transaction Code to be started

 IMPORTING
   E_SUBRC =  "Return Value of ABAP Statements

EXCEPTIONS
   ERROR_WITH_VARIANT = 1    NO_AUTHORITY = 2
.



IMPORTING Parameters details for RFC_F_SCMA_RFC

I_REPORT - Report to be started

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

I_VARIANT - Variant of report to be started

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

I_EXTERN_RFCDEST_C - Destination of Central system (Caller)

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

I_EXTERN_CALLER_ID - ID of calling job in Schedule Manager

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

I_EXTERN_RFCDEST_S - Destination of satellite system

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

I_EXTERN_UNAME - User Name to start the job

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

I_EXTERN_RFCDIA_C - Dialog-Destination of central system

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

I_EXTERN_RFCDIA_S - Dialog-Destination of satellite system

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

I_TCODE - Transaction Code to be started

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

EXPORTING Parameters details for RFC_F_SCMA_RFC

E_SUBRC - Return Value of ABAP Statements

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

EXCEPTIONS details

ERROR_WITH_VARIANT - Variant could not be started

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY - No authority to execute the transaction

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RFC_F_SCMA_RFC 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_e_subrc  TYPE SYSUBRC, "   
lv_i_report  TYPE PROGNAME, "   
lv_error_with_variant  TYPE PROGNAME, "   
lv_i_variant  TYPE VARIANT, "   
lv_no_authority  TYPE VARIANT, "   
lv_i_extern_rfcdest_c  TYPE RFCDEST, "   
lv_i_extern_caller_id  TYPE TZNTSTMPL, "   
lv_i_extern_rfcdest_s  TYPE RFCDEST, "   
lv_i_extern_uname  TYPE UNAME, "   
lv_i_extern_rfcdia_c  TYPE RFCDEST, "   
lv_i_extern_rfcdia_s  TYPE RFCDEST, "   
lv_i_tcode  TYPE TCODE. "   

  CALL FUNCTION 'RFC_F_SCMA_RFC'  "Schedul Manager: Start Job or Tcode in Satellite
    EXPORTING
         I_REPORT = lv_i_report
         I_VARIANT = lv_i_variant
         I_EXTERN_RFCDEST_C = lv_i_extern_rfcdest_c
         I_EXTERN_CALLER_ID = lv_i_extern_caller_id
         I_EXTERN_RFCDEST_S = lv_i_extern_rfcdest_s
         I_EXTERN_UNAME = lv_i_extern_uname
         I_EXTERN_RFCDIA_C = lv_i_extern_rfcdia_c
         I_EXTERN_RFCDIA_S = lv_i_extern_rfcdia_s
         I_TCODE = lv_i_tcode
    IMPORTING
         E_SUBRC = lv_e_subrc
    EXCEPTIONS
        ERROR_WITH_VARIANT = 1
        NO_AUTHORITY = 2
. " RFC_F_SCMA_RFC




ABAP code using 7.40 inline data declarations to call FM RFC_F_SCMA_RFC

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!