BPCS/LX Tip of the Week: Indirect Labor Reporting

Anthony Etzel / Wednesday, November 12, 2014 0 84175 Article rating: No rating

In the Shop Floor Control Module, you have the ability to key in both direct labor and indirect labor. However you want to establish specific types (reasons) for the indirect labor. The SFC600 labor entry program shows a reason code field, but it is designed for reject quantity and machine downtime reasons, not indirect labor reasons.

There is a way around this. With an MES solution you have the ability to setup and report indirect time against a specific reason code.

Baan/LN Tip of the Week: Configuring Items in Infor LN

Kathy Barthelt / Wednesday, November 12, 2014 0 95533 Article rating: No rating

In Infor LN, the configuration of a generic item not always results into a customized item. Configured items can now be customized items as well as standard items. If users configure items without PCS projects, standard items are generated instead of customized items.

Baan/LN Tip of the Week: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt / Wednesday, November 5, 2014 0 84470 Article rating: No rating

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

BPCS/LX Tip of the Week: Shop Order Status

Anthony Etzel / Wednesday, November 5, 2014 0 88039 Article rating: No rating

You can see the status of the Shop Order when using SFC300 Shop Order Inquiry. You want to be sure that your shop orders are at the correct status in order to report against them.

The following are the shop order status codes:

04 = The Shop order has been entered.

05 = The Shop order has been released and printed.

14 = The Shop order has been released, but not printed. If a shop order is at this status, you have released it and it is not printed due to a system failure, or the order has been put on hold.

XX = The Shop order is closed.

BPCS/LX Tip of the Week: Work Center & Machine Locations

Anthony Etzel / Thursday, October 30, 2014 0 91154 Article rating: 4.0

For either file, you must specify a valid location code as defined in the Location Master File.

If the machine master locations are blank, then the work center locations are used. There are cases where you may want to do a combination between the two in defining the locations.

Let’s say the end item has one operation. The operation is at work center 510 and Machine A is in the work center. You have locations setup in both the Work center file and the Machine master File. You report 100 complete at the work center without specifying the machine.

In this case, the inventory will be processed based on the locations defined in the work center file. If the transaction included the machine number, then the locations in the machine file would be used.

Baan/LN Tip of the Week: What could go wrong with GRINYA?

Kathy Barthelt / Thursday, October 30, 2014 0 86112 Article rating: No rating

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Baan/LN Tip of the Week: Differentiating An Item By Supplier - LN

Kathy Barthelt / Friday, October 24, 2014 0 88678 Article rating: No rating

In LN, you can differentiate between items at various suppliers:

Locations (warehouses),
Purpose (planning, purchase)
Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:

Items - Planning (cprpd1100m000)
Check Item Data by Warehouse (whwmd2210m000)
Item Supplier Plan (cpvmi0530m000)

These sessions define entities that have an n-to-1 relationship with the general item data.

BPCS/LX Tip of the Week: Inventory Control

Anthony Etzel / Friday, October 24, 2014 0 95201 Article rating: No rating

In Infor LX you need to determine how inventory will be moved in and out of warehouse storage locations, and which of the following transactions to use for inventory control:

A transfer transaction can be used to move inventory from one warehouse location to another warehouse location.
A production receipt transaction is used to add inventory to a warehouse location.
A material issue or backflush is used to reduce inventory from a warehouse location.

First Previous 130 131 132 133 134 135 136 137 138 139 Next Last

Tips: LX | BPCS | M3

9Mar2026

Infor ERP Tips & Tricks: Already Have Avalara? Integrate It with Your Infor ERP

Monday, March 9, 2026

10Feb2026

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Library BMRTOOLS contains the following commands

Tuesday, February 10, 2026

Next Last

Tips: LN | Baan

Crossroads RMC / Wednesday, March 2, 2022

/ Categories: Analytics Dashboard, Integrations & Enhancements, Support, Training & Workshops, Finance, Manufacturing, Operations, Technology

Manufacturing vs. Operations vs. Finance: Who WINS?

Infor LX | BPCS | Infor LN | Baan

Manufacturing Goals: develop high-quality products and services in response to the demands of the market, improve efficiency and maximize capacity utilization.

Operations Goals: utilize resources, labor, material, and equipment effectively in order to match supply and demand.

Finance Goals: analyze revenue growth opportunities, control costs, and maximize profitability.

So, who WINS?

Whose priorities take precedence when it comes down to it and what happens when the demands seem to compete? The answer to that question may be simpler than you think. Quite often, production, operations, and finance are operating based on their own sets of data which have been created within their respective group to serve the needs of the group alone. Finance likely does not have access to production or operations reports and production and operations hardly ever have access to financial reports. But why? What if all departments operated based on the same data, viewed in the same way? Would it not be easier to understand where the priorities should be and how the ship should be steered?

Dashboards provide real-time visualization of data through graphs, tables, and other visualization techniques. Through the use of dashboards, the complexity of large volumes of data gets stripped away and instead gets presented through manageable, digestible chunks of information so companies can focus their attention on the areas of the business that need it most. The dashboards then serve as a common ground for further dialogue and present information to everyone in a way that is mutually understandable.

Although the data represented in dashboards can be gathered through multiple reports and sometimes multiple reporting systems, consolidating the data into one unified source provides a highly effective tool to generate actionable insight.

Crossroads RMC's Analytics Dashboard provides a pre-built connection to Infor LX / BPCS and Infor LN / Baan and includes a full suite of ready-to-use, standard dashboards that can jump-start collaboration between your finance, operations, and production departments.