SAP BAPI_PATCASE_ADDABSENCE Function Module for IS-H BAPI PatientCase.AddAbsence - Create Absence
BAPI_PATCASE_ADDABSENCE is a standard bapi patcase addabsence 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 PatientCase.AddAbsence - Create Absence 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 patcase addabsence FM, simply by entering the name BAPI_PATCASE_ADDABSENCE into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2097
Program Name: SAPL2097
Main Program: SAPL2097
Appliation area: N
Release date: 31-Jul-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PATCASE_ADDABSENCE 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_PATCASE_ADDABSENCE'"IS-H BAPI PatientCase.AddAbsence - Create Absence.
EXPORTING
CLIENT = "Client
INSTITUTION = "Institution
PATCASEID = "Case Number
INPAT_ABSENCE_DATA = "Data for Case to Be Changed and Absence to Be Created
* TESTRUN = ' ' "Test Mode (No Changes in Database)
IMPORTING
NEW_PATCASE_DATA = "Case Data Changed
NEW_MOVEMNT_DATA_BEG = "Movement Data (Start of Absence) Created
NEW_MOVEMNT_DATA_END = "Movement Data (End of Absence) Created
WORST_RETURNED_MSGTY = "Most Severe Message Type
TABLES
* RETURN = "Return Messages
IMPORTING Parameters details for BAPI_PATCASE_ADDABSENCE
CLIENT - Client
Data type: BAPINALL-CLIENTOptional: No
Call by Reference: No ( called with pass by value option)
INSTITUTION - Institution
Data type: BAPINALL-INSTITUTIONOptional: No
Call by Reference: No ( called with pass by value option)
PATCASEID - Case Number
Data type: BAPINALL-PATCASEIDOptional: No
Call by Reference: No ( called with pass by value option)
INPAT_ABSENCE_DATA - Data for Case to Be Changed and Absence to Be Created
Data type: BAPI2097IABINOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN - Test Mode (No Changes in Database)
Data type: BAPINALL-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_PATCASE_ADDABSENCE
NEW_PATCASE_DATA - Case Data Changed
Data type: BAPI2097CASEOptional: No
Call by Reference: No ( called with pass by value option)
NEW_MOVEMNT_DATA_BEG - Movement Data (Start of Absence) Created
Data type: BAPI2097MOVEOptional: No
Call by Reference: No ( called with pass by value option)
NEW_MOVEMNT_DATA_END - Movement Data (End of Absence) Created
Data type: BAPI2097MOVEOptional: No
Call by Reference: No ( called with pass by value option)
WORST_RETURNED_MSGTY - Most Severe Message Type
Data type: BAPINALL-WORSTRETMSGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_PATCASE_ADDABSENCE
RETURN - Return Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_PATCASE_ADDABSENCE 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_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_new_patcase_data | TYPE BAPI2097CASE, " | |||
| lv_institution | TYPE BAPINALL-INSTITUTION, " | |||
| lv_new_movemnt_data_beg | TYPE BAPI2097MOVE, " | |||
| lv_patcaseid | TYPE BAPINALL-PATCASEID, " | |||
| lv_new_movemnt_data_end | TYPE BAPI2097MOVE, " | |||
| lv_inpat_absence_data | TYPE BAPI2097IABIN, " | |||
| lv_worst_returned_msgty | TYPE BAPINALL-WORSTRETMSG, " | |||
| lv_testrun | TYPE BAPINALL-TESTRUN. " SPACE |
|   CALL FUNCTION 'BAPI_PATCASE_ADDABSENCE' "IS-H BAPI PatientCase.AddAbsence - Create Absence |
| EXPORTING | ||
| CLIENT | = lv_client | |
| INSTITUTION | = lv_institution | |
| PATCASEID | = lv_patcaseid | |
| INPAT_ABSENCE_DATA | = lv_inpat_absence_data | |
| TESTRUN | = lv_testrun | |
| IMPORTING | ||
| NEW_PATCASE_DATA | = lv_new_patcase_data | |
| NEW_MOVEMNT_DATA_BEG | = lv_new_movemnt_data_beg | |
| NEW_MOVEMNT_DATA_END | = lv_new_movemnt_data_end | |
| WORST_RETURNED_MSGTY | = lv_worst_returned_msgty | |
| TABLES | ||
| RETURN | = lt_return | |
| . " BAPI_PATCASE_ADDABSENCE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_PATCASE_ADDABSENCE
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 INSTITUTION FROM BAPINALL INTO @DATA(ld_institution). | ||||
| "SELECT single PATCASEID FROM BAPINALL INTO @DATA(ld_patcaseid). | ||||
| "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