SAP ISM_SD_GET_WERK_FROM_ORDER Function Module for Specify Plant for Order
ISM_SD_GET_WERK_FROM_ORDER is a standard ism sd get werk from 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 Specify Plant for Order 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 ism sd get werk from order FM, simply by entering the name ISM_SD_GET_WERK_FROM_ORDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSDCOLLECTION
Program Name: SAPLJKSDCOLLECTION
Main Program: SAPLJKSDCOLLECTION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_SD_GET_WERK_FROM_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 'ISM_SD_GET_WERK_FROM_ORDER'"Specify Plant for Order.
EXPORTING
IM_ISSUE = "Material Number
IM_VBELN_CONTRACT = "Contract Number
IM_POSNR_CONTRACT = "Item Number in Contract
IM_PHASEMDL = "Phase Model in Phase-Based Delivery
IM_PHASENBR = "Sequence Number in Phase-Based Delivery
IMPORTING
EX_WERKS = "Plant
EXCEPTIONS
ERROR_WERK = 1
IMPORTING Parameters details for ISM_SD_GET_WERK_FROM_ORDER
IM_ISSUE - Material Number
Data type: ISMMATNR_ISSUEOptional: No
Call by Reference: Yes
IM_VBELN_CONTRACT - Contract Number
Data type: JVBELNCONTRACTOptional: No
Call by Reference: Yes
IM_POSNR_CONTRACT - Item Number in Contract
Data type: JPOSNRCONTRACTOptional: No
Call by Reference: Yes
IM_PHASEMDL - Phase Model in Phase-Based Delivery
Data type: JVPHASEMDLOptional: No
Call by Reference: Yes
IM_PHASENBR - Sequence Number in Phase-Based Delivery
Data type: JVPHASENBROptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_SD_GET_WERK_FROM_ORDER
EX_WERKS - Plant
Data type: WERKS_DOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_WERK -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_SD_GET_WERK_FROM_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_ex_werks | TYPE WERKS_D, " | |||
| lv_im_issue | TYPE ISMMATNR_ISSUE, " | |||
| lv_error_werk | TYPE ISMMATNR_ISSUE, " | |||
| lv_im_vbeln_contract | TYPE JVBELNCONTRACT, " | |||
| lv_im_posnr_contract | TYPE JPOSNRCONTRACT, " | |||
| lv_im_phasemdl | TYPE JVPHASEMDL, " | |||
| lv_im_phasenbr | TYPE JVPHASENBR. " |
|   CALL FUNCTION 'ISM_SD_GET_WERK_FROM_ORDER' "Specify Plant for Order |
| EXPORTING | ||
| IM_ISSUE | = lv_im_issue | |
| IM_VBELN_CONTRACT | = lv_im_vbeln_contract | |
| IM_POSNR_CONTRACT | = lv_im_posnr_contract | |
| IM_PHASEMDL | = lv_im_phasemdl | |
| IM_PHASENBR | = lv_im_phasenbr | |
| IMPORTING | ||
| EX_WERKS | = lv_ex_werks | |
| EXCEPTIONS | ||
| ERROR_WERK = 1 | ||
| . " ISM_SD_GET_WERK_FROM_ORDER | ||
ABAP code using 7.40 inline data declarations to call FM ISM_SD_GET_WERK_FROM_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