Ansicht
Dokumentation

BAPI_PATCASE_ENQUEUE - IS-H BAPI PatientCase.Enqueue - Enqueue Case

rdisp/max_wprun_time - Maximum work process run time   General Material Data  
This documentation is copyright by SAP AG.

Functionality

It locks a specific case to prevent further processing. This lock remains active until explicit unlocking. This prevents a case from being processed by several users at the same time.

This is only necessary if you call several BAPIs that write (change or create) data in direct succession for the object PatientCase or for other case-related objects (CaseService, CaseDiagnosis, for example). Only such a lock prevents another user from accessing the data in between. If you set set a lock using BAPI_PATCASE_ENQUEUE, you must cancel this lock using BAPI_PATCASE_DEQUEUE after your actions have been executed.

If you use internal number assignment when creating a new case, it is not necessary to call BAPI_PATCASE_ENQUEUE (since the PATCASEID to be locked is not known). However, calling these objects in this situation has no negative consequences. If a PATCASEID is not included in the data passed to the method, no data is locked.

Example

You want to create a case using exrternal number assignment. The correct call sequence is as follows:

1. BAPI_PATCASE_ENQUEUE
2. BAPI_PATCASE_ADDINPATADMISS
3. BAPI_TRANSACTION_COMMIT (with parameter WAIT = ' ')
4. BAPI_PATCASE_DEQUEUE

Notes

N_FALL_FNR.

Messages are returned in the Return parameter. The parameter documentation shows the return codes and their meanings.

Further information

Parameters

INSTITUTION
PATCASEID
RETURN
WORST_RETURNED_MSGTY

Exceptions

Function Group

2097

ABAP Short Reference   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 2408 Date: 20240523 Time: 181013     sap01-206 ( 51 ms )