The SAP Transport Dependency Check (TDC) is a little tool that helps you to find corresponding transport requests in your SAP NetWeaver Business Warehouse  which are not imported yet in your
target system (e.g. production system). First you have to enter a transport request you want to check and also a target system and the last considered date (e.g. last go live).

You can either have a look at a compressed view where you can only see the transport requests.

Or you choose the detail view which allows you to see every object on the transport request.

If you have the same problems as I do in some projects you will love this tool, because it makes your project day easier. If you have any questions feel free to contact me. You can get it in the
online store and soon there will be other useful ABAP tools available.

In our current project we had to deal with the requirement that the enduser only want to show a certain node of a hierarchy to filter. So we used the F4 restriction from the transaction spro. You
find the entry under Business Warehouse >> Enhancements >> BAdI: Restricting the Value Help in the Variables Screen. We implemented it in
the method GET_RESTRICTION_NODE.

At this time I had only experience with the method GET_RESTRICTION_FLAT and searched for implementation examples. I found a wiki entry on scn. In our case we had bookable nodes so we implemented it like
this to get these node and all children of it.

l_s_node-nodename = ‚NODE1‘.

l_s_node-niobnjm      = ‚ZZ_IO‘.

Append l_s_node to c_t_node.

But it didn’t work out. The debugging showed no error, but the restriction always showed the complete hierarchy. After a little digging we found our mistake, it have to look like the follwing:

l_s_node-nodename = ‚LEAF1‘.

Append l_s_node to c_t_node.

l_s_node-nodename = ‚LEAF2‘.

Append l_s_node to c_t_node.

And so on for all leafs. So we had to add all leafs and not the nodes. I didn’t found any good explanation so here is the short article about it. Thanks to my
collegue who had the problem.

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 the hide a position in a hierarchy, because it is a departmental requirement. The hierarchy is used by many departments so we cannot change it and we also don’t want
to have the same hierarchy two times (except for the one position). So we first excluded the position in the query.

But this didn’t worked.

So we had to think what could we do to hide the specific position of the hierarchy. So we think how could we hide a specific position and the idea was to use a customer exit variable. You find
the coding on Github. After I implemented the
customer exit, only the position „EBIT“ is now hided.

These posts might also be interesting:

• SAP BW Filter with Routine
• SAP BW: Keyfigure to Account Model
• SAP BW Use Pattern in Variable with Customer Exit

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 have to filter data with a lot of logic. So I build some ABAP routines in a DTP filter to receive the necessary data.
First you have to open the DataTransferProcess (DTP) in change mode and select the Filter button on the Extraction tab.

Now a new window is opened. You see the selection for the DTP. If your field is not visible, click on Change Selection and select the necessary field. When you have the field you
want to filter, use the small icon on the right to create a ABAP routine.

Enter a name for the routine and you see the following screen.

And now we have the full power of ABAP to build some really cool stuff. My example is we read a hierarchy and select all leaves under a node and set the DTP Filter with it. Or you read the
attributes of an InfoObject and select all entries which are equal to the attributes and enter them into the filter.

After I have now all elements in an internal table, I can add them to the DTP Filter.

After we saved our development and go back, we see a the little ABAP icon on the right (highlighted in red). If you want to remove a filter, click on the trashcan to remove the logic.

Sometimes it is necessary to filter your data. You could do this in different ways, but the most effiencient way is the DTP filter. Because the loading don’t touch the data you not select. If you
remove the data via a start routine, all the data has to be catched from the database and you select more than you need at the end. 

Besides ABAP routine you could also use variables to filter data. In SAP BW/4HANA the filter is a little bit different this will be covered in another post. 

In my current project I have a file to import, which only delivers me a string with a length of 1000. I also get a description what is in this file. Like the following points:

• Customer from 1 to 10
• City from 11 to 50

The file looks like: 0000123456London………………………. So I have a file and a description how to decode this file. Now I need to find a way to separate this information into
InfoObjects. I build a Z-Table which contains the decode information.

The content look like the following example.

After I filled all my necessary information into the table, I started to write my code in an expert routine. First I need some variables and internal tables.

1
2
3
4
5
6
7

DATA: lt_table0 TYPE TABLE OF z_dec,
      ls_table0 LIKE LINE OF lt_table0,
      lt_table1 TYPE TABLE OF z_dec,
      ls_table1 LIKE LINE OF lt_table1,
      lv_start  TYPE i.

FIELD-SYMBOLS: <fv_source> TYPE any.

After the variable declaration, we have to select our data and sort the internal tables.

1
2
3
4
5

SELECT * FROM z_dec INTO TABLE lt_table0 WHERE recordtype = 0.
SELECT * FROM z_dec INTO TABLE lt_table1 WHERE recordtype = 1.

SORT lt_table0 BY startfrom ASCENDING.
SORT lt_table1 BY startfrom ASCENDING.

Now we loop over the SOURCE_PACKAGE and loop over our internal table to assign all values.

 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

LOOP AT SOURCE_PACKAGE ASSIGNING <source_fields>.
  IF <source_fields>-field1(1) = 0.
   LOOP AT lt_table0 INTO ls_table0.
   "First I need to find the start of my information
     lv_start = ls_table0-startfrom - 1.
     "Now I assign the infoobject to my result structure
     ASSIGN COMPONENT ls_table0-infoobject OF STRUCTURE RESULT_FIELDS TO <fv_source>.
     "Here I write the value of string into the corresponding infoobject
     <fv_source> = <source_fields>-field1+lv_start(ls_table0-length).
   ENDLOOP.

   "Here we append the RESULT_FIELDS to the RESULT_PACKAGE.
   APPEND RESULT_FIELDS TO RESULT_PACKAGE.
  ELSEIF <source_fields>-field1(1) = 1.
    LOOP AT lt_table1 INTO ls_table1.
      "First I need to find the start of my information
      lv_start = ls_table1-startfrom - 1.
      "Now I assign the infoobject to my result structure
      ASSIGN COMPONENT ls_table1-infoobject OF STRUCTURE RESULT_FIELDS TO <fv_source>.
      "Here I write the value of string into the corresponding infoobject
      <fv_source> = <source_fields>-field1+lv_start(ls_table1-length).
    ENDLOOP.
    "Here we append the RESULT_FIELDS to the RESULT_PACKAGE.
    APPEND RESULT_FIELDS TO RESULT_PACKAGE.
  ENDIF.
ENDLOOP.

So when we now see the import file, which looks like the following.

The result looks like the a normal import.

You can download the whole source code from github. If
you have questions, feel free to ask.

These posts might also be interesting:

• SAP BW Create own reversal entry
• SAP BW Use Pattern in Variable with Customer Exit
• SAP BW: Keyfigure to Account Model
• 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.

In my current project we have a lots of source systems which delivers our data in a key figure model. In a normal case is this not a problem. But we need the values of the key figures in a
hierarchy. So there are two ways to realize it. First way would be we build a structure with restricted key figures and get our hierarchy. Here is the problem, the customer will need different
queries to realize his needs. If there is a change, we need to adjust different queries (each has a light different hierarchy) and the maintainace is immense.

Another way is to use an account model. Here is your first Problem, we only get a key figure model and it is not so easy to use rule groups or a simply routine, because we get around 100 key
figures. So it isn’t easy as Denis wrote in his post (this post is in German). But I found, really I can’t belive I found an article on the former SCN. This post decribes how to transform
a key figure based model to an account based model with some ABAP coding and an expert routine. So I think that must be the answer to my problem, but it isn’t so well writen that I could use it.
But the start was done. I need a Z-Table and some ABAP. First I created my Z-Table with four fields:

• MANDT
• AREA
• SOURCE_KF
• ACCOUNTPOSITION

AREA is necessary to use this table in different deparments, SOURCE_KF represents the source key figure for example /BIC/ZGROSSVAL and the
ACCOUNTPOSITION is the technical key of the account model, for example 15.

This was the easy part. Now I need some ABAP and here I had some struggle.

The Problem was the ASSIGN COMPONENT part, which I didn’t know how to work, but a colleague helped me here. So that’s it. The Z-Table can be modified to fulfill your needs, but the basic code
should help you to realize a solution.

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.