SAP V1, V2 and V3 Udates

Document update is where the transaction (documents) are updated in the application tables. This update is normally a synchronous update, i.e. if the update does not go through for whaterever reason, the complete transaction is rolled back.

Statistical update is the update of statistics for the transaction – like LIS or extractors for BW.

V1 – synchronous update. If the update is set to V1, then all tables are update and if any one fails, all are rolled back. Done for all transaction plus critical statistics like credit management, etc.

V2 – asynchronous update – transactions are updated and statistical updates are done when the processesor has free resources. If the statistical update fails, the transaction would have still gone through and these failures have to be addressed separately.

V3 – batch update – statistics are updated using a batch (periodic) job like every hour or end of the day. Failure behaviour is same as V2 updates.

Statistical update is also used as to describe the initial setup of the statistical tables for LO/LIS. When old transactions are updated in LO/LIS as a one time exercise, then it is called a statistical update also. Once these tables are upto date will all transactions, then every transaction is updated in them using V1, V2 or V3.

Key Points to remember at the time of Requirement Gathering for BPS Planning

1. What is the hierarchy of the people involved in the planning?
Based on this information, the creation of planning levels and the packages become easier.
Any vertical levels in the hierarchy will typically result in a planning level and any horizontal hierarchy can be converted into planning packages.
However, this is the simplest model I am talking about. The modelling procedure can be different also.

2. Who are the people involved in the planning and what is their area on which they work?
This explains the set of records, each of the person will be working on. Based on this detail, the selection criteria can be designed at the planning level and the planning package.

3. What are the different roles and responsibilities of each of the person?
This explains the authorizations that should be provided to the users.

4. What is the nature of work they do?
This information will be helpful to model different simulation models in BPS.

SAP SEM BPS Planning Application

SAP BPS is used to create planning applications using BW as a source of data. A Transactional/Real-Time InfoCube is created in the BW/BI server to store the planning data.

These Planning Applications are used as a complex analytical tool to make Enterprise wide decision by analysing Actuals and Plan data.

Web Interface Builder and Planning Folder is used to present these Planning Application to the end user in 3.x system.

BEx Analyzer, BEx Web Application Designer is used to create a user interface to present this Planning Application in BI 7.0 system using BEx Query Designer.

SEM BPS Contains Following Planning Applications:

1. Balance Sheet Planning:
This Planning Application helps to produce Income Statement, Balance Sheet and Cash Flow.
Planning Area: Balance Sheet Planning (4BP0001)
InfoCube: Profit, Balance Sheet and Cash Flow Statement Planning (0SEM_C06)

2. Sales and Profit Planning:
Sales and Profit Planning enables the planning of sales and the Revenue.  The Actuals Values from the previous should be the basis for planning following years  Sales (quantity) and Profits.  

3. Cost Center Planning

4. Personnel Planning

5. Sales Planning

6. Investment Planning

7. Liquidity Planning

8. Simplified Resources Planning

SAP Business Object Acquisition : Job prospects skills shortage

I always follow Jon Reeds career advise page to get lastest news on the SAP Skills shortage to position myself to market demand

Please go through this Recommendation by Guru

http://searchsap.techtarget.com/news/column/0,294698,sid21_gci1323799,00.html

Cheers

SAP BI – Data Extraction using DB Connect

Using DB Connect, SAP provided another options for extracting Data from an External Source System.   It enables to extract data from Table/View from the external DBMS.   In order to load the data from these external DBMS into SAP BW Application server; one has to first connect this in SAP BW’s source system and then create DataSource in order to extract data from Table/View.  Once the DataSource is created; rest of the extraction process is similar to typical BI extraction process.

Following are the list of DB Connected Supported DBMS

SAP DB (MaxDB)   (ADA)

Microsoft SQL Server   (MSS)

Oracle  (ORA)

Informix   (INF)

IBM DB2/390  (DB2)

IBM DB2/400   (DB2)

IBM DB2 UDB  (DB2)

Firstly, Create DBMS Source system in Source System folder of Administrative WorkBench(RSA1).  Fill in the following fields

1. DB Connection = (Logical System Name)

2. DMBS =(DBMS name — see above)

3. User Name & DB Password  = (Database username and password)

4. Connection Info = ( database and host name on which database is running)

5. Permanent = (if checked; the SAP workflow will try to re-establish the interrupted connection)

6. Connection Limit = ( number of simultaneous connection to DBMS; 0=max(255), 1=1, 10=10)

7. Connection Optimum.

Create DataSource:   Call Transaction Code RSDBC – Maintenance screen DB Connect: Overview of Tables and Views.  The Following entries should be maintained in this screen.

1. Application Component

2. DataSource Type

3.Transfer

4. Selection

5. Display Data from the Table or View

6. Checking the DataSource

7. Generate DataSource:

SAP BI Demo and screencam from SAP

https://www.sdn.sap.com/irj/sdn/bi?rid=/webcontent/uuid/ba95531a-0e01-0010-5e9b-891fc040a66c

Frequently used TRANSACTION CODE in SAP BI

S.No	Tcode	Description
1	RSA1	Administrator Work Bench
2	RSA11	Calling up AWB with the IC tree
3	RSA12	Calling up AWB with the IS tree
4	RSA13	Calling up AWB with the LG tree
5	RSA14	Calling up AWB with the IO tree
6	RSA15	Calling up AWB with the ODS tree
7	RSA2	OLTP Metadata Repository
8	RSA3	Extractor Checker
9	RSA5	Install Business Content
10	RSA6	Maintain DataSources
11	RSA7	BW Delta Queue Monitor
12	RSA8	DataSource Repository
13	RSA9	Transfer Application Components
	RSBBS	Maintain Query Jumps (RRI Interface)
14	RSD1	Characteristic maintenance
15	RSD2	Maintenance of key figures
16	RSD3	Maintenance of units
17	RSD4	Maintenance of time characteristics
18	RSDBC	DB connect
19	RSDCUBE	Start: InfoCube editing
20	RSDCUBED	Start: InfoCube editing
21	RSDCUBEM	Start: InfoCube editing
22	RSDDV	Maintaining
23	RSDIOBC	Start: InfoObject catalog editing
24	RSDIOBCD	Start: InfoObject catalog editing
25	RSDIOBCM	Start: InfoObject catalog editing
26	RSDL	DB Connect – Test Program
27	RSDMD	Master Data Maintenance w.Prev. Sel.
28	RSDMD_TEST	Master Data Test
29	RSDMPRO	Initial Screen: MultiProvider Proc.
30	RSDMPROD	Initial Screen: MultiProvider Proc.
31	RSDMPROM	Initial Screen: MultiProvider Proc.
32	RSDMWB	Customer Behavior Modeling
33	RSDODS	Initial Screen: ODS Object Processng
	RSDS	Data Source Repository
34	RSIMPCUR	Load Exchange Rates from File
35	RSINPUT	Manual Data Entry
36	RSIS1	Create InfoSource
37	RSIS2	Change InfoSource
38	RSIS3	Display InfoSource
39	RSISET	Maintain InfoSets
40	RSKC	Maintaining the Permittd Extra Chars
41	RSLGMP	Maintain RSLOGSYSMAP
42	RSMO	Data Load Monitor Start
43	RSMON	BW Administrator Workbench
44	RSOR	BW Metadata Repository
45	RSORBCT	BI Business Content Transfer
46	RSORMDR	BW Metadata Repository
47	RSPC	Process Chain Maintenance
48	RSPC1	Process Chain Display
49	RSPCM	Monitor daily process chains
50	RSRCACHE	OLAP: Cache Monitor
51	RSRT	Start of the report monitor
52	RSRT1	Start of the Report Monitor
53	RSRT2	Start of the Report Monitor
54	RSRTRACE	Set trace configuration
55	RSRTRACETEST	Trace tool configuration
56	RSRV	Analysis and Repair of BW Objects
57	SE03	Transport Organizer Tools
58	SE06	Set Up Transport Organizer
59	SE07	CTS Status Display
60	SE09	Transport Organizer
61	SE10	Transport Organizer
62	SE11	ABAP Dictionary
63	SE18	Business Add-Ins: Definitions
64	SE18_OLD	Business Add-Ins: Definitions (Old)
65	SE19	Business Add-Ins: Implementations
66	SE19_OLD	Business Add-Ins: Implementations
67	SE21	Package Builder
68	SE24	Class Builder
69	SE80	Object Navigator
70	RSCUSTA	Maintain BW Settings
71	RSCUSTA2	ODS Settings
72	RSCUSTV*
73	RSSM	Authorizations for Reporting
74	SM04	User List
75	SM12	Display and Delete Locks
76	SM21	Online System Log Analysis
77	SM37	Overview of job selection
78	SM50	Work Process Overview
79	SM51	List of SAP Systems
80	SM58	Asynchronous RFC Error Log
81	SM59	RFC Destinations (Display/Maintain)
82	LISTCUBE	List viewer for InfoCubes
83	LISTSCHEMA	Show InfoCube schema
84	WE02	Display IDoc
85	WE05	IDoc Lists
86	WE06	Active IDoc monitoring
87	WE07	IDoc statistics
88	WE08	Status File Interface
89	WE09	Search for IDoc in Database
90	WE10	Search for IDoc in Archive
91	WE11	Delete IDocs
92	WE12	Test Modified Inbound File
93	WE14	Test Outbound Processing
94	WE15	Test Outbound Processing from MC
95	WE16	Test Inbound File
96	WE17	Test Status File
97	WE18	Generate Status File
98	WE19	Test tool
99	WE20	Partner Profiles
100	WE21	Port definition
101	WE23	Verification of IDoc processing
102	DB02	Tables and Indexes Monitor
103	DB14	Display DBA Operation Logs
104	DB16	Display DB Check Results
105	DB20	Update DB Statistics
106	KEB2	DISPLAY DETAILED INFO ON CO-PA DATA SOURCE R3
107	RSD5	Edit InfoObjects
108	SM66	Global work process Monitor
109	SM12	Display and delete locks
110	OS06	Local Operating System Activity

111	RSKC	Maintaining the Permittd Extra Chars
112	SMQ1	qRFC Monitor (Outbound Queue)

Difference Between Star Schema and Snowflake Schema

Snowflake schema is a variation of Star Schema in which the Dimension tables are normalized to further break down into hierarchy of Dimension tables.  By doing so, the MDM system can utilize space efficiently but it will increase the number of join when retrieving the data from these dimension tables.