6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 1/55

Getting Started Newsletters Store

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Log On Join UsHi, Guest Search the Community

Activity Communications Actions

Brow se

BI Platform 255 Posts 1 … 5 6 7 8 9 … 17

PreviousNext

On Thursday this past week SAP’s Pierpaolo VEZZOSI provided this update to ASUG. He also goes by "PPaolo".

These are my notes and please note that SAP's usual legal disclaimer applies that things are subject to change.

Figure 1: Source: SAP

Figure 1 shows a “A world without HANA”, says PPaolo

He said it is a lot of steps to get data to your users.

Figure 2: Source: SAP

Figure 2 shows that you can place “data created immediately for use” according to PPaolo

What is new with BI4.1 with SAP HANA – ASUGWebcast

Posted by Tammy Powlas Aug 24, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 2/55

Figure 3: Source: SAP

HANA works closely to where data is sitting, and the features shown in Figure 3 reflect the customer value.

HANA is a good database for BI as it is in BI – it is fast, and it compresses the data

You don’t have to pre-aggregate models

Data is not cached outside of SAP HANA

Figure 4: Source: SAP

BI4 tools all support HANA with additional optimizations in BI4.1

With HANA you can do real-time analysis against operational data

You can connect a Universe to HANA as a relational database or you can connect to HANA Information models

You can use HANA Extended SQL to connect HANA Information Models.

You can automatically generate a universe against a HANA information model as well.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 3/55

Figure 5: Source: SAP

Figure 5 shows Crystal Reports can connect directly to SAP HANA using Freehand SQL and you can fine-tune the

request.

Figure 6: Source: SAP

Figure 6 shows the tools which has direct access to HANA, including Design Studio , Lumira, SAP

BusinessObjects Analysis, edition for OLAP , SAP BusinessObjects Analysis, edition for Microsoft Office and

SAP Crystal Reports for Enterprise.

The direct access may use different technologies.

The end user does not have to care how it connects to HANA – no universe, just open client tool and connect directly

to HANA (information models).

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 4/55

Figure 7: Source: SAP

No universe required in BI4.1 for Crystal Reports Enterprise; you can connect directly to a HANA model. It is a

dimensional connection meaning you can use hierarchies.

Figure 8: Source: SAP

Pierpaolo demonstrated Figure 8

I can use aggregate awareness meaning it will take the best view at run-time.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 5/55

Figure 9: Source: SAP

Figure 9 shows that if you have universe on Oracle or SQL Server you can migrate it to HANA along with your reports.

This migration is provided in the Information Design Tool.

Figure 10: Source: SAP

Figure 10 shows that HANA trusts BI server for authentication

You have to exchange a security certificate so it is secure.

PPaolo said there is no need to do anything complex

The name of the user in HANA and BI Platform must be the same.

Question & Answer:

Q: Are there any plans to have Web Intelligence access HANA data directly?

A: Yes, working with Web Intelligence team on this

________________________________________________________________

Q: Why have direct connection for Crystal reports but not for Webi?

A: Lack of team bandwidth to do Web Intelligence; working on this and planning for the future

________________________________________________________________

Q: Do we have a definite GA date for BI4.1 yet ?

A: No but soon.

________________________________________________________________

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 6/55

Q: can we have hierarchy in WEBI using SAP HANA

A: No

You can meet PPaolo in person at the ASUG BusinessObjects User Conference. His session is Advanced SQL in

Universes: the Mysterious Analytic Functions

Related Links:

SAP TechEd BusinessObjects Sessions

ASUG SAP TechEd Pre-conference BI4.1 Tools In a Day (includes SAP HANA BW

3412 View s 2 Comments

Tags: sapmentors, sapmentor, asug, hana, crystal_reports, w eb_intelligence, sap_hana, analysis_off ice, analysis_olap,

design_studio, bi4.1, bi4.1_hana

This is a fairly well known topic now but it is worth revisiting the reasons why it’s done so we can

have an idea of what to aim for in the type and number of adaptive servers to create.

As you probably know much of the work performed by a BI 4 platform is done by two B.I. servers, the Adaptive

Processing Server (APS) and the Adaptive Job Server (AJS). These are Adaptive in that they perform tasks for a large

number of services required to support the B.I platform.

After creating a standard CMS with all services you will find there is one APS and one AJS each of which supports all

of the services available. This will get you started but it is not ideal for a production server as it leads to long startup

times, critical services being impacted by less important services and a lack of flexibility in scaling the platform.

For example, the platform search runs as a background service and can be resource hungry so it shouldn’t be

competing with your WEBI service that is supporting interactive users and which needs fast response times.

Another reason for splitting the servers is for ease of scaling. This means that you can adjust the memory limits and

easily add new instances of an APS and/or AJS to cope with particular types of workload. For example if large

numbers of publications are required additional APS and AJS instances can be cloned from a base setup that

contains just the publishing services.

SAP note 1694041 has a good description of how to split the services so we won’t go into those details here. Instead

we’ll have a look at the best way to do the setup required.

Firstly you can only select services for an APS or AJS when the server is stopped but you do have the ability to clone

servers. This gives you a new server that is in a disabled and stopped state and leaves the original server running.

Start off with the default server, clone it and give it a name related to its purpose and prefixed with something sensible

(I use APS_ and AJS_ but you can use any convention you like - the aim is to make sure you can see your servers).

Once you have a new server then you can right click on it and chose “Select Services”. Initially you will see that it hosts

all the available services so you need to remove everything except the services required for this server. For example a

Publishing APS would have Publishing and Publishing Post Processing. Next, go into the properties of the server and

adjust the Java memory size according to the type of server being created and the physical memory available – a

publishing server would typically be given 4 Gb so you would change the Java parameter –Xmx1g to –Xmx4g.

Once you are happy with your new server you can enable and start it. When all of the servers have been setup disable

the original and un-tick the selection “Start with CMS”. After testing, the original servers can be deleted if desired.

It’s best to make a checklist of all the services and tick them off as they are added to the new servers to make sure

they are all included. It is easy to skip one of the services and end up with that service not being supported by an APS

or AJS. If that happens the impact can be fairly obvious and the cause easy to spot. Alternatively, it can be just one

feature that fails like saving a report to excel which can take some time to debug as you’ll need to eliminate other

causes like security settings, client versions etc.

One problem you can run into when scaling up the servers is that you can hit the maximum number of SAP Java

Virtual Machines (JVM) allowed. By default this is set to 32 per SAP system id and a BI4 installation is set to use

system id 8 for all of its processes. This is likely to happen if you need to run many publications at once and have

created a number of publication servers. As the workload hits these servers they will create new child processes

which are each SAP JVM’s in their own right. You can see this happening by viewing the Java processes in task

manager on the server. If the number of these increases to 30 and then stays at that level then chances are that some

of the publications are failing. The way around this is fairly simple – just increase the number of allowable SAP JVM’s

from the default. As long as your server has enough memory and CPU to cope then you can run many more than 32

Java instances. Unfortunately the BI4 default values cannot be changed, instead you must run some of your Adaptive

Job Servers under a different SAP system id and increase the SAP JVM count for these. To do this just add the

parameter Xjvmx,XsapSystem:09,XX:MaxVMs=<NumberOfProcesses> to the command line of the job server(s)

BI 4.0 Platform Tuning - Splitting adaptive servers

Posted by Clare Bryan Aug 7, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 7/55

having the problem (i.e. Publication). This gives that set of job servers a completely different limit to the base BI4

system so if your new system had a limit of 64 then your installation could run a total of 96 Java processes

concurrently.

One last thing, make sure that the servers have been setup as required before you start scaling the platform by

adding new servers. There’s nothing worse than realising you have to increase the memory for an APS after you have

created 8 of them.

SAP BI4 SAPJVM No free control area found. Increase number of VMs with option -XX:MaxVMs=<n>. Current value is

32.

Reference

SAP BI4 Adaptive Servers

2606 View s 1 Comments

Tags: intelligence, businessobjects, bi, sap, bi4, business_intelligence_(businessobjects), business_process_expert,

analytics, 4.0, bi4.0, data, reporting, analysis, bobj, bi4_upgrade, business_intelligence, bi_platform,

sap_businessobjects_business_intelligence_platform_4.0

Christopher Vozella and Saroj Parmar, SAP provided this ASUG webcast earlier this week. They discussed how

SAP delivers fixes for BI4, and what is the strategy points behind it.

Figure 1: Source: SAP

What testing occurs?

Figure 1 shows an overview for the maintenance strategy

How align with SAP across products – first requested item

What are the standards, including the quality and governance program; this is why SAP does ramp-ups

Critical corrections – from SAP BusinessObjects standpoint – getting a fix in time for go-live – for XI3 – LA fix but had

downstream challenges

Getting an Update on BI4 Maintenance Strategy -ASUG Webcast

Posted by Tammy Powlas Aug 1, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 8/55

Figure 2: Maintenance Delivery: Source: SAP

Figure 2 reviews maintenance delivery vehicles. Chris suggested printing this for reference.

A minor release is a larger release/rollup of SP corrections, generally around 1 year, with 2 years support with a 1

year between a minor release

Figure 3: Source: SAP

KBA 1479533 contains published release dates.

Frequency is an estimation. Review the KBA will give you information on the published release dates. Customers will

put messages in – this is the KBA to check the guidance.

Lifetime is a common question. How long will SAP support my product? Use the Product Availability Matrix which has

formal EOL dates for the products and for the maintenance life cycle.

Cumulative release plan – BI4 is a cumulative release – if you consume a patch, all the later patches contain fixes

from earlier patches. You need to be aware of Forward Fits and the cutoff points.

This is to help plan release cycle. When consuming fixes, Chris says to go to the most recent release. If you go to

SP6, go to the most recent patch.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 9/55

Figure 4: Source: SAP

Figure 4 discusses critical patches

If you have a go live issue is covered KB 166157 outlines requirements.

Business case needs to be included. Always go through a message, Chris said.

When a critical patch is raised, coordination occurs with development and IMS.

Figure 5: Source: SAP

Figure 5 shows the Patch Priority Paradigm, which is a visual representation of low to high.

Minor releases should have the highest number of releases.

Critical patches are high priority, major show-stopping critical issues.

2013 Focus

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 10/55

Figure 6: Source: SAP

Figure 6 shows their 2013 focus, including simplicity around Forward Fit plan. SP4 and 5 was confusing.

Forward Fits should not be complicated, says Chris. They are simplifying the Forward Fit plan starting with SP6

Improve quality and fixes

With transparency, they are still making improvements to Service Marketplace

New BI4 Forward Fit Plan

Figure 7: Source: SAP

Saroj said they received strong feedback from customers about regressions, as a result they made changes to

Forward Fit plan to address this.

Starting BI4 SP6 they made changes to Forward Fit.

Every fix on previous fix on SP get forward fitted to the highest SP and patches (see Figure 7).

Customers should not have to think about it – take the latest release and not lose any fixes.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 11/55

Figure 8: Source: SAP

The patches delivered on previous lines get forward fitted to unreleased lines.

Anything on 5x 6x get Forward Fitted to SP7 line.

Patch 6.1 is where SAP got caught up.

Figure 9: Source: SAP

Figure 9 shows the BI4.1 line

Any patches on BI4 SP5, 6 are getting forward fitted to BI4.1 SP1

Patches are delivered to the highest patch line

There is a code cutoff; there is a period in the project release lifecycle where they stop taking changes in that

maintenance line.

During that time, there is no new changes that go in; there may be a time period where patches are missing due to

code cutoff period to stabilize the release.

These changes will get forward fitted to the first patch to “catch up”. There is a maximum gap of 3 weeks when it is

released.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 12/55

Figure 10: Source: SAP

XI3.1 SP and Fix packs are getting forward fitted to BI4.1 not BI4.0, said Saroj.

SP’s are cumulative; if you take SP1 you can jump straight to SP6 – you don’t have to go sequentially in 4.x

Patches are cumulative as well.

Question & Answer

Q: When we have to patch hundreds of workstations (eg. Clients, CR4E, CR-2013, etc) in different regions for our

Company...is it "Best Practice" to patch the BI Platform Servers first, then the desktop clients.? Any risk / issue with

having the out-of-SYNC.?

A: good question. Best practice is always to keep them in alignment. I believe we have a KBA on the topic - will

double check. There will not always be a problem when not in synch but definitely a best practice.

A: 1807514 - How To: Patch a BI4.0 Cluster - one good KBA but will confirm additional.

________________________________________________________________

Q: Which SPs and FPs are included in SP7? What is the cut-off for Sp7?

A: Fixes from SP6, patch 6.1, 6.2, patches from 5.6 - 5.9, up to patch 4.15. Patch 6.3 will be FF to Patch 7.1 going

forward.

________________________________________________________________

Related Links:

Bernd Bergmann shares details on a New Patching Policy for SAP BI - written by Bernd Bergmann

BI4/4.1 Maintenance Demystified!

Old blog:

Business Intelligence BI 4.0 Maintenance Model and Roadmap - an ASUG Webcast

Slides from ASUG Annual Conference

Ask Ingo - Season 4

ASUG Promotion:

Newsflash: New e-book, Webcasts, TechEd

SAP TechEd Las Vegas | October 21–25, 2013 | ASUG Pre-Conference Seminars

2144 View s 1 Comments Tags: sapmentors, bi4, sapmentor, asug, bi4_maintenance

In this blog I have explored the visualization objects that are exported to businessObjects

BusinessObjects Query builder – ExploringVisualization Objects

Posted by Manikandan Elumalai Jul 30, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 13/55

repository. Visualization objects includes objects created in Explorer and Xcelcius applications.

Here we go.

Explorer Objects To get the list of available Explorer Information Spaces

SELECT * FROM CI_INFOOBJECTS WHERE SI_KIND='DATADISCOVERY'

By referencing the SI_DATASOURCEID field we can Identify the data source of

Information space. If it is just displaying objects CUID (something like

value="AUmNQF0NW55Klxms83RxePY") then the data source will be an universe. If it represents

value like (value="Spreadsheets|AY7BRSQ_frBPlWcpxJth2cI") then it is clearly evident that the

data source is an Spreadsheet.

SI_DATASOURCEID VALUE DATA SOURCE

value="AUmNQF0NW55Klxms83RxePY Universe

value="Spreadsheets|AY7BRSQ_frBPlWcpxJth2cI" Spreadsheet

To get the list of available Exploration Viewsets SELECT * FROM CI_INFOOBJECTS WHERE SI_KIND='DataDiscoveryAlbum'

Xcelcius Objects To get the list of available Xcelcius dashboards SELECT * FROM CI_INFOOBJECTS WHERE SI_KIND='XL.XcelsiusEnterprise'

We can get the canvas size of the dashboard using the file SI_CANVAS_SIZE. Please note the

individual component levels canvas properties cannot be extracted from repository.

Type of device compatibility can be referenced from SI_DEVICE_TYPE property. SI_DEVICE_TYPE DESCRIPTION

1 Desktop Only - Compatible only while accessing from Desktop

2 Mobile Only - Compatible only while accessing from Mobile device

3 Desktop and Mobile - - Compatible for both Desktop & Mobile

To get the list of available Flash objects SELECT * FROM CI_INFOOBJECTS WHERE SI_KIND='Flash'

Query Builder Blog series Basics

BusinessObjects Query builder - Basics

BusinessObjects Query builder – Best practices & Usability

Sample Queries

BusinessObjects Query builder queries

BusinessObjects Query builder queries - Part II

BusinessObjects Query builder queries - Part III

BusinessObjects Query builder queries - Part IV

BusinessObjects Query builder – Exploring Visualization Objects

Use cases

BusinessObjects Environment assessment using Query builder

BusinessObjects Environment Cleanup using Query builder

BusinessObjects Query builder – What's New in BI 4.0

4413 View s 0 Comments Tags: bo_querybuilder

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 14/55

Continuing with Query builder blog series here is another one with more emphasize on features of

BI 4.0. Below are the features of consideration

Users homepage is enhanced to view his/her latest documents and Alert notification.

Connection specific enhancements

Universe enhancements

Monitoring

And here is the respective queries for each consideration Alert Notification and recent document Query for User

SELECT SI_ID, SI_NAME, SI_RECENT_DOCUMENTS,SI_RECEIVED_ALERTNOTIFICATIONS

FROM CI_SYSTEMOBJECTS WHERE SI_KIND='USER'

This will be extracted for each user in the system. Probes

SELECT * FROM CI_INFOOBJECTS WHERE SI_KIND='MON.Probe' AND SI_INSTANCE =0

Please note I am just extracting probes alone not its instances. To retrive the proble

instances you need to use SI_INSTANCE =1 in the where clause.

Connections

SELECT * FROM CI_APPOBJECTS WHERE SI_KIND = 'CCIS.DATACONNECTION' this will extract all the data connections i.e. Relational and OLAP from the repository

Universe

SELECT SI_ID,SI_NAME,SI_SPECIFIC_KIND, SI_KIND FROM CI_APPOBJECTS WHERE

SI_KIND= 'DSL.MetaDataFile' We can further categorize the individual components of universe using

SI_SPECIFIC_KIND and this is the component list for the .unx universe.

DSL.BusinessLayer

DSL.DataFoundation

DSL.Connection

DSL.Universe

DSL.DataSecurityProfile

DSL.DataSecurityOptions

DSL.BusinessSecurityOptions

DSL.ConnectionShortcut

Hope this is interesting. Feel free to leave your comments. Thanks for reading.

Query Builder Blog series

Basics

BusinessObjects Query builder - Basics

BusinessObjects Query builder – Best practices & Usability

Sample Queries

BusinessObjects Query builder queries

BusinessObjects Query builder queries - Part II

BusinessObjects Query builder queries - Part III

BusinessObjects Query builder – What's New in BI4.0

Posted by Manikandan Elumalai Jul 26, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 15/55

BusinessObjects Query builder queries - Part IV

BusinessObjects Query builder – Exploring Visualization Objects

Use cases

BusinessObjects Environment assessment using Query builder

BusinessObjects Environment Cleanup using Query builder

BusinessObjects Query builder – What's New in BI 4.0

5137 View s 13 Comments Tags: bo_querybuilder

Project Synchronization in IDT (Able to multiple developers work on same universe at the same time)

1. Open IDT.

2. Click on toolbar Window\Select ‘Project Synchronization’

3. Project Synchronization window opens up on the right hand side.

1. Click on Session. It will prompt to enter the username (user1) and password to connect to session (Repository).

4. Click on Session. It will prompt to enter the username (user1) and password to connect to session (Repository).

5. Click on shared project to create a shared name

Tutorial- Step by Step - Project Synchronization- IDT

Posted by Jawahar Konduru Jul 22, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 16/55

6. Create Shared name. Shared name appear on ‘Local Project’ section

7. Right Click on ‘Sample’ shared name. Click on ‘Retrieve a published Universe’ from ‘Repository’

8. Click on “Refresh’ icon on project Synchronization’ space.

9. Click on icon ‘Save changes to server’ and Universe will appear on the bottom of the screen with Version#1.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 17/55

10. Make some changes in the universe .dfx or blx. And Refresh on the project synchronization. Notice changed

version shows “Changed locally’

11. Select the .blx ‘changed locally’ and click on ‘save changes to server’ icon.

12. Notice version# is changed to 2 of the blx on server side.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 18/55

13. When ever you make changes to universe, sync with Server.

14. Now login as second user who wants to make changes to same universe where first user also working.

15. Click on “Get changes from server” icon to get the project. Any changes you make , keep syncing the project to

server for other developers to access the latest changes.

16. If you don’t sync the changes from the server, developers will see only “ Changed Locally”. After synching the

related changes, you will see synchronization status is changed to “Synchronized”

The different synchronization statuses and what they mean are listed below.Status Description

Added Locally: The resource was added in the local project, but not in the

shared project.

Changed Locally: The resource was changed in the local project, but not in the

shared project since the last synchronization.

Deleted Locally: The resource was deleted in the local project but still exists in

the shared project.

Added on Server: The resource is not in the local project but exists in the shared

a. project.

Changed on Server: The resource was changed in the shared project, but not in

the local project since the last synchronization.

Deleted on Server: The resource exists in the local project, but was deleted in the

shared project.

Conflicting:

Any of the following situations creates a conflicting status:

• The resource was changed in both the local and shared

projects with different changes since the last synchronization.

• A resource with the same name was added both in the local

and shared projects since the last synchronization.

• The resource was changed in the local project, but deleted

from the shared project.

• The resource was changed in the shared project, but

deleted from the local project.

Synchronized The resources are identical.

711 View s 1 Comments

Continuing with of my previous blogs on BusinessObjects File repository servers here is another

one for Managing File Repository servers. Below are some of the best practices for managing File

Business Objects Administration - Managing FileRepository Servers

Posted by Manikandan Elumalai Jul 22, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 19/55

repository servers. A. Setting Instance limits at various folder levels based on the Business requirement

It is always recommended to maintain only instances that are required in the system at any point

of time. Managing reports that are no longer required by the business will take unnecessary disk

space in Output file repository. This is the place where Instance management is come in to picture

where you can limit instances based following criteria

a. Number of Instances

b. Age of Instance

c. Instance limit for Users/Groups

To understand more about the Instance management planning you can refer here

BusinessObjects Instance Management

B. Control the report storage in Users personal folders.

Personal folders

Controlling document storage with in User’s personal folder has also equally important

compared to that of instance management. Replication of same report in multiple places will

again create the report duplication in turn the space utilization in Input File store. To avoid this we

should have a firm security in place so that only the authorized users can create/copy the reports

that too only in their personal folders with their report level personalisation.

Inbox

Managing reports inside User’s inbox is also a cumbersome task for the administrator as

there are no utility/feature/Security rights to limit the number of objects for user’s Inbox. It is the

responsibility of the administrator to manually monitor user’s Inbox volume on periodic basis and

notify the user for deletion. There are some SDK utilities using which Administrators can limit

User’s inbox documents though there is no out-of –box solution.

C. Use of Repository Diagnostic Tool to minimize the CMS Database and File store

synchronization issues In most of the BusinessObjects deployments there could be a possibility for a

discrepancy between File repository store and the CMS database. This could be due to CMS server

crashes and Input/output FRS crash. As a result the report that is available in file store might miss

its corresponding entry in CMS database and the related entry CMS database could miss its

counterpart in File repository store.

Repository Diagnostic Tool will be handy to identify and resolve inconsistencies

between CMS database and the File repository. Refer the below wiki page to understand more

about RDT. http://wiki.sdn.sap.com/wiki/display/BOBJ/How+to+use+Repository+Diagnostic+Tool

Hope you find this interesting. File Repository Servers Management - Blogs

Business Objects Administration - File Repository Servers

BusinessObjects Administration – File repository store capacity planning Considerations

BusinessObjects Administration – File Repository Capacity planning

1675 View s 2 Comments Tags: bo_frs

Final Call - Customer Connect for BusinessObjects BIPlatform – Don’t let an idea languish because of 4

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 20/55

This week SAP’s Nadine Engler conducted the Final Call for Focus Topic BusinessObjects BI Platform.

You may listen to this webinar replay at https://sap.emea.pgiconnect.com/p73183994/

Nadine explained that the Collect phase ends July 26, which is now less than a week away.

Derek Wang, the product owner for BI platform, also joined this session. SAP wanted to provide an overview of

status of improvement requests.

The agenda is the overview of project timeline along with improvement requests and status. The legal disclaimer

applies, everything is subject to change.

Figure 1: Source: SAP

Figure 1 shows the project timeline.

In May they kicked off the call and asked everyone to submit and vote on idea.

Collect phase ends on July 26

The select phase will begins and SAP will review those ideas with 5 or more subscriptions. Only subscribers from

different companies are counted.

Improvement requests with less than 5 do not qualify for the select phase. Improvement requests cannot be too

large, impact architectural changes or impact other customers. Selection call is planned for first week in October.

Delivery of improvement request is planned for first quarter of 2014.

votes

Posted by Tammy Powlas Jul 20, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 21/55

Figure 2: Source: SAP

Figure 2 shows re 73 improvement requests have been submitted with 30 at the qualified stage for development.

Make sure all of your requests are in the customer connect tool and you are subscribed to the ones you are interested

in.

Derek Wang explained the status of the improvement requests.

Figure 3: Source: SAP

Figure 3 shows the list of requests collected so far.

Derek said this was a successful customer connect program with a lot of subscribers and qualified requests.

Some ideas may be good but may not belong in the BI Platform area.

First request – export from CMC to CSV – SAP wants more information. What would you do with the CSV file?

Second request is specific to Web Intelligence as functionality works in Crystal Reports.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 22/55

Figure 4: Source: SAP

Figure 4 covers recovering from more ideas, such as trash can and publication errors. The second idea already

exists says Derek. The last item is a global message capability.

Figure 5: Source: SAP

The first idea listed is similar to the CSV idea and SAP would like to have more conversation.

The last two items require changes with the BI client tools

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 23/55

Figure 6: Source: SAP

Derek said the first item in Figure 6 already exists.

The next idea is Web Intelligence specific and the BI platform cannot do anything about that.

Figure 7: Source: SAP

The second idea regarding LDAP – SAP wants more information and Import Wizard doesn’t exist in 4.0.

The third idea involves charting and does not involve BI Platform.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 24/55

Figure 8: Source: SAP

By next Friday, 7/26, the workspace will be set to read only. If you are the improvement request owner you may be

contacted for more details.

Question & Answer

Q: What happens with a good request which has not enough subscribers ?

A: Reach out to others in group to subscribe

Q: Is there still time to subscribe?

A: Yes, you can still subscribe, cut-off date is July 26

Q: What is more important here, subscribers or votes?

A: Subscribe – subscribe is what counts and meaning. It is not a contract but it is the pool of people that development

may reach out to for the feedback or ask them if they can pre-test before release. It is an engagement to be a

sounding board to SAP. Nadine said it is a “gentleman’s agreement” that you will use it.

Attendee Comments:

“Let's all take some time and review each other's IRs...see if we there are any good ones we can help get over the

threshhold!”

“Don’t let an idea languish because of 4 votes”

Links:

https://cw.sdn.sap.com/cw/community/influence/cc/businessobjects_bi_platform - Link to Workspace, requires logon

and authorization

Customer Connection for the BI BusinessObjects Platform - See how you can influence SAP

Influencing via Customer Connection to Enable the Installed Base – Web Intelligence

Are you ready to influence SAP’s BI Platform solution? In more than one way…

1681 View s 2 Comments Tags: sapmentors, sapmentor, bi_platform, influence, customer_connect

Translation Management Tool

1. Overview

2. Terminologies

3. Translation Approach

Language Translation Approach- TranslationManagement Tool

Posted by Jabir Mohammed Jul 17, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 25/55

4. Steps for Translation

1.Overview:-

The Translation Management Tool (TMT) is a tool used to translate Web Intelligence reports from one language to

various other languages.

The tool provides a simple graphical interface for easy and simple translations.

Important Points:-

Ø Translation manager can be used to translate Data Provider Name, Prompt text, Labels, Report Tab

names, User defined variables and Alerter.

Ø A designer can create one report for a multilingual audience, instead of creating a report for each language.

Ø Ability to manage approximately 130 locales

Ø Support for all Central Management Server (CMS) authentication modes, a standalone mode, and the ability

to export translated documents to the CMS

Ø To make strings in a report formula available for translation in Translation Manager, the report designer

must use the GetLocalized function when designing the report.

Ø The tool cannot translate the data itself.

Ø Translation manger tool will be using to translate only the static elements text in Business objects Webi

reports.

Ø Translated string in various languages should be made available to translate the reports into respective

native languages

2. Terminologies used in Translation:-

Ø Product Language - The language in which the application appears.

Ø Document Language - The language defined when creating documents (Universe and Web Intelligence).

Ø Preferred Viewing Language (PVL) - The preferred viewing language while working with the application

(Info View, Web Intelligence rich client).

Ø Substitution (Fallback) Language - The language that displays by default when the viewing language or

preferred viewing language is not available.

Ø Source Language - The source language for the Auto fill option used by Translation Manager.

Ø Locale- A locale defines a language and a geographical area. A language can be associated with several

countries

Ø Dominant locale- The dominant locale is a pre-defined locale that is used as the substitution language

when no substitution language is defined for the document.

Ø Product language- The product language is the language in which the Business Objects application

interface appears.

Ø Original content language- The original content language is the language used by the designer when

creating a universe or report.

3. Translation Approach:

Add and remove languages in your document

● Open or import the document from the Central Management Server (CMS).

● Open the Language Management view. Select Window > Language Management View

● To add a language, select the language in the Available Languages list and click the right arrow.

● The language is added to the Selected Languages list. A new column for the language is added to the

Translation Editor view.

● If the Auto fill Option is turned on, Translation Manager fills the column with content in the Auto fill source

language.

● To use the new language as source for the Auto fill option, select the Auto fill Source option button.

● To remove a language from the document, select the language in the Selected Languages list and click the

left arrow.

● Select File > Save to save the changes to the document.

Translating Strings

Short strings can be translated in the Translation Editor view. To translate longer strings, use the Text Editor view.

● In the Translation Editor, in the column with the language to translate, click the cell containing the content you

want to translate. If the language was added with the Auto fill option on, the cell contains the Auto fill source

language content. Otherwise the column is blank.

● Enter the translation by typing over the previous string. When you click the cell, the content appears in the Text

Editor view. Once you enter the translation, the status of the cell is automatically set to TRANSLATED.

● You cannot type into cells that contain date and numeric formats. To set a format, right click the cell and

select a default format, or use the Format Editor to create a custom format.

● To move to the next cell to translate, click the cell.

● Select File > Save.

● Text Editor can be used to translate the long strings.

● Open or import the document.

● Open the Text Editor view if it is not already open. Select Window > Text Editor View.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 26/55

● Click the cell of the content you want to translate. The source appears in the Source box of the Text Editor.

This content cannot be edited. Existing translated content appears in the Translation box.

● Edit the content in the Translation box.

● To apply what you have translated in the Translation Editor view, click Apply.

● To cancel the changes, click Reset.

Select File > Save

Info View Preferences –Change the Locale to Display the Translated Report

.

● When the user opens the document, the application tries to display content in the user's Preferred Viewing

Locale (PVL). The PVL must be set to Ready for use in Translation Manager. Only translated content with a

translation status in the "Translation Visible" category is displayed.

● If no visible translation is available in the PVL, the application tries to display the translation in the

substitution language. The language must have the Substitution option set in Translation Manager.

● If no visible translation is available in the substitution language, the application tries to display the translation

in the dominant locale of the user's PVL. The dominant locale language must be set to Ready for use in

Translation Manager.

● If no visible translation is available in the dominant locale, the application displays the original content

language.

4. Steps for Translation:

1.Open a Web Intelligent document (Webi) form local repository or Import from Central Management Console (CMC)

to translate.

2.Select the Webi document from the repository and click Add button. Click on Finish button once the document is

added

3.The document is opened in CMC as shown below

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 27/55

5. 4. Select translating languages from the Language Management view by moving them from Available Language to

Selected Languages . Once the languages to translate are moved from Available Languages to Selected Languages

in Language Management, the text for the selected languages is displayed by the default copy of the source

language. This is due to the Autofill option

5.Translate the document Name, in a specified field in Editor View by selecting the field. Enter the appropriate

translated words in Text Editor View. Click Apply .

The status will be changed automatically to “TRANSLATED” after clicking Apply button

6.Use this method to translate the fields of all languages . The prompts will be listed under the folder “Queries”

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 28/55

7.The prompts will be listed under the folder “Queries”

8.Report tab names are available under “Reports”

9.All other static strings are brought to TM by applying the function GetLocalized() to each strings in BO report and will

be listed in TM under “Strings to Localize”.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 29/55

10.Fallback option to be set for English to set it as substitution language (default translation). As an example, a

document is translated in English, German and Italian. The substitution language is English. If you want to view its

French version even though it is not translated you will view its substitution language, i.e. English.

11.Export the document to CMS

12.Exported to CMS

13Check whether the documents are translated into selected languages in InfoView. Log in to BI Launch Pad and

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 30/55

click on preference to change desired viewing language. The report can be viewed in the selected locale.

1154 View s 11 Comments

Problem Summary Error: The report failed while scheduling in Excel format in BO Xi 4.0.

Details In BO Xi 3.1, the scheduled report was successfully run, when the output format was Excel. The report when

manually refreshed ran successfully in 3.1 and 4.0 environments. The report when scheduled in 4.0 ran successfully

when the output format was Web Intelligence. The schedule parameters were the same in 3.1 and 4.0 environments.

Cause

Initially

obtained the ‘system cannot find the path specified’ error because the special character ‘/’ is not allowed in the report

name if scheduled. After resolving this issue obtained ‘Maximum character output size limit reached. Contact your

BusinessObjects administrator’ error because ‘maximum character stream size’

(Web Intelligence processing service property) was less than required (was only 5 MB).

Resolution

1. Go to 4.0 Development CMC

2. Under servres Open the Web

Intelligence Services.

3. Open the Web Intelligence Processing

Service properties.

4. Change the Maximum character output

size to 25 MB.

5. Restart the Web Intelligence

Processing Server.

6. Schedule the report in BO Xi 4.0

and output format set to Excel.

7. Repeat the same steps in BO Xi 4.0

SIT, UAT and production

851 View s 4 Comments

Scheduling WebI report in excel format issue

Posted by Salahudheen Kappan Jul 16, 2013

BusinessObjects Administration – File RepositoryCapacity planning

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 31/55

This is the continuation of my previous blogs BusinessObjects File repository servers here.

Business Objects Administration - File Repository Servers

BusinessObjects Administration – File repository store capacity planning Considerations Let us see the capacity planning process for FRS step by step

Capacity planning for Input FRS Below factors need to be considered for Input FRS disk space requirement

A. Number of Users

B. Number of reports per user’s personal folder (Favorites & Inbox)

C. Average Report Size in User’s personal folders (MB)

D. Number of Report Templates in public folders

E. Average Report Size in public folders (MB)

F. Number of Universes

G. Average Size of the universe (MB)

Considering all the factors above we can estimate the Input FRS space requirement as below

And the final Input FRS server sizing would be IFRS size = [ A * B * C ] + [ D * E ] + [ F * G ] in MB

Capacity planning for output FRS Below elements needs to be considered for output FRS disk space requirement

H. Total Number of Scheduled Reports

I. Number of report instances created in a month

J. Average Scheduled Report Size

We can estimate the output FRS space requirement as below

And the final output FRS server sizing would be OFRS size = = [ J ] * [H + ( I * 6 )] in MB * 6 is used for counting instances created in six months

of duration

Note : - The Capacity planning process is specific to a simple BusinessObjects environment with the

existance of reports like Crystal and WebI. You may need to add/incorporate certain parameters if

you are using tools like Explorer etc. so as to accomadate the space required for them.

- I have Considered only reports and Universes in capacity planning. You may required to add if

Posted by Manikandan Elumalai Jul 16, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 32/55

you have something. Hope you find this Blog is interesting. Thanks for reading.

1752 View s 4 Comments Tags: bo_capacityplan

This is the continuation of my previous blogs about BusinessObjects File repository servers here.

Business Objects Administration - File Repository Servers As part of sizing exercise we will estimate number of CPU cores and the memory requirement.

You can check for sizing best practices and the Quick sizer here. http://scn.sap.com/docs/DOC-

33183 Along with this it is always recommended to go with the optimum size of File repository store to

hold all your BI contents in the Disk. Below are some of the considerations while estimating disk

space for Input File store.

Disk space requirement considerations for Input File store. 1. Reports that are saved in public folder (Report templates) will be always stored in Input File

repository store.

2. Reports that are saved in user’s personal folder (Favorites) will be stored in Input File repository

store.

3. Reports that are sent to user’s Inbox will also be stored in Input File repository store.

BusinessObjects Administration – File repository storecapacity planning Considerations

Posted by Manikandan Elumalai Jul 15, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 33/55

to get the path of the Inbox document you should always use Query builder where the

Properties is not available in BI Launchpad

4. Universes will be stored in Input File repository store.

Continuing with the Input file store considerations below are some of the thoughts about

estimating disk space for output File store. Disk space requirement considerations for Output File store

Reports that are scheduled to any type of destination other than User’s Inbox will be stored in

Output File repository.

We will see more about FRS capacity planning in my upcoming blog. Stay tuned.

1790 View s 0 Comments Tags: bo_frs, bo_filer_epository

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 34/55

Dear SCN User,

Currently I am working on an Pilot / Prototype to connect the SAP BusinessObjects BI4.x platform against Google

BigQuery. In collaboration with our Developer teams, Google BigQuery Teams and Simba teams we have been able

to connect the BI4.x clients against Google BigQuery.

We reached the state that we are looking for a pilot environment/customer whom is interested in validating the

connectivity.

Although the pilot is build against BI4.x clients, this would not limit the prototype if you are currently using the XI3.x

platform.

Currently we have been able to connect the following BI clients to run against a Google BigQuery datasource:

- Universe Design Tool

- Information Design Tool

- Explorer

- Web Intelligence

- Crystal Reports 2011

- Dashboards 4.0

- Lumira 1.x (via Universe)

To put the cards open on the table, this is a prototype and connection to BigQuery is not yet fully supported. However,

if we recieve enough requests for access to BigQuery and have a successfull Pilot project, SAP is planning to further

investigate the addition of Google BigQuery support to it's portfolio.

If you are interested in piloting the Google Big Query access, please drop me a line by responding to the blog or direct

email.

Thanks

Merlijn

BI Solution Architect @ SAP Solution Management

2093 View s 0 Comments

Tags: bi, bi4, business_intelligence_(businessobjects), analytics, 4.0, bi4.0, business_intelligence

Google BigQuery support for the SAP BI platform

Posted by Merlijn Ekkel Jul 15, 2013

Migration and LCM BIAR Backup in BO 4.0 For Earlier business objects versions, Migration of objects (like universes, reports and program objects) from one

environment (development) to another environment (Test) and BIAR back up are done through Import Wizard but in

BO 4.0, this is handled through LCM (life cycle manager).The LCM is web based application; you can access through

web browsers.

The LCM BIAR backup steps are listed out as below

Steps for creating the job

1. Log on to the LCM through URL http://systemname:8080/BOE/LCM (system name refers your BO 4.0 server

name, this may be customized)

1.

Migration and LCM BIAR Back up in BO 4.0

Posted by venkatraman varadharajan Jul 12, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 35/55

step1.JPG

2. Create the new job for universe BIAR backup.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 36/55

step2.JPG

3. Enter the mandatory job formation such as Name, Save Job in (location to save the job), Source ( the server

details) and Destination details name Select the universes

BIAR backup activity : - The destination is “output to BIARLCM File” option.

Environment Migration : - The Destination is migration target server location

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 37/55

step3.jpg

4. Browse the source folder in the left side panel and select the universe objects from the universe folder

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 38/55

Step4.jpg

5. Select the objects and click on add and close option. The desired Job is created.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 39/55

step5.JPG

6. Promote the job and execute it after entering the change management ID.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 40/55

step6.JPG

Parameters for promoting the job

Mention the change Management ID : - Weekly_Bair_Backup

Password encryption : - Not applied here (Password pop up will be shown be when we

restore the LCMBIAR file).

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 41/55

step7.JPG

7. Save the BIAR file into the local folder.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 42/55

step8.JPG

8. We can also automate the BAIR backup activity

9. Schedule Job: - We can schedule the job based on our requirement. (we schedule the backup job on every

Friday week

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 43/55

step9.JPG

LCMBIAR location:- we have two option

1. File system

2. FTP Location.

We are planning to FTP the LCMBIAR to shared path \\system\shared\

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 44/55

step9.1.JPG

10. While Restoring the backup, we need to create the new job as mentioned above. source is our BIAR file and

destination is our BO environment

Import the LCMBIAR file

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 45/55

step10.JPG

Mention the file location

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 46/55

step11.JPG

Specify the destination and job save in details into the job and execute (please refer the above steps for

execution process)

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 47/55

Step12.jpg

2246 View s 5 Comments Tags: bi4.0

'X' Unx Universe Issue in BO 4.0

Issue

User is trying to create few test reports using the UNX version of the universe. They have encountered couple of

issues which is listed below

1. While generating the WebI report based on 'X' universe. It is throwing the below error.

Unx Universe Issue in BO 4

Posted by satheesh Menon Jul 8, 2013

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 48/55

2. While generating the Dashboard report, getting the below error

Solution:-

We need to modify the prompt filter definition in the join condition. The ' X' universe table join contains the below

prompt filters in 16 different places.

Ø ADMIN.V_DWH_GEOGR_ORG_DIM.SLS_FORC_CD IN @Prompt('Enter Sales Force:','A','Organization Sales

Force\Sales Force Code(For Cust Align Prompt)',MULTI,CONSTRAINED,PERSISTENT)

Ø ADMIN.V_DWH_ALL_GEOGR_ORG_CUST_ALIGN_REL.CUST_ALL_ALGN_TYP=@Prompt('Enter Customer

Alignment Type:','A',{'CURRENT CUSTOMER ALIGNMENT','CALL PLAN ALIGNMENT','TARGET UNIVERSE CALL PLAN

ALIGNMENT','CUSTOMER TERRITORY SEGMENT ALIGNMENT','CUSTOMER TERRITORY PRODUCT SEGMENT

ALIGNMENT'},MONO,CONSTRAINED,PERSISTENT) )

Ø ADMIN.V_DWH_PRDCT_HIER_PRDCT_DIM.MRKT_LVL_PRDCT_NM IN @PROMPT('Enter Market(s):

','A','Market\Market Name',multi,constrained,persistent))

Changes applied on 'X' unx format Universe are mentioned as below

Ø Create the List of values in the data foundation layer for object which was referring into prompt (Cust Align (static

lov), Market Name (custom sql) & Sales force code (custom sql))

Ø Create the parameter in the data foundation layer for prompt objects. Refer the lov which was created above.

Ø Change the prompt definition as @Prompt (parameter Name) for example @prompt (Market Name).The change

needs to be applied into the all join condition (16 prompt Filter)

Ø Save and close the data foundation and export the Business layer into the repository

Before changes:-

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 49/55

Ø ADMIN.V_DWH_GEOGR_ORG_DIM.SLS_FORC_CD IN @Prompt('Enter Sales Force:','A','Organization Sales

Force\Sales Force Code(For Cust Align Prompt)',MULTI,CONSTRAINED,PERSISTENT)

Ø ADMIN.V_DWH_ALL_GEOGR_ORG_CUST_ALIGN_REL.CUST_ALL_ALGN_TYP=@Prompt('Enter Customer

Alignment Type:','A',{'CURRENT CUSTOMER ALIGNMENT','CALL PLAN ALIGNMENT','TARGET UNIVERSE CALL PLAN

ALIGNMENT','CUSTOMER TERRITORY SEGMENT ALIGNMENT','CUSTOMER TERRITORY PRODUCT SEGMENT

ALIGNMENT'},MONO,CONSTRAINED,PERSISTENT) )

Ø ADMIN.V_DWH_PRDCT_HIER_PRDCT_DIM.MRKT_LVL_PRDCT_NM IN @PROMPT('Enter Market(s):

','A','Market\Market Name',multi,constrained,persistent))

Step 1:-

Create the List of values in the data foundation layer for object which was referring into prompt (Cust Align (static lov),

Market Name (custom sql) & Sales force code (custom sql))

Static lOV for Cust Align

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 50/55

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 51/55

Step 2:- Custom Sql based LOV for Market Name & Sales force code

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 52/55

Step 3:- Create the parameter in the data foundation layer and point the newly created LOV values

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 53/55

Step4:- Above mentioned prompt filter need to be replaced by the parameters

Before changes

A. ADMIN.V_DWH_ALL_GEOGR_ORG_CUST_ALIGN_REL.CUST_ALL_ALGN_TYP=@Prompt('Enter

Customer Alignment Type:','A',{'CURRENT CUSTOMER ALIGNMENT','CALL PLAN ALIGNMENT','TARGET

UNIVERSE CALL PLAN ALIGNMENT','CUSTOMER TERRITORY SEGMENT ALIGNMENT','CUSTOMER TERRITORY

PRODUCT SEGMENT ALIGNMENT'},MONO,CONSTRAINED,PERSISTENT) )

After Changes:- @Prompt(parameter)

A. ADMIN.V_DWH_ALL_GEOGR_ORG_CUST_ALIGN_REL.CUST_ALL_ALGN_TYP=@Prompt(Cust_align)

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 54/55

Step5:- Apply the same change for all the associated join (prompt filter) and publish the business layer after save the

data foundation layer.

6/3/2014 BI Platform | SCN

http://scn.sap.com/community/bi-platform/blog?start=90 55/55

Follow SCNSite Index Contact Us SAP Help Portal

Privacy Terms of Use Legal Disclosure Copyright

Step 6:- Generate the sample report and verify the report data.

1829 View s 6 Comments

1 … 5 6 7 8 9 … 17

PreviousNext