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

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

Anthony Etzel 0 83281 Article rating: No rating
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.

BPCS/LX Tip of the Week: The Item Master Requirements Code

Anthony Etzel 0 78973 Article rating: No rating

In the Item Master File, the requirements code is used to specify the type of demand for the item. Planned order requirements are determined from the type of demand. If the requirements code is left blank, the planning systems treat the item as a sum code (3).
 

Other options for the field are:


1 = Dependent demand that is indirectly generated from the parent item requirements.

2 = Independent demand generated from customer orders and forecasts.

3 = The Sum of both independent and dependent demand.

Grindmaster Cecilware Selects Crossroads RMC For Baan IV / Davisware Integration

Crossroads RMC 0 41680 Article rating: No rating

Grindmaster Cecilware, a leader in the development of products for the food and beverage industry, has selected Crossroads RMC to integrate their Baan IV system to Davisware Global Warranty. Davisware is an electronic customizable online solution that fits almost any warranty process. Grindmaster’s customers will be able to access the Davisware software online and process warranty claims which will then automatically feed back into the Baan IV system for further review and processing. The integration is expected to go live in Q1 of 2015.

Huf North America Goes Lives With Next Phase of RMC3 Data Collection

Crossroads RMC 0 42919 Article rating: No rating

Huf North America, a global leader in the production of mechanical and electronic key systems, lock sets, steering locks, and remote control systems for the automotive industry, has gone live with phase 2 of their Crossroads RMC data collection implementation. This go-live included Report Orders Complete, Labor Reporting, Material Issue, Inventory Transfers, barcode label modifications, as well as custom applications for their Paint / Polishing operations. This go-live was paired with the expansion of Huf’s Plastic Injection Molding and Paint Facility in Greeneville, TN. The next phase of this project will include the extension of the Crossroads RMC solution into Huf’s facility in Mexico.

Baan/LN Tip of the Week: Product Configurator - Part 2

Baan Tips

Kathy Barthelt 0 117657 Article rating: 3.0
Who gets involved?
  1. Most commonly Engineering is involved in writing the rules, creating the bills and routings.
  2. Sales or Customer Service determines the questions and the order they are asked in.
  3. Sales or Customer Service determines the rules for the pricing.
  4. Sales, or Customer Service, and Engineering work together in determining the part number, description and text.

What are the steps?

  1. You must start by defining the features and options (questions and answers) and the order in which these are asked. We work this out first using sticky notes and large easel paper. Normally during the process we find that we want to move these questions around. Setting them down on paper makes the process of getting the data into Baan much more efficient. We also then have a record of what decisions were made prior to entering the data. This is normally a joint effort of Engineering and Sales. This is required and must be the first step.
  2. Constraints for features and options. These are the rules for determining what questions are asked and which options are allowed. This is generally done by Engineering or whoever is responsible for the configurator. This is required.
  3. Generic Bill of Material. All possible bill options are entered here and constraints are written to determine which options are selected based on the answers to the questions. This is generally done by Engineering or whoever is responsible for the configurator. This is a required step.
  4. Generic Routing. Similar to the bill of material, but used for generation of the routing steps. This is generally done by Engineering or whoever is responsible for the configurator. This is optional.
  5. Generic Item Data. This consists of creating custom item numbers, descriptions, text, material, size or standard fields in the custom item master. This is generally done by Engineering or whoever is responsible for the configurator though Sales may have some involvement. This is optional.
  6. Generic Pricing. This is used to calculate the selling price based on the answers to the questions. This is normally a responsibility of Sales or whoever determines the pricing. This group is also trained on writing the constraints for this section only. This is optional.

BPCS/LX Tip of the Week: How To Capture Re-Work Time (Part 1)

Anthony Etzel 0 90962 Article rating: No rating
In SFC600, there is no code to capture the time spent on re-work. Re-work is usually at a specific operation, or when the part is finished and QC determines that re-work is required in order to pass inspection. You are faced with deciding on how to report the additional labor time.

Do you continue to report it against the operation, or create a re-work shop order?

If you are re-working through a specific operation you can capture the time as run labor with the SFC600 program. Now you need to deal with the variance of actual to standard time and what impact this has on costing.
First124125126127129131132133Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Defining “Unavailability” in Infor LN

This topic describes the definition of temporary unavailability for resources in a calendar.

Use one of the following sessions:

  • Recurring unavailability
    For recurring unavailability, such as national holidays, define the recurrence in the Recurrences (tcccp0143m000) session. Add that recurrence to the applicable calendar and availability type in the Calendar Recurrences (tcccp0144m000) session, and clear the Available check box for the unavailable days.
    With calendar recurrences you define recurring exceptions in a calendar, and set a time schedule for daily, weekly, monthly, or yearly unavailable time in one action.
  • Unavailable days for all availability types
    To define occasional unavailability, such as a department trip, use the Calendar Non-Available Days (tcccp0119m000) session. What you define here applies to all availability types.
     
  • Unavailable days for a specific availability type
    To define unavailability for a single day, complete the following steps:
  1. Start the Calendar Working Hours (tcccp0120m000) session.
  2. Find the applicable calendar and availability type, and clear the Available check box for a working hours type on the relevant date.
  • Unavailable during a part of a day
    To indicate that part of a day is unavailable, use the Calendar Recurrences (tcccp0144m000) or the Calendar Working Hours (tcccp0120m000) session to specify the time intervals that are available. All other times are considered unavailable. You cannot directly specify an unavailable time interval.

If you defined unavailable dates in the Calendar Non-Available Days (tcccp0119m000) or the Calendar Recurrences (tcccp0144m000) session, in the Calendar Working Hours (tcccp0120m000) session, click Update Calendar.

Note:

  • Unavailability always applies to entire days. If the Calendar Working Hours (tcccp0120m000) session contains multiple time intervals for a single date, and the Available check box is cleared for some intervals and selected for other intervals on the same day, the entire day is unavailable.
  • A calendar recurrence that makes a day unavailable has no effect on the availability of that day in the parent calendar.


It is not useful to define a special availability type for unavailability, because Infor LN does not maintain and update the working hours and the capacity data of a calendar in the Calendar Working Hours (tcccp0120m000) session based on non-available availability types.

Previous Article Infor LN & Baan Tip: Porting Set Issues
Next Article Infor ERP Tip of the Week: 5 Steps to Managing Sales Tax
Print
30070 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories