Use the Serialized Logistics mobile application to ship or return products.


You can do internal shipping or internal return to another warehouse of your company or do external shipping to a client.


Shipping TypeInternal or External?Return Possible?Description
By batchInternalNo

You can scan one pack to get a list of all the packs that belong to the same batch and ship them together. Only applicable if your warehouse is involved in manufacturing.

By stock transfer IDInternalYes*You can group products with a stock transfer ID (STID) and ship or return them together. By default, internal returns are not allowed. 
By purchase order IDExternalNoYou can create a transfer or execute an order. Both the transfer and the order take a purchase order ID (POID).

(Transfers only) When picking is enforced before shipping, you can only confirm the picked items and submit them for shipping.

*When internal returns are allowed.


Reporting the Shipment to an External System


The shipment is reported to the applicable external system through the channel configured for the warehouse (BPOM, SFDA RSD, or SAP ICH), through the channel configured for the supplier (Tatmeen UAE or SAP ICH), or through the channel configured for the client in the USA (AS2).


Reporting to an external system is driven by your business use case. Consult your use case description and identify the type of shipping event that must be reported to the external system. For more information, see Serialized Logistics Workflows.


If the channel setting is not configured, the shipment is recorded in Movilitas.Cloud only.


Verification against the NMVS (FMD Europe)


If an Arvato regulatory channel is set and the FMD verification on outbound checkbox is selected for the warehouse, each scanned pack is verified against the NMVS while shipping to a client.

  • If the item is valid (commissioned) but there is a warning from the NMVS, the application displays the warning message from the NMVS also. The warning does not block you from shipping the item.
  • If the pack is decommissioned or there is an issue with the pack, the pack is not added to the list in the mobile application and that pack cannot be shipped.


The shipment is not reported to the NMVS because shipping is a business-related activity not covered by the regulations.


Exporting Packs to a Non-FMD Country with Report to the NMVS (FMD Europe)


When the following conditions are met, the status of the items is set to Exported in the NMVS after submitting the items for shipping:

  • An Arvato regulatory channel is set for the warehouse.
  • The FMD verification on outbound checkbox is selected for the warehouse.
  • The client is not in an FMD country (outside EU).


The shipment is not reported to the NMVS because shipping is a business-related activity not covered by the regulations.


Commissioning while Shipping


For manufacturer sites, it is possible to commission the items while shipping hence performing multiple actions at the same time. As a prerequisite, the items must be created in Movilitas.Cloud through serialization activities in the Serialized Manufacturing application. The serialization activity is label printing or registering items in Movilitas.Cloud over the Manufacturer V2 API.

  • The commissioning while shipping can be activated or deactivated at the warehouse level.
  • The setting does not bring extra UI functions for the user in the mobile application but Movilitas.Cloud executes additional tasks and reports in the background.


Auto-unpack during Shipping


If the items to be shipped are aggregated and the hierarchy is known in Movilitas.Cloud, the application can unpack them automatically while shipping them to a client, and a manual unpack action is not required from the user.

  • The feature applies to outbound external orders only.
  • The setting can be activated or deactivated at the warehouse level.
  • The scope of the unpack can be also extended to dissolve parent container(s) (SSCCs).
  • The setting does not bring extra UI functions for the user in the mobile application but Movilitas.Cloud executes additional tasks in the background. For more information on the unpacking logic, see Unpack Products in Serialized Logistics (Mobile).


Note: The procedures described below take the use case when the operator scans the items by using the camera of the mobile device.

  • For mobile devices with built-in scanners, the GUI buttons related to scanning, like Scan Item, may not be displayed and you need to press the physical button on the device to scan.
  • For devices with external (table) scanners, you can point the scanner to the barcode to scan and you can ignore the GUI buttons on the screen related to scanning.


List of Procedures


Ship by Batch to a Warehouse (Internal)


Before You Begin


Make sure that the administrator has assigned you as an operator in the Serialized Logistics application and authorized you to ship products in the specified warehouse.


Procedure


1. Open the Serialized Logistics application in Movilitas Mobile.


2. Select Ship.


3. Select Internal.


4. Under Ship to drop-down, select a shipping destination. The application offers the list of warehouses registered in the Serialized Logistics application except for the warehouse where you are assigned.


5. Select Ship By Batch.


6. Select Scan Item and scan an item from the shipment. The application collects all the items with the same batch that are ready for shipping.


7. Select Ship. The application displays the result of the action. 

  • A transfer is created with the details in Movilitas.Cloud. You can check it by going to the Serialized Logistics application --> Transfers --> Outbound internal --> Ship by batch page.
  • If a BPOM regulatory channel is configured for the warehouse, the event is reported to BPOM.
  • Once an item is shipped, it is not in possession and it is not possible to perform an action on it until the item is received.


Back to the list of procedures



Ship by Stock Transfer ID to a Warehouse (Internal)


Before You Begin


Make sure that the administrator has assigned you as an operator in the Serialized Logistics application and authorized you to ship products in the specified warehouse.


Procedure


1. Open the Serialized Logistics application in Movilitas Mobile.


2. Select Ship.


3. Select Internal.


4. Leave the Return toggle button OFF.


Note: The button is visible only when internal returns are allowed for the warehouse.


5. Under Ship to drop-down, select a shipping destination. The application offers the list of warehouses registered in the Serialized Logistics application where you are allowed to ship.


6. Select Ship by Stock Transfer ID.


7. Scan the STID or enter it manually.


8. Tap Confirm.


9. Select Scan Item and scan the items one by one. The application displays the scanned items.

  • To view the details of an item or remove an item, slide the item to the left and select Preview or Remove.
  • If the scanned item is aggregated (packed), the application displays a pop-up message to confirm that you want to unpack the item. If not, the item is removed from the list.


10. When you finished scanning, select Ship.

  • The application displays the result of the action. A transfer is created with the details in Movilitas.Cloud. You can check it by going to the Serialized Logistics application --> Transfers --> Outbound internal --> Ship by stock transfer ID page.
  • If a BPOM regulatory channel is configured for the warehouse, the event is reported to BPOM.
  • Once an item is shipped, it is not in possession and it is not possible to perform an action on it until the item is received.


Back to the list of procedures



Return by Stock Transfer ID to a Warehouse (Internal)


You can return items to the sender by providing the reason for the return. You can provide only one reason at one time for the return so scan only the items where the reason for the return is the same.


Note: Applicable when internal returns are allowed at the warehouse level. Before performing any internal return, make sure that your business use case supports this action.


Before You Begin


Make sure that the administrator has assigned you as an operator in the Serialized Logistics application and authorized you to ship products in the specified warehouse.


Procedure


1. Open the Serialized Logistics application in Movilitas Mobile.


2. Select Ship.


3. Select Internal.


4. Turn the Return toggle button ON.


5. Under Ship to drop-down, select a return destination. The application offers the list of warehouses registered in the Serialized Logistics application where you are allowed to return.


6. Select Ship by Stock Transfer ID.


7. Scan the STID or enter it manually.


8. Tap Confirm.


9. Select Scan Item and scan the items one by one. The application displays the scanned items.

  • Make sure that all the scanned items will be returned for the same reason. You can return items for one reason at one time.
  • To view the details of an item or remove an item, slide the item to the left and select Preview or Remove, respectively.


10. Enter the reason for the return in the Reason field. After the reason is entered, the Ship button becomes active.


11. When you finished scanning and entered the reason, select Ship.

  • The application displays the result of the action. A transfer is created with the details in Movilitas.Cloud. You can check it by going to the Serialized Logistics application --> Transfers --> Outbound internal --> Ship by stock transfer ID page.
  • Once an item is returned, it is not in possession and it is not possible to perform an action on it.


Back to the list of procedures



Ship Items by Purchase Order ID to a Client (External) - Transfer Only


You want to ship items to a client in a transfer that was not registered as an order in Movilitas.Cloud. The activity in the warehouse is recorded but is not controlled in Movilitas.Cloud.


Choose this method when the orders are not created in Movilitas.Cloud and you want to create only a transfer in Movilitas.Cloud. This is fully driven by the business use case in place at your company.


For the following scenarios, you must follow this procedure:

  • Connecting to BPOM (Indonesia)
  • Connecting to Tatmeen (UAE)
  • Connecting to SFDA RSD (Saudi Arabia)
  • Shipping to Bahrain
  • Shipping to China with connection to SAP ICH
  • Shipping to the USA as a manufacturer or distributor.


For the following scenario, you can select this procedure:

  • Connecting to NMVS (Arvato)


To create a transfer, the items must be known in Movilitas.Cloud or an NMVS connection is required. Even if the application setting allows shipping unknown items, this mobile action is agnostic of the setting.


The naming convention for the transfer identifier (see purchase order ID) may not reflect the business processes in place at your company. The identifier may be called differently at your company. For example, transaction or import permit number.


Picking can be enforced before shipping. Picking limits the available actions for shipping. You can enforce picking at the warehouse level and this setting follows the business processes of your company.


The following table summarizes the possible setups.


ScenarioAvailable Actions
Picking is not enforcedYou can create a purchase order by ID, scan items, and ship the items.

You can search for an existing purchase order that was created while picking and you can execute the shipping.
Picking is enforcedYou can search for an existing purchase order that was created while picking and you can execute the shipping.


Before You Begin


Make sure that the administrator has assigned you as an operator in the Serialized Logistics application and authorized you to ship products in the specified warehouse.


Procedure


1. Open the Serialized Logistics application in Movilitas Mobile.


2. Select Ship.


3. Select External.


4. Under Ship to drop-down, select a shipping destination (client).

  • The application offers the list of clients registered in the Serialized Logistics application. After opening the drop-down, you can search for a client by using the search field.
  • Once the client is selected and two or more delivery addresses are registered for this client, the application displays another pop-up to select the delivery address. Otherwise, the delivery address is auto-selected (one delivery address) or only the client master data address is taken into account (no delivery address).
  • Orders that were created while picking and that belong to the selected client are listed.

 

5. Perform one of the following procedures.


#Shipping On-Demand*Shipping a Pick List
5.1

Scan the purchase order ID or enter it manually.


TIP: Follow your business processes when providing the purchase order ID. The identifier may be called differently based on the business processes. For example, transaction or import permit number.

Find the pick list by entering the purchase order ID in the search field.

TIP: Follow your business processes when providing the purchase order ID. The identifier may be called differently based on the business processes. For example, transaction or import permit number.

5.2
Tap Create Transfer. The application displays the External screen where you can scan the items.Select the pick list (order). The application displays the Ship picked items screen listing the picked items.
5.3

Select Scan Item and scan the items one by one. The application displays the scanned items.

  • To view the details of an item or remove an item, slide the item to the left and select Preview or Remove, respectively.
  • (FMD Europe only) If an Arvato regulatory channel is set and the FMD verification on outbound checkbox is selected for the warehouse:
    • The packs are verified against the NMVS.
    • If the item is valid (commissioned) but there is a warning from the NMVS, the application displays a yellow exclamation mark icon and a warning message from the NMVS. The warning does not block you from shipping the item.
    • If the item is decommissioned or there is an issue with the item, the application displays an appropriate message and stops the scanning process so that you can put the item away.
    • When an alert is raised, the application informs the user about it.
    • The item that is decommissioned or that has issues is not added to the list and it cannot be shipped.
    • It is not possible to scan a container (SSCC).
Confirm the picked items.

*This procedure is applicable when picking is not part of the business processes at your company or when picking is optional but was skipped.


6. When you finished scanning or confirming the picked items, select Ship. The application displays the result of the action.


The following table summarizes the system actions based on the business case or connection.


Business case/ConnectionSystem Action
GeneralA transfer is created with the details in Movilitas.Cloud. You can check it by going to the Serialized Logistics application --> Transfers --> Outbound external --> Transfers page.

Once an item is shipped, it is not in possession and it is not possible to perform an action on it until the item is received.

SAP ICH
BPOM (Indonesia)

The commissioning event (manufacturers only) and the shipping event are reported to the applicable external system through the channel configured for the warehouse.

Shipping to Bahrain*The system enables you to download the EPCIS 1.2 file and send the EPCIS 1.2 file to the supplier (MAH) by going to the Serialized Logistics application --> Transfers --> Outbound external --> Transfers page.
Shipping to the USA**The system enables you to download the EPCIS 1.2 file by going to the Serialized Logistics application --> Transfers --> Outbound external --> Transfers page.

If the client is a partner in Movilitas.Cloud, the client automatically receives the EPCIS file. Otherwise, you need to send the EPCIS file outside Movilitas.Cloud.

If an AS2 channel is associated with the client and the AS2 ID of the client is given, the EPCIS file is sent to AS2 through the AS2 channel.
Shipping to the UAE*An EPCIS 1.2 file (manufacturing report) is sent to Tatmeen on behalf of the supplier (MAH). A log about the message is created on the Tatmeen regulatory channel associated with the supplier (MAH).

If the shipment contains more than 50,000 items, the system splits the shipment into multiple EPCIS 1.2 files (messages). Each file describes a top-level parent and its hierarchy. If a top-level parent contains 50,000 or more items, it is not possible to ship any item from the shipment and the mobile application displays the following error message: Limit Exceeded! Number of items being shipped exceeds the allowed shipping limit toward Tatmeen.

The limit of 50,000 items per EPCIS file comes from Tatmeen. Movilitas.Cloud applies the limit to comply with the requirements in Tatmeen.

Shipping a large number of items might take some time and can lead to a timeout in the mobile application. Do not ship the items again because the transfer and the EPCIS message to Tatmeen are being created in the background. If an issue occurs with the shipment, a notification email is sent to the email address given on the Tatmeen regulatory channel.
Shipping within Saudi Arabia*The following messages are sent to SFDA RSD:
  • Dispatch - An XML file in a SOAP envelope that describes the lowest level of trade items that are shipped within Saudi Arabia.
  • Package Upload - An EPCIS file that describes the complete shipment including master data, sender/receiver, and events. The EPCIS file is uploaded to SFDA RSD as a ZIP file.
A separate log is created per message on the SFDA regulatory channel associated with the warehouse of the operator.
Shipping from Saudi Arabia to another country*The following message is sent to SFDA RSD:
  • 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.


A log is created per message on the SFDA regulatory channel associated with the warehouse of the operator.

NMVS (Arvato)If the client is located in a non-FMD country (outside Europe), the packs are exported and their status is set to Exported in the NMVS after submitting the shipping.
  • If the product is known in the NMVS, a bulk transaction is performed towards the NMVS.
    • The transaction details are available under the Reports & Analysis application > FMD > Bulk responses tab.
    • If the bulk transaction fails, Movilitas.Cloud sends an email to all administrators of the tenant, and optionally, to the operator, depending on the operator's settings.
  • If the product is not known in the NMVS (multi-country pack), an inter-market call is triggered. A single transaction is performed per pack towards the NMVS. The transactions are forwarded to the other, fulfilling NMVS through the EU Hub. 
    • Once all transactions are processed, the application collects the errors (if any) and sends a summary email about the errors to all administrators of the tenant and to the operator who performed the action.
    • The details of each transaction are available under the Reports & Analysis application > FMD > Scans tab.

*The transfer is a 3PL activity on behalf of a supplier that is the Marketing Authorization Holder (MAH) of the shipped items.

**The transfer is made by a manufacturer or a distributor that sells products to its clients.


Back to the list of procedures



Ship Items by Purchase Order ID to a Client (External) - Order


You execute an outbound external order that was created in Movilitas.Cloud in advance. The activity in the warehouse is controlled and recorded in Movilitas.Cloud.


You ship the delivery associated with the order:

  • You scan the items for the line items.
  • For non-serialized items, you provide the amount.


Choose this method when the orders are created in Movilitas.Cloud. This is fully driven by the business use case in place at your company.


For the following scenario, you can select this procedure:

  • Connection to NMVS (Arvato).
  • Acting as 3PL for the suppliers and shipping to the USA with a connection to SAP ICH.


IMPORTANT: To ship items in the mobile application, the order can contain one delivery only. When shipping in the mobile application, multiple deliveries are not supported.


Before You Begin


Make sure that the administrator has assigned you as an operator in the Serialized Logistics application and authorized you to ship products in the specified warehouse.


Procedure


1. Open the Serialized Logistics application in Movilitas Mobile.


2. Select Ship.


3. Select External.

  • The application displays the list of outbound external orders (and picked transfers), a search field, and a drop-down to select a client and filter the orders based on the supplier.
  • Only the orders in Open, In shipping, or Paused shipping status are listed.
  • If the order is assigned to an operator and the order is in progress, only that operator can see that order in the list.

4. Under Ship to drop-down, select a shipping destination (client).

  • The application offers the list of clients registered in the Serialized Logistics application. After opening the drop-down, you can search for a client by using the search field.
  • Once the client is selected and two or more delivery addresses are registered for this client, the application displays another pop-up to select the delivery address. Otherwise, the delivery address is auto-selected (one delivery address) or only the client master data address is taken into account (no delivery address).
  • The orders are filtered and only the orders that belong to the selected client are listed.


5. Find the order by entering the order ID in the search field or by scanning the order ID. The application filters the list of orders based on the search criteria.


6. Select the order. The application displays the order ID, the delivery ID, and the line items of the order.


7. Select one of the following methods to ship items.


MethodAction
Free ScanningSelect the Free Scanning button. By using this option, you can scan items belonging to different line items at once. You can scan both trade items (SGTINs) and containers (SSCCs).

Use this method in the following cases:
  • Scanning a container (SSCC).
  • You don't know which line item contains the items that you need to scan or it would be time-consuming to find and select the line item before scanning. The items next to each other may belong to multiple line items (products are heavily mixed in the delivery).
Note: If an unlimited delivery is not allowed for the order, the Free Scanning option is not available.
Scanning for a Line Item

Select a line item.


The application displays the line item details and you can scan the serialized items for that line item.


You can scan only trade items (SGTINs). It is not allowed to scan a container (SSCC).

Entering the Amount for Non-Serialized Items

Select a line item.


The application displays the line item details and you can enter the amount for non-serialized items.


8. Perform one of the following procedures.


Free ScanningScanning for a Line ItemEntering the Amount for Non-Serialized Items
Select Scan Item and scan the items one by one.


The application displays the scanned item in the list and updates the scanned quantity.

  • To view the details of the scanned item or remove the scanned item, slide the item to the left and select Preview or Remove.
  • If an item is already involved in a shipping activity, it is not possible to add it to the list.
  • (FMD Europe only) If an Arvato regulatory channel is set and the FMD verification on outbound checkbox is selected for the warehouse, the scanned item is verified against the NMVS.
    • If the item is valid (commissioned) but there is a warning from the NMVS, the application displays the warning message from the NMVS also. The warning does not block you from shipping the item.
    • If the item is decommissioned or there is an issue with the item, the application displays a red icon with an appropriate message and stops the scanning process so that you can put the item away.
    • When an alert is raised, the application informs the user about it.
    • To continue scanning, remove the item that is highlighted in red.
    • It is not possible to scan a container (SSCC).
  • Each scanned item is automatically linked to the related line item.
    • If the scanned container (SSCC) or parent trade item is known, the application goes down to the trade item level that has the product code of the line item and links those trade items to the line item. All trade items are automatically organized into the relevant line item.
    • If there is a trade item below the scanned container (SSCC) that does not match any line item, the application displays an error message and does not add anything from the container (SSCC).
    • If the scanned trade item or any of its children does not match any line item, the application displays an error message and does not allow scanning until the user removes the trade item that causes the issue.
    • If the scanned container or trade item is unknown and shipping unknown items is forbidden in the application settings, the application displays an error message. The application does not allow scanning until the user removes the item that causes the issue. Otherwise, the scanned item is added to the list.
  • If auto-unpack during shipping is activated at the warehouse level, the scanned item has a parent, and the hierarchy is known in Movilitas.Cloud, the application unpacks the item in the background. All parent trade items are dissolved in the hierarchy and optionally, the parent container(s) (SSCCs) can be also dissolved. These actions are performed on Movilitas.Cloud database only and the event is not sent to an external system.
  • If auto-unpack during shipping is not activated at the warehouse level and the scanned item has a parent, the application displays a red icon with an appropriate message and stops the scanning process until the item is removed from the list.
  • When you finished scanning the items, you can complete all the line items at once by selecting Complete on the Free scanning page. However, you can also complete the line items when shipping the order.
  • In the line item view, you can verify the assigned trade items and the parent container(s) (SSCC(s)) with hierarchy (if any). Go back to the Line items page and select the line item for the details.
    • Result of a scanned container (SSCC) - The application displays the top-level trade item but the quantity reflects the number of trade items having the product code of the line item.
    • Result of a scanned trade item - The application displays the scanned item but the quantity reflects the number of trade items having the product code of the line item.
  • You can return to free scanning even after all line items are completed until you ship the order.
  • You can pause shipping the order by selecting Pause on the Line items page which displays the order ID, the delivery ID, and the list of line items.

Select Scan Item and scan the items one by one.


The application displays the scanned item in the list and updates the scanned / expected quantity.

  • To view the details of the scanned item or remove the scanned item, slide the item to the left and select Preview or Remove.
  • If an item is already involved in a shipping activity, it is not possible to add it to the list.
  • (FMD Europe only) If an Arvato regulatory channel is set and the FMD verification on outbound checkbox is selected for the warehouse, the scanned item is verified against the NMVS.
    • If the item is valid (commissioned) but there is a warning from the NMVS, the application displays a yellow exclamation mark icon with a warning message from the NMVS. The warning does not block you from shipping the item.
    • If the item is decommissioned or there is an issue with the item, the application displays a red icon with an appropriate message and stops the scanning process so that you can put the item away.
    • When an alert is raised, the application informs the user about it.
    • To continue scanning, remove the item that is highlighted in red.
    • It is not possible to scan a container (SSCC).
  • If the scanned parent trade item is known, the application goes down to the trade item level that has the product code of the line item and links those trade items to the line item. The quantity reflects the number of trade items having the product code of the line item. However, the application displays the scanned trade item in the list.
    • If the scanned trade item or any of its children does not match the selected line item, the application displays an error message and does not allow scanning until the user removes the trade item that causes the issue.
    • If the scanned trade item is unknown and shipping unknown items is forbidden in the application settings, the application displays an error message. The application does not allow scanning until the user removes the item that causes the issue. Otherwise, the scanned item is added to the list.
  • If auto-unpack during shipping is activated at the warehouse level, the scanned item has a parent, and the hierarchy is known in Movilitas.Cloud, the application unpacks the item in the background. All parent trade items are dissolved in the hierarchy and optionally, the parent container(s) (SSCCs) can be also dissolved. These actions are performed on Movilitas.Cloud database only and the event is not sent to an external system.
  • If auto-unpack during shipping is not activated at the warehouse level and the scanned item has a parent, the application displays a red icon with an appropriate message and stops the scanning process until the item is removed from the list.
  • When you finished scanning the items, you can complete the line item by selecting Complete on the Line item page. However, you can also complete the line item when shipping the order.
  • If an unlimited delivery is not allowed for the order, the application informs you when you underdeliver or overdeliver considering the target quantity. The tolerance values are controlled at the order level in the Admin UI. Make sure that you keep the limits while shipping.
  • You can return to a completed line item and continue the operation until you ship the order. If an unlimited delivery is not allowed for the order, you need to keep the limits (tolerance values) specified at the order level in the Admin UI.
  • You can pause shipping the order by selecting Pause on the Line items page which displays the order ID, the delivery ID, and the list of line items.
Select Non-Serialized, enter the amount of the non-serialized items in the pop-up window, and select Assign Amount.

If there is a number in brackets on the Non-Serialized button, a quantity is already given. For example, Non-Serialized (8). By default, the application offers the target quantity to be assigned.
  • To update the entered quantity, select Non-Serialized, enter the new value, and select Update Amount.
  • To remove the entered quantity, select Non-Serialized, enter 0, and select Update Amount.
  • You can pause shipping the order by selecting Pause on the Line items page which displays the order ID, the delivery ID, and the list of line items.
  • When you finished entering the amount, you can complete the line item by selecting Complete on the Line item page. However, you can also complete the line item when shipping the order.
  • You can return to a completed line item and continue the operation until you ship the order. If an unlimited delivery is not allowed for the order, you need to keep the limits (tolerance values) specified at the order level in the Admin UI.


9. Ship the delivery for the order by selecting Ship on the Line items page.

  • If not all the line items are completed, the application asks you to confirm shipping the order and completing all the line items. To ship the delivery (and the order), all line items must be completed, even if a line item does not have any scanned or entered items. After clicking Yes, all line items are completed and the delivery (together with the order) is shipped.
  • When shipping is successful, the application displays a status message. The order with the delivery ID is shipped. You cannot scan more items or enter further amounts for the shipped delivery.


The following table summarizes the system actions based on the business case or connection:


Business case/ConnectionSystem Action
GeneralA transfer is created with the details in Movilitas.Cloud. You can check it by going to the Serialized Logistics application --> Transfers --> Outbound external --> Orders page.

Once an item is shipped, it is not in possession and it is not possible to perform an action on it until the item is received.

Shipping to the USA with connection to SAP ICH*

An EPCIS file is generated and sent through the SAP ICH channel that is configured for the supplier. The event is recorded as a DSCSA shipping event on the SAP ICH channel.

NMVS (Arvato)If the client is located in a non-FMD country (outside Europe), the packs are exported and their status is set to Exported in the NMVS after submitting the shipping.
  • If the product is known in the NMVS, a bulk transaction is performed towards the NMVS.
    • The transaction details are available under the Reports & Analysis application > FMD > Bulk responses tab.
    • If the bulk transaction fails, Movilitas.Cloud sends an email to all administrators of the tenant, and optionally, to the operator, depending on the operator's settings.
  • If the product is not known in the NMVS (multi-country pack), an inter-market call is triggered. A single transaction is performed per pack towards the NMVS. The transactions are forwarded to the other, fulfilling NMVS through the EU Hub. 
    • Once all transactions are processed, the application collects the errors (if any) and sends a summary email about the errors to all administrators of the tenant and to the operator who performed the action.
    • The details of each transaction are available under the Reports & Analysis application > FMD > Scans tab.

*The shipping is a 3PL activity on behalf of the supplier of the products.


Back to the list of procedures