Youp2001
23rd January 2003, 09:02
Hi,
I'm trying to create an interface and I do not want to change the standard Baan sessions. In the interface I have to create a file with all released production orders. These orders are needed by the other system.
For new and changed orders everything works ok, but how can I trap deleted orders?? They are not in the system anymore, do has anybody an idea for how I can trap deleted orders so I can notify the other system that an order has been deleted.
Hope to hear from you,
Youp
Leenaa
23rd January 2003, 11:45
From History Table
hi
U can easliy get this by history table.
morpheus
23rd January 2003, 12:01
Leena,
I don't think there is any history table in SFC module. Correct me if I am wrong!!
Leenaa
23rd January 2003, 12:23
table ticst021
morpheus
23rd January 2003, 12:55
Thanks Leena, for the info.
But, two more doubts I have -
This table gets updated only after backflushing/release outbound data, step is done!!? Right...
And is it possible to delete the production order if the status has been changed to "Released" or anything after "Released"!!?
Paul P
24th January 2003, 03:25
Dear all,
Deleted orders don't appear in the production order history. Production order history only contain production orders that went or are going through production operations. Youp, you might wanna try turning on audit trail on the production order table if it's important for you to see which orders were deleted (with this, you even get info on who did it, at what time, etc.) :)
Rgds,
Paul
morpheus
24th January 2003, 08:05
Yes, Paul is right. Deleted Production Orders do not appear in the Production Order history.
Also, Youp, putting audit on, on the "tisfc001" table, will effect the performance of the system to some extent. So, think before you put it on.
Good luck!!
lbencic
24th January 2003, 16:58
You can put a wrapper style program around the sessions that delete the records (QKEY, RMCgen, freeware version 'rush' on these boards). You can write to your file everytime the records are deleted, and it does not require or modify the source code. This would trap user deleted records. You may have less luck for deletions done by mass processes...