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: Automated Approach to Your Cash Application Process with ARP

Advanced Remittance Processing, ARP, provides an automated approach to your cash application process. ARP works together with Accounts Receivable to save valuable time and resources by automatically applying incoming payments to open receivables during daily batch processing. You can easily and efficiently resolve unapplied remittances online.

Advanced Remittance Processing (ARP) is an automatic cash application process that allows you to perform the following functions:

  • Receive lockbox deposits electronically from your banks on the day the payments are deposited
  • Automatically apply the majority of the day's receipts to open items in accounts receivable in one batch process
  • Perform online disposition of exceptions the system encounters during the automatic cash application process
  • Generate a complete set of daily reports and maintain historical deposit and payment information online to allow you to audit all cash applications

The ARP automatic cash application process can be summarized in a series of operations that highlight the labor savings provided. ARP processing requires some setup to ensure that the process operates as efficiently as possible.

ARP allows you to perform the following operations:

  • Receive/Edit Bank Transmission of Lockbox Deposits
  • Identify/Assign Customer Numbers
  • Select Customer Open Items
  • Summarize Open Items Extracted
  • Check Application Against Open Items
  • Produce Reports Recapping Check Application Process
  • Create Disposition and On-Account Payment Records
  • Report Check Differences
  • Create Applied Checks Interface Records to Accounts Receivable
  • Flag Disposition Records as Temporarily Paid on Ledger File
  • Update A/R Ledger and Audit Files
  • Open Item Extraction

Previous Article Revamp Your Productivity: Discover Crossroads RMC's Ultimate Solution
Next Article Infor LN & Baan Tip: Performance improvement by setting the First Free Number Cache (tcmcs0651m000)
Print
10586 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

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

12345678910Last

Theme picker

Tips: LN | Baan

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.

If you have a parts warehouse and prefer to use SIC for planning (re-order point) but need to use MRP/MPS planning for production, create a non-nettable warehouse for the parts warehouse and run the SIC plan against that warehouse.

When running the SIC plan, be sure to set the Order System to “MPS to MRP” for Baan IV and to “Planned to Planned” for Baan V and LN.

Using this method you keep the parts inventory out of the production planning and in the hands of the parts warehouse planner.

First133134135136138140141142Last

Theme picker

Categories