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

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

  • 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!

Previous Article BPCS/LX Tip of the Week: How to Move From Good to Great - Manufacturing Optimization
Next Article Tip of the Week: Ways to Manage the Pain of Losing a Key Employee Before it Ever Happens
Print
37247 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

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

I know a lot of our customers are considering virtualization projects. I came across this, and thought it might be useful:

The advantages of virtualization include the following:

• You get more out of your existing resources. Pool common infrastructure resources and break the legacy “one application to one server” model with server consolidation.

• You can reduce datacenter costs by reducing your physical infrastructure and improving your server to admin ratio. Fewer servers and related IT hardware means reduced real estate and reduced power and cooling requirements. With better management tools, you can improve your server to admin ratio so personnel requirements are reduced.

• You can increase the availability of hardware and applications for improved business continuity.

• Securely back up and migrate entire virtual environments with no service interruptions. Eliminate planned downtime and recover immediately from unplanned issues.

 

• Gain operational flexibility. Respond to market changes with dynamic resource management, faster server provisioning, and improved application deployment.

The disadvantages of virtualization include the following:

• Virtualization adds overhead to the CPU, memory, IO, and network.

• Virtualization adds an additional layer to the hardware and software stack. Therefore, additional complexity is introduced in the following circumstances:

  • When sizing the physical server.
  • When planning VM capacity.
  • When planning multiple VMs on the same physical server.
  • When investigating performance issues.

 

You can set up interest invoicing in Accounts Receivable and in the General Ledger.

To set up interest invoicing, use these sessions:

Invoice-to Business Partner (tccom4112s000)
For invoice-to business partners for which you want to raise interest invoices, select the Charge Interest checkbox.

Mapping Scheme (tfgld4573m000)
Use this session to define the mapping of the Interest Invoice / Revenues Analysis integration document type.

Interest Percentages (tfacr5102m000)
Use this session to define the interest percentages for each financial business-partner group, and for different periods of days.

Interest Invoice Related Data (tfacr5101s000)
Use this session to define whether interest must be calculated on unpaid invoices, partly paid invoices, interest invoices, and/or fully paid invoices. You can also indicate that LN must take advance payments, unallocated payments, and credit notes into account for the generation of interest invoices.

Optionally, set conditions
Example: LN only generates an interest invoice advice entry if these conditions are met: The total of all advice entries in one currency is higher than the allowed minimum amount of an interest invoice defined in the Minimum Amount for Interest Invoice field.

The invoice is overdue for a greater number of days than the number of days defined in the Minimum Days for Interest Invoice field.

First96979899101103104105Last

Theme picker

Categories