Do you have any question about this error?
Message type: E = Error
Message class: SR - RFC utilities
Message number: 300
Message text: Exception CX_BGRFC_RETRY_REQUEST caught by application
The method CL_BGRFC_SERVER=>RETRY_UNIT( ) was called on the server side
of a background RFC (bgRFC). This method uses the exception
CX_BGRFC_RETRY_REQUEST to send its parameters to the bgRFC scheduler.
This is why it must not be intercepted. Otherwise, calling the method
CL_BGRFC_SERVER=>RETRY_UNIT( ) has no effect.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
You must change the program on the application side to prevent the
exception from being intercepted.
Error message extract from SAP system. Copyright SAP SE.
SR300
- Exception CX_BGRFC_RETRY_REQUEST caught by application ?Get instant SAP help. Start your 7-day free trial now.
SR280
Destination does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SR275
This class cannot be used
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SR301
Queue names &1 and &2 are registered for different destinations
What causes this issue? You want to write an outbound/inbound unit for bgRFC or a LUW for classic qRFC to a set of queues. These queues are not all a...
SR302
Queue name &1 is not registered for bgRFC
What causes this issue? The queues assigned to an outbound/inbound unit for bgRFC or to a LUW for classic qRFC could not be assigned to a single bgRF...
Click on this link to search all SAP messages.