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

Kathy Barthelt

Infor LN & Baan Year-End Processing Checklist for Period and Fiscal Year Closure

The conclusion of the fiscal year is inevitably a hectic period, making it crucial not to overlook essential tasks within your ERP system to ensure a seamless year-end close and set the stage for a successful start to the upcoming year. Below are critical items to include in your comprehensive checklist:

Year-End Close Process:

  1. Remove discontinued items.
  2. Eliminate sold purchase receipts.
  3. Clear lot attributes for sold lots.
  4. Update standard cost based on the current cost field (for environments without Manufacturing only).

Prepare for Year-End Close:

  1. Conduct a comprehensive physical inventory and update quantities before the actual year-end or establish a robust cycle-counting program.
  2. Review and post any applicable sales and purchase invoices/returns.
  3. Prepare users for a year-end push to complete all year-to-date inventory adjustments, receipts, and invoicing.
  4. Determine procedures for handling new year transactions without immediate posting.
  5. Establish new standard costs for the upcoming year (Manufacturing).
  6. Discuss cutoff dates for removing Archived BOMs and Closed/Canceled Mfg Orders (Manufacturing).

Finance Specific Items:

  1. Set up financial periods for 2024 (fiscal, reporting, and tax, as applicable).
  2. Open January period in 2024.
  3. Finalize any outstanding transactions from the current year (2023).
  4. Perform a soft-close for any open periods in 2023.

General Baan/LN Tips:

  1. Issue any pending old sales invoices.
  2. Resolve outstanding financial integration errors.
  3. Establish new integration mapping for 2024 as needed.
  4. Test the mapping in a controlled environment before the new year.
  5. Review and update jobs to ensure they will process in 2024.
  6. Determine, for cash-flow purposes, which purchase invoices won’t be paid until 2024.
  7. Verify that calendars are set up for the new year with holidays correctly indicated.
  8. Check jobs to ensure that any with hard-coded dates will point at the new year.

For additional insights and tips on year-end processing, refer to the relevant documents in the Infor Knowledge Base.

 KB 

 Content 

 1879191  

 Document including step by step procedure, possible error/warning messages, and more (Infor LN) 

 1147023 

 Step by step procedure description (Infor LN)

 1116239 

 Step by step procedure description (Infor LN)

 1117334

 Step by step procedure description (Infor LN; Portuguese)

 1171300 

 Step by step procedure description (Baan IV) 

If you require assistance or have any questions, feel free to reach out to us, and we'll gladly guide you through the necessary steps to ensure a thorough and accurate completion of your year-end processes. Contact us at 1.800.762.2077 or via email at solutions@crossroadsrmc.com. Your success is our priority, and we're here to help.

Previous Article Infor LX/BPCS Tip What are the differences between INV810 and INV015 for Cycle Counting updates?
Next Article Infor LX & BPCS Year-End Close Checklist
Print
14372 Rate this article:
2.5
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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

The standalone LN UI allows enhanced URL-parameter configuration. A single session can be started directly. Based on the URL, users can choose if the menu must be available and if the displayed set of records must be restricted.

This can be useful for self-service kiosks or simple full-screen clients.

The production bill of material is globally specified at the company level. It can be used as a source for the definition of the local material lists, such as:

  • The production model in the repetitive module.
  • The production model in the job shop module.
  • The subcontracting model in the subcontracting module.

The production bill of material can be generated through the engineering bill of material. The new production bill of material differs from the old bill of material:

  • It has a header and a status.
  • It is always revision controlled.
  • The effective dates have been moved from the material lines to the header.
  • The BOM quantity has been moved from item production data to the header.
  • The use up has been moved from alternatives to the material line.
  • The material line excludes logistic data (no warehouse nor routing operation).

The production bill of material is not mandatory.

Production bill of material revisions:
The production bill of material is revision controlled. The objective of the revision is to control the changes to the bill of material over time.

The P-bom includes this revision-related data:

  • Revision number
  • Effective date and Expiry date
  • Status (New, Approved, Expired)
  • Creation date and Created by: user
  • Approval date and Approved by: user
  • Expiry date and Expired by: user
  • Source information
First5960616264666768Last

Theme picker

Categories