Reversal of Adjust Item Entries (& value ledger entries)

Need some feedback on this error faced.

Is is possible to to reverse out adjust item entries made via the Adjust Batch job? This may affect the value ledger entries which also may need to be reversed out as well.

Anybody tried this before?

Another point, after a revaluation of item is made, and subsequent item application (via sales and consumption), have anybody tried reversing the revaluation item at base 0, ie before the item application entries are made.

Thanks

Adjust Batch Job. Do you mean “Adjust Item Costs/Prices” ? This report only adjust costs in item card. To affect value entries you must use a revaluation journal.

Yup, I mean Adjust Item entries.

Anyway to create a function technically to reverse out the previous Adjust Item cost entries?

The only way it’s to use revaluation journal with previous cost.

Is there a reason you need to reverse it? Even if you reverse it now, you’re going to run the process someday, and when you run it, all the entries you reversed will come back.

The issue is that Adjust Cost Item entries does not allow you to specify the period to run this job. I guess if the user forgets to run this function over a period of time, the entire adjustment entries will be posted to the particular date specified. It will be good if we can determine the date period for the entries to be adjusted on a selective period basis.

The ability to reverse would then allow us to reconsider again the impact and the quantum affected. At present we are unable to quantify it.

The source of the issue is due to the nature of the Adjust Costs Items entries covering all the entries irrespective of the date period. If the user forgets to run this on a monthly basis, all the entries will be posted to 1 specific posting date on the next run date; it may be a big amount.

The ability to reverse would then allow us to reconsider again the impact and the quantum affected. At present we are unable to quantify it.

This problem has been addressed since 3.7b. You will only get this problem if you’re running versions between 3.00 to 3.7a.