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.

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.

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.

FINANCE: Release Holds from IDF Order Inquiry Host Job

OPERATIONS: Order Entry Action Code / Function Key Security

TECHNOLOGY: Library BMRTOOLS contains the following commands
 

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