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

George Moroses

Infor LX & BPCS: Explore IDF Programs

IDF (Infor Development Framework) configures your view of the application data without modifying the core application and its supportability. In version 8.3.4 and higher, IDF programs provide the replacement for most of the 300 series inquiry programs. Starting with version 8.4, Infor has added 100 series maintenance programs such as Item Master, Vendor Master, and Customer Master. With IDF, navigation drill-downs are far superior to any green-screen presentation of the data.

Included with IDF are several interfaces including:

  • PowerLink – A Windows-based client for end-users
  • Link Manager – A Windows-based environment administration client for importing environments, starting and stopping environments, and installing Fix Patches
  • Net-Link – A browser-based client (used by LX when running with SiW)
  • System-Link – A XML-based interface for processing transactions from external sources

The IDF ISO includes several components:

  • All of the above interfaces
  • Enterprise Integrator – for customizing IDF components and creating new business objects
  • EGLi – Enterprise General Ledger
  • CRMi – Customer Relationship Management


Don't see what you're looking for? Crossroads RMC provides additional Crossroads MES IDF Reports in the areas of Efficiency, Downtime, Machines, Operations, Parts, Orders, Quality, Receipts Work Centers, and more!

For more information please contact Anthony Etzel

Previous Article Infor LN & Baan: Trying to make your shipping labels generically work for all of your customers?
Next Article Infor LX & BPCS Tip: Customer Type
Print
27509 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

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.

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

First let’s look at some key BPCS Master File data starting with the routing file.

How many routing steps (operations) are set up that reflect how the product is produced in the factory? If you take a short cut and set up only one operation for the entire process, then you will limit the information seen on the SO inquiry program. Set up the operation steps to reflect what you want to report back to from the factory floor.

Will each of the routing steps run in one work center, or in different work centers? To keep it simple you may want to set up work centers as departments. For example:

  • Assembly
  • Machine
  • Paint
  • Etc.

For each operation setup consider how you have set up the following:

  • Load Codes – for example a code 5 is used if reporting both setup time and run labor time. These codes are maintained in the work center file
  • Basis Code – typical codes are P for pieces per hour,  3 is used for hours per 1,000 pieces
  • Setup hours – if you set them up, you also want to report them
  • Run hours – Direct Labor
  • Machine hours

How you set up th

FirstLast

Tips: LN | Baan

Categories