SAP Business Objects reporting Errors and resolutions

#multivalue
usually when section is created on a column having multiple values for respective data set.
Solution : By looking why multiple values are coming issue can be resolved.
#error:
#compute : Computation Error
comes due to Errors in formulae and Also due to objects used in computation not present in data block.
Solution 1: if summary data is needed from detailed block then keep copy of objects and use Fold at break level in Desktop reporting. But this option is not present in Web Intelligence WebI Reports XI but version XI Release 3 onwards introduced again in WebI.

#sync
Synchronisation between data provider.
List of Error Codes:
http://help.sap.com/businessobject/product_guides/boexir3/en/xi3_error_message_guide_en.pdf

Universe Development issue:
https://sandyclassic.wordpress.com/2013/09/18/how-to-solve-fan-trap-and-chasm-trap/

A day in life of BI Engineer part 2

Read Part1:
https://sandyclassic.wordpress.com/2014/01/26/a-day-in-life-of-business-intelligence-engineer/
Part 2:
First few days should understand business otherwise cannot create effective reports.
9:00 -10am Meet customer to understands key facts which affect business.
10-12 prepare HLD High level Document containing 10,000 feet view of requirement.
version 1. it may refined later subsequent days.
12-1:30 attend scrum meeting to update status to rest of team. co-ordinate with Team Lead, Architect and project Manager for new activity assignment for new reports.
Usually person handling one domain area of business would be given that domain specific reports as during last report development resource already acquired domain knowledge.
And does not need to learn new domain..otherwise if becoming monotonous and want to move to new area. (like sales domain report for Chip manufactuers may contain demand planning etc…)
1:30-2:00 document the new reports to be worked on today.
2:00-2:30 Lunch
2:30-3:30 Look at LLD and HLD of new reports. find sources if they exist otherwise Semantic layer needs to modified.
3:30-4:00 co-ordinate with other resource reports requirement with Architect to modify semantic layer, and other reporting requirements.
4:00-5:00 Develop\code reports, conditional formatting,set scheduling option, verify data set.
5:00-5:30 Look at old defects rectify issues.(if there is separate team for defect handling then devote time on report development).
5:30-6:00 attend defect management call and present defect resolved pending issue with Testing team.
6:00-6:30 document the work done. And status of work assigned.
6:30-7:30 Look at report pending issues. Code or research work around.
7:30-8:00 report optimisation/research.
8:00=8:30 Dinner return back home.
Ofcourse has to look at bigger picture hence need to see what reports other worked on.
Then Also needed to understand ETL design , design rules/transformations used for the project. try to develop frameworks and generic report/code which can be reused.
Look at integration of these reports to ERP (SAP,peopesoft,oracle apps etc ), CMS (joomla, sharepoint), scheduling options, Cloud enablement, Ajax-fying reports web interfaces using third party library or report SDK, integration to web portals, portal creation for reports.
So these task do take time as and when they arrive.

Telecom Technology Stack

For Enterprise class large projects Architecture frameworks like TOGAF are very important:
Read
TOGAF: The Open Group Architecture Framework was adopted and adapted to E-TOM framework or Enhanced Telecom Operational Map (E-TOM) .
E-TOM has two essential layers which cover most requirement on Telcos
{Telecom companies include (TEM) Telecom Equipment manufacturer like (ZTE, Cisco Ericsson  , Telecom Services companies like ( vodaphone, O2 etc)}.
1. Lowest Level 1: OSS (Operational System Software) which include systems which interfaces with most devices like routers, base station, towers, etc Cisco routers, Base station BTE software, NOS (network operation planning software), Activation Software, 2G, 3G stack management, tower management.
2. Upper layer: BSS (Business System Software) Which includes Business Interfacing software like Oracle Sieble CRM (Customer Relationship management ), Billing software like from Amdocs,or oracle BRMS (Billing and revenue management  software)
MIS and BI Business Intelligence software like OBIEE, SAP BO, Cognos BI etc.
Mediation: Software mediating between multiple layers.
Activation:
Now lets see like BT working on E-TOM. For software implementations
British Telecom (BT) use agile methodology of keeping inventory of requirements as low as possible to keep cost down and know defects early in life cycle and then more requirements (User Stories) can be taken for development , taken to testing in SIT system integration testing and once tested OK dropped into production.
Scrum meetings are regularly held , as release happen the Burn down charts are updated telling progress status.

BT having incorporated concepts in between like
use RFT (Right First Time) 90 % of the project taken up must be completed in correct specifications in right time.
Concept to Market (C2M):Bring Concept to market faster.
Lead To Cash: (L2C)
where a lead generated to Cash in hand cycles are (Opportunity, Quotation, Order, Delivery, Issue, Invoice) L2C cycles are captured in workflow and quickened.
SAP Order Management Of Lead to Cash workflow
SAP Order Management L2CWatch Demo of SAP Lead to Cash using SAP Business By Design.
http://www.youtube.com/watch?v=uXsY_cpr5f0

3. Trouble to Resolve (T2R). : where Each Trouble which needs resolution is trapped in CRM for reviewing the work.
4. Cycle time: Each Cycle must be pro-actively reduced in time frame.
You can Read this more detailed matrix Architecture Overview of Vision goals
http://www.btplc.com/innovation/journal/BTTJ/current/HTMLArticles/Volume26/08Matrix/Default.aspx

Read about TOGAF:
1. Comparison of Enterprise Architecture to Domain specific Architecture Roles :
https://sandyclassic.wordpress.com/2011/09/25/enterprise-architecture-togafitilzachmanetomngoss/
2. Enterprise Architecture and Security.
https://sandyclassic.wordpress.com/2013/02/28/498/
3. Links:
Oracle Seibel:
http://www.oracle.com/us/products/applications/siebel/overview/index.html
Oracle BRMS:http://www.oracle.com/us/corporate/press/2021078
Amdocs Billing software of the year:
http://www.amdocs.com/News/Pages/Amdocs-Receives-Most-Advanced-Billing-Software-of-the-Year-Award.aspx

 

 

Architecture Difference between SAP Business Objects and IBM Cognos part1

Lets understand how Cognos product works internally

Most of BI product Architecture are almost similar internally.
BI Bus: Enterprise service Bus which surrounds all the services/servers which tool provide.
Typical ESB from Oracle BEA Aqualogic Stack engulfing many Web services looks like:
ESB_archNow you can compare this popular ESB with BI internal Architecture.
you can read more about ESB at : http://docs.oracle.com/cd/E13171_01/alsb/docs20/concepts/overview.html
Under 4 tier system: A client connects the Web server  (which is protected by firewall) using dispatcher. Dispatcher connects to Enterprise Service Bus (ESB) which surrounds all the application server services (Web services). ESB in case of cognos is Cognos BI Bus surrounds Web services Servers (like Report Server, Job server, Content Management server etc ). Mediation Layer Cognos BI Bus interacts with Non Java , C++ code which could not to converted or purposefully kept in C++ for may be more flexibility and speed
Cognos BI Bushttp://pic.dhe.ibm.com/infocenter/cbi/v10r1m1/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.crn_arch.10.1.1.doc%2Fc_arch_themulti-tierarchitecture.html

In case of SAP Business Objects (BO) ESB was not properly developed so an intermediate layer was created which works for interfacing between multiple servers like Job server, report server, page server etc. BO XI R2 came in pervius version was more in C++ to C++ to java bridge was created in ESB layer. Since Java was preferred language for coarse grain interoperability  provided by web services. Each server was developed using web services.
interaction between web server was routed through BI Bus.
BO-xi-r3.1-infrastructureIn latest version here u find a pipe connecting all components call Business Objects XI 3.1 Enterprise Infrastructure. Earlier version had different names. here you can see its connecting all server like Crystal report server, IFRS input file repository server( storing template of reports), OFRS Output file repository services, Program Job server(storing all programs which can be published on Portal (Infoview) ). This ESB does mediation between different server and achieves interoperability yet control of different components of products. This is in competitor product Cognos is called Cognos BI Bus.
http://bobi.blog.com/2013/06/02/sap-business-object-architecture-overview-and-comparatice-analysis/
For latest BO uses in memory product SAP HANA more about its competitors follow:
https://sandyclassic.wordpress.com/2011/11/04/architecture-and-sap-hana-vs-oracle-exadata-competitive-analysis/

In Micro-strategy there are two important server Intelligent server which creates cubes

More I will cover in later issues:
Oracle BI Architecture:
http://www.rittmanmead.com/2008/02/towards-a-future-oracle-bi-architecture/

Implementation OF BI system is not related to these product Architecture :
A  typical BI system under implementation haveing componets of ETL, BI, databases, Web server, app server, production server, test/development server looks like:
typical BI ArchtectureMore details: http://www.ibm.com/developerworks/patterns/bi/product-s390-web.html
Big Data Architecture:
From components perspective of ETL to BI implementation Aspect is little different
bigdata-scalein-architecture

Hadoop Architecture layers:
hadoop-architecturehttps://sandyclassic.wordpress.com/2011/10/19/hadoop-its-relation-to-new-architecture-enterprise-datawarehouse/
http://codemphasis.wordpress.com/2012/08/13/big-data-parallelism-and-hadoopbasics/

Just like UDDI registry is repository of Web