Message type: E = Error
Message class: FITP -
Message number: 128
Message text: Communication error: RFC destination &1 cannot be called
The program you are using needs to communicate with an external program
in order to access the data in the external reservation system. However,
the communications interface is not available at the moment.,,
The system has determined that communication with the external
reservation system has been interrupted.
Contact your system administrator.
Communication with the external reservation system takes place across an
external gateway. Use Transaction SM59 to test the RFC destination
<ZH>&v1&</><ZH></> (under TCP/IP Connections). This call was not
successful in the application program and resulted in the error
<ZH><ZH>&V2&</></><ZH><ZH> &V3& </></>
The connection will only work in the application program once the test
using SM59 has been completed successfully without errors. In
particular, the program must be registered with the gateway.
In certain situations (particularly in a test environment), it may be
necessary to communicate with the current or another reservation system
using a different RFC destination. To do this, you must make settings in
Customizing under Financial Accounting -> Travel Management -> Travel
Planning -> Master Data -> Technical Control Parameters for Travel
Planning. For further information, see the documentation for that
activity and the documentation for Technical and Organizational
Prerequisites.
Error message extract from SAP system. Copyright SAP SE.
FITP128
- Communication error: RFC destination &1 cannot be called ?The SAP error message FITP128 indicates a communication error with a Remote Function Call (RFC) destination. This error typically occurs when the system is unable to establish a connection to the specified RFC destination. Here are the potential causes, solutions, and related information for this error: Causes: Incorrect RFC Destination Configuration: The RFC destination may not be configured correctly in the SAP system. Network Issues: There may be network connectivity issues between the SAP system and the target system. Target System Down: The target system that the RFC destination points to may be down or not reachable. Authorization Issues: The user credentials used for the RFC connection may not have the necessary authorizations. Firewall Restrictions: Firewalls or security settings may be blocking the communication between the systems. SAP Gateway Issues: The SAP Gateway service may not be running or may be misconfigured. Solutions: Check RFC Destination Configuration: Go to transaction SM59 in the SAP GUI. Locate the RFC destination that is
Get instant SAP help. Sign up for our Free Essentials Plan.
FITP127
Begin of service is in the past; availability query not possible
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FITP126
No trips correspond with the filter criteria
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FITP129
Trip is already reserved (deletion not possible)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FITP130
Enter a date for the train trip
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.