SAP CRM_IST_COPY_ITEM_TO_SC_ORDER Function Module for Create new change order for ISTB and ISTC processes
CRM_IST_COPY_ITEM_TO_SC_ORDER is a standard crm ist copy item to sc order SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create new change order for ISTB and ISTC processes 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 copy item to sc order FM, simply by entering the name CRM_IST_COPY_ITEM_TO_SC_ORDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_IST_ORDER_COPY
Program Name: SAPLCRM_IST_ORDER_COPY
Main Program: SAPLCRM_IST_ORDER_COPY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_IST_COPY_ITEM_TO_SC_ORDER 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_COPY_ITEM_TO_SC_ORDER'"Create new change order for ISTB and ISTC processes.
EXPORTING
* IV_APPLICATION_LOG = "Application Log: Log Handle
* IV_SOURCE_HEADER_GUID = "GUID of a CRM Order Object
IV_SOURCE_ITEM_GUID = "GUID of a CRM Order Object
* IV_PROCESS_TYPE = "Business Transaction Type
IV_NEW_ITEM_PROCESS = "Process
* IV_LOCK_PROD_GUID = "Internal Unique Identifier of Product
* IV_LOCK_TIME = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
* IV_LOCK_REASON = "Lock Reason
IMPORTING
ET_ORDERADM_I = "Item Admin: Communication Table
ES_ORDERADM_H_COM = "General Header Data - Structure of Communication Fields
EXCEPTIONS
FAILURE = 1 ERROR_OCCURRED = 2 NO_PRODUCT_FROM_IL = 3
IMPORTING Parameters details for CRM_IST_COPY_ITEM_TO_SC_ORDER
IV_APPLICATION_LOG - Application Log: Log Handle
Data type: BALLOGHNDLOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SOURCE_HEADER_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SOURCE_ITEM_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_PROCESS_TYPE - Business Transaction Type
Data type: CRMT_PROCESS_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NEW_ITEM_PROCESS - Process
Data type: IST_ITEM_PROCESSOptional: No
Call by Reference: Yes
IV_LOCK_PROD_GUID - Internal Unique Identifier of Product
Data type: CRMT_PRODUCT_GUID_DBOptional: Yes
Call by Reference: Yes
IV_LOCK_TIME - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
Data type: TIMESTAMPOptional: Yes
Call by Reference: Yes
IV_LOCK_REASON - Lock Reason
Data type: IST_LOCK_REASONOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CRM_IST_COPY_ITEM_TO_SC_ORDER
ET_ORDERADM_I - Item Admin: Communication Table
Data type: CRMT_ORDERADM_I_COMTOptional: No
Call by Reference: Yes
ES_ORDERADM_H_COM - General Header Data - Structure of Communication Fields
Data type: CRMT_ORDERADM_H_COMOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: Yes
NO_PRODUCT_FROM_IL - Kein Produkt im für Servicedatenänderungen gefunden.
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_IST_COPY_ITEM_TO_SC_ORDER 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_failure | TYPE STRING, " | |||
lv_et_orderadm_i | TYPE CRMT_ORDERADM_I_COMT, " | |||
lv_iv_application_log | TYPE BALLOGHNDL, " | |||
lv_error_occurred | TYPE BALLOGHNDL, " | |||
lv_es_orderadm_h_com | TYPE CRMT_ORDERADM_H_COM, " | |||
lv_iv_source_header_guid | TYPE CRMT_OBJECT_GUID, " | |||
lv_no_product_from_il | TYPE CRMT_OBJECT_GUID, " | |||
lv_iv_source_item_guid | TYPE CRMT_OBJECT_GUID, " | |||
lv_iv_process_type | TYPE CRMT_PROCESS_TYPE, " | |||
lv_iv_new_item_process | TYPE IST_ITEM_PROCESS, " | |||
lv_iv_lock_prod_guid | TYPE CRMT_PRODUCT_GUID_DB, " | |||
lv_iv_lock_time | TYPE TIMESTAMP, " | |||
lv_iv_lock_reason | TYPE IST_LOCK_REASON. " |
  CALL FUNCTION 'CRM_IST_COPY_ITEM_TO_SC_ORDER' "Create new change order for ISTB and ISTC processes |
EXPORTING | ||
IV_APPLICATION_LOG | = lv_iv_application_log | |
IV_SOURCE_HEADER_GUID | = lv_iv_source_header_guid | |
IV_SOURCE_ITEM_GUID | = lv_iv_source_item_guid | |
IV_PROCESS_TYPE | = lv_iv_process_type | |
IV_NEW_ITEM_PROCESS | = lv_iv_new_item_process | |
IV_LOCK_PROD_GUID | = lv_iv_lock_prod_guid | |
IV_LOCK_TIME | = lv_iv_lock_time | |
IV_LOCK_REASON | = lv_iv_lock_reason | |
IMPORTING | ||
ET_ORDERADM_I | = lv_et_orderadm_i | |
ES_ORDERADM_H_COM | = lv_es_orderadm_h_com | |
EXCEPTIONS | ||
FAILURE = 1 | ||
ERROR_OCCURRED = 2 | ||
NO_PRODUCT_FROM_IL = 3 | ||
. " CRM_IST_COPY_ITEM_TO_SC_ORDER |
ABAP code using 7.40 inline data declarations to call FM CRM_IST_COPY_ITEM_TO_SC_ORDER
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