FTR_ALE_FUTURE_REVERSE SAP Function module - BAPI -> IDoc: FTR_ALE_FUTURE_REVERSE

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

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

Pattern for FM FTR_ALE_FUTURE_REVERSE - FTR ALE FUTURE REVERSE

CALL FUNCTION 'FTR_ALE_FUTURE_REVERSE' "BAPI -> IDoc: FTR_ALE_FUTURE_REVERSE
  EXPORTING
    companycode =               " bapi2042-company_code  Company Code
    financialtransaction =      " bapi2042-transaction  Financial Transaction
*   reversalreason =            " bapi2042-reversal_reason  Reason for Reversal
*   activitycat =               " bapi2042-activitycat  Transaction Activity Category
*   testrun = SPACE             " bapi2042-testrun  Switch to Simulation Mode for Write BAPIs
*   obj_type = 'BUS5700'        " serial-obj_type
*   serial_id = '0'             " serial-chnum
  TABLES
    receivers =                 " bdi_logsys
*   communication_documents =   " swotobjid
*   application_objects =       " swotobjid
  EXCEPTIONS
    ERROR_CREATING_IDOCS = 1    "
    .  "  FTR_ALE_FUTURE_REVERSE

ABAP code example for Function Module FTR_ALE_FUTURE_REVERSE

The ABAP code below is a full code listing to execute function module FTR_ALE_FUTURE_REVERSE 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:
it_receivers  
 
 TYPE STANDARD TABLE OF BDI_LOGSYS,"TABLES PARAM
wa_receivers
 
 LIKE LINE OF it_receivers
,
it_communication_documents  
 
 TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM
wa_communication_documents
 
 LIKE LINE OF it_communication_documents
,
it_application_objects  
 
 TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM
wa_application_objects
 
 LIKE LINE OF it_application_objects
.



DATA(ld_companycode) = some text here


DATA(ld_financialtransaction) = some text here


DATA(ld_reversalreason) = some text here


DATA(ld_activitycat) = Check type of data required


DATA(ld_testrun) = some text here


DATA(ld_obj_type) = some text here


DATA(ld_serial_id) = Check type of data required
 

"populate fields of struture and append to itab
append wa_receivers to it_receivers.
 

"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents.
 

"populate fields of struture and append to itab
append wa_application_objects to it_application_objects.
.

CALL FUNCTION 'FTR_ALE_FUTURE_REVERSE'
  EXPORTING
    companycode =                ld_companycode
    financialtransaction =       ld_financialtransaction
*   reversalreason =             ld_reversalreason
*   activitycat =                ld_activitycat
*   testrun =                    ld_testrun
*   obj_type =                   ld_obj_type
*   serial_id =                  ld_serial_id
  TABLES
    receivers =                  it_receivers
*   communication_documents =    it_communication_documents
*   application_objects =        it_application_objects
  EXCEPTIONS
    ERROR_CREATING_IDOCS =       1
    .  "  FTR_ALE_FUTURE_REVERSE

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_companycode
 
 TYPE BAPI2042-COMPANY_CODE ,
it_receivers
 
 TYPE STANDARD TABLE OF BDI_LOGSYS ,
wa_receivers
 
 LIKE LINE OF it_receivers,
ld_financialtransaction
 
 TYPE BAPI2042-TRANSACTION ,
it_communication_documents
 
 TYPE STANDARD TABLE OF SWOTOBJID ,
wa_communication_documents
 
 LIKE LINE OF it_communication_documents,
ld_reversalreason
 
 TYPE BAPI2042-REVERSAL_REASON ,
it_application_objects
 
 TYPE STANDARD TABLE OF SWOTOBJID ,
wa_application_objects
 
 LIKE LINE OF it_application_objects,
ld_activitycat
 
 TYPE BAPI2042-ACTIVITYCAT ,
ld_testrun
 
 TYPE BAPI2042-TESTRUN ,
ld_obj_type
 
 TYPE SERIAL-OBJ_TYPE ,
ld_serial_id
 
 TYPE SERIAL-CHNUM .



ld_companycode = some text here 

"populate fields of struture and append to itab
append wa_receivers to it_receivers.

ld_financialtransaction = some text here 

"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents.

ld_reversalreason = some text here 

"populate fields of struture and append to itab
append wa_application_objects to it_application_objects.

ld_activitycat = Check type of data required

ld_testrun = some text here

ld_obj_type = some text here

ld_serial_id = Check type of data required