SAP BAPI_CASEDIAGNOSIS_CREATEMULT Function Module for IS-H BAPI CaseDiagnosis.CreateMultiple - Create Diagnoses for Case









BAPI_CASEDIAGNOSIS_CREATEMULT is a standard bapi casediagnosis createmult 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-H BAPI CaseDiagnosis.CreateMultiple - Create Diagnoses for Case 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 bapi casediagnosis createmult FM, simply by entering the name BAPI_CASEDIAGNOSIS_CREATEMULT into the relevant SAP transaction such as SE37 or SE38.

Function Group: 2098
Program Name: SAPL2098
Main Program: SAPL2098
Appliation area: N
Release date: 11-May-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_CASEDIAGNOSIS_CREATEMULT 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 'BAPI_CASEDIAGNOSIS_CREATEMULT'"IS-H BAPI CaseDiagnosis.CreateMultiple - Create Diagnoses for Case
  EXPORTING
   CLIENT =  "Client
   INSTITUTION =  "Institution
   PATCASEID =  "Case Number
*  TESTRUN = ' ' "Test Mode (No Changes in Database)

 IMPORTING
   WORST_RETURNED_MSGTY =  "Most Severe Message Type

TABLES
   INPUT_DIAGNOSIS =  "Table Containing Diagnosis Data to be Created
*  OUTPUT_DIAGNOSIS =  "Table Containing Generated Diagnosis Data
*  RETURN =  "Return Messages
.



IMPORTING Parameters details for BAPI_CASEDIAGNOSIS_CREATEMULT

CLIENT - Client

Data type: BAPINALL-CLIENT
Optional: No
Call by Reference: No ( called with pass by value option)

INSTITUTION - Institution

Data type: BAPI2098DATA-INSTITUTION
Optional: No
Call by Reference: No ( called with pass by value option)

PATCASEID - Case Number

Data type: BAPI2098DATA-PATCASEID
Optional: No
Call by Reference: No ( called with pass by value option)

TESTRUN - Test Mode (No Changes in Database)

Data type: BAPINALL-TESTRUN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_CASEDIAGNOSIS_CREATEMULT

WORST_RETURNED_MSGTY - Most Severe Message Type

Data type: BAPINALL-WORSTRETMSG
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_CASEDIAGNOSIS_CREATEMULT

INPUT_DIAGNOSIS - Table Containing Diagnosis Data to be Created

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

OUTPUT_DIAGNOSIS - Table Containing Generated Diagnosis Data

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

RETURN - Return Messages

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

Copy and paste ABAP code example for BAPI_CASEDIAGNOSIS_CREATEMULT 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_client  TYPE BAPINALL-CLIENT, "   
lt_input_diagnosis  TYPE STANDARD TABLE OF BAPI2098DATA, "   
lv_worst_returned_msgty  TYPE BAPINALL-WORSTRETMSG, "   
lv_institution  TYPE BAPI2098DATA-INSTITUTION, "   
lt_output_diagnosis  TYPE STANDARD TABLE OF BAPI2098DATA, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_patcaseid  TYPE BAPI2098DATA-PATCASEID, "   
lv_testrun  TYPE BAPINALL-TESTRUN. "   SPACE

  CALL FUNCTION 'BAPI_CASEDIAGNOSIS_CREATEMULT'  "IS-H BAPI CaseDiagnosis.CreateMultiple - Create Diagnoses for Case
    EXPORTING
         CLIENT = lv_client
         INSTITUTION = lv_institution
         PATCASEID = lv_patcaseid
         TESTRUN = lv_testrun
    IMPORTING
         WORST_RETURNED_MSGTY = lv_worst_returned_msgty
    TABLES
         INPUT_DIAGNOSIS = lt_input_diagnosis
         OUTPUT_DIAGNOSIS = lt_output_diagnosis
         RETURN = lt_return
. " BAPI_CASEDIAGNOSIS_CREATEMULT




ABAP code using 7.40 inline data declarations to call FM BAPI_CASEDIAGNOSIS_CREATEMULT

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 CLIENT FROM BAPINALL INTO @DATA(ld_client).
 
 
"SELECT single WORSTRETMSG FROM BAPINALL INTO @DATA(ld_worst_returned_msgty).
 
"SELECT single INSTITUTION FROM BAPI2098DATA INTO @DATA(ld_institution).
 
 
 
"SELECT single PATCASEID FROM BAPI2098DATA INTO @DATA(ld_patcaseid).
 
"SELECT single TESTRUN FROM BAPINALL INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 


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!