What is the significance of ODS in BIW?

What is the significance of ODS in BIW?

An ODS Object serves to store consolidated and debugged transaction data on a document level (atomic level). It describes a consolidated dataset from one or more InfoSources. This dataset can be analyzed with a BEx Query or InfoSet Query. The data of an ODS Object can be updated with a delta update into InfoCubes and/or other ODS Objects in the same system or across systems. In contrast to multi-dimensional data storage with InfoCubes, the data in ODS Objects is stored in transparent, flat database tables.

What is Bex?

Bex stands for Business Explorer. Bex enables end user to locate reports, view reports, analyze information and can execute queries. The queries in workbook can be saved to there respective roles in the Bex browser. Bex has the following components: Bex Browser, Bex analyzer, Bex Map, Bex Web

Define Meta data, Master data and Transaction data ?

Meta Data: Data that describes the structure of data or MetaObjects is called Metadata. In other words data about data is known as Meta Data. Master Data:

Master data is data that remains unchanged over a long period of time. It contains information that is always needed in the same way. Characteristics can bear master data in BW. With master data you are dealing with attributes, texts or hierarchies.

Transaction data: Data relating to the day-to-day transactions is the Transaction data.

BW over R/3? Would it be sufficient just to Web-enable R/3 Reports?

Performance – Heavy reporting along with regular OLTP transactions can produce a lot of load both on the R/3 and the database (cpu, memory, disks, etc). Just take a look at the load put on your system during a month end, quarter end, or year-end – now imagine that occurring even more frequently. Data analysis – BW uses a Data Warehouse and OLAP concepts for storing and analyzing data, where R/3 was designed for transaction processing. With a lot of work you can get the same analysis out of R/3 but most likely would be easier from a BW.

What is ERP?

ERP is a package with the techniques and concepts for the integrated management of business as a whole, for effective use of management resources, to improve the efficiency of an enterprise. Initially, ERP was targeted for manufacturing industry mainly for planning and managing core business like production and financial market. As the growth and merits of ERP package ERP software is designed for basic process of a company from manufacturing to small shops with a target of integrating information across the company.

Administration

AL11 Display SAP Directories

BD54 Maintain Logical Systems

OSS1 Logon to Online Service System

SALE IMG Application Link Enabling

SARA Archive Management

SCC3 Copy Analysis Log

SCC4 Client Administration

SCC5 Client Delete

SCC7 Client Import Post-Processing

SCC8 Client Export

SCC9 Remote client copy

SCCL Local Client Copy

SCU0 Customizing Cross-System Viewer

SICK Installation Check

SM01 Lock Transactions

SM02 System Messages

SM04 User Overview

SM12 Display and Delete Locks

SM13 Display Update Records

SM14 Update Program Administration

SM21 System Log

SM35 Batch Input Monitoring

SM50 Work Process Overview

SM51 List of SAP Servers

SM56 Number Range Buffer

SM58 Asynchronous RFC Error Log

SM59 RFC Destinations (Display/Maintain)

SM66 System Wide Work Process Overview

SAINT SAP Add-on Installation Tool

SPAM SAP Patch Manager (SPAM)

SPAU Display modified DE objects

SPDD Display modified DDIC objects

ST11 Display Developer Traces

ST22 ABAP/4 Runtime Error Analysis

SU56 Analyze User Buffer Alert Monitoring

AL01 SAP Alert Monitor

AL02 Database alert monitor

AL04 Monitor call distribution

AL05 Monitor current workload

AL16 Local Alert Monitor for Operat.Syst.

AL18 Local File System Monitor

RZ20 CCMS Monitoring Configuration FILE Cross-Client File Names/Paths

RZ04 Maintain Operation Modes and Instances

RZ10 Maintenance of Profile Parameters

RZ11 Profile parameter maintenance

SE93 Maintain Transaction Codes

SM63 Display/Maintain Operating Mode Sets

SPRO Customizing: Initial Screen

SWU3 Consistency check: Customizing Database Administration

DB01 Analyze exclusive lockwaits

DB02 Analyze tables and indexes

DB12 DB Backup Monitor DB13 DBA Planning Calendar

DB15 Data Archiving: Database Tables Jobs

SM36 Define Background Job

SM37 Background Job Overview

SM39 Job Analysis

SM49 Execute External OS commands

SM62 Maintain Events

SM64 Release of an Event

SM65 Background Processing Analysis Tool

SM69 Maintain External OS Commands Monitoring

AL08 Current Active Users

OS01 LAN check with ping

RZ01 Job Scheduling Monitor

RZ03 Presentation, Control SAP Instances

ST01 System Trace

ST02 Setups/Tune Buffers

ST04 Select DB activities

ST05 Performance trace

ST06 Operating System Monitor

ST10 Table call statistics

ST03 Performance, SAP Statistics, Workload

ST07 Application monitor

STAT Local transaction statistics

STUN Performance Monitoring (not available in R/3 4.6x)

Points to consider when Sizing

This sizing questionnaire is designed to collect enough information to allow us to configure and characterize an appropriate SAP Business Information Warehouse (SAP BW) landscape.

1. Customer Information-This includes customer contact information, in case the sizing engineer needs further input to process the sizing. Here we also ask about the number, version and software of OLTP source systems as well as certain operational issues important to the overall system design.

2. Landscape Configuration
     and  DW Design Planning-This section covers all information around the planned system and DW landscape as well as the Data Model design.

3. User Activity and Workload-There are three basic components to size for a SAP BW system:  number of users/processes, query mix and quantity of data stored in the DW.  This section will gather the information necessary to perform this process.

4. Data Quantity-In this section we ask for the amount of data you have planned to store in your DW and the data model you have planned to use.

5. Technical Requirements-Here we gather information regarding certain technical requirements, such as clustering or backup technology, that may influence the sizing of the system.

Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded to the BW System. Then, the LUWs of the previous delta may be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change when the first delta was loaded to the BW System