SWU_OBUF in EHP7

Mon Oct 28 19:12:14 EDT 2013

Hi Carolyn,

If the buffer wasn’t refreshed at the time you created the transaction in step 2 it might not automatically reassign itself if there were no selected agents at the time.

What you can use for such situations is transaction SWI1_RULE which will do this for you assuming the rule that finds the position is directly associated with the workflow step itself. That will let you find any work items without agent and then re-execute the rule to assign them, or even use an administrator forward to redirect them while you sort out organizational structure problems.

You should also check that the new approver is not an excluded agent – as of course then she would never be assigned to that work item.

SWU_OBUF was always a fairly crude measure for updating buffers.  That’s why the additional admin tools  (all the SWI1* and SWI2* transactions) were added several years ago.  It’s worth getting familiar with them.

Rgds,

Jocelyn

From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf Of Carolyn A Fuller
Sent: Tuesday, 29 October 2013 7:43 AM
To: SAP Workflow Users' Group
Cc: Workflow Administrators; Frank Quern
Subject: Re: SWU_OBUF in EHP7

Ionut,

I tested the Refresh Organizational Environment today and discovered strange behavior under EHP7 Release 740 SP-Level 0003.

1. I added someone to the approver's position

2. I created a transaction that triggered workflow that went to this position's inbox

3. I ran SWIA for the new approver and found workflows created on 04/08/2013 in her inbox but not the workflow I had just triggered

4. This new approver logged into the environment and went to her inbox. None of the workflows were there even though she just logged in.

5. She chose -> Settings -> Workflow Settings -> Refresh Organizational Environment in the Business Workplace

6. The workflows created on 04/08/2013 were in her inbox but the one workflow that I triggered a few moments after adding her to the position was not there.

7. I created a new transaction about 50 minutes after adding her to the inbox and it did show up in her inbox but the one created moments after she was added to the position never showed up.

Is there another method for refreshing the PDOrg that works reliably?

Carolyn

On Oct 28, 2013, at 7:03 AM, "Andronache, Ionut-Laurentiu" <ionut-laurentiu.andronache at sap.com<mailto:ionut-laurentiu.andronache at sap.com>> wrote:

Hi Carolyn,

From my experience SWU_OBUF is used for WFs objects (also tasks, rules, etc) modifications. To get a refresh to the OM changes you can refresh OM from Business Workplace -> Settings -> Workflow Settings -> Refresh Organizational Environment (this way you should get the result that you are looking for immediately).

Ionut Andronache

SAP ABAP Senior Consultant, SAP Romania

Specializations:       SAP Workflow Consultant

SAP ABAP HCM Consultant

SAP WebDynpro/ FPM Consultant

SAP Romania SRL
Str. Tipografilor 11-15, Clădirea A1 /LA, Etajul 2, 013714,1 Bucureşti

T + 40/ 31 225 28 73, F + 40/ 31 228 59 09, M +40/ 755 094 478
mailto:ionut-laurentiu.andronache at sap.com
www.sap.com<http://www.sap.com/>
Before printing, think about the environment
Informatia continuta in acest comunicat este confidentiala, poate fi privilegiata si a fost conceputa spre a fi utilizata exclusiv de catre destinatarul mentionat mai sus. In cazul in care primiti acest comunicat din eroare, va rugam sa anuntati imediat expeditorul si sa-l stergeti, impreuna cu toate documentele atasate. Daca nu sunteti destinatarul caruia ii este adresat acest comunicat, va este interzisa citirea, copierea, difuzarea sau folosirea in orice fel a oricarei informatii din acesta fara consimtamantul dat de catre SAP Romania. Va rugam luati nota de faptul ca email-urile nu garanteaza nici confidentialitatea si nici receptia corecta a mesajului trimis, prin urmare SAP Romania nu se face responsabila de nici un prejudiciu cauzat.

The information contained in this communication is confidential, may be privileged and is intended for the exclusive use of the above named addressee. If you receive this communication in error, please notify the sender immediately and delete it, and all its attached documents. If you are not the intended recipient, you are expressly prohibited from reading, copying, distributing, disseminating or, in any other way, using any of the information without the SAP Romania consent. Please note that Internet e-mail guarantees neither the confidentiality nor the proper receipt of the message sent, so that SAP Romania shall not be liable for any damages caused.

From: sap-wug-bounces at MIT.EDU<mailto:sap-wug-bounces at MIT.EDU> [mailto:sap-wug-bounces at MIT.EDU<mailto:wug-bounces at MIT.EDU>] On Behalf Of Carolyn A Fuller
Sent: 25 October 2013 22:32
To: SAP Workflow Users' Group
Cc: Workflow Administrators
Subject: SWU_OBUF in EHP7

Hi,

We are in the process of upgrading to EHP7 Release 740 SP-Level 0003. This morning one of the workflow administrators added someone to one of our approver positions, back dating the relationship and then ran SWU_OBUF to refresh the PD Org buffers.

Some pre-existing transactions appeared in this person's inbox after that but not all of them. And 50 minutes after she was added to the position, a document was created and sent to her position but did not appear in her inbox. A couple of hours later she repeated the test and it did appear in her inbox.

Shouldn't SWU_OBUF have ensured that the transaction created 50 minutes later would have appeared in her inbox? Is there workflow buffer a problem with EHP7?

---

Carolyn Fuller

Senior Analyst/ Programmer

Information Services and Technology

Massachusetts Institute of Technology

Room W92-215A

Cambridge, MA 02139

(617) 253-6213

http://fuller.mit.edu/

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto: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/20131028/1a86f97d/attachment-0001.htm