SAP SIPT_SIGN_SAFT Function Module for SIgnature PT: Generate Digital Signature









SIPT_SIGN_SAFT is a standard sipt sign saft SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SIgnature PT: Generate Digital Signature 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 sipt sign saft FM, simply by entering the name SIPT_SIGN_SAFT into the relevant SAP transaction such as SE37 or SE38.

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



Function SIPT_SIGN_SAFT 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 'SIPT_SIGN_SAFT'"SIgnature PT: Generate Digital Signature
  EXPORTING
   IV_INV_DATE =  "Signature PT: Invoice/Billing Date
   IV_SY_DATE =  "Signature PT: System Entry Date and Time
   IV_INV_NO_SAFT =  "Signature PT: Invoice Number
   IV_GROSS_TOTAL =  "Signature PT: Gross Amount
   IV_PREV_SIGNATURE =  "

 IMPORTING
   EV_SIGNATURE =  "
   EV_PRINT_CHAR =  "Signature PT: Print Characters
   EV_CERT_ID =  "Signature PT: Certification ID
   EV_KEY_VERS =  "Signature PT: Encryption Key Version
   EV_SERIALNO =  "
   EV_SUBJECT =  "SSF Name for Signatory/Recipient

EXCEPTIONS
   ERROR = 1
.



IMPORTING Parameters details for SIPT_SIGN_SAFT

IV_INV_DATE - Signature PT: Invoice/Billing Date

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

IV_SY_DATE - Signature PT: System Entry Date and Time

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

IV_INV_NO_SAFT - Signature PT: Invoice Number

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

IV_GROSS_TOTAL - Signature PT: Gross Amount

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

IV_PREV_SIGNATURE -

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

EXPORTING Parameters details for SIPT_SIGN_SAFT

EV_SIGNATURE -

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

EV_PRINT_CHAR - Signature PT: Print Characters

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

EV_CERT_ID - Signature PT: Certification ID

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

EV_KEY_VERS - Signature PT: Encryption Key Version

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

EV_SERIALNO -

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

EV_SUBJECT - SSF Name for Signatory/Recipient

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

EXCEPTIONS details

ERROR - Error has occured

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SIPT_SIGN_SAFT 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_error  TYPE STRING, "   
lv_iv_inv_date  TYPE SIPT_INV_DATE, "   
lv_ev_signature  TYPE STRING, "   
lv_iv_sy_date  TYPE SIPT_SY_DATE, "   
lv_ev_print_char  TYPE SIPT_PRINT_CHAR, "   
lv_ev_cert_id  TYPE SIPT_CERT_ID, "   
lv_iv_inv_no_saft  TYPE SIPT_INV_NO_SAFT, "   
lv_ev_key_vers  TYPE SIPT_KEY_VERS, "   
lv_iv_gross_total  TYPE SIPT_GROSS_TOTAL, "   
lv_ev_serialno  TYPE C, "   
lv_iv_prev_signature  TYPE STRING, "   
lv_ev_subject  TYPE SSFID. "   

  CALL FUNCTION 'SIPT_SIGN_SAFT'  "SIgnature PT: Generate Digital Signature
    EXPORTING
         IV_INV_DATE = lv_iv_inv_date
         IV_SY_DATE = lv_iv_sy_date
         IV_INV_NO_SAFT = lv_iv_inv_no_saft
         IV_GROSS_TOTAL = lv_iv_gross_total
         IV_PREV_SIGNATURE = lv_iv_prev_signature
    IMPORTING
         EV_SIGNATURE = lv_ev_signature
         EV_PRINT_CHAR = lv_ev_print_char
         EV_CERT_ID = lv_ev_cert_id
         EV_KEY_VERS = lv_ev_key_vers
         EV_SERIALNO = lv_ev_serialno
         EV_SUBJECT = lv_ev_subject
    EXCEPTIONS
        ERROR = 1
. " SIPT_SIGN_SAFT




ABAP code using 7.40 inline data declarations to call FM SIPT_SIGN_SAFT

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!