E1: 49: Ship Confirm (P4205) Transaction Processing Error on OTM Table
(Doc ID 2383556.1)
Last updated on FEBRUARY 01, 2019
Applies to:JD Edwards EnterpriseOne EDI - Version 9.1 to 9.2 [Release 9.1 to 9.2]
Information in this document applies to any platform.
When attempting to Ship Confirm (P4205) any sales order in the CRP environment (JPY910) the following error occurs.
Transaction cannot be committed. It was canceled.
The logs show the SQL Update to Sales Order Detail File - Secondary Tag Table (CRPDTA/F49T211) Fails, causing the transaction to rollback.
The Databrowser shows that there are no records in the Sales Order Detail File - Secondary Tag Table (CRPDTA/F49T211). This table is only used the Oracle Transportation Management (SY49T) module.
We checked the Enabled Functionality (P99410) and they do NOT have Oracle Transportation Management (SY49T) enabled.
When they test on a Windows Fat Client (PY910) with the same data, the problem does not occur.
The problem started after they upgraded their AS/400 Operating System from V7R1 to V7R2.
The issue can be reproduced at will on the JPY910 environment with the following steps:
- In Work With Shipment Confirmation (P4205), find a Sales Order and select the record.
- Click Ok to ship confirm the full quantity
- Return to Work With Shipment Confirmation (P4205) and click Find which displays error Transaction cannot be committed. It was canceled.
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