PA_DERIVE_FO_FOR_FX SAP Function module - PA: Durchführung der Ableitung (FOPA) für Devisen

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

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

Pattern for FM PA_DERIVE_FO_FOR_FX - PA DERIVE FO FOR FX

CALL FUNCTION 'PA_DERIVE_FO_FOR_FX' "PA: Durchführung der Ableitung (FOPA) für Devisen
* EXPORTING
*   i_trace_mode =              " kedr_trace_mode  Trace-Modus (' ': kein Protokoll, 'A': alles)
*   i_fx =                      " jbddr_str_fx  Struktur Devisen
*   i_date = SY-DATUM           " sy-datum
  IMPORTING
    e_trace_handle =            " kedr_trace_handle  Handle für den Trace
* CHANGING
*   c_char =                    " jbddr_char    Struktur Merkmale
*   c_fob =                     " jbddr_fob     Struktur Finanzobjekt (fixe Felder)
*   c_temp =                    " jbddr_temp    Struktur temporäre Felder
  EXCEPTIONS
    DERIVATION_FAILED = 1       "               Ableitung fehlgeschlagen
    .  "  PA_DERIVE_FO_FOR_FX

ABAP code example for Function Module PA_DERIVE_FO_FOR_FX

The ABAP code below is a full code listing to execute function module PA_DERIVE_FO_FOR_FX 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_e_trace_handle  
 
 TYPE KEDR_TRACE_HANDLE
.


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

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

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

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

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

DATA(ld_i_date) = '20210129'.
.

CALL FUNCTION 'PA_DERIVE_FO_FOR_FX'
* EXPORTING
*   i_trace_mode =               ld_i_trace_mode
*   i_fx =                       ld_i_fx
*   i_date =                     ld_i_date
  IMPORTING
    e_trace_handle =             ld_e_trace_handle
* CHANGING
*   c_char =                     ld_c_char
*   c_fob =                      ld_c_fob
*   c_temp =                     ld_c_temp
  EXCEPTIONS
    DERIVATION_FAILED =          1
    .  "  PA_DERIVE_FO_FOR_FX

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_c_char
 
 TYPE JBDDR_CHAR ,
ld_e_trace_handle
 
 TYPE KEDR_TRACE_HANDLE ,
ld_i_trace_mode
 
 TYPE KEDR_TRACE_MODE ,
ld_c_fob
 
 TYPE JBDDR_FOB ,
ld_i_fx
 
 TYPE JBDDR_STR_FX ,
ld_c_temp
 
 TYPE JBDDR_TEMP ,
ld_i_date
 
 TYPE SY-DATUM .


ld_c_char = '20210129'.
ld_i_trace_mode = '20210129'.
ld_c_fob = '20210129'.
ld_i_fx = '20210129'.
ld_c_temp = '20210129'.
ld_i_date = '20210129'.