You can set up the Serialized Logistics application to perform logistics activities on the items in your warehouse.
You can manage the Serialized Logistics application through the main tabs as described below.
TABLE OF CONTENTS
Orders
An order is a logical grouping of one or more deliveries. An order organizes the activities in the warehouse through the linked deliveries. The following table summarizes the order types:
| Order Type | Description | |
|---|---|---|
| Inbound | Internal | Delivery from another warehouse of your company. |
| External | Delivery from your supplier. | |
| Return | Return from a client or from another warehouse of your company. | |
| Outbound | Internal | Delivery (shipment) to another warehouse of your company. |
| External | Delivery (shipment) to your client. | |
The following operations are supported with orders:
- You can create the orders in the Admin UI, over the Serialized Logistics V2 API, or by an IDOC Delvry (outbound order only).
- You can manage the orders (deliveries) in the Admin UI.
- You can track the progress of the orders (deliveries):
- Orders (deliveries) that are prepared in the mobile application and shipped in the Admin UI.
- Orders (deliveries) that are prepared and shipped in the mobile application.
- You can update an order.
- You can delete an order.
- You can cancel/delete a delivery of an order.
- On outbound, you can validate a one-case delivery and move it to Picking validated status when the following conditions are met:
- The delivery is in In picking validation status.
- Its case (SSCC) was validated during the Validate picking action in the mobile application.
- The scanned quantity does not meet the expected quantity.
- On outbound, you can ship a delivery that 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 the authorized 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. The delivery is validated during the Pack an order action in the mobile application.
- The delivery is a pallet delivery that is built up and validated during the Pack an order action in the mobile application.
- Note: Besides manual shipping, the delivery can be automatically shipped by receiving an ASN IDOC from SAP ICH.
- On outbound, you can export the deliveries of the selected day to a Microsoft Excel file.
- On outbound, you can edit the delivery and inventory (reverse functions and removing empty containers from the delivery).
- You can track the progress of the orders (deliveries):
Pickings
You can track the pick lists that are created in the warehouses. Picking is a preparation step before shipping the items to a client as an outbound external transfer. The activity is similar to filling a shopping cart. The content of the shopping cart can change before the actual shipping. The goal is to accelerate the shipping activity.
A pick list is identified by a purchase order ID but the order is not created in Movilitas.Cloud in advance. This purchase order ID is used in the next step when shipping the items to a client. Once the items are shipped:
- An outbound external transfer is created with the same purchase order ID.
- The related pick list disappears from the Pickings view.
When shipping to Bahrain or the UAE (Tatmeen), you can also verify the EPCIS file generation for a pick list. This is a quality check to avoid the situation when the EPCIS file cannot be generated for a released shipment.
You can delete an empty pick list or all empty pick lists at once.
Transfers
Transfers record what was executed in the warehouse. The following table summarizes the transfer types.
| Transfer Type | Description | |
|---|---|---|
| Inbound internal | Receive by batch | Items were received by batch. The items come from the manufacturing site of your company (set as a warehouse). |
| Receive by stock transfer ID | Items were received by stock transfer ID. The items come from another warehouse of your company. | |
| Inbound external | Deliveries | Items were received from a supplier in one of the following ways:
|
| Returns | Items were received as a return from a client. | |
| Outbound internal | Ship by batch | Items were shipped by batch from the manufacturing site (set as a warehouse) of your company to another warehouse of your company. |
| Ship by stock transfer ID | Items were shipped by stock transfer ID to another warehouse of your company. | |
| Outbound external | Orders | Items were shipped to a client by executing a delivery. Before the execution, the delivery was created together with the order or it was added to an existing order in Movilitas.Cloud. |
| Transfers | Items were shipped to a client by purchase order ID but the order was not created in Movilitas.Cloud before the execution. The transfer was created on the fly in the mobile application or automatically after triggering the action from SAP ATTP. | |
| Returns transfer | Items were returned to a supplier by return ID (VRA) but an order was not created in Movilitas.Cloud before the execution. The transfer was created on the fly in the mobile application. | |
System Actions Triggered by an Inbound Internal Transfer (By batch or by stock transfer ID)
When connecting to BPOM (Indonesia), the event is reported through the BPOM channel set for the warehouse.
System Actions Triggered by an Inbound External Delivery
If the tenant acts as a 3PL for the supplier and a TraceLink channel is associated with the supplier as the collaboration channel, a receipt event (EPCIS file) is reported to the supplier through the TraceLink channel.
System Actions Triggered by an Inbound External Return
When receiving returns in a warehouse that is in Saudi Arabia and the warehouse has an SFDA regulatory channel, the action triggers requests to SFDA RSD as follows:
- If the client that returned the items is in Saudi Arabia, a Dispatch Cancel message is sent to SFDA RSD. The Dispatch Cancel message describes the lowest level of trade items.
- If the client that returned the items is in a country other than Saudi Arabia, an Export Cancel message is sent to SFDA RSD. The Export Cancel message describes the lowest level of trade items.
System Actions Triggered by an Outbound Internal Transfer (By batch or by stock transfer ID)
When connecting to BPOM (Indonesia), the event is reported through the BPOM channel set for the warehouse.
System Actions Triggered by an Outbound External Order
If the delivery is a Third-Party Logistics (3PL) activity on behalf of the supplier and an SAP ICH channel is configured for the supplier, the application generates an EPCIS 1.2 file and sends it to SAP ICH. A log is created on the SAP ICH business channel associated with the supplier. The format of the EPCIS file follows the client configuration settings:
- DSCSA shipping message (USA) - A DSCSA EPCIS file that contains the product master data, DSCSA transaction statement, supplier/client information, commissioning, aggregation, and shipping events.
- Full shipping message - A regular EPCIS file that contains the commissioning, aggregation, and shipping events.
If the delivery is a non-3PL activity (being a distributor or manufacturer) and a collaboration channel for outbound DSCSA EPCIS is associated with the client in the USA, a DSCSA EPCIS file is generated and sent over the channel. The following connections are supported:
- AS2
- LSPediA
- SFTP
- TraceLink
System Actions Triggered by an Outbound External Transfer
| Scenario | Shipping Destination | Description |
|---|---|---|
| The outbound external transfer is performed by a distributor in Indonesia | Within Indonesia | The event is reported to BPOM through the BPOM channel set for the warehouse. |
| The outbound external transfer is a Third-Party Logistics (3PL) activity on behalf of the supplier being the Marketing Authorization Holder (MAH) of the shipped items | Bahrain | The application generates an EPCIS 1.2 file. The file contains the commissioning, aggregation, and shipping events. The user can download the file to the local computer and send it to the supplier. If a TraceLink Partner channel is associated with the supplier as the collaboration channel, a shipment file is sent to TraceLink. |
| UAE | The application generates an EPCIS 1.2 file (manufacturing report) and sends it to Tatmeen on behalf of the supplier (MAH). The file contains the commissioning, aggregation, and shipping events. A log is created on the Tatmeen regulatory channel that is associated with the supplier. Depending on the client configuration, the application sends the EPCIS file by email and/or to an SFTP server through a previously configured SFTP channel. If a TraceLink Partner channel is associated with the supplier as the collaboration channel, a shipment file is sent to TraceLink. | |
| Within Saudi Arabia | The application sends the Dispatch and Package Upload messages to SFDA RSD. A separate log per message is created on the SFDA regulatory channel that is associated with the warehouse:
If a TraceLink Partner channel is associated with the supplier as the collaboration channel, a shipment file is sent to TraceLink. | |
| From Saudi Arabia to Another Country | The application sends the Export message to SFDA RSD. A log per message is created on the SFDA regulatory channel that is associated with the warehouse. The Export describes the lowest level of trade items. If a TraceLink Partner channel is associated with the supplier as the collaboration channel, a shipment file is sent to TraceLink. | |
| The outbound external transfer is performed by a distributor that sells products to clients in the USA | USA | The application generates an EPCIS 1.2 file. The EPCIS file is constructed as per the DSCSA requirements. If a collaboration channel for outbound DSCSA EPCIS is associated with the client, the file is sent over the channel automatically after the shipment is created. The following connections are supported:
On the transfers page, the user can download the file to the local computer and/or send it to the client in one of the following ways:
If the distributor and the client are partners in Movilitas.Cloud, the EPCIS file is automatically processed on the client's side. The client can download the EPCIS file from its partner supplier (distributor) in the client view. |
| A CMO reports a shipping event from SAP ATTP to an MAH in TraceLink | N/A | The application creates an outbound external transfer based on the input from SAP ATTP and the configuration. The user can verify the transfer in the application. |
| The manufacturer ships items to a wholesaler client in the UAE. The manufacturer triggers the shipping event from SAP ATTP to Movilitas.Cloud and the client is in partnership with the manufacturer in Movilitas.Cloud. | UAE | In the CMO view in Movilitas.Cloud, the application creates an outbound external transfer based on the input from SAP ATTP and the configuration. The user can verify the transfer in the application. In the client view in Movilitas.Cloud, the EPCIS file is generated and automatically processed. The user can download the EPCIS file from its partner supplier. |
| A CMO sends a generic report from SAP ATTP to Movilitas.Cloud to report an import request to Kazakhstan | Kazakhstan | The application creates an outbound external transfer based on the input from SAP ATTP and the configuration. The user can verify the transfer in the application. |
System Actions Triggered by an Outbound External Return
The outbound external return is performed by a distributor or a dispenser in the USA. The distributor or dispenser detects an issue with an item during receipt and returns the item to the supplier. The application generates an EPCIS 1.2 file. The EPCIS file is constructed as per the DSCSA requirements. On the transfers page, the user can download the file to the local computer.
Site Management
You can do all the administration related to the warehouses where the activities are performed:
- Configuring warehouses, sublocations, and storage locations.
- Activating operators.
- Assigning a warehouse and privileges to each operator.
- Assigning printer and scanner devices to each operator.
- Activating specific settings of the mobile application at the operator level.
- Registering your suppliers (inbound) and their products.
- Uploading an EPCIS 1.1 or 1.2 input file from a supplier.
- Registering your clients (outbound).
- Registering the routes that are used for deliveries to clients. Note: The delivery is registered by receiving an IDOC Delvry file from SAP ICH and each delivery refers to a route.
- Establishing a partnership with your suppliers and/or clients in Movilitas.Cloud.
- Verifying the EPCIS file received from a supplier in partnership, through a collaboration channel (SAP ICH, TraceLink, AS2, or LSPediA), or over API.
- (DSCSA USA only) Viewing the exceptions against the received EPCIS file from the supplier that occurred while receiving items in the warehouse.
Products
You can view the list of products managed in the application. When acting as a 3PL for the supplier and the shipment details are received in an EPCIS file from the supplier, you can view the inventory of a product, that is, how many items are in stock (in possession) per batch.
Batch History
You can view the history of a batch managed in the application. You can give the missing manufacturing date of a batch. You can also keep the stock data up-to-date related to the selected batch.
SSCCs and Packs
You can create and manage serial shipping container code (SSCCs) sequences as per the GS1 standard.
You can request the historical activities connected to each container.
Note: The SSCC pool is a shared collection between the Serialized Manufacturing and the Serialized Logistics applications.
You can request the historical activities connected to each pack.
Labels
You can create ZPL label templates for SSCCs.
Settings
This tab allows you to configure the application-level settings.
- You can select a default business channel for communication with an external system.
- You can provide an external GS1 Digital Link Resolver server URL so that Movilitas.Cloud can connect to the server to present digital information to the operators about the scanned pack.
- You can provide a Scandit license key to use matrix scanning in the installed version of the mobile application.
- You can forbid or allow packing and shipping of unknown items for orders.
- You can forbid or allow shipping of unknown items for transfers.
- You can configure the DSCSA USA settings for TI trace:
- Activate the ATP credentialing for TI trace responses.
- Provide an email to receive TI trace requests from your clients.
- Provide an email and phone number for DSCSA exceptions.
- You can configure the DSCSA USA letter settings for replacement orders.
- You can control the access to the Admin UI for users with the "User" or "Support" role.
For more information on typical use cases, see the Serialized Logistics Workflows.
