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 88198 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 71811 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 65326 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 40348 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 40942 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 85547 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.
First114115116117119121122123Last

Tips:  LX | BPCS | M3

This enhancement provides additional views, additional order and line details, improved navigation, and additional capabilities to the IDF Customer Order Inquiry cards and to customer order-related business objects such as Allocations, Customer Invoices, Inventory Transaction History, Promotions, Drop Shipments.

Enhanced Order views based on user roles such as customer service, warehouse/logistics, salesperson/commission, data analysis/management reporting

  • Improved sort, select and filter capabilities
  • Enhanced navigation, data organization and data display
  • Improved customer service access to all transactions throughout the entire customer order life cycle – from quote to order, related invoices, and any RMAs, return orders, related credit memos
  • Improved grouping of related fields
  • New cards to present additional order and order line details
  • Consolidation of cards and card details when appropriate
  • Enhanced Display and Maintain capabilities for drillback to related customer, ship-to, item, carrier, terms, and other master file details
  • Improved display of dates, times and applicable time zones when Region Code time zone support is implemented
  • Multi language Description, Name and Address fields displayed in user’s language, if defined, else in base language

This enhancement provides search capabilities on segment value description in Segment Value List window (WINGSVD).

Segment Value List (WINGSVD):

  • Converted to a standard subfile
  • New action code 10=Search

This makes it easier to locate segment values when defining segment values in Model Account Builder or Alias definition. In addition, WINGSVD has been redesigned as a subfile to enable WebTop grid capabilities.

Last

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tip: MPS planned vs. MRP planned

What items should be MPS planned, and what items should be MRP planned…

Master Scheduled Items are those items that are finished goods, or service items, that receive their requirements either specifically from Independent demand, or both Dependent and Independent demand.

  • Independent Demand is demand that cannot be calculated from higher-level demand in the product structure, and therefore must be either a forecast or an actual customer order (Finished Goods or Service parts sold to customers).
  • Dependent demand is derived from higher-level demand in the product structure. Dependent demand includes components, raw materials, and sub-assemblies. (these are not normally Master Scheduled Items).
  • Service Parts may have both independent demand from forecast and/or customer orders, as well as dependent demand from higher-level demand if that item is also used in other sub-assemblies or products.
  • Cumulative Lead Time is a concept used in Master Production Scheduling (MPS) that combines the “fixed” lead time, and the “variable” lead time needed to produce the product. It is the longest path through a given Bill-of-material. Based on the MPS setup options, your ERP will calculate cumulative lead time (also called “the Critical Path”) for you.

Infor LN does not differentiate between the two. Here, it is simply an enterprise planning EP with one set of planned orders. It is possible to set up items and generate orders at plan levels, but not necessary. In theory, you could make plan level 1 similar to MPS items.

Another way of defining independent demand in LN terms is that it is demand not related to other planned items. Dependent demand comes from related planned items above in the BOM structure.

COLT still exists both in purchase and manufactured planned items. It has both non-critical and critical lead times based on components set as critical. Once calculated it can be used to update the order and planning horizons of a plan item.

Relevant Sessions:

In Baan IV
Maintain Item Data tiitem0101m000
Generate MPS timps3201m000
Maintain Master Production Schedule timps3101m000
Display Planned Inventory Movements by Item timrp1510m000
Display Planned MRP Purchase Orders timrp1521m000

In Baan V
Plan Item Data cprpd1500m000
Item Master Plan cprmp2101m000
Time-Phased Overview cprrp0520m000

In Infor LN
Item – Planning cprpd1100m000
Item Master Plan cprmp2101m000 (same as Master MPS above if used)

Previous Article Infor ERP Tip: Is your Infor ERP system up to date with all of the sales tax changes for 2021?
Next Article Infor LN & Baan Tip: Remove Posted Payment/Direct Debit Batches
Print
49512 Rate this article:
3.8
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories