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: Remembered Keys

Anthony Etzel 0 1918 Article rating: No rating

Infor LX remembers certain key values, such as item number, salesperson,

or container, in your workstation memory as you process information in certain

programs. You can assign one of the following values to each field:

 

0  -Infor LX automatically retrieves this value from remember key memory. Infor LX updates this value on a continual basis.

 

1  -Infor LX automatically retrieves the value you specify in Display Remembered Keys, SYS080. It does not update the value from any other program.

 

2  -Infor LX does not retrieve or update remembered key fields. Use the Display Remembered Keys program, SYS080, to set up remembered keys.

Read more

Baan/LN Tip of the Week: Sales Order Acknowledgements

Kathy Barthelt 0 3109 Article rating: No rating

Sales Order Acknowledgements in Baan IV:
After a sales order is entered in Baan IV, users can print an order acknowledgement in Print Sales Order Acknowledgements/RMAs (tdsls4401m000), after which it can be sent to the customer.

Sales order acknowledgements in ERP LN:
In Infor LN, users can still use the Print Sales Order Acknowledgements/RMAs (tdsls4401m000) session to print order acknowledgements, however, the following functionality is added to this session:

  • In the Documents to Print field users can select whether to print order acknowledgments and/or return material authorizations.
  • With the Promotions check box users can indicate whether to print promotions on the order acknowledgement, if promotions apply to the order.
  • Users can control the printing of order acknowledgements based on the order amount and/or the delivery date.

These conditions only apply for order types that do not have the Print Sales Order Acknowledgements/RMAs (tdsls4401m000) linked as a mandatory activity to the order type in the Sales Order Type - Activities (tdsls0560m000) session.

Read more

BPCS/LX Tip of the Week: Operational Inefficiencies

Anthony Etzel 0 393 Article rating: No rating

Two big sources of inefficiencies in manufacturing are paper and spreadsheets. I know that you love ‘em, but they are the cause of more problems than you probably realize. Think of how long it takes you to get paper based data into the hands of those who can do something valuable with the data. Are you capturing all of the information correctly? Timely? What about those spreadsheets? Can everyone access that information across your organization? Is that data married with all of the related data regarding your operations to give your executive and middle management the information they need when they need it?

Make your shop floor paperless and put in place systems that talk to one another and automatically pull and push data to and from your ERP so that you can look in one place for all the information you need to run your business effectively.

If you’re not doing this today, you might as well be burning money.

Read more

Baan/LN Tip of the Week: Use of Correction Period

Kathy Barthelt 0 173 Article rating: No rating

There can only be one correction period, and it must be the last period in the period table.

There can only be a correction period for Fiscal periods and not for Reporting or Tax. This period is used for the posting of the Automatic Balancing of Profit and Loss entries as well as any auditor adjusting entries that may be made outside the normal year. This allows you to print a trial balance and financial statements of period 1-12, for example, eliminating any of those adjusting entries.

If you have the Company Parameter (Balancing of Profit & Loss) set to Individual Accounts, then it is critical to have a 13th period to post those entries to. With this setting, the Automatic Balancing will zero out each individual P&L account in the last period. You want this to be period 13 and not period 12.

Read more

BPCS/LX Tip of the Week: Understanding What Goes On – Out on the Factory Floor

Anthony Etzel 0 346 Article rating: No rating

Ok… so you want to know the status of a specific shop order that was released two days ago.

What do you do?

It’s a sure bet that you have a manager, supervisor, or planner who can walk the floor and find the order at whatever work center it happens to be at. He/she can then answer “what operations have been completed and how many were completed?” All this requires leg work, and of course, a fair amount of time.

Now, if you have setup your BPCS master files properly, and you report transaction activity, you should be able to get those shop order statuses much faster using the SFC300 Shop Order Inquiry Screen.

At your fingertips you can see:

  • Release date & due date
  • How many hours remain in total and at each operation
  • The quantity required, what was finished and the remaining quantity
  • What components (materials) have been issued

Pretty basic information, right? Are you getting what you need to know? If not, then you may want to reexamine how your BPCS files are setup and what transactions along with their frequency are captured.

Read more

Baan/LN Tip of the Week: Default Order Frequency

Kathy Barthelt 0 178 Article rating: No rating

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In Infor LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.

Read more

BPCS/LX Tip of the Week: Indirect Time

Anthony Etzel 0 1002 Article rating: No rating

In Infor LX, there are two ways to enter indirect labor. You can use either SFC600 or SFC650.
 

  1. If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
  2. If you use SFC650 and enter a reason code for the indirect, the reason code is not written to the labor Ticket file.

 

In either case, the reason code is not validated from the transaction file because there is no indirect transaction code. The indirect code that can be setup is machine downtime. If you need to validate and track indirect by reason and validate the reason code, then you may want to explore an MES solution that works with Infor LX.

 

Read more
First123124125126128130131132Last

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
304 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

x

Categories