SAP COM_PARTNER_CHANGES_GET_UI Function Module for Abfragen der auf den Screens durchgeführten Änderungen
COM_PARTNER_CHANGES_GET_UI is a standard com partner changes get ui SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Abfragen der auf den Screens durchgeführten Änderungen 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 com partner changes get ui FM, simply by entering the name COM_PARTNER_CHANGES_GET_UI into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_PARTNER_UI2
Program Name: SAPLCOM_PARTNER_UI2
Main Program: SAPLCOM_PARTNER_UI2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_PARTNER_CHANGES_GET_UI 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 'COM_PARTNER_CHANGES_GET_UI'"Abfragen der auf den Screens durchgeführten Änderungen.
EXPORTING
* IV_REFRESH = ' ' "Löscht die Changes (muß bei jedem PAI einmal gemacht werden)
* IV_REFRESH_ALL = ' ' "New input values
* IV_SUBSCREEN_ID = "Nur die Änderungen auf einem bestimmten Subscreen
IMPORTING
ET_CHANGES = "Table of Partner Changes on Subscreens
ET_DISPLAYED_PARTNERS = "Partners Displayed on Subscreen According to Index
ET_FCODES = "FCode for a Subscreen
EXCEPTIONS
NO_CHANGES = 1
IMPORTING Parameters details for COM_PARTNER_CHANGES_GET_UI
IV_REFRESH - Löscht die Changes (muß bei jedem PAI einmal gemacht werden)
Data type: XFLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
IV_REFRESH_ALL - New input values
Data type: XFLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
IV_SUBSCREEN_ID - Nur die Änderungen auf einem bestimmten Subscreen
Data type: COMT_PARTNER_SUBSCREEN_IDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for COM_PARTNER_CHANGES_GET_UI
ET_CHANGES - Table of Partner Changes on Subscreens
Data type: COMT_PARTNER_SCREEN_CHANGES_TOptional: No
Call by Reference: Yes
ET_DISPLAYED_PARTNERS - Partners Displayed on Subscreen According to Index
Data type: COMT_PARTNER_SCREEN_PARTNERS_TOptional: No
Call by Reference: Yes
ET_FCODES - FCode for a Subscreen
Data type: COMT_PARTNER_SCREEN_FCODE_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_CHANGES - No changes have been made
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for COM_PARTNER_CHANGES_GET_UI 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_et_changes | TYPE COMT_PARTNER_SCREEN_CHANGES_T, " | |||
| lv_iv_refresh | TYPE XFLAG, " SPACE | |||
| lv_no_changes | TYPE XFLAG, " | |||
| lv_iv_refresh_all | TYPE XFLAG, " SPACE | |||
| lv_et_displayed_partners | TYPE COMT_PARTNER_SCREEN_PARTNERS_T, " | |||
| lv_et_fcodes | TYPE COMT_PARTNER_SCREEN_FCODE_TAB, " | |||
| lv_iv_subscreen_id | TYPE COMT_PARTNER_SUBSCREEN_ID. " |
|   CALL FUNCTION 'COM_PARTNER_CHANGES_GET_UI' "Abfragen der auf den Screens durchgeführten Änderungen |
| EXPORTING | ||
| IV_REFRESH | = lv_iv_refresh | |
| IV_REFRESH_ALL | = lv_iv_refresh_all | |
| IV_SUBSCREEN_ID | = lv_iv_subscreen_id | |
| IMPORTING | ||
| ET_CHANGES | = lv_et_changes | |
| ET_DISPLAYED_PARTNERS | = lv_et_displayed_partners | |
| ET_FCODES | = lv_et_fcodes | |
| EXCEPTIONS | ||
| NO_CHANGES = 1 | ||
| . " COM_PARTNER_CHANGES_GET_UI | ||
ABAP code using 7.40 inline data declarations to call FM COM_PARTNER_CHANGES_GET_UI
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.| DATA(ld_iv_refresh) | = ' '. | |||
| DATA(ld_iv_refresh_all) | = ' '. | |||
Search for further information about these or an SAP related objects