Functionality
INCLUDE NBAPI_ISH
It unlocks a specific patient after processing.
This is only required if you call several BAPIs that write (change orcreate) data in direct succession for the same object instances, andfor this purpose, set a lock beforehand using BAPI_PATIENT_ENQUEUE
.
If you merely execute a single action (i.e. only one BAPI that writesdata for an object instance), it is not necessary to useBAPI_PATIENT_ENQUEUE or BAPI_PATIENT_DEQUEUE. For theirpart, the individual BAPIs lock their object instance.
When internal number assignment is used, it is not necessary to callBAPI_PATIENT_ENQUEUE or BAPI_PATIENT_DEQUEUE (since thePATIENTID to be created is not known). However, calling theseobjects in this situation has no negative consequences. If aPATIENTID is not included in the data passed, no data isunlocked.

Example
You want to create a patient master record using external numberassignment. You also want to create the risk factors for this patientwhen creating the patient master record. The correct call sequence isas follows:
RESET N1
BAPI_PATIENT_ENQUEUE
BAPI_PATIENT_CREATE
BAPI_TRANSACTION_COMMIT (with parameter WAIT = 'X')
BAPI_PATIENT_ADDRISKFACTOR
BAPI_TRANSACTION_COMMIT (with parameter WAIT = ' ')
BAPI_PATIENT_DEQUEUE

Notes
INCLUDE BAPI_RET
INCLUDE NBAPI_WORST_RETURNED_MSGTY
INCLUDE NBAPI_PATIENTID

Description
Any errors that occurred are returned in this table.