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

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)

RSS
First145146147148150152153154Last

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

Infor LN & Baan Tip of the Week: Limitations of Customer Defined Fields (CDFs)

Customer Defined fields are fields that can be added to tables, screens, reports, and BODs. Validation and calculation logic can be defined around those fields. This gives you great added capability and flexibility… however, are you aware of the limitations of using CDFs?

  • You cannot define customer-defined fields for tables within Tools (the tl and tt packages).
  • External integrations, such as Infor Integration, EDI, Office Integration, and SOA-based integration, do not support customer-defined fields.
  • You can use customer-defined fields within 4GL reports if editing the 4GL report layouts is still supported in your environment or by using the report personalization features of Infor LN Report Designer. For external reporting, only Infor Reporting and Microsoft Reporting (SSRS) support customer-defined fields.
  • Customer-defined fields cannot store application data in multiple data languages.
  • There is no direct limitation on the number of CDFs in a table. The actual number of fields in a table and the total length of all fields may be limited by the RDBMS you use.
  • Only superusers can run the Convert to Runtime Data Dictionary (ttadv5215m000) session to convert the customer-defined fields and the related domains to the runtime data dictionary.

Note: The full functionality of customer-defined fields is only available within Web UI and LN UI. Customer-defined fields are not displayed in the classic Infor LN BW UI.

If you have questions or need assistance with the use of CDFs, or Infor LN or Baan modifications in general, please contact us for assistance. We’d be happy to help. 800.762.2077 or kbarthelt@crossroadsrmc.com

Previous Article Infor LN & Baan Finance Tip: How to clear balances on invoices that will be moved to a new company
Next Article Infor LN & Baan Manufacturing Tip: Performance Problems in Generate Order Planning (cprrp1210m000)
Print
27586 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories