SAP SSFS_CALL_CONTROL Function Module for









SSFS_CALL_CONTROL is a standard ssfs call control 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 ssfs call control FM, simply by entering the name SSFS_CALL_CONTROL into the relevant SAP transaction such as SE37 or SE38.

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



Function SSFS_CALL_CONTROL 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 'SSFS_CALL_CONTROL'"
  EXPORTING
*  TXTDOCUMENT =  "
*  BSP_EVENT_ID =  "
*  ONLY_SIGCERT = ABAP_FALSE "
*  ONLY_VALIDCERT = ABAP_FALSE "
*  BINDOCUMENT =  "
*  DOC_TYPE = 'TXT' "
*  SIG_FORMAT = 'PKCS7' "
*  B_DETACHED = ' ' "
*  SSF_ID = ' ' "
*  SSF_PROF = ' ' "
*  GUI_TYPE = 'WIN_GUI' "
*  BSP_NAV =  "Business Server Page (BSP) Navigation

 IMPORTING
   CRC =  "
   SIGNATURE =  "
   BSP_SESS_ID =  "

EXCEPTIONS
   PARAMETER_ERROR = 1    CONVERSION_ERROR = 2    CONTROL_ERROR = 3    FRONTEND_ERROR = 4
.



IMPORTING Parameters details for SSFS_CALL_CONTROL

TXTDOCUMENT -

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

BSP_EVENT_ID -

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

ONLY_SIGCERT -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

ONLY_VALIDCERT -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

BINDOCUMENT -

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

DOC_TYPE -

Data type: SSFTYPE
Default: 'TXT'
Optional: Yes
Call by Reference: Yes

SIG_FORMAT -

Data type: SSFFORM
Default: 'PKCS7'
Optional: Yes
Call by Reference: Yes

B_DETACHED -

Data type: SSFBDETA
Default: SPACE
Optional: Yes
Call by Reference: Yes

SSF_ID -

Data type: SSFID
Default: SPACE
Optional: Yes
Call by Reference: Yes

SSF_PROF -

Data type: SSFPROF
Default: SPACE
Optional: Yes
Call by Reference: Yes

GUI_TYPE -

Data type: STRING
Default: 'WIN_GUI'
Optional: Yes
Call by Reference: Yes

BSP_NAV - Business Server Page (BSP) Navigation

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

EXPORTING Parameters details for SSFS_CALL_CONTROL

CRC -

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

SIGNATURE -

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

BSP_SESS_ID -

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

EXCEPTIONS details

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CONVERSION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CONTROL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

FRONTEND_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SSFS_CALL_CONTROL 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_crc  TYPE I, "   
lv_txtdocument  TYPE SSFTXTTAB, "   
lv_parameter_error  TYPE SSFTXTTAB, "   
lv_bsp_event_id  TYPE STRING, "   
lv_only_sigcert  TYPE ABAP_BOOL, "   ABAP_FALSE
lv_only_validcert  TYPE ABAP_BOOL, "   ABAP_FALSE
lv_signature  TYPE XSTRING, "   
lv_bindocument  TYPE XSTRING, "   
lv_conversion_error  TYPE XSTRING, "   
lv_doc_type  TYPE SSFTYPE, "   'TXT'
lv_bsp_sess_id  TYPE STRING, "   
lv_control_error  TYPE STRING, "   
lv_sig_format  TYPE SSFFORM, "   'PKCS7'
lv_frontend_error  TYPE SSFFORM, "   
lv_b_detached  TYPE SSFBDETA, "   SPACE
lv_ssf_id  TYPE SSFID, "   SPACE
lv_ssf_prof  TYPE SSFPROF, "   SPACE
lv_gui_type  TYPE STRING, "   'WIN_GUI'
lv_bsp_nav  TYPE IF_BSP_NAVIGATION. "   

  CALL FUNCTION 'SSFS_CALL_CONTROL'  "
    EXPORTING
         TXTDOCUMENT = lv_txtdocument
         BSP_EVENT_ID = lv_bsp_event_id
         ONLY_SIGCERT = lv_only_sigcert
         ONLY_VALIDCERT = lv_only_validcert
         BINDOCUMENT = lv_bindocument
         DOC_TYPE = lv_doc_type
         SIG_FORMAT = lv_sig_format
         B_DETACHED = lv_b_detached
         SSF_ID = lv_ssf_id
         SSF_PROF = lv_ssf_prof
         GUI_TYPE = lv_gui_type
         BSP_NAV = lv_bsp_nav
    IMPORTING
         CRC = lv_crc
         SIGNATURE = lv_signature
         BSP_SESS_ID = lv_bsp_sess_id
    EXCEPTIONS
        PARAMETER_ERROR = 1
        CONVERSION_ERROR = 2
        CONTROL_ERROR = 3
        FRONTEND_ERROR = 4
. " SSFS_CALL_CONTROL




ABAP code using 7.40 inline data declarations to call FM SSFS_CALL_CONTROL

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.

 
 
 
 
DATA(ld_only_sigcert) = ABAP_FALSE.
 
DATA(ld_only_validcert) = ABAP_FALSE.
 
 
 
 
DATA(ld_doc_type) = 'TXT'.
 
 
 
DATA(ld_sig_format) = 'PKCS7'.
 
 
DATA(ld_b_detached) = ' '.
 
DATA(ld_ssf_id) = ' '.
 
DATA(ld_ssf_prof) = ' '.
 
DATA(ld_gui_type) = 'WIN_GUI'.
 
 


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!