E1: G40: Reversal Spray Operation Does Not Create Journal Entries for Consumables in Grower Spray Operation (P31B68)
(Doc ID 2764694.1)
Last updated on JUNE 14, 2021
Applies to:
JD Edwards EnterpriseOne Grower Management - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
The Spray Operation Reversal does not create Journal Entries for Consumables in spray operation.
If the Spray Operation uses a Spray Item that is a Non Stock Line Type, there are No J/E records written for the Reversal for the Consumable Item (Stock Line Type) on the operation.
When reversing a Grower Spray Operation (P31B68), the reversing entry is made in the Cardex (F4111) correctly with a Batch Number, but does not write/show a J/E Line No. 0. Which results in no J/E Posted the the Reversal Batch which produces incorrect inventory balances.
In reviewing the logs from the Reversal, you will see Unique Constraint Errors when trying to Insert into the F0911 table.
Results after applying bug 30729078:
Now when Reversing a Grower Operation via P31B68, the reversing entry made in the Cardex (F4111) the batch number is written (fixed by Bug 30729078) now. However the Reversal Journal entries are still not being created for a spray operation Consumable because of the Insert into F0911 Failures errors in the logs. You will also see the Item Ledger Details record shows J/E Line No. 0.
Logs:
OCI0000227 - Error - ORA-00001: unique constraint (PDCURY.F0911_PK) violated
OCI0000226 - Unable to execute - INSERT INTO PDCURY.F0911
STEPS
- Create a Spray Operation with a Consumable.
- Make sure that the Spray Operation uses a Non Stock Line Type Item.
- The Consumable Item is a standard Stock Item.
- Close the Operation (review the Cardex)- all is good.
- Now, Reverse the Operation.
- Review the Cardex Record to verify that the Reversal does have a batch number.
- Notice that the detail J/E Line No. is ".0".
- The Reversal did NOT write Journal Entry.
- Review the logs from the Reversal and you will see Unique Constraint Errors when trying to Insert into the F0911 table.
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 |