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

FINANCE: Default Billing Reason Code from User Order Class
This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

TECHNOLOGY:  Security Manager
New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves, but are only allowed to access regular LX programs if granted authority by an LX security officer.

OPERATIONS: Track all order holds added & released
Enhancement: Order Hold Audit Functionality
This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves but are only allowed to access regular LX programs if granted authority by an LX security officer.

First2345791011Last

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.

123457910Last

Theme picker

Categories