Infor ERP Tips and Infor ERP News for Infor LX, BPCS, Infor ERP LX, Infor LN, Infor ERP LN, Baan, Infor M3, and Movex

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 Day: Company Calendar

Kathy Barthelt 0 159289 Article rating: 5.0

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

  • Master Production Scheduling
  • Material Requirements Planning
  • Capacity Requirements Planning
    (All three combined in a single planning module for Baan V and LN)
  • Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.

BPCS/LX Tip of the Week: Cycle Counting Part 1

Anthony Etzel 0 86853 Article rating: No rating

Understanding: The Cycle Count Transaction

If you rely on BPCS to provide you with a cycle count list, the number of items could vary from day to day from a few items to count, to several. So the person doing the cycle counting may spend a few minutes to a few hours counting items. After the cycle count is complete, the balances are not changed until the reconciliation is complete. This process could take some time before the balances are changed.

The cycle count transaction process is similar to the physical inventory transaction process.

Baan/LN Tip of the Week: GRINYA

Kathy Barthelt 0 178537 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 86583 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 82866 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 42950 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.

First128129130131133135136137Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

George Moroses

Infor LX/BPCS Tips & Tricks for EXECUTIVES

TECHNICAL: Synchronize users from LX to SiM in batch

This enhancement improves performance by submitting to batch the automatic synchronization of changes from LX user maintenance (SYS600) to System i Manager (SiM). During LX user maintenance, there are now three possible approaches to synchronizing the LX user changes to SiM, controlled by system parameters. Synchronizing LX user changes to SiM in batch allows the person executing SYS600 to continue with additional maintenance or other transactions without waiting for the synchronization to finish.


FINANCE: Inventory Transaction History to Ledger Book Journal Line Relationship

This enhancement provides IDF relationships from Inventory Transaction History (ITH) to Ledger Book Subsystem Transaction (GXR) and from Ledger Book Subsystem Transaction (GXR) to Ledger Book Journal Line. To implement this enhancement, request and apply MR 81558.

This enhancement provided the following relationships:

  • Inventory Transaction History
  • Relationship to Ledger Book Subsystem Transaction (1 to Many) Default view ‘General’
  • Ledger Book Subsystem card Default view ‘Inventory Processing’
  • Default subset ‘Inventory Processing’

This enhancement provides users with complete traceability from inventory transactions (ITH) to ledger book journal lines (GLH), regardless of how many ledgers are used and journals created. Due to the bi-directional relationship, users can see the source ITH detail from the journal lines.

OPERATIONS: Infor Business Context (IBC) messages for INV500 

This enhancement adds publication of IBC messages to additional LX screens. While entering data on the primary screen for inventory transactions, IBC message are now published and available for use in Ming.le contextual applications.

Print
1918 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories