Ansicht
Dokumentation

BAPI_PATIENT_ENQUEUE - IS-H BAPI Patient.Enqueue - Enqueue Patient

General Material Data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Functionality

It locks a specific patient to prevent further processing. This lock remains active until explicit unlocking. This prevents a patient data record 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 same object instance. Only such a lock prevents another user from accessing the data in between. If you set a lock using BAPI_PATIENT_ENQUEUE, you must cancel this lock using BAPI_PATIENT_DEQUEUE after your actions have been executed.

If internal number assignment is used when creating a patient, it is not necessary to call BAPI_PATIENT_ENQUEUE (since the PATIENTID to be locked 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 locked.

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

N_PATI_AKT.

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

PERFORM Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 2529 Date: 20240606 Time: 111724     sap01-206 ( 49 ms )