Shipping
Change in logic to handle shipment updates in existing loads
In a typical customer shipping process, a load or truck is composed of one or more shipments. Certain customers (suppliers) who manufacture a high volume of products have a requirement to adjust their load with no notice because of issues with transportation or inventory. For example, this happens when there is not an adequate supply for a part to ship, or not adequate space to ship in the truck.
In such cases, the load must be adjusted, and shipments may have to be removed from the existing load and moved to a different load. In addition, it may be necessary to add handling units after re-opening the original load.
This enhancement adds flexibility to match what is present in Infor LN which allows shipments to be moved from one load to another. Because of this mismatch in flexibility, this resulted in differences between the shipping structure in LN and the shipping structure in Automotive Exchange.
- Remove an existing shipment from an existing load;
- Add a new shipment to an existing load;
- Remove an existing shipment and add a new shipment to the existing load.
With this enhancement, the shipment paperwork and the ASN will match the final confirmed load in LN and Automotive Exchange.
Use of Flex Fields in Shipping
On the Shippers page, there is a Flex
Fields tab that shows the user area fields that are captured from LN. Flex fields allow for the publication and printing of the related
data for subsequent shipping tasks and documents. This includes labels, packing slips, EDI
waybills, waybills, and ASN. In , the new code list FlexFieldAllowList with a
trading partner hierarchy allows you to define the user area fields to be captured. This
code list definition determines which user area fields to accept from LN, instead of including every user area field available.