SAP SSFI_VERIFY_SIGNATURE Function Module for









SSFI_VERIFY_SIGNATURE is a standard ssfi verify signature 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 ssfi verify signature FM, simply by entering the name SSFI_VERIFY_SIGNATURE into the relevant SAP transaction such as SE37 or SE38.

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



Function SSFI_VERIFY_SIGNATURE 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 'SSFI_VERIFY_SIGNATURE'"
EXPORTING
SIGNED_DATA_LEN = "

IMPORTING
SIGNERID = "

TABLES
SIGNED_DATA = "
* OUTPUT_DATA = "

EXCEPTIONS
SYSTEM_ERROR = 1 VERIFICATION_ERROR = 2 SIGNER_ERROR = 3 MULTIPLESIGNER_ERROR = 4
.



IMPORTING Parameters details for SSFI_VERIFY_SIGNATURE

SIGNED_DATA_LEN -

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

EXPORTING Parameters details for SSFI_VERIFY_SIGNATURE

SIGNERID -

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

TABLES Parameters details for SSFI_VERIFY_SIGNATURE

SIGNED_DATA -

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

OUTPUT_DATA -

Data type:
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

SYSTEM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

VERIFICATION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SIGNER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

MULTIPLESIGNER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SSFI_VERIFY_SIGNATURE 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_signerid  TYPE SSFID, "   
lt_signed_data  TYPE STANDARD TABLE OF SSFBIN, "   
lv_system_error  TYPE SSFBIN, "   
lv_signed_data_len  TYPE I, "   
lt_output_data  TYPE STANDARD TABLE OF I, "   
lv_verification_error  TYPE I, "   
lv_signer_error  TYPE I, "   
lv_multiplesigner_error  TYPE I. "   

  CALL FUNCTION 'SSFI_VERIFY_SIGNATURE'  "
    EXPORTING
         SIGNED_DATA_LEN = lv_signed_data_len
    IMPORTING
         SIGNERID = lv_signerid
    TABLES
         SIGNED_DATA = lt_signed_data
         OUTPUT_DATA = lt_output_data
    EXCEPTIONS
        SYSTEM_ERROR = 1
        VERIFICATION_ERROR = 2
        SIGNER_ERROR = 3
        MULTIPLESIGNER_ERROR = 4
. " SSFI_VERIFY_SIGNATURE




ABAP code using 7.40 inline data declarations to call FM SSFI_VERIFY_SIGNATURE

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!