Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News, Crossroads Connection

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error.

It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Still have GRINYA questions you need answered?
Contact us. We’d be happy to help.

Job costing based on standards is great, but what if reality doesn’t match up to that?

What if jobs are really taking twice as long, and you don’t know that? What if jobs are taking ½ as long as you think, but you’re scheduling based on how much time they “should” take? Either way, you’re losing money and productivity. Getting a handle on start/stop times for jobs, and therefore the total amount of time actually spent allows you to take proper action and be more productive.

In Baan IV/V, project templates do not exist, but you can set up a project template by creating a regular project, and setting the status to simulated or free. This is done so that the project does not create plans. Under this scenario, you can easily copy one project to another.

In LN, when you create a new project, a template can be used as the starting point. This is similar to copying a normal project, but unlike normal projects, no costs or revenues can be posted on a template.