In my blog series Pattern-based Partitioning using the SPO BAdI I shared an approach how to realize central definition and maintenance of partitioning patterns. The standard Semantically Partitioned Object (SPO) functionality of SAP NetWeaver BW 7.3 is enhanced by implementing Business Add-in (BAdI) RSLPO_BADI_PARTITIONING and few control tables. It facilitates an automated (re)partitioning, either individually or collectively, and enables partitions, criteria, texts and Data Transfer Processes (DTPs) to be generated automatically and consistently.
The blog series consists of the following blogs:
I developed a working version of the BAdI implementation which I would like to share via two documents. Part 1 contains all technical details of creating the control tables and the related ABAP data dictionary objects. Implementing Pattern-based Partitioning using the SPO BAdI - Part 2: BAdI Implementation explains all technical details of implementing BAdI RSLPO_BADI_PARTITIONING and the necessary ABAP Object Oriented programming in the implementing class.
The following transparent tables have to be implemented:
From a data management perspective it makes sense to enhance the basic tables with e.g. table maintenance views or a maintenance transaction. This is not in scope of this document.
The following fields have to be implemented.
Figure 1: Table YSPOINFOPROV - Fields
The following entry helps and checks have to be implemented.
Figure 2: Table YSPOINFOPROV - Entry Help/Check
Figure 3: Table YSPOINFOPROV - Foreign Key Pattern ID 1 and 2
The following fields have to be implemented.
Figure 4: Table YSPOPATTERN - Fields
The following entry helps and checks have to be implemented.
Figure 5: Table YSPOPATTERN - Entry Help/Check
Figure 6: Table YSPOPATTERN - Foreign Key InfoObject
The following fields have to be implemented.
Figure 7: Table YSPOPATTERNT - Fields
The following entry helps and checks have to be implemented.
Figure 8: Table YSPOPATTERNT - Entry Help/Check
Figure 9: Table YSPOPATTERNT - Foreign Key Pattern ID
The following fields have to be implemented.
Figure 10: Table YSPOCRITERIA - Fields
The following entry helps and checks have to be implemented.
Figure 11: Table YSPOCRITERIA - Entry Help/Check
Figure 12: Table YSPOCRITERIA - Foreign Key Pattern Pattern ID
The following fields have to be implemented.
Figure 13: Table YSPODTP - Fields
The following entry helps and checks have to be implemented.
Figure 14: Table YSPODTP - Entry Help/Check
Figure 15: Table YSPODTP - Foreign Key SPO InfoProvider
Figure 16: Table YSPODTP - Foreign Key Source System
Figure 17: Table YSPODTP - Foreign Key DTP Template ID
The following domains have to be implemented:
The following data elements have to be implemented:
The following search help has to be implemented:
Figure 18: Domain YSPOPARTGROUP
Figure 19: Domain YSPOPATTERNID
Figure 20: Domain YSPOTLOGO
Figure 21: Domain YSPOTLOGO - Value Range
Figure 22: Data Element YSPOPARTGROUP
Figure 23: Data Element YSPOPATTERNID
Note: Data elements YSPOPATTERNID1 and YSPOPATTERNID2 are defined in exactly the same way and therefore not described further.
Figure 24: Data Element YSPOTLOGO
Figure 25: Search Help YSPO_DTPTEMPLATE
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
8 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 | |
3 | |
3 |