ISM_SE_CREATE_ORDER SAP Function module - IS-M: Create Order via RFC

ISM_SE_CREATE_ORDER is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISM_SE_CREATE_ORDER into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JKSEORDER11
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISM_SE_CREATE_ORDER - ISM SE CREATE ORDER

CALL FUNCTION 'ISM_SE_CREATE_ORDER' "IS-M: Create Order via RFC
  EXPORTING
    in_logid =                  " jksdprotocolhead-logid  Internal Number of Log in System
*   in_testrun =                " bapiflag-bapiflag  Test Run
    in_order_type =             " jauart        Sales Document Type
    in_use_copy_control =       " jcopy_control
    in_lockid =                 " vbak-vbeln    Lock ID
*   in_success_msg =            " xfeld
  TABLES
    in_nextissue_tab =          " rjkseordergenerationnextissue
    in_addissue_tab =           " rjkseordergenerationadd  IS-M: Type for Order Generation via RFC
    .  "  ISM_SE_CREATE_ORDER

ABAP code example for Function Module ISM_SE_CREATE_ORDER

The ABAP code below is a full code listing to execute function module ISM_SE_CREATE_ORDER including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_in_nextissue_tab  
 
 TYPE STANDARD TABLE OF RJKSEORDERGENERATIONNEXTISSUE,"TABLES PARAM
wa_in_nextissue_tab
 
 LIKE LINE OF it_in_nextissue_tab
,
it_in_addissue_tab  
 
 TYPE STANDARD TABLE OF RJKSEORDERGENERATIONADD,"TABLES PARAM
wa_in_addissue_tab
 
 LIKE LINE OF it_in_addissue_tab
.

 

SELECT single LOGID 
  FROM JKSDPROTOCOLHEAD 
  INTO @DATA(ld_in_logid).



DATA(ld_in_testrun) = some text here

DATA(ld_in_order_type) = 'Check type of data required'.

DATA(ld_in_use_copy_control) = 'Check type of data required'.
 

SELECT single VBELN 
  FROM VBAK 
  INTO @DATA(ld_in_lockid).


DATA(ld_in_success_msg) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_in_nextissue_tab to it_in_nextissue_tab.
 

"populate fields of struture and append to itab
append wa_in_addissue_tab to it_in_addissue_tab.
.

CALL FUNCTION 'ISM_SE_CREATE_ORDER'
  EXPORTING
    in_logid =                   ld_in_logid
*   in_testrun =                 ld_in_testrun
    in_order_type =              ld_in_order_type
    in_use_copy_control =        ld_in_use_copy_control
    in_lockid =                  ld_in_lockid
*   in_success_msg =             ld_in_success_msg
  TABLES
    in_nextissue_tab =           it_in_nextissue_tab
    in_addissue_tab =            it_in_addissue_tab
    .  "  ISM_SE_CREATE_ORDER

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_in_logid
 
 TYPE JKSDPROTOCOLHEAD-LOGID ,
it_in_nextissue_tab
 
 TYPE STANDARD TABLE OF RJKSEORDERGENERATIONNEXTISSUE ,
wa_in_nextissue_tab
 
 LIKE LINE OF it_in_nextissue_tab,
ld_in_testrun
 
 TYPE BAPIFLAG-BAPIFLAG ,
it_in_addissue_tab
 
 TYPE STANDARD TABLE OF RJKSEORDERGENERATIONADD ,
wa_in_addissue_tab
 
 LIKE LINE OF it_in_addissue_tab,
ld_in_order_type
 
 TYPE JAUART ,
ld_in_use_copy_control
 
 TYPE JCOPY_CONTROL ,
ld_in_lockid
 
 TYPE VBAK-VBELN ,
ld_in_success_msg
 
 TYPE XFELD .



SELECT single LOGID 
  FROM JKSDPROTOCOLHEAD 
  INTO ld_in_logid.
 

"populate fields of struture and append to itab
append wa_in_nextissue_tab to it_in_nextissue_tab.

ld_in_testrun = some text here 

"populate fields of struture and append to itab
append wa_in_addissue_tab to it_in_addissue_tab.
ld_in_order_type = 'Check type of data required'.
ld_in_use_copy_control = 'Check type of data required'.

SELECT single VBELN 
  FROM VBAK 
  INTO ld_in_lockid.

ld_in_success_msg = 'Check type of data required'.