SAP-BI@Reporting@Read Mode of the Queries

Read Mode of the Queries:-
-------------------------
3 read modes:-
------------
1) Query to read all data at once (A)
2) Query to read data during Navigation (X)
3) Query to read data on demand when  Navigating/Expanding Hier (H)
* RSRT - READ MODE FOR A QUERY.
* RDMD - Read mode for all the queries on a particular Info Provider.

SAP-BI@How to Load MD -ATTR/TEXT from Flat file

How to Load MD -ATTR/TEXT from Flat file?
-----------------------------------------
Steps:-
-------
1) Create Application Component.
2) Create Info Source.
*  Info Source will define Communication Structure.
*  Communication Structure is specific to SAP BW.
* Communication Structure is grouping of logically related info objects indicating in what 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 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 fileds indicating in what structure format data is coming from the SS.
* Mapping B/W Trnasfer Structure and Communication Structure - Trnafer Rules.

Types of Data Source:-
-----------------------
1) Attr
2) Text
3) Hier
4) Transaction Data
5) Create Info Package and run the load.
* Info package is specific to Data source

SAP-BI@Query Design

Query Design:-
-------------
1) Include / Exclude.
2) Reduce the Result Set of the query.
 a) More Characteristics into Free   Characteristics block.
 b) Place one 0r two    Characteristics with less   Cardinality into Rows.
3) Reduce the Formatting.
4) Exceptions. - only for result
5) Reduce the usage of customer Exits.
 - Variable with Customer Exit
  (RSR00001).
 - Virtual Key figures & Virtual   Characteristics.
  (RSR00002).

SAP-BI@ExtractionMethod-CO-PA Extraction

CO-PA Extraction
----------------
Introduction:-
--------------
1) CO-PA stands for Controlling - Profitablility analysis.
2) We can do Planning in CO-PA. So we will 2 types of transactions in CO-PA a) Actual and b)Plan.
3) Value type :- is used as indicatore for Actual/Plan.
4) Actual transaction is more detailed and Plan transaction is more Aggregated.
5) Planning can be in multiple versions.(Version)
6) In BW we do 0Vtype reporting on CO-PA Cube.
7) Co-PA is an Integration Module.
8) Each actual transaction is stored in 3 different curriencies.ex:- Company code Currency,Transaction currency,Operating Concern currecy.
9) Currecncy Type :- Used as indicator of the currency.
10) CO-PA comes as part of customer generated extractors.
11) CO-PA datasource is generated based on Operating Concern.
12) Operating Concern is the top most Legal entity for controlling which will have its own Data structure with Value fields and Charcteristic fields.
13) CE1xxxx - Actual Line Item table
    CE2xxxx - Plan Line Item table
    CE3xxxx - Segment level table
    CE4xxxx - Segment level table
14) We don't have a Business Content DS for Co_PA because CO-PA DS is based on Operating Concern and the Data Structure of Operating Concern can be different with specific to implementation.
How to generate the DS for CO-PA?
----------------------------------
Steps:-
-------
1) GO to T-code (KEB0)
2) Specify the CO-PA DS name in the given format. - 1_CO_PA%CL%ERK
* Max length of a CO-PA DS name is : 19.
3) Select Create,Operating Concern name
4) Specify Accounting based / Costing Based.
4.a) Costing based - Detailed Level of information, Accounting BAsed - Aggregated Information.
4.b) Costing BAsed - Product based company, Accounting based - service based company
4.c) Costing BAsed - Compnay code field is mabndatory, Accounting based - Company code, Controlling area, Cost element are mandatory fields.
5) Click on 'Execute' button.
6) In the next screen type '=init' in the command bar.
7) Field name for partitioning :- which segment.
8) generate the Catalog.
9) Save it
10) Generate
11) Replicate the DS.
How to Migrate the Data:-
-------------------------
* CO-PA runs delta based on timestamp.
* yyyymmddhhmmss (Time stamp).
* Timestamp information of a CO-PA DS can be viewed in T-Code (KEB2).
* Giving minimum of half hours time we call it as Safety delta.
1) Run thr Init load.
2) Once the Init is successful wait for minimum of Half hours time and schedule the delta loads.
Re-alignment of Timestamp:- (KEB5)--------------------------

SAP-BI@OLTPvsOLAP

Existance of an entity is not the business, but these entities should interact with each other to perform transactions, set of these transactions becomes business.
OLTP:-
----
When ever we perform a transaction, we record this transaction into the database.
* In OLTP System we generate Transaction data.
* Transaction Data:- data representing a particular transaction.
* Master Data:- Detailed Information about the Entities.
Customer, Material, Vendor,
OLAP:-
-----
* Online Analytical Processing
* As part of OLAP we extract all the transaction data from different OLTP Systems and store data and provide Analytical Data.
* Analytical Data:- Data which can be used for Analysis.
* SAP BW is an OLAP Application.
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 we 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 Systems in OLAP.
4. In OLAP we can provide authorizations based on the Data, But in OLTP we provide authorizations based on the reports/Transactions. because of this if we do reporting in OLTP system it affects ROI.
5. In OLAP we can have more Analytical reports like one of the Top customer did not buy one of your Top Product.

SAP-BI@Types of Update Rules

Types of Update Rules:-
-----------------------
Keyfigure:-
-----------
1) Direct Mapping
2) Routine
------------
 a) comm_structure
 b) routine_0001
* Return Table
* Unit CAlculation in the Routine
3) Formula
Characteristic:-
----------------
1) Direct Mapping
2) Constant
3) Routine
4) Formula
5) Master Data Attribute of
6) Initial Value
Time Characteristic:-
---------------------
1) Direct Mapping
2) Constant
3) Routine
4) Formula
5) Master Data Attribute of
6) Initial Value
7) Time Distribution
Note :- Automatic Time Conversions





 

SAP-BI@Types of Transfer Rules

Types of Transfer Rules:-
-------------------------
a) Direct Mapping
b) Constant
c) Routine or Transfer Routine
TRAN_STRUCTURE-/BIC/ZFCSAL * 50.
'Z'
TRAN_STRUCTURE-/BIC/ZFCNO
RESULT = 'Z' + TRAN_STRUCTURE-/BIC/ZFCNO.
CONCATENATE 'Z' TRAN_STRUCTURE-/BIC/ZFCNO INTO RESULT.
d) Formula

SAP-BI@Reporting@Variables

Variables:-
----------
* To Parameterise the queries.
* To make queries dynamic.
Types of Variables:-
--------------------
1) Characteristic value Variable
2) Text Variable
3) Formula Variable
4) Hierarchy Variable
5) Hierarchy Node Variable
Processing Types of Variables:-
-------------------------------
1) User Enter / Default
2) Customer Exit
3) SAP Exit
4) Authorization
5) Replacement Path
Case : I
--------
Characteristic value Variable with User Entry / Default.
---------------------------------------------
Case : II
---------
* Characteristic value Variable with Replacement path
---------------------------------------------
* when we want the Characteristic value Variable to be replaced with the query result of other query.
Case : III
----------
* Characteristic value Variable with SAP Exit.
---------------------------------------------
* All Business content Variables will have the process type as SAP Exit.
* We will never work with this.
Case : Iv
----------
* Characteristic value Variable with Authorizations
---------------------------------------------

SAP-BI@RRI (Report - to - Report Interface )-RSCRM_REPORT-

RRI (Report - to - Report Interface ):-
----------------------------------------
* We Use RRI to jump(Drill trough) from one Bex Report to other objects like ( BEx Report, Web Report, Web Address, Crystal Report, Transaction, Infoset Query, ABAP Report ).
* T-CODE (RSBBS).
* on CO-PA cube ( ZSDCOPA ).

RSCRM_REPORT:-
--------------
* By using RSCRM_REPORT we can sechedule the report in the background and place the output of the report into a table,Fixed length file, CSV file.
* T-Code is - RSCRM_REPORT
* Limitation of RSCRM_REPORT:-
------------------------------
* When we retract the data using RSCRM_REPORT we can only retract Data but not the Header file.

SAP-BI@Reporting@Restriction-Condition-Exception-

Restriction:-
---------
* When u want to restrict the output of the query for particular values of a Characteristic.
*Conditions:-
-----------
* When u want to restrict the all the coloumns of the query based on the values of a Key figure - Conditions.
* Active
* Can we build the Conditions for specific Characteristics - yes.
* We can build conditions only on the Structure Elements (Keyfigures used in Coloumns).
* We can even switch on/off the condition at the runtime of the query.
* We can have multiple conditions in a report.
* When we build a condition with multiple restrictions in it - it plays with OR and when we build multiple conditions with each of the restrictions in it - it plays with AND.
* we have used the conditions To design Top 10 Customers Report and Top 10 Products Report.
* Exceptions:-
-------------
* Exceptions are used to provider some alerts on the output of the report based on the values of a key figure.
* We can build Exceptions on only those keyfigures which are acting as Structure Elements (Keyfigures used in Coloumns).
* By using 'Cell restriction' tab we restrict the cells on which the exceptions should play.
* Using Exceptions would degrade the performance of the queries.
* When we were desiging the 'Profitability Analysis Report' we have used the Exceptions to play only on to result.

SAP-BI@Reporting@Structures-CellDefinitions-RestrictedKeyfigure-NewSelection-CalculatedKeyfigure-NewSelection-NewFormula

* Structures:-
-------------
* Structures act as the reusable components.
* Structures can be used to provide hierarchical effect or Level Up - level Down effect in the report by using Level-up level down.
* we can only have maximum of 2 structures in a report.
* Structures can be of 2 types
 a) Local
 b) Global
* By using the option 'Remove Reference' changes what we do for a global structure will not be reflected to other queries where it has been used.
* Cell Definitions:-
--------------------
* We can define Cell definitions only when we are using 2 structures in report.
* By using Cell Definitions we can do calculation or restriction specfic to a particular CELL.

* Restricted Keyfigure:-
-----------------------
* when we want restrict the value of a Key fugure based on the value of a characteristic.
* We can do restriction on Multiple characteristics.
* Restricted Key figure restricts only to a particular coloumn.
* Restricted key figure is global because once it is created it can be used on all the queries built on the same info provider.


*New Selection:-
----------------
* Same as Restricted Key figure but New selection is Local.
* New Formula:-
---------------
* Same as Calculated Key figure.
*Calculated Key figure / New Formula
------------------------------------
* Calculated Key figure is Global, New formula is Local.
* When compared to Calculated Key figure, New Formula will have 6 functions more.
* All Key figures can be used in Building Calculated Key figures but we can only use the key figures which are used as the structure elements in New formula.

* Restricted Keyfigure:-
-----------------------
* when we want restrict the value of a Key fugure based on the value of a characteristic.
* We can do restriction on Multiple characteristics.
* Restricted Key figure restricts only to a particular coloumn.
* Restricted key figure is global because once it is created it can be used on all the queries built on the same info provider.
*New Selection:-
----------------
* Same as Restricted Key figure but New selection is Local.
* New Formula:-
---------------
* Same as Calculated Key figure.
*Calculated Key figure / New Formula
------------------------------------
* Calculated Key figure is Global, New formula is Local.
* When compared to Calculated Key figure, New Formula will have 6 functions more.
* All Key figures can be used in Building Calculated Key figures but we can only use the key figures which are used as the structure elements in New formula.

SAP-BI@Products of SAP

Products of SAP:-
----------------
1) SAP R/3:-
------------
* This is an OLTP system
* PL + DB + OS + Concept
* ABAP/4 + any DB + (UNIX / Windows ) + ERP
* ERP - Enterprise Resource Planning.
Enterprise :- Very Big Company
Resources :- 4 m's
men, Machinery, material, Money
Planning:- any thing we decide in advance
* By Using this concept of ERP we can integrate all the transactions in the Business and reduce the mis manupulation of resources.
2) SAP BW:-
----------
* This is an OLAP Application
* PL + DB + OS + Concept
* ABAP/4 + any DB + (UNIX / Windows ) + DW
3) SAP CRM:-
------------
* Customer Relationship Management
* PL + DB + OS + Concept
* ABAP/4 + any DB + (UNIX / Windows ) + To Retain the existing Customer.
* Sub Modules:-
--------------
1) Internet Sales
2) Mobile
 a) Sales
 b) Services
3) Call centers
 a) Sales
 b) Services
4) SAP APO:-
-----------
* Advanced Planning Optimizer (Planning Application).
* PL + DB + OS + Concept
* ABAP/4 + any DB + (UNIX / Windows ) + Production Planning.
* Sub Modules:-
----------------
1) DP - Demand Planning
2) SNP - System Network Planning
3) GATP - Global Availability to promise
4) PP/DS - Production planning and   Scheduling.
5) TP/VS - Transportation and Scheduling.
5) SAP SEM:-
------------
* Strategic Enterprise Management - Financial Planning
* PL + DB + OS + Concept
* ABAP/4 + any DB + (UNIX / Windows ) + Financial Planning.
* Sub Modules:-
-------------
1) BPS - Business Planning and Simulation
2) CPM - Corporate Performance Monitor
3) SRM - Stake Holder Relationship Management
4) BCS - Business Consolidation and   Simulation.
6) Enterprise Portals:-
------------------------
* Single Sign on.
* we can publish reports of any application on to portals.

SAP-BI@Reporting

Reporting:-
----------
* BEx ( Business Explorer )
Components:-
-------------
* Analyzer - To Design, Change, Execute, Delete BEx queries by Using a Component - Query Designer.
* Browser - To Organise the Reports.
* WAD (Web Application Designer ) - To Design Web Reports.
Note:-
-----
1) Info Provider
2) Data Target
3) Data Provider
(All Data targets are Info Providers but all Info Providers are not Data Targets)
Analyzer (MS Excel with ADD-ON Components):-
-----------
* How to Design a Simple BEx Report?
------------------------------------
* Understanding the BEx Report Output.
----------------------------------------
1) Title of the Report
2) Navigation Block
3) Result Set of the Query.
* Query Execution Process:-
---------------------------
When we execute the BEx query it triggers the OLAP Processor and this identifies the Info Cube on which the BEx report should be executed on and triggers the query on to the Info Cube and selects the records and aggregate the records based on the Characteristic Values in the OLAP Processor and transfers the records to the Front end (BEx).
* Complex reporting with all the Aspects:-
------------------------------------
* Characteristic Properties:-
------------------------------
1) Heading of the Coloumn
2) Display as
3) Suppress Result Row
contd....
* Key Figure Properties:-
--------------------------
* Query Properties:-
--------------------

SAP-BI@Calculated Key Figure

Calculated Key Figure:-
----------------------
* When we calculate a new keyfigure based on the existing Keyfigures by performing some calculations and using some pre-defined functions.
* When we use Calculated Key figure it performs the same calculation through out the entire coloumn.
* Functions:-
-------------
- Basic Functions:-
-------------------
1) High(**) - Power of
 ex:- 2 high 5 = 2^5 = 32.
- Percentage Functions:-
-------------------------
2) Percentage Share(%A):- To calculate    Percentage.
 ex:- 40 %A 200 = 20.00%.
3) Percentage Variance(%) :- To Calcualte the         Percentage on         the Variance      (difference) on 2     operands.
 ex:- 40 % 200 = -80.00 %.
- Data Functions:-
------------------
4) Count - Value =1 if operand is not equal to 0 and if the operand is equal to 0 then it returms 0.
 Ex:- Count(12) = 1.
      Count(0)  = 0.
5) Date :- This function converts the numeric value into Date format by counting the number of days from 01.01.0001.
 ex:- Date(14) = 15.01.0001
  01.01.0001 + 14 days =      15.01.0001.
6) Delta :- Value =1 if operand is equal to 0 and if the operand is not equal to 0 then it returms 0.
 Ex:- Delta(12) = 0.
      Delta(0)  = 1.
7) NODIV - We use this function to control divide by Zero exception by converting infinite value into 0.
 Ex:- NODIV( 1500 /0 ) = 0.
8) NODIM - This function can be used to see the Key figure value without unit dimension.
 Ex:- if we have Revenue as 150.00 INR Then NODIM(Revenue) = 150.00.
 Ex:- if we have Quantity as 50.00 KG Then NODIM(Quantity) = 50.00.
9) NOERR - We use this function to control the exceptions when the keyfigure is not able to define the currency/unit for it.
10) Time :- We can convert the numeric value into time format by counting each value as one second starting from 00:00:00.
 Ex:- Time(100) - 00:01:40.
- Mathematical Functions:-
---------------------------
- Boolean Operators:-
---------------------

SAP-BI@Line Item Dimension

Line Item Dimension:-
-------------------
* When only one characteristic is assigned to the Dimension ( and ).
* When the caridinality of Dimension table is more than the 20% of the Fact table.
* when we make a Dimension as Line Item Dimension the Dimension ID in the Fact Table will be Refering to the SID Table.
NOTE : RSDEW_INFOCUBE_DESIGNS  - will give the cardinality of the dimension tables

SAP-BI@Indices or Index of the Info Cube

Indices or Index of the Info Cube:-
-----------------------------------
2 types of Indices:-
--------------------
1) Primary Index
2) Secondary Index
 2.a. Bitmap Index
 2.b. B-Tree Index
2.a. Bitmap Index:-
* When the caridinality of Dimension table is less than the 20% of the Fact table.
2.b. B-Tree Index:-
* When the caridinality of Dimension table is more than the 20% of the Fact table.
NOTE : RSDEW_INFOCUBE_DESIGNS  - will give the cardinality of the dimension tables.
* Card Height ( check box )
Note :- When we Build indices on a Info Cube it improves Query Performance but it Degrades Loading Performance subject to Data Volume.

 

SAP-BI@Start Routine

Start Routine:-
---------------
* Start Routine will Execute first before the Update rules.
* Start Routine will execute for the entire Data Packaet once.
* Name of the Start Routine - ROUTINE_9998
* We can also write Start routine in Transfer rules only if the transfer method is PSA.
* In BI 7.0 we also have END Routine.
* once info source can feed multiple cubes.
* multiple info sources can feed one cube.
* one info source can have multiple Data sources but same data source cannot be assined to multiple info sources.
---------------------------------------
zstru
f1 f2 f3 f4
c1 c2 10 20
--------------------------
table : DATA_PACKAGE
F1 F2   F3 F4
-------------

C2 EUR M2  20
C3 PAC M3  30
LOOP AT DATA_PACKAGE.
 IF DATA_PACKAGE-F2 = 'AMR'.
  DELETE DATA_PACKAGE.
 ENDIF.
ENDLOOP.



 

SAP-BI@Compression of Info Cube

Compression of Info Cube:-
-------------------------
* /F AND /E are the 2 fact tables.
* when we load data into the Info Cube it goes into /F table and when we compress the Cube it deletes the request id information and aggregates the records based on the Characteristic value combination and puts the Data into the /E table.
* When we do reporting on the Info Cube data comes from /F and /E tables.
* Once compress is done in the Info Cube we cannot delete data based on the request in the Info Cube, But we can solve the problem by doing request reverse posting only if data is available in PSA.
* In Collapse Tab when we specify a request and compress the cube - it only compresses the specified request and all the request below it.
* With Zero Elimination - after compression if it finds any records with all its keyfigure values being zero it deletes those records.

SAP-BI@Aggregates

Aggregates:-
-----------
* Smaller Cube built on a Info Cube to Improve the Query pderformance.
* If we dont rollup the request it will not be available for reporting.
* Thumb rule for Aggregate - DB time is greater than 30% of the total time and Aggregation Ration > 10.
* Activate / Deactivate
* Switch on / off
* Delete
* nAVIGATIONAL aTTRIBUTE CAN BE USED IN BUIDING THE AGGREGATE.
* Attribute change run
* Aggregate hierachy levels
Limitation:-
----------
1) It stores data redundently.

SAP-BI@Types of ODS

Types of ODS:-
--------------
1) Standard
2) Transactional
1) Standard:-
--------------
* Data Target and Info Provider
2) Transactional:-
--------------------
* Used only for Planning.
* Not available for Reporting.
* Only Active Data Table.
* Loading Data into Sebsequent data targets is possible.

SAP-BI@Types of Attributes

Types of Attributes:-
---------------------
1) Display Attribute:-
----------------------
* Completely Dependent on the Charectristic.
* It always gives the present truth.
2) Navigational Attribute:-
--------------------------
* It acts as a Charcteristic in the reporting.
* It always gives the present truth.
* Technical Name - YG_CNO__YG_CNAME.
3) Exclusive Attribute:-
-----------------------
* When we unselect Attribute only checkbox it becomes an Exclusive Attribute, So it can used as a Characteristic in the cube - giving fact.
4) Time - Dependent Attribute:-
------------------------------
* when we see the attribute value changing and if we want to maintain all the values of attribute with respective to different Time intervals we go for Time - Dependent Attribute.
* All Time dependent attributes will be stored in table  - /Q
* /Q table will by default holds DATE-TO AND DATE-FROM fields.
* in /Q table DATE-To filed will be acting as part of Primary Key.
* Value can be controlled by using Key date of the Query in the query properties.
5) Time Dependent NAvigational Attribute
-----------------------------------------
6) Compounding Attribute:-
--------------------------
* Superior Info Object
* When the Value of One Info Object is Dependent on the Value of Another Info Object - we go for compounding.
* 0SOURSYSTEM
Ex:- 0mat_plant
7) Transitive Attribute:-
---------------------------
* Second Level of Navigational Attribute.

SAP-BI@Remote Cubes

Remote Cubes:
---------------
 a) SAP Remote Cube
 b) General Remote Cube
* It is a Virtual Cube
* Remote Cubes are not Data Targets but Info Providers.
(Note :- ALL Data targets are Info providers but All info providers are not Data targets)
a) SAP Remote Cube
when:-
------
1) Reconciliation
2) Periodicity of the report usage is low
3) Refreshed transactions in the report
( Today is yesterday, Today is Today)
Advantages:-
------------
1) Improvised Database performance
2) Unnecessary process can be eliminated
Disadvantages:-
-----------------
1) Degrades the performance of the query

b) General Remote Cube:-
------------------------
* we use General Remote Cube to access data remotely from Non -SAP Source System.
c) With Services:-
------------------
* We can fill data into the Info Cube dynamically by using Function Module(SE37) at the run time of the query.








 

SAP-BI@Partitioning of InfoCube

Partitioning OF iNFO cUBE:-
---------------------------
* /F  table is by default partitioned based on the request number.
* when we partition a cube by default it pastitions the /E table.
* we can partition a cube based on "calender year/month" and "Ficsal year Period".
* we cannot partition a cube if it contains data in it.
* We cannot Re-partition an Info Cube till BW 3.5 but in BI 7.0 we can do Re-partition.
* We cannot partition an Info Cube if the backend Database is SQL Server.

SAP-BI@Open Hub Service ( Info Spokes )

Open Hub Service ( Info Spokes ):-
----------------------------------
* Retraction.
* Retracting the Data back from BW ( Info Cubes, ODS, MD - ATTR,TEXT,HIER) into Flat Files or Data base tables.
* Scenerio(1)  - Management Cockpit
* How to create Info Spokes to Retract data from Info Cube to Flat file?
* When we Retract data with the Infospokes it creates to files ( Data file and Header file (s_xxxxxxxx))
* Both the Flat files would be .CSV files.
* When retracting the Data the Infospokes are Aggregating the records based on the Characteristic values.
* NAMEING CONVENTION OF THE TABLE - /BIC/OHxxxxxx(DESTYINATION NAME ).
* Delta Mechanism for Info Spokes.
* Scenerio(2) - Loading from Info Cube to Info Cube based on a Request.
* Transformations Using BADIs's.
In the Infospoke screnn - Transformation Tab - Select the Chek box "Info Spoke with transformations using BADI's" then it automatically creates an Implementation class with the naming convention as 'ZCL_IM_xxxxxxxx' ( SE24 ) and with an interface 'IF_OPEN_HUB_TRANSFORM' and this interface brings in the method 'IF_OPEN_HUB_TRANSFORM' and then we start writing the transformation code in this method.
* loop at E_T_DATA.
if E_T_DATA-salval = 0 and E_T_DATA-salkg = 0.
delete E_T_data.
endif.
* Limitation of Info Spoke:-
--------------------------
* Using Info Spoke we cannot retrive the data if it is available in multiple data Targets.
* Info Spoke will not work for Virtual Providers.

SAP-BI@ProductionSupport@RealTimeWorkflow

* Production Support:-
----------------------
* 2 activities
     - Monitoring of Data loads using PC.          - Handling of the Tickets posted by the   end Users.
- Monitoring of Data loads using PC.
------------------------------------
* Criteria Document
* List of Errors and how to solve them.
* RSPC, RZ20,RSPCM, BWCCMS
* rspc_process_finish
* VPN  - (Secure ID)
* 34000 loads per day
* 24 X 7 support
* 8 members in off shore and 2 in onsite
* Telcone , mails, Sametime, Net meeting
* 40 - 50 Cubes , ODS
* 560 info packeges
* BP2, BD2, BQ2,
* 2 erors per day.
- Handling of the Tickets posted by the
 end Users.
--------------------------------------------
* What tickets?
----------------
- Creation of new report.
- Changing of existing Report.
- Data Mismatch Tickets.
- CR (Change Request) changing existing cube by adding new info Objects.
- Authorizations.
* SLA of tickets:-
------------------
pririty   repond time Solution Time
---------------------------------------
0 -  15 minutes 2 hours
1 -  15 minutes  5 hours
2 -  1 hour 24 hours
3 -  1 hour 56 hours
* SOP ( Standard Operating Procedures ).
* Ticket Handling Tools:-
-------------------------
1) Vantive
2) Synergy
3) pere - green
4) Designed by my Client
* Interface of the Tickect Handling Tool:-
------------------------------------------
* Did you interact with Customers any time?
--------------------------------------------
- Information on tickets.
- Weekly meeting / Monthly meetings
- We discuss on Ticket Status Report, Monitoring Status report, Resource Utilization report.

SAP-BI@Types of Cubes

Types of Cubes:-
---------------
1) Basic Cube
2) Transactional Cube
Virtual Cubes
-------------
3) SAP Remote Cube
4) General Remote Cube
5) with Services
Data Target:-
------------
Info Provider:-
--------------
Data Provider :-
---------------
BAsic Cube:-
------------
* It is an Data target and Info Provider.
Transactional Cube:-
-------------------
* Basic Cube + Planning
* Interagting SEM(BPS) and BW
* BPS - Business Planning and Simulation.
* Integrated Planning in Bi 7.0

SAP-BI@Proces Chains

Process Chains:-
---------------
* T-code to create PC - RSPC.
* Different Processes Connected like a chain we call it as PC.
* What ever we can do with event chains we can do the same with the help of process chains, But it will more Graphical and easy to monitor the Process Chains.
* Process / Variant
* Process :- Any Activity what we can perform in SAP BW.
ex:-
1) Deleting Index of Info Cube.
2) Create Index of Info Cube.
3) Roll Up.
4) Initial Fill.
5) Compression.
6) Info Spoke.
7) Load Data.
8) Attribute Change Run.
9) Reporting Agent Setting.
10) Deleting Data in the Cube.
11) ODS Data Activation.
12) PSA Deletion.
* Variant :- It is the object On which the process has to pe perormed.
* 2 types of Process Chains:-
------------------------------
1) Direct Chain :- It is a PC which can be scheduled directly.
2) Meta Chain :- It is a PC within another PC.
* Every PC must start with the Start Process.
* We can Deploy Parallism by using Process Chains.
* How to Create a Simple PC?
-----------------------------
Case Study:-
----------
P1 - > Delete the Index of the Cube ( ZY_PC)
p2 - > Load the Data to which cube ZY_PC
p3 - > Create the Index of the Cube ( ZY_PC)
p4 - > Rollup the req. to Aggregates (ZY_PC)
p5 - > Compression in ZY_PC.
Scenario:-
-----------
1) Loading it to cube

SAP-BI@BASICS

Characteristic:-
----------------
General
-------
Data Element:-
It Defines Technical Properties and Semantic properties
/BI(c/0)/OIxxxxxx
zc_cnum  -> /BIC/OIZC_CNUM
Data Type:-
Char - A-z ,0-9
Numc - 0-9
Dats - yyyymmdd
Tims - hhmmss
Length:-
Max. Length of info Object is : 60
Lower Case Letters:-
It allows both Capital Letters and small
sid TABLE:-
/BI(c,0)/SXXXXXX
ZC_CNUM
/BIC/SZC_CNUM













 

SAP-BI@BASICS OF DATABASE

BASICS OF DATABASE:-
--------------------
* Table.
* What is a Table?
-----------------
* Set of Rows and Coloumns.
* Coloumns would define the Logical Definetion of an entity.
* Each Row would define the physical definetion of an entity.
* Every table must have a Primary Key.
* Coloumn which can be used to maintain the Uniquness among all the records in the table - Primary Key.
* we have 2 types of coloumns in a table.
 1) Key Coloumn
 2) Non - Key Coloumn
Key Coloumn:- Coloumn which is a part of Primary Key.
Non - Key Coloumn:- Coloumn which is not a part of Primary Key.
* All Non - Key Coloumns act as Attributes or Properties for Key Coloumn.
Composite Key:-
---------------
* When 2 or more coloumns act as the primary key of a table - Composite Key.
* Denormalized Table:-
----------------------
* Table with Redundency of data.
* Wasting Database space.
* Degarded performance.
* Normalized Table:-
-----------------------
* Instead of storing the data in a single table, we split the data into multiple smaller tables connected with Primary key - Foreign Key where there is no data redundency - Normalized tables.
* Foreign Key:-
-------------
* When a Primary key of one table takes part in the other table we call it as Foreign Key.
* Normalization:-
-----------------
* The process of converting Denomalized tables into normalized tables by using normalization forms.

SAP-BI@How to Schedule the load in the Background

How to Schedule the load in the Background?
--------------------------------------------
* when we are loading from AS we can schedule the load in the BAck ground
Active :- Running
Fininshed :- Successfully done
Cancelled :- Failed
Released - waiting for the  next schedule
Ready :- Job is ready to run

SAP-BI@ODS

ODS

 

->  ODS STANDS FOR OPERATIONAL DATA STORE

->  IN BI7-WE CALL IT AS DATA STORE

->  IT IS A 2 DIMENSIONAL TABLE

->  IN BW 3.5 ODS IS OF 2 TYPES

     1>  STANDARD

     2>  TRANSACTIONAL

->  IN BI.7 ODS IS OF 3 TYPES

     1>  STANDARD

     2>  DIRECT UPDATE

     3>  WRITE OPTIMESED DATA STORE

->  WHEN WE CREATE ODS IT CREATS 3 TABLES INTERNALLY

     1> ACTIVE DATA TABLE

     2> NEW DATA TABLE

     3> CHANGE LOG TABLE

->  NAMING CONVENTIONS OF 3 TABLES

    ACTIVE DATA TABLE :  /BIC(C/0)/A{NAME OF ODS}00

    NEW DATA TABLE : /BI(C/0)/A{NAME OF ODS}40

    CHANGE LOG TABLE : SAME AS PSA TABLE

->  PROPERTY OF CUBE IS ADDITIVE

->  PROPERTY OF ODS IS OVER WRITE IF WE WANT WE CAN MAKE AS ADDITIVE

->  WHEN WE EXTRACT DATA INTO ODS IT GOES DIRECTLY INTO NEW DATA TABLE.

->  WHEN WE DO REPORTING ON ODS DATA COMES FROM ACTIVE DATA TABLE.

->  WHEN WE RUN INFO PACKAGE DATA GOES INTO NEW DATA TABLE BUT REQUEST WILL BE STILL IN YELLOW

    BECAUSE DATA HAS NOT GONE INTO ACTIVE DATA TABLE FOR THAT WE PERFORM FUNCTION ACTIVATE

    DATA IN ODS BUT TO DO THIS REQUEST MUST BE IN GREEN FOR THAT WE SET QUALITY STATUS TO GREEN.

->  WHEN WE ACTIVATE DATA IN ODS IT TAKES ALL THE RECORDS FROM NEW DATA TABLE TO

    ACTIVE DATA TABLE AND CROSS CHECKS THE RECORDS WHETHER ACTIVE DATA TABLE CONTAINS ANY

    RECORDS WITH SAME PRIMARY KEYS IF THERE IS NO RECORD THEN IT ADDS ASNEW RECORD IF THERE

    IS ANY RECORD WITH SAME PRIMARY KEY THEN IT OVER WRITES IN ACTIVE DATA TABLE.

->  WHILE DOING THIS PROCESS IT MAINTAINS IMAGE IN CHANGE LOG TABLE.

->  WHEN WE DO REPORTING REPORT FETCHES DATA FROM  ACTIVE DATA TABLE.

->  WHEN  WE DO INIT OR FULL LOAD INTO DATA FETCHES FROM ACTIVE DATA TABLE AND CHANGE LOG TABLE.

->  WHEN WE ACTIVATE DATA IN ODS DATA TRANSFERS FROM NEW DATA TABLE TO ACTIVE DATA TABLE.

    AND CLEANS DAT IN NEW DATA TABLE.

->  WE LOAD DTA DIRECTLY INTO CUBE OR FROM DATA SOURCE TO ODS TO CUBE DEPENDS ON

    DATA SOURCE FUNCTIONALITY.

->  IF DATA SOURCE ITSELF GIVES BEFORE IMAGE AND AFTER IMAGE THEN WE CAN LOAD DIRECTLY

    INTO CUBE.

->  IF DATA SOURCE IS NOT GIVING ANY BEFORE IMAGE AND AFTER IMAGE THEN ODS IS MANDATORY.

SAP-BI@Non - Cumulative Key figures

Non - Cumulative Key figures:-
------------------------------
* when we dont want the Key figure value to be Cumulated based the Characteristic value combination - we go for Non - Cumulative Key figures.
* We define Non - Cumulative Key figures by using a property "EXCEPTION AGGREGATION" in the aggregation tab of the Key figure.
1) No of Employees
2) Sales Employee Performance
3) Inventory Management

SAP-BI@FlatFile Loading into InfoCube

How to load into the Info Cube from Flat file?

Steps:-
1) Create the Application Component.
2) Create the Info Source of type Flexible Update.
3) Create Source System for Flat File.
4) Assign Data Source to Info Source.
5) Connect Info Source to the Info Cube by using Update Rules.
6) Create the Info PAckage and schedule the load.

SAP-BI@Info set

InfoSet:-
-----------
* we can join only 2 dimensional objects like ( ODS, Info Objects).
* atleast one infoobject of chararecteristic should be same in all the objects.
* the property of infoset is Inner Join or Left Outer Join
* irrespective of BEx reporting check box is selected or not we can include the ODS in the Info Set.

SAP-BI@Info Package Groups

Info Package Groups:-
--------------------
* By USing Info Package Groups we can automate the execution of info packages (Loading Process) sequentially.
* We can only include those infopackages which can scheduled in the background into the info package groups.
* Info Package group runs only in the background.
* Limitations of Info Package Group:-
------------------------------------
* Using Info PAckage Groups we can only automate the process of Loading and does not support to autoamte any other process like Deleting Index, Createing Index, Roll up, Compression, info Spokes, Reporting Settings, Ods Activation, PSA Deletion, Attribute Change Run, Deleting Contents of Data Targets, Activating MAster Data, Initial Fill.

SAP-BI@Implementation Project

* Implementation Project:-
--------------------------
* ASAP Methodology
 - Project Preperation
 - Blue Print Phase
 - Realization Phase
 - Testing
 - Go- Live and Support.
* Project Preperation:-
----------------------
1) Identify the Project Manager or Accounts Manager.
2) He prepares Project Plan.
3) PM appoints Project Lead or Team Lead for SAP BW.
4) PL forms the core team with some SR. Consultants.
5) PL + Core Team will go to the onsite.
* Blue Print Phase:-
---------------------
- Gathering User Rquirements.
1) 80 % of the requirements can be collected from  the reports what is available in legacy system.
2) We collect the sample output of all these reports.
3) We form a document called - PI Documentation Tree.
4) We segregate the no. of users based on the Role.
5) We conduct interviews for the Power users based on the role and understand the requirements.
6) We form a document called - PI Documentation Tree for each Role.
7) Get the Sign off.
- Blue Print the Documents (Preparing the Functional Specs)
1) We interact with Core Function Team to understand the PI, Business Subjects.
2) We form a document called 'PI Measure Glossary'.
3) Define the Scope of the Project - by identifying to which Modules data we have to extract.
4) prepare the FS by doing GAP ANalysis
 - Graphical Star Schema view(IC)
 - Key Fields & Data Fileds
 - DFD for the Data Targets.
- Submit these Functional Specs and get the Sign off.
* Realization:-
---------------
1) Prepare the Technical Specs as per the FS.
 - Data Target Technical Spec Doc.
 - Mapping Document.
 - ETL Document.
 - Report Technical SPec. Doc.

Event Chains

Event Chains:-
-------------
* With the help of event chains we can automate the execution of any process in SAP BW with the help of events.
Example:-
--------
p1 -> Delete the Indexes of (YC_SD01)
p2 -> Load the Data into YC_SD01
p3 -> Create Indexex of (YC_SD01).
* T-code to create Events - SM62.
* T-Code to trigger an Event - SM64.
Limitations of Event Chains:-
------------------------------
* It is tough to monitor the process which are triggred by event chains.





 

DataSource Enhancement

Data Source Enhancement:-
------------------------
when:-
-----
* when we are not satisfied with thw fields in the ready made ES delivered by SAP as part of Business content.
* How?
------
Lo & Non-Lo
LO
---
1) Append a field to Communication Structure.
2) Maintain the Extract Structure by selecting the field from the Communication Structure to Extract structure.
3) write the enhancement code to populate data into these fields - RSAP0001.
NON-lO
------
1) Append a field to Extract Structure.
2) write the enhancement code to populate data into these fields - RSAP0001.

SAP-BI-Business Content Objects

How to Install Business Content Objects?
----------------------------------------
2 types of objects is SAP BW:-
------------------------------
a) Standard or Business Content Objects
---------------------------------------
* Versions -  A,M,N,D
* ALL the Business Content Objects delivered by SAP will in Delivered Version.
* All Business Content Objects will have technical name prefixed with 0.
* T-Code - RSOR.
* Collection Mode - Automatic Collection / Manual Collection.
* Grouping
 1) Only Necessary objects
 2) In Data Flow Before
 3) In Data Flow Afterwards
 4) In Data Flow Before and                  afterwards
b) Customized object

MultiProvider

Multi Provider (Multi Cube):-
------------------------------
* we can join Info Cubes,ODS,Info Objects,Info Sets
* It is Virtual Cube
* Atleast one infoobject of type Char should available in both the objects.
* Info Provider
* Multiprovider works with Union (Left Outer Join).
* ODS for which BEX reporting check box is selected can be included into Multiprovioder.
* we can build multiprovider on a single cube

SAP-BI7-Advanced Features

* New Features in BI 7.0
--------------------------
* RSA1 -> Enterprise Data Warehouse workbench
* RSA1_old -> Administrator workbench
* PSA is the only Transfer method.
* Infosource is not mandatory.
* TR and UR are replaced with Transformations.
* END Routine in Transformations.
* Expert Routine.
* Info package can be used to load data from SS to PSA.
* Standard DTP ( Data Transfer Process ) is used to load data from PSA to Data Targets.
* Error records will be written into Error Stack, we can do editing in Error Stack and use Error DTP to upload data from Error DTP to Data Targets.
* ODS is called Data Store.
* 3 types of Data Store:-
 1) Standard
 2) Write Optimized
 3) Direct Update.
* Basic Cube - Standard Cube
* Transaction Cube - Real Time Cube
* Remote cubes  - Virtual Providers.
* Info Cubes can also be included into Info Sets.
* Maximum we can only have 2 info cubes in an info set.
* Re-partioning.
* Re-Modelling.
* Display mode of Process chains.
* Direct flexibility of Copying the process chain - in the RSPC - PRocess Chain Menu.
* Decision Process type implemented with Formula Editor.
* Real-Time Aquisition.
* we can Info Spokes on Multi provider.
* Reporting:-
--------------
* GUI of Query designer has changed.
* WEB Analyzer.
* Report Designer.
* All the Functionalities of Reporting Agent has moved to Information Broadtcasting.
* old Reporting agent -t-code 'REPORTING_AGENT'.
* BI Acclerator is implemented with Hardware components called Blades to improve the performance of the queries.
* Integrated Planning - similar to BPS and more functialities.
* Data Archiving.
* Data Mining.
* SS connections - UD connect, Web Sevices
* External system connection with BAPI is not avilable in BI 7.0

ER MODEL Design

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 locations, 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 relationship diagrams.
 * if N.K.C is related to K.c as 1:M then split the N.K.C into other table 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 table.
 * if N.K.C is related to K.c as M:M then split the N.K.C into other table 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 entity.
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 Entities.
* ER model is Normalized.
---------------------------------------------