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: Infor LN & Baan Tips

Infor LN & Baan Tip of the Week: Customer requested delivery date

The “Use Customer Requested Delivery Date” parameter has been introduced in the Sales Order Parameter (tdsls0100s400) session, which is used to track the customer’s requested delivery date.

If this parameter check box is selected, various additional date fields become available to track the customer Initial Requested Delivery Date and the Original Promised Planned Delivery Date.

Previous Article Infor LX & BPCS Tip of the Week: ION Tip – Pausing Receiving and Sending of Messages
Next Article Analytics Dashboard: How To Save Time, Effort AND Money
Print
42033 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

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error.

To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Optimize Your Manufacturing Today!

Seems obvious – you want real time data and you want it to be accurate. Do you have the systems in place to allow for this?

Here are 4 reasons you need a data collection system:

  1. See the differences between actuals and standards
  2. Determine the source of project overruns
  3. Prevent mis-shipments to customers
  4. Avoid unnecessary reordering of parts

An automated data collection system will analyze your current data, allowing you to efficiently optimize your manufacturing and the benefits will be huge and far reaching.

Optimize Your Manufacturing Today!

First8788899092949596Last

Theme picker

Categories