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

Infor LN & Baan Tip: 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 impact the related outbound advice, shipments, or shipment lines.

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

  1. Update the outbound order line if the originating order is changed.
  2. Cancel the originating order line and the outbound order line.
  3. Delete the canceled outbound order line.

Updating Outbound Order Lines

  • Allowed: Changes made to the originating order are updated to the outbound order line. Related outbound advice and picking lists, if present, are deleted.
  • Not Allowed: A message is displayed, and input is blocked when trying to change the originating order line.

Canceling Outbound Order Lines

  • 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, related outbound advice and picking lists are also deleted.
    • Outbound order lines originating from manual order origins cannot be deleted when canceled.
  • Not Allowed: You cannot cancel the originating order line or the outbound order line. A message is displayed when attempting to cancel the originating order line.

Processing Canceled Outbound Order Lines

  • To process an outbound order line 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.
  • When a canceled outbound order line is set to Shipped, the shipped quantity is automatically set to 0.
  • A transfer order can be created to return the not-shipped goods to inventory.

Preventing Shipment When Canceling is Not Allowed

  • Complete the outbound and shipment procedures to prevent goods from being shipped.
  • When confirming the shipment line, set the shipped quantities to 0 and create a transfer order to return the not-shipped goods to inventory.

Previous Article inPower 2024 - Join Gold Sponsor Crossroads RMC
Next Article Reskilling and Upskilling Your Staff – Why You Shouldn’t Ignore This
Print
8564 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

12345678910Last

Theme picker

Tips: LN | Baan

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.

If you have a parts warehouse and prefer to use SIC for planning (re-order point) but need to use MRP/MPS planning for production, create a non-nettable warehouse for the parts warehouse and run the SIC plan against that warehouse.

When running the SIC plan, be sure to set the Order System to “MPS to MRP” for Baan IV and to “Planned to Planned” for Baan V and LN.

Using this method you keep the parts inventory out of the production planning and in the hands of the parts warehouse planner.

First133134135136138140141142Last

Theme picker

Categories