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.):
Archive for the 'Basis' Category
There are wonderful reports available in standard SAP’s Information Structures (E.g. MCxx reports). It can be so cruel though when data gets corrupted. You usually end up comparing report figures with whatever reasonable value you find elsewhere in SAP. If you want to be sure about the Information Structure’s reliability it is worthwhile to update an infostructure (say S021 – Production Order), store it under a temporary version ‘&(1′, and finally call this test version in a report that default uses version ’000′.
To call up another version than ’000′ go to System > User profile > User parameters and enter the parameter ID ‘MCR’ with the value ‘X’.
Now if you call up a standard analysis like MCP3 – Production Order Analysis a new field is visible for version selection. See picture below.
The major benefit of this procedure is that you don’t have to backup/delete current production data in version ’000′.
It is also possible to compare the current version ’000′ with the new test version going to Menu > Edit > Comparisons > Planned/Actual…
Last week I spent some time finding out how to implement barcode printing in SAP. As usual I googled the internet and a couple of alternatives were flung at me: middleware, hardware vendor applications, installing fonts, etc.
Interestingly enough there is one very simple solution: using the standard barcode font that SAP standard offers for SmartForms. You wonder why there are so many alternatives while SAP already includes the easiest one. The main requirements for printing barcodes this way are:
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
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:
- 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 ).
- 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.
- finally check Excel options (Tools > Options ). Either use system settings or enter the figures manually.
Now you are set to avoid frustration.
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.
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.
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.
2) In the command field enter ‘&SAP_EDIT’ and press enter. The maintenance indicator in SE16N will switch on.
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.
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
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.