0012463: Issue 4370: Valued Stock Report doesn't include changes made on the selected date

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0012463

Openbravo ERP

04. Warehouse management

public

2010-02-24 20:21

2010-05-18 12:12

Reporter

RenateNieuwkoop

Assigned To

adrianromero

Priority

urgent

Severity

minor

Reproducibility

always

Status

closed

Resolution

duplicate

Platform

OS Version

Product Version

2.50MP11

Target Version

2.50MP17

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0012463: Issue 4370: Valued Stock Report doesn't include changes made on the selected date

Description

Warehouse Management || Analysis Tools || Valued Stock Report || Valued Stock Report

The report looks at changes made previous to the date you select, rather than to include the changes from that day.

So if you changed a price on a product on a Purchase Order, performed a goods receipt for that product on 10-7-2008, you then run 'Generate Average Costs' and
go to the valued Stock report and select 10-7-2008 as the date and run the report,
the new Average Cost is not reflected on the output.
However, when you click on the Product, to take you to the Costing of the product setup, you do see the changed average cost reflected there.
So you need to run the report for 11-7-2008 to see the changes made on 10-7-2008.

Steps To Reproduce

Enter PO for Product with large quantity and a different price than the default.
Do Goods Receipt for the PO. Run Generate Average Costs. Go to Valued Stock Report and query that product.

Proposed Solution

This is a regression. It needs to be fixed for 250M14.

The solution must be:

In the stored procedure (M_GET_PRODUCT_COST) when comparing the dateto entered the value has to be compared as:

v_dateto+1>DATETO instead of v_dateto>=DATETO. This is the way it's done in the whole application and doing this you get the whole day of the v_dateto. For example if DATETO is "25/02/2010 15:34:15" and you compare with the date entered in the report, for example "25/02/2010" then actually how it's done:

"25/02/2010" >= "25/02/2010 15:34:15" and as you can see it doesn't fit so that's the bug

But if you my approach:

""25/02/2010" +1 = "26/02/2010" > "25/02/2010 15:34:15" and this fits it

Additional Information