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

To create and maintain shop orders use SFC500 Shop Order Entry Maintenance. These orders use the standard bill of material (BOM) as the base list of components. You can also set up standard routings, which list the operations,

or work steps, involved in manufacturing.

 

To release shop orders, use the Shop Order Release program, SFC505. Infor ERP LX groups shop orders by user ID for batch processing. Use Shop Packet Print, SFC520, to print the shop orders that you select. SFC530 allows you to create multi-level shop orders to link shop orders together with a common end item parent. Linking multiple shop orders together for a final assembly product provides support for make-to-order and engineer-to-order manufacturing environments which need to schedule these multiple orders together or as a vertical slice in the production schedule.

 

You can make changes to shop orders after you print them. Use Shop Order Entry/Maintenance, SFC500, to update the shop orders. Changes are immediately visible on the inquiry screens for SFC300 and SFC350. To reprint the shop packet, use Reprint Shop Packet, SFC560.

The system automatically performs offsets for requirements dates for components in the MPS/MRP calculations. It also performs offsets for calculation of material need dates at the time that shop orders are released.


To calculate the offset, the system takes the parent lead time from the Item 
Master and adjusts it by the bill of materials offset (plus or minus) for the component. This gives the lead time days for that specific component. The system starts with the due date of the parent and backs up and skips all non-work days in the shop calendar.


Note that the offset calculation uses only calendar records that have a blank 
work center (the calendar record applies to all work centers). See the information for the Shop Calendar Maintenance program SFC140, in your Shop Floor Control documentation for shop calendar details.

First131132133134136138139140Last

Theme picker

Tips: LN | Baan

Table Timestamp Definitions (ttadv4136m000)

Use this session to define timestamps for Infor LN tables. A timestamp is an additional column that stores the date and time of the last change for each record.

Timestamps are utilized by features like the extraction logic of CPM Enterprise Analytics. They enable CPM to perform incremental data extractions. For example, CPM can use the timestamps to extract records that were changed during the last week in a weekly extraction process.

To Create Timestamps...

Operations: To absorb the cost of cost items into specific projects, you'll need to handle them as customized items. However, cost items cannot directly be defined as customized items. Customized items must be physical, either manufactured or purchased.

That said, it's still possible to absorb cost items into a project, although indirectly. Here's how:

  1. Set Up Ledger Account: First, create a new ledger account in session tfgld0508m000 and set the type to "PCS" (project) in the operations management integrations. This account will be used for matching and approving purchase orders for cost items.

  2. Create and Activate Projects: Ensure that the necessary projects are created and set to active status.

  3. Purchasing Cost Items...

12345678910Last

Theme picker

Categories