CLASS I: ravikiran.sapbi@gmail.com
SAP :
SYSTEMS APPLICATION AND PRODUCTS :
USES :
1. AUTOMATE THE BUSINESS PROCESS.
2. CENTRALISATION OF DATA
DEVELOP AN APPLICATION THROUGH CODING. (PROGRAMMING)
SET OF PROGRAMMS TO AUTOMATE THE BUSINESS IS APPLICATION.
SET OF INSTRUCTIONS.
SAP HAS BEEN DEVELOPED BASED ON A CONCEPT
CALLED ERP.
ENTERPRISE RESOURCE PLANNING :
RES : 4M MEN, MATERIAL, MONEY AND MACHINERY.
ERPS ARE READYMADE APPLICATIONS.
INTEGRATED SUITE OF APPLICATIONS.
SAP R/3 : CONCEPT ERP (UPDATE DAY TO DAY BUSINESS DATA)
REAL TIME 3 TIER ARCHITECTURE.
MODULES OF SAP :
TECHNICAL FUNCTIOANAL NEW DIM
ABAP/4 SD
(DEVELOPER) MM
BASIS PP
(ADMIN) SAPR/3
PM
HR
FI
CO
QC
ABAP : ADVANCED BUSINESS APPLICATION PROGRAMMING.
CUSTOMISATION
ENHANCEMENT
SD
READYMADE .................> GAP CLIENT B.P
BUSINESS PROCESS
ENQUIRY E
QUOTATION Q
ORDERS O
DELIVERY B
BILLING D
BI : BUSINESS INTELLIGENCE
CONCEPT CALLED AS DATA WAREHOUSING
OVERVIEW OF BI :
1. MODELLING : DEVELOPMENT OF OBJECTS IN BI DATA BASE. (TARGET)
2. EXTRACTION : DEVELOPMENT OF LINK FROM SOURCE TO TARGET.
3. REPORTS : GENERATING THE REPORTS BASED ON EXTRACTED DATA.
4. PERFORMANCE TUNING : WHATEVER THE REPORT THAT WE HAVE TO DESIGNED HAS TO BE EXECUTED AS EARLY AS POSSIBLE.
5. BROADCASTING : SENDING THE REPORTS TO CONCERNED END USER.
a) WHEN TO SEND ? (TIME)
b) HOW TO SEND ? (FORMAT : XL, PDF, URL)
c) WHERE TO SEND ? (LOCATION : EMAIL ID, PORTAL)
CLASS II.
1. MODELLING DEVELOPING THE TARGET.
a) INFO OBJECTS : FIELDS
INFO PROVIDERS :
b) INFO CUBES (MDM)
c) DATA STORE OBJECTS (DSOs) (2DM)
d) MULTI PROVIDERS (VIEWS)
e) INFO SETS (JOINS)
INFO PROVIDERS: OBJECTS WHICH SENDS DATA FOR REPORTING
ARE CALLED AS INFO PROVIDERS.
2) EXTRACTION :
DEVELOPING A LINK FROM SOURCE TO TARGET.
a) DATA SOURCE : DEFINES WHAT DATA HAS TO BE EXTRACTED
FROM THE SOURCE.
b) PSA : (PERSISTANT STAGING AREA) 2 DIM TABLE.
STAGING PURPOSE.
c) TRANSFORMATIONS : TO TRANSFORM THE DATA
SCHEDULERS :
d) INFO PACKAGE :
e) DATA TRANSFER PROCESS :
3. REPORTING : BUSINESS EXPLORER
COMBINATION OF 4 APPLICATIONS.
a) ANALYSER : USING ANALYSER WE CAN REPORT IN THE FORM OF
EXCEL SHEET.
I/P FOR ANALYSER : QUERY, INFO PROVIDER
b) QUERY DESIGNER : USING Q.D WE CAN DESIGN THE QUERY ACCORDING TO REQUIREMENTS OF END USER AND WE CAN
EXECUTE IT IN BROWSER.
I/P FOR Q.D IS INFO PROVIDER.
c) REPORT DESIGNER :
WHENEVER WE WANT TO FORMAT THE OUTPUT OF QUERY WE USE
REPORT DESIGNER.
FORMATTED O/P IS CALLED AS CRYSTAL REPORT.
I/P FOR REPORT DESIGNER IS QUERY.
d) WAD (WEB APPLICATION DESIGNER)
1. WE DESIGN THE WEB PAGE.
2. ASSIGN THE I/P FOR THE WEB PAGE. (DATA BINDING)
I/P FOR WAD : QUERY, INFO PROVIDER, QUERY VIEW.
4. PERF TUNING :
a) AGGREGATES
b) COMPRESSION
c) PARTIOTIONS
d) INDEXES
e) LINE ITEM DIMENSION
f) OLAP CACHE
g) BI ACCELERATOR INDEX
5) BROADCASTING : SENDING THE REPORTS TO CONCERNED END USER
a) WHEN TO SEND? (TIME)
b) HOW TO SEND? (FORMAT)
c) WHERE TO SEND ? (LOCATION)
CLASS III.
SAP NETWEAVER :
CONCEPT CALLED E.S.A OR S.O.A
ENTERPRISE SERVICE ARCHITECTUE
SERVICE ORIENTED ARCHITECTURE.
APPLICATION WHICH PROVIDES END TO END SOLUTION OF
BUSINESS IS CALLED AS ESA APPLICATION.
application :
DATA WAREHOUSING WORKBENCH :
TO START USE MENU :
OR TCODE : SHORT CUT RSA1
TYPE RSA1 IN TRANSACTION BAR
DWWB HAS TWO FRAMES
LEFT FRAME
RIGHT FRAME.
LEFT FRAME HAS DIFF TABS
EACH TAB HAS DIFFERENT LEVELS
IN THE RIGHT FRAME IT VIL DISPLAY ALL THE OBJECTS ACC TO WHAT WE SELECT IN THE LEFT FRAME.
FUNCTIONS OF DWWB :
1. MODELLING : WHENEVER WE WANT TO CREATE ANY OBJECT IN
BI WE USE MODELLING TAB.
2. ADMINISTRATION : TO SCHEDULE THE LOADS IN THE BACKGROUND AND TO MONITOR THEM.
3. TRANSPORT CONNECTION :
TO TRANSPORT THE OBJECTS FROM ONE SYSTEM TO ANOTHER.
OBJECTS ARE DEVELOPED IN DEV SYSTEM.
PERFORM UNIT TESTING
SENDING THE OBJECTS TO QUALITY.
CLIENT PERFORMS USER ACCEPTANCY TEST.
SENDING THE OBJECTS TO PRODUCTION
T.C T.C
DEVELOPMENT .............>QUALITY............>PRODUCTION
4. DOCUMENTS : TO DO DOCUMENTAION.
5. BI CONTENT :
THE READYMADE OBJECTS GIVEN IN BI ARE CALLED AS BI
CONTENT OBJECTS.
WHENEVER WE WANT TO USE THESE OBJECTS WE USE BI CONTENT TAB.
ALL BI CONTENT OBJECTS STARTS WITH ZERO.
TRANSLATION :
TO TRANSLATE THE OBJECTS FROM ONE LANGUAGE TO ANOTHER.
META DATA REPOSITRY :
DATA ABOUT DATA IS CALLED AS METADATA.
INFORMATION ABOUT ALL THE OBJECTS.
CLASS IV.
TYPES OF APPLICATIONS :
1. OLTP (ONLINE TRANSACTION PROCESSING) :
AS SOON AS THE BUSINESS TAKES PLACE THIS DATA HAS TO BE UPDATED IMMEDIATELY INTO THE DATA BASE WE USE OLTP
TYPE OF APPLICATIONS.
2.OLAP (ONLINE ANALYTICAL PROCESSING)
08:00 1000................................................>08:00 1000
08:05 5.................................................> 08:05
.................
1005
SAP R/3 BI
EXTRACT
OLTP........................................................>OLAP
1. PRIMARY OPERATION : UPDATE 1. ANALYSE
2. RELEVANCE OF DATA : CURRENT 2. HISTORICAL
3. UPDATION OF DATA :MORE 3. LESS FREQUENTLY
TO DB FREQUENTLY
4. AMOUNT OF DATA 4. HUGE
PER TRANSACTION : SMALL
5. DATA IN THE DB : NORMALISED 5. DENORMALISED
6. NO OF USERS : MORE 6. FEW
7. LEVEL OF ANALYSIS : LESS 7. HIGH
EXTRACTION PROCESS :
UPDATE MODE : IS A PARAMETER WHICH HAS TO BE SET
BEFORE EXTRACTING THE DATA TO BI WHICH DEFINES WHAT
AMOUNT OF DATA HAS TO BE EXTRACTED FROM SOURCE.
TYPES OF UPDATE MODES :
1. FULL UPDATE
2. INITIAL UPDATE
3. DELTA UPDATE
FULL UPDATE : WHENEVER WE USE UPDATE MODE AS FULL UPDATE
AND ONCE WE EXTRACT THE DATA TO BI IT EXTRACTS ENTIRE DATA
FROM SOURCE TO TARGET.
INITIAL UPDATE : SAME AS FULL UPDATE BUT IT VIL MAINTAIN A
POINTER.
DELTA UPDATE : COMPARE TO THAT POINTER IT VIL EXTRACT
ONLY UPDATIONS.
IT EXTRACTS ONLY MODIFIED AND NEWLY ADDED RECORDS
COMPARE TO PREVIOUS LOAD. (ARE CALLED AS LUWS)
LUW'S : LOGICAL UNIT OF WORKS
SAP R/3 BI
INITIAL UPDATE
08:00 1000.......................................................>08:00 1000
DELTA UPDATE
LUWS
09:00 10 MODIFIED ............................> 09:00 10 M
10 NEW 10 N
................. ....................
1010 1010
.........>2011:02:07:09:00:00
DATA BASE DESIGNS :
R/3 DB DESIGN :
R/3 IS CALLED AS A 2 DIM MODEL.
R/3 DATA IS STORED IN THE FORM OF A TABLE.
A TABLE CONSISTS OF ROWS AND COLOUMNS.
EVERY TABLE VIL HAVE FIELDS OR ENTITIES.
FIELD DEFINES PHYSICAL EXISTENCE OF AN OBJECT.
EVERY COL IS FIELD
EACH ROW IS A RECORD.
EVERY TABLE VIL HAVE A PRIMARY KEY.
A PRIMARY KEY IS ONE WHICH IS UNIQUE.
THE COLOUMN WHICH HAS PRIMARY KEY IS CALLED AS KEY COLOUMN.
REST ARE CALLED AS NON KEY COLOUMNS.
AND THE FIELD WHICH IS P.K IS CALLED AS KEY FIELD.
R/3 DB IS DESIGNED BASED ON A CONCEPT CALLED
E-R MODEL : ENTITY RELATIONSHIP MODEL
ANY TRANSACTION TAKES PLACE THIS DATA VIL NOT BE
UPDATED IN A SINGLE TABLE, THE TRANSACTION HAS BEEN
SPLITTED (BASED ON RELATIONSHIP BETWEEN THE ENITIES)
AND UPDATED INTO MULTIPLE TABLES IN ORDER TO AVOID
REDUNDANCY.
CLASS V.
BI CONCEPTS :
1) INFO OBJECTS : FIELD
MODELLING STARTS WITH DEFINING THE INFO OBJECTS.
2) TYPES OF INFO OBJECTS :
a) CHARACTERS
b) KEY FIGURES
c) UNIT CHARACTERS
d) TIME CHARACTERS
KEY FIGURES : THE OBJECTS WHICH WE ANALYSE IN THE REPORTS
HAS TO BE DEFINED AS KEY FIGURES.
KEY FIGURES ARE THE MEASURABLE OBJECTS.
KEY FIGURES ARE ALWAYS NUMERICS.
CHARACTERS : ON WHAT BASIS WE ANALYSE THE KEY FIGURES
ARE NOTHING BUT CHARACTERS.
UNIT CHARACTERS : VIL GIVE VALUE FOR THE KEY FIGURES.
WHEEREVER WE USE A KEY FIGURE A UNIT CHARACTER VIL FOLLOW THE KEY FIGURE.
CNO RVN RUNIT
C1 200 INR
TIME CHARACTERS : VIL HOLD VALUES RELATED TO DOT, YOT, MOT
3) TYPES OF DATA :
a) MASTER DATA
b) TRANSACTION DATA
MASTER DATA : THE DETAILED LEVEL OF INFORMATION OF CHARACTER INFO OBJECT IS CALLED AS MASTER DATA.
THIS DATA IS NOTHING TO DO WITH OCCURENCE OF THE BUSINESS.
MASTER DATA VIL NOT CHANGE FREQUENTLY.
TRANSACTION DATA : DATA RELATED TO OCCURENCE OF THE
BUSINESS IS CALLED AS TRANSACTION DATA.
TRANSACTION DATA CHANGES FREQUENTLY.
4) BEHAVIOUR OF DATA :
a) MASTER DATA : DATA IN THE MASTER TABLE OVERWRITES.
MASTER DATA GIVES PRESENT TRUTH.
CNO ADR
C1 BGL
C1 HYD
------------------------------------------
C1 HYD
b) TRANSACTION DATA : DATA IN THE TRANSACTION TABLE ADDS UP.
TRANSACTION DATA GIVES FACT TRUTH.
CNO BAL
C1 10K
C1 5K
------------------------------------------
C1 15K
NON CUMULATIVE KEY FIGURES :
THESE VIL NOT ADD UP IN THE TRANSACTION TABLE.
DOT END STOCK
07/02 1000
08/02 500
--------------------------------------
5) TYPES OF MASTER DATA :
IT IS CATEGORISED BASED ON HOW WE REPRESENT THE DATA IN THE DATABASE.
MASTER DATA CAN BE REPRESENTED IN 3 WAYS IN BI.
a) ATTRUBITES
b) TEXTS
c) HIERARCHY
ATTRIBUTES : WHENEVER WE REPRESENT MASTER DATA IN SUCH A WAY THAT IF ALL OTHER INFO OBJECTS ARE ENTIRELY DEPENDING ON PRIMARY KEY INFO OBJECT THEN THAT IS CALLED AS ATTRIBTE OF REPRESENTATION.
TEXTS : TEXTS MAINTAINS LANGUAGE AND DESCRIPTION.
HIERARCHY :WHENEVER WE WANT TO REPRESENT MASTER DATA IN LEVEL UPS AND LEVEL DOWNS WE USE HIERARCHY TYPE OF REPRESENTATION.
USING HIERARCHY :
1. DATA STORES REDUNDANTLY WHICH DEGRADES DB PERFORMANCE:
2. EXTRACTION OF HIERARCHY TYPE OF DATA FROM R.3 TO BI
DIRECTLY IS NOT POSSIBLE.
6) TYPES OF TRANSACTION DATA :
1. ACTUAL
2. PLANNED
STEPS OF MODELLING :
1. IDENTIFY THE NUMBER OF INFO OBJECTS TO BE CREATED IN BI.
2. IDENTIFY EACH INFO OBJECT AS WHAT TYPE IT HAS TO BE
CREATED
3. IDENTIFY WHAT TYPE OF DATA WE NEED TO EXTRACT.
4. IDENTIFY WHAT TYPE OF MASTER DATA WE NEED TO EXTRACT.
CLASS VI.
BI DATA BASE DESIGN :
BI IS CALLED AS MULTI DIMENSIONAL MODEL
IN THE CASE OF BI DATA IS STORED IN THE FORM OF CUBE.
DESIGNING THE CUBE IS CALLED AS SCHEMA DESIGN :
1. STAR SCHEMA : BW 1.0,1.1,1.1C, ...>
2.0, 2.1,2.1D....
2. EXTENDED STAR SCHEMA : BIW 3.0, 3.1 3.1C 3.5
BI 7.0
3. SNOW FLAKE SCHEMA : INFORMATICA
4. HYBRID SCHEMA :
CLASS VII.
BI DB DESIGN :
BI IS A MDM.
IN CASE OF BI DATA IS STORED IN THE FORM OF A CUBE.
DESIGNING THE CUBE IS CALLED AS SCHEMA DESIGN.
1. STAR SCHEMA : BW1.0, ........., 2.0
DISADVANTAGES
2. EXTENDED STAR SCHEMA : BIW 3.0, 3.1,.... BIW 3.5, BI7.0
3. SNOW FLAKE SCHEMA
4. HYBRID SCHEMA
STAR SCHEMA :
1. IN THE CASE OF STAR SCHEMA DESIGN FACT TABLE/TRANSACTION TABLE IS KEPT INSIDE THE CUBE.
2. EVEN THE MASTER TABLES ARE ALSO KEPT INSIDE THE CUBE.
3. FACT TABLE AND MASTER TABLE ARE CONNECTED WITH PRIMARYY KEY AND FORIEGN KEY RELATIONSHIP.
4. FOR EVERY DIMENSION OF A CUBE ONE MASTER TABLE IS
LINKED.
FACT TABLE...........> MASTER TABLE
MASTER TABLE...........> DIMENSION
FACT TABLE...........> DIMENSION
CNO RVN MNO RVN
C1 800 M1 600
C2 400 M2 600
----------------------- .....................................
1200 1200
DISADVANTAGES OF STAR SCHEMA :
1. AS THE MASTER TABLE IS INSIDE THE CUBE IT IS NOT REUSABLE
WHICH DEGRADES THE DATABASE PERFORMANCE.
2. PROCESSING TAKES MORE TIME DUE TO ALPHA NUMERIC VALUES IN THE FACT TABLE WHICH DEGRADES THE PROCESSING PERFORMANCE.
3.ANALYSIS IS LIMITED TO 16 CHARACTERS.
EXTENDED STAR SCHEMA :
1. IN THE CASE OF E.S.S THE FACT TABLE IS KEPT INSIDE THE CUBE
WHERE AS MASTER TABLE IS KEPT OUTSIDE THE CUBE.
2. IN ORDER TO IMPROVE THE PROCESSING PERFORMACE SAP HAS COME UP WITH A CONCEPT CALLED SID TECHNOLOGY.
(SURROGATE ID)
SID CONCEPT IS ONLY APPLIED FOR CHARACTERS.
a) WHENEVER WE CREATE A CHARACTER INFO OBJECT SYSTEM VIL GENERATE AN ADDITIONAL TABLE IN THE DB CALLED AS SID TABLE.
b) WHENEVER WE LOAD MASTER DATA SYSTEM VIL GENERATE
A UNIQUE NUMERIC ID CALLED AS SID IN ITS CORRESPONDING
SID TABLE.
3. IN ORDER TO IMPROVE THE ANALYSIS SAP HAS COME UP WITH A CONCEPT CALLED DIMENSIONAL TABLES.
WHENEVER WE WANT TO CREATE A CUBE :
a) SPECIFY THE NUMBER OF DIMENSIONS REQUIRED.
FOR EVERY DIMENSION WE SPECIFY SYSTEM VIL GENERATE ONE DIMENSIONAL TABLE WITHIN THE CUBE.
b) ASSIGN THE CHARACTERS TO DIMENSIONS
A LINK FROM SID TABLE OF THE ASSIGNED CHARACTER TO DIMENSIONAL TABLE IS FORMED IN THE DATA BASE.
DESIGN 1 :
CNO............> DIM1
MNO..............> DIM2
DESIGN 2 :
CNO............>
DIM1
MNO..............>
1D.........>3C
16D..........> 16*3
ANY TABLE MAX FIELDS
256
1 ---------DID
................
255
7 INTERNAL PURPOSE
-----------
248
FOR 1 DIMENSION MAX OF 248 CHARACTERS CAN BE ASSIGNED
FO 16 DIM ....................> 16 *248
MY BUSINESS
100 CUSTOMERS
200 MATERIALES
RELATIONSHIP : CUST...> MATERIAL . 1:M
C1...........>M1
M2
M3
M200
ALL 1:1 ASSIGN IT ONE DIMENSION
1:M ASSIGN IT DIFFERENT DIMENSIONS.
EXTENDED STAR SCHEMA :
1. WHENEVER WE CREATE CHARACTER INFO OBJECT SYSTEM VIL GENERATE MASTER TABLE AND SID TABLE IN THE DATA BASE.
2. WHENEVER WE CREATE INFO CUBE SYSTEM VIL GENREATE
DIMENSIONAL TABLES AND FACT TABLE.
3. WHENEVER WE LOAD MASTER DATA, MASTER TABLE AND SID TABLE ARE FILLED.
4. WHENEVER WE LOAD TRANSACTION DATA, DIMENSIONAL TABLES
AND FACT TABLE ARE FILLED.
CLASS VIII.
EX 1 : LOADING OF MASTER DATA OF TYPE ATTRIBUTES INTO BI
USING MANUAL ENTRY OPERATION :
SOLUTION :
1. CREATE 4 CHAR IO.
2. SPECIFY OTHER3 IO AS ATTRIBUTES TOWARDS CNO.
STEP 1 : CREATION OF INFO AREA
IT IS A FOLDER WHICH IS USED TO SEGGREGATE THE PROJECT.
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE INFO OBJECTS AT THE TOP
CONTEXT MENU (RIGHT CLICK) SELECT CREATE INFO AREA
GIVE NAME AND DESCRUPTION
CONTUNUE.
STEP 2 : CREATION OF INFO OBJECT CATALOGUE.
INFO OBJECT CATALOGUE IS ALSO A FOLDER WHICH IS USED TO
SEGGREGATE THE INFO OBJECTS.
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE INFO AREA (CREATED IN STEP 1)
CONTEXT MENU CREATE INFO OBJECT CATALOGUE
GIVE NAME AND DESCRIPTION
INFO OBJECT TYPE SELECT CHAR
CLICK ON CREATE.
VERSION : DEFINES STATUS OF THE OBJECT W.R.T DATA BASE
TYPES :
1. NEW : WHENEVER WE CREATE ANY OBJECT INITIALLY VERSION VIL BE NEW.
2. ACTIVE : ONCE WE CREATE AN OBJECT WE HAVE TO ACTIVATE THIS OBJECT. ONCE WE ACTIVATE VERSION CHANGES FROM NEW TO ACTIVE.
WE CAN USE THOSE OBJECTS WHICH ARE AVAIALABLE IN ACTIVE VERSION.
3. MODIFIED OR REVISED :
ONCE WE CHANGE THE ACTIVE VERSION OBJECT VERSION CHANGES TO REVISED. AGAIN ACTIVATE THE OBJECT VERSION CHANGES TO ACTIVE.
4. DELIVERED : ALL BI CONTENT (READYMADE) OBJECTS ARE AVAILABLE IN A VERSION CALLED DELIVERED.
STEP 3 : CREATION OF INFO OBJECTS :
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE INFO OBJECT CATALOGUE
CONTEXT MENU CREATE INFO OBJECT.
GIVE NAME AND DESCRIPTION
CLICK ON CONTINUE.
GENERAL TAB :
DATA TYPE : CHAR
LENGTH : 8 (MAX LENGTH CAN BE GIVEN IS 60)
LOWE CASE LETTERS :
CHECK THIS INDICATOR IT ALLOWS BOTH LOWER CASE AND UPPERCASE.
IF NOT ONLY UPPER CASE
CONV ROUTINE : ALPHA
c1
CNO
- - - - - - - -
00001000
WHENEVER WE CREATE A CHAR INFO OBJECT SYSTEM VIL GENREATE 3 TABLES IN THE DATA BASE BY DEFAULT.
1. MASTER DATA TYPE ATTRIBUTES (P TABLE) : /BIC/PYC_CNO
2. MASTER DATA TYPE TEXTS (T TABLE) : /BIC/TYC_CNO
3. SID TABLE (S TABLE) : /BIC/SYC_CNO
NAMING CONVENTION OF TABLES :
ANY TABLE :
STARTS WITH /BIC/P<NAME OF INFO OBJECT>
0 T
S
C - CUST DEFINED
0 - READYMADE
TO SEE THE TABLES : TCODE : SE11
STEP 4 :SPECIFY OTHER INFO OBJECTS AS ATTRIBUTES TOWARDS
PRIMARY KEY INFO OBJECT
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE PRIMARY KEY INFO OBJECT
CLICK ON CHANGE
GO TO ATTRUBUTE TAB
AND SPECIFY THE ATTRIBUTES
STEP 5 : MAINTAIN MASTER DATA MANUALLY
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE PRIMARY KEY INFO OBJECT
CONTEXT MENU MAINTAIN MASTER DATA
CLASS IX.
EX 1 : LOADING OF MASTER DATA OF TYPE ATTRIBUTES INTO BI
USING MANUAL ENTRY OPERATION :
SOLUTION :
1. CREATE 4 CHAR IO.
2. SPECIFY OTHER3 IO AS ATTRIBUTES TOWARDS CNO.
STEP 1 : CREATION OF INFO AREA
IT IS A FOLDER WHICH IS USED TO SEGGREGATE THE PROJECT.
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE INFO OBJECTS AT THE TOP
CONTEXT MENU (RIGHT CLICK) SELECT CREATE INFO AREA
GIVE NAME AND DESCRUPTION
CONTUNUE.
STEP 2 : CREATION OF INFO OBJECT CATALOGUE.
INFO OBJECT CATALOGUE IS ALSO A FOLDER WHICH IS USED TO
SEGGREGATE THE INFO OBJECTS.
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE INFO AREA (CREATED IN STEP 1)
CONTEXT MENU CREATE INFO OBJECT CATALOGUE
GIVE NAME AND DESCRIPTION
INFO OBJECT TYPE SELECT CHAR
CLICK ON CREATE.
VERSION : DEFINES STATUS OF THE OBJECT W.R.T DATA BASE
TYPES :
1. NEW : WHENEVER WE CREATE ANY OBJECT INITIALLY VERSION VIL BE NEW.
2. ACTIVE : ONCE WE CREATE AN OBJECT WE HAVE TO ACTIVATE THIS OBJECT. ONCE WE ACTIVATE VERSION CHANGES FROM NEW TO ACTIVE.
WE CAN USE THOSE OBJECTS WHICH ARE AVAIALABLE IN ACTIVE VERSION.
3. MODIFIED OR REVISED :
ONCE WE CHANGE THE ACTIVE VERSION OBJECT VERSION CHANGES TO REVISED. AGAIN ACTIVATE THE OBJECT VERSION CHANGES TO ACTIVE.
4. DELIVERED : ALL BI CONTENT (READYMADE) OBJECTS ARE AVAILABLE IN A VERSION CALLED DELIVERED.
STEP 3 : CREATION OF INFO OBJECTS :
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE INFO OBJECT CATALOGUE
CONTEXT MENU CREATE INFO OBJECT.
GIVE NAME AND DESCRIPTION
CLICK ON CONTINUE.
GENERAL TAB :
DATA TYPE : CHAR
LENGTH : 8 (MAX LENGTH CAN BE GIVEN IS 60)
LOWE CASE LETTERS :
CHECK THIS INDICATOR IT ALLOWS BOTH LOWER CASE AND UPPERCASE.
IF NOT ONLY UPPER CASE
CONV ROUTINE : ALPHA
c1
CNO
- - - - - - - -
00001000
WHENEVER WE CREATE A CHAR INFO OBJECT SYSTEM VIL GENREATE 3 TABLES IN THE DATA BASE BY DEFAULT.
1. MASTER DATA TYPE ATTRIBUTES (P TABLE) : /BIC/PYC_CNO
2. MASTER DATA TYPE TEXTS (T TABLE) : /BIC/TYC_CNO
3. SID TABLE (S TABLE) : /BIC/SYC_CNO
NAMING CONVENTION OF TABLES :
ANY TABLE :
STARTS WITH /BIC/P<NAME OF INFO OBJECT>
0 T
S
C - CUST DEFINED
0 - READYMADE
TO SEE THE TABLES : TCODE : SE11
STEP 4 :SPECIFY OTHER INFO OBJECTS AS ATTRIBUTES TOWARDS
PRUMARY KEY INFO OBJECT
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE PRIMARY KEY INFO OBJECT
CLICK ON CHANGE
GO TO ATTRUBUTE TAB
AND SPECIFY THE ATTRIBUTES
STEP 5 : MAINTAIN MASTER DATA MANUALLY
RSA1......> MODELLING TAB............> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT THE PRIMARY KEY INFO OBJECT
CONTEXT MENU MAINTAIN MASTER DATA
CLASS X.
BIW 3.5 DATA FLOW :
SOURCE SYSTEM : THE SYSTEM FROM WHICH WE EXTRACT THE DATA TO BIW SYSTEM IS CALLED AS SOURCE SYSTEM.
EG : SAPR/3, FILE, DB, WBA, EXT SYST
INFO SOURCE : DEFINES COMMUNICATION STRUCTURE.
GROUPONG OF LOGICALLY RELATED INFO OBJECTS
IN WHICH FORMAT DATA HAS TO BE LOADED INTO BIW SYSTEM.
DATA SOURCE :
TRANSFER RULES :
UPDATE RULES :
U.R ARE SPECIFIC TO TARGET
T.R ARE GLOABAL TO TARGET.
PSA : PERSISTANT STAGING AREA
PSA IS A 2 D TABLE.
DATA COMING FROM THE SOURCE SYSTEM HAS BEEN STAGED IN BIW SYSTEM AT PSA FOR ERROR HANDLING.
PSA CONSISTS OF RAW DATA
INFO PACKAGE : IS A SCHEDULER
WHICH DEFINES WHEN THE LOAD HAS TO BE TRIGGERED.
SOURCE SYSTEM CONNECTIONS :
CREATING INTERFACE TWO SYSTEMS.
SYSTEM GENERATES IDOCS CALLED AS DATA CONTAINERS
WHICH CARRIES DATA FROM ONE SYSTEM TO ANOTHER.
BIW IS A
E T T L TOOL (EXTRACT TRANSFER TRANSFORM AND LOADING)
TRANSFER METHOD :
DEFINES HOW DATA AND INFORMATION SHOULD BE TRANSFERED
BETWEEN TWO SYSTEMS.
TWO TYPES :
1. PSA :
DATA ...........> DATA IDOCS (PASSES THROUGH PSA)
INFO ..........> INFO IDOCS
2. IDOCS
DATA ...........> DATA IDOCS (NO PSA)
INFO ..........> INFO IDOCS
IN BIW 3.5 PSA IS NOT MANDATORY.
DIFFERENCES BETWEEN BIW 3.5 AND BI 7.0 DATA FLOW :
BIW 3.5 BI7.0
1. INFO SOURCE IS MANDATORY 1. INFO SOURCE IS NOT MANDATORY
2. PSA IS NOT MANDATORY 2. PSA IS MANDATORY
3. TRANSFER RULES AND 3. TRANSFORMATIONS
UPDATE RULES
4. INFO PACKAGE : EXTRACT 4. INFO PACKAGE : EXTRACT
DATA FROM SOURCE SYSTEM DATAFROMSOURCESYSTEM
TO TARGET. TO D.S/PSA.
5. NO CONCEPT OF DTPS 5. DATA TRANSFER PROCESS
EXTRACTS DATA FROM DS/PSA TO TARGET
6. ETTL 6. ETL
DTPS ARE SOURCE AND TARGET SPECIFIC.
STEPS IN BI EXTRACTION :
STEP 1 : DEFINE THE TARGET
STEP 2 : DEFINE THE DATA SOURCE
IT DEFINES WHAT DATA HAS TO BE EXTRACTED FROM THE
SOURCE SYSTEM.
a) IF IT IS A FLAT FILE EXTRACTION DEFINE THE DATASOURCE IN BI SYSTEM ITSELF.
b) IF IT IS OTHER THAN FLAT FILE DEFINE THE DATA SOURCE IN
SOURCE SYSTEM AND REPLICATE IT TO BI SYSTEM.
STEP 3 : CREATE TRANSFORMATIONS
DEFINES HOW DATA HAS TO BE TRANSFORMED FROM DS/PSA TO TARGET.
STEP 4 : CREATE INFO PACKGE
WHICH EXTRACTS DATA FROM SOURCE SYSTEM TO DS/PSA
STEP 5 : CREATE DATA TRANSFER PROCESS
WHICH EXTRACTS DATA FROM DS/PSA TO TARGET.
CLASS XI.
TYPES OF DTPS :
1. STANDARD DTP :
STD DTP VIL PHYSICALLY EXTRACT THE DATA FROM DS/PSA TO TARGET.
STD DTP HAS TO BE SCHEDULED BY THE USER.
2. DIRECT ACCESS DTP :
IT IS USED IN A CONCEPT CALLED VIRTUAL PROVIDER.
VIRTUAL PROVIDERS VIL NOT HOLD DATA PHYSICALLY.
DIRECT ACCESS DTPS VIL DIRECTLY ACCESS THE DATA FROM THE SOURCE SYSTEM AT THE RUN TIME.
D.A DTPS ARE SCHEDULED BY THE SYSTEM ITSELF.
USING V.P IMPROVES DATABASE PERFORMANCE BUT DEGRADES QUERY PERFORMANCE.
GENERALLY WE PREFER D.A DTPS WHEN WE WANT A QUERY ONCE IN A WHILE AND THAT TO REPORT IS RESTRICTED TO A SMALL AMOUNT OF DATA.
3. ERROR DTPS :
WHENEVER WE TRIGGER STD DTP ALL THE SUCEESFUL VALID RECORDS VIL BE UPDATED INTO THE TARGET AND ANY ERROR RECORDS VIL BE UPDATED INTO ERROR STACK.
RECTIFY THE ERROR STACK AND TRIGGER ERROR DTP WHICH EXTRACTS THE DATA FROM ERROR STACK TO TARGET.
4. RDA DTP (REAL TIME DATA ACQUISTION DTP)
WHENEVER WE WANT FREQUENT EXTRACTION WE VIL GO WITH RDA CONCEPT.
USING RDA CONCEPT WE CAN EXTRACT THE DATA AS MINIMUM AS
90 SECONDS TO A MAX OF 90 MINUTES.
IN THE CASE OF RDA CONCEPT WE VIL ASSIGN REAL TIME INFO PACKAGE AND RDA DTP TO A PROCESSOR CALLED DAEMON.
DAEMON CAN BE SCHEDULED IN TWO WAYS :
1. TIME INTERVAL
2. CHANGE OF DATA IN THE SOURCE.
USING RDA DEGRADES THE PROCESSING PERFORMANCE OF THE SOURCE SYSTEM.
RDA IS SUPPORTED ONLY WHEN THE SOURCE IS SAPR/3 OR WEB BASED APPLICATION.
TYPES OF TRANSFORMATIONS :
6 TYPES OF TRANSFORAMTIONS :
4 TRANSFER RULES
a) DIRECT ASSIGNMENT
b) CONSTANT
c) ROUTINE
d) FORMULA
e) NO TRANSFORMATION
f) READ MASTER DATA
NO TRANSFORMATION : WHEENEVER WE DONT WANT TO UPDATE SOME PARTICULAR OBJECT IN THE TARGET WE USE NO TRANSFORMATION.
READ MASTER DATA :
THIS TYPE OF TRANSFORMATION CAN BE USED ONLY IF MASTER DATA IS ALREADY AVAILABLE.
WHENEVER WE WANT TO READ MASTER DATA FROM ONE TABLE AND UPLOAD IT INTO ANOTHER TABLE WE USE READ MASTER DATA TYPE OF TRANSFORMATION.
INFO SOURCE IS MANDATORY IN TWO SCENARIOS :
1. WHEN WE WANT DOUBLE TRANSFORMATIONS.
2. WHEN WE HAVE MULTIPLE SOURCES AND A SINGLE TARGET
OR SINGLE SOURCE MULTIPLE TARGETS
CLASS XII.
fEX 2 : LOADING OF MASTER DATA OF TYPE ATTRIBUTES INTO BI FROM A FLAT FILE.
BI SUPPORTS TWO TYPES OF FILE FORMATS.
1) .CSV (COMMA SEPERATED VALUE)
2) ASCII FILES
CREATION OF SOURCE SYSTEM CONNECTION :
RSA1.........> MODELLING TAB...........> SOURCE SYSTEM LEVEL
IN THE RIGHT FRAME SELECT FILE CLICK ON CREATE.
STEP 1 : DEFINE THE TARGET
PERFORM EX1 UNTIL STEP 4
TGT :INFO OBJECT (YC_CNO)
SEGGREGATE BETWEEN THE TARGETS (ATTRIBUTE OR TEXTS)
INSERT CHARACTER AS INFO PROVIDER
RSA1.........> MODELLING TAB..............> INFO PROVIDER LEVEL
IN THE RIGHT FRAME SELECT INFO AREA CONTEXT MENU
SELECT INSERT CHAR AS INFO PROVIDER.
GIVE THE NAME OF P.KEY INFO OBJECT
CONTINUE
TGT IS READY : ATTRIBUTES YC_CNO
STEP 2 : DEFINE THE DATA SOURCE.
DEFINES WHAT DATA HAS TO BE EXTRACTED FROM THE SOURCE SYSTEM.
STEP 2a) CREATION OF APPLICATION COMPONENT
IS A FOLDER WHICH IS USED TO SEGGREGATE THE DATA SOURCES.
RSA1..........> MODELLING TAB.............> DATA SOURCE LEVEL
IN THE RIGHT FRAME CHOOSE SOURCE SYSTEM
SELECT DATA SOURCES AT THE TOP
CONTEXT MENU CREATE APP COMP
GIVE NAME AND DESCRIPTION
STEP 2b) CREATION OF DATA SOURCE
RSA1..........> MODELLING TAB.............> DATA SOURCE LEVEL
IN THE RIGHT FRAME SELECT APP COMP (CREATED IN STEP 2a)
CONTEXT MENU CREATE DATA SOURCE
NAME : YDS_CNO
S.S :
DATA TYPE OF DS : SELECT MASTER DATA TYPE ATTRIBUTES.
CONTINUE
GENERAL TAB :
GIVE THE DESCRIPTION
EXTRACTION TAB :
DELTA PROCESS : DELTA BY FULL UPLOAD
DIRECT ACCESS :
NO DTP ALLOWED FOR DIRECT ACCESS : (STD DTP)
ALLOWED : DIRECT ACCESS DTP
REAL TIME : RDA CONCEPT IS NOT SUPPORTED.
ADAPTER: LOAD TEXT TYPE OF FILE FROM LOCAL W.S
NAME OF FILE :
HDR ROWS TO BE IGNORED : 1
DATA FORMAT :
SEPERATOR : ,
ESCAPE SIGN : ;
PROPOSAL TAB : CLICK ON LOAD EXAMPLE DATA
FIELDS TAB :
COPY THE PROPERTIES OF TARGET INFO OBJECT TO THE FIELDS
OF THE DATA SOURCE USING TEMPLATE INFO OBJECT.
cLASS 13.
EX 2 : LOADING OF MASTER DATA OF TYPE ATTRIBUTES INTO BI FROM A FLAT FILE.
BI SUPPORTS TWO TYPES OF FILE FORMATS.
1) .CSV (COMMA SEPERATED VALUE)
2) ASCII FILES
CREATION OF SOURCE SYSTEM CONNECTION :
RSA1.........> MODELLING TAB...........> SOURCE SYSTEM LEVEL
IN THE RIGHT FRAME SELECT FILE CLICK ON CREATE.
STEP 1 : DEFINE THE TARGET
PERFORM EX1 UNTIL STEP 4
TGT :INFO OBJECT (YC_CNO)
SEGGREGATE BETWEEN THE TARGETS (ATTRIBUTE OR TEXTS)
INSERT CHARACTER AS INFO PROVIDER
RSA1.........> MODELLING TAB..............> INFO PROVIDER LEVEL
IN THE RIGHT FRAME SELECT INFO AREA CONTEXT MENU
SELECT INSERT CHAR AS INFO PROVIDER.
GIVE THE NAME OF P.KEY INFO OBJECT
CONTINUE
TGT IS READY : ATTRIBUTES YC_CNO
STEP 2 : DEFINE THE DATA SOURCE.
DEFINES WHAT DATA HAS TO BE EXTRACTED FROM THE SOURCE SYSTEM.
STEP 2a) CREATION OF APPLICATION COMPONENT
IS A FOLDER WHICH IS USED TO SEGGREGATE THE DATA SOURCES.
RSA1..........> MODELLING TAB.............> DATA SOURCE LEVEL
IN THE RIGHT FRAME CHOOSE SOURCE SYSTEM
SELECT DATA SOURCES AT THE TOP
CONTEXT MENU CREATE APP COMP
GIVE NAME AND DESCRIPTION
STEP 2b) CREATION OF DATA SOURCE
RSA1..........> MODELLING TAB.............> DATA SOURCE LEVEL
IN THE RIGHT FRAME SELECT APP COMP (CREATED IN STEP 2a)
CONTEXT MENU CREATE DATA SOURCE
NAME : YDS_CNO
S.S :
DATA TYPE OF DS : SELECT MASTER DATA TYPE ATTRIBUTES.
CONTINUE
GENERAL TAB :
GIVE THE DESCRIPTION
EXTRACTION TAB :
DELTA PROCESS : DELTA BY FULL UPLOAD
DIRECT ACCESS :
NO DTP ALLOWED FOR DIRECT ACCESS : (STD DTP)
ALLOWED : DIRECT ACCESS DTP
REAL TIME : RDA CONCEPT IS NOT SUPPORTED.
ADAPTER: LOAD TEXT TYPE OF FILE FROM LOCAL W.S
NAME OF FILE :
HDR ROWS TO BE IGNORED : 1
DATA FORMAT :
SEPERATOR : ,
ESCAPE SIGN : ;
PROPOSAL TAB : CLICK ON LOAD EXAMPLE DATA
FIELDS TAB :
COPY THE PROPERTIES OF TARGET INFO OBJECT TO THE FIELDS
OF THE DATA SOURCE USING TEMPLATE INFO OBJECT.
CLASS 14.
ERROR HANDLING :
1. RECTIFY THE DATA IN THE ERROR STACK.
SELECT THE DTP
GO TO MONITOR
SELECT THE LOAD WHICH HAS FAILED
CLICK ON EROR STACK
CHANGE THE DATA.
STEP 2 : TRIGGER ERROR DTP :
GO TO STD DTP
UPDATE TAB
CLICK ON CREATING ERROR DTPS
CLASS 15.
CREATION OF KEY FIGURES.
PRICE UNIT CHARACTER
100 INR
200 USD
300 EUR
WHENEVER WE WANT TO CREATE A KEY FIGURE
FIRST WE HAVE TO CREATE A UNIT CHARACTER
PRICE UNIT CHARACTER
100 INR
200 INR
300 INR
1. FIXED UNIT : IF UNIT IS FIXED NO NEED TO CREATE
A UNIT CHAR.
2. VARIABLE UNITS : CREATE A UNIT CHARACTER
PRICE UNIT CHARACTER
100 INR
200 USD
300 EUR
UNIT CHARACTERS :
a) CURRENCY
b) UNIT OF MEASURE
EITHER WE CAN CREATE A UNIT CHARACTER INFO OBJECT
OR WE CAN USE A READYMADE UNIT CHARACTERS.
1) 0CURRENCY : CURRENCY
2) 0UNIT : UNIT OF MEASURE
PRC 0CURRENCY
100 INR
200 USD
300 EUR
EVEN THOUGH WE CREATE A UNIT CHARACTER IT IS DESIGNED SUCH A WAY THAT IT ALWAYS GETS THE REFERENCE FROM
0CURRENCY
PRC 0CURRENCY RVN
100 INR 200 INR
200 USD 300 USD
300 EUR 400 EUR
2 KEY FIGURES USED IN SAME INFO PROVIDER
SAME UNIT VALUES
WE CAN USE SAME UNIT CHARACTERS.
PRC 0CURRENCY RVN YU_UNIT
100 INR 200 USD
200 USD 300 INR
300 EUR 400 EUR
2 KEY FIGURES USED IN SAME INFO PROVIDER
DIFFERENT UNIT VALUES
WE CAN USE DIFFERENT UNIT CHARACTERS.
2 KEY FIGURES USED IN DIFFERENT INFO PROVIDERS
SAM OR DIFF UNIT VALUES WE CAN USE THE SAME UNIT CHARACTER.
CREATION OF UNIT CHARACTER :
TCODE : RSD1
CREATE ANY INFO OBJECT.
IF WE CREATE OBJECT FROM RSD1 IT VIL BE UNDER INFO AREA CALLED UNASSIGNED NODES.
SELECT UNIT
GIVE NAME
CLICK ON CREATE
CREATION OF KEY FIGURES :
RSA1..........> MODELLING TAB................> INFO OBJECT LEVEL
IN THE RIGHT FRAME SELECT KEY FIGURE CATALOGUE
CONTEXT MENU CREATE INFO OBJECT
PRC
100.56
CNO RVN
C1 100
C1 200
---------------------------
C1 300
MNO PRC
M1 100
M1 150
.............................
IT IS NOT POSSIBLE TO CREATE A INFO OBJECT OF TYPE
TIME CHARACTERS.
THE ONLY ONE OBJECT WHICH WE CANNOT CREATE IN BI IS TIME
CHARACTER.
CLASS 16.
creation of info cube :
CUBE IS AN INFOPROVIDER AS WELL AS DATA TARGET.
OBJECTS WHICH SENDS DATA FOR REPORTING ARE CALLED AS INFO PROVIDERS.
OBJECTS TO WHICH WE CAN LOAD DATA ARE CALLED AS DATA TARGETS.
TYPES OF INFO CUBES :
a) WITH PHYSICAL DATA STORE
1) STANDARD INFO CUBE : FOR A STD INFO CUBE WE CANNOT LOAD
DATA MANUALLY. PLANNING IS NOT ALLOWED.
2) REAL TIME INFO CUBE : FOR A REAL TIME INFO CUBE WE CAN
LOAD DATA MANUALLY. PLANNING IS ALLOWED
(TRANSACTION INFO CUBES IN BIW 3.5)
b)WITHOUT PHYSICAL DATA STORE
(VIRTUAL PROVIDER)
1) BASED ON DTP FOR DIRECT ACCESS :
WHEN WE REMOTELY ACCESSING THE DATA FROM SAP OR FILE AS SOURCE SYTEM.
2) BASED ON BAPI :
WHEN WE REMOTELY ACCESSING THE DATA FROM NON SAP AS SOURCE SYTEM.
3) BASED ON FUNCTIONAL MODULE :
USER DEFINED FM IS THE DATA SOURCE.
CREATION OF INFO CUBE :
RSA1.............> MODELLING TAB................> INFO PROVIDER LEVEL
IN THE RIGHT FRAME SELECT UR INFO AREA CONTEXT MENU
CREATE INFO CUBE.
GIVE NAME AND DESCRIPTION :
SELECT INFO PROVIDER TYPE
CREATE.
OUT OF 16 DIMENSIONS IN A CUBE 3 ARE CALLED AS FIXED DIMENSIONS.
1. DATA PACKAGE : (CUBE NAME P)
BY DEFAULT ALL THE TECHNICAL OBJECTS ARE ASSIGNED TO DATA PACKAGE DIMENSION.
TECHNICAL OBJECT IN THE CUBE IS REQUEST ID.
2. TIME : (CUBE NAME T)
ALL THE TIME CHARACTERS HAS TO BE ASSIGNED TO TIME DIMENSION.
3. UNIT (CUBE NAME U)
ALL THE UNIT CHARACTERS HAS TO BE ASSIGNED TO UNIT
DIMENSION
STEP 1 : CREATION OF DIMENSIONS
SELECT THE DIMENSIONS
RIGHT CLICK CREATE NEW DIMENSIONS.
STEP 2 : ASSIGN THE CHARACTERS TO DIMENSIONS
LEFT FRAME USE A TEMPLATE :
STEP 3 :ASSIGN THE KEY FIGURES TO KEY FIGURES FOLDER.
BACK END :
TO SEE THE SCHEMA DESIGN :
TCODE : LISTSCHEMA
CLASS 17.
EX : 4
LOADING OF TRANSACTION DATA INTO INFO CUBE FROM A FLAT FILE.
TO ACEES THE FILE IN THE SERVER
TCODE : AL11
APPLICATION DIRECTOTRIES.
DIR_HOME
STEP 1 : DEFINE THE TARGET
PERFORM CREATION OF CUBE EXERCISE :
YIC_DEMO
STEP 2 : CREATION OF DATA SOURCE
RSA1......> MODELLING TAB..............> DATA SOURCE LEVEL
IN THE RIGHT FRAME SELECT THE APP COMP
CONTEXT MENU CREATE DATA SOURCE.
EXTRACTION
ADAPTER :
CREATE ROUTINE FOR FILE NAME : TO PICK THE FILE FROM THE SERVER DYNAMICALLY.
FILE NAMES :
TDATA_20110227.CSV : YEST FILE
TDATA_20110228.CSV : TODAYS FILE
TDATA_20110301.CSV : TOMMOROWS FILE
DATA :STR1 TYPE C (60) LIKE D:\usr\sap\DEV\DVEBMGS00\work\TDATA_.
DATA : STR2 TYPE D (8) LIKE SY_DATUM.
DATA : STR3 TYPE C (4) LIKE .CSV.
P_FILE NAME = CONCATENATE STR1 STR2 STR3.
STEP 3 : CREATION OF TRANSFORMATIONS :
SOURCE : DS/PSA YDS_DEMO
TARGET : INFO CUBE YIC_DEMO
RSA1......> MODELLING TAB..............> DATA SOURCE LEVEL
IN THE RIGHT FRAME SELECT THE DATA SOURCE CONTEXT MENU
CREATE TRANSFORMATION
APPLY TRANSFORMATIONS.
RULE GROUPS :
WHENEVER WE WANT MULTIPLE SETS OF TRANSFORMATIONS WE USE RULE GROUPS.
CNO MNO PRC QTY RVN
(P*Q)
RG1 C1 M1 100 2 200
C2 M2 200 3 600
C3 M3 300 1 300
CNO MNO PRC QTY RVN
(P*Q*0.9)
RG2 C4 M4 400 2 720
C5 M5 500 3 1350
START ROUTINE :
EXECUTES BEFORE EXECUTION OF TRANSFORMATION.
ANY LOGIC TO BE APPLIED BEFORE EXECUTION OF TRANSFORMATION USE START ROUTINE.
END ROUTINE :
EXECUTES AFTER EXECUTION OF TRANSFORMATION.
ANY LOGIC TO BE APPLIED AFTER EXECUTION OF TRANSFORMATION USE END ROUTINE.
EXPERT ROUTINE :
DELETE ALL THE TRANSFORMATIONS.
WE HAVE TO WRITE ABAP CODE TO SPECIFY HOW DATA HAS TO GO FROM DS/PSA TO TARGET.
step 4 : CREATION OF INFO PACKAGE.
RSA1......> MODELLING TAB..............> DATA SOURCE LEVEL
IN THE RIGHT FRAME SELECT THE DATA SOURCE CONTEXT MENU
CREATE INFO PACKAGE
STEP 5 :TRIGGER DTP
RSA1.....> MODELLING TAB..........> INFO PROVIDER LEVEL
IN THE RIGHT FRAME SELECT THE TARGET
EXPAND IT AND DOUBLE CLICK ON DTPS.
EXTRACTION TAB :
SEMANTIC GROUPS :
DEFINES WHAT RECORDS HAS TO BE WRITTEN TO ERROR STACK.
SELECTION OF KEY FIELDS FOR ERROR STACK.
CNO MNO RVN (CNO AS SEMANTIC KEY)
#C1 M1 100 ................> ERROR STACK
C1 M2 200 ....................> E.S
C1 M3 300 ......................> E.S
C2 M2 400 ...........................> TARGET
C2 M3 500 ...........................> TARGET
CNO MNO RVN (CNO,MNO AS SEMANTIC KEY)
#C1 M1 100 ................> ERROR STACK
C1 M2 200 ....................> TARGET
C1 M3 300 ......................> TARGET
C2 M2 400 ...........................> TARGET
C2 M3 500 ...........................> TARGET
THE LARGER THE SEMANTIC KEYS THE LESS SIZE OF ERROR STACK.
CLASS 18.
TO SEE THE CONTENTS OF INFO CUBE :
SELECT THE CUBE CLICK ON MANAGE
GO TO CONTENTS TAB
DATA IN THE CUBE CAN BE HANDLED W.R.T REQUEST ID.
FACT TABLE 'F' IS PARTITIONED BASED ON REQUEST ID.
HOW TO SEE THE PARTITION :
TCODE : SE14
FILE............................................................................>CUBE
1) 10 REC
CNO MNO PRC QTY RVN.........................>CNO MNO PRC QTY RVN
C1 M1 100 2 200 C1 M1 100 2 200
2) 2 REC
C1 M1 100 5 500 C1 M1 100 5 500
........................................................... ............................................................
C1 M1 100 5 500 C1 M1 100 7 700
THIS PROBLEM IS HAPPENING AS MY DATA SOURCE IS NOT MAINTIANIG THE REFERENCE IN THE FORM OF IMAGES.
IF THE DATA SOURCE IS NOT MAINTAINING THE REFERENCE IN THE
FORM OF IMAGES, LOAD DATA TO DATA STORE OBJECT.
DSO VIL MAINTAIN THE IMAGES FROM DSO LOAD DATA TO INFO
CUBE.
IMAGES : IMAGES ARE THE REFERENCE MAINTAINED BY THE SYSTEM TO UNDERSTAND WHAT TYPE OF RECORD IS THAT.
TYPES :
1. NEW IMAGE 'N'
2. BEFOR IMAGE 'X'
3. AFTER IMAGE '-' (BLANK)
NEW IMAGE : ANY RECORD WHICH ENTERS THE DSO FOR THE FIRST TIME VIL BE MARKED AS 'N' (NEW IMAGE)
WHENEVER WE LOAD A MODIFIED RECORD LUW TO DSO IT TAKES AS TWO RECORDS.
1) BEFORE IMAGE : BEFORE CHANGING WHAT IS THE VALUE
SAME REC AS 'N' BUT KEY FIGURES BEING MULTIPLIED WITH -1.
2) AFTER IMAGE : AFTER CHANGING WHAT IS THE VALUE
FILE....................................>DSO (IMAGES).......................>CUBE
C1 M1 100 2 200...........>C1 M1 100 2 200 'N'..........>C1 M1 100 2 200
C1 M1 100 5 500 .........>C1 M1 -100 -2 -200 'X'.........> C1 M1 0 3 300
......................................... C1 M1 100 5 500 '-' .....................................
C1 M1 100 5 500 C1 M1 100 5 500
C6 M2 200 1 200 C6 M2 200 1 200 'N' C6 M2 200 1 200
DSO : DATA STORE OBJECT
DSO IS A 2 DIMENSIONAL TABLE
DSO IS A INFO PROVIDER AS WELL AS DATA TARGET.
WHENEVER WE CREATE A DSO SYSTEM VIL GENERATE 3 TABLES BY DEFAULT.
1. NEW DATA TABLE
2. ACTIVE DATA TABLE
3. CHANGE LOG TABLE
WHENEVER WE LOAD DATA TO DSO DATA ENTERS NEW DATA TABLE FIRST.
WHENEVER WE LOAD DATA TO THE CUBE FROM DSO
a) WITH FULL UPDATE : DATA COMES FROM ACTIVE DATA TABLE OF DSO.
b) WITH DELTA UPDATE : DATA COMES FROM CHANGE LOG TABLE
OF DSO.
CHANGE LOG TABLE OF DSO VIL MAINTAIN THE IMAGES.
WHENEVER WE EXECUTE A QUERY ON DSO DATA COMES FROM ACTIVE DATA TABLE OF DSO.
ACTIVATION OF DATA IN DSO :
WHENEVER WE ACTIVATE THE DATA IN DSO DATA VIL MOVE FROM
NEW DATA TABLE TO ACTIVE DATA TABLE AND CHANG LOG
TABLE.
IF WE DONT ACTIVATE THE DATA IN DSO THIS REQUEST VIL NOT BE AVIALABLE FOR REPORTING.
IP..........>DTP1................>A.D. IN DSO.........................>DTP2
PSA N.D.T OF N.D.T.....>A.D.T CUBE
DSO .....>C.L.T
CLASS 19.
EX :
LOADING OF TRANSACTION DATA INTO INFO CUBE FROM A FLAT FILE THROUGH DSO.
STEPS :
1. CREATION OF DSO
2. CREATION OF DATASOURCE
3. CREATE TRANSFORMATION
SOURCE : DS/PSA
TARGET : DSO
4. CREATION OF INFO CUBE
5. CREATION OF TRANSFORMATION
SOURCE : DSO
TARGET : CUBE
6. TRIGGER INFO PACKAGE
EXTRACTS DATA FROM DS/PSA TO TARGET
7. TRIGGER DTP1
EXTRACTS DATA FROM DS/PSA TO N.D.T OF DSO
8. ACTIVATE THE DATA IN DSO.
DATA VIL MOVE FROM N.D.T TO A.D.T AND C.L.T
9. TRIGGER DTP2
EXTRACTED FROM DSO TO CUBE.
TO SEE THE CONTENTS OF INFO CUBE :
SELECT THE CUBE CLICK ON MANAGE
GO TO CONTENTS TAB
DATA IN THE CUBE CAN BE HANDLED W.R.T REQUEST ID.
FACT TABLE 'F' IS PARTITIONED BASED ON REQUEST ID.
HOW TO SEE THE PARTITION :
TCODE : SE14
FILE............................................................................>CUBE
1) 10 REC
CNO MNO PRC QTY RVN.........................>CNO MNO PRC QTY RVN
C1 M1 100 2 200 C1 M1 100 2 200
2) 2 REC
C1 M1 100 5 500 C1 M1 100 5 500
........................................................... ............................................................
C1 M1 100 5 500 C1 M1 100 7 700
THIS PROBLE IS HAPPENING AS MY DATA SOURCE IS NOT MAINTIANIG THE REFERENCE IN THE FORM OF IMAGES.
IF THE DATA SOURCE IS NOT MAINTAINING THE REFERENCE IN THE
FORM OF IMAGES, LOAD DATA TO DATA STORE OBJECT.
DSO VIL MAINTAIN THE IMAGES FROM DSO LOAD DATA TO INFO
CUBE.
IMAGES : IMAGES ARE THE REFERENCE MAINTAINED BY THE SYSTEM TO UNDERSTAND WHAT TYPE OF RECORD IS THAT.
TYPES :
1. NEW IMAGE 'N'
2. BEFOR IMAGE 'X'
3. AFTER IMAGE '-' (BLANK)
NEW IMAGE : ANY RECORD WHICH ENTERS THE DSO FOR THE FIRST TIME VIL BE MARKED AS 'N' (NEW IMAGE)
WHENEVER WE LOAD A MODIFIED RECORD LUW TO DSO IT TAKES AS TWO RECORDS.
1) BEFORE IMAGE : BEFORE CHANGING WHAT IS THE VALUE
SAME REC AS 'N' BUT KEY FIGURES BEING MULTIPLIED BU -1.
2) AFTER IMAGE : AFTER CHANGING WHAT IS THE VALUE
FILE....................................>DSO (IMAGES).......................>CUBE
C1 M1 100 2 200...........>C1 M1 100 2 200 'N'..........>C1 M1 100 2 200
C1 M1 100 5 500 .........>C1 M1 -100 -2 -200 'X'.........> C1 M1 0 3 300
......................................... C1 M1 100 5 500 '-' .....................................
C1 M1 100 5 500 C1 M1 100 5 500
C6 M2 200 1 200 C6 M2 200 1 200 'N' C6 M2 200 1 200
DSO : DATA STORE OBJECT
DSO IS A 2 DIMENSIONAL TABLE
DSO IS A INFO PROVIDER AS WELL AS DATA TARGET.
WHENEVER WE CREATE A DSO SYSTEM VIL GENERATE 3 TABLES BY DEFAULT.
1. NEW DATA TABLE
2. ACTIVE DATA TABLE
3. CHANGE LOG TABLE
WHENEVER WE LOAD DATA TO DSO DATA ENTERS NEW DATA TABLE FIRST.
WHENEVER WE LOAD DATA TO THE CUBE FROM DSO
a) WITH FULL UPDATE : DATA COMES FROM ACTIVE DATA TABLE OF DSO.
b) WITH DELTA UPDATE : DATA COMES FROM CHANGE LOG TABLE
OF DSO.
CHANGE LOG TABLE OF DSO VIL MAINTAIN THE IMAGES.
WHENEVER WE EXECUTE A QUERY ON DSO DATA COMES FROM ACTIVE DATA TABLE OF DSO.
ACTIVATION OF DATA IN DSO :
WHENEVER WE ACTIVATE THE DATA IN DSO DATA VIL MOVE FROM
NEW DATA TABLE TO ACTIVE DATA TABLE AND CHANG LOG
TABLE.
IF WE DONT ACTIVATE THE DATA IN DSO THIS REQUEST VIL NOT BE AVIALABLE FOR REPORTING.
IP..........>DTP1................>A.D. IN DSO.........................>DTP2
PSA N.D.T OF N.D.T.....>A.D.T CUBE
DSO .....>C.L.T
DATA IN THE ACTIVE DATA TABLE OVERWRITES.
ADVANTAGES OF DSO :
1. TO MAINTAIN THE IMAGES
2. TO UTILISE OVER WRITE FUNCTIONALITY
3. ACTS AS A BACKUP
4. DETAILED LEVEL OF ANALYSIS
5. RECONCILATION
CHECK WHETHER DATA COMING FROM THE SOURCE IS
SAME OR NOT.
TYPES OF DSOS :
1. STANDARD DSO :
IT HAS 3 TABLES N.D.T, A.D.T, C.L.T
2. DIRECT UPDATE DSO : FOR A DIRECT UPDATE DSO WE CAN UPDATE THE DATADIRECTLY.
IT IS USED IN PLANNING AND MINING APPLICATIONS.
IT HAS ONLY ONE TABLE i.e; ACTIVE DATA TABLE.
3. WRITE OPTIMISED DSO
WHEN OUR UPDATE HAS TO STOP AT DSO LEVEL ITSELF WE USE WRITE OPTIMISED DSO.
IT HAS ONLY ONE TABLE , ACTIVE DATA TABLE.
USING W.O DSO WE CAN IMPROVE THE PERFORMANCE
AS WE NEED NOT ACTIVATE THE DATA IN DSO.
IN BIW 3.5 ONLY TWO TYPES OF ODS :
1. STD ODS
2. TRANSACTIONAL ODS (DIRECT UPDATE DSO)
CLASS 20.
LOADING OF TRANSACTION DATA INTO INFO CUBE FROM A FLAT FILE THROUGH DSO
STEP 1 : CREATION OF DSO
RSA1...........> MODELLING TAB...............> INFO PROVIDER LEVEL
IN THE RIGHT FRAME SELECT THE INFO AREA CONTEXT MENU
CREATE DATA STORE OBJECT.
GIVE NAME AND DESCRIPTION :
SETTINGS
1. Type of DataStore Object : STD
2. SIDs Generation upon Activation : CHECK
3. Unique Data Records : DONT CHECH THIS
IF WE SELECT THIS INDICATOR IT VIL ALLOW US TO LOAD ONLY NEW RECORDS TO DSO.
4. Set Quality Status to 'OK' Automatically : CHECK THIS
TO SET THE AM STATUS FROM YELLOW TO GREEN
5. Activate Data Automatically :
IF WE SELECT THIS WE NEED NOT ACTIVATE THE DATA IN DSO.
TO SELECT IT 4TH SETTING IS MANDATORY.
6. Update Data Automatically :
PLACE THE PRIMARY KEY FIELDS
UNDER KEY FIELDS
REST UNDER DATA FIELDS
DATA IN THE ACTIVE TABLE OVERWRITES BASED ON KEY FIELDS.
CNO MNO ( CNO AS KEY FIELD)
C1 M1
C1 M2
-----------------------
C1 M2
CNO MNO ( CNO,MNO AS KEY FIELD)
C1 M1
C1 M2
ACTIVATE.
FRONT END WE ARE CREATING A DSO
BUT INTERNALLY IN THE DATABASE IT GENERATES 3 TABLES
AND ONE DATA SOURCE ALSO.
NAMING CONVENTION :
1. NEW DATA TABLE: /BIC/A<DSONAME>40
2. ACTIVE DATA TABLE : /BIC/A<DSONAME>00
3. CHANGE LOG TABLE : /BIC/B<10DIGIT RANDOM NUMBER>
4. DATA SOURCE : 8<DSONAME>
STEP 2 :CREATION OF DATA SOURCE :
STEP 3 :CREATION OF TRANSFORAMATIONS :
SOURCE : DS/PSA
TARGET : DSO
STEP 4 : CREATION OF INFO CUBE.
STEP 5 : CRATION OF TRANSFORMATION
SOURCE : DSO
TARGET : INFO CUBE
STEP 6 : CRATION OF INFOPACKAGE.
STEP 7 : TRIGGER DTP1
SELECT THE DSO EXPAND IT AND DOUBLE CLICK ON DTP
STEP 8 : ACTIVATE DATA IN DSO :
SELECT THE DSO CLICK ON MANAGE
ACTIVATE DATA
STEP 9 : TRIGGER DTP2
SELECT THE CUBE EXPAND AND DOUBLE CLICK ON DTPS.
No comments:
Post a Comment