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

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Impact of Configuration Changes on Audit Trails

Impact of Configuration Changes on Audit Trails

The impact of changes in the audit settings varies depending on the specific circumstances. The issues typically arise when changes made to audit settings are implemented at runtime without requiring all users to exit the system (LN). As a result, some users may continue to generate audit trails using the old configuration, while those who log in after the changes take effect will create audit trails based on the new configuration.

Changes in User Profiles

Below is a summary table that illustrates the effects of these changes for a specific table within a company:

Change Description Impact
Add a table Users that still use the old settings do not audit some transactions.
Remove a table Some transactions that must not be audited with the new settings are still audited by users that use the old settings.
Change the audit type for a table or field Some transactions are audited according to the old settings, and other transactions are audited according to the new settings.
Add or remove a field After you audit transactions in the table with the new settings, users that use the old settings can no longer perform transactions on this table. Therefore, users with the old settings can be forced to restart LN.

Note on Changes in Field-Specific Auditing:
When you toggle field-specific auditing on or off for a table, which alters the number of fields being audited, the effect is analogous to adding or removing a field. However, not every modification to the audit settings impacts the runtime settings. Converting the new settings to runtime might result in no net change for the entire configuration if the overall effect of the adjustments neutralizes each other.

Previous Article Infor LN & Baan Tips & Tricks for OPERATIONS: Using Country of Origin for Purchase Orders
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Print
28592 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Spreadsheets are often the tool of choice for many organizations to store and arrange information for financial planning, analytics, compliance, and more. Ironically, for many business processes that involve managing data, it creates the exact opposite effect––silos of information and inefficiency. And because it stores organizational data in a readily sharable way, there is a high risk of exposing confidential information.

Read this Infor best practice guide to discover the top five business processes that a modern data and analytics architecture can automate and deliver far more value than spreadsheet-driven techniques.

Infor Best Practice Guide: 5 Ways Modern Analytics Reduces Spreadsheet Risk and Inefficiency

How do I know which orders are on hold? – Pick Release / Pick Confirm

Orders that are on credit hold, customer hold, user hold, margin hold, credit card hold, or pricing hold cannot be selected for Pick Release or Pick Confirm. The ORD952B, Orders Not Selected Report, can be requested at Pick Release or Pick Confirm to list any order that would normally qualify for selection, but has been excluded for other reasons, and to print that reason. ORD952B has been modified to validate the hold status of the original customer order, instead of the intercompany automation warehouse order that is being processed, and to print a reference to the original customer order along with the reason.

FirstLast

Tips: LN | Baan

Categories