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
6721 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

Did you know that you can set up one-time vendors in LX? One Time Vendor (1,A): Specify Y to indicate that this vendor is a one-time vendor. Otherwise, could you specify N. The system removes a one-time vendor's information from the Vendor Master file after all transactions are reconciled. If this vendor already exists as a one-time vendor, you can specify N to change the vendor to a regular vendor.

Determining whether to use Master Production Schedule (MPS) planning or Material Requirements Planning (MRP) planning for items in Infor LX and BPCS involves understanding the nature of the items and their demand characteristics.

Master Scheduled Items typically encompass finished goods or service items. These items receive their requirements either from Independent demand, Dependent demand, or a combination of both...

12345678910Last

Theme picker

Tips: LN | Baan

How do I assign an unallocated payment to a purchase invoice when the document dates are not the same?

When trying to assign an unallocated payment, it is possible that the purchase invoice is not displayed in session Assign Unallocated / Advance Payments to Invoices (tfcmg2106s000), even though it is showing in the open entries. This can happen when the document date of the unallocated payment lies before the document date of the purchase invoice you want to assign it to. There are 2 ways to handle this...

You may be wondering if it's necessary to have separate item codes for incoming and outgoing subassemblies.

No, it is not necessary to have separate item codes for incoming and outgoing subassemblies, but it is recommended. In theory, you could have only one item code with the description subassembly and use the same item code for the outgoing subassembly and for the incoming subassembly. However, when monitoring inventory movements and financial integration transactions, it will be difficult to understand the process. Also, the costing logic is much clearer when different item codes for the incoming and outgoing subassemblies are used. Because of this, it is advised to use a different item code for the outgoing subassembly and a different item code for the incoming subassembly.

First7891012141516Last

Theme picker

Categories