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

BPCS/LX Tip of the Week: Shop Order Release Date

Anthony Etzel 0 37351 Article rating: No rating

The shop order release date is the date that the shop order is scheduled to be released for production.

If you want to use the backward schedule method, make sure the release date is blank and the due date is maintained.

If you maintain the quantity on the shop order and the due date is prior to the system date, the due date and the release date are the same.

Baan/LN Tip of the Week: Plan Codes

Kathy Barthelt 0 41585 Article rating: No rating

In Baan IV, plan items exist within the context of a plan code. A plan code includes only items of the MPS Item item type. Planned orders are independent of a plan code. Users can compare plan codes by means of the Plan Code Performance Comparison (cprmp4504m000) session.

The scenario concept in Infor LN replaces the plan code concept in Baan IV.

In Infor LN, the basic data for plan items is the same for all scenarios. However, users maintain not only the master plan within a scenario, but the planned orders as well.

For example, for each scenario, Users can specify:

  • Special demand for an item.
  • The availability of resources (in the Scenario – Availabilities (cprpd4160m000) session).
  • The sourcing strategies and supply strategies.

Users can compare scenarios by means of the Performance Indicators (cprao2201s000) session.

RSS
First135136137138140142143144Last

Theme picker

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

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
19359 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories