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

Infor LX & BPCS Period End & Fiscal Year End Processing Checklist

Infor LX & BPCS Year-End Close Checklist

Year-end is always a busy time and it is easy to forget all the things that must be done in your Infor ERP system to close out the year properly and set you up for success the following year. Here are some things you should have on your checklist:

The year-end close process provides an opportunity to:

_____ Remove discontinued items.

_____ Remove sold purchase receipts.

_____ Remove lot attributes for sold lots.

_____ Update standard cost based on current cost field (only for environments without Manufacturing).


Preparing for Year-End Close:

_____ Conduct full physical inventory and update quantities before actual year-end or establish a strong cycle-counting program.

_____ Make sure to close out all purchase contracts and PO’s. Make sure no receipts are allowed against any of the 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.

_____ Determine what new standard costs should be entered 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 the financial periods for 2022. Do this before the new year begins.

_____ Open period January in 2022. 

_____ Finalize any outstanding transactions from the current year - 2021.

_____ COPY the CEA Book for the new year. Creating the Book requires the user to set up all the Journal Sources, while Copying ensures that every needed record is in place.

General LX & BPCS Items:

_____ Run ACP920 (1099 Report) before running ACP910 (Year End Close), as the Close Program clears the 1099 Payments History.

_____ Issue any old sales invoices.

_____ Fix any outstanding financial integration errors.

_____ Set up new integration mapping for 2022 as needed.

_____ Test the mapping in a test environment prior to the new year.

_____ Review & update jobs as needed to ensure they will process in 2022.

_____ Determine for cash-flow purposes, what purchase invoices won’t be paid until 2022.


Want even more tips for month-end and year-end processing? See the attached document that covers LX and BPCS Period End and Fiscal Year-End Processing and provides details regarding what each program does and what files are updated.
LX & BPCS Period End & Fiscal Year End Processing Document>

Need help? Contact us and we’ll be happy to walk you through what needs to be done to ensure that everything is done correctly and completely. 1.800.762.2077 or solutions@crossroadsrmc.com
 

Previous Article Infor LN & Baan Tip: Using the “Use Up” Functionality in Infor LN
Next Article Infor LN & Baan Period End & Fiscal Year End Processing Checklist
Print
15006 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

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