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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Getting the Most Out of the Shop Order Inquiry Program – Part 2

Understanding: How many hours remain in total and at each operation?

Now let’s look at what information is being supplied from the shop floor.

It’s not uncommon for transaction reporting to be captured manually on the shop packet that was issued to the factory floor when the SO was released.

The big question is, is anything done with the data? Is it collected and keyed to a  spreadsheet and not shared, or is the transaction data keyed to SFC600? If it is being keyed, ask how often and by whom? Some companies use alternative methods to capture transaction data that do not require batch keying via a keyboard.

Not a lot of data is required to be keyed to SFC600 in order for the SO Inquiry to be useful. The data that should be reported for the transaction process is as follows:

  • The type of hours being reported – machine, run labor, setup labor
  • If reporting setup and run labor you want an employee clock number
  • The shop order and the operation that is being reported
  • Is the operation complete
  • How many good were produced at this operation
  • How many hours – the numbers of hours are critical. Do the employees estimate how many hours they worked, or do they track actual time started and stopped in order to calculate the actual number of hours.

Based on what is captured and how often will have an impact on the SO inquiry screen. Understanding the batch times as to when the transactions are keyed will provide you with the window as to the SO status at that point in time. Or, are they keyed as they happen in a near real time fashion so that you can have a more current view of the factory floor.

Previous Article Baan/LN Tip of the Week: ERP Setup - Pros & Cons
Next Article Downtime Tips
Print
33369 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

The package includes numerous reports and sessions to view the variances in a way that Finance can identify problems based on the Finance Integration Transactions in the General Ledger.

There are a few main sessions with many detailed sessions linked to them. The reports can be run from the main Print Production Order Variance Reports or in the individual detailed session.

Sessions included in the report package:

1. Print Finalized Trans – Variance Reports.

a. Financial Trans. by L/Acct – Prod. Order Variances - Recap

b. Financial Trans. by L/Acct – Prod. Order Variances – Details

2. Update Production Order Variances (updates special variance table).

3. Production Order Variance Overview – Main view

a. Production Order Variance Details

b. Price Variance Details – Material Variances

c. Price Variance Details – Operation Variances

d. Efficiency Variance Details – Material Variances

e. Efficiency Variance Details – Operation Variances

f. Efficiency Variance Details – Reject Variances

g. ACO Variance Details – Reject Variances

h. Accept Production Order Variances

i. Un-accept Production Order Variances

j. Finally Accept Production Order Variances

4. Print Production Order Variance Reports:

a. Production Order Variance – Overview

b. Production Order Price Variance – Material Revaluation

c. Production Order Price Variance – Operation Revaluation

d. Production Order Efficiency Variance – Material

e. Production Order Efficiency Variance – Operation

f. Production Order Efficiency Variance – Rejects

g. Production Order ACO Variance – Rejects-Additional Costs

5. Delete Production Order Variances (used to redo a month)

Contact Kathy Barthelt to learn more.

Graphical representation makes complex concepts—like the intricacies of an ERP system—more universal, relatable and easy to understand.

ERP dashboards gather and visualize critical metrics from across the organization, offering insight into the performance, outlook and interconnectivity of business processes.

By setting up ERP dashboards that illustrate key metrics and compellingly communicate operational performance, key stakeholders will have a clear picture of the health of the business—and make better, more informed business decisions as a result.

The Crossroads Analytics Dashboard has preconfigured views for all of the following:

 Infor LN & Baan
  • Accounts Payable
  • Accounts Receivable
  • Journal
  • Booked Sales
  • Invoiced Sales
  • Production
  • Receipts
  • Purchase Orders
  • Inventory

To learn more visit our Analytic Dashboard webpage.

First5455565759616263Last

Theme picker

Categories