Schlagwort: sapbw

Sometimes it is necessary to check your data model if it still fit your needs. For this you can use the transaction rsrv. Select there under All Elementary Tests >>
Database >> Database information about InfoProvider tables.

Now you can enter one InfoCube and choose Transfer. Now you can add more tests or click Execute to run the test.

After you click execute, you will see the log.

As you can see, the design of dimension 2 is very bad. It contains 100% of the entries of the f-table. So now we can plan our redesign. You can also check your cube design with the report
SAP_INFOCUBE_DESIGNS. How important a good InfoCube design is, will I show you in a futher post.

These posts might also be interesting:

• SAP BW Performance optimization for mass data without SAP HANA
• SAP BW Use Pattern in Variable with Customer Exit
• SAP BW Create SPO via BAdI – Part 3
• SAP BW find meta chain

I am Tobias, I write this blog since 2014, you can find me on twitter and youtube. If you want you can leave me a paypal coffee donation. You can also contact me directly if you want.

In my current project I had to clean up the existing process chains. A lot of process chains were created via SPOs and not really used in the system. First I had to check, if one is used in a another process chain or in which one they are used.

In the transaction SE16 open table RSPCCHAIN and insert into VARIANTE the technical name of your process chain.

The column CHAIN_ID shows you the corresponding meta-chain.

These posts might also be interesting:

• SAP BW Visio Shapes
• SAP BW Copy Queries to a new MultiProvider
• Install your own SAP BW on a virtual machine
• BW/4HANA Export Transports

I am Tobias, I write this blog since 2014, you can find me on twitter and youtube. If you want you can leave me a paypal coffee donation. You can also contact me directly if you want.

In my current project we have to transport from a maintenance system to our development system. The problem is when you now transport the objects into quality system, you have to check the option
„Overwrite Originals“ so that your transport is working. But you have to put this flag on every transport you make in the future from your development system to quality.

Nobody will remember this after a huge project, so every request has to be transported twice and this is annoying. So we have to find a solution for this. I found a thread on the SCN which describes a solution that worked for me. Yes I found a link which is
still working after the redesign of the SCN. I was surprised. Here is the solution:

First you can check in the transaction SE16 the table TADIR how many objects are not correct. You can filter with the field SRCSYSTEM. In my
case I looked for the SRCSYSTEM Z01.

Now open the transaction SE03 and choose under Object Directory >> Change Object Directory Entries.

Now you see a screen, where you can restrict your selection, in my case I want to find all objects which original system is Z01. After you filled your parameters click
Execute (F8).

You can either select each entry with a double click and edit it.

Or you can select a bunch of entries with F6 or the menu item Select/Deselect.

And enter MASS in the transaction code field and press Enter. Now you get a other dialog displayed, which allows you change all object at once.

As you can see it is really easy to change the source system of objects. If you now check the table TADIR, you will see that there are all entries for Z01 are
gone.

These posts might also be interesting:

• SAP BW Transport of Copies (ToC)
• Video How to maintain Master Data in SAP 7.4 
• BW/4HANA Export Transports
• SAP BW Analysis Process Designer (APD)

I am Tobias, I write this blog since 2014, you can find me on twitter and youtube. If you want you can leave me a paypal coffee donation. You can also contact me directly if you want.

In my current project, we have a copy of the productive system as a maintenance system, because we made huge changes in

the development system in case of the project. So if there is an error in the production, we can easily repair it.

Some changes have also be transported into the development system, so we have the same state and our future request can be transported into production. For this we use the functionality
Transport of Copies. All objects of the originally request are still locked. If you want to create a transport of copies, open the transaction SE01. Check the
option “Transport of Copies” and click on Display.

Create a new transport via icon or F6.

Choose the request type Transport of copies.

Define a short description and a target system.

The request is now created. Now we can add our objects we need to transport. We copy all objects of the original request into our new request. It is important to take task after task, because a
request can contain more than one task.

Select the request id with CTRL + Y and copy it with CTRL + C. Now select the transport of copies request and click on Include Objects (CTRL + F11).

Choose the Object List from Request and paste the original request id.

Now all objects of the original request are in your copy and you can continue with your normal transport management.

These posts might also be interesting:

• SAP BW Create SPO via BAdI – Part 3
• BW/4HANA Export Transports
• SAP BW Change Object Directory Entries
• SAP BW Analysis Process Designer (APD)

I am Tobias, I write this blog since 2014, you can find me on twitter and youtube. If you want you can leave me a paypal coffee donation. You can also contact me directly if you want.

After we created in Part 1 the transparent tables and in Part 2 all BAdI implementation, we can now maintain and create our SPO. First we have to fill our table ZSPOPATTERN with a
PATTERNID and a corresponding INFOOBJECT. Go to the se16 and create a new table entry. As PATTERNID enter a unique id for
example CALYEAR and as INFOOBJECT 0CALYEAR. For TXTLG and TXTSM enter a useful text. Depending on how many InfoObject are used for a partition, create the other
pattern.

After we filled ZSPOPATTERN, we can now fill ZSPOINFOPROV. As SPONAME enter the technical Name of the SPO. As PATTERNID1 to
PATTERNID4 enter your previous created pattern. For example Y_TM as SPONAME and CALYEAR as PATTERNID1.

The next table is ZSPOCRITERIA. Enter the previous created PATTERNID, a PARTGROUP, a LOWVALUE and if necessary a
HIGHVALUE. For example:

• PATTERNID – CALYEAR
• PARTGROUP – 1
• LOWVALUE – 2016

For 2017 use PARTGROUP 2, for more explanation see the screenshot below.

The last table is ZSPODTP. Enter a SPONAME, OBJTYPE, LOGSYS, DTPTEMPLATE and DTPTEMPLATEID.
The DTPTEMPLATEID can be found in table RSLPO_DFG_DTPTPL. For example:

• SPONAME – Y_TM
• OBJTYPE – ODSO
• OBJNAME – YTM01
• LOGSYS – T04CLNT100
• DTPTEMPLATE – DSO FULL
• DTPTEMPLATEID – 00O2TGUDQNX7RY71D737H5IZ2

After the initial maintenance is done, we can go to the transaction RSA1. We can either maintain our SPO directly or under Administration you find the
Mass Activation of BAdI SPOs. The first new partion will be created directly and the second and third under Mass Activation of BAdI SPOs. When you start from scretch you
click on Change Partitions to create your new partitions. Now you can choose your criteria.

As you can see on the screenshot below, when you select Read Charactcs. from BAdI, the InfoObject 0CALYEAR is automatically add as criteria.

In the screenshot below you see the partition 1 is automatically added with the year 2016.

Now we can activate our SPO and see, that the partition 1 is created. You can now add your new partitions either by clicking on Build Version From or via Mass Activation
of BAdI SPOs. I choose the second way to show you how can activate multiple SPOs at once. Goto Administration >> Mass Activation of BAdI SPOs.

As you can see in the screeshot above, our SPO find new partitions. With the function Version Comparison you can compare the actual version with the new.

As you see, the two new partitions for 2017 and 2018 will be created. By click on Activate, the partitions are created.

Now our SPO is up to date and all partitions are created. If you need for example 2019, you have to maintain the table ZSPOCRITERIA and go back to the Mass Activation of BAdI
SPOs. The last part is now to create the DTPs. Go to the SPO and open it in change mode. Click on Create Data Transfer Processes. You will see the following screen.

Select your partitions and click on the button BAdI Version.

The DTPs automatically appear and you only have to generate them.

That’s it. Your SPO and associated DTPS can be created via BAdI. I tested it with a Business Warehouse 7.31 SP18, maybe it is a little bit
different in a higher release.

These posts might also be interesting:

• SAP BW Copy Queries to a new MultiProvider
• SAP BW Visio Shapes
• SAP BW Performance optimization for mass data without SAP HANA
• Install your own SAP BW on a virtual machine

I am Tobias, I write this blog since 2014, you can find me on twitter and youtube. If you want you can leave me a paypal coffee donation. You can also contact me directly if you want.

After we created in part 1 all tables and objects, we can now create a new BAdI to generate the partitions. Go to
the transaction se19 and create a new implementation with the Name RSLPO_BADI_PARTITIONING.

Give the enhancement implementation a name and a short text.

Click continue and save. Now specify the BAdI implementation name, the implementation class and the BAdI
definition. Select for the BAdI Definition RSLPO_BADI_PARTITIONING, click continue and save.

After that the following screen appears.

Double click the implementation class and the following screen appears. The 6 methods of the class ZCL_DEMO_BADI_PARTITION which we use to define the partitions are displayed in the right panel.

• GET_T_SPO
• GET_T_PART
• GET_T_PART_TEXT
• GET_T_PART_CRIT
• GET_T_PART_PROP
• GET_T_PART_DTP

Each method has a specific role, which you can see under the short description. Double click the method IF_RSLPO_BADI_PARTITIONING~GET_T_SPO.

First we have to implement the name of the Semantic Partitioning Object (SPO).

1
2
3
4
5
6
7
8

method IF_RSLPO_BADI_PARTITIONING~GET_T_SPO.
  DATA: l_spo TYPE rslponame.
  
  "Return a table with names of supported BAdI SPOs.
  SELECT SPONAME from ZSPOINFOPROV into l_spo.
    APPEND l_spo TO r_t_spo.
  ENDSELECT.
endmethod.

Save and activate the method and the class. Now implement the

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

method IF_RSLPO_BADI_PARTITIONING~GET_T_PART.

DATA: l_cnt TYPE i,
      l_posit TYPE i VALUE 1,
      l_id TYPE c LENGTH 2,
      l_s_part TYPE rslpo_badi_s_part,
      "ZSPOINFOPROV Variable
      l_it_spoinfoprov TYPE TABLE OF ZSPOINFOPROV,
      l_wa_spoinfoprov TYPE ZSPOINFOPROV.

SELECT * from ZSPOINFOPROV into CORRESPONDING FIELDS OF TABLE L_IT_SPOINFOPROV where SPONAME = I_SPO.

Loop at L_IT_SPOINFOPROV into L_WA_SPOINFOPROV.
  SELECT COUNT(*) from zspocriteria into l_cnt where PATTERNID = L_WA_SPOINFOPROV-PATTERNID1.
    WHILE l_posit LE l_cnt.
      UNPACK l_posit to l_id.
      l_s_part-IDPART = l_id.
      l_s_part-POSIT = l_posit.
      APPEND l_s_part TO r_t_part.
      l_posit = l_posit + 1.
    ENDWHILE.
    CLEAR l_posit.
  ENDLOOP.
  
endmethod. 

IF_RSLPO_BADI_PARTITIONING~GET_T_PART_TEXT specifies the text for each partition. The problem is, the customer normally named the partitions after his own mind, so I just
implemented a comment, so it would be initialized. The comment is necessary.

1

"Coding will follow later

Now we implement the IF_RSLPO_BADI_PARTITIONING~GET_T_PART_CRIT. This implementation specifies the partition criteria.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

method IF_RSLPO_BADI_PARTITIONING~GET_T_PART_CRIT.

DATA: l_id TYPE c length 2,
      l_s_part_crit TYPE rslpo_badi_s_part_crit,
      "SPOCRITERIA Variable
      l_it_criteria TYPE TABLE OF ZSPOCRITERIA,
      l_wa_criteria TYPE ZSPOCRITERIA,
      "ZSPOINFOPROV Variable
      l_it_spoinfoprov type table of zspoinfoprov,
      l_wa_spoinfoprov type zspoinfoprov.

SELECT * from ZSPOINFOPROV into CORRESPONDING FIELDS OF TABLE L_IT_SPOINFOPROV where SPONAME = I_SPO.

Loop at L_IT_SPOINFOPROV into L_WA_SPOINFOPROV.
  SELECT * from ZSPOCRITERIA into CORRESPONDING FIELDS OF TABLE l_it_criteria where patternid = L_WA_SPOINFOPROV-PATTERNID1 or patternid = l_wa_spoinfoprov-patternid2 or patternid = l_wa_spoinfoprov-patternid3 or patternid = l_wa_spoinfoprov-patternid4.

  LOOP AT l_it_criteria INTO l_wa_criteria.
    SELECT INFOOBJECT FROM ZSPOPATTERN into l_s_part_crit-IOBJNM where patternid = l_wa_criteria-patternid.
      If L_WA_CRITERIA-HIGHVALUE NE ''.
        l_s_part_crit-opt = 'BT'.
      ELSE.
        l_s_part_crit-opt = 'EQ'.
      ENDIF.
      UNPACK L_WA_CRITERIA-PARTGROUP to l_id.
      l_s_part_crit-IDPART = l_id.
      l_s_part_crit-low = l_wa_criteria-LOWVALUE.
      l_s_part_crit-high = l_wa_criteria-HIGHVALUE.
      l_s_part_crit-posit = L_WA_CRITERIA-PARTGROUP.
      APPEND l_s_part_crit TO r_t_part_crit.
    ENDSELECT.
  ENDLOOP.
ENDLOOP.

endmethod.

The method IF_RSLPO_BADI_PARTITIONING~GET_T_PART_PROP will only be initialized with the following code:

1

"Coding will follow later

The next and last method is IF_RSLPO_BADI_PARTITIONING~GET_T_PART_DTP. It specifies the template of the DTP.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

method IF_RSLPO_BADI_PARTITIONING~GET_T_PART_DTP.

DATA: l_posit TYPE i VALUE 1,
      l_cnt TYPE i,
      l_id TYPE c LENGTH 2,
      l_s_part_dtp type rslpo_badi_s_part_dtp,
      "ZSPODTP Variable
      l_it_dtp type table of zspodtp,
      l_wa_dtp type zspodtp,
      "ZSPOINFOPROV Variable
      l_it_spoinfoprov type table of zspoinfoprov,
      l_wa_spoinfoprov type zspoinfoprov.

SELECT * from ZSPOINFOPROV into CORRESPONDING FIELDS OF TABLE L_IT_SPOINFOPROV where SPONAME = I_SPO.

Loop at L_IT_SPOINFOPROV into L_WA_SPOINFOPROV.

  SELECT COUNT(*) FROM ZSPOCRITERIA into l_cnt where PATTERNID = L_WA_SPOINFOPROV-PATTERNID1.
  SELECT * from ZSPODTP into CORRESPONDING FIELDS OF TABLE l_it_dtp where SPONAME = I_SPO.

  LOOP at l_it_dtp into l_wa_dtp.
    l_s_part_dtp-DTPTEMPLATE = l_wa_dtp-DTPTEMPLATE.
    l_s_part_dtp-OBJNM = l_wa_dtp-OBJNAME.
    l_s_part_dtp-LOGSYS = l_wa_dtp-LOGSYS.
    l_s_part_dtp-TLOGO = l_wa_dtp-OBJTYPE.
    WHILE l_posit LE l_cnt.
      UNPACK l_posit to l_id.
      l_s_part_dtp-IDPART = l_id.
      APPEND l_s_part_dtp TO r_t_part_dtp.
      l_posit = l_posit + 1 .
    ENDWHILE.
  ENDLOOP.
ENDLOOP.

endmethod.

After all methods are implemented, activate the Enhancement Implementation. Now we are able to create a Semantic Partitioning Object (SPO). What we need to maintain will be described in Part 3 of this series.

These posts might also be interesting:

• SAP BW find meta chain
• SAP BW Change Object Directory Entries
• SAP BW Transport of Copies (ToC)
• SAP BW Copy Queries to a new MultiProvider

I am Tobias, I write this blog since 2014, you can find me on twitter and youtube. If you want you can leave me a paypal coffee donation. You can also contact me directly if you want.

At my current project I needed a way to create Semantic Partitioning Object (SPO) via BAdI to reduce the end-of-year work. After a little search via Google (you cannot find anything on the new
SAP Community Page), I found these threads.

• Implementing Pattern-based Partitioning using the SPO BAdI
  – Part 1: Control Tables
• Step by step procedure to create dynamic partition on SPO using
  BAdi

Both were not perfect, so I build a solution between them. I also put everything via control tables, so it would be easier for the users to manage them. So let’s get started.

The following domains have to be implemented:

• ZSPOPARTGROUP – SPO Partition Group
• ZSPOPATTERNID – SPO Partitioning Pattern
• ZSPOTLOGO – SPO Object Type for DTP

After we created the domains, we have to create the following data elements:

• ZSPOPARTGROUP – SPO Partition Group
• ZSPOPATTERNID – SPO Partitioning Pattern
• ZSPOPATTERNID1 – SPO Partitioning Pattern 1
• ZSPOPATTERNID2 – SPO Partitioning Pattern 2
• ZSPOPATTERNID3 – SPO Partitioning Pattern 3
• ZSPOPATTERNID4 – SPO Partitioning Pattern 4
• ZSPOTLOGO – SPO Object Type for DTP

Note: The data elements ZSPOPATTERNID1, ZSPOPATTERNID2, ZSPOPATTERNID3 and ZSPOPATTERNID4 are defined like the ZSPOPATTERNID.

We also implement a search help ZSPO_DTPTEMPLATE – SPO Templates

After all these elements are created, we can now create the following transparent tables:

• ZSPOINFOPROV – SPO BAdI Managed InfoProvider
• ZSPOPATTERN – SPO Authorized Partition Pattern
• ZSPOPATTERNT – SPO Authorized Partition Pattern Text
• ZSPOCRITERIA – SPO Pattern Partition Criteria
• ZSPODTP – SPO BAdI Managed DTP

The following fields have to be implemented:

• PATTERNID
• INFOOBJECT

This entry helps and checks have to be implemented:

The following fields have to be implemented:

• LANGU
• PATTERNID
• TXTLG
• TXTSM

This entry helps and checks have to be implemented:

The following fields have to be implemented:

• PATTERNID
• PARTGROUP
• LOWVALUE
• HIGHVALUE

This entry helps and checks have to be implemented:

The following fields have to be implemented:

• SPONAME
• PATTERNID1
• PATTERNID2
• PATTERNID3
• PATTERNID4

This entry helps and checks have to be implemented:

The following fields have to be implemented:

• SPONAME
• OBJTYPE
• OBJNAME
• LOGSYS
• DTPTEMPLATE
• DTPTEMPLATEID

This entry helps and checks have to be implemented:

After we created all control tables, we can now create an implementation of BAdI RSLPO_BADI_PARTITIONING. How this works, can be read in Part 2.

These posts might also be interesting:

• SAP BW 7.4 Maintain characteristics
• SAP BW remove symbols
• Setup BW/4HANA on Amazon AWS
• List of all SAP BW Users

I am Tobias, I write this blog since 2014, you can find me on twitter and youtube. If you want you can leave me a paypal coffee donation. You can also contact me directly if you want.

So after I read a lot about BW/4HANA, I decided to create a own SAP BW/4HANA 1.0 [Developer Edition] instance on my Amazon AWS account. First I had to extend my normal AWS account with a IAM
user. For this you choose under Security, Identity & Compliance >> IAM. Under Users you click on Add user.

You have to give the user a name, in my example bw4hana and as access type I choose Programmatic access. Next step is to set the permissions. I only attach
existing policies directly, because it is only a test user. The following policies are needed:

• AmazonEC2FullAccess
• AmazonVPCFullAccess
• ReadOnlyAccess
• AWSAccountUsageReportAccess

After you created the user, you have save your access key id and secret access key. These are required for the set up on the page cal.sap.com. After you logon you can choose the SAP BW/4HANA 1.0 [Developer Edition]  easily by click on Create Instance. Now
you need the access key id and the secret access key to set up your instance. The costs are:

• 1,31 USD per hour when the system is active and you use it
• 23,00 USD per month when the system is suspended

So you can see you don’t have to spend a lot of money to test the new technology. The setup process takes about 60 minutes.

Note: The interesting part is you don’t need a S-User, you can also use a P-User.

After the setup is done, you can access the systems via RDP oder directly through a SAP Logon Pad. I used the SAP Logon Pad, because on my machine is also Analysis Office, Design Studio and the BW Modeling Tools
installed. So I ran into my first issue, there is no RSA1 anymore. You have to use the BW Modeling Tools. Which is in some places hard to use, I hope they will fix some stuff there.

After a little bit playing with new objects and load some sample data my first test ended here. So stay tuned. If there are any questions post them down here in the comments.

These posts might also be interesting:

• BW Modeling Tools
• SAP BW Create SPO via BAdI – Part 1
• BW/4HANA Export Transports
• SAP BW Change Object Directory Entries

I am Tobias, I write this blog since 2014, you can find me on twitter and youtube. If you want you can leave me a paypal coffee donation. You can also contact me directly if you want.