LINK_INCOME_EXPENSE_BUDGETDOC SAP Function module

LINK_INCOME_EXPENSE_BUDGETDOC is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name LINK_INCOME_EXPENSE_BUDGETDOC into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FMUD
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM LINK_INCOME_EXPENSE_BUDGETDOC - LINK INCOME EXPENSE BUDGETDOC

CALL FUNCTION 'LINK_INCOME_EXPENSE_BUDGETDOC' "
  EXPORTING
    ip_buart =                  " fmudbsegp-buart
    ip_doctyp =                 " bkpf-blart
    ip_fikrs =                  " fm01-fikrs    Financial Management Area
*   ip_forecast = SPACE         " fmud_fcdoc
    ip_gjahr =                  " bseg-gjahr
    ip_receiver =               " fmud_holder
*   ip_recovery_order =         " fmud_rodoc
*   ip_sender =                 " fmud_holder
    .  "  LINK_INCOME_EXPENSE_BUDGETDOC

ABAP code example for Function Module LINK_INCOME_EXPENSE_BUDGETDOC

The ABAP code below is a full code listing to execute function module LINK_INCOME_EXPENSE_BUDGETDOC including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

 

SELECT single BUART 
  FROM FMUDBSEGP 
  INTO @DATA(ld_ip_buart).

 

SELECT single BLART 
  FROM BKPF 
  INTO @DATA(ld_ip_doctyp).

 

SELECT single FIKRS 
  FROM FM01 
  INTO @DATA(ld_ip_fikrs).


DATA(ld_ip_forecast) = 'Check type of data required'.
 

SELECT single GJAHR 
  FROM BSEG 
  INTO @DATA(ld_ip_gjahr).


DATA(ld_ip_receiver) = 'Check type of data required'.

DATA(ld_ip_recovery_order) = 'Check type of data required'.

DATA(ld_ip_sender) = 'Check type of data required'.
.

CALL FUNCTION 'LINK_INCOME_EXPENSE_BUDGETDOC'
  EXPORTING
    ip_buart =                   ld_ip_buart
    ip_doctyp =                  ld_ip_doctyp
    ip_fikrs =                   ld_ip_fikrs
*   ip_forecast =                ld_ip_forecast
    ip_gjahr =                   ld_ip_gjahr
    ip_receiver =                ld_ip_receiver
*   ip_recovery_order =          ld_ip_recovery_order
*   ip_sender =                  ld_ip_sender
    .  "  LINK_INCOME_EXPENSE_BUDGETDOC

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ip_buart
 
 TYPE FMUDBSEGP-BUART ,
ld_ip_doctyp
 
 TYPE BKPF-BLART ,
ld_ip_fikrs
 
 TYPE FM01-FIKRS ,
ld_ip_forecast
 
 TYPE FMUD_FCDOC ,
ld_ip_gjahr
 
 TYPE BSEG-GJAHR ,
ld_ip_receiver
 
 TYPE FMUD_HOLDER ,
ld_ip_recovery_order
 
 TYPE FMUD_RODOC ,
ld_ip_sender
 
 TYPE FMUD_HOLDER .



SELECT single BUART 
  FROM FMUDBSEGP 
  INTO ld_ip_buart.


SELECT single BLART 
  FROM BKPF 
  INTO ld_ip_doctyp.


SELECT single FIKRS 
  FROM FM01 
  INTO ld_ip_fikrs.

ld_ip_forecast = 'Check type of data required'.

SELECT single GJAHR 
  FROM BSEG 
  INTO ld_ip_gjahr.

ld_ip_receiver = 'Check type of data required'.
ld_ip_recovery_order = 'Check type of data required'.
ld_ip_sender = 'Check type of data required'.