Month: October 2013

Wow…  I have to tell you, I pretty much feel like the dumbest guy on earth right now.  I’ve been fumbling for a few hours trying to do something as simple as automatically generate an inbound delivery for a repair order.  To set the stage, I’m trying to generate data in my test system is an automated fashion.  In short, I realize I need a lot more data to help me test the performance on my dashboards.  Well, if you want to at least make it look good, you should be generating some data every day, pretend like it’s a real company.  So I’ve got notification being generated every day, repair sales orders, and I thought the inbound delivery would be a nice easy piece…  Well, shame on me…

After spending way too much time on this, I wanted to give you benefit of my bonehead day.

1.  Be careful if you try to do BDC with an Enjoy transaction.  Sometimes it works, sometimes weird things happen, especially in the background.  I found this with VL01N.

2.  Most popup message DO NOT need to be addressed in the BDC.  This was the point that killed me.  I set it up to work perfectly on-line.  My example was to create an inbound delivery with serial number.  Well, if you have a status of ECUS on the serial number/equipment, you get that annoying popup to tell you that.  I confess, I haven’t played with BDC in a while, so I totally forgot that even though it happens on-line and in error mode, it doesn’t happen when you move to N mode.  “Doom on Me”, as one of my  favorite authors always said.  I eventually came to the revelation to find everything worked great.  DOH!

3.  Use transaction SHDB to get your recording information.  But remember #2 above.

Anyway, just wanted to float that tidbit out there in case you might be thinking of trying anything similar.

Thanks for reading,

Once again, thanks to my good friend Jeremy.  He has once again given me a cool tool to use.  The report:
RPR_ABAP_SOURCE_SCAN
It works as a Where Used within code to find any particular statement.  It’s provided by SAP, but like so many thing, it isn’t advertised.  Jer deals with a highly customized environment, so this tool is invaluable.

Here’s the basics of it, you get to define define what program(s) you want to search through (along with lots of other selection options).  Then enter in the String you are looking for.

In my recent optimization, I needed to hunt through my code and find all the places I was using ENDSELECT.  It would’ve been much easier had I used this program to find everywhere, instead of my hunt and paste methodology going through lots of different programs and ABAP methods.  So, my gift to those of you that didn’t know about this, here you go.  Courtesy of SAP =)
Thanks for reading,

One of my favorite tools when I’m developing is transaction SE30, ABAP Runtime Analysis.  I’ve been using this a lot more lately in an attempt to optimize my code in my Service Management Dashboard.  Whenever you deal with a dashboard, you are always hitting a lot of different tables, as well as implementing a lot of different code.  Using SE30 is a great way to quickly see the biggest pain points in your code.  Let me walk you through the basics of using it.

I’ve highlighted the 4 biggest fields you need to enter to execute it.

1.  Description
2. Transaction/Program/Function Module – I’m a fan of transaction whenever it’s available, but pick what you have.
3.  Execute Button – press when you populated everything else.
4.  Variant if you have one.

Press execute button, and you’ll see your program/transaction.  Execute all the steps you want to analyze.  Be careful with this step.  You maybe want to pinpoint certain parts of the transaction, and if you click too many options your results could be scewed.

When you’re done, you’ll this on the bottom.  Press Evaluate, and now you can start the real work.

This next screen will show you where all the work is, is it in ABAP, the Database, or the system.
PRess F5 to start the hit list.

Now, here’s all the information.  The column I tend to pay the most attention to Net %.  I will typically sort on this column to see where the worst performing code is.  Now you do need to be aware, that a lot of times your problems can be “obscured” if you code is too modular.  You may simply see that most of the time is in one function call or one method call.  So you may need to “throw” those numbers out and pay attention to next items on the list.  But i’m sure you’ll figure that out quick enough
Thanks for reading.

Today, special thanks go out to my buddy Jeremy.  He set me straight on some things, and helped me streamline my code in my service management dashboard.

I’m quickly learning that my system works great, except when it comes to volume testing.  (I’m working on this in a separate initiative).  But back to my original thought.  The select statement.  I found out recently that using the SELECT with an ENDSELECT Statement to close it off, and then add some logic in the middle is terrible when it comes to database performance.  Take this example:

Select vbeln posnr from VBAP into (lv_vbeln, lv_posnr)
for all entries in table LT_TABLE
where pstyv = ‘TAC’.
<add some logic here>
endselect.

While this code works, and will produce the correct results, as the table VBAP grows, so will the runtime.  Now, the better approach (thanks Jer), is to build and internal table first, then loop through it…  like this.

define a type and a table for lt_result with the fields you want (vbeln & posnr)

Select vbeln posnr from VBAP lt_result
for all entries in table LT_TABLE
where pstyv = ‘TAC’.
loop at lt_result into wa_result.
<add some logic here>
endloop.

Now, this will improve performance, but the real trick to employ if you need to improve performance is to provide an index on the table you are seeing poor performance.  In essence, the index on a table is a lot like changing the key fields set for the table, and allows for faster searching.  This obvious involves a basis person and some additional storage space.  So, if you need to improve performance use the following guidelines.
1. try to set the key fields in the where statement.
2. avoid the select/endselect combination.
3. if using inner join, make sure you need to do it, and try to limit the number of inner joins to 2 or 3 tables max.
if you follow these guidelines, you code should work in nearly any enviroment.
Again, thanks Jer.  And for everyone else, Thanks for reading.