Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Support, Training & Workshops

Infor LN & Baan Tip: Important Porting Set Announcement (all versions of LN & Baan)

There has been a recent porting set change due to Infor’s Product Life Cycle Policy.  

How to determine the maintenance stage of an Infor LN product version and release

Before a customer starts deploying Porting Set 9.4a or a later release, they must determine the actual maintenance stage of their Baan / Infor LN product. The definition of the maintenance stages for the product versions and releases of all versions of Baan and Infor LN are outlined in the Product Support schedule as published in the PLC policy. The maintenance stage of the ERP version is either “Mainstream Maintenance”, “Extended Maintenance” or “Sustaining Maintenance”.

How to manage Porting Set updates

The following conditions apply to customers who intend to upgrade to Porting Set 9.4a or later Porting Set releases:

  • For customers with a product version in Mainstream Maintenance, there will be no difference with regards to Porting Set updates. They can install Porting Set 9.4a or any newer release.
  • Customers with a product version in Extended Maintenance will be able to use Porting Set 9.4a only under the condition that they acquire an Extended Maintenance license and have applied the corresponding validated license key to their SLM License server. This key is a Server license type.
  • Customers with a product version in Extended Maintenance who have not acquired an Extended Maintenance license will not be able to use Porting Set 9.4a or any newer version. The latest Porting Set for these customers that can be installed and used is 9.3j which was released in April 2021.
  • Customers with a product version in Sustaining Maintenance will not be able to use Porting Set 9.4a or any newer version. The latest Porting Set for these customers is 9.3j which was released in April 2021. Customers who are not entitled to upgrade to Porting Set 9.4a can use any Porting Set release prior to Porting Set 9.4a. These continue to be available through the Infor Support Portal.

You can find more information in KB 1946498 General: Infor LN and Baan Product Lifecycle Policy and KB 2204515, or you may contact Crossroads RMC for assistance in determining whether or not you are able to upgrade your porting set.

800.762.2077

Previous Article Are You Running Your IT Department, or is IT Running You?
Next Article Infor LX & BPCS Tip: Customer Tax Exempt Declarations, SYS160D1
Print
26350 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

Read more

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.
Read more

In LN, you can differentiate between items at various suppliers:

  • Locations (warehouses),
  • Purpose (planning, purchase)
  • Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:
 
  • Items - Planning (cprpd1100m000)
  • Check Item Data by Warehouse (whwmd2210m000)
  • Item Supplier Plan (cpvmi0530m000)
These sessions define entities that have an n-to-1 relationship with the general item data.

 

Read more
First153154155156158160161162Last

Theme picker

Categories