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: 3 Common ERP Mistakes & How to Avoid Them

For many businesses, a high-powered ERP can streamline processes, increase efficiency, and strengthen the bottom line—at least in theory. In reality, some companies miss out on the opportunity to achieve greater ROI by overlooking a few fundamental truths about ERPs.

1. Implementation takes longer than usually anticipated.

2. Company buy-in and sufficient training can predict success.

3. Implementing the full range of features can make the difference between success and failure.

Can your ERP move with you into your next growth phase? Can it scale and flex as your business expands? Is your business making the most of your investment?

Read Full Article

Optimize Your Manufacturing Today!

Previous Article Baan/LN Tip of the Week: 3 Common ERP Mistakes & How to Avoid Them
Next Article Baan/LN Lunch & Learn Webinar: What Manufacturers Need to Know About Sales Tax Compliance
Print
28946 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

This is a simple way to go from the customer order to making the order and shipping the order. It involves a few simple steps:

  1. Receive and enter the customer order
  2. Automatic credit review
  3. Automatic release of the shop order tied to the customer order
  4. Issue material, report labor to the production order receipt
  5. Pick the order, ship the order, invoice the customer


With lean, you can skip processing the demand through MRP. You can go directly from the customer order to the shop order creation.

Define Inventory transactions for issuing components to the shop and receiving finished items. See the Inventory help text for examples of transactions.

  • Transaction type I - Single Issue to Shop Order. Use this transaction type to issue one component at a time. Use this for high-value items that are marked as Must Single Issue on the Item Master file.
  • Transaction type M - Multiple Issue to Shop Order. Use this transaction type to issue all the components as listed in the Shop Order, in one transaction. Note that this transaction type does not issue Must Single Issue items.
  • Transaction type S - Receipt from shop. Use this transaction type to receive the finished item into stock and update the shop order accordingly. 

The Shop Order Lot/Location Allocation program is an alternative to using the above Inventory transactions. Use this when the item is finished, and you want to review exactly what was used to make it. You can review the components as allocated, make any changes, and finally accept the finished order.

First132133134135137139140141Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

1345678910Last

Theme picker

Categories