The Check Quality screen in the Repacker FMD desktop application enables the quality personnel to supervise the activities and take the necessary action in case of issues.


After each step in the repackaging process, a request is created:

  • When the original packs are received in the desktop application, a verification request is sent to the European (EU) Hub automatically.
  • When the original packs are decommissioned in the mobile application, a decommissioning request is sent to the EU Hub automatically.
  • When the new packs are repacked in the desktop application, a commissioning request is created and you need to check and manually approve it on the Check Quality screen before sending it to the EU Hub.


If there is a sending error towards EU Hub, you can resend the request on the Check Quality screen.


After a request is sent, the EU Hub sends back a response:

  • If the request is successful, the SSCC takes the next status automatically.
  • If there is an error, you need to check the cause on the Check Quality screen and take action.


IMPORTANT: 

  • The description below illustrates the case when the request is directly sent to the EU Hub, so an active connection to the EU Hub is available.
  • When an active connection to the EU Hub is not available, the request is wrapped into a JSON file, and the JSON file is sent to the email address specified on the EU Hub channel. You can use the JSON file to update the EU Hub manually. In this setup, the quality check is restricted to monitoring the Movilitas.Cloud side, but there is no information about errors in the EU Hub.


List of Procedures


Managing Verifications


The Verifications tab lists the pending verification requests and verification errors after receiving goods.


Procedure


1. Open the Repacker FMD desktop application.


2. Select CHECK QUALITY --> Verifications.


The application displays two lists next to each other:

  • The left one is for pending requests and requests with sending errors on Movilitas.Cloud side.
  • The right one is for requests that returned with an error from the EU Hub.


For each record, you can see an expand (>) icon, the status, the SSCC ID, and the available action.


Example:



3. (Optional) Select Auto refresh on the top-right corner to automatically refresh the list.


As an alternative, you can manually refresh the list by clicking the Refresh icon at the top of the list next to the title.


4. In the Pending Verifications list on the left, expand the record that you want to investigate by selecting >. The application displays the history of the SSCC.


Example:



StatusAction
Error sending verificationReview the history and click Resend.
Pending verificationReview the history and select the refresh icon next to Pending Verifications title.


5. In the Verification errors list on the right, expand the record that you want to investigate by selecting >. The application displays the alert code received from the EU Hub and the pack data.


For more information on the alert codes and the possible root cause, see EMVS Alert Codes.


Example:



6. Take the necessary actions based on the root cause.


For example, in Movilitas Desktop, remove the item from the SSCC that raised the issue and then receive the SSCC again. Then, click the Refresh icon next to the Verification errors title or next to the specific error.


For certain cases, you can manually approve the error by selecting MANUAL APPROVE.


Next Steps


After the verification errors have been resolved and the goods are received, you can decommission the goods and check for any errors.


Back to the list of procedures


Managing Decommissioning Requests


The Decommissioning tab lists the pending decommissioning requests and decommissioning errors.


Procedure


1. Open the Repacker FMD desktop application.


2. Select CHECK QUALITY --> Decommissioning.


The application displays two lists next to each other:

  • The left one is for pending requests and requests with sending errors on Movilitas.Cloud side.
  • The right one is for requests that returned with an error from the EU Hub.


For each record, you can see an expand (>) icon, the status, the SSCC ID, and the available action.


Example:



3. (Optional) Select Auto refresh on the top-right corner to automatically refresh the list.


As an alternative, you can manually refresh the list by clicking the Refresh icon at the top of the list next to the title.


4. In the Pending Decommissionings list on the left, expand the record that you want to investigate by selecting >. The application displays the history of the SSCC.


Example:



StatusAction
Error sending decommissioningReview the history and click Resend.
Pending decommissioningReview the history and select the refresh icon next to Pending Decommissionings title.


5. In the Decommissioning errors list on the right, expand the record that you want to investigate by selecting >. The application displays the alert code received from the EU Hub and the pack data.


For more information on the alert codes and the possible root cause, see EMVS Alert Codes.


Example:



6. Take the necessary actions based on the root cause and click the Refresh icon next to the Decommissioning errors title or next to the specific error.


For certain cases, you can manually approve the error by selecting MANUAL APPROVE.


Next Steps


After the decommissioning errors have been resolved and the SSCC with its content is inactive, you can repack the goods and check for any commissioning errors.


Back to the list of procedures


Managing Commissioning Requests


The Commissioning tab lists the pending commissioning requests and commissioning errors. You need to check and manually approve each commissioning request before sending them to the EU Hub.


Procedure


1. Open the Repacker FMD desktop application.


2. Select CHECK QUALITY --> Commissioning.


The application displays two lists next to each other:

  • The left one is for pending requests and requests with sending errors on Movilitas.Cloud side.
  • The right one is for requests that returned with an error from the EU Hub.


For each record, you can see an expand (>) icon, the status, the SSCC ID, and the available action.


Example:



3. (Optional) Select Auto refresh on the top-right corner to automatically refresh the list.


As an alternative, you can manually refresh the list by clicking the Refresh icon at the top of the list next to the title.


4. In the Pending Commissionings list on the left, expand the record that you want to investigate by selecting >. The application displays the history of the SSCC.


Example:



StatusAction
Error sending commissioningReview the history and click Resend.
Pending commissioning approvalReview the history and do as follows:
  • Select Set non-serialized origin GTIN and provide the origin GTIN if it is not specified yet for the new product code. If the origin GTIN is stored in the system, the origin GTIN is pre-filled and you can check it.
  • Select Approve Commissioning to approve the request.


5. In the Commissioning errors list on the right, expand the record that you want to investigate by selecting >. The application displays the alert code received from the EU Hub and the pack data.


For more information on the alert codes and the possible root cause, see EMVS Alert Codes.


6. Take the necessary actions based on the root cause and click the Refresh icon next to the Commissioning errors title or next to the specific error.


For certain cases, you can manually approve the error by selecting MANUAL APPROVE.



Back to the list of procedures