SAP ISHMED_CORDER_CR_SIMPLE Function Module for









ISHMED_CORDER_CR_SIMPLE is a standard ishmed corder cr simple 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 ishmed corder cr simple FM, simply by entering the name ISHMED_CORDER_CR_SIMPLE into the relevant SAP transaction such as SE37 or SE38.

Function Group: N1CONN_WS
Program Name: SAPLN1CONN_WS
Main Program: SAPLN1CONN_WS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ISHMED_CORDER_CR_SIMPLE 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 'ISHMED_CORDER_CR_SIMPLE'"
  EXPORTING
   I_LOCALPATIENTID =  "Connectivity: Partner Patient ID
   I_INSTITUTION =  "IS-H: Institution
   I_BPID =  "Connectivity: Business Partner ID
   I_FILLERID =  "CORD/Prereg.: Treatment Organizational Unit
   I_ORDERTYPEID =  "IS-H: CORD/PREG: Identification of the Clinical Order Type
*  I_ORDER_REMARK =  "IS-H: Comment Text

 IMPORTING
   E_RC =  "IS-H: Return Code for Method Calls
   ET_MESSAGES =  "IS-H*MED: Table Type for Table BAPIRET2
   ET_ERRORMESSAGES =  "Table with Error Messages from Web Services
   E_ORDERID =  "IS-H: CORD/PREG: Identification of a Clinical Order
   E_ORDERNO =  "Order Number
.



IMPORTING Parameters details for ISHMED_CORDER_CR_SIMPLE

I_LOCALPATIENTID - Connectivity: Partner Patient ID

Data type: N1CONN_LPID
Optional: No
Call by Reference: No ( called with pass by value option)

I_INSTITUTION - IS-H: Institution

Data type: EINRI
Optional: No
Call by Reference: No ( called with pass by value option)

I_BPID - Connectivity: Business Partner ID

Data type: N1CONN_BPID
Optional: No
Call by Reference: No ( called with pass by value option)

I_FILLERID - CORD/Prereg.: Treatment Organizational Unit

Data type: N1VKGOE
Optional: No
Call by Reference: No ( called with pass by value option)

I_ORDERTYPEID - IS-H: CORD/PREG: Identification of the Clinical Order Type

Data type: N1COTID
Optional: No
Call by Reference: No ( called with pass by value option)

I_ORDER_REMARK - IS-H: Comment Text

Data type: STRING
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISHMED_CORDER_CR_SIMPLE

E_RC - IS-H: Return Code for Method Calls

Data type: ISH_METHOD_RC
Optional: No
Call by Reference: No ( called with pass by value option)

ET_MESSAGES - IS-H*MED: Table Type for Table BAPIRET2

Data type: ISHMED_T_BAPIRET2
Optional: No
Call by Reference: No ( called with pass by value option)

ET_ERRORMESSAGES - Table with Error Messages from Web Services

Data type: ISH_T_WS_MSG
Optional: No
Call by Reference: No ( called with pass by value option)

E_ORDERID - IS-H: CORD/PREG: Identification of a Clinical Order

Data type: N1CORDID
Optional: No
Call by Reference: No ( called with pass by value option)

E_ORDERNO - Order Number

Data type: N1CORDNR
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISHMED_CORDER_CR_SIMPLE 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_e_rc  TYPE ISH_METHOD_RC, "   
lv_i_localpatientid  TYPE N1CONN_LPID, "   
lv_et_messages  TYPE ISHMED_T_BAPIRET2, "   
lv_i_institution  TYPE EINRI, "   
lv_i_bpid  TYPE N1CONN_BPID, "   
lv_et_errormessages  TYPE ISH_T_WS_MSG, "   
lv_e_orderid  TYPE N1CORDID, "   
lv_i_fillerid  TYPE N1VKGOE, "   
lv_e_orderno  TYPE N1CORDNR, "   
lv_i_ordertypeid  TYPE N1COTID, "   
lv_i_order_remark  TYPE STRING. "   

  CALL FUNCTION 'ISHMED_CORDER_CR_SIMPLE'  "
    EXPORTING
         I_LOCALPATIENTID = lv_i_localpatientid
         I_INSTITUTION = lv_i_institution
         I_BPID = lv_i_bpid
         I_FILLERID = lv_i_fillerid
         I_ORDERTYPEID = lv_i_ordertypeid
         I_ORDER_REMARK = lv_i_order_remark
    IMPORTING
         E_RC = lv_e_rc
         ET_MESSAGES = lv_et_messages
         ET_ERRORMESSAGES = lv_et_errormessages
         E_ORDERID = lv_e_orderid
         E_ORDERNO = lv_e_orderno
. " ISHMED_CORDER_CR_SIMPLE




ABAP code using 7.40 inline data declarations to call FM ISHMED_CORDER_CR_SIMPLE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!