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

Is Your ERP System Hurting Your Business?

The Importance of an Integrated System

Kathy Barthelt 0 10725 Article rating: 5.0

It could be if your ERP system isn't integrated with other systems that contain mission-critical business data.

Having data in two (or more) systems that don’t talk to one another is like baking a pizza crust in one oven and the toppings in another. Once baked, you may have food to snack on, but it sure isn’t pizza! Pizza requires the cheese, sauce and spices to bake with the crust, so all the flavors meld together when you take that first delicious bite. 

That’s the value of an integrated ERP system. When you...

Optimize with Infor Development Framework: IDF

Infor LX | BPCS | M3

George Moroses 0 13249 Article rating: 5.0

Why You Need IDF

The Infor Development Framework (IDF) not only helps you modernize the look and feel of your LX software but also the interactions of the IBM i software with other applications in your business.

“The IDF is a multi-user interface, single codebase architecture that’s metadata-driven (and) provides a lot of flexibility to adapt the software for their processes.” says Infor. This is the direction that Infor is going starting...

Managing the Inventory Risk

Infor LN & Baan

Kathy Barthelt 0 9548 Article rating: 5.0

Proper Inventory Management & Planning is not for the weak!

Any of these ever happen to you?

  • My supplier can’t provide the raw materials I need when I need them because I waited too long to order.
  • I underestimated how much raw material I had on hand and now my customer’s order is waiting on hold until I can get the parts I need.
  • I couldn’t meet the desired delivery date for my customer’s order, so they took their business somewhere else.
  • I ordered too many raw materials or made too many sub-assemblies because I didn’t have good visibility to my on-hand inventory.

...

LN & Baan | LX & BPCS Tip: 9 Tips for Secure Manufacturing Business Systems Through OT Cybersecurity Vulnerability Management

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

Crossroads RMC 0 17982 Article rating: 5.0

Always happy to share a good article on protecting your business from cybersecurity threats. 

9 OT Cybersecurity Strategies To Secure Manufacturing Industries

By Will Fastiggi - Technology for Learners - January 23, 2023

Let’s delve into the details of how to secure manufacturing industries through OT cybersecurity vulnerability management. Below are some tips and tricks.

1. Implement a...

RSS
First1415161719212223Last

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: All About Invoicing Methods

Invoicing Methods are a set of parameters that define the types of orders and order lines that can be collected on an invoice, the type of invoice to be generated and the costs to be aggregated on Project invoices and Service invoices.

If options to combine tax codes, departments, sales representatives' line of business area, etc... are checked, LN will combine all available transactions ready to be invoiced that have different tax codes departments, sales representatives, etc...into only one invoice.

If options to combine sales orders, sales order types, and shipments are checked then all sales orders that are created for the same business partner where the shipment and/or sales order type is different will be combined into one invoice.

For example:

  1. If sales order SLS001 is created for BP BP1000 with 2 lines where each line has a different shipment number, and the invoice method is combining shipments, both lines will be part of the same invoice. If the option to combine shipments is not checked then LN will create an invoice per shipment.
  2. If sales order SLS001 is created for BP BP1000 with 2 lines and 2 different shipment numbers and sales order SLS002 is created for the same BP with a cost item, LN will create one invoice for both orders if the option to combine sales orders and shipments is checked. If only the option to combine sales orders is checked then 3 different invoices will be created as all 3 lines will have different shipment numbers. If they have different sales order types and this option is not checked on the invoice method session then also 3 invoices will be created but if it is checked along with sales order and shipment number then only one invoice will be created.
  3. If we take scenario 1 again and both lines have different tax codes and the option to combine tax codes is not selected then LN will create a separate invoice for each line based on the tax code.
     

Note: In the case that the Business Partner Tax Country is different, even if we select combine tax codes, the system will create a separate invoice based on the Business Partner Country to full the statutory compliances for that BP country.

Previous Article Infor LN & Baan Tip: Cash Flow Functionality and Setup
Next Article Infor LN & Baan Tip: Why was the session "General Ledger Diagnostics Workbench" built?
Print
16873 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories