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
28626 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

The Cycle Counting Sub-System Within Inventory Management

The system uses the following information as the basis for cycle counting selection:

  • Cycle Counts/Year: The system calculates the time between cycle counts based on your entry in this Item Master file field for each item (optional).
  • Last Cycle Count Date: This date is in the Location Inventory file, ILI, if you use locations, or in the Warehouse Inventory file, IWI, if you don't.

The system adds the time between cycle counts (calculated as described above) to this date. If the result is less than or equal to today's date, the item is selected for cycle counting. If it is greater than today's date, the item is not selected, it is not due yet for cycle counting.

There is another special condition that causes an item to be selected for cycle counting. If the ILI/IWI record of the item has a Y in the Cycle Flag field, the item is selected automatically. This flag indicates that the item's on-hand balance has gone to a negative value sometime since the last cycle count. That applies even if the value is not negative at selection time. The programs that can set this field are INV500D, INV510, and BIL540.

You can also limit the items selected for counting by specifying limits of the item numbers or warehouses to be searched.

FirstLast

Tips: LN | Baan

Categories