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

Baan/LN Tip of the Week: Plan Codes

Kathy Barthelt 0 39922 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 36189 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.

Baan/LN Tip of the Week: Purchase Inquiry

Kathy Barthelt 0 46104 Article rating: No rating

In Baan IV Purchase Control, the purchase inquiry procedure enables the user to:

  • Request a specific supplier to submit a quotation on the purchase inquiry for the delivery of an item.
  • Compare the prices and discounts of the quotations that are submitted by different suppliers.
  • Copy the inquiry data to a purchase order.


In LN, you can:

  • Request multiple business partners to submit a quotation on a specific request-for-quotation for the delivery of an item.
  • Compare the received quotations based on the following criteria:
  1. Price
  2. Quantity
  3. Vendor rating
  4. Delivery dates
  5. RFQ subjective criteria
  • Copy the quotation data to a purchase order, a purchase contract, or a price book.
RSS
First133134135136138140141142Last

Theme picker

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Warehouse Material Movement / Problems With the Inventory Structure Table (whinr150)

This has come up as an issue during various stages of warehouse material movements – transfers, outbounds, shipments. We have seen it right up to 10.4. The inventory structure table (whinr150) becomes a problem. The error points to that table, but users are lost as to how to fix it.

In the session Units by Unit Set many companies let the field Storage default to Yes. If the UOM is not intended to be used in inventory then that setting should be No. 

If an item is purchased in UOM different from the inventory unit and the setting is Yes then LN adds a record in that UOM to the inventory structure table. It is that record that causes problem later.

The session has an option to change the value of the storage field. Specific > Convert Use for Storage. This option works both ways and will correct all inventory in the UOM range. 

Should a user receive an error that references inventory structure table then the solution is to check that session to see if an odd UOM exists in it. If so use the Convert Use for Storage to correct the problem.

Previous Article Baan/LN Tip: Disabling Unused Functionality in LN
Next Article Baan/LN Tip: New Mapping Scheme
Print
36505 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories