sukesh75
2nd August 2010, 16:29
Hello,
Has anyone out here experienced a situation (in Baan4c4) where in all the estimated materials inside all Active Production Orders got issued in a mysterious manner? In a matter of 10 minutes, 6,900 lines of material issue took place that affected around 700 odd production orders. The possibility of this happening due to someone running the Issue Inventory (for all production orders) by mistake (or on purpose) is the first conclusion but our relevant setup prevents this from happening. The user whose name got recorded in the tdinv700 table against all these records of material issue is someone who left the company few months back and who doesn't have permission to run the session Issue Inventory {tisfc0207m000}. In fact none of the users who are responsible for material issues, have permission to this session and all they have is access to Issue Stock {tisfc0207s000} through which it is near to impossible to make a global issue. There is no indication on the Baan server event viewer that the user logged in at that particular time or day. Given all these, how could something like this happen? :confused:
regds
sk
Has anyone out here experienced a situation (in Baan4c4) where in all the estimated materials inside all Active Production Orders got issued in a mysterious manner? In a matter of 10 minutes, 6,900 lines of material issue took place that affected around 700 odd production orders. The possibility of this happening due to someone running the Issue Inventory (for all production orders) by mistake (or on purpose) is the first conclusion but our relevant setup prevents this from happening. The user whose name got recorded in the tdinv700 table against all these records of material issue is someone who left the company few months back and who doesn't have permission to run the session Issue Inventory {tisfc0207m000}. In fact none of the users who are responsible for material issues, have permission to this session and all they have is access to Issue Stock {tisfc0207s000} through which it is near to impossible to make a global issue. There is no indication on the Baan server event viewer that the user logged in at that particular time or day. Given all these, how could something like this happen? :confused:
regds
sk