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 News You Can Use: Driving Digital Product Passport Compliance

Crossroads RMC 0 5718 Article rating: 5.0

Prepare for Digital Product Passport Compliance with Expert Insight from Lora Cecere
Founder, Supply Chain Insights

With the EU Digital Product Passport (DPP) set to launch in 2027 for initial industries—batteries, consumer electronics, and textiles (footwear and apparel)—businesses are beginning to confront a rapidly evolving compliance landscape. Yet with many requirements still undefined, confusion is widespread.

Lora Cecere's latest research helps organizations cut through the uncertainty by offering actionable insights and a clear, customer-centric, outside-in approach to DPP readiness.

Key Highlights:

  • Start with the Customer in Mind
    Align compliance efforts with market demands to drive growth and gain a competitive advantage.

  • Break Down Silos
    Cross-functional collaboration—across sustainability, supply chain, procurement, and policy is essential for success.

  • Clarify Compliance
    Understand the core elements that define DPP compliance and the practical steps needed to achieve it.

  • Learn from Diverse Approaches
    See how companies are navigating DPP differently, with no one-size-fits-all path to readiness.

  • Adopt GS1 Standards
    Address the existing gap in the implementation of critical global standards for traceability and product information.

Build the capabilities your organization needs today to meet the demands of tomorrow—with a forward-looking, customer-first strategy.

👉 [Access the full research here

5 WARNING SIGNS Your Disconnected Business Systems Are Costing You Money

Crossroads RMC 0 5628 Article rating: 5.0
  1. You Can’t Track Project Costs in Real-Time
    If you're waiting until after a project wraps up to find out whether it was profitable, that’s a major red flag. Without real-time cost tracking, you're making critical decisions in the dark.

  2. Quoting and Estimating Are Slow, Manual, or Inconsistent
    Does it take hours—or even days—to build a custom quote because you're pulling information from multiple systems? That lost time translates directly into lost sales opportunities.

  3. You Rely on Spreadsheets for Critical Operations
    Spreadsheets are useful—until they’re not. Issues like version control problems, accidental overwrites, and human error can lead to costly mistakes.

  4. Scheduling and Inventory Management Are Disconnected from Financials
    If your production and finance teams aren’t working from the same data, it’s only a matter of time before you face delays, stockouts, or budget overruns.

  5. You Don’t Have a Real-Time View of Project Profitability
    Without live costing tied directly to jobs, small losses can accumulate unnoticed, until it's too late.

Disconnected data refers to information stored outside your core business systems, like your ERP. While this data has value, a lack of integration causes inefficiencies and misalignment across your organization, often more than you realize.

The Cost of Disconnected Data...

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Authorization and Security - LN REST APIs

Kathy Barthelt 0 7741 Article rating: 5.0

In typical LN REST API integrations, permissions and authorizations are not implemented or rarely used. To ensure smooth data exchange and avoid errors, it is recommended to disable the authorization and security settings.

Recommendation:

  • In the Authorization and Security Parameters session (tcsec0100m000):

    • Clear the Authorization and Security Enabled check box.

    • Clear all check boxes under Authorization Enable for on the Enabling tab.

Why This Matters:

  • Enabling authorization and security without proper setup can lead to errors and blocked transactions during integration.

  • For example, work center permissions may interfere with:

    • Creating new shifts

    • Booking machine hours

    • Read more

Infor LN & Baan Tips & Tricks for OPERATIONS: Copy Customized Product Structure to Standard Structure (tipcs2232m000)

Kathy Barthelt 0 5935 Article rating: 5.0

This functionality allows you to copy the product structure of a customized item to a standard item.

Note: When a customized structure is copied to a standard structure, the Customized check box in the Items session (tcibd0501m000) is cleared.

Item Types:

  • Standard Items: Identified by a regular item code.

  • Segmented Items: Consist of a project code segment and an item base segment (i.e., the customized item’s item code). Segments are defined in the Item Code Segmentation session (tcibd0500m000).

Only components valid for the specified Effectivity Unit will be copied.

Copy Options:

  • Target Routing Code
    Enter the code of the standard routing to which the customized structure should be copied.

  • Copy Product Structure
    Choose whether to:

    • Copy the entire structure

    • Copy only the first level

    • Perform the copy interactively

  • Reference Date
    Only parts of the product structure valid on this date will be copied.

  • Copy E-Item Relationships
    If selected, related E-item records will be copied.

  • Copy All Components and Effectivity Statements
    If selected, unit effectivity is copied to the standard structure. You can specify the unit.
    Exceptions related to routings and operations (that meet date effectivity) are also copied.

  • Alternative Material
    If selected, alternative BOM components are included in the copy.

  • Use-Up Material
    If selected, use-up materials from BOM components are included.

Infor LN & Baan Tips & Tricks for FINANCE: Rebuild History for Account Matching (tfgld1218m000)

Kathy Barthelt 0 7394 Article rating: 5.0

Use this session to rebuild the ledger account history for account matching. This is particularly useful if you’ve recently defined a ledger account, on which transactions already exist, as a matchable account.

You can specify the fiscal year and period for which you want to rebuild the account matching history.

Note: This session can also be used to remove unmatched transactions if you decide to stop performing account matching for a specific ledger account.

Field Information

Selection Range

  • Use Job Reference Date
    If selected, Infor LN uses the Job Reference Date as the basis for rebuilding history data.

  • Job Reference Date
    Specifies the date and time used for the rebuild process.
    Enabled only if "Use Job Reference Date" is selected.

  • Financial Company
    The financial company for which you want to rebuild a ledger account history.

  • Ledger Account
    The specific ledger account to rebuild.

  • Fiscal Year
    The fiscal year for which you want to rebuild the ledger account matching history.


     

Infor LX/BPCS Tips & Tricks for FINANCE: Override Warning in Invoice Entry PO Costing

George Moroses 0 10751 Article rating: 5.0

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.

Infor LX / BPCS Tips & Tricks for OPERATIONS: Auto Calculate Vendor Delivery Date

George Moroses 0 2942 Article rating: 5.0

Enhances purchase order efficiency by automatically calculating the Vendor Delivery Date based on user input.

  • When a purchase order line is created, the user enters the item, order quantity, and Due Date.

  • LX automatically calculates the Vendor Delivery Date, adding buffer time for quality control, testing, and inspection activities.

  • If the Due Date is revised, an informational message prompts the user to review and potentially update the Vendor Delivery Date.

Enhancements:

  • A new PUR820 system parameter enables automatic recalculation of the Vendor Delivery Date.

  • Instead of a manual reminder, PUR500 now issues a message: “Vendor Delivery Date recalculated,” showing the updated date.

Benefits:

  • Eliminates the need to manually review and update the Vendor Delivery Date.

  • Removes the need to delete and recreate PO lines to trigger automatic date calculation.

First678911131415Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE: Using Dimensions

You can independently define dimensions and use them to prepare analyses of ledger account transactions and balances. You can use up to 12

dimension types. You can define a name and an entire structure of dimension codes for each of these dimension types. There is no relationship between the dimension types.

For example, you can set up these dimensions:

  • Dimension Type 1 = Cost center
  • Dimension Type 2 = Item group
  • Dimension Type 3 = Business unit
  • Dimension Type 4 = Geographical area
  • Dimension Type 5 = Activities

You can separately define the dimension structure for each of these dimension types, in other words, you can set up a dimension structure for the cost centers, a structure for item groups, and so on.

You can define the number of dimension types that you use in the Group Company Parameters (tfgld0101s000) session. If you have several financial companies in a company group, the dimension types used apply to all the companies in the group.

You can name the dimension types and define linked objects in the Dimension Type Descriptions (tfgld0102m000) session. You can then define the dimension codes to be used in each company in the Dimensions (tfgld0510m000) session. You can also make multilevel dimension structures with totals and subtotals. You can build a dimension hierarchy of up to ten levels.

In the Dimensions (tfgld0510m000) session, you can define the dimensions for each dimension type, and link the dimensions to parent dimensions and child dimensions.

Dimensions are always used together with ledger accounts. For each ledger account, you can define which dimension type or types are linked to the ledger account in the Chart of Accounts (tfgld0508m000) session. For each dimension type, you must select whether the dimensions type is MandatoryOptional, or Not Used by the ledger account.

When you enter a transaction, you must first state the ledger account. Then you must enter a dimension for each Mandatory dimension type that is linked to the ledger account, and you can enter a dimension for each Optional dimension type.

For example, the sales revenues ledger account is linked to dimension type 2 (item group) and dimension type 4 (area). The dimension type 1 (cost center) and dimension type 3 (business unit) are not used for the ledger account. The freight costs ledger account is linked to only dimension type 1 (cost center). The other dimension types are not used for the ledger account.

For each dimension type, you can define one dimension with an empty dimension code. If the dimension type is Optional for a ledger account, LN posts transactions for which no dimension is specified to this dimension. In this way, differences between the ledger history and the dimension history can be avoided.

In the Cross Validation Rules (tfgld0151m000) session, you can define the ranges of allowed dimensions by ledger accounts. You cannot change the dimension range for a ledger account that occurs in an unfinalized batch.

You can create transactions for Financials from the integration with other LN packages. You can enter these transactions into ledger accounts and into dimensions. You can define the assignment to ledger accounts through the Mapping Scheme (tfgld4573m000) session.

You can use the dimensions to split the transactions on the customer and supplier control accounts by departments, persons responsible for the revenues, costs, properties, debts, and so on.

The dimensions also provide the basis for the cost allocation in the Cost Accounting module. In CAT, you can allocate the costs (and any revenues) within a dimension type from one dimension code to another and from one dimension type to another.

TECHNOLOGY: High Contrast Skin

The high contrast skin can be activated by users who experience low vision, color-blindness, or similar visual impairments.

If the high contrast skin is active, LN UI is colored so that all controls comply with the WCAG AA norms for accessibility.

Guideline 1.4.3 Contrast (Minimum)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. For level AA, these exceptions apply:

  • Large text: large-scale text and images of large-scale text have a contrast ratio of at least 3:1.
  • Incidental: the following text or images of text have no contrast requirement:
    • Text or images of text that are part of an inactive user interface component.
    • Text or images of text that are pure decoration.
    • Text or images of text that are not visible to anyone.
    • Text or images of text that are part of a picture that contains significant other visual content.
  • Logotypes: text that is part of a logo or brand name has no minimum contrast requirement.

OPERATIONS: Blocking Operations

Note: The Blocked Operations (tisfc0540m000) session displays the blocked operations.

Introduction

Sometimes a problem occurs that must be solved before an operation proceeds. Examples of such situations are:

  • The quality of an intermediate product must first be inspected.
  • A machine is in repair.
  • A supplier cannot deliver an essential component in time.
  • A customer is late with its payments.

In these situations the operation can get the operation status Blocked.

An operation can be blocked:

  • Manually.
  • Automatically by Quality.

Blocking reasons

Every blocked operation must have a blocking reason. The blocking reason of a blocked operation has two purposes:

  • To indicate why the operation is blocked.
  • To determine which actions you can no longer perform on the operation.

Types of blocking

The following actions can be blocked by means of a blocking reason:

  • Reporting a quantity completed.
  • Reporting a quantity rejected.
  • Reporting a quantity to be inspected.
  • Reporting an operation completed.

You normally carry out these actions in the Report Operations Completed (tisfc0130m000) session.

You can define blocking reasons in the Blocking Reasons (tisfc2100m000) session.

Manual blocking

Use the Report Operations Completed (tisfc0130m000) session to block an operation. When you block an operation, you must also enter a blocking reason. If Quality has already blocked the operation, you can only enter a blocking reason, which is more restrictive than the blocking reason of Quality.

Blocking by Quality Management

Quality uses the blocking reasons specified in the Quality Management Parameters (qmptc0100m000) session, to block operations. For details, see the Using QM for manufacturing operations topic.

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories