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

Analytics Dashboard: How To Save Time, Effort AND Money

Infor LX, BPCS, Infor M3, Infor LN & Baan

Crossroads RMC 0 32773 Article rating: 5.0

So often companies spend a lot of time, effort, and money to create custom reports to analyze their data.

Sometimes 5, 10 or more reports are necessary to satisfy the different needs of executives, managers, and sales reps.

Why go through this hassle when everyone can create their own views of the data without customizing a single thing?

Crossroads RMC's Analytics Dashboard puts the control in the hands of the users. Multiple views of the data can be created, saved, and retrieved all with the click of a button.

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

Infor LN & Baan Tip of the Week: Customer requested delivery date

Kathy Barthelt 0 44669 Article rating: 5.0

The “Use Customer Requested Delivery Date” parameter has been introduced in the Sales Order Parameter (tdsls0100s400) session, which is used to track the customer’s requested delivery date.

If this parameter check box is selected, various additional date fields become available to track the customer Initial Requested Delivery Date and the Original Promised Planned Delivery Date.

Infor LX & BPCS Tip of the Week: ION Tip – Pausing Receiving and Sending of Messages

Anthony Etzel 0 46599 Article rating: 5.0

If it is necessary to pause sending and receiving of BOD messages on your IBM i during your month end process, it is best practice for the document flows that point to the IBM i to guarantee delivery of BOD messages. Once the month end process has been completed, you will need to Resume the ‘Receiving’ and ‘Sending’ Active Connection Points so your documents will continue to process.

Pausing Sending messages

To pause sending messages to ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be paused for sending messages.
  3. In the Sending Paused column, click Pause. The page is automatically refreshed and the Sending Paused checkbox is selected. A Resume button becomes available. 

Sending of messages by this connection point is stopped....

Tax Law Changes by the Numbers - Infor LX & BPCS Integration to Avalara

A look at what's changed in 2018-2019

Anthony Etzel 0 37621 Article rating: 4.0

Are you up to speed on all of the sale tax changes that could affect your business?

Tax Law Changes by the Numbers
A look at what's changed in 2018-2019

  • 21 states adopted economic nexus as of December 31, 2018, requiring out-of-state businesses with a certain amount of economic activity in the state to collect and remit sales tax
  • 33 states have enforced economic nexus as of June 30, 2019
  • 43 states will enforce economic nexus as of December 31, 2019
  • 7 states had marketplace facilitator sales tax laws as of December 31, 2018, requiring marketplaces to collect sales tax on behalf of their sellers
  • 15 states have marketplace facilitator sales tax laws as of June 30, 2019
  • 28 states will have marketplace facilitator sales tax laws as of January 1, 2020

The trend to tax remote sales is certain to continue, and there will be the normal slew of rate, regulation, and product taxability changes. 

Sales Tax is complicated! Crossroads RMC provides the integration from Infor LX & BPCS to Avalara to make it easy. Click Here to Learn More

Steps to undo an IDF modification and restore to the default

Anthony Etzel 0 31140 Article rating: 5.0

Changes are great, but if you want to undo an IDF modification and restore to the default, you need to follow these steps:

Reset to an Infor shipped view (“un-modify” it)

  1. Open the public node of an object you would like to reset to the shipped status. Notice that all of the standard views (i.e., those owned by Infor) are unmodified.
  2. Select the row with the Modified column = yes
  3. Select the Reset to default button on the toolbar
  4. Say Yes to the prompt
  5. The object is now back to the way it was shipped by Infor. Note that it now shows that it has not been modified. If you display the editor, you will see that the attribute you deleted has been restored. Note that only objects owned by Infor can be reset. If you change a standard definition, and later regret it, you can use this feature to restore it with a couple of clicks.

How to Improve Customer Shipments With OTTO - A Case Study

Anthony Etzel 0 24386 Article rating: 5.0

Setting Industry Service Standards

Shenandoah Manufacturing, a $20 million producer of poultry-raising equipment (heaters and brooders), had been having difficulty for some time shipping orders to customers in a timely manner. They had successfully implemented a popular ERP system and had been using it for more than 3 years, yet the situation didn't improve.

Customer Service Representatives were complaining about the frequent backorders and late orders. Employees were giving it their best effort, but were frustrated, and customers were threatening to take their business elsewhere.

The company considered installing an APS system as a possible solution, but found implementation would be difficult, expensive, and running the system might be a challenging task as a number of key business practices would have to be changed. A consultant familiar with OTTO suggested they look at that product as an alternative to APS. Several OTTO aspects cited by the consultant convinced them to consider a cursorily review. Specifically:

  • The non-intrusive nature of the product.
  • It's relative inexpensive initial investment.
  • The low overall total cost of ownership.
  • The integration with their ERP system.

The initial demonstration was impressive. OTTO was installed on Shenandoah's server within 45 minutes of arrival and, most impressively, it was fully functional with their real "live" data immediately. Needless to say, the demo was well received. Even more importantly Shenandoah was able to "test drive" the software to prove its applicability before making any dollar commitments.

According to Mark Shank, Information Systems Manager, some baseline measurements were made last year, and it was determined that approximately 50% of their customer orders had shipped on time. As they began using OTTO, on-time order performance rose to 90% for the month. And Shenandoah caught up on its entire backlog and started working ahead on February's orders. In February on-time shipment performance jumped to 92% and subsequently on-time performance has ranged somewhere between 98.3% and 99.5% — well above the 96% goal set by Management.

OTTO provides the means for keeping the whole production organization focused on the few things that have to happen as the ship date approaches to get each order shipped on time. Components that have the potential for delaying an order are identified so they can be managed. Shenandoah's staff, a precious and limited resource, now concentrates on analyzing information and managing the right things at the right time rather than digging out date. To quote one production control individual: "what use to take hours now takes seconds."

According to Roy Hackett, Plant Manager: "Knowing the right things to pay attention to at the right time"

Crossroads RMC's Analytics Dashboard serves as the perfect complement to extend your MES solution

George Moroses 0 28163 Article rating: 5.0

Did you know our Analytics Dashboard serves as the perfect complement to extend your MES solution?

Need real-time information regarding what shop orders are active, which lines are down, and overall OEE? Want to display all of this data in easy to understand graphs and charts with drill-down capability?

Contact us today to find out how our Analytics Dashboard can provide all of the information you need in real-time.

  • MES Work Center Job Step Status
  • MES Work Center Machine Status
  • MES Shop Order Status
  • MES Order / Operation Status
  • MES Order / Parts Status
  • MES Badge Status

Contact George Moroses to learn more.

Infor and Crossroads RMC Partner to Drive Success at Ridewell

Anthony Etzel 0 30742 Article rating: 5.0

Earlier this year, Ridewell Corporation inked a deal with Infor to move their BPCS 4.05 CD system to Infor LX. As part of that deal, Crossroads RMC’s MES software was selected to provide shop floor automation. 

For the ERP upgrade, Infor reached out to Crossroads RMC to provide support for both Finance and Data Conversion due to our positive track record with 4.05 CD to LX migrations. Crossroads RMC has extensive migration experience and developed a methodology for converting legacy 4.05 CD GL into CEA. 

The process Crossroads RMC developed makes it cleaner, more manageable, and easy to embrace from the client perspective. Infor also engaged Crossroads RMC to provide technical support to manage the data conversion, utilizing the Infor utilities and converting Ridewell’s 4.05 CD data to standard LX.

RSS
First5556575860626364Last

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories