SAP FI_PP_CHANGE_DOC_WRITE Function Module for

Search SAP Function Modules

FI_PP_CHANGE_DOC_WRITE is a standard fi pp change doc write 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 fi pp change doc write FM, simply by entering the name FI_PP_CHANGE_DOC_WRITE into the relevant SAP transaction such as SE37 or SE38.

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

Function FI_PP_CHANGE_DOC_WRITE 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 'FI_PP_CHANGE_DOC_WRITE'"
  EXPORTING
   I_XUPDATE =  "

TABLES
   T_VBKPF_NEW =  "
   T_VBSEC_NEW =  "
   T_VBSEG_NEW =  "
   T_VBSET_NEW =  "
   T_VBKPF_OLD =  "
   T_VBSEC_OLD =  "
   T_VBSEG_OLD =  "
   T_VBSET_OLD =  "

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLF0PR_001 FM Account Determination
EXIT_SAPLF0PR_002 Checks for Payment Requests / Incoming Payment Requests
EXIT_SAPLF0PR_003 Writing Payment Request / Incoming Payment Request

IMPORTING Parameters details for FI_PP_CHANGE_DOC_WRITE

I_XUPDATE -

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

TABLES Parameters details for FI_PP_CHANGE_DOC_WRITE

T_VBKPF_NEW -

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

T_VBSEC_NEW -

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

T_VBSEG_NEW -

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

T_VBSET_NEW -

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

T_VBKPF_OLD -

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

T_VBSEC_OLD -

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

T_VBSEG_OLD -

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

T_VBSET_OLD -

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

Copy and paste ABAP code example for FI_PP_CHANGE_DOC_WRITE 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.

ABAP code using 7.40 inline data declarations to call FM FI_PP_CHANGE_DOC_WRITE

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.

Search for further information about these or an SAP related objects