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 Day: Multi-Company Taxation – LN

Kathy Barthelt 0 278 Article rating: No rating
Tax reporting is part of the financial accounting and is restricted to one country. Therefore, the LN tax handling in a multi-company structure is similar to the tax handling in a single company environment.

Tax handling in LN includes the following:

· Tax registration

For tax registration, you define the various tax details for each country in the Taxation module. In the General Ledger module of Financials, you specify the ledger accounts for the tax amounts separately for each financial company. LN can post the tax amounts calculated for a tax code to different ledger accounts in the individual financial companies, for example, in a single logistic, multi-financial company structure.

BPCS/LX Tip of the Day: Accounts Payable / Purchasing

Anthony Etzel 0 981 Article rating: No rating

You can integrate Accounts Payable (ACP) with Purchasing. ACP requires more detailed information in the Vendor file than Purchasing requires. Accounts Payable automatically checks for a valid purchase order when you

match invoices to POs and receipts. Enter any outstanding active purchase orders through PO Release, PUR500, before you can match invoices in Accounts Payable.

 

Accounts Payable can also update the Actual Cost fields in the Inventory Master file directly from vendor invoices. You must provide the following information in order for Accounts Payable to complete this update:

▪ Define a type C inventory transaction.

▪ Enter a valid purchase order on the Invoice Entry header screen, ACP500D2-01, or in the Next Purchase Order field on the Invoice Entry: PO Costing screen, ACP500D3-01.

▪ Enter the information for the actual cost transaction on the appropriate lines.

Baan/LN Tip of the Day: Virtualization

Kathy Barthelt 0 47271 Article rating: No rating

The advantages of virtualization include the following:
 

• You get more out of your existing resources. Pool common infrastructure resources and break the legacy “one application to one server” model with server consolidation.

• You can reduce datacenter costs by reducing your physical infrastructure and improving your server to admin ratio. Fewer servers and related IT hardware means reduced real estate and reduced power and cooling requirements. With better management tools, you can improve your server to admin ratio so personnel requirements are reduced.

• You can increase the availability of hardware and applications for improved business continuity.

• Securely back up and migrate entire virtual environments with no service interruptions. Eliminate planned downtime and recover immediately from unplanned issues.

• Gain operational flexibility. Respond to market changes with dynamic resource management, faster server provisioning, and improved application deployment.

 

The disadvantages of virtualization include the following:

 Virtualization adds overhead to the CPU, memory, IO, and network.

 Virtualization adds an additional layer to the hardware and software stack. Therefore, additional complexity is introduced in the following circumstances:

CST Industries Goes Live With LN Ecommerce Site for Dealers

Crossroads RMC 0 29968 Article rating: No rating

Crossroads RMC has partnered with Xenitel Managed Service Solutions and CST Industries to create an online parts ordering site for CST’s dealers. The site is live as of June, 2015. This site was developed largely to simplify the ordering process for CST’s dealers, providing information on available inventory, flexible ordering, fast shipments, and improved dealer support.

 

CST is a global leader in the manufacture and construction of factory coated metal storage tanks, aluminum domes and specialty covers.

Baan/LN Tip of the Day: First Free Numbers

Kathy Barthelt 0 316 Article rating: No rating

In Baan IV, users define series and numbers in the Maintain First Free Numbers (tcmcs0147m000) session. In the Type of Number field, users must select the type of documents for which the series will be used. The generated document numbers are always numeric and can consist of up to six characters.

 

In LN, users must define number groups in the Number Groups (tcmcs0151m000) session and then in the First Free Numbers (tcmcs0150m000) session, define the series and numbers of each number group. Users assign the number groups to various purposes in the corresponding sessions. For example, in the Sales Order Parameters (tdsls0100s400) session, users can select the number group for sales orders and sales schedules. In the Sales Offices (tdsls0512m000) session, users can then select a series of that number group for the sales orders generated by a specific sales office. As the series codes can be alphanumeric, the generated document numbers can be alphanumeric and they can consist of up to nine characters.

BPCS/LX Tip of the Day: Material Requirement Dates and Lead Time Offsets in MRP

Anthony Etzel 0 343 Article rating: No rating

The system automatically performs offsets for requirements dates for components in the MPS/MRP calculations. It also performs offsets for calculation of material need dates at the time that shop orders are released.

To calculate the offset, the system takes the parent lead time from the Item Master and adjusts it by the bill of materials offset (plus or minus) for the component. This gives the lead time days for that specific component. The system starts with the due date of the parent and backs up and skips all non-work days in the shop calendar.

 

Note that the offset calculation uses only calendar records that have a blank work center (the calendar record applies to all work centers). See the information for the Shop Calendar Maintenance program, SFC140, in your Shop Floor Control documentation for shop calendar details.

Baan/LN Tip of the Week: Database Sizing – Moving to LN

Kathy Barthelt 0 219 Article rating: No rating
The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.
First110111112113115117118119Last

Tips:  LX | BPCS | M3

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

  • When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

This enhancement improved the subfile utilized in MRP320D Master Schedule Detail Inquiry -SCR001 by expanding the subfile with data rather than clearing the subfile as user pages. This change provides full support for the WebTop 4.8 Grid decorator.

This enhancement updated the approach used to populate the subfile to allow a deployed Webtop Grid to function correctly. There is no visible or user-impacted change to the way the program functions.

This enhancement provides improved functionality and full support of a Webtop grid applied to the subfile.

Last

Tips: LN | Baan

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 & Infor LN / Baan Tip: A New Wave of Cyber Attacks: Five Actions to Take Now
Next Article ​Infor LN & Baan Tip: Determining What Data to Archive or Delete
Print
23600 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories