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 56053 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 53746 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 59153 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 50680 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 26881 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 62371 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 57993 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 65988 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 Tips & Tricks for EXECUTIVES:

Operations: Copying EBOMs - Which copying method should I use?

To determine which copying method you must use, answer question 1 and follow the instructions.

Question 1: Is the source component a project item (that is, is a project defined in the first segment of the item code)?

  • If the answer is yes, proceed with question 3.
  • If the answer is no, proceed with question 2.


Question 2: Is the target component a project item?

  • If the answer is yes, select copy method NonProj Item to Proj Item.
  • If the answer is no, proceed with question 4.

Question 3: Is there a relationship with the same project?

  • If the answer is yes, select copy method EBOM to Production BOM Only.
  • If the answer is no, proceed with question 4.


Question 4: Is there a relationship with the target item?

  • If the answer is yes, proceed with question 5.
  • If the answer is no, select copy method No Copy Action.


Question 5: Does the item exist already?

  • If the answer is yes, select copy method EBOM to Production BOM Only.
  • If the answer is no, select copy method Copy E-Item to Item.

Technology: Using audit files in the Exchange module

The audit server logs all database actions that change the contents of a table in so-called audit files. The Exchange module can use these audit files, which are useful in a multisite environment because the databases on all sites must have identical data. These audit files can also be used in data conversions.

Only the updates in a specific period are exchanged, which leads to an improvement in performance. Specify this period in the Export Data (Non-Regular) (daxch0233m000) and Export Data (on a Regular Basis) (daxch0234m000) sessions. Changes such as insert, update, and delete are processed and written into the ASCII files. Actions such as drop, clear, and create tables are ignored.

Audit control data is added to the resulting ASCII file. This data consists of a batchline ID, transaction ID, sequence ID, and an indicator. The control data is added at the beginning of each line and is formatted like other data fields such as the enclosing and separator characters.

An update writes two lines to the ASCII file. One line contains the key fields and old values of the updated fields. The other line contains the new values of the key fields and updated fields, even if a key field does not change.

The batchline ID is used for recognition when processing the ASCII files. The transaction and sequence IDs are used to ensure that the transactions are replayed in the same order as on the exporting site. The indicator defines the type of action that is executed on the table. Use the letter I to insert; use the letter D to delete; use the letter U to update with old values; and use the letter N to update with new values.

Finance: Problem Invoices

You can use a problem code to indicate that a problem exists for a sales invoice. If the invoice-to business partner notifies you about a problem with the invoice and does not pay it, you can link a problem code to the invoice.

In the direct debits procedure, problem invoices are automatically discarded. For each problem code, you can set an option to prevent linked invoices from being selected on reminder letters.

Previous Article Infor LN & Baan Tips & Tricks: Action Required - Infor LN Cloud Edition - Fonts Update!
Next Article Infor LN & Baan Tips & Tricks for Operations: Copying EBOMs - Which copying method should I use?
Print
49772 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories