The QPPD supports the distribution of its objects between two QPPD instances. The QPPD standard IDOC or an RFC connection can be used for this purpose.
Technical requirements
The distribution of QPPD data is generally controlled utilizing message types and the standard SAP distribution model. By assigning the corresponding follow-up processes to the specification types for IDOC distribution (SCT_IDOC_OUT) or RFC distribution (SCT_RFC_OUT), distribution is switched on for the associated objects. For this, the standard QPPD follow-up processes must be set in the basic settings.
Before data can be distributed between two systems/clients, a connection must be established between these two systems.
For distribution to be technically possible, the QPPD instances involved must be compatible with each other: During distribution, the sending system must have at most the same release level as the receiving system. The sending system must not have a higher release than the receiving system.
In exceptional cases, however, it may be possible that two different QPPD releases are nevertheless compatible with each other from a technical point of view for distribution.
We, therefore, recommend keeping the QPPD instances in a system landscape at the same release level for interoperability.
IDOC
When distributing with the standard QPPD IDOC, generic standard QPPD segments are used to transport the data between systems/clients, it is therefore possible to distribute any customer-specific objects.
The QPPD supports the extension of database fields. Provided that no database fields have been extended, the Data Distribution via IDOC -Standard- (H) can be used.
If database fields have been extended, the Data Distribution via IDOC -with Extension- (H) must be used.
RFC
Distribution using RFC is also implemented in the standard QPPD and is explained in RFC Data Distribution (H).