Hi there,
 
Thanks. Well, actually we cannot run a Recalc, since the value is too high
for the DB to swallow.
 
So currently I think that I will "just" clear the value in InventTrans and
InventSum. However, as a result of failed Recalc's we also have transactions
in the table InventSettlement, which our Oracle DB does not like either.
 
It seems that Ax is really trying to fix things during Recalc, but the
values are just too high to handle.
 
We have only 8-9 transactions for that item number, so it is rather easy to
overview.
 
Any pointers as to clearing the large values in InventSettlement as well -
since they sum up a fine 0 anyways ... ? 
 
/Jens

  _____  

From: Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Allen Joseph
Sent: Friday, March 09, 2007 1:09 PM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: Re: [Axapta-Knowledge-Village] Huge CostAmountValue...



Hi Jens,

In addition to Lukas's suggestion, It would be good to run an Inventory
'Recalculation' for the Item in question.

Also make sure that you cancel/close all the
sales/purchase/production/transfer orders involving the items in question.

Hope this helps too!! :)

PS: I was introduced to this issue while supporting a client using AX3 SP3.
There were 2 hotfixes on Inventory closing / costing for SP3. You might want
to go through the explanation document for these hotfixes too!!

Allen.J

Lukas Nugroho Putro <sancta_mariae@ <mailto:sancta_mariae%40yahoo.com>
yahoo.com> wrote:
hi jens,

I have this experience once. I assume that the you allow Negative Physical
Inventory on your Inventory Model Group and check field include physical
value and you do inventory closing. Before you do inventory closing : 
1. you should close any production transaction. 
2. Do not allow negative physical inventory
3. Invoicing Purchase and Sales Order that have status Received and
Delivered
4. Do not check include physical value

hope it helps 

lukas nugroho putro

Jens Strandberg <[EMAIL PROTECTED] <mailto:jens%40strandbergs.dk> dk> wrote:
Hello there,

Running Ax3SP4. I am experiencing a very strange problem here.

I have a record in InventTrans, where the CostAmountPhysical is - and I am
not kidding - -2903766228490648.00 ...

The quantity is -1, i.e. StatusIssue is "Deducted" and is with reference to
a production line. Now, needless to say this value cannot be processed by
our Oracle DB, and therefore I need to get rid of it somehow.

But, am I correct in thinking that I cannot make a transaction adjustment
with the tools available, since this is an issue, not a receipt ?

I see the same value in the corresponding records in the tables InventSum
and InventSum*TTS, and I suspect that I need to clear these values also. Any
hints - as I expect to have to fix this by code ... ?

Thanks in advance ...

Best regards,
Jens

[Non-text portions of this message have been removed]

---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.

[Non-text portions of this message have been removed]


---------------------------------
Here's a new way to find what you're looking for - Yahoo! Answers 

[Non-text portions of this message have been removed]



 


[Non-text portions of this message have been removed]

Reply via email to