SSFS_GET_SIGNATURE SAP Function module

SSFS_GET_SIGNATURE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SSFS_GET_SIGNATURE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SSFS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SSFS_GET_SIGNATURE - SSFS GET SIGNATURE

CALL FUNCTION 'SSFS_GET_SIGNATURE' "
* EXPORTING
*   gui_type = 'WIN_GUI'        " string
*   bsp_req =                   " if_http_request  HTTP Framework (iHTTP) HTTP Request
  IMPORTING
    crc =                       " i
    signature =                 " xstring
    bsp_sess_id =               " string
  EXCEPTIONS
    FRONTEND_ERROR = 1          "
    BASE64_ERROR = 2            "
    .  "  SSFS_GET_SIGNATURE

ABAP code example for Function Module SSFS_GET_SIGNATURE

The ABAP code below is a full code listing to execute function module SSFS_GET_SIGNATURE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_crc  
 
 TYPE I
,
ld_signature  
 
 TYPE XSTRING
,
ld_bsp_sess_id  
 
 TYPE STRING
.


DATA(ld_gui_type) = 'Check type of data required'.

DATA(ld_bsp_req) = 'Check type of data required'.
.

CALL FUNCTION 'SSFS_GET_SIGNATURE'
* EXPORTING
*   gui_type =                   ld_gui_type
*   bsp_req =                    ld_bsp_req
  IMPORTING
    crc =                        ld_crc
    signature =                  ld_signature
    bsp_sess_id =                ld_bsp_sess_id
  EXCEPTIONS
    FRONTEND_ERROR =             1
    BASE64_ERROR =               2
    .  "  SSFS_GET_SIGNATURE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_crc
 
 TYPE I ,
ld_gui_type
 
 TYPE STRING ,
ld_signature
 
 TYPE XSTRING ,
ld_bsp_req
 
 TYPE IF_HTTP_REQUEST ,
ld_bsp_sess_id
 
 TYPE STRING .


ld_gui_type = 'Check type of data required'.
ld_bsp_req = 'Check type of data required'.