SAP Tables

SSFC_BASE64_ENCODE SAP Function module




SSFC_BASE64_ENCODEis a standard SAP function module available within R/3 SAPsystems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import/export parameters, exceptions etc as well as any documentation contributions specific to the object. See here to view full function module documentation and code listing, simply by entering the name SSFC_BASE64_ENCODE into the relevant SAP transaction such as SE37 or SE80.

Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SSFC_BASE64_ENCODE or its description.


Pattern for FM SSFC_BASE64_ENCODE - SSFC BASE64 ENCODE
Associated Function Group: SSFC
Released Date: Not Released
CALL FUNCTION 'SSFC_BASE64_ENCODE' "
  EXPORTING
    bindata =                   " xstring       Binary Data
*   binleng =                   " i
  IMPORTING
    b64data =                   " string
  EXCEPTIONS
    SSF_KRN_ERROR = 1           "
    SSF_KRN_NOOP = 2            "
    SSF_KRN_NOMEMORY = 3        "               Main Memory Not Sufficient
    SSF_KRN_OPINV = 4           "
    SSF_KRN_INPUT_DATA_ERROR = 5  "
    SSF_KRN_INVALID_PAR = 6     "               An SSF Parameter is Erroneous
    SSF_KRN_INVALID_PARLEN = 7  "               Length of an SSF Parameter is Erroneous
    .  "  SSFC_BASE64_ENCODE

ABAP code example for Function Module SSFC_BASE64_ENCODE

The ABAP code below is a full code listing to execute function module SSFC_BASE64_ENCODE including all data declarations. The code uses the latest in-line data declaration syntax but I have included an abap code snipet at the end to show how declarations would look using the original method of declaring data variables up front. 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).
DATA:
ld_b64data   TYPE STRING.

DATA(ld_bindata) = 'Check type of data required'.
DATA(ld_binleng) = 'Check type of data required'.. CALL FUNCTION 'SSFC_BASE64_ENCODE' EXPORTING bindata = ld_bindata * binleng = ld_binleng IMPORTING b64data = ld_b64data 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_ENCODE
IF SY-SUBRC EQ 0.   "All OK ELSEIF SY-SUBRC EQ 1. "Exception   "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception   "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception   "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception   "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception   "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception   "Add code for exception here ELSEIF SY-SUBRC EQ 7. "Exception   "Add code for exception here ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
ld_b64data TYPE STRING ,
ld_bindata TYPE XSTRING ,
ld_binleng TYPE I .

ld_b64data = 'Check type of data required'.
ld_bindata = 'Check type of data required'.
ld_binleng = 'Check type of data required'..