Kontakt

Ansicht
Dokumentation

/ISDFPS/ALE_SYS - Systems and Connection Parameters

/ISDFPS/ALE_SYS - Systems and Connection Parameters

General Material Data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you define the connection parameters for the central and decentralized systems. You must make an entry for each system.

  • In the decentralized system, you make one entry for the decentralized system itself, and one for the central system.
  • In the central system, you make one entry for the central system itself, and one entry for each of the decentralized systems that are connected with this central system.

In this activity, you can also make settings for transient transition by defining the operating parameters for IDoc dispatch and synchronization.

Enter the following values:

  • General
  • Logical System

Name of the logical system
  • Planned Mode

System type in the DFPS system landscape (planned online/offline)
  • Central System

Name of the upstream system
  • RFC Destination for Synchronization

RFC destination for processing synchronization activities with a partner system
The RFC user requires the authorization DF_BAS_ALE.
  • ALE Routing System

If required, specify the logical name of the XI system. If no system is specified, synchronization is carried out directly (without an XI system).
  • Synchronization for this System

Specify whether data synchronization is to be carried out for this system.
  • Connection Test
  • Number of PINGs

Number of PING attempts
  • PING Timeout

The timeout value for PING (value in seconds)
  • Max. Ping Loss

The packet loss rate for PING
  • FTP Server for Transports
  • Host Name

Enter a canonical host name or and IP address of an FTP server on which user <LOGSYS> has an FTP user account.
  • TR Password

The password (scrambled) for retrieving transport files via FTP; the password must correspond to the user configuration of the FTP server
  • tRFC Parameter
  • Repetition Pause,,,,

The time between repeated attempts to send an IDoc (value in minutes)
  • Connection Attempts

The maximum number of attempts to send an IDoc
  • DELTA_O

You can use the ALE sync parameter Delta O to set the system offline temporarily (value in minutes), for example, if there is a longer connection failure
  • DELTA_S

You can use the Delta S parameter to define the interval in minutes after which a further synchronization attempt is made.
  • Repetitions

The number of repetitions
  • ALE Inbound Processing
  • Delta-IP

ALE sync parameter DELTA_ALE_IP -ALE-In-Processing [min]: This value controls the delay (in minutes) with which ALE inbound processing is started after the synchronization report has ended.
  • D-IP after UPS

ALE sync parameter DELTA_ALE_IP -ALE-Inp. after UPS [min]: During ALE inbound processing, this value controls the time interval (in minutes) between processing UPS IDocs and other IDocs. It can be used to optimize the system load.
  • Organizational Unit for Error Handling
You specify who is to receive notifications (user, administrator, or an organizational unit) if there are problems in the synchronization process. If you want to specify a user or administrator as the recipient, enter the object type US and the user name. If you want to specify an organizational unit as the recipient, enter the object type O and the object ID of the organizational unit. You must define an e-mail address for the organizational unit.
  • User Distribution
See also User Distribution: Systems
  • Central User Administration
If the functions for the emergency deactivation of the CUA connection are changed, these fields are no longer required.
  • Destination: User Administration

The RFC destination for setting user data, profiles, and authorizations
  • CUA Central System

The central system for Central User Administration
Both fields are filled automatically if you use transaction /ISDFPS/CUA_SWITCH to carry out emergency deactivation of CUA. The system needs these values to reactivate CUA. As a rule, you do not need to make any manual changes here.
The RFC user in the central system requires the role /ISDFPS/CUA_SWITCH_CENTRAL, while the RFC user in the decentralized system requires the role /ISDFPS/CUA_SWITCH_CLIENT.
  • RFC Destinations
  • Destination: Status Signal

The RFC destination that, as part of CCMS monitoring mechanisms, is notified if there are changes in the status of a connection to a partner system
The RFC user does not require additional authorizations.
  • Destination: GNR Test

The RFC destination for changing number range settings in a partner system
The RFC user requires the standard authorizations that are also required for transaction SNUM.






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 8011 Date: 20240426 Time: 175418     sap01-206 ( 85 ms )