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

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

Here are some issues that you might run into if you stay on an old porting set too long:

  • Incompatibility because of operating system patches
  • Printing issues because of out-of-date libraries
  • Potential performance issues if binaries are not updated
  • Updating third-party products may not be possible because of dependencies
  • Limited support from Infor
  • Issues with updating database software/patches because of dependencies (if the database is also running on the same server as the application)

Need help getting on a newer porting set? Let us know! We’d be happy to help.

In Baan IV, plan items exist within the context of a plan code. A plan code includes only items of the MPS Item item type. Planned orders are independent of a plan code. Users can compare plan codes by means of the Plan Code Performance Comparison (cprmp4504m000) session.

The scenario concept in Infor LN replaces the plan code concept in Baan IV.

In Infor LN, the basic data for plan items is the same for all scenarios. However, users maintain not only the master plan within a scenario, but the planned orders as well.

For example, for each scenario, Users can specify:

  • Special demand for an item.
  • The availability of resources (in the Scenario – Availabilities (cprpd4160m000) session).
  • The sourcing strategies and supply strategies.

Users can compare scenarios by means of the Performance Indicators (cprao2201s000) session.

First129130131132134136137138Last

Theme picker

Categories