on 12-31-2016 5:37 PM
When setting up partitioning on a source table, within DS, the data flow becomes duplicated for each partition value. What about the case when using an SAP table as a source and using ABAP execute preloaded? Can we use the partitioning feature with this scenario since the ABAP is static?
Yes. ABAP is the preferred option. I fully agree with this option. I am assuming that there are indexes on the huge SAP tables being used.
Let me know if you see any difference when using partitioning feature and then using ABAP Data flows to extract data.
Regards
Arun Sasi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With a regular data flow, aren't you forced to use OpenHub? That limits the operations allowed when extracting from SAP, such as the lack of performing a join to another table. ABAP is preferred. I think it could be built into the application when using partitions, so that a where clause is included when generating the ABAP and variables get used to pass the partition values. The .dat files would need to be dynamic as well. OpenHub is too limited.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Dani,
Partitioning option cane be used when you are using Regular Data flow as per SAP Supplement Guide.
Eventhough you use ABAP data flow with Execute Preloaded option, partition would be helpful in improving performance as it would finally hit the SAP Table. This is kind of a fake partition which is used by Data Services.
Regards
Arun Sasi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.