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

If it is necessary to pause sending and receiving of BOD messages on your IBM i during your month end process, it is best practice for the document flows that point to the IBM i to guarantee delivery of BOD messages. Once the month end process has been completed, you will need to Resume the ‘Receiving’ and ‘Sending’ Active Connection Points so your documents will continue to process.

Pausing Sending messages

To pause sending messages to ION:

  1. Select Connect > Active Connection Points.
  2. Select the connection point that must be paused for sending messages.
  3. In the Sending Paused column, click Pause. The page is automatically refreshed and the Sending Paused checkbox is selected. A Resume button becomes available. 

Sending of messages by this connection point is stopped....

The database in LX 8.4 has undergone a significant change from previous versions. The database has been created using SQL DDL language instead of the old DDS language. The newer format allows for LX to take better advantage of advances in IBM database technologies as they move forward. Additionally, LX will be better able to make changes to tables (aka files) in the future without causing very large MR explosions to replace all programs that use a specific table. To ease the impact of this significant change, the LX tables (aka physical files) have new names that are the same as the previous version file names but with a “P” at the end, for example IIM is now IIMP. The old file names now belong to SQL views that looks just like the tables. This change made it easier to upgrade all the LX programs without changing every reference to every file. Many of the logical files remain although some have been replaced by SQL indexes to improve performance.

First6263646567697071Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories