Hi @jenjen0510, a few questions to clarify the context of the renaming process:
- Will the renaming of Part/Serial No. occur without involving inventory movement?
- Is this renaming primarily needed for servicing an object, or are there other use cases as well?
@PubudikaW our testing has been only when the part is already in inventory since that is a requirement of the rename functionality. The rename is performed at the end of our process once the return is performed. The original part and serial are processed on the work task return tab and then the part serial rename process is completed. This is primarily talking about the need to service assets for our customers.
Hi @jenjen0510.
Small question on the above,
At point do you identify the that actual part no or the serial no is incorrect? For the serial object to be returned I presume you’d have to enter the serial no on the return line. Should the serial no be renamed to the correct serial no before returning to the inventory so that the return line on the work task reflects the correct serial number?
@Asitha Rajapaksha since the part serial must exist in inventory in order to use part serial rename, during testing we had planned to return the original part serial into inventory using the return on the work task. Then the rename function would be performed which would update inventory to the correct outgoing part and serial. We like this option because it provides the traceability of the rename. If the updated part serial are returned via the work task return line, there is no traceability in the system of the original part serial changing to this updated part serial. We will have custom fields to reflect this on the work task, but nothing like the history tracking on the part serial record itself.
The serial object is usually identified as being incorrect or needing an upgrade during the repair process, but not while a part serial is actually in inventory. That will not occur until the part is moved into inventory via the return tab.
