SAP BAPI_CASESERVICE_CH_XML Function Module for
BAPI_CASESERVICE_CH_XML is a standard bapi caseservice ch xml 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 bapi caseservice ch xml FM, simply by entering the name BAPI_CASESERVICE_CH_XML into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2099CH
Program Name: SAPL2099CH
Main Program: SAPL2099CH
Appliation area: N
Release date: 28-Oct-2003
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_CASESERVICE_CH_XML 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_CASESERVICE_CH_XML'".
EXPORTING
CLIENT = "
* TESTRUN = ' ' "
IMPORTING
WORST_RETURNED_MSGTY = "
TABLES
CASESERVICE_XML = "
* CASESERVICE_DATA = "
* CASESERVICE_ASSPAR = "
* CASESERVICE_ASSSRV = "
* CASESERVICE_TIMEUNITMEAS = "
* CASEDIAGNOSIS = "
* RETURN = "
* RETURN_XML = "
IMPORTING Parameters details for BAPI_CASESERVICE_CH_XML
CLIENT -
Data type: BAPINALL-CLIENTOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN -
Data type: BAPINALL-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_CASESERVICE_CH_XML
WORST_RETURNED_MSGTY -
Data type: BAPINALL-WORSTRETMSGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_CASESERVICE_CH_XML
CASESERVICE_XML -
Data type: BAPI2099CHXMLOptional: No
Call by Reference: Yes
CASESERVICE_DATA -
Data type: BAPI2099DATAOptional: Yes
Call by Reference: Yes
CASESERVICE_ASSPAR -
Data type: BAPI2099ASSPAROptional: Yes
Call by Reference: Yes
CASESERVICE_ASSSRV -
Data type: BAPI2099ASSSRVOptional: Yes
Call by Reference: Yes
CASESERVICE_TIMEUNITMEAS -
Data type: BAPI2099CHTIMEUNITMEASOptional: Yes
Call by Reference: Yes
CASEDIAGNOSIS -
Data type: BAPI2098DATAOptional: Yes
Call by Reference: Yes
RETURN -
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
RETURN_XML -
Data type: BAPI2099CHXMLOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_CASESERVICE_CH_XML 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_caseservice_xml | TYPE STANDARD TABLE OF BAPI2099CHXML, " | |||
| lv_worst_returned_msgty | TYPE BAPINALL-WORSTRETMSG, " | |||
| lv_testrun | TYPE BAPINALL-TESTRUN, " SPACE | |||
| lt_caseservice_data | TYPE STANDARD TABLE OF BAPI2099DATA, " | |||
| lt_caseservice_asspar | TYPE STANDARD TABLE OF BAPI2099ASSPAR, " | |||
| lt_caseservice_asssrv | TYPE STANDARD TABLE OF BAPI2099ASSSRV, " | |||
| lt_caseservice_timeunitmeas | TYPE STANDARD TABLE OF BAPI2099CHTIMEUNITMEAS, " | |||
| lt_casediagnosis | TYPE STANDARD TABLE OF BAPI2098DATA, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_return_xml | TYPE STANDARD TABLE OF BAPI2099CHXML. " |
|   CALL FUNCTION 'BAPI_CASESERVICE_CH_XML' " |
| EXPORTING | ||
| CLIENT | = lv_client | |
| TESTRUN | = lv_testrun | |
| IMPORTING | ||
| WORST_RETURNED_MSGTY | = lv_worst_returned_msgty | |
| TABLES | ||
| CASESERVICE_XML | = lt_caseservice_xml | |
| CASESERVICE_DATA | = lt_caseservice_data | |
| CASESERVICE_ASSPAR | = lt_caseservice_asspar | |
| CASESERVICE_ASSSRV | = lt_caseservice_asssrv | |
| CASESERVICE_TIMEUNITMEAS | = lt_caseservice_timeunitmeas | |
| CASEDIAGNOSIS | = lt_casediagnosis | |
| RETURN | = lt_return | |
| RETURN_XML | = lt_return_xml | |
| . " BAPI_CASESERVICE_CH_XML | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_CASESERVICE_CH_XML
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 TESTRUN FROM BAPINALL INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
Search for further information about these or an SAP related objects