The users can manage the outbound orders under the Orders --> Outbound orders tab in the Serialized Logistics application.


An outbound order is a logical grouping of multiple deliveries. An order organizes the activities in the warehouse through the linked deliveries.


The outbound orders can be one of the following types:

  • Internal orders (Stock Transfer Orders)*
  • External orders (Purchase Orders)

*Not supported end-to-end


Parts of an order


An order consists of three parts as described in the table below:


Order partDescription
Settings

Collects the master data of the order:

  • Order ID
  • Order type
  • Source and destination details
  • Different dates and deadline
  • The operator who executes the order in the warehouse
  • Tolerance values for under-delivery and over-delivery (if any)


Besides the settings, a status is also associated with the order.


The order takes one of the following statuses:

  • Open
  • In shipping
  • Paused shipping
  • Shipped
Line items

Represents the products to be shipped.


Each line item represents one product. For each line item, you specify the product data, the target quantity to be shipped with the unit of measurement, and optionally you can also provide sales parameters.


Status is also associated with the line item:

  • Open
  • In shipping
  • Completed
Deliveries

The operator can execute the order under a delivery in the warehouse. Actually, when the operator executes an order, they scan for line items and they always complete the line items under a delivery.


An order can have multiple deliveries at the same time.

  • The first delivery can be created for the order while creating the order in the Admin UI, through API, or by processing an IDOC Delvry that is received from SAP ICH/uploaded on an SAP ICH channel.
  • Further deliveries can be added to the order by processing IDOC Delvry files. Each IDOC Delvry describes a new delivery, specifies the warehouse sublocation, and can specify the route that delivery belongs to:
    • You must register all sublocations of a warehouse under the Site management --> Warehouses --> Sub locations tab in advance.
    • If an IDOC Delvry specifies a route, you must register all the possible routes under the Site management --> Routes tab in advance.


The delivery has an ID, a status, a warehouse, and optionally a route. The delivery takes one of the following statuses:

  • Open
  • In shipping
  • In picking validation
  • Picking validated
  • Processing shipping
  • Shipped


Statuses and status transitions


An outbound external order can be executed in one of the following ways:

  • By performing a group of actions in the mobile application (validating picking/packing to order/packing an order) and in the Admin UI (validating picking for a one-case delivery/releasing a validated picking).
  • By shipping items in the mobile application.


Based on the type of execution, different statuses, and status transitions are applicable.


The following diagram illustrates the parts of an outbound external order and the status transitions when performing the following actions:

  • Validating picking in the mobile application.
  • Packing to an order (Packing - orders) in the mobile application.
  • Packing an order in the mobile application.
  • Validating picking for a one-case delivery in the Admin UI.
  • Releasing a validated picking in the Admin UI.



The following diagram illustrates the parts of an outbound external order and the status transitions when shipping items in the mobile application:


IMPORTANT: To ship items in the mobile application, the order can contain one delivery only. When shipping in the mobile application, multiple deliveries are not supported.



List of Procedures


Creating an Outbound Order


You can create an outbound order in one of the following ways:

  • Through API.
  • Through Admin UI.
  • By sending an IDOC Delvry from SAP ICH to Movilitas.Cloud (SAP ICH channel is required).
  • By uploading an IDOC Delvry on the SAP ICH channel (SAP ICH channel is required).


The following procedure describes how to create an outbound order in the Admin UI.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders and the Create new outbound order form.


Note: When viewing the details of an order, you can open the Create new outbound order form by clicking Add new +.


Example:



2. Fill in the form as described in the table below. The required fields are marked with an asterisk (*) in the form.


FieldAction
Order IDEnter the order ID. Free-form text field.
Order typeSelect the order type:
  • Internal
  • External
Delivery IDEnter the delivery ID. By default, the delivery ID is prefilled and it takes the order ID as the value.

After saving the order, the Delivery ID field disappears and all the related data are displayed under the Deliveries tab.

ClientFor an outbound external order, select the client that receives the products of the order. The application displays a prefiltered list in the drop-down but you can search for a previously registered client by entering an expression in the search field. Only applicable to outbound external orders.
Delivery addressAfter selecting the client for an outbound external order, select the delivery address for the client.

You can select the client master data address or a delivery address (if any) from the drop-down. You can select from the addresses that were provided during client registration.
Destination warehouseFor an outbound internal order, select the destination warehouse that receives the products of the order. The application offers the previously registered warehouses for selection. Only applicable to outbound internal orders.
Order dateSelect the date of order by using the datepicker.
Expected shipping dateSelect the expected shipping date by using the datepicker.
DeadlineSelected the deadline by using the datepicker.
Source warehouseSelect the sender warehouse

After saving the order, the warehouse is linked to the delivery and the warehouse is displayed under the Deliveries tab.
OperatorSelect the operator that must execute the order.
Allow unlimited overdelivery and underdelivery

If you want to allow an unlimited amount of delivery (shipment), keep this checkbox selected.


When this checkbox is selected, the tolerance values will not be displayed (not applicable). The default setting is "Selected".


After clearing the checkbox, an unlimited delivery is not allowed and the application displays the tolerance fields.


IMPORTANT: The setting applies to all deliveries and line items of the order and cannot be changed once the order is in a status other than Open.

Underdelivery tolerance [%]

Set the under-delivery tolerance.


The operator in the warehouse must keep the target quantity with the tolerance defined here. For example, if you set 10%, the operator cannot ship less than 90% of the target quantity.


The allowed value is 0 or a value that is greater than 0. For an order that is created in the Admin UI, the default value is 0.


IMPORTANT: The tolerance value applies to all deliveries and line items of the order and cannot be changed once the order is in a status other than Open.

Overdelivery tolerance [%]

Set the over-delivery tolerance.


The operator in the warehouse must keep the target quantity with the tolerance defined here. For example, if you set 10%, the operator cannot ship more than 110% of the target quantity.


The allowed value is 0 or a value that is greater than 0. For an order that is created in the Admin UI, the default value is 0.


IMPORTANT: The tolerance value applies to all deliveries and line items of the order and cannot be changed once the order is in a status other than Open.


Example:



3. Click Create.

  • The order is created and added to the list.
  • The order tabs become active.
  • The Delivery ID field disappears and all the related data are displayed under the Deliveries tab.


4. To add line items to the order, select the Line items tab.



5. Click Add Line Item and fill in the form as described below. The required fields are marked with an asterisk (*) in the form.



FieldDescription
Line item numberEnter the line item number. The application auto-fills the field and provides "1" for the first line item. When adding a new line item, the application automatically offers a new value. You can change the line item number based on your preference but two line items cannot have the same number.
Product code schemaSelect the product code schema.
  • GTIN
  • PPN
Select productSelect a product code. The application displays a searchable drop-down with a prefiltered list of products. You can search for any product registered in the system by entering the product code or the product name in the search field.
BatchSpecify a batch for the product code (if applicable). If you don't know the batch, you can leave the field empty. In this case, the application accepts any batch that is scanned for the product.


You can select an existing batch or you can specify one inline. The application displays a searchable drop-down with a list of batches available for that product code in the system.

  • You can search for a batch of the product by entering the batch number (ID) in the search field.
  • If the entered batch is not existing, you can create the batch by clicking on the Create batch button displayed in the search drop-down.


You can clear the field by clicking on the X button on the right side of the drop-down.

QuantityEnter the quantity to be shipped. A positive number is accepted only.
Unit of measurementEnter the unit of measurement of the quantity. Free-form text field.
Sales quantityOptionally, enter the sales quantity. A positive number is accepted only.
Sales unit of measurementOptionally, enter the unit of measurement of the sales quantity. Free-form text field.


EXAMPLE 1


The following example illustrates the case when adding a line item without a batch for the selected product code:



EXAMPLE 2


The following example illustrates the case when the batch is specified inline while adding the line item:




6. Click Add in the Add line item window. The line item is added to the list.


The following example illustrates the case when the previously defined two line items are added to the order, one after the other. The first line item is expanded:



7. Add further line items as needed.


You can add multiple line items that have different or the same product data, there is no restriction. For example:

  • You have two line items with the same product code and batch but with different sales parameters.
  • You have line items with completely different product codes, batches, and other data.


Each line item added to the order is linked to the delivery also.


Next Steps


An operator can execute the outbound order in the warehouse.


Back to the list of procedures



Searching for and Viewing an Outbound Order


You select the order view and check the details.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. To open the order view, select Order ID in the ID column field. The application displays the list of orders in the Outbound orders panel.


Note: The application remembers the selected view mode until the user logs out.


3. Enter the order ID in the search field, select the statuses, and/or select the order types.

  • The list of the orders is filtered based on the search criteria.
  • You can reset the filter by clicking Reset filters.


4. Select the order to view its details. The application displays the Update outbound order panel with the Settings tab.

  • You can view the order master data such as order ID, order type, destination information, dates and deadlines, and the under-delivery/over-delivery settings.
  • If the order is created by receiving an IDOC Delvry file from SAP ICH or by uploading an IDOC Delvry file on the SAP ICH channel, the Allow unlimited overdelivery and underdelivery checkbox is automatically cleared, meaning that an unlimited delivery is not allowed. The tolerance values are automatically set but they remain configurable for an order in Open status:
    • The under-delivery tolerance value is 100%. This means under-delivery is allowed without restrictions.
    • The over-delivery tolerance value is 0%. This means over-delivery is not allowed, the maximum quantity is the target quantity.


In the following example:

  • We are filtering external orders that are in In shipping status and the search expression contains the order ID,  "OUT2402271730".
  • There is one search result that is selected.
    • The Outbound orders panel shows the Order ID and Order status columns.
    • The order master data (settings) are displayed as read-only.



5. Select the Line items tab to view the line items of the outbound order. You can expand a line item to view more details.

  • Line item number (#)
  • Product code
  • Status
  • Target quantity
  • Unit of measurement
  • Actions (Edit and Delete)


If unlimited over-delivery and under-delivery are allowed, the application explicitly indicates it. If the over-delivery and under-delivery are limited, the application displays the tolerance values.


The following example continues the previously selected order. The selected order has three line items.



6. Select the Deliveries tab to view the list of deliveries.

  • You can view the status of each delivery.
  • For each delivery, you can verify the warehouse where the delivery is executed.
    • The deliveries can be executed in different warehouses by receiving IDOC Delvry files from SAP ICH.
    • The IDOC Delvry specifies a warehouse site that points to a warehouse sublocation in the Serialized Logistics application. The application links the delivery to the warehouse while creating the delivery.
    • As a prerequisite, you must register all sublocations of all warehouses under the Site management > Warehouses tab.
  • If a route is specified for the delivery, you can verify the route name. Otherwise, the route name field is empty. 
    • It is only applicable when the delivery is created by receiving an IDOC Delvry file from SAP ICH.
    • The IDOC Delvry specifies the route, and the application links the delivery to the route while creating the delivery.
    • As a prerequisite, you must register all the routes under the Site management > Routes tab.
  • You can view the line items belonging to each delivery with the actual status.
  • For each delivery, you can verify the expected versus the shipped quantity per line item.
  • After selecting (clicking) a delivery, the application shows a snapshot of the picked case SSCCs, pallet SSCCs, and users (operators) for that delivery in a paginated view (5 items per page) in a pop-up (top to bottom hierarchy view).  
  • After selecting (clicking) a line item of a delivery, the application shows a snapshot of the included labels (trade items) with parents for that line item in a paginated view (10 items per page) in a pop-up (bottom to top hierarchy view).


The following example continues the previously selected order:

  • The order contains five deliveries. The order is a logical grouping of the deliveries.
  • The users are working on multiple deliveries in two warehouses in parallel for the same order.
  • Each delivery is linked to a route so the deliveries were created by receiving IDOC Delvry files from SAP ICH.
  • The fourth delivery, DEL24022704, is expanded.
    • The delivery is validated and ready for shipping.
    • The expected quantities versus the quantities to be shipped match.



After clicking on the delivery row (DEL24022704) in the above example, the application displays a pop-up that shows the picked SSCCs, pallet SSCCs, and users for that delivery in a tab view:


Displayed InformationExample
Picked SSCCs with their status and the underlying hierarchy

The picked case SSCCs come from the Validate Picking mobile action.

Each case SSCC can be expanded. If the underlying child trade items are aggregated, the items can be further expanded.
Pallet SSCCs with underlying hierarchy

The pallet SSCCs come from the Pack an order and Packing - orders (Pack to order) mobile actions.


Note: Pallets can also be created in the Packing - items mobile action, but those pallets are added to the delivery in the Pack an order mobile action.


Each pallet SSCC can be expanded to see the child containers and trade items:

  • Clicking on a child container opens the Picked SSCC History page with the underlying hierarchy that was shipped.
  • If the underlying child trade items are aggregated, the items can be further expanded.

Users

The Users tab shows the operators working on the delivery with their names and email address.


After clicking on the first line item ("Cialis") in the above example, the application displays a pop-up that shows the details of the trade items:

  • Where the quantity is greater than 1, the trade item contains child trade items.
  • For parent trade items, the product code is different from the product code of the line item. The difference is the first and the last digit of the product code. The included child trade items have the product code of the line item.
  • There are individual trade items where the product code matches the product code of the line item.
  • The trade items are aggregated into containers. Several containers are also aggregated (multi-level containers).
  • After expanding the first item, the application shows the hierarchy of the parent containers (Parent SSCCs).



7. Select the History tab to view the status changes of the order.


The following example continues the previously selected order.



Back to the list of procedures



Searching for and Viewing a Delivery


You select the delivery view and check the details.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. To open the delivery view, select Delivery ID in the ID column field. The application displays the list of deliveries in the Outbound deliveries panel.


Note: The application remembers the selected view mode until the user logs out.


3. Enter the delivery ID in the search field and/or apply filters:

  • Status changed (with datepicker) - It filters all deliveries that have a change in status on the selected day. By setting this filter, the Export Deliveries button becomes active. For more information, see Exporting the Deliveries of the Selected Day.
  • Status
  • Order type

After providing the search expression and applying filters:

  • The list of deliveries is filtered based on the search criteria.
  • You can reset the filter by clicking Reset filters.


4. Select the delivery to view the list of deliveries that belong to the order. The application displays the Update outbound order panel with the Deliveries tab.

  • You can view the status of each delivery.
  • For each delivery, you can verify the warehouse where the delivery is executed.
    • The deliveries can be executed in different warehouses by receiving IDOC Delvry files from SAP ICH.
    • The IDOC Delvry specifies a warehouse site that points to a warehouse sublocation in the Serialized Logistics application. The application links the delivery to the warehouse while creating the delivery.
    • As a prerequisite, you must register all sublocations of all warehouses under the Site management > Warehouses tab.
  • If a route is specified for the delivery, you can verify the route name. Otherwise, the route name field is empty. 
    • It is only applicable when the delivery is created by receiving an IDOC Delvry from SAP ICH.
    • The IDOC Delvry specifies the route, and the application links the delivery to the route while creating the delivery.
    • As a prerequisite, you must register all the routes under the Site management > Routes tab.
  • You can view the line items belonging to each delivery with the actual status.
  • For each delivery, you can verify the expected versus the shipped quantity per line item.
  • After selecting (clicking) a delivery, the application shows a snapshot of the picked case SSCCs, pallet SSCCs, and users (operators) for that delivery in a paginated view (5 items per page) in a pop-up (top to bottom hierarchy view).  
  • After selecting (clicking) a line item of a delivery, the application shows a snapshot of the included labels (trade items) with parents for that line item in a paginated view (10 items per page) in a pop-up (bottom to top hierarchy .


In the following example:

  • All deliveries with "DEL240227" in the delivery ID are listed. In this case, there are five deliveries in different statuses. The Outbound deliveries panel shows the Delivery ID and Delivery status columns. 
  • The fourth delivery "DEL24022704" is selected. The application displays all the deliveries, including the selected one, that belong to the same order on the right.
  • The deliveries filtered on the left side and the deliveries of the order on the right side match. The order is a logical grouping of the deliveries.
  • The users are working on multiple deliveries in parallel for the same order.
  • Each delivery is linked to a warehouse and a route so the deliveries were created by receiving IDOC Delvry files from SAP ICH.
  • The fourth delivery, which is selected, is in Picking validated status. The delivery is highlighted in green on the right side so the expected quantities match the quantities to be shipped.



After expanding the delivery, the application displays the quantities per line item:



After clicking on the delivery row (DEL24022704) in the above example, the application displays a pop-up that shows the picked SSCCs, pallet SSCCs, and users for that delivery in a tab view:


Displayed InformationExample
Picked SSCCs with their status and the underlying hierarchy

The picked case SSCCs come from the Validate Picking mobile action.

Each case SSCC can be expanded. If the underlying child trade items are aggregated, the items can be further expanded.
Pallet SSCCs with underlying hierarchy

The pallet SSCCs come from the Pack an order and Packing - orders (Pack to order) mobile actions.


Note: Pallets can also be created in the Packing - items mobile action, but those pallets are added to the delivery in the Pack an order mobile action.


Each pallet SSCC can be expanded to see the child containers and trade items:

  • Clicking on a child container opens the Picked SSCC History page with the underlying hierarchy that was shipped.
  • If the underlying child trade items are aggregated, the items can be further expanded.

Users

The Users tab shows the operators working on the delivery with their names and email address.


After clicking on the second line item ("Olumiant") in the above example, the application displays a pop-up that shows the details of the trade items:

  • Where the quantity is greater than 1, the trade item contains child trade items.
  • For parent trade items, the product code is different from the product code of the line item. The difference is the first and the last digit of the product code. The included child trade items have the product code of the line item.
  • There are individual trade items where the product code matches the product code of the line item.
  • The trade items are aggregated into containers. Several containers are also aggregated (multi-level containers).
  • After expanding the first item, the application shows the hierarchy of the parent containers (Parent SSCCs):



5. Select the Settings tab to view the order details.

  • You can view the order master data such as order ID, order type, destination information, dates and deadlines, and the under-delivery/over-delivery settings.
  • If the order is created by receiving an IDOC Delvry file from SAP ICH or by uploading an IDOC Delvry file on the SAP ICH channel, the Allow unlimited overdelivery and underdelivery checkbox is automatically cleared, meaning that an unlimited delivery is not allowed. The tolerance values are automatically set but they remain configurable for an order in Open status:
    • The under-delivery tolerance value is 100%. This means under-delivery is allowed without restrictions.
    • The over-delivery tolerance value is 0%. This means over-delivery is not allowed, the maximum quantity is the target quantity.


The following example continues the previously selected delivery (order). The order settings are read-only:



6. Select the Line items tab to view the line items of the outbound order the selected delivery belongs to. You can expand a line item to view more details.

  • Line item number (#)
  • Product code
  • Status
  • Target quantity
  • Unit of measurement
  • Actions (Edit and Delete)


If unlimited over-delivery and under-delivery are allowed, the application explicitly indicates it. If the over-delivery and under-delivery are limited, the application displays the tolerance values.


The following example continues the previously selected delivery (order). The order of the delivery has three line items.



7. Select the History tab to view the status changes of the order.


The following example continues the previously selected delivery (order).



Back to the list of procedures



Updating an Outbound Order


If the order is in Open status, you can update the order settings (master data) as well as the line items. You can add line items, edit the existing line items, and delete line items at the order level. As the line items are linked to the delivery, the delivery is adjusted when adding a line item to or removing a line item from the order.


Once the order is in In shipping or Paused shipping status, you cannot edit the master data (settings) of an order but you can manage the line items.


When updating an outbound order, avoid any change that is not in line with the data in an external system. Especially, when the order was created through API or by sending an IDOC Delvry from SAP ICH.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. Find and select the order you want to update. The application displays the Update outbound order panel with the Settings tab.


3. For an order in Open status, modify the order settings (as applicable).


4. Select the Line items tab and manage the line items of the order as needed.


Operation on Line ItemDescription
AddClick Add Line Item, fill in the form as described below, and click Add. The required fields are marked with an asterisk (*) in the form.

FieldDescription
Line item numberEnter the line item number. The application auto-fills the field and provides "1" for the first line item. When adding a new line item, the application automatically offers a new value. You can change the line item number based on your preference but two line items cannot have the same number.
Product code schemaSelect the product code schema.
  • GTIN
  • PPN
Select productSelect a product code. The application displays a searchable drop-down with a prefiltered list of products. You can search for any product registered in the system by entering the product code or the product name in the search field.
BatchSpecify a batch for the product code (if applicable). If you don't know the batch, you can leave the field empty. In this case, the application accepts any batch that is scanned for the product.


You can select an existing batch or you can specify one inline. The application displays a searchable drop-down with a list of batches available for that product code in the system.

  • You can search for a batch of the product by entering the batch number (ID) in the search field.
  • If the entered batch is not existing, you can create the batch by clicking on the Create batch button displayed in the search drop-down.


You can clear the field by clicking on the X button on the right side of the drop-down.

QuantityEnter the quantity to be shipped. A positive number is accepted only.
Unit of measurementEnter the unit of measurement of the quantity. Free-form text field.
Sales quantityOptionally, enter the sales quantity. A positive number is accepted only.
Sales unit of measurementOptionally, enter the unit of measurement of the sales quantity. Free-form text field.
EXAMPLE 1

The following example illustrates the case when adding a line item that has a product with an existing batch:



EXAMPLE 2


The following example illustrates the case when the batch is specified inline while adding the line item:




You can add multiple line items that have different or the same product data, there is no restriction. For example:

  • You have two line items with the same product code and batch but with different sales parameters.
  • You have line items with completely different product codes, batches, and other data.
EditClick on the edit icon, modify the parameters in the opened form as described above, and click Save.
DeleteClick on the delete icon.

Note: The application does not request confirmation but it immediately removes the line item from the list.

Example:



Back to the list of procedures



Validating Picking for a One-Case Delivery


You can validate a one-case delivery in the Admin UI when the following conditions are met:

  • The delivery is in In picking validation status.
  • Its single case (SSCC) was validated during the Validate picking action in the mobile application.
  • The scanned quantity does not meet the expected quantity.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. In delivery view mode, find the delivery you want to validate. For the potential deliveries in In picking validation status, the application displays a checkmark icon (Validate button) in the Action column.


3. Review the order settings, the line items of the order, the delivery details, and the order history.


The following example illustrates a one-case delivery, "MULTIDEL070603", in In picking validation status.

  • All items are scanned into one picked case SSCC that is validated. The checkmark icon (Validate picking) is visible in the Action column.
  • The delivery belongs to an order that contains five deliveries. The selected delivery is the third one in the list and it is expanded.
  • The delivery contains two line items. For each line item, the expected quantity is 12 while the scanned quantity is 6 waiting for validation.



After selecting the delivery, the application displays a pop-up about the picked SSCCs, pallet SSCCs, and users in a tab view.

  • One picked case SSCC contains all the items. The SSCC is expanded to show the underlying hierarchy.



  • It is a one-case delivery because there is no pallet SSCC.



  • One user is linked to the delivery.



4. Click on the checkmark icon (Validate picking) in the Action column.



5. Confirm the action by clicking Yes in the pop-up.


If there is under-delivery below the tolerance value, the application displays an error message:

  • You can reverse the validation status of the picked case SSCC and address the under-delivery. For more information, see Reversing the Validation Status of a Picked Case SSCC.
  • Over-delivery is already checked in the Validate Picking mobile action that precedes this procedure.
  • By default, over-delivery is not allowed while it is possible to include less than the expected quantity or do not include anything for a line item (product). However, custom delivery limits may apply as set by a user in the Admin UI for the parent outbound order.


If the delivery totals are within the tolerance range, the delivery goes to Picking validated status and the application shows the truck icon (Ship delivery) in the Action column.


Next Steps


Release (Ship) the delivery.


Back to the list of procedures



Releasing (Shipping) a Delivery


If the delivery is in Picking validated status, the delivery is ready for shipping. You can review the delivery in the Admin UI and ship it.


The delivery is in Picking validated status due to one of the following reasons:

  • The delivery is a one-case delivery and its case is validated during the Validate picking action in the mobile application because the scanned quantity meets the expected quantity.
  • The delivery is a one-case delivery that is validated by a user in the Admin UI because the scanned quantity does not meet the expected quantity. As a prerequisite, the case is validated during the Validate picking action in the mobile application.
  • The delivery is a multi-case delivery without pallets that was validated by the user in the Pack an order action in the mobile application.
  • The delivery is a pallet delivery that was constructed and validated by the user in the Pack an order action in the mobile application.


Note: Shipping a delivery is possible in the mobile application but this action is another execution route and not part of the description below.



Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. In delivery view mode, find the delivery you want to ship. The delivery must be in Picking validated status.


3. Verify the color of the delivery in the delivery list on the right.

  • If the selected delivery is highlighted in green on the right, the expected quantities and the quantities to be shipped match.
  • If the selected delivery is highlighted in red on the right, the delivery needs attention. There is a quantity mismatch. The expected quantity does not match the quantity to be shipped for one or more line items.  


The following example illustrates delivery "MULTIDEL070602" in Picking validated status:

  • The delivery belongs to an order that contains five deliveries.
  • The selected delivery is the second one in the list and it is highlighted in green which means the expected quantities and the quantities to be shipped match.



The following example illustrates delivery "DEL24021302" in Picking validated status:

  • The delivery belongs to an order that contains four deliveries.
  • The selected delivery is the second one in the list and it is highlighted in red which means there is a quantity mismatch. The delivery needs attention.
    • Note: The same is true for the third delivery, but only the second delivery is elaborated in this description and the same approach applies to all other deliveries that are highlighted in red.



4. View the details of the delivery:

  • Expand the delivery to see the quantities.
  • Select the delivery to view the picked case SSCCs, pallet SSCCs, and users.


The following example illustrates the scenario when the previous delivery (DEL24021302) is expanded. There is under-delivery for both line items of the delivery.



After selecting the delivery, the application displays a pop-up about the picked SSCCs, pallet SSCCs, and users in a tab view.

  • There are two picked case SSCCs for the delivery. The first SSCC is expanded to show the underlying hierarchy.



  • It is a multi-case delivery because there are no pallet SSCCs.



  • Two users are linked to the delivery.



5. Confirm that the delivery data are correct.


6. Before shipping, confirm that there is no empty container (SSCC) in the delivery.


It also applies to deliveries that are highlighted in green. The application displays the delete icon next to empty containers (SSCCs). For more information, see Removing Empty Containers (SSCCs) from a Delivery.


7. Click on the truck icon (Ship delivery) in the Action column.


Example:



8. Confirm the action by clicking Yes in the pop-up. 


The application processes the shipping, so the delivery goes to Processing shipping status:



Once the processing is completed, the delivery goes to Shipped status.


An EPCIS file is generated and sent to SAP ICH as a DSCSA shipping event in case of the following conditions are met:

  • An SAP ICH channel is configured for the tenant.
  • The client is located in the United States.
  • The supplier of the shipped products is registered and the SAP ICH channel is associated with this supplier.
  • The tenant acts as a 3PL for the supplier.


If an issue occurs during the processing, the application displays an error message and the delivery goes back to Picking validated status. Once the error is identified and resolved, you can retry the shipping.


Back to the list of procedures



Removing Empty Containers (SSCCs) from a Delivery


Sometimes operators in the warehouse can scan containers (SSCCs) and then realize that they scanned the wrong one without removing that container from the delivery. This causes issues during shipping because empty containers cannot be shipped. An authorized user can remove the empty and unnecessary containers from the delivery.


If the empty container is a picked case SSCC that is put on a pallet SSCC, it is not possible to remove the empty picked case SSCC from the delivery. To resolve the issue, the user has to remove the empty picked case SSCC from the pallet SSCC in the Pack an order mobile action while the delivery is in In picking validation status, and then retry the procedure below.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. In delivery view mode, find the delivery where you want to check empty containers. The delivery is in In picking validation or Picking validated status.


3. In the Update outbound order panel, select the delivery under the Deliveries tab to view the picked case SSCCs and pallet SSCCs.


The following example illustrates a scenario when selecting the last delivery from the list (DEL24021304) on the right panel.



The application shows the picked case SSCCs, pallet SSCCs, and users for that delivery in a tab view in a pop-up. The application indicates empty SSCCs by showing the delete icon next to the SSCC.

  • Example of empty picked case SSCCs - The last two in the list:



  • Example of an empty pallet SSCC - The last one in the list:



4. Find the SSCC that you want to delete.


5. Click on the delete icon next to the SSCC.


The following example illustrates the scenario when removing an empty picked case SSCC from the delivery. The case SSCC is validated:



The following example illustrates the scenario when removing an empty pallet from the delivery:



6. Confirm the action by clicking Yes in the pop-up.

  • The SSCC is removed from the related list.
  • If the SSCC is not empty because someone has added an item to it in parallel and the browser is not refreshed on your side, the application displays an error message, Container selected is not empty.


Back to the list of procedures



Reversing the Validation Status of a Delivery


For a delivery in Picking validated status, an authorized user can reverse the status to In picking validation status. This option is useful when you find an issue on a delivery that shall be addressed before shipping. 


After reversing the status, the delivery becomes active on the shopfloor again. The operators in the warehouse can work on the delivery in the Validate Picking, Packing - items, Packing - orders, and Pack an order mobile actions.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. In delivery view mode, find the delivery where you want to reverse the status. The delivery must be in Picking validated status.


The following example illustrates a delivery where the delivery totals do not match, hence the delivery is highlighted in red on the right:



3. View the details of the delivery:

  • Expand the delivery to see the quantities.
  • Select the delivery to view the picked case SSCCs, pallet SSCCs, and users.


4. Click on the back arrow icon (Reverse validation status) next to the delivery in the Action column.


Example:



5. Confirm the action by clicking Yes in the pop-up.

  • The delivery status goes back to In picking validation status.
  • The payload of the shipment remains untouched.


Next Steps


You can reverse the validation status of a picked case SSCC by using the back arrow icon (Reverse validation status) next to the SSCC. For more information, see Reversing the Validation Status of a Picked Case SSCC.


You can delete an empty picked case SSCC by using the delete icon (if any). For more information, see Removing Empty Containers (SSCCs) from a Delivery.


The operators in the warehouse can work on the delivery.


Back to the list of procedures



Reversing the Validation Status of a Picked Case SSCC


If a delivery in In picking validation status contains a picked case SSCC in Picking validated status, an authorized user can reverse the case SSCC status to In picking validation status. This option is useful when you want to re-open a case SSCC for the Validate Picking mobile action.


If the picked case SSCC is put on a pallet SSCC, it is not possible to reverse its validation status. To resolve the issue, the user has to remove the picked case SSCC from the pallet SSCC in the Pack an order mobile action, and then retry the procedure below.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. In delivery view mode, find the delivery that contains the picked case SSCC for which you want to reverse the validation status. The delivery must be in In picking validation status.


3. In the Update outbound order panel, select the delivery under the Deliveries tab to view the picked case SSCCs.


The following example illustrates a scenario when selecting the first delivery from the list (DEL24022701) on the right panel.



The application shows the picked case SSCCs, pallet SSCCs, and users for that delivery in a tab view in a pop-up. The following example illustrates the picked case SSCCs of the previously selected delivery:



4. Find the picked case SSCC for which you want to reverse the validation status.


5. Click on the back arrow icon (Reverse validation status) next to the picked case SSCC.


Example:



6. Confirm the action by clicking Yes in the pop-up.

  • The status of the picked case SSCC goes back to In picking validation status.
  • The payload of the shipment remains untouched.


Next Steps


The operators in the warehouse can work on the case SSCC in the Validate Picking mobile action.


Back to the list of procedures



Reversing All the Activities of a Delivery


An authorized user can reverse all the activities of a delivery and move back the delivery to Open status. The function is available while the delivery is in In picking validation or Picking validated status.


IMPORTANT: The reverse action withdraws all activities on the delivery, so all activities performed on the delivery will be lost. Use the function carefully.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. In delivery view mode, find the delivery where you want to reverse all the activities. The delivery must be in In picking validation or Picking validated status.


The following example illustrates a delivery where the delivery totals do not match, hence the delivery is highlighted in red on the right:



3. View the details of the delivery to make sure you are going to reverse all the activities of the right delivery:

  • Expand the delivery to see the quantities.
  • Select the delivery to view the picked case SSCCs, pallet SSCCs, and users.


The following example illustrates the scenario when the previous delivery (DEL23092701) is expanded that is a pallet delivery:

  • There are quantity mismatches for two line items (unlimited delivery is allowed for the parent outbound order).
  • For one of the line items (Castor Oil), nothing is scanned.



After selecting the delivery, the application displays a pop-up about the picked SSCCs, pallet SSCCs, and users in a tab view.

  • There are three picked case SSCCs for the delivery. The first SSCC is expanded to show the underlying hierarchy.



  • There are four pallet SSCCs for the delivery. The first pallet SSCC is expanded to show the underlying hierarchy.



  • Two users are linked to the delivery.




4. Click on the circular arrow icon that has a clock inside (Reverse all activities) next to the delivery in the Action column.


IMPORTANT: Before proceeding, make sure that reversing all the activities of the delivery is the correct approach. All activities on the delivery will be lost due to this action. You can decide to reverse the validation status of the delivery only; in that case, the activities on the delivery are not lost but can be corrected. 


Example:



5. Confirm the action by clicking Yes in the pop-up.

  • The reversed delivery goes back to Open status. The delivery can be executed later or can be deleted.
  • The picked quantity is reset to 0.
  • The previously assigned items are detached from the delivery and are in stock again. They can be reused for this delivery or another delivery.
  • All containers (SSCCs) that were printed and used for aggregation in Movilitas.Cloud are cleared (no hierarchy below) but the containers remain in Commissioned status in the system. They can be reused for this delivery or another delivery.
  • Homogeneous (full) pallets added to the delivery through the Packing - orders (Pack to order) mobile action are untouched, however, they are detached from the delivery. They can be reused for this delivery or another delivery.


Next Steps


You can delete the delivery or the operators in the warehouse can execute the delivery again from scratch.


Back to the list of procedures



Exporting the Deliveries of the Selected Day


You can export the deliveries with a status change on the selected day to a Microsoft Excel (.xlsx) file. The file lists the details of each delivery on a line item basis.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. In delivery view mode, set the Status changed filter by using the datepicker. The Export Deliveries button becomes active.


Example:



Note: If you find the Export Deliveries button inactive, you are not in the right view. Hover your mouse over the button to get some help on how to make the button active.


3. Click on Export Deliveries. The application displays a pop-up to specify the location of the file.


4. Save the file to your local computer.


Back to the list of procedures



Deleting an Outbound Order


You can delete the orders that do not have scanned items. Once items have been scanned for the order, you cannot delete the order.


IMPORTANT: Deleting an order deletes all the deliveries of the order. By deleting an order, you lose all connected deliveries.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. In order view mode, find the order you want to delete.


Example:



3. Click the delete icon next to the order and confirm the deletion by clicking Yes.


Back to the list of procedures



Deleting a Delivery


You can delete the deliveries that do not have scanned items:

  • Deleting a delivery does not delete the order that contains that delivery but the line item settings at the order level are adjusted.
  • Deleting a delivery does not have any impact on the order master data (settings).
  • It is possible to delete all the deliveries of an order.


Procedure


1. In the Serialized Logistics application, select the Orders --> Outbound orders tab. The application displays the list of outbound orders or deliveries, depending on the selected view.


2. In delivery view mode, find the delivery you want to delete.


Example:



3. Click the delete icon next to the delivery and confirm the deletion by clicking Yes.


Back to the list of procedures