Infor ERP Tips and Infor ERP News for Infor LX, BPCS, Infor ERP LX, Infor LN, Infor ERP LN, Baan, Infor M3, and Movex

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

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Library BMRTOOLS contains the following commands

George Moroses 0 494 Article rating: 5.0

INSTALLBMR

  • Installs BMR Explosions from *SAVF or *LIB
  • Installs objects after backing up replaced objects
  • Installs source after backing up replaced source
  • Installs Webtop Metadata
  • Installs /InforBMR subdirectories
  • Writes all activity to log file and spooled file report
  • Optionally runs DBUPDATE command

DBUPDATE

  • Installs new or updates existing database tables, views, indexes, triggers, procedures, logical files.
  • Installs source for above objects
  • Sets authorities to replaced objects based on previous object settings
  • Sets journalling on replaced objects based on previous object settings
  • Installs Priming Data
  • Installs SSAOVR updates
  • Installs message file updates for core message files
  • Installs message file updates for NLV message files if included in explosion

This enhancement reduces the time required to install BMR Explosions. There still may be manual steps required after the processing completes, but the overall time required is dramatically reduced.

Read more

Infor LX/BPCS Tips & Tricks for OPERATIONS: Order Entry Action Code / Function Key Security

George Moroses 0 504 Article rating: 5.0

Access to Order Entry/Maintenance has traditionally been controlled by using LX Program Security to grant or remove authority to ORD700. LX Company Security and LX Warehouse Security further control which transactions a user is allowed to create or maintain. A separate 8.4.2 enhancement allows security managers to control which types of transactions a user is allowed to create or maintain, through LX Order Type Security and LX Order Class Security. Building on these LX transaction security features, the Order Entry Action Code/Function Key Security enhancement allows security managers to further control what actions a user can take regarding an authorized transaction.

Security managers can now control the actions each user is allowed to be restricted from in the Order Entry job stream. The benefit is easily illustrated by some examples:

  • Regular users can be allowed to create and revise customer orders but are restricted from deleting an order.
  • Salespersons can be authorized to full authority with quotes and can be allowed to create customer orders but not to revise or delete them.
  • Or, salespersons could be restricted from 1=Create in Order Directory, with the result that they could only create an order by copying a quote, if they are authorized to 3=Copy in Quote Directory.
  • Only selected customer service users can be allowed to create RMAs, by controlling 1=Create in RMA Directory. A different group of customer service users who handle the actual returns can be authorized to create the return orders or credit memos from those RMAs, by controlling 3=Copy in RMA Directory.

Read more

Infor LX/BPCS Tips & Tricks for FINANCE: Release Holds from IDF Order Inquiry Host Job

George Moroses 0 328 Article rating: 5.0

This enhancement provides the ability for IDF Order Inquiry to release order holds via a host job.

LX IDF Order Inquiry displays numerous details about an order, order lines, special lines and related files. An Order Inquiry user can copy, modify or delete an order through WebTop calls to ORD700 Order Maintenance, if authorized. Among the many details Order Inquiry also lists the Hold Codes for customer hold, credit hold, user hold, margin hold, and credit card hold. This enhancement provides the capability to release holds through a host job function that executes ORD680B, Order Hold Mass Release.   Batch Hold Release host job has been added to IDF Order Inquiry. The Order Inquiry user must be authorized to ORD680 in LX program security, SYS600.

ORD680 has been modified to accept parameters for multiple executions by host job. The user can release holds for a single order, a range of orders, or for multiple individually selected orders.

The following hold releases can be requested:

  • Credit hold – orders on credit hold by the system (01) or by a user (02) are released from credit hold.
  • Customer hold – orders on customer hold are released.
  • User hold – orders on user hold are released.
  • Margin hold – ORD680 re-evaluates orders or order lines that are on margin hold.
Read more

2026 is HERE: Is your Baan/LN strategy ready for the "2030 Countdown"?

Kathy Barthelt 0 686 Article rating: 5.0

The calendar has turned to 2026, and for Infor Baan and LN users, the roadmap ahead is more critical than ever. As we move closer to the end-of-decade legacy milestones, the status quo is no longer a viable strategy for your mission-critical operations.

What is your 2026 ERP Roadmap?

Think of your ERP strategy as a high-stakes navigation system. Without a clear plan, you risk stalling your business growth, falling behind on automation, and facing the "performance debt" of aging systems.

As you kick off the new year, ask yourself:

  • Does our legacy setup align with our 2026-2030 growth targets?
  • Are we leveraging AI and automation, or are we stuck in manual, time-consuming workflows?
  • Is our team fully trained on the latest features, or are we losing data integrity through "workarounds"?

How Crossroads RMC Can Future-Proof Your Operations

Whether you are optimizing your current system or planning a high-performance migration to Infor CloudSuite, we provide the specialized expertise that your business requires:

  • Utilization Reviews: Identify where current systems are underutilized and align ERP functionality with current and future business goals, ensuring the software evolves alongside the company.

  • Strategic Upgrades: Navigate the path from Baan or early LN 10.x) to the Infor CloudSuites to gain access to modern features such as AI-driven analytics and industry-specific capabilities.

  • Hyper-Automation: Deploy ERP add-ons that eliminate manual data entry and connect your entire shop floor.

  • Expert Training: Ensure your staff is prepared for the 2026 digital landscape with best-practice workshops.

Let’s Make 2026 Your Most Efficient Year Yet.

Don't let your ERP be a roadblock. Let’s turn it into your competitive advantage. Contact the Crossroads RMC team today to schedule your 2026 Strategy Session.

Contact the Crossroads RMC team today to schedule your 2026 Strategy Ses

Read more

Infor LN & Baan Tips & Tricks for OPERATIONS: Blocking Operations

Kathy Barthelt 0 1599 Article rating: 5.0

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 Managem

Read more

Infor LN & Baan Tips & Tricks for TECHNOLOGY: High Contrast Skin

Kathy Barthelt 0 1342 Article rating: 5.0

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.
     
Read more

Infor LN & Baan Tips & Tricks for FINANCE: Using Dimensions

Kathy Barthelt 0 1702 Article rating: 5.0

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 Mandatory, Optional, 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 l

Read more
245678910Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Manufacturing

Infor LN & Baan Manufacturing Tip: Performance Problems in Generate Order Planning (cprrp1210m000)

When the Generate Order Planning (cprrp1210m000) session is run it can take minutes to days to finish the process.

The performance of this session depends on many settings, like the number of plan items, the number of orders, but it also depends on hardware and database setup.

Here are some guidelines on how performance can be improved.

  • Be sure you are always on the latest solutions with the planning sessions. We are constantly improving the software to gain more speed in the Enterprise Planning (EP) sessions.
  • The number of planned items is critical. Try to reduce the number of planned items. Is it necessary that all items be planned via EP? For shop floor stock the TPOP or SIC replenish systems are often more suitable.
  • When you use PCS, be sure to close the projects when they are finished. When a PCS project has status Closed, the customized items will not be planned.

It's better to run Remove Plan Items for closed Projects (cprpd1220m000). This session removes the item planning data for customized items of closed projects.

  • If you run EP with the option, Also Generate Item Master Plan and/or Online Update Item Master Plan, consider if you need an Item Master Plan for all plan items. An Item Master Plan is usually meant for global long-term planning. Again this is not very useful for shop floor stock. Reducing the number of master-planned items improves performance.
  • When you use Resource Master Plans; are all your resources really critical? If a work center is not critical do not create a Resource Master Plan for it.
  • When using Item Master Plans and/or Resource Master Plans, set in Scenarios (cprpd4100m000) the total scenario length as short as possible. For example, if your sales order horizon is 2 years, a scenario end date which is 3 years after the current date is sufficient. During the calculations of the Item Master Plan and the Resource Master, all periods defined in the scenario are checked and calculated. So if you have the end date of the scenario on 2038, EP will do the calculations (for every master-planned item) until 2038.

Defining a rolling scenario will keep your scenario length constant and you don’t have to worry that you run beyond your scenario's end date.

  • Updating the pegging relations has a serious impact on the EP performance. In EP Parameters (cprpd0100m000) you can set the Pegging Horizon in days. Keep this horizon as short as possible. The Update Signals by Item/Planner option also has some impact, but less than the pegging.
  • EP uses the so-called phase numbers to detect the lowest level in which an item is used within a BOM structure or in a supplying relation. If the phase numbers are not ‘up-to-date’, EP will correct the phase numbers during the planning. This takes time during the planning run. If there are loops in BOMs or in supplying relations, this recalculation has a big impact on the performance. Therefore you could run Compute Phase Numbers (cprpd6200m000) on a regular basis. For example once a month. Always run this session with the Generate Report option selected. If loops are detected these are reported. Be sure to solve all the reported errors.
  • When unexpected results occur, especially when the data is imported from external packages, always check the number of records in tables cprpd100 and cprpd120. The number of records should match! Remark: From 10.4 onwards the table cprpd120 has become obsolete so this point not applicable anymore.
  • The number of calendars also impacts planning performance. Then for every warehouse, work center, or BP, and so on, a different calendar is defined. Planning has to read all of these calendars from start to end. This can have a huge impact on performance.
    • If you link a calendar to a work center or warehouse, avoid defining a new calendar for every work center/warehouse. Try to link the same calendar to more than one department.
    • Define the start of the calendar close to the start date of the scenario. For example, the current date is 01-07-2014, the start date of the scenario is 365 days in the past. So a start date for your calendar could be 01-07-2012.
    • Define the end date of the calendar not too far in the future. Depending on the end date of the scenario you could use 5 years ahead.  For example, the current date is 01-07-2014, the end date of the scenario is 3 years in the future. So an end date for your calendar could be 01-07-2022. Do not define an end date past 19-01-2038, which is the last UTC date Infor LN can handle.

Also, the interaction with the database can have a big impact on performance. 
A commonly used way to improve the total run time of the EP run is to start the session in parallel processing. 
See also Knowledge Base Article 22881401 Performance, Tracing and tuning Guide, for more details.

These guidelines are just some hints, and a good starting point because performance is a complex issue.

Previous Article Infor LN & Baan Tip of the Week: Limitations of Customer Defined Fields (CDFs)
Next Article Infor LN & Baan Tip: Broadcast message to users
Print
71808 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

x

Categories