What do you mean by
Can you provide more detail of what you are trying to do?
Right every company’s model/procedure for warranty (ahem, it’s Product Support) is different.
We spend exactly zero on direct labor for warranty Product Support, so we don’t use Field Service (though we own it).
We are an automotive OEM, so our dealers do the work and use their own component parts for repair, and then we reimburse them. It’s not what FS is designed for. FS expects you (the OEM) to do everything out of your own inventory and labor.
How does your company approach warranty, @Craig ?
how are you linking those reimbursements back to the warrantied item?
We sell airplane seats, the tray table breaks, we send them a new one with 0 price with a warranty product group sales order.
we want some data to show this tray table was linked to this serial number seat for this customer.
Some times we let an outside company do the work to repair stuff, we would just pay that person but we want to link it to the original serial number seat to track what parts/ customers are getting the most warranty, etc.
I currently do not have the module that includes warranty but have used it before. If you apply a warranty to a part, the system will calculate if it is in/out of the warranty period based on the shipment. It’s been a real long time, but I believe there are ways to handle each type of warranty that could arise. Replacement, repair, and other stuff.
i assume that would require a warranty code for each part number to handle that calculation?
I was thinking i could just add UD fields and do the calculations myself.
If all you want is to report on them, a UD field would do the trick. If you want to do any accounting changes, you might want to consider Sales Category or Product Group changes.
Uh yeah…
So we have a redundant system (a website) that’s external to Kinetic. We are working on integrating it with Kinetic, but I am told that the web database tracks the “chassis ID” (aka our Project ID) and ties the costs there. Point is, it’s not in Kinetic.
We have considered some UD fields on… everything.. to do that reporting in Kinetic, though. (AR CMs, AP invoices, sales orders)
We do this also.
Hi Ernie. We are already using Warranty product groups to control GL mapping. Thats why I was thinking I dont really need field service, just some UD fields.
We do pretty much as you described at the top: warranty product group for the GL control, and a case to link the serial number of the full product. Serial number typically also gets copied to the comments on the order to make it more visible, but the main reporting point is the warranty/spare parts order is linked to a case which has a serial number and all the details about why this part is being replaced under warranty.
Yes, when setting up the part you determine if there is a warranty that gets applied.
That’s up to your Company. 
I remember the functionality worked well once I figured out how to use it. My personal preference is to use modules instead of customizing, but if your Company does not want to pay for it, your idea sounds good.
That oughta do it.
That is my preference as well. But I also dont like spending money on more modules if I dont have to. 