SFDA is the regulatory system that supports the track and trace legislation to the pharmaceutical industry in Saudi Arabia. The SFDA channel enables the tenant to connect to SFDA RSD.


Currently, the SFDA channel can be used in the following application:

  • Serialized Logistics


List of Procedures


For more information on the general channel actions, see Managing Channels for a Tenant (Overview).


Configuring an SFDA Channel


Before You Begin


Make sure that a user is onboarded in SFDA RSD and owns the credentials:

  • Username
  • Password


The Marketing Authorization Holder (MAH) can onboard the user in SFDA RSD for you.


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, select the Channels tab. The application displays the list of channels assigned to the tenant.



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


#Create a ChannelModify an Existing Channel
4.1Click the + icon (Create channel). The application displays the Create channel dialog.

To search for an SFDA channel, use the search criteria field and the filters:

  • Enter the channel name in the search criteria field.
  • Select the status.
  • Select SFDA as the source.
  • Select Regulatory channel as the type.
4.2Select Regulatory 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.		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 with the current channel settings.
4.3Enter a name for the channel and select SFDA as the source.N/A
4.4

Click Create Channel.


The application informs you about the 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.

N/A


Example when creating an SFDA channel:



5. Provide the SFDA channel settings as explained in the table below.


Function/ParameterAction
UsernameEnter your username in SFDA RSD.
PasswordEnter the password belonging to your username in SFDA RSD.
Support e-mailEnter the email address where Movilitas.Cloud can send notifications about errors (warnings or failures) on the channel.


6. Click Save Settings.


7. Check the connection status at the top of the SFDA settings form. Click on the status to refresh it.


If the status message is Connected to SFDA, the connection is successfully established.


8. (Optional) If needed, change the name of the channel and click Save Channel.


Back to the list of procedures



Monitoring SFDA Messages


You can view the messages sent to SFDA RSD from Movilitas.Cloud with their status.


The following message types are supported:

  • Dispatch - An XML file in a SOAP envelope that describes the lowest level of trade items that are shipped within Saudi Arabia. The aggregation data (if any) is not included. The response from SFDA RSD contains the notification ID, the product list, and the response code (success or an error) for each product.
  • Export - An XML file in a SOAP envelope that describes the lowest level of trade items that are shipped from Saudi Arabia to another country. The aggregation data (if any) is not included. The response from SFDA RSD contains the notification ID, the product list, and the response code (success or an error) for each product.
  • Dispatch Cancel - An XML file in a SOAP envelope that describes the lowest level of trade items that are received from the client as a return. The aggregation data (if any) is not included. The client is in Saudi Arabia. The response from SFDA RSD contains the notification ID, the product list, and the response code (success or an error) for each product.
  • Export Cancel - An XML file in a SOAP envelope that describes the lowest level of trade items that are received from the client as a return. The aggregation data (if any) is not included. The client is in a country other than Saudi Arabia. The response from SFDA RSD contains the notification ID, the product list, and the response code (success or an error) for each product.
  • Package Upload - An EPCIS file in a SOAP envelope that describes the complete shipment including master data, sender/receiver, and events. The EPCIS file is uploaded to SFDA RSD as a ZIP file. The response from SFDA RSD contains the transfer ID. Only applicable to the case when shipping within Saudi Arabia (Dispatch).


Shipping to the client in the Serialized Logistics mobile application triggers the following requests:

  • Shipping within Saudi Arabia:
    • Dispatch
    • Package Upload
  • Shipping from Saudi Arabia to another country:
    • Export


Receiving a return from the client in the Serialized Logistics mobile application triggers one of the following requests:

  • Dispatch Cancel - When the client is in Saudi Arabia.
  • Export Cancel - When the client is in a country other than Saudi Arabia.


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, select the Channels tab. The application displays the list of channels assigned to the tenant.

4. Find the SFDA channel. Use the search field and the filters:

  • Enter the channel name in the search field.
  • Select the status.
  • Select SFDA as the source.
  • Select Regulatory channel as the type.


5. To view the SFDA channel information, click on the channel name or the edit icon (Edit channel) next to the channel. The application displays the SFDA settings and Documents panels.


Example:



6. View the messages under the Messages tab on the Documents panel.


7. Find a message by entering a purchase order ID, data from the request, or data from the response in the search field.

  • For search expression from the request or the response, for example, give the notification ID, transfer ID, correlation ID, batch, or serial number.
  • The messages are filtered based on the search criteria.


IMPORTANT: Searching may not be effective and may not give a result on large messages:

  • If both the request and the response are large, the message is not included in search results because the content is not searchable.
  • If the request or the response is searchable (content preview is available in the log), searching can be effective and give a result depending on the search expression.


8. To view the message details, expand the message by clicking > (Expand).


For the messages, the following parameters and functions are displayed:


Parameter/FunctionDescription
> (Expand) icon

You can view the details of the message.


After expanding the log, you can download the request in the XML part by using the download icon next to the content.


For a "Package Upload" message that contains a large EPCIS file, the application does not display the EPCIS content in the XML part but you can download the EPCIS file.

Status

Status of the message:

  • Pending (Circular arrows icon) - Processing the message is in progress.
  • Success (Checkmark icon) - SFDA RSD returned a positive response (no error).
  • Warning (Yellow exclamation mark) - SFDA RSD returned one or more errors in the response but provided a notification ID or transaction ID depending on the request type. The notification ID can be a fixed “0”. The message needs attention.
  • Failed (Red exclamation mark) - Either it was not possible to send the message to SFDA RSD due to an issue at SFDA RSD or SFDA RSD returned one or more errors in the response but did not provide a notification ID or transaction ID. The message needs attention.
Request type

The following request types are displayed on the Messages tab:

  • Dispatch
  • Export
  • Dispatch Cancel
  • Export Cancel
  • Package Upload
Sent DatetimeThe timestamp when the message was sent to SFDA RSD.
Sender GLNThe GLN of the sending entity.
Receiver GLNThe GLN of the receiving entity.
Notification IDSFDA RSD returns the notification ID for the following requests:
  • Dispatch
  • Export
  • Dispatch Cancel
  • Export Cancel 
Transfer IDSFDA RSD returns the transfer ID for the "Package Upload" message.
MD5 ChecksumA 32-character hexadecimal number that is computed on a file for data integrity purposes.

Note: For successful "Package Upload" messages only.
Correlation IDSFDA RSD returns the correlation ID for the following requests:
  • Dispatch
  • Export
  • Dispatch Cancel
  • Export Cancel
  • Package Upload


When the shipping action generates two requests (Dispatch & Package Upload), both requests receive the same correlation ID.

XMLThis is the request that is sent to SFDA RSD.

For "Package Upload", if the EPCIS file is large, the application displays the Download EPCIS file button but does not display the content. It is not possible to search for this request and the message may not be included in the search results.
Last responseThis is the last response from SFDA RSD. Because the same message can be resent in case of an error, the application displays only the last response from SFDA RSD.

If the response from SFDA RSD is large, the application displays the Download response file button but does not display the Last response section. It is not possible to search for this response and the message may not be included in the search results.
Errors column

Error message in the expanded log		A summary of the errors from SFDA RSD (if any). Applicable to message status Warning or Failed.
Error ListWhen applicable, each error is listed and described in a paginated view:
  • Product code.
  • Batch.
  • Expiration date.
  • Serial number.
  • Error message that explains the error.


Note: The error list does not apply to all errors.

Resent (Column)If the message is resent, the application displays the Resent message indicator. Otherwise, the field is blank.
Resend button (Circular arrows icon)If SFDA RSD returns an error message or sending the message fails due to an issue at SFDA RSD, the application displays the Resend button in the Action column to resend the message. Applicable to message status Warning or Failed.

If a message is resent, the application displays the Resent message indicator in the Resent column.

Resending does not create a new log but the existing log is updated as per the last response from SFDA RSD.

IMPORTANT:
  • Before resending a message, identify the root cause. If the issue is in SFDA RSD, make sure that the settings in SFDA RSD are correct, and then resend the message. Resending applies only after the error is resolved on the SFDA RSD side.
  • Errors due to misconfigurations in Movilitas.Cloud cannot be resolved by resending the message that holds an improper configuration. In this case, contact Movilitas.Cloud Support.


The following example illustrates a successful "Dispatch" message:

  • The user can view both the request (XML) and the last response content. The user can download the request (XML).
  • The response contains the notification ID that is also explicitly displayed in the general data part.



The following example illustrates a successful "Dispatch" message:

  • The user can view the request (XML). The user can download the request (XML).
  • The response is a large file so the user can only download the file but cannot view the response.



The following example illustrates a successful "Package Upload" message:

  • The request (XML) is not a large EPCIS file so the user can view the file content. The user can download the request (XML).
  • The response from SFDA contains the transfer ID that is also explicitly displayed in the general data part.


 

The following example illustrates a successful "Package Upload" message:

  • The request (XML) is a large EPCIS file so the user can only download the EPCIS file but cannot view the file content.
  • The response from SFDA contains the transfer ID that is also explicitly displayed in the general data part.



The following example illustrates the case when the "Dispatch Cancel" message has warnings and it needs attention:

  • The user can view both the request (XML) and the last response content. The user can download the request (XML).
  • The SFDA returns with errors, however, a notification ID is also provided. The response contains the notification ID that is also explicitly displayed in the general data part.
  • The Errors column and the Error message field show a summary of the errors.
  • The Error List section lists each trade item that has an error. The user can view the product details and the error message from SFDA RSD.
    • In this example, the product is not registered.
    • The message is not resent (no indicator).
    • After the SFDA RSD configuration is updated, the user can resend.



The following example illustrates the case when the "Package Upload" message failed and needs attention:

  • The request (XML) is a large EPCIS file so the user can only download the EPCIS file but cannot view the file content.
  • The response from SFDA contains an error. The Errors column and the Error message field show the meaning of the error.
    • In this example, the destination information is invalid (unknown).
    • The message is not resent (no indicator).
    • After the SFDA RSD configuration is updated, the user can resend.



The following example illustrates the case when the "Dispatch" message failed and needs attention:

  • The user can view both the request (XML) and the last response content. The user can download the request (XML).
  • The response from SFDA contains an error. The Errors column and the Error message field show the meaning of the error.
    • In this example, the receiver stakeholder is passive.
    • The message is not resent (no indicator).
    • After the receiver stakeholder status is resolved, the user can resend.



Back to the list of procedures