This section provides an overview of how to configure and manage the Serialized Logistics application. The Serialized Logistics application supports companies in carrying out transfer, verification, and other logistics-related activities in their warehouses and reporting these activities to the market (when applicable).


The workflows below illustrate typical use cases for the user. The description is not exhaustive and is not meant to be exhaustive. The goal is to help the users to get an idea of how to use the application for certain activities.


IMPORTANT:

  • In the below use cases, we assume that you have already activated the Serialized Logistics application in Movilitas.Cloud. For certain cases, the Reports & Analysis application also needs to be activated in Movilitas.Cloud. This is a one-time activity when you start your journey with Movilitas.Cloud. For more information, see Enabling Applications for a Tenant.
  • For users that have the “User” or "Support" role, the administrators of the tenant can configure access to the Serialized Logistics application but this is optional. In this way, the administrators can customize the available functions for each user with the “User”  or "Support" role. For more information, see Roles and Access to the Serialized Logistics Application.


List of Use Cases


Reporting Transfers to BPOM (Indonesia)


In this use case, you want to perform shipping and receiving activities in your warehouses and report these activities to BPOM. Your warehouses can have either the manufacturer or the distributor role.



Before You Begin


Make sure that:

  • You have added mobile users to your tenant. For more information, see Managing Users of a Tenant.
  • You have configured the BPOM channels you need. For more information on the channel, see BPOM.


For the BPOM channel, specify the type of the shipping locations (warehouse or client) and import them to the Serialized Logistics application. The imported shipping locations are available under the Site management --> Warehouses or Site management --> Clients tab, respectively.


Procedure


1. (Optional) Set the default channel under the Serialized Logistics application --> Settings tab. For more information, see Settings.


2. Configure the site-related aspects.


OptionAction
Warehouses

Configure the warehouses where the scanning activities will be performed:

  1. Specify the name, address, country, assign the BPOM channel as the regulatory channel.
  2. Define whether the warehouse is involved in manufacturing or distribution activities. For a manufacturing site, you can activate commissioning while shipping.
  3. Optionally, assign devices to the warehouses by giving their Universally Unique Identifier (UUID). Only the given device can be used in the warehouse.


Note: The BPOM shipping locations specified as warehouses on the BPOM channel settings page are automatically imported and are available in the list. The configuration form is prefilled with the existing data and the application displays the text Imported through BPOM channel under the warehouse name in the list.

Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the privileges, that is, what activities they can perform.
  3. Optionally, activate ignoring double scans per operator to make scanning faster.
  4. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.
Clients

Specify the clients that are the destinations of the shipping activities (outbound external only).


Note: The BPOM shipping locations specified as clients on the BPOM channel settings page are automatically imported and are available in the list. The configuration form is prefilled with the existing data and the application displays the text Imported through BPOM channel under the client name in the list.


For more information, see Managing Warehouses, Managing Operators, and Managing Clients.


3. As an operator, perform the transfer activities in the warehouses by using Movilitas Mobile.


In this use case, they will perform the following actions:

  • Ship products
  • Receive products


Note: For manufacturer sites, it is also possible to commission the items while shipping to accelerate serialization and logistics activities. The setting can be activated or deactivated on the warehouse level and it requires administrator rights. The setting does not bring extra UI functions for the user in the mobile application who wants to ship. However, the application executes additional tasks and reports in the background.


For more information, see Movilitas Mobile for Serialized Logistics.


4. Monitor the transfers. For more information on the transfers, see Viewing Inbound Transfers and Viewing Outbound Transfers.


5. Check the BPOM logs and make sure that the activities in your warehouse are successful. For more information, see Configuring BPOM Channel, Viewing BPOM Logs, and Importing Shipping Locations.


6. (Optional) Open the Serialized Manufacturing application and go to the SN/SSCC pool tab. Track the SSCC or pack history. For more information, see Viewing the SSCC History (Serialized Manufacturing application) and Viewing the Pack History (Serialized Manufacturing application).


Note: Only applicable to products that were produced by this tenant.


7. (Optional) View the batch data and the pack status summary for the batch. For more information, see Managing Batches.


Back to the list of use cases



Verifying Items against SAP ATTP and Requesting Product Information


In this use case, you want to verify items against SAP ATTP in your distributor warehouse to make sure the items are valid. Also, you want to provide electronic content for the operators in the warehouse to know more about the product (for example, storage details).



Before You Begin


Make sure that:

  • You have added mobile users to your tenant. For more information, see Managing Users of a Tenant.
  • You or your company has prepared a GS1 Digital Link Resolver Server to serve electronic content requests from Movilitas.Cloud. The server is an external component that you cannot control in Movilitas.Cloud. You can only set the server URL in Movilitas.Cloud and the Serialized Logistics application connects to this server when an operator will request electronic content in the warehouse.
  • You have configured the SAP ATTP channel. For more information on the channel, see SAP ATTP.


Procedure


1. (Optional) Set the default channel and provide the GS1 Digital Link Resolver Server URL under the Serialized Logistics application --> Settings tab. For more information, see Settings.


2. Configure the site-related aspects.


OptionAction
WarehousesConfigure the warehouses where the scanning activities will be performed:
  1. Specify the name, address, country, SGLN, and assign the SAP ATTP channel as the business channel.
  2. Select Distributor for the role.
  3. Optionally, assign devices to the warehouses by giving their Universally Unique Identifier (UUID). Only the given device can be used in the warehouse.
Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the Verifying and Electronic content privileges.
  3. Optionally, ignore location warning per operator for the verification action.
  4. Optionally, activate ignoring double scans per operator to make scanning faster.
  5. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.


For more information, see Managing Warehouses and Managing Operators.


3. As an operator, perform the scanning activities in the warehouses by using Movilitas Mobile. 


In this use case, you can perform the following actions:

  • Verify items
  • Scan items offline for verification
  • Submit the items scanned offline to the external system
  • Request electronic content


For more information, see Movilitas Mobile for Serialized Logistics.


Back to the list of use cases



Commissioning while Shipping to a Client and Reporting to SAP ICH (China)


In this use case, you are at a manufacturing site, and you want to commission and ship to a client at the same time. You want to report the activity to SAP ICH.



Before You Begin


Make sure that:

  • You have added mobile users to your tenant. For more information, see Managing Users of a Tenant.
  • You have configured the SAP ICH channel. For more information on the channel, see SAP ICH.

 

Procedure


1. (Optional) Set the default channel under the Serialized Logistics application --> Settings tab. For more information, see Settings.


2. Configure the site-related aspects.


OptionAction
Warehouses

Configure the warehouses where the scanning activities will be performed:

  1. Specify the name, address, country, SGLN, and assign the SAP ICH channel as the business channel.
  2. Select Manufacturer for the role, and activate commissioning while shipping.
  3. Optionally, assign devices to the warehouses by giving their Universally Unique Identifier (UUID). Only the given device can be used in the warehouse.
Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the Shipping privilege.
  3. Optionally, activate ignoring double scans per operator to make scanning faster.
  4. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.
Clients

Specify the clients that are the destinations of the commissioning and shipping activities (outbound external only).


For more information, see Managing Warehouses, Managing Operators, and Managing Clients.


3. As an operator, perform the shipping activity in the warehouse. Create outbound external transfers in Movilitas Mobile.


Note: The operators commission the items while shipping to accelerate serialization and logistics activities. The setting can be activated or deactivated on the warehouse level and it requires administrator rights. The setting does not bring extra UI functions for the user in the mobile application who wants to ship. However, the application executes additional tasks and reports in the background.


For more information, see Ship or Return Products in Serialized Logistics (Mobile)


4. Monitor the outbound external transfers. For more information, see Viewing Outbound Transfers.


5. Check the messages on the SAP ICH channel and make sure that the activities in your warehouse are successful. For more information, see Configuring and Monitoring an SAP ICH Channel.


6. (Optional) Open the Serialized Manufacturing application and go to the SN/SSCC pool tab. Track the pack history. For more information, see Viewing the Pack History (Serialized Manufacturing application).


7. (Optional) View the batch data and the pack status summary for the batch. For more information, see Managing Batches (Serialized Manufacturing application).


Back to the list of use cases



Receiving Inbound External Orders and Verifying Items Against the NMVS (FMD Europe)


In this use case, you are a wholesaler (distributor) in the European pharma market and you want to receive products from your suppliers. You create orders to organize the activities in the warehouse and you verify the items against the National system of your country to make sure that the item from the supplier is valid.


The scans are stored in the database and you can also view the details of the scans, including alerts (if any).



Before You Begin


Make sure about the following:

  • If you want to use matrix scanning, you have a Scandit license. Matrix scanning is an ultrafast reading alternative to item-by-item scanning. You can scan a set of barcodes at once by using the camera of the mobile device.
  • You have added mobile users to your tenant. For more information, see Managing Users of a Tenant.
  • You have configured an Arvato regulatory channel to access the NMVS of your country. For more information on the channel, see Arvato Channel. Make sure you select the regulatory channel type.
  • You have configured a Serialized Logistics V2 API channel and Webhook. For more information, see Serialized Logistics V2 API Channel and Webhook.

 

Procedure


1. (Optional) If you want to use matrix scanning, provide the license key obtained from Scandit in the application settings. Matrix scanning is only available in the installed version of the mobile application. For more information, see Managing Settings.


Note: The standard way of scanning is available in all cases without any license (no change).


2. Configure the site-related aspects.


OptionAction
WarehousesConfigure the warehouses where the scanning activities will be performed:
  1. Specify the name, the warehouse tag, and the country. Make sure that you provide the warehouse tag during the warehouse creation in the Admin UI. This tag identifies the warehouse and links the warehouse to the order while creating the order over API.
  2. Assign the Arvato Regulatory channel as the regulatory channel.
  3. Select Distributor for the role.
  4. Optionally, assign devices to the warehouses by giving their Universally Unique Identifier (UUID). Only the given device can be used in the warehouse.
Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the Receiving privilege and optionally the Verifying privilege. While receiving, there is an automatic verification against the NMVS in the background.
  3. Optionally, ignore location warning per operator for the verification action.
  4. Optionally, activate ignoring double scans per operator to make scanning faster.
  5. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.
Suppliers

Configure the suppliers that are the sources of the receiving activities (inbound external only).


You can create the products of the suppliers in the UI or also through API while creating the orders. Make sure that you also provide a supplier tag during the supplier creation in the Admin UI. This tag identifies the supplier and links the supplier to the product while creating the order over API.


For more information, see Managing Warehouses, Managing Operators, and Managing Suppliers.


3. Create the inbound external orders over API from the external system. For more information, see Creating an Inbound Order.


The order is created and is listed under the Serialized Logistics application --> Orders --> Inbound orders tab.


4. As an operator, perform the receiving activity for an inbound external order in the warehouse by using Movilitas Mobile.


For more information, see Receive Products in Serialized Logistics (Mobile).


While scanning the items for receiving, each item is verified against the NMVS through the configured Arvato regulatory channel. If an item is not in the correct status (inactive in the market or there is an issue with the item), the operator shall put the item aside and that item cannot be received.


5. Monitor the inbound external order. For more information, see Managing Inbound Orders.


6. After the order is received, check the inbound external transfer --> deliveries. For more information, see Viewing Inbound Transfers.


7. If the received quantity is less than the expected quantity in the order, create a new delivery for the order over API in the external system. For more information, see Adding a Delivery to an Inbound Order.


You can add a new delivery to a received inbound external order. By adding the new delivery to the order, the order is reopened and goes to New delivery status. The operators can continue scanning for the order in the warehouse.


An order can have one or more deliveries, but only one delivery is open for the order at one time. If an order is received, it can be reopened by introducing a new delivery.


8. As an operator, receive the new delivery for the order by using Movilitas Mobile.


9. Monitor the inbound external order again.


10. After the order is received again, check the inbound external transfer --> deliveries.


11. (Optional) Open the Reports & Analysis application and check the FMD scans. Investigate the alerts (if any). For more information, see Viewing FMD Scans (Reports & Analysis application).


Back to the list of use cases



Shipping to a Client and Connecting to the NMVS (FMD Europe)


In this use case, you are a wholesaler (distributor) in the European pharma market and you want to ship products to your clients.


Before shipping, you can pick the items and create a pick list that is similar to a shopping cart. Picking is a preparation step before shipping. Picking can be made mandatory or can be optional:

  • When picking precedes shipping, you verify the items against the national system of your country during picking.
  • When shipping to a client that is located in an FMD country (inside EU) and picking is skipped, you verify the items against the national system of your country.
  • When shipping to a client that is located in a non-FMD country (outside EU), you mark the items as Exported and report them in bulk to the National system of your country.


The scans are stored in the database and you can also view the details of the scans, including alerts (if any). For bulk export, you can verify the bulk responses.



Before You Begin


Make sure that:

  • You have added mobile users to your tenant. For more information, see Managing Users of a Tenant.
  • You have configured an Arvato regulatory channel to access the NMVS of your country. For more information on the channel, see Arvato Channel. Make sure you select the regulatory channel type.

 

Procedure


1. Configure the site-related aspects.


OptionAction
WarehousesConfigure the warehouses where the scanning activities will be performed:
  1. Specify the name and the country.
  2. Assign the Arvato Regulatory channel as the regulatory channel.
  3. Select Distributor for the role.
  4. Select the FMD verification on outbound checkbox.
  5. Optionally, enforce picking before shipping, by selecting the Enforce picking checkbox.
  6. Optionally, assign devices to the warehouses by giving their Universally Unique Identifier (UUID). Only the given device can be used in the warehouse.
Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the Picking, the Shipping, and optionally the Verifying privileges.
  3. Optionally, ignore location warning per operator for the verification action.
  4. Optionally, activate ignoring double scans per operator to make scanning faster.
  5. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.
Clients

Specify the clients that are the destinations of the shipping activities (outbound external only).


For more information, see Managing Warehouses, Managing Operators, and Managing Clients.


2. As an operator, pick the items for your client.

  • You can create a pick list by giving the purchase order ID.
  • You can keep the pick list open and resume until it is shipped.
  • Each item is verified against the NMVS through the configured Arvato regulatory channel. If an item is not in the correct status (inactive in the market or there is an issue with the item), the operator shall put the item aside and that item cannot be picked.


For more information, see Pick Products in Serialized Logistics (Mobile).


Note: If picking is not part of the business processes at your company or picking is optional, then you can also skip it and start with shipping. However, you cannot resume a shipping activity but you need to complete it once you started.


3. Check the pick lists waiting for shipping. For more information, see Viewing Pickings (Pick lists) and Verifying EPCIS File Generation.


4. As an operator, ship the items by purchase order ID to the client in Movilitas Mobile.

  • While scanning the items for shipping (picking is skipped), each item is verified against the NMVS through the configured Arvato regulatory channel. If an item is not in the correct status (inactive in the market or there is an issue with the item), the operator shall put the item aside and that item cannot be shipped.
  • After submitting the shipping action:
    • An outbound external transfer is created.
    • If the client is located in a non-FMD country (outside EU), the items are marked as Exported and are reported to the NMVS.


For more information, see Ship or Return Products in Serialized Logistics (Mobile).


Note: Only applicable when picking is performed before shipping and the pick list is still open (not yet shipped).


5. Check the outbound external transfer. For more information, see Viewing Outbound Transfers.


6. (Optional) Open the Reports & Analysis application and check the following:

  • FMD scans. Investigate the alerts (if any). For more information, see Viewing FMD Scans (Reports & Analysis application).
  • Bulk responses to bulk export. Verify that the bulk export was successful. For more information, see Viewing FMD Bulk Responses (Reports & Analysis application).


Back to the list of use cases



Decommissioning or Reactivating Packs towards the NMVS (FMD Europe)


In this use case, you are a hospital pharmacy or a distributor (wholesaler) in the European pharma market and you want to decommission or reactivate packs towards the National system of your country.


The scans are stored in the database and you can also view the details of the scans, including alerts (if any).



Before You Begin


Make sure that:

  • You have added mobile users to your tenant. For more information, see Managing Users of a Tenant.
  • You have configured an Arvato regulatory channel to access the NMVS of your country. For more information on the channel, see Arvato Channel. Make sure you select the regulatory channel type.


Procedure


1. Configure the site-related aspects.


OptionAction
WarehousesConfigure the warehouses where the scanning activities will be performed:
  1. Specify the name, and the country.
  2. Assign the Arvato Regulatory channel as the regulatory channel.
  3. Select Distributor for the role.
  4. Optionally, assign devices to the warehouses by giving their Universally Unique Identifier (UUID). Only the given device can be used in the warehouse.
Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the privilege:
    • Decommissioning - Destroy
    • Decommissioning - Export
    • Decommissioning - Sample
    • Decommissioning - Supply
    • Decommissioning - Lock
    • Decommissioning - Stolen
    • Decommissioning - Free sample
    • Reactivating
  3. Optionally, activate ignoring double scans per operator to make scanning faster.
  4. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.


For more information, see Managing Warehouses and Managing Operators.


2. As an operator, decommission or reactivate the items in the warehouse by using Movilitas Mobile.


For more information, see Decommission Products in Serialized Logistics (Mobile) and Reactive Products in Serialized Logistics (Mobile).


After the items are submitted, the action is reported to NMVS through the configured Arvato regulatory channel. If an item is not in the correct status, the application informs the operator.


3. (Optional) Open the Reports & Analysis application and check the FMD scans. Investigate the alerts (if any). For more information, see Viewing FMD Scans (Reports & Analysis application).


Back to the list of use cases



Performing Logistics on Behalf of a Marketing Authorization Holder and Sending the Transfer Report as an EPCIS 1.2 File (To Bahrain)


In this use case, you act as a Third-Party Logistics (3PL) company that performs logistics activities on behalf of a Marketing Authorization Holder (MAH).


The MAH provides the input as an EPCIS 1.1 file to you containing the trade items and containers that are ready for further aggregation and shipping to the client in Bahrain. For the additional aggregations, you print SSCC labels in Movilitas.Cloud or you can use external SSCCs given by the MAH. You also receive returns from the client.


The outbound external transfers (shipping) are reported in EPCIS 1.2 files that you can download and/or send to the MAH that will perform the administration.


Finally, you can generate 3PL reports about the total number of scans in the Reports & Analysis application.



Before You Begin


Make sure that:

 

Procedure


1. Register the MAH as a supplier.

  • Give the name and address.
  • Provide a supplier email address.
  • Specify that you act as a 3PL for this supplier and provide the supplier SGLN.


For more information, see Managing Suppliers.


2. Create one or more ZPL label templates for the SSCCs. For more information, see Managing ZPL Printing Templates for SSCCs.


Note: This is only required when you want to print SSCC labels by using Movilitas.Cloud. External SSCCs having the company prefix of the supplier (MAH) can also be used.


3. Generate SSCCs in-house. These SSCCs will be used for aggregation. For more information, see Managing the SSCC Pool.


Note: This is only required when you want to use SSCCs generated in Movilitas.Cloud for aggregations. External SSCCs having the company prefix of the supplier (MAH) can also be used.


4. Configure the warehouse. Make sure that you provide the warehouse SGLN and select a previously created preprint SSCC template. For more information, see Managing Warehouses.


5. Configure the operators.

  • Assign (activate) operators.
  • Select the warehouse for the operator.
  • Specify the Zebra printing channel and select a printer for the operator.
  • Assign privileges to the operator: Preprint SSCCs, Packing, Picking,Shipping, and/or Receiving.
  • Optionally, activate ignoring double scans per operator to make scanning faster.
  • Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.


For more information, see Managing Operators.


6. Configure the clients. Make sure that you provide the client SGLN and select Bahrain for the country. For more information, see Managing Clients.


7. Upload the EPCIS 1.1 file received from the supplier (MAH). This file includes the trade items and containers to be shipped and further aggregation may also be required. 


By uploading an EPCIS file, the application automatically creates the products and links them to the supplier. However, if a product belongs to multiple suppliers, you need to manually specify the country where the supplier is the MAH and repeat the action for each supplier.


For more information, see Managing Suppliers.


8. As an operator, perform the activities in the warehouse:

  • Preprinting SSCC labels
  • Packing
  • Picking
  • Shipping to clients
  • Receiving external returns from clients


For more information, see Movilitas Mobile for Serialized Logistics.


9. Monitor the pick lists waiting for shipping to the client. Verify the EPCIS file generation before shipping. For more information, see Viewing Pickings (Pick lists) and Verifying EPCIS File Generation.


10. Monitor the transfers (outbound external and inbound external return). For more information, see Viewing Inbound Transfers and Viewing Outbound Transfers and Getting an EPCIS 1.2 File.


11. For outbound external transfers, download and send the EPCIS 1.2 file to the supplier. For more information, see Viewing Outbound Transfers and Getting an EPCIS 1.2 File.


Note: The application generates the EPCIS 1.2 file before executing the action. Depending on the size of the transfer, the operation might take a few minutes.


12. Monitor the SSCC pool and the SSCC history. For more information, see Managing the SSCC Pool and Viewing the SSCC History.


13. View the batch history and keep the stock data up-to-date. For more information, see Viewing the Batch History and Adjusting the Batch Data.


14. Generate 3PL reports about the total number of scans in the Reports & Analysis application. For more information, see Generating Total Count Reports as a 3PL.


Back to the list of use cases



Sending Manufacturing Reports on Behalf of a Marketing Authorization Holder to Tatmeen (Free Trade Zone --> United Arab Emirates)


In this use case, you act as a Third-Party Logistics (3PL) company that performs logistics activities on behalf of a Marketing Authorization Holder (MAH). You connect to Tatmeen on behalf of the MAH from Movilitas.Cloud.


The MAH provides the input as an EPCIS 1.1 file to you containing the trade items and containers that are ready for further aggregation and shipping to the client in the UAE. For the additional aggregations, you print SSCC labels in Movilitas.Cloud or you can use external SSCCs given by the MAH. You also receive returns from the client.


After shipping, Movilitas.Cloud generates the manufacturing report (EPCIS) and sends it on behalf of the MAH to Tatmeen through the configured Tatmeen regulatory channel.


Finally, you can generate 3PL reports about the total number of scans in the Reports & Analysis application.



Before You Begin


Make sure that:

 

Procedure


1. Register the MAH as a supplier.

  • Give the name and address.
  • Provide the supplier SGLN.
  • Specify that you act as a 3PL for this supplier and assign the Tatmeen channel to the supplier.


For more information, see Managing Suppliers.


2. Create one or more ZPL label templates for the SSCCs. For more information, see Managing ZPL Printing Templates for SSCCs.


Note: This is only required when you want to print SSCC labels by using Movilitas.Cloud. External SSCCs having the company prefix of the supplier (MAH) can also be used.


3. Generate SSCCs in-house. These SSCCs will be used for aggregation. For more information, see Managing the SSCC Pool.


Note: This is only required when you want to use SSCCs generated in Movilitas.Cloud for aggregations. External SSCCs having the company prefix of the supplier (MAH) can also be used.


4. Configure the warehouse. Make sure that you provide the warehouse SGLN and select a previously created preprint SSCC template. For more information, see Managing Warehouses.


5. Configure the operators.

  • Assign (activate) operators.
  • Select the warehouse for the operator.
  • Specify the Zebra printing channel and select a printer for the operator.
  • Assign privileges to the operator: Preprint SSCCs, Packing, Picking, Shipping, and/or Receiving.
  • Optionally, activate ignoring double scans per operator to make scanning faster.
  • Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.


For more information, see Managing Operators.


6. Configure the clients.

  • Make sure that you provide the client SGLN and select the United Arab Emirates for the country.
  • Optionally, you can give an email address or specify an SFTP connection to send the EPCIS Tatmeen files to the client.


For more information, see Managing Clients.


7. Upload the EPCIS 1.1 file received from the supplier (MAH). This file includes the trade items and containers to be shipped and further aggregation may also be required. 


By uploading an EPCIS file, the application automatically creates the products and links them to the supplier. However, if a product belongs to multiple suppliers, you need to manually specify the country where the supplier is the MAH and repeat the action for each supplier.


For more information, see Managing Suppliers.


8. As an operator, perform the activities in the warehouse:

  • Preprinting SSCC labels
  • Packing
  • Picking
  • Shipping to clients
  • Receiving external returns from clients


For more information, see Movilitas Mobile for Serialized Logistics.


9. Monitor the pick lists waiting for shipping to the client. Verify the EPCIS file generation before shipping. For more information, see Viewing Pickings (Pick lists) and Verifying EPCIS File Generation.


10. Monitor the transfers (outbound external and inbound external return). For more information, see Viewing Inbound Transfers and Viewing Outbound Transfers.


11. Monitor the SSCC pool, the SSCC history, and the pack history. For more information, see Managing the SSCC Pool, Viewing the SSCC History, and Viewing the Pack History.


12. View the batch history and keep the stock data up-to-date. For more information, see Viewing the Batch History and Adjusting the Batch Data.


13. View the messages on the Tatmeen channel.

  • Verify that the message is successfully processed.
  • Investigate failed messages.
  • Send a message manually.


For more information, see Configuring a Tatmeen Channel (UAE) and Managing Documents (UAE). 


14. Generate 3PL reports about the total number of scans in the Reports & Analysis application. For more information, see Generating Total Count Reports as a 3PL.


Back to the list of use cases



Shipping and Receiving Items in Saudi Arabia as a Third-Party Logistics Company (Saudi Arabia)


In this use case, you act as a Third-Party Logistics (3PL) company that performs logistics activities on behalf of a Marketing Authorization Holder (MAH) in Saudi Arabia. You connect to SFDA RSD on behalf of the MAH from Movilitas.Cloud.


The MAH provides the input as an EPCIS file to you containing the trade items and containers that are ready for further aggregation and shipping to the client in Saudi Arabia. For the additional aggregations, you print SSCC labels in Movilitas.Cloud or you can use external SSCCs given by the MAH. You also receive returns from the client.


When shipping within Saudi Arabia, Movilitas.Cloud sends the following two messages to SFDA RSD through the configured SFDA regulatory channel:

  • Dispatch
  • Package Upload


When shipping from Saudi Arabia to another country, Movilitas.Cloud sends the following message to SFDA RSD through the configured SFDA regulatory channel:

  • Export


When receiving returns from a client that is in Saudi Arabia, Movilitas.Cloud sends the following message to SFDA RSD through the configured SFDA regulatory channel:

  • Dispatch Cancel


When receiving returns from a client that is in a country other than Saudi Arabia, Movilitas.Cloud sends the following message to SFDA RSD through the configured SFDA regulatory channel:

  • Export Cancel


Finally, you can generate 3PL reports about the total number of scans in the Reports & Analysis application.



Before You Begin


Make sure that:

 

Procedure


1. Register the MAH as a supplier.

  • Give the name and address. Make sure that you select Saudi Arabia for the country.
  • Provide the supplier SGLN.
  • Specify that you act as a 3PL for this supplier.


For more information, see Managing Suppliers.


2. Create one or more ZPL label templates for the SSCCs. For more information, see Managing ZPL Printing Templates for SSCCs.


Note: This is only required when you want to print SSCC labels by using Movilitas.Cloud. External SSCCs having the company prefix of the supplier (MAH) can also be used.


3. Generate SSCCs in-house. These SSCCs will be used for aggregation. For more information, see Managing the SSCC Pool.


Note: This is only required when you want to use SSCCs generated in Movilitas.Cloud for aggregations. External SSCCs having the company prefix of the supplier (MAH) can also be used.


4. Configure a warehouse for each SFDA connection.

  • Give the name and address. Make sure that you select Saudi Arabia for the country. 
  • Provide the SGLN.
  • Select the SFDA regulatory channel.
  • Select a previously created preprint SSCC template.


For more information, see Managing Warehouses.


5. Configure the operators.

  • Assign (activate) operators.
  • Select the warehouse for the operator.
  • Specify the Zebra printing channel and select a printer for the operator.
  • Assign privileges to the operator: Preprint SSCCs, Packing, Picking, Shipping, and/or Receiving.
  • Optionally, activate ignoring double scans per operator to make scanning faster.
  • Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.


For more information, see Managing Operators.


6. Configure the clients. Make sure that you provide the client SGLN and select the country. For more information, see Managing Clients.


7. Upload the EPCIS file received from the supplier (MAH). This file includes the trade items and containers to be shipped and further aggregation may also be required. 


By uploading an EPCIS file, the application automatically creates the products and links them to the supplier. However, if a product belongs to multiple suppliers, you need to manually specify the country where the supplier is the MAH and repeat the action for each supplier.


For more information, see Managing Suppliers.


8. As an operator, perform the activities in the warehouse:

  • Preprinting SSCC labels
  • Packing
  • Picking
  • Shipping to clients
  • Receiving external returns from clients


For more information, see Movilitas Mobile for Serialized Logistics.


9. Monitor the pick lists waiting for shipping to the client. For more information, see Viewing Pickings (Pick lists) and Verifying EPCIS File Generation.


10. Monitor the transfers (outbound external and inbound external return). For more information, see Viewing Inbound Transfers and Viewing Outbound Transfers.


11. Monitor the SSCC pool, the SSCC history, and the pack history. For more information, see Managing the SSCC Pool, Viewing the SSCC History, and Viewing the Pack History.


12. View the batch history and keep the stock data up-to-date. For more information, see Viewing the Batch History and Adjusting the Batch Data.


13. View the messages on the SFDA channel.

  • Verify that the message is successfully processed.
    • For a Dispatch, Export, Dispatch Cancel and an Export Cancel message, find the notification ID in the response from SFDA RSD.
    • For a Package Upload, find the transfer ID in the response from SFDA RSD.
  • Investigate failed messages or messages with warnings.
  • After the issue is resolved in SFDA RSD, resend failed messages or messages with warnings.


For more information, see Configuring an SFDA (Saudi Arabia) Channel and Monitoring Messages.


14. Generate 3PL reports about the total number of scans in the Reports & Analysis application. For more information, see Generating Total Count Reports as a 3PL.


Back to the list of use cases



Processing Shipping Event from SAP ATTP to TraceLink


In this use case, you use the Serialized Logistics application and other Movilitas.Cloud services as a gateway between SAP ATTP and TraceLink systems to perform serialization activities and logistics. Movilitas.Cloud forwards commissioning requests from SAP ATTP to TraceLink. The request also contains the shipping event that is automatically processed just like the produced items and aggregations.


Your company acts as a Contract Manufacturing Organization (CMO) that uses SAP ATTP to send the commissioning request and the shipping event to the Marketing Authorization Holder (MAH) that uses TraceLink.




Before You Begin


Make sure that:


Procedure


1. Configure the site-related aspects.


OptionAction
WarehousesConfigure the warehouse where the shipping is performed.
  1. Specify the name, address, country, and SGLN. Make sure that you specify the SGLN.
  2. Select Manufacturer for the role.
Clients

Specify the client that is the destination of the shipping activities (outbound external only).

  1. Specify the name, business address, country, and SGLN. The SGLN relates to the business location.
  2. Select the TraceLink collaboration channel and the TraceLink company identifier belonging to the client.
  3. Specify the delivery address(es). As a minimum, provide the delivery address ID, country, and delivery address SGLN. The SGLN relates to the facility location.


For more information, see Managing Warehouses and Managing Clients.


2. Configure the SAP ATTP channel to receive requests from SAP ATTP.

  • You will need the Movilitas.Cloud endpoints and the credentials so that you can send requests to Movilitas.Cloud from SAP ATTP.
  • Activate direct release to market from SAP ATTP.
  • Activate processing shipping events.
  • You can activate accepting only assigned items. This setting ensures that only the serials from Movilitas.Cloud can be used during commissioning.


For more information, see Configuring an SAP ATTP Channel and Managing the Requests.


3. As an SAP ATTP user, send the commissioning request to Movilitas.Cloud.


The commissioning request contains:

  • The produced items including aggregations.
  • The shipping event.


You can monitor the incoming requests on the SAP ATTP channel and receive notifications about errors on the channel through email after you give an email address in the channel settings.


Movilitas.Cloud automatically processes the produced items, the aggregations, and the shipping event:

  • A commissioning request is uploaded to TraceLink.
  • A shipping event is uploaded to TraceLink.
  • An outbound external transfer is created in the Serialized Logistics application.


You can monitor the transactions on the TraceLink Partner channel and receive notifications about errors on the channel through email after you give an email address in the channel settings.


4. Check the outbound external transfers. For more information, see Viewing Outbound Transfers.


Back to the list of use cases



Performing 3PL Activities in the USA and Reporting to SAP ICH


In this use case, you use the Serialized Logistics application as a 3PL to perform logistics on behalf of the supplier in the USA.


The supplier provides the input to the 3PL by sending EPCIS and IDOC files from SAP ICH to Movilitas.Cloud. The 3PL reports the activities to SAP ICH.



Before You Begin


Make sure that:

 

Procedure


1. Configure the DSCSA (USA) letter settings.

  • Receiver email address.
  • Name of the sending company.
  • Address of the sending company.
  • Logo of the sending company.


For more information, see Settings.


2. Create one or more ZPL label templates for the SSCCs. For more information, see Managing ZPL Printing Templates for SSCCs.


3. Generate SSCCs in-house. These SSCCs will be used for aggregation. For more information, see Managing the SSCC Pool.


4. Configure the site-related aspects.


OptionAction
Warehouses

Configure the warehouse. Make sure that:

  • You specify the SGLN.
  • You specify the address data. You select the United States as the country.
  • You select the SAP ICH channel as the business channel for the warehouse.
  • You specify previously created preprint SSCC templates.
  • You select Distributor for the role.
  • You configure the unpacking logic and whether the unpacking is reported towards SAP ICH.
  • You activate verification against Movilitas.Cloud only (and not against SAP ICH).
  • You configure the sublocations (sites) of the warehouse. For each sublocation, specify a unique sublocation tag that must match the partner ID of the shipping point (OSP) in the IDOC Delvry file.
Operators

Configure the operators.

  • Assign (activate) operators.
  • Select the warehouse for the operator.
  • Specify the Zebra printing channel and select a printer for the operator.
  • Assign privileges to the operator:
    • Verifying
    • Unpacking
    • Decommissioning - Sample
    • Decommissioning - Inactive
    • Preprint SSCCs
    • Validate picking
    • Check validate picking
    • Packing - Items
    • Packing - Orders (Pack to order)
    • Pack an order
    • View hierarchy
    • Replace
  • Optionally, activate ignoring double scans per operator to make scanning faster.
  • Optionally, activate ignoring non-GS1 barcodes during the Validate picking action. 
  • Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.
SuppliersConfigure a supplier. Make sure that:
  • You act as a 3PL for the supplier.
  • You specify the SGLN.
  • You select the SAP ICH channel as the collaboration channel for inbound EPCIS as well as for outbound EPCIS on behalf of the MAH.
RoutesDefine the routes for your deliveries. A delivery is described in an IDOC Delvry file that is received from SAP ICH and is processed as part of an outbound order. The IDOC Delvry file can refer to a route and you must define all possible routes before receiving the IDOC Delvry files.

If you ship multi-case deliveries without pallets on a specific route, select the Pack an order mode on outbound external orders is multi-case checkbox for the route.


For more information, see Managing Warehouses, Managing Operators, Managing Suppliers, and Managing Routes.


Note: The clients are auto-created while sending an IDOC Delvry in a later step. 


The supplier sends the EPCIS file from SAP ICH to Movilitas.Cloud.

The EPCIS contains the items that the 3PL receives.

Product master data (including NDC) is fetched from openFDA.


5. Verify the items from the supplier.

  • If an issue occurs during EPCIS processing and the transaction is aborted, correct the EPCIS file. The supplier can resend the EPCIS file from SAP ICH or you can manually upload the corrected EPCIS file for the supplier.
  • If it is not possible to send the EPCIS from SAP ICH, you can manually upload the EPCIS file for the supplier. 


For more information, see Managing Suppliers.


6. As an operator, perform actions on the items in stock in the warehouse:

  • Verifying items.
  • Viewing hierarchy.
  • Unpacking.
  • Decommissioning.
  • Preprinting SSCC labels.
  • Replacing the children of a parent trade item. Note: Replacing the children is a quality assurance step to keep the parent saleable item active while replacing certain child trade items due to damage or taking them as a sample.
  • Packing - items. Note: This action enables you to create mixed pallets. The mixed pallets contain cases of multiple products.


The following events are reported to SAP ICH:

  • Verification - Optional, because the preferred verification method is against Movilitas.Cloud database only.
  • Unpacking - Optional, because unpack messages can be deactivated towards SAP ICH at the warehouse level.
  • Decommissioning


For more information, see Movilitas Mobile for Serialized Logistics.


The supplier sends the IDOC DELVRY from SAP ICH to Movilitas.Cloud.

The IDOC DELVRY describes a delivery to a client. The delivery belongs to an outbound external order. The delivery refers to a route that must be registered in the Serialized Logistics application in advance.

Product master data is fetched from openFDA.

Client master data and delivery address are auto-created in the application.

The outbound order and delivery are auto-created in the application.

Each delivery is assigned to a specific warehouse.


7. If the client or the delivery address is new, verify the auto-created client master data and delivery address. Complete the client configuration by performing manual post-actions:

  • (Required) Provide the SGLN (location data).
    • Client master data (always).
    • Client delivery address (only for purchase orders and donations).
  • (Conditional) Set a special flag to fulfill replacement orders for the client in the USA.
  • (Optional) Set a special flag to use the delivery address SGLN as the receiver in the outbound DSCSA EPCIS file for the client in the USA. This situation applies when the delivery address is a 3PL of the client.
    • (Conditional) If multiple delivery addresses belong to the same 3PL, set a special flag and specify the common receiver SGLN to be used as the receiver in the DSCSA EPCIS in each applicable client delivery address setting.
  • (Conditional) Set a special flag if the client is in a country other than the USA and you want to send a regular EPCIS file to SAP ICH without DSCSA-specific data.


For more information, see Managing Clients.


8. Verify the auto-created delivery. If the delivery belongs to a new order, verify also the auto-created outbound order. For more information, see Managing Outbound Orders.


If the outbound order, the delivery, or the client is not auto-created, there is an issue with the IDOC Delvry:

  • Check the logs of the incoming messages on the SAP ICH channel and take action.
  • You can also manually upload an IDOC Delvry on the SAP ICH channel.


For more information, see Configuring and Monitoring an SAP ICH Channel.


9. As an operator, prepare the delivery for shipping. Perform the following actions in the mobile application:


Mobile ActionDescription
Validate pickingThe items are picked in advance but the picking is not executed in Movilitas.Cloud. The picked items are put into a case (SSCC) and all items are validated.
Check validate pickingA quality check on a picked case SSCC from the Validate picking action before the case is sealed.
Pack to order (Packing - orders)Adding homogeneous pallets to the delivery (order).
Pack an orderTwo activities depending on the route:
  • Validating multi-case deliveries without a pallet.
  • Building up pallets for a delivery, adding mixed pallets to the delivery, and validating the delivery.


10. As an authorized user, perform the following actions in the Admin UI:

  • Validate a one-case delivery that is not complete in terms of scanned versus expected quantity.
  • Verify a delivery in Picking validated status before shipping. If there is an issue with the delivery, edit the delivery and inventory:
    • Reverse the validation status of a delivery to enable the operators to work on the delivery in the warehouse. After reversing the validation status of the delivery to In picking validation, you can do the following: 
      • Reverse the validation status of a picked case SSCC unless the case SSCC is put on a pallet.
        • If the case SSCC is put on a pallet, remove the case SSCC from the pallet in the Pack an order mobile action and then reverse its validation status.
      • Remove empty containers from a delivery (if any) unless the container (case SSCC) is put on a pallet.
        • If the container (case SSCC) is put on a pallet, remove the case SSCC from the pallet in the Pack an order mobile action and then remove it from the delivery.
    • Reverse all activities of a delivery. Note: The action also applies to deliveries in In picking validation status.
      • The previously assigned items are detached from the delivery and are in stock again.
      • The delivery can be deleted or the operators can execute the delivery from scratch in the warehouse.


Note: An authorized user can edit the delivery and inventory during the shipping process while preparing the delivery for shipping and does not need to wait for the delivery to be validated.


For more information, see Movilitas Mobile for Serialized Logistics and Managing Outbound Orders.


11. Ship a validated (packed) delivery in one of the following ways:

  • Manual - As an authorized user, ship the delivery in the Admin UI. For more information, see Managing Outbound Orders.
  • Automatic - As the supplier, send an ASN IDOC from SAP ICH to Movilitas.Cloud. The action triggers automated shipping. The action is equivalent to manually shipping the delivery in the Admin UI.


Result: 

  • For purchase orders and donations, an EPCIS file is sent to SAP ICH.
  • For replacement orders, a DSCSA letter is sent to the email address configured in the Serialized Logistics application settings.


12. Monitor the transfers (outbound external orders - deliveries).


13. Monitor the SSCC pool, the SSCC history, and the pack history. For more information, see Managing the SSCC Pool, Viewing the SSCC History, and Viewing the Pack History.


14. Export the deliveries of a selected day. For more information, see Managing Outbound Orders.


15. Monitor the inventory of a product. For more information, see Viewing Products.


16. Check the messages (incoming and outgoing) on the SAP ICH channel and make sure that the activities in your warehouse are successful. For more information, see Configuring and Monitoring an SAP ICH Channel.


17. View the activity count on 3PL scans for a given timeframe per warehouse in the Reports & Analysis application. For more information, see Viewing Activity Count on 3PL Scans.


18. Generate inventory reports in the Reports & Analysis application based on GTIN, batch, and inventory status. For more information, see Generating Inventory Reports.


19. Monitor the workload in the Reports & Analysis application. For more information, see Downloading a Workload Report.


Back to the list of use cases



Receiving the Produced Items from the CMO through a 3PL


In this use case, you are the Marketing Authorization Holder (MAH) and you want to receive the produced items from your Contract Manufacturing Organizations (CMOs). The receiving activity enables you to verify that the items that you commissioned match the physical items shipped by the CMO.


You involve a Third-Party Logistics (3PL) company that uses your tenant in Movilitas.Cloud to receive the items. You create inbound external orders to organize the activities in the warehouse (3PL location).



Before You Begin


Make sure about the following:

 

Procedure


1. Configure the site-related aspects.


OptionAction
WarehousesConfigure the warehouses (3PL locations) where the scanning activities will be performed:
  1. Specify the name, the address, and the country.
  2. Select Distributor for the role.
  3. Optionally, assign devices to the warehouses by giving their Universally Unique Identifier (UUID). Only the given device can be used in the warehouse.
Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the Receiving privilege.
  3. Optionally, activate ignoring double scans per operator to make scanning faster.
  4. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.
Suppliers

Configure the supplier that is the MAH: 

  1. Specify the name, the address, and the country.
  2. Set that you act as 3PL for this supplier.
  3. Create the products of the supplier in the UI (product code and name).


For more information, see Managing Warehouses, Managing Operators, and Managing Suppliers.


2. Create the inbound external orders in the Admin UI. For more information, see Managing Inbound Orders.


3. As an operator, perform the receiving activity for an inbound external order in the warehouse by using Movilitas Mobile.


For more information, see Receive Products in Serialized Logistics (Mobile).


4. Monitor the inbound external order. For more information, see Managing Inbound Orders.


5. After the order is received, check the inbound external transfer --> deliveries. For more information, see Viewing Inbound Transfers.


Back to the list of use cases



Receiving Products from a Designated Wholesaler (FMD Europe)


In this use case, you are a distributor that receives products from a designated wholesaler in the European pharma market. You are connected to a National System (NMVS) through an Arvato regulatory channel. 


As per the FMD regulation, when receiving products from a designated wholesaler, you don't need to verify the items against the National System. You need to record the received amount only.



Before You Begin


Make sure that:

  • You have added mobile users to your tenant. For more information, see Managing Users of a Tenant.
  • You have configured an Arvato regulatory channel to access the NMVS of your country. For more information on the channel, see Arvato Channel. Make sure you select the regulatory channel type.


Procedure


1. Configure the site-related aspects.


OptionAction
WarehousesConfigure the warehouses where the scanning activities will be performed:
  1. Specify the name, the address, and the country.
  2. Select Distributor for the role.
  3. Optionally, assign devices to the warehouses by giving their Universally Unique Identifier (UUID). Only the given device can be used in the warehouse.
Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the Receiving privilege.
  3. Optionally, activate ignoring double scans per operator to make scanning faster.
  4. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.
Suppliers

Configure the supplier. Specify the name, the address, and the country.


For more information, see Managing Warehouses, Managing Operators, and Managing Suppliers.


2. Create or edit the products of the suppliers in the UI. Mark the products where the supplier is a designated wholesaler. 


The application obtains the designated wholesaler data from the National System. The application offers to overwrite the supplier master data with the data from the National System in case of data mismatch.


For more information, see Managing Suppliers.


3. Decide how you want to receive the items in the warehouse:

  • By creating an inbound external transfer in the mobile application.
  • By creating an inbound external order in the Admin UI or over the Serialized Logistics V2 API before the activity in the mobile application. For more information, see Managing Inbound Orders or Create Inbound Order over API.


4. As an operator, perform the receiving activity in the warehouse by using Movilitas Mobile.


When scanning a product in the warehouse, the application detects whether the product is from a designated wholesaler:

  • If yes, you only need to enter the amount to receive. Scanning is not required for that product.
  • If no, you need to scan each pack of that product. The packs are verified against the National System.


5. Check the inbound external transfer --> deliveries. For more information, see Viewing Inbound Transfers.


Back to the list of use cases



Receiving and Shipping Items in the USA as a Distributor


In this use case, you are a distributor of pharmaceutical products in the USA market that receives items from suppliers and ships items to clients.


The TI/TS information (EPCIS) as per DSCSA is exchanged in both directions:

  • Receiving the EPCIS from a supplier.
  • Sending the EPCIS to a client.


By following your business processes, you can customize the configuration of Movilitas.Cloud. The following workflow collects multiple scenarios.


 

Before You Begin


Make sure that:

  • You have added mobile users to your tenant. For more information, see Managing Users of a Tenant.
  • (Optional) You have configured the SAP ICH channel. For more information on the channel, see SAP ICH.
  • (Optional) You have configured the TraceLink Partner channel. For more information on the channel, see TraceLink Partner Channel.
  • (Optional) You have configured the AS2 channel. For more information on the channel, see AS2 Channel.
  • (Optional) You have configured the LSPediA channel. For more information on the channel, see LSPediA Channel.
  • (Optional) You have configured the SFTP channel. For more information on the channel, see SFTP Channel.
  • (Optional) You have configured a Serialized Logistics V2 API channel and the Webhook to integrate your system with Movilitas.Cloud. For more information, see Serialized Logistics V2 API Channel and Webhook.


Procedure


1. Configure the DSCSA (USA) settings.

  • Contact addresses (email and phone number) for the processes in the DSCSA scope.
  • Activation of ATP credentialing.


For more information, see Managing Settings.


2. Configure the site-related aspects.


OptionAction
Warehouses

Configure the warehouse:

  1. Specify the address data. Select the United States as the country.
  2. Specify the SGLN.
  3. Select Distributor for the role.
  4. When communicating over API, specify the warehouse tag to identify the warehouse for your requests.
Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the relevant privileges:
    • Receiving
    • View hierarchy
    • Unpacking
    • Decommissioning - Inactive
    • Decommissioning - Sample
    • Shipping
  3. Optionally, activate ignoring double scans per operator to make scanning faster.
  4. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.
SuppliersConfigure a supplier, including the master data and the shipping address(es):
  1. Specify the address data, including the country (both master data and shipping address).
  2. Specify the SGLN (both master data and shipping address).
  3. When communicating over API, specify the supplier tag to identify the supplier for your requests.
  4. Enter the DSCSA contact emails (exception handling, verifications, and trace request).
  5. To receive inbound EPCIS from the supplier through a collaboration channel, select an SAP ICH, TraceLink Partner, AS2, or LSPediA channel for the supplier.
  6. To receive an EPCIS in partnership, establish a partnership with the supplier in Movilitas.Cloud.
ClientsConfigure a client, including the master data and the delivery address(es):
  1. Specify the address data, including the country that is the United States (both master data and delivery address).
  2. Specify the SGLN (both master data and delivery address).
  3. When communicating over API, specify the client ID and client delivery address ID to identify the client for your requests.
  4. Enter the DSCSA contact emails (sending DSCSA EPCIS, exception handling, verifications, and trace request).
  5. To send an EPCIS to AS2, associate an AS2 channel with the client and specify the AS2 ID.
  6. To send an EPCIS to LSPediA, associate an LSPediA channel with the client.
  7. To send an EPCIS to SFTP, associate an SFTP channel with the client.
  8. To send an EPCIS in partnership, establish a partnership with the client in Movilitas.Cloud.


For more information, see Managing Warehouses, Managing Operators, Managing Suppliers, and Managing Clients.


3. Receive the EPCIS from the supplier:

  • In partnership with the supplier in Movilitas.Cloud.
  • From a collaboration system through a collaboration channel (SAP ICH, TraceLink, AS2, or LSPediA).
  • Over the Serialized Logistics V2 API.
  • By uploading the EPCIS on the supplier manually. For more information, see Uploading an EPCIS File section in Managing Suppliers.


Automated actions are triggered in Movilitas.Cloud:

  •  The Advanced Shipping Notification (ASN) is stored.
    • The received items and the hierarchy are registered in Movilitas.Cloud.
    • The shipping event is registered in Movilitas.Cloud.
  • Product master data is fetched from openFDA.
  • GTIN is converted to NDC.


4. Verify the items received in partnership, through a collaboration channel, over API, or after the manual EPCIS upload. For more information, see Managing Suppliers.


5. If you want to execute your inbound external orders in Movilitas.Cloud, create the inbound external orders from your warehouse management system over API. For more information, see Create Inbound Order over API.


If webhook is configured on the Serialized Logistics V2 API channel, each time there is a change in the status of the inbound order, a message is sent through webhook to the subscribed external system.


6. Perform actions on the items of the inbound EPCIS in the warehouse. Finally, ship the items to the client.


You have two alternatives here:


#AlternativeActionReference
ASerialized Logistics V2 API to integrate your warehouse management system with Movilitas.Cloud.
  1. Get the Advanced Shipping Notification from Movilitas.Cloud to obtain the received items (API)
  2. Perform inbound and outbound scanning on the items in the external system (outside Movilitas.Cloud).
  3. Create the outbound external transfer in Movilitas.Cloud to generate the TI/TS information (EPCIS) for the client (API).
For more information, see the relevant articles of Serialized Logistics V2 API.
BMovilitas Mobile
  • Receive
    • Check whether the received items are in line with the ASN from the TI/TS information (EPCIS).
    • If webhook is configured on the Serialized Logistics V2 API channel, each time there is a change in the status of the inbound external order, a message is sent through webhook to the subscribed external system.
  • View hierarchy
  • Unpack
  • Decommission
  • Ship to the client by creating an outbound external transfer in the mobile application.
For more information, see the relevant articles of Movilitas Mobile (Serialized Logistics).


7. Elaborate on the exceptions during receipt (if any) and send the incident report to the supplier. 


The supplier can respond by email and the incident is automatically updated with the response. 


For more information, see Managing DSCSA Exceptions in the Reports & Analysis application.


8. Monitor the inbound external deliveries and/or the outbound external transfers. For more information, see Viewing Inbound Transfers and Viewing Outbound Transfers and Getting an EPCIS 1.2 File.


9. Send the TI/TS information (DSCSA EPCIS) to the client.

  • If the client is a partner in Movilitas.Cloud, the EPCIS is sent automatically. The client can confirm the processed EPCIS on the supplier's page in the client view.
  • If there is a collaboration channel associated with the client (AS2, LSPediA, or SFTP), the EPCIS is sent to the collaboration system through the associated channel automatically. The outbound message (EPCIS) is logged on the applicable channel.
  • Otherwise, download the EPCIS file of the outbound external transfer. Send the file to the client outside Movilitas.Cloud.


The outbound DSCSA EPCIS file can be downloaded for all outbound external transfers, even if there is a partnership in Movilitas.Cloud or a collaboration channel is associated with the client. Moreover, the file can be manually resent over the collaboration channel or by email. For more information, see Viewing Outbound Transfers and Getting an EPCIS 1.2 File.


Back to the list of use cases



Sending a Shipping Event from SAP ATTP to a Partner Client in Movilitas.Cloud (UAE)


In this use case, the manufacturer (supplier) invites the wholesaler (client) to establish a partnership with each other in Movilitas.Cloud. The wholesaler (client) is in the UAE.


If the wholesaler does not have a tenant in Movilitas.Cloud, the wholesaler registers one and then accepts the partner request.


Regarding the payment model, the wholesaler can become a full-paying customer in Movilitas.Cloud or can be in "Partner" mode meaning that the tenant that sent the invitation pays the invoices (the manufacturer).


The manufacturer ships items to the wholesaler. The manufacturer sends a commissioning request from SAP ATTP to Movilitas.Cloud. The commissioning request is an EPCIS file that meets the requirements from Tatmeen. Tatmeen is the regulatory system in the UAE. Movilitas.Cloud processes the shipping event and creates the items in the database.


The manufacturer and the wholesaler are integrated within Movilitas.Cloud with their customized views and functions. The partnership enables the manufacturer and the wholesaler to exchange data in an efficient, controlled, and secure manner:

  • In the manufacturer (supplier) view, Movilitas.Cloud creates an outbound external transfer in the Serialized Logistics application.
  • In the wholesaler (client) view, Movilitas.Cloud logs the receipt in the Serialized Logistics application on the supplier's Uploads tab.  


 


Procedure


#Manufacturer (Supplier)Wholesaler (Client)
1.Configure the site-related aspects.
  • Warehouse (Sender) - Make sure that you provide the SGLN.
  • Client (Receiver) - Make sure that the country is set to the United Arab Emirates and provide the SGLN.


For more information, see Managing Warehouses and Managing Clients.

N/A
2.Invite the client to be a partner in Movilitas.Cloud. For more information, see Managing Clients.N/A
3.N/AIf the tenant does not exist in Movilitas.Cloud, register in Movilitas.Cloud. For more information, see Registering to Movilitas.Cloud through a Partner Invitation from Another Company.
4.

N/A

Review and accept the partner request. For more information, see Managing Partners.
5.

Create an SAP ATTP channel and configure it to receive requests from SAP ATTP.

  • You will need the Movilitas.Cloud endpoints and the credentials so that you can send requests to Movilitas.Cloud from SAP ATTP.
  • Select the Bypass Commissioning in Serialized Manufacturing checkbox. The setting automatically selects the Process shipping events checkbox.
  • Make sure that the Only accept assigned items checkbox is cleared.


For more information, see Configuring an SAP ATTP Channel and Managing the Requests.

Complete the supplier master data in the Serialized Logistics application:
  • Supplier SGLN
  • Supplier address


For more information, see Managing Suppliers.

6.

As an SAP ATTP user, send the commissioning request to Movilitas.Cloud.


The commissioning request (EPCIS) contains:

  • The produced items including aggregations.
  • The shipping event.


You can monitor the incoming requests on the SAP ATTP channel and receive notifications about errors on the channel through email after you give an email address in the channel settings.


Movilitas.Cloud automatically creates items and the shipping event.

  • An outbound external transfer is created in the Serialized Logistics application.
  • The destination is the client in the UAE. The client is in partnership with the sending tenant (supplier) in Movilitas.Cloud.
N/A
7.Verify the outbound external transfer in the Serialized Logistics application.

For more information, see Viewing Outbound Transfers.		Verify the received EPCIS file and its content in the Serialized Logistics application, on the supplier's Uploads tab.

For more information, see Managing Suppliers.


Back to the list of use cases



Shipping to the USA as a Manufacturer and Sending the DSCSA EPCIS to SFTP


In this use case, the Contract Manufacturing Organization (CMO) ships the produced items physically to the client of the Marketing Authorization Holder (MAH) while the product ownership remains at the MAH. The DSCSA EPCIS file about the shipment is sent to SFTP.



Before You Begin


Make sure that:

  • You have provided the tenant SGLN in the tenant settings. This SGLN is used in the outbound DSCSA EPCIS file as the sender (source owning party or sold-from). For more information, see the Tenant Settings.
  • You have added mobile users to your tenant. For more information, see Managing Users of a Tenant.
  • You have configured the SFTP channel. For more information on the channel, see SFTP Channel.

 

Procedure


1. Configure the site-related aspects.


OptionAction
Warehouses

Configure the warehouses where the scanning activities will be performed:

  1. Specify the name, address, country, and SGLN.
  2. Select Manufacturer for the role.
  3. Optionally, assign devices to the warehouses by giving their Universally Unique Identifier (UUID). Only the given device can be used in the warehouse.
Operators

Configure the operators:

  1. Assign (activate) operators.
  2. For each operator, select the warehouse and assign the Shipping privilege.
  3. Optionally, activate ignoring double scans per operator to make scanning faster.
  4. Optionally, assign devices to the operator by giving the Universally Unique Identifier (UUID) of the device. The operator can use only the given device for scanning. This setting is overwritten by the UUID setting at the warehouse level.
Clients

Specify the client that is the destination of the shipments and DSCSA EPCIS files.

  1. Specify the client master data. The client master data represents the MAH.
    1. Give the name, address, country, and SGLN.
    2. Associate the SFTP channel with the client as the collaboration channel for outbound DSCSA EPCIS.
    3. Optionally, specify the file path on the SFTP server. If not specified, the file is uploaded to the root folder.
  2. Specify the client delivery address. The client delivery address represents the client of the MAH.
    1. Give the name, address, country, and SGLN.


For more information, see Managing Warehouses, Managing Operators, and Managing Clients.


2. Create the outbound external orders that control the activities in the warehouse. For more information, see Managing Outbound Orders.


3. As an operator, execute the outbound external orders in the warehouse by using Movilitas Mobile.


For more information, see Ship or Return Products in Serialized Logistics (Mobile).


4. Monitor the outbound external orders (deliveries). For more information, see Viewing Outbound Transfers.


5. Track the pack history and container history. For more information, see Viewing the Pack History and Viewing the SSCC History.


6. Check the messages on the SFTP channel and make sure that the uploads are successful. For more information, see the SFTP Channel.


Back to the list of use cases