Bdocs stuck....

Hi Guys
I am struggling with some serious bdoc issues, I have a number of Bdocs that are stuck,
Most of the Bdocs are of the type BUS_TRANS_MSG and they are in the intermediate status
"BDoc stored before update task" however I can not find a way to release them I have tried to reprocess them but they are still failing and get stuck in the same state. How can I find out what the problem is?
There is a trace button but it is not active, how do I activate it?
My first thought: There is a number of queues in SMQ2 and I have tried to activate them but the message back is that the queue is registered and can not be activated, however they have been running for several weeks without anything happening... so something is def. wrong...
Any ideas on how to analyse the problem with all the Bdocs?
FYI, These BUS_TRANS_MSG errors inturn cause the contracts/orders to be in status "being distributed" and therefore can not be updated and that in turn causes other bdocs to get stuck such as the BEABILLDOCCRMB that is not able to update the contract....
PLEASE advise, i will for sure give points to good answers.
/Mr Hut

Yes I seem to have a number of terminations, however
User         Date       Time     TCode                I n f o              Status
KONVERTERING 2008.11.26 09:50:07 SE38                                         Error (no retry)
KONVERTERING 2008.11.26 09:46:43 SE38                                         Error (no retry)
KONVERTERING 2008.11.26 09:45:45 SE38                                         Error (no retry)
KONVERTERING 2008.11.26 09:39:12 SE38                                         Error (no retry)
KONVERTERING 2008.11.26 09:33:41 SE38                                         Error (no retry)
KONVERTERING 2008.11.26 09:32:03 SE38                                         Error (no retry)
KONVERTERING 2008.11.26 09:30:27 SE38                                         Error (no retry)
KONVERTERING 2008.11.26 09:28:41 SE38                                         Error (no retry)
KONVERTERING 2008.11.19 08:47:50 SE38                                         Error (no retry)
CONTROLM     2008.11.05 17:28:15                                              Error (no retry)
CONTROLM     2008.11.05 17:28:10                                              Error (no retry)
CONTROLM     2008.11.05 17:28:05                                              Error (no retry)
CONTROLM     2008.11.05 17:28:00                                              Error (no retry)
CONTROLM     2008.11.05 17:27:54                                              Error (no retry)
CONTROLM     2008.11.05 17:27:48                                              Error (no retry)
CONTROLM     2008.10.31 09:54:00                                              Stopped (no retry)
CONTROLM     2008.10.28 02:18:21                                              Stopped (no retry)
CONTROLM     2008.10.28 00:40:21                                              Stopped (no retry)
How should I go forward with these? They seem to belong to a number of dumps, the causes to the dumps have been solved but how do I resend the Bdocs? All Bdocs are still stuck and gets stuck if i resend them but there is no new entry in SM13 after i have tried to resend it.
Any ideas?

Similar Messages

R/3 to CRM product replication Problem

Hello Experts,
I am facing middleware issue.
We have sap CRM and R/3 systems are there.
I could replicate all the products from R/3 to CRM system except one product.
I checked that product in R/3 there that is available but it is not available in CRM system.
Please let me know hoe to replicate only that particular product from R/3 to CRM system.
Thanks

HI
Things you need to do
i. See if there are any BDocs stuck in the SMWO1 for the product in question. if none then do the below
i. Create an explicit download request for this product. Go to TCODE R3AR2. Give a name starting with Z ; Adapter object would be MATERIAL. Then click on request detail and enter the following
Table name : MARA
Field name : MATNR
incl/exl - INclusive deined set/array
option - Equality (=Low)
Low = Enter your product number that you want to download from R/3.
SAVE
ii. Go to tcode R3AR4 and enter the object created in previous step. Enter source site and target site.
SELECT EXECUTE.
Now see if the product is downloaded or not. If not, check BDocs and queues.
please award if it helps.
Sandy

Middleware problem -Outbound queue is stuck in SAP R/3 system with message

Hi Middleware gurus ,
We are stuck with a serious issue . We are trying to download Business partners from SAP R/3 4.6c system to SAP CRM 5.2 system using CRM Middleware
Previously we did a successful Initial download of 2 Business partners from SAP R/3 to CRM . Their BP numbers in CRM are 001 and 002 . The Delta load is working fine for the both the BPs which are already downloaded
Now , the real problem is when we are trying to download a new Business partner . When we set the Filter ( BP no 003 ) in MW adaptor object CUSTOMER_MAIN and start the Initial load again , we see that the Outbound queue is getting stuck with message STOP .
There are two queues generated in SAP R/3 system with names MASS_CRM_CUSTOME and R3AD_CUSTOME . The status for both the queues is STOP and when go for details it mentions sapsuck ..SAPMSSY1 -Message no. SR 053.
Even we checked the txn SMW01, the Bdocs message is "Recived ( Intermediate state) " for Bdoc type BUPA_MAIN.
We really dont as to why the Initial load worked fine with 2 BPs and later when want to do more BP Initial Load the Outbound queue is getting stuck
Also , by unlocking the 2nd queue R3AD_CUSTOME we are able to release it , but the first queue MASS_CRM_CUSTOME* is stuck
Please help us urgently
Regards
Dinesh and Ritvij
Email : [email protected]
Mobile -+91=9704933315

Hi Praveen and other Middleware gurus,
We checked on this . Actually the RFC is used for connecting to SAP R/3 system.
We also raised an OSS message on this and found a reply that in transaction CRMM_BUPA_MAP, we can map the required BP . But the SAP support guy recived an error received the error:
An RFC link is not maintained in the Middleware
Message no. CRM_BUPA_MAPPING051
We have set the RFC link , but still the problem continues!!!
Please help further..
Regards
Dinesh and Ritvij

Search criteria for insert/update bdoc

Hi All,
In our set up we have ecc to crm replication of BP. If one goes and checks the extension data of a stuck bdoc it has an Object Task- Insert or Update.
Can someone help me with search criteria so that i can pull out bdocs which have an Insert as the Object task ??
We have search criteria for errored/intermediate state bdocs; for inbound vs outbound; bdoc type etc etc..
Need one based on Insert/Update Task so that any new data replication if stuck with its very first bdoc( Insert type) can be immediately queried.
Regards
Abhinav

Hello Abhinav,
I do not think that we have such a search criteria to search for BDocs based on the Task Type, which comes under the
data part of the BDoc.
One alternative way is to find out in which table these data gets stored and write a program to fetch the revelent Bdocs.
Hope thisl helps!
Best Regards,
Shanthala Kudva

Inbound Queues stuck with RFC errors

Hi Experts,
Greetings for the Day !
We have BDOC related issue and we need your expert help ASAP in resolving the same.
We ahev a few BDOCS lying in intermediate state in transaction SMW01, which we found using BDOC monitoring on daily basis. When we check the same in SMQR - inbound queue, we found that the queues are stuck with an RFC error message.
We are re-activate these queues to actually resolve the intermediate bdocs. But, my query is
1> The raeson for getting these BDOCS in intermediate state & stuck queues
2> A permanent resolution for the same.
Please help and let us know if you need more details.
Regards,
Kanika

Hi Kanika,
RFC error can be due to a bad connection as well. If the server is down, there might be a problem in communication with the connected system and the queues will not be processed further. You need to reactivate or unlock to get the queues processed.
But if there are any specific errors for which the queues are stuck do state the same, so that we can look into an actual resolution.
Regards,
Venkat

XIF or BDoc Trigger even with errors in Business Document

Hello Experts,
I am stuck in an issue regarding BDoc trigger. My query is as per my understanding, if a business document like Sales order or Opportunity is in error but is saved, there is no BDoc triggered. Please correct if I am wrong.
My actual Requirement is to trigger BDoc and thus XIF IDOC if Opporutnity is saved even with error.
Do we have a method for this apporach.
Please assist.
Thx,
Ravi

Hey Luis,
Thanks for your assistance.
I assumed this functionality will haunt me. Can you suggest any workaround. The XIF IDOC will not get send also because internally they are connected to BDoc adapter itself.
Do we have any method to trigger XIF IDOC by some logic etc.
Thx,
Ravi

BDOC Error : "BDoc stored before update task (intermediate state)"

Hi Experts,
I have stuck BDOCs under BDOC type "BUS_TRANS_MSG" and the error msg as "BDoc stored before update task (intermediate state)". The error occurs when BDoc Message was not written to qRFC queue. I checked the update tasks in transaction
SM13 and could find the entries there. I opened one of the entry and was able to spot the error in one of the function module.
The error was encountered at some later point in time and is been fixed. I now want to re-send the update so that the new update is written and the BDOCs are processed.
Kindly guide me through the steps that need to be performed in order to re-process the BDOCS.
Thanks,
Chaudh

Hi,
BDocs were stuck at time when we really had a problem; now the problem is re-solved. I have checked SM13 we have entries highlighting the problem, but i really don't know how to re-update the error entries in SM13.
I believe once that is done then i might possibly be able to re-process the BDOCs in SMW01.
Thanks,
Chaudh

BDocs stay yellow - status I02 Written to qRFC Queue (intermediate state)

We upgraded our system from SAP CRM 7.0 EHP3 SP3 to SP4.
Now all the BDocs in smw01 stay yellow. I can manually reprocess them, then they become green. There is no error message and there are no dumps in st22.
The CSA* queues are registered. The scheduler says "inactive" (and briefly goes to active when saving a business partner, product or transaction, as it should).
The CSA* queues relevant for each "stuck" business partner, transaction or product is in status "STOP".
There's a note, 1593693 - BDoc's in state I02, but it doesn't help. We don't have a problem with the number or load of the RFC processes (as far as I can tell), there is very little going on on the system, right now I am the only one logged on) and the queues are not in status READY, either.
MW_CHECK says "All post-processing steps are done."
GENSTATUS counts 0 errors or waiting.
MW_MODE is on, of course.
smw3_00 is empty (which it was before the SP installation, too).
The CRM is not connected to an ERP system, it sends búsiness partner and transactional data via the XIF adapter (via web services). Which, up to now, worked just fine.

I was given the solution: Use transaction smq2, search for CSA*, click on the queue, click the unlock button. That worked.

Reg:SMQ2 failed BDocs in CRM server

Hi SDNites,
We have a few failed BDocs in our CRM system with the system status SYSFAIL,when I reset the status manually and try to re-process the LUWs,it says "Function module does not exist or EXCEPTION raised"
there are several queues in SMQ2 with the same status,kindly guide me thru so as to process the BDocs.
Rgds
Venu

HI,
SYSFAIL
A serious error occurred while the first LUW of this queue was being executed. The execution was interrupted. When you double-click on this status, the system displays an error text. For more information on this error, see the corresponding short dump in the target system (transaction ST22). No background job is scheduled for a retry and the queue is no longer processed. To solve the problem, information from the affected application is required. See SAP Note 335162 for the error text "connection closed".
if you normally can reprocess the queues in SMQ2 and the queue is running ok, then I think you could schedule the batch job in background.
Just create a variant with the part of the queuename (for example SI_ORDER*) in queuename-field.
But perhaps you are not meaning the queues but the Bdocs in SMW01? Is it the queues in SMQ2 och the Bdocs in SMW01 that you have to reprocess every day.you can schedule the background job to process the queueus automatically
You find detailed information about qRFC status in SAP Note 378903
Transaction SMW01 allows you to display the data of a BDoc.By means of transaction
SMW02 it is possible to access the display of the processing status of individual BDoc from
the BDoc types themselves.
Search for special error situations per Bdoc-ID, date, Site ID, message ID ...,
u2022
Transaction SMW01/SMW02 (BDocs in error state)
If you could check for some of the Middleware notes or RFC Queue notes, there is a background job that you can schedule in CRM which shall automatically try to re-process the queues at a specific amount of time. This is the best approach for re-processing queues if they are stuck say due to RFC Destination failures etc.
Regards
Sreedhar Reddy

Inbound Stuck Queue in the SMQ2

Hi,
One of the Q got stuck in the Inbound of the CRM system.
It is showing the system status as "Running".IT has been in this staus for the past 2 days.
When I try to activate it is giving Message"The queue is registered and therefore cannot be activated"
The Q is giving Dump Error "Exception condition DELETE_ERROR raised
When I chekced the Bdoc SMW01 the BDOC is in "Yellow Status".
How can i process this queue.

Implement SAP note 758677 for this. This exactly deals with your issue.
This Basically speaks about scheduling 'RSQIWKEX' for inbound and 'RSQOWKEX' for outbound queues.
Also, you need to set the parameter 'QRFC_Restart_ALLOWED' to '1' in the transaction 'SXMB_ADM' -> Integration engine. Its in the runtime dropdown menu.
Note : without this parameter being set this will not work.
Thanks,
Karthik
Edited by: Karthik Rangaraju on Oct 1, 2008 2:13 PM

Error- Update Bdoc status failed- R3AD_Accounting

Hi ,
We are trying to replicate service order from CRM to r/3, after saving a service order in SMW01 it shows error "No r/3 upload"
In SMQ2 there is a queue R3AD_Accounting with status SYSFAIL stuck with the error message "Update BDoc status failed - BDoc not found"
In R3AC1 the object Accounting does not have any entries for tables or initial flow context.
Please let me know where we can maintain the entries for this Adapter object-Accounting.
Regards
Prathiba

Try releasing the queue, might be a temporary problem.
If not, check out the lockings in transactions sm13 (or sm12: I'm not sure).
Michael.

Inbound stuck queues

Hi guys,
There are a few inbound stuck queues in the CRM system with the error SYSFAIL.
When we checked in smw01 the error is"The transaction getting locked by the user"
When we manually activate the queues the queue gets processed out.
But we need to manaully go in every day to reprocess these queues .any idea of automatically reprocessing these stuck queueus.
Thanks,
Krishna

Hi Krishna,
You can reprocess those queues automatically, but again I would suggest the administrator should manually go and reprocess it as SAP standard don't recomment the autoprocess of the Queues/ BDocs, because this may lead to inconsistency.Again in the end decision is ours but SAP would never take responsibility if anything goes wrong as of SAP standard practice is not followed.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

BDOCs in status E01 - Technical Error

We are using CRM 7.0 with service order.
We have BDOCs that created automatically after creation of service order or changing in BP details and got stuck in the system and were not processed (SMW03) .
The BDOCs types:
BUPA_MAIN
BUS_TRANS_MSG
These BDOCs entered into queues in SMQ2 in status ready.
In order these BDOCs will be read automatically, we registered the queues which started with CSA* in SMQR.
Unfortunately, the BDOCs still not processed and now in status E01 u2013 Technical Error (incomplete).
The messages are for each type (BUPA_MAIN and BUS_TRANS_MSG respectively) are:
u201CCould not determine module name: BUPA_MAIN GENKEY: REP_GET_RECIPIENTu201D
u201CService that caused the error: SMOH_REPLICATION_WRAPPER_MSGu201D
Could not determine module name: BUS_TRANSACTION_MESSAGE GENKEY: REP_GET_RECIPIENTu201D
u201CService that caused the error: SMOH_REPLICATION_ERAPPER_MSGu201D
It is important to mention that these BDOCs were not deleted in order not damage data that suppose to be uploaded to the BI.
Due to security issues, we cannot provide connection to the system.
Please advice
Best regards,
Hanoch Aharoni

Hi Hanosh
Please see bleow, this is an extract from very helpful document attached to note 768503 for the E01 bdocs status:
Description
Technical error. If any of the flow services fail a technical error is raised. Possible reasons
for that error are:
- Data inconsistencies (e.g. between CRM and CDB)
- Implementation and programming errors
- Missing functionality (implementation problems)
Inbound
s-flow
(SI1)
Detection:
Select BDoc message, click button u2018Errorsu2019 and u2018Classical Datau2019
Possibly the inbound s-flow definition (transaction SMO8FD) is not correct
(services do not exist or have syntax error) or the rejection handling in case
of validation errors is not correct.
Solution:
- If no validation errors and no receiver errors exist, retry to process the
message. Otherwise (if no retry possible) correct the error, send the changes
from the sender site (usually Mobile Client) again if possible or request the
data from the leading system to the different receivers and mark the original
failed BDoc message to u201Cdeletedu201D.
Inbound
m-flow
(MI0)
Detection:
Select BDoc message, click button u2018Errorsu2019:
- No validation function defined for BDoc type
- Technical error occurred: Service (usually validation service), BDoc type <>,
BDoc <>
Solution:
Check in table SMW3BDOCIF if the validation module is entered for the
BDoc type. If no retry is possible correct the error, request the message from
the sender system and set the original failed BDoc to u201Cdeletedu201D.
If the error occurs during the call of the validation module, start the
debugging mode, restart the BDoc processing and put a breakpoint at the
validation module. This requires knowledge in the implementation of the
validation module (and application logic). Look for notes related to that
function module, if this is a SAP standard function.
E01
Outbound
m-flow
(MO1)
Detection:
Select BDoc message, click button u2018Errorsu2019:
- Technical error occurred: Service <>, BDoc type <>, Message <>
- Service that caused the error: <>
Solution:
Find a solution to the errors that occurred, for example through SAPNet Note
search or opening a SAPNet problem message on the corresponding
application component. The right application component can be found in the
corresponding properties of the package where the service is implemented
(use transaction SE37 to display the attributes of that function module).
Possibly there is something wrong inside the Mobile Bridge or in the following
services of the s-flow (like CDB update).
Re-process the message (this is allowed for testing purposes; be careful in
the case of a production system, especially if the data in the BDoc message
is not current) or request the data from the sender or from the original system
(this is usually possible for master data but not always for transactional data).
==================================================================
Best regards
Christophe

Procedure To Enhance BDoc : BUPA_REL

All,
I'd like to know the steps (in detail) involved in enhancing the BDoc: BUPA_REL. Typically, I'll be synchronizing data between SAP CRM and SAP R/3 systems whenever there is a change in the BP Relationship screen.
Regards,
Ravi

Hi Martin,
Here is the steps to debug the BDoc from one system to other.
1> Go to Tr. SMQS and deregistor the R/3 System .
2> reprocess the BDoc is Tr. SMW01, and you will see one stopped queue in the CRM outbound Tr. SMQ1.
3> Press the debug button and you will find yourself in R/3 system and from here onwards you can debug the R/3 inbound.
Do not forget to registor the R/3 system which you have deregistor in step 1 otherwise all the queues will get stuck in CRM outbound.
<b>Reward points if it helps!!</b>
Best regards,
Vikash.

Bdoc state - Received (intermediate state)

Hi experts,
Can you please help me with this. We've just found out that we have several bdocs with state "Received (intermediate state)" in middleware. They said that if these are in this state for quite some time, we need to reprocess it to prevent any future problems. When I choose one and click on Show Bdoc Msg Errors/Receivers, it only says "No receivers or error segments for Bdoc message found."
Can you please let us know how to clear these? I'm providing below two bdocs on these state that may help you understand the problem.
1.
Bdoc state description: Received (intermediate state)
Bdoc type: BUPA_REL
Flow context description: mBdoc Validate
Send date: 01.09.2010
Send time: 19:01:06
Sender site name: (This is our ECC box)
Queue name: R3AD_CUSTOMExxxxxxxxxx (x > customer number)
User (Creator): MWRFCXXX (x > our ECC box)
2.
Bdoc state description: Received (intermediate state)
Bdoc type: CND_M_SUP
Flow context description: mBdoc Validate
Send date: 09.02.2011
Send time: 15:43:04
Sender site name: (This is our ECC box)
Queue name: R3AD_DNL_COND_A594
User (Creator): MWRFCXXX (x > our ECC box)
Hope you can help us here. Thanks a lot!
Kind regards,
Mike

Hi,
Go to transaction R3AR3,Are all your requests still there.IS there any queue stuck in smq2 and SMQ1.If there is nothing stuck in SMQ1 or SMQ2,then i think for you Bdoc type BUPA_REL,for all those queues in intermediate state there is no number found for the range which you used to create request for Partner relationship.
Regards,
Arya

Bdocs stuck....

Similar Messages

Maybe you are looking for