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 Growth with Connected eCommerce & Tax Automation

Frank Petrasio 0 98 Article rating: 5.0

Is your current Infor LX or BPCS system holding back your growth? It doesn't have to.

In 2026, staying competitive means moving beyond manual workflows and data silos. Crossroads RMC has partnered with Aleran and Avalara to provide an integrated, end-to-end solution designed specifically for manufacturers and distributors in the Infor LX and BPCS market.

Transform Your Operations from Quote to Cash

This powerful partnership enables you to maximize your existing ERP investment without the need for a total overhaul.

  • Aleran: Modern B2B eCommerce
    • 24/7 Digital Catalog: Provide a fully branded shopping experience that connects directly to your LX/BPCS data.
    • Self-Service Portals: Empower customers and dealers with real-time access to inventory, quotes, and order history.
    • Streamlined CPQ: Simplify complex product configurations and pricing to accelerate sales cycles.
  • Avalara: Automated Tax Compliance

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: User Provisioning

George Moroses 0 94 Article rating: 5.0

This enhancement: 

  • Provides an ability for LX to integrate with Infor Federation Services (IFS) to automate provisioning of users.
  • Activates LX exit points during maintenance of LX business roles and business units to publish the SyncSecurityRoleMaster BOD which can be received by IFS as LX-specific roles in addition to the three IFS predefined LX-specific roles: LX-SystemAdministrator (corresponding to LX security type S = LX Security Officer); LX-SystemManager (corresponding to LX security type M = LX Security Manager); and LX-User (corresponding to LX security type U = LX User).
  • Enables support for LX receiving an inbound SyncSecurityUserMaster BOD (sent from IFS) and creating or revising the associated LX user (or security manager or security officer). This enhancement also supports creating an IBMi user profile which can then be defined as an LX user (or security manager or security officer).
  • Activates LX exit points during maintenance of LX users (and security managers and security officers) to send the ProcessSecurityUserMaster BOD to IFS requesting creation or revision of a user on behalf of LX.
  • Automates sending revised LX user authorities to corresponding System i Manager (SiM) tasks which can then be uploaded to System i Workspace (SiW).

Infor LX/BPCS Tips & Tricks for OPERATIONS: IDF RMA Inquiry

George Moroses 0 91 Article rating: 5.0

This enhancement provides a robust RMA Inquiry capability. The base RMA Inquiry application delivers role-based functionality to support customer service, sales, pricing and business analysis functions.

The IDF RMA Inquiry presentation enhances a number of customer service and data analysis functions.

  • RMA List provides filters that allow sorting and sequencing by any displayed data field, such as RMA number, customer number, Total RMA amount, request date, good thru date, Customer reason code, Disposition reason code, Q/C reason code.
  • RMA Line List provides filters that allow sorting and sequencing by any displayed data field, such as item number, request date, extended amount, net price, Customer reason code, Disposition reason code, Q/C reason code.
  • RMA detail cards provide additional details about the RMA, as well as about any orders that will result from the RMA.


IDF RMA Inquiry provides significant enhancement to several business roles:

Customer service personnel, customer service managers responsible for handling customer complaints and negotiating return conditions with the customer Warehouse personnel, warehouse manager at the return warehouse. Billing personnel, billing managers responsible for processing credits to the customer and handling questions related to the RMA, return and eventual credit.

Managers responsible for analysis of returns related to reasons for returns, resulting replacement orders, recommendations for improving pricing or internal processes to reduce returns.

Infor LX/BPCS Tips & Tricks for FINANCE: Archive Net Price for Deleted Lines

George Moroses 0 85 Article rating: 5.0

Infor LX now stores the Net Price for a deleted line, so that the information is available for later analysis.

If an order line is canceled, LX stores the current Net Price in a new Net Price Archive field. The Net Price Archive field is updated whether the line is deleted through Line Entry (ORD700D2) or Fast Line Entry (ORD700DA), or the entire transaction is deleted through Order, Quote or RMA Directory (ORD700D1).

The Net Price Archive field can be useful when analyzing the reasons for canceled order lines. Users can define Cancellation Reason Codes related to pricing. Review of the archived Net Price, along with other values from canceled order lines such as Order Quantity and Selling Unit of Measure, Cancellation Reason Code, Request Date, Price Book Date, Item Number and Customer Number, can lead to adjustments to pricing structures, promotion qualifiers or other actions that can avoid loss of revenue on future orders, or follow-up actions to recover the canceled line.

Is your team still manually entering UPS and FedEx information into your Baan or Infor LN system?

Kathy Barthelt 0 167 Article rating: 5.0

If so, those manual shipping steps are likely costing you time, money, and customer satisfaction:

❌ Re-entering shipping details into Baan or Infor LN

❌ Copy-pasting tracking numbers

❌ Delayed invoicing and frustrated customers

There’s a better way to manage your parcel shipping.

RMCship: Seamless UPS & FedEx Integration

RMCship is a powerful automation solution that fully integrates UPS WorldShip and FedEx Ship Manager directly with Baan IV, Baan V, and Infor LN.

We eliminate manual entry and streamline your entire workflow:
 

Before RMCship (Manual)

After RMCship (Automated)

Re-keying data into two systems      

✔️ Create cartons/pallets directly in ERP

Delayed tracking updates

✔️ Auto-send shipment data to UPS/FedEx

Manual tracking number entry

✔️ Instantly pull back tracking numbers, freight, and more 

Manual invoice updates

✔️ Auto-add shipping data to sales orders & invoices

The Results Are Clear:

Infor LN & Baan Tips & Tricks for OPERATIONS: Simulated Purchase Prices (ticpr1170m000)

Kathy Barthelt 0 633 Article rating: 5.0

Use this session to define simulated purchase prices for purchased items per site.

Field Information:

  • Cost Calculation Code - price calculation code
  • Item

The raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, and sold.

An item can also represent a set of items handled as one kit, or which exist in multiple product variants.

You can also define nonphysical items, which are not retained in inventory but can be used to post costs or to invoice services to customers. The examples of nonphysical items:

  • Cost items (for example, electricity)
  • Service items
  • Subcontracting services
  • List items (menus/options)
     
  • ​Site - The site for which the purchase price is simulated.
  • Purchase Currency - The currency of the simulated purchase price.
  • Simulated Price - Purchase price

The simulated purchase price and currency are recorded twice.

  • Simulated Price Multi Currency - The purchase price in multiple currencies.

The simulated purchase price and currency are recorded twice. The amount in this field is related to the price of the supplier.

  • Unit - Purchase price unit
  • Cost Component - The cost component that must be of the type Material Costs.

Note: The cost component specified in this field does not become part of the standard cost detail structure if it is part of the cost component scheme of the selected item. If calculations are performed with a calculation code not used for actualization (simulations only), the simulated purchase price is mapped to the cost component defined in the records for this session.

123457910Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

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
70469 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories