My Oracle Support Banner

E1: 76B: Transfer Order Not Fetching Purchase Use Code (PUC) From P76B432 As Instructed in Brazilian -Purchase Order (P4310BR) (Doc ID 2622419.1)

Last updated on JULY 21, 2020

Applies to:

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

Symptoms

 

When creating a Transfer Order, the Sales order (P4210/P4210BR ZJDE7007) correctly retrieves the PUC from P76B432 as per setup in the processing options. However, on the Purchase Order side of the transfer order,  (P4310/P4310BR ZJDE7007), the system fails to follow the  P4310BR processing option instruction (B76PSE) = 1,  for PUC to be fetched from  P76B432  for the corresponding  transaction nature and suffix.  The new purchase order generated updates the  Purchase Order Detail Tag File-Brazil (F76B432) incorectly. 

 
The setup and steps to reproduce this symptom are:

Activate Brazilian Localization in User Profile (BR)

Setup:

1. P76B15 Work With Transaction Nature
2. P76B432 with the transaction nature/suffix/PUC to be used. For this test : SO: 611/00/RES  and  PO: 212/00/RW
3. Transfer Order versions for P4210/P4210BR and P4310/P4310BR ZJDE7007, which should include value equal 1 in the processing option for the PUC retrieval from P76B432-Transaction Nature/Suffix/PUC

 

Steps:

1. (P4210 ZJDE7007) Create transfer order for Sales B/P SP-Venda order type VT.
2. Enter Purchasing B/P RS-Venda
3. System creates the corresponding Purchase Order type HT which number is populated in the header of the form
4. Complete the information and exit saving the order.

Results:

5. Inquire on SO (VT) SO Brazilian Information Detail and observe that the PUC equals RES. Or databrowse F76422 SO detail tag file-Brazil to confirm it as well. This PUC matches correctly from P76412B.
6. Inquire on the generated PO (HT) PO Brazilian Information Detail and observe that the PUC equals DBG instead of the expected PUC is RAW. Or databrowse F76423 PO detail tag file-Brazil to confirm that PUC is not correct nor is being retrieved from
P76412B. (Further verification confirms that the erroneous DBG for PUC is stored in the Item Branch Regional Location Info P76412B).

 

Note: 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 P4310BR Default/processing option  was added so when PUC processing option is set to 1, system will fetch the corresponding values from table F76B4321 and populate the detail line PUC column (F76423). Review KM Document E1: 76B: Populate Purchase Use Codes Automatically in P4310BR and P4210BR According to the Transaction (Doc ID 2224342.1).

 

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!


In this Document
Symptoms
Cause
Solution
References


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