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

BPCS/LX TIP OF THE WEEK: REGULATORY ENHANCEMENTS

Anthony Etzel 0 22023 Article rating: No rating

In LX 8.3.5, a new report has been added that meets the regulatory reporting requirement for purchase and sales transactions (invoices, debit notes, credit notes) of a company. The report refers to transactions from the previous year (January – December). The report is available in an eFile layout.

The enhancement provides a new display and batch programs to extract the data and format the reports. New logs are provided in addition to the extraction report.

This enhancement will assist the user in meeting the regulatory requirement for reporting transactions.

Baan/LN Tip of the Week: Restricted User Access

Kathy Barthelt 0 40428 Article rating: No rating

Administrators are able to restrict access in Baan in several ways – including Companies, Packages, Modules, Sessions, and Tables – using the Authorization capabilities of the system.

In Baan IV, access can be given or denied on a user by user basis.

In Baan V and LN, the Authorization Management System can provide or deny access based upon roles to which users are assigned.

BPCS/LX TIP OF THE WEEK: INVENTORY MANAGEMENT

Anthony Etzel 0 24785 Article rating: No rating

Establishing the Quantity On-Hand and the Quantity Available.

LX maintains buckets for information associated with the following inventory transactions for each item:

  • Opening Balance
  • Issues
  • Receipts
  • Adjustments
  • Allocations for the Customer
  • Allocations for Manufacturing

The on hand quantity does not include any allocations. To arrive at the on hand quantity, start with the opening balance, less any issues, plus any receipts, then add or subtract any adjustments. Available inventory is the on-hand less any allocations.

Baan/LN Tip of the Week: Old Porting Set

Kathy Barthelt 0 36968 Article rating: No rating

Here are some issues that you might run into if you stay on an old porting set too long:

  • Incompatibility because of operating system patches
  • Printing issues because of out-of-date libraries
  • Potential performance issues if binaries are not updated
  • Updating third party products may not be possible because of dependencies
  • Limited support from Infor
  • Issues with updating database software/patches because of dependencies (if database is also running on same server as application)

Need help getting on a newer porting set? Let us know! We’d be happy to help.

RSS
First9091929395979899Last

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