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

Grindmaster Cecilware Selects Crossroads RMC For Baan IV / Davisware Integration

Crossroads RMC 0 42098 Article rating: No rating

Grindmaster Cecilware, a leader in the development of products for the food and beverage industry, has selected Crossroads RMC to integrate their Baan IV system to Davisware Global Warranty. Davisware is an electronic customizable online solution that fits almost any warranty process. Grindmaster’s customers will be able to access the Davisware software online and process warranty claims which will then automatically feed back into the Baan IV system for further review and processing. The integration is expected to go live in Q1 of 2015.

Read more

Huf North America Goes Lives With Next Phase of RMC3 Data Collection

Crossroads RMC 0 43418 Article rating: No rating

Huf North America, a global leader in the production of mechanical and electronic key systems, lock sets, steering locks, and remote control systems for the automotive industry, has gone live with phase 2 of their Crossroads RMC data collection implementation. This go-live included Report Orders Complete, Labor Reporting, Material Issue, Inventory Transfers, barcode label modifications, as well as custom applications for their Paint / Polishing operations. This go-live was paired with the expansion of Huf’s Plastic Injection Molding and Paint Facility in Greeneville, TN. The next phase of this project will include the extension of the Crossroads RMC solution into Huf’s facility in Mexico.

Read more

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

Baan Tips

Kathy Barthelt 0 122060 Article rating: 3.0
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.
Read more

BPCS/LX Tip of the Week: How To Capture Re-Work Time (Part 1)

Anthony Etzel 0 92050 Article rating: No rating
In SFC600, there is no code to capture the time spent on re-work. Re-work is usually at a specific operation, or when the part is finished and QC determines that re-work is required in order to pass inspection. You are faced with deciding on how to report the additional labor time.

Do you continue to report it against the operation, or create a re-work shop order?

If you are re-working through a specific operation you can capture the time as run labor with the SFC600 program. Now you need to deal with the variance of actual to standard time and what impact this has on costing.
Read more

BPCS/LX Tip of the Week: Configuration Management

Anthony Etzel 0 84692 Article rating: No rating

Make to Order? No problem if you use the Configuration Management System. This LX product allows you to define and configure a make to order product during Customer Order Entry. Basically, you have the option to create different products under the same common product item. You will get two completely different common end items that are configured from the same common parent.

The customer orders are planned and turned into shop orders for each end item with all the associated components. With an MES solution in place, the shop order side is easy to schedule and allows you to manage the shop floor.

Read more

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

Kathy Barthelt 0 83755 Article rating: No rating
What is it?
The configurator consists of a set of features (questions). The options (answers) to these questions then are used to generate the custom bill of material and routing. These questions may be answered at the time of order entry, prior to order entry (in a project or quote) or after order entry (in the project). The order of the questions need not have any relationship to the bill of materials. The configurator may also calculate the selling price, create a unique “smart” item number, custom description and text. Simple rules are used to interpret the answers.

Who uses the configurator?
Companies whose products have options. The configurator eliminates the need for part numbers for all combinations of options. The configurator ensures that the pricing and bills are correct. The configurator also keeps statistics on the frequency the options are selected.
Read more

BPCS/LX Tip of the Week: Uses for LX Bill of Material

Anthony Etzel 0 92465 Article rating: No rating
In Infor LX, based on how your items are set up and on how you structure the Bill of Material, the following are some usages of a bill of material by functioning area:

  • Engineering & QA – change control, product design and specifications
  • Manufacturing – build instructions , material pick lists
  • Accounting – product costing
  • Materials Inventory – material and inventory planning
  • Sales – customer order processing
  • Production Scheduling – item scheduling (also a component of an MES solution)
Read more

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

Kathy Barthelt 0 80484 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
First127128129130132134135136Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Executive

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE: Using Dimensions

You can independently define dimensions and use them to prepare analyses of ledger account transactions and balances. You can use up to 12

dimension types. You can define a name and an entire structure of dimension codes for each of these dimension types. There is no relationship between the dimension types.

For example, you can set up these dimensions:

  • Dimension Type 1 = Cost center
  • Dimension Type 2 = Item group
  • Dimension Type 3 = Business unit
  • Dimension Type 4 = Geographical area
  • Dimension Type 5 = Activities

You can separately define the dimension structure for each of these dimension types, in other words, you can set up a dimension structure for the cost centers, a structure for item groups, and so on.

You can define the number of dimension types that you use in the Group Company Parameters (tfgld0101s000) session. If you have several financial companies in a company group, the dimension types used apply to all the companies in the group.

You can name the dimension types and define linked objects in the Dimension Type Descriptions (tfgld0102m000) session. You can then define the dimension codes to be used in each company in the Dimensions (tfgld0510m000) session. You can also make multilevel dimension structures with totals and subtotals. You can build a dimension hierarchy of up to ten levels.

In the Dimensions (tfgld0510m000) session, you can define the dimensions for each dimension type, and link the dimensions to parent dimensions and child dimensions.

Dimensions are always used together with ledger accounts. For each ledger account, you can define which dimension type or types are linked to the ledger account in the Chart of Accounts (tfgld0508m000) session. For each dimension type, you must select whether the dimensions type is Mandatory, Optional, or Not Used by the ledger account.

When you enter a transaction, you must first state the ledger account. Then you must enter a dimension for each Mandatory dimension type that is linked to the ledger account, and you can enter a dimension for each Optional dimension type.

For example, the sales revenues ledger account is linked to dimension type 2 (item group) and dimension type 4 (area). The dimension type 1 (cost center) and dimension type 3 (business unit) are not used for the ledger account. The freight costs ledger account is linked to only dimension type 1 (cost center). The other dimension types are not used for the ledger account.

For each dimension type, you can define one dimension with an empty dimension code. If the dimension type is Optional for a ledger account, LN posts transactions for which no dimension is specified to this dimension. In this way, differences between the ledger history and the dimension history can be avoided.

In the Cross Validation Rules (tfgld0151m000) session, you can define the ranges of allowed dimensions by ledger accounts. You cannot change the dimension range for a ledger account that occurs in an unfinalized batch.

You can create transactions for Financials from the integration with other LN packages. You can enter these transactions into ledger accounts and into dimensions. You can define the assignment to ledger accounts through the Mapping Scheme (tfgld4573m000) session.

You can use the dimensions to split the transactions on the customer and supplier control accounts by departments, persons responsible for the revenues, costs, properties, debts, and so on.

The dimensions also provide the basis for the cost allocation in the Cost Accounting module. In CAT, you can allocate the costs (and any revenues) within a dimension type from one dimension code to another and from one dimension type to another.

TECHNOLOGY: High Contrast Skin

The high contrast skin can be activated by users who experience low vision, color-blindness, or similar visual impairments.

If the high contrast skin is active, LN UI is colored so that all controls comply with the WCAG AA norms for accessibility.

Guideline 1.4.3 Contrast (Minimum)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. For level AA, these exceptions apply:

  • Large text: large-scale text and images of large-scale text have a contrast ratio of at least 3:1.
  • Incidental: the following text or images of text have no contrast requirement:
    • Text or images of text that are part of an inactive user interface component.
    • Text or images of text that are pure decoration.
    • Text or images of text that are not visible to anyone.
    • Text or images of text that are part of a picture that contains significant other visual content.
  • Logotypes: text that is part of a logo or brand name has no minimum contrast requirement.

OPERATIONS: Blocking Operations

Note: The Blocked Operations (tisfc0540m000) session displays the blocked operations.

Introduction

Sometimes a problem occurs that must be solved before an operation proceeds. Examples of such situations are:

  • The quality of an intermediate product must first be inspected.
  • A machine is in repair.
  • A supplier cannot deliver an essential component in time.
  • A customer is late with its payments.

In these situations the operation can get the operation status Blocked.

An operation can be blocked:

  • Manually.
  • Automatically by Quality.

Blocking reasons

Every blocked operation must have a blocking reason. The blocking reason of a blocked operation has two purposes:

  • To indicate why the operation is blocked.
  • To determine which actions you can no longer perform on the operation.

Types of blocking

The following actions can be blocked by means of a blocking reason:

  • Reporting a quantity completed.
  • Reporting a quantity rejected.
  • Reporting a quantity to be inspected.
  • Reporting an operation completed.

You normally carry out these actions in the Report Operations Completed (tisfc0130m000) session.

You can define blocking reasons in the Blocking Reasons (tisfc2100m000) session.

Manual blocking

Use the Report Operations Completed (tisfc0130m000) session to block an operation. When you block an operation, you must also enter a blocking reason. If Quality has already blocked the operation, you can only enter a blocking reason, which is more restrictive than the blocking reason of Quality.

Blocking by Quality Management

Quality uses the blocking reasons specified in the Quality Management Parameters (qmptc0100m000) session, to block operations. For details, see the Using QM for manufacturing operations topic.

Previous Article Infor LN & Baan Tips & Tricks for OPERATIONS: Simulated Purchase Prices (ticpr1170m000)
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Using Dimensions
Print
298 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

x

Categories