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

George Moroses

Infor LX/BPCS Tips & Tricks for EXECUTIVES

TECHNICAL: Synchronize users from LX to SiM in batch

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.


FINANCE: Inventory Transaction History to Ledger Book Journal Line Relationship

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.

OPERATIONS: Infor Business Context (IBC) messages for INV500 

This enhancement adds publication of IBC messages to additional LX screens. While entering data on the primary screen for inventory transactions, IBC message are now published and available for use in Ming.le contextual applications.

Previous Article The Far-Reaching Impact of Disconnected Data
Next Article Improve Productivity & Agility with Modern ERP
Print
333 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

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