Work Items not showing up in users inbox - Basis Issue?

[kyle_mccarter]

Recently I was testing a new workflow with a user in our quality environment. He claimed he wasn't getting SOME of the work items that were definitely assigned to him. I could see they were assigned to him in the workflow log. While I won't belabor the specifics of my investigation, I became highly suspicious that work items created on different application servers of the same SAP instance, were not visible beyond the server they were created on.

To test this theory, I assisted my user in changing his SAP login so that he was no longer logging in to the (load balanced) group server set up by our basis team, but to one of our two application servers. Once there we looked into the SAP Business Workplace (SBWP). Some of the work items assigned to this user were visible. We did this once more for the second application server. This time his inbox showed the remaining work items I knew to be assigned to him. In NEITHER case was he able to see ALL of the work items assigned to him.

ISSUED FIXED- I contacted our basis team and relayed our test efforts above. They DID FIX the issue, and now my user can see all the work items assigned to him. Upon querying the basis team as to what was causing this behavior, I received NO reply at all.

This issue looks very much like that discussed a couple years ago in the workflow space (http://scn.sap.com/thread/1122712). Unfortunately, there too, the solution was not shared.

Can anyone enlighten me? Kindest Regards to all and thanks in advance for your insights.

[kyle_mccarter]

Alwina,

I think you've probably got it! Here is a screen shot of the system log. Can you shed some light on what I'm seeing?

Thank you for all your great input!

KM

[alwina_enns]

Hello Kyle,

thanks 🙂 Could you please attach also the corresponding exerpt from work process trace dev_w46 and dev_w56, if there is more information on the messages in syslog are reported? Could you please check also buffer overview in AL12, how often buffers are synchronized? But if your basis people have already solved the issue, AL12 is probably OK already.

regards,
Alwina

[kyle_mccarter]

Hi Alwina... I'll put each of the items you requested in their own post. Here is a screen shot of AL12

KM

[kyle_mccarter]

Hi Alwina,

Here is the relevant portion of dev_w46.

trc file: "dev_w46", trc level: 1, release: "720"

*
*  ACTIVE TRACE LEVEL           1
*  ACTIVE TRACE COMPONENTS      all, MJ
*
M sysno      03
M sid        RPG
M systemid   274 (HP (IA-64) with HP-UX)
M relno      7200
M patchlevel 0
M patchno    522
M intno      20020600
M make       single threaded, ASCII, 64 bit, optimized
M profile    <removed by Kyle>
M pid        14183
.....
M Tue Jul 15 00:00:51 2014
M  SecAudit(check_daily_file): audit file closed /usr/sap/RPG/D03/log/audit_20140714
M  SecAudit(check_daily_file): audit file opened /usr/sap/RPG/D03/log/audit_20140715
E
E Tue Jul 15 04:00:27 2014
E  Enqueue Info: enque/use_pfclock2 = FALSE
E  Enqueue Info: row condense enabled
S
S Tue Jul 15 04:01:27 2014
S  found spool memory service RSPO-ACTIONS at c00000008cfb7600
A
A Tue Jul 15 04:35:27 2014
A  Localtime1 1405416927, Loaltime2 1405416927, Localtime3 1405416927
A  DBTime1 1405416927, DBTime2 1405416927
A  Avarage loctime 1405416927, Avarage DBTime 1405416927, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 05:05:28 2014
A  Localtime1 1405418728, Loaltime2 1405418728, Localtime3 1405418728
A  DBTime1 1405418728, DBTime2 1405418728
A  Avarage loctime 1405418728, Avarage DBTime 1405418728, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 05:35:28 2014
A  Localtime1 1405420528, Loaltime2 1405420528, Localtime3 1405420528
A  DBTime1 1405420528, DBTime2 1405420528
A  Avarage loctime 1405420528, Avarage DBTime 1405420528, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 06:35:28 2014
A  Localtime1 1405424128, Loaltime2 1405424128, Localtime3 1405424128
A  DBTime1 1405424128, DBTime2 1405424128
A  Avarage loctime 1405424128, Avarage DBTime 1405424128, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 07:31:00 2014
A  PXA APG: skipping current run due to transport activities
A
A Tue Jul 15 07:35:29 2014
A  Localtime1 1405427729, Loaltime2 1405427729, Localtime3 1405427729
A  DBTime1 1405427729, DBTime2 1405427729
A  Avarage loctime 1405427729, Avarage DBTime 1405427729, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 08:05:30 2014
A  Localtime1 1405429530, Loaltime2 1405429530, Localtime3 1405429530
A  DBTime1 1405429530, DBTime2 1405429530
A  Avarage loctime 1405429530, Avarage DBTime 1405429530, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 08:35:30 2014
A  Localtime1 1405431330, Loaltime2 1405431330, Localtime3 1405431330
A  DBTime1 1405431330, DBTime2 1405431330
A  Avarage loctime 1405431330, Avarage DBTime 1405431330, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
M
M Tue Jul 15 09:07:12 2014
M  Deactivate ASTAT hyper index locking
B
B Tue Jul 15 13:16:30 2014
B  dbexpbuf[EXP_OTR]: Aquired semaphore 55 in db_exp_init(EXP_INVALIDATE)
B  ***LOG BBD=> reset of buffer OTR       , mode and status: InvalBeg    [dbexpbuf     2400]
B  dbexpbuf[EXP_OTR]: buffer OTR   installed with
B    semkey             = 55
B    shmkey             = 64
B    wp_n               = 72
B    sclass             = 13
B    block_length       = 128
B    max_objects        = 2000
B    max_obj_size       = 891136
B    pref_obj_size      = 0
B    est_large_obj_size = 10240
B    free_vec_lg        = 81
B    hash_vec_size      = 4001
B    buffer_l           = 4194304
B    max_blocks         = 27854
B    free_blocks        = 27854
B    mutex_n            = 4001
B    max_mtx_wait_time  = 17000
B    recovery_delay     = 500000
B    tracing            = 0
B    force_checks       = 0
B    protect_shm        = 0
B  ***LOG BBD=> reset of buffer OTR       , mode and status: InvalEnd    [dbexpbuf     2485]
B  dbexpbuf[EXP_OTR]: semaphore 55 released in db_exp_init
A
A Tue Jul 15 16:01:01 2014
A  PXA APG: skipping current run due to transport activities
A
A Tue Jul 15 16:17:01 2014
A  *GENER* starting anticipatory generation: SAPLSEEF_UPGRADE
A
A Tue Jul 15 16:17:07 2014
A  *GENER* starting anticipatory generation: CL_ENH_TOOL_BADI_IMPL=========CP
A
A Tue Jul 15 17:05:35 2014
A  Localtime1 1405461935, Loaltime2 1405461935, Localtime3 1405461935
A  DBTime1 1405461935, DBTime2 1405461935
A  Avarage loctime 1405461935, Avarage DBTime 1405461935, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 17:33:02 2014
A  *GENER* starting anticipatory generation: SAPLCOIH
A
A Tue Jul 15 17:33:35 2014
A  *GENER* starting anticipatory generation: SAPLXCO1
A
A Tue Jul 15 17:35:35 2014
A  Localtime1 1405463735, Loaltime2 1405463735, Localtime3 1405463735
A  DBTime1 1405463735, DBTime2 1405463735
A  Avarage loctime 1405463735, Avarage DBTime 1405463735, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 18:05:35 2014
A  Localtime1 1405465535, Loaltime2 1405465535, Localtime3 1405465535
A  DBTime1 1405465535, DBTime2 1405465535
A  Avarage loctime 1405465535, Avarage DBTime 1405465535, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 18:35:36 2014
A  Localtime1 1405467336, Loaltime2 1405467336, Localtime3 1405467336
A  DBTime1 1405467336, DBTime2 1405467336
A  Avarage loctime 1405467336, Avarage DBTime 1405467336, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).
A
A Tue Jul 15 20:05:37 2014
A  Localtime1 1405472737, Loaltime2 1405472737, Localtime3 1405472737
A  DBTime1 1405472737, DBTime2 1405472737
A  Avarage loctime 1405472737, Avarage DBTime 1405472737, Diff 0
A  Returncodes codes db_time 0 0 0
A  Local time adjusted (0 sec).

[kyle_mccarter]

Hi Alwina,

Here is the relevant portion of dev_w56.

trc file: "dev_w56", trc level: 1, release: "720"

*
*  ACTIVE TRACE LEVEL           1
*  ACTIVE TRACE COMPONENTS      all, MJ
*
M sysno      03
M sid        RPG
M systemid   274 (HP (IA-64) with HP-UX)
M relno      7200
M patchlevel 0
M patchno    522
M intno      20020600
M make       single threaded, ASCII, 64 bit, optimized
M profile    <Removed by Kyle>
M pid        14197
....
M Tue Jul 15 00:00:51 2014
M  SecAudit(check_daily_file): audit file closed /usr/sap/RPG/D03/log/audit_20140714
M  SecAudit(check_daily_file): audit file opened /usr/sap/RPG/D03/log/audit_20140715
B
B Tue Jul 15 17:31:56 2014
B  dbexpbuf[EXP_OTR]: Aquired semaphore 55 in db_exp_init(EXP_INVALIDATE)
B  ***LOG BBD=> reset of buffer OTR       , mode and status: InvalBeg    [dbexpbuf     2400]
B  dbexpbuf[EXP_OTR]: buffer OTR   installed with
B    semkey             = 55
B    shmkey             = 64
B    wp_n               = 72
B    sclass             = 13
B    block_length       = 128
B    max_objects        = 2000
B    max_obj_size       = 891136
B    pref_obj_size      = 0
B    est_large_obj_size = 10240
B    free_vec_lg        = 81
B    hash_vec_size      = 4001
B    buffer_l           = 4194304
B    max_blocks         = 27854
B    free_blocks        = 27854
B    mutex_n            = 4001
B    max_mtx_wait_time  = 17000
B    recovery_delay     = 500000
B    tracing            = 0
B    force_checks       = 0
B    protect_shm        = 0
B  ***LOG BBD=> reset of buffer OTR       , mode and status: InvalEnd    [dbexpbuf     2485]
B  dbexpbuf[EXP_OTR]: semaphore 55 released in db_exp_init

[alwina_enns]

Hello Kyle,

many thanks. I only see, that OTR buffer was reset. After searching for some information in the SAP notes this is the "online text repository" buffer, and I'm not sure, if this is related to the work items. If I reset this buffer in AL12 I get the same entries in the syslog under my user id like in your screenshot. Do you know, when you have reported the issue to your basis team and when it was resolved? Could you please check the syslog for this time frame, if you see entries for a basis user, if they have called something? Some actions on the system like parameter switches at runtime or buffer reset are logged in the syslog. If you know the user ID, under which basis team works on the system, you can check also statistics in ST03 for this user, you should see, which transactions and reports they have called.

Regards,
Alwina

[kyle_mccarter]

Hi Alwina,

I've looked into the tranactional audit logs and ST03 for both DDIC and the basis user ID who reported resolving the issue (see attached screen shots). The only transactions that look promising are SWU3 (Worklfow Runtime customizing)and SWU4 (Workflow task consistency checks). While it is possible one of these starts some synchronization process, I couldn't find anything like that explicitly in either transaction. By the way, these two transactions would fall into the window of time the issue was resolved.

I am not familiar with the entry (in attached screen shot) for <AD_NTAB_SYNC>. Nor could I determine the time this was done which is probably due to a lack of understanding on my part as to what this entry represents.

Thanks for all your support. I appreciate the time you have taken to assist me in unravelling this mystery.

Kindest Regards,

KM

[alwina_enns]

Hello Kyle,

there is this note:

https://service.sap.com/sap/support/notes/1098805

1098805 - Troubleshooting Tips & Tricks for workflow issue

which explain possible reasons for this. Is the BAdi implementation WF_BWP_SELECT_FILTER active and were the work items for the affected user filtered by this BAdi?

Regards,
Alwina

[kyle_mccarter]

Greetings Alwina,

Thank you for the reply. I should have mentioned BAdI WF_BWP_SELECT_FILTER is NOT currently active. Nor did I find a possible cause in the troubleshooting note you mention. I refer to that one often

Cheers,

KM

[alwina_enns]

Hello Kyle,

if you could see different work items on different application servers, then probably there was a problem with the table buffer synchronization. Do you see any messages in syslog about buffer synchronization at the time when the issue occurred?

regards,
Alwina