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: Action Required - Infor LN Cloud Edition - Fonts Update!

Kathy Barthelt 0 61556 Article rating: 5.0

In April 2025, Infor LN Cloud Edition release 2025.04 will introduce the deprecation of Windows® fonts in LN report design and output. This means that Windows fonts will need to be replaced by Google fonts.

Actions Required:

  • All LN Cloud Edition customers must identify all reports modified with the LN report designer and update them by replacing the Windows fonts with Google fonts.
  • Completed before the 2025.04 Maintenance Window.
  • Please see Knowledge Base (KB) article 3523663 for more information, details and FAQs.

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Archiving Data from tipcs300 and ticst300 Tables

Kathy Barthelt 0 59934 Article rating: 5.0

1. Archiving tipcs300

  • Using Session tipcs2260m000:
    • When archiving PCS projects, selecting the "Archive Financial data" option ensures that:
      • Records in tipcs300 are archived to the archiving company.
      • Records are deleted from the original company.
    • If records remain in tipcs300:
      • They may belong to projects that have not been archived.
      • The project may have been archived without selecting "Archive Financial data."
    • Verify there are no errors during the archiving process.
  • Using Session tipcs3500m001:
    • The session "Delete Financial Transactions by Project" can delete records from tipcs300.
    • Note: This session is not for archiving; it removes records without copying them to the archiving company.

2. Archiving ticst300

  • Using Session ticst0250m000:
    • The session "Archive Production Orders" allows:
      • Archiving and deleting records from the original company.
      • Only deleting records from the original company.
    • When executed:
      • Records in ticst300 associated with archived orders are removed.
      • Remaining records belong to unarchived orders.

Infor LN & Baan Tips & Tricks for OPERATIONS: What is Statistical Inventory Control (SIC) and How Does It Work?

Kathy Barthelt 0 53101 Article rating: 5.0

Statistical Inventory Control (SIC) is an inventory-controlled order system designed to maintain stock levels based on predefined thresholds, rather than being demand-driven like EP (Enterprise Planning). Since SIC relies on inventory levels, it may lead to higher stock levels. To minimize financial risks, SIC is best suited for:

  • Low-cost items.
  • Items with predictable demand or short lead times.


Applications of SIC

  • Low-Cost Items: Particularly effective for inexpensive goods.
  • Predictable Demand or Short Lead Time: Suitable when demand patterns are stable or lead times are minimal.
  • Warehouse-Specific Planning: Useful for planning by warehouse rather than across the supply chain.
  • Trading Industries: Commonly employed in sectors like supermarkets.
  • Immediate Demands: Effective for items required immediately by customers.
  • Ease of Use: Simple to implement and manage.


Limitations of SIC

Eliminating ERP Customizations: Key Considerations and Modern Solutions

Kathy Barthelt 0 9697 Article rating: 5.0

Transitioning away from customizations can indeed pose challenges, but it's not insurmountable with the right approach. Here’s a look at the real issues and solutions that can pave the way for a streamlined, up-to-date ERP.


Common Challenges:

  1. Dependency on Custom Processes
    Custom processes become ingrained, and removing them disrupts established workflows. However, business processes often evolve over time, as do best practices incorporated into modern ERP systems.

  2. Cost and Time Constraints
    Testing, retraining, and hiring consultants for an upgrade are valid concerns. Yet, consider the efficiency gains and reduced maintenance costs over time by utilizing standard ERP features.

  3. User Resistance
    Change management is critical, as employees can be skeptical of losing tools they’re familiar with. Effective communication about the benefits of standardized, future-ready tools can help ease the transition.


The Reality Check: Has Your Organization Changed?

Evaluate how much your business needs have shifted, how user expectations have evolved, and if any workarounds or interim solutions are now adding unnecessary complexity. Many companies discover that industry-standard ERP features can replace outdated customizations.


Did You Know?

Infor LN & Baan Tips & Tricks for FINANCE: Use of Electronic Bank Statements

Kathy Barthelt 0 45381 Article rating: 5.0

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

First45679111213Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES:

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:

  • Select the Quantity-dependent Routing check box in the Item - Production (tiipd0101m000) session.

  • Enter the routing codes in the Item - Routings (tirou1101m000) session. Enter the maximum quantity for which a routing is valid in the Up to Quantity field.

Note: If multisite functionality is activated, the routings available may vary per site on the job shop bill of material selected. Differences in routings have an impact on the standard cost calculation.

Default routing

If the Quantity-dependent Routing check box is not selected, the default routing applies to an item. However, this default routing must also be linked to the item. To find out, LN checks the default routing code in the Default Routing field of the Job Shop Master Data Parameters (tirou0100m000) session. Next, LN checks whether the default routing code is linked to the item in the Item - Routings (tirou1101m000) session. If so, the default routing applies to the item. If the default routing is not linked to the item, no routing is used.


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.

  • The destination financial company.

  • The transaction type and series.

  • The ledger account and dimensions.

  • The transaction currency.

  • The fiscal year and the financial period, the tax period, and the reporting period.

  • The integration document type and the Debit/Credit indicator.

  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

 
TECHNOLOGY: Infor LN Rest API

Frequently Asked Questions (KB2316174)

For Infor LN a framework has been developed to support REST API-based services for lean integrations. This framework is now made available for the LN application. This KB answers some common questions you may have and procedures that are needed for using the LN Rest APIs.

More details on these topics can be found in the Infor LN REST API Administration Guide.

Previous Article Infor LN & Baan Tips & Tricks for FINANCE: Integration Transactions - Compression
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Ledger Account Blocked Error
Print
21850 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories