This blog wil be updated almost daily and the topics will be dealing with the daily support of SAP BusinessObjects BI support. So check back daily! Protected by Copyscape Online Plagiarism Test

Thursday, May 23, 2013

SAP BO 4.0 Update: Newly Added Authentication Types

Protected by Copyscape Online Plagiarism Test


What is Authentication?
In terms of software applications, authentication is the process of identifying whether a user has appropriate rights to access an application or data.

What is Authorization?
Authorization is the process of giving someone permission to do certain activity or access privileged applications/systems.

Authentication precedes Authorization or many a time, both happens at the same time.

SAP BusinessObjects Systems Security
In SAP BusinessObjects, system security is managed by the Central Management Server (CMS), security plug-ins, and third-party authentication tools, such as SiteMinder or Kerberos. These components authenticate users and authorize user access for the SAP BusinessObjects User Management System, its folders, and other objects. 

In the old version such as 3.x, we had the following authentication types when we try to login on SAP InfoView, CMC and/or any other SAP BusinessObjects applications.

In InfoView:
                                                       FIG 01


In CMC Authentication:

                                          FIG 02

In the new SAP BusinessObjects 4.0, few more Authentication types are added such as : Oracle EBS, JD Edwards EntepriseOne, PeopleSoft Enterprise and Siebel.

These have to be custom installed and then enabled. The instructions to install and configure these utilities are given in the Installation guides

                                          FIG 03


I hope this will be helpful.

*****
****
***
**
*



Monday, February 25, 2013

SAP Promotion code is available now for 2013 - 50% off

Protected by Copyscape Online Plagiarism Test


SAP promotion code is out now for 2013, Use this promotion code -13CERTED.
You can use this code if you are appearing exam though PearsonVUE.

*******
******
*****
****
***
**
*

Friday, February 15, 2013

Pointing the WebI Report to Prod system after migrating from Dev

Protected by Copyscape Online Plagiarism Test

After migrating the WebI report from BWD (or even BWQ) to BWP, you will get this error if you try to run the report:
“A database error occurred. The database error text is: The SAP SSO authentication process will fail because the current user doesn’t have an alias that matches system BWDCLNT… (WIS 10901)”

                                         Fig 1 - Database error when running a WebI Report   It is time to point this report to the BWP universe as it is still pointing to BWD. Follow these steps.



My environment:

SAP BW 7.01
SAP BusinessObjects XI 3.1 (WebI)
Webi Report built on top of a Universe which is on top of a BEx query

  1. Open your Universe Designer and from the Tools menu, select Connections



  2. 
    Fig 2 – Universe Designer Tools option
 
    2.    Select your connection from the list and then click Edit
 
Fig 3 - Wizard Connection - Connection List
 
 3.   This will open up the Edit Connections, here you will have to change the connections parameters
 
Fig 4-1 - Edit Connections - Login Parameters [2-4]
 
 
 4.   The changed parameters should reflect BWP info and then click Next



Fig 4-2 - Edit Connection - Login Parameters [2-4]



5.   On the next screen, select the universe that your WebI report should be pointing to



Fig 5 - Edit Connection - Catalog-Database Parameters [3-4]

6.   On the next screen, just click Finish



Fig 6 - Edit Connections - Configuration Parameter [4-4]

7.   You will come back to the Connection Wizard, here highlight the Connection and then click Test



Fig 7 - Connections Test

       You should get this confirmation

Fig 8 - Connections Test Confirmation

8.    Now click Finish

Fig 9 - Connection Wizard Finish

Now logon to InfoView and run the report, the report should run fine.

Please comment/correct any thing in here

************
***********
**********
*********
********
*******
******
*****
****
***
**
*

Saturday, December 15, 2012

Resolving "processDPCommands' API" Error when accessing WebI XI 3.1 report

Protected by Copyscape Online Plagiarism Test

If you are getting an error "An internal error occurred while calling 'processDPCommands' API. (Error: Err_WIS_30270)" when accessing a SAP WebI XI 3.1 report .

My environment when this error was recreated:

SAP BW: BW 7.0 and above but not BW 7.3
SAP BusinessObjects: SAP BO XI 3.1 SP3 FP6.7
SAP InfoView: Client version XI 3.1 FP6.7
SAP Integration Kit: version XI 3.1 FP 6.7

SAP WebI report is access via SAP InfoView (XI 3.1) version. The source is universe version XI 3.1 on an SAP BW MultiProvider.

If we carefully trace how this happened, it would come to light that migration sequence was not right. You will get this error mostly when the report was migrated before the universe or the universe was migrated before the SAP BW infoproviders were transported in SAP BW.

Solution: Open the Universe in Designer, make the that it is pointing to the right source (if it was not, you would have gotten a different error altogether). Perform an integrity check.

When you do so, you will see probably a result very similar to this:


Parse Joins: 1 Errors
ParseObjects: 4 Errors
Parse Conditions: OK
Check Loop: OK
Check for Context : OK

Check the errors, fix them, save the universe and export to the CMS again.

Now access your SAP WebI report and hopefully you should no see the error. If error persists, you might want to repeat these steps.

Inform me if any more information needs to be added.

*******
******
*****
****
***
**
*

Wednesday, February 15, 2012

Assignment of Source System ID in SAP BW

If a characteristic ZCUST_ID is coming from multiple source systems and is also defined as Master Data bearing InfoObject in SAP BW and is compounded with Source System ID (0SOURSYSTEM), then it becomes necessary to do Source System Assignment in SAP BW to let the system know which system the value for this characteristic ZCUST_ID is coming from.


This is true for even the delivered InfoObjects and even if that field is mapped to another field in several SAP source systems.

All you have to do is follow these steps to create the Source Systems ID’s and do the assignment.

1)      In the Administrator Workbench, choose Tools  à Assignment Source System to Source System ID.
Fig 01 – Assignment of Source System ID
2)      Choose Create.
Fig 02 – Create Source System ID

3)    Enter the logical system name and a description, and confirm you entries (in this example the name 
       would be BIDCL100 or DEVCL100).

4)   In the Source System ID column enter the ID name that you also entered in BW1 for the corresponding source system. (In this example it would be ID 01 or ID 02).
5)    Save your entries.
Fig 03 – Display Source System IDs
I hope this will be helpful to others.

*******
******
*****
****
***
**
*

Thursday, February 9, 2012

Comprehensive List of BI Tools - 2 of 10 Parts

I'm continuing the series with some other BI Tools that I'm aare of in this Part. The Part 1 list is given here

Part 2 list continues here:
Teleview
Features:
-  Touted as Self Service Enterprise BI
-  Comes integrated with a database, data capture and data processing component and an interactive
    front end with multiple visualizations
-  Data Integration and Data Processing
-  Modular Architecture
-  Role based security
-  Dashboard Creator
-  Works with Linux and Windows (64 bit for server and 32/64 bit client)

Version:
Website: http://abibasystems.com/teleview.htm
Developed by: ABIBA Systems Private Limited


Datawatch

Features:
-  Is referred to as Monarch Report Manager on Demand (Monarch RMOD)
-  Monarch RMOD can be integrated with CRM applications, Web Portals
-  Can be installed on Windows Server 2008 R2, IBM AIX, Solaris, Linux – Red Hat 5.2
-  Application Servers: JBOSS, IBM WebSphere, Apache Tomcat
-  Java-based desktop deployment

Version:
Website: http://www.datawatch.com/Monarch/Report_Management.php
Developed by: Datawatch Corporations

Will continue with the list in other posts ....

*********
********
*******
******
****
***
**
*

Monday, February 6, 2012

Dates in WebI always in the different format 1/1/70

The date always displayed as 1/1/70 in WebI that are built on top of BEx queries.
SAP BusinessObjects 4.0 (Product: 14.0.0) Patch level 2.6
SAP BW: SAP EHP 1 for SAP NetWeaver 7.0 (Patch 08)

The BEx : BI AddOn 7.x on (based on 7.10); SP 10, Patch 1

Java Pug-in: Java version 6 Update 29 (build 1.6.0_29b11)

I’m using the WebI from BI Launch Pad which uses Java plug-in to work. I’m not using SAP Web Intelligence Rich Client (this one needs local client installation).

For e.g.:

Fig 01 – Wrong WebI dates

While it suppose to display

Fig 02 – Corrected WebI dates

The solution for this is given in this SAP Note. You will need an OSS ID to access the SAP service marketplace to see this note.


1648578 - date values displayed wrong

The issue is fixed in Patch 2.7 and has adapted as ADAPT01585086.

I hope this will help others. Please leave comments or suggest a coorection.

********
******
****
***
**
*


Sunday, February 5, 2012

Some Options are disabled / not funtional in WebI 4.0 on top of SAP BW BEx Query

 SAP BusinessObjects introduced a new functionality where now WebI documents can be created on top of BEx query using BICS.


SAP BusinessObjects 4.0 (Product: 14.0.0) Patch level 10.0

SAP BW: SAP EHP 1 for SAP NetWeaver 7.0 (Patch 08)

The BEx : BI AddOn 7.x on (based on 7.10); SP 10, Patch 1

Java Pug-in: Java version 6 Update 29 (build 1.6.0_29b11)

I’m using the WebI from BI Launch Pad which uses Java plug-in to work. I’m not using SAP Web Intelligence Rich Client (this one needs local client installation).

1) The Scope of Analysis and View Script (previously View SQL) option in the Design mode of the Query
     Panel are not available if you use BEx queries as a source. You will see those disabled.


                    FIG 01 – The Scope of Analysis and View Script options disabled
 
2) In the Filter area in WebI on BEx, the AND operand does not change to OR
 
 
    Fig 02 – Query Filters using AND operand
 
If you try to double-click on this operand AND to try change it to OR, this will not work.
 
3) The search operands underscore (“_”) and percentage (“%”) doesn’t seems to work in WebI on
    top of BEx queries. Only operand “*” works. The obvious reason is the List of Values are not save
    on server.
 
 
 Fig 03 – Search Operand for List of Values
 
 
   Fig 04 – Search in Keys option
 
 
4) The Use Query drill also doesn’t work. Although you can check it in the Document Properties but it
    doesn’t work
 
 
         Fig 05 – Use Query Drill option in Document properties
 
At this time I could only find these options not to work. There could be other’s which I could not yet test.


Please update and let me know if anything here needs to be corrected or needs to be added here.


*******
******
*****
****
***
**
*



Wednesday, November 30, 2011

Installing SAP Data Services 4.0: Part 3 - Integrating with SAP BusinessObjects BI Platform

Protected by Copyscape Online Plagiarism Test
I came across a blog where the expert author Stuart Wallace provides details on installing SAP BusinessObjects Data Services. An excellent read.

Installing SAP Data Services 4.0: Part 3 - Integrating with SAP BusinessObjects BI Platform


I hope you will like it.
 
*****
****
***
**
*

Thursday, November 3, 2011

How to fix Error 09 ...

Protected by Copyscape Online Plagiarism Test

Issue:


While activating the DataSource or even when executing an InfoPackage, you might come up with a “Caller 09 …” error message.

While trying to preview data from DataSource, you might come up with this type of error

“S:RSSDK:300 Field DATE not a member of /BIC/CAZDS_TEST_0 00040000001”

FIG 01: Error message in Monitor
 
This error message has the same roots as the error message in the inset box.


This might happen even if you are loading data from a DSO into an InfoCube.

Cause:


It is a memory dump; load got failed due to memory space unavailable.

Troubleshooting:


If you look at details, you will see this message

Error message from the source system

Diagnosis
An error occurred in the source system.

System Response
Caller 09 contains an error message.

Further analysis:
The error occurred in Extractor .
Refer to the error message.

Procedure
How you remove the error depends on the error message.

Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.

Check transaction code ST22 to see if there are short dumps.

Check transaction code SM12 to see if there are any locks.

Check transaction code SM21 to check system logs

Check transaction code SM37 to check status of the Job (finished or terminated).

Resolution:


Nevertheless, these points might help:

  • If this is happening at the while loading that Data from DSO into the InfoCube, then drop the indexes and try reloading data in several ‘smaller’ request by slitting the data with an appropriate filter on an InfoObject for e.g. 0CALYEAR



  • If the source is SAP systems and also if you are in Production environment, it would be necessary to activate the DataSource

  1. Go to transaction code SE38
  2. Run the program RSDS_DATASOURCE_ACTIVATE_ALL (If you are on SAP BW 3.5, then use this RS_TRANSTRU_ACTIVATE_ALL)
  3. Select the Source System and select the DataSource name and click execute. Check box for "Only Inactive objects"
  • If this error happens in dev environment and the Source Systems are non-SAP, I would recommend deleting the DataSource and creating a new one. This will surely fix the problem.


The messages in here might be helpful in getting this resolved.




I hope this will be helpful.

*****
****
***
**
*

Thursday, October 20, 2011

Comprehensive List of BI Tools - 1 of 10 Parts

I'm starting this blog with a list of all BI tools that I came across. Hopefully I can cover this in 10 parts.


arcplan Enterprise
Features:
-          Application server works with Windows and UNIX environment and provides centralized web interface to manage Administration.
-          Works with different types of DataSources such as ERP (including SAP ERP), relational databases, OLAP, Web Services, etc.
-          Comes with arcplan Application Designer as a frontend report designer.

Version: arcplan 7 Patch 2 (7.0.2.71)
Developed by: arcplan based in Düsseldorf, Germany


SAS Business Intelligence
Features:
-          SAS Analytics capabilities, including statistics, predictive analytics, data and text mining, forecasting, and optimization – all integrated within the business context for better, faster decision making.
-          Portal and customizable dashboards
-          Business visualization, Web and desktop reporting, Mobile analytics, Microsoft Office and SharePoint integration, Query and analysis

Version: SAS 9.3
Developed by: SAS Institute Inc



IBM Cognos Business Intelligence
Features:
-          Designed for enterprise-level deployment
-          WYSIWYG capability
-          Supported DataSources include: Relational databases from IBM, Oracle, Microsoft, Teradata and Sybase, various sources accessible via ODBC and dimensionally aware sources like SAP BW.
-          Supports ERP systems, including SAP R/3, PeopleSoft Enterprise, JD Edwards EnterpriseOne, Oracle eBusiness Suite and Siebel CRM.

Version: v10.1
Developed by: IBM
Will continue with list in part 2 ....

Tuesday, September 20, 2011

Apache Tomcat Versus Oracle BEA WebLogic


<>   <>     <>    <>    <> 
Issue Type ↓ Apache Tomcat Oracle BEA WeblogicRemarks
VersionApache Tomcat 6.0.26WebLogic Server 11gR1 (10.3.3) Apache Tomcat works with BO XI 3.1 while WebLogic 10 is supported also
supported
FeaturesAdministration  and  cluster (needs to configure) support, multiple JVM support, OS Windows and Unix platform support, Memory requirements pretty
less
administration and clustering support out-of-the-box, Multiple JVM support, OS Windows and Unix supported, minimum memory requirement needed
AcquisitionComes with BusinessObjects Package hence licensing not a problem and it comes freeSignificant license fee
Performance and JVMReliableReliable
Technical SupportSelf Support (mostly from tech forums). No official support from ApacheComplete Vendor Support In fact, customers prefer BEA Weblogic for efficient technical support but Tomcat is most widely used becuase it is free

Sunday, September 11, 2011

Transposing the Fields in SAP BW Transformation

Scenario

The business records the daily exposure and positions into one record for a term. In my example, a term is for 10 days. So the record looks like this:

<> 
Transaction ID Date Day 1Day 2Day 3Day 4Day 5
6465784/17/2011 432.00 606.002011.002169.00379.00


This means that I will have to come up with 10 key figures in SAP BW InfoProvider design which might not be a good design.

Target Design

I wanted to show this as 1 key figure and with another field that shows what day it is.

Transaction ID Date Day EndingPrice Per day
6465784/17/2011 01 432.00
6465784/17/2011 02 606.00
6465784/17/2011 03 2011.00
6465784/17/2011 04 2169.00
6465784/17/2011 05 379.00

Resolution

The solution presented in here is following this Dataflow: Source System -> Write-Optimized DSO -> Standard DSO. The solution given below can be applied between the Transformation that exists between Write-Optimized and Standard DSO. This can be applied in any Transformations.


Fig 1: Dataflow

This can be extended up to 25 fields. After 15 fields, it might give you an error.

First Solution:

One way to do was to write Start Routine and End Routine in Transformation.







Fig 2: Transformation - Start and End Routine

The code might look like this but you will need to modify this depending on your needs:

Start Routine:

DATA: wa_source_package TYPE _ty_s_SC_1.

    
LOOP AT SOURCE_PACKAGE INTO
 wa_SOURCE_PACKAGE.
      wa_sp-/BIC/ZTRAN_ID = wa_source_package-/BIC/ZTRAN_ID.
      wa_sp-/BIC/ZDATE = wa_source_package-/BIC/ZDATE.
      wa_sp-/bic/ZPDP_DY1 = wa_source_package-/bic/ZPPD_DY1.
      wa_sp-/bic/ZPDP_DY2 = wa_source_package-/bic/ZPPD_DY2.
      wa_sp-/bic/ZPDP_DY3 = wa_source_package-/bic/ZPPD_DY3.
      wa_sp-/bic/ZPDP_DY3 = wa_source_package-/bic/ZPPD_DY3.
      wa_sp-/bic/ZPDP_DY4 = wa_source_package-/bic/ZPPD_DY4.
      wa_sp-/bic/ZPDP_DY5 = wa_source_package-/bic/ZPPD_DY5.


End Routine:


DATA: rem TYPE I.
    
DATA: lt_rp TYPE TABLE OF
 _ty_s_TG_1,
          wa_rp 
TYPE
 _ty_s_TG_1.

    lt_rp[] = RESULT_PACKAGE[].
    
REFRESH
 RESULT_PACKAGE.

    
LOOP AT lt_rp INTO
 wa_rp.
      
READ TABLE it_sp INTO wa_sp WITH KEY

      /BIC/ZTRAN_ID  = wa_rp-/BIC/ZTRAN_ID
      /BIC/ZDATE = wa_rp-/BIC/ZDATE
  
      
IF  sy-subrc = 0.
        wa_rp-/BIC/ZDAY_END = 
'Day 1'
.
        wa_rp-/BIC/ZPPD_PR = wa_sp-/bic/ZPPD_DY1.
        
APPEND wa_rp TO
 RESULT_PACKAGE.

        wa_rp-/BIC/ZDAY_END = 
'Day 2'
.
        wa_rp-/BIC/ZPPD_PR = wa_sp-/bic/ZPPD_DY2.
        
APPEND wa_rp TO
 RESULT_PACKAGE.

        wa_rp-/BIC/ZDAY_END = 
'Day 3'
.
        wa_rp-/BIC/ZPPD_PR = wa_sp-/bic/ZPPD_DY3.
        
APPEND wa_rp TO
 RESULT_PACKAGE.

        wa_rp-/BIC/ZDAY_END = 
'Day 4'
.
        wa_rp-/BIC/ZPPD_PR = wa_sp-/bic/ZPPD_DY4.
        
APPEND wa_rp TO
 RESULT_PACKAGE.

        wa_rp-/BIC/ZDAY_END = 
'0ay 5'
.
        wa_rp-/BIC/ZPPD_PR = wa_sp-/bic/ZPPD_DY5.
        
APPEND wa_rp TO RESULT_PACKAGE.


Transformation looks like this:

Fig 3 : Transformation with Start and End Routine

Second Solution:

By using the Rule Groups
We can use the Rule Groups functionality to achieve the same what I did with Start and End routine.

  1. Create two new InfoObjects: Day Ending (Characteristics type and type CHAR with Length as 6 and Price Per Day (Key figure as Amount)
  2. Insert these InfoObjects Standard DSO
  3. In the Transformation between, Write-Optimized DSO and Standard DSO, click on Rule Groups and create one.
  • For day 1, give the name of the Rule group as Day 1, Map the Price Per Day 1 to Price Per Day and Hard code Day Ending as Day 1
  • For day 2, give the name of the Rule group as Day 2, Map the Price Per Day 2 to Price Per Day and Hard code Day Ending as Day 2
Follow the same steps for all other days.

Fig 4: Rule Groups

The data that looked like this earlier

Fig 5: Data in Write-Optimized DSO

Will look like this

Fig 6: Data in Standard DSO

I hope this will be helpful to somebody.

*
**
***
****
*****