Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

BPCS/LX Tip of the Day: Material Requirement Dates and Lead Time Offsets in MRP

Anthony Etzel 0 343 Article rating: No rating

The system automatically performs offsets for requirements dates for components in the MPS/MRP calculations. It also performs offsets for calculation of material need dates at the time that shop orders are released.

To calculate the offset, the system takes the parent lead time from the Item Master and adjusts it by the bill of materials offset (plus or minus) for the component. This gives the lead time days for that specific component. The system starts with the due date of the parent and backs up and skips all non-work days in the shop calendar.

 

Note that the offset calculation uses only calendar records that have a blank work center (the calendar record applies to all work centers). See the information for the Shop Calendar Maintenance program, SFC140, in your Shop Floor Control documentation for shop calendar details.

Read more

Baan/LN Tip of the Week: Database Sizing – Moving to LN

Kathy Barthelt 0 219 Article rating: No rating
The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.
Read more

How Do You Measure Success in Your Business?

Anthony Etzel 0 52934 Article rating: 5.0

Business owners may measure success in different ways – some tangible, some intangible.

In order to establish how you should measure success for your business, you need to first examine how you measure your personal success. If you are a business owner, or a part of the management team of the company you work for, ask yourself these questions to see how you measure up:

Assess personal success.

1.    Am I happy in my job?

2.    Do I have passion for what I’m doing?

3.    Do I get the desired results based on the effort I’m putting in?

4.    Am I putting forth my best effort?

5.    Am I patient and allow for sufficient time to see results?

6.    Do I get respect from my co-workers?

7.    Do I have the endurance to hang in there when things get a bit rough?


Reflect on successes and failures.

After answering these questions, do you need to make any changes? Do you still have the same ambition and drive to achieve the goal? Are you content with your work, or have you come to the conclusion that you have not done your best?

To be successful...

Read more

Baan/LN Tip of the Week: Switching to a Difference Series

Kathy Barthelt 0 204 Article rating: No rating

In general, you can enter a different series in the order field if you have an available series.

To add a new series, find the appropriate group in the First Free Number session, and add a new series and first free number (usually 1).

In Baan IV, go to the Maintain First Free Numbers Session (under Common, Tables, Maintain Logistics Tables, Maintenance 1). Groups are easily identified (e.g., Purchase Order, Sales Order, etc.).

In Baan V, go to the First Free Number Session (under Common Data, Tables, Logistics). There are number groups (e.g., 570 may be for Purchase Orders, 650 may be for Sales Orders, etc.).

In LN, go to the First Free Number Session (tcmcs0150m000 – it is in different places in the menu under different Feature Packs). There are number groups (e.g., 210 may be for Purchase Orders, 310 may be for Sales Orders, etc.).

Read more

BPCS/LX Tip of the Day: MRP/MPS Simulation

Anthony Etzel 0 786 Article rating: No rating
The system allows you to manipulate and maintain a simulated MPS and MRP. You can copy the simulation from the existing first cut or you can create a totally new schedule. You can also perform a simulation of the rough-cut capacity plan. This allows a quick visual inspection by inquiry or menu of needed work center loads for the proposed MPS. After you choose a suitable MPS and rough-cut capacity, the system allows you to transfer the simulated MPS to the live Master Production Schedule.
Read more

BPCS/LX Tip of the Day: Inventory Stocking Levels – LX

Anthony Etzel 0 735 Article rating: No rating

The system supports four levels of inventory. You can view summaries of stock at each level through the Material Status Inquiry program or through reports.

 

Below are the four levels:

â–ª  Item

â–ª  Item + warehouse

â–ª  Item + warehouse + location

â–ª  Item + warehouse + location + lot

 

The lot number level and/or container of inventory can cross multiple warehouses and locations. For example, item + lot or item + lot + container. Locations exist within warehouses. There is no limit on the number of warehouses, locations, or lots that you can assign to an item.

Read more

Baan/LN Tip of the Day: Transfers - LN

Kathy Barthelt 0 2779 Article rating: No rating
A Transfer involves either one or two warehouses. If items are transferred between two different warehouses, all activities of the warehousing procedures must be carried out. However, if a transfer takes place between two locations within the same warehouse, the receipt activities are not carried out. You can use transfer orders to define a replenishment system within a single warehouse. This system controls replenishment from bulk locations to pick locations. Note: LN allows you to modify the outbound order line data based on the value the Allow Updating Outbound Order Lines up to and including field is set to in the Warehousing Order Types (whinh0110m000) session.
Read more

BPCS/LX Tip of the Day: LX Inventory Pallet Status Flow

Anthony Etzel 0 49923 Article rating: No rating

Four fields in the Item/Warehouse record (IIW file) affect the disposition of the

pallet status.

 

1.  Goods Receiving Code: You define these codes in Goods Receiving Maintenance (WHM130). The codes control whether or not the stock passes through inspection, what percentage, or quantity of a delivery to inspect, and the number of quarantine days, if any.

 

2.  Inspection Zone/Inspection Location: Either the Inspection Zone or the Inspection Location must be entered on the Item/Warehouse Master Maintenance screen WHM150D2-01.

 

Read more
First112113114115117119120121Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Read more
Last

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Manufacturing

Infor LN & Baan Manufacturing Tip: Performance Problems in Generate Order Planning (cprrp1210m000)

When the Generate Order Planning (cprrp1210m000) session is run it can take minutes to days to finish the process.

The performance of this session depends on many settings, like the number of plan items, the number of orders, but it also depends on hardware and database setup.

Here are some guidelines on how performance can be improved.

  • Be sure you are always on the latest solutions with the planning sessions. We are constantly improving the software to gain more speed in the Enterprise Planning (EP) sessions.
  • The number of planned items is critical. Try to reduce the number of planned items. Is it necessary that all items be planned via EP? For shop floor stock the TPOP or SIC replenish systems are often more suitable.
  • When you use PCS, be sure to close the projects when they are finished. When a PCS project has status Closed, the customized items will not be planned.

It's better to run Remove Plan Items for closed Projects (cprpd1220m000). This session removes the item planning data for customized items of closed projects.

  • If you run EP with the option, Also Generate Item Master Plan and/or Online Update Item Master Plan, consider if you need an Item Master Plan for all plan items. An Item Master Plan is usually meant for global long-term planning. Again this is not very useful for shop floor stock. Reducing the number of master-planned items improves performance.
  • When you use Resource Master Plans; are all your resources really critical? If a work center is not critical do not create a Resource Master Plan for it.
  • When using Item Master Plans and/or Resource Master Plans, set in Scenarios (cprpd4100m000) the total scenario length as short as possible. For example, if your sales order horizon is 2 years, a scenario end date which is 3 years after the current date is sufficient. During the calculations of the Item Master Plan and the Resource Master, all periods defined in the scenario are checked and calculated. So if you have the end date of the scenario on 2038, EP will do the calculations (for every master-planned item) until 2038.

Defining a rolling scenario will keep your scenario length constant and you don’t have to worry that you run beyond your scenario's end date.

  • Updating the pegging relations has a serious impact on the EP performance. In EP Parameters (cprpd0100m000) you can set the Pegging Horizon in days. Keep this horizon as short as possible. The Update Signals by Item/Planner option also has some impact, but less than the pegging.
  • EP uses the so-called phase numbers to detect the lowest level in which an item is used within a BOM structure or in a supplying relation. If the phase numbers are not ‘up-to-date’, EP will correct the phase numbers during the planning. This takes time during the planning run. If there are loops in BOMs or in supplying relations, this recalculation has a big impact on the performance. Therefore you could run Compute Phase Numbers (cprpd6200m000) on a regular basis. For example once a month. Always run this session with the Generate Report option selected. If loops are detected these are reported. Be sure to solve all the reported errors.
  • When unexpected results occur, especially when the data is imported from external packages, always check the number of records in tables cprpd100 and cprpd120. The number of records should match! Remark: From 10.4 onwards the table cprpd120 has become obsolete so this point not applicable anymore.
  • The number of calendars also impacts planning performance. Then for every warehouse, work center, or BP, and so on, a different calendar is defined. Planning has to read all of these calendars from start to end. This can have a huge impact on performance.
    • If you link a calendar to a work center or warehouse, avoid defining a new calendar for every work center/warehouse. Try to link the same calendar to more than one department.
    • Define the start of the calendar close to the start date of the scenario. For example, the current date is 01-07-2014, the start date of the scenario is 365 days in the past. So a start date for your calendar could be 01-07-2012.
    • Define the end date of the calendar not too far in the future. Depending on the end date of the scenario you could use 5 years ahead.  For example, the current date is 01-07-2014, the end date of the scenario is 3 years in the future. So an end date for your calendar could be 01-07-2022. Do not define an end date past 19-01-2038, which is the last UTC date Infor LN can handle.

Also, the interaction with the database can have a big impact on performance. 
A commonly used way to improve the total run time of the EP run is to start the session in parallel processing. 
See also Knowledge Base Article 22881401 Performance, Tracing and tuning Guide, for more details.

These guidelines are just some hints, and a good starting point because performance is a complex issue.

Previous Article Infor LN & Baan Tip of the Week: Limitations of Customer Defined Fields (CDFs)
Next Article Infor LN & Baan Tip: Broadcast message to users
Print
66209 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

x

Categories