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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Multi-level Shop Order Release Due Dates

Previously, Material Requirements Planning (MRP) preferred practices meant that the component’s due date was the same as the parent’s shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The user is now able change how the due date is determined for multi-level shop orders. If the Due Date of Children parameter is set to 1=Yes, the due date of the child components is the same as the release date of the parent. If the parameter is set to 0=No, the due date is the day before the release date of the parent.

Optimize Your Manufacturing Today!

Previous Article Baan/LN Tip of the Week: How is Your Productivity?
Next Article Demand-Driven Manufacturing Metrics that Drive Action - White Paper
Print
25274 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

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

In LN, a supplier's reliability is no longer based only on correct deliveries. The vendor rating functionality of LN is based on various objective criteria and subjective criteria that can be used to calculate the vendor’s rating.

 

The set up procedure for analyzing suppliers has changed completely compared to Baan IV.  To execute the vendor rating process, users must update the vendor ratings in the Update Vendor Rating (tdpur8850m000) session.

If users update the vendor ratings, the following stages exist in the update vendor rating procedure:


1. Calculate actual weightings

2. Calculate ratings for objective criteria

3. Calculate ratings for subjective criteria

4. Update overall vendor rating

In Baan IV, this session is called Release Commissions/Rebates to Invoicing (tdcms2201m000) and is used to set the status of the commissions/rebates to Reserved, or Closed. In Infor LN, this session is only used to set the status to  Closed. Users can reserve commissions/rebates in the Reservation and Approval of Reserved Commissions/Rebates (tdcms2202m000) session. In addition, the following fields are added to the Release Commissions/Rebates to Invoicing (tdcms2201m000) session:

▪ Commissions to Accounts Payable

▪ Rebates to Central Invoicing

First136137138139141143144145Last

Theme picker

Categories