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 82545 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 34342 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 24149 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 42649 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 59091 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 72848 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 73318 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.

First7273747577798081Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Day: LX Inventory Pallet Status Flow

Four fields in the Item/Warehouse record (IIW file) affect the disposition of the

pallet status.

 

1.  Goods Receiving Code: You define these codes in Goods Receiving Maintenance (WHM130). The codes control whether or not the stock passes through inspection, what percentage, or quantity of a delivery to inspect, and the number of quarantine days, if any.

 

2.  Inspection Zone/Inspection Location: Either the Inspection Zone or the Inspection Location must be entered on the Item/Warehouse Master Maintenance screen WHM150D2-01.

 

3.  Default Inventory Status: If the status is 0 (Received) or 1 (Inspection), the item moves from the receiving location to the inspection location in inspection status. If the pallet status is not 0 or 1 (that is, 4 (Available) or 9 (Rejected)), the pallet moves to the inspection location with the default status, but the pallet will not proceed from the Inspection location to the Putaway location. You must manually move the stock.

 

4.  Pallet Status Codes: 0 (Received), 1 (Inspection), 4 (Available), and 9 (Rejected) are the only pallet status codes reserved by the system to update and advance inventory/pallet status. To do this Warehouse Management uses the following rules:

 

·    Rejected inventory goes from receiving to a Reject (type 9) Location with a Location Type A (Rejected) in the Location Extension file (ILE) record. All inventory received into a reject location is set to a pallet/inventory status of Reject (9).

·    Inventory received by Goods Receiving (WHM510) into a Receiving Location takes on the Default Inventory Status that is in the Item Warehouse file (IIW) record.

·    If the Default Inventory Status is 0 (Received), the system places the pallet status at 0 (Received) in the Receiving Location, I (Inspection) in the Inspection Location, and 4 (Available) if moved from Inspection to any palletized location other than rejection. If moved to rejection the Default Inventory Status changes to 9 (Rejected).

Print
51319 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Categories