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 Year-End Close Checklist

As the year draws to a close, the hustle and bustle of year-end activities can sometimes lead to overlooking critical tasks within your Infor ERP system. Ensuring a proper year-end close is essential for setting the stage for success in the coming year. Here is a comprehensive checklist to guide you through the process:

Year-End Close Process Objectives:

  • Remove discontinued items.
  • Remove sold purchase receipts.
  • Remove lot attributes for sold lots.
  • Update standard cost based on the current cost field (only for environments without Manufacturing).

Preparing for Year-End Close:

  • Conduct a full physical inventory and update quantities before the actual year-end or establish a robust cycle-counting program.
  • Close out all purchase contracts and PO’s, ensuring no receipts are allowed against any contract line items.
  • Prepare users for a year-end push to complete all year-to-date inventory adjustments, receipts, and invoicing.
  • Determine how to handle new year transactions without posting.
  • Decide on new standard costs for the upcoming year (Manufacturing).
  • Discuss cutoff dates for removing Archived BOMS and Closed/Canceled Mfg Orders (Manufacturing).
  • Run PRF900 to update performance measurements and purge closed shop orders.

Finance Specific Items:

  • Set up financial periods for 2024 before the new year begins.
  • Open the January period in 2024.
  • Finalize any outstanding transactions from the current year (2023).
  • Copy the CEA Book for the new year, ensuring all Journal Sources are set up. Copying ensures that every needed record is in place.

General LX & BPCS Items:

  • Run ACP920 (1099 Report) before ACP910 (Year End Close), as the Close Program clears the 1099 Payments History.
  • Address any old sales invoices.
  • Rectify outstanding financial integration errors.
  • Set up new integration mapping for 2024 as needed.
  • Test the mapping in a test environment before the new year.
  • Review and update jobs as needed to ensure they will process in 2024.
  • Determine, for cash-flow purposes, which purchase invoices won't be paid until 2024.

For additional insights and details about each program's functionalities and the files they update during the LX and BPCS Period End and Fiscal Year-End Processing, please refer to the attached document: LX & BPCS Period End & Fiscal Year End Processing Document

If you require assistance, please don't hesitate to contact us. We are here to guide you through the process to ensure everything is completed correctly and comprehensively. Reach us at 1.800.762.2077 or solutions@crossroadsrmc.com.

Previous Article Infor LN & Baan Year-End Processing Checklist for Period and Fiscal Year Closure
Next Article Infor LX / BPCS & Infor LN / Baan Tip: Time for the Notorious TRIO: Manual -  Physical -  Inventory
Print
10025 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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

Ensuring access to historical logistical and financial transaction information for your employees is crucial. However, before proceeding with archiving or deletion, it's essential to evaluate the necessity of retaining this data. Baan and Infor LN (ERP LN) offer standard archiving sessions within major modules that typically handle a significant volume of historical transactions. These sessions are designed to transfer historical data to an archive company before deleting it from the operational company.

When it comes to archiving sessions, you have three primary options:

Many transactions in all kinds of modules use order numbers or serial numbers. These order numbers are most often automatically generated. In the Number Groups (tcmcs0151m000) session you can define groups of order numbers used for dedicated areas. A Number Group is a group of the first free number series that you can assign to a specific use. All the numbers that Infor LN generates in the number groups that are dedicated to the same purpose are unique.

All the first free numbers are stored in the table tcmcs050.

As many different processes can request a free number from the number groups, we often see delays in the performance, due to locking on the first free number records. This locking issue can have a severe impact on the performance of huge batch-type transactions, but also on the performance perceived by individual users in many areas in LN.

For example:

First89101113151617Last

Theme picker

Categories