You can set up the Serialized Logistics application to do the logistics of serialized items.


You can manage the Serialized Logistics application through the main tabs below:


Orders


Orders organize the activities in the warehouse. The following table summarizes the order types:


Order TypeDescription
InboundInternalDelivery from another warehouse of your company.
ExternalDelivery from your supplier.
ReturnReturn from a client or from another warehouse of your company.
OutboundInternalShipment to another warehouse of your company.
ExternalShipment 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 in the Admin UI.
    • You can update an order.
    • You can delete an order.
    • You can validate a one-case outbound order and move it to Picking validated status when the following conditions are met:
      • The order 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.
    • You can ship an outbound order that is in Picking validated status due to one of the following reasons:
      • The order is a one-case order and its case is validated during the Validate picking action in the mobile application because the scanned quantity meets the expected quantity.
      • The order is a one-case order 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 order is a multi-case order that is validated by the user during the Pack an order action in the mobile application.

Note: In all other cases, shipping the outbound order is possible in the mobile application only.


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. 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, 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.


Transfers


Transfers record what was executed in the warehouse. The following table summarizes the transfer types.


Transfer TypeDescription
Inbound internalReceive by batch
Items were received by batch. The items come from the manufacturing site of your company (set as a warehouse).

When connecting to BPOM (Indonesia), the event is reported through the BPOM channel set for the warehouse.
Receive by stock transfer IDItems were received by stock transfer ID. The items come from another warehouse of your company.

When connecting to BPOM (Indonesia), the event is reported through the BPOM channel set for the warehouse.
Inbound external DeliveriesItems were received from a supplier by executing an inbound external order. The inbound external order was created in Movilitas.Cloud in advance.
ReturnsItems were received as a return from a client.
Outbound internalShip by batchItems were shipped by batch from the manufacturing site (set as a warehouse) of your company to another warehouse of your company.

When connecting to BPOM (Indonesia), the event is reported through the BPOM channel set for the warehouse.
Ship by stock transfer IDItems were shipped by stock transfer ID to another warehouse of your company.

When connecting to BPOM (Indonesia), the event is reported through the BPOM channel set for the warehouse.
Outbound externalOrders
Items were shipped to a client by executing an outbound external order. The outbound external order was created in Movilitas.Cloud in advance.

If the outbound external order is a Third-Party Logistics (3PL) activity on behalf of the supplier, the items are shipped to the USA, and an SAP ICH channel is configured for the supplier, the following applies:
  • The application generates an EPCIS 1.2 file (DSCSA shipping) and sends it to SAP ICH.
  • The EPCIS file is constructed as per the DSCSA requirements. It contains the product master data, DSCSA transaction statement, supplier/client information, commissioning, aggregation, and shipping events.
  • A log is created on the SAP ICH business channel associated with the supplier.
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.

  • If 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, one of the following is applicable:
    • Shipping to 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.
    • Shipping to the 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 associated with the supplier.
  • If the outbound external transfer is performed by a distributor that sells products to clients in the USA, the application generates an EPCIS 1.2 file. The EPCIS file is constructed as per the DSCSA requirements. The user can download the file to the local computer. 
  • When a CMO reports a shipping event from SAP ATTP to a MAH in TraceLink, 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.
  • When a CMO sends a generic report from SAP ATTP to Movilitas.Cloud to report an import request to 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.


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).


Products


You can view the list of products managed in the application.


Batch History


You can view the history of a batch managed in the application. You can also keep the stock data up-to-date related to the selected batch.


SSCCs


You can create and manage serial shipping container code (SSCCs) sequences as per the GS1 standard. You can also 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.


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 control the access to the Admin UI for users with the "User" role.


For more information on typical use cases, see the Serialized Logistics Workflows.