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

George Moroses
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip of the Week: Purge optional during Month/Period End - LX 8.4

For various month/period end programs, the purge function is now optional.

Scope:

INV903, Inventory Month End Close, optionally purges both inventory records as well as customer invoices. Some applications already have a flag or option for purging (for example, ACP900) and other applications are stand-alone. If you do not want to purge, do not run these programs: Order Purge and Close, ORD900, Close Quotes, ORD930, and Delete RMAs, ORD935. Now there are options on whether to purge records during the month end or period end programs.

The Benefits include:

• Flag or option added to allow the user to decide whether to perform month-end function with or without purge.

• Allows for month-end processing without purge.

• Improves efficiency of month-end processing.

Impact:

This enhancement includes these programs or areas:

• INV903, Inventory Month End Close

• ACR900, A/R Period Close

• CST900, PRF900, SFC900 Shop Order Close

• PUR900, Purchasing Month End Close
Previous Article Johnson Crushers Selects Crossroads RMC for LN 10.6 Data Collection
Next Article Why should you upgrade to LX 8.4.x?
Print
33363 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

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:

1345678910Last

Theme picker

Categories