SAP Function Modules
FI_PAYMENT_REQUEST_PP_WRITE SAP Function module
FI_PAYMENT_REQUEST_PP_WRITE 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 FI_PAYMENT_REQUEST_PP_WRITE into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
F0PR_EU
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM FI_PAYMENT_REQUEST_PP_WRITE - FI PAYMENT REQUEST PP WRITE
CALL FUNCTION 'FI_PAYMENT_REQUEST_PP_WRITE' "
* EXPORTING
* i_update = " boole-boole Update in dialog (not initial) or update task
* i_payrq_old = " payrq Old payment request
* i_payrq_new = " payrq New payment request
* i_paybu_old = " paybu Old payment transfer
* i_paybu_new = " paybu New payment transfer
* i_payrc_old = " payrc
* i_payrc_new = " payrc
* i_post = SPACE " boole-boole
IMPORTING
e_keyno = " payrq-keyno
TABLES
* t_vbkpf_old = " vbkpf Old document headers
* t_vbsec_old = " vbsec Old CPD data
* t_vbseg_old = " vbseg Old document items
* t_vbset_old = " vbset Old taxes
t_vbkpf_new = " vbkpf New document headers
t_vbsec_new = " vbsec New CPD data
t_vbseg_new = " vbseg New document items
t_vbset_new = " vbset New taxes
* t_payko_old = " payko Additional line item fields
* t_payct_new = " payct
* t_payct_old = " payct
* t_payko_new = " payko Additional line item fields
. " FI_PAYMENT_REQUEST_PP_WRITE
ABAP code example for Function Module FI_PAYMENT_REQUEST_PP_WRITE
The ABAP code below is a full code listing to execute function module FI_PAYMENT_REQUEST_PP_WRITE 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).
| ld_e_keyno | TYPE PAYRQ-KEYNO , |
| it_t_vbkpf_old | TYPE STANDARD TABLE OF VBKPF,"TABLES PARAM |
| wa_t_vbkpf_old | LIKE LINE OF it_t_vbkpf_old , |
| it_t_vbsec_old | TYPE STANDARD TABLE OF VBSEC,"TABLES PARAM |
| wa_t_vbsec_old | LIKE LINE OF it_t_vbsec_old , |
| it_t_vbseg_old | TYPE STANDARD TABLE OF VBSEG,"TABLES PARAM |
| wa_t_vbseg_old | LIKE LINE OF it_t_vbseg_old , |
| it_t_vbset_old | TYPE STANDARD TABLE OF VBSET,"TABLES PARAM |
| wa_t_vbset_old | LIKE LINE OF it_t_vbset_old , |
| it_t_vbkpf_new | TYPE STANDARD TABLE OF VBKPF,"TABLES PARAM |
| wa_t_vbkpf_new | LIKE LINE OF it_t_vbkpf_new , |
| it_t_vbsec_new | TYPE STANDARD TABLE OF VBSEC,"TABLES PARAM |
| wa_t_vbsec_new | LIKE LINE OF it_t_vbsec_new , |
| it_t_vbseg_new | TYPE STANDARD TABLE OF VBSEG,"TABLES PARAM |
| wa_t_vbseg_new | LIKE LINE OF it_t_vbseg_new , |
| it_t_vbset_new | TYPE STANDARD TABLE OF VBSET,"TABLES PARAM |
| wa_t_vbset_new | LIKE LINE OF it_t_vbset_new , |
| it_t_payko_old | TYPE STANDARD TABLE OF PAYKO,"TABLES PARAM |
| wa_t_payko_old | LIKE LINE OF it_t_payko_old , |
| it_t_payct_new | TYPE STANDARD TABLE OF PAYCT,"TABLES PARAM |
| wa_t_payct_new | LIKE LINE OF it_t_payct_new , |
| it_t_payct_old | TYPE STANDARD TABLE OF PAYCT,"TABLES PARAM |
| wa_t_payct_old | LIKE LINE OF it_t_payct_old , |
| it_t_payko_new | TYPE STANDARD TABLE OF PAYKO,"TABLES PARAM |
| wa_t_payko_new | LIKE LINE OF it_t_payko_new . |
DATA(ld_i_update) = some text here
DATA(ld_i_payrq_old) = 'Check type of data required'.
DATA(ld_i_payrq_new) = 'Check type of data required'.
DATA(ld_i_paybu_old) = 'Check type of data required'.
DATA(ld_i_paybu_new) = 'Check type of data required'.
DATA(ld_i_payrc_old) = 'Check type of data required'.
DATA(ld_i_payrc_new) = 'Check type of data required'.
DATA(ld_i_post) = some text here
"populate fields of struture and append to itab
append wa_t_vbkpf_old to it_t_vbkpf_old.
"populate fields of struture and append to itab
append wa_t_vbsec_old to it_t_vbsec_old.
"populate fields of struture and append to itab
append wa_t_vbseg_old to it_t_vbseg_old.
"populate fields of struture and append to itab
append wa_t_vbset_old to it_t_vbset_old.
"populate fields of struture and append to itab
append wa_t_vbkpf_new to it_t_vbkpf_new.
"populate fields of struture and append to itab
append wa_t_vbsec_new to it_t_vbsec_new.
"populate fields of struture and append to itab
append wa_t_vbseg_new to it_t_vbseg_new.
"populate fields of struture and append to itab
append wa_t_vbset_new to it_t_vbset_new.
"populate fields of struture and append to itab
append wa_t_payko_old to it_t_payko_old.
"populate fields of struture and append to itab
append wa_t_payct_new to it_t_payct_new.
"populate fields of struture and append to itab
append wa_t_payct_old to it_t_payct_old.
"populate fields of struture and append to itab
append wa_t_payko_new to it_t_payko_new. . CALL FUNCTION 'FI_PAYMENT_REQUEST_PP_WRITE' * EXPORTING * i_update = ld_i_update * i_payrq_old = ld_i_payrq_old * i_payrq_new = ld_i_payrq_new * i_paybu_old = ld_i_paybu_old * i_paybu_new = ld_i_paybu_new * i_payrc_old = ld_i_payrc_old * i_payrc_new = ld_i_payrc_new * i_post = ld_i_post IMPORTING e_keyno = ld_e_keyno TABLES * t_vbkpf_old = it_t_vbkpf_old * t_vbsec_old = it_t_vbsec_old * t_vbseg_old = it_t_vbseg_old * t_vbset_old = it_t_vbset_old t_vbkpf_new = it_t_vbkpf_new t_vbsec_new = it_t_vbsec_new t_vbseg_new = it_t_vbseg_new t_vbset_new = it_t_vbset_new * t_payko_old = it_t_payko_old * t_payct_new = it_t_payct_new * t_payct_old = it_t_payct_old * t_payko_new = it_t_payko_new . " FI_PAYMENT_REQUEST_PP_WRITE
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_e_keyno | TYPE PAYRQ-KEYNO , |
| ld_i_update | TYPE BOOLE-BOOLE , |
| it_t_vbkpf_old | TYPE STANDARD TABLE OF VBKPF , |
| wa_t_vbkpf_old | LIKE LINE OF it_t_vbkpf_old, |
| ld_i_payrq_old | TYPE PAYRQ , |
| it_t_vbsec_old | TYPE STANDARD TABLE OF VBSEC , |
| wa_t_vbsec_old | LIKE LINE OF it_t_vbsec_old, |
| ld_i_payrq_new | TYPE PAYRQ , |
| it_t_vbseg_old | TYPE STANDARD TABLE OF VBSEG , |
| wa_t_vbseg_old | LIKE LINE OF it_t_vbseg_old, |
| ld_i_paybu_old | TYPE PAYBU , |
| it_t_vbset_old | TYPE STANDARD TABLE OF VBSET , |
| wa_t_vbset_old | LIKE LINE OF it_t_vbset_old, |
| ld_i_paybu_new | TYPE PAYBU , |
| it_t_vbkpf_new | TYPE STANDARD TABLE OF VBKPF , |
| wa_t_vbkpf_new | LIKE LINE OF it_t_vbkpf_new, |
| ld_i_payrc_old | TYPE PAYRC , |
| it_t_vbsec_new | TYPE STANDARD TABLE OF VBSEC , |
| wa_t_vbsec_new | LIKE LINE OF it_t_vbsec_new, |
| ld_i_payrc_new | TYPE PAYRC , |
| it_t_vbseg_new | TYPE STANDARD TABLE OF VBSEG , |
| wa_t_vbseg_new | LIKE LINE OF it_t_vbseg_new, |
| ld_i_post | TYPE BOOLE-BOOLE , |
| it_t_vbset_new | TYPE STANDARD TABLE OF VBSET , |
| wa_t_vbset_new | LIKE LINE OF it_t_vbset_new, |
| it_t_payko_old | TYPE STANDARD TABLE OF PAYKO , |
| wa_t_payko_old | LIKE LINE OF it_t_payko_old, |
| it_t_payct_new | TYPE STANDARD TABLE OF PAYCT , |
| wa_t_payct_new | LIKE LINE OF it_t_payct_new, |
| it_t_payct_old | TYPE STANDARD TABLE OF PAYCT , |
| wa_t_payct_old | LIKE LINE OF it_t_payct_old, |
| it_t_payko_new | TYPE STANDARD TABLE OF PAYKO , |
| wa_t_payko_new | LIKE LINE OF it_t_payko_new. |
ld_i_update = some text here
"populate fields of struture and append to itab
append wa_t_vbkpf_old to it_t_vbkpf_old.
ld_i_payrq_old = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_t_vbsec_old to it_t_vbsec_old.
ld_i_payrq_new = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_t_vbseg_old to it_t_vbseg_old.
ld_i_paybu_old = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_t_vbset_old to it_t_vbset_old.
ld_i_paybu_new = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_t_vbkpf_new to it_t_vbkpf_new.
ld_i_payrc_old = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_t_vbsec_new to it_t_vbsec_new.
ld_i_payrc_new = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_t_vbseg_new to it_t_vbseg_new.
ld_i_post = some text here
"populate fields of struture and append to itab
append wa_t_vbset_new to it_t_vbset_new.
"populate fields of struture and append to itab
append wa_t_payko_old to it_t_payko_old.
"populate fields of struture and append to itab
append wa_t_payct_new to it_t_payct_new.
"populate fields of struture and append to itab
append wa_t_payct_old to it_t_payct_old.
"populate fields of struture and append to itab
append wa_t_payko_new to it_t_payko_new.
SAP Documentation for FM FI_PAYMENT_REQUEST_PP_WRITE
Data for payment requests and parked documents is stored in the
respective tables (insert/update). If there is no entry in the
...See here for full SAP fm documentation
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 FI_PAYMENT_REQUEST_PP_WRITE or its description.