Movilitas

Movilitas.
Cloud Overview
Movilitas.Cloud is a cloud-based platform hosting a group of tailor-made applications to
enable companies to meet manufacturing, serialization, and reporting requirements.
Parties of the pharmaceutical industry can perform serialization and reporting activities:
 Manufacturers, wholesalers, pre-wholesalers, parallel importers, repackers, and

hospital pharmacies use applications that are tailored to individual requirements.
 The applications enable the participants to comply with the regulations introduced by
the government.
Parties of the agricultural industry can perform manufacturing activities and serialized
logistics:
 Manufacturers can record the quantities and batches during production and update
their external systems integrated with Movilitas.Cloud.
 Participants of the serialized logistics can perform inbound and outbound activities in
the supply chain and update external systems integrated with Movilitas.Cloud.
Movilitas.Cloud Admin
Use Movilitas.Cloud Admin to customize the solution to your needs. Movilitas.Cloud Admin
helps in:
 Configuring and managing the Movilitas.Cloud applications.

 Extending the applications with Movilitas Mobile and Movilitas Desktop.
The configuration enables the businesses to carry out the scanning activities for operations
like commissioning, decommissioning, packing, repacking, serializing, shipping, or
scheduling reports.
In Movilitas.Cloud, you can establish connections to the following external systems:
 EU Hub
 National Medicines Verification Systems in Europe
 BPOM (Indonesia)
 Russian Drug Circulation Monitoring System (MDLP) and Advanced Technology
Development Center in Russia (CRPT)
 SAP Advanced Track and Trace for Pharmaceuticals (SAP ATTP)
 SAP Information Collaboration Hub for Life Sciences (SAP ICH)
 Tatmeen (UAE)
 TraceLink
 TRVST (Africa)
 VRS Providers (DSCSA USA)
Movilitas Mobile
The applications that support scanning are extended with the Movilitas Mobile application.
Movilitas Mobile is available in different languages.
You have two choices:
 For handheld (mobile) scanners or mobile devices, install Movilitas Mobile on the
devices. You also need to configure the scanner.
 For table scanners connected to the USB of your device, open Movilitas Mobile in a
web browser on https://mobile.movilitas.cloud/login (production environment). You
also need to configure the scanner.
Movilitas Desktop (Repacker FMD Only)
When using the Repacker FMD application, use Movilitas Desktop in a web browser with
table scanners connected to the USB of your device. This is a legacy solution, limited to the
Repacker FMD application to perform certain operations. You also need to configure the
scanner.
About Serialized Manufacturing Application

Modified on: Sun, 2 Jul, 2023 at 7:03 PM
The Serialized Manufacturing application helps manufacturers to perform serialization of

the manufactured products.
With this application, the manufacturers can use the following capabilities:
Connections to External Systems, Shopfloor, and Printing Destinations
The connections to external systems, shopfloor, and printing destinations are established
through respective channels.
In the pharmaceutical industry, you can connect to the following:
 BPOM (Indonesia market)

 Code OMS (Uzbekistan)
 EU Hub (EMVO)
 OMS Cloud (Kazakhstan)
 SAP ICH
 Shopfloor (Packaging lines)
 Printing Destinations (Zebra Cloud Connect, FTP servers, and NiceLabel Label
Cloud)
 TraceLink
 TRVST (Africa)
 VRS (USA market)
Administrator UI
Enables the users to configure and manage the application.
Movilitas Mobile
Enables the operators to scan items for commissioning. The scanned items are commissioned to Movilitas.Cloud
and then they are ready for commissioning to the market.
Manufacturer V2 API
The Serialized Manufacturing application can be extended through the Manufacturer V2

API in the following ways:
 To request serials
 To request SSCCs
 To release serials
 To release SSCCs
 To commission serials
 To decommission serials
 To aggregate trade items on a container or a trade item
 To aggregate containers on a container
 To disaggregate trade items from a container or a trade item
 To disaggregate containers from a container
 To create a packaging order
 To get open packaging orders
 To get order details
 To assign serials to one or more packaging orders
 To release a packaging order to a packaging line
 To start a packaging order without serial number assignment (bypassing serials)
 To cancel a packaging order
 To finish a packaging order
About Serialized Logistics Application

The Serialized Logistics application enables users to handle serialized logistics in the
warehouse.
With this application, you can use the following capabilities:
Connecting to External Systems
The connections to external systems are established through respective channels.
In the pharmaceutical industry, you can connect to the following systems to report activities:
 SAP ATTP
 SAP ICH
 BPOM (Indonesian market)
 NMVS (Arvato)
 Tatmeen (UAE)
 TraceLink
Connecting to a GS1 Digital Link Resolver Server
The Serialized Logistics application can communicate with an external GS1 Digital Link Resolver server. The
Serialized Logistics application forwards the electronic content request from the users to the
server that redirects them to an external website presenting the digital information. For more
information about the GS1 Digital Link standard, visit the GS1 website.
Administrator UI
Enables the users to configure and manage the application:
 Managing inbound and outbound orders.

o (Outbound) Shipping a delivery to a client in the USA. A DSCSA shipping
event is reported to SAP ICH.
 Viewing pick lists (outbound) and verifying EPCIS file generation for a pick list when
shipping to Bahrain on behalf of the supplier. In the latter case, the supplier is the
Marketing Authorization Holder (MAH) of the product.
 Tracking the transfer activities performed in the warehouse or initiated from SAP
ATTP.
 Sending an EPCIS 1.2 file to the supplier. The file contains the items that are shipped
on behalf of the supplier to Bahrain. The supplier is the Marketing Authorization
Holder (MAH) of the product.
 Downloading the EPCIS 1.2 file of a shipment as a distributor in the USA. The
EPCIS 1.2 file is constructed as per the DSCSA requirements.
 Managing sites, including warehouses, operators, suppliers, and clients.
 Establishing a partnership with a supplier and/or a client.
 Uploading an EPCIS 1.1 or 1.2 input file received from a supplier. The file contains
the items to be shipped.
 Verifying the EPCIS file received from a supplier in partnership or through a
collaboration channel (SAP ICH or TraceLink).
 Viewing the products that are managed in the warehouses.
 Viewing the history of a batch that is managed in a warehouse.
 Generating SSCCs and viewing the historical activities of a container.
 Defining ZPL label templates for SSCCs.
 Controlling application-level settings.
o GS1 Digital Link Resolver URL.
o Scandit license to utilize matrix scanning in the mobile application.
o Access control for users with the "User" role.
Movilitas Mobile
Operators in the warehouse can complete the following activities on the products in the
mobile application:
 Verify
 Request electronic content by scanning a GS1 2D barcode
 Pack
o Items - Aggregating items.
o Orders - Adding homogeneous pallets to a delivery of an outbound external
order. Visible in the "Pack an order" screen.
 Unpack
 Decommission
 Receive – The operators can see the stock transfer IDs and batches that have been
shipped to the operator’s warehouse but have not been received yet.
 Pick
 Ship
o By batch - Shipping by batch is only possible at manufacturer sites (set for the
warehouse).
o By stock transfer ID
o By purchase order ID
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.
 Preprint SSCC labels on Zebra Cloud Connect printers

 Validate picking (not related to the "Pick" action)
 View hierarchy
 Pack an order (a post-action after Validate picking)
 Replace the children of a parent trade item
Depending on the business use case, the actions are reported through the channel configured
for the warehouse or the supplier.
Offline Scanning (Only for Verification)
The mobile application also offers offline scanning for verification purposes for the users
working on a site with a limited connection to the Internet. The user can submit the items for
verification after logging into the application once the device has a connection to the Internet
again.
Serialized Logistics V2 API and Webhook
The Serialized Logistics application can be extended through the Serialized Logistics V2 API.
 Create inbound order

 Add a delivery to an inbound order
 Create outbound order
 Get Advanced Shipping Notification
 Create outbound external transfer
When there is a change in the status of an inbound external order, Movilitas.Cloud can send the order details to
an external system through a webhook. The user can provide the endpoint URL of the subscribing system,
activate sending webhooks, and test the webhook settings by manually executing a webhook for an inbound
external order.
Movilitas.Cloud Tenant Dashboard Overview

Modified on: Wed, 21 Sep, 2022 at 6:55 PM
You can manage the tenant-level settings in the Movilitas.Cloud Tenant Dashboard.
# GUI Section Description

1 Navigation pane After selecting a tenant, the application extends the navigation
pane with further functions compared to the status after login.
The navigation pane contains:
 Movilitas.Cloud logo directing you to the Console

 Tenant dashboard option directing you to the
Dashboard of the currently selected tenant
 Applications drop-down with the list of applications
activated for the selected tenant
 Movilitas.Cloud console directing you to the Console
 Movilitas.Cloud tools offering an Arvato book
generator and a data matrix generator
 Application store to activate or deactivate applications
 Notifications
 Logout
 User Settings
For the login view, see Movilitas.Cloud Console Overview.

You can do the following activities by clicking on a tab from
left to right:
 Go back to the Tenant Dashboard opening page

 View, assign, and unassign users
 View, create, edit, and delete channels used across
2 Tenant Dashboard tabs multiple applications
 View, create, edit, and delete repositories
 View, create, edit, and delete API keys that are needed
to get the authentication token for API communication
 Manage partners (Limited functionality)
 View Logs
Tenant name and

Displays the tenant name and the unique tenant identifier in
3 [unique tenant
square brackets. You can't change the unique tenant identifier.
identifier]
You can manage the company (tenant) information, global
settings, company logo, and provide the billing information
here.
4 Tenant Settings
You can also delete the tenant (company) from Movilitas.Cloud
here.
5 Notifications Displays notifications about the activities in the system.
You can find a live summary of the current configuration for
the tenant:
 A donut chart about the current channels

 The number of applications that have been enabled
 Number of users who were active in the last 72 hours
 Number of API keys
 Number of repositories
6 Configuration summary  Pending invitations. After clicking on the button, the
application lists the invited users who have not created
an account yet. You can resend the invitation or remove
the invitation.
 Mobile requests from users who requested to join the
tenant from Movilitas Mobile. After clicking on the
button, the application lists the users and you can accept
or deny the request.
Displays buttons to access a file or another page:
 Download Movilitas Mobile - You can download the

APK file to an Android device and install the
application.
 Movilitas Mobile Web - You can open Movilitas
7 Buttons (Links) Mobile application in the browser to use it with table
scanners.
 Movilitas.Cloud Acceptance - You can access the
Movilitas.Cloud acceptance environment.
 Application store - You can activate or deactivate
applications.
Displays the list of activated applications.
8 Activated applications To access an application click on the applicable tile or go to

Navigation pane --> Applications and select the application
from the list.
Tenant Settings
Modified on: Fri, 28 Jul, 2023 at 2:28 PM
You can change the details you provided about your company and yourself when you
registered.
You can modify the following settings of the tenant:
 Change the details of the tenant, like the name or address. You can’t change the unique
tenant identifier.
 Registration over mobile application
 Availability of contact list on mobile application
 Billing information
 Company logo
Managing the Company Information, Global Settings, and Company

Logo
Procedure
1. Go to Movilitas.Cloud Console --> My tenants.
2. Select the tenant or click Open tenant next to it.
3. On the tenant dashboard, click Settings. The application displays the Tenant Settings
page.
4. On the Settings tab, configure the general settings.
GUI section Action
Company information Fill in the form with the company information and click Save Settings.
Global configuration 1. Set the global configuration by selecting or clearing the checkboxes:
 Show contact list on mobile application

 Enable public registration over mobile application
 Enable manual approval of mobile users
Note: The Enable manual approval of mobile users checkbox is only

visible when public registration over the mobile application is activated.
If this checkbox is selected, you have control over the public
registration and you can manually approve or reject the request.
GUI section Action
Otherwise, the user is automatically assigned to the tenant.
2. Click Save Settings to save your changes.

1. Click Select Image.
2. Browse for an image and open it.
Change logo
3. Manipulate the image.
4. Click Upload Image.
Back to the list of procedures
Providing Billing Information for a Tenant
You have completed the registration to Movilitas.Cloud and have set up the system for use
for your company. Before the end of the first month of using the product, you need to provide
your billing information. In case of any change, you can update the billing information.
Procedure
3. On the tenant dashboard, click Settings.
4. Select the Billing information tab. The application displays the Billing information form.
Example:
5. Provide the required details in the form. The mandatory fields are marked with an asterisk
(*) in the form.
Filling in the form is self-explanatory, but the following list collects some best practices:
 Contact email(s) - These are the addresses where Movilitas.Cloud sends the invoice. You can
provide one or more email addresses. To add an email address to the list, enter the email
address, and then hit enter or click on another part of the form. The emails are added as
chips that you can remove by clicking on the X button.
 Notification email - This is the address where Movilitas.Cloud sends payment reminders and
the confirmation when the payment is received.
 Yes, I would like to receive payment confirmation email - This checkbox enables you to turn
on or off payment confirmations. By default, the checkbox is selected meaning that
Movilitas.Cloud sends a confirmation when the payment is received.
 The VAT number field is not applicable to the United States. This field is automatically
hidden when the selected country is the United States.
6. To receive the UBL (XML) file as an attachment along with the invoice, select the Add
UBL (XML) with invoicing email checkbox.
Note: When the Add UBL (XML) with invoicing email checkbox is selected, it is
mandatory to fill in the PO fields.
7. If the shipping address is not the same as the one in the invoice, select the Shipping
address checkbox and provide the details.
8. Click Save Settings.
Example:
Managing Users of a Tenant
Modified on: Tue, 16 May, 2023 at 6:42 PM
You can assign users to the tenant to enable coworkers to use the system. You can also search
for, edit, and unassign users.
Roles
In Movilitas.Cloud, users can have the following roles:
 Administrator
 Moderator
 Analyzer
 User
 None (for Mobile users only)
It is possible to combine Administrator, Moderator, User, or None roles with the mobile user
setting. As a mobile user, you have access to the Movilitas Mobile and Movilitas Desktop
applications. Only mobile users can be assigned to the mobile and desktop applications as
operators.
You are the administrator of every tenant that you create in the system. You, as an
administrator, can then assign users to a specific tenant with any of the above roles. A user
has one role in each tenant, and the role can be different, for example, the user has
the Administrator role in Tenant A, but the user is only a mobile user in Tenant B.
The following table explains the details of each role with respect to the Administrator UI.
Role Description
As an administrator of a certain tenant, you perform administration
activities on the tenant level as well as on the application level. You
can do the following:
 View the tenant details in the Dashboard.

Administrator  Manage the details of the tenant, for example, assign users,
create channels, or activate applications.
 Change the settings of the tenant, for example, provide billing
information.
 Configure the applications you activated for the tenant.
Moderator As a moderator of a certain tenant, you perform administration

Role Description
activities in the scope of applications rather than in the scope of the
tenant. You can do the following:
 View the tenant details in the Dashboard.

 Manage the details of the tenant, for example, assign users,
create channels, or activate applications.
 Configure the applications you activated for the tenant.
Note: The "Moderator" role is not available for the Serialized

Manufacturing and the Serialized Logistics applications.
As an analyzer of a certain tenant, you can do the following:
 Open the overview page of the tenant in the Dashboard.

 View the enabled applications, the number of active users, the
donut chart about the available channels.
 On the Users tab of the tenant, you can view the users
assigned to the tenant and display their details.
Analyzer
 In the FMD Reports application:
o You have access to the audit trail
o You can schedule reports, update existing schedules,
and download reports for analysis.
Note: The "Analyzer" role is reserved for the FMD Reports

application.
User As a user assigned to a tenant, you can do the following:
 Open the overview page of the tenant in the Dashboard and

view a limited part of the current configuration.
 View the enabled applications, the number of active users, the
donut chart about the available channels.
 On the Users tab of the tenant, you can view the users
assigned to the tenant and display their details.
Users with the "User" role can access the Serialized Manufacturing
application and the Serialized Logistics application for
administration tasks but an administrator of the specific tenant can
customize their access. They cannot control application-level settings
and certain functions. For more information, see Roles and Access to
Serialized Manufacturing Application and Roles and Access to
Serialized Logistics Application.
For other legacy applications, this role is used for operators (mobile
Role Description
users) in the warehouse and they cannot access the applications for
the specific tenant in the Administrator UI.
As a mobile user of a certain tenant without any specific role above,
you can perform activities in the warehouse but you cannot access the
Dashboard and the applications for the specific tenant in the
None (together with
Administrator UI.
Mobile user)
This role can only be used for operators (mobile users) in the
warehouse.
Irrespective of the role you have, you can change the settings of your account, like your email
address, your avatar, or your password.
Statuses
The following table summarizes the user statuses in Movilitas.Cloud.
Status Description
The user registered an account in Movilitas.Cloud by following the invitation
Pending email sent from Movilitas.Cloud, but the user has not activated the account
yet through the activation email from Movilitas.Cloud.
The user is an active member of the tenant, and the user can apply all
Active functions as per the role. This is the expected status for a user to perform
actions in Movilitas.Cloud.
The user account is inactive in Movilitas.Cloud. Only a system administrator
Inactive
can set this role (not available to administrators of the tenant).
The user account is banned in Movilitas.Cloud. Only a system administrator
Banned
can set this role (not available to administrators of the tenant).
Searching for a User and Viewing Its

Details
Procedure
3. On the Tenant Dashboard, select the Users tab. The application displays the list of users
assigned to the tenant.
4. Enter the name or the email address in the search field. Filter based on the status and/or the
role.
 The list of users is filtered based on the search criteria.

 You can reset the filter by clicking the Reset filters icon.
The following example illustrates the case when only the Administrators in Pending status
are displayed. The Pending status means that the user registered an account in
Movilitas.Cloud by following the invitation email sent from Movilitas.Cloud, but the user has
not activated the account yet through the activation email from Movilitas.Cloud:
The following example illustrates the case when searching for all active mobile users that
have the "cloud" expression in the email address or in the name:
5. Click the eye icon (More details) next to the user to view the user details.
Assigning Users to a Tenant
Assign users to the tenant to enable coworkers to use the system.

Procedure
4. Click the + icon (Assign user). The application displays the Assign user dialog.
5. Provide the email address of the person you want to assign to the tenant.
6. Specify a role.
7. (Optional) If the user does not have operator tasks on a site, that is, they do not use the
Movilitas Mobile or Movilitas Desktop application, clear the Mobile user checkbox.
Note: If you want to use the None role, make sure that the Mobile user checkbox is selected.
8. Click Assign user.
If the user has not registered in the system yet, an invitation email is sent to the email address
you provided, and the user must register first. After the user registers, the user is assigned to
the tenant immediately, but the user must activate the account to be an active user in the
system:
 Until the user activates the account, the user is in Pending status.
 After activating the account, the user is in Active status.
Editing a User
Procedure
4. Find the user and click on the user's name or the edit icon. The application displays the
Edit user dialog.
5. (Optional) Change the role of the user.
6. (Optional) Select or clear the Mobile user checkbox depending on whether the user
performs scanning activities on the site. If the user does not have operator tasks on a site, clear
the checkbox.
Note: If you want to use the None role, make sure that the Mobile user checkbox is selected.
7. Click Save.
Unassigning a User from a Tenant
Procedure
4. Find the user in the list you want to unassign.
5. Click the delete icon to remove the user from the list of users of the tenant. The application
displays a confirmation window.
6. Confirm the action by clicking Yes.
Note: The user is not removed from Movilitas.Cloud, only the connection to the tenant is
terminated. If you want to remove the user from Movilitas.Cloud, contact Movilitas.Cloud
Support.
Managing Channels for a Tenant (Overview)

Modified on: Wed, 26 Jul, 2023 at 9:52 AM
You can configure Movilitas.Cloud to communicate with an external system that the
company uses for its processes.
You create a channel to establish a connection between Movilitas.Cloud and an external

system. To maintain your connections, you can search for, edit, and delete channels.
You can configure the following types of channels in the system:
Channel Description
You use the business channel type to establish connections to external
business systems, for example:
Business  SAP ATTP

 SAP ICH
 EU Hub
You use the regulatory channel type to establish connections to regulatory

Regulatory
systems, for example, BPOM.
Shopfloor You use the shopfloor channel type to establish connections to:
Channel Description
 The shopfloor, like packaging lines.

 The public APIs of the Movilitas.Cloud applications.
You use the printing channel type to establish connections to Zebra Cloud
Printing Connect printers through the Zebra Cloud Connect server of
Movilitas.Cloud.
List of Procedures
 Creating a Channel
 Searching for a Channel and Editing a Channel
 Deleting a Channel
Creating a Channel
Procedure
3. On the Tenant Dashboard, select the Channels tab. The application displays the list of
channels assigned to the tenant.
4. Click the + icon (Create channel). The application displays the Create channel dialog.
5. Select a type from the list and click Create. The application displays the Create Channel
page with an empty form to give the basic parameters of the channel.
Example (Business Channel):

6. Enter a name for the channel and select a source.
7. Click Create Channel.
The application informs you about the additional costs. After confirming the creation, the
application displays a form where you can provide the connection details for the channel. The
form varies depending on the selected channel.
SAP ATTP example:

8. Provide the details of the connection.
9. Click Save Settings and Save Channel.
Searching for a Channel and Editing a

Channel
Procedure
4. To search for a channel, use the search criteria field and the filters:
 Enter the channel name in the search criteria field.

 Select the status, source, and type.
Example about searching for a specific SAP ATTP channel:
5. To view the channel information, click on the channel name or the edit icon (Edit
channel) next to the channel. The application displays the Edit Channel page.
 Modify the settings or

 Go back to the previous page by clicking the <- (Back) button
Example:
6. (Optional) Modify the required fields as needed.
7. Save your settings by clicking Save Settings and Save Channel, respectively.
Deleting a Channel
Procedure
4. Find the channel and click the delete icon (Delete channel) next to the channel.
The application displays a confirmation window.
5. Confirm the action by clicking Yes. The channel is removed from the list.
Configuring an FTP Channel

The File Transfer Protocol (FTP) business channel helps in creating a connection between the
FTP server and the Movilitas.Cloud application.
Use the FTP channel to upload all kinds of reports that are created in the FMD Reports
application.
In this section, you will learn how to configure an FTP channel.

Currently, the FTP channel can be used in the following applications:
 FMD Reports
For more information on the general channel actions, see Managing Channels for a Tenant
(Overview).
Procedure

3. On the Tenant Dashboard, select the Channels tab. The application displays the list of channels
4. Depending on your setup, create a new FTP channel or modify an existing one. Follow one
of the procedures described in the table below.
# Create a Channel Modify an Existing Channel
To search for an FTP channel, use the search
criteria field and the filters:
 Enter the channel name in the search
Click the + icon (Create channel). The
criteria field.
4.1 application displays the Create
 Select the status.
channel dialog.
 Select FTP as the source.
 Select Business channel as the type.
Select Business channel as the type and To view the channel information, click on the
click Create. channel name or the edit icon (Edit channel)
next to the channel.
4.2
The application displays the Create
Channel page with an empty form to give the The application displays the Edit Channel page
basic parameters of the channel. with the current channel settings.
Enter a name for the channel and select FTP as
4.3 N/A
the source.
Click Create Channel.
The application informs you about the

4.4 additional costs. After confirming the creation, N/A
the application displays the Edit Channel page
with a form where you can provide the
connection details for the channel.
Example when creating an FTP channel:
Example when opening an existing FTP channel:

5. Provide the FTP connection settings as explained in the table below:
Parameter Description
FTP Host Enter the FTP host IP or URI address.
FTP Port Enter the FTP port.
FTP Username Enter the FTP username.
FTP Password Enter the FTP password.
Secure connection Select the checkbox to activate FTPS. The data will be encrypted.
7. Validate the connection to the FTP server by clicking FTP Connection Check button. The
application displays the result and if something goes wrong, displays the reason.
If there is a connection error, make sure that you are connected to the Internet and you
provide the correct data for your FTP server.
8. (Optional) If needed, change the name of the channel and click Save Channel.
Next Steps
Select the FTP channel in the FMD Reports application to upload scheduled reports to the
FTP server.
Configuring an SFTP Channel

The Secure File Transfer Protocol (SFTP) business channel helps in creating a connection
between the SFTP server and the Movilitas.Cloud application.
Use the SFTP channel to upload all kinds of reports that are created in the FMD Reports
application.
In this section, you will learn how to configure an SFTP channel.
Currently, the SFTP channel can be used in the following applications:
 FMD Reports
(Overview).
Procedure
4. Depending on your setup, create a new FTP channel or modify an existing one. Follow one
of the procedures described in the table below.

To search for an SFTP channel, use the
search criteria field and the filters:
Click the + icon (Create channel). The  Enter the channel name in the search
4.1 application displays the Create channel criteria field.
dialog.  Select the status.
 Select SFTP as the source.
Select Business channel as the type and To view the channel information, click on
click Create. the channel name or the edit icon (Edit
channel) next to the channel.
4.2
Channel page with an empty form to give The application displays the Edit Channel
the basic parameters of the channel. page with the current channel settings.
Enter a name for the channel and select
4.3 N/A
SFTP as the source.
4.4 Click Create Channel. N/A

additional costs. After confirming the

creation, the application displays the Edit
Channel page with a form where you can
provide the connection details for the
channel.
Example when creating an SFTP channel:
Example when opening an existing SFTP channel:
5. Provide the SFTP connection settings as explained in the table below:
SFTP Host Enter the SFTP host IP or URI address.
SFTP Port Enter the SFTP port.
SFTP Username Enter the SFTP username.
SFTP Password Enter the SFTP password.
7. Validate the connection to the SFTP server by clicking SFTP Health Check button. The
application displays the result and if something goes wrong, displays the reason.
If there is a connection error, make sure that you are connected to the Internet and you
provide the correct data for your SFTP server.
Next Steps
Select the SFTP channel in the FMD Reports application to upload scheduled reports to the
SFTP server.
Configuring Zebra Cloud Connect Channel and Managing

Zebra Printers
The Zebra Cloud Connect channel enables users to register Zebra Cloud Connect printers in
Movilitas.Cloud and to check the connection status from Movilitas.Cloud.
The user can also test printing or can send the content of the printing job to a file instead of
sending it to the printer.
Prerequisite to This Article

The Zebra Cloud Connect channel communicates with the Zebra devices that are connected
to the Zebra Cloud Connect server (endpoint) of Movilitas.Cloud. To have a working
connection to a printer from Movilitas.Cloud, you first need to configure your Zebra device
to connect to the Zebra Cloud Connect server of Movilitas.Cloud. For more information, see
Connecting Zebra Cloud Connect Printers to Movilitas.Cloud.
Next Steps After Setting the Zebra Cloud Connect Channel (After This Article)
After setting the printing channel, you can define printing destinations in the specific
Movilitas.Cloud application, and then you can submit printing orders to these destinations.
Currently, the Zebra Cloud Connect channel can be used in the following applications:
 Serialized Manufacturing
(Overview).
Configuring a Zebra Cloud Connect Channel
Before registering your Zebra printers in Movilitas.Cloud, you need to set up a printing
channel.
Procedure
5. Select Printing channel as the type and click Create. The application displays the Create
Channel page with an empty form to give the basic parameters of the channel.
6. Enter a name for the channel and select Zebra Cloud Connect as the source.
The application informs you about the additional costs. After confirming the creation, the
application displays the Edit Channel page with the Zebra devices panel and the Add new
Zebra device form.
Optionally, you can change the name of the channel and then click Save Channel to update
the settings.
Example:
Next Steps
Add the Zebra Cloud Connect printers to the channel. For more information, see Adding a
Zebra Cloud Connect Printer.
Adding a Zebra Cloud Connect Printer
When adding a Zebra Cloud Connect printer to the channel, you provide the name, the device
ID, and the printer status. Optionally, you can activate sending the content of the printing jobs
to a file instead of sending them to the printer.
Before You Begin

Make sure that:
 The printers are connected to the Zebra Cloud Connect server of Movilitas.Cloud. For more
information, see Connecting Zebra Cloud Connect Printers to Movilitas.Cloud.
 You have the Zebra device ID. Find the label on the physical device and use the serial
number.
Procedure
4. To search for a Zebra Cloud Connect printing channel, use the search field and the filters:
 Enter the channel name in the search field.

 Select Zebra Cloud Connect as the source.
 Select Printing channel as the type.
5. Click on the channel name or the edit icon (Edit channel) next to the channel. The
application displays the channel settings, the Zebra devices panel, and the Add new Zebra
device form.
Note: You can also open the Add new Zebra device form by clicking Add more + button
on the Zebra devices panel.
6. Fill in the Add new Zebra device form as described in the table below. The required fields
are marked with an asterisk (*) in the form.
Field Description
Device name Enter the name of the device.
Check the label on the printer and find the serial number. Enter
Device ID
the serial number in this field.
Status Set the status of the device (Active or Inactive).
If you want to print the content of the printing jobs to a file, select
Print the content to file instead
the checkbox and then specify the email address in the field
of printer
displayed after the checkbox.
Enter the email address when printing to a file. Only applicable,

when the Print the content to file instead of printer checkbox is
selected.
Email
Note: You must add an email address to receive the file. You
cannot retrieve the file from Movilitas.Cloud.
7. Click Add New Device. The device is added to the list.
8. Click on the Refresh icon in the Zebra devices panel header to refresh the connection
status and to verify that the device is connected to Movilitas.Cloud.
Printers that are connected to Movilitas.Cloud have an active Wi-Fi icon displayed, while the
disconnected ones have an inactive (strike-through) Wi-Fi icon displayed.
Viewing and Editing Zebra Cloud Connect Printers
You can check the connection status and other details of the printers, activate or inactivate
printers, and activate or deactivate sending the content of printing jobs to a file.
Before You Begin
Make sure that:
 The printers are connected to the Zebra Cloud Connect server of Movilitas.Cloud. For more
information, see Connecting Zebra Cloud Connect Printers to Movilitas.Cloud.
 You have the Zebra device ID. Find the label on the physical device and use the serial
number.
Procedure


application displays the channel settings, the Zebra devices panel with the list of devices,
and the Add new Zebra device form.
Example:
status.
7. Click on the edit icon next to a device to view and modify the settings.
8. Modify the device settings as required.
 Change the name of the device.

 Activate or inactivate the device by selecting Active or Inactive under Status drop-down,
respectively. Before inactivating, make sure that the printer does not have assigned printing
jobs in Movilitas.Cloud.
 If you want to print the content of the printing jobs to a file, select the checkbox and then
specify the email address in the field displayed after the checkbox.
In the following example, we select the checkbox Print the content to file instead of
printer and then we give the email address where the file will be sent:
9. Click Update Device.
Sending ZPL Code to Printer

If you want to test printing on a device, you can paste the test ZPL code into the text field of a
window and send it to the printer.
Before You Begin
Take any valid ZPL code that you can use for printing.
To send the ZPL code to the printer, the connection with the device must be up and running.
You must deactivate sending the content to a file, that is, you need to physically print the
content on the device.
Procedure

status.
7. On the Zebra devices panel, find the printer you want to test.
Note: The connection with the printer must be up and running. Also, the function of sending
the content to a file must be deactivated.
Example:
8. Click on the printer icon next to the printer. The application displays a window where you
can paste the ZPL code.
9. Paste the ZPL code in the text area.
Example:
10. Click Send to printer. The ZPL code is printed on the device.
If sending the ZPL code to the printer fails for any reason, the application displays an
appropriate error message.
Deleting a Zebra Cloud Connect Printer

If you do not want to use a printer, you can delete it from the list. It is recommended to delete
only the printers that are inactivated.
Before You Begin
Make sure that the printer is in Inactive status before deleting it. Before inactivating a printer,
make sure that the printer does not have assigned printing jobs in Movilitas.Cloud.
Procedure

6. On the Zebra devices panel, find the printer you want to delete.
Example:
7. Click on the delete icon next to the printer and confirm the deletion by clicking Yes.
Configuring a Serialized Logistics for Agro API Channel

Modified on: Thu, 9 Feb, 2023 at 11:20 AM
The Serialized Logistics for Agro API is an extension of the Serialized Logistics for Agro
application. With this API channel, you can integrate with the Movilitas.Cloud application.
Through the API, you can perform the following actions:
 Send the inbound orders to the application from an external system.

 Send the outbound orders to the application from an external system.
 Receive SSCCs from the external system.
 Replace the inbound order in the application from an external system.
 Replace the outbound order in the application from an external system.
You can configure the Serialized Logistics for Agro API channel by following the steps
explained below. For more information on the general channel actions, see Managing
Channels for a Tenant (Overview).
Procedure

5. Select Shopfloor channel as the type and click Create. The application displays the Create
Channel page with an empty form to give the parameters of the channel.
6. Enter a name for the channel and select Serialized Logistics for Agro API as the source.
 The application informs you about the additional costs. Confirm the creation.
 The channel key is also generated that you will need when sending the API requests to the
Movilitas.Cloud application. You can find and copy the channel key at the top of the Edit shopfloor
channel panel.
 Optionally, you can modify the name of the channel at any time.
Example:
Next Steps
To communicate over the Serialized Logistics for Agro API:

1. Configure the Serialized Logistics for Agro application.
2. Get the authentication token. After creating the API key and secret, request a dynamic one
through the Authentication API or generate a static one.
3. Copy and keep the channel key of the Serialized Logistics for Agro API channel for the API
communication.
Configuring a TraceLink Partner Channel and Managing

SFTP Transactions
Modified on: Sat, 29 Jul, 2023 at 10:33 PM
Movilitas.Cloud application provides the TraceLink Partner channel to establish a connection

to TraceLink.
By default, the SFTP connection is automated, meaning that communication does not need
human intervention. However, the users can monitor and manage the incoming transactions
(=from TraceLink) and the outgoing transactions (=towards TraceLink).
Scenario 1
Movilitas.Cloud - including the Serialized Manufacturing application - acts as a gateway

between SAP ATTP and TraceLink systems for serialization purposes, Movilitas.Cloud
automatically uploads the files to TraceLink and automatically downloads the response files
from TraceLink:
 If a transaction fails, Movilitas.Cloud sends a notification to the email address specified on

the channel.
 You can view the status and other details of the outgoing transactions.
 You can manually upload a file to TraceLink and you can monitor the processing of the file.
 For an incoming transaction where the automatic download failed, you can view and copy
the content of the file by accessing the related TraceLink folder directly from
Movilitas.Cloud.
Scenario 2
The MAH uses Movilitas.Cloud - including the Serialized Manufacturing application - to

receive shipment files from a CMO and commission the items to the market.
 Movilitas.Cloud checks for new files in TraceLink every morning. If there is a new file, the
application downloads and processes it automatically.
 You do not need to wait for the automatic action and can pre-emptively download and
process the files manually.
 If the CMO sends the TraceLink shipment file outside TraceLink, you can upload the file to
Movilitas.Cloud and process it.
 The processed items are listed under the Serialized Manufacturing application -->
Commissioning tab.
 If the file is processed with errors, Movilitas.Cloud sends a notification to the email address
specified on the channel.
Scenario 3
The distributor in the USA market uses Movilitas.Cloud - including the Serialized Logistics
application - to receive DSCSA EPCIS files from a supplier.
 Movilitas.Cloud checks for new files in TraceLink every morning. If there is a new file, the
application downloads and processes it automatically.
 You do not need to wait for the automatic action and can pre-emptively download and
process the files manually.
 If the supplier sends the TraceLink shipment file outside TraceLink, you can upload the file to
Movilitas.Cloud and process it.
 The processed items are listed under the Serialized Logistics application --> Site
management --> Suppliers --> Uploads tab for the supplier.
 If the file is processed with errors, Movilitas.Cloud sends a notification to the email address
specified on the channel.
List of Procedures
 Configuring a TraceLink Channel
 Managing Incoming SFTP Transactions That Are Pending or In Queue (Inbox)
 Uploading a File to Movilitas.Cloud for Processing (Inbox)
 Monitoring Outgoing SFTP Transactions (Outbox)
 Uploading a File to TraceLink through SFTP (Outbox)
(Overview).
Configuring a TraceLink Channel
Procedure
4. Depending on your setup, create a new TraceLink channel or modify an existing one.
Follow one of the procedures described in the table below.
To search for a TraceLink channel, use the search

field and the filters:
Click the + icon (Create channel). The
4.1 application displays the Create channel  Enter the channel name in the search field.
dialog.  Select the status.
 Select TraceLink Partner as the source.
click Create. channel name or the edit icon (Edit channel) next
to the channel.
4.2 The application displays the Create
Channel page with an empty form to give The application displays the Edit Channel page with
the basic parameters of the channel. the current channel settings.
Enter a name for the channel and select

4.3 N/A
TraceLink Partner as the source.
4.4 Click Create Channel. N/A

additional costs. After confirming the

creation, the application displays the Edit
Channel page with a form where you can
provide the connection details for the
channel.
Example when creating a TraceLink channel:
5. Provide the settings for the TraceLink channel as explained in the table below:
Parameter Action
Enter the email address where Movilitas.Cloud can send

notifications about errors on the channel. The email will contain the
Support e-mail
name of the TraceLink channel with a link to the channel page
where the error occurred.
Enter the TraceLink company identifier of your company. Identifies

Company identifier
the sender company in the outbound TraceLink files.
Select type of connection Select the type of connection:
 HTTP
 SFTP
Parameter Action
The rest of the connection settings changes depending on the

selected type of connection.
For SFTP connection, select the environment:
Select environment  Test

 Production
SFTP username For SFTP connection, enter the username.
SFTP password For SFTP connection, enter the password.
HTTP Host For HTTP connection, enter the host URL.
HTTP Port For HTTP connection, enter the port.
HTTP Username For HTTP connection, enter the username.
HTTP Password For HTTP connection, enter the password.
Example:
Next Steps
Configure the relevant application with the TraceLink channel.
Managing Incoming SFTP Transactions That Are Pending or In

Queue (Inbox)
The Inbox tab points to the Outbox folder of TraceLink. After selecting a transaction type,
you can check the files that are still in the TraceLink folder.
Transaction Type Reason What Can You Do?
SNX_RESPONSE There was an error and the file You can download the file to
was not downloaded your local computer without
automatically from TraceLink, any processing. If the
therefore, the file is not response file contains the
processed. requested serials but the file
was placed on TraceLink too
 For example, the late, you can use this file in
response file was not your serialization activities
placed in the TraceLink outside Movilitas.Cloud.
folder related to the
transaction type on time
(timeout issue).
 Another example is that
Note: For the
Transaction Type Reason What Can You Do?
SNX_RESPONSE
transaction type, the normal
the response file does
business logic is that
not contain the expected
content, but an error
Movilitas.Cloud
message. automatically downloads
and processes the response
file, and then deletes the file
in TraceLink. These
successfully processed files
are not listed on this page.
 You can check if there
is any pending file.
You do not have to
wait for the
automated action but
you can pre-emptively
process the file. After
the file is processed,
SOM_SHIPMENT_EVENT Movilitas.Cloud has not executed Movilitas.Cloud
PT_SOMINT_SALES_SHIPMENT the daily automatic action yet. deletes the file in
TraceLink.
 To view the content of
the file, you can
download the file to
your local computer
without any
processing.
Procedure
4. To search for a TraceLink channel, use the search field and the filters:

The application displays the Edit Channel page with the current channel settings and the
TraceLink SFTP Transactions panel. By default, the Inbox tab is selected on the panel.
6. Under the Inbox tab, select the transaction type. The transaction type follows the folder
name used in TraceLink.
Transaction Type Description
A file for this transaction contains serial numbers or SSCCs as a

response to the corresponding SNX_REQUEST transaction.
SNX_RESPONSE
The files listed for this transaction type were not downloaded
automatically due to an error. In the normal case, these files are
automatically downloaded and processed.
A shipment file containing the items produced by a manufacturer

(commissioning and aggregation events).
Movilitas.Cloud automatically downloads and processes the files

every morning. However, you do not have to wait for the automated
action but you can pre-emptively download and process the file.
After the file is processed, Movilitas.Cloud deletes the file in
TraceLink.
SOM_SHIPMENT_EVENT
The items are listed under the Serialized Manufacturing application
--> Commissioning tab.
Note: As a prerequisite, the Serialized Manufacturing application

must be properly configured in advance:
 The product must be registered.

 The CMO must be registered, including SGLN. The TraceLink
Partner channel must be associated with the CMO.
A DSCSA EPCIS file that contains the items from a supplier (USA
market).
Movilitas.Cloud automatically downloads and processes the files

every morning. However, you do not have to wait for the automated
action but you can pre-emptively download and process the file.
After the file is processed, Movilitas.Cloud deletes the file in
TraceLink.
The log about the processed file is listed under the Serialized
Logistics application --> Site management --> Suppliers --> Uploads
PT_SOMINT_SALES_SHIPMENT tab for the supplier. The log contains the items and the Advanced
Shipping Notification.
Note: As a prerequisite, the Serialized Logistics application must be

properly configured in advance:
 The supplier must be registered, including SGLN. The

TraceLink Partner channel must be associated with the
supplier as the collaboration channel for inbound EPCIS.
 The warehouse must be registered, including the country
(US) and SGLN.
After selecting the transaction type, the application displays the list of files that are still in the
TraceLink folder:
 For each file, you can see the file name, the file size, and the date of the last modification. To
see the latest files and status, click on the Refresh icon next to the Transaction type drop-
down on the right.
 Download the file by clicking on the Download XML button.
 For the SOM_SHIPMENT_EVENT or PT_SOMINT_SALES_SHIPMENT transaction, you can
manually process the file by clicking Process.
 For the SOM_SHIPMENT_EVENT or PT_SOMINT_SALES_SHIPMENT transaction, the
application displays a log of the downloaded and processed files in the Processed
Files section. The Processed Files section contains the automatically and manually processed
files also:
o To see the latest files and status, click on the Refresh icon in the top-right corner of
the Processed Files section.
o To upload a file to Movilitas.Cloud for processing, use the Select File for Import and
Upload File buttons. For more information, see Uploading a File to Movilitas.Cloud
for Processing (Inbox).
In the following example, we selected the SNX_RESPONSE transaction type to view the
files that were not downloaded automatically due to an error:
In the following example, we selected the SOM_SHIPMENT_EVENT transaction type to

view the pending files and to view the processed files.
WHEN YOU WANT TO MANUALLY PROCESS
A SOM_SHIPMENT_EVENT OR PT_SOMINT_SALES_SHIPMENT FILE
FROM TRACELINK, CONTINUE WITH THE NEXT STEPS.
OTHERWISE, END OF PROCEDURE.
7. Click Process next to the file. A log is created in the Processed Files section.
8. In the Processed Files section, verify that the file was processed successfully. To see the
latest status, click on the Refresh icon on the right.
Example:
The status of the transaction can be one of the following:
Status Description
The file is downloaded and processed successfully. Then, the file is

deleted in TraceLink:
 SOM_SHIPMENT_EVENT: The items are listed under the

Serialized Manufacturing application --> Commissioning tab.
You can commission the items to the market.
 PT_SOMINT_SALES_SHIPMENT: The log about the processed
file is listed under the Serialized Logistics application --> Site
Finished (Green) o The log contains the items and the Advanced Shipping
Notification. You can perform warehouse-related
actions on the items in the mobile application.
o IMPORTANT: The log can show an error even if the
processing on the TraceLink Partner channel is
successful. Verify that the log status is successful
(checkmark icon). Otherwise, take the necessary
action. For more information, see the Verifying the
EPCIS File Received in Partnership or through a
Collaboration Channel section in Managing Suppliers.
Downloading and processing the file is in progress. Wait for the

Pending operation to be completed.
The file is downloaded and processed but there are errors. You need to
investigate the issue.
Error (Red)
The file is deleted in TraceLink.
9. Click the > (Expand) icon on the left:
 To have the content of the XML, click on the Download button and save the content into a
file.
 For a file that is successfully processed, the application either displays the processed items
or provides a link to view the processed items (depending on transaction type).
 For a file that is processed with errors, investigate the errors and take the necessary actions.
Each item that has an error is listed together with the error message.
The following tables list some typical errors.
SOM_SHIPMENT_EVENT
Error Action
1. Update the shipment file so that it contains commissioning events.

No commissioning event in
the received TraceLink 2. Upload the file manually as described in Uploading a File to
file. Movilitas.Cloud for Processing (Inbox).
1. Make sure that the CMO is correctly registered under the

Serialized Manufacturing application > Site management >
CMOs tab:
Commissioning event(s) in
the TraceLink file cannot
 The TraceLink Partner channel is associated with the CMO.
be linked to any CMO
 The SGLN of the CMO is provided.
registered in the Serialized
Manufacturing
application.
2. Upload the file manually as described in Uploading a File to
Movilitas.Cloud for Processing (Inbox).
1. Make sure that the product is registered under the Serialized
Manufacturing application > Products > Products tab.
Commissioning event(s) in
the TraceLink file cannot
Assigning the product to the CMO is strongly recommended
be linked to any product.
under the Serialized Manufacturing application > Site
The CMO is registered but
management > CMOs tab.
the product is unknown in
the Serialized
Manufacturing
application.
The serial is already Do not send serials in the shipment that are already commissioned in
commissioned. Movilitas.Cloud. Only include serials in the shipment that are not yet
Error Action
commissioned in Movilitas.Cloud.
PT_SOMINT_SALES_SHIPMENT
Error Action
1. Make sure that the supplier is correctly registered under the

Serialized Logistics application > Site management >
Suppliers tab:
 The TraceLink Partner channel is associated with the supplier

Supplier with SGLN is not as a collaboration channel for inbound EPCIS.
found.  The SGLN of the supplier (master data) is provided.

EXAMPLE 1 - SOM_SHIPMENT_EVENT
The transaction was successful. For the product, the items are organized per batch.
The transaction has errors. The SGLN of the CMO is not provided in the Serialized
Manufacturing application, hence, the application cannot identify the sender (CMO).
EXAMPLE 3 - PT_SOMINT_SALES_SHIPMENT
The transaction was successful. The user can click on the link to get to the supplier's page and
verify the processed items.
The transaction was not successful. The application could not identify the sender (supplier).
Uploading a File to Movilitas.Cloud for Processing (Inbox)
The sender might send the file to you outside TraceLink, for example, by email. After
selecting the transaction type on the Inbox tab, you can upload the received TraceLink XML
file to Movilitas.Cloud for processing. The file is not uploaded to TraceLink, it is uploaded to
Movilitas.Cloud and it is processed in Movilitas.Cloud.
The following transaction types are supported:
Transaction Type End result (Positive case)
The items are listed under the Serialized Manufacturing application

SOM_SHIPMENT_EVENT
--> Commissioning tab.
The log about the processed file is listed under the Serialized
Logistics application --> Site management --> Suppliers --> Uploads
PT_SOMINT_SALES_SHIPMENT
tab for the supplier. The log contains the items and the Advanced
Shipping Notification.
Procedure

6. Under the Inbox tab, select the SOM_SHIPMENT_EVENT transaction type:
 SOM_SHIPMENT_EVENT
 PT_SOMINT_SALES_SHIPMENT
The application displays:
 The list of files that are still in the TraceLink folder waiting for taking them.
 A log of the downloaded and processed files in the Processed Files section. The Processed
Files section contains the automatically and manually processed files also.
 The Select File for Import and Upload File buttons in the Processed Files section.
The following example illustrates uploading a SOM_SHIPMENT_EVENT file:

7. Click Select File for Import and select the file you want to upload.
After selecting the file, the Upload File button becomes active.
Example:
8. Click Upload File: <FILENAME>. A log is created in the Processed Files section.
9. In the Processed Files section, verify that the file was processed successfully. To see the
latest status, click on the Refresh icon on the right.
Example:
Status Description
The file is processed successfully:
 SOM_SHIPMENT_EVENT: The items are listed under the

Serialized Manufacturing application --> Commissioning tab.
You can commission the items to the market.
 PT_SOMINT_SALES_SHIPMENT: The log about the processed
file is listed under the Serialized Logistics application --> Site
o The log contains the items and the Advanced Shipping
Finished (Green) Notification. You can perform warehouse-related
actions on the items in the mobile application.
o IMPORTANT: The log can show an error even if the
processing on the TraceLink Partner channel is
successful. Verify that the log status is successful
(checkmark icon). Otherwise, take the necessary
action. For more information, see the Verifying the
EPCIS File Received in Partnership or through a
Collaboration Channel section in Managing Suppliers.
Processing the file is in progress. Wait for the operation to be

Pending completed.
The file is processed but there are errors. You need to investigate the
Error (Red)
issue.
10. Click the > (Expand) icon on the left:
 To have the content of the XML, click on the Download button and save the content into a
file.
 For a file that is successfully processed, the application either displays the processed items
or provides a link to view the processed items (depending on transaction type).
 For a file that is processed with errors, investigate the errors and take the necessary actions.
Each item that has an error is listed together with the error message.
The transaction was successful. For the product, the items are organized per batch.
The transaction failed. Each item that has an error is listed with the details.
The transaction was successful. The user can click on the link to get to the supplier's page and
verify the processed items.
Monitoring Outgoing SFTP Transactions (Outbox)
The Outbox tab points to the Inbox folder of TraceLink. After selecting a transaction type,
you can monitor the status of transactions, detect any issue that occurred while uploading the
files, and investigate the transaction details. You can download the request XML and the
response XML (if any).
Procedure


6. Select the Outbox tab and then select the transaction type. The transaction type follows the
folder name used in TraceLink.
Used for Serial Number Request files. The file can contain requests for
SNX_REQUEST
pack serial numbers or for SSCCs.
Used for Commissioning Request files. The file can contain stand-
SNX_DISPOSITION_ASSIGNED
alone packs and containers (SSCCs) including the aggregation details.
Used for Sales Shipment files. The file describes the shipping event of
SOM_SALES_SHIPMENT
a commissioning request.
After selecting the transaction type, the application displays the list of files that have been
uploaded to the applicable TraceLink folder:
 For each transaction, you can see the status, request ID, date and time of sending, sender,
receiver, and comments.
 Each transaction can be expanded for further details.
In the following example, we are viewing the SNX_REQUEST transactions:

The status of the transaction can be one of the following:
Status Description
The transaction was successful. The file is successfully uploaded to the

Finished (Green)
applicable folder in TraceLink.
The processing of the transaction is pending. Uploading the file to

Pending
TraceLink is in progress. Wait for the transaction to be completed.
An error occurred while uploading the file to TraceLink. The

Error (Red)
transaction failed. You need to investigate the issue.
7. To see the latest transactions and status, click on the Refresh icon next to the search field
on the right.
8. Search for a transaction by entering an expression from the request XML, as described in
the table below. The list of transactions is filtered based on the search criteria.
Transaction Type Search Expressions
Content from the request XML, for example, request ID or the

SNX_REQUEST
product code.
SNX_DISPOSITION_ASSIGNED Content from the request XML, for example, pack data or SSCC.
Content from the request XML, for example, Purchase Order (PO),
SOM_SALES_SHIPMENT
pack data, or SSCC.
9. Click the > (Expand) icon on the left to see the details of the transaction and to download
the XML files:
 Request XML
 Last raw response (if any)
EXAMPLE 1
We are searching for the SNX_REQUEST transaction with request ID

"20220309170337023". The transaction failed. We are expanding it to see the details of the
request. There is no response:
To have the content of the XML, click on the Download button.
EXAMPLE 2
In the following example, we are searching for the SNX_REQUEST transaction with request
ID "20220323110355422". The transaction is successful. After expanding the transaction, the
following are displayed:
 Transaction details
 Request XML
 Last raw response
The Last raw response contains the requested items. To have the content of the XML, click
on the Download button.
EXAMPLE 3
In the following example, we are searching for the SNX_DISPOSITION_ASSIGNED

transaction(s) that contain(s) the following pack data (product code, expiry date, batch, and
serial number):
"(01)07611618750909(17)270501(10)22070212(21)E5K650W9R633".
Only one log contains the pack and the transaction is successful. After expanding the
transaction, the following are displayed:
 Transaction details
 Request XML
To have the content of the XML, click on the Download button.

Next Steps
For failed transactions, investigate the issue and find the root cause. If needed, you can
manually upload the file to TraceLink.
Uploading a File to TraceLink through SFTP (Outbox)
The Outbox tab points to the Inbox folder of TraceLink. After selecting a transaction type,
you can import an XML file from your local computer to Movilitas.Cloud and then you can
upload the file to TraceLink. The transaction type specifies which TraceLink folder to use for
the upload. Only XML files are allowed and content validation is performed in the
background.
In the normal case, Movilitas.Cloud automatically uploads the file to TraceLink. You need to
manually upload a file because of an error, for example, the automatic upload of the file
failed. Investigate the issue before uploading a file manually.
Before You Begin
For the SNX_REQUEST transaction, make sure that the XML file you want to upload
contains a unique request ID in the description (message body):
 The request ID must be different from the one in the original XML file that failed.
 It is not possible to upload an XML file that contains an already used request ID.
 Uploading an XML file that does not contain a request ID will fail.
 For the request ID, the allowed data type is "string". Movilitas.Cloud generates request ID
based on timestamp, in the format of YYYYMMDDHHMMSSsss, where Y - Year, M - Month, D
- Day, H - Hour, M - Minute, S - Second, s - Millisecond.
Procedure

6. Select the Outbox tab and then select the transaction type. The transaction type follows the
folder name used in TraceLink.
Used for Serial Number Request files. The file can contain requests for
SNX_REQUEST
pack serial numbers or for SSCCs.
Used for Commissioning Request files. The file can contain stand-
SNX_DISPOSITION_ASSIGNED
alone packs and containers (SSCCs) including the aggregation details.
Used for Sales Shipment files. The file describes the shipping event of
SOM_SALES_SHIPMENT
a commissioning request.
After selecting the transaction type, the application displays the list of files that have been
uploaded to the applicable TraceLink folder:
 For each transaction, you can see the status, request ID, date and time of sending, sender,
receiver, and comments.
 Each transaction can be expanded for further details.
In the following example, we selected SNX_REQUEST:

7. Click Select File for Upload and select the file you want to upload. After selecting the file,
the Upload File button becomes active.
IMPORTANT: For the SNX_REQUEST transaction, make sure that the XML file you want
to upload contains a unique request ID in the description (message body):
 The request ID must be different from the one in the original XML file that failed.
 It is not possible to upload an XML file that contains an already used request ID.
 Uploading an XML file that does not contain a request ID will fail.
 For the request ID, the allowed data type is "string". Movilitas.Cloud generates request ID
based on timestamp, in the format of YYYYMMDDHHMMSSsss, where Y - Year, M - Month, D
- Day, H - Hour, M - Minute, S - Second, s - Millisecond.
8. Click Upload File: <FILENAME>. Movilitas.Cloud puts the file in the applicable folder
under the Inbox folder in TraceLink.
9. Monitor the processing of the file and make sure that the transaction is successfully
processed. To see the latest status, click on the Refresh icon next to the search field on the
right.
If the transaction fails, you need to investigate the issue again and understand the root cause.
If the problem can be resolved by repeating the upload operation, reupload the file.
Configuring a Serial Number Management Channel

Serial number management (SNM) is the internal serial numbers repository in

Movilitas.Cloud that enables the users to generate serial numbers. In the Movilitas.Cloud
application, the users can request the serial numbers using the Serial Number Management
(SNM) channel.
Currently, the SNM channel can be used in the following applications:
 Manufacturer for Pharma

 Serialized Manufacturing
(Overview).
Procedure

4. Depending on your setup, create a new SNM channel or modify an existing one. Follow
one of the procedures described in the table below.

To search for an SNM channel, use the search
criteria field and the filters:
Click the + icon (Create channel). The  Enter the channel name in the search
4.1 application displays the Create criteria field.
channel dialog.  Select the status.
 Select Serial number management as
the source.
click Create. channel name or the edit icon (Edit channel)
next to the channel.
4.2
Channel page with an empty form to give the The application displays the Edit Channel page
basic parameters of the channel. with the current channel settings.
Enter a name for the channel and select Serial
4.3 N/A
number management as the source.
Click Create Channel.
4.4 The application informs you about the N/A

additional costs. After confirming the creation,
the application displays the Edit Channel page
with a form where you can provide the
connection details for the channel.
Example:
5. Provide the SNM channel settings as explained in the table below:
Parameter/Function Description
[A-Z] [a-z] [0-9] [A-Z] – click on it to add the alphabets in capital case
Special characters
[a-z] – click on it to add the alphabets in normal case
[0-9] – click on it to add the numerical digits

Parameter/Function Description
Special characters – click on it to add the special characters
The added characters are displayed in the Charset field where you
can manually remove the unneeded character set.
Enter a number to specify the length of the serial number. The

Serial number length
allowed value is from 5 to 20.
Managing Repositories
By default, all the scans that are created for a certain tenant are stored in the common
repository of Movilitas.Cloud. If you want to have a separate repository for your scans, you
can create and manage one. After the repository is created, you can edit its name or delete it.
Movilitas.Cloud supports two types of repositories:
 FMD repository
 Serialized Logistics repository
List of Procedures
 Creating a Repository
 Viewing and Editing a Repository
 Deleting a Repository
Creating a Repository
Procedure
3. On the Tenant Dashboard, select the Repositories tab. The application displays the list of
repositories for the tenant.
4. Click + icon (Create repository). The application displays the Add new repository panel.
5. Specify a name and a source for the repository.

6. Click Create Repository. The application displays the repository settings form.
An email is sent to Movilitas.Cloud support to complete the repository settings. This process
usually takes about 1 day. You will be contacted by email once the repository is available.
Viewing and Editing a Repository
Procedure
4. Click on the repository name or the edit icon next to the repository name. The application
displays the Edit Repository page.
The following example illustrates the settings page for an FMD repository. You can see the
same parameters for a Serialized Logistics repository.
5. Optionally, modify the repository name.
IMPORTANT: Do NOT change the repository settings. If you want to change any setting,
contact Movilitas.Cloud support to avoid making your repository unavailable due to incorrect
data.
6. Save your name update by clicking Save Repository.
Deleting a Repository
Delete a repository only in case you are sure you do not want to use it for storing data
anymore. Existing data already stored in the repository will not be deleted.
Procedure

4. Find the repository and click on the delete icon.
5. Confirm the deletion.
Managing API Keys and Static Token

External systems can send data to Movilitas.Cloud through the API of the given
Movilitas.Cloud application. These external systems must be authenticated first so that they
can communicate with Movilitas.Cloud.
For authentication, you must get a token in one of the following ways:
Token Type How to Get the Token? Expiry
1. Create an API key and secret.

Valid for one day. Reauthentication
Dynamic 2. Request the token through the Authentication
is required.
API by using the API key and secret.
1. Create an API key and secret. No expiry date. You can revoke it
Static 2. Generate the token on the API Keys page, and generate a new token at any
next to the API key and secret. time.
The authentication token is needed for each API call that is sent to Movilitas.Cloud.
Although Movilitas.Cloud accepts a static token for authentication, we recommend you to use
a dynamic token to comply with the highest security standards.
Note: Dynamic tokens cannot be used when you want to send CRPT OMS messages to
Movilitas.Cloud.
This article describes:
 How to manage API keys that are essential to get the authentication token (both dynamic
and static).
 How to manage static tokens.
List of Procedures
 Creating an API Key
 Copying an API Key to Your Clipboard
 Editing an API Key
 Generating a Static Token
 Retrieving the Static Token
 Revoking the Static Token
 Deleting an API Key
Creating an API Key
You must create an API key in Movilitas.Cloud, independently of the token type you want to
use.
Procedure
3. On the Tenant Dashboard, select the API keys tab. The application displays the list of API
keys generated for the tenant.
4. Click the + icon (Create API key). The application displays the Create API key form
with the automatically generated API key.
To copy the API key to your clipboard, click the Copy icon next to the API key. You can use
the API key to get a dynamic token for API communication.
5. Specify a name and an API secret.
Note: The password must be a minimum of 8 characters long. It must include at least one
uppercase letter, lowercase letter, number, and special character. Keep the API secret in a
safe place because you will need it along with the API key when sending an authentication
request over API to get a dynamic token.
6. Click Create.
Copying an API Key to Your Clipboard
You will need the API key when you want to use a dynamic token.
Procedure
4. Click the Copy icon next to the API key.
The API key is copied to your clipboard and you can use the API key to get a dynamic token
for API communication.
Editing an API Key
Procedure
4. Click on the API key name or the edit icon next to the API key. The application displays
the Update API key form and the Static token panel.
5. Modify the API key name or the API secret, as needed.
To copy the API key to your clipboard, click the Copy icon next to the API key. You can use
the API key to get a dynamic token for API communication.
6. Click Update.
Generating a Static Token
After you create an API key, you can generate a static token. Also, after you revoke all the
tokens for the API key, you can generate the static token again.
Note: If you want to send CRPT OMS messages to Movilitas.Cloud over API, you must use
static tokens. For other use cases, the static token is an alternative to dynamic tokens and you
can decide which one to use. However, static tokens are less secure than dynamic tokens.
Procedure
Example:
5. Click Generate Static Token. The application generates and displays the static token.
To copy the static token to your clipboard, click the Copy icon next to the token. You can use
the token for authentication when sending API requests to Movilitas.Cloud.
Example:
Retrieving the Static Token
Once a static token has been generated, and you revisit the API key page, the static token is
not displayed for security reasons. You need to retrieve it from the database and then you can
copy the token to your clipboard.
Procedure

Example:
5. Click Retrieve Static Token.
To copy the static token to your clipboard, click the Copy icon next to the token. You can use
the token for authentication when sending API requests to Movilitas.Cloud.
Example:
Revoking the Static Token
You can revoke the static token generated for the API key. By revoking the static token, you
also revoke all the dynamic tokens generated for the API key to date.
Procedure
In the following example, we have a static token generated for the API key:
5. Click Revoke Static Token. The application displays a confirmation window informing
you that you are going to revoke all the tokens (static and dynamic) by confirming the action.
6. Click Yes.
Deleting an API Key
Procedure
4. Click the delete icon next to the API key you want to remove and confirm the deletion.
Viewing Logs
Modified on: Fri, 17 Dec, 2021 at 3:38 PM
Movilitas.Cloud logs each user activity connected to each tenant. By default, all the user logs
of the actual day are displayed for the selected tenant. You can filter the logs to view the
activities of a certain user in a given time period.
Note: Movilitas.Cloud refers to tenants as customers in the logs.
Procedure
3. On the Tenant Dashboard, select the Logs tab. The application displays the search criteria
fields and all the user logs of the actual day.
4. In the Filter by drop-down, select User.
5. Enter the name or email address and click Add filter. The selected filter is displayed after
the Time period section.
6. Set a time period.
7. Click Search. The logs are filtered based on the given criteria.
 You can expand a log by clicking > next to the log.

 You can set the displayed number of items per page by selecting Items per page
drop-down.
 You can reset the filter by clicking Reset.
Example:
Managing Pending User Invitations
Modified on: Wed, 14 Sep, 2022 at 12:48 PM
You can get an overview of all pending user invitations for your tenant. You can resend the
invitation email or remove the invitation to join the tenant.
Procedure
2. Select the tenant or click Open tenant next to it. The application displays the Tenant
Dashboard.
Example:
3. On the Tenant Dashboard, click Pending invitations under the donut chart. The
application displays the list of invited users and the action buttons on the right.
Note: When the Mobile user checkbox was selected during the invitation (while assigning
the user), two records are added to the list with the same email address: one for the user role
and one for the mobile user capability.
Example:
4. (Optional) Do one of the following:
 To resend the invitation by email, click on the Resend invitation button (Redo icon).
 To remove the invitation to join the tenant, click on the Remove invitation button
(Delete icon).

Movilitas

Uploaded by

Copyright:

Available Formats

Movilitas

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Movilitas

Uploaded by

Copyright:

Available Formats

Movilitas.

 Manufacturers, wholesalers, pre-wholesalers, parallel importers, repackers, and

 Configuring and managing the Movilitas.Cloud applications.

In Movilitas.Cloud, you can establish connections to the following external systems:

You have two choices:

About Serialized Manufacturing Application

The Serialized Manufacturing application helps manufacturers to perform serialization of

Connections to External Systems, Shopfloor, and Printing Destinations

In the pharmaceutical industry, you can connect to the following:

 BPOM (Indonesia market)

Enables the users to configure and manage the application.

The Serialized Manufacturing application can be extended through the Manufacturer V2

About Serialized Logistics Application

With this application, you can use the following capabilities:

Connecting to External Systems

The connections to external systems are established through respective channels.

Connecting to a GS1 Digital Link Resolver Server

Enables the users to configure and manage the application:

 Managing inbound and outbound orders.

 Preprint SSCC labels on Zebra Cloud Connect printers

Offline Scanning (Only for Verification)

Serialized Logistics V2 API and Webhook

 Create inbound order

Movilitas.Cloud Tenant Dashboard Overview

# GUI Section Description

The navigation pane contains:

 Movilitas.Cloud logo directing you to the Console

For the login view, see Movilitas.Cloud Console Overview.

 Go back to the Tenant Dashboard opening page

Tenant name and

 A donut chart about the current channels

 Download Movilitas Mobile - You can download the

Displays the list of activated applications.

8 Activated applications To access an application click on the applicable tile or go to

You can modify the following settings of the tenant:

Managing the Company Information, Global Settings, and Company

2. Select the tenant or click Open tenant next to it.

4. On the Settings tab, configure the general settings.

GUI section Action

 Show contact list on mobile application

Note: The Enable manual approval of mobile users checkbox is only

Otherwise, the user is automatically assigned to the tenant.

2. Click Save Settings to save your changes.

Back to the list of procedures

Providing Billing Information for a Tenant

1. Go to Movilitas.Cloud Console --> My tenants.

2. Select the tenant or click Open tenant next to it.

3. On the tenant dashboard, click Settings.

8. Click Save Settings.

In Movilitas.Cloud, users can have the following roles:

 View the tenant details in the Dashboard.

Moderator As a moderator of a certain tenant, you perform administration

 View the tenant details in the Dashboard.

Note: The "Moderator" role is not available for the Serialized

 Open the overview page of the tenant in the Dashboard.

Note: The "Analyzer" role is reserved for the FMD Reports

 Open the overview page of the tenant in the Dashboard and

The following table summarizes the user statuses in Movilitas.Cloud.

Searching for a User and Viewing Its

2. Select the tenant or click Open tenant next to it.