SAP J_1BNFE_EVENT_UPDATE Function Module for Update event table
J_1BNFE_EVENT_UPDATE is a standard j 1bnfe event update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update event table 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 j 1bnfe event update FM, simply by entering the name J_1BNFE_EVENT_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: J_1B_NFE_EVENT
Program Name: SAPLJ_1B_NFE_EVENT
Main Program: SAPLJ_1B_NFE_EVENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function J_1BNFE_EVENT_UPDATE 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 'J_1BNFE_EVENT_UPDATE'"Update event table.
EXPORTING
IS_EVENT_COMMON = "NF-e Events Table
IV_UPDMODE = "Single-Character Indicator
* IS_CCE = "NF-e CCe Table
IMPORTING Parameters details for J_1BNFE_EVENT_UPDATE
IS_EVENT_COMMON - NF-e Events Table
Data type: J_1BNFE_EVENTOptional: No
Call by Reference: No ( called with pass by value option)
IV_UPDMODE - Single-Character Indicator
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
IS_CCE - NF-e CCe Table
Data type: J_1BNFE_CCEOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_1BNFE_EVENT_UPDATE 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_is_event_common | TYPE J_1BNFE_EVENT, " | |||
| lv_iv_updmode | TYPE CHAR1, " | |||
| lv_is_cce | TYPE J_1BNFE_CCE. " |
|   CALL FUNCTION 'J_1BNFE_EVENT_UPDATE' "Update event table |
| EXPORTING | ||
| IS_EVENT_COMMON | = lv_is_event_common | |
| IV_UPDMODE | = lv_iv_updmode | |
| IS_CCE | = lv_is_cce | |
| . " J_1BNFE_EVENT_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM J_1BNFE_EVENT_UPDATE
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.Search for further information about these or an SAP related objects