SAP BAPI_RE_AT_CREATE Function Module for
BAPI_RE_AT_CREATE is a standard bapi re at create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bapi re at create FM, simply by entering the name BAPI_RE_AT_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: REAJ_BAPI_ADJUSTMENT_TASK
Program Name: SAPLREAJ_BAPI_ADJUSTMENT_TASK
Main Program: SAPLREAJ_BAPI_ADJUSTMENT_TASK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_RE_AT_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 'BAPI_RE_AT_CREATE'".
EXPORTING
ADJUSTMENT_TASK_ID_EXT = "
* ADJUST_TASK = "
* TRANS = "
* TEST_RUN = ' ' "
IMPORTING
ADJUSTMENTTASKID = "
TABLES
* ADJUST_TASK_OBJ = "
* EXTENSION_IN = "
RETURN = "
* OBJ_ASSIGN = "
* OBJECT_REL = "
* PARTNER = "
* MEAS_CN = "
* FINPLAN = "
* EXPENSE = "
* RESUBM_RULE = "
* STATUS = "
IMPORTING Parameters details for BAPI_RE_AT_CREATE
ADJUSTMENT_TASK_ID_EXT -
Data type: BAPI_RE_ADJUST_TASK_KEY-ADJUSTMENT_TASK_IDOptional: No
Call by Reference: No ( called with pass by value option)
ADJUST_TASK -
Data type: BAPI_RE_ADJUST_TASK_DATOptional: Yes
Call by Reference: No ( called with pass by value option)
TRANS -
Data type: BAPI_RE_ADDITIONAL_FIELDS-TRANSOptional: Yes
Call by Reference: No ( called with pass by value option)
TEST_RUN -
Data type: BAPI_RE_ADDITIONAL_FIELDS-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_RE_AT_CREATE
ADJUSTMENTTASKID -
Data type: BAPI_RE_ADJUST_TASK_KEY-ADJUSTMENT_TASK_IDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_RE_AT_CREATE
ADJUST_TASK_OBJ -
Data type: BAPI_RE_AT_OBJ_DATOptional: Yes
Call by Reference: Yes
EXTENSION_IN -
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
OBJ_ASSIGN -
Data type: BAPI_RE_OBJ_ASSIGN_DATOptional: Yes
Call by Reference: Yes
OBJECT_REL -
Data type: BAPI_RE_OBJECT_REL_DATOptional: Yes
Call by Reference: Yes
PARTNER -
Data type: BAPI_RE_PARTNER_DATOptional: Yes
Call by Reference: No ( called with pass by value option)
MEAS_CN -
Data type: BAPI_RE_MEAS_CN_DATOptional: Yes
Call by Reference: Yes
FINPLAN -
Data type: BAPI_RE_FINPLAN_DATOptional: Yes
Call by Reference: Yes
EXPENSE -
Data type: BAPI_RE_EXPENSE_DATOptional: Yes
Call by Reference: Yes
RESUBM_RULE -
Data type: BAPI_RE_RESUBM_RULE_DATOptional: Yes
Call by Reference: No ( called with pass by value option)
STATUS -
Data type: BAPI_RE_STATUS_DATOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_RE_AT_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: | ||||
| lt_adjust_task_obj | TYPE STANDARD TABLE OF BAPI_RE_AT_OBJ_DAT, " | |||
| lv_adjustmenttaskid | TYPE BAPI_RE_ADJUST_TASK_KEY-ADJUSTMENT_TASK_ID, " | |||
| lv_adjustment_task_id_ext | TYPE BAPI_RE_ADJUST_TASK_KEY-ADJUSTMENT_TASK_ID, " | |||
| lt_extension_in | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_obj_assign | TYPE STANDARD TABLE OF BAPI_RE_OBJ_ASSIGN_DAT, " | |||
| lv_adjust_task | TYPE BAPI_RE_ADJUST_TASK_DAT, " | |||
| lv_trans | TYPE BAPI_RE_ADDITIONAL_FIELDS-TRANS, " | |||
| lt_object_rel | TYPE STANDARD TABLE OF BAPI_RE_OBJECT_REL_DAT, " | |||
| lt_partner | TYPE STANDARD TABLE OF BAPI_RE_PARTNER_DAT, " | |||
| lv_test_run | TYPE BAPI_RE_ADDITIONAL_FIELDS-TESTRUN, " SPACE | |||
| lt_meas_cn | TYPE STANDARD TABLE OF BAPI_RE_MEAS_CN_DAT, " | |||
| lt_finplan | TYPE STANDARD TABLE OF BAPI_RE_FINPLAN_DAT, " | |||
| lt_expense | TYPE STANDARD TABLE OF BAPI_RE_EXPENSE_DAT, " | |||
| lt_resubm_rule | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE_DAT, " | |||
| lt_status | TYPE STANDARD TABLE OF BAPI_RE_STATUS_DAT. " |
|   CALL FUNCTION 'BAPI_RE_AT_CREATE' " |
| EXPORTING | ||
| ADJUSTMENT_TASK_ID_EXT | = lv_adjustment_task_id_ext | |
| ADJUST_TASK | = lv_adjust_task | |
| TRANS | = lv_trans | |
| TEST_RUN | = lv_test_run | |
| IMPORTING | ||
| ADJUSTMENTTASKID | = lv_adjustmenttaskid | |
| TABLES | ||
| ADJUST_TASK_OBJ | = lt_adjust_task_obj | |
| EXTENSION_IN | = lt_extension_in | |
| RETURN | = lt_return | |
| OBJ_ASSIGN | = lt_obj_assign | |
| OBJECT_REL | = lt_object_rel | |
| PARTNER | = lt_partner | |
| MEAS_CN | = lt_meas_cn | |
| FINPLAN | = lt_finplan | |
| EXPENSE | = lt_expense | |
| RESUBM_RULE | = lt_resubm_rule | |
| STATUS | = lt_status | |
| . " BAPI_RE_AT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_RE_AT_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 ADJUSTMENT_TASK_ID FROM BAPI_RE_ADJUST_TASK_KEY INTO @DATA(ld_adjustmenttaskid). | ||||
| "SELECT single ADJUSTMENT_TASK_ID FROM BAPI_RE_ADJUST_TASK_KEY INTO @DATA(ld_adjustment_task_id_ext). | ||||
| "SELECT single TRANS FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_trans). | ||||
| "SELECT single TESTRUN FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_test_run). | ||||
| DATA(ld_test_run) | = ' '. | |||
Search for further information about these or an SAP related objects