This content has been marked as final. Show 4 replies
I am not sure that this is a good idea to start the encumbrance mid-stream.
The funds obligations are done during approval, which is already completed for the purchase order - so there
would be no reservation of funds, yet then you are receiving - post encumbrance - which is then creating journals
with the assumption that the PO at one time was reserved.
It seems this would be very hard to balance the ledgers.
Understand that it is not a good idea, but this is the condition that we're facing in our production instance.
Any idea how to fix this?
in bug 6792004, which was closed by development as not a bug.
Development said the following:
"Using" or "Not using" Encumbrance Accounting decision should be
taken once forever at the time of implementing the application. Customers are not supposed to
switch between these options.
If any Customer wants to enable this after using application for sometime, ideally they are
supposed to final close/cancel all the existing PO before doing so. In this case also ct is
supposed to cancel/close all the POs before disabling the encumbrance.
thanks for the reply. we've solved this issue several months ago