Fragmented problem record-continuous update ...

1.Transaction Historical Summary

On the date 31-dec-2008, quantity was 0.00341. Since the showing upto 2 digits after the decimal, it is showing as 0.00

If the customer want to show till 5 digits after decimal, they have to change the
Profile ' inv:dynamic Precision Option for Quantity on Reports '. Set the
Profile value to ' -99,990.00000 '.

For more information, run the following query

Select meaning "Profile Format", Lookup_code "Precision"
From Mfg_lookups
WHERE lookup_type = ' inv_srs_precision '
and Enabled_flag = ' Y '
Order BY Lookup_code;

2.form Development Preparation ...

Put the TEMPLATE.FMB,APPSTAND.FMB, folder resource under the Unified folder, such as under C:/ORACLE1/ORA90/FORMS60, and then enter the registry, modify the Forms60_path value of c:/ ORACLE1/ORA90/FORMS60; C:/oracle1/ora90/forms60/resource; C:/oracle1/ora90/tools/open60/plsqllib

The form builder can be used smoothly at this time

3.Transaction Historical Summary

--from Oracle

The development updated with the following:

We have analyzed the data provided for the item ' Poatsfbr-775bhcz '. Basically this issue is because of backdated
Transactions.

Backdated transactions[created for April period (transaction_date) in May (Creation_date)] 47121626, 47132585, 47132558,
47132541, 47139981, 47147475 were costed after the standard cost update
Transaction 47125140 (May Period) is costed.

Standard cost update increased the inventory valuation. Since the backdated transactions costed after this
Transaction they hit the inventory valuation with a new cost. Since Customer is
Running till 30th April, this standard the cost update transaction (transaction_date
In May) "value is not" coming in the "the" showing value in negative.

Clearly this isn't a bug. Customer can run the "on" 6th May, 2009 to check
Quantity and value matching.

We suggest the customer to explore cost cut of date feature and not to create backdated transactions into the future to Avoi D
These type of problems.

--from Me

This is a good news. I run the "on" the "6th May", 2009 for the item ' Poatsfbr-775bhcz ', and get the result
This is normal. Please refer to Attachment "Transaction historical
Summary_280809.txt ".

For this issue, I have some questions as follows:
1.When I Run the "the" on 30th Apr 2009,the the "the" the "unit" cost on 30th Apr 2009,right.
2.After Standard Cost Update, if I create transaction currently, it's normal. If Creating transaction date before Standard Cost update date, we'll get variance when we run the [Rollback date B Efore Standard Cost update date).
Is my understanding correct?

--from Oracle

Customers understanding is correct. Please insist the customer does not have backdated transactions in the future.
Also suggest the customer to explore cost cut of date feature.