Please Wait a Moment
X

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

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

George Moroses
/ Categories: Infor LX & BPCS Tips, Operations

Infor LN & Baan Tips & Tricks for OPERATIONS: WebTop Grid Support Enhancement for MRP320D

This enhancement modifies the subfile used in MRP320D Master Schedule Detail Inquiry (SCR001) to expand the subfile with data instead of clearing it as the user pages. This update enables full compatibility with the WebTop 4.8 Grid decorator.

To implement this enhancement, request and apply MR 81428.

Functionally, this change only affects how the subfile is populated to support a deployed WebTop Grid. There is no visible change or user impact in how the program operates.

In summary, the enhancement improves functionality and ensures full WebTop Grid support for the

Previous Article Infor LX/BPCS Tips & Tricks for FINANCE & TECHNOLOGY: Add Number of Assigned Users to SYS600
Next Article Crossroads RMC Shows Off New AI Dashboard at inPOWER 2025
Print
112 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses
Contact author

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.

Read more

Categories