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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: What conditions must exist before changing an item's inventory unit?

Is there a procedure for changing an item’s inventory unit? What conditions must exist before it can be done?

Once inventory transactions (receipts or issues) have occurred for an item, the inventory unit cannot be changed. If only orders have been placed against the item (sales or purchase), the inventory unit can be changed if these orders are removed and the economic stock of the item is zero.

The reason that the inventory unit cannot be changed once transactions have been made is due to how transactions are recorded. The inventory transactions are recorded in units. These units are the inventory unit of the item. The inventory unit is not held in this table, however. The inventory unit is held on the item data. For example, if 5 pieces (pcs) of an item are issued and the inventory unit is later changed to pounds (lbs), there will be a mismatch in the inventory history of the item. In the past, the item was issued as pcs, and now the item master inventory unit is lbs. As the inventory unit is not date effective, the inventory has then been issued in two different units (pcs and lbs), but there is no method to recognize this difference.

Previous Article Infor LX & BPCS Tip: 4 Approaches to Customizing LX / BPCS - Preparing for a Future Upgrade
Next Article Reskilling and Upskilling Your Staff – Why You Shouldn’t Ignore This
Print
15322 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

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:

Many transactions in all kinds of modules use order numbers or serial numbers. These order numbers are most often automatically generated. In the Number Groups (tcmcs0151m000) session you can define groups of order numbers used for dedicated areas. A Number Group is a group of the first free number series that you can assign to a specific use. All the numbers that Infor LN generates in the number groups that are dedicated to the same purpose are unique.

All the first free numbers are stored in the table tcmcs050.

As many different processes can request a free number from the number groups, we often see delays in the performance, due to locking on the first free number records. This locking issue can have a severe impact on the performance of huge batch-type transactions, but also on the performance perceived by individual users in many areas in LN.

For example:

First89101113151617Last

Theme picker

Categories