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

This enhancement simplifies access to LX programs that are available through System i Manager (SiM), as well as Workflow for System I (WFi). This provides an easy way to promote common WFi business processes from one LX environment (for example, test or environment) to another LX environment (for example, production). 

LX also provides a set of four-character task codes that can be used within SiM, System i Workspace (SiW), and WFi, for default programs in LX. These predefined LX task codes begin with 0,1,2,3, or 4. Users can specify task codes for their custom programs that are flagged as valid menu options in LX, but these task codes cannot begin with 0,1,2,3, or 4. Users can specify the task codes in Infor LX Object Master Maintenance, SYS625D. This enhancement provides simplified access to LX programs that are flagged as valid menu options in System i Manager and Workflow for System i environments. In SYS625D, The user can also specify task codes in SYS625D for customized programs that are flagged as valid menu options.

Users are no longer limited to backing up or saving files to a tape or diskette.They can now use a Save File (SAVF) to save data and objects. LX programs that perform saves and/or backups were modernized to add a new SAVF option.  

There were numerous places in LX where users are prompted to save a file or library. These screens have options for tape or diskette. Diskette refers to the old 8” diskettes used on System/38. These devices are outdated and virtually obsolete. The current means of saving objects on the IBM i, is through the use of a Save File (SAVF). This compresses the data into a single object that can be saved and is easily transferred between systems.

These objects were modified and/or created for this enhancement:

  • Backup Simulation (FOR630C, FOR630D, FOR630FM, FOR640HT, and FOR630HT)
  • Month End Close (INV903D, INV903FM, INV901C, and INV903HT)
  • Purge YTH/Restore Archived Lots (INV912C, INV912D, INV912DHT, and INV912FM)
  • Purge and Save ITH records (INV932C, INV932D, INV932FM, and INV932HT)
  • Labor Ticket Save (SFC905D, SFC905FM, SFC901C, and SFC905HT)
  • Backup Infor LX Files (SYS700C, SYS700D, SYS700FM, and SYS700HT)
  • Backup Infor LX Programs (SYS710C, SYS710D, SYS710FM, and SYS710HT)
  • Backup Infor LX Source (SYS740C, SYS740D, SYS740FM, and SYS740HT)
  • Save File Name Selection (SYS912D, SYS912FM, and SYS912HT)


Benefit

Use the Backup Simulation to copy a simulation file to a SAVF or tape. Users may want to do this to transfer simulation data from one system to another, from site to site, or to save the data before permanently deleting it from the system.

First6970717274767778Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories