Monday, December 2, 2013

How to copy BEx RKF (Copying Calculated/Restricted Key Figures)

There is an easy way to make a copy of you global Restricted/Calculated Key Figures. You can copy within the InfcoCube / MultiProvider or copy for one InfoCube to the second one.

Here are the steps:

  1. Run transaction code RSZC
  2. Choose the name of source and target object (it could be the same object)
  3. Choose the type of structure, you would like to copy
  4. Select the object and enter a new technical name for the copied objects.

 

In the same way you can copy other structures like query, filter, structures.

Tuesday, December 4, 2012

SAP BI Analysis Authorization - required concept in BW 7.3x

SAP NetWeaver BW 7.3 brings a lot of new features. Some old concepts are also superseded by new ones. The 'old' reporting authorization is no longer supported by BW 7.3. You need to migrate to analysis authorization before upgrade. You also can't switch back to 'old' concept.

When upgrading to analysis authorization, the following Notes will help you:

      931898 Migration Analysis Authorizations
      938871 Migration Reporting Authorizations II
      1001652 (characteristic 0TCAKYFNM), 958665, 946724
      942799 and 944929 (RSECADMIN)

There is an interesting Expert Session on upgrading into BW 7.3, that covers authoriation topics.

What kind of problems did you faced during authorization swith? Please share with us your experiences!

Tuesday, February 21, 2012

Attributes Change Run - applying changes in aggregates

Basics of Attribute Change Run

Attributes Change Run applies changes into aggregates if there was a change in navigation attributes used in aggregates or in hierarchies of a characteristic.

This process in necessary, because in aggregates data from InfoCube are persistently stored in aggregated form (In InfoCube, no data related to navigation attributes or hierarchies are stored).

To start Attributes Change Run, go to:

RSA1, use menu Tools>Hierarchy/Attribute Changes.

You will see there a list of available sets of InfoObjects and appropriate change status.

If you mark a line, and click InfoObject List button, you will see a list of objects that are planned for that Change Run.

The second important button is Execute button. Use it when you already market the line, for which you would like to start Attribute Change Run.

Change Run process steps

  1. Change Run checks which characteristics and hierarchies had changes since the last change run. Run specifies which aggregates must be adjusted.
  2. Change Run apply changes (dialog process for each required InfoCubes' aggregates).
  3. Activation of changes in master data and hierarchies.

There is a SAP lock, that (during point 1) is preventing other changes runs to start a job for the same time. Also rollups and aggregate builds are not executed. The name of the lock: CHNGRUN_ST

The second SAP lock (CHANGERUN) is locking objects (InfoObjects, InfoCubes, hierarchies) that are involved in the adjustment (point 2).

When the work is finished, the CHANGERUN lock is removed.

There could be only one change run in the initial phase (1). If other change run starts, it will fail immediately. It is not possible to start multiple change runs. Read about parallel change run in SAP Note 534630.

Additional Notes:

Change Run process can be monitored, restarted using RSDDS_CHANGERUN_MONITOR ABAP report. You can start it using se38 transaction.

It is better to run CHR for all newly loaded master data in the process chain. Do not start it for each master data load.

Usefully links:

Sunday, September 20, 2009

How to insert two queries into one BEx Analyzer workbook.

I frequently need to use data form different InfoProviders. Sometimes, instead creating MultiProvider, it is faster to put two or more queries into one workbook and create separate tab to display joined data. Here are 7 steps to create such a solution:

1. Create queries you would like to join.
2. Open one of the queries in BEx Analyzer and save it as a workbook.
3. Create two additional tabs in the workbook, and give them names (e.g., query2, results)
4. Edit the query2 tab by adding design items: click BEx Analyzer > Design Toolbar > Insert Analysis Grid
5. Click on the Properties dialog box, change Data Provider's name and click create button.
6. Choose the second query and confirm your choice.
7. Create a table, on the result tab, that merge data form both queries. Save the workbook.

What about selection screen? The variables related to the queries will be displayed on one selection screen, if you use the same variable in the queries - there will be only one field for the shared variables.

To learn more about analysis grid, read Analysis Grid section at sap.help.com.

Tuesday, June 9, 2009

Search sites about SAP BW using customer search

I created Search sites on SAP BW and Reporting, my search engine, focused on searching sites about SAP BW, using Google Customer Search. It shows results mainly form the sites: help.sap.com, sdn.sap.com, bwarea.com, sap.ittoolbox.com (BW group), sapfans.com (BW forum). If you think it is helpful, interesting or ... worthless - give me your feedback.

Monday, June 8, 2009

SAP BW Process Chains - automation and job scheduling

Would you like to automate repetitive BW tasks like loading transaction data? Create Process Chains!

Let's begin with basic definitions:
  • Process chain (PC) is a sequence of processes linked together.
  • Each Process have a type (BW activity, e.g., activate ODS) and a variant (contains parameters).
  • Start process describes when the process will start (immediately, scheduled job, metaprocess, API).
  • Connector is linking processes; you can choose 1 of 3 options of starting next process: when previous finishes with success (green arrow), failure (red) or always start the next process (black).
  • Variant is a set of parameters passed to the process, such as the name of the InfoPackage to use for loading, the name of the InfoObject to perform a change run for.
Selected icon bar buttons:
  • Planning view enables to create and modify processes.
  • Checking view checks consistency of a process chain selected in plan view.
  • Log view shows log of the execution of a process chain selected in plan view.
Selected left panel buttons:
  • Process Chains displays process chains.
  • Process Types displays process types, enable to drag and drop process into main panel.

The picture below shows simple PC (loading transaction data into ODS and than into InfoCube).


Loading Hierarchy using Process Chain

Now, we will describe how to load a hierarchy into an InfoObject. The process will start every day at 1PM. The process chain will have the following processes:

Start >  Load Hierarchy > Save Hierarchy > Attr. Change Run

1. Start transaction RSPC and choose Process Chain > Create. Enter a name of the chain and description. You will be asked to insert a name of start process - choose New, enter a variant name and description.
2. Select Direct Scheduling option and click Change Selection. Click Date/Time, enter schedule start date and hour (current date, 01:00:00). Click Period values > Daily > Save > Save > Save > Back
3. Click Process Types button on the left panel. Expand Load process and click twice Execute InfoPackage. Choose the InfoPackage for the Hierarchy you would like to load and confirm the choice. To connect the Start process with the load process: right click on the Start, choose process > Connect with > Load Data > created process. 
4. Add processes to save hierarchy and attributes change run (commits changes in the InfoObject).
5. Save the process. Click Checking View button. If the chain is OK, activate and schedule the chain by clicking Activate and then Schedule buttons.

Additional information
  • To work with PC, you need authorization for authorization object S_RS_PC.
  • To monitor selected processes create a list of PCs using TCode RSPCM. This tool will enable you to see statuses of selected PCs and provide a link to process chains' log.
  • To have a PC that can be scheduled and maintained only in specified client - press Process Chain > Attributes > Editing Client, and enter the name of the selected client.
  • To transport client dependant PC with complete starting options, enter required background user data in the target system using TCode RSTPRFC.
  • If you transport PC with scheduling option: immediately the PC will start immediately after the transport.
  • To "stop" scheduled PC click Execution > Remove from Schedule.
  • To see overall PCs status - start BWCCMS tool.
  • PC can send e-mail message when process failed. To create e-mail alert right click on the process and choose Maintain Message option.
  • To see technical names and additional information about processes: click View > Detail View.
Examples of BW PC
Example of processes sequence when deleting overlapping requests form a InfoCube:
Start > Del. indexes > Load InfoCube > Delete Overlapping request > Gen. Indexes

Loading hierarchy, attributes and texts into InfoObjects:
Start > Load Attr. > Load Hierarchy > Save Hierarchy > Attr. Change Run > Load Texts

Additional resources:
Creating process chains (SAP Help)
Decision Makers in PC (SDN Article)
Create process chain - step by step tutorial (SDN Blog)
Presentation on Process Chains (SAP Library)

Wednesday, March 18, 2009

Transporting SAP BI queries

In this post I present basic steps to transport SAP BI queries from development to quality server. The steps are performed in source and target system, so you need authorizations to release and import objects.

Source system
Start with transaction RSOR (Transport Connection), insert initial and target source system names using Conversion button (2) and choose grouping type (3). Select queries you would like to transport to target system and press Execute and than Transport objects (truck) button.


Release the change request to transport using SE10 transaction. Press Display, choose tasks and requests you would like to release and press the button with single truck (or F9). When both task and request have been released successfully, start transport in target system.

Target system
To import queries to quality system start STMS transaction > Import Overview (F5) > Display Import Queue. On the Import Queue screen select the request and press Import (truck with a small loading). Choose target client's number and press enter. The queries will be written to the target system.

Standard BEx Transport Request
When the request, you have released, was set as Standard BEx Transport Request, you need created a new standard request. If there is no standard request, nobody is able to process queries or workbooks on the system. When you try to do so, you will receive the error: The query could not be saved due to a problem in transport. BEx transport request is not available or not suitable.

To create a new request you need to press BEx and than Assign / Delete button, add the request and save the choice.


Now all new objects and modifications will be written to the chosen BEx transport request. For more information on the standard transport request see this note:194051.

Additional resource:
Transporting: role and objects.
Authorizations for change and transport: S_TRANSPRT and S_CTS_ADMI.