Costing Issue in Adjust Cost - Item Entry

fjgilliefjgillie Member Posts: 17
Background:
We ran NAV 4.0 SP 1 for a trading company. There is no manufacturing, just purchase inbound and sales outbound, and some internal transfer order. The costing method is Average Costing. Normally we leave the initial unit cost equal to zero or 0.01 when the end user create new item card.
Inventory Setup
Automatic Cost Posting = YES, Expected Cost Posting to G/L = YES

Now I have an issue as following:
After running ACIE batch job, some acutal cost didn't show up in the field Cost Amount(Actual) in Item Ledger Entry with Entry Type = Sales. Acutally for this item, its related sales and purchase invoice are all posted. So I think ACIE must generate the cost adjustment entry to show the COGS. But it did not as expected.

During the batch running, there is an exception, i.e. we got the error message that is "*** entry have existed in table 5804 Avg. Cost Adjmt. Entry Point". I forget that its exact description.... I delete all the records in table 5804. I am not sure if there is any impact of the action. If any, how can I recover it?

As I know there are some tables and field related to ACIE batch job, but not quite sure of their relation and trigger point.

table 5804 Avg. Cost Adjmt. Entry Point
Item Application Entry
Item. "Cost is Adjusted" Item."Allow Online Adjustment"
"Item Ledger Entry"."Applied Entry to Adjust"
"Value Entry"."Valued By Average Cost"
"Value Entry".Adjustment

My question is:
If now I make sure of all sales/purchase invocie are posted and the ACIE didn't generate the adjustment entry. How can I judge when the adjustment entry will be trigger, or can I modify some specific above fields or insert/modify the above releated table to let ACIE re-running to generate the expected adjustment entries.


Thanks very much in advance.

Comments

  • kinekine Member Posts: 12,562
    1) 5804 Avg. Cost Adjmt. Entry Point table keep records for oldest date from which must be the average cost recalculated for specific item/location/variant (it means that it is oldest date with which something was posted for the item/location/variant from latest Adj. job) - but take this info as only 75% certainty, because it is some time I worked with average cost...

    2) Look for possible bugs resolved in SP2 and SP3. SP1 as any other version has some problems...

    3) Are you working on MS SQL or Native DB?
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • fjgilliefjgillie Member Posts: 17
    Thanks, kine.
    1) still not quite of the use of table 5804. I have deleted all record in table 5804. Do you mean it is no impact. The system will generate the temporary records for this table.

    2) where can I download SP2/SP3 document to review the fixed bugs?
    3) MS SQL
    kine wrote:
    1) 5804 Avg. Cost Adjmt. Entry Point table keep records for oldest date from which must be the average cost recalculated for specific item/location/variant (it means that it is oldest date with which something was posted for the item/location/variant from latest Adj. job) - but take this info as only 75% certainty, because it is some time I worked with average cost...

    2) Look for possible bugs resolved in SP2 and SP3. SP1 as any other version has some problems...

    3) Are you working on MS SQL or Native DB?
  • kinekine Member Posts: 12,562
    1) on MS SQL there were some situations in which NAV client didn't see some records in the table. Solution was to set special attribute in db_property table of the db.

    2) Documents about changes are on the install CD of the new version in root directory
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • ctnoble58ctnoble58 Member Posts: 3
    We ran on V3.7 until February 2007 and had serious problems with average costing. We then tested V4 SP1 and still found issues. We upgraded to V4 SP3 in February 2007 and this has fixed all our average cost issues. We are running on the native Navision database so I can't confirm that the problems are fixed in SQL.
Sign In or Register to comment.