SAP CRM_ISUEXT_CHANGE_OW Function Module for Preise Dummy
CRM_ISUEXT_CHANGE_OW is a standard crm isuext change ow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Preise Dummy 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 isuext change ow FM, simply by entering the name CRM_ISUEXT_CHANGE_OW into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_ISUEXT_OW
Program Name: SAPLCRM_ISUEXT_OW
Main Program: SAPLCRM_ISUEXT_OW
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_ISUEXT_CHANGE_OW 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_ISUEXT_CHANGE_OW'"Preise Dummy.
EXPORTING
IV_GUID = "
IS_ISUEXT_COM = "EEW: Generated Object (Do not Process Manually)
CHANGING
CT_INPUT_FIELD_NAMES = "Table with Names of Fields to be Changed
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for CRM_ISUEXT_CHANGE_OW
IV_GUID -
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: Yes
IS_ISUEXT_COM - EEW: Generated Object (Do not Process Manually)
Data type: CRMT_ISUEXTA4_COMOptional: No
Call by Reference: Yes
CHANGING Parameters details for CRM_ISUEXT_CHANGE_OW
CT_INPUT_FIELD_NAMES - Table with Names of Fields to be Changed
Data type: CRMT_INPUT_FIELD_NAMES_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED - Errors have occurred
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CRM_ISUEXT_CHANGE_OW 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_iv_guid | TYPE CRMT_OBJECT_GUID, " | |||
lv_error_occurred | TYPE CRMT_OBJECT_GUID, " | |||
lv_ct_input_field_names | TYPE CRMT_INPUT_FIELD_NAMES_TAB, " | |||
lv_is_isuext_com | TYPE CRMT_ISUEXTA4_COM. " |
  CALL FUNCTION 'CRM_ISUEXT_CHANGE_OW' "Preise Dummy |
EXPORTING | ||
IV_GUID | = lv_iv_guid | |
IS_ISUEXT_COM | = lv_is_isuext_com | |
CHANGING | ||
CT_INPUT_FIELD_NAMES | = lv_ct_input_field_names | |
EXCEPTIONS | ||
ERROR_OCCURRED = 1 | ||
. " CRM_ISUEXT_CHANGE_OW |
ABAP code using 7.40 inline data declarations to call FM CRM_ISUEXT_CHANGE_OW
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