BDocs 
The same BDocs are used for uploads as for downloads. This refers to BDoc categories SI_CONNOBJ for connection objects and SI_POD for PoDs (points of delivery).
When you create or change a technical object in the CRM system, the system generates a corresponding BDoc. In the ERP Adapter, the technical object data is sent to the IS-U backend system. If the object can be successfully created, a response BDoc is generated. In the validation service, this response BDoc updates the ERP key for the technical object in the CRM system.
Queue Names
Because no R/3 key is known when the technical objects are created in the CRM system, it is also not possible to form queue names from the connection object number. In the case of uploads, the queue CSA_MASS_CONNOBJ is used for all new objects. The queue names from R3AD_CONNOBJ<connection object number> are only available for downloads.
Error Processing
Serious errors, such as a missing master data template in the IS-U backend system, result in the BDoc having an error status. Once you have corrected the system settings you can restart the BDoc.
Caution
If errors occur when processing the master data templates, you must process these errors in the IS-U backend system. You can do this using the new transaction IS-U Contract Error Monitor (ISU_ECRMREPLM). In this case, the BDoc is given the status "OK".
Caution
For detailed information on this transaction, see document "Error Handling IS-U for Utility Contracts, Technical Objects from CRM". This is located in the SAP Service Marketplace under http://service.sap.com/utilities
Product Information 
SAP CRM for Utilities Cookbooks & Guidelines 
.