/tema1 by rapha Torres

!"#$%&'()'*$+,-.'/$01/.1(/2$3(&4.&5 !"#$%&

 SAP AG 2006

TERP10

2-3

?:@+A$.&8.B+A6.&%,..+C8,%$"&)

! !"#$%&'$(&)%$*+*,-,*.+$%/+0$.(,"+/$($+1")-&/,+(2,+ 3"$0,4)"5+(2$(+.611)"(.+(2,+76.&%,..+("$%.$8(&)%.9+ :,1)"(&%#+$**)4.+;)6+()+-&,4+0$.(,"+/$($<+$.+4,**+ $.+(2,+)6(16(+)3+76.&%,..+("$%.$8(&)%.9+=.+$+1")>,8(+ (,$0+0,07,"<+&(+&.+&01)"($%(+(2$(+;)6+6%/,".($%/+ (2,+36%/$0,%($*+8)%8,1(.+)3+)"#$%&'$(&)%$*+*,-,*.<+ 0$.(,"+/$($<+("$%.$8(&)%+/$($<+$%/+",1)"(&%#9+

 SAP AG 2006

TERP10

2-4

309)@(&-:&?)56789 309)9,&-'-,"-".)A,+-:) B>C$:'-D$&

8')'*$):,":;<&-,"),/)'*-&)',+-:=)6,<)4-;;)>$)(>;$)',? ! !"#$%&'("#)'*$)+,&-'-,"-".),/)012)3"'$%+%-&$) ',4(%#&)56789 309)

 SAP AG 2006

TERP10

2-5

!"#$%"&'($")*"+,*)-.'/0),"1$23,)4)56 89:0,$::";$<90-$.$,/:

A!G";@H

A!G";@I

.6A!G"D;G A$-(02$BC-0$,/$7" !-230/$2/9-$:

'"(")%*"

!"#$%&"

A/-'/$502 F'49$

=40$,/@A$-($!-230/$2/9-$

D**020$,26 E"=),/-)4

=$,/-'40>$7 =).?9/0,5"

!9/).'/0), !7(',2$.$,/"0,"1$23,)4)56  SAP AG 2006

"#$%&'&()%!*%&+(,%)!-&,.($%,$/&%!0"*-1!%#234%)!3/)(#%))!(##5+2$(5#!36!4%+%&27(#7!%8()$(#7!9:! 2))%$);!<28(<(=(#7!27(4($6;!2#>!&%>/,(#7!:5$24!?5)$!5@!AB#%&).('!0:?A1C!!*-D!E%$B%2+%&!()! $.%!2''4(,2$(5#!2#>!(#$%7&2$(5#!'42$@5&<!$.2$!3%)$!)/''5&$)!"*-!/)(#7!F%3!*%&+(,%)! :%,.#54576C!

Starting from the 70‘s there have been major technology waves – from mainframe computing to client server architectures, and now from client server technology to service oriented architectures

In the past such shifts in technology have caused a complete replacement of the underlying IT infrastructure, but with the shift from SAP R/3 to mySAP ERP that‘s no longer true

SAP will protect and leverage the 200 billion $ investments already made in R/3 and will take an evolutionary approach for the next technology shift towards web services driven architectures

TERP10

2-6

",01.*+0*2,+$34$56!"#$(%#

*++',#-.,&%

8302/$.)$*1./$032,/+

!"#$(77$

!"#$%&'&()

!"#$%&'$()*+,-,./+

ďŁŠ SAP AG 2006

After the SAP R/1 and SAP R/2 products, SAP introduced SAP R/3 in 1992. Now there was a two layer architecture (SAP Basis and SAP Application).

With mySAP ERP, which has been available since March 2003, SAP offered a bundle of components supporting ERP business processes. At this point, SAP R/3 Enterprise was one of those components. As you can see here, even from this point mySAP ERP was more than just SAP R/3 Enterprise plus SAP NetWeaver, since it offered many functional enhancements like Self Services, SAP SEM, and others.

The SAP ERP Central Component (ECC) represents the next step in this evolution. As you can see, the orange boxes represent the items that can be operated on an SAP ERP Central Component. And in the SAP NetWeaver area, you can see the dark blue frames that are technically integrated in the SAP ERP Central Component (Business Intelligence only on a project basis). .

Since Release 4.6C, SAP R/3 consisted of two parts: SAP Basis (the technology platform) and the application. To come to a higher SAP R/3 Release, customers had to upgrade both the technology and the application.

With mySAP ERP, a new mySAP solution was born. Although there are many other SAP components included in mySAP ERP, SAP R/3 Enterprise is also included in mySAP ERP. This explains why a customer who has implemented SAP R/3 Enterprise has nothing to do from a technical perspective when changing his license to mySAP ERP.

ÂŠ SAP AG

TERP10

2-7

-%7!9.:;9.#"<.7!9.=3&>3#835 !"#$%&'(%&12&+3*&2455*226/&'(%& 677*/189&+6&#$%&(:;< ! *,"(&'6"#$'&%BC')3.-%7!9.:;9 '"($,<3).#$$. &A3.@,"(&'6"#$'&%.6@.7!9.;DE.:"&3505')3

! F3(A"6$62%BC')3.-%7!9.:;9 ').G,'$&.6". 7!9.=3&>3#835.

!"#$%&'(% !"#$%&'() *'"#"('#$) +,-#"./#0'&#$.1#"#23-3"& 4035#&'6") /65065#&3.7358'(3) #$%&)*+,*-.*/0

H 73$@.7358'(3)I./6$$#G65#&'83.*6$<35). #"<./6$$#G65#&'83.956J3(&)H H 7&5#&32'(.:"&3505')3.1#"#23-3"&I 1#"#235.73$@.7358'(3)H H*'"#"('#$.7,00$%./A#'".1#"#23-3"&I 73$@B7358'(3.956(,53-3"&H H73$@.7358'(3)I !<6G3.95'"&'"2.*65-)H 76-3.3?#-0$3).6@.@,"(&'6"#$'&%.$3835#2'"2. =3&>3#835 &3(A"6$62'3)  SAP AG 2006

mySAP ERP is powered by SAP NetWeaver. Let’s now have a look at how the solution is already making use of the capabilities of SAP NetWeaver.

This slide gives some examples that answer this question.

One very good example is the Self Services provided with mySAP ERP. They utilize the portal capabilities, make use of SAP Business Information Warehouse (BW) through the Manager Self Services, and are technically based on the SAP Web Application Server.

Other functionalities, like the Self-Service Procurement, utilize the Integration Broker (SAP Exchange Infrastructure).

TERP10

2-8

!"#$%&'(%&)*&+&*,-./),0&1)/2)0&!"#$%&3.*)04**&#.)/4

!"#$%&34567-55&#46.!"#$%&%)(

!"#$% #*(

!"#$%&+*%

!"#$% '*(

!"#$%&#'(

#$%&,-./-01-2  SAP AG 2006

mySAP ERP is the solution suite within the mySAP Business Suite

It is based on SAP´s listening to customers, user groups and further inputs from analysts and other thought leaders to better serve market demands of our customers and prospects.

It is ready to service operational, tactical and strategic needs of enterprise and beyond enterprises ensuring collabortion among partners.

Business Solutions are part of mySAP ERP which before had to be licensed separately with the benefit to be pre – integrated due its development being continously based on our Netweaver platform.

Let us have a closer look at the solution map you are all familiar with from a high level perspective.

mySAP ERP – mySAP Enterprise Resource Planning mySAP CRM – mySAP Customer Relationship Management mySAP PLM – mySAP Product Lifecycle Management mySAP SRM – mySAP Supplier Relationship Management mySAP SCM – mySAP Supply Chain Management

TERP10

2-9

#$%&' ()'"%*+,-.*/"012

!" ďŁŠ SAP AG 2004

The figure above represents the mySAP ERP solution map. As with all other mySAP solutions, a solution map shows you the processes enabled by a specific solution.

The picture shows the top-level of the mySAP ERP solution map. To find out more, you can look at the solution map at the SAP Service Marketplace, where you can click on the different areas in the map to get more detail. The map is available at !""#$%%&'()*+',&-#,+./%01&*2'&&/-#&344536(.&&4 7281&"(93:-#&34453;2"'(#(*&'3<'&.1(+'3=>-22*2?. "#$%& You must have a registered user ID to access the map. After registering, you can also install the SAP Solution Composer from &'()*+',&-#,+./%&4+./#.&'( (be aware that the solution map may change with the evolution of market terminology, so always use the most recent one by updating SAP Solution Composer regularly).

As you can see, this figure highlights several areas. These are the areas where mySAP ERP offers additional capabilities compared with SAP R/3 Enterprise, making mySAP ERP the state-of-the-art ERP solution. As an example, a mySAP ERP customer can use SAP NetWeaver capabilities by implementing the SAP Business Information Warehouse or the SAP Enterprise Portal. Or, the customer can implement Self-Service Procurement, Internet Sales, or other functionalities.

SAP Best Practices have a few of these highlights pre-configured such as New General Ledger, Analytics, others need to be evaluated on a project basis.

ÂŠ SAP AG

TERP10

2-10

!"#$%&'()'*$+,-.# !"#$#/'(0(/1(12$3/4()$ -5++&6,

?/5$&69$1/>$&@A9$0/* ! 71896'0&18$0:9$4/'(0(/1(12$/;$"<=$!109646('9$ 0/>&68'$+,-.# !"#

 SAP AG 2006

TERP10

2-11

!"#$%&'()'*$+,-&.(/&0(1.&2$34542'$617()$ +894)0(54'

=0$0;4$)1.)2>'(1.$1?$0;('$017()@$A1>$B(22$84$&824$01* ! :4'),(84$0;4$<=#$!.04,7,('4$1,-&.(/&0(1.&2$24542'$

 SAP AG 2006

TERP10

2-12

;(8-%*<-&*/%-5?9'3'5+?@ A'(2*%/5/86 !"# $%&'()(*+' 4/2)-%6

45*'%& 4/2)-%6 4/7'

!0=+*7*-(6

#5-%&

>-:&/(6

!-5'+ ;(8-%*<-&*/%

!-5'+ ;(8-%*<-&*/% 1')-(&2'%&

1*3*+*/%

B0+*%'++ "('-

1*3*+*/% !&/(-8' 9/:-&*/%+

,-('./0+'+

 SAP AG 2006

Organizational Levels: A company’s enterprise structure is mapped to SAP applications using organizational units. They are used to represent the enterprise structure in terms of legal and/or business-related purposes. Organizational elements include legal company entities, plants, storage locations, sales offices, and profit centers.

Examples: • The highest-level unit of all organizational elements is the Client" The Client represents the enterprise/headquarters group. • A Company Code is a unit included in the balance sheet of a legally-independent enterprise and is the central organizational element of Financial Accounting. • In the context of Sales and Distribution, the Sales Organization is the central organizational element that controls the terms of sale to the customer. Division is usually used to represent product line. • In the context of Production Planning, Plant is the central organizational unit. A Plant can manufacture product, distribute product, or provide a service. • In Inventory Management, material stocks can be differentiated within one plant according to Storage Location.

Organizational units may be assigned to a single application (such as Sales Organization assigned to Sales and Distribution, or to several applications (such as Plant assigned to Materials Management and Production Planning).

TERP10

2-13

8)+*%#9*&#(%*"3,$:$";3

!"#$%&

!(01*%23!(4$ 6...

!(01*%23!(4$ 5...

!(%&)(""#%+37)$* /... <"*%&36...

'&()*+$ ,(-*&#(% ...6

<"*%&366..

'&()*+$ ,(-*&#(% .../

<"*%&36/..

'&()*+$ ,(-*&#(% ...5

ďŁŠ SAP AG 2006

"#$!#%&#$'()*$+$*!$*$,$-(!./!0**!.1&0-%20(%.-0*!$*$,$-('!%'!(#$!3*%$-(4 The client can be an enterprise group with several subsidiaries. All of the enterprise data in an SAP System implementation is split into at least the client area, and usually into lower level organizational structures as well.

Flexible organizational elements in the SAP System enable more complex enterprise structures to be represented. If there are many organizational elements, the legal and organizational structure of an enterprise can be presented in different views.

By linking the organizational units, the separate enterprise areas can be integrated and the structure of the whole enterprise represented in the SAP System. This links are defined in Customizing.

When defining the organizational units, bear in mind that they define the structure for how data is to be entered, tracked, and extracted from the SAP system.

The controlling area identifies a self-contained organizational structure for which costs and revenues can be managed and allocated. It represents a separate unit of cost accounting.

ÂŠ SAP AG

TERP10

2-14

!"#$%&'($"% ,-.-%-/0%

!"#$%&"($"& )***& )*& *+ *+

!"#$%&"($"& )***& )*& *+ *1

!"#$%&"($"& )***& )*& *+ *2 ďŁŠ SAP AG 2006

The combinations of sales organization, distribution channels and divisions are called "#$%"!#&%#".

For each sales area, you can make customer-specific agreements, for example, about partial deliveries or price and payment conditions. In a sales area you can create statistics and carry out separate marketing activities.

ÂŠ SAP AG

TERP10

2-15

!"#$%,

--&'((( ./01&2345#$6

!"#$%&'(((

!"#$%&''((

!"#$%&')((

!"#$%&'*((

!"#$%&'+((

7#5894:

;34"<$

/43,=3$

>4#$?@94%

1%9%%:#4%

ďŁŠ SAP AG 2006

The central organizational unitt in Logistics is the "#$%&. A number of plants can be contained in a company code, that is, they are assigned to the same company code in the configuration.

All company-code relevant transactions from one of these five plants are posted to company code 1000 in Accounting.

ÂŠ SAP AG

TERP10

2-16

!"#$%&'()* +#*&)(,&-(.)'

!>&)-01222

!>&)-01122

!>&)-01E22

!>&)-01F22

!>&)-01G22

;&9<"#*

=8#>()

4#8'?8)

@#&)AB"#-

6-"--*&#-

!"#$%&'()*0.#*&)(,&-(.)012220C"#$%&'8'0B.#DDD

!"#$%&'8 .#*&)(,&-(.) 122203456078#9&):

!"#$%&'()* (' C.'-8? ()0 DDD

//01222 3456078#9&):

ďŁŠ SAP AG 2006

Purchasing for the plants is completed by the "#$%&'()*+!,$+'*)-'.),*. Each country in which plants operate has one purchasing organization. It purchases for all plants in the country and posts the purchases in the company code of that country.

In Germany, for example, purchasing organization 1000 takes care of purchasing for all German plants (Hamburg, Berlin, Dresden, Frankfurt, Stuttgart). Purchases are posted in the German company code 1000.

ÂŠ SAP AG

TERP10

2-17

!"#$%&'()'*$+,-&.(/&0(1.&2$34542'617() 89::&,;

@19$&,4$.1A$&=24$01* ! <4'),(=4$0>4$8?#$!.04,7,('4$1,-&.(/&0(1.&2$24542'

 SAP AG 2006

TERP10

2-18

!"#$%&'()'*$+&',-.$/&,&$0 123()$456-),(7-'$

<,$,8-$)2;)=:'(2;$29$,8('$,23()>$?2:$@(==$5-$&5=-$,2* ! /-').(5-$,8-$9:;),(2;$29$+&',-.$/&,&$

 SAP AG 2006

TERP10

2-19

!"#$%&'("$"'3 *+#$,-%&'!"#$%&

/%0%&"1'("$"

!"#$%&'("$" )*+#$,-%&'!"#$%&'("$".

2"1%#'("$"

ďŁŠ SAP AG 2006

"#$%&'!(#%#) Data which is used long-term in the SAP System for several business processes. Master data is created centrally and can be used by all applications and all authorized users. Examples of master data in SAP include customers, materials, and vendors.

A customer master contains key information that defines the business relationship between a company and its customer. The master data is used to support execution of key business processes such as customer requests, deliveries, invoices, and payments.

Master data also has an organizational aspect as the information is organized into views which are assigned to organizational elements.The customer master is organized into three views which are each located at a different organizational level: General Data (Client), Financial Accounting Data (Company Code), and Sales Data (Sales Area).

Data on the client level can be used by all company codes. The customer account number is assigned on this level. That means the same customer has an explicit accounts receivable number in all company codes from a financial view.

ÂŠ SAP AG

TERP10

2-20

E/",%")-0(,%

1(+2",3& 1(4$

1*%-(+$/ ."%-$/ ."-$/0"# ."%-$/

!"#$% 5/6",07"-0(, ;-$+

."-$/0"# B*",-0-3

?'@<A==

9@<=A

'0%-/0C*-0(, 1D",,$# '080%0(, 9#",!-(/"6$ :()"-0(,

!"#$%& '()*+$,-

ďŁŠ SAP AG 2006

"#$%&$'()*%&+ Application programs which execute business processes in the SAP System such as creating a customer order, posting an incoming payment, or approving a leave request.

,*'-./%(+ A data record that is generated when a transaction is carried out.

When creating an order for a customer, you must take transport agreements, delivery and payment conditions, and so on, with business partners into consideration. To avoid re-entering this information each time for every activity related to these business partners, relevant data for the activity from the master record of the business partner is simply copied.

In the same way, the material master record stores information, such as the price per unit of quantity, and stock per storage location that is processed during order entry. This concept is valid for processing data for each master record included in the activity.

When performing each transaction, applicable organizational elements must be assigned. Assignments to the enterprise structure in the document are generated in addition to the information stored for the customer and material.

The document generated by the transaction contains all relevant pre-defined information from the master data and organizational elements.

A document is generated for each transaction carried out in the SAP System.

ÂŠ SAP AG

TERP10

2-21

!"#$%&& #'%"'(%)* !+"$,-&% .#/!-0

!+"$,-&% .#/!-0

1"2%" 4%;+("%:%7.

1"2%"

<-.%"(-= 8%72#" >+55=(%" !=-7. !+"$,-&(7? 1"?@ !+"$,-&%" 3"#+5

3##2& 4%$%(5.

67'#($%/ 8%"(9($-.(#7

!-0:%7.

!-0 <%.,#2 B-7C

A-"%,#+&% 8%72#"

ďŁŠ SAP AG 2006

From a logistical point of view, requirements planning is carried out first of all. To do this, the responsible department can register a materials requirement manually to Purchasing using an order requirement. It is possible to have the "#$%#!#%&'(#%)%*+ automatically created by the system.

,'#-./0%!"#$%#!./*$1(*2: The system provides you with entry tools when creating "#$%#0. The required entry data such as supplier, material, plant and other data relevant to the organization of purchasing must be provided.

When 2""$0!/#%!#%-%(3%$, the system checks, among other things, the quantity of goods received against the order quantity. A material document is created in MM to update the inventory. At the same time, a document is created in FI with which the evaluated goods are posted to the material stock account or the consumption account (debit) and to a goods receipt / invoice receipt account (credit).

After the invoice has been received in the 4*3"(-%!5%#(6(-/+("*, the 5%*$"#!4*3"(-% is checked as to the correctness of computation and content. All of these purchasing processes are settled in Logistics. The vendor invoice is posted in MM and, at the same time, a document is created in FI with which the invoice amount is posted to the goods receipt / invoice receipt account (debit) and the vendor account (credit). The goods receipt / invoice receipt account is used to make sure that a goods receipt is executed for every invoice and vice versa.

The ,/7)%*+!,#"-%00(*2 usually takes place in Financial Accounting. It is here that decisions are made about the payment process, such as, for example, the payment methods and the bank settlement.

ÂŠ SAP AG

TERP10

2-22

!"#&+(( 31+"12+45 3"$+"-'#-6)(7

3"$+"-'#-6)(7 !"#$%&' ()*+ +,-('#&.

A9&#@29> 3"$+"(

8")9(:#"'

;+*21+"<

=2**29>

;%9929> ? !)<@+9'

=2**29>

;%9929> ? !)<@+9'

/)*+-#0-)-(+"12&+

A9&#@29> 3"$+"(

B&&#%9' )((2>9@+9'( 0"#@ )&'212'2+(

ďŁŠ SAP AG 2006

The sales order is the basis of the sales process. Many different scenarios can be settled via the sales order in SD. Two scenarios which are typical for Accounting are introduced here as an example: The anonymous "#$%!&'!()&*+,-"!%.!"-&,/!and the 0#*%!-&!&)*%)!()&*+,-1&2!+"123!-4%!3%2%)#-1&2!&'! #!"%)51,%!#"!#2!%.#0($%.

Product sale ex stock: In this process, a sales order is created for material which is kept in inventory. Costs and revenues are derived automatically from the material production costs or from the SD sales prices. An outbound *%$15%)6!*&,+0%2- is created. The delivery cannot be billed until the goods have been removed from the stock and posted as goods issue. You can create a 7)#2"(&)-! 8)*%)! that generates a transfer order. The required goods are removed from the stock and prepared for delivery. The goods to be delivered are posted as 9&&*"!:""+%. In MM, a goods issue document and an accounting document in FI are created. The last step in the sales and distribution process is ;1$$123< An invoice document is created in SD and a printed invoice is sent to the customer. Billing is also the point when revenues are transferred to Controlling. When!=#60%2- has been made by the customer, you receive your money and post the receipt of payment in FI.

Producing a service represents, in contrast to ex stock sales, a direct "%)51,%"!3%2%)#-1&2!()&,%"" that can also be displayed via a sales order item. The sales order item is a ,&"-!>%#)%). This means that the costs, and also the revenues, can be posted individually and directly on the SD item. The steps incoming orders, billing, payment are nearly all identical to the steps in sales ex stock. However, in this services example, transport and delivery do not apply. The cost bearer sales order item can be posted for all transactions of the "%)51,%!3%2%)#-1&2 directly. When the service is completed, you can pass on the costs and revenues to the profitability analysis (CO-PA) via the 8)*%)!?%--$%0%2-.

ÂŠ SAP AG

TERP10

2-23

!"#$%&'()'*$+&',-.$/&,&$0 123()$4566&.7

<25$&.-$;2=$&8>-$,2* ! /-').(8-$,9-$:5;),(2;$2:$+&',-.$/&,&$

 SAP AG 2006

TERP10

2-24

!"#$%&'()'*$"+,-./(01$2-34/(-0'$5 6-,()$789+)/(:+'

>/$/?+$)-0)34'(-0$-@$/?('$/-,()A$<-4$B(33$8+$&83+$/-* ! !;,3&(0$!"#$&0&3</()&3$=$.+,-./(01$'-34/(-0'

 SAP AG 2006

TERP10

2-25

!"#"$%"&'()*+'$,)-.'/#+

0-45-' 2-"46#5."4 3&).'++5-7

0123 2-"46+5+$#))4+

!282 %29:; <0=>: 277&'7"#'?$5-@)&A"#5)-

0183

:F#'&-"4 ?"#"

E"#'&5"4+ A"-"7'A'-# >"4'+$"-? ?5+#&5C*#5)-

3&)?*.#5)/4"--5-7

D5-"-.5"4 "..)*-#5-7

0-45-' 8&"-+".#5)3&).'++5-7

B-#'7&"#'?$"//45."#5)-$A)?*4'+  SAP AG 2006

While you are using the transactions in the Logistics applications, the Logistics Information System (LIS) updates relevant information. You can also update information from other systems in the LIS.

The LIS aggregates and stores this information in the data warehouse. Data can be aggregated on a qualitative as well as on a quantitative basis: • quantitative reduction by aggregating on period level • qualitative reduction by selecting specific key figures

You can then use the tools in the Sales Information System (SIS) to analyze this aggregated information. The aggregation leads to an improvement of the response times and of the quality of the resulting reports.

TERP10

2-26

!"#$"%&$"'%()*+,-.$"/,01%2'-3.$"/,)4%/"-'%3,%$#

*+,-.$"/,) 4%/"-'%3,%$

A6#$'3,-# 56#"%,##)7-'&,##,# 7-'G6&$# 56#"%,##) H$-.$,?I

*-G,-# *:;7

1%2'-3.$"/,) 4%/"-'%3,%$

*:<7

4D$-.&$"'%

;-.%#2'-3.$"'%

E%'FB,G?,

!.$.)8.-,9'6#,

=>'3'?,%"@.$"'%) AB,.%#"%?C

ďŁŠ SAP AG 2006

SAP BW enables the analysis of data from operative SAP applications as well as all other business applications and external data sources such as databases, online services, and the Internet.

Administrator Workbench (AWB) functions allow you to control, monitor, and maintain all data procurement processes.

SAP BW enables Online Analytical Processing (OLAP) for staging information from large amounts of operative and historical data. OLAP technology permits multi-dimensional analyses according to various business perspectives.

The BW server, which is preconfigured by Business Content for core areas and processes, allows you to examine the relationships in every area within your company. Business Content provides targeted information to companies, divided into roles. This helps your employees to carry out their tasks. As well as roles, Business Content includes other preconfigured objects such as InfoCubes, queries, key figures, and characteristics. These objects facilitate the implementation of SAP BW.

The Business Explorer (BEx) component provides users with extensive analysis options.

ÂŠ SAP AG

TERP10

2-27

!"#$%&'()'*$"+,-./(01$2-34/(-0'$5 6-,()$2477&.8

:-4$&.+$0-;$&<3+$/-* ! !9,3&(0$!"#$.+,-./(01$'-34/(-0'

 SAP AG 2006

TERP10

2-28

!"#$%&'()'*$+,(-$./00&12

E3/$&18$,3:$&>A8$-3* ! #3'(-(3,(,4$35$"67$!,-8191('8$-3:&1;'$02.<# !"# ! =8')1(>8$-?8$02.<# !"#$314&,(@&-(3,&A$A8B8A'$ ! =8')1(>8$-?8$5/,)-(3,$35$02.<# !"#C&'-81 =&-& ! !D9A&(,$02.&9 !"#$18931-(,4$'3A/-(3,'

 SAP AG 2006

TERP10

2-29

!"#$%&'(&)*&+

203'&3'-4 ! ,)-./-$01$%&'(&)*&+

 SAP AG 2004

TERP10

3-1

!"#$%&'(&)*&+,$-./'$012&3'/*&4

"'$'6&$37.3=?4/7.$7:$'6/4$?./'B$C7?$>/==$1&$)1=&$'7, ! 5&43+/1&$'6&$37897.&.'4$7:$%&'(&)*&+ ! ;<9=)/.$67>$%&'(&)*&+$4?997+'4$'6&$1?4/.&44$ 9+73&44&4$ ! 5&43+/1&$'6&$4'+)'&@/3$)A*).')@&$7:$%&'(&)*&+

 SAP AG 2004

TERP10

3-2