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: Event / News, Consulting

Factors to considered when undertaking an ERP implementation or upgrade

Things to consider when choosing your ERP Implementation Partner:

ERP Partner Value Add

  • Proven track record
  • References
  • Focused on-time / on budget
  • Strategic partnership with Infor
  • Knowledge of extension products that are available for your ERP
  • Post-implementation – What does the partner bring to the table once the project is complete?

Project Management

  • Does your assigned project manager fit your needs?
  • Past project management experience with the same ERP
  • Project Management methodology
  • Project Plan development and style
  • Does the PM develop a realistic plan with clear objectives, timeline and responsibilities?

 
Consulting Team Selection​

Need help figuring out if your organization is properly positioned for an implementation or upgrade?
Contact Kathy Barthelt today. We can help to ensure that your organization is positioned for success.

  • Does my ERP Implementation partner have the team to support my project?
  • Resume review
  • Interview all candidates
  • Working knowledge of ERP system/version
  • Communication skills
  • Geographic location
  • Relative industry experience
  • Technical Viewpoint
  • Understanding of any enhancements made to your system and what the best approach to streamlining for future releases. Knowing the tools available to accomplish this task.
Previous Article LN & Baan Tip of the Week: Inventory In Transit Report – 10.7
Next Article Johnson Crushers Selects Crossroads RMC for LN 10.6 Data Collection
Print
32327 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Automatically synchronize security changes from LX to IDF, replacing CPYSECIDF. This new process synchronizes users in IDF with those in core LX security whenever a user’s security settings are changed. When a user is deleted from an LX environment, they can also be automatically removed from the IDF environment. Changes to a user’s access to programs in LX are mirrored in IDF. Access to Companies, Facilities, and Warehouses are also synchronized. Additionally, when Business Roles or Business Units access is changed, all users assigned to those roles or units are updated in IDF security.

In the Shop Order Selection program, action 3=Copy is available. This action allows copying any shop order except for flow orders or campaign orders. Instead of copying from the parent item's bill of material and routing, the new shop order’s materials and operations will be copied from the selected shop order. Note that if the existing shop order is linked to a customer order or line, this linkage will not be copied to the new shop order.

First567810121314Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

1234567810Last

Theme picker

Categories