Bdocs are in error status how to reprocess it?

[Former Member]

Hi CRM Middleware Experts,

We have error bdocs in CRM production system, number is huge like millions. What is the best way to clear it?

Business scenario: BUPA_MAIN, BUPA_REL, BUAG_MAIN bdoc type data is coming from ISU (Industry Solution- Utility) to CRM. But many million bdoc are in error status and which are there in system for last 6 months. So we have data inconsistencies in CRM.

I am thinking of reprocessing it but below question raised.

If one bdoc fails for particular BP then successive bdoc for that BP can go as success or will it struck in the system? If the later bdoc is success then reprocessing will over write the earlier data and it is not correct. Is this assumption correct?

Most of the bdoc are in yellow status (warning) and few of them are validation errors.

Any kind of help is much appreciated to clear all the bdoc

Thanks,

Surendar Potu

[jothivenkatesh_m]

Hi,

I have gone through the query. If a Bdoc is errored out for a particular BP, it is never a hard and fast rule that all the Bdocs are going to be stuck.

Say for example, if a BDoc carries a BP for creation in CRM system but it is errored out for some reason, then all the Bdocs carrying further information about that BP via Bdoc will be errored out since the BP has not been created yet in the CRM system. Now every other Bdoc carries different message identifier and there is absolutely no connection between the errored out Bdocs and the further Bdocs which are getting stuck.

Concept of yellow Bdocs are as follows:

1. When the Bdoc is waiting for a feedback from the connected system then it will be in yellow state.

2. If there are lot of yellow CSA* bdocs look at the SMQ2 queue and check if there are any queues which are stuck.

3. Usually subsequent queues will get stuck, when the predecessor has the same Queue name and this can be customised.

It is always better to monitor SMW01 on a regular basis. As for as the Red bdocs are concerned, the error has to be analysed. Since the stagnation has happened up until the last 6 months, it is better to do the request download for those partners and agreements. You cannot really check all the Bdocs that had errored out in the last 6 months. Monitor the Bdocs atleast once a day in SMW01 to avoid these scenarios in future.

I hope this helps.

Regards,

Venkat

[Former Member]

Thanks Madde for testing it.

Please let me know if you find anything in your research on message identifier?

Thanks,

Surendar Potu.

[Former Member]

Hi Madde,

I have tested for multiple Bdoc. If first bdoc fails also successive bdoc for same bp is processing as usual.. To stop this behaviour do we need to do any customization in CRM?

I am also looking in to each error, most of them are validatation error with phone number not correct and mail address is wrong.

Thanks in advance!!

Thanks,

Surendar Potu.

[Former Member]

hi,

This is very unusual, can you please explain with an example as in which scenario the successor BDocs are flowing inspite the first ones are not. what are the changes getting updated in BP with such behavior.

as far as re-processing of Bdocs, you need to first correct the master data as it seems most of them are incorrect field entry, if you need it in your business environment. Or you can just delete them in case you dont require anymore.

regards,

Madhup

[Former Member]

Hi Madhu,

Let's say first i have changed the address then bdoc is created and struck with error called " Bussiness partner is locked". next scenario we have changed the first name and last name of bp then it went as a success bdoc and changed the data correctly.

next scenario we have changed the address again and send it then address also updated . this is correct.

now we have reprocessed the bdoc which is in error,now it is reprocessed correctly and updated with old address. this is the problem (when i reprocess all the error bdocs).

thanks,

Surendar Potu.

[Former Member]

Hi Suren,

As per the standard method, this shouldnt happen, as even i tested the same thing last time, and it dint allow any changes to the BP, till the initial Bdoc was process.

This also depends on the Bdoc status which obeys its flow in CRM and the concept of acknowledgement and sending sites and more other parameters of Middleware.

However, for your quick solution, reprocessing the BDocs might cause inconsistencies sometimes, as you are experiencing.

If you do not need these BDocs, why dont you delete them.

You can do this by scheduling a report in background:

Report: smo6_reorg2 (new version of smo6_rorg)

Here specify the date range of which Bdoc to be deleted.

Regards,

Madde

[Former Member]

Hi Suren,

I was anxious on your scenario and gone back and tested few things on my end, well yes, if there is a Bdoc failure for a BP, and you try and make any changes, the generating changes will only flow if they have a different Bdoc Messenger Identifier.

This means changes to BP will flow to R/3 system, if they have got different Bdoc Messenger Identifier.

What s the importance of Messenge Identifier even I am not aware, need to research further.

But yes, if the changes which you are making lies in the same messenger identifier, then delta changes will not flow unless you clear the initial Bdoc of it.

Hope this makes some sense.

Regards,

Madde

[rohit_sharma2]

You need to find out about the validation errors that have cause the BDocs to enter an erroneous state.

[Former Member]

Hi,

If one bdoc fails for particular BP then successive bdoc for that BP can go as success or will it struck in the system? If the later bdoc is success then reprocessing will over write the earlier data and it is not correct. Is this assumption correct?

First Question : Response

If a Bdoc fails for one BP, the successive bdocs for that BP will not flow unless you clear the inital one.

Second Question: Response

Unless you dont clear the inital Bdoc, later Bdocs will not get processed, so you need to re-process the inital one.

As for clearing of Bdocs are concerned, it depends the kind of errors they persist, you need to first rectify those errors based on the type, and then you can reprocess all the bdocs from SMW01.

Hope this helps,

Madde