零碎的问题记录--持续更新中......_is my understanding correct?-优快云博客

本文档讨论了Oracle系统中交易历史汇总报告的显示精度调整方法及成本更新导致的数据偏差问题。通过调整配置文件“INV:DynamicPrecisionOptionforQuantityonReports”的值，可以改变报告中小数位数的显示精度。此外，还分析了回溯交易的成本计算问题，并提出了避免此类问题的方法。

1.Transaction historical summary

On the date 31-DEC-2008, quantity was 0.00341. Since the report is 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开发准备...

把TEMPLATE.fmb,APPSTAND.fmb,文件夹resource放在统一文件夹下,比如放在C:/Oracle1/ora90/FORMS60下,然后进入注册表,修改FORMS60_PATH的值为C:/Oracle1/ora90/FORMS60;C:/Oracle1/ora90/FORMS60/resource;C:/Oracle1/ora90/TOOLS/OPEN60/PLSQLLIB

此时就可以顺利使用form builder

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) was costed.

Standard cost update increased the inventory valuation. Since the backdated transactions costed after this
transaction they hit the inventory valuation with new cost. Since customer is
running till 30th April, this standard cost update transaction(transaction_date
in may) value is not coming in the report showing value in negative.

Clearly this is not a bug. Customer can run the report 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 in the future to avoid
these type of problems.

--from me

Here is a good news. I run the report on 6th May, 2009 for the item 'POATSFBR-775BHCZ',and get the result
that 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 report on 30th Apr 2009,the report will get 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 will get variance when we run the report(Rollback date before standard cost update date).
Is my understanding correct?

--from Oracle

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