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

Customer Defined Fields (CDFs) can be added to tables, screens, reports and BODs and validation and calculation logic can be defined around those fields.

Use the CDF concept to store additional data in the standard Infor LN tables. The CDF definitions are stored separately from the table definitions in the Data Dictionary. For the end user, the CDFs behave in the same way as the standard fields, if defaulting, validations, etc. are built using the CDF logic of the table extension point. The session extension point also has features for the CDFs.

CDFs are configured per package combination. This implies that when moving your companies from one package combination to another, the CDF definitions must be present in the target package combination. Otherwise you lose the data in the CDFs.

The package includes numerous reports and sessions to view the variances in a way that Finance can identify problems based on the Finance Integration Transactions in the General Ledger.

There are a few main sessions with many detailed sessions linked to them. The reports can be run from the main Print Production Order Variance Reports or in the individual detailed session.

Sessions included in the report package:

1. Print Finalized Trans – Variance Reports.

a. Financial Trans. by L/Acct – Prod. Order Variances - Recap

b. Financial Trans. by L/Acct – Prod. Order Variances – Details

2. Update Production Order Variances (updates special variance table).

3. Production Order Variance Overview – Main view

a. Production Order Variance Details

b. Price Variance Details – Material Variances

c. Price Variance Details – Operation Variances

d. Efficiency Variance Details – Material Variances

e. Efficiency Variance Details – Operation Variances

f. Efficiency Variance Details – Reject Variances

g. ACO Variance Details – Reject Variances

h. Accept Production Order Variances

i. Un-accept Production Order Variances

j. Finally Accept Production Order Variances

4. Print Production Order Variance Reports:

a. Production Order Variance – Overview

b. Production Order Price Variance – Material Revaluation

c. Production Order Price Variance – Operation Revaluation

d. Production Order Efficiency Variance – Material

e. Production Order Efficiency Variance – Operation

f. Production Order Efficiency Variance – Rejects

g. Production Order ACO Variance – Rejects-Additional Costs

5. Delete Production Order Variances (used to redo a month)

Contact Kathy Barthelt to learn more.

First5657585961636465Last

Theme picker

Categories