cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Work Manager 6.3 notification data distribution by assignment type '5' issue

Former Member
0 Kudos

Hi Experts!

We use SAP Work Manager 6.3.1 as a fully standard application with Sap Mobil Platform 3.0 SP11.

We have a problem about notification fetching:

In the Agentry Customizing panel, we set the Assigment_Type filters value to „5- Header Level Work Center” int he NOTIFICATION_GENERIC’s MDO, as you can see:


We set a User Parameter called: VAP and a Work Center, and we create a lot of new Notification whit this Work Center. After Client Synchronization, the Notifications not received. The serves log shows,  maybe this setting not succesfully adapted, you can see the Employee ID field:


Int the workmanager-6.3.1.0.jar file the com.syclo.sap.component.notification.bapi.NotificationFetchBAPI Class in Setparameters method we found a hard coded section as you can see:


public void setParameters(SAPObject obj) throws Exception {
super.setParameters(obj);
this._notification = (Notification) obj;
Logger log = new Logger(this._user, "setParameters");
this.setFilterRange("IT_EMPLOYEE_ID_RA", "I", "EQ", this._notification.getPersNum(), "0");
log.info("IT_EMPLOYEE_ID_RA LOW=" + this._notification.getPersNum());
log.info("done");
}

We think, this hard coded value overrides the setting that we set in Agentry Customizing Panel?!


thanks,

Peter

Accepted Solutions (0)

Answers (7)

Answers (7)

former_member265714
Participant
0 Kudos

Hi Peter,

The KBA will be released soon.

Subash

Former Member
0 Kudos

not yet...

former_member265714
Participant
0 Kudos

Hi Peter,

Thanks for pointing out the documentation error. I have created a KB article :

2350471- SAP Work Manager: Notifications with different assignment types are not downloaded to the client

https://launchpad.support.sap.com/#/notes/2350471

Thanks

Subash Narayan

SAP Support Engineer

Former Member
0 Kudos

Hallo Subash,

I wrote many times, that the note is not released....

sravanthi_polu
Contributor
0 Kudos

Hi Gaál Péter,

Verify the filter work_cntr in configuration panel for Notification MDO. Maintain VAP parameter as a filer condition.In su01 maintain only work center parameter ID as VAP. Might also be the case that the user has some work center defaulted in HR configurations. Debugg the ABAP class and verify if the notifications are fetched for 5 assignment type in select query.

Thanks&Regards,

Sravanthi Polu

0 Kudos

Can you pls paste the screenshots of all filter conditions you have set for MDO NOTIFICATION_GENERIC ?

Former Member
0 Kudos

hello,

SAP answer:

Hi Customer,
I have asked this question to development as per their answer is OOB  we do not support different assignment type levels for notification object. The backend configuration supports it but the java and client is not supported. To make this work , you would need to customize the java code and client to support different assignment type level for notification object. You can customize it by taking on existing example from the work order object assignment types.
Thanks
Subash Narayan
SAP Support Engineer

former_member197782
Participant
0 Kudos

Yes Peter.

What SAP suggested is the correct answer.

You must have to customize the functionality to support your custom assignment type.

The back end notification download ABAP class & Java classes have to be customized.

Thanks & Regards,

Roopa M.

Former Member
0 Kudos

Customizing or Development? We Think this two things are not the same, Customizing means, the program code is already written by SAP developers. We just e.x.: set different parameters value, like SPRO and Agentry Customizing Framework, but development means, we have to write the whole program code.

The Original SAP Work Manager Configuration Guide contains that What kind of assigment types can we set and how it works in a standard way. We don't understand,why not included this standard feature in Work Manager?

https://websmp205.sap-ag.de/~sapidb/012002523100004850182016E/SAPWM63_Configuration.pdf

How can we develop a standard *.jar files? What is the way that we will get the java Source code? We try to download it, but we see only the Work Manager 6.3 Deployment.


thanks,

Peter

former_member197782
Participant
0 Kudos

Hi Peter,

When you are changing the download assignment types you need to customize the existing functionality by copying the standard classes and BAPI's to Z name space.

In the same way you have to create the custom java package along with standard code.

The standard work manager java code will not be available in service market place and you must have to raise a request to SAP Team to get the source code and it is not free ware.

Your client have to pay for that. For more details please raise an OSS ticket to AGS Team and they can guide you in correct way.

Thanks & Regards,

Roopa M.

Former Member
0 Kudos

Without knowledge of the java source code, the standard code completion is a very hard project, almost impossible.

Returning the original topic, when will be ready the standard function, (Different notification assignment types) that the Original SAP Work Manager Customizing Document contains?

Former Member
0 Kudos

you have to request to SAP with explaining the requirement of new feature.

mark_pe
Active Contributor
0 Kudos

Just to clarify this statement:

"

The standard work manager java code will not be available in service market place and you must have to raise a request to SAP Team to get the source code and it is not free ware.

Your client have to pay for that. For more details please raise an OSS ticket to AGS Team and they can guide you in correct way.

"

Product Support does not handle Source Code request.  It is handled by the SAP Account Executive as you need to sign legal paper works to even access it. The SAP AE will request the SAP internal team to get it for you.  The software product support does not have a means give the source code to customer.

Regards,

Mark

Former Member
0 Kudos

hallo Mark,

OK, thank you,

but could you help regarding the original topic, when will be ready (or ready yet?) the standard function, (Different notification assigment types) that the Original SAP Work Manager Customizing Document contains?

mark_pe
Active Contributor
0 Kudos

Peter,

Hi. As far as the original request, this is what is required based on our notes.

1. When you do a Notification in the backend, you are required to make sure that a WorkCenter is associated to the Mobile user.  I believed Roopa said something about it above. Need you to check your HR items.

2. Once you have item 1 in your business, when you create your Notification in the backend (ERP), the header should state the Work center that is associated with this Technician.

3. In your picture above, you specified Assignment type = 5 for the filter. This is strictly Notification Header Work Center usage.  This means that the Employee number is not required.  This is also the reason that when you look at your code or log it states that the person id is blank.

"public void setParameters(SAPObject obj) throws Exception {
super.setParameters(obj);
this._notification = (Notification) obj;
Logger log = new Logger(this._user, "setParameters");
this.setFilterRange("IT_EMPLOYEE_ID_RA", "I", "EQ", this._notification.getPersNum()  <-- This returns blank as the filter is tied to the WorkCenter associated with the user, "0");
log.info("IT_EMPLOYEE_ID_RA LOW=" + this._notification.getPersNum());
log.info("done");
"

So your data above is probably stating that your user (mobile user name that is blanked out) is probably not associated with the workcenter that you are using.  You may need to share how you created your Notification in ERP and how you associate the user to the workcenter.  If the association is an issue then your user will not get anything.  Please also double check that you do not have "custom Development" tied to notification in ERP as if you do then you may need to use the BAdl/SMERP/MDO_PM_NOTIF_BADI  with GET_ASSIGNMENT_TYPE5 and modify it to fit your backend ERP.

That is what I can tell from the discussion above.

But you know from my colleagues statement above (Subash), he got that statement from the Java Code developer who supports the JAR file of SAP Work Manager.  So if they state that the Assignment type 5 may not be supported in Java then you may need to extend it as a system designer (Need to develop it.  Lots of lab example on how to do this in the SAP MOB310 class for Work Manager). The statement that I made above is based on the Mobile Configuration back end configuration requirement.

Regards,

Mark Pe
SAP Platinum Support Engineer

mark_pe
Active Contributor
0 Kudos

Peter,

I believe this discussion of yours is taken internally in our internal project group (consulting - you may be in calls with them as known today August 12, 2016) as it is a business requirement for your company.  So most likely both consulting and dev needs to be involved to make your project work. 

You may decide to update this thread as you own it on the results of the discussion.

Thanks for using SCN and reaching out to us.

Best Regards,

SAP Mobile Support Team

mark_pe
Active Contributor
0 Kudos

Peter and team,

As discussed internally, we may have a documentation error and I will try to check with our internal team of documentation to fix it (Add a note or disclaimer - making the standard not available to support it in Java or in the client and development needs to be done while the /SYCLO/CONFIGPANEL has features to state it does).

I will reach out to the key documentation team to address and fix it so that this confusion will be fixed.

Also as stated above, your issue is discussed internally with our SAP consultants. You may share the outcome of the suggestion and if it works for you.

With respect to the documentation, we thank you for pointing out this issue here -> https://websmp205.sap-ag.de/~sapidb/012002523100004850182016E/SAPWM63_Configuration.pdf

Regards,

Mark Pe
SAP Platinum Support Engineer

mark_pe
Active Contributor
0 Kudos

Peter and team,

The official documentation (in the link) will be re-written to state something like this on final form under the Notification Distribution Rules section:

"Note: Distribution rules for Notification are supported by Mobile add-on. However, you must also perform customizations in Java and the Agentry Editor to implement notifications."

With respect to more detail, the details are not included in the said SAPWM63_Configuration.pdf file.

Again, thanks for pointing this out to us.

For the other team or user, if you want to share on what you did in Java + editor, that will be a nice document to write up for SCN.

Regards,

Mark Pe
SAP Platinum Support Engineer

former_member197782
Participant
0 Kudos

Hi Peter,

When retrieving the data based on work center data your / login id must be assigned to that work center at IR02.

So please verify whether your pernr has been assigned to the work center in IR02 through HRMS.

Looking forward for your reply.

Thanks & Regards,

Roopa M.

Former Member
0 Kudos

This hard coded value will not make any difference.

I would suggest try to execute the bapi from se37 transactiona and check is it returning any values or not. also check is there any filter criteria for date or status?