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

Crossroads RMC Welcomes Robert Brown!

Crossroads RMC 0 15766 Article rating: 5.0

Crossroads RMC Welcomes Robert Brown, as a Sr. Business Consultant!
Bob brings 30+ years of shop floor and project management skills to Crossroad RMC. He is a self-starter that has progressively mastered the Manufacturing, Supply Chain, and Finance modules within Infor LX. Bob will get started with EDI/ECM set up for new trading partners and within the Supply Chain ranks. Bob is a great addition to the Crossroads RMC team, and we look forward to his leadership expertise on implementations and upgrades in the near future.

You can benefit from a business process review only if...

Infor LX | BPCS | Infor LN | Baan

Crossroads RMC 0 17383 Article rating: 5.0

Did you implement your ERP system 5 years ago… or maybe 20 years ago? At the time, it was like a brand new car… sleek, fast, top-of-the-line, and fuel-efficient. And although it may have needed a few minor “adjustments”, overall you were very pleased. Fast forward to today. Does it still have that new car smell? Does it run as efficiently as it used to? Do you know how to fix a problem when it occurs?

While ERP systems are certainly designed to last, over time, your business changes, your customers’ needs change, employees change and you are left with a system that may run “fine”, but you certainly don’t feel the same way about it as you did when it was brand new.

So the good news is that you CAN restore that “new car smell” with a utilization review, or business process review.

What is a Utilization or Business Process Review and Why Do I Need One?
Simply put, a business process review is an...

Dashboards vs. Reports – What do they offer and which do I need?

Crossroads RMC 0 23555 Article rating: 5.0

Companies are collecting oceans of data, and struggle with transforming it into usable information. Most businesses focus on two methods of sharing data - the report and the dashboard. While these two terms mean many things to many people, it is important to understand what these terms mean and how the report and dashboard have similar features but they are not the same thing.  

What is a Report?

A report is meant to be used to gather detailed intelligence on the operations within an organization, thus a report can be either very broadly covering a wide scope of related information, or narrowly focusing on details of a single item, purpose, or event. All of this information, while presented in a report, is meant to be a snapshot in time.

Quite often, a report is built within the ERP system itself and often is constrained by the graphical and user limitations within the ERP. More often than not, large amounts of data are exported to Excel where added features allow for better manipulation of the data to a format that is digestible by users. Regardless, the data is only valid for that moment and time.

What is a Dashboard?

A dashboard is a graphical interface that provides at-a-glance views revolving around answering a central question. For example, an executive may ask you for up-to-the-minute details on "how the business is doing?". The answer to that question is as complex as the organizational structure of the company, but it is probably very simply measured with approximately 10 metrics. Those 10 metrics can likely be analyzed in chart form, and can and should be combined into one chart when the numbers are relatable or are on a similar scale. All these things should be considered when building a dashboard.

Dashboards, similar to the one in your vehicle, display critical data. Imagine driving down the road and having to push a bunch of buttons to find out how much fuel you have left, or having to pull over and pop the hood to check the oil pressure. It would be dangerous and a waste of your precious time. Your car's control panel or dashboard displays the most crucial information in an easy-to-use, graphical way.

How do Dashboards and Reports differ?

Infor Customer Meeting: LX, XA, and System21 All-Hands Call

Live Webinar for all Users - Wednesday, April 20 2022

Crossroads RMC 0 15884 Article rating: 5.0

Infor Customer Meeting: 
Live Webinar for all Users

Wednesday, April 20
11:30am - 12:00pm EST

Please join Infor leadership, who will discuss the exciting future strategy for our LX, XA, and System21 customers in the Americas. In this session, we will cover our stated direction, product future, and how this will positively impact your business.  Additionally, we will discuss the driving forces behind these changes and how our study group of customers has been reacting.  Whether you are a long-time customer or a relatively new customer of Infor’s, we welcome you to join this brief update of the future of your ERP solution and introduce you to the Infor team that will service and support your organization.

Our GM of the Americas, Bill Vellante, and VP of the Americas, Jay Allison will host this 30-minute session.

RSVP now

Join Event

Infor ERP Tip: Top 5 Ways Modern Analytics Reduces Spreadsheet Risk & Inefficiency

Infor LX | BPCS | Infor LN | Baan

Crossroads RMC 0 21952 Article rating: 5.0

Spreadsheets are often the tool of choice for many organizations to store and arrange information for financial planning, analytics, compliance, and more. Ironically, for many business processes that involve managing data, it creates the exact opposite effect––silos of information and inefficiency. And because it stores organizational data in a readily sharable way, there is a high risk of exposing confidential information.

Read this Infor best practice guide to discover the top five business processes that a modern data and analytics architecture can automate and deliver far more value than spreadsheet-driven techniques.

Infor Best Practice Guide: 5 Ways Modern Analytics Reduces Spreadsheet Risk and Inefficiency

Infor LN & Baan Tip: Cost Component Setup

Kathy Barthelt 0 20372 Article rating: 5.0

To break down an item’s standard cost, sales price, or valuation price, use cost components. With cost components, you can compare estimated and actual costs, calculate production variances, and analyze costs in Standard Cost Calculation.

If cost components are set up in a detailed way, detailed records...

Manual Processes Are Killing Your Productivity

Infor LX | BPCS | Infor LN | Baan

Crossroads RMC 0 17548 Article rating: 5.0

Nearly 70% of workers say that the biggest opportunity of automation lies in reducing time wasted on repetitive work.

Which repetitive tasks would workers most like to see automated? A recent study by McKinsey Global Institute found that there are three productivity killers that workers are eager to automate:

  1. Data Collection: Eliminate human error and manual data entry by automatically collecting, uploading, or syncing data into a system of record (55%).
  2. Approvals: Become more efficient by automating approvals, sign-offs, and confirmation requests (36%).
  3. Updates: Reduce wasted time by automatically requesting status updates and other information (32%).

Workers believe that automating these tasks will reduce wasted time (69%), eliminate human error (66%) and recover hours lost to manual, repetitive tasks that could be automated (59%).

Too expensive you say? Too big of an effort to make it happen?  Not necessarily...

RSS
First1718192022242526Last

Theme picker

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories