Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony⤷
SCON (Package) SAPconnect - External Communication
Basic Data
| Data Element | SXRETRYHOU |
| Short Description | SAPconnect: Maximum Repetition Time (hours) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM3 | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Rep. (hrs) |
| Medium | 20 | Repetition time(hrs) |
| Long | 32 | Maximum repetition time (hours) |
| Heading | 50 | Maximum Repetition Time (Hours) for RFC to Node |
Documentation
Definition
In the case of temporary errors when connecting to a SAPconnect node, the system tries to connect to this node again and to send the message (fax, e-mail,...).
At the earliest, the second send attempt is made 10 minutes after the failed attempt due to a temporary error if a send process, started automatically or manually, is then running. If a further error occurs, the system tries again after a further 10 minutes, and so on.
The maximum amount of time this process is carried out for can be specified in hours and minutes. After this time period, the messages are returned with the message "Message could not be sent".
If no value (hours/minutes) is specified, the maximum waiting time is zero minutes and the error message "Message could not be sent" is generated as soon as the RFC error occurs.
History
| Last changed by/on | SAP | 20020827 |
| SAP Release Created in |
