Please Wait a Moment
X

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

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: What Could go Wrong With GRINYA?

One common GRINYA issue would be incorrectly entered Integration Setups.

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.

Optimize Your Manufacturing Today!
 
Previous Article BPCS/LX Tip of the Week: Efficiency– The What & How
Next Article Crossroads RMC Moves Arrowhead from 4.0.05CD to Infor LX
Print
219007 Rate this article:
No rating

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

You use LN audit features to fully or partially log changes that users make to the LN database tables when they use LN sessions.

The audit functionality is based on the concept of audit profiles. In an audit profile, you define which tables and fields are audited and when, in the context of an audit profile. To bundle profiles in the same functional area, you can relate the profiles to audit categories. You can export and import audit profiles with various options to enable a quick configuration. The audit trail is stored in sequence files, which are generated for each combination of company and table.

Note: For some important parameter tables it is required that auditing is enabled.

You can view or print the history of modifications.

Categories