SAP FEUI_CD_INCOME_EXPENSE Function Module for
FEUI_CD_INCOME_EXPENSE is a standard feui cd income expense 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 feui cd income expense FM, simply by entering the name FEUI_CD_INCOME_EXPENSE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FEUI
Program Name: SAPLFEUI
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FEUI_CD_INCOME_EXPENSE 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 'FEUI_CD_INCOME_EXPENSE'".
EXPORTING
I_BELNR = "
* I_TCTYPE = "
I_OLDNEW = "O = Old values, N = New values
IMPORTING
OBJECTID = "
TCODE = "
UTIME = "
UDATE = "
USERNAME = "
UPD_FMUDKBLP = "
PLANNED_CHANGE_NUMBER = "
OBJECT_CHANGE_INDICAT = "
PLANNED_OR_REAL_CHANG = "
TABLES
T_FMUDKBLP = "
YFMUDKBLP = "
XFMUDKBLP = "
EXCEPTIONS
NEITHER_OLD_NOR_NEW = 1
IMPORTING Parameters details for FEUI_CD_INCOME_EXPENSE
I_BELNR -
Data type: KBLK-BELNROptional: No
Call by Reference: No ( called with pass by value option)
I_TCTYPE -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_OLDNEW - O = Old values, N = New values
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FEUI_CD_INCOME_EXPENSE
OBJECTID -
Data type: CDHDR-OBJECTIDOptional: No
Call by Reference: No ( called with pass by value option)
TCODE -
Data type: CDHDR-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
UTIME -
Data type: CDHDR-UTIMEOptional: No
Call by Reference: No ( called with pass by value option)
UDATE -
Data type: CDHDR-UDATEOptional: No
Call by Reference: No ( called with pass by value option)
USERNAME -
Data type: CDHDR-USERNAMEOptional: No
Call by Reference: No ( called with pass by value option)
UPD_FMUDKBLP -
Data type: CDPOS-CHNGINDOptional: No
Call by Reference: No ( called with pass by value option)
PLANNED_CHANGE_NUMBER -
Data type: CDHDR-PLANCHNGNROptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_CHANGE_INDICAT -
Data type: CDHDR-CHANGE_INDOptional: No
Call by Reference: No ( called with pass by value option)
PLANNED_OR_REAL_CHANG -
Data type: CDHDR-CHANGE_INDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FEUI_CD_INCOME_EXPENSE
T_FMUDKBLP -
Data type: FMUDKBLPOptional: No
Call by Reference: No ( called with pass by value option)
YFMUDKBLP -
Data type: CFMUDKBLPOptional: No
Call by Reference: No ( called with pass by value option)
XFMUDKBLP -
Data type: CFMUDKBLPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NEITHER_OLD_NOR_NEW -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FEUI_CD_INCOME_EXPENSE 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_belnr | TYPE KBLK-BELNR, " | |||
| lv_objectid | TYPE CDHDR-OBJECTID, " | |||
| lt_t_fmudkblp | TYPE STANDARD TABLE OF FMUDKBLP, " | |||
| lv_neither_old_nor_new | TYPE FMUDKBLP, " | |||
| lv_tcode | TYPE CDHDR-TCODE, " | |||
| lv_i_tctype | TYPE CDHDR, " | |||
| lt_yfmudkblp | TYPE STANDARD TABLE OF CFMUDKBLP, " | |||
| lv_utime | TYPE CDHDR-UTIME, " | |||
| lv_i_oldnew | TYPE CDHDR, " | |||
| lt_xfmudkblp | TYPE STANDARD TABLE OF CFMUDKBLP, " | |||
| lv_udate | TYPE CDHDR-UDATE, " | |||
| lv_username | TYPE CDHDR-USERNAME, " | |||
| lv_upd_fmudkblp | TYPE CDPOS-CHNGIND, " | |||
| lv_planned_change_number | TYPE CDHDR-PLANCHNGNR, " | |||
| lv_object_change_indicat | TYPE CDHDR-CHANGE_IND, " | |||
| lv_planned_or_real_chang | TYPE CDHDR-CHANGE_IND. " |
|   CALL FUNCTION 'FEUI_CD_INCOME_EXPENSE' " |
| EXPORTING | ||
| I_BELNR | = lv_i_belnr | |
| I_TCTYPE | = lv_i_tctype | |
| I_OLDNEW | = lv_i_oldnew | |
| IMPORTING | ||
| OBJECTID | = lv_objectid | |
| TCODE | = lv_tcode | |
| UTIME | = lv_utime | |
| UDATE | = lv_udate | |
| USERNAME | = lv_username | |
| UPD_FMUDKBLP | = lv_upd_fmudkblp | |
| PLANNED_CHANGE_NUMBER | = lv_planned_change_number | |
| OBJECT_CHANGE_INDICAT | = lv_object_change_indicat | |
| PLANNED_OR_REAL_CHANG | = lv_planned_or_real_chang | |
| TABLES | ||
| T_FMUDKBLP | = lt_t_fmudkblp | |
| YFMUDKBLP | = lt_yfmudkblp | |
| XFMUDKBLP | = lt_xfmudkblp | |
| EXCEPTIONS | ||
| NEITHER_OLD_NOR_NEW = 1 | ||
| . " FEUI_CD_INCOME_EXPENSE | ||
ABAP code using 7.40 inline data declarations to call FM FEUI_CD_INCOME_EXPENSE
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 BELNR FROM KBLK INTO @DATA(ld_i_belnr). | ||||
| "SELECT single OBJECTID FROM CDHDR INTO @DATA(ld_objectid). | ||||
| "SELECT single TCODE FROM CDHDR INTO @DATA(ld_tcode). | ||||
| "SELECT single UTIME FROM CDHDR INTO @DATA(ld_utime). | ||||
| "SELECT single UDATE FROM CDHDR INTO @DATA(ld_udate). | ||||
| "SELECT single USERNAME FROM CDHDR INTO @DATA(ld_username). | ||||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_fmudkblp). | ||||
| "SELECT single PLANCHNGNR FROM CDHDR INTO @DATA(ld_planned_change_number). | ||||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_object_change_indicat). | ||||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_planned_or_real_chang). | ||||
Search for further information about these or an SAP related objects