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: Reports to Analyze Company Performance

You know what ERP data you need to analyze your company’s financial and production health, but sometimes it's a struggle to get that data in a format that is meaningful. Here are some reports in BPCS & Infor LX which you may find useful.

As is the case with most ERP reports, with each version progression from the earliest versions of BPCS to the latest version of Infor LX, there are improvements in selection criteria and report content. Some may require some setup and others may require some formatting if you would like to export them to Excel. Contact me if you have questions or need assistance.

BPCS & LX FINANCE REPORTS:

BPCS:

  • GLD240 - General Ledger - Trial Balance
    • This report allows you to produce a menu-driven Trial Balance that shows Opening and Closing balances, and Activity, for any range of Profit Centers and accounts in the GL Master. 
  • GLD250 - Journal Entry Audit Report
    • This report answers the Audit need. It provides Journal detail for selected Journal Sources and includes Reference fields that tie GL transactions to the Subsystem source. 

Infor LX

  • CLD220 - General Ledger - Trial Balance
    • This report allows you to produce a menu-driven Trial Balance that shows Opening and Closing balances, and Activity, for any account range from a customized Chart of Accounts. Year and Period selectivity, along with Journal Source choices, allow for as focused a view of an organization's GL activity as an accounting department needs. 
  • CLD285 - CEA Audit Report
    • This report answers the Audit need. It provides Journal detail for all Account Strings selected and includes Reference fields that tie GL transactions to the Subsystem source.


BPCS & LX MANUFACTURING REPORTS:

BPCS / Infor LX:

  • CST270 – Shop Order Cost Variance & WIP Report
    • This is by far the best total picture of what happened on any Shop Order from several perspectives (cost/efficiency/overall performance).
       
  • INV220 – Stock Status Summary & INV210 – Turnover Analysis
    • ​Both of these reports give you a view of how your inventory is moving to use as a measurement of the Planning Settings and which items need closer review.
Previous Article The Best Baan | Infor LN Manufacturing Reports to Analyze Company Performance
Next Article Infor LN & Baan Tip of the Week: Reports to Analyze Company Performance
Print
25744 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

Ok… so you want to know the status of a specific shop order that was released two days ago.

What do you do?

It’s a sure bet that you have a manager, supervisor, or planner who can walk the floor and find the order at whatever work center it happens to be at. He/she can then answer “what operations have been completed and how many were completed?” All this requires leg work, and of course, a fair amount of time.

Now, if you have setup your BPCS master files properly, and you report transaction activity, you should be able to get those shop order statuses much faster using the SFC300 Shop Order Inquiry Screen.

At your fingertips you can see:

  • Release date & due date
  • How many hours remain in total and at each operation
  • The quantity required, what was finished and the remaining quantity
  • What components (materials) have been issued

Pretty basic information, right? Are you getting what you need to know? If not, then you may want to reexamine how your BPCS files are setup and what transactions along with their frequency are captured.

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.

 

First140141142143145147148149Last

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