SAP CRM_IST_ITEM_EXTENSION_FIELDCH Function Module for Field check
CRM_IST_ITEM_EXTENSION_FIELDCH is a standard crm ist item extension fieldch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Field check 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 crm ist item extension fieldch FM, simply by entering the name CRM_IST_ITEM_EXTENSION_FIELDCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_IST_ITA3_FC
Program Name: SAPLCRM_IST_ITA3_FC
Main Program: SAPLCRM_IST_ITA3_FC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_IST_ITEM_EXTENSION_FIELDCH 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 'CRM_IST_ITEM_EXTENSION_FIELDCH'"Field check.
EXPORTING
IS_FIELDCHECK_COM = "Communication Structure for Field Selection
CHANGING
CT_INPUT_FIELD_NAMES = "Table with Names of Fields to be Changed
IMPORTING Parameters details for CRM_IST_ITEM_EXTENSION_FIELDCH
IS_FIELDCHECK_COM - Communication Structure for Field Selection
Data type: CRMT_FIELDCHECK_COMOptional: No
Call by Reference: Yes
CHANGING Parameters details for CRM_IST_ITEM_EXTENSION_FIELDCH
CT_INPUT_FIELD_NAMES - Table with Names of Fields to be Changed
Data type: CRMT_INPUT_FIELD_NAMES_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_IST_ITEM_EXTENSION_FIELDCH 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_is_fieldcheck_com | TYPE CRMT_FIELDCHECK_COM, " | |||
lv_ct_input_field_names | TYPE CRMT_INPUT_FIELD_NAMES_TAB. " |
  CALL FUNCTION 'CRM_IST_ITEM_EXTENSION_FIELDCH' "Field check |
EXPORTING | ||
IS_FIELDCHECK_COM | = lv_is_fieldcheck_com | |
CHANGING | ||
CT_INPUT_FIELD_NAMES | = lv_ct_input_field_names | |
. " CRM_IST_ITEM_EXTENSION_FIELDCH |
ABAP code using 7.40 inline data declarations to call FM CRM_IST_ITEM_EXTENSION_FIELDCH
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