My Oracle Support Banner

E1:76B: PUC Not Defaulting As Per Transaction Nature/Suffix Setup in P76B432 For P4310BR and P4210BR (Doc ID 2311769.1)

Last updated on JULY 21, 2020

Applies to:

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


When creating a Sales Order (P4210BR) and/or Purchase Order (P4310BR) the system is not defaulting in the order detail the transaction nature and Purchase Use Code expected as per setup in its processing options and P76B432 Work with Purchase Use Code.

Bug 25447958 introduced application P76B432-Work with Purchase Use Code and its corresponding Table F76B4321 where specific Purchase Use Code information is setup based on transaction nature and suffix. At the same time, a new set of P4210BR and P4310BR Default/processing options was added so when PUC processing option 4 is set to 1, system will fetch the corresponding values from table F76B4321 and populate in the detail line purchase use code column. This is not happening.


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

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