| Oracle® Retail Store Operations Cloud Service User Guide Release 17.0 E88477-05 |
|
 Previous |
 Next |
| Oracle® Retail Store Operations Cloud Service User Guide Release 17.0 E88477-05 |
|
Previous |
Next |
The shipping and receiving functions in SOCS have several common components. The following functional areas are included: Customer Order Deliveries, Return to Vendor Shipments, and Transfer Shipping/Receiving for store, warehouse, and external finisher. They include tasks usually performed by shipping or receiving associates. This also includes integrating to a third-party manifesting system for rate shopping to find the least expensive delivery method.
The feature of shipping and receiving available in mobile is:
Manifest web services for rate shopping
Manifesting systems help retailers create manifest documents, Bill of Lading (BOL), shipping container labels for shipments, and reduce cost through rate shopping by finding the least expensive delivery method for the given shipping criteria.
For larger shipments, multiple containers may exist and each container requires a separate tracking ID. For RTV Shipment and Transfer Shipment, the manifesting service will be called when confirming each container. The carrier and service are required to be the same for all containers within the same shipment. The container and shipment are all inclusive for Customer Order Deliveries.
A user creates a shipment (store, warehouse, finisher, customer order delivery, or return to vendor) and enters in the package type of "Small" and Weight of 2.3 lbs. The Manifesting system will do the rate shopping for the carrier and service and automatically print out a label for the package.
The above flow shows the confirmation of a container and how a call is made to the manifest system. The flow is highlighted in different colors to help identify different integration points.
When the user confirms each container for an RTV or Transfer shipment, the system can invoke the web service to provide the required shipment details to the manifesting system and subsequently return a tracking ID for each container.
After all containers have received their tracking ID, the user is able to ship the shipment, or an external system indicates to SOCS that the shipment is dispatched.
|
Note: Customer Order Deliveries only use the web service at submit or dispatch since the shipment will always be a single container. |
If SOCS is configured to publish a pre-shipment, it sends the pre-shipment notice to the pre-shipment system.
If the carrier must be changed for the shipment with transfer shipment or RTV shipment, the user is required to adjust the carrier, which will cause all containers to move back to 'In Progress'. Once the shipment has been dispatched, the user will no longer be able to adjust the carrier.
The above flow represents when a Customer Order Delivery is dispatched and a call is made to the manifest system. The flow is highlighted in different colors to help identify different integration points.
Features:
Enter Carrier BOL Information
Enter Container ID, Weight, Package Type, and Tracking ID
View Carrier BOL Information
Set External Printer
The user has the ability to enter the carrier details for Transfer Shipments, RTV Shipments and Customer Order Deliveries. The user can access the Edit Shipment screen by navigating to the Shipment and selecting Edit Shipment from the Footer menu.
For Transfer Shipments, if the shipment is for sending items to a warehouse or finisher, the user has the option to enter an Authorization Number. This is not applicable to Transfer to Store or Customer Order Deliveries. Security permissions exist for the user to enter an Authorization Number.
In order to prepare the shipment for manifesting, the user is required to enter the carrier information on this screen. When the carrier Type is Third Party and the Carrier Service is a (P) parcel service, the manifesting service is called when the user confirms the container. Security permissions exist for the user to edit the Carrier BOL information.
The carrier type is defaulted based on the store parameter 'Carrier Default' set up for each type of transaction (store, finisher, warehouse, and RTV).
| Delivery Type | Default Carrier |
|---|---|
| Customer Order Delivery | Third Party if the customer has identified a carrier to use on the customer order. If no carrier is identified on the customer order the Sender. |
| Ship To Customer | Sender |
| Pick Up | Receiver |
If the carrier type is Third Party, the Carrier is available for selection. This field may be overwritten by the manifesting system when used. The user may select 'Other' from the list of carriers. If 'Other' carrier is selected, the Carrier Name and Address will be enabled.
When a carrier is selected, a list of services available for the carrier will be selectable. This field may be overwritten by the manifesting system when used in addition to the Carrier. The manifesting service call made can include checking for the best rate and will override what was selected by the user.
Shipment Carriers, Shipment Carrier Services, Shipment Weight UOM, and Shipment Package Sizes are setup and maintained in EICS.
Each Carrier will have one of three manifest types: (P) Parcel, (H) Home Fleet, and (O) Other. Only carriers with a manifest type of (P) Parcel will be used with the manifesting integration service. Depending on the carrier service, weight and package size may be required. The system will alert the user when the information is missing.
The motive for the shipment is based on the functional area and sequence number. The code with the sequence of 1 will be displayed by default. The user can create and manage Motives through EICS.
The BOL Details for a shipment gets frozen once the first container is confirmed and cannot be changed without moving all the containers for the shipment back to an 'In Progress' state. This is done by using the Adjust Carrier feature. The BOL Details can be adjusted until the shipment is dispatched if the user has the appropriate permissions. Once the user selects Adjust Carrier, a new carrier may be selected and each container will need to be reconfirmed to manifest again.
The Edit Container screen is only applicable to Transfer Shipments and RTV Shipments, since Customer Order Deliveries shipment and container is all inclusive. The user will enter the package type, weight, and other container details from this screen. Security permissions exist for the user to edit this screen. If manifesting is used, the manifesting service will return the tracking ID. The Edit Container screen is accessed from the Footer menu of Transfer/RTV Ship Container screen, RTV Ship Container Screen, and Transfer Receiving Container screens. Since the Edit Shipment screen defines the entire shipment, the Edit Container screen is used to identify the package type, weight, and tracking ID for each individual container.The customer order feature does not use this screen. For customer order deliveries, the package type weight and tracking ID are entered directly on the Edit Shipment screen. The Transfer Receiving feature also uses this screen to enter Reference Container ID, Damage Reason. The tracking ID may also be captured on this screen.The validations listed below apply to Transfer Shipments, RTV Shipments, and Customer Order Deliveries. The validations for Transfer Shipments and RTV Shipments are performed at the time of confirming the container, while Customer Order Deliveries performs the validations upon submit or dispatch of the shipment.
The Tracking ID will contain a single ID for tracking the package; it can be entered by the user, come from the manifesting system or come from the shipping ASN. It may get overwritten/updated by an external manifesting system. The tracking ID entered within the Transfer Receiving dialog can be leveraged to find a container.
The weight field is used to enter in the weight of the package. The weight will be entered in the unit of measure based on the store admin Manifest weight UOM.
The package type is used to define the dimensions of package such as Large Envelope, Small Box, Medium Box, and so on. The package type will be selected from a defined list of packaged types in the Carton Dimension table.
Depending on the carrier/service selected for the shipment, the package type and weight may be required (this is only validated when the manifesting system is called). The Shipment Carrier Service table identifies when the weight and package type is required. This table is populated from a data script.
Note that when creating a transfer shipment container or RTV shipment container on the mobile, the carrier is defaulted based upon a store setting, Carrier Default. When the setting is Third Party, the carrier is Other and the service is blank. Therefore, the user is not prompted for the weight and/or package type unless the carrier /service had been set as something different.
This screen can be accessed within the Shipments by selecting External Printing from the Footer menu of Transfer/RTV Ship Containers screen. The external printer can be defined for the pre-shipment and manifest documents. These settings will remain until the user logs out of the application. This setting is applicable across all functional areas within SOCS that use the Pre-Shipment and Manifest documents. If the printer is selected for Transfer Shipment, the same printers will be set for Customer Order Deliveries dialog and RTV Shipment and vice versa.
