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 25485 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
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: All About Invoicing Methods

Invoicing Methods are a set of parameters that define the types of orders and order lines that can be collected on an invoice, the type of invoice to be generated and the costs to be aggregated on Project invoices and Service invoices.

If options to combine tax codes, departments, sales representatives' line of business area, etc... are checked, LN will combine all available transactions ready to be invoiced that have different tax codes departments, sales representatives, etc...into only one invoice.

If options to combine sales orders, sales order types, and shipments are checked then all sales orders that are created for the same business partner where the shipment and/or sales order type is different will be combined into one invoice.

For example:

  1. If sales order SLS001 is created for BP BP1000 with 2 lines where each line has a different shipment number, and the invoice method is combining shipments, both lines will be part of the same invoice. If the option to combine shipments is not checked then LN will create an invoice per shipment.
  2. If sales order SLS001 is created for BP BP1000 with 2 lines and 2 different shipment numbers and sales order SLS002 is created for the same BP with a cost item, LN will create one invoice for both orders if the option to combine sales orders and shipments is checked. If only the option to combine sales orders is checked then 3 different invoices will be created as all 3 lines will have different shipment numbers. If they have different sales order types and this option is not checked on the invoice method session then also 3 invoices will be created but if it is checked along with sales order and shipment number then only one invoice will be created.
  3. If we take scenario 1 again and both lines have different tax codes and the option to combine tax codes is not selected then LN will create a separate invoice for each line based on the tax code.
     

Note: In the case that the Business Partner Tax Country is different, even if we select combine tax codes, the system will create a separate invoice based on the Business Partner Country to full the statutory compliances for that BP country.

Previous Article Infor LN & Baan Tip: Cash Flow Functionality and Setup
Next Article Infor LN & Baan Tip: Why was the session "General Ledger Diagnostics Workbench" built?
Print
17040 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories