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

Baan/LN Tip of the Week: GRINYA

Kathy Barthelt 0 109524 Article rating: 3.0
GRINYA is one of the more complex issues in ERP Finance. GRINYA is the tracking via ledger account of the value of items received on a purchase order that have not been matched to a supplier invoice.

Baan solutions for Baan IV and V were incomplete. To take full advantage of the current GRINYA reconciliation process, check Infor solution #107147, which contains the GRINYA user manual and a link to download the software for your version of Baan. For ERP LN, look at Document Code U8942C US.

It is called User Guide for Reconciliation and Analysis. If you are not running the latest GRINYA solutions, patching will require a good amount of time in filling the Interim tables this solution runs from. Infor has posted several procedural write ups, so check the Support Site and read up before tackling this for the first time.

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

Anthony Etzel 0 81587 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 76241 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 40984 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 42204 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 109069 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.
First118119120121123125126127Last

Tips:  LX | BPCS | M3

Kathy Barthelt

Tip of the Week: 10 Ways to Succeed at an OEE Project Where 90% Fail

  1. Collect the requirements. Learn from everyone with the intent of developing a phased approach to implementing on your shop floor with OEE being Phase 1. 
  2. Create your list. Capture all of required functions, taking into account what the “output” of the system will be. What does the plant manager need to see in real-time? What KPI’s does each line need displayed in real-time? What reports are required?
  3. Insist Upon Real-time. In the moment data for the right OEE is the right approach. If it’s possible, collect the data automatically. Remember that real-time feedback to line operators results in an automatic increase in OEE.
  4. Evaluate your lines. Focus where production counts can be monitored automatically. If the data is in your PLC’s, can you get it out? OPC communication is the right way to go here. If not, the approach is to install a new dedicated PLC with sensors installed on each line.
  5. Find Your Data Points. If automatic production monitoring is not applicable, what will be your collection points and how will you collect the data?
  6. Calculate the Load. Determine how to load the “job” you’re reporting on into the OEE system. This will typically be the order/operation or the product from the ERP.
  7. Recognize Great Data. Do not accept “manual collection of data” as a viable approach because it produces false results and is labor-intensive.
  8. Be Tough. Evaluate systems based on OEE specificity to start and expandability to future phase functions as determined by your requirements. Plan to justify the OEE purchase on its own merits.
  9. Go Easy. Make sure the system is easy to implement. Software installation and configuration should take no more than 2 weeks.
  10. Be Simple. Put together a detailed but simple project plan indicating who will do what, how long it will take, and how you will monitor progress.
Read Full Article

Optimize Your Manufacturing Today!

Previous Article BPCS/LX Tip of the Week: 5 Ways to Motivate Your Employees
Next Article Tip of the Week: Gain Efficiency & Save Money - Evaluate Your Production Lines
Print
106635 Rate this article:
No rating

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Tips: LN | Baan

You can move monthly periods to a different parent period. For example, if you have a monthly calendar, you can create quarter periods and move months to the quarters.

  1. Select Financials > Global Ledger > Setup > Finance Enterprise Group > Maintenance.
  2. Open the finance enterprise group.
  3. Click the Calendar tab.
  4. Open the calendar for which you want to move periods.
  5. Click the Hierarchy tab.
  6. Select the periods to move.
  7. Select Actions > Move.
  8. Select the new parent period under which you want to move the periods.
  9. Click OK.

Categories