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

Infor LX/BPCS Tips & Tricks for EXECUTIVES:

George Moroses 0 17110 Article rating: 5.0

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.

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Security Manager

George Moroses 0 15783 Article rating: 5.0

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.

VJES (Visual Job Execution Software) for Infor LN & Baan

Kathy Barthelt 0 10547 Article rating: 5.0

​Every manufacturer relies on a few core metrics to manage operations: efficiency, productivity, capacity, and labor and equipment utilization. These benchmarks are used worldwide to assess performance and process effectiveness.

What if you could integrate quality control into every operation at every work center to ensure high-quality finished goods and simultaneously train high-quality operators? Manufacturing quality can be achieved using documented, repeatable, and measurable processes.

Introducing Crossroads RMC's ERP-independent solution, VJES (Visual Job Execution Software). VJES is an electronic work instruction interface that bridges engineering and the paperless manufacturing floor. VJES ensures that only one version of the work instructions is available—the correct one. By deploying up-to-date, visually rich work instructions, images, and videos, VJES provides personnel the best opportunity to build it right the first time and tracks worker productivity throughout the build process.

VJES achieves RESULTS:

  • Turn new hire welders into specialized welders in 2 weeks
  • Improve quality scores from 68/100 to 93/100 in 12 months
  • Reduce employee training time from 1 week to 3 days within the first month of use
  • Maintain a first-pass yield percentage of 100% for 8 consecutive months this year
  • Incorporate a quality cell after productivity increases due to the bandwidth gained from adopting VJES
     

Contact us to learn more, or Request a Demo today!

800.762.2077

Infor LN & Baan Tips & Tricks for FINANCE: Integration Transactions - Compression

Kathy Barthelt 0 22864 Article rating: 5.0

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.

Infor LX/BPCS Tips & Tricks for FINANCE: Default Billing Reason Code from User Order Class

George Moroses 0 16539 Article rating: 5.0

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.

Infor LN & Baan Tips & Tricks for OPERATIONS: Order Quantity Dependent Routings vs Default Routings

Kathy Barthelt 0 18506 Article rating: 5.0

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:

Infor LX/BPCS Tips & Tricks for OPERATIONS: Track all order holds added & released

George Moroses 0 14414 Article rating: 5.0

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.

First910111214161718Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Defining “Unavailability” in Infor LN

This topic describes the definition of temporary unavailability for resources in a calendar.

Use one of the following sessions:

  • Recurring unavailability
    For recurring unavailability, such as national holidays, define the recurrence in the Recurrences (tcccp0143m000) session. Add that recurrence to the applicable calendar and availability type in the Calendar Recurrences (tcccp0144m000) session, and clear the Available check box for the unavailable days.
    With calendar recurrences you define recurring exceptions in a calendar, and set a time schedule for daily, weekly, monthly, or yearly unavailable time in one action.
  • Unavailable days for all availability types
    To define occasional unavailability, such as a department trip, use the Calendar Non-Available Days (tcccp0119m000) session. What you define here applies to all availability types.
     
  • Unavailable days for a specific availability type
    To define unavailability for a single day, complete the following steps:
  1. Start the Calendar Working Hours (tcccp0120m000) session.
  2. Find the applicable calendar and availability type, and clear the Available check box for a working hours type on the relevant date.
  • Unavailable during a part of a day
    To indicate that part of a day is unavailable, use the Calendar Recurrences (tcccp0144m000) or the Calendar Working Hours (tcccp0120m000) session to specify the time intervals that are available. All other times are considered unavailable. You cannot directly specify an unavailable time interval.

If you defined unavailable dates in the Calendar Non-Available Days (tcccp0119m000) or the Calendar Recurrences (tcccp0144m000) session, in the Calendar Working Hours (tcccp0120m000) session, click Update Calendar.

Note:

  • Unavailability always applies to entire days. If the Calendar Working Hours (tcccp0120m000) session contains multiple time intervals for a single date, and the Available check box is cleared for some intervals and selected for other intervals on the same day, the entire day is unavailable.
  • A calendar recurrence that makes a day unavailable has no effect on the availability of that day in the parent calendar.


It is not useful to define a special availability type for unavailability, because Infor LN does not maintain and update the working hours and the capacity data of a calendar in the Calendar Working Hours (tcccp0120m000) session based on non-available availability types.

Previous Article Infor LN & Baan Tip: Porting Set Issues
Next Article Infor ERP Tip of the Week: 5 Steps to Managing Sales Tax
Print
28300 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories