Is there a way to have one request contract and tie it to multiple Recurring Service Programs with differing customers? We had planned on using request contracts for our rental program where thru the course of an service object’s life, the object is either at a customer location or in house location.
Below is an example of what we are trying to achieve.
Service object PC4500-80-10017728 is a ‘Company Rental Asset’
The object is tied to 2 parties, the internal customer and an external customer. As time progresses as this object goes on rent and off rent there will be multiple more Party’s. The object’s location is currently at the external party’s location.
For our rental program we are using Request Contracts to drive activity types on Requests. It’s a CRIM. We are using Request Contracts to view all RSPs tied to a customer. For rental there are 2 customers, the internal customer and the external customer.
Screenshot of Request 63… Note the main customer is our internal customer, prefixed by ‘IC’ and we have used the ‘Additional Customer’ tab to note the external customers.
When we attempt to create a new RSP connected to contract id 63 and external customer 10003002 we get the following message “Contract 63 is not valid for customer 10003002”, even though we have added the same customer to the additional customers tab on the request contract. Is this intended functionality or are we missing something obvious? For various reasons we were hoping to be able create an RSP and connect it to the alternate customer and the contract.
At the end of the day we are trying to tie the objects current location to the request external location or internal location, while having a central location for viewing RSPs for multiple objects related to our internal customer.
It should be noted we have explored using scopes, but we have run into an issue with an external mobile application, so are exploring alternate routes.
Any help or thoughts would be appreciated.
We are using version 24R2
