RSPO_SPOOLDATA_GET_PRINTABLE SAP Function module

RSPO_SPOOLDATA_GET_PRINTABLE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name RSPO_SPOOLDATA_GET_PRINTABLE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SPOC
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RSPO_SPOOLDATA_GET_PRINTABLE - RSPO SPOOLDATA GET PRINTABLE

CALL FUNCTION 'RSPO_SPOOLDATA_GET_PRINTABLE' "
  EXPORTING
    spool_data =                "
*   data_length = 0             " rststype-linelength  TemSe: Line length
*   codepage =                  " tcp02-cpcodepage  SAP character set identification
  IMPORTING
    printable =                 " c
    charlen =                   " i
    basiccharlen =              " i
    hex1 =                      " c
    hex2 =                      " c
    hex3 =                      " c
    hex4 =                      " c
  EXCEPTIONS
    DATA_TOO_SHORT = 1          "
    FAILED = 2                  "
    .  "  RSPO_SPOOLDATA_GET_PRINTABLE

ABAP code example for Function Module RSPO_SPOOLDATA_GET_PRINTABLE

The ABAP code below is a full code listing to execute function module RSPO_SPOOLDATA_GET_PRINTABLE including all data declarations. The code uses 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 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_printable  
 
 TYPE C
,
ld_charlen  
 
 TYPE I
,
ld_basiccharlen  
 
 TYPE I
,
ld_hex1  
 
 TYPE C
,
ld_hex2  
 
 TYPE C
,
ld_hex3  
 
 TYPE C
,
ld_hex4  
 
 TYPE C
.


DATA(ld_spool_data) = 'some text here'.


DATA(ld_data_length) = Check type of data required
 

SELECT single CPCODEPAGE 
  FROM TCP02 
  INTO @DATA(ld_codepage).

.

CALL FUNCTION 'RSPO_SPOOLDATA_GET_PRINTABLE'
  EXPORTING
    spool_data =                 ld_spool_data
*   data_length =                ld_data_length
*   codepage =                   ld_codepage
  IMPORTING
    printable =                  ld_printable
    charlen =                    ld_charlen
    basiccharlen =               ld_basiccharlen
    hex1 =                       ld_hex1
    hex2 =                       ld_hex2
    hex3 =                       ld_hex3
    hex4 =                       ld_hex4
  EXCEPTIONS
    DATA_TOO_SHORT =             1
    FAILED =                     2
    .  "  RSPO_SPOOLDATA_GET_PRINTABLE

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
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_printable
 
 TYPE C ,
ld_spool_data
 
 TYPE STRING ,
ld_charlen
 
 TYPE I ,
ld_data_length
 
 TYPE RSTSTYPE-LINELENGTH ,
ld_basiccharlen
 
 TYPE I ,
ld_codepage
 
 TYPE TCP02-CPCODEPAGE ,
ld_hex1
 
 TYPE C ,
ld_hex2
 
 TYPE C ,
ld_hex3
 
 TYPE C ,
ld_hex4
 
 TYPE C .


ld_spool_data = 'some text here'.

ld_data_length = Check type of data required

SELECT single CPCODEPAGE 
  FROM TCP02 
  INTO ld_codepage.