SAP SSFT_PPPI_VERIFY Function Module for









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

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



Function SSFT_PPPI_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 'SSFT_PPPI_VERIFY'"
  EXPORTING
*  SSFAPPLICATION = ' ' "
   SIGNER =  "
*  SIGNING_METHOD = 'S' "
   OSTR_SIGNED_DATA_L =  "

CHANGING
   OSTR_INPUT_DATA_L =  "

TABLES
   OSTR_INPUT_DATA =  "
   OSTR_SIGNED_DATA =  "

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



IMPORTING Parameters details for SSFT_PPPI_VERIFY

SSFAPPLICATION -

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

SIGNER -

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

SIGNING_METHOD -

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

OSTR_SIGNED_DATA_L -

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

CHANGING Parameters details for SSFT_PPPI_VERIFY

OSTR_INPUT_DATA_L -

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

TABLES Parameters details for SSFT_PPPI_VERIFY

OSTR_INPUT_DATA -

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

OSTR_SIGNED_DATA -

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

EXCEPTIONS details

SYSTEM_ERROR - System Error

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

SECTK_ERROR - Error in Security Product

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

PROFILE_ERROR -

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

SIGNATURE_ERROR -

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

SIGNATURE_ERROR_DATA -

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

SIGNATURE_ERROR_WRONGSIGNER -

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

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

DATA:
lv_system_error  TYPE STRING, "   
lv_ssfapplication  TYPE SSFARGS-APPLIC, "   ' '
lt_ostr_input_data  TYPE STANDARD TABLE OF SSFARGS, "   
lv_ostr_input_data_l  TYPE SSFPARMS-INDATALEN, "   
lv_signer  TYPE SSFPARMS-SIGNER, "   
lv_sectk_error  TYPE SSFPARMS, "   
lt_ostr_signed_data  TYPE STANDARD TABLE OF SSFBIN, "   
lv_profile_error  TYPE SSFBIN, "   
lv_signing_method  TYPE SIGNMETHOD, "   'S'
lv_signature_error  TYPE SIGNMETHOD, "   
lv_ostr_signed_data_l  TYPE SSFPARMS-SIGDATALEN, "   
lv_signature_error_data  TYPE SSFPARMS, "   
lv_signature_error_wrongsigner  TYPE SSFPARMS. "   

  CALL FUNCTION 'SSFT_PPPI_VERIFY'  "
    EXPORTING
         SSFAPPLICATION = lv_ssfapplication
         SIGNER = lv_signer
         SIGNING_METHOD = lv_signing_method
         OSTR_SIGNED_DATA_L = lv_ostr_signed_data_l
    CHANGING
         OSTR_INPUT_DATA_L = lv_ostr_input_data_l
    TABLES
         OSTR_INPUT_DATA = lt_ostr_input_data
         OSTR_SIGNED_DATA = lt_ostr_signed_data
    EXCEPTIONS
        SYSTEM_ERROR = 1
        SECTK_ERROR = 2
        PROFILE_ERROR = 3
        SIGNATURE_ERROR = 4
        SIGNATURE_ERROR_DATA = 5
        SIGNATURE_ERROR_WRONGSIGNER = 6
. " SSFT_PPPI_VERIFY




ABAP code using 7.40 inline data declarations to call FM SSFT_PPPI_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.

 
"SELECT single APPLIC FROM SSFARGS INTO @DATA(ld_ssfapplication).
DATA(ld_ssfapplication) = ' '.
 
 
"SELECT single INDATALEN FROM SSFPARMS INTO @DATA(ld_ostr_input_data_l).
 
"SELECT single SIGNER FROM SSFPARMS INTO @DATA(ld_signer).
 
 
 
 
DATA(ld_signing_method) = 'S'.
 
 
"SELECT single SIGDATALEN FROM SSFPARMS INTO @DATA(ld_ostr_signed_data_l).
 
 
 


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!