Ansicht
Dokumentation

BAPI_PATIENT_DEQUEUE - IS-H BAPI Patient.Dequeue - Dequeue Patient

CL_GUI_FRONTEND_SERVICES - Frontend Services   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Functionality

It unlocks a specific patient after processing.

This is only required if you call several BAPIs that write (change or create) data in direct succession for the same object instances, and for this purpose, set a lock beforehand using BAPI_PATIENT_ENQUEUE.

If you merely execute a single action (i.e. only one BAPI that writes data for an object instance), it is not necessary to use BAPI_PATIENT_ENQUEUE or BAPI_PATIENT_DEQUEUE. For their part, the individual BAPIs lock their object instance.

When internal number assignment is used, it is not necessary to call BAPI_PATIENT_ENQUEUE or BAPI_PATIENT_DEQUEUE (since the PATIENTID to be created is not known). However, calling these objects in this situation has no negative consequences. If a PATIENTID is not included in the data passed, no data is unlocked.

Example

You want to create a patient master record using external number assignment. You also want to create the risk factors for this patient when creating the patient master record. The correct call sequence is as follows:

1. BAPI_PATIENT_ENQUEUE
2. BAPI_PATIENT_CREATE
3. BAPI_TRANSACTION_COMMIT (with parameter WAIT = 'X')
4. BAPI_PATIENT_ADDRISKFACTOR
5. BAPI_TRANSACTION_COMMIT (with parameter WAIT = ' ')
6. BAPI_PATIENT_DEQUEUE

Notes

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

Further information

Parameters

PATIENTID
RETURN
WORST_RETURNED_MSGTY

Exceptions

Function Group

1084

BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 2523 Date: 20240523 Time: 182750     sap01-206 ( 44 ms )