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

ERP & the Importance of Accuracy & Productivity

Infor LN & Baan

Kathy Barthelt 0 9925 Article rating: 5.0

If you don't think accuracy and productivity are important, you need to take a hard look at HOW you’re running your ERP system.

  • Have you eliminated large amounts of data entry?
  • Is your data error-free at month's end?
  • Do all of your systems talk to one another?

If the answer is no, Crossroads RMC can improve accuracy and productivity with system integration and/or automation.

Too expensive you say? Too time-consuming and way too much effort to make it happen? Not necessarily... 

Effective September 30, 2023, IBM® will end support of the IBM i operating system 7.3

AND Infor will no longer support LX and related products on IBM i 7.3 as of June 1, 2024

Crossroads RMC 0 10795 Article rating: 5.0

THE CLOCK is T I C K I N G ... 

MARK YOUR CALENDARS!
Effective September 30, 2023, IBM® will end support of the IBM i operating system 7.3  AND  in line with IBM’s support policy, Infor will no longer support LX and related products on IBM i 7.3 after May 31, 2024.

All Infor LX releases, patches, and related solutions will be...

Infor LN & Baan Tip: Considerations for Release to Warehousing for a Cost Item

Kathy Barthelt 0 15152 Article rating: 5.0

When there are two Cost Items, one with Release to Warehousing applied and the other with Release to Warehousing not applied, upon approval of the Sales Order, the Cost Item that is released to Warehousing will go straight to Staged status, pending Shipment confirmation, while the Cost Item that is not released to Warehousing will be up for Sales Deliveries.

Apart from this main difference in functionality between having and not having this option to release to Warehousing checked, there are other impacts to consider...

Reskilling and Upskilling Your Staff – Why You Shouldn’t Ignore This

Crossroads RMC 0 11111 Article rating: 5.0

According to the World Economic Forum, half of all employees will require significant reskilling or upskilling by 2025.

For many of you, your Infor ERP system was implemented 5, 10, 15, or 20+ years ago, and now there are only a handful of people left from that implementation if any at all. Since most of your "how and why" walked out the door, how much longer can you get by on “tribal knowledge”? While many companies understand the importance of employee training, implementing that training remains a challenge. What’s the best way to proceed you ask?

Infor LN & Baan Tip: What conditions must exist before changing an item's inventory unit?

Kathy Barthelt 0 15321 Article rating: 5.0

Is there a procedure for changing an item’s inventory unit? What conditions must exist before it can be done?

Once inventory transactions (receipts or issues) have occurred for an item, the inventory unit cannot be changed. If only orders have been placed against the item (sales or purchase), the inventory unit can be changed if these...

Infor LX & BPCS Tip: 4 Approaches to Customizing LX / BPCS - Preparing for a Future Upgrade

George Moroses 0 11803 Article rating: 5.0

How do I modify BPCS/LX to allow for the ease of upgrading in the future?

  1. Exit Points...
RSS
First1112131416181920Last

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
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip of the Week: Job Groups in LN

In a scenario where performing job A depends on the result of job B, it is hard to decide at what time job A must be scheduled, and how long job B runs. To handle dependent jobs, you can now create a job group. Use the Job Groups (ttaad5140m000) session to create a job group. A job group has a name, with the same characteristics as a job name, and a description. The Status and User of the job group are handled automatically.

After creating the job group, the jobs are added to the group, approximately in the order the jobs must be performed. The first job in the group (with the lowest Group Number) determines the handling of the whole job group, such as execution date and whether the job group is being repeated. If the job group is not repeating, the job group and all non-repeating jobs in the job group are deleted when the job group has run.

The dependencies of the jobs in the job group are also determined. A job in the job group can only depend on a job in the same job group with a lower job number.

You can use the specific options in the Job Groups (ttaad5140m000 andttams5640m000) sessions to change the status of the job group. The job group statuses have the same meaning as the status of the jobs and the same status changes are allowed.

Note: Job groups are only handled by the BSE service Job Scheduler Service.

Previous Article Infor LN & Baan Tip of the Week: Credit Checks for Business Partners
Next Article Infor LN & Baan Tip of the Week: Customer requested delivery date
Print
40544 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories