Identify the most commonly used BW transactions for Planning and Consolidation for Netweaver (BPC NW) 7.5 and 10, and a brief explanation of their usage. It is aimed at BPC users that may be new to BW administration.
BW transction codes are technical names, with a commonly ambiguous combination of letters. When the transaction is opened, a menu item or ABAP program is initiated. This list contains the most useful BW transactions, when using and supporting BPC NW. The list expands on the note in the 'related content', by providing a description and screenshot (please click the thumbnail to enlarge) of each transaction. The reader will require a basic understanding of how to operate BW. Many steps do not include full step-by-step instructions, and some interpretation of the options presented may be necessary.
Each transaction is run by inputting the transaction code (t-code) in the input box at the top-left corner of SAP GUI.
If this box is not visible, it is compressed. It can be expanded by clicking the <| icon to the left of the save button. If you are currently in a transaction, you must put /n in front of a new transaction to open it in the same window. This will replace the current transaction, eg. /nSNOTE will open transaction SNOTE.
Installation and upgrade:
SPAM : Support Package Manager.
Used to install new Support Packages, in order to upgrade the version of BPC for Netweaver installed.
You must be logged into client 000 to access the full features of SPAM. The following are the typical steps to upgrade a Support Package:
- Load the package: Support package -> Load packages -> From Front End -> Select the package (available from the Service Marketplace
- Support package -> Import SPAM/SAINT Update
- Display/Define -> All components -> Calculate queue
- Support package -> Import queue
SNOTE : used to implement SAP Notes
Used to apply a note for a specific ABAP fix. Must know the number of the SAP note to apply.
The following are the typical steps to apply an SAP note:
- Download SAP note (Ctrl + F8)
- It will be listed as a new note, as per the screenshot above. Double-click the note to open it.
- The 'Implementation status' should be 'Can be implemented'.
- Implement SAP note (Ctrl + F1)
- At the 'Prompt for Transportable Workbench Request', Create Request (F8)
- Confirm changes
Administration and logs
RSA1 : overview of InfoProviders and InfoObjects
This is the primary tool for data warehousing processing tasks. It is used to provide data modeling, control, monitoring and maintenance functions of all SAP BW processes. In the screenshot below, 'Modelling' is the current function area open in the navigation window.
InfoProvider: Presents a breakdown of all BPC Appsets/Environments in BW.
ST22 : to find ABAP runtime errors (ABAP dumps)
The ABAP dump analysis lists the ABAP runtime errors that have occurred, which conform to the selection criteria inputted.
Above: An example of an ST22 dump.
SLG1 : Display application log
Given a specific criteria, the application log will collect messages, and display them as logs. For BPC NW, look for UJ* in the object field. It is possible to view more information on each log entry, including the return code. SLG1 is a useful tool to easily and quickly find the time and reason for a job failing.
SM21 : Display system log
This log contains all system errors, warnings, user locks and process messages of the BW server.
SU01 : User Maintenance
This transaction is useful for the following:
1. Managing Users, Groups, and Roles
2. Assigning Principals to Roles or Groups
3. Locking or Unlocking Users
4. Password Management
The screenshot above shows the roles assigned to a particular user. For more information: http://wiki.sdn.sap.com/wiki/x/280
Tracing and jobs:
ST01 : System trace
The most useful functionality of the system trace is 'Authorization check'. Checking all authorization objects, it will provide detailed descriptions of any missing authorisations that occur during the tracing period.
Follow the steps below to perform an authorization trace:
- Tick the 'authorization check' box
- Click 'Trace on' and perform the activity that you wish to monitor
- Click 'Trace off', and 'Analysis'
- Next screen set the restrictions, and click 'Execute'. The failed authorizations should be marked in red.
RSTT: MDX trace
MDX statements are not recorded in SLG1. MDX is the language used that allows BPC for Netweaver to interact with BW. It is possible to view these statements in RSTT.
Follow the steps below to perform an MDX trace:
- Provide the system administrator user ID to 'Trace User' field.
- Click 'Activate' and perform the traceable steps in the BPC client.
- 'Deactivate' the trace, and select 'Trace Collection' from the left pane.
- To view the log, note the log ID, and run program RSR_MDX_RSTT_TRACE_EXTRACT
SM37 : Overview of jobs running on the instance
This transaction allows your to check all background jobs, and their current status. It is possible to release processing jobs.
Programs and tables :
UJFS : File service
This transaction is an interface to access BPC NW web and file folders. Upon selecting an environment, users who are familiar with traditional file navigation structures will be able to rename, copy, lock, unlock, delete and download documents.
SE38 : Run ABAP programs
In the screenshot below, UJA_DATA_CHECKER can be seen input in the 'Program' field. It is possible to run, or view the source code for this program. If another program name is known, it can indeed be entered here. To find default ABAP programs for BPC NW, you can perform a search for UJ*. Run the program, press 'Execute' - and the interface will present you with any further inputs that program requires.
SE16 : Database tables browser
The table browser requires that the user already knows the name of the table. Most conveniently, the table names can be copied from the particular InfoCube in t-code RSA1. Enter the table name of the table, and select the button at the top left of the screen. The interface will present a selection screen, as an opportunity to select which fields in the table are viewed.