E1: 34: F3411 Table not being Populated with the Generated OP Number from P43060 in 9.0 (Doc ID 1615206.1)

Last updated on DECEMBER 23, 2015

Applies to:

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

Symptoms

On : 9.0 version, MRP P3411

ACTUAL BEHAVIOR
---------------
MRP Message Table - Update MMDOCO When Message Processed.

When an MRP Purchase Order message is processed, the MMDOCO in the F3411 table is not being populated with the order number that is created from the message processing. The document Type seems to be created fine but not the Order Number.


EXPECTED BEHAVIOR
-----------------------
Expect that the purchase order number be populated to F3411 when the order is created from processing P3411 purchase order message.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.  From P3411, select an OP order message with valid supplier.
2.  Row > Process Message. Processed message flag set to Y.
3.  Cancel out to display P43060 order screen. Form > Generate Orders.
4.  Close and reinquire. Note that the order number is not populated, but a new order exists in P4310. This is incorrect.

BUSINESS IMPACT
-----------------------
Due to this issue, users cannot review processed message to verify order number generated. Work around is to note order number prior to exit from P43060.

Cause

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 hundreds of Community platforms