cancel
Showing results for 
Search instead for 
Did you mean: 

Approval not grouped when serveral SC items exist

Former Member
0 Kudos

Hi all!

I'm currently experiencing problems with grouping of items in the mySAP SRM interface where managers handle shopping carts in an item based approval process. As of now, items show up sequentially, meaning that an approver responsible for two items will recieve two work items, among which the second will be displayed only when the first has been processed.

We've managed to get grouping to work earlier (in our sandbox), and it is imperative to allow the customer to approve or reject multiple lines in a single screen. Am I using the approval objects incorrectly?

Thankful for any hints!

Sincerely,

Mike.

Accepted Solutions (1)

Accepted Solutions (1)

pvanhoove
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

In order to group items in one workitem, you have to link them to the same approval object.

One approval object = one workitem.

Rgds,

Pierre

Former Member
0 Kudos

Thanks for the input!

Just to make sure I'm doing this correctly;

Using the BBP_WFL_DIN_APP_OBJ_GET function correctly, is it still my responsibility to arrange the approval objects? I'm looping over SC items, call the function above, and if the returned object is new assign agents to it using the approval table and the item approval table.

So;

  • Loop over items

  • Create approval object

  • Check if new

  • If new, assign agents to approval objects by;

  • Adding agent data to approval table.

  • Adding approval object GUID to approval table.

  • Once per item adding approval object GUID and item GUID to item approval table.

Am I doing this correctly? Everything works, except for the grouping in the approver's interface.

Sincerely,

Mike

pvanhoove
Product and Topic Expert
Product and Topic Expert
0 Kudos

I think it is almost that:

- For each approval step:

  • increment approval step number

  • loop over item

  • Set approval object using the function BBP_WFL_DIN_APP_OBJ_GET (a new approval object will be generated if necessary)

  • link approval object with item

  • append agent, approval step number, approval object to approval table (do it for new agent or new approval object or symply delete duplicates)

Rgds,

Pierre

Former Member
0 Kudos

Thanks for your answer!

I think that's how I do it...

However, I still can't seem to get the grouping to work.

I'll try to explain my logic in pseudocode for n-level of my flow (non-relevant sections removed);



Loop over all items in SC
   Get approval object (using standard function)
   If new object
      Get approver(s) for current SC item (based on same criteria as the approval object)
      Loop over approvers  
         Add data to AT (level n, user data, approval object GUID)
      Endloop
      Add data to IAT (approval object GUID, item GUID)
   Endif
Endloop

Am I supposed to manually process the AT, linking approval objects with approvers in another way?

Thankful for clues

Best regards,

Mike

pvanhoove
Product and Topic Expert
Product and Topic Expert
0 Kudos

Almost ....

the "if new object" is not usefull, and tables won't be filled properly.

Better than coding think at what approval tables should like

App tables

Level 1 , Approver 1, Approval Object 1

Approval object:

Approval object 1; criterai/value

Item approval

Item 1, Approval Object 1

Item 2, Approval object 1

This way, item 1 and 2 are grouped.

Answers (0)