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

Baan/LN Tip of the Week: Default Order Frequency

Kathy Barthelt 0 1943 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.

BPCS/LX Tip of the Day: Cost Accounting – LX

Anthony Etzel 0 868 Article rating: No rating

The challenge in cost accounting is tracking your manufacturing to the levels needed for useful management information. You need feedback for corrective action; but, you need to minimize the cost of collection. Some parts of your operation require specific job-cost tracking while the Just-in-Time areas require

costing in terms of cost per process hour or day. Apply overhead in different ways to different processes and products. Segregate costs into enough detail

to provide management with an accurate picture of the contents of your product. Material, material overhead, labor, fixed overhead, variable overhead, outside processing, outside processing overhead, and so forth all have to be considered.

 

LX meets your cost accounting needs with the following functionality:

▪ Four sets of costs: actual, standard, frozen standard, and simulated

▪ Nine user-defined elements per set

▪ Full and partial cost roll-up and simulation

▪ Cumulative in-process cost tracking

▪ Cost summaries by item

▪ Cost definition tied to work centers or material type

▪ Process hour costing

Baan/LN Tip of the Day: Vendor Rating

Kathy Barthelt 0 1416 Article rating: No rating

In LN, a supplier's reliability is no longer based only on correct deliveries. The vendor rating functionality of LN is based on various objective criteria and subjective criteria that can be used to calculate the vendor’s rating.

 

The set up procedure for analyzing suppliers has changed completely compared to Baan IV.  To execute the vendor rating process, users must update the vendor ratings in the Update Vendor Rating (tdpur8850m000) session.

If users update the vendor ratings, the following stages exist in the update vendor rating procedure:


1. Calculate actual weightings

2. Calculate ratings for objective criteria

3. Calculate ratings for subjective criteria

4. Update overall vendor rating

Baan/LN Tip of the Day: Release Commissions/Rebates to Invoicing

Kathy Barthelt 0 3103 Article rating: No rating

In Baan IV, this session is called Release Commissions/Rebates to Invoicing (tdcms2201m000) and is used to set the status of the commissions/rebates to Reserved, or Closed. In Infor LN, this session is only used to set the status to  Closed. Users can reserve commissions/rebates in the Reservation and Approval of Reserved Commissions/Rebates (tdcms2202m000) session. In addition, the following fields are added to the Release Commissions/Rebates to Invoicing (tdcms2201m000) session:

▪ Commissions to Accounts Payable

▪ Rebates to Central Invoicing

BPCS/LX Tip of the Day: How Does LX Fit in With Just-In-Time?

Anthony Etzel 0 364 Article rating: No rating

For years, repetitive manufacturing industries have been applying many of the principles in Just-in-Time philosophy. They have established balanced production lines that depend on a steady flow of material to each work station. They schedule production in daily or weekly rates rather than in discrete shop order lots. They track finished inventory by work center rather than by job. They typically backflush stock balances (decrement stock balances upon completion of specific manufacturing steps rather than issued at the beginning of each production run).

 

Costing is typically based upon a daily rate or hourly rate rather than being associated with specific shop orders. 

 

Repetitive manufacturers use MRP II software adaptable to their environments

in the following key areas:


 Product definition

 Inventory tracking

 MRP/Master Scheduling

 Shop Floor Control

 Purchasing

 Costing

BPCS/LX Tip of the Day: What is Just-In-Time?

Anthony Etzel 0 313 Article rating: No rating

Just-in-Time (JIT) is a management philosophy that focuses on minimizing the resources necessary to add value to your products and to operate your factory in ways that eliminate waste. Resources are labor, materials, equipment, space, and time. Waste is anything that does not add value to your products. Moving work-in-process from place to place, stacking and sorting, investing capital in large work-in-process and raw material inventories, inspecting materials at your vendors' sites, and tying up warehouse space with finished goods are all activities that add cost, not value, to your products. 

JIT is a process that reduces lead time. JIT does not replace an MRP, an inventory program, a scheduling technique to bypass your Master Schedule, or a materials management project. JIT is the never-ending commitment of everyone, from top management to your workers on the floor, to maximize your effectiveness through continuous, incremental improvements.

Baan/LN Tip of the Day: Configuring Items

Kathy Barthelt 0 2237 Article rating: No rating

In LN, the configuration of a generic item not always results into a customized item. Configured items can now be customized items as well as standard items. If users configure items without PCS projects, standard items are generated instead of customized items.

 

The sessions for generating product variant structures for sales quotations and sales orders are moved from the Product Configuration module in Manufacturing to the Sales Control module in LN. The following new sessions are available in Sales Control:

▪ Generate (Budget) Structure for Sales Quotations (tdsls1201m100).

▪ Generate (Project) Structure for Sales Orders (tdsls4244m000)

BPCS/LX Tip of the Day: Shop Order Control

Anthony Etzel 0 443 Article rating: No rating

To create and maintain shop orders use SFC500 Shop Order Entry Maintenance. These orders use the standard bill of material (BOM) as the base list of components. You can also set up standard routings, which list the operations,

or work steps, involved in manufacturing.

 

To release shop orders, use the Shop Order Release program, SFC505. Infor ERP LX groups shop orders by user ID for batch processing. Use Shop Packet Print, SFC520, to print the shop orders that you select. SFC530 allows you to create multi-level shop orders to link shop orders together with a common end item parent. Linking multiple shop orders together for a final assembly product provides support for make-to-order and engineer-to-order manufacturing environments which need to schedule these multiple orders together or as a vertical slice in the production schedule.

 

You can make changes to shop orders after you print them. Use Shop Order Entry/Maintenance, SFC500, to update the shop orders. Changes are immediately visible on the inquiry screens for SFC300 and SFC350. To reprint the shop packet, use Reprint Shop Packet, SFC560.

First110111112113115117118119Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Performance improvement by setting the First Free Number Cache (tcmcs0651m000)

Many transactions in all kinds of modules use order numbers or serial numbers. These order numbers are most often automatically generated. In the Number Groups (tcmcs0151m000) session you can define groups of order numbers used for dedicated areas. A Number Group is a group of the first free number series that you can assign to a specific use. All the numbers that Infor LN generates in the number groups that are dedicated to the same purpose are unique.

All the first free numbers are stored in the table tcmcs050.

As many different processes can request a free number from the number groups, we often see delays in the performance, due to locking on the first free number records. This locking issue can have a severe impact on the performance of huge batch-type transactions, but also on the performance perceived by individual users in many areas in LN.

For example:

  • Processing warehouse transactions. Single or in-batch
  • Completing / closing orders
  • Backflushing of production orders
  • Generate Order Planning
  • Cost calculation and warehouse revaluation


How this performance can be improved?

Resolution

In the Number Groups (tcmcs0151m000) session you can open the details of a specific Number Group (tcmcs0651m000) or start the session stand-alone.

In the Number Group, you define the Series with the related First Free Numbers. Per Serie in the First Free Number, you have the option to define the Cache Size.

This Cache size is defaulted on a value of 0 (zero). A cache size of zero means No Cache. How does the First Free Number caching works:

  • When the Cache Size is zero: With this setting a process requests a Free Number from the Serie and the first free number is issued to the process. But the first free number record is not updated yet. At the moment the requesting process is finished, without errors, it reports back that the number is used and the first free number record is updated. All the time that the process is working on the transactions the first free number record is locked. If another process is requesting a free number from the same series, it must wait (retries) until the record is updated and released by the previous process. This is the locking which is causing delays in the other processes.  
  • Setting the Cache Size to a higher value then zero activates the caching. When the Cache Size is set to 1 or higher, the requested free number is sent to the requesting process, the first free number is updated, with the number as defined in the Cache size, and the record is saved. It does not wait until the requesting process has reported back that is finished, with or without errors. In this way the record is immediately released and no locking will occur. If another process is requesting a free number, it does not need to wait until the free number record is released by the earlier process. If the process is ended with errors and therefor the number is not used, this number from the series is lost. This can result in gaps in the numbering. When the cache size is greater than 1, for example it is set to 5, the requesting process receives 5 free numbers. Even if it only needs less than 5. In this way the process only has to request for a new free number after it has used the first 5 numbers from the cache. This will also speedup the process in case of large batch transactions. For ‘warehouse integration users’, like for example Factory Track or WMS users we advise to set the cache size to 5.  

Note that financial documents are not based on number group series / first free numbers. Instead they are based on transaction type series, for which the caching functionality does not exist. Financial documents, like sales invoices, bank transactions, are thus not cached.

The caching is especially important to improve the performance of all logistical processes.

It is strongly recommended (mandatory) to set the Cache Size for all Number Groups to a minimum of 1.

Previous Article Infor LX / BPCS & Infor LN / Baan Tip: A New Wave of Cyber Attacks: Five Actions to Take Now
Next Article ​Infor LN & Baan Tip: Determining What Data to Archive or Delete
Print
26210 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories