SAP BS_TRANSFER_POST Function Module for Balance Sheet Transfer for Loan









BS_TRANSFER_POST is a standard bs transfer post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Balance Sheet Transfer for Loan 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 bs transfer post FM, simply by entering the name BS_TRANSFER_POST into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVVD_BSTR
Program Name: SAPLFVVD_BSTR
Main Program: SAPLFVVD_BSTR
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BS_TRANSFER_POST 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 'BS_TRANSFER_POST'"Balance Sheet Transfer for Loan
  EXPORTING
   IS_VDARL =  "
*  I_TRANSFER_TA = ' ' "
   IS_VDKOREF =  "Worklist File for Bal. Sheet Transfer / Acct Assignment Ref.
*  IS_VDDEBTTRANS =  "Daten des Schuldnerwechsels
*  I_FLG_DEBTTRANSFER = ' ' "' X' = Aufruf aus Schuldnerwechsel
*  I_SUPERPRIMANOTA = ' ' "Super prima nota for grouping in autom.deb.pos.
   I_BKTXT =  "
*  I_PROTOCOL = '1' "Single-Character Flag
   I_SIMU =  "Single-Character Flag
*  I_STOGR =  "

 IMPORTING
   E_FLAG_NO_TP =  "Single-Character Flag

EXCEPTIONS
   POSTING_IMPOSSIBLE = 1
.



IMPORTING Parameters details for BS_TRANSFER_POST

IS_VDARL -

Data type: VDARL
Optional: No
Call by Reference: Yes

I_TRANSFER_TA -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

IS_VDKOREF - Worklist File for Bal. Sheet Transfer / Acct Assignment Ref.

Data type: VDKOREF
Optional: No
Call by Reference: Yes

IS_VDDEBTTRANS - Daten des Schuldnerwechsels

Data type: VDDEBTTRANS
Optional: Yes
Call by Reference: Yes

I_FLG_DEBTTRANSFER - ' X' = Aufruf aus Schuldnerwechsel

Data type: CHAR1
Default: ' '
Optional: Yes
Call by Reference: Yes

I_SUPERPRIMANOTA - Super prima nota for grouping in autom.deb.pos.

Data type: VVRPNSUP
Default: ' '
Optional: Yes
Call by Reference: Yes

I_BKTXT -

Data type: BKPF-BKTXT
Optional: No
Call by Reference: Yes

I_PROTOCOL - Single-Character Flag

Data type: CHAR1
Default: '1'
Optional: Yes
Call by Reference: Yes

I_SIMU - Single-Character Flag

Data type: CHAR1
Optional: No
Call by Reference: Yes

I_STOGR -

Data type: VDBEKI-SSTOGRD
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BS_TRANSFER_POST

E_FLAG_NO_TP - Single-Character Flag

Data type: CHAR1
Optional: No
Call by Reference: Yes

EXCEPTIONS details

POSTING_IMPOSSIBLE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BS_TRANSFER_POST 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_is_vdarl  TYPE VDARL, "   
lv_e_flag_no_tp  TYPE CHAR1, "   
lv_posting_impossible  TYPE CHAR1, "   
lv_i_transfer_ta  TYPE XFELD, "   SPACE
lv_is_vdkoref  TYPE VDKOREF, "   
lv_is_vddebttrans  TYPE VDDEBTTRANS, "   
lv_i_flg_debttransfer  TYPE CHAR1, "   ' '
lv_i_superprimanota  TYPE VVRPNSUP, "   ' '
lv_i_bktxt  TYPE BKPF-BKTXT, "   
lv_i_protocol  TYPE CHAR1, "   '1'
lv_i_simu  TYPE CHAR1, "   
lv_i_stogr  TYPE VDBEKI-SSTOGRD. "   

  CALL FUNCTION 'BS_TRANSFER_POST'  "Balance Sheet Transfer for Loan
    EXPORTING
         IS_VDARL = lv_is_vdarl
         I_TRANSFER_TA = lv_i_transfer_ta
         IS_VDKOREF = lv_is_vdkoref
         IS_VDDEBTTRANS = lv_is_vddebttrans
         I_FLG_DEBTTRANSFER = lv_i_flg_debttransfer
         I_SUPERPRIMANOTA = lv_i_superprimanota
         I_BKTXT = lv_i_bktxt
         I_PROTOCOL = lv_i_protocol
         I_SIMU = lv_i_simu
         I_STOGR = lv_i_stogr
    IMPORTING
         E_FLAG_NO_TP = lv_e_flag_no_tp
    EXCEPTIONS
        POSTING_IMPOSSIBLE = 1
. " BS_TRANSFER_POST




ABAP code using 7.40 inline data declarations to call FM BS_TRANSFER_POST

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.

 
 
 
DATA(ld_i_transfer_ta) = ' '.
 
 
 
DATA(ld_i_flg_debttransfer) = ' '.
 
DATA(ld_i_superprimanota) = ' '.
 
"SELECT single BKTXT FROM BKPF INTO @DATA(ld_i_bktxt).
 
DATA(ld_i_protocol) = '1'.
 
 
"SELECT single SSTOGRD FROM VDBEKI INTO @DATA(ld_i_stogr).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!