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

George Moroses
/ Categories: Infor LX & BPCS Tips, IDF

LX & BPCS Tip: Unlocking Efficiency and Customization: The Power of Infor Development Framework (IDF)

The Infor Development Framework (IDF) is a significant component of Infor's efforts to modernize its Infor LX application. IDF aims to enhance the user experience by introducing a task-oriented approach to accessing information within Infor LX. It is designed to replace LX Inquiry screens. Here are some key points about IDF:

  1. Efficient Interaction: IDF re-architects the way users interact with Infor LX, making it more efficient and user-friendly.

  2. Configurability: Users can configure their view of application data without making modifications to the core application. This preserves the core application's supportability and reduces the risk of introducing errors.

  3. Centralized Data Management: IDF can serve as a centralized management utility for all data, both within and outside the IBMi environment.

Examples of how users can benefit from IDF include:

  • Grouping and Sequencing: Users can arrange application information into multiple groupings and sequences that align with their specific job requirements.

  • Information Hiding: Unnecessary information can be hidden to declutter the interface and focus on the task at hand.

  • Record Filtering: Users can filter records to display only the information relevant to their current job or task, improving productivity.

  • Customization: IDF allows for customization at various levels, including individual user preferences, group-specific settings, or changes that apply to all users.

Additionally, the latest version of IDF includes file maintenance functions, which can be used for tasks such as managing the Item master file.

For more information on how Infor's IDF can benefit your company, you are encouraged to reach out to Anthony Etzel for detailed insights and assistance.

Previous Article Are you ready to maximize the benefits of Infor ERP System?
Next Article LN & Baan Tip: Unlocking Efficiency: Embrace Cycle Counting for Smoother Inventory Management
Print
12884 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

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

Baan/LN Tip: New Mapping Scheme

After a new mapping scheme is copied from an existing one, it is possible to check transactions in a simulation mode, before activating the new scheme. However, before the simulation can take place, the new mapping scheme needs to have completed the “Check Mapping Scheme” step. When the check is completed, a transaction can be simulated by highlighting it and from the Specific menu, selecting “Map with Specific Mapping Scheme.” Any errors can be corrected without having to activate the new mapping scheme.

This has come up as an issue during various stages of warehouse material movements – transfers, outbounds, shipments. We have seen it right up to 10.4. The inventory structure table (whinr150) becomes a problem. The error points to that table, but users are lost as to how to fix it.

In the session Units by Unit Set many companies let the field Storage default to Yes. If the UOM is not intended to be used in inventory then that setting should be No. 

If an item is purchased in UOM different from the inventory unit and the setting is Yes then LN adds a record in that UOM to the inventory structure table. It is that record that causes problem later.

The session has an option to change the value of the storage field. Specific > Convert Use for Storage. This option works both ways and will correct all inventory in the UOM range. 

Should a user receive an error that references inventory structure table then the solution is to check that session to see if an odd UOM exists in it. If so use the Convert Use for Storage to correct the problem.

First7374757678808182Last

Theme picker

Categories