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

Join Infor LX User Groups Open Discussion on Infor ION Basic

The Next-Generation Business Process Connectivity Software - Infor ION (Intelligent Open Network)

October 12, 2021 | 9:00am CDT
Infor ION Basic Meeting - Learn how to connect Infor LX to other systems

Please join Crossroads RMC's very own, Tim Baker, Sr. Solutions Architect, to learn how to use Infor ION to connect Infor LX to other systems, along with how to move data using Stored Procedures, API, SQL Database, and much more. 

Bring your questions and share in the open discussion!

*Register today via the LX Community calendar>

*Not a member of the Infor LX Community yet? Join today!>

Infor ION is an intelligent network that allows you to move information between systems easily without having to create point-to-point integrations. This platform loosely couples systems together so they speak the same language but are not dependent upon each other. Much like the Internet, one application can be upgraded, replaced, or even fail without taking down the entire network. Built using non-proprietary standards, Infor ION provides an open architecture that is flexible, scalable, and adaptable.

Learn more about Infor ION on Crossroads RMC's website>

---------------------------------------------------------------------

*ACCOUNT ACTION REQUIRED - PLEASE NOTE: The LX User Group has moved to https://concierge.infor.com. Please confirm you have access ASAP. All access requests require approval by your organization's support admin, so please sign in to confirm access, or sign up now, or reach out to your organization's support admin to ask them to add you.

Once you have access to https://concierge.infor.com, click on the Communities box, and join the LX - User Group - LX. You'll find this meeting on the calendar.

----------------------------------------------------------------------

More ways to join the meeting on October 12th:

Join from the meeting link:
https://formica.webex.com/formica/j.php?MTID=m9fb912c4927f947a034247aefc1cd94b

Join by meeting number: 
Meeting number (access code): 2311 777 6157
Meeting password: pWJFmmRX522

Tap to join from a mobile device (attendees only):
+1-646-992-2010,,23117776157## United States Toll (New York City)
+44-20-3198-8143,,23117776157## United Kingdom Toll

Join by phone:
+1-646-992-2010 United States Toll (New York City):
+44-20-3198-8143 United Kingdom Toll
Global call-in numbers | Toll-free calling restrictions

Join from a video system or application:
Dial 23117776157@formica.webex.com
You can also dial 173.243.2.68 and enter your meeting number

Previous Article Infor LX & BPCS Tip: Infor ION - What is ION, and why do I need it?
Next Article Infor LN & BaanTip: Restructuring Your Warehouse
Print
30054 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