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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip of the Week: Warehouse Blocking – LN 10.7

The functionality to block a warehouse for inbound or outbound transactions has been enhanced. A check for blocks is performed not only during receipt and shipment confirmation, but at multiple stages in the process. In addition, you can specify these blocking options for the inbound and outbound processes:

• No

• Yes

• Interactive

For example, if Blocked for Inbound is set to Yes, no inbound actions are allowed in the warehouse. Consequently, users cannot confirm receipts, generate and put away inbound advice or storage lists, and perform inbound inspections. 

If Interactive is set, during a non-automatic warehouse inbound procedure, warnings are displayed which offer the user a choice to either cancel the action or continue. Batch or automatic inbound processes continue, but the corresponding reports and logs make note of the blocking. However, in all scenarios, receipt confirmation is not allowed.

The same rules are applicable for the warehouse outbound procedure steps. The restriction for receipt confirmation also applies to shipment confirmation.

For warehouse transfer orders, not only the ship-from warehouse is checked for outbound process blocks, but also the ship-to warehouse. This prevents situations in which goods get stuck in transit due to inbound procedure blocks that apply to the destination warehouse. Now, the transfer process is already blocked during outbound.

Previous Article Partner News: Are you up to date on all of the sales tax changes that have gone into effect this year?
Next Article Consulting News: Are you familiar with your Infor LN / Baan System Log?
Print
73667 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Understanding: What Was Issued to the Shop Order

The shop order inquiry program provides several function keys. By using the function key for the material, the display will present what components have been issued under the issued quantity column. You are also presented with the required quantity. While viewing the quantities you may see that more was issued than what was required. Possibly there was scrap and more material was required to be issued. Perhaps there was an over issue and the balance of the material is slated to be returned to stock.

A red flag should go up if the Shop Order quantity finished is equal to the required quantity for the end item and all the components have not been issued. You may want to investigate why.

Understanding: The quantities required, finished and remaining at the operation and in total for the Shop Order

The shop order may require 1,000 pieces but only 950 are reported as finished in total for the shop order. The quantity required is what is planned on the SO and it may be a higher number than what is finished, factoring in that there can be scrap. If a 1,000 pieces are required to be produced, and there is always is scrap of 10 pieces, then plan for scheduling a quantity of 1,010.

The quantity finished for the end item is what is reported in the inventory application with a production order receipt transaction. At the operation level, if the quantity is reported at the operation, there will be a value in the PCS Complete field on the operation detail screen showing the pieces completed through that operation.

If you want to get a handle on the difference between the required quantity and the finished quantity, you may want to look into reporting quantities at the operation level as well as examining how scrap is controlled and reported.

FirstLast

Tips: LN | Baan

Categories