Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

BPCS/LX Tip of the Week: Batch Allocation

Anthony Etzel 0 41362 Article rating: 5.0

Thinking of moving from your old BPCS Version to LX?

There are numerous reasons to consider moving to Infor LX. It is a proven migration and it is easy to get there.

An area of interest may be allocations. Allocations can be difficult to manage, but with Infor LX, there is a new selection of ranges for Batch Allocations:

    • Sold To Customer
    • Ship To Number
    • Order Class
    • Order Number
    • Item Number
    • Request Date
    • Schedule Date
Read more

Baan/LN Tip of the Week: Safety Time

Kathy Barthelt 0 55031 Article rating: No rating

You can add safety time in the item master for the item. This will add the number of days safety time to the order lead time thus bringing the order in x number of days early. (x is the safety time).

The safety time is on form 4 of the item master in Baan IV and in Item Ordering Data – Generation I tab in Baan V and LN.

Read more

Baan/LN Tip of the Week: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt 0 52214 Article rating: No rating

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

 

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

Read more
RSS
First155156157158160162163164Last

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.

Read more

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.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Product Configurator - Part 2

Baan Tips

Who gets involved?
  1. Most commonly Engineering is involved in writing the rules, creating the bills and routings.
  2. Sales or Customer Service determines the questions and the order they are asked in.
  3. Sales or Customer Service determines the rules for the pricing.
  4. Sales, or Customer Service, and Engineering work together in determining the part number, description and text.

What are the steps?

  1. You must start by defining the features and options (questions and answers) and the order in which these are asked. We work this out first using sticky notes and large easel paper. Normally during the process we find that we want to move these questions around. Setting them down on paper makes the process of getting the data into Baan much more efficient. We also then have a record of what decisions were made prior to entering the data. This is normally a joint effort of Engineering and Sales. This is required and must be the first step.
  2. Constraints for features and options. These are the rules for determining what questions are asked and which options are allowed. This is generally done by Engineering or whoever is responsible for the configurator. This is required.
  3. Generic Bill of Material. All possible bill options are entered here and constraints are written to determine which options are selected based on the answers to the questions. This is generally done by Engineering or whoever is responsible for the configurator. This is a required step.
  4. Generic Routing. Similar to the bill of material, but used for generation of the routing steps. This is generally done by Engineering or whoever is responsible for the configurator. This is optional.
  5. Generic Item Data. This consists of creating custom item numbers, descriptions, text, material, size or standard fields in the custom item master. This is generally done by Engineering or whoever is responsible for the configurator though Sales may have some involvement. This is optional.
  6. Generic Pricing. This is used to calculate the selling price based on the answers to the questions. This is normally a responsibility of Sales or whoever determines the pricing. This group is also trained on writing the constraints for this section only. This is optional.

What other modules will be affected?
  1. Quotes, sales orders and projects.
  2. PRP planning for the configured items.
  3. Managing changes to the configuration. Who, what and when?
  4. Variant statistics.
  5. MPS and generic items.
Previous Article Baan/LN Tip of the Week: Product Configurator - Part 1
Next Article Baan/LN Tip of the Week: Printing Pick Lists
Print
60934 Rate this article:
3.0
Tags: Baan Tips ERP LN Tips Infor LN Tips LN Tips
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Theme picker

Contact author

x

Categories