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: Latest Porting Set – All Versions of Infor LN & Baan

Are you on the latest porting set for your version of Baan / Infor LN? Check here to be sure:

VERSIONS: Infor LN, Infor Baan ERP 5.0c, Infor Baan IVc4

LAST MODIFIED ON:
13th Jan, 2021: Updated with 9.3i porting set, see KB 2176336 for this version. Available from LN CE release 2021.01
9th Oct, 2020: Updated with 9.3h porting set, see KB 2158949 for this version. Available from LN CE release 2020.10
9th July, 2020: Updated with 9.3g porting set, see KB 2142625 for this version. Available from LN CE release 2020.07
10th April, 2020: Updated with 9.3f porting set, see KB 2125567 for this version. Available from LN CE release 2020.04
13th Jan, 2020: Updated with 9.3e porting set, see KB 2108810 for this version
11th Oct, 2019: Updated with 9.3d porting set, see KB 2093165 for this version
11th July, 2019: Updated with 9.3c porting set, see KB 2075437 for this version
13th March, 2019: Updated with 9.3b porting set, see KB 2051365 for this version
7th Dec, 2018: Updated with 9.3a porting set, see KB 2033165 for this version
6th Sept, 2018: Updated with 9.2b.01 porting set, see KB 2014729 for this version
8th June, 2018: Updated with 9.2b porting set, see KB 1997100 for this version
12th March, 2018: Updated with 9.2a.01 porting set, see KB 1972861 for this version
11th Dec, 2017: Updated with 9.2a porting set, see KB 1954406 for this version
8th Sept, 2017: Updated with 9.1c.01 porting set, see KB 1934704 for this version
10th June, 2017: Updated with 9.1c porting set, see KB 1915968 for this version
20th March, 2017: Updated with 9.1b.01 porting set, see KB 1897691 for this version
9th Dec, 2016: Updated with 9.1b porting set, see KB 1876613 for this version
22nd Sept, 2016: Updated with 9.1a.01 porting set, see KB 1856545 for this version
23rd June, 2016: Updated with 9.1a porting set, see KB 1836486 for this version
14th March, 2016: Updated with 9.0c.01 porting set, see KB 1700568 for this version
11th Dec, 2015: Updated with 9.0c porting set, see KB 1677286 for this version
17th Sept, 2015: Updated with 9.0b.01 porting set, see KB 1654371 for this version
19th June, 2015: Updated with 9.0b porting set, see KB 1630218 for this version
20th March, 2015: Updated with 9.0a.01 porting set, see KB 1605781 for this version
9th Jan, 2015: Updated with 8.9a.06 porting set, see KB 1586121 for this version, this is only 32 bit for windows and linux.
17th Nov, 2014: Updated with 9.0a porting set, see KB 1572748 for this version, 12 Dec 2014, new version for windows released.
26th Sept, 2014: Updated with 8.9a.05 porting set, see KB 1539050 for this version
11th July, 2014: Updated with 8.9a.04 porting set, see KB 1517147 for this version
5th April, 2014: Updated with 8.9a.03 porting set, see KB 1490061 for this version
10th Jan, 2014: Updated with 8.9a.02 porting set, see KB 1465391 for this version
4th Oct, 2013: Updated with 8.9a.01 porting set, see KB 1442188 for this version
19th July, 2013: Updated with 8.9a porting set, see KB 1422389 for this version
1st March, 2013: Updated with 8.8a.03 porting set, see KB 1381629 for this version
30th Nov, 2012: Updated with 8.8a.02 porting set, see KB 1356958 for this version
13th Sept, 2012: Updated with 8.8a.01 porting set, see KB 1181506 for this version
30th May, 2012: Updated with 8.8a porting set, see KB 1154144 for this version
19th Jan, 2012: Updated with 8.7b.01 porting set, see solution 1120445 for this version. This is the first version that can also be used for Infor BaanIV c
7th Oct, 2011: Updated with 8.7a.03 porting set, see solution 1062346 for this version
17th June, 2011: Updated with 8.7a.02 porting set, see solution 1025539 for this version
31st March, 2011: Updated with 8.7a.01 porting set, see solution 1007520 for this version
17th Jan, 2011: Updated with new version of 8.7a porting set
3rd Dec, 2010: Updated with 8.7a porting set, see solution 22945526 for this version
8th Oct, 2010: Updated with 8.6a.03 porting set, see solution 22899106 for this version
17th June, 2010: Updated with 8.6a.02 porting set, see solution 22899105 for this version
1st April, 2010: Updated with 8.6a.01 porting set, see solution 22899104 for this version
11th February, 2010: Updated with the 64-bit 8.6a porting set, see solution 22899103 for this version
1st Dec, 2009: Updated with new 8.6a porting set, see solution 22899103 for this version
1st Oct, 2009: Updated with new 8.5a.03 porting set, see solution 22899102 for this version
18th June, 2009: Updated with new 8.5a.02 porting set, see solution 22899101 for this version
19th March, 2009: Updated with new 8.5a.01 porting set, see solution 22899100 for this version
4th Dec, 2008: Updated with new 8.5a porting set, see solution 22899099 for this version
23th Oct, 2008: Updated with new 8.4c.02 porting set, see solution 22899098 for this version
23th July, 2008: Updated with new 8.4c.01 porting set, see solution 22899097 for this version
2nd July, 2008: Updated with new 8.4c porting set, see solution 22899096 for this version
13th March, 2008: Updated with new 8.4b porting set, see solution 22899095 for this version
24th Jan, 2008: Updated with new 8.4a.02 porting set, see solution 22899094 for this version
21st Dec, 2007: Updated with new 8.4a.01 porting set for Windows, see solution 22899093 for this version
31st Aug, 2007: Updated with new 8.4a.01 porting set, see solution 22899093 for this version
25th June, 2007: Updated with new 8.4a porting set, see solution 22899115 for this version
4th Jan, 2007: Updated with new 8.3a.01 porting set, see solution 22899114 for this version
20th Oct, 2006: Updated with new 8.3a porting set, see solution 22899113 for this version
23th Aug, 2006: Updated with new 8.2b porting set for windows, see solution 22899112 for this version
16th June, 2006: Updated with Porting set 8.2b: see solution 22899112 for this version
28th April, 2006: Updated with Porting set 7.6b_01: see solution 22899111 for this version
9th March, new version of 7.6b Porting set released, see solution below,(22899110)
6th Dec, 2005: Updated with Porting set 7.6b: see solution 22899110 for this version
15th June, 2005: Updated with Porting set 7.6a.02: see solution 22899109 for this version
27th April, 2005: Updated with Porting set 7.6a.01: see solution 22899108 for this version
4th Dec, 2004: Updated with Porting set 7.6a: see solution 22899107 for this version


SITUATION DESCRIPTION:
A porting set is a set of binaries, which are operating system dependent. It is the layer between the operating system and the application software. Infor regularly releases a new porting set. A bugfix number recognizes every modification made in the porting set.

Previous Article Infor LX & BPCS Tip: Special Functions
Next Article And Then There Were None - Short Staffed?
Print
29686 Rate this article:
4.5
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

EGLi provides Infor LX Configurable Enterprise Accounting (CEA) functionality including Advanced Transaction Processing (ATP), a configurable ledger, and batch transaction processing in the IDF architecture.

EGLi is a complete replacement for CEA. Infor LX applications integrate with EGLi, and subsystem transactions generated in Infor LX are used to create journal entries in EGLi. The Infor LX integration system parameters allow you to specify whether CEA or EGLi is your primary financial product.

We recommend that you select CEA while you test the integration. The primary financial product flag and the CEA migration programs are designed to assist existing CEA clients with their implementation of EGLi. Journals are produced in both GL systems so you can verify that the data in both GL systems are the same. This integration includes migration programs that copy your existing CEA files to corresponding EGLi files. After you run the migration programs, EGLi should be configured and ready to use. If you are already running IDF via Ming.le or SiW, before you install EGLi, you will need to see the Ming.le integration guide for instructions on how to export EGLi tasks from IDF to SiW/Ming.le.

Learn More > Infor LX Integration Guide for Enterprise General Ledger

Read more
  • Control Date Lead Times – LX provides five separate Control Date Lead Time fields so you can specify additional lead time values for Shop Orders, Purchase Orders and Planned and Firm Planned orders. Each Control Lead Time Date represents additional time (days) required at each step in the process that needs more time (Quarantine, Stabilize), that is to say, when a component is due, and when it can be used. (working with an aerospace  precision bearing manufacturer, I had to account for the QA requirement that no measurements could be taken until the parts had been “soaked” (stored) in an atmospheric controlled environment (72 degrees, and controlled humidity) for 24 hours. This requirement added one full day of lead time between each machining operation) The MPS/MRP Generation program, as well as programs that Shop Order Material Allocation records use the five control date lead times to adjust component required dates to function in the same way as the BOM Offset Lead Time.
     
  • All programs that create MRP Planned Orders, MRP Firm Planned Orders, Shop Orders, and Purchase Orders call the Control Date Calculation program (MRP515B) to establish all five control dates. A Control Lead Time Date is used to adjust the component Required Dates data in the Material Requirements file (KMR), based on planned orders for a parent, and the FMA Required Dates data, based on shop order release dates for a parent.
Read more
First5859606163656667Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

Read more
12345678910Last

Theme picker

Categories