SAP FEB_BSPROC_FB05_INTERF_PREPARE Function Module for









FEB_BSPROC_FB05_INTERF_PREPARE is a standard feb bsproc fb05 interf prepare 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 feb bsproc fb05 interf prepare FM, simply by entering the name FEB_BSPROC_FB05_INTERF_PREPARE into the relevant SAP transaction such as SE37 or SE38.

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



Function FEB_BSPROC_FB05_INTERF_PREPARE 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 'FEB_BSPROC_FB05_INTERF_PREPARE'"
EXPORTING
IS_BKPF = "
* IS_IKOFI = "
* I_POSTING_AREA = "
IT_FEBRE = "
IT_FEBCL = "
IT_BSEG = "
IX_RST = "
IT_OPEN_ITEM_CLR = "
IX_SAVE_DRAFT = "
* I_AUGLV = 'EINGZAHL' "
* I_TCODE = 'FB05' "
IS_FEBKO = "
IS_FEBEP = "

IMPORTING
ET_FTCLEAR = "
ET_FTPOST = "
ET_FTTAX = "
E_AVSID = "
ES_BAPIRET2 = "
ES_ADVICE_KEY = "
.



IMPORTING Parameters details for FEB_BSPROC_FB05_INTERF_PREPARE

IS_BKPF -

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

IS_IKOFI -

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

I_POSTING_AREA -

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

IT_FEBRE -

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

IT_FEBCL -

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

IT_BSEG -

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

IX_RST -

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

IT_OPEN_ITEM_CLR -

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

IX_SAVE_DRAFT -

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

I_AUGLV -

Data type: T041A-AUGLV
Default: 'EINGZAHL'
Optional: No
Call by Reference: Yes

I_TCODE -

Data type: SY-TCODE
Default: 'FB05'
Optional: No
Call by Reference: Yes

IS_FEBKO -

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

IS_FEBEP -

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

EXPORTING Parameters details for FEB_BSPROC_FB05_INTERF_PREPARE

ET_FTCLEAR -

Data type: ANY TABLE
Optional: No
Call by Reference: Yes

ET_FTPOST -

Data type: ANY TABLE
Optional: No
Call by Reference: Yes

ET_FTTAX -

Data type: ANY TABLE
Optional: No
Call by Reference: Yes

E_AVSID -

Data type: AVIK-AVSID
Optional: No
Call by Reference: Yes

ES_BAPIRET2 -

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

ES_ADVICE_KEY -

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

Copy and paste ABAP code example for FEB_BSPROC_FB05_INTERF_PREPARE 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_bkpf  TYPE BKPF, "   
lv_et_ftclear  TYPE ANY TABLE, "   
lv_is_ikofi  TYPE IKOFI, "   
lv_i_posting_area  TYPE POSAR_BF, "   
lv_it_febre  TYPE FEB_T_FEBRE, "   
lv_it_febcl  TYPE FEB_T_FEBCL, "   
lv_it_bseg  TYPE FEB_T_BSEG, "   
lv_et_ftpost  TYPE ANY TABLE, "   
lv_ix_rst  TYPE FEB_BSPROC_RESID, "   
lv_et_fttax  TYPE ANY TABLE, "   
lv_e_avsid  TYPE AVIK-AVSID, "   
lv_it_open_item_clr  TYPE FEB_T_BSPROC_OPEN_ITEM_CLR, "   
lv_es_bapiret2  TYPE BAPIRET2, "   
lv_ix_save_draft  TYPE FEB_BSPROC_SAVE_DRAFT, "   
lv_i_auglv  TYPE T041A-AUGLV, "   'EINGZAHL'
lv_es_advice_key  TYPE FEB_BSPROC_ADVICE_KEY, "   
lv_i_tcode  TYPE SY-TCODE, "   'FB05'
lv_is_febko  TYPE FEBKO, "   
lv_is_febep  TYPE FEBEP. "   

  CALL FUNCTION 'FEB_BSPROC_FB05_INTERF_PREPARE'  "
    EXPORTING
         IS_BKPF = lv_is_bkpf
         IS_IKOFI = lv_is_ikofi
         I_POSTING_AREA = lv_i_posting_area
         IT_FEBRE = lv_it_febre
         IT_FEBCL = lv_it_febcl
         IT_BSEG = lv_it_bseg
         IX_RST = lv_ix_rst
         IT_OPEN_ITEM_CLR = lv_it_open_item_clr
         IX_SAVE_DRAFT = lv_ix_save_draft
         I_AUGLV = lv_i_auglv
         I_TCODE = lv_i_tcode
         IS_FEBKO = lv_is_febko
         IS_FEBEP = lv_is_febep
    IMPORTING
         ET_FTCLEAR = lv_et_ftclear
         ET_FTPOST = lv_et_ftpost
         ET_FTTAX = lv_et_fttax
         E_AVSID = lv_e_avsid
         ES_BAPIRET2 = lv_es_bapiret2
         ES_ADVICE_KEY = lv_es_advice_key
. " FEB_BSPROC_FB05_INTERF_PREPARE




ABAP code using 7.40 inline data declarations to call FM FEB_BSPROC_FB05_INTERF_PREPARE

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 AVSID FROM AVIK INTO @DATA(ld_e_avsid).
 
 
 
 
"SELECT single AUGLV FROM T041A INTO @DATA(ld_i_auglv).
DATA(ld_i_auglv) = 'EINGZAHL'.
 
 
"SELECT single TCODE FROM SY INTO @DATA(ld_i_tcode).
DATA(ld_i_tcode) = 'FB05'.
 
 
 


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!