SAP ISV_EVENT_5030 Function Module for EXTERNAL: Add Account Assignment Data
ISV_EVENT_5030 is a standard isv event 5030 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EXTERNAL: Add Account Assignment Data 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 isv event 5030 FM, simply by entering the name ISV_EVENT_5030 into the relevant SAP transaction such as SE37 or SE38.
Function Group: VKA1
Program Name: SAPLVKA1
Main Program: SAPLVKA1
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISV_EVENT_5030 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 'ISV_EVENT_5030'"EXTERNAL: Add Account Assignment Data.
EXPORTING
* I_FKKKO = "Header Data for Open Item Accounting Document
* I_COKEY = "FI-CA: CO Account Assignment Key
* I_HVORG = "External Main Transaction
* I_TVORG = "External Subtransaction
* I_FKKCL = "Selected Items for Write-Off
* I_XCOAC = ' ' "Add or Determine CO Account Assignments
* I_XFMAC = ' ' "FM Account Assignment Derivation for Write-off
* I_XINH = ' ' "Transfer G/L Account from Items to be Written Off
CHANGING
C_FKKOPK = "Offsetting Item Created
TABLES
* T_FKKOPK = "G/L Account Items in Open Item Account Document
IMPORTING Parameters details for ISV_EVENT_5030
I_FKKKO - Header Data for Open Item Accounting Document
Data type: FKKKOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_COKEY - FI-CA: CO Account Assignment Key
Data type: TFKCOD-COKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_HVORG - External Main Transaction
Data type: TFKHVO-HVORGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TVORG - External Subtransaction
Data type: TFKTVO-TVORGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FKKCL - Selected Items for Write-Off
Data type: FKKCLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_XCOAC - Add or Determine CO Account Assignments
Data type: RFKA1-XCOACDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_XFMAC - FM Account Assignment Derivation for Write-off
Data type: RFKA1-XFMACDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_XINH - Transfer G/L Account from Items to be Written Off
Data type: RFKA1-XINHDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ISV_EVENT_5030
C_FKKOPK - Offsetting Item Created
Data type: FKKOPKOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISV_EVENT_5030
T_FKKOPK - G/L Account Items in Open Item Account Document
Data type: FKKOPKOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISV_EVENT_5030 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_i_fkkko | TYPE FKKKO, " | |||
| lv_c_fkkopk | TYPE FKKOPK, " | |||
| lt_t_fkkopk | TYPE STANDARD TABLE OF FKKOPK, " | |||
| lv_i_cokey | TYPE TFKCOD-COKEY, " | |||
| lv_i_hvorg | TYPE TFKHVO-HVORG, " | |||
| lv_i_tvorg | TYPE TFKTVO-TVORG, " | |||
| lv_i_fkkcl | TYPE FKKCL, " | |||
| lv_i_xcoac | TYPE RFKA1-XCOAC, " SPACE | |||
| lv_i_xfmac | TYPE RFKA1-XFMAC, " SPACE | |||
| lv_i_xinh | TYPE RFKA1-XINH. " SPACE |
|   CALL FUNCTION 'ISV_EVENT_5030' "EXTERNAL: Add Account Assignment Data |
| EXPORTING | ||
| I_FKKKO | = lv_i_fkkko | |
| I_COKEY | = lv_i_cokey | |
| I_HVORG | = lv_i_hvorg | |
| I_TVORG | = lv_i_tvorg | |
| I_FKKCL | = lv_i_fkkcl | |
| I_XCOAC | = lv_i_xcoac | |
| I_XFMAC | = lv_i_xfmac | |
| I_XINH | = lv_i_xinh | |
| CHANGING | ||
| C_FKKOPK | = lv_c_fkkopk | |
| TABLES | ||
| T_FKKOPK | = lt_t_fkkopk | |
| . " ISV_EVENT_5030 | ||
ABAP code using 7.40 inline data declarations to call FM ISV_EVENT_5030
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 COKEY FROM TFKCOD INTO @DATA(ld_i_cokey). | ||||
| "SELECT single HVORG FROM TFKHVO INTO @DATA(ld_i_hvorg). | ||||
| "SELECT single TVORG FROM TFKTVO INTO @DATA(ld_i_tvorg). | ||||
| "SELECT single XCOAC FROM RFKA1 INTO @DATA(ld_i_xcoac). | ||||
| DATA(ld_i_xcoac) | = ' '. | |||
| "SELECT single XFMAC FROM RFKA1 INTO @DATA(ld_i_xfmac). | ||||
| DATA(ld_i_xfmac) | = ' '. | |||
| "SELECT single XINH FROM RFKA1 INTO @DATA(ld_i_xinh). | ||||
| DATA(ld_i_xinh) | = ' '. | |||
Search for further information about these or an SAP related objects