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

On Time Orders: OTTO - The Right Tools!

George Moroses 0 29441 Article rating: 5.0

Your business doesn’t run without the right people and processes in place, but in order for people to manage the right things at the right time, they need tools... the RIGHT tools

OTTO helps manufacturing plants consistently meet customer commitments, allowing supervisors and managers to spend more time analyzing, making decisions, communicating, and coordinating. We can prove that OTTO is the right tool for the job.

Give it a test drive for 30 days at no charge and see immediate results.

Contact George Moroses today to learn more.

Infor LX & BPCS Tip of the Week: Control Number, POCNO, added to CEA502B1

George Moroses 0 33888 Article rating: 5.0

This enhancement makes the control number field in the purchase order file available for macros. Previously, the POCNO field (control number) in the purchase order was not available for macros. This enhancement allows the user to create macros that use this field. This enhancement provides the user with the ability to keep track of control numbers in their journal entries.

The programs impacted include:

  • CEA502B1, ACP Engine Resolution Program
  • CGL091B, ERPLX ACP File I/O Program

Managing IDF for LX Version 06.03.05.84

21-Jun-2019

George Moroses 0 28535 Article rating: 5.0

Read these instructions prior to beginning your installation or upgrade of IDF for LX 8.4. This document also provides current information related to using, installing, and configuring IDF for LX Version 06.03.05. New information will be added to this document as it becomes available. IDF for LX 06.03.05.84 is compatible with LX 8.4 environments.

Updates
21-Jun-2019 – Fix Patch 06.03.05.84.02.01 and SH16143692
Also see Link Manager Fix Level for 06.03.05.84.02.01 for the list of IDF Client fixes.
BMR 80211 Cumulative Patch 84.02.01 includes changes to support Infor’s Java strategy, see the Infor LX IDF Client Runtime Update for Corretto for special instructions on installing this IDF patch.
For information on LX moving from Oracle to Corretto Java see KB 2069811.

22-May-2019 – Fix Patch 06.03.05.84.01.02 and SH16143692
Also see Link Manager Fix Level for 06.03.05.84.01.02 for the list of IDF Client fixes.
MR 79799 Item gets deleted after pick confirm but does not delete after invoice.
MR 79876 Enhancement - Enterprise Item Relationship to PO Lines.
MR 80001 Attributes associated with a business object are not available to be added to a View if the business object is defined as not being allowed on menu.
MR 80004 IDF issues found while testing enhancement to IDF Change.
MR 80037 Extended Amount incorrect for DWM items in IDF Purchase Order Inquiry.
MR 80105 Integrator Translations need to be added to the “Default” card file.
MR 80039 In IDF Power-link listed under Maintain dropdown are IDF Inquiry business objects that are not maintainable in IDF.
MR 80079 Shop Order has wrong labels/descriptions.
MR 80083 Should not allow users to change an item record to DWM if there is active inventory.
MR 80099 Error: "The field TBBT1F is not maintainable" is received when attempting to change Main toolbar buttons for Net-Link from Standard actions only to IDF.
MR 80116 Host print allows selection of Suspended (Inactive) language and does not return an error message.
MR 80117 Orders details in IDF Customers object under Orders tab doesn't show all 9 digits of the Order Number.
MR 80125 Not able to Create Customer when Multi currency flag is OFF.
MR 80194 The Vendor Tax Code and Customer Tax Code do not fully display in Vendor’s Tax tab and Customer's Tax tab in Ming.le Change mode only.
MR 80208 IDF secondary objects are not setWebCapable(True); therefore customizations do not appear in NetLink.

Information and Instructions
New Installs of IDF
If you don’t have IDF installed please refer to the LX IDF 06.03.05 Installation and Upgrade Guide available on the Infor Support Portal for important instructions.

Upgrading existing IDF installations
If you already have IDF installed for LX 8.3.x environments it needs to be upgraded to 06.03.05 prior to adding LX 8.4 IDF environments. Please refer to the...

RSS
First4748495052545556Last

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

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
61228 Rate this article:
3.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories