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: Performance improvement by setting the First Free Number Cache (tcmcs0651m000)

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:

  • Processing warehouse transactions. Single or in-batch
  • Completing / closing orders
  • Backflushing of production orders
  • Generate Order Planning
  • Cost calculation and warehouse revaluation


How this performance can be improved?

Resolution

In the Number Groups (tcmcs0151m000) session you can open the details of a specific Number Group (tcmcs0651m000) or start the session stand-alone.

In the Number Group, you define the Series with the related First Free Numbers. Per Serie in the First Free Number, you have the option to define the Cache Size.

This Cache size is defaulted on a value of 0 (zero). A cache size of zero means No Cache. How does the First Free Number caching works:

  • When the Cache Size is zero: With this setting a process requests a Free Number from the Serie and the first free number is issued to the process. But the first free number record is not updated yet. At the moment the requesting process is finished, without errors, it reports back that the number is used and the first free number record is updated. All the time that the process is working on the transactions the first free number record is locked. If another process is requesting a free number from the same series, it must wait (retries) until the record is updated and released by the previous process. This is the locking which is causing delays in the other processes.  
  • Setting the Cache Size to a higher value then zero activates the caching. When the Cache Size is set to 1 or higher, the requested free number is sent to the requesting process, the first free number is updated, with the number as defined in the Cache size, and the record is saved. It does not wait until the requesting process has reported back that is finished, with or without errors. In this way the record is immediately released and no locking will occur. If another process is requesting a free number, it does not need to wait until the free number record is released by the earlier process. If the process is ended with errors and therefor the number is not used, this number from the series is lost. This can result in gaps in the numbering. When the cache size is greater than 1, for example it is set to 5, the requesting process receives 5 free numbers. Even if it only needs less than 5. In this way the process only has to request for a new free number after it has used the first 5 numbers from the cache. This will also speedup the process in case of large batch transactions. For ‘warehouse integration users’, like for example Factory Track or WMS users we advise to set the cache size to 5.  

Note that financial documents are not based on number group series / first free numbers. Instead they are based on transaction type series, for which the caching functionality does not exist. Financial documents, like sales invoices, bank transactions, are thus not cached.

The caching is especially important to improve the performance of all logistical processes.

It is strongly recommended (mandatory) to set the Cache Size for all Number Groups to a minimum of 1.

Previous Article Infor LX & BPCS Tip: Automated Approach to Your Cash Application Process with ARP
Next Article Introducing VJES (Visual Job Execution Software)
Print
10802 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

Are you on the latest porting set for your version of Infor LN or Baan? Check here to be sure:

VERSIONS: Infor LN, Infor Baan ERP 5.0c, Infor Baan IVc4

LAST MODIFIED ON:
13th Jan, 2021: Updated with 9.3i porting set, see KB 2176336 for this version. Available from LN CE release 2021.01
9th Oct, 2020: Updated with 9.3h porting set, see KB 2158949 for this version. Available from LN CE release 2020.10
9th July, 2020: Updated with 9.3g porting set, see KB 2142625 for this version. Available from LN CE release 2020.07
10th April, 2020....

Serial and Lot are additional characteristics/properties of Items that can be used to uniquely or collectively identify and track the item along with its Item code. Any Item can be made as Serialized and/or Lot controlled by choosing options "Serialized" and "Lot Controlled" in Items-General session under traceability section on the Details tab.

Further in Items-Warehousing data under the Identification tab, you can enable "Lot Tracking", "Lot in Inventory", "Serial Tracking" and "Serial in Inventory" which enables tracking of the Items. You can also define if the Item is "Serial/Lot not in inventory" then where you want to record the serial and lot details in the transactions like "Direct Delivery", "Receipt", "Transfer", "Register during As-Built, Service and Maintenance".

Below are some topics related to Serialized and Lot Controlled Items that will be useful...

First3940414244464748Last

Theme picker

Categories