FMCA_SAMPLE_P216 SAP Function module - EVENT for PaymentDirectiveERPCreateRequestConfirmation_In(Outbound)

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

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

Pattern for FM FMCA_SAMPLE_P216 - FMCA SAMPLE P216

CALL FUNCTION 'FMCA_SAMPLE_P216' "EVENT for PaymentDirectiveERPCreateRequestConfirmation_In(Outbound)
  EXPORTING
    i_confirmation =            " genebpp_confirmation  Biller Direct: Returns Data
  CHANGING
    c_output =                  " fmca_payment_directive_erpcr14  confirmation to the request for creation of a payment direct
    ct_messages =               " bapirettab    Table with BAPI Return Information
    c_returncode =              " sy-subrc      Return Value of ABAP Statements
    .  "  FMCA_SAMPLE_P216

ABAP code example for Function Module FMCA_SAMPLE_P216

The ABAP code below is a full code listing to execute function module FMCA_SAMPLE_P216 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_c_output) = 'Check type of data required'.

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

DATA(ld_c_returncode) = '20210129'.

DATA(ld_i_confirmation) = '20210129'.
.

CALL FUNCTION 'FMCA_SAMPLE_P216'
  EXPORTING
    i_confirmation =             ld_i_confirmation
  CHANGING
    c_output =                   ld_c_output
    ct_messages =                ld_ct_messages
    c_returncode =               ld_c_returncode
    .  "  FMCA_SAMPLE_P216

IF SY-SUBRC EQ 0.
  "All OK
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_output
 
 TYPE FMCA_PAYMENT_DIRECTIVE_ERPCR14 ,
ld_i_confirmation
 
 TYPE GENEBPP_CONFIRMATION ,
ld_ct_messages
 
 TYPE BAPIRETTAB ,
ld_c_returncode
 
 TYPE SY-SUBRC .


ld_c_output = '20210129'.
ld_i_confirmation = '20210129'.
ld_ct_messages = '20210129'.
ld_c_returncode = '20210129'.

SAP Documentation for FM FMCA_SAMPLE_P216