One of your ideas has been delivered from your suggestion.Exchange Part without Requiring a Returned Part

You can now create part exchange shipments when the broken part will not be returned by the customer.   As you can see in the screen shot below of the Add Part UI, you now have the option to reference a broken customer asset when creating a part exchange shipment.  When a new part is shipped to the customer, its asset record will get updated with the parent asset and remaining warranty/subscription from the broken asset.  Also, the broken asset will be updated to indicate that it has been replaced.

Add Part UI for shpping a replacement part without the return of a broken part

Add Part UI for Shipping a Replacement Part without the Return of a Broken Part

This functionality reduces the need to manually update the installed base to transfer information (for example, remaining warranty coverage) from the broken part that is not being returned to the replacement part being shipped to the customer.

Steps to Enable

You don't need to do anything to enable this feature.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

  • Access Part Requirements Header for Administrator (RCL_ADMIN_PART_REQUIREMENTS_HEADER_PRIV)
  • Access Part Requirements Header for Technician (RCL_FSTECH_PART_REQUIREMENTS_HEADER_PRIV)
  • Access Part Requirements Details for Administrator (RCL_ADMIN_PART_REQUIREMENTS_DETAILS_PRIV)
  • Access Part Requirements Details for Technician (RCL_FSTECH_PART_REQUIREMENTS_DETAILS_PRIV)