Review how product, asset, claim, and location records support the Warranty Parts Return service process.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions. |
Warranty Parts Return uses records from Warranty Lifecycle Management, inventory, and dealer accounts. The intake OmniScript queries these records at runtime. Create them in the order shown so that users can select an asset, claim item, returnable parts, locations, and a contact.
Records That Work Together
| Record | Description | Creation Order |
|---|---|---|
| Product | Represents vehicles and the replacement parts referenced on claim coverage payment details. The Unified Catalog template also creates a Product2 record for the service process. | 1 |
| Contact | Identifies dealer contacts who participate in the return. | 2 |
| Asset | Represents the vehicle or part instance covered by the claim. | 3 |
| Claim Item | Identifies the claimed asset. The intake OmniScript lists claim items whose Asset ID matches the selected asset. The process doesn't validate warranty coverage before listing those items. | 4 |
| Claim Coverage Payment Detail | Identifies the replacement parts to return. The intake OmniScript lists only payment details where Is Part Return Required is true and the related claim coverage points to the selected claim item. | 5 |
| Location | Represents the inventory and shipping sites used for the return. Location provides the values that appear in Destination Location on the return order. | 6 |
| Associated Location | Forms the basis for the values shown in Source Location on the return order, drawn from the locations associated with the account. | 6 |
| Claim Participant | Identifies the participants and their roles on the claim, which the process uses to associate the correct contact with the return request. | 7 |
Return Order Records
The Process Warranty Parts Return fulfillment flow (API name ProcWrntyPrtRtrn) creates a Return Order and Return Order Line Items from the selected claim coverage payment details. It sets Status and Status Category to Draft and Process Type to ServicePartReturn, and then copies Contact, Account, Case, Source Location, and Destination Location from the request. The flow doesn't set Processing Plan or Repayment Method. After the records are created, it emails the case contact and sets the case Status to Closed.