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 Tip of the Week: Inventory aging analysis report

Kathy Barthelt 0 85848 Article rating: 5.0

A new standard Inventory Aging report can be printed in the Perform Inventory Aging Analysis (whina1440m000) session. This report is mainly based on the physical incoming and outgoing inventory movements and transactions. The date of inventory consumption or issue is compared to the date of receipt. If inventory is not yet issued, a reference date is used for aging calculation.

The report includes this information:

• Which inventory items are not frequently used or are obsolete.

• How long items have been stored in a warehouse.

• Inventory and transaction values. This facilitates the financial auditing process.

To use this new feature, an inventory aging analysis definition must be available in the Inventory Aging Analysis Definition (whina1140m000) session.

What do you get with IDF?

Infor Development Framework

George Moroses 0 33666 Article rating: 5.0

What do you get with IDF?

With Infor Development Framework (IDF), you can configure your view of the application data without modifying the core application and its supportability. Included with IDF are several interfaces including:

• PowerLink – A Windows-based client for end users

• Link Manager – A Windows-based environment administration client for importing environments, starting and stopping environment, and installing Fix Patches.

• Net-Link – A browser-based client (used by LX when running with SiW)

• System-Link – A XML-based interface for processing transactions from external sources.

The IDF ISO includes several components:

• All of the above interfaces

• Enterprise Integrator – for customizing IDF components and creating new business objects

• EGLi – Enterprise General Ledger 

• CRMi – Customer Relationship Management 

If you already have IDF installed for Infor LX 8.3.x, then it must be upgraded to a level that is compatible with LX 8.4. IDF PTFs and Fix Patches are required. See the Infor LX IDF 06.03.05 Installation and Upgrade Guide for details.

OTTO Q&A from the Director of Planning & Technology at Champion Industries

George Moroses 0 31256 Article rating: 5.0

1.  How difficult is it to initially install OTTO?

Dead easy is the straight answer. We relied on you to install, and you installed in the predicted 1 hour.  

2.  Would you install it on a test system or on the production system?

Production system is another easy answer. I use OTTO as the ideal prototype when talking to business contacts about “add-on” products. It is non-invasive; it only reads data from our ERP files. I know the implementation is 100% safe because no ERP files are ever updated (read corrupted) by OTTO.

3.  How difficult was it to implement OTTO? Was there a negative impact on daily operations?

There is a learning curve involved in using any new tool that has value to add. OTTO implementation is very low on the impact scale, but I would strongly recommend that a prospective client plan on investing in education and practice. OTTO implementation is low impact. No valuable tool is “no impact”.

Click here to learn more about OTTO

Is the Crossroads Analytics Dashboard Product Better than Spreadsheets?

Crossroads RMC 0 34439 Article rating: 5.0

You bet it is!

The Analytics Dashboard allows you to take your data and configure it any way you’d like, all without touching your ERP system! 

Any number of reports can be generated with just a few mouse clicks. In addition, full color graphs are automatically generated to illustrate the data being presented. Paper reports and Excel spreadsheets are dated. With Analytics Dashboard, data is refreshed at the touch of a button. 

Analytics Dashboard for Infor LN & Baan >
Analytics Dashboard for Infor LN, BPCS, & M3 >

MES News: Current trends indicate plants and factories are seeking to improve...

George Moroses 0 37432 Article rating: 5.0

Current trends indicate plants and factories are seeking to improve internal flexibility, implement a common information platform, and deliver real-time information. MES supports a variety of lean concepts on the plant floor, including kanban, waste reduction, load balancing, etc.  It maximizes your existing investment in your ERP system while embracing lean initiatives.  Visit our Crossroads MES page to learn more.

Infor LX & BPCS Tip of the Week: Purge optional during Month/Period End - LX 8.4

George Moroses 0 58750 Article rating: 5.0

For various month/period end programs, the purge function is now optional.

Scope:

INV903, Inventory Month End Close, optionally purges both inventory records as well as customer invoices. Some applications already have a flag or option for purging (for example, ACP900) and other applications are stand-alone. If you do not want to purge, do not run these programs: Order Purge and Close, ORD900, Close Quotes, ORD930, and Delete RMAs, ORD935. Now there are options on whether to purge records during the month end or period end programs.

The Benefits include:

• Flag or option added to allow the user to decide whether to perform month-end function with or without purge.

• Allows for month-end processing without purge.

• Improves efficiency of month-end processing.

Impact:

This enhancement includes these programs or areas:

• INV903, Inventory Month End Close

• ACR900, A/R Period Close

• CST900, PRF900, SFC900 Shop Order Close

• PUR900, Purchasing Month End Close

Johnson Crushers Selects Crossroads RMC for LN 10.6 Data Collection

Kathy Barthelt 0 38308 Article rating: 5.0

Johnson Crushers International (JCI), a global leader in engineering and manufacturing full lines of cone crushers, horizontal and incline vibrating screens and track-mounted, portable and stationary crushing and screening plants, has selected Crossroads RMC’s Data Collection solution for their Infor LN 10.6 implementation. 

JCI’s main objectives with this project are to support their continued growth and enable a continuous improvement effort to drive additional value to the business. In phase 1 of this project, JCI will implement Crossroad RMC’s Labor Reporting and Maintain Receipts data collection applications. Go live is expected to occur in early Q1 of 2020.

First6465666769717273Last

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories