BDOC Stored before update task error

Question

Hi Experts,
I am using FM CRMXIF_PRODUCT_MATERIAL_SAVE to update one of the custom aatributes in COMMPR01.
once i run this FM i see an entry of bdoc in SMw01 with the below error
"BDOC stored before update task(intermediate state).
I checked ST22 and i saw no dumps, i checked Sm13 and i didnt see any update tasks. Cananyone help me?
Thanks!

Answer 1

HI Divya,
BDoc Message was not written to qRFC queue, yet. Search for update tasks in transaction
SM13. The sender creates a BDoc message to post data to the receivers. The application
calls the messaging flow.
Detection:
Check if there are any update terminations which occurred in the update task
by using transaction SM13. Check if there are inbound messages related to
that outbound message, double-click u2018Original BDocu2019 field to display the
original inbound message. Typically the inbound message (s-BDoc in flow
context SI1 or m-BDoc in flow context MI0) is already on a final state F02, i.e.
the validation was successful but the asynchronous update failed. The
original inbound message in final state might have been already reorganized.
Solution:
Solve the problem with the open update tasks and then execute them again
in SM13. Check whether after succesful reexecution in SM13 the BDoc state
has been changed.
If not, or if you donu2019t find any open updates, but you do find a corresponding
original message, proceed as following:
· Variant 1: Try to reprocess the inbound message to check if the newly
created outbound message has also status I04. If BDoc is processed, no
retry of the failed BDoc is allowed. Set the message as deleted.
Reprocessing the related inbound message is sometimes not possible,
because the state is final. In this case copy the inbound message using
transaction SMW19 and set the new state of the copied message to I01.
Then you can reprocess it.
· Variant 2: Use the solution from SAP notes 876855 (CRM 3.X) or 835761
(CRM 4.0) to convert the inbound s-BDoc into an error state E09.
Advantage is, that in this state the inbound message does not get
reorganized. More important, it also allows you to restart the inbound
processing after the error situation has been resolved. However, in that
case you need to delete the already pending update tasks from the
previous run in transaction SM13.
When there are no open update tasks anymore, check whether the data
changes according to the inbound BDoc message have actually been posted
to the CRM online application tables. If the changes are present (i.e. a new
application object was succesfully created), you should not use variant 2,
because you might get a problem of posting the same data again (i.e. getting
an "insert duplicate record" situation).
For more info about error analysis. please refer to
http://saptricks.com/wp-content/uploads/2010/05/BestPractice-BDoc-Analysis-V2.pdf
Cheers, Satish