Reporting Strategies in SAP BW

7/27/2019 Reporting Strategies in SAP BW

http://slidepdf.com/reader/full/reporting-strategies-in-sap-bw 1/49

ReportingStrategies inSAP BW

Paula GistNetWeaver RIG,SAP Labs, LLCOctober 16, 2003



SAP AG 2002, Title of Presentation, Speaker Name 2

Reporting Strategies - Overview

Purpose

To discuss decision points and methodologies when defining thesource, purpose, frequency, availability, dissemination,standardization and user base of information managed in the SAPBW system.

The SAP Business Information Warehouse (SAP BW) should:

Support Decisions at all Levels of User

Be scalable

Be a comprehensive Toolset

Have fast deployment

Have the ability to be accessed anywhere




SAP NetWeaver and Business Intelligence -Information Integration

SAP NetWeaver delivers complete business integration

at all levels

Information Integration makes both structured andunstructured information available in the enterprise in aconsistent and accessible manner:Users demand ubiquitous access to information wherever itresides. That information must be served in a consistentmanner and its integrity guaranteed.

Knowledge management with user-centric servicesprovides a single access point to SAP's content management

system and third-party repositories -- with integrated search,taxonomy, classification, content management, publishing,

and related workflow processes.

Business intelligence -- This capabilityenables you to integrate, analyze, anddisseminate relevant and timely information. It isdelivered through SAP Business Intelligence,which provides a robust suite of businessintelligence tools to help you create and deploycustomized, interactive reports and applications,

supporting decisions at every level.

Master data management -- This capability promotes informationintegrity across a business network in a heterogeneous ITenvironment. It enables the sharing of harmonized master dataformerly trapped in multiple systems and ensures cross-system dataconsistency -- regardless of system location or vendor. Thiscapability is delivered through SAP Master Data Management.




SAP NetWeaver and Business Intelligence -Information Integration

Business Intell igence with SAP NetWeaver

One of the core components of SAP NetWeaver is SAP Business Information Warehouse (SAP BW),which covers the following functional areas:

Data warehousing, which forms the application-neutral foundation for Business Intelligence. SAPBW supports the complete data warehousing process, from data integration, data transformation,consolidation and cleansing to data provision for analysis.

A business intelligence platform that serves as the technological infrastructure to support

information access and comprehensive analytics.

Business intelligence suite that transforms data into insightful information and serves a widevariety of users for decision-making.

As part of the SAP NetWeaver architecture, SAP BW draws from and utilizes the capabilities of theother components for business intelligence usage. The sum of the functionality of SAP BW and thecontribution of other components of SAP NetWeaver form a BI platform that represents the next majorstep in the evolution of business intelligence.

SAP NetWeaver is the technical foundation for all SAP applications as well as partners' products and

solutions. With Analytical Applications that run on top of SAP NetWeaver and business content thatgoes across all functional areas of SAP BW, SAP offers a comprehensive solution: mySAP BusinessIntelligence.

For more information on SAP NetWeaver and Busi ness Intelligence go to sdn.sap.com




Reporting Strategies -

What the Experts say…………..

Bill Inmon: “When organizations discover the data warehouse, in many cases theythink they have found the answer to their prayers when it comes to getting at corporateinformation. A first reaction of many organizations first discovering the data warehouseis the thought that any and all reporting should be done from the data warehouse.Built properly, data warehouses unleash information into the corporation as neverbefore. The fact is that there are different kinds of reports and that - as useful as the

data warehouse is - not all types of reporting should come from the datawarehouse.” (1)

Methodology,Strategy,Decisions





What the Others say…………..

John Ladley: “We know our information is valuable, but how do we measure it?”

Many organizations want to know how to present the potential value of information andknowledge to upper management. They need to do this proactively, …….”(2)

John L. Doran: “Business intelligence is more than just a reporting environment;preparing and planning for more skillful ways to leverage data is essential for asuccessful business intelligence environment. Providing frameworks that supportactionable decision making will provide the right ingredients for success.”(3)

Value,Action,

Success





What the Customers say…………..

Can I do this?: How do we reduce the number of reports from over 5000 tosomething more manageable?

Who should do this?: How do we help users get the information they need withoutevery one being a super user?

How should I this?: We need all of our source data in the BW, Is this OK?

How should I present this?: I need information accessible out in the field, will Webreports give me what I want?

Tell me what I shouldbe doing!, What is

the best way to buildreports?




Reporting Strategies - Definition

What is a “ Reporting Strategy” ?

Reporting: The act of returning or presenting information with conclusions orrecommendations. The dissemination of Information to achieve some stated goal,answer questions or meet predefined requirement for the reader or information user.

Strategy: A careful plan. The logical, purposeful methodology to achieve some statedgoal or end.

Reporting Strategy (SAP BW): The decisions agreed to and implemented within anorganization, entity or unit to gather, validate, store and disseminate information tovarious users based on a set of predefined requirements.

A Reporting Strategy should answer:

How to support decisions at all levels of user.

Define tool sets that support the required reports.

How to make the organization ready for the information available.

Help users decide on integration with or replacement of 3rd party datawarehousing tools.




Reporting Strategies - Observations

Observations

The reporting of information stored in the BW is sometimes managed as just areplication of existing legacy reporting requirements. There is too often amisconception or lack of understanding of the performance improvements, dataflexibility, measurement capability and hardware implications behind simply replicatingexisting reports in an OLAP system.

The following discussions should be a starting point to examine effective processes todetermine the “ RIGHT INFORMATION, AT THE RIGHT TIME, TO

THE RIGHT PERSON, FOR THE RIGHT DECISIONS”

The discussion will follow those 4 categories

1. The Right Information

2. At the Right Time

3. To the Right Person

4. For the Right Decisions




Reporting Strategies – Sample Scenarios

Strategy A

Replicate All Current Existing Reporting In the BWEnvironment

Scenario: There are minimal available resources to gather requirements for reporting tobe delivered in the BW environment, Can we just replicate what we already have and

evaluate it later after we have the BW live and in production?Diagnosis: No time for requirements gathering. The shortest route to reporting is OK.

Things to consider : The existing reporting may no longer be what is truly needed. There will be more information available that could not be efficiently reported on before.Has the source system for data changed (say a new SAP R/3 implementation)?

Will the end user base and process business owners find value inreplicating existing reporting or are they looking for differentinformation now?

Is there new information available?

NO

YESDECISION

POINT





Strategy B

Use SAP R/3 BW delivered content for all reporting.

Scenario: There is a need for BW functionality but not enough knowledge to create anBW report. Can we just take what was delivered and make our business users use that?We can see if they like it and change.

Diagnosis: No time for requirements gathering. No knowledge on how. The shortestroute to reporting is OK.

Things to consider : The existing reporting may no longer be what is truly needed. Therewill be more information available that could not be efficiently reported on before. Has thesource system for data changed (say a new SAP R/3 implementation)?

Will the end user base and process business owners find value in thestandard delivered reporting?

NO

YESDECISION

POINT





Strategy C

Define all requirements during the planning phase of the BWimplementation

Scenario: SAP BW is chosen as the Enterprise Wide Business Intelligence informationtool. SAP ASAP for BW is the project implementation methodology. ASAP requires thatthe reporting requirements are documented as part of the planning phase.

Diagnosis: Using ASAP accelerators for how to gather and document requirements andsuggestions on who should participate makes the process flow smoother.

Things to consider : Using predetermine accelerators and resourcing suggestions is agreat starting point. If there are other issues/concerns that are not addressed in hismethodology, enhancements can certainly be made to fit your particular business needs.

Is there experienced resources, internal and external, available to determinerequirements? Is there time to determine all requirements?

NO

YESDECISION

POINT





Strategy D

Use SAP R/3 BW delivered content where it is feasible, definegaps and create custom reporting.

Scenario: SAP BW is chosen as the Enterprise-Wide Business Intelligence informationtool. SAP ASAP for BW is the project implementation methodology and the businesscontent delivered with the BW will be activated and delivered as the Phase I deliverable. The reporting requirements have been documented but there are some additional objectsthat you would like see in your reports.

Diagnosis: Gap analysis will determine if the business content will be sufficient to insurethat your requirements will be met for your deliverables.

Things to consider : If the enhancements to delivered business content are minimal, thisshould easily fit into your timeline. If the enhancements are so many that the content isnot really meeting any of your requirements and must be created by you, timeline issuesand available resources must be taken into consideration.

Is there experience available to perform Gap Analysis?

NO

YESDECISION

POINT




Reporting Strategies – The Right Information

Source

SAP/R3

Legacy System

External Data

Other Sources





Source

SAP/R3 Legacy System

External Data

Other Sources

The source of the information has important implications for reporting. While the SAP BWcan import data from various Non-SAP systems, the SAP R/3 product suite has extractorsdelivered with business content and information can be easily selected, extracted,transformed and loaded in the SAP BW with minimal extra effort (dependent on individualdata design).

One important consideration in any reporting decision will be if complex extractioncoding has to be created, tested and maintained, does the cost of this effort outweigh

the benefit o f the in formation itself?

NO

YESDECISION

POINT





Source

SAP/R3

Legacy System

External Data

Other Sources

Information loaded via Flat Files and ETL tools are delivered functionality in SAP BW.Extra effort in configuration may be required. Ascential DataStage is certified ETL tool.

Is the Legacy Data easily accessible? Is the data easily mapped to SAP BW fieldrequirements? Is the data clean or will extensive transformations need to be

considered? Is there already an ETL tool available or will one have to be secured?

NO

YESDECISION

POINT





Source

SAP/R3 Legacy System

External Data

Other Sources

Information such as The Group Gartner industry survey data or Dunn and Bradstreet canbe loaded into SAP BW. Also Data Mining functionality and tools are available through3rd party vendors such as TeaLeaf.

Is the External Data easily accessible? Is the data easily mapped to SAP BW fieldrequirements? Is the data clean or will extensive transformations need to beconsidered? Will an Data Mining too l have to be secured?

NO

YESDECISION

POINT





Source

SAP/R3

Legacy System

External Data

Other Sources

Are there other sources of data needed?

NO

YESDECISION

POINT





Need or Requirement for Information

Based on Information Availability Based on Existing Reports

Based on Corporate Benchmarks

Based on Regulatory Requirements

What the others say:John L. Doran, DM Review:

“Business stakeholders must move beyond simple report generation and

toward identifying valuable unknowns, drawing conclusions and optimizingresults that lead to action. These are the true drivers behind businessintelligence investments. “ (3)

…data visibili ty …

Provides greater insight for

decision making…

John Doran






Based on Information Availability

Based on Existing Reports



The availability of information is a key step to reporting on the information. This mayseem a elementary concept but imagine if you are using SAP R/3 as the source of thedata and not all components are implemented. Or better still the information is no longercreated but there is some requirement for usage of the data. Now what can be done ?Also consideration needs to be given to the level of detail needed and/or available. Insome cases summarized data is not sufficient for the active information consumer anddetail data is not needed for the C-Level executive analyzing benchmark reporting once a

month. A validation and review of requirements is essential for proper requirementsgathering.

Is the required information available? What system is the information available in?

Is this information requirement currently valid? How Granular is the information

required to be? To the line items level or can it be summarized?

NO

YESDECISION

POINT






Based on Information Availability

Based on Existing Reports



Using existing reporting for requirements gathering is a good starting point for discussion,

but should not be the end goal for deliverables. Timing and resource restrictions cansometimes put the utilization towards the data modeling deliverable and away from thereporting deliverable. There is value in making these parallel activities (at least inblueprinting) so that data model decisions are validated with current requirements andcurrent requirements are validated for appropriateness.

There most likely were limitations to the current reporting capabilities that the OLAPenvironment can resolve with the functionality delivered in the BW (ex – filtering verseshard coding data selections and formulas that transform results at the time of queryexecution).

Are the exist ing reporting requi rements useful as a s tar ti ng point for requirements

gathering Can It be determined what transformations to data was done? Can the

number of reports be consolidated ad the slice and dice functionality fulfill the

different view required?NO

YESDECISION

POINT









C-Level executives often are mandated to present information in scorecards or to report

on benchmarks as set forth by the executive board. These initiatives need to bedeveloped along with the strategic and tactical reporting requirements to insure theappropriate data design is implemented. The use of cockpits, delivered and custom isimportant in satisfying the high level information user.

Are there corporate ini tiatives that require Benchmarks, scorecards or

cockpits?

NO

YESDECISION

POINT









Regulated industries such as Utilities, Federal Agencies, and FinancialInstitutions often require that formatted reporting be used. The location of certain information must be exactly the same each time the data is refreshed apresented. Formatted reporting tools, like certified 3rd party supplier CrystalReports, can fulfill this requirement..

Are there requirements for formatted r eport ing?

Is the appropriate 3rd party too l available or need to be secured?

NO

YESDECISION

POINT




Reporting Strategies – The Right Time

Avai lability

When is the required information available? How difficult is it to Extract and Load?





Avai lability


The requirement for data is dependent on when the information required is made availablefor extraction in whichever system the information is created in. Global Operations that

have a 24/7 production environment sometimes pose a tight window to extract data.Functionality for real time data extraction being delivered in our future release may satisfythis requirement. Batch reporting for large processes (POS, MRP) can demanddedicated processing windows and leave tight timeframes to create data and post datathat is to be extracted.

When is data available and how widei s the window for extraction? Are

there any hindrances to the availability of the data? SAP system such as

APO, SEM CRM?

NO

YESDECISION

POINT





Avai lability


The SAP BW delivers extractors for R/3 in business content. Custom extractors can be

very complex and have challenges with the ability to capture delta information. Datadependencies, master data and transaction, sometimes require complex scheduling toinsure integrity of extracted data, Process Chains, 3rd party scheduling tools help toinsure dependencies are met.

What are the dependencies of the data being extracted?

Are there impacts to the availabi li ty of the data.?

NO

YESDECISION

POINT





Frequency

How often is information to be added, refreshed or changed?

When is window of opportunity to extract?





Frequency

How often is information to be added, refreshed or changed? When is window of opportunity to extract?

The update of data is dependent on the intended use of the BW. Active users will most

likely use the data on a frequent even daily bases (and even through out the day if

possible), Analysts will use the data overtime (say weekly) to determine trends andperform other analysis and the C-level executive are probably infrequent users that wantexception reporting and to be prepared to report on responsibility center results after a

periodic financial closing.

How often does the data need to be updated? For Whom?

NO

YESDECISION

POINT





Frequency How often is information to be added, refreshed or changed?

When is window of opportunity to extract?

The BW most often is updated in off production hours or quiet times. As stated before the

type operation (global, 24/7, heavy usage of batch processing) and the processorcapability can determine the frequency of data updates. In some instances the BW mustbe available at certain times (say 8:00 am each morning) thus making daily updatesoccur on a very tight schedule.

What is the data volume expected? How much time for update available?

When can data updates begin? When do they have to end?

NO

YESDECISION

POINT




Reporting Strategies – To the Right Person

Level/Type of User

Who are the users?

How active will user be with information?

What is the security level for data access?





Level/Type of User Who are the users?



Users can be defined as

Authors and Analysts

Executives and Knowledge Workers

Information Consumers.

Has a survey of users been done?

How many users are in each category?

How many users in total?

NO

YESDECISION

POINT





Level/Type of User

Who are the users? How active will user be with information?

What is the security level of data access?

Authors and Analysts - create reports and use information actively but maybe not on adaily bases. They need data that provides insight into the business. They need advancedanalysis functionality and Ad Hoc Reporting capabilities. Can also includes the Project Team member, Power User and Ad Hoc user.

Executives and Knowledge Workers - use summary, high level, personalized data with theoption for in-depth analysis. Usage can be active but not necessarily daily. They needdata that is converted into information that is accessible in predefined analysis paths viaintuitive user interface.

Information Consumers - are probably the most active users. They will normally use thedata daily (or at least frequently). They need specific data that is often actionable, on a

timely bases. Includes End User.

Has a survey of users been done? How will users use the data provided?

NO

YESDECISION

POINT





Level/Type of User Who are the users?



Authorization profiles and roles have been delivered in business content. This can be

used with nor without further changes. Or, these can serve as a model for creatingcustom profiles and roles. Data can be secured at a very detail level (by field ortransaction) or at a very high level (wide open). Discussions on the sensitivity of the datamust conducted to determine appropriate security level. and decide Who has access toWhat. Please be cautioned that the lower the level of security the greater the effort tomaintain. Expensive overhead

Who can see What?

NO

YESDECISION

POINT




Reporting Strategies – For the Right Decisions

Report Dissemination

What state/format is information to be delivered?What tool/mechanism is information to be made available?

What the others say:

Mike Kelly, DM Review:

“ Where large numbers of users of different levels throughout the extended enterpriseneed not only Web reports, but also the ability to perform free- form analysis on thedata and reports they receive, analysis computation must be transferred to clientmachines. This forms the basis of data publishing architecture. “(4)

…information

consumers Can haveone click access to

web reports…Mike

Kelly





Report Dissemination What state/format is information to be delivered?

What tool/mechanism is information to be made available?

On demand query execution provides the user with the ability to dynamically retrieve themost current information made available from the Info Provider. This enable highlyinteractive results analysis.

Static information is managed information. It is normally recalculated and pushed out to adelivery point.

How is the data to be delivered?

NO

YESDECISION

POINT





Report Dissemination

What state/format is information to be delivered?

What tool/mechanism is information to be made available?

Web reporting is the future and the future is now. Data access can be Web based and

access through the browser and/or the SAP Enterprise Portal. BEx reports use Windowsbased components and require SAPGui for delivery. SAP BW delivers a comprehensive

toolset for query design, reporting and analysis.

Decisions on desktop and browser standards play a part in any discussion on DataDelivery and Access. Mobile devices should also be discussed. 3rd party delivery toolsand software must be considered if it is part of the Corporate Information ManagementStrategy.

What Data access tool or mechanism will be used? Is there a corporate

standard for data delivery?

NO

YESDECISION

POINT





Strategic vs. Tactical Is information Analytical in Nature?

Is information Operational in Nature? Is summary or detail data appropriate?

What the experts say:Bill Inmon: “ FORCING THE ISSUE

There is an interesting question that follows from the observation that operational reporting

is very different from informational reporting. That question is - what happens to the data

warehouse environment if you try to force ALL reports out of the data warehouse?

If the data warehouse architect ends up trying to force all reports out of the data warehouse,

the consequences are:

The data warehouse is FORCED to be designed to the lowest level of granularity of the corporation. This may or may not be an acceptable design constraint,

Updates will need to be done in the data warehouse. While this can usually be doneby the dams that manages the data warehouse, this in many ways runs contrary to theway that data warehouses are run,

The timing of adjustments and transactions being entered and reflected inside the datawarehouse becomes an issue, usually to the detriment of the other operationsoccurring inside the data warehouse. “ (1)

Is the report str ategic?

“ Just Because the

Data warehouse can

be forced to support

Operational reporting

Doesn’t mean it

ought to….” Bil l

Inmon





Strategic vs. Tactical

Is information Analytical in Nature? Is information Operational in Nature? Is summary or detail data appropriate?

Analytical Reporting will take information over time in comparison to some goal,

measurement or benchmark. This information is normally in summary format and isoften accompanied by charts and graphs. This information provides insight to theperformance of the entity.

Is the report strategic? Can summary data be used? Is the report reallyavailable on the transaction system or is a custom report required to becreated? Is the data required to be in real time?

NO

YESDECISION

POINT





Strategic vs. Tactical

Is information Analytical in Nature? Is information Operational in Nature?

Is summary or detail data appropriate?

Operational reporting will use detail data to show the results of current operations. This

is also transactional reporting. This information is usually required frequently (say daily).Performance improvement on the productive system is often the major reason fordeciding to store and report on transactional data in the BW. Cross application datamodels can be maintained with less manual report coding efforts than creating thesereports on the source. This information is actionable.

Is the report tactical ? Is detailed data required? Is the report currently

available on the transaction system? Is the data required to be real time?

NO

YESDECISION

POINT




Reporting Strategies - Sample Requirements Matrix withAdditional Considerations

Heavy inf ormation access isrequired in an OLTP system thatalready have performance issu ebased on post tuning

performance measurements

Performance issue in R/3 OLTP system

General rule of thumbData integration needed fr om

Cross Functi onal R/3,

New Dimension p roduct s, and

Non-R/3 system Environ ments

Frequency of use – low

Operational report available in

R/3 or legacy system DataIntegration from other system

not a requirement

Customization effort – high

Data unavailable in BW

customization required

Type report:

Operational

ex: payroll register.

Legal w/special format

List or Mailing Label

Data created/stored in R/3

Data integration fr om other sourc es

not required

BWLegacyR/3Decision PointCriteria

Matrix created by Amelia Lo, SAP Labs LLC




Reporting Strategies - Sample Requirements Matrix withAdditional Considerations

Customization effort – high

Extract loading time - long

Operational Window in R/3 or

Legacy systems are very narrow

Low volume and for analytical

– use remote cube a

possibili ty (be aware of

performance impact)

Up to th e minute info needed

General rule of thum bUp to th e minute info needed

Type report:

Operational

ex: payroll register.

Legal w/special format

List or Mailing Label

Data created/stored in R/3

Data integration fr om other sourc es

not required

BWLegacyR/3Decision PointCriteria

Matrix created by Amelia Lo, SAP Labs LLC




Reporting Strategies - Sample Reporting Tool Matrix

Matrix created by Bryan Katis, SAP Labs LLC

How to…ReportingAgent/BWOnlineDocumentation

WebApp./Work

TBDPrecalcDailyDetailDrilldown/Online

Volume (bycharacteristic

3


WebApp./Work

TBDPrecalcMthly/Qrtrly

SummaryDrilldown/Online


2


WebApp./Work

TBDPrecalcMthly/Qrtrly

SummaryStatic/Offline


1

References on

SAP Net

Report

TypeWork,WebApp.,InfoSet,R/3 Rpt,ABAPQuery

Reco

rds

Accessed

Precalcu

lation:O

LAPCache,RA,DwnloadSchedr,Wrkbks

Freque

ncy:

Daily/Wkly/Mthly/Qrtrly

Aggregat i

on:

Summary/Detail

Navigation:

Drilldown/

Static;Online/Offline

Report

Description/

ReportingCharacteristic






BW OnlineDocumentation- Classic InfoSet

ClassicInfo Set

TBDNoPrecalc

DailyDetailOnlineReporting onfield in a table

6

BW OnlineDocumentation

WebApp./Work

TBDNoPrecalc

Mthly/Qrtrly

DetailDrilldown/Online

Master Datareporting

5

R/3Report/ABAPQuery

TBDNoPrecalc

DailyDetailOnlineVolume (bycharacteristic

4

References on

SAP Net

Report

Type

Work,WebApp.,InfoSet,R/3 Rpt,ABAPQuery

Reco

rds

Accessed

Precalcu

lation:O


Freque

ncy:


Aggregat i

on:

Summary/Detail

Navigation:

Drilldown/


Report

Description/








WebApp./Portal

TBDNoPrecalc

DailyDetailDrilldown/Online

Reporting fromoff site locations

9


WebApp./Work

TBDPrecalcWeeklyDetailStatic/Offline

Evaluation of exceptions -based onweeklysummary ortrends

8


WebApp./Work


Evaluation of exceptions -based on dailydata

7

References on

SAP Net

Report

Type


Reco

rds

Accessed

Precalcu

lation:O


Freque

ncy:


Aggregat i

on:

Summary/Detail

Navigation:

Drilldown/


Report

Description/







How to…Create anInformationCockpit/BWOnlineDocumentation

WebApp./Portal

TBDPrecalcDailyDetailDrilldown/OnlineReports froman InformationCockpit

12

How to…ValidateInfoCube Databy comparingwith PSA Data

QueryusingRemoteCubeandMultiProvider

TBDNoPrecalc

WeeklyDetailDrilldown/Online

Data Validation- InfoCube toPSA

11


WebApp./Portal


Reporting fromintracompanynetwork

10

References on

SAP Net

Report

Type


Reco

rds

Accessed

Precalcu

lation:O


Freque

ncy:


Aggregat i

on:

Summary/Detail

Navigation:

Drilldown/


Report

Description/







CrystalDecisions

CrystalReports

TBDPrecalcDailyDetailOnlineRegulatedReports

16

CrystalDecisionsCrystalReports TBDPrecalcWkly/Mthly/Qrtrly

SummaryStatic/OfflineRegulatedReports15


WebApp./Work

TBDPrecalcWkly/Mthly/Qrtrly

SummaryDrilldown/Online

Data Validation- InfoCube toPSA

14


WebApp./Work

TBDPrecalcDailyDetailStatic/Offline

Static/Precaluated Data

13

References on

SAP Net

Report

Type


Reco

rds

Accessed

Precalcu

lation:O


Freque

ncy:


Aggregat i

on:

Summary/Detail

Navigation:

Drilldown/


Report

Description/





Reporting Strategies - Sample Decision Tree to BW or not to BW

Determine Reportin g

Requirements

Search Sourcesystem

For existing report

Does it exist

In source

system

Use Standard s ource

System Report

RequiresCurrent Days

Information

Reportin g Team toDevelop in source

system

Type of

Report

BEx Reportin g

with

SAPGui

Use Crystal

Reports on the BW

Custom Created

Report on BW

Review BW

Content

Transactional

Formatted Analytical

Operational/

Management

Reportin g Team

To develop in

source

system

Does it exist

In BW Business

ContentUse BW

Content

Determine BW

Report

Delivery StrategyWeb Based

Reporting with

WAS/Portal

NO YES

YES

YES

NO

NO




Reporting Strategies – Closing

Conclusion

The discussion on the proceeding pages should be considered a starting point for aworkshop or focus group to enable decisions on information that should be reported onfrom the BW environment to accomplish getting:

“ RIGHT INFORMATION, AT THE RIGHT TIME, TO THE RIGHT

PERSON, FOR THE RIGHT DECISIONS”




Reporting Strategies – Closing

References

1) OPERATIONAL AND INFORMATIONAL REPORTING

by W. H. Inmon, Bill Inmon Associates

2) Beyond the Data Warehouse: The Value of Information

By J ohn LadleyPublished in DM Review Online in May 2003 :

3) Business Intelligence Building Blo cks: Decision Frameworks

By J ohn L. DoranPublished in DM Review Online in June 2003

4) Data Publishing Architecture for the Extended EnterpriseByMike Kelly

Published in DM Direct in May 2003

“ RIGHT INFORMATION, AT THE RIGHT TIME, TO THE RIGHT PERSON,

FOR THE RIGHT DECISIONS”

Date post:	02-Apr-2018
Category:	Documents
Upload:	okrashid2001
View:	224 times
Download:	1 times

Reporting Strategies in SAP BW

Documents