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

Baan & LN Integration News: Playing Telephone Can Get You In Trouble

Somehow information must be relayed from one person to another, and the “connection” (as it turns out) is pretty manual, and error prone.

How about moving into the 21st century and eliminate the manual effort. How about automating your integrations? Learn About Crossroads RMC Consulting

We have tied Baan and Infor LN to:

  • Warranty systems
  • CRM systems
  • Web portals
  • Automated batch picking systems, and so much more!

Contact us to find out how we can automate the communication between your systems, so you don’t have to worry about what got lost in translation.

Previous Article Baan/LN Tip: New Mapping Scheme
Next Article BPCS/LX Tip of the Week: Shelf Life Days and Retest Days
Print
27798 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

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:

123457910Last

Theme picker

Categories