Get ahead of the curve with a seamless, comprehensive integration strategy that surpasses other competitive solutions. In part two of this webinar, join our discussion of best practice integration tricks and solutions from a fellow customer’s office of finance. Understand what makes their integration approach effective and review best practices in integrating your IBM i solution to other office of finance solutions (F9/EPM/Birst/GRC).

Hosted by Peg Tuttle from the IBM i podcast, “The Incredible i Show”. 

• How version upgrades have tightened internal control loopholes.
• Structural IBM i advancements designed to safeguard your organization.
• IBM i ecosystem solutions that strengthen both data and access vulnerabilities.

Don't miss this fourth fireside chat, Eight Ways to Modernize your IBM i product – Topic #3 of 8: Best practices in integration for the office of finance (Part 2). Register today!

Register today!

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.

In Baan IVC, plan items on the lowest plan level were automatically actual items (not product families). All plan items on higher plan levels were product families.

The relationship between a product family and items on lower plan levels was defined in a planning bill of material.

In Infor LN, every family item must be defined in the Item Base Data module. A family item can exist on any plan level. The relationship between a family item and items on lower plan levels is defined in aggregation relationships.

Aggregation relationships in Infor LN are much more flexible than the planning bills of material in Baan IV. For example, users can define aggregation relationships between items on the same plan level.

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

• Master Production Scheduling
• Material Requirements Planning
• Capacity Requirements Planning (All three combined in a single planning module for Baan V and LN)
• Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.