This section serves as a reference to the boundaries and limitations regarding the Tool.
Copying a Query is so far only supported, if the InfoProvider on which the Query is based, has the type DSO, InfoCube or MultiProvider. Also, the underlying InfoProvider must have at least one entry in the TADIR table. If not, the Docu Performer shows an error message, recommending to reactivate the InfoProvider.
Queries, which are using InfoProvider Type-specific Modeling Objects (DSO: 1ROWCOUNT; InfoCube: 0REQUID; MultiProvider: 0REQUID, 0INFOPROV; HANA CompositeProvider: 1ROWCOUNT, 0REQUID, 0INFOPROV, 0REQTSN) shouldn’t be copied to an InfoProvider from a different type. The table below might help to clarify the different dependencies.
Target-InfoProvider | |||||
Source-InfoProvider (InfoProvider-specific Modeling Objects) | DSO | InfoCube | MultiProvider | HANA CompositeProvider | Aggregation Levels |
DSO | ok | ok | ok | ok | don’t copy |
InfoCube | ok | ok | ok | ok | don’t copy |
MultiProvider | ok | ok | ok | ok | don’t copy |
HANA CompositeProvider | ok | ok | ok | ok | don’t copy |
DSO (1ROWCOUNT) | ok | don’t copy | don’t copy | ok | don’t copy |
InfoCube (0REQUID) | don’t copy | ok | ok | ok | don’t copy |
MultiProvider (0REQUID) | don’t copy | ok | ok | ok | don’t copy |
MultiProvider (0INFOPROV) | don’t copy | don’t copy | ok | ok | don’t copy |
HANA CompositeProvider (1ROWCOUNT) | ok | don’t copy | don’t copy | ok | don’t copy |
HANA CompositeProvider (0INFOPROV) | don’t copy | don’t copy | ok | ok | don’t copy |
HANA CompositeProvider (0REQUID) | don’t copy | ok | ok | ok | don’t copy |
HANA CompositeProvider (0REQTSN) | don’t copy | don’t copy | don’t copy | ok | don’t copy |
Aggregation Levels | don’t copy | don’t copy | don’t copy | don’t copy | ok |
The Tool doesn’t support copying Queries of version 3.x.
Downward compatibility when Copying Queries
...
With every SAP-Release or even Patch, table elements can change, are added or might be deleted. Furthermore, the structure of Function Modules used by the Docu Performer might have changed and are leading to missing data in the “Query-tables”. The following table shows an extract of three SAP-Releases with their corresponding fields which were added, deleted or can’t be filled. If a Query request is mainly based on those fields, information can get lost as these elements won’t be copied.
Table | Field | Releases | ||
|
| 740 SP9 | 730 SP9 | 701 SP6 |
RSZCALC | AGGRCHA2 | ok | not included | not included |
RSZCALC | AGGRCHA3 | ok | not included | not included |
RSZCALC | AGGRCHA4 | ok | not included | not included |
RSZCALC | AGGRCHA5 | ok | not included | not included |
RSZCOMPIC | FOLDER | ok | ok | not included |
RSZELTPROP | EQSUPPORT | ok | ok | not included |
RSZELTPROP | ODATASUPPORT | ok | not included | not included |
RSZELTPROP | HANASUPPORT | ok | not included | not included |
RSZGLOBV | CMP_SUPPORT | not supported by | ||
Function Module | ok | not included |
SAP Content Exit Variables
There could be the case that a content customer exit variable exists in the target but not in the source system. We do not allow to copy copying that variable in this case and you will see the message in the status column "Content Exit Variable not supported in target system".