E1: 34: Entering a Branch Plant Relationship Record (P3403T) With Different Effective From and Thru Dates Ends in an Error "JAS MSG317 Duplicate Key Not Allowed" With Error ID 317
(Doc ID 2880108.1)
Last updated on JULY 04, 2022
Applies to:JD Edwards EnterpriseOne Requirements Planning - Version 9.2 and later
Information in this document applies to any platform.
When attempting to create a new branch plant relationship record by closing the previous record using effective through dates ends in the following error
"JAS MSG317 Duplicate key not allowed. Please correct the duplicate key field" Error ID 317
The issue can be reproduced at will with the following steps:
1. P3403T - Create a branch plant relationship record between supply branch S1 and demand branch D1 and source percent to 100% and effective through date to 12/31/2040 and save
2. P3403T - Reinquire and set the effective thru date to 7/31/2022
3. P3403T - Add a new line to create a branch plant relationship record between supply branch S1 and demand branch D1. Set effective from date to 1/8/2022, effective through date to 12/31/2040 and source percent to 80% and save
4. Observe a hard error "JAS MSG317 Duplicate key not allowed. Please correct the duplicate key field" is displayed
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