RSPO_CF_DTB_POST SAP Function module

RSPO_CF_DTB_POST 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_CF_DTB_POST into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM RSPO_CF_DTB_POST - RSPO CF DTB POST

CALL FUNCTION 'RSPO_CF_DTB_POST' "
  EXPORTING
    devicetype =                " tsp0a-patype
*   update = 'X'                " c
  IMPORTING
    errstring =                 " string
    warning_list =              " cft_charline
    trace_list =                " cft_charline
  EXCEPTIONS
    DEVICETYPE_NOT_FOUND = 1    "
    DEVICETYPE_NOT_POST = 2     "
    NO_CASCADING_FONTS_DEFINED = 3  "
    NO_CFPIF_FILE = 4           "
    ERROR_IN_CFPIF_FILE = 5     "
    OTHER_ERROR = 6             "
    .  "  RSPO_CF_DTB_POST

ABAP code example for Function Module RSPO_CF_DTB_POST

The ABAP code below is a full code listing to execute function module RSPO_CF_DTB_POST 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_errstring  
 
 TYPE STRING
,
ld_warning_list  
 
 TYPE CFT_CHARLINE
,
ld_trace_list  
 
 TYPE CFT_CHARLINE
.

 

SELECT single PATYPE 
  FROM TSP0A 
  INTO @DATA(ld_devicetype).


DATA(ld_update) = 'Check type of data required'.
.

CALL FUNCTION 'RSPO_CF_DTB_POST'
  EXPORTING
    devicetype =                 ld_devicetype
*   update =                     ld_update
  IMPORTING
    errstring =                  ld_errstring
    warning_list =               ld_warning_list
    trace_list =                 ld_trace_list
  EXCEPTIONS
    DEVICETYPE_NOT_FOUND =       1
    DEVICETYPE_NOT_POST =        2
    NO_CASCADING_FONTS_DEFINED =    3
    NO_CFPIF_FILE =              4
    ERROR_IN_CFPIF_FILE =        5
    OTHER_ERROR =                6
    .  "  RSPO_CF_DTB_POST

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
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_errstring
 
 TYPE STRING ,
ld_devicetype
 
 TYPE TSP0A-PATYPE ,
ld_warning_list
 
 TYPE CFT_CHARLINE ,
ld_update
 
 TYPE C ,
ld_trace_list
 
 TYPE CFT_CHARLINE .



SELECT single PATYPE 
  FROM TSP0A 
  INTO ld_devicetype.

ld_update = 'Check type of data required'.