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

Infor LX & BPCS Tips & Tricks for OPERATIONS: WebTop Grid Support Enhancement for MRP320D

George Moroses 0 1042 Article rating: 5.0

This enhancement improved the subfile utilized in MRP320D Master Schedule Detail Inquiry -SCR001 by expanding the subfile with data rather than clearing the subfile as user pages. This change provides full support for the WebTop 4.8 Grid decorator.  To implement this enhancement, request and apply MR 81428

This enhancement updated the approach used to populate the subfile to allow a deployed Webtop Grid to function correctly. There is no visible or user-impacted change to the way the program functions.

This enhancement provides improved functionality and full support of a Webtop grid applied to the subfile.

Infor LX/BPCS Tips & Tricks for FINANCE & TECHNOLOGY: Add Number of Assigned Users to SYS600

George Moroses 0 1001 Article rating: 5.0

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.

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Synchronize users from LX to SiM in batch

George Moroses 0 1975 Article rating: 5.0

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.

Infor LX/BPCS Tips & Tricks for FINANCE: Inventory Transaction History to Ledger Book Journal Line Relationship

George Moroses 0 406 Article rating: 5.0

This enhancement provides IDF relationships from Inventory Transaction History (ITH) to Ledger Book Subsystem Transaction (GXR) and from Ledger Book Subsystem Transaction (GXR) to Ledger Book Journal Line. To implement this enhancement, request and apply MR 81558.

This enhancement provided the following relationships:

  • Inventory Transaction History
  • Relationship to Ledger Book Subsystem Transaction (1 to Many) Default view ‘General’
  • Ledger Book Subsystem card Default view ‘Inventory Processing’
  • Default subset ‘Inventory Processing’

This enhancement provides users with complete traceability from inventory transactions (ITH) to ledger book journal lines (GLH), regardless of how many ledgers are used and journals created. Due to the bi-directional relationship, users can see the source ITH detail from the journal lines.

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Add Last Maintained Audit Fields to SYS600

George Moroses 0 6314 Article rating: 5.0

LX has enhanced the SYS600 User Security Maintenance application by adding the ZXUP audit fields:

  • Last Maintained Date

  • Last Maintained Time

  • Last Maintained User

These fields are updated whenever a user or role is revised, deleted, or reactivated.

This enhancement provides standard audit tracking to identify who modified a User Security record and when. The audit fields can be used for ad hoc tracking, reporting, and analysis.

1345678910Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

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.

Categories