The clients represent external destinations and they are involved in outbound external orders/transfers.

In the Serialized Logistics application:

You can register and manage your clients.
You can establish a partnership with a client in Movilitas.Cloud.
For the USA, you can get the complete profile of a client from the Pulse Profile system.

When connecting to BPOM, all the shipping locations saved as clients on the BPOM channel settings page are automatically imported into the Serialized Logistics application. You may need to reorganize the address data after the import.

When sending an IDOC Delvry to Movilitas.Cloud from SAP ICH or uploading an IDOC Delvry on the SAP ICH channel, the client master data and the delivery address are automatically created in the Serialized Logistics application. However, you still need to perform some manual actions to complete the client configuration:

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

List of Procedures

Creating a Client (Master Data)
Registering the Delivery Addresses of a Client
Establishing a Partnership with a Client in Movilitas.Cloud
Removing the Partnership with a Client in Movilitas.Cloud
Searching for a Client
Viewing a Pulse Profile (DSCSA USA Only)
Viewing the Orders (Deliveries) of a Client
Updating a Client
Deleting a Client

Creating a Client (Master Data)

To create a client, you need to provide the master data of the client. The master data includes the client name, the client ID, and the business address (business location). If the client has one or more delivery addresses (facility/storage locations), you can provide further addresses after creating the client.

Automatic Client Creation

The Serialized Logistics application offers automatic client creation in the following cases meaning that you do not need to manually create them from scratch:

Case	Description	Any Manual Action after Automatic Client Creation?
Connection to BPOM (Indonesia)	You can save the client on the BPOM channel settings page and automatically import it to the Serialized Logistics application. For more information, see Configuring a BPOM Channel, Managing Logs, Viewing BPOM Returns, and Importing Shipping Locations.	Yes. You may need to reorganize the address data after the import. Go to Updating a Client.
IDOC Delvry from SAP ICH	After sending an IDOC Delvry to Movilitas.Cloud from SAP ICH or uploading an IDOC Delvry on the SAP ICH channel, the client master data and the delivery address are automatically created in the Serialized Logistics application. As a prerequisite, you need to configure an SAP ICH channel including the GLN values of the participants and you also need to configure SAP ICH to have the Movilitas.Cloud endpoint where the IDOC Delvry is sent. For more information, see Configuring and Monitoring an SAP ICH Channel.	Yes: Provide the SGLN (location data): Client master data (always). Client delivery address (only for purchase orders and donations). To fulfill replacement orders for the client in the USA, select the Don't send EPCIS file, create DSCSA letter checkbox. Otherwise, leave the checkbox in the default (cleared) status. If you want to use the delivery address SGLN as the receiver in the outbound DSCSA EPCIS file for the client in the USA, select the Delivery addresses are 3PLs of the Client checkbox. If multiple delivery addresses belong to the same 3PL partner, select the Use different Receiver sGLN for EPCIS checkbox and specify the common receiver SGLN to be used as the receiver in the DSCSA EPCIS in each applicable client delivery address setting. 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, select the Send full EPCIS checkbox. Go to Updating a Client.
Manually uploaded IDOC

Case

Description

Any Manual Action after Automatic Client Creation?

Connection to BPOM (Indonesia)

You can save the client on the BPOM channel settings page and automatically import it to the Serialized Logistics application. For more information, see Configuring a BPOM Channel, Managing Logs, Viewing BPOM Returns, and Importing Shipping Locations.

Yes. You may need to reorganize the address data after the import. Go to Updating a Client.

IDOC Delvry from SAP ICH

After sending an IDOC Delvry to Movilitas.Cloud from SAP ICH or uploading an IDOC Delvry on the SAP ICH channel, the client master data and the delivery address are automatically created in the Serialized Logistics application.

As a prerequisite, you need to configure an SAP ICH channel including the GLN values of the participants and you also need to configure SAP ICH to have the Movilitas.Cloud endpoint where the IDOC Delvry is sent. For more information, see Configuring and Monitoring an SAP ICH Channel.

Yes:

Provide the SGLN (location data):
- Client master data (always).
- Client delivery address (only for purchase orders and donations).
To fulfill replacement orders for the client in the USA, select the Don't send EPCIS file, create DSCSA letter checkbox. Otherwise, leave the checkbox in the default (cleared) status.
If you want to use the delivery address SGLN as the receiver in the outbound DSCSA EPCIS file for the client in the USA, select the Delivery addresses are 3PLs of the Client checkbox.
- If multiple delivery addresses belong to the same 3PL partner, select the Use different Receiver sGLN for EPCIS checkbox and specify the common receiver SGLN to be used as the receiver in the DSCSA EPCIS in each applicable client delivery address setting.
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, select the Send full EPCIS checkbox.

Go to Updating a Client.

Manually uploaded IDOC

Procedure

1. In the Serialized Logistics application, select Site management --> Clients tab. The application displays the list of clients and the Create client form.

Note: When viewing the details of a client, you can open the Create client form by clicking Create.

Example:

2. On the Master data tab, fill in the form as described below. The required fields are marked with an asterisk (*) in the form.

Field	Country	Action
Client name	All	Enter the client name. (USA only) If a few characters are entered for a client in the USA market, the application searches the Pulse Profile system and offers hits in a drop-down: Select a value and the application populates the address and country (United States) fields and displays the Pulse logo button at the bottom of the form. By clicking on the Pulse logo button, the application fetches the complete profile of the client from the Pulse Profile system and shows the details in a pop-up. For more information, see Viewing a Pulse Profile (DSCSA USA Only).
Client ID	All	Enter a unique client ID. The unique ID enables the application to identify the client.
Client does not have a GLN	All	If the client does not have a Global Location Number (GLN), select this checkbox. As a result, the Client SGLN field disappears.
Client SGLN	All	Enter the location number of the client in the SGLN format: <GS1 company prefix>.<location reference>.<extension or "0" when no extension>. For example, "1234567.00012.0". This SGLN is the business, owning party, or sold-to location. The client SGLN is required in the following cases: You send the shipping event to the client in a TraceLink XML file. You send the shipment details in an EPCIS 1.2 file. To use the built-in GLN to SGLN converter, click on the conversion button (Help me to define the SGLN) on the right. The application displays a pop-up. Provide the following data and click Convert: Client location in the GLN format (13 digits). Company prefix length (6 to 11 digits or no company prefix). If the company does not have a company prefix, select No company prefix. The question mark (help) icon displays a short message about it after hovering. This is equivalent to a 12-digit long company prefix. Extension digit that is 0 by default. Example: The provided GLN value is converted to the SGLN format and the field is populated. Example:
City	All	Enter the city where the client is located.
Street	All	Enter the street. The form offers three rows (levels) for the street data.
State	All	Enter the state.
ZIP code	All	Enter the postal code.
Select country	All	Select the country. Start entering the country name to filter the countries. For locations imported through a BPOM channel, the field is automatically set to Indonesia and the field is read-only.
Don't send EPCIS file, create DSCSA letter	USA	To fulfill a replacement order, select the checkbox. A DSCSA letter is sent by email instead of a DSCSA EPCIS file to an external system (SAP ICH). The delivery address must be in the USA. To fulfill a purchase order (delivery) or donation, clear the checkbox (default). The DSCSA EPCIS file is sent to an external system (SAP ICH). The DSCSA letter is a PDF document that contains a QR code (link) to a website where the receiver can download the DSCSA EPCIS file. The DSCSA letter parameters (receiver email, sending company name, sending company logo) are configured under the Settings tab. For a client in a country other than the USA, the checkbox is not visible.
Send full EPCIS	Non-USA	Select this checkbox to send a regular EPCIS file to SAP ICH about the shipment to the client. The regular EPCIS file contains the commissioning, aggregation, and shipping events without master data. Only applicable when the following conditions are met: The tenant acts as a 3PL for the supplier. See the Site management --> Suppliers tab. The collaboration channel for the outbound EPCIS file on behalf of the MAH is SAP ICH. See the Site management --> Suppliers tab. The warehouse is in the USA. See the Site management --> Warehouses tab. The client is in a country other than the USA but the delivery address can be in the USA. The following list helps you to define the setting of this checkbox: Client delivery address is in the USA but a regular EPCIS is required --> Select the checkbox. Client delivery address is in the USA and a DSCSA EPCIS is required --> Clear the checkbox. Client delivery address is in a country other than the USA and a regular EPCIS is required --> Select the checkbox. Note: Otherwise, a non-compliant EPCIS is generated that contains the shipping event only. If the client is in the USA, the checkbox is not visible. The application generates a DSCSA EPCIS file that is either sent to SAP ICH (3PL mode) or downloadable (wholesaler mode).
BPOM id	Indonesia	Unless already filled in during the shipping location import, enter the BPOM ID of the client. Only applicable when the selected country is Indonesia. For imported locations, the field is read-only. For locations created on-demand, the field is editable. Note: Make sure that you are using the BPOM ID that is assigned to that location by BPOM. The BPOM ID is important for the sender who wants to ship items to this location because the destination BPOM ID is sent to BPOM during the report.
Collaboration channel - outbound EPCIS DSCSA	USA	Select the collaboration channel to send the DSCSA EPCIS file about the shipment to the external system represented by the channel. Only applicable when the selected country is the United States. Supported channels: LSPediA SAP ICH TraceLink Partner AS2 SFTP The application offers the channels for selection that are configured on the tenant. If an AS2 channel is selected, the application displays the AS2 partner field. If an SFTP channel is selected, the application displays the File path field.
AS2 partner	USA	Select the AS2 partner from the drop-down. The application offers the AS2 service providers onboarded in Movilitas.Cloud. If you cannot find the AS2 partner in the list, contact Movilitas.Cloud Support. Only applicable when the selected country is the United States and an AS2 channel is selected as the collaboration channel for outbound DSCSA EPCIS.
File path	USA	Set the file path on the SFTP server. Follow the help text under the field and do not add "/" at the beginning of the file path. If the file path is not given, the file is saved in the roots folder. If the specified folder does not exist, the folder is automatically created during the first file upload unless a setting on the SFTP server blocks creating the folder. Only applicable when the selected country is the United States and an SFTP channel is selected as the collaboration channel for outbound DSCSA EPCIS.
Client E-mail	All	Enter the general email address of the client.
E-mail address for sending DSCSA EPCIS	USA	Enter the contact email address to send the DSCSA EPCIS file by email. You can send the file under the Transfers --> Outbound External --> Transfers page (Note: Orders are not supported yet). Only active if a collaboration channel for outbound DSCSA EPCIS files is not selected. Once a collaboration channel is selected, the DSCSA EPCIS file is sent over the channel, and sending by email is not active. The field is only available when the country of the client is the United States.
E-mail address for EPCIS exception handling	USA	Enter the contact email address to handle inbound EPCIS exceptions. The field is only available when the country of the client is the United States.
E-mail address for Verifications	USA	Enter the contact email address in case of issues with verifications. The field is only available when the country of the client is the United States.
E-mail address for Trace request	USA	Enter the contact email address to send the TI trace requests. The field is only available when the country of the client is the United States.
Delivery addresses are 3PLs of the Client	USA	If the GLN of the delivery address shall be used as the receiver in the outbound DSCSA EPCIS file, select the checkbox. Otherwise, leave the checkbox cleared (default) and the GLN of the client master data is used as the receiver in the outbound DSCSA EPCIS file. The checkbox is only available when the country of the client is the United States.
Registration type	Kazakhstan	Enter the registration type as specified in the generic report that is sent from SAP ATTP to Movilitas.Cloud. Only applicable when the selected country is Kazakhstan and the generic report from SAP ATTP is an import request to Kazakhstan. Note: When receiving the generic report from SAP ATTP for the first time, the client is auto-created, meaning that the field is auto-filled with the value in the generic report from SAP ATTP.
Registration number	Kazakhstan	Enter the registration number as specified in the generic report that is sent from SAP ATTP to Movilitas.Cloud. Only applicable when the selected country is Kazakhstan and the generic report from SAP ATTP is an import request to Kazakhstan. Note: When receiving the generic report from SAP ATTP for the first time, the client is auto-created, meaning that the field is auto-filled with the value in the generic report from SAP ATTP.
Email to send EPCIS Tatmeen file	UAE	Enter the email address where Movilitas.Cloud can send the EPCIS file that was reported to Tatmeen after shipping the order (import permit) to the client. The field is only available when the country of the client is the United Arab Emirates. To send the EPCIS Tatmeen file by email, the following conditions must be fulfilled: The tenant acts as a 3PL for the supplier of the products. A Tatmeen regulatory channel is configured and associated with the supplier. A shipping action to the client is performed in the mobile application.
SFTP channel	UAE	Select a previously configured SFTP channel to send the EPCIS Tatmeen file to the SFTP server. The EPCIS file is reported to Tatmeen and is sent to the SFTP server after shipping the order (import permit) to the client. The field is only available when the country of the client is the United Arab Emirates. To send the EPCIS Tatmeen file to an SFTP server, the following conditions must be fulfilled: The tenant acts as a 3PL for the supplier of the products. A Tatmeen regulatory channel is configured and associated with the supplier. An SFTP channel is configured and associated with the client. A shipping action to the client is performed in the mobile application. To stop sending files to an SFTP server, clear the field by clicking on the X button.
File path	UAE	Once an SFTP channel is selected, set the file path on the SFTP server. Follow the help text under the field and do not add "/" at the beginning of the file path. If the file path is not given, the file is saved in the roots folder. The field is only available after an SFTP channel is selected.
Tracelink collaboration channel	Not country-specific	Select a previously configured TraceLink Partner channel. This setting is required when your company reports the shipping event to the client in TraceLink. The field is only available when your tenant has a TraceLink Partner channel and an SAP ATTP channel in Movilitas.Cloud.
Tracelink company identifier	Not country-specific	Enter the TraceLink company identifier of the client. This setting is required when your company reports the shipping event to the client in TraceLink. The field is only available when your tenant has a TraceLink Partner channel and an SAP ATTP channel in Movilitas.Cloud.

3. Click Save. The client is added to the list.

Next Steps

Register the delivery address(es) of the client. For more information, see Registering the Delivery Addresses of a Client.

You can establish a partnership with the client in Movilitas.Cloud. For more information, see Establishing a Partnership with a Client in Movilitas.Cloud.

Back to the list of procedures

Registering the Delivery Addresses of a Client

The delivery address holds the facility/storage/ship-to location information.

Procedure

1. In the Serialized Logistics application, select Site management --> Clients tab. The application displays the list of clients.

2. Find and select the client in the list you want to update.

3. On the Update client form, select the Delivery addresses tab.

In the following example, the selected client does not have any delivery address yet:

4. To add a delivery address, click Add Delivery Address. The application displays the Create delivery address pop-up with a form.

Example:

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

Field	Action
Delivery address name	Enter the name of the delivery address.
Delivery address ID	Enter a unique delivery address ID.
Delivery address SGLN	Enter the location number of the facility in the SGLN format: <GS1 company prefix>.<location reference>.<extension or "0" when no extension>. For example, "1234567.00012.0". This SGLN is the facility, storage, or ship-to location where the shipments are sent. The delivery address SGLN is required in the following cases: You send the shipping event to the client in a TraceLink XML file. You send an EPCIS shipment file. To use the built-in GLN to SGLN converter, click on the conversion button (Help me to define the SGLN) on the right. The application displays a pop-up. Provide the following data and click Convert: Client delivery address location in the GLN format (13 digits). Company prefix length (6 to 11 digits or no company prefix). If the company does not have a company prefix, select No company prefix. The question mark (help) icon displays a short message about it after hovering. This is equivalent to a 12-digit long company prefix. Extension digit that is 0 by default. Example: The provided GLN value is converted to the SGLN format and the field is populated.
Use different Receiver sGLN in EPCIS	If the Delivery addresses are 3PLs of the Client checkbox is selected in the client master data settings, the Use different Receiver sGLN in EPCIS checkbox is displayed in the client delivery address settings. Set the Use different receiver SGLN for EPCIS checkbox as follows: If multiple delivery addresses belong to the same 3PL partner, select the checkbox to use a common SGLN as the receiver in the outbound DSCSA EPCIS file and provide the SGLN in the Receiver SGLN field in each applicable delivery address settings. If one delivery address belongs to the 3PL partner, leave the checkbox in cleared status (default). The given delivery address SGLN is used as the receiver in the outbound DSCSA EPCIS file. Note: Only applicable to the USA and when the tenant acts as a 3PL.
Receiver SGLN	Enter the location number of the common receiver in the SGLN format: <GS1 company prefix>.<location reference>.<extension or "0" when no extension>. For example, "1234567.00012.0". The given common receiver SGLN is used as the receiver in the outbound DSCSA EPCIS file while the delivery address master data and the shipping destination location data still point to the specific delivery address in the file. You can use the built-in GLN to SGLN converter by clicking on the conversion button (Help me to define the SGLN) on the right. For more information on the converter, see the description of the Delivery address SGLN field above. The Receiver SGLN field applies and can be edited if the Use different receiver SGLN for EPCIS checkbox is selected. Note: Only applicable to the USA and when the tenant acts as a 3PL.
City	Enter the city.
Street	Enter the street. The form offers three rows (levels) for the street data.
State	Enter the state.
ZIP code	Enter the postal code.
Select country	Select the country. Start entering the country name to filter the countries. Required in one of the following cases: A TraceLink collaboration channel is set for the client and the shipping event is triggered from SAP ATTP. Shipping to the USA.

Example:

6. Click Save. The shipping address is added to the list.

Example:

Back to the list of procedures

Establishing a Partnership with a Client in Movilitas.Cloud

By establishing a partnership in Movilitas.Cloud, the supplier and the client are integrated within Movilitas.Cloud with their customized views and functions. The partnership enables the supplier and the client to exchange data in an efficient, controlled, and secure manner.

You can invite a client to be a partner in Movilitas.Cloud by providing the contact email address.

If the client does not have a tenant in Movilitas.Cloud, the client registers a tenant. Depending on the payment model, the client becomes a full-paying customer in Movilitas.Cloud or the supplier that sent the invitation pays the invoices and the client is in "Partner" mode. Then, the client accepts the invitation and gets access to the Serialized Logistics application in a customized view.
If the client already has a tenant in Movilitas.Cloud, the client reviews the partner request, accepts the invitation, and gets access to the Serialized Logistics application in a customized view.

Procedure

1. In the Serialized Logistics application, select Site management --> Clients tab. The application displays the list of clients.

2. Find and select the client to view its details. The application displays the master data of the client on the Update client panel and the empty Invite partner panel.

Example:

3. On the Invite partner panel, enter the contact email address.

Example:

4. Click Invite Partner.

Case	System Response	Action
The contact email address is not known in the system.	The application sends a registration email to the address. The client has to register a tenant in Movilitas.Cloud and then accept the partner request. Until the partner request is accepted, the request is in pending status. Example:	Track the status of the partner request on the Tenant Dashboard, under the Partner management tab. You can cancel the request by clicking on the cancel icon on the right.
The contact email address belongs to one tenant in Movilitas.Cloud.	The application sends a partner review request email to the address. Note: The email address must belong to a user with the “Administrator” role so that the partnership can be established. Until the partner request is accepted, the request is in pending status. Example:	Track the status of the partner request on the Tenant Dashboard, under the Partner management tab. You can cancel the request by clicking on the cancel icon on the right.
The contact email address belongs to multiple tenants in Movilitas.Cloud.	The application displays the Multiple partner options window to select a tenant from the list.	1. Select a tenant and click Confirm. After the tenant is selected, the application sends a partner review request email to the address. Note: The email address must belong to a user with the “Administrator” role so that the partnership can be established. Until the partner request is accepted, the request is in pending status. You can cancel the request by clicking on the cancel icon on the right. 2. Track the status of the partner request on the Tenant Dashboard, under the Partner management tab. You can cancel the request by clicking on the cancel icon on the right.

Case

System Response

Action

The contact email address is not known in the system.

The application sends a registration email to the address.

The client has to register a tenant in Movilitas.Cloud and then accept the partner request.

Until the partner request is accepted, the request is in pending status.

Example:

Track the status of the partner request on the Tenant Dashboard, under the Partner management tab.

You can cancel the request by clicking on the cancel icon on the right.

The contact email address belongs to one tenant in Movilitas.Cloud.

The application sends a partner review request email to the address.

Note: The email address must belong to a user with the “Administrator” role so that the partnership can be established.

Until the partner request is accepted, the request is in pending status.

Example:

Track the status of the partner request on the Tenant Dashboard, under the Partner management tab.

You can cancel the request by clicking on the cancel icon on the right.

The contact email address belongs to multiple tenants in Movilitas.Cloud.

The application displays the Multiple partner options window to select a tenant from the list.

1. Select a tenant and click Confirm.

After the tenant is selected, the application sends a partner review request email to the address. Note: The email address must belong to a user with the “Administrator” role so that the partnership can be established.
Until the partner request is accepted, the request is in pending status.
You can cancel the request by clicking on the cancel icon on the right.

2. Track the status of the partner request on the Tenant Dashboard, under the Partner management tab.

You can cancel the request by clicking on the cancel icon on the right.

Once the partner request is accepted, the partnership is live. The application displays the active partnership as follows:

Indicators	Description	Example
Partnership status indicator next to the client name in the list	The status indicator displays the payment model in place: Movilitas.Cloud customer (full-paying customer) in purple. Partner in red. If there is no partnership status indicator, that means a partnership is not established with the client in Movilitas.Cloud.
Invite partner panel	Status - Active partner. Name of the tenant. Payment model - Movilitas.Cloud customer (full-paying customer) versus Partner.	The following example illustrates tenant "Partner Client" with payment model "Partner":

Indicators

Description

Example

Partnership status indicator next to the client name in the list

The status indicator displays the payment model in place:

Movilitas.Cloud customer (full-paying customer) in purple.
Partner in red.

If there is no partnership status indicator, that means a partnership is not established with the client in Movilitas.Cloud.

Invite partner panel

Status - Active partner.
Name of the tenant.
Payment model - Movilitas.Cloud customer (full-paying customer) versus Partner.

The following example illustrates tenant "Partner Client" with payment model "Partner":

Back to the list of procedures

Removing the Partnership with a Client in Movilitas.Cloud

You can remove the partnership with a client in Movilitas.Cloud. After the partnership is removed, the integration between the supplier and the client is degraded. The data exchange between the supplier and the client in Movilitas.Cloud is canceled.

Procedure

1. In the Serialized Logistics application, select Site management --> Clients tab. The application displays the list of clients.

2. Find and select the client to view its details. The application displays the master data of the client on the Update client panel and the active partner on the Invite partner panel.

3. On the Invite partner panel, click on the delete icon (Remove partner) on the right.

The application asks you to confirm the action.

4. In the confirmation window, click Yes.

The application removes the partnership with the client.
The data exchange between the supplier and the client in Movilitas.Cloud is canceled.
The client still has the tenant in Movilitas.Cloud but the configuration is not updated from the supplier anymore.

Back to the list of procedures

Searching for a Client

Procedure

1. In the Serialized Logistics application, select Site management --> Clients tab. The application displays the list of clients.

2. Enter the client name in the search field.

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

3. Select the client to view its details.

Check the client master data on the Master data tab. You can find screenshot examples in this procedure.
Check the delivery addresses on the Delivery addresses tab. For screenshot examples, see Registering the Delivery Addresses of a Client.

In the following example, we are searching for the client "Apotek Dummy":

The client is located in Indonesia and is imported through the BPOM channel as stated under the client name on the left.
The full client address is imported into the Street field which may need reorganization.
The client has a BPOM id that was also imported through the BPOM channel.
The client is not a partner in Movilitas.Cloud.

In the following example, we are searching for the client "Dubai Client":

The client is located in the United Arab Emirates.
The client SGLN is provided because the shipment is reported to Tatmeen.
The EPCIS file is sent to the client by email because the Email to send EPCIS Tatmeen file field is filled in.
The EPCIS file is also sent to an SFTP server through the selected SFTP channel. The file is uploaded to the SFTP location as given in the file path.
The client is not a partner in Movilitas.Cloud.

In the following example, we are searching for the client "Partner Client":

The tenant established a partnership with the client in Movilitas.Cloud.
The client is in "Partner" mode. The tenant that sent the invitation pays the invoices.
The client is located in Belgium.
The client SGLN is provided.

In the following example, we are searching for the client "Movilitas Client Belgium":

The client is located in Belgium.
The tenant has a TraceLink and an SAP ATTP channel, so the TraceLink collaboration channel and TraceLink company identifier fields are displayed.
The client receives the shipping event in TraceLink. The SGLN field and the TraceLink fields are set. The delivery address must also be set as described in Updating a Client.
The client is not a partner in Movilitas.Cloud.

In the following example, we are searching for the client "Pharmacy Client USA":

The client is located in the USA.
The client does not have a GLN so the Client does not have a GLN checkbox is selected.
Contact email addresses to perform DSCSA-related tasks are added. A general email address is also added for topics other than DSCSA-related tasks.
It is not possible to send an EPCIS file because the client does not have a GLN:
- There is no collaboration channel to send DSCSA EPCIS files.
- Creating DSCSA letter does not apply either because that function is for replacement orders only with a DSCSA EPCIS file requirement.
The Pulse logo button is available to fetch the complete profile of the supplier from the Pulse Profile system and show the details in a pop-up.
The client is not a partner in Movilitas.Cloud.

In the following example, we are searching for the client "Maine Client USA":

The client is located in the USA.
The client has a GLN so the SGLN field is populated besides the address field.
The tenant acts as a distributor and sends the DSCSA EPCIS files about the shipments to AS2. A previously configured AS2 channel is selected and the AS2 partner of the client is given.
Contact email addresses to perform DSCSA-related tasks are added.
The Pulse logo button is available to fetch the complete profile of the supplier from the Pulse Profile system and show the details in a pop-up.
The client is not a partner in Movilitas.Cloud.

In the following example, we are searching for the client "Montana Client USA":

The client is located in the USA.
The client has a GLN so the SGLN field is populated besides the address field.
The tenant acts as a manufacturer and sends the DSCSA EPCIS files about the shipments to SFTP. A previously configured SFTP channel is selected and the file path is given.
Contact email addresses to perform DSCSA-related tasks are added. A general email address is also added for topics other than DSCSA-related tasks.
The Pulse logo button is available to fetch the complete profile of the supplier from the Pulse Profile system and show the details in a pop-up.
The client is not a partner in Movilitas.Cloud.

Back to the list of procedures

Viewing a Pulse Profile (DSCSA USA Only)

If a client operates in the USA, you can get the complete profile of the client from the Pulse Profile system.

Procedure

1. In the Serialized Logistics application, select Site management --> Clients tab. The application displays the list of clients.

2. Find and select the client.

3. On the Update client panel, click on the Pulse logo button.

Example:

The application fetches the complete profile of the client from the Pulse Profile system and shows the details in a pop-up. However, the displayed information is not a proof of an active license or a license in good standing.

Example:

Back to the list of procedures

Viewing the Orders (Deliveries) of a Client

You can check the orders (deliveries) belonging to a client. You can change between order or delivery view and click on an item in the list to view the corresponding order (delivery) details.

Procedure

1. In the Serialized Logistics application, select Site management --> Clients tab. The application displays the list of clients.

2. Find and select the client in the list for which you want to check the orders (deliveries).

3. Select the Orders tab in the Update client form. The application displays the list of orders belonging to the client.

Example:

4. Change the view in the ID column drop-down:

Order ID
Delivery ID

The application lists the orders or deliveries in a paginated view with the date and time of creation, ID, and status.

The following example illustrates changing the view to delivery:

5. Find the order or delivery in the list and click on it. You are redirected to the order (delivery) page to view the details. For more information, see Managing Outbound Orders.

Back to the list of procedures

Updating a Client

When updating a client, you can modify the master data including the business address (business location) and you can also manage the delivery addresses (facility/storage/ship-to locations).

Providing a delivery address is required when at least one of the following is applicable:

The shipments are sent to a location different from the business address (business location).
A TraceLink collaboration channel is selected and a TraceLink company identifier is provided in the client master data.

After an automatic client creation, you may need to perform some manual actions. The following table summarizes these cases.

Case	Description	Action
Connection to BPOM (Indonesia)	The BPOM (Indonesia) 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.	(Optional) Reorganize the address data after the import.
IDOC Delvry from SAP ICH	After sending an IDOC Delvry to Movilitas.Cloud from SAP ICH or uploading an IDOC Delvry on the SAP ICH channel, the client master data and the delivery address are automatically created in the Serialized Logistics application. The application stores the GLN (location data) both for the client master data and for the delivery address to help the user determine the SGLN format.	(Required) Provide the SGLN (location data) by using the built-in converter: Client master data (always). Client delivery address (only for purchase orders and donations). (Conditional) To fulfill replacement orders for the client in the USA, select the Don't send EPCIS file, create DSCSA letter checkbox. (Optional) To use the delivery address SGLN as the receiver in the outbound DSCSA EPCIS file for the client in the USA, select the Delivery addresses are 3PLs of the Client checkbox. (Conditional) If multiple delivery addresses belong to the same 3PL partner, select the Use different Receiver sGLN for EPCIS checkbox and specify the common receiver SGLN to be used as the receiver in the DSCSA EPCIS in each applicable client delivery address setting. (Conditional) 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, select the Send full EPCIS checkbox.
Manually uploaded IDOC

Case

Description

Action

Connection to BPOM (Indonesia)

The BPOM (Indonesia) 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.

(Optional) Reorganize the address data after the import.

IDOC Delvry from SAP ICH

After sending an IDOC Delvry to Movilitas.Cloud from SAP ICH or uploading an IDOC Delvry on the SAP ICH channel, the client master data and the delivery address are automatically created in the Serialized Logistics application.

The application stores the GLN (location data) both for the client master data and for the delivery address to help the user determine the SGLN format.

(Required) Provide the SGLN (location data) by using the built-in converter:

Client master data (always).
Client delivery address (only for purchase orders and donations).

(Conditional) To fulfill replacement orders for the client in the USA, select the Don't send EPCIS file, create DSCSA letter checkbox.
(Optional) To use the delivery address SGLN as the receiver in the outbound DSCSA EPCIS file for the client in the USA, select the Delivery addresses are 3PLs of the Client checkbox.

(Conditional) If multiple delivery addresses belong to the same 3PL partner, select the Use different Receiver sGLN for EPCIS checkbox and specify the common receiver SGLN to be used as the receiver in the DSCSA EPCIS in each applicable client delivery address setting.

(Conditional) 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, select the Send full EPCIS checkbox.

Manually uploaded IDOC

Procedure

1. In the Serialized Logistics application, select Site management --> Clients tab. The application displays the list of clients.

2. Find and select the client in the list you want to update.

3. On the Master data tab in the Update client form, modify the master data as needed.

Field	Country	Action
Client name	All	Enter the client name. (USA only) If a few characters are entered for a client in the USA market, the application searches the Pulse Profile system and offers hits in a drop-down: Select a value and the application populates the address and country (United States) fields and displays the Pulse logo button at the bottom of the form. The application can overwrite existing client data with the data from the Pulse Profile system. By clicking on the Pulse logo button, the application fetches the complete profile of the client from the Pulse Profile system and shows the details in a pop-up. For more information, see Viewing a Pulse Profile (DSCSA USA Only).
Client ID	All	Enter a unique client ID. The unique ID enables the application to identify the client.
Client does not have a GLN	All	If the client does not have a Global Location Number (GLN), select this checkbox. As a result, the Client SGLN field disappears.
Client SGLN	All	Enter the location number of the client in the SGLN format: <GS1 company prefix>.<location reference>.<extension or "0" when no extension>. For example, "1234567.00012.0". This SGLN is the business, owning party, or sold-to location. The client SGLN is required in the following cases: You send the shipping event to the client in a TraceLink XML file. You send shipment details in an EPCIS 1.2 file. To use the built-in GLN to SGLN converter, click on the conversion button (Help me to define the SGLN) on the right. The application displays a pop-up. Provide the following data and click Convert: Client location in the GLN format (13 digits). If the client is created automatically by receiving an IDOC Delvry file from SAP ICH or uploading an IDOC Delvry file on the SAP ICH channel, you do not need to enter the GLN manually. The application populates this field automatically. Company prefix length (6 to 11 digits or no company prefix). If the company does not have a company prefix, select No company prefix. The question mark (help) icon displays a short message about it after hovering. This is equivalent to a 12-digit long company prefix. Extension digit that is 0 by default. The provided GLN value is converted to the SGLN format and the field is populated.
City	All	Enter the city where the client is located.
Street	All	Enter the street. The form offers three rows (levels) for the street data.
State	All	Enter the state.
ZIP code	All	Enter the postal code.
Select country	All	Select the country. Start entering the country name to filter the countries. For locations imported through a BPOM channel, the field is automatically set to Indonesia and the field is read-only.
Don't send EPCIS file, create DSCSA letter	USA	To fulfill a replacement order, select the checkbox. A DSCSA letter is sent by email instead of a DSCSA EPCIS file to an external system (SAP ICH). The delivery address must be in the USA. To fulfill a purchase order (delivery) or donation, clear the checkbox (default). The DSCSA EPCIS file is sent to an external system (SAP ICH). The DSCSA letter is a PDF document that contains a QR code (link) to a website where the receiver can download the DSCSA EPCIS file. The DSCSA letter parameters (receiver email, sending company name, sending company logo) are configured under the Settings tab. For a client in a country other than the USA, the checkbox is not visible.
Send full EPCIS	Non-USA	Select this checkbox to send a regular EPCIS file to SAP ICH about the shipment to the client. The regular EPCIS file contains the commissioning, aggregation, and shipping events without master data. Only applicable when the following conditions are met: The tenant acts as a 3PL for the supplier. See the Site management --> Suppliers tab. The collaboration channel for the outbound EPCIS file on behalf of the MAH is SAP ICH. See the Site management --> Suppliers tab. The warehouse is in the USA. See the Site management --> Warehouses tab. The client is in a country other than the USA but the delivery address can be in the USA. The following list helps you to define the setting of this checkbox: Client delivery address is in the USA but a regular EPCIS is required --> Select the checkbox. Client delivery address is in the USA and a DSCSA EPCIS is required --> Clear the checkbox. Client delivery address is in a country other than the USA and a regular EPCIS is required --> Select the checkbox. Note: Otherwise, a non-compliant EPCIS is generated that contains the shipping event only. If the client is in the USA, the checkbox is not visible. The application generates a DSCSA EPCIS file that is either sent to SAP ICH (3PL mode) or downloadable (wholesaler mode).
BPOM id	Indonesia	Unless already filled in during the shipping location import, enter the BPOM ID of the client. Only applicable when the selected country is Indonesia. For imported locations, the field is read-only. For locations created on-demand, the field is editable. Note: Make sure that you are using the BPOM ID that is assigned to that location by BPOM. The BPOM ID is important for the sender who wants to ship items to this location because the destination BPOM ID is sent to BPOM during the report.
Collaboration channel - outbound EPCIS DSCSA	USA	Select the collaboration channel to send the DSCSA EPCIS file about the shipment to the external system represented by the channel. Only applicable when the selected country is the United States. Supported channels: LSPediA SAP ICH TraceLink Partner AS2 SFTP The application offers the channels for selection that are configured on the tenant. If an AS2 channel is selected, the application displays the AS2 partner field. If an SFTP channel is selected, the application displays the File path field.
AS2 partner	USA	Select the AS2 partner from the drop-down. The application offers the AS2 service providers onboarded in Movilitas.Cloud. If you cannot find the AS2 partner in the list, contact Movilitas.Cloud Support. Only applicable when the selected country is the United States and an AS2 channel is selected as the collaboration channel for outbound DSCSA EPCIS.
File path	USA	Set the file path on the SFTP server. Follow the help text under the field and do not add "/" at the beginning of the file path. If the file path is not given, the file is saved in the roots folder. If the specified folder does not exist, the folder is automatically created during the first file upload unless a setting on the SFTP server blocks creating the folder. Only applicable when the selected country is the United States and an SFTP channel is selected as the collaboration channel for outbound DSCSA EPCIS.
Client E-mail	All	Enter the general email address of the client.
E-mail address for sending DSCSA EPCIS	USA	Enter the contact email address to send the DSCSA EPCIS file by email. You can send the file under the Transfers --> Outbound External --> Transfers page (Note: Orders are not supported yet). Only active if a collaboration channel for outbound DSCSA EPCIS files is not selected. Once a collaboration channel is selected, the DSCSA EPCIS file is sent over the channel, and sending by email is not active. The field is only available when the country of the client is the United States.
E-mail address for EPCIS exception handling	USA	Enter the contact email address to handle inbound EPCIS exceptions. The field is only available when the country of the client is the United States.
E-mail address for Verifications	USA	Enter the contact email address in case of issues with verifications. The field is only available when the country of the client is the United States.
E-mail address for Trace request	USA	Enter the contact email address to send the TI trace requests. The field is only available when the country of the client is the United States.
Delivery addresses are 3PLs of the Client	USA	If the GLN of the delivery address shall be used as the receiver in the outbound DSCSA EPCIS file, select the checkbox. Otherwise, leave the checkbox cleared (default) and the GLN of the client master data is used as the receiver in the outbound DSCSA EPCIS file. The checkbox is only available when the country of the client is the United States.
Registration type	Kazakhstan	Enter the registration type as specified in the generic report that is sent from SAP ATTP to Movilitas.Cloud. Only applicable when the selected country is Kazakhstan and the generic report from SAP ATTP is an import request to Kazakhstan. Note: When receiving the generic report from SAP ATTP for the first time, the client is auto-created, meaning that the field is auto-filled with the value in the generic report from SAP ATTP.
Registration number	Kazakhstan	Enter the registration number as specified in the generic report that is sent from SAP ATTP to Movilitas.Cloud. Only applicable when the selected country is Kazakhstan and the generic report from SAP ATTP is an import request to Kazakhstan. Note: When receiving the generic report from SAP ATTP for the first time, the client is auto-created, meaning that the field is auto-filled with the value in the generic report from SAP ATTP.
E-mail to send EPCIS Tatmeen file	UAE	Enter the email address where Movilitas.Cloud can send the EPCIS file that was reported to Tatmeen after shipping the order (import permit) to the client. The field is only available when the country of the client is the United Arab Emirates. To send the EPCIS Tatmeen file by email, the following conditions must be fulfilled: The tenant acts as a 3PL for the supplier of the products. A Tatmeen regulatory channel is configured and associated with the supplier. A shipping action to the client is performed in the mobile application.
SFTP channel	UAE	Select a previously configured SFTP channel to send the EPCIS Tatmeen file to the SFTP server. The EPCIS file is reported to Tatmeen and is sent to the SFTP server after shipping the order (import permit) to the client. The field is only available when the country of the client is the United Arab Emirates. To send the EPCIS Tatmeen file to an SFTP server, the following conditions must be fulfilled: The tenant acts as a 3PL for the supplier of the products. A Tatmeen regulatory channel is configured and associated with the supplier. An SFTP channel is configured and associated with the client. A shipping action to the client is performed in the mobile application. To stop sending files to an SFTP server, clear the field by clicking on the X button.
File path	UAE	Once an SFTP channel is selected, set the file path on the SFTP server. Follow the help text under the field and do not add "/" at the beginning of the file path. If the file path is not given, the file is saved in the roots folder. The field is only available after an SFTP channel is selected.
Tracelink collaboration channel	Not country-specific	Select a previously configured TraceLink Partner channel. This setting is required when the tenant (your company) reports the shipping event to the client in TraceLink. The field is only available when your tenant has a TraceLink Partner channel and an SAP ATTP channel in Movilitas.Cloud.
Tracelink company identifier	Not country-specific	Enter the TraceLink company identifier of the client. This setting is required when the tenant (your company) reports the shipping event to the client in TraceLink. The field is only available when your tenant has a TraceLink Partner channel and an SAP ATTP channel in Movilitas.Cloud.

4. Click Save.

5. If applicable, select the Delivery addresses tab and manage the delivery addresses.

Operation on Delivery Address

Description

Add

Click Add Delivery Address, fill in the form as described below, and click Save. The required fields are marked with an asterisk (*) in the form.

Field	Description
Delivery address name	Enter the name of the delivery address, for example, the company name.
Delivery address ID	Enter a unique delivery address ID.
Delivery address SGLN	Enter the location number of the facility in the SGLN format: <GS1 company prefix>.<location reference>.<extension or "0" when no extension>. For example, "1234567.00012.0". This SGLN is the facility, storage, or ship-to location where the shipments are sent. The delivery address SGLN is required in the following cases: You send the shipping event to the client in a TraceLink XML file. You send an EPCIS shipment file. To use the built-in GLN to SGLN converter, click on the conversion button (Help me to define the SGLN) on the right. The application displays a pop-up. Provide the following data and click Convert: Client delivery address location in the GLN format (13 digits). Company prefix length (6 to 11 digits or no company prefix). If the company does not have a company prefix, select No company prefix. The question mark (help) icon displays a short message about it after hovering. This is equivalent to a 12-digit long company prefix. Extension digit that is 0 by default. The provided GLN value is converted to the SGLN format and the field is populated.
Use different Receiver sGLN in EPCIS	If the Delivery addresses are 3PLs of the Client checkbox is selected in the client master data settings, the Use different Receiver sGLN in EPCIS checkbox is displayed in the client delivery address settings. Set the Use different receiver SGLN for EPCIS checkbox as follows: If multiple delivery addresses belong to the same 3PL partner, select the checkbox to use a common SGLN as the receiver in the outbound DSCSA EPCIS file and provide the SGLN in the Receiver SGLN field in each applicable delivery address settings. If one delivery address belongs to the 3PL partner, leave the checkbox in cleared status (default). The given delivery address SGLN is used as the receiver in the outbound DSCSA EPCIS file. Note: Only applicable to the USA and when the tenant acts as a 3PL.
Receiver SGLN	Enter the location number of the common receiver in the SGLN format: <GS1 company prefix>.<location reference>.<extension or "0" when no extension>. For example, "1234567.00012.0". The given common receiver SGLN is used as the receiver in the outbound DSCSA EPCIS file while the delivery address master data and the shipping destination location data still point to the specific delivery address in the file. You can use the built-in GLN to SGLN converter by clicking on the conversion button (Help me to define the SGLN) on the right. For more information on the converter, see the description of the Delivery address SGLN field above. The Receiver SGLN field applies and can be edited if the Use different receiver SGLN for EPCIS checkbox is selected. Note: Only applicable to the USA and when the tenant acts as a 3PL.
City	Enter the city.
Street	Enter the street. The form offers three rows (levels) for the street data.
State	Enter the state.
ZIP code	Enter the postal code.
Select country	Select the country. Start entering the country name to filter the countries. Required in one of the following cases: A TraceLink collaboration channel is set for the client and the shipping event is triggered from SAP ATTP. Shipping to the USA.

Edit

a) Click on the edit icon.

b) Modify the fields in the opened form as described for the Add action.

If the delivery address is created automatically by receiving an IDOC Delvry file from SAP ICH or uploading an IDOC Delvry file on the SAP ICH channel, complete the client delivery address configuration.

For clients placing a purchase order or involved in donations, give the delivery address SGLN:

Use the built-in GLN to SGLN converter (Convert icon in the SGLN field). The application populates the GLN automatically.
Provide the company prefix length and optionally the extension digit, then click Convert. The application converts the GLN to SGLN.

For clients where the client delivery address is a 3PL of the client (like donations) and multiple delivery addresses belong to the same 3PL partner:

Select the Use different receiver SGLN in EPCIS checkbox.
Provide the receiver SGLN in the Receiver SGLN field by using the built-in GLN to SGLN converter.

c) Click Save.

The following example illustrates the case when the client delivery address is a 3PL of the client and the common receiver SGLN is specified because the 3PL partner has multiple delivery addresses: