SAP Mental Notes » Basis

SQVI – Create quick report

Kowboy — Fri, 23 Jan 2009 07:36:32 +0000

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.):

1) Go to transaction SQVI: In the section ‘Quickviews for …’ you may see some prepared reports already. Since you are new to this it is likely to be empty. Since we are going to create a new report enter a name for the report in the Quickview name field and press < Create>.

SQVI - Main screen

2) In the selection window enter descriptions and choose ‘Table join’ as ‘Data source’. This means we are going to connect and use multiple tables. Press to continue.

3) In the screen ‘Choose data source’ press the ‘Insert table’ button. In the window that pops up enter the name of the table that you need.

SQVI - Add table

4) Repeat the previous step for all required tables. Your screen will now look like below:

SQVI - Tables

5) Press ‘F3′ to go to the configuration screen. In the left side of the screen you can select per table which fields are for selection and/or list purpose. E.g. if you only select a field as ‘List field’ it will show up in the report results, but will not appear in the selection screen of the report as a filter criterium. For the header I choose: document number, doc date, sales organization, distribution channel and sold-to party (all list and selection). On item level I select: Material Number and Reason for rejection (to be able to exclude rejected lines). Both List and Selection. For Schedule I pick: Item, Schedule Line, Schedule line category, Schedule line date and Confirmed qty. Only Schedule line category and date both List and Selection. The others only List. Now your screen will look like below.

SQVI - Fields selected

6) Now it’s time to test drive your report! Press . It takes a short time for SAP to build te report. You are taken to the selection screen of the report. Now it is important that you have an idea of what data you are going to find. Enter filter criteria based on this idea. I mention this because you need to validate the data you will be presented in the report. Do not just accept the quantities. Analyze the results and if the numbers are off find out why and adjust your report’s filter criteria and/or add extra filters to remove redundant data.

SQVI - Report

7) If you are satisfied with the quality of the report save it for future use. It is possible to link it to a transaction code and make it accesible for users through authorization. I will post a guide on this in the future.

Kowboyz BV / CC BY-ND 3.0

Test standard LIS analyses with different source versions

Kowboy — Wed, 14 Jan 2009 10:27:05 +0000

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’.

Parameter MCR

Now if you call up a standard analysis like MCP3 – Production Order Analysis a new field is visible for version selection. See picture below.

MCP3 - New version field

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…

Kowboyz BV / CC BY-ND 3.0

Printing barcode labels in SAP R/3

Kowboy — Thu, 13 Nov 2008 13:36:59 +0000

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:

It will only work with SmartForms. If you are still using SapScript this is the time to switch to the modern era of form design.
SAP R/3 4.6C: you are running an older version? Seriously? Then wake up your CIO.

How to approach label design with barcodes:

1) Design the label: choose the text elements and the type of barcode. Think about what technical data elements to include and from what structure table these can be taken (e.g. MATNR for material number). The below example is designed to let the barcode represent the batch number.

Bar code label

2) In your design include Font: standard text is Helvetica, but your barcode is the standard font that SAP offers. Go to transaction SE73 to create the appropriate barcode type. On the opening screen of SE73 choose “System Bar Codes” > Change.

3) On the screen choose Create (F5). Choose new barcode technology. Run through the steps that SAP offers you. It will ask you what type of barcode you prefer. Code 128 is a common type that will fit your need in most cases. Create your new type starting with ‘Z’.

4) The developer will make sure that using your data elements and font types in SmartForm the label will be ready for use. If your batch code (CHARG) is ’1234567890′ then with the new barcode font this number will be displayed as the barcode in the example label above.

5) Set up the output configuration through customizing. In case of GR labels: IMG > Materials Management > Inv Management and Phys Inventory > Output Determination. Unfortunately the special label output determination (output types WEE1, WEE2 and WEE3) don’t go together with SmartForms. This means you cannot use the ‘special’ label output determination as described here.

Other

If you experience problems printing barcode labels in SAP, below you find links to two of the most popular printer vendors who partner with SAP:

Printing SmartForm barcode labels with SATO
Printing SmartForm barcode labels with Zebra

Below is a link to SAP note 64158 that explains in nitty-gritty detail the new bar code functionality (SAP Service log-on required):

SAP note 64158 – New Barcode Technology for SmartForms

Finally, if you wish to stick to SapScript for your forms and require barcode support, I recommend following solutions that involve installing a SAP barcode printer driver on your local machines. Site licenses are approximately 1200 EUR (1500 USD). Demos are available at:

Barcode .dll by TEC-IT
Barcode .dll by e-bizco.com
Barcode .dll by MW6 Technologies

Kowboyz BV / CC BY-ND 3.0

Change log SE16N

Kowboy — Tue, 11 Nov 2008 14:33:09 +0000

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

Kowboyz BV / CC BY-ND 3.0

Decimal separator

Kowboy — Tue, 28 Oct 2008 21:02:54 +0000

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.

XP control panel

Kowboyz BV / CC BY-ND 3.0

No related posts.

Customizing Change Log

Kowboy — Tue, 28 Oct 2008 20:48:14 +0000

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. Related posts:Change log SE16N Related posts:

Change log SE16N

Transaction variant

Kowboy — Sun, 26 Oct 2008 19:13:50 +0000

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

Kowboy — Sun, 26 Oct 2008 18:59:55 +0000

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.

Step-by-step

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

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

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

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

Kowboyz BV / CC BY-ND 3.0

Transaction usage history

Kowboy — Sun, 26 Oct 2008 18:59:16 +0000

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.

Transaction variant