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 40090 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 36356 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 46259 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

​Infor LN & Baan Tip: Determining What Data to Archive or Delete

Ensuring access to historical logistical and financial transaction information for your employees is crucial. However, before proceeding with archiving or deletion, it's essential to evaluate the necessity of retaining this data. Baan and Infor LN (ERP LN) offer standard archiving sessions within major modules that typically handle a significant volume of historical transactions. These sessions are designed to transfer historical data to an archive company before deleting it from the operational company.

When it comes to archiving sessions, you have three primary options:

  1. Archiving and Deleting: Data is transferred to the archive company and then deleted from the operational company.
  2. Deleting: Data is directly removed from the operational company without archiving.
  3. Archiving Only: Data is moved to the archive company without deletion from the operational company.

It's important to note that options 1 and 2 result in irreversible actions. However, with option 3, where Archiving Only is selected, multiple archiving processes can be executed for previewing results.

Additionally, during archiving sessions, you can typically specify:

  • The cutoff date for the data to be archived.
  • Whether accompanying texts should also be archived.
  • Whether existing texts in the archive company should be replaced.

For more detailed information on archiving procedures, you can refer to the Baan IV and Infor LN documents provided.

Previous Article Infor LN & Baan Tip: Performance improvement by setting the First Free Number Cache (tcmcs0651m000)
Next Article Infor LN & Baan: Customizing Shipping Labels for All Customers
Print
8372 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories