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: Product Routing

Anthony Etzel 0 43739 Article rating: No rating

Defining the Product Routing first requires the items to be setup in the Item Master file. Other master files also need to be defined prior to creating the routing.
These include:

  • The Facility defined with a SYS program
  • The Warehouses defined with an INV program
  • Locations defined with an INV program
  • The Machines (required if using capacity planning or an MES interface) defined with an MDM program

After the above data is set up, the Department file and Work Center files can be setup in MDM. Now you are ready to define a product route.

Baan/LN Tip of the Week: Month End – Miscellaneous To-Do’s

Kathy Barthelt 0 57056 Article rating: No rating
  • Print Sales Order History Information
    • all invoices processed through sales
  • Check Inventory Valuation
    • this should tie out to your inventory accounts
  • Print Integration Information
    • see all postings from WIP to finished goods
  • Print G/L Transaction Information
    • print specific transaction types for any GL account
  • Print Lot Control Information
    • will show where serial numbers were used
RSS
First156157158159161163164165Last

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

Infor LN & Baan Tip: Financial Integration Mapping Scheme

Transactions to be mapped - In the mapping scheme, you must define the ledger mapping and the dimension mapping for these types of transactions:

  1. Financial integration transactions resulting from logistic events in Operations Management.
  2. General Ledger transactions.
  3. Procurement card transactions in Accounts Payable.


In addition, to support dimension accounting you must define the dimension mapping of financial transactions from Accounts Payable and from Invoicing to the various dimensions.

The setup procedure - creating, changing, or extending an integration mapping scheme, consists of these steps:

  1. Map scheme prerequisites.
  2. If no mapping scheme exists, create a mapping scheme.
  3. Create a mapping scheme version.
  4. Map by Reconciliation Group (tfgld4166m000)
  5. Set up the integration transaction document numbers for the integration transactions.
  6. Set up compression of the transactions.
  7. Check and activate a mapping scheme for your mapping scheme version.

Previous Article Is it time to get more out of Infor LN & Baan?
Next Article Infor LN & Baan Tip: Using the “Use Up” Functionality in Infor LN
Print
20714 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories