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

Function LINK_INCOME_EXPENSE_MAIN 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 'LINK_INCOME_EXPENSE_MAIN'".
EXPORTING
IP_ACTION = "
IP_BUDAT = "
IP_BZDAT = "
IP_DOCTYP = "
IP_FIKRS = "Financial Management Area
* IP_FORECAST = ' ' "
IP_ITABKEY = "
IP_MANUELL = "
* IP_RECOVERY_ORDER = "
* IP_SENDER = "
IP_BUKRS = "
IMPORTING
OP_BUDGET_INCREASED = "
OP_CHANGED = "
EXCEPTIONS
FUNCTION_CANCEL = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLFMUD_001 Check Compatibility of Output Addresses for Cmmt Bdgt and Payment Budget
EXIT_SAPLFMUD_002 Do not use! Check whether the commitment budget is to be increased
EXIT_SAPLFMUD_003 Check Whether a Forecast Is Required
EXIT_SAPLFMUD_004 User-Specific Check of Expend. FM Acct Assgt for Cmmt Bdgt and Payt Bdgt
EXIT_SAPLFMUD_005 Do not use! Check whether the commitment budget is to be increased
EXIT_SAPLFMUD_006 Determine Value Type for which a Revenues FM Account Assgnt Increases Bdgt
IMPORTING Parameters details for LINK_INCOME_EXPENSE_MAIN
IP_ACTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IP_BUDAT -
Data type: COBL-BUDATOptional: No
Call by Reference: No ( called with pass by value option)
IP_BZDAT -
Data type: COBL-BZDATOptional: No
Call by Reference: No ( called with pass by value option)
IP_DOCTYP -
Data type: BKPF-BLARTOptional: No
Call by Reference: No ( called with pass by value option)
IP_FIKRS - Financial Management Area
Data type: FM01-FIKRSOptional: No
Call by Reference: No ( called with pass by value option)
IP_FORECAST -
Data type: FMUD_FCDOCDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IP_ITABKEY -
Data type: IFMUDECK-ITABKEYOptional: No
Call by Reference: No ( called with pass by value option)
IP_MANUELL -
Data type: FMDY-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
IP_RECOVERY_ORDER -
Data type: FMUD_RODOCOptional: Yes
Call by Reference: No ( called with pass by value option)
IP_SENDER -
Data type: FMUD_HOLDEROptional: Yes
Call by Reference: No ( called with pass by value option)
IP_BUKRS -
Data type: COBL-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LINK_INCOME_EXPENSE_MAIN
OP_BUDGET_INCREASED -
Data type: FMDY-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
OP_CHANGED -
Data type: FMDY-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FUNCTION_CANCEL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LINK_INCOME_EXPENSE_MAIN 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_ip_action | TYPE STRING, " | |||
| lv_function_cancel | TYPE STRING, " | |||
| lv_op_budget_increased | TYPE FMDY-XFELD, " | |||
| lv_ip_budat | TYPE COBL-BUDAT, " | |||
| lv_ip_bzdat | TYPE COBL-BZDAT, " | |||
| lv_ip_doctyp | TYPE BKPF-BLART, " | |||
| lv_op_changed | TYPE FMDY-XFELD, " | |||
| lv_ip_fikrs | TYPE FM01-FIKRS, " | |||
| lv_ip_forecast | TYPE FMUD_FCDOC, " SPACE | |||
| lv_ip_itabkey | TYPE IFMUDECK-ITABKEY, " | |||
| lv_ip_manuell | TYPE FMDY-XFELD, " | |||
| lv_ip_recovery_order | TYPE FMUD_RODOC, " | |||
| lv_ip_sender | TYPE FMUD_HOLDER, " | |||
| lv_ip_bukrs | TYPE COBL-BUKRS. " |
|   CALL FUNCTION 'LINK_INCOME_EXPENSE_MAIN' " |
| EXPORTING | ||
| IP_ACTION | = lv_ip_action | |
| IP_BUDAT | = lv_ip_budat | |
| IP_BZDAT | = lv_ip_bzdat | |
| IP_DOCTYP | = lv_ip_doctyp | |
| IP_FIKRS | = lv_ip_fikrs | |
| IP_FORECAST | = lv_ip_forecast | |
| IP_ITABKEY | = lv_ip_itabkey | |
| IP_MANUELL | = lv_ip_manuell | |
| IP_RECOVERY_ORDER | = lv_ip_recovery_order | |
| IP_SENDER | = lv_ip_sender | |
| IP_BUKRS | = lv_ip_bukrs | |
| IMPORTING | ||
| OP_BUDGET_INCREASED | = lv_op_budget_increased | |
| OP_CHANGED | = lv_op_changed | |
| EXCEPTIONS | ||
| FUNCTION_CANCEL = 1 | ||
| . " LINK_INCOME_EXPENSE_MAIN | ||
ABAP code using 7.40 inline data declarations to call FM LINK_INCOME_EXPENSE_MAIN
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 XFELD FROM FMDY INTO @DATA(ld_op_budget_increased). | ||||
| "SELECT single BUDAT FROM COBL INTO @DATA(ld_ip_budat). | ||||
| "SELECT single BZDAT FROM COBL INTO @DATA(ld_ip_bzdat). | ||||
| "SELECT single BLART FROM BKPF INTO @DATA(ld_ip_doctyp). | ||||
| "SELECT single XFELD FROM FMDY INTO @DATA(ld_op_changed). | ||||
| "SELECT single FIKRS FROM FM01 INTO @DATA(ld_ip_fikrs). | ||||
| DATA(ld_ip_forecast) | = ' '. | |||
| "SELECT single ITABKEY FROM IFMUDECK INTO @DATA(ld_ip_itabkey). | ||||
| "SELECT single XFELD FROM FMDY INTO @DATA(ld_ip_manuell). | ||||
| "SELECT single BUKRS FROM COBL INTO @DATA(ld_ip_bukrs). | ||||
Search for further information about these or an SAP related objects