SAP BI Cockpits & Dashboards best practice

Here is an overview of the options you have for dashboards, cockpits and scorecards using Web Application Designer, Visual Composer, Java SDK, 3rd Party, SEM- CPM, Portal iViews.. As well as best practices for developing Cockpits by Deepu Sasidharan & Dr. Bjarne Berg called "SAP BI Cockpits & Dashboards best practice: Evaluate and choose the right BI tool to build management cockpits".
Like always, we provide PowerPoints, so that everyone can take the slides they like: http://csc-studentweb.lrc.edu/swp/Berg/articles/Reporting_Analytics_2006_Cockpits_v10.ppt

Dear Berg,
Could you send it to my e-mail, I need to do web quwry to publisb in portal 6.o with BI 7.0, and I dont know how to execute it. Will be help full if cound send me step by step guide. My e-mail is [email protected]
Thanks in advance,
Antony

Similar Messages

SAP CRM V1.2007 Best Practice

Hello,
we are preparing the installation of a new CRM 2007 system and we want to have a good demo system.
We are considering too options;
. SAP CRM IDES
. SAP CRM Best Practice
knwoing that we have an ERP 6.0 IDES system we want to connect to.
The Best Practice seems to have a lot of preconfigured scenarios that will not be available in the IDES system (known as the "SAP all in one").
How can we start the automatic installation of the scenarios (with solution builder) connecting to the ERP IDES system?
Reading the BP Quick guide, it is mentioned that in order to have the full BP installation we need to have a ERP system with another Best Practice package.
Will the pre customized IDES data in ERP be recognized in CRM?
In other words, is the IDES master data, transactional data and organizational structure the same as the Best Practice package one?
Thanks a lot in advance for your help
Benoit

Thanks a lot for your answer Padma Guda,
The difficult bit in this evaluation is that we don't know exactly the
difference between the IDES and the Best Practice. That is to say,
what is the advantage to have a CRM Best Practice connected to an ERP
IDES as opposed to a CRM IDES system connected to a ERP IDES system?
As I mentioned, we already have an ERP IDES installed as back end system.
I believe that if we decide to use the ERP IDES as the ERP back end, we will loose some of the advantage of having an ERP Best practice connected to an CRM best practice e.g. Sales area already mapped and known by the CRM system, ERP master data already available in CRM, transactional data already mapped, pricing data already mapped etc.
Is that righ? Or do we have to do an initial load of ERP in all cases?

How to Embed a CR in Dashboard best practice

i want to work on Inventory Dashboard in Purchasing module Best practice.
it has 4 CR reports to embed " all plant in client " ,All inventory KPI , All Material Group , Turn ovar. ( i already uploaded on CMC )
the Excel of the dashboard has 5 pages " setting " , Data , Display , Datasource , transaction .
So how to embed CR reports in Dashboard and how can i know which cell should i can insert my CR.

You mean i embed every CR in a diffrent excel sheet ?! how this can be done if i have 3 CR reports and 5 excel sheets and how can i know which CR repot to embed in excel sheet ? please i need more details
Thanks

SAP GUI Roll Out Best Practice

I was wondering what is the best practice for rolling out a new SAP GUI. My plan is to upgrade our IT Department, and Super Users with the upgraded GUI and see if any errors/problems occur. If I don't have any major issues I would roll out to the User Community after about two/three weeks.
Is this typical practice ? I have heard other Professionals say to just roll the GUI out, and don't worry about testing it ? and I have heard other companies etc.. do a set of testing scripts etc..
Any feedback appreciated. - Thanks.

Hi,
yes I have done it on our company for years.
once new released or new patch of SAPGUI is launched, I will ask my SAP Functional, ABAP and BASIS mates to try it for a month with various report and transaction variation for standard and Z-tcodes, for dialog and background processing, printing, and export and import data.
After my IT-SAP mates feels that SAPGUI is ready to be used, I will launched it to all user in another department and keep to listen any feedback from them regarding this SAPGUI.
hope it help you.
rgds,
Alfonsus Guritno

Best Practices For Dashboard design through BI

Hi
If I want to create a dashboard through BI7 .what is the best way to suggest the client people. Which way SAP recommended for BI7 Best practices for dashboard design.
Thanks & Regards,
Praveen

Sloved

SAP ASE Best Practice latest update

Hello experts,
just wondering if somebody already reviewed thoroughly latest guide for best practices on SAP Sybase ASE?
I am talking about the document from note 1680803 - SYB: Migration to SAP Adaptive Server Enterprise - Best Practice (former note 1722359 - SYB: Running SAP applications on SAP ASE - Best Practice).
The guide for normal runtime operation was merged with the guide for migration, but there are some contradictory statements.
Apart from that the study case is again designed for server with huge memory and lot of CPU cores (so not so real case normally, I wonder who setup so often such huge servers...), I have found some inconsistencies.
E.g. in part "Reconfigure Engines and Parallel Processing", they talk about to limit ASE engines to 16, but the command configures 32.
alter thread pool syb_default_pool with thread count = 32, idle timeout = 2000
No change to the previous setup for migration. Is this just typo? I understand it should be 16, and then also number of network tasks for normal operation would be 4 (as mentioned in the beginning of guide that normally you set up 1 per 3-4 engnes). If this is not typo, then number of network tasks is wrong as it should be 8.
Also they introduced idle timeout, but only talking about ERP and possible lower value for Solman - does this mean that for BW you keep default value (which if I am not mistaken is 100)? As per ADM540 you should even decrease this timeout when SAP system is sharing server with database - I know that document is old, but is again contradictory, not saying that it is wrong, but not well explained.
If anybody checked new version of guide, please let me know, I think it is bit messed up and is bit difficult to distinguish what you should set up for migration case and what for normal operation case.
Thanks!
Regards,
Matus

Actually, quite a few customers run with that many engines/memory.   In fact, it is difficult these days to even buy a server with less than 128GB of memory and 16 cores/32 threads.    Pretty much the only time we see less is when the install is in a VM.   Interestingly, we had comments from the first version suggesting the numbers were not realistic given the typical size of systems being deployed were much larger....    In addition, in my experience with customers on SAP systems, they were not aware of how much memory was necessary to really support medium to large systems based on the configurations they were attempting.
I am sorry that you feel some of the examples are contradictory. You are correct in pointing out that the text refers to 16 engines and the example configures 32....   So yes, for that specific example, it should have been 16.
Secondly, not having seen ADM540, but I think there is a bit of a problem if they suggest that.   I my opinion (and I have spent a lifetime tuning ASE), the idle timeout for ERP and BW should likely both be 1000+ and 2000 is not unreasonable.   The comment in ADM540 is likely due to if ASE and a NW CI are sharing the same cores - e.g. you have a 4 core box and ASE is running on 2 cores (we will ignore threads for this discussion) and you have 30 NW worker processes - which obviously will need to bump ASE off the cpu in order to run.   This may be fine in a test/dev or even a solution manager system, but bumping ASE off the core is NOT a good thing for a production system. In fact, I would encourage using numactl or similar to fence off the the cores used for ASE from NW worker processes if at all possible.   We have seen cases of overloaded NW installations with multiple CI instances with hundreds of worker processes each starving cpu away from ASE......sooo....I would tend to actually be a bit more than firm on suggesting that 100 is a very bad starting point.   Given the number of client side joins that SAP uses to avoid [DBMS proprietary] temp tables, it is critical that ASE's (or any DBMS) response time be minimized as much as possible.....having ASE yield the core practically as soon as it gets done processing one task (and puts it to sleep pending an IO) just really causes things to run slow.   Think of a typical query that returns 10 rows - say wide enough that each row fills 1 packet.   If the packet transmit time (and client ACK) takes more than 100 microseconds on CPU (almost a given for network interactions...as clock ticks are in nanoseconds and networking is minimally milliseconds - 1000 microseconds), ASE would yield the CPU every time it sent a packet.    When the client wanted the next packet, the OS would have to wake up the ASE process (an interrupted sleep) which is a nasty heavy weight operation.   Hence it is best for ASE to hang out on the CPU until reasonably sure that nothing more is going to happen very soon....and on current cpus...and having it run for 1-2ms (1000-2000 microseconds) shouldn't be a hardship.     If you created a separate thread pool for batch worker processes, then I could see maybe using a lower idle timeout such as 200 or 250......100 is just plain too low in my mind...it is like saying ASE is expecting an odd query every few seconds vs. a steady workload. Basically at that level, there had better be a task in the ASE job queue or one on the way on the network already, or that engine is going to sleep.
While I state that with regards to ADM540 itself, I have not seen the class (perhaps)...one customer did show me the notebook of a class (ASE Sys Admin) they went to and it was really targeted at non-SAP installations more than SAP installations - from a reality/experience aspect.   Part of the issue with the class the customer showed me was it borrowed liberally from the old SY classes as a starting point, but at the point the class was developed there was not a lot of experience with running SAP installations on ASE to really point out the fine tweaking areas such as idle timeout.
However, the document was really aimed primarily at Business Suite vs. BW systems or a Solution Manager install (which are much smaller) - there are a lot of other considerations for BW the guide doesn't get into - although some of the sizing is a better start than the defaults provided by SAPINST
The former runtime guide essentially was just merged in to the Post-Migration Steps section.
May do a quick refresh in the near-future (due to some recent experiences), so if you have other specific examples of the text and SQL not aligning - please let me know.

Benchmark Your Best Practices through the ASUG/SAP Enablement Survey

One of the most frequent questions asked by companies implementing SAP is u201Chow do other companies get their employees ready to use the system?u201D They want to know how similar companies have addressed the most critical success factors for preparing and sustaining their end users for new technology deployment. SAP is consolidating knowledge of best practices used in the market through the ASUG and SAP Enablement Survey.
ASUG and SAP have teamed together to build a survey that will allow respondents to gain insight into how the market is addressing enablement, and how similar companies rate their achievements. All responses are consolidated to provide insight on enablement practices by industry, company size, region, budget allocation, and more. Individual responses remain confidential.
As a respondent you will receive a report outlining the most critical enablement practices implemented by comparable companies. The report provides specific insight about your enablement practice in relation to similar companies. Please take the time to complete this short survey (10-15 minutes) today. Your voice matters and we really appreciate you taking the time and completing the survey.
Click on the link to access the survey:
[ASUG/SAP Enablement Benchmarking and Best Practices Survey|http://www.benchmarking.sap.com/cgi-bin/qwebcorporate.dll?idx=CUX8C2&SHSP1Q2A=ASUG&LNG=0]
Edited by: Claudia Mandelli on Feb 22, 2012 11:53 PM

Hi ,
Please find my answers below:
1. The roles will be created in BW and should automatically appear in BO CMC Authentication SAP roles, if there is a connectivity setup between BO and BW irrespective of the SSO.The roles are transported by the BW security team.
2. Every environement will have a unique connection to the corresponding SAP BW environment.For example SAP BW DEV will be mapped to BO DEV, SAP BW PROD will be mapped to BO PROD.So these settings cannot be migrated through Promotion Management.
3.This authentication can be applied to all tools , the SSO does not depend on the tool ,it depends on the integration between two systems which in this case are BO and SAP BW
As mentioned earlier, after integration all tools can have SSO
You can refer to a lot of help documents on this site which will help you to setup the integration between SAP BW AND SAP BO.
Kind Regards,
Priyanka

Seaching for Best Practice links that work

Hi,
past few years I have been able to access SAP Best Practices documents like SAP Best Practices SAP Best Practices for CP and Wholesale Industries
(this one still works and guides me to the building block and process overview documents!).
Recently any link I can find to SAP Industry or Baseline Best Practices ends up with a dead link. See for example trying to get from here SAP Best Practices Baseline packages – SAP Help Portal Page
to Localized for Netherlands V1.607 SAP Best Practices package further below on that page, results in screen shot attached. I have seen that in many more examples (different countries, or in Industry Best Practice Packages instead of Country Baseline packages....)
Does any know whether and how SAP redesigned their access to Best Practices documents (Configuration Guides, eCatts, Scenario Process Overviews etc.?
Thanks for your reply.
Thijs

Hi, Thijs,
There is currently a problem with Best Practices on the Help Portal. On the home page of the portal (http://help.sap.com/) there is a message that reads "Stay Tuned - There are temporary problems when accessing some content types, for example PDF documents or Best Practices. We are working on a solution."
Our Wholesale Distribution industry group does not manage the Help Portal pages, so, unfortunately, I don't know the status of the problem or when it might be resolved.
Lynn

Re engineering of existed process / Best Practice (customization)

Hi all of you,
We are implementing SAP ECC 6.0 for one of our clients. Client is asking us to compare their existed business process with Best Practice / standard process and based on the result, asking to prepare a GAP analysis between the existed and best practice for his business.
SAP itself is a best practice in the respective domains / business processes. By implementing SAP ERP, the client will have best practice for his business processes as I know. But thing is, how can I explain to the client that SAP has given the best practice and based on which, client will consider the SAP practice as Best Practice for the business??
Please give me a solution
Regards,
Ramki

f l,
I'm not sure deleting keys from the registry is ever a best practice, however Xcelsius has listings in:
HKEY_CURRENT_USER > Software > Business Objects > Xcelsius
HKEY_LOCAL_MACHINE > SOFTWARE > Business Objects > Suite 12.0 > Xcelsius
The current user folder holds temporary settings, such as how you've modified your interface.
The local machine folder holds more important information.
As always, it's recommended that you backup the registry and/or create a restore point before modifying or deleting any keys.
As for directories, the only directory Xcelsius uses is the one you install to. It also places some install logs in the temp directory, but they have no effect on the application.

Highly Required CRM 5.0 Best practices for CRM Service Module

Dear all,
I have been searching for CRM 5.0 version best practices in Internet quiete a long period, but could not find anywhere.
currently SAP is providing only best practices for SAP CRM 2007 version.
since most of configuration is differing because of Webclient Interface, I request you to refer a source from where I can get the CRM 5.0 Best Practices for Service module.
Your suggestions and help will be highly appreciated.
Best regards
Raghu ram

Hi Srini,
<removed by moderator>
Thank you & Best regards
Raghu ram
Edited by: Raghu Ram on Jul 16, 2009 6:09 AM
Edited by: Raghu Ram on Jul 16, 2009 6:11 AM
Moderator message please review the rules of engagement located here:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/home/rulesofEngagement
Edited by: Stephen Johannes on Jul 16, 2009 8:12 AM

System requirement tp install Utilities Best practices(utilities-V1.500)

Hello All,
We want to install SAP Best Practices for Utilities (UTILITIES - V1.500) in our landscape. I checked the system requirements proposed by SAP and observed that most of the s/w releases they are reffering to are ECC5 (500) and our system is at release ECC6 (600). I beleive that there will be a lot of changes in the config nodes of ECC6 from ECC5. So if we install it in our landscape then will it cause a conflict in configuration? So is it advisable to install Utilities Best Practices in our system? Please find below the system requirement proposed by SAP for installation of best practice and RTD system Configuration. Kindly let me know.
System Requirements proposed by SAP is as follows
Software Component     Release     Support Package     Highest Support     Short Description of Software Component
               Package
SAP_BASIS     640     13     SAPKB64013     SAP Basis Component
SAP_ABA     640     13     SAPKA64013     Cross-Application Component
ST-PI     2005_1_640     2     SAPKITLQH2     SAP Solution Tools Plug-In
PI_BASIS     2004_1_640     10     SAPKIPYI6A     Basis Plug-In (PI_BASIS) 2004_1_640
SAP_BW     350     13     SAPKW35013     SAP_BW 350
SAP_APPL     500     9     SAPKH50009     Logistics and Accounting
SAP_HR     500     11     SAPKE50011     Human Resources
EA-IPPE     300     7     SAPKGPIC07     SAP iPPE 300
EA-APPL     500     9     SAPKGPAC09     SAP R/3 Enterprise PLM, SCM, Financials
EA-DFPS     500     9     SAPKGPDC09     SAP R/3 ENTERPRISE DFPS
EA-FINSERV     500     9     SAPKGPFC09     SAP R/3 Enterprise Financial Services
EA-GLTRADE     500     9     SAPKGPGC09     SAP R/3 Enterprise Global Trade
EA-HR     500     11     SAPKGPHC11     SAP R/3 Enterprise HR Extension
EA-PS     500     9     SAPKGPPC09     SAP R/3 Enterprise Public Services
EA-RETAIL     500     9     SAPKGPRC09     SAP R/3 Enterprise Retail
FINBASIS     500     9     SAPK-30009INFINBASIS     FINBASIS 300 : Add-On Installation Request
SLL-LEG     300     9     SAPK-30009INSAPSLL     SLL-LEG 300_640 : Add-On Installation
CPROJECTS     300_640     8     SAPK-31408INCPROJECT     SAP cProject Suite 3.10 (based on 640)
BI_CONT     353     5     SAPKIBIFP5     BI_CONT 353 : Add-On Delta Upgrade
BP-INSTASS     500V3     0          -     Best Practices Installation Assistant
BP-BLERP     500V6     0          -     Best Practices All-in-One (based on ECC
Our RTD System
Software Component     Release     Support Package     Highest Support     Short Description of Software Component
               Package
SAP_BASIS     701     4     SAPKB70104     SAP Basis Component
SAP_ABA     701     4     SAPKA70104     Cross-Application Component
ST-PI     2005_1_700     6     SAPKITLQI6     SAP Solution Tools Plug-In
PI_BASIS     701     4     SAPK-70104INPIBASIS     Basis Plug-In
SAP_BW     701     4     SAPKW70104     SAP Business Warehouse
SAP_APPL     604     3     SAPKH60403     Logistics and Accounting
SAP_HR     604     11     SAPKE60411     Human Resources
EA-IPPE     400     15     SAPKGPID15     SAP iPPE
EA-APPL     604     3     SAPKH60403     Logistics and Accounting
EA-DFPS     600     13     SAPKGPDD13     SAP Enterprise Extension Defense Forces & Public Security
EA-FINSERV     600     3     SAPKGPFD03     SAP Enterprise Extension Financial Services
EA-GLTRADE     600     5     SAPKGPGD05     SAP Enterprise Extension Global Trade
EA-HR     604     11     SAPK-60411INEAHR     SAP Enterprise Extension HR
EA-PS     600     13     SAPKGPPD13     SAP Enterprise Extension Public Services
EA-RETAIL     600     5     SAPKGPRD05     SAP Enterprise Extension Retail
FINBASIS     600     13     SAPK-60013INFINBASIS     Fin.
Thanks a lot in Advance!
Boby Mathew

Hi ,
Please go with the sequence 4, 1, 2 ,3. This would give you solution manager key for the other systems also.
Rest of the stuff you can get it in the installation guides. http://service.sap.com/instguides
Regards,
Pavan

Transport Best Practices - Cumulative Transports

Hi All,
    I am looking for a some sort of authoritative guide from SAP on ECC Transport Best Practices, especially around merging/combining/accumulating multiple transports into fewer ones. We are a very large project, but we haven't figured out the CVSs like ChaRm so we still deal with individual transports.
The reason I am asking this is that we some development leads on our project that insist that ALL transports that leave Development system must be imported into Production. They claim this the SAP best practice. An SAP consulting review of our system also left a vague note that "We are orphaning transports". This could mean that 1. either we are not importing all the stuff that leaves Dev system 2. or we are not keeping track of our code changes across all environments. Proponents of "All transports must get to PRD" are interpreting this as "1".
I have my team cumulate transport for subsequent changes into newer transport and only take the newest Transport to Production. The continuous rolling of old Transport into new one using SE01 "Include Objects" options ensures that all changes part of current development are in a single TR. Fewer transports mean fewer housekeeping across all systems, and less chances of something going out of sequence or missed out. This is for Workbench Transports only. I understand Config transports could get a little tricky with rolling in.
If you can't point me to a link, what is your take on "Send everything to Prod" vs. "Combine changes into fewer Transports"? I can't think of any software packaging methodology that suggests putting everything, including some junk/crap, into production build. I have looked at SAP enhancement packs, SPS, and Notes. I haven't found any evidence of SAP including older buggy code in what it releases to its customers.
Thank you all!

Jānis, Christian,
    I think we are all on the same page. Let me clarify my specific scenario a little bit more.
We are about 15 ABAP developers team, for production support. We don't do huge changes. Our code updates are mostly limited to a handful of objects (average 2 - 5). We often have multiple iterations to same objects. For large scale development objects, this approach may not work very well. Those should really utilize SolMan or other CVS tools.
Here is How I have my team putting together final transport.
step 1. Change is done to object X. Transport #1 created and released after standard checks.
step 2. More change is needed for object X. Transport #2 Started. Transport #1 is brought in using SE01 include objects at the main task. Changed objects are in lower tasks. This way, I can tell what was brought over, and what really changed this time. Releases of the Transport #2 inspects all objects and insures all objects from #1 are included in #2, and that there are no other changes between #1 and #2 to any of the objects. This is very easy check mostly from Version History.
Step 3. More changes needed to object X and Y. Transport #3 started. Transport #2 brought in at main task. Same check from Step 2 is done to ensure no other changes exist.
step 4....6. Step 6 ended at Transport #6. All changes verified in QA system.
Only the Transport #6 needs to be sent to Production since previous Transports 1 to 5 were rolled into #6.
Jānis, the deletions will be covered automatically just like standard SAP. No special manual steps needed.
Christian,
   The transport of copies works in similar way. Only thing different is that the Main/cumulative transport is released at very last, possibly after QA tests have been confirmed.
I had thought about doing Copies vs. cumulative. I preferred to go with having Transport in QA already at the time of approval. I would have hard time explaining to our client why a Transport was released out of Dev After all tests were done and signed off.
However, the Copies have advantage that intermediate versions or parallel changes of same objects are easily recognized upfront vs. us having to check each transport before release.
Jānis, the "copies of Transport" also creates extra versions in version history just like manually adding objects in a transport.
My quick analysis between copies and cumulative only came with one different that 'copies' have a different flag/attribute in Table E070. I am sure the flag means something to SAP, but for versioning history, it makes no differences.
Regardless of if I cumulate or not, based on your experiences, have you come across notion that everything that leaves Dev must get to PRD as SAP Best Practice? What would your reply be if someone insists that is the only way to move code to production?

Best Practices vs. BPM

Hi,
I'm new on XI, and I have to define some best-practices and naming convention that will be used by our company. The goal is to try to start working in XI the right way.
I found following sources of information :
<a href="https://websmp207.sap-ag.de/~sapidb/011000358700004455192006E/NameConventions.pdf">SAP XI 3.0 Best Practices for Naming Conventions</a>
<a href="/people/r.eijpe/blog/2006/05/22/d-xie-soap-part-3-determine-software-component-version-of-standard-sap-idocs-and-rfms Soap part 3: Determine Software Component Version of standard SAP IDocs and RFMs</a>
<a href="/people/alwin.vandeput2/blog/2006/06/07/d-xie-soap-part-4-xi-software-component-architecture-for-point-to-point-scenarios Soap part 4: XI Software Component Architecture for Point-to-Point Scenarios</a>
Here is my scenario (probably a classic one!) :
SAP R/3 (Via RFC) ==> XI ==> 3rdParty Product (Via File Adapter)
If I follow best-practices indicated in previous documents, I need 3 products with their corresponding SWCV :
- One for SAP R/3 (custom function) : Contains the RFC
- One for XI : Mapping Objects, Integration Scenarios / Processes
- One for 3rdParty Product : Interface Objects
Up to now... Does it sound correct based on your experience ??
Now, here is my problem : BPM. It sounds logic to place the Integration Process in the XI SWCV. But I cannot use Message Interfaces from another SWCV (i.e. from my 3rd Party Product or from SAP R/3).
There is probably something wrong in my understanding, and I would really appreciate if somebody could help !! How should I proceed ? I'm not sure I should put everything under the same SWCV to use BPM !
Thanks in advance,

Hello Anne,
Sebastien asked me to respond to your question.
I think you have already your question answered by Wojciech Gasior. You should use Abstract interfaces. The Abstract interface should be created in the same SWCV as the BPM.
Your flow is:
Outbound interface (RFC) ==> Message mapping 1 ==> Abstract interface ==> BPM ==> Abstract interface ==> Message mapping 2 ==>Inbound interface (File)
Now the second question...how many SWCVs?
If you follow ..
- "SAP XI 3.0 Best Practices for Naming Conventions"
- weblog "Structuring Integration Repository Content - Part 1: Software Component Versions" and
- our weblog "D-XIE Soap part 4: XI Software Component Architecture for Point-to-Point Scenarios"...
... than you should have at least 3 SWCVs:
...but you could even think of 4.
SCVW 1: "Sender application"
- Outbound interface (RFC)
SCVW 2: "XI as integration engine"
- Message mapping 1
SCVW 3: "XI as process engine"
- Abstract interface
- BPM
- Abstract interface
SCVW 2: "XI as integration engine"
- Message mapping 2
SCVW 4: "Receiver application"
- Inbound interface (File)
We advice not to place mapping programs in the sender or receiver SWCVs because those are not the applications who execute the mappings. XI executes the mappings. So it should be an XI SWCV.
Why splitting the mappings from the BPM? The mappings are executed by the integration engine in the pipeline. The BPM is executed by process engine.
Why not splitting the Abstract interfaces from the BPM? The abstract interfaces are the interfaces (signature) of the BPM.
Is 4 SWCV not an enormous overkill in stead of using 1 or maybe 2? Thats up to you. Staying flexible in reuse means splitting up your SWCV.
My opinion about using just one SWCV: It is wrong. Because you dont have a good administration of the relation between interfaces and SWCV. See our weblog for a detailed description of the administration problem.
My opinion about using two SWCV: Where do you put your mapping? In the Sender or in the Receiver SWCV? It is not the Sender application or the Receiver application which executes the mapping, but XI executes the mapping.
My opinion about using three SWCV: For point-to-point scenarios it is the best. Now you stay flexible to upgrade to all kinds of scenarios.
My opinion about using four SWCV: For BPM scenarios, it is the most flexible one. A good way of controlling the versioning of the SWCs.
Hope it helps you and I would like to hear your and other SDNers opinion about our opinion.
Kind regards,
Alwin.
(See also our D-XIE weblogs.)

SAP BO Dashboards 4.1 best practice on layout and components

Dear SCN,
I have requirement to create a BO 4.1 dashboard with data & Visualization based on a excel sheet which is currently in use as a Mgmt dashboard. The current excel dashboard is having more than 100 KPIs in one view which is readable only if you put in on a slide and view it in full screen by running a slideshow.
Question 1:
1. Being the suggested size of the Xcelsius canvas not more than 1024 X 768 so that it is viewable with out scroll bar in BI launchpad or in any browser or in pdf, I am trying to confirm in this forum that the canvas size of 1024 X 768 is the recommended maximum size for the dashboard to get the clear view in any browser/BI launchpad . Pls confirm as it will help me in doing the design for the KPIs and its visualization.
Question 2:
1. I am using the BICS connection and accessing the source data from BW. Because the no. of KPIs are more and ranging between 10 cubes and 40 queries as the data is across different modules, I would like to know what is the recommended no. of connections for queries /cubes in dashboard using BICS connectivity which does not affect the performance
2. For the same dashboard using BICS connection, What is ideal number of components like Charts/Scorecard/Spreadsheet table that is recommended to use to ensure better performance?
I appreciate your answers which can help the finalization of the dashboard design for this dashboard of data and visualization requirements which is very high when compared to the normal dashboards.
Thanks and Regards
Jana

Hi Suman,
Thanks for your answers.You answers and links which you have attached are helpful and It answered my questions related to canvas size and Connections.
I am expecting some benchmark numbers as per the best practices with respect to the No. of components to be used to ensure the better loading of the dashboard. As the increase in number of components increase the size of the dashboard and also it requires more time to load the data for the components, I am looking for the number as per the best practice by considering the below points.
1. When I say the no. of components, I am not considering the components like label, text box,combo box or list box. I am considering the components which is used for visualization and interactive drill down on top of the visualized charts ( For Eg. Column charts, Pie charts, Gauges ).
2.I am not going to use more calculations/formulas in my dashboards as the values and structure are almost the same with the BEx query.
3.Having around 10 to 12 connections.
4.The data sets are not more than 900 rows totally. For any control, we will be binding only 100 rows at the max as the data for the KPIs are summarized at the year/month level at the BW layer.
Since the KPIs are more, the Visualizations are more and we can't re-use the Visualization charts for most of the KPIs. Currently I am ending up with ~35 charts/ gauges along with other label and selection controls which I will be using to show 100 KPIs with unique visualization requirements and I am going for the tab-wise layout with more dynamic to accommodate and separate logically.
Hope these details will give clear picture of why I am looking for the Benchmark on No. of components .
I appreciate your help!
Thanks and Regards
Jana

Best practices of BO/BW SSO SAP Authentication transports

Hi Friends,
We are going to integrate BW system with BO (SAP authentication). All the queries are built through BICS connections. And we have various reporting tools to implement SSO SAP authentication (Webi,Crystal,Dashboard.Design studio…etc)
As per the process there are certain activities which has to be performed at BW level
e.g -- BW Roles creation (PFCG---Crystal role enablement) and assigning to BO users
Once it is created in BW , we have to do integration at BO level( in CMC application) by selecting authentication and roles import followed by ……Groups..Users…folder and access level...
My question here is
Transports of BW objects for BO SSO (SAP) authentication (such as roles created for Users, Keystore certificate, uploads). Will these objects be transported by BW team or they will be separately downloading or uploading the certificate in different systems (like QAS ...PROD….)
And at BO level, once I integrate BO SSO, Do I need to do manual integration in QAS and Production system as well or it can be transported with promotion management of BO tool
Will these SSO(SAP) authentication can be applied to all tools in BI Launchpad such as (Design studio,Webi,Web application,Crystal….etc) as all users are required to have SSO to all BO tool
Regarding LUMIRA tool , Can we do SSO authentication
Please share your thoughts and experience.
I t would be great if I get BO administration best practices document for BW BO SSO and Users and Group management in CMC for implementing
Thanks in advance

Hi ,
Please find my answers below:
1. The roles will be created in BW and should automatically appear in BO CMC Authentication SAP roles, if there is a connectivity setup between BO and BW irrespective of the SSO.The roles are transported by the BW security team.
2. Every environement will have a unique connection to the corresponding SAP BW environment.For example SAP BW DEV will be mapped to BO DEV, SAP BW PROD will be mapped to BO PROD.So these settings cannot be migrated through Promotion Management.
3.This authentication can be applied to all tools , the SSO does not depend on the tool ,it depends on the integration between two systems which in this case are BO and SAP BW
As mentioned earlier, after integration all tools can have SSO
You can refer to a lot of help documents on this site which will help you to setup the integration between SAP BW AND SAP BO.
Kind Regards,
Priyanka

SAP BI Cockpits & Dashboards best practice

Similar Messages

Maybe you are looking for