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 of the Week: Dynamic Assembly Control BOM (LN 10.7)

In previous releases of LN, the Assembly Control Bill of Material (BOM) offered limited flexibility. For each end item configuration, users were required to create unique Engineering Modules, which are used to determine the assembly parts that are consumed in a specific Line Station during a specific operation.

If LN is integrated with Design Studio, previously called Infor CPQ, BOM structures can be maintained in Design Studio for Assembly Control. These structures can include non-configurable parts that are directly linked to configurable items. When communicating these structures to LN using the Assembly Control, Product Variant Structure (tiapl3510m000) session, the structures were rejected because non-configurable parts were not supported by the session logic.

In this release, BOM structures that include non-configurable parts can now be accepted in LN. Consequently, if LN is integrated with Design Studio, it is no longer required to use the Engineering Module. Using the Engineering Module has become optional.

Previous Article Infor LX & BPCS Tip of the Week: Multi-Level Backflush (LX 8.4)
Next Article Tip of the Week: 8 Ways to Improve Production Efficiency in Your Manufacturing Plant
Print
52903 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

The Customer Tax Exemption Maintenance program, SYS160, allows you to specify customer declarations used by the Customer Order Entry (ORD) and Billing (BIL) applications to apply a tax rate code to specific order lines of an invoice.

With this program, Infor LX can invoice customers without value-added tax (VAT) if one of the following conditions occurs:

  • The cumulated...

Don’t laugh! I know, I know…many of our customers say that after 7-10 years they are finally settling in after the implementation! We have seen many a customer stretch out the lifespan of their ERP system to 20+ years. That sounds great for the company’s bank account, but is it good for the business?

An outdated ERP system hurts your business in many ways, not just with slow performance. The best-of-breed functionality is now 2 decades old, and obsolete technology can't leverage newer technology. Lack of integration leads to siloed data that hurts communication and your internal teams feel the pain, and your customers are noticing. Poor visibility into your operations makes it nearly impossible to achieve industry-based regulatory compliance and meet financial auditing requirements. Not to mention the sheer size of Big Data that is being collected today vs. 2 decades ago or the fact that your vendor is no longer supporting your ERP version.

Let’s scrap it all and start over!...

First3031323335373839Last

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:

12345678910Last

Theme picker

Categories