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

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

Anthony Etzel 0 88354 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 184976 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 89015 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 84143 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 43812 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 44629 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.

First129130131132134136137138Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Infor LN & Baan Year-End Processing Checklist for Period and Fiscal Year Closure

The conclusion of the fiscal year is inevitably a hectic period, making it crucial not to overlook essential tasks within your ERP system to ensure a seamless year-end close and set the stage for a successful start to the upcoming year. Below are critical items to include in your comprehensive checklist:

Year-End Close Process:

  1. Remove discontinued items.
  2. Eliminate sold purchase receipts.
  3. Clear lot attributes for sold lots.
  4. Update standard cost based on the current cost field (for environments without Manufacturing only).

Prepare for Year-End Close:

  1. Conduct a comprehensive physical inventory and update quantities before the actual year-end or establish a robust cycle-counting program.
  2. Review and post any applicable sales and purchase invoices/returns.
  3. Prepare users for a year-end push to complete all year-to-date inventory adjustments, receipts, and invoicing.
  4. Determine procedures for handling new year transactions without immediate posting.
  5. Establish new standard costs for the upcoming year (Manufacturing).
  6. Discuss cutoff dates for removing Archived BOMs and Closed/Canceled Mfg Orders (Manufacturing).

Finance Specific Items:

  1. Set up financial periods for 2024 (fiscal, reporting, and tax, as applicable).
  2. Open January period in 2024.
  3. Finalize any outstanding transactions from the current year (2023).
  4. Perform a soft-close for any open periods in 2023.

General Baan/LN Tips:

  1. Issue any pending old sales invoices.
  2. Resolve outstanding financial integration errors.
  3. Establish new integration mapping for 2024 as needed.
  4. Test the mapping in a controlled environment before the new year.
  5. Review and update jobs to ensure they will process in 2024.
  6. Determine, for cash-flow purposes, which purchase invoices won’t be paid until 2024.
  7. Verify that calendars are set up for the new year with holidays correctly indicated.
  8. Check jobs to ensure that any with hard-coded dates will point at the new year.

For additional insights and tips on year-end processing, refer to the relevant documents in the Infor Knowledge Base.

 KB 

 Content 

 1879191  

 Document including step by step procedure, possible error/warning messages, and more (Infor LN) 

 1147023 

 Step by step procedure description (Infor LN)

 1116239 

 Step by step procedure description (Infor LN)

 1117334

 Step by step procedure description (Infor LN; Portuguese)

 1171300 

 Step by step procedure description (Baan IV) 

If you require assistance or have any questions, feel free to reach out to us, and we'll gladly guide you through the necessary steps to ensure a thorough and accurate completion of your year-end processes. Contact us at 1.800.762.2077 or via email at solutions@crossroadsrmc.com. Your success is our priority, and we're here to help.

Previous Article Infor LN & Baan Tip: When is backflushing disabled in LN?
Next Article Infor LX / BPCS & Infor LN / Baan Tip: Time for the Notorious TRIO: Manual -  Physical -  Inventory
Print
72767 Rate this article:
2.5
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories