cLIENT:

-------
000, 066 -> SAP Clients
100(Active Client) which is a copy of 000 [Client Copy]
for SAP BW we can only have one Active Client which is copy of 000.
[Refreshing Client]
In SAP BW we will have only Client Independent Tables?
?
-----------------------------------------------------------
but for SAP R/3, can have Multiple Active Clients which are a copy of 000.
?
In SAP R/3 we will have 2 types of Table -
1) Client dependent
2) Client Independent
===========================================================
COMPUTERS:
-------------
s/w AND h/w
-------------
s/w [software]
-----------------
- Set of Programmes is S/W.
- Set of Instructions is a Program.
- We can give instructions to the computer by using P.L(c, C++,Java,Cobol)
- Programming Languages:
------------------------
Ex :- C, C++, JAVA, COBOL, .nET, vb, vC++, pEARL,
WE USE p.l WE develope some Programes.
- DataBase:
-----------
Ex:- Oracle, SQl Server, Sybase,DB2, Ms access
- To Store the Data for future refernce or analysis.
- Operating System:-
--------------------
Ex:- Windows, Linux, Unix
- It acts an interface between user and the system.
- Packages:-
------------
Ex:- Tally, Ms Office
- It is a Software which is ready to use with out any customization.
- Aplications :-
----------------
Ex:- SAP BW
- It is a softeware which is customized as per the Client\User requirements.
Application :- PL + DB + OS + CONCEPT
-------------------------------------
PL - To Design the Front End and Application Logic
DB - To Design the Backend
OS - It acts an Interface
Concept - Billing of Super markets
2 types of Applications:-
------------------------
1) OLTP (Online Transaction Processing)
2) OLAP (Online Analytical Processing)
================================================
what do you mean by Business/Business Process/ System?
-----------------------------------------------------
- set of Business Activities / Transaction
----------------------------------
When 2 or more parties (Entities) interacting with each other, Perform a
Transactions like (Buying, Selling)
What do you mean by Business/Business Process/System ?
----------------------------------------------------
- Set of Business Activities / Transactions (S/B)?
-------------------------------------------------
- When 2 or more parties(Entity) interact with each in the Business
, They generate a Transaction.
--------------------------------------------------
- Entity?
Any object which can perform work by itself or which we can use it to p
erform some work.
---------------------------------------------------
" Exsitance of Entity is not the Business, These entities should interact with e
ach other to generate the transactions and set of these transactions is Business
"
- Master Data:- Detailed information about the Entities
- Transaction data:- Data Representing a Transaction
- Transaction Data is generated when ever we have a transaction perf
ormed in the business
- Product
----------
pno pname price pclr pmsr
------------------------------------
P1 BOOK 5 WHITE EA
P2 PEN 6 BLUE EA
- vendor
--------
VNO VNAME VADD
--------------------
V1 ABC HYD
V2 XYZ BAG
- Customer
-----------
CNO CNMAE CADD CSAL
----------------------------
C1 RAMU HYD 10000
C2 SATISH BAG 20000
- Shop Owner
------------
SNO SNMAE
---------------
S1 TRNETRASROSDNKJ
CNO PNO SNO P Q A
--------------------------------------------
C1 P1 S1 5 10 50
Entity: (Noun)
------
Any object which can perform work by itself or which we can use it to perform so
me work.
[* Existance of entity is not the Business, These entities should interact with
each other, to perform transactions and Set of the these Transactions is "Busine
ss" ]
Master Data:-
-------------
Detailed Information about an Entity (Stronger Entity or Attribute of Stronger E
ntity)
Transaction Data:-
------------------
Data representing particular Transaction.
OLTP:-
------
* Online Transaction Processing
* In OLTP applications, when ever we perform a transaction, we record the transa
ction into the Database and if there is a change in the transaction, we have to
change the transaction in the database. we can even select the transactions from
the database and show the same data as a Report.
* In OLTP applications, Transaction data is generated.
Ex:- Billing Application in Super market, SAP R/3, Railway Reservation Applicati
on, Banking Application, Hospital Management Application .
OLAP:-
-----
* Online Analytical Processing
* As part of OLAP tool, we extract all the Transaction data from different heter
togeneous OLTP sytems into OLAP and stag the Data and provide Analytical reports
(Analytical Data)
* Analytical Data - Data which can be used for analysis.
* TD + OLAP ==> AD
Ex:- SAP BW, Cognos
OLTP V/s OLAP or Why OLAP or Why SAP BW:-
---------------
1. When we do Reporting in OLTP it degrades the Performance of OLTP System, So w
e extract all the transaction data from different OLTP Systems and store data in
OLAP and provide Analytical Data.
2. In OLTP we dont store TD for Longer time, So in OLAP we store Historical Data
fro 5 - 10 Yrs.
3. In OLAP we can Integrate/Consolidate the data coming from different OLTP Syst
ems in OLAP.
4. In OLAP we can provide authorizations based on the Data, But in OLTP we provi
de authorizations based on the reports/Transactions. because of this if we do re
porting in OLTP system it affects ROI(Return on Investment).
5. In OLAP we can have more Analytical reports like one of the Top customer did
not buy one of your Top Product very easily.
****************************************************************
Basics of Database:
---------------------
* In any Database we store the data in a structure format called : Table.
* Table:-
--------
* Set of rows and coloumns.
* Coloumns are used to define the properties or attributes of an object or Entit
y.
* Coloumns will define the Logical Definetion of an Entity.
* Rows will define the physical existance of an entity.
* Each row in a table is also called as Record.
* Every table must have a Primary Key.
* We Use Primary Key to Uniquiely identify each and every record in a table.
* Every table will have 2 types of Coloumns
- Key Coloumn (Part of Primary Key)
- Non - Key Coloumn (Not part of Primary Key)
* All Non - Key Coloumns act as Attributes / Properties of a Key Colomn.
* Composite Key / Super Key:
-----------------------------
* When 2 or more coloumns of a table together act as the Primary key we call it
as Composite Key / Super Key.
* De-Normalized Table:
----------------------
When we store all the data in a single big table, and we find the data being sto
red redundently/Duplicatly,we call it as De-Normalized Table.
Dis - Advantages of De-Normalized Table:
----------------------------------------
1) Wasting Database Space
2) Complexity will be high.
To overcome with these problems we spilit the De-Normalized Tables into multiple
Smaller tables and these tables will be connected with the Primary Key and Fore
ign Key. The process of doing this we call it as "NORMALIZATION".
*Foreign Key:
-------------
* When a Primary of one Table takes part in the other table we call it as foreig
n Key.
****************************************************************
Data Warehousing:
-----------------
* W.H.Immon
* Data Warehousing is an Concept.
* extracting Data from different heterogeneous OLTP applications and store the d
ata and provide Analytical Reports for Decision Making Process.
- The data what we extract should have the following Proper
ties:
1. T - Time Variant
2. I - integrated
3. N - Non - Volatile
4. S - Subject Oriented
* Data Warehousing is a part of Business Intelligence.
Applications implementing the concept of DW:
--------------------------------------------
1) Cognos - R
2) Informatica - ETL tool (E)
3) Data Stag - M (Staging)
4) Oracle (EDW) - M (Staging)
5) Business Objects - R
6) SAP BW - is an End-to-End Data Warehousing Solution (E,M,R).
****************************************************************
Database Design in OLTP:-
-------------------------
* 2 dimensional
* Normalized
* Entity Relationship Model
---------------------------------------------
How to Design ER Model?
---------------------------------------------
Step 1:-
--------
Define the Business/Concept/Business Process/System:-
---------------------------------------------
"XYZ Co is supermarket with 200 employess, having branches in different location
s, we deal with different products,
we have lot of customers generating the bills in different branhces."
Step 2:-
--------
Identify the Entities in the Business:-
---------------------------------------
- By using Noun Phrase approach.
1) employess
2) branches
3) Products
4) Customer
5) Bills
Step 3:-
--------
Draw the Entity diagrams:-
-------------------------
Step 4:-
--------
Convert each entity diagram into a Table:-
------------------------------------------
Step 5:-
-------
Form the Intersection Entity/table:-
-----------------------------------
Step 6:-
-------
Normalize all the tables (Entity Tables and Intersection entity table ).
6.1) Indentify the K.c and N.K.c of a table.
6.2) Whether all N.K.c are dependent/related on the Primary Key or not.
* If N.K.C are not dependent on the Complete Primary Key then split the
N.K.C into other table and connect Primary Key and Foreign Key.
6.3) Understand the Relationship between N.K.c and K.c and draw the entity relat
ionship diagrams.
* if N.K.C is related to K.c as 1:M then split the N.K.C into other tabl
e and connect with Primary Key and Foreign Key.
* if N.K.C is related to K.c as 1:1 then store the N.K.C in the same tab
le.
* if N.K.C is related to K.c as M:M then split the N.K.C into other tabl
e and connect with Primary Key and Foreign Key.
---------------------------------------------
Points to be noted:-
--------------------
* Interscetion Entity:- Table which stores all the intersection data.
* Stronger Entity :- are those which are directly connected to the Intersection
Entity.
* Attributes of Stronger Entity:- Tables which are connected to the stronger ent
ity.
ER Model:-
---------
* Different entities(Tables) playing in the Business stored in different tables
connected with PK and FK.
* It will have Interscetion Entities, Stronger Entities,Attributes of Stronger E
ntities.
* ER model is Normalized.
****************************************************************
Star Schema:
--------------
----> Star schema is an MDM ( Multi Dimensional Model ) which contains Fact tab
le / Transaction data Table at the center,
surrounded by Dimension tables / Master Data Tables existing within
the Cube.
---->These Dimension Tables / Master Data Tables are linked to the Fact table /
Transaction data table with Primary Key Foreign Key Relationship.
Limitations of Star Schema:
------------------------------
1) Master Data is not Reused, So master data is maintained Redundantly.
2) Degraded performance.
3) Limited Analysis.
****************************************************************
Extended Star Schema:-
---------------------
* Star Schema + SID technology ( Surrogate ID).
* Fact table inside the cube connected to dimension tables and the dimension tab
les are connected to the SID tables which are connected to the Master data table
s.
* Master data tables are outside the info cube.
* Every master data table will have its own SID table.
* When we load the master data, the system would generate the SID's in the SID t
able.
* we have three types of master data : ATTR, TEXT, HIER.
* Max. no of dimesion tables : 16
* Max. no of keyfigures in the fact table : 233.
* Max. no of characteristics can be assigned to 1 dimension : 248.
* Fact table contains - Dimension ID's and Key figures.
* Any information which is stored as the attribute of another charcteristic will
always give the PRESENT TRUTH.
* Any information what is stored inside the cube or referenced to the fact table
will always give the : FACT.
* In order to design the optimized info cube we should always concentrate on red
ucing the dimension tables and at the same time reduce the number of records in
dimension table :-
STANDARDS:-
-----------
* If the master data tables are related as M:M, we assign them to different dime
nsion tables.
* If the master data tables are related as 1:M or 1 : 1, we should assign them t
o same dimension table.
- CS
------
- Programing Languages:
-------------------------------
? - ABAP/4
- Database:
-------------
? To Store Data
- OS:
-----
? Interface
- Packages:
--------------
? Ms office, Tally
- Applications:
-----------------
- SW install & Customize as per the USer requirements and use it.
- SAP BW
- Applications:
------------------
- OLTP
- OLAP
- Business / Business Process .....?
-----------------------------------------
- Set of Transactions / Busines activities ...?
------------------------------------------------------
- When 2 or parties / Entities ...? interact with each, they gen
erate a Transaction.
- Any Object which can peform work by itsekf or we use it to per
form some work, is an entity.
- OLTP:
---------
- To process all the transactions in the business.
- PL + DB + OS + Concept
- Data representing a Transaction - Transaction Data.
- Transcation data is generarted in OLTP applications.
- OLAP:
----------
- Online Analytical Processing.
- PL + DB + OS + Concept
- TD + Application --> AD
- SAP BW -- - PL + DB + OS + Concept
--- ABAP/4 + (Any Database) + Windows , Unix + Data Warehousing
- SAP BW:
------------
- Extraction
- Modelling
- Reporting
- Database Design in OLTP & SAP BW:
---------------------------------------------
- Basics of Database:
-------------------------
- Store data in for a Table. ...? (Set of Rows and Cloumns)
- cOLUMNS - lOGHICAL dEFINETIONS / PROPERTIES
- ROWS / RECORDS - Physical existance of an Entity.
- Every Table will have a Primary Key.
- Key Columns / Non- Key Columns
- All Non - Key columns will act as Attributes / properties of Key column.
- Composite Key - When 2 or more columns act as primary key in a table.
- Foreign Key:- When a Primat key of table takes part into ohter table, Foreign
KEy
- De-Normalized Tables: table where we have data redundency.
- Normalized Tables:- Tables wher there is no Redundency.
- Normalization: The process of converting De-Normalized tables into Normalized
tables .
- Database Design in OLTP:
--------------------------------
- Normalized
- 2 Dimensinal
- ER Model [Entity Relationship Model]
---------------------------------------------
- Identify the Entities and Undesatnd the Relationship between the entities. The
n based on this we decide about the No of Databse Tables and Relationship betwee
n these tables.
- Steps:
---------
1. Understand the Business Process / Business / Business Activities.
2. Define the Business
3. Indentify the Entities
- Noun Phrase Approach
- Customer
- Product
- Supplier
- Branch
- Sales Executives
- Bills or Bill Transaction
4. Entity Diagrams
5. Understand the Relationship between these entities.
1: m, M:m, 1:1
6. Convert each entity into one Table.
7. Creates a Join between these tables with P_key & F_key based on the Realtions
hip between entities.
- Types of Entities:
-----------------------
- Intersection Entity -
- Stronger Entity
- Attributes of Stronger Entity
- Database Design in OLAP:
---------------------------------
MDM:- Multi dimensional model.
* We can analyze data from multiple angles/dimensions by slicing and dicing the
Info Cube.
* De-Normalized
- MDM
-----------------------------------
- Star Schema (or) Traditional Star Schema
- Extended Star Schema (or) BW Star Schema
- Snow Flake
- Hybrid
- Star Schema:
------------------
-Fact Table/Transaction data table at the center surrounded by Dimension tables/
Master data tables connected with Primary Key - Foreign Key and all these tables
existing inside the cube.
* Fact Table?
-------------
* any data what is stored in this table cannot be changed.
* Transaction data Table ?
-------------------------
* We store Transaction data in this table.
* Master data Tables ?
----------------------
* These tables store Master data(Detailed information about an entity).
* Dimension Tables ?
---------------------
* Each Master data table is acting as a side of a cube.
* Transaction Data Table / Fact Table will have 2 types of Coloumns:-
a) Characteristics : on what basis we analyze a keyfigure.
b) Keyfigures : What we are Analyzing.
* Each Characteristics coloumn in the fact table/transaction data table will con
nect to one Dimension table/Master data Table.
- Extended Star Schema or BW Star Schema
----------------------------------------------------
- Star Schema + SID technology (Surrogate ID)
- Basic Data Model of Extended star schema:
-----------------------------------------------------
- Relation with the Tables:
-------------------------------
- Charecteristic & Key figures:
------------------------------------
- Key figures:- All Quntitative measures what we use to analyze the business sub
jects (KPI).
- Characteristics:- All Business subjects what we analyze.
- Master data tables and SID Tables:
-------------------------------------------
- 100
- '100'
* every characteristic will have an SID table
* When ever we load the master data, SID's are generated.
- Fact TAble and Dimension TAble:
-----------------------------------------
- Fact TAble:
---------------
- 255
- 6
--------
- 249
- 16
-------
233
- Dimension table:
-----------------------
- 255
- 6
--------
249
- 1
-------
248 - SID columns
- DIM ID's
-------------
- When we load transaction data to the Info Cube, DIM ID's are genersted based o
n the sid'S.
- CAn we load TD without MD?
-----------------------------------
Standard - Always load MD first and then load TD to improve loading performance.
- Standards to Design an Info Cube:
----------------------------------------
- 1. Whe we have 2 characteristcs related as M:M, we will have to assign to diff
erent dimensions.
- 2. Whe we have 2 characteristcs related as 1:M or 1:1, we will have to assign
to same dimension.
- 3. Modelling a Key figure:
--------------------------------
- If we Model the Keyfigure as an Attribute of a Characteristic - it gives Pres
ent Truth because the property of master data is Overwrite.
- If we Model the Key figure inside the Fact Table - it gives Fact, Beacuse the
property of Cube is Additive.
- 4. Modelling a Characteristic:
------------------------------------
- If we Model a Characteristic as an Attribute of another charecteristuic - it g
ives Present truth, because the property of Master data is Overwrite.
- If we Model a Characteristc by connecting the SID table to a Dimension Table -
It gives Fact, Beacuse the property of Info Cube is Additive.
Login Information:-
-------------------
Client:-
--------
* 000 and 066 - SAP Clients.
* Active client is created by using a client copy of 000.
* In SAP BW, we can only have one active client because of Client Independent ta
bles (Integration).
* 100, 076, 029, 222
Username:-
-----------
* Transaction Codes:-
----------------------
RSA1 - Administrator Workbench
Administrator Workbench
************************
- Command bar
-------------
- To Execute the T-codes
- RSA1 - Administrator Workbench
Adminstrator Workbench
----------------------
- Modelling
-----------
- We create the BW objects like (Info Area, Info Objects, Info Cube, Info Source
, ODS, Multi Provider, Info Set)
- We do perform procedures to load data into these objects.
- Monitoring
------------
- We monitor all the BW Objects
- we do even monitor the Loading Process
- Reporting Agent
------------------
- To Broadcast the Data
- Transport Connection
------------------------
- Landscape
- Documents
-----------
- BDS
- Business Content
------------------
- Standard Objects or Business Content Objects
- Any Object delivered by SAP
- Technical Name of the BC object will be prefixed with : 0
- Versions
-----------
N - new
A - active
M - Modified
D - Delivered
- All the BC objects will be in Delivered version, But if we need to use
the objects they sholud be available in Active version, So in the Business Cont
ent Tab - we install the Business content objects ( Creating a Copy of the Deliv
erd version objects into Active Version)
- Customized Objects
- Translation:
--------------
We use this tab to translate the objects from one Language to another Language
- When we translate an object only Description of an Object will change
but not the Technical Name
- Meta Data:
------------
- Data about Data
- Meta Data is Maintained in Meta Data Repository maintained by Meta Data Manage
r
- Modelling:
-------------
- T-code - RSA1
- Info Area:
--------------
- we use this to organise the project.
- similar to Folder in Windows
- Info Object Catalogs:
----------------------------
- we use this to organise the project based on the type of Info object.
INFO OBJECTS
------------
* Info Object is the basic unit to build any structure(Info Cube,ATTR table,Text
Table) in SAP BW.
* Info Object is Reusable to build any structure in SAP BW.
* Each Coloumn in a table in OLTP system is a Field.
* Each field in OLTP system will correspond to an Info Object in SAP BW.
Types of Info Objects:
----------------------
a) Characteristics
------------------
All Descriptive Data, which we use it to analyse the keyfigures.
Ex:- CNO,CREGION
B) Key Figures
---------------
ALL Quantitative measures, which we analyse
Ex- Price,Quantity,Revenue,Wages,Tax,Salaries,
c) Unit Characteristics
-----------------------
When we want Info Object to hold diff. Types of Currencies or diff. Types of Mea
sures(UOM).
* 2 Unit Characteristics given by SAP as part of Business Content - 0CURRENCY, 0
UNIT
* If you want to create an Unit Characteristics it should be created with refere
nce to either 0CURRENCY or 0UNIT.
d) Time Characteristics
-----------------------
When we want to store time factor information
ex:- date,month,week,year,year/month
* we cannot create Time Characteristics but we can only use the existing Time Ch
aracteristics delivered by SAP as part of Business Content.
Ex:- 0calday,0calmonth,0time
- Info Objects:
-----------------
- Characteristics - Business Subjects or Descriptive Matters
- Time Characteristics
- Unit Characteristics
- Key Figures - Measureble Data
- cHARARCTERISTIC:
---------------------------
/BIC/SZ_CNO
- /BIC,0/SXXXXXX
Z_CNO
- /BIC/SZ_CNO
- kEY FIGURE:
-----------------
- Unit Char:
----------------
- RSD1
RSD2
RSD3
RSD4
- Characteristic:
-------------------
- Data Element
-------------------
/BIC,0/OIXXXXXX
Z_MNO
/BIC/OIZ_MNO
- ALPHA - Conversion Routine
-------------------------------------
conversion_exit_xxxxx_input
conversion_exit_xxxxx_output
- sid tABLE:
--------------
/BIC,0/SXXXXXX
Z_MNO
/BIC/SZ_MNO
- Key Figures:
-----------------
Key Figure Info Object:-
-----------------------
1. Key figure with Fixed Currency or Fixed unit
2. Key figure with reference to Unit Characteristics(0currency, 0unit, etc..)
- Unit Charractreristic:
---------------------------
- 0UNIT
- 0CURRENCY
/BI0/SUNIT
- Time Characteristic:
-------------------------
- We can never create a Time Chracteristic
- RSD1
Creating Master Data Tables(ATTR/TEXT):-
---------------------------------------
Step 1:-
-------
Identify the no of Coloumns/Fields in the given Master data table in OLTP system
.
Step 2:-
--------
Out of the given fileds/coloumns, Identify what fields should be maintained in M
aster Data ATTR and what fileds should be maintaines Master data TEXT table.
Step 3:-
-------
Create the Info Objects for all the fields required by the Master Data - ATTR ta
ble.
Step 4:-
---------
Build the Master Data - ATTR table by using all these info objects ( YC_MATNO, Y
C_MATNM,YC_MATGRP,YK_MATPRC,YU_MATUOM).
Note :-
------
* we are supposed to build the Master Data - ATTR table for the info object corr
esponding to Primary Key field in the OLTP system.
* /BI(C/0)/PXXXXXX
Step 5:-
--------
Create the master data - Text table to store the S,M,L description.
Note :-
------
* /BI(C/0)/TXXXXXX
* Importance of Language key Field in Text Table:- If we want to maintain the de
scription in multiple languages, then we need to select the check box (Text lang
uage dependent) , then 'Langu key' field will be acting as part of primary key i
n the text table allowing us to maintain description in multiple languages.
* Creating Master Data Table ( ATTR, TExt, Hier ):-
---------------------------------------------------
Steps:
------
1. Indetify the Column - ATTR/Text(Segregate the Coloumns for ATTR / TEXT tables
)
2. List the fields to be maintained in ATTR table
- MATNO
- MNAME
- MPRC
- MCUR
- MUOM
3. CREATE THE INFOOBJECTS FOR EACH FIELD
- MATNO -- YZ_MATNO
- MNAME -- YZ_MNAME
- MPRC -- ZMPRC
- MCUR -- ZMCUR
- MUOM -- YUOM9
Using these info objects we have to build the attribute table for ZS_CNO.
4. Define the attribute infoobjects for YZ_MATNO
Naming Convention of ATTR table : /BI(C/0)/PXXXXXXX
5) Define the Text table for YZ_MATNO
Naming Convention of text table : /BI(C/0)/TXXXXXXX
YZ_MATNO - /BIC/TYZ_MATNO
/BIC/TYZ_MATNO
------------------------------------------------------
YZ_MATNO
- /BIC/PYZ_MATNO
- /BIC/TYZ_MATNO
- /BIC/SYZ_MATNO
t-CODE - SE11
- How to Create Master Data Text Table:
--------------------------------------------
zregion
- /BIC/SZREGION
- /BIC/TZREGION
SE11
ZREGION - /BIC/ZREGION
0CURRENCY -- CURRENCY
Maintaining Master Data:-
-------------------------
* eVERY TIME WE INSERT A RECORD INTO THE MASTER THE SYSTEM GENERATES AN SID IN T
HE SID TABLE.
* SID Number is generated from number range object for sid's.
* for changing the number range object of SID for any info Object - SNRO
- How to Create Master Data - Attr table
---------------------------------------------
MNO,MNAME,MGRP,MTYPE,MPRC,MUOM
-------------------------------------------
- Master Data Tables:
-----------------------
- Cno, Cname, Cadd, Cregion,Csal,S,M,L
---------------------------------------------
YPCNO
SID Table :- /BIC/SYPCNO
Text Table :- /BIC/TYPCNO
Attr Table :- /BIC/PYPCNO
- Loading Master Data ATTR and TEXT from Flat file:
---------------------------------------------------------
Pre-requisites:
----------------
- Source Data is available
- Target Objects
- Source System Connection - Flat file
- Pre-requisites:
-----------------
1. Check the Flat files are in (.csv/.ASCII)
2. attr TABLE AND TEXT TABLE SHOULD BE READY
3. Source System connection between Flat file and SAP BW
Types of SS
------------
1) SAP Automatic
2) SAP Manual
3) Myself(SAP BIW)
4) File System Inteface (Flat Files)
5) DB connect
6) External system using BAPI
7) UD connect (J2ee Applicaton Server)
- Flat file Source System Connection
-------------------------------------
It configures IDoc's (Intermediate Document)
- IDoc is the SAP standard for transfering the Data
- Data Idoc's ( used to carry the Data )
- Info IDoc's ( Used to carry the Information )
Steps:-
-------
1. Create the Application Component
2. Create the Info Source - Direct Update
- Info Source Defines Communication Structure
* Info Source will define Communication Structure.
* Communication Structure is specific to SAP BW.
* Communication Structure is grouping of logically related info objects indicati
ng in what (SEQUENCE) structure format the SAP BW takes in the data.
* Info Source will be of 2 types
a) Direct Update
b) Flexible Update
3) Create Source System connection between faltfile and SAP BW.
Types:-
-------
1) SAP Automatic - SAP
2) SAP MAnual - SAP
3) SAP BIW(Myself) - SAP BW to BW
4) Flat file Interface - Flat file
5) DB Connect - RDBMS ( oracle,sql server,msaccess,DB2
6) External System with BAPI - ETL Tools(Informatica,Tipco,Web
methodsd) (Hyperion)
BI 7.0
------
1) UD Connect:- runs with J2EE application and can be used to any database.
2) Web services:- To extract from XML files
* when we craete the SS connection the system will configure IDoc's.
* IDoc stands for Intermediate Douument and it is standard for transfering data
in SAP environment.
* 2 types of Idocs
a) Data idoc - used to transfer Data
b) Info Idoc - used to transfer information
4. Assign the Data Source to Info Source
- * Data Source will define Transfer structure and transfer rules
* Transfer structure is specific to source system.
* Transfer structure is grouping of fileds indicating in what structure format d
ata is coming from the SS.
* Mapping B/W Trnasfer Structure and Communication Structure - Trnafer Rules.
- 4 types of Data Sources:
--------------------------
- ATTR
- TEXT
- HIER
- TRANSACTION DATA
4. Create the Info Package and schedule the load
* Info package is specific to Data source
Note :- Every Data Source will have an Info Package
- How to Maintain the Data for Master Data ATTR - TEXT
---------------------------------------------------------------
- How to Install the Business Content Master Data Objects
---------------------------------------------------------------
- 0CUSTOMER
- /BI0/SCUSTOMER
/BI0/SCUSTOMER
SID is always a Numeric
SID will be generated from the "NUMBER RANGE OBJECT - FOR SID'S".
* How to change the Number range buffer for SID objects -- [ SNRO ]
-------------------------------------------------------
* How to Extract Master data (ATTR/ TEXT) from Flat files ?
-------------------------------------------------------
Pre-requsites :-
-----------------
1) Data Aqusition Layer / Source Systems :-
-----------------------------------------
- Create the Source system for Flat File
- It configures IDoc's.[ Intermediate Document ]
IDoc is the SAP standard for Transfering the Data.
- It Configures 2 types of IDoc's:-
1) DATA Idoc - Data
2) INFO Idoc - Information
2) Make the Flat file Ready.
----------------------------
Note :- SAP BW will accept only 2 types of Files
1) CSV ( Comma Seperated Values )
2) ASCII ( File with ASCII code )
Steps:-
-------
1. Create Application Component
2. Create the Info Source.
- Communication Structure
- 2 types of Info Sources
a) Direct Update
b) Flexible Update
3. Assign Data Source to Info Source
- Transfer Structure and Transfer Rules
- 4 types of data Source
a) ATTR
b) TEXT
c) HIER
d) Transaction Data
4) Create Info Package and run/Schedule the Loading Process.
Topics:-
--------
1) How to delete data in the Info Cube?
2) different types of Update rules
3) Error handling options - in the Info Package ( Update )
4) Can we laod data into Multiple cubes from one Info Source? yes - How?
5) Can we load data into one Info Cube from Multiple Info Sources? Yes - How?
6) Difference between Transfer rules and Update rules?
-------------------------------------------------------
- How to Design an Info Cube:
-----------------------------------
- Top - Down Approach
- Bottom - Up Approach
- Mixed Approach
- Bottom - Up Approach
-----------------------------
Steps:
--------
1. Identify the Source Structure.
2. Identify the Characteristics & key figures
- Charateristics:
--------------------
- Bill Number
- Cno
- Pno
- Date of Transaction (0calday)
- Key figures:
-----------------
price
- qty
- discount
- amount
- Draw the Bubble Diagram.
- Draw the Graphical Star schema view
- Create the Info Cube in SAP BW:
----------------------------------------
- Info Area
- IOC
- Create the Info Objects - Requred to create the Info Cube
- Create the Info Cube
- nAMING CONVENTION TABLES:
-----------------------------------------
FACT TABLE - /BIC,0/FXXXXXX
ZC_001 --- /BIC/FZC_001
Dimension Tables:- /BIC,0/DXXXXXX1,2,3,4,5,6,7,8,9,A,B,C,D,P,T,U
- How to data from Flat file(.CSV) to Info Cube:
----------------------------------------------------------
- Pre-Requistes:
-------------------
1. Info Cube Must Be Active.
2. Flat file should be available.
3. Flat file - Source System Connection
Steps:
--------
1. Create the Application Component.
2. Create the Info Source of type Flexible Update.
3. Define the Communication Structure of the Info Source.
4. Assign the Data Source to Info Source
5. Customize the Transfer Structure as per the File Structure
6. Activate the Transfer rules.
7. Create the Update Rules to connect Info Cube and Info Source.
8. Create the Info package and specify all the details of the file and run it.
- How to load data from Flat file(.CSV) to Info Cube:
---------------------------------------------------------------
Pre-Requisites:
------------------
- Info Cube Should be active
- Flat file (.CSV)
- Source System Connection - Flat File
---------------------------------------------
Source System
SourceSystem
-----------------
- Types of Connectors / Adapters:
-----------------------------------------
- SAP Connection Automatic
- SAP Connection Manual
- Myself Connection
- Flat file Interface
- DB Connect
- UD Connect
- External Applications with BAPI
- Create the Flat file Interface Connection.":
-----------------------------------------------------
- IDoc
- Data IDoc
- Info IDoc
- Steps:
----------
1. Create the Application Component.
2. Create the Info Source.- Communication Structure.
- Direct Update
- Flexible Update
3. Assign the Data Source to Info Source : Transfer Structure
- ATTR
- TExT
- HIER
- Transaction Data
4. Create the Transfer Rules and Activate. ..?
5. Create the Update Rules to Connect Info Source & data Target (Info Cube)
6. Create the Infopackage and schedule the load.
- ETL Process:
-----------------
- Extraction Transferring & Loading
- Transfer Methods:
-----------------------
- PSA & IDoc
- IDoc:
-------
- Information through Info IDoc's
- Data through Data IDoc's
- PSA:
-------
- 2 dimensional table
- Structure of PSA TAble:- 4 technial Keys (Request No, Data packet No, Record N
o, Partion No) + Transfer structure.
- When we activate the transfer rules with PSA as the transfer method. it create
s a PSA table.
- PSA table Naming Convention :- /BIC/B000*
- iNFORMATION THROUGH iNFO idOC'S
- Data is transfered directly to PSA table using TRFC
- PSA will have the replica of data coming from source
- we can do editing in PSA. - Error handling
- Delete data in PSA
- Error Handling:
-------------------
1. Delete the Bad Request from the Info Cube.
2. Edit the Data in PSA
3. Reconstruct the Request
Record 1 :Value '20101401 ' of characteristic 0DATE is not plausible
- Processing / Loading Types:
------------------------------------
- PSA:
--------
- Deleting data in Info Cube:
---------------------------------
- 3 ways:
------------
1. Delete Data
2. Delete data based on the Request
3. Selective Deletion
- Update Modes:
-------------------
- Full Update
- Initialize Delta update
- Delta Udate
How to extract the Data Selectively FROM FLAT FILE?
---------------------------------------------------
G101 - G105
G111 - G115
G109
* Data Slections with different info objects will work with AND.
* Multiple Data Selections with in single info object will work with OR.
- Data Selections:
----------------------
- when we want to extract the data selectively from the source, we use Data Sele
ctions.
- Within in single field - OR, for multiple fields - AND
- Exclude is not possible.
- How to load the data from Flat file which is in the Application Server?
--------------------------------------------------------------------------------
----------
- AL11
C:\usr\sap\PBR\DVEBMGS00\work\ZF_MNO_ATTR.csv
- How to Schedule the Info Package in the BAckground?
-------------------------------------------------------------------
Note:- Client Workstation - Cannot be scheduled in the background
- Scheduling Options
- SM37
---------
Job Status:
--------------
- Active
- Finished
- Cancelled
- Released
- ready
- cASE 2:
----------
- Factory Calendar
- Control-M
- Redhood
- Dynamic Selection of Flat file:
-------------------------------------
Billing_20040102.csv
Billing_20040103.csv
D:\usr\sap\ERP\DVEBMGS00\work\Billing_20040102.csv
D:\usr\sap\ERP\DVEBMGS00\work\Billing_20040102.csv
str1 = 'D:\usr\sap\ERP\DVEBMGS00\work\Billing_'.
str2 = sy-datum.
str3 = '.csv'.
concatenate str1 str2 str3 into p_filename.
- Data Target Tab:
---------------------
- Delete entire content
- Deleting Overlapping Selections
- Update Tab:
----------------
- Dynamic Data Selections:
---------------------------------
L_T_RANGE
L_T_RANGE-IOBJNM = '0CALDAY'.
L_T_RANGE-FIELDNAME = 'CALDAY'.
L_T_RANGE-SIGN = 'I'.
L_T_RANGE-OPT = 'EQ'.
L_T_RANGE-LOW = SY-DATUM.
2 0 0 4 0 1 0 1
Y Y Y Y M M D D
0 1 2 3 4 5 6 7
SY-DATUM+0(4).
L_T_RANGE-IOBJNM = '0CALYEAR'.
L_T_RANGE-FIELDNAME = 'CALYEAR'.
L_T_RANGE-SIGN = 'I'.
L_T_RANGE-OPT = 'EQ'.
L_T_RANGE-LOW = SY-DATUM+0(4).
DATA V_PYEAR TYPE I.
V_PYEAR = SY-DATUM+0(4).
V_PYEAR = V_PYEAR - 1.
L_T_RANGE-IOBJNM = '0CALYEAR'.
L_T_RANGE-FIELDNAME = 'CALYEAR'.
L_T_RANGE-SIGN = 'I'.
L_T_RANGE-OPT = 'EQ'.
L_T_RANGE-LOW = V_PYEAR.
Types of Connectors / Providers
----------------------------------
i) SAP Connection Automatic
ii) SAP Connection Manually
iii) SAP MySelf Connection
iv) Flat File Connection
v) UD Connect
vi) DB Connect
vii) Connection by using BAPI's [ Business Application Programming Interface ].
*All the connection configurations are done by BASIS people.
When ever you maintain Connection b/w SSys and SAP BW.
Configures Intermediate Documents [IDOC's]
We have two types of IDOC's
i) Data IDOC's.---> carries records
ii) Info IDOC's. ----> How many records are get carried.
When ever you work with external Sourcesys
Make sure whether the connection is OK or NOT.
InfoSource
-------------
Grouping of Logical related info objects in what way / what sequence thery are g
oin to communicate with the Source System
****Infosource refers to Communication Structure.
We have 2 types of Infosources
i) Flexible Update
ii) Direct Update
i) When ever our target is placed in INFOPROVIDER level we will go with Flexible
Update. (eg: Infocube, ODS, Infoobject,.)
ii) When ever our target is placed in INFOOBJECT level we will go with Direct Up
date. (eg: Infoobject)
* If the Infoobject is at Infoprovider level we have flexibility to generate rep
orts on that Infoobject.
* If the infoobject is at Infoobject level, we can't do reporting on that infoob
ject.
Data Source
--------------
Grouping of Fields in what sequence they are comming from Source system.
*Data source refers to Transfer Structure.
We have 4 types of Datasources
i) ATTR
ii) TEXT
iii) HIER
iv) Transaction data

- Transfer Rules & Update rules:
----------------------------------------
- Transfer Rules:
---------------------
- Mapping Between Communication Structure & Transfer Structure.
- We use Transfer rules to perform any kind of transformation to the data coming
from Source.
- Types of Transfer Rules:
-------------------------------
1. Direct Mapping [Info Object]
2. Constant
3. Routine
4. Formula
1. Direct Mapping [Info Object]:
--------------------------------------
- Field --> Info Object
2. Constant:
---------------
- Fixed value for all the records
3. Formula:
--------------
4. Routine:
--------------
- Transfer Routine
- TRAN_STRUCTURE
- TRAN_STRUCTURE-/BIC/ZCNO
- RESULT
/BIC/ZQTY
/BIC/ZPRC
RESULT = .
/BIC/Y_PRC
/BIC/Y_QTY
* Reference and Template
------------------------
If we have an info object 'A', when we create the Info object 'B' by taking 'A'
as the reference, all the properties of 'A' are copied towards 'B' and we cannot
change any properties to 'B', We cannot load any data to the info object 'B' bu
t it refers to the data / data dictionary tables of main info object 'A'.
If we have an info object 'A', when we create the Info object 'C' by taking 'A'
as the Template, all the properties of 'A' are copied towards 'C' and we can ch
ange the properties of 'C', we can load the seperate master data for the info ob
ject 'C'.
When do we go with reference:
-----------------------------
When we want to create the new master data object which is supposed to hold the
data which is already a sub set of some other Master data objects, we go for cre
ating the Master data object with reference.
Reference Example:-
-----------------------
- Sold to Party , Ship to Party, Bill to Party, Payer are created with reference
to Customer.
- Sender Cost Center and Reciever Cost Center are created with reference to Cost
Center.