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

Nazdaq has released Version 3.0 of B2Win Suite

Partner News

Kathy Barthelt 0 30890 Article rating: No rating

New Release of B2Win Suite: Format customer reports, email documents to your suppliers and customers, and more! 

New features – B2Win Suite - You are no longer limited to the data that comes from your canned reports! You can now add new columns to your already existing reports in Excel, based on SQL commands that bring additional data from any database (ERP or other), based on values from the report.

Existing Nazdaq customers should contact us to learn how we can convert your software to the latest and greatest Nazdaq product suite!

For more information: watch our webinar:

Webinar Recording: 48:18

Crossroads is proud to work with Johnson Crushers International on their LN re-implementation to 10.6

Kathy Barthelt 0 14624 Article rating: 5.0

Johnson Crushers International (JCI), a global leader in engineering and manufacturing full lines of cone crushers, horizontal and incline vibrating screens and track-mounted, portable and stationary crushing and screening plants, has selected Crossroads RMC to help them re-implement Infor LN on 10.6.  JCI’s main objectives with this project are to support their continued growth, align and standardize their business processes, and enable a continuous improvement effort to drive additional value to the business. Go live is expected to occur in early Q1 of 2020.

Baan/LN Tip of the Week: Warehouse Material Movement / Problems With the Inventory Structure Table (whinr150)

Kathy Barthelt 0 38351 Article rating: No rating

This has come up as an issue during various stages of warehouse material movements – transfers, outbounds, shipments. We have seen it right up to 10.4. The inventory structure table (whinr150) becomes a problem. The error points to that table, but users are lost as to how to fix it.

In the session Units by Unit Set many companies let the field Storage default to Yes. If the UOM is not intended to be used in inventory then that setting should be No. 

If an item is purchased in UOM different from the inventory unit and the setting is Yes then LN adds a record in that UOM to the inventory structure table. It is that record that causes problem later.

The session has an option to change the value of the storage field. Specific > Convert Use for Storage. This option works both ways and will correct all inventory in the UOM range. 

Should a user receive an error that references inventory structure table then the solution is to check that session to see if an odd UOM exists in it. If so use the Convert Use for Storage to correct the problem.

Baan/LN Tip: Disabling Unused Functionality in LN

Kathy Barthelt 0 38378 Article rating: No rating

If functionality such as Commissions, Rebates, or Contracts are enabled in the parameters, LN checks this functionality during transactions, even if you did not specify anything for these concepts. Therefore, if you do not use certain functionality within LN, to improve performance, disable the corresponding parameter.

Optimize Your Manufacturing Today!

3 Essential Tactics to Increase Efficiency on the Manufacturing Floor

Crossroads RMC 0 59273 Article rating: No rating

From John O'Kelly's article on Manufacturing.net:

"Regardless of industry, efficiency gains and increased speed provide a competitive edge. The ever-increasing competition in the manufacturing world makes it necessary to find new, efficient ways to speed up the process while remaining accurate and productive. While flying robots and miracle technologies may promise to reshape the industry, we still have a way to go until full automation, and thus the most important asset on the manufacturing floor in 2019 will remain its people.

In 2019, the focus will undoubtably be increasing efficiencies, and this can be achieved through investing in employees, equipping them with the proper techniques and tools. An invested labor force will limit mistakes on the manufacturing floor and improve throughput at every level of the process."

Here are a few best practices to increase efficiency on the manufacturing floor in 2019:

  1. Invest in your labor force
  2. Prioritize quality assurance
  3. Improve labeling errors

You can read the full article with detailed descriptions at: https://blog.safe.com/

Optimize Your Manufacturing Today!

RSS
First6364656668707172Last

Theme picker

Tips:  LX | BPCS | M3

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES:

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:

  • Select the Quantity-dependent Routing check box in the Item - Production (tiipd0101m000) session.

  • Enter the routing codes in the Item - Routings (tirou1101m000) session. Enter the maximum quantity for which a routing is valid in the Up to Quantity field.

Note: If multisite functionality is activated, the routings available may vary per site on the job shop bill of material selected. Differences in routings have an impact on the standard cost calculation.

Default routing

If the Quantity-dependent Routing check box is not selected, the default routing applies to an item. However, this default routing must also be linked to the item. To find out, LN checks the default routing code in the Default Routing field of the Job Shop Master Data Parameters (tirou0100m000) session. Next, LN checks whether the default routing code is linked to the item in the Item - Routings (tirou1101m000) session. If so, the default routing applies to the item. If the default routing is not linked to the item, no routing is used.


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.

  • The destination financial company.

  • The transaction type and series.

  • The ledger account and dimensions.

  • The transaction currency.

  • The fiscal year and the financial period, the tax period, and the reporting period.

  • The integration document type and the Debit/Credit indicator.

  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

 
TECHNOLOGY: Infor LN Rest API

Frequently Asked Questions (KB2316174)

For Infor LN a framework has been developed to support REST API-based services for lean integrations. This framework is now made available for the LN application. This KB answers some common questions you may have and procedures that are needed for using the LN Rest APIs.

More details on these topics can be found in the Infor LN REST API Administration Guide.

Previous Article Infor LN & Baan Tips & Tricks for FINANCE: Integration Transactions - Compression
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Ledger Account Blocked Error
Print
6212 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories