FM_LEDGER_VBUND_FLAG_SET SAP Function module - Set trading partner ID flag and federal/non-federal flag

FM_LEDGER_VBUND_FLAG_SET 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 FM_LEDGER_VBUND_FLAG_SET into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM FM_LEDGER_VBUND_FLAG_SET - FM LEDGER VBUND FLAG SET

CALL FUNCTION 'FM_LEDGER_VBUND_FLAG_SET' "Set trading partner ID flag and federal/non-federal flag
* EXPORTING
*   i_lifnr =                   " lfa1-lifnr    Account number of vendor or creditor
*   i_kunnr =                   " kna1-kunnr    Customer number
*   i_saknr =                   " ska1-saknr    G/L account number
*   i_bukrs =                   " t001-bukrs    Company Code
*   i_derive_flg =              " xfeld         Checkbox
* CHANGING
*   c_vbund_flg =               " ifmblin-vbund_flg  FM Trading partner (VBUND) flag for budgetary ledger
*   c_trade_id =                " ifmblin-trade_id  Company ID of trading partner
    .  "  FM_LEDGER_VBUND_FLAG_SET

ABAP code example for Function Module FM_LEDGER_VBUND_FLAG_SET

The ABAP code below is a full code listing to execute function module FM_LEDGER_VBUND_FLAG_SET 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).

DATA(ld_c_vbund_flg) = some text here


DATA(ld_c_trade_id) = some text here
 

SELECT single LIFNR 
  FROM LFA1 
  INTO @DATA(ld_i_lifnr).

 

SELECT single KUNNR 
  FROM KNA1 
  INTO @DATA(ld_i_kunnr).

 

SELECT single SAKNR 
  FROM SKA1 
  INTO @DATA(ld_i_saknr).

 

SELECT single BUKRS 
  FROM T001 
  INTO @DATA(ld_i_bukrs).


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

CALL FUNCTION 'FM_LEDGER_VBUND_FLAG_SET'
* EXPORTING
*   i_lifnr =                    ld_i_lifnr
*   i_kunnr =                    ld_i_kunnr
*   i_saknr =                    ld_i_saknr
*   i_bukrs =                    ld_i_bukrs
*   i_derive_flg =               ld_i_derive_flg
* CHANGING
*   c_vbund_flg =                ld_c_vbund_flg
*   c_trade_id =                 ld_c_trade_id
    .  "  FM_LEDGER_VBUND_FLAG_SET

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_c_vbund_flg
 
 TYPE IFMBLIN-VBUND_FLG ,
ld_i_lifnr
 
 TYPE LFA1-LIFNR ,
ld_c_trade_id
 
 TYPE IFMBLIN-TRADE_ID ,
ld_i_kunnr
 
 TYPE KNA1-KUNNR ,
ld_i_saknr
 
 TYPE SKA1-SAKNR ,
ld_i_bukrs
 
 TYPE T001-BUKRS ,
ld_i_derive_flg
 
 TYPE XFELD .



ld_c_vbund_flg = some text here

SELECT single LIFNR 
  FROM LFA1 
  INTO ld_i_lifnr.


ld_c_trade_id = some text here

SELECT single KUNNR 
  FROM KNA1 
  INTO ld_i_kunnr.


SELECT single SAKNR 
  FROM SKA1 
  INTO ld_i_saknr.


SELECT single BUKRS 
  FROM T001 
  INTO ld_i_bukrs.

ld_i_derive_flg = 'Check type of data required'.