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

Did you know that you can set up one-time vendors in LX? One Time Vendor (1,A): Specify Y to indicate that this vendor is a one-time vendor. Otherwise, could you specify N. The system removes a one-time vendor's information from the Vendor Master file after all transactions are reconciled. If this vendor already exists as a one-time vendor, you can specify N to change the vendor to a regular vendor.

Determining whether to use Master Production Schedule (MPS) planning or Material Requirements Planning (MRP) planning for items in Infor LX and BPCS involves understanding the nature of the items and their demand characteristics.

Master Scheduled Items typically encompass finished goods or service items. These items receive their requirements either from Independent demand, Dependent demand, or a combination of both...

12345678910Last

Theme picker

Tips: LN | Baan

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

In LN, you can differentiate between items at various suppliers:

  • Locations (warehouses),
  • Purpose (planning, purchase)
  • Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:
 
  • Items - Planning (cprpd1100m000)
  • Check Item Data by Warehouse (whwmd2210m000)
  • Item Supplier Plan (cpvmi0530m000)
These sessions define entities that have an n-to-1 relationship with the general item data.

 

First144145146147149151152153Last

Theme picker

Categories