SAP ISMSD_ISSUE_INSERT_TO_ORDER Function Module for IS-M/SD: Adjust M/SD Orders (API: Insert Issue)
ISMSD_ISSUE_INSERT_TO_ORDER is a standard ismsd issue insert to 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 IS-M/SD: Adjust M/SD Orders (API: Insert Issue) 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 ismsd issue insert to order FM, simply by entering the name ISMSD_ISSUE_INSERT_TO_ORDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKISSUE
Program Name: SAPLJKISSUE
Main Program: SAPLJKISSUE
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISMSD_ISSUE_INSERT_TO_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 'ISMSD_ISSUE_INSERT_TO_ORDER'"IS-M/SD: Adjust M/SD Orders (API: Insert Issue).
EXPORTING
ISSUE_INSERT = "
* XTEST = "Test Mode
ISSUE_CHANGETYPE = "Issue change type
EXCEPTIONS
PROCESS_CANCELLED = 1
IMPORTING Parameters details for ISMSD_ISSUE_INSERT_TO_ORDER
ISSUE_INSERT -
Data type: JDVA_JDTVAUSGB_STRUOptional: No
Call by Reference: No ( called with pass by value option)
XTEST - Test Mode
Data type: JPSD_XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
ISSUE_CHANGETYPE - Issue change type
Data type: TJD71-CHTYPE_ISSUEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PROCESS_CANCELLED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISMSD_ISSUE_INSERT_TO_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_issue_insert | TYPE JDVA_JDTVAUSGB_STRU, " | |||
| lv_process_cancelled | TYPE JDVA_JDTVAUSGB_STRU, " | |||
| lv_xtest | TYPE JPSD_XFELD, " | |||
| lv_issue_changetype | TYPE TJD71-CHTYPE_ISSUE. " |
|   CALL FUNCTION 'ISMSD_ISSUE_INSERT_TO_ORDER' "IS-M/SD: Adjust M/SD Orders (API: Insert Issue) |
| EXPORTING | ||
| ISSUE_INSERT | = lv_issue_insert | |
| XTEST | = lv_xtest | |
| ISSUE_CHANGETYPE | = lv_issue_changetype | |
| EXCEPTIONS | ||
| PROCESS_CANCELLED = 1 | ||
| . " ISMSD_ISSUE_INSERT_TO_ORDER | ||
ABAP code using 7.40 inline data declarations to call FM ISMSD_ISSUE_INSERT_TO_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.| "SELECT single CHTYPE_ISSUE FROM TJD71 INTO @DATA(ld_issue_changetype). | ||||
Search for further information about these or an SAP related objects