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 LN & Baan Tips & Tricks for TECHNOLOGY: Audit Fields by Table (ttaud3125m000)

Kathy Barthelt 0 1 Article rating: 5.0

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.

Infor LN & Baan Tips & Tricks for OPERATIONS: Sales Contract Linked Documents (tdsls3506m000)

Kathy Barthelt 0 1 Article rating: 5.0

Use this session to view the documents linked to a sales contract. You can view these documents only when a sales order line or a sales schedule line is linked to a sales contract line.

Note: 

  • You can view this session only if the Contracts check box is selected in the Sales Parameters (tdsls0100s000) session.
  • You can use the Linked Document option from the References menu to view the details of a specific linked document.


Field Information

Contract: The code of the sales contract.

Description

Line: The sequence number of the sales contract line.

Sales Office: The code of the sales office.

Description

Linked Document: The document type that is linked to the sales contract line.

Note: This field can be set to Sales Order Line or Sales Schedule Line only.

Allowed values

Linked Document Company: The company in which the document is linked to the sales contract line.

Linked Document: The code of the document that is linked to the sales contract line.

Note: 

  • The code of the sales order is defaulted from the Order Line field in Sales Order Lines (tdsls4101m000) session.
  • The code of the sales schedule is defaulted from the Schedule field in the Sales Schedule Lines (tdsls3107m000) session.

Linked Document Reference: The reference number of the linked document.

Note: 

  • The line number of the sales order line is defaulted from the Line field in the Sales Order Lines (tdsls4101m000) session.
  • The line number of the sales schedule line is defaulted from the Line field in the Sales Schedule Lines (tdsls3107m000) session.

Link Sequence: The sequence number of the linked document.

Infor LN & Baan Tips & Tricks for FINANCE: Clear Rounding Differences for Documents with Period Change (tccri7214m000)

Kathy Barthelt 0 2 Article rating: 5.0

Use this session to adjust the rounding difference transactions, calculated during the internal conversion, for inter-period postings.

Inter-period postings are the postings made to the ledger accounts defined in the Finance Company Parameters (tfgld0503m000) session for fiscal and reporting period changes.

If inter-period postings exist, very big rounding differences are calculated . If you run this session, those rounding differences are replaced with values that properly deal with an observed period change.

If inter-period postings exist, during the internal conversion rounding differences can be calculated for the wrong period. If you run this session, those rounding differences are deleted and the rounding differences are created for the correct period.

JOIN WEBINAR: Chat With Your IBM i Data

Thursday, October 16 2025 --- 1:00-2:00pm US/Eastern

Nick Olson 0 91 Article rating: 5.0

Imagine being able to ask questions directly to your IBM i data and get answers in real time. In this session, we’ll demonstrate how AI-driven tools can connect with your IBM i, making data analysis faster, more intuitive, and more accessible than ever before.

  • Thursday, October 16, 2025

  • 1:00-2:00PM US/Eastern

  • Presenter: Nick Olson, Crossroads RMC


Register Today: https://ibmi.workoutloud.com/Event/ai-in-manufacturing/Register

Crossroads RMC Shows Off New AI Dashboard at inPOWER 2025

📰 Read the full story on IT Jungle

Nick Olson 0 73 Article rating: 5.0

Crossroads RMC debuted its new AI-powered NextTrack Insights Analytics Dashboard at Infor’s inPOWER 2025 event in Wisconsin. The latest version lets users chat with their ERP data in plain English—no code, no custom reports, just instant answers.

Built on .NET Core with advanced AI and API integration, the dashboard connects directly to Infor ERP LX, XA, and Db2 for i, delivering real-time KPIs like cycle times, downtime, and equipment effectiveness.

📰 Read the full story on IT Jungle:
Crossroads RMC Shows Off New AI Dashboard at inPOWER 2025 ›

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

George Moroses 0 113 Article rating: 5.0

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

123457910Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Data Sizing Moving to LN

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.

Previous Article Baan/LN Tip of the Week: SIC Planning for MRP/MPS Planned Items
Next Article Baan/LN Tip of the Week: Plan Codes
Print
58129 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories