SAP STRUSTCAB_PARSE_CERTIFICATE Function Module for









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

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



Function STRUSTCAB_PARSE_CERTIFICATE 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 'STRUSTCAB_PARSE_CERTIFICATE'"
  EXPORTING
   IF_CERTIFICATE =  "
*  IF_FORMAT = 1 "

 IMPORTING
   EF_SUBJECT =  "
   EF_VALID_TO =  "
   EF_FINGERPRINT =  "
   EF_FINGERPRINTSHA1 =  "
   EF_SUBJECT_KEY_ID =  "
   EF_PKFINGERPRINT =  "
   EF_EMAIL_ADDRESS =  "
   EF_SUMMARY =  "
   EF_TO_STRING =  "
   EF_ISSUER =  "
   EF_SUBJECT_SHA1 =  "
   EF_ISSUER_SHA1 =  "
   EF_SERIAL_NO =  "
   EF_SERIAL_INT =  "
   EF_SERIAL_NO_SHA1 =  "
   EF_SERIAL_INT_SHA1 =  "
   EF_VALID_FROM =  "

EXCEPTIONS
   INVALID_CERT = 1
.



IMPORTING Parameters details for STRUSTCAB_PARSE_CERTIFICATE

IF_CERTIFICATE -

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

IF_FORMAT -

Data type: I
Default: 1
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for STRUSTCAB_PARSE_CERTIFICATE

EF_SUBJECT -

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

EF_VALID_TO -

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

EF_FINGERPRINT -

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

EF_FINGERPRINTSHA1 -

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

EF_SUBJECT_KEY_ID -

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

EF_PKFINGERPRINT -

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

EF_EMAIL_ADDRESS -

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

EF_SUMMARY -

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

EF_TO_STRING -

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

EF_ISSUER -

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

EF_SUBJECT_SHA1 -

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

EF_ISSUER_SHA1 -

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

EF_SERIAL_NO -

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

EF_SERIAL_INT -

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

EF_SERIAL_NO_SHA1 -

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

EF_SERIAL_INT_SHA1 -

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

EF_VALID_FROM -

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

EXCEPTIONS details

INVALID_CERT -

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

Copy and paste ABAP code example for STRUSTCAB_PARSE_CERTIFICATE 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_ef_subject  TYPE STRING, "   
lv_invalid_cert  TYPE STRING, "   
lv_if_certificate  TYPE XSTRING, "   
lv_ef_valid_to  TYPE DATS, "   
lv_ef_fingerprint  TYPE STRING, "   
lv_ef_fingerprintsha1  TYPE HASH160X, "   
lv_ef_subject_key_id  TYPE STRING, "   
lv_ef_pkfingerprint  TYPE STRING, "   
lv_ef_email_address  TYPE STRING, "   
lv_ef_summary  TYPE STRING, "   
lv_ef_to_string  TYPE STRING, "   
lv_ef_issuer  TYPE STRING, "   
lv_if_format  TYPE I, "   1
lv_ef_subject_sha1  TYPE HASH160X, "   
lv_ef_issuer_sha1  TYPE HASH160X, "   
lv_ef_serial_no  TYPE STRING, "   
lv_ef_serial_int  TYPE STRING, "   
lv_ef_serial_no_sha1  TYPE HASH160X, "   
lv_ef_serial_int_sha1  TYPE HASH160X, "   
lv_ef_valid_from  TYPE DATS. "   

  CALL FUNCTION 'STRUSTCAB_PARSE_CERTIFICATE'  "
    EXPORTING
         IF_CERTIFICATE = lv_if_certificate
         IF_FORMAT = lv_if_format
    IMPORTING
         EF_SUBJECT = lv_ef_subject
         EF_VALID_TO = lv_ef_valid_to
         EF_FINGERPRINT = lv_ef_fingerprint
         EF_FINGERPRINTSHA1 = lv_ef_fingerprintsha1
         EF_SUBJECT_KEY_ID = lv_ef_subject_key_id
         EF_PKFINGERPRINT = lv_ef_pkfingerprint
         EF_EMAIL_ADDRESS = lv_ef_email_address
         EF_SUMMARY = lv_ef_summary
         EF_TO_STRING = lv_ef_to_string
         EF_ISSUER = lv_ef_issuer
         EF_SUBJECT_SHA1 = lv_ef_subject_sha1
         EF_ISSUER_SHA1 = lv_ef_issuer_sha1
         EF_SERIAL_NO = lv_ef_serial_no
         EF_SERIAL_INT = lv_ef_serial_int
         EF_SERIAL_NO_SHA1 = lv_ef_serial_no_sha1
         EF_SERIAL_INT_SHA1 = lv_ef_serial_int_sha1
         EF_VALID_FROM = lv_ef_valid_from
    EXCEPTIONS
        INVALID_CERT = 1
. " STRUSTCAB_PARSE_CERTIFICATE




ABAP code using 7.40 inline data declarations to call FM STRUSTCAB_PARSE_CERTIFICATE

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.

 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_if_format) = 1.
 
 
 
 
 
 
 
 


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!