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

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

1345678910Last

Theme picker

Tips: LN | Baan

Table Timestamp Definitions (ttadv4136m000)

Use this session to define timestamps for Infor LN tables. A timestamp is an additional column that stores the date and time of the last change for each record.

Timestamps are utilized by features like the extraction logic of CPM Enterprise Analytics. They enable CPM to perform incremental data extractions. For example, CPM can use the timestamps to extract records that were changed during the last week in a weekly extraction process.

To Create Timestamps...

Operations: To absorb the cost of cost items into specific projects, you'll need to handle them as customized items. However, cost items cannot directly be defined as customized items. Customized items must be physical, either manufactured or purchased.

That said, it's still possible to absorb cost items into a project, although indirectly. Here's how:

  1. Set Up Ledger Account: First, create a new ledger account in session tfgld0508m000 and set the type to "PCS" (project) in the operations management integrations. This account will be used for matching and approving purchase orders for cost items.

  2. Create and Activate Projects: Ensure that the necessary projects are created and set to active status.

  3. Purchasing Cost Items...

1345678910Last

Theme picker

Categories