The document discusses an issue with business documents (BDOCs) hanging in yellow status when creating transactions or making changes to business partners in CRM that need to be replicated to R/3. The yellow status means the documents were sent to R/3 but not yet confirmed. It is suggested to check that the transaction types and item categories match between the two systems. Additionally, registering the queue name in transaction SMQ2 in CRM and ensuring the BTE is maintained in R/3 table TBE31 for sales transactions may help resolve the issue. The discussion continues with attempts to set the proper source and receiver for initial loading of the object to replicate the data properly between the systems.
The document discusses an issue with business documents (BDOCs) hanging in yellow status when creating transactions or making changes to business partners in CRM that need to be replicated to R/3. The yellow status means the documents were sent to R/3 but not yet confirmed. It is suggested to check that the transaction types and item categories match between the two systems. Additionally, registering the queue name in transaction SMQ2 in CRM and ensuring the BTE is maintained in R/3 table TBE31 for sales transactions may help resolve the issue. The discussion continues with attempts to set the proper source and receiver for initial loading of the object to replicate the data properly between the systems.
The document discusses an issue with business documents (BDOCs) hanging in yellow status when creating transactions or making changes to business partners in CRM that need to be replicated to R/3. The yellow status means the documents were sent to R/3 but not yet confirmed. It is suggested to check that the transaction types and item categories match between the two systems. Additionally, registering the queue name in transaction SMQ2 in CRM and ensuring the BTE is maintained in R/3 table TBE31 for sales transactions may help resolve the issue. The discussion continues with attempts to set the proper source and receiver for initial loading of the object to replicate the data properly between the systems.
The document discusses an issue with business documents (BDOCs) hanging in yellow status when creating transactions or making changes to business partners in CRM that need to be replicated to R/3. The yellow status means the documents were sent to R/3 but not yet confirmed. It is suggested to check that the transaction types and item categories match between the two systems. Additionally, registering the queue name in transaction SMQ2 in CRM and ensuring the BTE is maintained in R/3 table TBE31 for sales transactions may help resolve the issue. The discussion continues with attempts to set the proper source and receiver for initial loading of the object to replicate the data properly between the systems.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1of 6
Nadh R
Apr 29, 2008 8:02 AM
Hi Experts, Our Client is using CRM 5.0 and R/3 4.7. Integration was done through middleware and initial load of Customizing data, Master data( Customer master and Material master) was finished. In Administration console( Transaction code- SMOEAC), R/3 site was subscribed for 'All Business transactions(MESG)' and 'All Business Partners(MESG)'. If i create a new customer or material in R/3, they are replicating immediately to CRM. But if i create a transaction( Sales or Service) or if i made any changes to the Business partner( Which is actually downloaded from R/3) those are not replicating immediately to R/3. If i see in the Transaction- SMW01, BDOCs were hanging with yellow traffic light and the BDOC description is "Sent to receivers(not all have confirmed)". Each time i am processing thse BDOCs manually to change the traffic light to Green and the BDOC description to 'Confirmed (fully processed by all receivers)'. Can anybody tell me, why the system behaviour is like this. Do i need to do any additional settings for the immediate replication. Please guide me to solve this issue. Thanks in advance Nadh. 2161 Views Topics: customer_relationship_management Reply Average User Rating (0 ratings) My Rating: Re: Middleware : CRM to R/3 - BDOCs are hanging in Trx SMW01 with Yellow status
ramana kumar Apr 29, 2008 8:53 AM (in response to Nadh R) hi nadh, the transactions which are created in CRM will be replicated successfully when the transaction type, item category of CRM transaction should be similar to that of r/3 or viceversa. please check whether the transaction type and item category are similar in both the systems. o Alert Moderator o Like (0) o Reply Re: Middleware : CRM to R/3 - BDOCs are hanging in Trx SMW01 with Yellow status
Sandeep Jha Apr 29, 2008 9:40 AM (in response to Nadh R) 1) Go to tx SMQ2 in CRM system 2) Register the Queue name * o Alert Moderator o Like (0) o Reply Re: Middleware : CRM to R/3 - BDOCs are hanging in Trx SMW01 with Yellow status
Jose Manuel Chavez Uribe Apr 8, 2009 5:22 PM (in response to Nadh R) HI Nadh, Did you solve this? I have the same issue. Best Regards. o Alert Moderator o Like (0) o Reply o Re: Middleware : CRM to R/3 - BDOCs are hanging in Trx SMW01 with Yellow status
Vikash Krishna Apr 9, 2009 2:49 PM (in response to Jose Manuel Chavez Uribe) Hi There, The problem is because the BTE is not maintained in the ECC table TBE31 for the sales transactions. Systems maintains the entry when you trigger the load for the first time and then onwards the delta will get trigger. Since the BTE is not maintained the queues are hanging in yellow status because CRM is sending the data to ECC but ECC is not replying back for the confirmation. Solution for this is that put some filter for the object BUS_TRANS_MSG e.g sales order created in future date ( by doing that you will not bring any transaction to CRM but when you will trigger the initial load for the object it will maintain the BTE in ECC side.) After proper filter setting start the initial load of the object once this is done. you can test the delta from CRM to ECC and the BDocs should be green. Hope this will help. Thanks, Vikash. Alert Moderator Like (0) Reply Re: Middleware : CRM to R/3 - BDOCs are hanging in Trx SMW01 with Yellow status
Pablo Rodrguez Mateos Sep 30, 2009 8:57 PM (in response to Vikash Krishna) Hi Vikash, I have also BUS_TRANS_MSG Bdocs in yellow, like other SDNs reported. I am trying to replicate the steps you gave, but, after settinf the filter, I am not able to start initial download of object BUS_TRANS_MSG, since it asks me for a proper source & receiver, and only CRM source is available, but there's no receiver in matchcode. I always get the error "Please fill required fields". In R3AC1 I can see that the only source site is CRM, and target sites CDB, XIF, etc, but not ERPSite. I can't modify or insert any value, so I can't proceed as you described. I will appreciate any suggestion. thanks in advance. Pablo Alert Moderator Like (0) Reply Re: Middleware : CRM to R/3 - BDOCs are hanging in Trx SMW01 with Yellow status
Vikash Krishna Oct 1, 2009 3:30 AM (in response to Pablo Rodrguez Mateos) Hi Pablo, The scenario I talked was from ECC to CRM so source should be ECC and Taget should be CRM. Check your adaptor object in Transaction R3AC1 and verify the Source site type and target site type in tab Initial flow context. The source should be ERP and target should be CRM. After verifying it , assuming it is correct, Just go to R3AS and enter the object name and hit enter and the source and target should get filled automatically. Hope this will help. Thanks, Vikash. Alert Moderator Like (0) Reply Re: Middleware : CRM to R/3 - BDOCs are hanging in Trx SMW01 with Yellow status
Pablo Rodrguez Mateos Oct 1, 2009 9:13 AM (in response to Vikash Krishna) Vikash, We've got our transactions replicated in R3... but they are not confirmed back to CRM, so we can't modify anything there since the status is still 'sent to receivers...'. On the other hand, we are able to deliver and invoice those R3 orders. I agree on what you say, but I am unable to edit tab 'Initial flow context' in the adaptor object. I can set filters and modify certain fields of that object... but I can't enter 'ERPSite', so I can't run R3AS, since field 'source' fills with 'CRM' and 'receiver' does not even fill at all !!! It is frustrating!!! any idea? thanks Pablo Alert Moderator Like (0) Reply Re: Middleware : CRM to R/3 - BDOCs are hanging in Trx SMW01 with Yellow status
Pablo Rodrguez Mateos Oct 1, 2009 11:11 AM (in response to Vikash Krishna) Hi again Vikash, Finally, I solved the problem. The initial load was not for object BUS_TRANS_MSG, but SALESDOCUMENT, where source is ERPSite and receiver CRM. You have to maintain filters there, as said in Note 490932 - Data exchange of sales transactions between CRM and R3, where there are interesting hints. Now BDocs are ok and we can process documents also in CRM, since status is distributed!! Thank you for your effort. bye