Skip to Content

Source

Note https://service.sap.com/sap/support/notes/1566108

Problem:

We need to update the status of OSS message to check if there is any problem with the connection from SAP solution Manager 7.1 and SAP to sync message

Process:

The process that we had use before on old release before 7.1, with program RNOTIFUPDATE01, is now obsolete, and don’t work (really don’t know the moment of the change, I think that I use old report before SP8 and it works). On Solution Manager 7.1 for update current message that we sent to SAP on VAR scenario ( used on PCE, CCOE, RunSAP certification process and for some direct sap customer ) if we found a synchronization problem on job REFRESH MESSAGE STATUS we can use a new report.

Report:  AI_CRM_IM_UPDATE_FROM_SAP

After finish we have to check application log trough SLG1 with “SOLMAN_INCIDENT_UPD” log sub-object

Step by Step:

Lets go to see steps by steps how we can check errors on a single message update form SAP:

1.- We have to run the report “AI_CRM_IM_UPDATE_FROM_SAP” from SE38 transaction.

/wp-content/uploads/2013/09/cap1_283828.png

2.- On the selection screen we have to fill mandatory for a single message that fields: “sap customer number”, “installation number”, “message number in SAP OSS” (remember to include the middle part of the SAP message); and un-flag option “Include confirmed message” that is flagged as default; and execute the report.

/wp-content/uploads/2013/09/cap7_283886.png

*On the image bellow the SAP message number is arrowed, I don’t know what is the first number and the last part of the message also don’t know exactly but I suppose that is for current year. 😉

/wp-content/uploads/2013/09/cap2_283880.png

* check how is filled selection screen

3.- After report finish the synchronization, you will see a popup that tell you the sub-object to find logs in SLG1 application.

/wp-content/uploads/2013/09/cap3_283881.png

And a simple result of the synchronization process (here you can see quick if the sync found problem or not)

/wp-content/uploads/2013/09/cap4_283882.png

4.- Then, because we have found problems, we have to run SLG1 transaction with sub-object “SOLMAN_INCIDENT_UPD” and we will be able to see if on the update process the detailed list of problems and errors.

/wp-content/uploads/2013/09/cap7_283886.png

If we see some error on the SLG1, we can see more information about the message; it’s hard to find the problem here but it’s a good point to investigate the root cause of the problem.

/wp-content/uploads/2013/09/cap6_283884.png

That’s the detailed result of the synchronization from OSS, if you need more information about the job that update all message you have to check SAP Note:

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

Information from that Note about refresh message Status:

“…AI_CRM_IM_UPDATE_FROM_SAP report (Job REFRESH MESSAGE STATUS): This report is used for incident management in solution manager, to retrieve or replicate SAP messages. It replaces for ST 7.10 the old report RNOTIFUPDATE01 (see note 1566108). Scheduled hourly, since ST710 SP1. Since ST710 SP5 this job is scheduled in the “IT Service Management”, “Incident, Problem & Request Management” specific setup scenario…”

Regards,

Luis

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply