Showing results for 
Search instead for 
Did you mean: 

Team Cart: Taking Over the SC as SC Creator instead of Requestor

0 Kudos

Hello Experts,

In Team Cart scenario, when a Team member tries to Take over the existing Cart, then system updates the Partner Function 16 (requestor) data.

But if a SC is a BOBO SC then the take Over process is changing the requestor data. I have couple of ideas to save this:

1. When Take over is being done then saving the Existing requester in any Z field and letting the system to change the requester. Finally when SC is being Ordered then again updating the SC requester to original requested value. I am little concerned here about the workflow part. Will System be able to identify the correct workflow assignee

2. Otherwise, I was trying to lookout for option to add a new Partner Function to the SC which will have similar privilege like that of Requester. but, here I am not sure how system works internally for authorization. Does it grants Authorization based on Partner function Code or the Function type value listed in table:


Please advise.


Manish Agrawal

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Any Inputs?