Geert Van Zeir Cegeka Business Solutions Business Solution Architect

When you manually change the delivery type to direct delivery on the SO line, the system automatically changes the warehouse on the SO line to the direct delivery warehouse, setup on the item. The same should happen when you click the Create direct delivery PO button and flag lines for direct delivery. Currently this does not happen, and both the SO lines and PO lines have the wrong warehouse (in many cases, this is an advanced WHS, that does not support Direct deliveries). Hence, a ‘corrupt’ situation is created and the whole process needs to be re-done, which is a real pain in a live environment (the PO may already have been sent to the supplier, extra work, etc… )

I understood that it is currently not possible to use an external scanner (e.g. wired or Bluetooth) on the asset management mobile app. There is only the option to either enter the (item) codes manually or to use the camera of the mobile device itself. Using the camera is extremely un-accurate for aiming at the correct barcode and unpractical in many cases: e.g. our customer docs the tablet onto a cart and would use the external scanner to confirm the scanned items (some of these products are stacked closely together, so aiming for the correct barcode with the device camera is a nightmare). A handheld scanner would solve many issues.

to streamline the inbound process for vendors that don't provide an ASN, we will create an inbound load, based on the vendor packing slip information. We then print a load document in a uniform way, with all required barcodes so that the warehouse worker can use it for Load item receiving. The quantity entered on the load line is updated with the quantity from the vendor packing slip. In a lot of cases, this qty is more than ordered. However, the system does not allow this.

Even if over-delivery percentage is filled in on the load line (e.g.1000%) it is still not possible to enter a load line quantity that is greater than the PO line quantity for which the load is created. The system shows a warning message: "The quantity is greater than the quantity left to load for load line for Purchase order, order number PO..." but in fact this is treated as a blocking error (not able to save the load line). This is inconsistent with how the same load would behave when a packing structure is added for that inbound load. When adding a packing structure, I can create a packing structure line for a qty that is more than the load line quantity (and thus more than the PO line qty). When scanning the label from the packing structure (LP receiving) the packing structure quantity is registered and the work created qty on the load line is updated with the qty from the LP in the packing structure. When the load is 'receiving completed' the load line qty is updated with the packing structure qty. If it is possible to allow this via Packing structure, it should also be allowed to update the qty directly on the load line. If that requires an auto-update of deliver remainder (behind the scenes) to make this technically work, then that's probably how it should be done.

imagine following scenario: some users in the purchasing department are only working with intercompany vendors. For these users, a view, called "IC purchases", has been created on the 'all purchase orders' form, that filters on e.g. the vendor group 'IC'. When such user adds a new purchase order for an intercompany vendor and returns to the 'all purchase orders' form, the grid is showing the PO's from all vendors (view is broken and shows an asterix next to the view name > IC purchases*. Switching back and forth between standard view and the IC purchases view doesn't to a thing, The only way to reload the correct view is to reload the entire page.

As MS is heavily promoting the use of saved views, and customers are relying on them, I think the use of the saved views should be made much more user friendly by not 'forgetting the filters'.

Side note: if, in the above scenario, such user would be creating a PO for a NON IC vendor, then I think it would be logical that the user will NOT see this order, when he/she returns to the 'IC filtered' PO grid, as it would be filtered out.