SAP Rounds manager - notification type missing when adding notification to measuring points

[former_member198720]

Hello Experts,

We have deployed SAP Rounds manager 3.0 in the SMP dev landscape, successfully connected to SAP backend (PM module). We tested the app - Eg: the readings taken in measuring points from MELs, FLoc etc. they get updated in the SAP backend system after transmission.
But when we add a notification for any of the measuring points, we are not able to select the Notification types (dropdown is inactive), while there are upto 10 notification types in the backend. Similarly, the severity dropdown also shows only one option (Z - Z-priority) whereas there are more options in the backend.
Because of which we get error while transmitting notification "AddNotificationSteplet" - Notification type is initial.

I think, the standard app rounds manager is not able to fetch Notification type data from backend - may be any association is missing with NOTIF_TYPE, but we were unable to determine what?
Is this something to be resolved from Agentry project in editor, Agentry Add-on, SAP PM or ABAP?
We have done a similar standard deployment in another landscape but there we faced no issues in the Notification types.

Environment details:
SAP Rounds manager - SAPRounds300Deployment-143461_7051
SMP server version - SMP3 SP10
SMP SDK version - SMP3 SP10
Agentry client - 70.10.0.9
ATE - 70.10.0.9
DB - Oracle

Thank you
Sajan Mathew

[Former Member]

sajan.mathew2 Hi Sajan..I need to talk to you about your experience of Rounds Manager. Could you please share your number or email.

Thanks

Mandar

[former_member198720]

Hello Mark Pe, Chung Yu, Former Member, bill.froelich

Greetings!!!

Further with reference to this issue, we have a situation as described below. Could you please check if you can help us with something here.

Issue/Error: "Please enter valid priority" error during transmission while creating Notification from SAP Rounds manager app.

Standard Rounds manager behavior (that do not fit with the custom SAP ECC configurations): While trying to create a Notification in RM app, we get only one priority (which is "Z") under the priority type "PM" and Rounds manager is not fetching the priorities other than Z priority. We checked this in SAP ECC backend by adding two more priorities under the priority type "PM" and found that Rounds manager client fetched the newly added priorities 1 & 2 and also the Notification was successfully added from the app to the SAP Backend. This shows that the Rounds manager app fetches the priority values only from the priority type "PM" and tries to return the priority value (Z) to the type "Z5" type (as per the configuration done in our ECC system), but since there is no Z value for Z5 type it throws the "Invalid priority error".

Our Requirement: In our case, we want the Rounds manager app to fetch the priority values from the custom priority type "Z5" and also return the value back to the same type (Z5).

Requests:

1.Can you help us with some high level steps required to do this kind of customization.

2.We only have the Rounds manager project in Agentry Editor imported from Agentry.ini file and do not have the java source code behind it. Is there any changes that needs to be made in the Java source code for this requirement? or some tweaks in configpanel/Editor project and ECC is enough. Because we believe that this level of flexibility must be available with an SAP standard product and not be a kind of limitation to accommodate such small changes.

Thanks

Regards

Sajan Mathew

[former_member198720]

Hi Chung,

I am on leave right now. Will work with you once I come back.

Appreciate your help, thank you!!!

Sajan mathew

[former_member194451]

^{Hi Sajan,}

^{I am glad you were able to resolve the missing Notification Type per suggested by take care of the filter in the MDO}

^{Regard to "Priority", you would need to look into the screen set of Add/Edit notification per suggested in our last phone conversation. There is a rule that determine what to be included. I believe standard is "PM".}

^{Note: Since you have an incident opened for the "Notification Type" and "Priority" data missing. I will work with you going in the incident going forward.}

^Regards,

^{Chung Yu}

^{SAP Senior Support Engineer}

[mark_pe]

Sajan,

This error: while transmitting notification "AddNotificationSteplet" - Notification type is initial. <-- On past issues are tied to the QMEL table.

QMEL – Empty row causing Notification create to fail from the mobile client. This is preventing the process to work. You may need to delete a blank row.

See if this is your error.

Best Regards,

Mark Pe
SAP Platinum Support Engineer

[former_member198720]

Hello Mark,

This seems like one we wouldn't have found without you 🙂

1) Though development system, we are not allowed/authorized to delete this blank row (Yes, we found one). I will try getting this done going through approvals. Meanwhile, can you let me know if there is any alternative to delete / correct this row using any specific patch update or function module.

2) Also as mentioned earlier, We were unable to fetch "Notification type" and "Priority" data in the mobile client from the backend. Now we are able to fetch "Notification Type" by removing all related standard filters in the mobile add-on but when doing the same with "Priority" (removing all standard priority related filters on MDO-GET) still does not fetch any data other than "Z - Z-priority". Do you know from where/how we can bring this data to the mobile client?

Many thanks for your answer!

Best Regards

Sajan Mathew

[former_member198720]

Do anyone have any idea about this issue?

Regards

Sajan Mathew

[former_member198720]

Hi Chung Yu,

Thanks for your answer!

Yes, I have already checked the filter, It is set correctly. So that is not the issue here.

Please check the screenshot I have attached in my previous post. That is the Bapi used to fetch Notification type in Rounds manager app. We checked that Bapi in SAP Backend giving input parameters "Username" & "USER_GUID" which gives the result "No data found"

Best Regards

Sajan Mathew

[former_member194451]

Hi Sajan,

Did you check the filter in configpanel to make sure you have the correct filter?

Regards,

Chung Yu

SAP Senior Support Engineer

[former_member198720]

Please view the below screenshot, fetching data from the Bapi "/SMERP/PM_CTNOTIFTYPE_GET". Since there is no data found here, Notification Type field while adding notification in Rounds manager app is inactive.

As I said earlier. we already have notification types defined in SAP Backend but not sure what is wrong or where is the assignment missing that it is not being fetched by the app.

notif-type-result-no-data-found.jpg

Please let me know if anyone has the answer.

Thank you

Sajan Mathew

[former_member198720]

Below is the log collected replicating the error in Debug mode. Pls have a look -

2016/10/19 13:00:16.388: client is current

2016/10/19 13:00:16.388: + User=com.sap.SAPRM1.1-thomas

2016/10/19 13:00:16.388: + ANGEL Vine=3787207787

2016/10/19 13:00:16.388: Sending response, type 26

2016/10/19 13:00:16.388: + ANGEL Connection=10.**.**.**

2016/10/19 13:00:16.388: Attempt to send 4 bytes of data

2016/10/19 13:00:16.388: + Data Chunk=0

2016/10/19 13:00:16.388: Sending 4 bytes of data (with header)

2016/10/19 13:00:16.404: + WorkFunction=000000006CDFF2A8

2016/10/19 13:00:16.404: + User=com.sap.SAPRM1.1-thomas

2016/10/19 13:00:16.404: + User=com.sap.SAPRM1.1-thomas

2016/10/19 13:00:16.404: Received Business Object Transaction message 21 status changed to 'In Progress'

2016/10/19 13:00:16.404: + Application=com.sap.SAPRM1.1

2016/10/19 13:00:16.404: Received NotificationAdd Transaction

2016/10/19 13:00:16.404: Notification '192513778625' (current)

2016/10/19 13:00:16.404: MeasuringPoint '17192' (current)

2016/10/19 13:00:16.404: Applying transaction

2016/10/19 13:00:16.404: Transaction 'NotificationAdd': Transaction id (35) is not same as previous transaction id (208) => not a re-post

2016/10/19 13:00:16.404: Transaction 'NotificationAdd': Getting back end connections

2016/10/19 13:00:16.404: Transaction 'NotificationAdd': Beginning transactions

2016/10/19 13:00:16.404: Transaction 'NotificationAdd': Executing 0 DataState steps

2016/10/19 13:00:16.404: Transaction 'NotificationAdd': Executing 1 Update steps

2016/10/19 13:00:16.404: Transaction 'NotificationAdd': Update step 0: Run Always

2016/10/19 13:00:16.404: Transaction 'NotificationAdd': Executing Update step 'AddNotificationSteplet'

2016/10/19 13:00:16.404: + BackEnd=Java-SAPJavaConnection

2016/10/19 13:00:16.404: Backend step is configured as a Java Class; using Java class com.syclo.sap.component.notification.steplet.AddNotificationSteplet

2016/10/19 13:00:16.404: Using Java Class com.syclo.sap.component.notification.steplet.AddNotificationSteplet for AddNotificationSteplet

2016/10/19 13:00:16.607: + BackEnd=Java-SAPJavaConnection

2016/10/19 13:00:16.607: : 2 lines, 0 non-printing characters, 319 total characters

Exception while running transaction update step for step '': Java Business Logic Error: com.syclo.agentry.BusinessLogicException: AddNotificationSteplet - Notification type is initial

in AddNotificationSteplet at c:\agsrv_dev64\src\com.sap.mobile.platform.server.agentry\syclo\ag3\agent\javabe\AgentryJavaSteplet.h:298

2016/10/19 13:00:16.623: *** Exception 'Java Business Logic Error' caught, see events.log

2016/10/19 13:00:16.623: + Application=com.sap.SAPRM1.1

2016/10/19 13:00:16.623: + User=com.sap.SAPRM1.1-thomas

2016/10/19 13:00:16.623: + ANGEL Vine=3787207788

2016/10/19 13:00:16.623: Sending response, type 3

[former_member198720]

Hi Former Member, bill.froelich @michael.appleby @ mark.pe

Can you please help me here.

Regards

Sajan Mathew