Monitor for Processed XML Messages

[Former Member]

Hello Experts!

We have been using SNC for about a year. We have approximately 480 suppliers set up. We use use SNC to communicate with our Suppliers PO and PO Changes using ORDERS05 as well as Non-actionable forecast (OFM) using PROACT01, and Suppliers create PO Confirmations (ORDERS05) and ASN (DELVRY05) documents. We do not use SAP ECC, instead we have about 5 different back end systems who send/receive the IDOCS.

I have been using XSMB_MONI and SLG1 to monitor application and system failures. As you can image, as we bring on more suppliers and more plants, the volume is getting out of control. Usually the errors relate to master data, such as UOM conversion errors, missing Product, missing TL, etc). Is there an easier way to display the errors in a format that allows me to see the error details without going to the screen and viewing each error line by line?

I have tried using the alert monitor, but many of the items are not in alert monitor. I heard something about using CCMS, but I have been unable to find any information on what to set up in CCMS. There has to be a better way than the on-screen tools I am using. The volume is creeping higher and higher.

Help is greatly appreciated!

[Former Member · Accepted solution]

Hi Michele,

This is a really good question because we faced the same issue before..

We have done a big implementation for Unilever Asia which covers more then 30 countries, 2000+ users and daily sxmb_moni messages were more then 10.000+. Both collaboration scenarios (SMI+VMI) were included in the project.

In this situation, sxmb_moni was not very helpfull for monitoring activities. It has started to create impact on daily transactions because of small master data relevant failures. Also alert monitor doesnt have a very good performance to measure these issues out.

According to this problem, we have copied the source code of sxmb_moni and created another program called zxmb_moni.

We have added few columns in the report like customer number, supplier number, company code (Business partner) and few others to have an initial information about the error message.

In addition to that, we have created special error numbers and added them inside inbound BADI's for the message where can see the summary of the error. As an output, we figure out these master data relevant problems and taken proactive action like automatic CIF jobs. Another job is also set to run on hourly basis to re-run the failed messages.

As a result, SAP provides standart solutions like alert monitor and message monitoring (sxmb_moni) but in real life its not helping a lot in rush environments. Just some Z report development and pro-active actions can help you to struggle this issue.

Regards,

Selim

[RahulHanda]

Hi Michele,

Of course this is a hectic task to gather such information when you have thousands of records to process on daily basis and business is expanding. Just as an update for yourself some reports are available in SCM itself. Go through the reports and cross check in simulation version. Check below SAP note for the same:

1325288 - Reports for Correcting Failed Publication of XML Messages

Let me know if it really helped.

Regards

Rahul

[Former Member]

Rahul, Thanks for the note, but this was already applied in our environment. It is important for me to note here that we have integrated non-SAP systems into SNC, so many of the ECC tools do not cover the non-SAP sites we have integrated. The Alert Monitor does not cover every scenario, but we are woking on figuring out how to work with the tools that we have.

I appreciate all the feedback, but so far, the best case for us is to use something similar to what Selim references. I expect this to become more of an issue as we expand to other regions and begin to have trouble identifying which team should handle which message failures.

Seems like SAP could do better than what they have for managing large volumes of transactions which could have errors. As we add more regions and expand the footprint of SNC, I will update this post.

[RahulHanda]

Hi Michele,

Thanks for sharing more information about your system landscape. We have developed such a report in ECC on the basis of failed IDOC's.

What we have done is, first we have written logic in different message type itself to cross check certain parameters or business functions when IDOC's are being posted. Example if I am posting an IDOC for incoming invoice, check whether invoice qty. is equal to GR qty. If that's not the case IDOC would fail with message "Invoice qty. greater then PO GR qty". I assume you also have the same and see the reason's why IDOC's failed.

Now if we go in this failed IDOC the status would be 51 with relevant message.

So on the basis of the same we developed a custom report which would pull all IDOCs (could be failed/passed, depending upon what you want to see but with filters) with message 51. When executed it would show supplier, PO number, message for failed IDOC (basically reason) and all other necessary information.

I hope this helps you in defining your custom report.

Regards

Rahul

[Former Member]

Hi Rahul,

I would like to join the conversation again at this point.

SCM integrations are much more different then the ECC. Firstly SCM SNC works generally on XML messages. Even idocs are used but issues are mostly coming from master data part. The example which you shared is much more different compared the basic SNC integration problems.

For example; if there is a problem related to GR & Invoice quantity then it should be checked at "Validation Profiles" to ensure that functionality is working as required. Of course failed message statuses are even exists in XML integration but main problem is generally much more different then which is seen at the surface. Once there is such an issue then you should dig the problem much more detailed where needs to analyzed for end to end integration process.

Also there are standard reports which can re-execute failed IDOC/XMLs in both SCM or ERP environment.

Regards,

Selim

[Former Member]

Hi Michele,

As you are using only POC, you can use alert monitor.

We have an alert: 7035 which will get triggers when ever PO related xml fails in SNC system inbound.

7035

Exception during validation of purchase order

PO

SAP SNC detected a problem during validation. This alert is a general validation alert.

This alert you can use effectively by logining as customer and check what are the PO's failed for that particular customer.

Hope this helps you.

Br//

Rakesh G

[Former Member]

Hi Michele,

We have also simialr monitoring activity in SXMB_MONI, to simplify our work we have set up the variants to suit our monitoring activity for each process. Example

For PROACT01 message we have a variant as below :

Length of Output List - 200 by default (you can change as required)

Status group - 4 - Errors

Date - Enter the required date range

Receiver interface name - ProductActivityNotification_In

You can also use similar variants depending upon the incoming messages, this will surely help to some extent.

Regards,

Jagadev