MODELLING & ADVANCED MODELLING

Info Area:It is a folder where we can organize our project.

We can create IA inside IA. Info Object Catalog:It is a container 4 maintain more number of objects which are same type. We have two types of catalogs 1)Characteristic. 2)Key Figure.

CHARACTERISTIC CATALOG

KEY FIGURE CATALOG

Info Object:It is an entity for maintain the data. It is 2 types 1)Characteristics: Object which is used to analyze data. 2)Key Figure: Object which is used to perform calculation.

Characteristics:

Key Figure

10

11

12

13

14

Types Of Characteristics:We have 3 types of characteristics 1)UNIT CHARACTERISTC It(Standard/Customized) maintains the units/currency In case of customized it takes reference from 0unit/0currency We can create unit char in 2 ways a)in T-code:RSD1

b)Create under not-assigned units catalog.

15

16

b)Create under not-assigned units catalog.

17

2)TIME CHARACTERISTC It maintains the details of time like date, month, year, week, quarter. We can create time char in char as well as kf 3)TECHNICAL CHARACTERISTC It maintains all technical details like a)Request-id b)Data Packet Number c)Partition Number d)Record Number

Master Data:It contains detailed information about the object. It mainly contains 3 tables. 1)Attribute Table. 2)Text Table. 3)Hierarchy Table. a)Text Table: It will helps u to maintain the object info in multiple LANGUAGES. It contains ATTRIBUTE KEY,LANGUAGE KEY,DESCRIPTION(SHORT,MEDIUM,LONG). The naming convention of Text table is /BIC/T(INFO OBJ NAME).

18

b)Hierarchy Table:It maintains the parent-child relationship between diff attributes. If we r going 2 maintain the hierarchy on any obj that obj is in leaf level(lower level). Highest level of node is parent node. Max num of nodes are 98. We have 3 types of Hierarchies 1)Time Dependent(Structure depends on time). 2)Not-Time Dependent(Structure depends on time). 3)Entirely Time Dependent(Entire Structure depends on time). Select Type of hier

19

We need to select some obj(attr) 4 structure and activate

We can maintain the hier manually by clicking on MAINTAIN HIERARCHIES

20

. Just click on create & give description

we will get window like as follows

to insert obj click on char nodes and select object

21

we will get window as follows(Here condition is we must have at least text tab otherwise we will get null values)

maintain hierarchy as follows

22

After activating hier we will get tree symbol under the char as follows.

23

24

c)Attribute Table:It maintains the detailed info about the object like cust num have name,adrs,.etc. If we are maintaining the attr of any obj that will act as key to its table. The naming convention of attr table is /BIC/P(OBJ NAME).

Attr always gives present truth only and they are over writable. TYPES OF ATTRIBUTES:We have 7 types of attributes. 1)Display Attr. It completely depends on Master characteristic in reporting. We can access in any Attr Table. It is available in /BIC/P table. When ever we select ATTR ONLY that will b display attr.

25

In query Cust name,income will appear in query design when cno is in qd Otherwise they wont appear in qd

26

In report Cust name,income will appear in result set when cno is in drill down
Key Figures CUST NUM CUST NUM C100 C101 C102 C103 Key Figures CUST NUM Number of Records 17 CUST'S NAME VISH SOM CHAN DAYA CUST'S INCOME 100,000.00 200,000.00 300,000.00 400,000.00 Number of Records 1 1 1 1

Otherwise they wont appear in result set

2)Navigational Attr It is not depends on Master characteristic in reporting. We can access in any Attr Table. It is available in /BIC/X table. When ever we de-select ATTR ONLY that will be nav attr Where ever we want to use cno in any obj like(cube/ods) sys will take nav_attr in nav part. And kf cannt a nav attr .The naming convention of nav_attr is M_CNO__M_CNAME(attr tab_attr name) De-select attr-only

switch on nav_attr and select text to get description

we will get nav_attr under obj 27

if we use cno in any obj(CUBE/ODS) sys will take nave attr.

In query In report
Key Figures STATE REGION CNO CNO REGION STATE INCOME

28

#/#

# Result

# Result

Overall Result Key Figures STATE REGION CNO REGION # Overall Result STATE # Result INCOME 0.00 INR 0.00 INR 0.00 INR

0.00 INR 0.00 INR 0.00 INR 0.00 INR

3)Time Dependent Attr When we have an attrs val is changing over period of time.And we want to maintain the historical data.It is depends/not depends on Master characteristic in reporting. We can access in any Attr Table. It is available in /BIC/Q table. When ever we select/de-select ATTR ONLY that will be TD attr.For this attr we will get 2 more objs (DATE_TO , DATE_FROM) We need to select Time-dependent Table 4 time dependent attr

data

29

In reporting it shows diff data based on time

ADDR CNO CNO P1/C100 P1/C200 P2/C300 P2/C400 ADDR VIJ VIJN BAN DEL

ADDR CNO CNO P1/C100 P1/C200 P2/C300 P2/C400 ADDR VIJ VIJN BAN1 NDEL

4)Time Dependent Navigational Attr When we have an attrs val is changing over period of time.And we want to maintain the historical data.It is depends/not depends on Master characteristic in reporting. We can access in any Attr Table. It is available in /BIC/Y table. When ever we select/de-select ATTR ONLY that will be TD attr.For this attr we will get 2 more objs (DATE_TO , DATE_FROM).. It is not depends on Master characteristic in reporting. We can access in any Attr Table. When ever we de-select ATTR ONLY that will be nav attr Where ever we want to use cno in any obj like(cube/ods) sys will take nav_attr in nav part. And kf cannt a nav attr .The naming convention of nav_attr is M_CNO__M_CNAME(attr tab_attr name) We need to select Time-dependent Nav-attr.

Table 4 time dependent nav attr 30

In reporting

CNO STATE CNO P1/C100 P1/C200 P2/C300 P2/C400 STATE AP1 AP4 KA1 DEL1

CNO STATE

31

CNO P1/C100 P1/C200 P2/C300 P2/C400

STATE AP1 AP4 KA2 DEL2

5)Exclusive Attr. It is not depends on Master characteristic in reporting. We can access in any Attr Table oand obj like(cube/ods). It is available in /BIC/P table.When ever we de-select ATTR ONLY that will be exclusive attr.

CNO Key Figures

32

CNO P1/C100 P1/C200 P2/C300 P2/C400

INCOME 0.00 INR 0.00 INR 0.00 INR 0.00 INR

6)Compound Attr. It is superior info obj. One value of info obj depends on value of other obj.It will act as other primary key to attr table

Here cno is differed by plant number.

CNO PLANT CNO P1/C100 P1/C200 P2/C100 P2/C200 PLANT P1 P1 P2 P2

7)Transitive Attr. It is 2nd level of navigational attr. And it is Nav-attr of Nav-attr. It is not depends on Master characteristic in reporting. We can access in any Attr Table. It is available in /BIC/X table. When ever we de-select ATTR ONLY that will be nav attr Where ever we want to use cno in any obj like(cube/ods) sys will take nav_attr in nav part. And kf cannt a nav attr .The naming convention of nav_attr is M_CNO__M_CNAME(attr tab_attr name) 33

FINALLY WE WILL GET 10 TABLES FOR MASTER TABLE: /BIC/S/BIC/M/BIC/T/BIC/H/BIC/K/BIC/I/BIC/P/BIC/X/BIC/Q/BIC/YSID table for obj Master table for obj Text table for obj The hierarchical relationships of the characteristic values are stored in this table, if external hierarchies are used for the characteristic The conversion of hierarchy nodes into SIDs is stored in this table. Contrary to characteristic values, hierarchy nodes get negative SIDs The hierarchy structure is stored in this table All attributes will store in Table for Navigational attr Table for Time Dependent attr Table for Time Dependent Navigational attr.

DIFFERENCE BETWEEN TEMPLATE AND REFERENCE:Source obj

34

1)Template brings the all properties of source obj 2 destination obj and we can change the properties.

35

2)Reference brings the all properties of source obj 2 destination obj and we can not change the properties.

36

CUBE: IMPORTANT POINTS TO REMEMBER TO DESIGN THE CUBE: A)Decide the type of cube like. 1)Top Down(Based on Reporting) 2)Bottom Up(Based on Source System) 3)Mixed(Based on Reporting and Source System) B)Identify business Characteristics/Subject. C)Identify the KPI. D)Identify the stronger characteristic. E)Optimize the DIMENTION. 1)If the relationship b/n 2 chars is M:M keep them in 2 different dimensions.

37

2) If the relationship b/n 2 chars is M:1/1:M keep them in same dimension

3)If one char is attr of other char if clinent wants only present values then keep them in same dimension

4) If one char is attr of other char if clinent wants only fact values then keep them in diff dimensions

5)Reference characteristics should be in same dimension. 38

6)We need to set dimension as LINE_ITEM when we have only one char is assigned to it to increase reporting performance 7)If we have more data in cube we need to select CARD-HIEGHT to increase reporting performance F)If we place Key Figure in master table we will get only present or in fact table we will get only fact values G)If we have reports on month/year wise or quarter/year wise we need to perform partition on cube. H)Max num of sid are connected to dim table is 248 so total num of chars used in cube is 13X248=3224 Max num of kf connected to fact table is 233 STEPS TO DESIGN CUBE: 1)Identify the chars and kf. Char kf Cno qty Mno price Date 2)Identify info objects for each field C_CNO,C_MNO,C_QTY,C_PRI,0CALDAY 3)Draw BUBBLE diagram

4)Draw the graphical star schema.

39

5)At least we need to take 1 char,1 kf,1 time-char and we need to assign char 2 one dim. Other wise sys will show error Create cube under any info area.

40

SELECT CHARACTERISTICS

41

ASSGN THEM TO DIMENSIONS

42

SELECT TIME CHARACTERISTIC

43

SELECT KEY FIGURE

44

To see the structure of cube go to T-Code is LISTSCHEMA

45

FINALLY WE WILL GET 18 TABLES FOR CUBE: /BIC/D(cube name)T /BIC/D(cube name)U /BIC/D(cube name)P /BIC/ D(cube name)1 /BIC/ D(cube name)2 | | /BIC/D(cube name)9 /BIC/D(cube name)A | -Dimension Table for TIME -Dimension Table for UNIT -Dimension Table for DATA PACKAGE -Dimension Table for (CUSTOMER GENERATED) -Dimension Table for (CUSTOMER GENERATED) -Dimension Table for (CUSTOMER GENERATED) -Dimension Table for (CUSTOMER GENERATED) 46

| /BIC/D(cube name)D /BIC/F(cube name) /BIC/E(cube name)

-Dimension Table for (CUSTOMER GENERATED) -Fact Table -Fact Table

TYPES OF CUBES: 1)Standard Cube(BASIC CUBE) 2)Transactional Cube 3)SAP Remote Cube 4)General Remote Cube. 5)With Services Cube. Standard Cube:

SELECT CHARACTERISTICS

47

ASSGN THEM TO DIMENSIONS

48

SELECT TIME CHARACTERISTIC

SELECT KEY FIGURE

49

Transactional Cube

50

SELECT CHARACTERISTICS

51

ASSGN THEM TO DIMENSIONS

SELECT TIME CHARACTERISTIC

52

SELECT KEY FIGURE

53

Here we have (BASIC CUBE + TRANSACTIONAL)properties. For this cube we have 2 types of modes for loading data 1)Loading Mode(Normal ETL process) 2)Planning Mode(User can enter data manually) We can put any mode but we cannt allow 2 modes at a time(We can select any mode and load data)

For planned mode we can load data with the T-Code : RSINPUT

Enter the data manually 54

After saving we will get.

In manage we will get req in yellow color that means req is in open it will close after getting 50,000 records

55

we cannt get data in reporting directly why bcz we dont have rep symbol..We can get in 3 ways 1)Set the req in green color. 2)Set cube in loading mode. 3)We have variable called MOST RECENT DATA under the Req-ID. In reporting

56

SAP Remote Cube: It is Virtual Provider. It access the source system when we want to fetch the data remotely from SAP application at the run time. It wont store data physically. It extracts the data 4m remote SAP appl and gives the data 2 report.

Create a table and its data source in R/3 or MYSELF. 1)Create table in SE11.

57

select db tab view maint:dis/maint is allowed.

Class:A

Enter field names and give type and its length.

58

One primary key must be there. We can use data elements too.

59

For CURR,QUAN we must give REFERENCE Field and Tables name(reference fields) name

We must set Technical settings for table.

In Technical settings we must give data class and size of table

60

61

Activate table For Entries to table

Enter the data as follows.

To c contents of table

62

2)Create Data Source For Table. Go to RSO2.

We can create DS . 63

3)Create Info source wit MYSELF/ R/3.

64

4)Create info cube 4 SAP Remote Cube

65

66

67

5)Assign Source System.

and 4 r/3

In Reporting

68

Calendar Year Source System Key Figures CUST NUM MAT NUM CUST NUM C1 C2 C3 Overall Result MAT NUM M1 M2 M1 Source System My IDES BW & SEM My IDES BW & SEM My IDES BW & SEM Calendar Year 2009 2010 2011 QUANTITY 123 EA 123 L 123 KG 369.000 MIX PRICE 1,230.00 INR 1,230.00 AUD $ 1,230.00 3,690.00 MIX

General Remote Cube: It is Virtual Provider. It access the source system when we want to fetch the data remotely from NON-SAP application at the run time. It wont store data physically. It extracts the data 4m remote NON-SAP appl and gives the data 2 report. 1)Create Table in NON-SAP application server 1)Prepare Table in SQL server. ********** TO CREATING TABLE. SQL> CREATE TABLE TRAN(CNO VARCHAR(5),MNO VARCHAR(5),ZDATE NUMBER(8),QTY NUMBER(5),UNIT VARCHAR(5), PRI NUMBER(5),CURR VARCHAR(5)); Table created. 69

********** TO INSERT ROWS. SQL> INSERT INTO TRAN VALUES('C124','M1',20110129,1,'EA',16000,'INR'); 1 row created. SQL> INSERT INTO TRAN VALUES('C125','M2',20110219,2,'L',35000,'USD'); 1 row created. SQL> INSERT INTO TRAN VALUES('C126','M3',20110301,3,'KG',50000,'AUD'); 1 row created. SQL> COMMIT; Commit complete. ********** TO C LIST OF TABLES IN SERVER SQL> SELECT * FROM TAB; TNAME TABTYPE CLUSTERID ------------------------------ ------- ---------TRAN TABLE ********** TO C DATA. SQL> SELECT * FROM TRAN; CNO MNO ZDATE QTY UNIT PRI CURR ----- ----- ---------- ---------- ----- ---------- ----C124 M1 20110129 1 EA 16000 INR C125 M2 20110219 2L 35000 USD C126 M3 20110301 3 KG 50000 AUD 2)Create data source 4 NON-SAP system. Create DS for DB connection.

70

71

3)Insert Table into DB connection.

72

4)Create Cube with Generic Remote Cube

73

74

75

In Reporting

76

ODS(OPERATIONAL DATA STORE): It is 2 dimensional table. It over writes the data records with same Key Field combination. It is mainly used for PERMINENT staging purpose(PSA 4 TEMPORARY staging) It maintains the GRANULAR DATA. We have 2 main parts in ODS 1)KEY Fields(acts as keys 4 ods max num of key fields are 16 only characteristics but not kf) 2)DATA Fields(except kf all objs are df only max num of df are 749) We have 3 tables in ODS 1)NEW Table 2)Change Log Table 3)Active Table When ever we load data into ODS data will loaded into NEW Table the req will be in yellow color. and we need to set into green color and activate request when ever we activate request the data will goes into active table. while moving data 4m new table to active table the change log stores the changes in recs which contains same kf combination

77

78

. If we are trying to create ods we can set some settings those settings are 1) BEx Reporting 2) ODS Object Type - For generating Reports. -Standard(NORMAL ODS) -Transactional(users plan) 3) Unique Data Records -If we select this it wont allow duplicate records (same kf combination)in same package. 4) Check table for Info Object 5) Set quality status to 'OK' automatically -It sets the req in green color(OK)when data is loaded into NEW table. 6) Activate ODS object data automatically -It activates the req. 7) Update data targets from ODS object automatically -It loads the data 4m ods to its target when ever we load data into ods Even we select any settings sys wont show which we have selected. if we want c the changes in settings of ods 79

FINALLY WE WILL GET 3 TABLES FOR ODS: /BIC/A(ODS Name)40 /BIC/A(ODS Name)00 /BIC/B000*ODS-NAME* -NEW Table -ACTIVE Table -CHANGE LOG Table

NEW Table-(KEYS{LOADING REQ+DATAPACKID+RECORD}+KF+DF+RECORD MODE)

80

ACTIVE Table-(KEYS{KF}+DF_RECORD MODE)

CHANGE LOG Table-(KEYS{LOADING REQ+DATAPACKID+RECORD+PART NUM}+KF+DF+RECORD MOD) Record Mode -N-new img [ ]-after img x-before img 81

82

TYPES OF ODS: 1)Standard ODS(BASIC ODS) 2)Transactional ODS Standard ODS: Refer above ods In Reporting

Calendar Year

83

Key Figures MAT NUM CUST NUM MAT NUM M1 M2 M3 Overall Result Number of Records QUANTITY PRICE 28 32.000 MIX 397,000.00 INR 28 67.000 MIX 530,000.00 MIX 26 78.000 MIX 1,254,500.00 AUD 82 177.000 MIX 2,181,500.00 MIX

Transactional ODS: It is Manual Ods We can load data Manually only. We dont have ETL process We have only ACTIVE Table It supports DATA MARTS but it wont supports DELTA why bcz we dont have CHANGE LOG TABLE. It dont have any settings like standard ods. It wont supports 4 Reports directly. We can get data 4m Tran ods through INFO SET. Create normal ODS change settings(ODS OBJECT TYPE)

84

If want to load data thorough RSINPUT

85

86

For reporting create INFOSET and generate report on tran-ods

Calendar Year CUST NUM MAT NUM Key Figures MAT NUM QUANTITY PRICE

87

M1 M2 M3 # Overall Result

8 EA 120,000.00 INR 16 KG $ 160,000.00 24 L 400,000.00 AUD 0.000 0.00 48.000 MIX 680,000.00 MIX

MULTIPROVIDER: It combines CUBES,ODS,INFO OBJECT,INFO SET. It is Virtual Provider. It access the all info providers under multi provider when we want to extract the data at the run time. It wont store data physically. It works with UNION. We cannt access Transactional ODS and Transactional CUBE(in PLANNED MODE) It is not a view INDESIGNING MP WE HAVE ATLEAST ONE CHAR MUST BE COMMON-data element. We can create mp under any IA.

88

89

90

91

92

93

94

95

96

In Reporting

97

INFO SET: It combines only ODS and INFO OBJECT. It is Virtual Provider. It access the all info providers under INFO SET when we want to extract the data at the run time. It wont store data physically. It works with JOIN. We cannt access Any type CUBE It is not a view INDESIGNING MP WE HAVE ATLEAST ONE CHAR MUST BE COMMON-data element. We have 3 types of joins 1)Inner Join(ODS-ODS && ODS-INFO OBJ) It Brings only combined data 2)Outer Join(ODS-ODS && ODS-INFO OBJ) It Brings combined data as well as extra records 4m opposite ods 3)Temporal Join(ODS-ODS && ODS-INFO OBJ) It Brings the data related to date Ex:-if we have month in one ODS and date, reg in ODS1. if we put TEMP JOIN and if we give month in rep sys will shows reg at particular mont Create 1st ODS 4 cust details:

98

Create 2nd ODS 4 Transactional data

99

We can create mp under any IA.

1)Inner Join

100

4 inner join we will get only common records only.

MAT NUM Calendar Year Key Figures CUST NUM 4 TRAN CUST'S NAME CUST NUM 4 DETAILS CUST NUM 4 TRAN C100 CUST NUM 4 DETAILS VISH CUST'S NAME VISH QUANTITY PRICE 1 EA 15,000.00 INR Number of Records 1

101

C101 C102 C103 C104 C105 C106 C107 C108 C109 C110 C111 C112 C113 Overall Result

SOM CHAND DAYA MANJ NAG RAJU SESHU LAX KITTU DEV PHANI RAMU BALU

SOM CHAN DAYA MANJ NAG RAJU SESH LAX KITT DEV PHAN RAMU BALU

2 KG $ 20,000.00 3 L 50,000.00 AUD 1 EA 15,000.00 INR 2 KG $ 20,000.00 3 L 50,000.00 AUD 1 EA 15,000.00 INR 2 KG $ 20,000.00 3 L 50,000.00 AUD 1 EA 15,000.00 INR 2 KG $ 20,000.00 3 L 50,000.00 AUD 1 EA 15,000.00 INR 2 KG $ 20,000.00 27.000 MIX 375,000.00 MIX

1 1 1 1 1 1 1 1 1 1 1 1 1 14

2)LEFT OUTTER JOIN

CUST NUM 4 DET Calendar Year MAT NUM Key Figures CUST NUM 4 TRAN CUST'S NAME

102

CUST NUM 4 TRAN C100 C101 C102 C103 C104 C105 C106 C107 C108 C109 C110 C111 C112 C113 #

CUST'S NAME VISH SOM CHAN DAYA MANJ NAG RAJU SESH LAX KITT DEV PHAN RAMU BALU RANG RATN

QUANTITY 1 EA 2 KG 3L 1 EA 2 KG 3L 1 EA 2 KG 3L 1 EA 2 KG 3L 1 EA 2 KG 0.000 0.000

PRICE 15,000.00 INR $ 20,000.00 50,000.00 AUD 15,000.00 INR $ 20,000.00 50,000.00 AUD 15,000.00 INR $ 20,000.00 50,000.00 AUD 15,000.00 INR $ 20,000.00 50,000.00 AUD 15,000.00 INR $ 20,000.00 0.00 0.00

Number of Records 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

AND OTHER INFOSET 4 OUTTEER JOIN

CUST NUM 4 DET Calendar Year MAT NUM Key Figures CUST NUM 4 TRAN CUST'S NAME CUST NUM 4 TRAN C100 C101 C102 C103 C104 C105 C106 C107 C108 C109 CUST NUM 4 DET C100 C101 C102 C103 C104 C105 C106 C107 C108 C109 CUST'S NAME VISH SOM CHAN DAYA MANJ NAG RAJU SESH LAX KITT QUANTITY 1 EA 2 KG 3L 1 EA 2 KG 3L 1 EA 2 KG 3L 1 EA PRICE 15,000.00 INR $ 20,000.00 50,000.00 AUD 15,000.00 INR $ 20,000.00 50,000.00 AUD 15,000.00 INR $ 20,000.00 50,000.00 AUD 15,000.00 INR

Number o

103

C110 C111 C112 C113 C114 C115 C116

C110 C111 C112 C113 # # #

DEV PHAN RAMU BALU # # #

2 KG 3L 1 EA 2 KG 3L 1 EA 2 KG

$ 20,000.00 50,000.00 AUD 15,000.00 INR $ 20,000.00 50,000.00 AUD 15,000.00 INR $ 20,000.00

3)TEMPORAL JOIN

104

NON-CUMULATED KEY FIGURE: When we dont want the kf values to be cumulated we go 4 Non-Cumulated Key Figure. By using Exception Aggregation we will define nckf. Senario1:-According 2 year we want number of Employee Create Char,Kf 4 Kf

105

Create cube and load data

In Reporting we will get like.

Calendar Year Key Figures COMPANEY COMPANEY C1 Calendar Year 2009 2010 2011 NUMBER OF EMPLOYEES 2,500 2,000 3,000 3,000

Overall Result

106

Senario2:-According 2 date we need stock. Create Char,Kf 4 Kf

Create cube and load data

Key Figures MNO Calendar Day MNO M1 Calendar Day 01.01.2011 02.01.2011 03.01.2011 Result 01.01.2011 02.01.2011 03.01.2011 Result STOCK 1,000 2,000 3,000 3,000 5,000 1,500 1,111 1,111

M2

107

Senario3:-Calculate one emp how many times visit each shop Create Char,Kf 4 Kf

Calendar Day Key Figures EMP SHOP EMP E100 SHOP S1 S2 S3 S4 Result S1 S2 S3 Result AMOUNT 1 1 1 1 4 1 1 1 3

E101

OPEN HUB SERVICES: INFOSPOKE: To retract the data 4m objects into files in external systems file and table We can retract data data into file in Appl-Server, Client Work Station, Data Base Table. 108

When ever we are trying 2 retract data 2 ff inas,cw we will get 2 files they are 1)(Info spoke name).CSV 2)S_(Info spoke name).CSV

109

FF 2 Appl-Server

110

111

112

113

InfoSpoke;INFO_SPOKE1 TimeStamp;20020120183821 C:\usr\sap\SBW\DVEBMGS01\work\INFO_SPOK.CSV

COLUMN;FIELDNAME;KEY;TYPE;LENGTH;OUTPUTLEN;DECIMALS 1;CALDAY;X;DATS;000008;000010;000000 2;CALMONTH;X;NUMC;000006;000007;000000 3;CALMONTH2;X;NUMC;000002;000002;000000 4;CALQUART1;X;NUMC;000001;000001;000000 5;CALQUARTER;X;NUMC;000005;000006;000000 6;CALWEEK;X;NUMC;000006;000007;000000 7;CALYEAR;X;NUMC;000004;000004;000000 8;CHNGID;X;NUMC;000014;000014;000000 9;CURRENCY;X;CUKY;000005;000005;000000 10;FISCPER;X;NUMC;000007;000008;000000

00000000;000000;00;0;00000;000000;0000;00000000000000;AUD;0000000;K1;0;REQU_A9EPGXEP7O682809LQQUCCRHH;KG;C126;M 3.000 00000000;000000;00;0;00000;000000;0000;00000000000000;INR;0000000;K1;0;REQU_A9EPGXEP7O682809LQQUCCRHH;EA;C124;M

FF 2 Client Work Station

114

FF 2 Data Base Table

If we select full update we need to select this for reducing duplication If we select this we will get 3 extra technical fields they are REQID,DPKTID,RECNO

115

116