Update Model after a request is submitted

[simonmueller]

Let's say we published in the catalog Model X v4. We have now received a request for Model X v4 through a request. However, we only have stock of Model X v3 (prior model). Is there a simple way to update the model in the RITM/Sourcing Task to assign the prior model instead of the most current? I could not find an option and only way I have seen it would be to cancel the request and then re-submit a new request for the old model. 

[DavidWallace1]

Yes you can. When you have the sourcing task (child of the REQuest record) and there is no stock of the item in your warehouse to do a transfer and you want to change the model on the request, you do the following.

- go back up to the parent REQ record

- find the RITM for the hardware item that you just failed to source (because of no stock)

- on the RITM record you will see that the Item field is editable - select a different catalog item for a different model  (that you DO have stock for)

- go back to the sourcing task

- now when you use the Source Request UI action you will see that the model to be sourced will have changed to the one that you just selected on the RITM, and there will now be available stock to do a Transfer (or consume)

[Mark Manders]

So both models are active and they can be selected? Or do you have separate forms for both models? 

You could add a text that states that as long as older models are available, those will be assigned. Or you add logic to the one form that it won't show the new model, as long as the old one is in stock. But we are missing a lot of information to give you a well thought-through solution.

[DavidWallace1]

Both models have to have an active cat item in the catalog (but you can add visible for etc conditions so you only show the preferred one for example).

• User fills in form and requests model A
• Warehouse team see that they can't fulfil Model A so swap it out for Model B (which is an invisible cat item in the catalog). They will add a comment onto the request/ritm so that the user understands why they got Model B instead of Model A

It isn't a full/especially great solution imo.

There is the concept of substitutes against models - but at the moment this doesn't do anything more than act as a prompt as to which model to use instead if one is out of stock, there is no automation behind it. In future releases I would expect this to evolve into a more joined up approach.

• User requests model A
• Model A is out of stock
• Model B is specified as a substitute for Model A
• Model B is applied to the requested item instead of model A
• Sourcing creates a transfer order for model B to fulfil the request (and adds a comment etc for the requestor)

But it doesn't do that right now, and I haven't made the time to go make it, it happens relatively rarely for me and the warehouse team know how to do this substitution manually.

[Mark Manders]

Not sure why you are answering questions I asked the original poster, without him having given any feedback on either one of us. Are you making assumptions on how the setup is for the person that asked the question? Do you know his setup?