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 109593 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 81620 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 76365 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 41003 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 42220 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 109425 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

Tips: LN | Baan

Anthony Etzel

How to Improve Customer Shipments With OTTO - A Case Study

Setting Industry Service Standards

Shenandoah Manufacturing, a $20 million producer of poultry-raising equipment (heaters and brooders), had been having difficulty for some time shipping orders to customers in a timely manner. They had successfully implemented a popular ERP system and had been using it for more than 3 years, yet the situation didn't improve. 

Customer Service Representatives were complaining about the frequent backorders and late orders. Employees were giving it their best effort, but were frustrated, and customers were threatening to take their business elsewhere.

The company considered installing an APS system as a possible solution, but found implementation would be difficult, expensive, and running the system might be a challenging task as a number of key business practices would have to be changed. A consultant familiar with OTTO suggested they look at that product as an alternative to APS. Several OTTO aspects cited by the consultant convinced them to consider a cursorily review. Specifically:

  • The non-intrusive nature of the product.
  • It's relative inexpensive initial investment.
  • The low overall total cost of ownership.
  • The integration with their ERP system.

The initial demonstration was impressive. OTTO was installed on Shenandoah's server within 45 minutes of arrival and, most impressively, it was fully functional with their real “live” data immediately. Needless to say, the demo was well received. Even more importantly Shenandoah was able to “test drive” the software to prove its applicability before making any dollar commitments.

According to Mark Shank, Information Systems Manager, some baseline measurements were made last year, and it was determined that approximately 50% of their customer orders had shipped on time. As they began using OTTO, on-time order performance rose to 90% for the month. And Shenandoah caught up on its entire backlog and started working ahead on February's orders. In February on-time shipment performance jumped to 92% and subsequently on-time performance has ranged somewhere between 98.3% and 99.5% — well above the 96% goal set by Management.

OTTO provides the means for keeping the whole production organization focused on the few things that have to happen as the ship date approaches to get each order shipped on time. Components that have the potential for delaying an order are identified so they can be managed. Shenandoah's staff, a precious and limited resource, now concentrates on analyzing information and managing the right things at the right time rather than digging out date. To quote one production control individual: “what use to take hours now takes seconds.”

According to Roy Hackett, Plant Manager: "Knowing the right things to pay attention to at the right time — information provided by OTTO — has allowed on-time shipping to be improved by 40 percentage points in less than one month and a lead time reduction from 3-4 weeks to 1-2 weeks on the most important products"

Guessing at what and how much of the work being processed is for real customer orders versus planned orders is eliminated which is especially important when capacity is short during the heavy portion of the business cycle. 

“By focusing on the right things at the right time, production expedites and interruptions are far fewer, production flow is much smoother and productivity is significantly improved.”

Print
30956 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Categories