...
Use a different CU from the one used to install the customer.
...
| Info |
|---|
In some cases you can record repossession the normal way as if CUs are matching. See attached related tickets. |
| Info |
|---|
If the above fails, then try record as CUs are not matching: Related ticket: | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 66cc1948-fd1c-3147-8367-bc66529b4eb8 |
|---|
| key | CMS-28814 |
|---|
|
 Image Added
|
Step3: Void Repossession:
...
Note: It may take some time for ERP to update Smart Solar for the CU state or ask the Device team to help to changed the state.
Related ticket(s):
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 66cc1948-fd1c-3147-8367-bc66529b4eb8 |
|---|
| key | CMS-27179 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 66cc1948-fd1c-3147-8367-bc66529b4eb8 |
|---|
| key | CMS-27600 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 66cc1948-fd1c-3147-8367-bc66529b4eb8 |
|---|
| key | CMS-28812 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 66cc1948-fd1c-3147-8367-bc66529b4eb8 |
|---|
| key | CMS-28823 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 66cc1948-fd1c-3147-8367-bc66529b4eb8 |
|---|
| key | CMS-28822 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 66cc1948-fd1c-3147-8367-bc66529b4eb8 |
|---|
| key | CMS-28738 |
|---|
|
