Bring New Life to Your ERP System

Did you implement your ERP system 5 or 20 years ago? Back then, it was like a brand-new car—sleek, fast, and efficient. It may have needed minor adjustments, but you were very pleased. Fast forward to today, does it still have that new car smell? Does it run as efficiently as it used to?

While ERP systems are designed to last, your business evolves. Customer needs change, employees come and go, and you are left with a system that may run “fine” but lacks its original spark.

GOOD NEWS: You can restore that “new car smell” with a utilization, or business process review.

What is a Utilization or Business Process Review?

Our consultants review your Infor ERP system's current usage and related business processes to make recommendations that reinvigorate your system and its users.

Does My Organization Need One?

While every company could benefit, it's especially worthwhile if you have a specific problem to solve or a goal to achieve.

Financial Benefits Include:
Technology Benefits Include:

We are excited to invite you to the Infor user group inPower event this September 23-26, 2024.

As a Gold Sponsor, Crossroads RMC is proud to support this premier event. Here are some reasons you should attend:

• Networking: Connect with peers and industry experts.
• Product Updates: Discover the latest features and future roadmaps.
• Training: Participate in hands-on workshops and expert-led sessions.
• Problem Solving: Learn from other users’ success stories.
• Influence: Provide feedback to Infor’s product development teams.
• ROI: Gain insights on maximizing your Infor investments.
• Community: Engage with special interest groups and regional user communities.

This event is a great opportunity to enhance your knowledge, solve challenges, and optimize your use of Infor solutions. Don't miss out!

What's in it for me?

inPower has something for everyone!

Technology:
Operations:
Finance:
Executives:

Infor and IBM  i - An Aligned Strategy for the Future

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.

Compression

Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

• The source financial company.
• The destination financial company.
• The transaction type and series.
• The ledger account and dimensions.
• The transaction currency.
• The fiscal year and the financial period, the tax period, and the reporting period.
• The integration document type and the Debit/Credit indicator.
• If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

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.

Order quantity-dependent routings

An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings: