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

Kathy Barthelt

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
26382 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

In the Item Master File, the requirements code is used to specify the type of demand for the item. Planned order requirements are determined from the type of demand. If the requirements code is left blank, the planning systems treat the item as a sum code (3).
 

Other options for the field are:


1 = Dependent demand that is indirectly generated from the parent item requirements.

2 = Independent demand generated from customer orders and forecasts.

3 = The Sum of both independent and dependent demand.

In SFC600, there is no code to capture the time spent on re-work. Re-work is usually at a specific operation, or when the part is finished and QC determines that re-work is required in order to pass inspection. You are faced with deciding on how to report the additional labor time.

Do you continue to report it against the operation, or create a re-work shop order?

If you are re-working through a specific operation you can capture the time as run labor with the SFC600 program. Now you need to deal with the variance of actual to standard time and what impact this has on costing.
First144145146147149151152153Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories