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 Tips & Tricks for OPERATIONS: Update, Cancel or Remove Outbound Order Lines

When the originating order or order line of an outbound order line is canceled or changed, this affects the outbound order line and may affect the related outbound advice, shipments, or shipment lines.

For most order origins, warehousing order-type parameters determine whether these actions are allowed:

  • Update the outbound order line if the originating order is changed.
  • Cancel the originating order line and the outbound order line.
  • Delete the canceled outbound order line.

If updating is allowed, changes made to the originating order are updated to the outbound order line and the related outbound advice, and, if present, picking lists, are deleted.

If updating is not allowed, a message is displayed, and the input is blocked when you try to change the originating order line.

If canceling is allowed, the outbound order line is deleted or set to Canceled when the originating order line is canceled.

When a canceled outbound order line is deleted, if present, the related outbound advice and picking list are also deleted. Outbound order lines originating from manual order origins cannot be deleted when canceled.

To process an outbound order line that is not deleted but set to Canceled, the outbound order line must be set to Shipped. The status of the outbound order line determines whether all steps of the outbound and shipment procedures must be completed to process the outbound order line.

When a canceled outbound order line is set to Shipped, the shipped quantity is automatically set to 0. You can create a transfer order to return the not-shipped goods to inventory.

If canceling is not allowed, you cannot cancel the originating order line or the outbound order line. A message to that effect is displayed when you try to cancel the originating order line.

To prevent the goods from being shipped when canceling is not allowed, you must complete the outbound and shipment procedures. When confirming the shipment line, you must set the shipped quantities to 0 and create a transfer order to return the not-shipped goods to inventory.

Previous Article Streamline Your Shipping Processes – Boost Efficiency and Reduce Errors
Next Article Infor LN & Baan Tips & Tricks for FINANCE:  Currency Differences Accounts
Print
51920 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