BRF Workflow - SRM Shopping Cart Approval at item level

[Ramki Maley]

Raja,

It is not a good idea to change the status on your own. As far as I know 
what you want to do is not achievable. The documentation clearly states 
all items in the SC must be approved at each level before the next level 
can be processed.

Regards,
Ramki.

On 4/3/11 10:21 PM, Raja wrote:
> Hello Ramki ,
> Thank You for your response .
>
> Is there a way through coding/customization  , to create decision sets 
> at item level  so that  for example when the line item 1 is approved , 
> it does not have to wait for item 2 ? . Basically , what I am looking 
> for is , item 1 status should be changed to "Approved" so that 
> follow-on documents will be created.
>
> Or Shall I use any BAPI to change the status  or write custom method 
> to change the item's system  status to "approved " ?.
>
> Any ideas or suggestions welcome.
>
>
> Thanks,
> Raja
> 248 910 0604 Cell
>
> ------------------------------------------------------------------------
> *From:* Ramki Maley <rmaley at erpworkflow.com>
> *To:* SAP Workflow Users' Group <sap-wug at mit.edu>
> *Sent:* Sun, April 3, 2011 5:07:01 PM
> *Subject:* Re: BRF Workflow - SRM Shopping Cart Approval at item level
>
> Raja,
>
> What you are experiencing in both cases is standard system behavior. 
> Please see the SAP documentation for Decision Sets 
> <http://help.sap.com/saphelp_srm70/helpdata/EN/2c/2ecf5596524af59d454ee6f1684b4d/content.htm>. 
>
>
> Regards,
> Ramki.
>
> On 4/2/11 8:38 PM, Raja wrote:
>>
>> Hello Experts ,
>>
>> We are using SRM 7.01 and SP Level3 .
>>
>> We are in the process of implementing Shopping Cart Approval at item 
>> level using Business Rule Framework using Process Controlled Schema 
>> evaluation .
>>  I have used the BADI implementation /SAPSRM/BD_WF_RESP_RESOLVER  and 
>> methods
>> /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID  and 
>> /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_AREA_TO_ITEM_MAP
>> to create area GUID and map it to the item.
>>
>> Problems I am facing :
>> Scenario 1 :   For example  SC got two items  ; item 1  requires two 
>> level of approval and item 2 requires 3 level of approval .  Item 1 
>> is approved by both the levels  and item 2 needs 3rd level approval.
>>
>> What is happening here is , line item 1 is also in the waiting 
>> approval status, technically item should go to "Approved" ,but the SC 
>> is waiting for item 2 to be approved by 3 rd level . Then the SC 
>> status is changed to "Approved".
>>
>> Scenario 2 :   For example  SC got two items  ; item 1  requires two 
>> level of approval and item 2 requires 3 level of approval .  Item 1 
>> is approved by both the levels  and item 2 rejected by 3 rd level . 
>> Even in this case ,the rejected item needs decision  from the SC 
>> creator , then only the other item is going for approval.
>>
>> Basically only one instance of  workflow (WS40000014) is called at 
>> for the entore shopping cart and the approval workitem is created
>> at the n-step approval sub-workflow (WS40000015 and WS40000016). In 
>> our situation there should be either multiple instances
>> of WS400000154/WS40000015 should be called so that every item will be 
>> considered as a separate approval.
>>
>> I read from SDN that Process Schema's  evaluation is at  header level 
>> only by default .
>> We have done coding in the  item area map method /BADI  and Rule 
>> Context to to go for different approval process at item level.
>>
>> Any ideas and  suggestions welcome . I appreciate your time and 
>> effort in advance.
>>
>>
>> Note : I am willing to share my code if anybody wants to have a look 
>> at to provide suggestion.
>>
>>
>> Thanks,
>> Raja Mahamani
>> 248 910 0604
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110404/0f6138ca/attachment.htm