SAP ISU_PPLAN_CLOSE_REMOTE Function Module for IC WC: Close and Unlock Payment Plan Object
ISU_PPLAN_CLOSE_REMOTE is a standard isu pplan close remote SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IC WC: Close and Unlock Payment Plan Object 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 isu pplan close remote FM, simply by entering the name ISU_PPLAN_CLOSE_REMOTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: E325R
Program Name: SAPLE325R
Main Program: SAPLE325R
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ISU_PPLAN_CLOSE_REMOTE 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 'ISU_PPLAN_CLOSE_REMOTE'"IC WC: Close and Unlock Payment Plan Object.
EXPORTING
* X_PPID = "
IMPORTING
YT_MSG = "Return Table
EXCEPTIONS
NO_AUTHORIZATION = 1
IMPORTING Parameters details for ISU_PPLAN_CLOSE_REMOTE
X_PPID -
Data type: EPPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_PPLAN_CLOSE_REMOTE
YT_MSG - Return Table
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_AUTHORIZATION - Non-authorized
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_PPLAN_CLOSE_REMOTE 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_x_ppid | TYPE EPPID, " | |||
| lv_yt_msg | TYPE BAPIRET2_T, " | |||
| lv_no_authorization | TYPE BAPIRET2_T. " |
|   CALL FUNCTION 'ISU_PPLAN_CLOSE_REMOTE' "IC WC: Close and Unlock Payment Plan Object |
| EXPORTING | ||
| X_PPID | = lv_x_ppid | |
| IMPORTING | ||
| YT_MSG | = lv_yt_msg | |
| EXCEPTIONS | ||
| NO_AUTHORIZATION = 1 | ||
| . " ISU_PPLAN_CLOSE_REMOTE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_PPLAN_CLOSE_REMOTE
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