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
39195 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

If it is necessary to pause sending and receiving of BOD messages on your IBM i during your month end process, it is best practice for the document flows that point to the IBM i to guarantee delivery of BOD messages. Once the month end process has been completed, you will need to Resume the ‘Receiving’ and ‘Sending’ Active Connection Points so your documents will continue to process.

Pausing Sending messages

To pause sending messages to ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be paused for sending messages.
  3. In the Sending Paused column, click Pause. The page is automatically refreshed and the Sending Paused checkbox is selected. A Resume button becomes available. 

Sending of messages by this connection point is stopped....

The database in LX 8.4 has undergone a significant change from previous versions. The database has been created using SQL DDL language instead of the old DDS language. The newer format allows for LX to take better advantage of advances in IBM database technologies as they move forward. Additionally, LX will be better able to make changes to tables (aka files) in the future without causing very large MR explosions to replace all programs that use a specific table. To ease the impact of this significant change, the LX tables (aka physical files) have new names that are the same as the previous version file names but with a “P” at the end, for example IIM is now IIMP. The old file names now belong to SQL views that looks just like the tables. This change made it easier to upgrade all the LX programs without changing every reference to every file. Many of the logical files remain although some have been replaced by SQL indexes to improve performance.

First6465666769717273Last

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