SAP COM_PARTNER_FIELDSELECTION_IF Function Module for Feldselektion auf der Oberfläche









COM_PARTNER_FIELDSELECTION_IF is a standard com partner fieldselection if SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Feldselektion auf der Oberfläche 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 fieldselection if FM, simply by entering the name COM_PARTNER_FIELDSELECTION_IF into the relevant SAP transaction such as SE37 or SE38.

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



Function COM_PARTNER_FIELDSELECTION_IF 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_FIELDSELECTION_IF'"Feldselektion auf der Oberfläche
  EXPORTING
   IV_SUBSCREEN_ID =  "IDs for Partner Processing Subscreens
   IS_SCREEN_LAYOUT =  "Tax Information for the User Interface for PV
   IS_LOGICAL_KEY =  "Logical Key for Identifying a Partner
   IS_PARTNER_CONTROL =  "Control Data in Partner Processing

 IMPORTING
   EV_PARTNER_CHANGEABLE =  "New input values
   EV_ADDRESS_CHANGEABLE =  "New input values
   EV_DISPLAY_MODE =  "Display Mode for Partner Processing Subscreen

CHANGING
   CS_PARTNER_COM =  "Transfer Structure for Partners
   CT_INPUT_FIELD_NAMES =  "Table with Names of Fields to be Changed
.



IMPORTING Parameters details for COM_PARTNER_FIELDSELECTION_IF

IV_SUBSCREEN_ID - IDs for Partner Processing Subscreens

Data type: COMT_PARTNER_SUBSCREEN_ID
Optional: No
Call by Reference: Yes

IS_SCREEN_LAYOUT - Tax Information for the User Interface for PV

Data type: COMT_PARTNER_SCREEN_LAYOUT
Optional: No
Call by Reference: Yes

IS_LOGICAL_KEY - Logical Key for Identifying a Partner

Data type: COMT_PARTNER_LOGIC_PARTNER_KEY
Optional: No
Call by Reference: Yes

IS_PARTNER_CONTROL - Control Data in Partner Processing

Data type: COMT_PARTNER_CONTROL
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for COM_PARTNER_FIELDSELECTION_IF

EV_PARTNER_CHANGEABLE - New input values

Data type: XFLAG
Optional: No
Call by Reference: Yes

EV_ADDRESS_CHANGEABLE - New input values

Data type: XFLAG
Optional: No
Call by Reference: Yes

EV_DISPLAY_MODE - Display Mode for Partner Processing Subscreen

Data type: COMT_PARTNER_SCREEN_MODE
Optional: No
Call by Reference: Yes

CHANGING Parameters details for COM_PARTNER_FIELDSELECTION_IF

CS_PARTNER_COM - Transfer Structure for Partners

Data type: COMT_PARTNER_COM
Optional: No
Call by Reference: Yes

CT_INPUT_FIELD_NAMES - Table with Names of Fields to be Changed

Data type: COMT_PARTNER_INPUT_FIELD_N_TAB
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COM_PARTNER_FIELDSELECTION_IF 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_cs_partner_com  TYPE COMT_PARTNER_COM, "   
lv_iv_subscreen_id  TYPE COMT_PARTNER_SUBSCREEN_ID, "   
lv_ev_partner_changeable  TYPE XFLAG, "   
lv_is_screen_layout  TYPE COMT_PARTNER_SCREEN_LAYOUT, "   
lv_ct_input_field_names  TYPE COMT_PARTNER_INPUT_FIELD_N_TAB, "   
lv_ev_address_changeable  TYPE XFLAG, "   
lv_is_logical_key  TYPE COMT_PARTNER_LOGIC_PARTNER_KEY, "   
lv_ev_display_mode  TYPE COMT_PARTNER_SCREEN_MODE, "   
lv_is_partner_control  TYPE COMT_PARTNER_CONTROL. "   

  CALL FUNCTION 'COM_PARTNER_FIELDSELECTION_IF'  "Feldselektion auf der Oberfläche
    EXPORTING
         IV_SUBSCREEN_ID = lv_iv_subscreen_id
         IS_SCREEN_LAYOUT = lv_is_screen_layout
         IS_LOGICAL_KEY = lv_is_logical_key
         IS_PARTNER_CONTROL = lv_is_partner_control
    IMPORTING
         EV_PARTNER_CHANGEABLE = lv_ev_partner_changeable
         EV_ADDRESS_CHANGEABLE = lv_ev_address_changeable
         EV_DISPLAY_MODE = lv_ev_display_mode
    CHANGING
         CS_PARTNER_COM = lv_cs_partner_com
         CT_INPUT_FIELD_NAMES = lv_ct_input_field_names
. " COM_PARTNER_FIELDSELECTION_IF




ABAP code using 7.40 inline data declarations to call FM COM_PARTNER_FIELDSELECTION_IF

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!