In document Step by step to download equipment from ERP with hierarchy, the steps to replicate equipment from ERP to CRM are described. By default the equipment in ERP is modeled as individual object in CRM with object family 0401. With correct customizing, certain changes could be made on those equipment in CRM, and the change could also be replicated back to ERP.
: it is NOT support to upload an equipment created from CRM ( that is, its original system is set as CRM ) to ERP. Only those equipment whose original system set as ERP could be replicated back to ERP.
The note 1267718 – Upload of individual objects changes from CRM to ERP contains the most fundamental settings but without detail explanation on its item. So this document includes how to perform equipment upload in detail.
CRM: system AG3 client 001
ERP: system ERP client 001
(1) Activate adapter DNL_EQUIPMENT in tcode R3AC1
By default this adapter is deactivated. If you could not see it in list, click button “In-/Active” to show all inactive one.
If you need also to replicate the hierarchy change on equipment back to ERP, you must also activate adapter DNL_EQUI_HIER as well.




All the settings in SMOEAC will be stored in a series of database table SMOH*. In the runtime your settings will be evaluated by middleware framework.
(5) Enable description change in CRM
By default once an equipment is replicated from ERP to CRM, it is not allowed to change it on CRM. However partial changes could be manually enabled via SPRO: Customer Relationship Management -> Master Data -> Products -> Business Add-Ins->BAdI: Allow Changes to Product Data:
The above entry means it is allowed to change the short description ( set type COMM_PR_SHTEXT ) of the equipment ( object family 0401 ) in CRM.
(6) Trigger upload via equipment description change
Make changes on equipment description and save the transaction.
If you have deactivated inbound queue processing in tcode SMQR, you could see an inbound queue with name consisting of prefix CSA_INDOBJ + in tcode SMQ2.
This outbound queue is responsible for the actual upload to ERP.
For trouble shooting purpose, refer to this blog How to debug Product initial upload in ERP and CRM system.