Tag Archive for 'Basis'

SQVI – Create quick report

In an earlier post I promised to give a quickguide to creating a query in SAP based in transaction SQVI. I’m going to show you how you can quickly build a custom report for reporting Sales Schedule Lines based on different filter criteria and multiple tables (VBAK, VBAP and VBEP: header, item and schedule line data resp.):

Continue reading ‘SQVI – Create quick report’

Change log SE16N

In SE16N you can change SAP tables directly. I explained how to in a previous post. I also warned for the risks involved in doing this. Luckily direct changes in SAP tables are also logged, so you can trace back to the culprit who messed things up. You can query the following SAP tables to report on hacks:
SE16N_CD_KEY : Change Documents – Header
SE16N_CD_DATA : Change Documents – Data

Decimal separator

Aaaaargh! This can be frustrating in reporting out of SAP into Excel: decimals are considered thousands separator or numbers are not recognized at all as a number. There are three settings involved. To properly solve this issue:

  1. first check what is the standard decimal figure used in your company. Then check if this is also used in SAP (System > User profile > Own data ).
  2. then check the regional settings of Windows (in XP look in Control Panel). The regional settings also determine the decimal settings. Make sure this is also in sync.
  3. finally check Excel options (Tools > Options ). Either use system settings or enter the figures manually.

Now you are set to avoid frustration.

XP control panel

XP control panel

Customizing Change Log

To review changes in customizing / IMG use transaction code SCU3. Make sure that logging is activated for the client. The system will ask you to do so and give instructions if it isn’t.

Transaction variant

Lots of clients who wish to make their SAP transactions dummy-proof by making fields mandatory, closing fields for editing or craving for default values. Different paths to Rome here, but one powerful solution being offered through transaction SHD0 in conjunction with SE93. The first transaction allows you to create a transaction variant where it is possible to hide fields, make them mandatory, add default values, add voice recognition, opt for world peace, etc. OK so the last two maybe not, but the message is: “you can do a lot of modifying here.” The second transaction SE93 allows you to link the variant to a new home made transaction code. Your customer will love you till the end of times because of this.

Edit SAP tables

No matter security on table editing. When in transaction SE16N use the command &SAP_EDIT in the command field in SAP and off you go: edit table content directly.

Know what you are doing cause this is far from a best practice way of changing data and can screw up things pretty bad if you don’t really know what you are doing. If the value that you wish to change is a dependent variable to another (background) process stay clear of this method. If you are not sure – seriously: don’t edit the table content.

See my other post on how to track change by people who edited tables with this method.


1) Go to transaction SE16N or alternatively use shortcut and type just ‘N’. Enter here the table that you wish to edit.

SE16N or just N

SE16N or just N

2) In the command field enter ‘&SAP_EDIT’ and press enter. The maintenance indicator in SE16N will switch on.

Command field entry

Command field entry

3) Narrow your search results by entering selection criteria and press F8 to run the report.

4) You can remove lines or just add/change data and press save.

&SAP_EDIT - SE16N - Table results

&SAP_EDIT – SE16N – Table results

Voila! You just hacked your way into the table structure and made some changes.

Update 05-Oct-2009: interesting comments made on this hack: blog on IT toolbox

Transaction usage history

A very useful tool to track usage of transaction: ST03N and STAD. This transaction can report on different levels how often a specific transaction is used and by which users. This can be handy in determining authorization profiles after Golive. It can also be used by Big Brother to check whether end user testing has really taken place.