Record Lock Found When Click Cancel Button To Close The Receiving Control Form Without Change
(Doc ID 2257536.1)
Last updated on MARCH 15, 2022
Applies to:
Oracle Purchasing - Version 12.1.3 and laterOracle Inventory Management - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Symptoms
On : 12.1.3 version, Receiving Functions
When attempting to create receipt against purchase order, the following error occurs.
Error:
APP-FND-00204: Concurrent Manager encountered an error while running the spawned concurrent program Receiving Transaction Manager - RCVOLTM for your concurrent request 19132388. TM-TIMEOUT
Replication Steps:
The issue can be reproduced at will with the following steps:
1) Login as a Buyer -> Search and locate the Purchase Order
2) Open it -> Choose Lines - then Shipments -> Open Receiving Control -> Click Cancel
3) Check using sql developer and found record lock on the PO_HEADERS_ALL, PO_LINES_ALL and PO_LINE_LOCATIONS_ALL table
4) As th form remains open – the locking is not gone
5) Login with another user and perform a Purchase Order receipt on the above Purchase Order.
It is not possible since the record is locked
6) Save the Receipt gives the following error.
APP-FND-00204: Concurrent Manager encountered an error while running the spawned concurrent program Receiving Transaction Manager - RCVOLTM for your concurrent request 19132387. TM-TIMEOUT
Script to find the lock:
SELECT NVL(S.USERNAME,'Internal') username,s.process EBS_PID,l.ctime,s.machine,L.SID||','||S.SERIAL# Kill,s.module,U1.NAME||'.'
|SUBSTR(T1.NAME,1,20) table_name,
DECODE(L.LMODE,1,'No Lock', 2,'Row Share', 3,'Row Exclusive', 4,'Share', 5,'Share Row Exclusive', 6,'Exclusive',NULL) lmode,
s.program,
DECODE(L.REQUEST,1,'No Lock', 2,'Row Share', 3,'Row Exclusive', 4,'Share', 5,'Share Row Exclusive', 6,'Exclusive',NULL) request
FROM V$LOCK L,
V$SESSION S,
SYS.USER$ U1,
SYS.OBJ$ T1
WHERE L.SID = S.SID
AND T1.OBJ# = DECODE(L.ID2,0,L.ID1,L.ID2)
AND U1.USER# = T1.OWNER#
AND S.TYPE != 'BACKGROUND'
AND U1.name != 'SYS'
ORDER BY l.ctime DESC,
2,6 ;
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |