SAP Function Modules

comments icon Comments

REAL_ESTATE_DOCUMENTS SAP Function module







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

Associated Function Group: FVI4
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM REAL_ESTATE_DOCUMENTS - REAL ESTATE DOCUMENTS 





CALL FUNCTION 'REAL_ESTATE_DOCUMENTS' "
* EXPORTING
*   flg_soll_id = ' '           "
*   posting_var = '    '        " vislid-svorg
*   protokoll = 'X'             "
*   sammelbuchung = ' '         "
*   simulation = ' '            "
*   imp_vislid = ' '            " vislid
*   imp_sxblnr = ' '            " vibepp-sxblnr
*   imp_lfdnr = 0               " i
*   do_not_clear_tab = ' '      "
  IMPORTING
    exp_vislid =                " vislid        Flow records
    exp_can_commit =            "
    exp_lfdnr =                 " i
  TABLES
    fehler =                    " sprot_u       Flow records
    tbssbkpf =                  " bssbkpf       Document header
    tbssbseg =                  " bssbseg       Line Items
    tbsspara =                  " bsspara
    tvibepp =                   " rvibepp       Flow records
*   tvibepp_mod =               " rvibepp
  EXCEPTIONS
    NO_EXTBELNR = 1             "               Flow records
    .  "  REAL_ESTATE_DOCUMENTS

ABAP code example for Function Module REAL_ESTATE_DOCUMENTS





The ABAP code below is a full code listing to execute function module REAL_ESTATE_DOCUMENTS 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_exp_vislid    TYPE VISLID
,
ld_exp_can_commit    TYPE STRING
,
ld_exp_lfdnr    TYPE I
,
it_fehler    TYPE STANDARD TABLE OF SPROT_U,"TABLES PARAM
wa_fehler  LIKE LINE OF it_fehler
,
it_tbssbkpf    TYPE STANDARD TABLE OF BSSBKPF,"TABLES PARAM
wa_tbssbkpf  LIKE LINE OF it_tbssbkpf
,
it_tbssbseg    TYPE STANDARD TABLE OF BSSBSEG,"TABLES PARAM
wa_tbssbseg  LIKE LINE OF it_tbssbseg
,
it_tbsspara    TYPE STANDARD TABLE OF BSSPARA,"TABLES PARAM
wa_tbsspara  LIKE LINE OF it_tbsspara
,
it_tvibepp    TYPE STANDARD TABLE OF RVIBEPP,"TABLES PARAM
wa_tvibepp  LIKE LINE OF it_tvibepp
,
it_tvibepp_mod    TYPE STANDARD TABLE OF RVIBEPP,"TABLES PARAM
wa_tvibepp_mod  LIKE LINE OF it_tvibepp_mod
.




DATA(ld_flg_soll_id) = 'some text here'.
 

SELECT single SVORG 
  FROM VISLID 
  INTO @DATA(ld_posting_var).


DATA(ld_protokoll) = 'some text here'.

DATA(ld_sammelbuchung) = 'some text here'.

DATA(ld_simulation) = 'some text here'.

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

SELECT single SXBLNR 
  FROM VIBEPP 
  INTO @DATA(ld_imp_sxblnr).


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

DATA(ld_do_not_clear_tab) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_fehler to it_fehler.
 

"populate fields of struture and append to itab
append wa_tbssbkpf to it_tbssbkpf.
 

"populate fields of struture and append to itab
append wa_tbssbseg to it_tbssbseg.
 

"populate fields of struture and append to itab
append wa_tbsspara to it_tbsspara.
 

"populate fields of struture and append to itab
append wa_tvibepp to it_tvibepp.
 

"populate fields of struture and append to itab
append wa_tvibepp_mod to it_tvibepp_mod.
.

CALL FUNCTION 'REAL_ESTATE_DOCUMENTS'
* EXPORTING
*   flg_soll_id =                ld_flg_soll_id
*   posting_var =                ld_posting_var
*   protokoll =                  ld_protokoll
*   sammelbuchung =              ld_sammelbuchung
*   simulation =                 ld_simulation
*   imp_vislid =                 ld_imp_vislid
*   imp_sxblnr =                 ld_imp_sxblnr
*   imp_lfdnr =                  ld_imp_lfdnr
*   do_not_clear_tab =           ld_do_not_clear_tab
  IMPORTING
    exp_vislid =                 ld_exp_vislid
    exp_can_commit =             ld_exp_can_commit
    exp_lfdnr =                  ld_exp_lfdnr
  TABLES
    fehler =                     it_fehler
    tbssbkpf =                   it_tbssbkpf
    tbssbseg =                   it_tbssbseg
    tbsspara =                   it_tbsspara
    tvibepp =                    it_tvibepp
*   tvibepp_mod =                it_tvibepp_mod
  EXCEPTIONS
    NO_EXTBELNR =                1
    .  "  REAL_ESTATE_DOCUMENTS

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_exp_vislid  TYPE VISLID ,
ld_flg_soll_id  TYPE STRING ,
it_fehler  TYPE STANDARD TABLE OF SPROT_U ,
wa_fehler  LIKE LINE OF it_fehler,
ld_exp_can_commit  TYPE STRING ,
ld_posting_var  TYPE VISLID-SVORG ,
it_tbssbkpf  TYPE STANDARD TABLE OF BSSBKPF ,
wa_tbssbkpf  LIKE LINE OF it_tbssbkpf,
ld_exp_lfdnr  TYPE I ,
ld_protokoll  TYPE STRING ,
it_tbssbseg  TYPE STANDARD TABLE OF BSSBSEG ,
wa_tbssbseg  LIKE LINE OF it_tbssbseg,
ld_sammelbuchung  TYPE STRING ,
it_tbsspara  TYPE STANDARD TABLE OF BSSPARA ,
wa_tbsspara  LIKE LINE OF it_tbsspara,
ld_simulation  TYPE STRING ,
it_tvibepp  TYPE STANDARD TABLE OF RVIBEPP ,
wa_tvibepp  LIKE LINE OF it_tvibepp,
ld_imp_vislid  TYPE VISLID ,
it_tvibepp_mod  TYPE STANDARD TABLE OF RVIBEPP ,
wa_tvibepp_mod  LIKE LINE OF it_tvibepp_mod,
ld_imp_sxblnr  TYPE VIBEPP-SXBLNR ,
ld_imp_lfdnr  TYPE I ,
ld_do_not_clear_tab  TYPE STRING .




ld_flg_soll_id = 'some text here'. 

"populate fields of struture and append to itab
append wa_fehler to it_fehler.

SELECT single SVORG 
  FROM VISLID 
  INTO ld_posting_var.
 

"populate fields of struture and append to itab
append wa_tbssbkpf to it_tbssbkpf.
ld_protokoll = 'some text here'. 

"populate fields of struture and append to itab
append wa_tbssbseg to it_tbssbseg.
ld_sammelbuchung = 'some text here'. 

"populate fields of struture and append to itab
append wa_tbsspara to it_tbsspara.
ld_simulation = 'some text here'. 

"populate fields of struture and append to itab
append wa_tvibepp to it_tvibepp.
ld_imp_vislid = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_tvibepp_mod to it_tvibepp_mod.

SELECT single SXBLNR 
  FROM VIBEPP 
  INTO ld_imp_sxblnr.

ld_imp_lfdnr = 'Check type of data required'.
ld_do_not_clear_tab = 'some text here'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name REAL_ESTATE_DOCUMENTS or its description.


   
 

REAL_ESTATE_DOCUMENTS - 
REAL_ESTATE_DEBIT_POST_RULE - 
REAL_ESTATE_CUSTOMER_FIND_CN - 
REAL_ESTATE_CUSTOMER_FIND - 
REAL_ESTATE_CREATE_PAYSPLIT - 
REAL_ESTATE_CPD_FILL -