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: ERP News, Event / News, IDF

Steps to undo an IDF modification and restore to the default

Changes are great, but if you want to undo an IDF modification and restore to the default, you need to follow these steps:

Reset to an Infor shipped view (“un-modify” it)

  1. Open the public node of an object you would like to reset to the shipped status. Notice that all of the standard views (i.e., those owned by Infor) are unmodified.
  2. Select the row with the Modified column = yes
  3. Select the Reset to default button on the toolbar
  4. Say Yes to the prompt
  5. The object is now back to the way it was shipped by Infor. Note that it now shows that it has not been modified. If you display the editor, you will see that the attribute you deleted has been restored. Note that only objects owned by Infor can be reset. If you change a standard definition, and later regret it, you can use this feature to restore it with a couple of clicks.
Previous Article How to Improve Customer Shipments With OTTO - A Case Study
Next Article Tax Law Changes by the Numbers - Infor LX & BPCS Integration to Avalara
Print
30886 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

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

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.

In Baan IV Purchase Control, the purchase inquiry procedure enables the user to:

  • Request a specific supplier to submit a quotation on the purchase inquiry for the delivery of an item.
  • Compare the prices and discounts of the quotations that are submitted by different suppliers.
  • Copy the inquiry data to a purchase order.


In LN, you can:

  • Request multiple business partners to submit a quotation on a specific request-for-quotation for the delivery of an item.
  • Compare the received quotations based on the following criteria:
  1. Price
  2. Quantity
  3. Vendor rating
  4. Delivery dates
  5. RFQ subjective criteria
  • Copy the quotation data to a purchase order, a purchase contract, or a price book.
First132133134135137139140141Last

Theme picker

Categories