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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Receiving to Inspection

If the item being received needs to be inspected prior to being available for use, there are two schools of thought.

The first is to receive the item to a QC hold location. The downside is the item will show up in on hand inventory.

A better method would be to do a PO receipt to inspection. Both Inv500 and Pur550 support this method. Now you have received the item without showing it in inventory. Only the PO quantity in inspection is updated. This method also allows you to create an Inspection Dispatch Report. After the QC process for the item is complete, then the transaction Receipt from Inspection to Stock is processed. That transaction then updates the PO quantity received field and the Item on hand field in inventory.

Previous Article Baan/LN Tip of the Week: Purchase Inquiry
Next Article Baan/LN Tip of the Week: Plan Codes
Print
71415 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Industry Insight: Why ERP Data Stays Siloed, and What to Do About It

Most manufacturers don't have a data problem. They have a connection problem.

Production data lives in one system. Sales and customer data lives in another. Finance runs somewhere else entirely. Each system does its job well on its own, but without a way to connect them, the organization never gets the full picture, and neither do the people trying to run the business.

Why This Happens
ERP systems are often the core of a manufacturer's operations, but they rarely operate alone. Over time, businesses add third-party software for CRM, e-commerce, warehouse management, EDI, and more. Each addition solves an immediate need, but without integration, it also creates another silo.

The result is familiar across manufacturing: teams end up manually re-entering data between systems, waiting on reports that should be immediate, and making decisions without visibility into what's happening elsewhere in the business.

Integration vs. Enhancement
There are two ways to close this gap, and they solve different problems:

  1. ERP Integration connects your ERP to the third-party software you use every day, creating a single source of data instead of several disconnected ones. Whether it's a one-way, two-way, or complex systems integration, the goal is the same: eliminate errors, reduce manual entry, and give everyone access to the same real-time information.
  2. ERP Enhancement goes a step further, creating new functionality or modifying existing functionality within the ERP itself, so the system matches how your business actually operates rather than forcing your business to adapt to the system's limitations. Done right, enhancements use parameter-co

Categories