SAP BAPI_CASE_CREATE Function Module for Create Case
BAPI_CASE_CREATE is a standard bapi case create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create 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 case create FM, simply by entering the name BAPI_CASE_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCMG_BAPI_CASE
Program Name: SAPLSCMG_BAPI_CASE
Main Program: SAPLSCMG_BAPI_CASE
Appliation area:
Release date: 19-May-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_CASE_CREATE 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_CASE_CREATE'"Create Case.
EXPORTING
CASE_TYPE = "Case Type of Case
* CASE_GUID = "Technical Key of Case
* CASE_WF_PATH = "Process Route Pattern ID
* SKIP_ERRORS = "Switch: Stop Insert After First Error
IMPORTING
GUID = "Technical Key of Case
TABLES
RETURN = "Return Code
* CASE_ATTRIBUTES = "Attribute Value Table
* CASE_NOTES = "Case Notes: Text Lines
* CASE_NOTE_IDS = "Case Notes: Text ID
* ELEMENT_IDENTIFICATION = "Identification of Elements to be Inserted
* ELEMENT_INSERTION = "Information for Inserting Elements into Record
* ELEMENT_ATTRIBUTES = "Additional Element Attributes
* ELEMENT_RELATIONS = "Element-Record Relation
IMPORTING Parameters details for BAPI_CASE_CREATE
CASE_TYPE - Case Type of Case
Data type: BAPISCMGCASE-CASE_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
CASE_GUID - Technical Key of Case
Data type: BAPISCMGCASE-CASE_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
CASE_WF_PATH - Process Route Pattern ID
Data type: BAPISCMGCASE-WF_TEMPLATE_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
SKIP_ERRORS - Switch: Stop Insert After First Error
Data type: BAPISRMREC-BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_CASE_CREATE
GUID - Technical Key of Case
Data type: BAPISCMGCASE-CASE_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_CASE_CREATE
RETURN - Return Code
Data type: BAPIRET2Optional: No
Call by Reference: Yes
CASE_ATTRIBUTES - Attribute Value Table
Data type: BAPIPROPTBOptional: Yes
Call by Reference: Yes
CASE_NOTES - Case Notes: Text Lines
Data type: BAPINOTEOptional: Yes
Call by Reference: Yes
CASE_NOTE_IDS - Case Notes: Text ID
Data type: BAPINOTEIDOptional: Yes
Call by Reference: Yes
ELEMENT_IDENTIFICATION - Identification of Elements to be Inserted
Data type: BAPIPROPMEOptional: Yes
Call by Reference: Yes
ELEMENT_INSERTION - Information for Inserting Elements into Record
Data type: BAPIDOCINSOptional: Yes
Call by Reference: Yes
ELEMENT_ATTRIBUTES - Additional Element Attributes
Data type: BAPIPROPMEOptional: Yes
Call by Reference: Yes
ELEMENT_RELATIONS - Element-Record Relation
Data type: BAPIRELTBOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_CASE_CREATE 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_guid | TYPE BAPISCMGCASE-CASE_GUID, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_case_type | TYPE BAPISCMGCASE-CASE_TYPE, " | |||
| lv_case_guid | TYPE BAPISCMGCASE-CASE_GUID, " | |||
| lt_case_attributes | TYPE STANDARD TABLE OF BAPIPROPTB, " | |||
| lt_case_notes | TYPE STANDARD TABLE OF BAPINOTE, " | |||
| lv_case_wf_path | TYPE BAPISCMGCASE-WF_TEMPLATE_ID, " | |||
| lv_skip_errors | TYPE BAPISRMREC-BOOLEAN, " | |||
| lt_case_note_ids | TYPE STANDARD TABLE OF BAPINOTEID, " | |||
| lt_element_identification | TYPE STANDARD TABLE OF BAPIPROPME, " | |||
| lt_element_insertion | TYPE STANDARD TABLE OF BAPIDOCINS, " | |||
| lt_element_attributes | TYPE STANDARD TABLE OF BAPIPROPME, " | |||
| lt_element_relations | TYPE STANDARD TABLE OF BAPIRELTB. " |
|   CALL FUNCTION 'BAPI_CASE_CREATE' "Create Case |
| EXPORTING | ||
| CASE_TYPE | = lv_case_type | |
| CASE_GUID | = lv_case_guid | |
| CASE_WF_PATH | = lv_case_wf_path | |
| SKIP_ERRORS | = lv_skip_errors | |
| IMPORTING | ||
| GUID | = lv_guid | |
| TABLES | ||
| RETURN | = lt_return | |
| CASE_ATTRIBUTES | = lt_case_attributes | |
| CASE_NOTES | = lt_case_notes | |
| CASE_NOTE_IDS | = lt_case_note_ids | |
| ELEMENT_IDENTIFICATION | = lt_element_identification | |
| ELEMENT_INSERTION | = lt_element_insertion | |
| ELEMENT_ATTRIBUTES | = lt_element_attributes | |
| ELEMENT_RELATIONS | = lt_element_relations | |
| . " BAPI_CASE_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_CASE_CREATE
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 CASE_GUID FROM BAPISCMGCASE INTO @DATA(ld_guid). | ||||
| "SELECT single CASE_TYPE FROM BAPISCMGCASE INTO @DATA(ld_case_type). | ||||
| "SELECT single CASE_GUID FROM BAPISCMGCASE INTO @DATA(ld_case_guid). | ||||
| "SELECT single WF_TEMPLATE_ID FROM BAPISCMGCASE INTO @DATA(ld_case_wf_path). | ||||
| "SELECT single BOOLEAN FROM BAPISRMREC INTO @DATA(ld_skip_errors). | ||||
Search for further information about these or an SAP related objects