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 86863 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 71543 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 64682 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 40298 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 40888 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 84260 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

George Moroses
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip: System i Workspace AnyWhere information and Important Support Dates for IBM and Microsoft Products

System i Workspace AnyWhere is a web application framework that provides a common user interface for Infor’s IBM i products.

*** We strongly recommend that you subscribe to this KB to receive automatic notification when it is updated ***

Latest Updates
System i Workspace AnyWhere - Feature Pack 22 is now available - see the Update History section below (as of January 4, 2024)

  • Tomcat 9.0.80 Upgrade Installer Released - see the Update History section below (October 9, 2023)
  • Installer Hotfixes - affects both Silver Copy and Tomcat Upgrade Installers (August 17, 2023)
  • Removed Support for Microsoft Windows 8.1 (January 11, 2023)
  • System i Workspace AnyWhere - Silver Copy Build 220930 FP17 (Microsoft Windows 2016/2019/2022 Server - Tomcat 9) has been released (October 6, 2022)
  • System i Workspace AnyWhere - Silver Copy Build 220930 FP17 (IBM i OS/400 - WebSphere Application Server 9) has been released (October 6, 2022)
  • Added support for IBM OS/400 V7R5 (October 6, 2022)
  • Removed Support for Internet Explorer (January 11, 2022)
  • Removed Support for the System i Emulator and Update Manager (January 11, 2022)
  • Removed support for IBM OS/400 V7R2 (July 16, 2021)
  • Removed support for Mozilla Firefox web browser (March 30, 2021)
  • Added support for Microsoft Windows Server 2019 (May 18, 2020)
  • Added support for IBM OS/400 V7R4 (November 28, 2019)

Documentation

  • System i Workspace AnyWhere - Installation & Admin Guide (December 15, 2023)
  • System i Workspace AnyWhere - FAQ (December 4, 2023)
  • System i Workspace AnyWhere - Feature Pack Release Summary (December 4, 2023)
  • System i Workspace AnyWhere - Product Guide (August 30, 2023)
  • System i Workspace AnyWhere - InforOS Integration Guide for System21 (August 31, 2023)
  • System i Workspace AnyWhere - Quick Install Guide (September 13, 2022)
  • System i Workspace AnyWhere (IBM i) - Quick Install Guide (August 25, 2022)
  • System i Workspace AnyWhere - Release Summary (March 3, 2023)
  • System i Workspace AnyWhere - SSO MustGather & Troubleshooting (March 3, 2023)
  • System i Workspace AnyWhere - Load Balancing Guide (August 31, 2023)
  • System i Workspace AnyWhere - 5250 AnyWhere Emulator Designer Guide (December 4, 2023)
  • System i Workspace AnyWhere - 5250 AnyWhere Emulator Extensions Guide (June 6, 2023)
  • System i Workspace AnyWhere - Drillback Guide (August 31, 2023)

 

Release Notes

Withdrawal of support for legacy Operating Systems and Products from IBM and Microsoft

Support for the following Operating Systems with System i Workspace AnyWhere has now been withdrawn...

  • IBM OS/400 V7R2 (support ended by IBM on 04/30/2021)
  • Microsoft Windows 8.1 (extended support ended by Microsoft on 10/01/2023)

The System i Workspace AnyWhere documentation has been updated to reflect the removal of support for these Operating Systems.

Advance Notice of 3rd party vendor end-of-life (EOL) dates:

  • Microsoft's retirement date for Windows 10 is 10/14/2025
  • Microsoft's extended support for Windows Server 2016 will end on 12/01/2027
  • IBM's standard program support for IBM i 7.3 ended on 09/30/2023 (extended support available until 09/30/2026)  

Note: An official statement from Infor in relation to our support will be made nearer the EOL date of each product.

Print
23971 Rate this article:
2.5
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories