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

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

• It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

• For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

• The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

LX has added the number of users assigned to a Role or Unit to the first screen of SYS600. When displaying the list of profiles on the first screen of SYS600, the list previously included the counts per profile of assigned Roles and Units when the profile was a user. A new column called Users have been added to show the number of assigned users for Roles or Units.

This enhancement provides a quick way to see the number of users assigned to a Role or Unit.

Use this session to load tables for an audit profile.

Usually, this session is run from the Specific menu of the Audit Tables by Profile (ttaud3120m000) session. The selected profile in that session is displayed in the first line of the current session.

The result of loading the tables depends on...

This enhancement improves performance by submitting to batch the automatic synchronization of changes from LX user maintenance (SYS600) to System i Manager (SiM). During LX user maintenance, there are now three possible approaches to synchronizing the LX user changes to SiM, controlled by system parameters. Synchronizing LX user changes to SiM in batch allows the person executing SYS600 to continue with additional maintenance or other transactions without waiting for the synchronization to finish.

During an Exchange import, you can use all the functionality programmed into the Data Access Layer (DAL). If you use the DAL, Exchange carries out all the constraint checks, integrity checks, and side effects, for example, updates on other tables, that are programmed into the DAL. Database integrity is guaranteed automatically.

Using the DAL reduces the costs of interface development. You can use the DAL to import standard interfaces developed by Infor for partner products, as well as for specific interfaces built by customers, for example, to integrate LN with legacy systems. You can use the DAL in both single site and multisite environments.

The checks or additional actions specified in the DAL are carried out for each row that is imported. Database errors are logged in the same way for DAL and non-DAL import. DAL hook errors are also logged. You can specify whether the DAL property checks are or are not carried out.

If you specify the use of the DAL for a table relation for an import, the dal.new, dal.update, and dal.destroy functions are used instead of db.insert, db.update, and db.delete. You can choose to use DAL for particular tables and not for other tables, therefore, an import batch can contain both types of table relations simultaneously. The import through DAL works for both the import based on audit or indicators (inserts, updates, deletes), and the full import (inserts only).

DAL settings are run time aspects, which means you can change these aspects without having to regenerate the import program. DAL settings are also logged in the log table at batch line level, to enable you to find out what the DAL settings were when the import was run.

Important to realize is that an update through the DAL can result in a number of side effects. Actions performed by the DAL must not be carried out twice. For example, if the DAL updates the available to promise (ATP) quantity for an item when importing order data, the ATP quantity must not be updated in a condition script as well.

For this reason, you must not add any actions in condition scripts, or import additional data, that are already handled in the DAL.