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 What are the differences between INV810 and INV015 for Cycle Counting updates?

INV810 only deletes the sequence number from the ILI of the item so it is not selected again for counting and does not delete the ICY record.

The ICY Cycle Count sequential history file increases in size with each new cycle count session. Running INV015 will purge all the old ICY records up to the date entered on the set-up screen ‘Enter Cycle Count Ending Date’ field. Physically deleting the old ICY files.

In most cases, when you complete the cycle count posting and run the reports, you can reconcile the data as required. After you reconcile the data for a specific day (or group of days), you can run INV015 to purge the data for that day (or group of days).

Previous Article Infor LN & Baan Tip: When is backflushing disabled in LN?
Next Article Infor LN & Baan Year-End Processing Checklist for Period and Fiscal Year Closure
Print
11784 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:

1345678910Last

Theme picker

Categories