Is it true that Locks (SM12) not released after COMMIT?
Article ID: KB0092228
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | - |
| Not Applicable | - |
Description
Resolution:
When we use adapter with explicit commit option, in SM12 transaction it is seen that locks are not getting released after adapter has successfully processed the request.
There are some specific BAPI like BAPI_OBJCL_CHANGE at the SAP end which does not release the lock for some request and therefore the connection is not released.
This we can check at the SAP end itself without involving the adapter,
1) Do not start the adapter
2) Log on to SAP system and go to /NSE37 transaction
3) Give the name of the RFC and press F8
4) Give the same inputs which are causing the issue.
5) Do not give any value for "RFC Target Sys" field
6) Press F8 and check in the SM12 transaction in SAP whether the locks are still there.
When we use adapter with explicit commit option, in SM12 transaction it is seen that locks are not getting released after adapter has successfully processed the request.
There are some specific BAPI like BAPI_OBJCL_CHANGE at the SAP end which does not release the lock for some request and therefore the connection is not released.
This we can check at the SAP end itself without involving the adapter,
1) Do not start the adapter
2) Log on to SAP system and go to /NSE37 transaction
3) Give the name of the RFC and press F8
4) Give the same inputs which are causing the issue.
5) Do not give any value for "RFC Target Sys" field
6) Press F8 and check in the SM12 transaction in SAP whether the locks are still there.
Issue/Introduction
Is it true that Locks (SM12) not released after COMMIT?
Feedback
Yes
No
Powered by
