E1: OMW: Version Check in Fails and E1 Crashes when Trying to Checkin a Version to Environment Different from Login Environment
(Doc ID 2082013.1)
Last updated on FEBRUARY 10, 2022
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 to 9.2 [Release 9.2]Information in this document applies to any platform.
Symptoms
When trying to check in a batch version into 2 path codes at the same time by logging into DV and using project code 26 to check in a version, Version check in fails and E1 crashes.
STEPS TO REPRODUCE ISSUE
----------
1. Log into EnterpriseOne fat client , Make sure to log into DV920
2. Fast Path: OMW
3. Create a version in a project with status 26.
4. Check in the version
5. Check in will fail and E1 crashes
Same issue might also occur if you try to check in a batch version at status 21 but OMW transfer activity rules for status 21 are configured to transfer the specs to two locations . In such cases you will notice two records for transfer activity rules for UBEVER Object type.
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 |