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
35226 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

In Infor LX, there are two ways to enter indirect labor. You can use either SFC600 or SFC650.
 

  1. If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
  2. If you use SFC650 and enter a reason code for the indirect, the reason code is not written to the labor Ticket file.

 

In either case, the reason code is not validated from the transaction file because there is no indirect transaction code. The indirect code that can be setup is machine downtime. If you need to validate and track indirect by reason and validate the reason code, then you may want to explore an MES solution that works with Infor LX.

 

Certain industries require lot control, where others may find it an option based on how they want to trace the material used in a product in the event of a defect, or recall.

LX provides tight lot controls and flexibility with lot number assignments. Shop orders can have a pre-assigned lot number, or a lot number can be automatically assigned when the item is produced. You can also assign a specific lot number for the entire shop order, or for each item/quantity reported against a shop order.

FirstLast

Tips: LN | Baan

Categories