Ship confirm is the process of confirming that items have shipped. When you ship confirm a delivery, Shipping Execution confirms that the delivery lines associated with the delivery have shipped.
You use the Confirm Delivery window to manually select or deselect ship confirm options. The options in the Confirm Delivery window provide flexibility for automating many tasks associated with processing deliveries with many delivery lines. For example, when the Ship Entered Quantities, Unspecified Quantities Ship option is selected at ship confirm, the shipped amounts are automatically processed so that each delivery line with a missing shipped quantity value is recorded as fully shipped. This saves you from manually entering each item as fully shipped.
Note: Oracle Shipping Execution supports up to 5 decimal points for order quantities created in Discrete Inventory organizations. Existing order quantities containing more than 5 decimal points must not be entered during ship confirm to avoid the ship confirm process from failing.
During ship confirm, you can also automatically create a trip and related stops for a delivery that has not been assigned to a trip.
Note: For a list of the actions that cause recalculating, see Freight Rate Recalculation Actions
During Ship confirm, the application validates the actual departure against the following:
Shipping calendar associated with the location of the organization.
If there is no assignment of a shipping calendar to the organization location, and there is an assignment at organization level (shipping calendar), then the application defaults the shipping calendar of the assignment at the organization level and validates against that.
Receiving calendar for customer.
If there is an assignment of receiving calendar at customer location, then the application considers it for validation. Otherwise, the application defaults the calendar at customer level (if any).
Carrier calendar.
If there are assignments at organization location or customer location, then the application considers these calendars. Otherwise, the application considers the calendar defined at organization level (for a particular carrier), and the one defined at customer level (if any).