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

Crossroads RMC, in partnership with Infor, takes Yupo to LX 8.3.4

Crossroads RMC 0 25484 Article rating: 5.0

Yupo Corporation, a leader in synthetic paper, with products that are 100% recyclable, waterproof and tree-free, went live on Infor LX 8.3.4 on April 3, 2017. Yupo partnered with Crossroads RMC for this important technology upgrade. Included in the implementation were the Finance, Supply Chain, Manufacturing and Plant Maintenance (EAM) modules.

Crossroads RMC Takes Polar to LX 8.3.4

Crossroads RMC 0 27809 Article rating: No rating

Polar Beverages, the largest independent soft drink bottler in the United States, went live on Infor LX 8.3.4 on January 16, 2017. Polar partnered with Crossroads RMC for this important technology initiative. Included in the implementation were the Finance Supply Chain and Manufacturing modules. Phase 2 will include Adirondack Beverages, a subsidiary of Polar. This project will begin in Q3 2017.

BPCS/LX Tip of the Week: Handwritten Inventory Tickets

Anthony Etzel 0 21249 Article rating: No rating

Are you still using handwritten tickets for your inventory?  This method of inventory tracking is slow and prone to human error.

Putting a simple barcode system in place speeds up the process of tracking inventory movements, reduces the likelihood of mistakes, and creates a recorded history of the who/what/where that can provide valuable insight to those who make critical business decisions for your business.

Not sure where to start? Contact us and we’d be happy to help you take the first step.

Baan/LN Tip of the Week: Ledger Default Account

Kathy Barthelt 0 34339 Article rating: No rating

If you do not wish to define a detailed mapping to various ledger accounts for specific integration transactions, you can map the corresponding integration document type to a default account. All the transactions of the integration document type for which an account cannot be determined based on the mapping scheme details, are posted to the default account.

 

The mapping of an integration document type to a default account is direct, without the need for element groups and mapping elements. No distinction is made on any of the transaction details.

 

Default accounts can be used in two ways:

  • Instead of a detailed mapping to various ledger accounts. All the transactions are posted to the same account. For example, all warehouse receipts are posted to the Inventory ledger account, without any distinction.
  • In addition to a detailed mapping. If a transaction cannot be mapped based on the detailed mapping scheme, it is posted to the default account.
RSS
First96979899101103104105Last

Theme picker

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

Kathy Barthelt

Infor LN & Baan Tip: Important Porting Set Announcement (all versions of LN & Baan)

There has been a recent porting set change due to Infor’s Product Life Cycle Policy.  

How to determine the maintenance stage of an Infor LN product version and release

Before a customer starts deploying Porting Set 9.4a or a later release, they must determine the actual maintenance stage of their Baan / Infor LN product. The definition of the maintenance stages for the product versions and releases of all versions of Baan and Infor LN are outlined in the Product Support schedule as published in the PLC policy. The maintenance stage of the ERP version is either “Mainstream Maintenance”, “Extended Maintenance” or “Sustaining Maintenance”.

How to manage Porting Set updates

The following conditions apply to customers who intend to upgrade to Porting Set 9.4a or later Porting Set releases:

  • For customers with a product version in Mainstream Maintenance, there will be no difference with regards to Porting Set updates. They can install Porting Set 9.4a or any newer release.
  • Customers with a product version in Extended Maintenance will be able to use Porting Set 9.4a only under the condition that they acquire an Extended Maintenance license and have applied the corresponding validated license key to their SLM License server. This key is a Server license type.
  • Customers with a product version in Extended Maintenance who have not acquired an Extended Maintenance license will not be able to use Porting Set 9.4a or any newer version. The latest Porting Set for these customers that can be installed and used is 9.3j which was released in April 2021.
  • Customers with a product version in Sustaining Maintenance will not be able to use Porting Set 9.4a or any newer version. The latest Porting Set for these customers is 9.3j which was released in April 2021. Customers who are not entitled to upgrade to Porting Set 9.4a can use any Porting Set release prior to Porting Set 9.4a. These continue to be available through the Infor Support Portal.

You can find more information in KB 1946498 General: Infor LN and Baan Product Lifecycle Policy and KB 2204515, or you may contact Crossroads RMC for assistance in determining whether or not you are able to upgrade your porting set.

800.762.2077

Previous Article Don't laugh - the average lifespan of an ERP system is 7-10 years
Next Article Infor LN & Baan Tip: Save Space in General Ledger
Print
26942 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories