No Un-ambiguous Selection of Mapping Module (above one) for BUPA_MAIN BDocs

Question

Hi All
I seem to have hit a snag here. I am trying to replicate customers from CRM to ERP but am getting these two errors:
Main error: Partially send, receivers have errors.
No un-ambiguous selection of mapping module (above one) for BDoc type 3932399B34D6279BE10000000A11449E.
Service that caused the error: SMW3OUTBOUNDADP_CALLADAPTERS._
I have searched on Googleand SDN but have come up with nothing as far as these errors are concerned. We have managed to replicate Business Partners, Materials and Conditions from ERP to CRM without any problems but when it cam e to replicating back, these errors started popping up.
I have used all the tools for analysis but have come up with nothing the really suggest to me what is wrong. I have monitored queues, traces and dumps. I have played around with the filter setting and all.
With regards to the process itself, i followed the C03 best practices config guide and i believe that i have everything in place. Here are the steps i followed:
1.Create an Internal number range for the CRM customer group.
2. Assigned the number range to the Customer group
3. Created a corresponding number range (External) in ERP and a corresponding CRM Customer account group as a copy of the standard 0001 Sold-to-party account group and assigned the number range to it.
4. Defined Partner functions (SP, SH, BP, and PY) for the account group
5. I mapped the CRM classification for customers (B) to the created account group (CRM Customer)
6. I synchrponized the fields for the account group created and the BP roles in CRM including changes on a per client (BUPA) basis.
7. I redowloaded all the cutomizing objects (though i only needed the DNL_CUST_KTOKD) for the sake of the mappings directly in CRM or R/3 Account group maintenance during the creation of the BP.
8. I customized the filter settings in BUPA_MAIN and included the BUT100 table for the filetring of the customers who were created as SP, BP, PY, or SHand who belonged to the Customer group we had created. (BUT000->BU_GROUP & BUT100->RLTYP) for source site CRM.
9. Activated the necessary function modules through transactions COM_BUPA_CALL_FU in ERP and CRMC_BUT_CALL_FU in CRM according to [http://help.sap.com/saphelp_crmscen70/helpdata/en/60/85b5d333f4174b8e982c1c15db35f3/frameset.htm]
10. Using transaction R3AS i sought to replicate the BUPA_MAIN object.
Because of the few customers created in CRM, it only executes within a single block so the queues would be empty by the time SMQ1 and SMQ2 are executed. R3AM1 shows it as running. SMW01 shows the above error.
When creating a BP through the tx code BP, the main error would be Technical error(Incomplete) and the two other errors as mentionme above would also be there
Is there anyone out there who has met this very same problem or knows the solution to this.
Thanks in advance.

Answer 1

We managed to get a solution to the problem. Here it goes:
When a new adapter object (e.g a custom one) is created, the SMOFOBJECT table is populated with the entry and, in turn, the SMOFUPLMAP is populated with the object and the mapping module for uploading to R/3. During the upload process, a search for custom mapping modules is done and if not found the standard mapping modules are used. However, and it seems weird since it seems as if it applies to the BUPA_MAIN object or the corresponding mapping module (BUPA_MWX_BDOC_UPLOAD_MAIN_R3), there has  to be a one-to-one mapping between an mapping module and adapter object.
I had created a custom adapter object (Z_BUPA_MAIN) to which I wanted to put some custom filters and did not want to test with the standard object. So two objects using the same mapping module ended up existing  in the SMOFUPLMAP table (one-to-many mapping). The function module in which this happens is the GET_UPL_FUNCTION_FOR_OBJ.
So the solution would be to delete the object if it is not needed or to maintain the SMOFUPLMAP table to remove the entry. When you delete the object, it sometimes does not automatically/subsequently remove the entry in SMOFUPLMAP, so manual maintenance has to be done or the same object has to be recreated and have the mapping module allocated. After this, the problem would be solved. What is weird to me is that the only one-to-one mapping is allowed. I created a custom object for the download of conditions and I did not get that error. So it means that in this case you would have to copy the mapping module and create a custom one for the custom object.