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 Tip of the Week: Year End
George Moroses

Infor LX & BPCS Tip of the Week: Year End

Year-End is always a busy time!

So busy that it's easy to forget things that must be done in your ERP system to close out the year properly and set you up for a good start to the following year. Here are some things to add to your to-do 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. (for environments without Manufacturing only)
     

Prepare 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 before year-end. Make sure no receipts are allowed against any of the contract line items after year-end.
  • 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.
  • Discuss cutoff dates for removing Archived BOMS and Closed/Canceled Mfg Orders
  • Run PRF900 to update performance measurements and purge closed shop orders

Previous Article M3/Movex Tip of the Week: Year-End
Next Article Infor LX & BPCS Tip of the Week: Year-End for Finance
Print
28413 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

FINANCE: Default Billing Reason Code from User Order Class
This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

TECHNOLOGY:  Security Manager
New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves, but are only allowed to access regular LX programs if granted authority by an LX security officer.

OPERATIONS: Track all order holds added & released
Enhancement: Order Hold Audit Functionality
This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves but are only allowed to access regular LX programs if granted authority by an LX security officer.

First2345791011Last

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:

1345678910Last

Theme picker

Categories