Object Management Workbench (OMW) in JD Edwards EnterpriseOne controls object development, check-in/check-out status, and token locking. Understanding how objects and tokens are tracked in the database is critical for CNC administrators and developers troubleshooting locked objects or development issues.
This blog explains how to:
-
List objects based on check-out status
-
Identify token usage
-
Find checked-in / checked-out objects
-
Release OMW tokens using SQL
1. List of Objects Not Checked Out and No Token
This query returns objects that are:
-
NOT checked out
-
NOT holding any token
SELECT * FROM SY920.F98222
WHERE POOMWCHS = '0'
AND POOMWOST = '02'
AND POOMWPOS1 = '0'
AND POOMWPON1 = 0
AND POOMWPRJID = 'Project_Name';
2. List of Objects Not Checked Out but Have Token
This query identifies objects that:
-
Are NOT checked out
-
STILL hold a token
SELECT *
FROM SY920.F98222
WHERE POOMWCHS = '0'
AND POOMWOST = '02'
AND POOMWPOS1 = '1'
AND POOMWPRJID = 'Project_Name';
3. List of Objects Checked Out and Have Token
This query returns objects that are:
-
Currently checked out
-
Holding a token
SELECT *
FROM SY920.F98222
WHERE POOMWCHS = '1'
AND POOMWOST = '03'
AND POOMWPOS1 = '1'
AND POOMWPRJID = 'Project_Name';
4. Release OMW Token Using SQL
In some cases, tokens remain locked due to:
-
Unexpected session termination
-
Network disconnection
-
Abnormal OMW exit
You can release the token using SQL update.
UPDATE SY920.F98222
SET POOMWPOS1 = '0',
POOMWPON1 = 0
WHERE POOMWOST = '02'
AND POOMWPOS1 = '1'
AND POOMWPRJID LIKE 'Project_Name';