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 TECHNOLOGY: User Provisioning

George Moroses 0 3819 Article rating: 5.0

Enables integration between LX and Infor OS Federation Services (IFS) to automate user provisioning.

  • Bi-directional user synchronization between Infor OS and LX:

    • Infor OS user creation or changes automatically create or update users in LX.

    • IBM i user profiles can be created if needed.

    • Updates to SYS600 user data are reflected in Infor OS.

  • Security Role Integration:

    • LX Security Roles and Units are published as IFS Security Roles via SyncSecurityRoleMaster BODs.

    • LX receives inbound SyncSecurityUserMaster BODs from IFS to create or update user records in SYS600.

    • SYS600 Exit Points trigger ProcessSecurityUserMaster BODs to request user creation or updates in IFS on behalf of LX.

Available Versions: 8.3.5, 8.4.1, 8.4.2

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Application Personalization

Kathy Barthelt 0 39776 Article rating: 5.0

Users can personalize sessions and apply special formatting to the data displayed in sessions. The personalizations and formatting settings that are specified by the users are stored on the LN server. Administrators can maintain these settings.

  • Session personalizations

    Users can personalize sessions in various ways. users can, for example, hide fields, change labels, customize the toolbar, and move fields to another tab. Administrators can maintain the personalizations defined by the users. For example, an administrator can export personalizations to an XML file, import personalizations from an XML file, and copy personalizations to another user, to a DEM role, or to a company number.

  • Report personalizations

    You can use the Report Designer (ttstppersrep) to personalize the layouts and style of reports, without modifying the standard reports or using an external reporting solution. The changes are stored as personalizations.

    You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer (ttstppersrep), or modify them in Infor LN Studio.

    For details, see the Infor LN Report Designer Development Guide
     
  • Conditional formatting

    users can define conditions to apply special formatting to the data displayed in LN sessions. The users can define multiple conditions per session and different types of formatting, such as a specific color for particular fields or rows, and a warning symbol for particular rows. Administrators can maintain the formatting settings specified by the users and can define system-wide formatting settings.

Infor LN & Baan Tips & Tricks for OPERATIONS: Deleting Purchase Orders

Kathy Barthelt 0 38424 Article rating: 5.0
  • If Finances is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.

You cannot delete a purchase order (line) if:

  • The linked warehouse order is closed but cannot be removed.
  • The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
  • A consignment replenishment order is not yet consumed completely.
  • The invoice is yet to be completely matched and approved.
  • The invoice amount is not yet inserted as turnover history.
  • The sales order or service order that is linked to the purchase order line, and for which an internal invoice must be sent from the purchase office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.

Infor LN & Baan Tips & Tricks for FINANCE: Cash Forecast Reports and Inquiries

Kathy Barthelt 0 29407 Article rating: 5.0

To produce the cash flow forecast, the combined information from the following is used:

  • Customer and supplier accounts
  • Open sales and purchase orders
  • Purchase quotations
  • Purchase requisitions
  • Standing orders
  • Projects
  • Financial budgets

You can use the bank balances of the bank relations that are maintained in the Bank Relations (tfcmg0510m000) session, to generate the reports with details of cash inflows and outflows of the company for a specified period of time.

You can also manually specify the Opening Balance for the cash forecast. Use the sessions below to print and generate the reports:

  • Cash Forecast Summary by Date Range/Currency (tfcmg3518s000)
  • Print Cash Forecast Details by Date Range/Currency (tfcmg3412m000)
  • Print Cash Forecast Summary by Period/Currency (tfcmg3410m000)
  • Cash Forecast Summary by Date/Currency (tfcmg3519s000)
  • Print Detailed Cash Forecast in Cash Forecast Currency (tfcmg3413m000)
  • Cash Forecast Components by Date/Currency (tfcmg3520m000)
  • Print Forecast Components by Date/Currency (tfcmg3420m000)

Infor LX/BPCS Tips & Tricks for OPERATIONS: Override inspection days lead time at item-facility

George Moroses 0 20327 Article rating: 5.0

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

  • When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Improve WebTop Grid Support for MRP320D Master Schedule Detail Inquiry

George Moroses 0 20766 Article rating: No rating

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.

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: IDF Ledger Book Journal Line Analysis

George Moroses 0 14477 Article rating: 5.0
  1. This enhancement added the IDF Ledger Book Journal Line Analysis business object for displaying reference information on summarized journal lines. This enhancement provided Ledger Book Journal Line Analysis business object and a bi-directional relationship to Ledger Book Journal Line Source.
  2. This enhancement provides the user with detailed reference information on summarized journal lines for analysis purposes.

✨ You're Invited: LN NAUG Face-to-Face Annual Meeting 2025

May 13–15, 2025 | Naperville, IL

Kathy Barthelt 0 4531 Article rating: No rating

Why You Should Attend

LN NAUG Face-to-Face is the must-attend gathering for Infor LN and Baan ERP users across North America. Join fellow ERP professionals, decision-makers, and industry experts for three days of knowledge-sharing, innovation, and networking you won't find anywhere else.

💡 Get Inspired by real-world success stories from LN users

🤝 Connect with peers and solution providers shaping the future of Infor LN

📈 Level Up your ERP strategy with sessions on automation, analytics, integration, and more


Visit Crossroads RMC's Booth

Explore what’s new and what’s next with Crossroads RMC:

🔹 AI Consulting – Unlock insights and transform your ERP processes
🔹 Visual Job Execution Software (VJES) – Train new employees faster, work smarter
🔹 LN Integration Services – Seamlessly connect systems for maximum efficiency
🔹 Help Desk Services for Infor LN – Support that understands your business
🔹 …and more!


🎟️  Don’t miss out — register now and reserve your spot at LN NAUG 2025!

First7891012141516Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for TECHNOLOGY & FINANCE: Archiving Finalized Transactions

TECHNOLOGY & FINANCE: Archiving Finalized Transactions

To support correct archiving in a multicompany structure, the following rules apply:

  • Each company must have its own archive company. Companies cannot share an archive company.
  • The structure of archive companies must be an exact copy of the live environment.
  • A company must keep the same archive company until the end of its lifetime. Once data has been archived, you cannot change the archive company.

If extra archiving capacity is required, it is recommended that you set up a second archiving environment, which must also be an exact copy of the live environment. Define the companies of the second archive environment as the archive companies of the companies of the first archive environment. If necessary, a third and more archiving environments can be set up. You must then archive the data from each archive company to its archive company in the second archiving environment, and so on.

When you archive the data, LN builds an array with all the companies of the group and the archive company linked to each company. If any of the companies in the group does not have an archive company, LN reports an error and aborts the archiving process.

Batches and batch lines are only archived and/or deleted if you perform archiving and deletion in the company in which they exist. This is always the source company. Any intercompany documents and related finalized transactions that belong to the batch are not archived and/or deleted until the target company is archived.

If the batch has been deleted from the live environment, such intercompany documents and transactions will then temporarily exist without a batch in the live environment until the target company’s transactions are archived. Therefore, it is recommended to archive all the companies of a group within a short time.

Finalization runs are also archived. A finalization run can only be deleted from the live environment if all the attached batches have also been deleted.

Financial documents are archived and/or deleted if you perform archiving and deletion in the company in which they exist. For each document, LN searches whether a related intercompany document exists.

If the document’s transaction type indicates that the document numbering does not have to be in a fixed sequence, the document is not deleted from the live environment, to avoid duplicate document numbers.

A finalized transaction is not deleted from the live environment if the fiscal year of the transaction does not equal the fiscal year of the batch and the fiscal year of the transaction cannot yet be archived. If the Archive option is selected, the related batch, batch line, and document are copied to the archive company and retained in the live environment.

If a transaction is still referenced by open sales orders or purchase orders, it is marked as Deleted but not actually deleted. The related batch, batch line, and document are copied to the archive company and retained in the live environment. They are deleted when the referenced open transactions are closed and archived, for example, when you run the Archive/Delete Fully Paid Purchase Invoices (tfacp2250m000) session

If the transaction’s ledger account is a matchable account, any related matching data is also archived.

During the archiving process, the originating company of the finalized transaction is replaced with the originating company’s archive company. In this way, the archive environment will not contain references to the live environment.

During archiving, intercompany document relations are also copied to the archive environment. In the archive environment, these relations are updated in such a way, that each document in the relation refers to the environment in which the document actually exists. In the live environment, the document relation is retained until all related finalized transactions are deleted. For invoice-related transactions, this only occurs during the removal of fully-paid invoices. The document relation is also updated in the live environment, in order to refer to the archived document if all related finalized transactions have been removed from the live environment.

After the normal archiving process, an additional archiving step is performed in which all transactions and documents in the live company that arise from intercompany postings, are archived. During this step, intercompany relations are archived and/or deleted as described earlier.

Batches, batch lines, and documents that have the Deleted status are deleted from the live environment, unless the document’s transaction type indicates that the document numbering does not have to be in a fixed sequence. Such documents are not deleted from the live environment, to avoid duplicate document numbers.

Previous Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Next Article Infor LN & Baan Tips & Tricks for OPERATIONS: Simulated Purchase Prices (ticpr1170m000)
Print
494 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories