BDOCs in status E01 - Technical Error

Question

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

Answer 1

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