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 56058 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 53764 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 59155 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 50694 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 26882 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 62377 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 58022 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 66001 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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Day: LX Inventory Pallet Status Flow

Four fields in the Item/Warehouse record (IIW file) affect the disposition of the

pallet status.

 

1.  Goods Receiving Code: You define these codes in Goods Receiving Maintenance (WHM130). The codes control whether or not the stock passes through inspection, what percentage, or quantity of a delivery to inspect, and the number of quarantine days, if any.

 

2.  Inspection Zone/Inspection Location: Either the Inspection Zone or the Inspection Location must be entered on the Item/Warehouse Master Maintenance screen WHM150D2-01.

 

3.  Default Inventory Status: If the status is 0 (Received) or 1 (Inspection), the item moves from the receiving location to the inspection location in inspection status. If the pallet status is not 0 or 1 (that is, 4 (Available) or 9 (Rejected)), the pallet moves to the inspection location with the default status, but the pallet will not proceed from the Inspection location to the Putaway location. You must manually move the stock.

 

4.  Pallet Status Codes: 0 (Received), 1 (Inspection), 4 (Available), and 9 (Rejected) are the only pallet status codes reserved by the system to update and advance inventory/pallet status. To do this Warehouse Management uses the following rules:

 

·    Rejected inventory goes from receiving to a Reject (type 9) Location with a Location Type A (Rejected) in the Location Extension file (ILE) record. All inventory received into a reject location is set to a pallet/inventory status of Reject (9).

·    Inventory received by Goods Receiving (WHM510) into a Receiving Location takes on the Default Inventory Status that is in the Item Warehouse file (IIW) record.

·    If the Default Inventory Status is 0 (Received), the system places the pallet status at 0 (Received) in the Receiving Location, I (Inspection) in the Inspection Location, and 4 (Available) if moved from Inspection to any palletized location other than rejection. If moved to rejection the Default Inventory Status changes to 9 (Rejected).

Print
50016 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Categories