Technique/SAP BW2011. 7. 12. 10:34

Remodeling on DSO
Sriman Kanchukommala 
Business Card
Company: Cognizant
Posted on Jul. 11, 2011 09:15 AM in Enterprise Data Warehousing/Business Warehouse

 
 

Remodeling on DSO

Remodeling Overview

Remodeling on DSO is a new feature available from BI 7.3 which enables to change the structure of a DSO already loaded.

Note: Now this feature is supporting for DSO in BI 7.3 and not supported for Info objects.

Using remodeling a characteristic can be simply deleted or added/replaced with a constant value, value of another Info Object, with value of an attribute of another Info Object.

Similarly a Key Figure can be deleted, replaced with a constant value or a new Key Figure can be added.

This blog describes how to add a new characteristic to DSO using the remodeling feature and populating data for added Characteristic.

 Note following before you start remodeling process:

  • Back-up of existing data.
  • During remodeling process DSO is locked for any changes or data loads so make sure you finished all the data loads for this DSO till the time this process finishes.

Note following after you finish remodeling process and start daily loads and querying this DSO:

  • All the objects dependent on DSO like transformations, Multi Providers will have to be re-activated.
  • Adjust queries based on this DSO to accommodate the changes made.
  • If new field was added using remodeling than don’t forget to map it in the transformation rules for future data loads.

  Initial Structure of DSO

 Initial structure of DSO

 

 

 

 

 

 

 

 

 Start the remodeling toolbox. This can be done either via Transaction Code: RSMRT or from the DSO context menu.

 

In the next screen enter the technical name you want for the remodeling rule to be and in the next box enter DSO technical name being remodeled. Click on Create button.

 

 

In the next screen enter the relevant description and click on Transfer button.

 

Click on the Add Icon to create a new remodeling rule.

 

Select the radio button Add characteristic, enter/select the new characteristic.

 

Check the key field button

 

 Remodeling rule is now ready and can be scheduled. Click on the schedule button.

 

 Select the desired scheduling option. While the remodeling rule is being executed it can be monitored by clicking on the monitor button.

 

 DSO Structure after adding New Characteristic,

 

 Finally add the new characteristic to the query and execute it.

 

 

 

 

Sriman Kanchukommala   Mr. Srimannarayana.Kanchukommala is working as a Priciple Consultant in SAP BI for Cognizant Technology Solutions, with over all 8+ years of experience in SAP BI.


http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/25362%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A+SAPNetworkWeblogs+%2528SAP+Network+Weblogs%2529

Posted by AgnesKim
Technique/SAP BW2011. 5. 11. 22:59

Remodeling in SAP BI 7.0
nehagarg 
Business Card
Company: HCL Tech
Posted on May. 11, 2011 05:47 AM in Enterprise Data Warehousing/Business Warehouse

URL: http://help.sap.com/saphelp_nw04s/helpdata/en/9b/0bc041f123c717e10000000a155106/content.htm

 
 

Before the release of SAP BI 7.0, in the previous version 3.x; we were not able to redesign the info cubes without deleting the existing data from the info cube. We had to delete all the data, modify the cube & then re-load the data again. But with the release of 7.0; the concept of Remodeling introduced as a feature to change the design of an info cube without deleting the Existing Data.

 

Before starting with the steps of Remodeling, I would like to mention the Dos & DONTs –

  • No data loading should be in process
  • After remodeling, check all the BI objects that are connected to the InfoProvider like transformation rules, MultiProviders, DTPs have been deactivated. You have to re-activate these objects manually.
  • The remodeling makes existing queries that are based on the InfoProvider invalid. You have to manually adjust these queries according to the remodeled InfoProvider.
  • You cannot replace or delete units. This avoids having key figures in the InfoCube without the corresponding unit

Following are the steps to be followed

Go to the context menu of Info cube that is to be redesign, select Remodeling as shown in fig. or select the Administration tab from the Left Most Area. There you can select Remodeling or can go direct to the T-Code RSMRT.

Fig1

Fig2

It opens the screen for remodeling the info cube. Enter the Remodeling Rule name & the Info Cube name. Click on create button. Write the description for Remodeling Rule.

Fig3

Fig4

Select the Add button shown circled in the below figure. It adds an operation into the list.

Fig5

Select the Radio Button as per requirement. Here I am selecting the ADD Characteristics to add the info object into the Info cube.

Fig6

The Info Object 0REGION is the new field to be incorporated into the Info Cube by reading Master data from info object 0SOLD_TO. Click on Transfer Tab & then save the changes.

Fig7

**We can even fix the value for the new info object as a Constant or can do One to One Mapping with the existing characteristics in the Info cube or write a customer exit to populate the vale of New Info Object.

Fig8

Check the consistency of the Info Cube.

Now click on the Schedule Button & execute for either “Start Immediate” or “Start Later”.

Fig9

Monitor the request.

Fig10

Now go to the info cube in RSA1, check the new Info Objects incorporated into the Cube with their corresponding data.

Fig11

Fig12

Also remember to activate the Transformation as well as the DTP of the Info Cube. Now there you can map the new Info Objects in the transformation but no need to upload the whole data again.

In the similar way, we can delete the Characteristics from the info cube without deleting the existing data into the Info Cube.

nehagarg   SAP BI Consultant HCL Technologies


http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24470%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A+SAPNetworkWeblogs+%2528SAP+Network+Weblogs%2529
Posted by AgnesKim
Technique/SAP BW2011. 5. 10. 19:54

Interrupting the Process chain
YJV Active Contributor Silver: 500-1,499 points
Business Card
Posted on May. 10, 2011 02:36 AM in Enterprise Data Warehousing/Business Warehouse

 
 

 Scenario:

Let’s say there are two Process chains A and B and C.  A and B are the Master chains which extracts the data from different non sap source systems. All our BW chains are dependent on a non sap source system, when the jobs get completed on non sap systems, it’ll send a message to the third party system from where our BW jobs will get triggered an Event based.

Note: Reason why the non sap system sends the message to third party triggering tool is because when ever there is failure in the non sap System; it will not raise an event to kick off the BW chain(s). we have to trigger them manually. To avoid this we use the third party triggering toll to trigger the chains at a time using an Event .

Now C is dependent both on A and B, In other words C has to trigger only after A and B is completed. 

We can achieve this using the Interrupt Process type.                          

For example, if Process chain A got completed and B is still running, then using the Interrupt we can make the Process chain C to wait until both the Chains got completed.

Let’s see step by step.

 Process Chain A and B

image

 Process chain C

Process chain C is dependent on both A and B chains, we use interrupts (A_interrupt, B_interrupt) which will wait till those chains got completed.

image

Now let’s see how interrupt works

A_interrupt: Interrupting the PC C until PC A gets completed.

image

image

Copy the highlighted Event and Parameters

image

Enter the above copied Event and Parameter in the Interrupt Process type like below screen 

image

Activate and schedule all the three process chains.

Note: All the three process chains (A, B, C) get triggers on Event based.

When the process chain C is in Scheduling, you can see the job BI_INTERRUPT_WAIT      in both A and B chains like below screens.

image

Three chains (A , B , C) got triggered by the same Event

<image

 

C will wait for both A and B like below.

image

 

 

 


YJV  Active Contributor Silver: 500-1,499 points is a SAP BI consultant


http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24505%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A+SAPNetworkWeblogs+%2528SAP+Network+Weblogs%2529
Posted by AgnesKim
Technique/SAP BW2011. 4. 8. 23:59

BW 7.30: New MDX test environment
Roman Moehl SAP Employee 
Business Card
Company: SAP AG
Posted on Apr. 08, 2011 04:00 AM in Analytics, Business Intelligence (BusinessObjects), Enterprise Data Warehousing/Business Warehouse, Standards

 
 

Abstract

SAP NetWeaver BW 7.30 introduces a new test transaction for creating, running and analyzing MDX statements. The following article explains how you can use the test environment to efficiently use the query language MDX.

Motivation

MDX is a query language for accessing multidimensional data sources. It is the central technology of SAP BW’s Open Analysis Interface.

MDX allows dimensional applications to access OLAP data in a generic and standard-based way. Besides external reporting clients from other vendors, MDX is also used by SAP’s own products, for example by BusinessObjects Web Intelligence or BPC.

As a language, MDX offers a variety of functions that potentially result in very complex statements. Customers or client applications that create their own statements often lack of good editing- and tool support. Therefore, SAP BW 7.30 offers a new test transaction for composing, executing and analyzing MDX statements.

The new test transaction MDXTEST is typically used by developers (working on MDX-based integration for SAP BW), administrators and consultants.

Hands on MDXTEST

The new test transaction MDXTEST consists of three parts:

  1. Pane Section
  2. Editor
  3. ResultSet Renderer

MDXTEST Overview

Pane section

The pane section on the left side of the transaction consists of three sub sections.

Pane section

Metadata browser

The metadata browser exposes the ODBO related metadata of the selected Cube. The selected objects (for example Members or Hierarchies) can be dragged onto the MDX editor. This improves and accelerates the construction of MDX statements. The user sees all the available objects that are available for defining statements.

Function library

The function library provides a list of all available MDX functions and methods. For each function or method, a corresponding code snippet can be added to the editor by drag and drop. The functions in the browser are arranged by on their return types, for example Member, Tuple or Set.

Statement navigator

The statement navigator provides a list of stored statements. By double clicking on a statement, the statement is read from the persistency and displayed in the MDX editor. This allows the user to easily find the stored MDX statements.

Editor

The central part of the test transaction is the editor pane. The editor itself provides a set of new functionality that is known from the ABAP editor such as mono-spaced font for indentation and formatting, line numbering or drag-and-drop of function templates.

Editor

Pretty Printer

Most MDX statements are generated by clients. These statements are often not in a readable format. Most of them need to be manually formatted to get a better understanding of statement structure. In addition, the statements are typically quite complex and often consist of a composition of multiple functions. Formatting and restructuring of the statement consumes a lot of time. A built-in pretty printer transforms the text into a “standard” formatting.

ResultSet Renderer

The result of a MDX query is displayed in a separate window to analyze the statement and its result in a decoupled way. Besides the data grid, additional information about the axis and details about MDX-specific statistic events are added to the query result.

ResutlSet Rendering

Executing a MDX statement

Once you’ve constructed your MDX in the editor, there are two ways of executing the statement:

  1. Default: The status bar provides a default execution button. The statements are executed via the multidimensional interface and the default settings.
  2. Expert mode: If you need to run the MDX statement via a different interface, then the expert mode is the right choice. The expert mode is available via a button right next to the default execution button.

The expert mode provides the following options:

  • Interface: It’s possible to run a MDX statement via several APIs. The most common interface is the default multidimensional API. In addition, it’s possible to run the statement via the flattening or XML/A interface.
  • Row restriction: The flattening API allows you to restrict the range of rows that are about to retrieved. Besides a fix from- and to-number, it’s also possible to define a fixed package size. This setting is only available if the flattening API is chosen.
  • Display: The rendering of the result can be influenced by the display setting. In general, you can switch off the default HTML rendering. This might be handy if you run performance measurements and you would like to exclude the rendering overhead.
  • Debug settings: there are a couple of internal MDX-specific debug-breakpoints which are typically only used by SAP support consultants.

Summary

In this article, you learned about the new central UI for testing MDX statements. The various components of the test environment support you in creating, executing and testing MDX with minimal effort.

Roman Moehl   Roman is Senior Developer in SAP NetWeaver BW


http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23519%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A+SAPNetworkWeblogs+%2528SAP+Network+Weblogs%2529

Posted by AgnesKim
Technique/SAP BW2011. 3. 27. 15:24

SAP BW - RFC Function Module Reconciliation SAP BW and ECC Sales Header Data

Suraj Tigga    Article     (PDF 664 KB)     21 March 2011 

Overview

Document specifies the detailed understanding for reconciling the SAP ECC (Sales Order Header data - 2LIS_11_VAHDR) with the data loaded to SAP BI. Reconciliation of the data is done using RFC function module and ABAP report. Advantage of using this method is one can schedule the ABAP report at any specific time and get the detail list of mismatched Sales Order.

Posted by AgnesKim
Technique/SAP BW2011. 3. 27. 15:22

SAP BW - Excel Pivot Chart and Pivot Table Report (Excel)

Suraj Tigga (Capgemini Consulting)    Article     (PDF 590 KB)     21 March 2011  


Overview

Document explains to create Excel Pivot Chart and Pivot Table Report for the SAP BW data using Microsoft Excel.

Posted by AgnesKim
Technique/그외2011. 3. 27. 15:21

New Memory Analysis Tools for ABAP Web Dynpro
Stephen Pfeiffer SAP Employee 
Business Card
Company: SAP AG
Posted on Mar. 24, 2011 03:41 PM in ABAP

Before NetWeaver 7.0 EHP2, it used to be difficult to analyze memory problems that were really specific to an ABAP Web Dynpro application and not just related to some mammoth internal table deep down in the application logic.

The problem was that it was hard to see the forest for the trees in the Memory Objects ranking lists:

  • What objects belong to the ABAP Web Dynpro runtime?
  • What objects belong to the Web Dynpro application?  
  • What belongs to the backend infrastructure? 

The old memory analysis functions could not tell the difference between one type of object and another.   

Here’s an example:

 What memory objects belong to ABAP Web Dynpro?

In the New ABAP Debugger, the application-specific memory analysis tool for ABAP Web Dynpro brings some order to the situation and lets you analyze the memory consumption of your ABAP Web Dynpro application much more easily and efficiently.

 Memory Analysis Views for ABAP Web Dynpro

There is also an extra filter option that lets you hide memory objects that do not pertain to the Web Dynpro application and runtime. In this case, that includes objects that belong to the ESI framework (web service infrastructure).  Here, you can see the effect of the filter – it lets you concentrate exclusively on memory objects that belong to ABAP Web Dynpro.

 Memory Analysis Objects filtered for ABAP Web Dynpro

 

 

 

Stephen Pfeiffer   is a senior developer in the ABAP Infrastructure development group.



http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23873%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A+SAPNetworkWeblogs+%2528SAP+Network+Weblogs%2529

Posted by AgnesKim
Technique/그외2011. 3. 27. 15:19

New Memory Analysis Features in NetWeaver 7.0 EHP2
Stephen Pfeiffer SAP Employee 
Business Card
Company: SAP AG
Posted on Mar. 24, 2011 03:42 PM in ABAP

 
 

In the old R/3 days, ABAP programmers rarely needed to analyze memory consumption in their programs.  The simple and robust ABAP memory model made it very hard for anyone to program a serious ABAP memory leak.

With the addition of more types of dynamic memory objects – not just internal tables, but also strings, anonymous data objects, boxed components – and a trend toward transactions that live longer, it’s now possible to write an ABAP program that can run into memory problems.

Since ABAP programmers can no longer ignore memory consumption, the ABAP Workbench has greatly enhanced the memory analysis tools in the New ABAP Debugger and in the Memory Inspector (transaction SMI or S_MEMORY_INSPECTOR).

This weblog showcases the enhancements that come with EHP2:

  • The Dominator Tree (or keep-alive tree) for containment hierarchies in memory objects – which runtime entity is keeping which memory object alive. This new analysis tool is offered in both the New ABAP Debugger and in the Memory Inspector. 
  • The Memory Object Explorer in the New ABAP Debugger, for navigating up and down through the memory objects in the keep-alive hierarchy of objects. Starting from any memory object, you can navigate up to its parents or down to its children, and you can take a look at the contents of each memory object.
  • A separate weblog shows you the new Application-specific memory analysis tools in the New ABAP Debugger – for looking at the memory consumption of ABAP Web Dynpro applications. There is also a similar tool for analyzing Web Service / HTTP applications.

You may also notice that doing memory analysis in the debugger is much more comfortable, and that we have made improvements in the user interface in the Memory Inspector as well. But we do not go into these UI changes in detail, nor will we look at the Memory Inspector transaction in this blog.

The New Features in Practice in the Debugger

You do memory analysis usually for one of two purposes:

  • You want to see how big your program – or objects in it - are in terms of memory consumption. Is it bigger than you expect?  Usually you’re in the New ABAP Debugger when you do this.
  • You want to see whether you have a memory leak. Does the memory consumption of your program change over time?  Or – how did it get so big that it dumped because of lack of memory – this question also sometimes comes up.

Usually, you’re comparing memory snapshots in the Memory Inspector (transaction SMI) when you’re doing this type of analysis.

Let’s see how the new memory analysis features work if you are in the debugger, just checking how much memory your program uses. Maybe you’re just being cautious in doing this checking – or maybe you’ve learned:  a long-running transaction or service with lots of dynamic memory objects means, you better check the memory consumption before your customers find out about it for you.  What you see here on the new memory analysis features applies just as well in the separate Memory Inspector transaction.

A Comfortable Quick Look at Memory Consumption – The Memory Analysis Tab

You don’t have to switch to a memory analysis tool anymore to see how much memory objects in your program are using.  There’s a new Memory Analysis tab in the new ABAP Debugger, on the Variable Fast Display. Just switch to the tab, click on a variable in your program, and you can see how much memory the object uses.

The Memory Analysis Tab in the ABAP Debugger 

Here we have two tables that have the same number of rows, and we happen to know that they contain the same data - except that IT_CUSTOMERS contains extra data.  Even so, IT_CUSTOMERS is smaller in memory.  How is the difference explained?   Does IT_CUSTOMERS offer a more efficient way to organize the table?  A closer look shows that we don’t understand how IT_CUSTOMERS is organized. The table statistics don’t seem to match the memory size.

  • The size of table IT_SCUSTOM is okay – 4637 rows of 16 fields with a row-length of 464 bytes is close to the Bound Used Memory (bound memory is the memory that would be freed if the table were cleared) plus some management overhead.   The table simply is that big.
  • The size of IT_CUSTOMERS is puzzling. It has the same number of rows as IT_SCUSTOM but a row length of 32 bytes. No way that the table body itself comes close to 1.7 million bytes of bound memory.

Analyzing Table IT_CUSTOMERS with the Memory Analysis Tool

To study table IT_CUSTOMERS, you activate the Memory Analysis Tool by choosing the New Tool or Replace Tool button, opening the Memory Management folder, and clicking on Memory Analysis.

 image

The tool that was available before EHP2 was the Memory Objects view, shown below in its form in NetWeaver 7.0 EHP2. This tool shows you the memory objects of the program (the representations of dynamic variables in the memory management system) ranked by size. 

Memory Objects also shows you which variables reference each memory object.  But the view does not help us to understand the differences between the IT_CUSTOMERS and IT_SCUSTOM tables. Essentially we just have an unstructured list of memory objects ranked by size.

 image

Here’s where the new Dominator Tree view (below) shows how useful it is.  In this view, it’s immediately clear how IT_CUSTOMERS is structured. The rows are so short because they contain only an object reference. The CUSTOMER objects in the table contain, by the way, a further object, ACCOUNT.  The CUSTOMER objects are also keeping several strings – variables NAME, ADDRESS, and CITY - alive.  The bound storage of the table is so high because the table is keeping all of the customer object hierarchies alive.  (Without the references from IT_CUSTOMER, the ABAP garbage collector would clear the objects away and free the memory.)

image 

The organization of the table is now clear. Where does the advantage in memory use of the IT_CUSTOMERS table come from, compared to table IT_SCUSTOM? 

To find the answer, you could copy the name of a CUSTOMER object into the clipboard, and start the Memory Object Explorer (available only in the debugger, not in the Memory Inspector). In the Memory Object Explorer (below), we can follow edges from the CUSTOMER object to its children, all of the objects that it references.

The Dominator Tree shows only strings and instances of classes that belong to the bound storage of each CUSTOMER class object. These are the objects that CUSTOMER keeps alive. The Memory Object Explorer, by contrast, also shows objects that are referenced by more than one CUSTOMER instance, memory objects that are in effect shared. Can it be that sharing of objects accounts for the reduced storage use?

We follow a CUSTOMER object to its referenced objects and then check some of the referenced objects themselves in the Explorer. COUNTRY looks like a good variable to check for sharing among multiple CUSTOMER objects. So we go from string {S:S9} ADDRESS-COUNTRY up the memory hierarchy – Higher-Level Memory Objects - to see the parents of this string, objects that reference this string.

image 

And in fact, as you can see below, the more efficient storage use in table IT_CUSTOMERS than in IT_SCUSTOM could be due to massive sharing of string objects in memory.  There are many CUSTOMER objects from our table that reference the same COUNTRY string.

image 

The IT_CUSTOMERS table design takes advantage of the fact that string variables that have the same content share a single memory object.  (See ‘value semantic’ in the ABAP Online Help (transaction ABAPHELP or at help.sap.com).  ABAP gives a string or other value-semantic object its own memory object only on an as-needed basis – if the string is changed.

In many applications, a table like this list of customers is rarely changed, but is used instead to guide processing. In this case, it may make sense to make use of memory object sharing to reduce storage consumption.  In this application, CUSTOMER attributes like the country-of-residence reference the same string, as long as the same country is being referenced.  You can check out whether the strategy is really worthwhile – when filling a table, when reading a table, in the event that object attributes are changed – by doing some testing of the alternatives in the ABAP Runtime Analysis, transaction SAT. (See the weblogs by Olga Dolinskaja on the new SAT.)

An advantage of doing memory analysis in the debugger is that you can see what the value of the variables is. This is something that you cannot do when you analyze memory snapshots in the Memory Inspector (transaction SMI).  A double click on string {S:S9} above shows us what country all of those customers inhabit:

 Displaying the Value of a Memory Object in the ABAP Debugger

But the Memory Inspector, in turn, has the advantage of being able to compare memory snapshots and show changes in memory use over time. That’s an invaluable capability for checking for leaks in a long-running ABAP application.

 

 

 

 

 

 

 

 

 

Stephen Pfeiffer   is a senior developer in the ABAP Infrastructure development group.


http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23875%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A+SAPNetworkWeblogs+%2528SAP+Network+Weblogs%2529

Posted by AgnesKim
Technique/그외2011. 3. 27. 15:17

Difference between transactions RS12 / SM12 ?
Martin Maruskin 
Business Card
Company: self employed
Posted on Mar. 25, 2011 01:35 PM in Enterprise Data Warehousing/Business Warehouse

URL: http://sapport.blogspot.com/2011/03/difference-between-transactions-rs12.html

Seems there is no difference; at least as of BW 3.0 and above. According SAP Note 316329 - Master data table locked locks on master data were handled differently in BW versions 2.0 – 2.1C. The difference is that not standard SAP lock mechanism was used but there was BW specific locking mechanism used. This was however removed in version 3.0 and subsequent. Therefore transaction RS12 is still in BW just because of BW history. As you can see the same ABAP report (RSENQRR2) is called by both TAs.

SM12

 

RS12

Martin Maruskin   SAP NetWeaver BW certified consultant


http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23880%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A+SAPNetworkWeblogs+%2528SAP+Network+Weblogs%2529

Posted by AgnesKim
Technique/SAP BW2011. 3. 27. 15:16

How to find BWA version?
Martin Maruskin 
Business Card
Company: self employed
Posted on Mar. 25, 2011 01:46 PM in Enterprise Data Warehousing/Business Warehouse

URL: http://sapport.blogspot.com/2011/03/how-to-find-bwa-version.html

 
 

Well, from SAP BW side not that easy J however everything is possible since there is a class CL_RSDDTREX_SERVICE.

For very simple information about BWA release and its revision you can call GET_BIA_RELEASE method:

GET_BIA_RELEASE

For little bit more comprehensive information about SP of BW as itself you can call method COMP_BI_SP_BIA_REV.

 COMP_BI_SP_BIA_REV

Martin Maruskin   SAP NetWeaver BW certified consultant


Comment on this article
Comment on this weblog

Showing messages 1 through 3 of 3.

Titles Only Main Topics Oldest First
  • What was the background?
    2011-03-26 07:34:19 Vitaliy Rudnytskiy Business Card [Reply]

    Thanks for sharing Martin. What was the case where you needed to check it in ABAP? Thanks. -Vitaliy
    • What was the background?
      2011-03-26 09:31:28 Martin Maruskin Business Card [Reply]

      Hi Vitaliy, at current prj I have access only to BW backed into which BWA is connected to. And simply I was just curious about BWA version. For sure there many other ways to find it out from different places e.g OS shell scripts?, TREX Admin Tools?. This is just one that I was able to find.
      Cheers, Martin
      • What was the background?
        2011-03-26 12:50:12 Vitaliy Rudnytskiy Business Card [Reply]

        If you do not have access to standard transactions RSDDBIAMON and TREXADMIN, but have access to RSRV (and time, because it might take some time depending on the size of BWA) go to RSRV -> System Information -> BI Accelerator -> Simple BIA functionality check.
        In the output you'll find:
        ...
        ====== BIA Instances ======
        BIA instance found on ...
        ------ Instance XXX/00 ------
        version: 700.54.216538
        ...

Showing messages 1 through 3 of 3.



http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23805%3Futm_source%3Dtwitterfeed%26utm_medium%3Dtwitter%26utm_campaign%3DFeed%253A+SAPNetworkWeblogs+%2528SAP+Network+Weblogs%2529
Posted by AgnesKim