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

George Moroses

Infor LX & BPCS: Waste in Manufacturing

In manufacturing, waste is anything that doesn’t add value to or benefit the end customer. Reducing waste enables manufacturers to save money and increase productivity. Where is the waste happening in your processes?

How often is your department spending time and resources on the following tasks?

Manufacturing:

  • Correcting repeated problems with production quality
  • Juggling manual production schedules
  • Holding up production due to delayed component deliveries
  • Constantly evaluating labor and material resource needs


Materials:

  • Correcting deliveries with missing or wrong items
  • Sending overstocked inventory back to a warehouse or other location
  • Searching for raw materials, tools, or other equipment
  • Waiting on a late delivery from a supplier


Finance:

  • Managing increasing carrying costs of inventory
  • Dealing with budget overruns on projects
  • Managing cash flow due to unnecessarily long lead times and shipment times
  • Constantly evaluating labor and material costs to get overall production costs down


Company-wide:

  • Correcting repeated problems with production quality
  • Correcting deliveries with missing or wrong items
  • Holding up production due to delayed component deliveries
  • Constantly evaluating labor and material costs to get overall production costs down


What if you could eliminate these problems by spending $5/day?

Crossroads MES (Manufacturing Execution System) captures all of your ERP production data and harnesses the power of that data to “UP” your team’s efficiency by providing the right information at the right time to the right people to eliminate waste and optimize your business.

Watch video (2:00) to learn more:

Previous Article Infor LX & BPCS Tip: Overhead Costs - CST120D1
Next Article Infor LN & Baan: BIG DATA - Keeping Track of Key Metrics
Print
31465 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

During an Exchange import, you can use all the functionality programmed into the Data Access Layer (DAL). If you use the DAL, Exchange carries out all the constraint checks, integrity checks, and side effects, for example, updates on other tables, that are programmed into the DAL. Database integrity is guaranteed automatically.

Using the DAL reduces the costs of interface development. You can use the DAL to import standard interfaces developed by Infor for partner products, as well as for specific interfaces built by customers, for example, to integrate LN with legacy systems. You can use the DAL in both single site and multisite environments.

The checks or additional actions specified in the DAL are carried out for each row that is imported. Database errors are logged in the same way for DAL and non-DAL import. DAL hook errors are also logged. You can specify whether the DAL property checks are or are not carried out.

If you specify the use of the DAL for a table relation for an import, the dal.new, dal.update, and dal.destroy functions are used instead of db.insert, db.update, and db.delete. You can choose to use DAL for particular tables and not for other tables, therefore, an import batch can contain both types of table relations simultaneously. The import through DAL works for both the import based on audit or indicators (inserts, updates, deletes), and the full import (inserts only).

DAL settings are run time aspects, which means you can change these aspects without having to regenerate the import program. DAL settings are also logged in the log table at batch line level, to enable you to find out what the DAL settings were when the import was run.

Important to realize is that an update through the DAL can result in a number of side effects. Actions performed by the DAL must not be carried out twice. For example, if the DAL updates the available to promise (ATP) quantity for an item when importing order data, the ATP quantity must not be updated in a condition script as well.

For this reason, you must not add any actions in condition scripts, or import additional data, that are already handled in the DAL.

Categories