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

Tip of the Week: Ways to Manage the Pain of Losing a Key Employee Before it Ever Happens

Anthony Etzel 0 32250 Article rating: No rating
  • Sit down with your IT team. Decide how the information will be captured and where it will be stored so that employees have access to it. What software tools need to be used to capture the information? How does it need to be organized? Create a repeatable process to make this easy for your staff.
     
  • Interview the person. Have them talk you through his/her job. What are the things they do every day? What are their biggest challenges? How do they overcome them? 
     
  • Have someone shadow the person for a week. Watch what they do and how they do it. Ask questions. Who does he/she interact with in their department? Outside of their department? Why?
     
  • Find out what tools he/she uses to perform their job? Are there spreadsheets?  Reports within your ERP / outside of your ERP? Separate stand-alone databases? Drawings? Websites? Why does he/she use them?
     
  • Video record how the person does their job. Is their technique critical to “doing it right” the first time and not ending up with a bunch of scrap that you can’t reuse?
     
  • Figure out if the person does anything special on a monthly, quarterly, or annual basis that might not come up during the observation period or interview. 
     
  • Map how he/she uses your business system and how that impacts the rest of the company. Understand both the “what” and the “why”. Without this, new employees may end up figuring out what they need to do, but never understand why they need to do it.

Optimize Your Manufacturing Today!

Tip of the Week: Ways to Manage the Pain of Losing a Key Employee Before it Ever Happens

Kathy Barthelt 0 39338 Article rating: No rating
  • Sit down with your IT team. Decide how the information will be captured and where it will be stored so that employees have access to it. What software tools need to be used to capture the information? How does it need to be organized? Create a repeatable process to make this easy for your staff.
     
  • Interview the person. Have them talk you through his/her job. What are the things they do every day? What are their biggest challenges? How do they overcome them? 
     
  • Have someone shadow the person for a week. Watch what they do and how they do it. Ask questions. Who does he/she interact with in their department? Outside of their department? Why?
     
  • Find out what tools he/she uses to perform their job? Are there spreadsheets?  Reports within your ERP / outside of your ERP? Separate stand-alone databases? Drawings? Websites? Why does he/she use them?
     
  • Video record how the person does their job. Is their technique critical to “doing it right” the first time and not ending up with a bunch of scrap that you can’t reuse?
     
  • Figure out if the person does anything special on a monthly, quarterly, or annual basis that might not come up during the observation period or interview. 
     
  • Map how he/she uses your business system and how that impacts the rest of the company. Understand both the “what” and the “why”. Without this, new employees may end up figuring out what they need to do, but never understand why they need to do it.

Optimize Your Manufacturing Today!

BPCS/LX Tip of the Week: How to Move From Good to Great - Manufacturing Optimization

Anthony Etzel 0 33970 Article rating: No rating
  • Are you tracking downtime? Is it done manually, or with some type of automation or application that gathers information in real-time, or is it based upon history?
  • If you are measuring team effectiveness by shift, you know there are significant differences between them. Have you figured out why?

One of our automotive customers was experiencing significant inefficiencies and difficulties with their receiving operations. After analyzing their operation, we discovered a disconnect between how they were tracking their incoming goods and what their ERP system thought was on hand.

This disconnect created time-consuming steps to process incoming material and determine where the material was needed. The manual process slowed production, caused additional staffing needs and hindered their ability to effectively get needed material to the assembly line. They chose to implement our data collection solution to automate the process.

Since implementing the solution, receiving and moving material was quicker, more accurate and efficient. This enabled the addition of another assembly line, increasing production volume – without adding staff.

Optimize Your Manufacturing Today!

RSS
First114115116117119121122123Last

Theme picker

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: What conditions must exist before changing an item's inventory unit?

Is there a procedure for changing an item’s inventory unit? What conditions must exist before it can be done?

Once inventory transactions (receipts or issues) have occurred for an item, the inventory unit cannot be changed. If only orders have been placed against the item (sales or purchase), the inventory unit can be changed if these orders are removed and the economic stock of the item is zero.

The reason that the inventory unit cannot be changed once transactions have been made is due to how transactions are recorded. The inventory transactions are recorded in units. These units are the inventory unit of the item. The inventory unit is not held in this table, however. The inventory unit is held on the item data. For example, if 5 pieces (pcs) of an item are issued and the inventory unit is later changed to pounds (lbs), there will be a mismatch in the inventory history of the item. In the past, the item was issued as pcs, and now the item master inventory unit is lbs. As the inventory unit is not date effective, the inventory has then been issued in two different units (pcs and lbs), but there is no method to recognize this difference.

Previous Article Infor LN & Baan Tip: Serialized Controlled Item >> to >> Non-Serialized Controlled item
Next Article Infor LN & Baan Tip: Considerations for Release to Warehousing for a Cost Item
Print
15621 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories