• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/8

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

8 Cards in this Set

  • Front
  • Back
  • 3rd side (hint)
DataSource
Data is transferred into SAP BW in a flat structure, that is, a table, rather than a multidimensional
data structure. DataSources contain the definitions of source data.
Data is transferred into SAP BW in a flat structure,
PSA
Persistent Staging Area (PSA): In the SAP BW information model, data is physically stored in the PSA object, a transparent database table. A PSA is the initial storage area of data,
where requested data is saved unchanged from the source
system according to the structure defined in the DataSource.
InfoSource
InfoSource: InfoObjects that belong together logically
– from a business point of view – are grouped into Info-
Sources. InfoSources (and their underlying InfoObjects)
can be “filled” with any data from within the enterprise or
from external sources. (See “Extraction, Transformation, and
Loading (ETL)” below.) They can hold both transactional
data and master data. Transactional data is generated from
transactions in an Online Transaction Processing system
(OLTP), such as SAP R/3; it is “quantifiable;” and it can be granular. Master data, such as a customer address or an organizational structure, typically remains unchanged over a long period. Master data in SAP BW includes attributes, texts, and
hierarchies.
ODS object
SAP BW uses ODS object technology to build
the operational data store (ODS) layer and the data warehouse
layer. The ODS object describes a consolidated dataset
from one or several InfoSources. In contrast to the multidimensional
data models of InfoCubes, data in ODS objects
is stored in flat, transparent database tables. ODS object data
can be updated into InfoCubes or other ODS objects using a
delta update. Data in an ODS object can be analyzed with the
SAP BW Business Explorer (BEx) tool, the business intelligence
suite of mySAP BI.
InfoCubes
InfoCubes are containers that organize data around its
multidimensionality in terms of business dimensions. This
means that users can analyze information from various business
perspectives, such as geographic region or type of sales
channel. InfoCubes can be accessed by the SAP BW Business
Explorer for reporting and OLAP (Online Analytical Processing)
analysis. (See the “Multidimensional Models and
Aggregates” section below.)
ETL
In many companies, data is fragmented and spread across
dozens, if not hundreds, of databases and applications. Decision
makers need information to develop a comprehensive view of
the company and to answer key business questions accurately
and completely. To be useful, data must be integrated, standardized,
synchronized, and enriched. This is done through
processes known as extraction, transformation, and loading
Data Aging
The Strategy for Data Aging
In today’s business environment, a sound approach to data
warehousing must include a data-aging strategy. That’s increasingly
important because large amounts of data are generated
and used for everything from managing the supply chain to
managing customer relationships. Older data may be accessed
less frequently, but it is still useful. As a result, older data must
be stored and kept available, which can be an expensive undertaking
if traditional disk storage is used.
BAPI
Business Application Programming Interface (BAPI)
Standard R/3 interface that enables the integration of thirdparty
software into the R/3 System. BAPIs are defined in the
Business Object Repository (BOR) as methods applied to SAP
business objects, in order to perform specific business tasks.