E1: 43: ProcessPurchaseOrder JP430000 Not Creating F4209 When Putting Order On Hold

(Doc ID 2128623.1)

Last updated on OCTOBER 03, 2017

Applies to:

JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.1 and later
Information in this document applies to any platform.


On : 9.1 version, BSSV

When a hold code is entered for an existing order in P4310 it populates the F4301 with the hold code and writes a F4209 record. When doing the same via processPurchaseOrder JP430000 it does not write a F4209 record.

When processing via processPurchaseOrder JP430000 it should write a F4209 record.

The issue can be reproduced at will with the following steps:
1) P4310. Create a new stock order and save.
2) P4310. Re-inquire in header mode and populate a Hold Code and click OK through the order.
3) P4310. Note the header and F4209 are populated with the hold code.
4) P4310. Create another new stock order and save.
5) soapUI. Create a payload to update the order header with a hold code and submit.
6) P4310. Note the header is populated with the hold code but no F4209 record was written.
The issue has the following business impact:
Due to this issue, users cannot release purchase orders on hold via P43070.


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