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

BPCS/LX Tip of the Week: What is your M.O.?

Anthony Etzel 0 52664 Article rating: No rating

I’m not talking “Modus Operandi,” which is a fancy way to say: “what’s your plan to get stuff done”.  I’m talking about Manufacturing Optimization. 

It is all about efficiency, and by that I mean doing more with less. Less labor, less time, less materials, while still delivering a high quality product on time.

The Three Secrets to Improving your MO

1. Identify the key metrics
You need benchmark data so you know what realistic goals are, then track them and publish your performance along with a brief comment from time to time on how things are trending and how you compare with others, particularly your primary competitors. The best thing about this is that it is a system that develops a life of its own.

2. Measure it
Automatically, people start to think about improving things. Then the fun part, stuff begins to improve by itself. Once in place, the system just hums along and the benefits appear, because it has motivated people to think about it, and figure out what they can do to make it better.

3. Communicate it
So if you publish gross profit numbers, explain to people how what they do affects the numbers. Employees tend to start to modify their behavior as a result, and look more critically at whether a given purchase is even necessary.

Baan/LN Tip of the Week: What is your M.O.?

Kathy Barthelt 0 76601 Article rating: No rating

I’m not talking “Modus Operandi,” which is a fancy way to say: “what’s your plan to get stuff done”.  I’m talking about Manufacturing Optimization. 

It is all about efficiency, and by that I mean doing more with less. Less labor, less time, less materials, while still delivering a high quality product on time.

The Three Secrets to Improving your MO

1. Identify the key metrics
You need benchmark data so you know what realistic goals are, then track them and publish your performance along with a brief comment from time to time on how things are trending and how you compare with others, particularly your primary competitors. The best thing about this is that it is a system that develops a life of its own.

2. Measure it
Automatically, people start to think about improving things. Then the fun part, stuff begins to improve by itself. Once in place, the system just hums along and the benefits appear, because it has motivated people to think about it, and figure out what they can do to make it better.

3. Communicate it
So if you publish gross profit numbers, explain to people how what they do affects the numbers. Employees tend to start to modify their behavior as a result, and look more critically at whether a given purchase is even necessary.

BPCS/LX Tip of the Week: Ways to Prevent Scrap & Rework From Costing You

Anthony Etzel 0 49940 Article rating: No rating

Scrap and rework costs are a manufacturing reality impacting organizations across all industries and product lines.

Scrap and rework costs are caused by many things—when the wrong parts are ordered, when engineering changes aren’t effectively communicated or when designs aren’t properly executed on the manufacturing line.

No matter why scrap and rework occurs, its impact on an organization is always the same—wasted time and money. And while no one, especially an operations manager, wants to admit it, these expenses add up quickly and negatively impact the bottom line...

Read Full Article

Baan/LN Tip of the Week: Ways to Prevent Scrap & Rework From Costing You

Kathy Barthelt 0 78597 Article rating: No rating

Scrap and rework costs are a manufacturing reality impacting organizations across all industries and product lines.

Scrap and rework costs are caused by many things—when the wrong parts are ordered, when engineering changes aren’t effectively communicated or when designs aren’t properly executed on the manufacturing line.

No matter why scrap and rework occurs, its impact on an organization is always the same—wasted time and money. And while no one, especially an operations manager, wants to admit it, these expenses add up quickly and negatively impact the bottom line...

Read Full Article

Tip of the Week: 8 Common-Sense Rules for Inventory Management

Anthony Etzel 0 51918 Article rating: No rating

Common sense rules. We may not like them, but generally, they stand the test of time and should be followed. Here are 8 common sense rules related to inventory management published by Inbound Logistics back in 2007. They still hold true today. 

1. If you don' t know where you are going, no road will take you there. Enterprise resource management systems are designed to tell you about today' s inventory. With some work, you can also access information about past inventory. To manage inventory proactively, however, you must know projected inventory levels for the future.

2. Make what you can sell. An integrated Sales and Operations Plan will naturally take into account expected demand in its production plan. Inventory is not an independent variable - it is the direct result of demand and supply.

3. Sell what you can make. Too often, a disconnect exists between sales and marketing desires and the reality of production capabilities.

4. If you can' t sell it, stop making it. If demand for your product does not materialize, you need to identify that gap quickly to avoid a buildup of non-moving inventory. Numerous mechanisms can be put in place to identify such trends.

For tips 5 through 8 and more details into the other tips, click the button below to read the full article.

Read Full Article

Tip of the Week: 8 Common-Sense Rules for Inventory Management

Kathy Barthelt 0 75085 Article rating: No rating

Common sense rules. We may not like them, but generally, they stand the test of time and should be followed. Here are 8 common sense rules related to inventory management published by Inbound Logistics back in 2007. They still hold true today. 

1. If you don' t know where you are going, no road will take you there. Enterprise resource management systems are designed to tell you about today' s inventory. With some work, you can also access information about past inventory. To manage inventory proactively, however, you must know projected inventory levels for the future.

2. Make what you can sell. An integrated Sales and Operations Plan will naturally take into account expected demand in its production plan. Inventory is not an independent variable - it is the direct result of demand and supply.

3. Sell what you can make. Too often, a disconnect exists between sales and marketing desires and the reality of production capabilities.

4. If you can' t sell it, stop making it. If demand for your product does not materialize, you need to identify that gap quickly to avoid a buildup of non-moving inventory. Numerous mechanisms can be put in place to identify such trends.

For tips 5 through 8 and more details into the other tips, click the button below to read the full article.

Read Full Article

Crossroads RMC to Exhibit at Inforum 2016

Crossroads RMC 0 27194 Article rating: No rating

Inforum 2016  returns as a three and a half-day event of educational seminars and workshops focused on the future of enterprise software and your business. This event is Infor’s premier event for 2016, and Crossroads RMC is excited to sponsor the event! Come see us in Booth 173 to learn about Crossroads MES and Analytics Dashboard solutions for the shop floor, our Services for Baan/LN and BPCS/LX, and see a demo of our latest solution, Analytics Dashboard, which can be connected to any ERP to provide up to the minute sales analysis data.

    
 

If ERP is plumbing for the Enterprise - How do we unplug it and keep it from making a huge mess?

David Dickson 0 36469 Article rating: 5.0

I have been working with ERP in various roles for over 30 years, directly involved in over a hundred implementations, while my company has been involved with over 400 more. Of course, in many ways the systems we use today are completely different from what we used in the ‘80s – back then it was green screens, simple transaction entry forms, and cumbersome updates (at best) to link what one department did with all the other areas that needed access to that information. Then there were those planning programs that took all the information along with various parameters the users needed to set and told us what to do.

The More Things Change, the More They Stay the Same

First979899100102104105106Last

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.

Last

Tips: LN | Baan

Kathy Barthelt

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
66273 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories