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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Plan Codes

In Baan IV, plan items exist within the context of a plan code. A plan code includes only items of the MPS Item item type. Planned orders are independent of a plan code. Users can compare plan codes by means of the Plan Code Performance Comparison (cprmp4504m000) session.

The scenario concept in Infor LN replaces the plan code concept in Baan IV.

In Infor LN, the basic data for plan items is the same for all scenarios. However, users maintain not only the master plan within a scenario, but the planned orders as well.

For example, for each scenario, Users can specify:

  • Special demand for an item.
  • The availability of resources (in the Scenario – Availabilities (cprpd4160m000) session).
  • The sourcing strategies and supply strategies.

Users can compare scenarios by means of the Performance Indicators (cprao2201s000) session.

Previous Article Infor Next Presentation – Achieve Fast and Easy Upgrades for CloudSuite Industrial (Syteline)
Next Article BPCS/LX Tip of the Week: Shop Order Release Date
Print
45495 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Exit Points is a new feature in Infor LX Version 8 that allows users to customize, without changing the original LX source code. Exit points provide a way for you to call an external program and pass a set of parameters to implement any needed custom logic. By using Exit Points, LX customers are able to modify the software, and still take advantage of new releases from Infor. Exit points are available in many LX programs. A complete list is available on the Infor support website.

Optimize Your Manufacturing Today!

Poor performance indicators make for poor outcomes.

Companies today continue to tolerate and accept how labor and production information is recorded, and the reliability on that information is questionable. In addition to collecting labor and production information, there are many other pieces of information manually recorded from the shop floor.

A critical element of information for productivity throughput would be to examine how much time the work center or machine was actually up and running. Downtime is another critical element of data that is usually manually recorded along with a reason identifying what caused production to stop. If this information is not provided on a timely and accurate basis, then what good is it anyway? Forms are filled out, data may or may not be keyed to a spreadsheet, the forms are sorted and filed, but is anybody really looking at the information that was recorded? Think about the amount of time it takes to manage the manual collection of information from your shop floor. 

What would real time access to data mean to your organization?
The benefits:

  1. Real Time Production Visibility
  2. Reduced Paperwork Load
  3. Downtime and Scrap Visibility
  4. WIP Inventory Visibility
  5. Improve Efficiency, Capacity Utilization

Optimize Your Manufacturing Today!

First101102103104106108109110Last

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:

12345678910Last

Theme picker

Categories