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

Infor LN / Baan Tip of the Week: Deleting Records

Kathy Barthelt 0 81240 Article rating: 5.0

To improve performance and reduce database growth, deleting records is highly effective. The disadvantage of deleting records is that data is no longer available. Usually, however, not all records need to be saved. For example, line activities are stored by warehouse. Normally, you do not need to keep these records. Therefore, after closing a warehouse order, line activities can be removed. The User's Guide for ERP LN Archiving describes several sessions you can use to delete old data. Other data such as items and business partners can be reviewed once in a while, after which you can delete the data you no longer need. For every order and contract table a session is available to archive and delete old orders. In these sessions, you can specify several characteristics to select the orders to be removed, such as date or status. Run these sessions on a regular basis.

Explore your IDF programs

Anthony Etzel 0 33681 Article rating: 5.0

If you haven't already, you may want to start to explore your IDF programs. Currently they provide the replacement for the 300 series inquiry programs. In addition, navigation drill downs are far superior to any green screen presentation of the data.

Consistently meet customer commitments without last minute surprises

George Moroses 0 23633 Article rating: 5.0

What if you had a solution that allowed you to consistently meet customer commitments without last-minute surprises and unexpected extra effort and cost?

We do this by preventing slippage — slippage is any break in the plan that disrupts both normal material flow and the rhythm of the plant that is preventable by timely key user intervention.
Click here to learn more about OTTO, On-Time Orders.

Crossroads RMC and FIFCO to partner on an Infor LX / ION Project

Anthony Etzel 0 42209 Article rating: 5.0

A quote from the Applications and Development Manager at FIFCO…

"FIFCO has a long standing relationship with Crossroads RMC. Over the past 20 years, Crossroads has been committed to our success. We chose Crossroads to implement ION for the technical expertise and in-depth knowledge they have of ERPLX. I have found this to be true of all the consultants I have worked with over the years from Crossroads. I hope for FIFCO USA and Crossroads RMC to continue their partnership for many more years to come."

BPCS / LX Tip of the Week: Inventory Period Balance Freeze

Anthony Etzel 0 58178 Article rating: 5.0

This enhancement provides clients the ability to store the opening/ending on hand balance for each Inventory period at the Item (IIM), Warehouse/Item (IWI) and Lot/Location (ILI) levels. Infor LX clients can back date inventory transactions into the immediate previously closed period, and thus update what was saved as the opening/ending balance throughout the current open period. 

Tracking the opening/ending/period balance for each inventory period can give users insights into the levels of inventory for each item, item/warehouse and item/warehouse/lot/location combination.

Crossroads RMC is proud to enter their 21st year in partnership with Paccar for Baan data collection

Kathy Barthelt 0 71648 Article rating: 5.0

In 1998, Paccar, Inc. chose Crossroads RMC to be their data collection partner for Baan IV. That partnership has grown over the years and now incorporates almost 200 data collection licenses and 15 different Crossroads applications that run on mobile devices throughout Paccar’s facility. This year, Paccar has elected to extend the Crossroads Data Collection - Web Collect to some of their 3rd party contractors in order to support an increase in production. With the installation of the Crossroads Data Collection - Web Collect, the subcontractors will be able to complete sub-assembly activities and inventory transfers all within Paccar’s Baan system which the subcontractors will be accessing via a point to point solution built for them.

Baan / LN Tip of the Week: Analyzing Inventory Adjustments – 10.6

Kathy Barthelt 0 72174 Article rating: 5.0

Want to understand the financial ramifications of inventory changes in Infor LN? 

Analyze Inventory Adjustments in-LN 10.6

Several display and print sessions are available.  In these examples, the item number used is 020000.

1--Adjustment Orders Session

Double click on the order line to get to the Lines detail.

In the Lines session, double click on the item to see the details.

The “Adjustment” tab provides the quantities.

First6970717274767778Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

[EasyDNNnews:IfExists:Event]
[EasyDNNnews:IfExists:EventRegistration][EasyDNNnews:EventRegistration:RegisterButton][EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:Payment][EasyDNNnews:Price][EasyDNNnews:EndIf:Payment] [EasyDNNnewsLocalizedText:Eventdate]: [EasyDNNnews:EventDate] [EasyDNNnewsLocalizedText:ExportEvent] [EasyDNNnews:IfExists:EventLocation]

[EasyDNNnewsLocalizedText:EventLocation]: [EasyDNNnews:EventLocation]

[EasyDNNnews:EndIf:EventLocation] [EasyDNNnews:IfExists:EventRegistration]
  • [EasyDNNnewsLocalizedText:NumberOfAttendants]: [EasyDNNnews:EventRegistration:NumberOfAttendants]
  • [EasyDNNnewsLocalizedText:MaxNumberOfTickets]: [EasyDNNnews:EventRegistration:MaxNumberOfTickets]
  • [EasyDNNnewsLocalizedText:NotUsedTickets]: [EasyDNNnews:EventRegistration:NotUsedTickets]
  • [EasyDNNnews:IfExists:Payment]
  • [EasyDNNnewsLocalizedText:Price]: [EasyDNNnews:Price]
  • [EasyDNNnews:EndIf:Payment]
[EasyDNNnews:EventRegistration:InfoMessage] [EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:EventSignUp]

[EasyDNNnewsLocalizedText:AreYouGoing]

[EasyDNNnews:SignUpActionBar]
[EasyDNNnews:EndIf:EventSignUp]
[EasyDNNnews:EndIf:Event]
Kathy Barthelt
/ [EasyDNNnewsLocalizedText:Categories]: [EasyDNNnews:Categories]

Baan/LN Tip of the Week: Ledger Default Account

If you do not wish to define a detailed mapping to various ledger accounts for specific integration transactions, you can map the corresponding integration document type to a default account. All the transactions of the integration document type for which an account cannot be determined based on the mapping scheme details, are posted to the default account.

 

The mapping of an integration document type to a default account is direct, without the need for element groups and mapping elements. No distinction is made on any of the transaction details.

 

Default accounts can be used in two ways:

  • Instead of a detailed mapping to various ledger accounts. All the transactions are posted to the same account. For example, all warehouse receipts are posted to the Inventory ledger account, without any distinction.
  • In addition to a detailed mapping. If a transaction cannot be mapped based on the detailed mapping scheme, it is posted to the default account.
Previous Article Baan/LN Tip of the Week: Clusters in LN
Next Article Baan/LN Tip of the Week: Creating Product Variants
Print
70677 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories