My Oracle Support Banner

E1: 34: R3483 MRP Multi-Plant Triggers Unique Constraint Error on the F3413 for Every F3413 "GD" Record for Process Items (Doc ID 2619677.1)

Last updated on DECEMBER 12, 2019

Applies to:

JD Edwards EnterpriseOne Requirements Planning - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.

Symptoms

When running R3483 - Multiplant MRP - for a Process parent and not suppressing the Time Series, a Unique Constraint error will occur on the F3413 for every F3413 "GD" record written.
 
OCI0000226 - Unable to execute - INSERT INTO PRODDTA.F3413 (MRITM, MRMCU, MRQT, MRSTRT, MRTRQT) VALUES (:BND1,:BND2,:BND3,:BND4,:BND5) in buffered mode (record 1 of 100)
OCI0000227 - Error - ORA-1: unique constraint (PRODDTA.F3413_PK) violated
OCI0000178 - Unable to execute - INSERT INTO PRODDTA.F3413 (MRITM, MRMCU, MRQT, MRSTRT, MRTRQT) VALUES (:BND1,:BND2,:BND3,:BND4,:BND5)
OCI0000179 - Error - DBOCI: error during buffered insert
JDB9900401 - Failed to execute db request
JDB3400009 - Failed to perform Insert for F3413
Exiting JDB_InsertTable with Failure (Table F3413)
 
This does not impact the results of MRP.

This issue can be reproduced at will using the following steps:

  1. Create  Process parent (STKT=R), ingredients and co-by products and set-up a simple Process routing.
  2. Create demand for the co-products via Sales Order or Forecast.
  3. Set-up a version of R3483 to use Process Mfg and not suppress the Time Series.
  4. Run R3483 on a Fat Client.
  5. Review the jde.log and jdedebug.log and note a unique constraint error on the first F3413 record when attempting to flush the buffer. This record is the [GD] Generation Date record.

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!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.