SAP SSFC_BASE64_CODE Function Module for
SSFC_BASE64_CODE is a standard ssfc base64 code 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 ssfc base64 code FM, simply by entering the name SSFC_BASE64_CODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SSFZ
Program Name: SAPLSSFZ
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SSFC_BASE64_CODE 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 'SSFC_BASE64_CODE'".
EXPORTING
* DECODE = ' ' "
* IO_SPEC = 'T' "
OSTR_INPUT_DATA_L = "
IMPORTING
OSTR_DIGESTED_DATA_L = "
TABLES
OSTR_INPUT_DATA = "
OSTR_DIGESTED_DATA = "
EXCEPTIONS
SSF_KRN_ERROR = 1 SSF_KRN_NOOP = 2 SSF_KRN_NOMEMORY = 3 SSF_KRN_OPINV = 4 SSF_KRN_INPUT_DATA_ERROR = 5 SSF_KRN_INVALID_PAR = 6 SSF_KRN_INVALID_PARLEN = 7
IMPORTING Parameters details for SSFC_BASE64_CODE
DECODE -
Data type: SSFPARMS-BDETACHEDDefault: ' '
Optional: Yes
Call by Reference: Yes
IO_SPEC -
Data type: SSFPARMS-IOSPECDefault: 'T'
Optional: Yes
Call by Reference: Yes
OSTR_INPUT_DATA_L -
Data type: SSFPARMS-INDATALENOptional: No
Call by Reference: Yes
EXPORTING Parameters details for SSFC_BASE64_CODE
OSTR_DIGESTED_DATA_L -
Data type: SSFPARMS-DIGDATALENOptional: No
Call by Reference: Yes
TABLES Parameters details for SSFC_BASE64_CODE
OSTR_INPUT_DATA -
Data type:Optional: No
Call by Reference: Yes
OSTR_DIGESTED_DATA -
Data type:Optional: No
Call by Reference: Yes
EXCEPTIONS details
SSF_KRN_ERROR -
Data type:Optional: No
Call by Reference: Yes
SSF_KRN_NOOP -
Data type:Optional: No
Call by Reference: Yes
SSF_KRN_NOMEMORY - Main Memory Not Sufficient
Data type:Optional: No
Call by Reference: Yes
SSF_KRN_OPINV -
Data type:Optional: No
Call by Reference: Yes
SSF_KRN_INPUT_DATA_ERROR -
Data type:Optional: No
Call by Reference: Yes
SSF_KRN_INVALID_PAR - An SSF Parameter is Erroneous
Data type:Optional: No
Call by Reference: Yes
SSF_KRN_INVALID_PARLEN - Length of an SSF Parameter is Erroneous
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SSFC_BASE64_CODE 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_decode | TYPE SSFPARMS-BDETACHED, " ' ' | |||
| lv_ssf_krn_error | TYPE SSFPARMS, " | |||
| lt_ostr_input_data | TYPE STANDARD TABLE OF SSFPARMS, " | |||
| lv_ostr_digested_data_l | TYPE SSFPARMS-DIGDATALEN, " | |||
| lv_io_spec | TYPE SSFPARMS-IOSPEC, " 'T' | |||
| lv_ssf_krn_noop | TYPE SSFPARMS, " | |||
| lt_ostr_digested_data | TYPE STANDARD TABLE OF SSFPARMS, " | |||
| lv_ssf_krn_nomemory | TYPE SSFPARMS, " | |||
| lv_ostr_input_data_l | TYPE SSFPARMS-INDATALEN, " | |||
| lv_ssf_krn_opinv | TYPE SSFPARMS, " | |||
| lv_ssf_krn_input_data_error | TYPE SSFPARMS, " | |||
| lv_ssf_krn_invalid_par | TYPE SSFPARMS, " | |||
| lv_ssf_krn_invalid_parlen | TYPE SSFPARMS. " |
|   CALL FUNCTION 'SSFC_BASE64_CODE' " |
| EXPORTING | ||
| DECODE | = lv_decode | |
| IO_SPEC | = lv_io_spec | |
| OSTR_INPUT_DATA_L | = lv_ostr_input_data_l | |
| IMPORTING | ||
| OSTR_DIGESTED_DATA_L | = lv_ostr_digested_data_l | |
| TABLES | ||
| OSTR_INPUT_DATA | = lt_ostr_input_data | |
| OSTR_DIGESTED_DATA | = lt_ostr_digested_data | |
| EXCEPTIONS | ||
| SSF_KRN_ERROR = 1 | ||
| SSF_KRN_NOOP = 2 | ||
| SSF_KRN_NOMEMORY = 3 | ||
| SSF_KRN_OPINV = 4 | ||
| SSF_KRN_INPUT_DATA_ERROR = 5 | ||
| SSF_KRN_INVALID_PAR = 6 | ||
| SSF_KRN_INVALID_PARLEN = 7 | ||
| . " SSFC_BASE64_CODE | ||
ABAP code using 7.40 inline data declarations to call FM SSFC_BASE64_CODE
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 BDETACHED FROM SSFPARMS INTO @DATA(ld_decode). | ||||
| DATA(ld_decode) | = ' '. | |||
| "SELECT single DIGDATALEN FROM SSFPARMS INTO @DATA(ld_ostr_digested_data_l). | ||||
| "SELECT single IOSPEC FROM SSFPARMS INTO @DATA(ld_io_spec). | ||||
| DATA(ld_io_spec) | = 'T'. | |||
| "SELECT single INDATALEN FROM SSFPARMS INTO @DATA(ld_ostr_input_data_l). | ||||
Search for further information about these or an SAP related objects