SAP BAPI_RESUB_EVENT_CREATE Function Module for BAPI: Create Resubmission Using Event
BAPI_RESUB_EVENT_CREATE is a standard bapi resub event 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: Create Resubmission Using Event 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 bapi resub event create FM, simply by entering the name BAPI_RESUB_EVENT_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_RESUB_BAPI
Program Name: SAPLFKK_RESUB_BAPI
Main Program: SAPLFKK_RESUB_BAPI
Appliation area:
Release date: 01-Aug-2016
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_RESUB_EVENT_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_RESUB_EVENT_CREATE'"BAPI: Create Resubmission Using Event.
EXPORTING
* RESUB_OBJ_CATEGORY_ID = 'BO' "Category of Objects in Persistent Object References
RESUB_OBJ_TYPE_ID = "Category of Objects in Persistent Object References
RESUB_OBJ_INSTANCE_ID = "Instance Ident. in BOR Compat. Persistent Object References
RESUB_DATE = "ABAP System Field: Current Date of Application Server
* RESUB_CREATED_BY = SY-UNAME "USer That Creates Resubmission
IMPORTING
EVENT_ID = "ID of an Event Instance
TABLES
* RESUB_TEXT = "Create Fields for Resubmission BAPI: Text
* RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_RESUB_EVENT_CREATE
RESUB_OBJ_CATEGORY_ID - Category of Objects in Persistent Object References
Data type: BAPICRRESUB-CATEGORY_IDDefault: 'BO'
Optional: Yes
Call by Reference: No ( called with pass by value option)
RESUB_OBJ_TYPE_ID - Category of Objects in Persistent Object References
Data type: BAPICRRESUB-TYPE_IDOptional: No
Call by Reference: No ( called with pass by value option)
RESUB_OBJ_INSTANCE_ID - Instance Ident. in BOR Compat. Persistent Object References
Data type: BAPICRRESUB-INSTANCE_IDOptional: No
Call by Reference: No ( called with pass by value option)
RESUB_DATE - ABAP System Field: Current Date of Application Server
Data type: BAPICRRESUB-DATEOptional: No
Call by Reference: No ( called with pass by value option)
RESUB_CREATED_BY - USer That Creates Resubmission
Data type: BAPICRRESUB-CREATED_BYDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_RESUB_EVENT_CREATE
EVENT_ID - ID of an Event Instance
Data type: BAPICRRESUB-EVENT_IDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_RESUB_EVENT_CREATE
RESUB_TEXT - Create Fields for Resubmission BAPI: Text
Data type: BAPICRRESUBTXTOptional: Yes
Call by Reference: Yes
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_RESUB_EVENT_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_event_id | TYPE BAPICRRESUB-EVENT_ID, " | |||
| lt_resub_text | TYPE STANDARD TABLE OF BAPICRRESUBTXT, " | |||
| lv_resub_obj_category_id | TYPE BAPICRRESUB-CATEGORY_ID, " 'BO' | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_resub_obj_type_id | TYPE BAPICRRESUB-TYPE_ID, " | |||
| lv_resub_obj_instance_id | TYPE BAPICRRESUB-INSTANCE_ID, " | |||
| lv_resub_date | TYPE BAPICRRESUB-DATE, " | |||
| lv_resub_created_by | TYPE BAPICRRESUB-CREATED_BY. " SY-UNAME |
| CALL FUNCTION 'BAPI_RESUB_EVENT_CREATE' "BAPI: Create Resubmission Using Event |
| EXPORTING | ||
| RESUB_OBJ_CATEGORY_ID | = lv_resub_obj_category_id | |
| RESUB_OBJ_TYPE_ID | = lv_resub_obj_type_id | |
| RESUB_OBJ_INSTANCE_ID | = lv_resub_obj_instance_id | |
| RESUB_DATE | = lv_resub_date | |
| RESUB_CREATED_BY | = lv_resub_created_by | |
| IMPORTING | ||
| EVENT_ID | = lv_event_id | |
| TABLES | ||
| RESUB_TEXT | = lt_resub_text | |
| RETURN | = lt_return | |
| . " BAPI_RESUB_EVENT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_RESUB_EVENT_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 EVENT_ID FROM BAPICRRESUB INTO @DATA(ld_event_id). | ||||
| "SELECT single CATEGORY_ID FROM BAPICRRESUB INTO @DATA(ld_resub_obj_category_id). | ||||
| DATA(ld_resub_obj_category_id) | = 'BO'. | |||
| "SELECT single TYPE_ID FROM BAPICRRESUB INTO @DATA(ld_resub_obj_type_id). | ||||
| "SELECT single INSTANCE_ID FROM BAPICRRESUB INTO @DATA(ld_resub_obj_instance_id). | ||||
| "SELECT single DATE FROM BAPICRRESUB INTO @DATA(ld_resub_date). | ||||
| "SELECT single CREATED_BY FROM BAPICRRESUB INTO @DATA(ld_resub_created_by). | ||||
| DATA(ld_resub_created_by) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects