SAP SIGN_VERIFY Function Module for

Search SAP Function Modules

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

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

Function SIGN_VERIFY 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 'SIGN_VERIFY'"
  EXPORTING
*  SSFAPPLICATION =  "
*  SIGDATEGLOB =  "
*  SIGNAMEF =  "
*  SIGNAMEL =  "
*  B_ADDINFO =  "
*  DOC_TXT =  "
*  DOC_BIN =  "
*  DOC_TYPE = 'TXT' "
   SIGNATURE =  "
*  SIGNER =  "
*  SIGNMETHOD = 'S' "
*  SIGCOMMENT =  "
*  SIGREASON =  "
*  SIGREMARK =  "
*  SIGTIMELOC =  "
*  SIGDATELOC =  "
*  SIGTIMEGLOB =  "

EXCEPTIONS
   CONVERSION_ERROR = 1    SYSTEM_ERROR = 2    SECTK_ERROR = 3    PROFILE_ERROR = 4    SIGNATURE_ERROR = 5    SIGNATURE_ERROR_DATA = 6    SIGNATURE_ERROR_WRONGSIGNER = 7 

.

IMPORTING Parameters details for SIGN_VERIFY

SSFAPPLICATION -

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

SIGDATEGLOB -

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

SIGNAMEF -

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

SIGNAMEL -

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

B_ADDINFO -

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

DOC_TXT -

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

DOC_BIN -

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

DOC_TYPE -

Data type: SSFTYPE
Default: 'TXT'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SIGNATURE -

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

SIGNER -

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

SIGNMETHOD -

Data type: SIGN_METHOD
Default: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SIGCOMMENT -

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

SIGREASON -

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

SIGREMARK -

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

SIGTIMELOC -

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

SIGDATELOC -

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

SIGTIMEGLOB -

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

EXCEPTIONS details

CONVERSION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SECTK_ERROR -

Data type:
Optional: No
Call by Reference: Yes

PROFILE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SIGNATURE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

SIGNATURE_ERROR_DATA -

Data type:
Optional: No
Call by Reference: Yes

SIGNATURE_ERROR_WRONGSIGNER -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SIGN_VERIFY 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.

ABAP code using 7.40 inline data declarations to call FM SIGN_VERIFY

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