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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

If you specify a configurable item on the sales order line, you can configure or link a product variant.

An item is configurable if the Configurable check box is selected in the Item - General (tcibd0101s000) session.

Manufactured items with theDefault Supply Sourceset to Assembly in the Item - General (tcibd0101s000) session and Generic items, are always configurable.

Purchased items with the Purchase Schedule in Use check box selected in the Item - General (tcibd0101s000) session, can be configurable.

If you do not wish to define a detailed mapping to various ledger accounts for specific integration transactions, you can map the corresponding integration document type to a default account. All the transactions of the integration document type for which an account cannot be determined based on the mapping scheme details, are posted to the default account.

 

The mapping of an integration document type to a default account is direct, without the need for element groups and mapping elements. No distinction is made on any of the transaction details.

 

Default accounts can be used in two ways:

  • Instead of a detailed mapping to various ledger accounts. All the transactions are posted to the same account. For example, all warehouse receipts are posted to the Inventory ledger account, without any distinction.
  • In addition to a detailed mapping. If a transaction cannot be mapped based on the detailed mapping scheme, it is posted to the default account.
First100101102103105107108109Last

Theme picker

Categories