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
33265 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

This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

Enhancement: Order Hold Audit Functionality

This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

First34568101112Last

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:

123456810Last

Theme picker

Categories