SAP BAPI_CASE_CHANGE Function Module for Changes to Case
BAPI_CASE_CHANGE is a standard bapi case change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Changes to 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 change FM, simply by entering the name BAPI_CASE_CHANGE 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_CHANGE 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_CHANGE'"Changes to Case.
EXPORTING
GUID = "Technical Case Key (Case GUID)
* SKIP_ERRORS = "Switch: Stop Change Action After First Error
* NEW_VERSION = "Switch: Save Record as New Version
* DELETE_ONLY_FIRST = 'X' "Switch: Delete First Element Found or All Elements of this Type
TABLES
RETURN = "Return Parameters
* ELEMENT_IDENT_SP_POID = "SP Part of Element POID, Including Encoded Element Type
* CASE_ATTRIBUTES = "Case Attributes to Be Changed
* CASE_NOTE_IDS = "Case Notes: Text ID
* CASE_NOTES = "Notes to Be Inserted in Case
* 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
* ELEMENT_IDENT_RECPOS = "'Delete From' Node ID in Record
IMPORTING Parameters details for BAPI_CASE_CHANGE
GUID - Technical Case Key (Case GUID)
Data type: BAPISCMGCASE-CASE_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
SKIP_ERRORS - Switch: Stop Change Action After First Error
Data type: BAPISRMREC-BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
NEW_VERSION - Switch: Save Record as New Version
Data type: BAPISRMREC-BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
DELETE_ONLY_FIRST - Switch: Delete First Element Found or All Elements of this Type
Data type: BAPISRMREC-BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_CASE_CHANGE
RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: Yes
ELEMENT_IDENT_SP_POID - SP Part of Element POID, Including Encoded Element Type
Data type: BAPIPROPMEOptional: Yes
Call by Reference: Yes
CASE_ATTRIBUTES - Case Attributes to Be Changed
Data type: BAPIPROPTBOptional: Yes
Call by Reference: Yes
CASE_NOTE_IDS - Case Notes: Text ID
Data type: BAPINOTEIDOptional: Yes
Call by Reference: Yes
CASE_NOTES - Notes to Be Inserted in Case
Data type: BAPINOTEOptional: 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
ELEMENT_IDENT_RECPOS - 'Delete From' Node ID in Record
Data type: BAPIRECPOSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_CASE_CHANGE 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, " | |||
lt_element_ident_sp_poid | TYPE STANDARD TABLE OF BAPIPROPME, " | |||
lv_skip_errors | TYPE BAPISRMREC-BOOLEAN, " | |||
lt_case_attributes | TYPE STANDARD TABLE OF BAPIPROPTB, " | |||
lv_new_version | TYPE BAPISRMREC-BOOLEAN, " | |||
lt_case_note_ids | TYPE STANDARD TABLE OF BAPINOTEID, " | |||
lt_case_notes | TYPE STANDARD TABLE OF BAPINOTE, " | |||
lv_delete_only_first | TYPE BAPISRMREC-BOOLEAN, " 'X' | |||
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, " | |||
lt_element_ident_recpos | TYPE STANDARD TABLE OF BAPIRECPOS. " |
  CALL FUNCTION 'BAPI_CASE_CHANGE' "Changes to Case |
EXPORTING | ||
GUID | = lv_guid | |
SKIP_ERRORS | = lv_skip_errors | |
NEW_VERSION | = lv_new_version | |
DELETE_ONLY_FIRST | = lv_delete_only_first | |
TABLES | ||
RETURN | = lt_return | |
ELEMENT_IDENT_SP_POID | = lt_element_ident_sp_poid | |
CASE_ATTRIBUTES | = lt_case_attributes | |
CASE_NOTE_IDS | = lt_case_note_ids | |
CASE_NOTES | = lt_case_notes | |
ELEMENT_IDENTIFICATION | = lt_element_identification | |
ELEMENT_INSERTION | = lt_element_insertion | |
ELEMENT_ATTRIBUTES | = lt_element_attributes | |
ELEMENT_RELATIONS | = lt_element_relations | |
ELEMENT_IDENT_RECPOS | = lt_element_ident_recpos | |
. " BAPI_CASE_CHANGE |
ABAP code using 7.40 inline data declarations to call FM BAPI_CASE_CHANGE
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 BOOLEAN FROM BAPISRMREC INTO @DATA(ld_skip_errors). | ||||
"SELECT single BOOLEAN FROM BAPISRMREC INTO @DATA(ld_new_version). | ||||
"SELECT single BOOLEAN FROM BAPISRMREC INTO @DATA(ld_delete_only_first). | ||||
DATA(ld_delete_only_first) | = 'X'. | |||
Search for further information about these or an SAP related objects