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 56026 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 53712 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 59118 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 50648 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 26875 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 62351 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 57966 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 65963 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
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Considerations for Release to Warehousing for a Cost Item

When there are two Cost Items, one with Release to Warehousing applied and the other with Release to Warehousing not applied, upon approval of the Sales Order, the Cost Item that is released to Warehousing will go straight to Staged status, pending Shipment confirmation, while the Cost Item that is not released to Warehousing will be up for Sales Deliveries.

Apart from this main difference in functionality between having and not having this option to release to Warehousing checked, there are other impacts to consider. Below is some information gathered from various KBs related to the impact of having release to Warehousing applied (or not). KBs used as reference are listed as “– REF: KB XYZ”. Editing the checkbox “Release to Warehousing” itself If there is a Sales Order (in status Free is enough) for a Cost Item, the check box is not editable. As soon as all the Sales Orders for which the Item is involved are Closed (or Canceled or Deleted) the check box becomes editable again. – REF: KB 1439313 & KB 1613780 Simultaneous/separate release to Warehousing with Physical Items In a scenario where a Cost Item (that is released to Warehousing) and a physical Item are released to Warehousing separately, then the shipment confirmation of each of these Items will occur separately. If they are released simultaneously, the shipment of the Cost Item will not be processed unless and until the physical Item is ready to be shipped. – REF: KB 1449001 Note: Ensure a Warehouse is added to Order Lines to ensure Release to Warehousing Activity is applicable. – REF: KB 2229767 Invoicing

To invoice them separately or together, factors to consider are:

  • Composing Criteria, a list of fields that need to match to have a single invoice created – REF: KB 717977
  • Invoicing Methods (tcmcs0555m000) in the General tab, select Combine, for example, Shipments, to combine different Shipments of the same Sales Order into one Invoice. This Invoicing Method is also defined in
  • Invoice-to role of a Business Partner (tccom4112s000) in the Invoicing tab. – REF: KB 812637
  • For a Return Order where a Cost Item and a Physical Item were originally invoiced together, to invoice them together again, consider using Original Document type = Invoice and link the original Invoice to the Return Order. – REF: KB 2072847 

Note: Consider solution in KB 2108605 if Composing Criteria is met, yet still Credit Notes are not combined for a Return Sales Order copied from original Sales Order for one Physical Item and one Cost Item without release to Warehousing. 

ASN ASN cannot be generated for Purchase Order Lines with Cost Item if not released to Warehousing. – REF: KB 1548301 & KB 2111341 Intercompany Trade Intercompany Trade can be applied for a Cost Item that is released to Warehousing, as Intercompany Trade needs a Warehouse and a Department. – REF: KB 2112430 Customs Value Cost Items that are released to Warehousing that are handled via normal Sales Order Lines are considered as delivered goods and will get the customs value assigned like other Items being subject to warehouse handling. Cost Items handled on Shipment Lines as "Additional Cost" are not considered as delivered goods but as pure costs. The customs value of these shipment lines gets defaulted with a zero amount and cannot be modified. The same applies to additional costs on sales order lines. – REF: KB 1600847 Freight  Cost Items cannot be used for Freight handling. – REF: KB 1830170 Additional Cost

  • For automatically generated Additional Costs in Sales Orders, Cost Items that are released to Warehousing are not released to Warehousing. This is because automatic Additional Costs are always generated with 0 quantity, therefore only the amount is filled for these Lines, which leads to the Delivery Type being set to Sales and not Warehouse. As a result, delivery must take place in Sales module. – REF: KB 1995781
  • For Additional Cost Lines added to Shipment for Cost Items, refer to KB 2236856.

Intrastat Record When using Cost Items without release to Warehousing, there is no shipping data within Invoicing. Therefore, the corresponding Intrastat record cannot be found during the printing of the Invoice. To get the Invoice data filled on the Intrastat record, Cost Items with release to warehousing should be used. Otherwise, session Update Intrastat Transactions with Invoicing Data (tccom7271m100) should be ran to update the Invoicing data in Intrastat. – REF: KB 2005482

Previous Article Infor LN & Baan Tip: What conditions must exist before changing an item's inventory unit?
Next Article Infor LN & Baan Tip: Cash Flow Functionality and Setup
Print
52626 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories