SAP FKK_PT_CHECK_DS_EXIST Function Module for Checks if a Digital Signature is Existing









FKK_PT_CHECK_DS_EXIST is a standard fkk pt check ds exist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks if a Digital Signature is Existing 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 fkk pt check ds exist FM, simply by entering the name FKK_PT_CHECK_DS_EXIST into the relevant SAP transaction such as SE37 or SE38.

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



Function FKK_PT_CHECK_DS_EXIST 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 'FKK_PT_CHECK_DS_EXIST'"Checks if a Digital Signature is Existing
EXPORTING
IS_DOC_DFKKEXTDOC2 = "
IF_NO_PRE_DOC = "General Indicator
IF_PRE_DOC_VALID = "General Indicator
* IF_SINGLE_FICA_DOC = "Digital Signature PT: Flag to Mark a Valid Document
* IF_CHECK_ALL_FICA_DOC = "Digital Signature PT: Flag to Mark a Valid Document

IMPORTING
EF_DS_AVAILABLE = "
EV_DS_BASE64 = "
EV_DS_PRINTPAT = "Digital Signature PT: Print Pattern of Previous Document

EXCEPTIONS
DS_NOT_EXIST = 1 DS_INCONSISTENT = 2 ODN_NOT_EXIST = 3 DET_FAILED = 4
.



IMPORTING Parameters details for FKK_PT_CHECK_DS_EXIST

IS_DOC_DFKKEXTDOC2 -

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

IF_NO_PRE_DOC - General Indicator

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

IF_PRE_DOC_VALID - General Indicator

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

IF_SINGLE_FICA_DOC - Digital Signature PT: Flag to Mark a Valid Document

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

IF_CHECK_ALL_FICA_DOC - Digital Signature PT: Flag to Mark a Valid Document

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

EXPORTING Parameters details for FKK_PT_CHECK_DS_EXIST

EF_DS_AVAILABLE -

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

EV_DS_BASE64 -

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

EV_DS_PRINTPAT - Digital Signature PT: Print Pattern of Previous Document

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

EXCEPTIONS details

DS_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

DS_INCONSISTENT -

Data type:
Optional: No
Call by Reference: Yes

ODN_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

DET_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FKK_PT_CHECK_DS_EXIST 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_ds_not_exist  TYPE STRING, "   
lv_ef_ds_available  TYPE ENCCRE_KK, "   
lv_is_doc_dfkkextdoc2  TYPE DFKKEXTDOC2, "   
lv_ev_ds_base64  TYPE ENCCHAR_ST_KK, "   
lv_if_no_pre_doc  TYPE GENERAL_FLAG, "   
lv_ds_inconsistent  TYPE GENERAL_FLAG, "   
lv_odn_not_exist  TYPE GENERAL_FLAG, "   
lv_ev_ds_printpat  TYPE IDPT_DS_PREVPRINT_CHAR, "   
lv_if_pre_doc_valid  TYPE GENERAL_FLAG, "   
lv_det_failed  TYPE GENERAL_FLAG, "   
lv_if_single_fica_doc  TYPE IDPT_DS_VALID_DOC, "   
lv_if_check_all_fica_doc  TYPE IDPT_DS_VALID_DOC. "   

  CALL FUNCTION 'FKK_PT_CHECK_DS_EXIST'  "Checks if a Digital Signature is Existing
    EXPORTING
         IS_DOC_DFKKEXTDOC2 = lv_is_doc_dfkkextdoc2
         IF_NO_PRE_DOC = lv_if_no_pre_doc
         IF_PRE_DOC_VALID = lv_if_pre_doc_valid
         IF_SINGLE_FICA_DOC = lv_if_single_fica_doc
         IF_CHECK_ALL_FICA_DOC = lv_if_check_all_fica_doc
    IMPORTING
         EF_DS_AVAILABLE = lv_ef_ds_available
         EV_DS_BASE64 = lv_ev_ds_base64
         EV_DS_PRINTPAT = lv_ev_ds_printpat
    EXCEPTIONS
        DS_NOT_EXIST = 1
        DS_INCONSISTENT = 2
        ODN_NOT_EXIST = 3
        DET_FAILED = 4
. " FKK_PT_CHECK_DS_EXIST




ABAP code using 7.40 inline data declarations to call FM FKK_PT_CHECK_DS_EXIST

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!