SAP FTR_ALE_FUTURE_CREATE Function Module for BAPI -> IDoc: FTR_ALE_FUTURE_CREATE









FTR_ALE_FUTURE_CREATE is a standard ftr ale future create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: FTR_ALE_FUTURE_CREATE processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for ftr ale future create FM, simply by entering the name FTR_ALE_FUTURE_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FTR_BAPI_FUTURE
Program Name: SAPLFTR_BAPI_FUTURE
Main Program: SAPLFTR_BAPI_FUTURE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FTR_ALE_FUTURE_CREATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'FTR_ALE_FUTURE_CREATE'"BAPI -> IDoc: FTR_ALE_FUTURE_CREATE
EXPORTING
FUTURE = "Create Product-Specific Data for a Future
GENERALCONTRACTDATA = "Greate General Data for a Future
* TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs
* OBJ_TYPE = 'BUS5700' "
* SERIAL_ID = '0' "

TABLES
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "

EXCEPTIONS
ERROR_CREATING_IDOCS = 1
.



IMPORTING Parameters details for FTR_ALE_FUTURE_CREATE

FUTURE - Create Product-Specific Data for a Future

Data type: BAPI_FTR_CREATE_FUTURE
Optional: No
Call by Reference: No ( called with pass by value option)

GENERALCONTRACTDATA - Greate General Data for a Future

Data type: BAPI_FTR_CREATE
Optional: No
Call by Reference: No ( called with pass by value option)

TESTRUN - Switch to Simulation Mode for Write BAPIs

Data type: BAPI2042-TESTRUN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUS5700'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FTR_ALE_FUTURE_CREATE

RECEIVERS -

Data type: BDI_LOGSYS
Optional: No
Call by Reference: No ( called with pass by value option)

COMMUNICATION_DOCUMENTS -

Data type: SWOTOBJID
Optional: Yes
Call by Reference: No ( called with pass by value option)

APPLICATION_OBJECTS -

Data type: SWOTOBJID
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_CREATING_IDOCS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FTR_ALE_FUTURE_CREATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_future  TYPE BAPI_FTR_CREATE_FUTURE, "   
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_error_creating_idocs  TYPE BDI_LOGSYS, "   
lv_generalcontractdata  TYPE BAPI_FTR_CREATE, "   
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_testrun  TYPE BAPI2042-TESTRUN, "   SPACE
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'BUS5700'
lv_serial_id  TYPE SERIAL-CHNUM. "   '0'

  CALL FUNCTION 'FTR_ALE_FUTURE_CREATE'  "BAPI -> IDoc: FTR_ALE_FUTURE_CREATE
    EXPORTING
         FUTURE = lv_future
         GENERALCONTRACTDATA = lv_generalcontractdata
         TESTRUN = lv_testrun
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
    TABLES
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " FTR_ALE_FUTURE_CREATE




ABAP code using 7.40 inline data declarations to call FM FTR_ALE_FUTURE_CREATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
"SELECT single TESTRUN FROM BAPI2042 INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 
 
"SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'BUS5700'.
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!