Saturday, May 14, 2016

Change your Working domain Join Into SAP Career





Customize your course Content:
Learn
SAP BW
SAP BI
SAP ABAP
SAP BASIS...

Learn at your place on Weekends...


Labels: , ,

Know What is SAP,Startup your Career in SAP

http://sunilbabusanjamala.wix.com/sapbwtraining
http://sunilbabusanjamala.wix.com/sapbwtraining
http://sunilbabusanjamala.wix.com/sapbwtraining




Labels: , ,

Tuesday, April 5, 2016

SAP BI Links

Labels: , , , , , ,

Tuesday, March 29, 2016

Jobs Interview Questions and Answers Resume Points Cutover Checklist


SAP Job Resume Points


He has more than 13 years of SAP R/3 experience in managing projects, data migration and ABAP development. He has managed small to medium size projects for roll-outs to 10 countries. As architect and technical consultant has worked on wide range on SAP modules (MM, SD, PM, PP, PS, HR and FI). He has been involved in analysis of functional requirements, drafting technical specifications, development and unit testing and delivers timely and quality solutions. He has an experience of working in capacity of onsite/offshore coordinator, team lead and team member. He has got strong logical and analytical capabilities. Some of his strengths are positive attitude, good grasping power and urge to learn new things.


SAP BI Cutover Task CHECKLIST

Description
Schedule downtime of ECC for initial loads
Determine test queries
Schedule resources for cutover including basis
Setup cutover role for BW and source systems
Assign user authorisations in portal if applicable
Set up ALEREMOTE (BWREMOTE) with proper security
Test cutover roles
Set up BW ensure connections to source systems
Validate source system settings
Check FTP directory for flat files
Manually configure in BW (RS_PERS_ATIVATE) per note 754206
Apply SAP notes to Prod
Apply database/kernel patches to prod
Set up printers
Check permitted chars
Check default package size (spro)
Check flat file paramters (spro)
Check any external systems need rescheduled/impacts of this change
Backup BW system
Ensure Checkpoint calls (eg ECC system/BW system offline completed) are in there

Transport requirements:/Order:
Change source system name after transport (rsa1)
Maintain source system ids (rsa1)
Transport ECC data-sources
Transport data-sources in VW
Replicate datasources
Transport info objects, validate
Info Providers, valudate
Transformations, validate
DTP, valudate#Info packages, validate
Process chains, validtate
Queries & query elements
Reporting roles
Web Templates

Portal:
Set up portal, save i-views

Prior to load:
Check traffic light settings
Set traffic light waiting time
Check permitted chars (RSKC)
Lock users out of ecc
Transfer global settings

Validation:
Reporting roles
Web templates
Process chains
Data loads
Queries and analysis

Data loads:
Set up programs in ecc
Schedule jobs for v3 logistics cockpit
Run delta initialisations for master data
Run delta initialisations for transaction data
Schedule periodic loads
Schedule process chains
Monitor loads


Labels: , , , , , , ,

Monday, March 28, 2016

SAP BI Reporting-Concepts-Features



Info-Object

An InfoObject is a generic term for characteristics and key figures in the Business Information Warehouse. InfoObjects are used in data targets and in the three structures that are relevant for data requests; extract, transfer, and communication structures.

Hierarchies

Hierarchies are tree-like structure of characteristic values for a particular characteristic. Characteristic hierarchies are stored in their own data tables. They act like master data and can therefore be used in all InfoProviders.
Example: Hierarchy using cost centres that are assembled in cost centre groups.

Infocube

InfoCubes are InfoProviders but are not necessarily data targets (InfoCubes are also data targets only if data is physically stored in them).

From a reporting point of view, an InfoCube describes a self-contained dataset, for example, of a business-orientated area. This dataset can be evaluated in a BEx query.         
An InfoCube is a quantity of relational tables arranged according to the star schema: A large fact table in the middle surrounded by several dimension tables.
InfoCubes are made up of a number of InfoObjects. All InfoObjects (characteristics and key figures) are available InfoCube-independently. Characteristics relate to master data with their attributes and text descriptions.

An InfoCube consists of several InfoObjects and is structured according to the star schema. This means there is a (large) fact table that contains the key figures for the InfoCube as well as several (smaller) dimension tables which surround it. The characteristics of the InfoCube are stored in these dimensions.
An InfoCube fact table only contains key figures, in contrast to an ODS object, whose data part can also contain characteristics. The characteristics of an InfoCube are stored in its dimensions.

Data Store Objects (DSO)

A DSO object acts as a storage location for consolidated and cleaned-up transaction data (transaction data or master data, for example) on the document (atomic) level.
It describes a consolidated dataset from one or more InfoSources. This dataset can be evaluated using a BEx query.

Info-source

An InfoSource is a quantity of information that logically belongs together, summarized into a single unit. InfoSources contain either transaction data or master data (attributes texts and hierarchies).

An InfoSource is always a quantity of InfoObjects that logically belong together. The structure in which these are stored is called a communication structure.

ABAP Routines

ABAP routines may be created to manipulate & QA data for transformation and Update.

Info-packages

This describes which data in a DataSource should be requested from a source system. The data can be precisely selected using selection parameters (for example, only controlling area 001 in period 10.1997).

An InfoPackage can request the following types of data:
·         Transaction data
·         Attributes for master data
·         Hierarchies for master data
·         Master data texts

Info-package Group

In order to summarize data requests which logically belong together from a business point of view, and to therefore simplify the request, you can collect data requests (meaning the InfoPackages) into an InfoPackage Group. You can schedule each of these groups in the scheduler. With the data request the scheduler can access InfoPackage groups directly and thereby request more than one InfoPackage at a time, corresponding to the setting in the InfoPackage group. Thus, you can support InfoPackage groups with the serialization of your data requests.


Collection of a selection of characteristics and key figures (InfoObjects) for the analysis of the data of an InfoProvider. A query always refers exactly to one InfoProvider, whereas you can define as many queries as you like for each InfoProvider.
You define a query in the Bex Query Designer, in which you select InfoObjects or reusable structures for an InfoProvider and specify the view of the data (query view) by distributing them to filters, rows, columns, and free characteristics. You used this saved query view as a basis for data analysis and reporting in the Bex Analyzer, in Bex Web applications, in Bex Mobile Intelligence, or in formatted reporting

Bex Query Variant
A query variant is a query for which the variable values have already been selected. The variants may be used for both opening the query in the online display and for background processing.

Restricted Key Figures (InfoProvider Level)

A restricted key figure is a key figure that is restricted to certain characteristic values. It is defined in the query and limits the selected data to the values or range of values selected.

Calculated Key Figures (InfoProvider Level)

A calculated key figure is a key figure that is calculated of one or more other key figures. Standard, custom, restricted key figures and other calculated key figures can be used for the calculation.


Variables are parameters of a query that you defined in the Query Designer and that are filled with values when you execute the query or Web application. They serve as a store for characteristic values, hierarchies, hierarchy nodes, texts and formula elements, and can be processed in different ways.


Currency Translation Types contain a combination of different parameters that establish how the exchange rate for the translation is executed. A translation type can be determined independently from source and target currencies.


Authorization objects enable you to define complex authorizations by grouping up to 10 authorization fields in an AND relationship to check whether a user is allowed to perform a certain action. To pass an authorization test for an object, the user must satisfy the authorization check for each field in the object.

An authorization is the empowerment to carry out a certain activity in the Business Information Warehouse. Each authorization refers to an authorization object and defines one or more values for each field that is contained in the authorization object. Individual authorizations are summarized into authorization profiles by system administration. You can copy the roles delivered by SAP and adjust them when you want. The system administrator creates these authorizations and enters them into individual users’ master records in the form of profiles.

There are two object classes in the Business Information Warehouse:

·         Business Information Warehouse – Reporting

No authorization objects are delivered in this object class. You create user authorization objects for reporting as and when you require them.

·         Business Information Warehouse


Roles are collections of activities which allow a user to use one or more business scenarios of an organization.

You can create workbook templates, into which you can insert your queries. Workbook templates contain the following elements:
·         Preset positions for the different areas (title, filter cells, results area, text element).
·         Format settings: You can change the background pattern, color scheme, and so on.
·         Logo, Bitmaps.
·         VBA macros.

Workbooks

Queries are inserted into workbooks so you can display them. When you insert a query, a link is made between the cell areas of the worksheet and the data of the Info Provider upon which the query is based. A link therefore exists between the Business Explorer and the Business Information Warehouse Server (BW Server). This link stays in place until you interrupt it.

When you open a query and insert it into a workbook, the query is calculated and the view (initial view) of the data established in the Query Designer is displayed.

A Web template determines the structure of a Web application. You use the Web Application Designer to insert placeholders into a HTML document for Web items (in the form of object tags), data providers (in the form of object tags) and BW URLs. The HTML document with the BW-specific placeholders is called a Web template. Web templates are checked into the Web Application Designer. The HTML page that is displayed in the Internet browser is called a Web application. Depending on which Web items you have inserted into the Web template, a Web application contains one or more tables, an alert monitor, charts, maps, and so on.

Web Reports

Web reporting enables the publishing of queries defined in the Business Explorer Analyzer to the Intranet or Internet. It is possible to insert and display queries in any HTML page. Multiple queries may be embedded into one HTML page, and graphics used to display the data (cockpit). Navigation functions are available to report on the data contained in a Web query (drilldown, refresh, and so on).


Name for a particular type of Info-Provider: An Info-Set describes data sources that are usually defined as joins for OD objects or Info-Objects (characteristics with master data). A time-dependent join or temporal join is a join that contains an Info-Object that is a time-dependent characteristic.
An Info-Set is a semantic layer over the data sources and is not itself a data target.
Unlike the classic Info-Set, an InfoSet is a BW-specific view of data.
A Classic InfoSet gives you a view of a dataset that you report on using the InfoSet Query. The Classic InfoSet determines which tables or fields within a table an InfoSet Query refers to.
Since Release 2.0B, InfoSets have been used in the Business Information Warehouse for InfoObjects (master data), ODS objects, and joins for these objects. These InfoSets are Basis Objects, not BW Repository Objects. The InfoSet Query can be used to carry out tabular (flat) Reporting on these InfoSets.

InfoSet User Groups

InfoSet User Groups are used to control who may access InfoSet Queries. Users may not be allowed to modify queries from other user groups, although they may, under certain circumstances, copy and execute them (see Copying Queries).

Within a user group, it is irrelevant who has defined a certain query, since anyone who belonging to that group can execute it. However, only users with the appropriate authorization can change queries or define new ones.

Each user can be assigned to several user groups.


Labels: , , , , , ,

Monday, June 8, 2015

How to Learn SAP BW


Hi Readers,



Have planned to publish an e-book on this topic soon.


The best link in one-shot is the one below provided by SAP.
Try to leverage this :

http://wiki.scn.sap.com/wiki/display/BI/SAP+Business+Warehouse+Home




Happy Reading!!!



Labels: , , , , , ,

Wednesday, August 22, 2012

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.



Labels: , , , , , , ,

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

Labels: , , , , , , ,

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).

Labels: , , , , , , ,

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)--------------------------

Labels: , , , , , , ,

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.

Labels: , , , , , , ,

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





 

Labels: , , , , , , ,

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

Labels: , , , , , , ,

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
---------------------------------------------

Labels: , , , , , , ,

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.

Labels: , , , , , , ,

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.

Labels: , , , , , , ,

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.

Labels: , , , , , , ,

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.






















Labels: , , , , , , ,

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:-
--------------------










Labels: , , , , , , ,

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:-
---------------------

































Labels: , , , , , , ,