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
73544 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

Enhances purchase order efficiency by automatically calculating the Vendor Delivery Date based on user input.

  • When a purchase order line is created, the user enters the item, order quantity, and Due Date.

  • LX automatically calculates the Vendor Delivery Date, adding buffer time for quality control, testing, and inspection activities.

  • If the Due Date is revised, an informational message prompts the user to review and potentially update the Vendor Delivery Date.

Enhancements:

  • A new PUR820 system parameter enables automatic recalculation of the Vendor Delivery Date.

  • Instead of a manual reminder, PUR500 now issues a message: “Vendor Delivery Date recalculated,” showing the updated date.

Benefits:

  • Eliminates the need to manually review and update the Vendor Delivery Date.

  • Removes the need to delete and recreate PO lines to trigger automatic date calculation.

Enables integration between LX and Infor OS Federation Services (IFS) to automate user provisioning.

  • Bi-directional user synchronization between Infor OS and LX:

    • Infor OS user creation or changes automatically create or update users in LX.

    • IBM i user profiles can be created if needed.

    • Updates to SYS600 user data are reflected in Infor OS.

  • Security Role Integration:

    • LX Security Roles and Units are published as IFS Security Roles via SyncSecurityRoleMaster BODs.

    • LX receives inbound SyncSecurityUserMaster BODs from IFS to create or update user records in SYS600.

    • SYS600 Exit Points trigger ProcessSecurityUserMaster BODs to request user creation or updates in IFS on behalf of LX.

Available Versions: 8.3.5, 8.4.1, 8.4.2

FirstLast

Tips: LN | Baan

Categories