View the history of a specific SSCC in the Serialized Manufacturing application.
Before You Begin
Make sure that the SSCC is registered in Movilitas.Cloud.
Procedure
1. In the Serialized Manufacturing application, select the SN/SSCC pool --> SSCC history tab.
2. Enter the SSCC number in the SSCC field.
3. Click Get SSCC History.
The application displays:
| Section | Description |
|---|---|
| Summary | Pool status, container status, and parent. |
| Pool History | The actions performed on the SSCC and the status for each action. |
| Container History | The actions performed on the container (physical item) and the result per action. |
| SSCC Hierarchy | The hierarchy of the SSCC up to the lowest child, with details for each level. By default, the application displays only the SSCC under investigation with a summary of the next level:
The user can expand each level for further details and the application displays data for the next level as described above. For example, for nested containers, the application shows the child container first, and then it shows the content of the child container after expanding the child container. |
The SSCC can take one of the following statuses in the SSCC pool:
| Status | Description |
|---|---|
| Available | The SSCC is free to use. |
| Assigned | The SSCC is reserved for an activity. |
The SSCC as a physical container can take one of the following statuses:
| Status | Description |
|---|---|
| Active | The container and its content are produced but not yet commissioned to the market. |
| Commissioned | The container and its content are commissioned to the market. |
| Decommissioned | The container and its content are decommissioned due to one of the following reasons:
|
| Unknown | The container (SSCC) is not known by Movilitas.Cloud. |
If the SSCC is not in possession (shipped), the application informs the user in a pop-up that the provided data may not match the current reality.
The following example illustrates a commissioned container at the tertiary level that has a child container at the secondary level with five packs at the primary level:
The following example illustrates a container not in possession (shipped). The application displays a pop-up informing the user:
