Hi,

In Baan Ivc4 there’s a few items that have a last inventory transaction date (tiitm001.ltdt) that lies in the future. This can’t be correct.

Four of these items have been received on the same date (on a purchase order). Other items on this purchase order that have been received at different dates don’t have a last inventory transaction date in the future so it seems it is related to the receipt.

Does this sound familiar to anybody? What could’ve caused this situation?

Thanks,

Frank

Hi Frank,

sounds very strange. I suppose you're talking about purchased items. Did you check the inventory transactions in the history table (tdinv750) for this items?

Martin

I suppose you mean tdinv700, Martin? Yep, I checked that one but the last transaction date in there is still a date in the past.

The last inventory date (in tdilc101) is in the past as well.

But indeed, it concerns purchased items. Lot controlled by lot, FIFO, anymous MRP.

Sorry, of course it's tdinv700.
I have to admit that we don't have ILC implemented in our system. So all my experience does not consider ILC issues.

I tired to reproduce a similar situation in our test system - without success. All dates in future were rejected by the system (date has to be equal or less then current date).

Regards,

Martin

For me, that clearly sounds like a bug. I would not waste too much time on it now, probably it's one of these one-time-and-never-again problems that sometimes happen with Baan. Correct the dates with ttaad4100, and write a short sql query that you can run once a week to check if that problem occurs again. Then, however, you should go into detail - I would go and have a look where that last inventory date gets filled from for lot controlled items.

Just a few thoughts...

Does your firm have users in multiple time zones? I sometimes see deliveries made "tomorrow" (because it is a NZ user shipping in his "today")

I seem to recall that inspection does some strange things and sets some transaction times to 23.59.59 - was this what you saw? or was it really days ahead?

Cheers.

We too have seen that the time shown on many transactions is 23:59:59.

Baan date stamps inbound with the original receipt date, regardless of when it's maintained. If you maintain inbound on the original receipt date, baan will time stamp with the correct system time. If you maintain inbound on any day proceeding the original receipt date, baan time stamps the transaction with 23:59:59.

Manish.

Thanks everybody for your input.

Manish is right with the 23:59-thing: that happens in inbound cases but also in some other situations where the transaction date is prior to the system date. This is programmed in the function tcmcs0016

In our case it's not a time-zone-issue, the last inventory date is something like two weeks into the future.

Most times the date gets filled in tcmcsdll0100 but this dll gets input from sessions like 'maintain receipts', 'maintain deliveries', 'release outbound data' etc. In these sessions it's not possible to enter transaction dates in the future.

Any other ideas?

Frank

I have seen 23:59 time stamp long time back in Baan where no ILC is implemented. Feedback from Baan was it was generated by Baan one of the correction program’s for correcting quantity changes in maintains receipts and was fixed by Baan.

Please Also check was system time changed by mistake? Any inventory transactions in history for those future days?

Thanks,

Abr

Hi -

We had situations in the past (with ILC turned on) where transactions were able to be posted in future periods, so long as the fiscal period in finance had a status of "Open".

Needless to say, we are very careful now to ensure that only the current fiscal period status is open, and all others are closed.

Regards,
Linda