Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: B1 - ALE group messages
Message number: 355
Message text: No object for requested IDoc selected for sending
No object was selected for dispatch for the requested message type &v1&
Check the contents of the request IDoc and generate a new request if
necessary.
Error message extract from SAP system. Copyright SAP SE.
B1355
- No object for requested IDoc selected for sending ?The SAP error message B1355, "No object for requested IDoc selected for sending," typically occurs when there is an issue with the IDoc processing in SAP. This error indicates that the system could not find any IDoc that matches the criteria specified for sending. Here are some common causes, solutions, and related information for this error:
Causes:
- Incorrect Selection Criteria: The selection criteria used to fetch IDocs for processing may be incorrect or too restrictive, leading to no IDocs being found.
- IDoc Status: The IDocs may not be in a status that allows them to be sent. For example, they might be in a status like "error" or "not ready."
- IDoc Configuration: There may be issues with the configuration of the IDoc type or message type, which could prevent the IDoc from being selected for sending.
- Outbound Processing: The outbound processing settings may not be correctly configured, leading to no IDocs being selected for transmission.
- Data Issues: There may be data issues in the IDoc that prevent it from being processed or sent.
Solutions:
- Check Selection Criteria: Review the selection criteria used for fetching IDocs. Ensure that they are set correctly and are not too restrictive.
- Review IDoc Status: Use transaction code WE02 or WE05 to check the status of the IDocs. Ensure that the IDocs you expect to send are in a status that allows them to be processed (e.g., "ready for dispatch").
- Verify Configuration: Check the configuration for the IDoc type and message type in transaction WE20. Ensure that the partner profiles are set up correctly for outbound processing.
- Check Outbound Processing Settings: Review the settings in transaction WE41 (for outbound IDocs) to ensure that the processing is set up correctly.
- Data Validation: Validate the data in the IDocs to ensure there are no issues that would prevent them from being sent. This may involve checking for missing mandatory fields or incorrect data formats.
- Reprocess IDocs: If IDocs are in error status, you may need to correct the issues and reprocess them using transaction BD87.
Related Information:
By following these steps, you should be able to identify the cause of the B1355 error and implement a solution to resolve it.
Get instant SAP help. Sign up for our Free Essentials Plan.
B1354
Version & of process code & not allowed for ALE
What causes this issue? Process code &v2& has version &v1&, which is not allowed for ALE input.How to fix this error? Check the part...
B1353
Parameter & missing in container of task &
What causes this issue? The system attempted to determine the attributes of parameter &v1& in the container of task &v2& and has foun...
B1356
Account group in the IDoc is different
What causes this issue? Changes cannot be made automatically to the account group of a customer master record. The customer with number &v1& ...
B1357
Status records with status 51 after status 53
What causes this issue? The application function module controlling the ALE inbound processing has passed several status records to ALE. The status o...
Click on this link to search all SAP messages.