Do you have any question about this error?
Message type: E = Error
Message class: B1 - ALE group messages
Message number: 358
Message text: No status record was passed to ALE by the application
The application failed to return a status record to the ALE layer after
the IDoc was processed.
This is due to an error in the application function module which
processed the inbound IDoc.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If you wrote the application function module yourself, you need to
change the program.
If the function module in question is a standard application function
module, you should consult SAP.
Error message extract from SAP system. Copyright SAP SE.
B1358
- No status record was passed to ALE by the application ?The SAP error message B1358 ("No status record was passed to ALE by the application") typically occurs in the context of Application Link Enabling (ALE) when there is an issue with the data being sent between systems. This error indicates that the application did not provide a status record that is necessary for the ALE processing.
Causes:
- Missing Status Record: The application that is supposed to send the status record did not generate or send it.
- Configuration Issues: There may be configuration issues in the ALE settings, such as incorrect distribution model settings or missing logical systems.
- Data Issues: The data being processed may not meet the required criteria for generating a status record.
- Application Logic: The application logic may not be correctly implemented to handle the status record generation.
Solutions:
- Check Application Logic: Review the application logic to ensure that it is correctly generating and sending the status record. This may involve debugging the application code or reviewing the relevant transaction.
- Review ALE Configuration: Check the ALE configuration settings in transaction
WE20
(Partner Profiles) andBD64
(Distribution Model) to ensure that they are set up correctly.- Check for Data Issues: Verify that the data being processed is valid and meets the criteria for generating a status record. This may involve checking the input data or the conditions under which the status record is generated.
- Monitor Application Logs: Use transaction
SLG1
to check application logs for any related errors or warnings that may provide more context about the issue.- Consult Documentation: Review SAP documentation or notes related to ALE and the specific application you are working with for any known issues or additional troubleshooting steps.
Related Information:
WE02
(IDoc Display), WE19
(IDoc Test Tool), and SLG1
(Application Log) for monitoring and troubleshooting.If the problem persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
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...
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& ...
B1359
No active event coupling for & . & found, no error work items
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
B1360
Status was set automatically
What causes this issue? Status was set by an implementation of the BAdI IDOC_REPROCESS during an inbound tRFC.System Response The system issues an e...
Click on this link to search all SAP messages.