Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Does your existing data collection equipment and barcode label printers need some love and attention?

Kathy Barthelt 0 30074 Article rating: 5.0

Crossroads RMC knows that new equipment is not something that everyone can or wants to include in their budget. Sometimes you need to make due with what you have. We are proud to partner with a local company that repairs existing data collection equipment, and sells refurbished devices as well.

Want to bring a little life back into your equipment and extend their use? Contact us today to see if your data collection equipment can be given new life! 

Kathy Barthelt – VP Sales
Crossroads RMC
Phone: 1.630.955.1310, x113 | Cell: 1.630.408.7759
kbarthelt@crossroadsrmc.com

Read more

Do you have spreadsheets and separate databases that may or may not be tied to Baan/LN?

Kathy Barthelt 0 30861 Article rating: 5.0

Do you have spreadsheets and separate databases that you’re keeping on the side that may or may not be tied to Baan/LN?

-Do you wish they were integrated so that you didn’t have to manually go into each system to report on the data or look up information? 
-Are you running into problems because you don’t have exposure to all of the data that is critical to running your business?

Crossroads RMC has a team of integration experts who can create the integration you’ve been dreaming about… AND we have developed RMCconnector to allow for quick and easy translation data from your front end system into a format accepted by your back end ERP. 

Learn More

Read more

Baan/LN Tip: Saving Space in Your General Ledger

Kathy Barthelt 0 41453 Article rating: 5.0

Compressing Integration Transactions

One way to save space in your general ledger is to compress integration transactions. The transactions are combined into one ledger account number. However, the detail is still available in the integration transactions sessions.

The compression is seen after the transactions are finalized. 

Compression is established in the mapping scheme by checking the box under the columns “Compression of Debit/Credit Transactions". This can only be done in a mapping scheme that is not activated. 

Read more

BPCS/LX Tip: Backup and Save options

Anthony Etzel 0 32901 Article rating: No rating

Users are no longer limited to backing up or saving files to a tape or diskette.They can now use a Save File (SAVF) to save data and objects. LX programs that perform saves and/or backups were modernized to add a new SAVF option.  

There were numerous places in LX where users are prompted to save a file or library. These screens have options for tape or diskette. Diskette refers to the old 8” diskettes used on System/38. These devices are outdated and virtually obsolete. The current means of saving objects on the IBM i, is through the use of a Save File (SAVF). This compresses the data into a single object that can be saved and is easily transferred between systems.

These objects were modified and/or created for this enhancement:

  • Backup Simulation (FOR630C, FOR630D, FOR630FM, FOR640HT, and FOR630HT)
  • Month End Close (INV903D, INV903FM, INV901C, and INV903HT)
  • Purge YTH/Restore Archived Lots (INV912C, INV912D, INV912DHT, and INV912FM)
  • Purge and Save ITH records (INV932C, INV932D, INV932FM, and INV932HT)
  • Labor Ticket Save (SFC905D, SFC905FM, SFC901C, and SFC905HT)
  • Backup Infor LX Files (SYS700C, SYS700D, SYS700FM, and SYS700HT)
  • Backup Infor LX Programs (SYS710C, SYS710D, SYS710FM, and SYS710HT)
  • Backup Infor LX Source (SYS740C, SYS740D, SYS740FM, and SYS740HT)
  • Save File Name Selection (SYS912D, SYS912FM, and SYS912HT)


Benefit

Use the Backup Simulation to copy a simulation file to a SAVF or tape. Users may want to do this to transfer simulation data from one system to another, from site to site, or to save the data before permanently deleting it from the system.

Read more

Navistar goes global with Crossroads RMC!

Kathy Barthelt 0 22009 Article rating: 4.7

Navistar, a leading manufacturer of commercial trucks, buses, defense vehicles, and engines, has selected Crossroads RMC’s data collection middleware to use for their global data collection solution. Implementation began in late 2018 with Navistar’s Illinois facility and will be completed in all other divisions by the end of 2019.

Read more

Don’t Let Malware Destroy Your ERP System!

Crossroads RMC 0 21355 Article rating: 5.0

We just got a report that another one of our customers has been affected by malware. In this case it wiped out their ERP server. We are working with them to restore it an get everything up and running again. It is highly likely that this got into their network by an email attachment. This seemed like a good opportunity to remind everyone to be extremely careful with email attachments. Even if it appears to be from someone that you know, email “From” addresses can be forged.

Best practice is to save the attachment to a folder, and run a virus scan before opening or viewing the file.

Read more

Baan/LN Tip: Credit Control Parameters (ACR Parameters)

Kathy Barthelt 0 45067 Article rating: 5.0

In the Credit Control Parameters, you can indicate if the same letter will be sent for reminding and action taken if amounts are zero or negative. The reminder letters work in conjunction with overdue sales invoices and the “Reminder Diary Margin.” When an invoice has passed its due date plus a certain margin of days, LN generates a reminder advice for the invoice. 

Read more

Crossroads Welcomes Ridewell Corporation – MES for Infor LX

Anthony Etzel 0 21831 Article rating: 5.0

Crossroads RMC welcomes Ridewell Corporation as our newest client having selected Crossroads MES (Manufacturing Execution System) for their shop floor automation with integration to Infor LX. 

Ridewell engineers and manufactures air-ride, rubber-ride, steel spring and mechanical suspension systems for the truck, trailer, RV and bus industries. The company has served the transportation industry since 1967 and holds many active patents for exclusive features that provide for low maintenance and superior ride quality.

Ridewell’s objective was to eliminate shop floor paperwork and manual processes, obtain real time performance metrics, and achieve greater visibility over manufacturing operations. After carefully conducting their due diligence they selected Crossroads MES to address these challenges.

Crossroads Manufacturing Execution System connects your manufacturing plant to the rest of your enterprise by using touch screen PCs on the shop floor. Powered by IBM I Power Systems, Crossroads MES fills the gap that exists between your ERP system and your lean manufacturing initiatives by modernizing and transforming the ERP experience. It delivers paperless shop packets to your entire workforce, captures live manufacturing data, and then delivers real-time status to your Tablet or PC.

Key Features include:

  • Paperless Shop Floor                               
  • Labor and Machine Time
  • Production Reporting
  • Material Issue
  • Scrap Reporting
  • Scheduling
  • Capacity Load Balancing
  • Label Integration
  • Dashboard Analytics                    

Crossroads MES provides information that helps manufacturing decision makers understand how current conditions on the plant floor can be optimized to improve production output.

Crossroads RMC is proud to have Ridewell Corporation as a client and we look forward to working together to support their company growth and success.

Read more
RSS
First6263646567697071Last

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.

Read more

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.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Manufacturing

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
Contact author

Theme picker

Contact author

x

Categories