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: Alternate Items

Anthony Etzel 0 56040 Article rating: No rating
How can I use an alternate item on a shop order?

The best way is to have the approved alternate item appear on the Bill of Material just after the standard item with a zero required quantity. Now the alternate item will appear on the Shop Order. So, if the standard item is not available, the alternate item can be issued to the shop order.

When the shop order is closed out, one item will have an unfavorable variance while the other shows a favorable variance. This is an easy way to provide alternate items provided engineering approves and they are part of the Bill of Material.

Baan/LN Tip of the Week: Negative Inventory

Kathy Barthelt 0 53718 Article rating: No rating

If Location Control is turned on in Baan IV, then inventory should never be negative.

If Location Control is not turned on in Baan IV, and the parameter “Negative Inventory Allowed” in INV Parameters is set to “NO”, then inventory should never be negative.

In Baan V and LN, the parameters in Inventory Handling Parameters determine whether you can have negative inventory. If these parameters are set to “NO”, then inventory should never be negative.

BPCS/LX Tip of the Week: User Defined Transactions

Anthony Etzel 0 59126 Article rating: No rating

When to use a user defined inventory transaction

ERP LX (BPCS) provides you with the flexibility to create inventory transactions without program modifications. The typical transaction types are defined with effects set on how the transaction will impact inventory balances.

Perhaps you want to process a customer return and don’t want to the inventory to be impacted. You can create a user define transaction effect to allow the customer receipt and not update the inventory balance.

Baan/LN Tip of the Week: Old Porting Set

Kathy Barthelt 0 50657 Article rating: No rating

Here are some issues that you might run into if you stay on an old porting set too long:

  • Incompatibility because of operating system patches
  • Printing issues because of out-of-date libraries
  • Potential performance issues if binaries are not updated
  • Updating third-party products may not be possible because of dependencies
  • Limited support from Infor
  • Issues with updating database software/patches because of dependencies (if the database is also running on the same server as the application)

Need help getting on a newer porting set? Let us know! We’d be happy to help.

Crossroads MES Released for Windows 10

Anthony Etzel 0 26876 Article rating: No rating

Crossroads RMC is pleased to announce the availability of Crossroads MES, V11 for Windows 10. Any customers wishing to upgrade from a previous version to V11 can do so by contacting  support@crossroadsrmc.com. As previously announced, Crossroads MES  is also compatible with tablet PCs running Windows 8.1. Tablet PCs are becoming the clipboard replacement for supervisors and managers to monitor what’s happening on the shop floor.

BPCS/LX Tip of the Week: Shop Order Release Date

Anthony Etzel 0 62357 Article rating: No rating

The shop order release date is the date that the shop order is scheduled to be released for production.

If you want to use the backward schedule method, make sure the release date is blank and the due date is maintained.

If you maintain the quantity on the shop order and the due date is prior to the system date, the due date and the release date are the same.

Baan/LN Tip of the Week: Plan Codes

Kathy Barthelt 0 57981 Article rating: No rating

In Baan IV, plan items exist within the context of a plan code. A plan code includes only items of the MPS Item item type. Planned orders are independent of a plan code. Users can compare plan codes by means of the Plan Code Performance Comparison (cprmp4504m000) session.

The scenario concept in Infor LN replaces the plan code concept in Baan IV.

In Infor LN, the basic data for plan items is the same for all scenarios. However, users maintain not only the master plan within a scenario, but the planned orders as well.

For example, for each scenario, Users can specify:

  • Special demand for an item.
  • The availability of resources (in the Scenario – Availabilities (cprpd4160m000) session).
  • The sourcing strategies and supply strategies.

Users can compare scenarios by means of the Performance Indicators (cprao2201s000) session.

BPCS/LX Tip of the Week: Receiving to Inspection

Anthony Etzel 0 65974 Article rating: No rating

If the item being received needs to be inspected prior to being available for use, there are two schools of thought.

The first is to receive the item to a QC hold location. The downside is the item will show up in on hand inventory.

A better method would be to do a PO receipt to inspection. Both Inv500 and Pur550 support this method. Now you have received the item without showing it in inventory. Only the PO quantity in inspection is updated. This method also allows you to create an Inspection Dispatch Report. After the QC process for the item is complete, then the transaction Receipt from Inspection to Stock is processed. That transaction then updates the PO quantity received field and the Item on hand field in inventory.

First106107108109111113114115Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

Kathy Barthelt

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
59416 Rate this article:
2.5
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories