Purpose
This report is used to synchronize systems in the distributed DFPSsystem landscape.

Integration
DFPS

Prerequisites
Customizing:
,,- Distributed system landscape (/ISDFPS/ALE_SYS)
,,- Object categories and transportation priorities
,,- Assignment of message types to object categories
,,- Organizational unit responsible for error handling
,,- Inclusion of CCMS monitoring (main system - for test scenarios)

Features
Callup in the decentralized system - send IDocs to selected partnersystem, and obtain and import transports. Trigger the send process forIDocs from the selected partner system to own system by remote start ofa synchronization report running in that system.

Selection

Description of Selection Screen Parameters
- Partner system
- ALE IDoc parameters
Maximum IDoc priority
Only IDocs up to the selected priority are sent
tRFC queue from
Earliest date for triggering tRFC processes again, which for example,have an error status due to an interruption in communication
Prefill with current data
Send only
Only IDocs are sent to the partner system
Opposite active synchronization report is not started in the partnersystem
Evaluate change pointer
Evaluating the change pointer can create additional IDocs, depending onthe system setting
Evaluate NAST (notification control)
Evaluating the notification control before IDocs are sent. This cancreate additional IDocs, depending on the setting
Evaluate ALE status
Evaluating the ALE status can transfer additional information for IDocprocessing to the original sending system in the form of additionalIDocs
- Transport handling parameters
Process transports
"Main switch" for transport handling functions - only when this isselected do the subsequent switches have an effect on the runtime
Transfer transports by FTP
Collection of transport files for own system from a specifiedcollection server
The files are copied from the "colfiles" and "data" directories of theFTP home directory to the corresponding directory of the local TRANSDIRand then deleted from the FTP server.
In the standard shipment, the collection takes place from an FTP serverfrom the HOME directory of an FTP user with the name (ownLOGSYS name). This is done for security reasons. The aim is to preventdifferent systems from obtaining transport data for other LOGSYS as aresult of configuration errors (for example, if FTP users have the samename).
Transfer IDoc transports
Controls the sequence of IDoc shipments and FTP collection
Import transports
If you select this option, existing transport files in the localTRANSDIR are added to the TMS import queue and then imported.
It does not matter whether the transport files are imported by theabove FTP procedure, by data carrier, or by other means (such as TMS).
- Number range data
Send NR data
If you select this option, local number range statuses are transferredto the specified, central reviewing system (/ISDFPS/ALE_SYS) once theIDocs have been sent.

Standard_variants
SAP

Output
Application log.