SAP ISM_CONTRACTDEMANDVERSION_CPY Function Module for
ISM_CONTRACTDEMANDVERSION_CPY is a standard ism contractdemandversion cpy SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 contractdemandversion cpy FM, simply by entering the name ISM_CONTRACTDEMANDVERSION_CPY into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSDVERSION
Program Name: SAPLJKSDVERSION
Main Program: SAPLJKSDVERSION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_CONTRACTDEMANDVERSION_CPY 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_CONTRACTDEMANDVERSION_CPY'".
EXPORTING
FROMVERSION = "
TOVERSION = "
* REPLACE_ALL = ' ' "
* REPLACE_DUP = ' ' "
* IN_FLAG_CHANGE_FIXED = "
IMPORTING
RETURN = "
TABLES
IN_DEMAND = "
EXCEPTIONS
INVALID = 1 NOT_FOUND = 2 LOCK_FAILED = 3 DELETE_FAILED = 4 NOT_AUTHORIZED = 5
IMPORTING Parameters details for ISM_CONTRACTDEMANDVERSION_CPY
FROMVERSION -
Data type: JSDVERSIONOptional: No
Call by Reference: No ( called with pass by value option)
TOVERSION -
Data type: JSDVERSIONOptional: No
Call by Reference: No ( called with pass by value option)
REPLACE_ALL -
Data type: JREPLACEALLDefault: ' '
Optional: No
Call by Reference: No ( called with pass by value option)
REPLACE_DUP -
Data type: JREPLACEDUPDefault: ' '
Optional: No
Call by Reference: No ( called with pass by value option)
IN_FLAG_CHANGE_FIXED -
Data type: XFELDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISM_CONTRACTDEMANDVERSION_CPY
RETURN -
Data type: CL_ISM_SD_MESSAGEOptional: No
Call by Reference: Yes
TABLES Parameters details for ISM_CONTRACTDEMANDVERSION_CPY
IN_DEMAND -
Data type: JKSDDEMANDOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID -
Data type:Optional: No
Call by Reference: Yes
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
LOCK_FAILED -
Data type:Optional: No
Call by Reference: Yes
DELETE_FAILED -
Data type:Optional: No
Call by Reference: Yes
NOT_AUTHORIZED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_CONTRACTDEMANDVERSION_CPY 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_return | TYPE CL_ISM_SD_MESSAGE, " | |||
| lv_invalid | TYPE CL_ISM_SD_MESSAGE, " | |||
| lt_in_demand | TYPE STANDARD TABLE OF JKSDDEMAND, " | |||
| lv_fromversion | TYPE JSDVERSION, " | |||
| lv_not_found | TYPE JSDVERSION, " | |||
| lv_toversion | TYPE JSDVERSION, " | |||
| lv_lock_failed | TYPE JSDVERSION, " | |||
| lv_replace_all | TYPE JREPLACEALL, " ' ' | |||
| lv_replace_dup | TYPE JREPLACEDUP, " ' ' | |||
| lv_delete_failed | TYPE JREPLACEDUP, " | |||
| lv_not_authorized | TYPE JREPLACEDUP, " | |||
| lv_in_flag_change_fixed | TYPE XFELD. " |
|   CALL FUNCTION 'ISM_CONTRACTDEMANDVERSION_CPY' " |
| EXPORTING | ||
| FROMVERSION | = lv_fromversion | |
| TOVERSION | = lv_toversion | |
| REPLACE_ALL | = lv_replace_all | |
| REPLACE_DUP | = lv_replace_dup | |
| IN_FLAG_CHANGE_FIXED | = lv_in_flag_change_fixed | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| IN_DEMAND | = lt_in_demand | |
| EXCEPTIONS | ||
| INVALID = 1 | ||
| NOT_FOUND = 2 | ||
| LOCK_FAILED = 3 | ||
| DELETE_FAILED = 4 | ||
| NOT_AUTHORIZED = 5 | ||
| . " ISM_CONTRACTDEMANDVERSION_CPY | ||
ABAP code using 7.40 inline data declarations to call FM ISM_CONTRACTDEMANDVERSION_CPY
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.| DATA(ld_replace_all) | = ' '. | |||
| DATA(ld_replace_dup) | = ' '. | |||
Search for further information about these or an SAP related objects