SAP Business One DI Event Service Article

Transcription

1 SAP Business One DI Event Service Article Applies T: SAP Business One / SAP Business One SDK. Fr mre infrmatin, visit the Business One hmepage.. Summary This article describes hw t define and implement a DI Event Service that runs n tp f the existing SAP Business One SDK interfaces. This service will prvide ntificatin f events related t SAP Business One DI API bjects thrugh a listener-based interface. Tgether with this article yu can dwnlad an implementatin sample. The develpment envirnment chsen is.net, fr bth C# and VB.NET prgramming languages. Authr: SAP B1 Slutin Architects Cmpany: SAP Created n: 28 February SAP AG 1

2 Table f Cntents Intrductin... 3 Interface... 3 B1DIEventsListener Cnstructr... 4 Cnnect Methd... 4 AddListener Methd... 4 RemveListener Methd... 5 Discnnect Methd... 5 Architecture... 6 Server... 8 B1DIEventService... 9 Installatin Installing the Server Installing the Client Cnfiguratin Server Client Trubleshting Hw t Dwnlad Annexe B1DIEventService.dll, B1DIEventsService Interface SBO_SP_TransactinNtificatin Cde Client cde sample Client and Server Cnfiguratin File Related Cntent Cpyright SAP AG 2

3 Intrductin Actually the SDK DI API des nt ffer a way t be ntified when a DI API bject has been added/updated/remved in the database. The nly accepted pssibility t implement this kind f ntificatin by partners is t place sme cde int the SBO_SP_TransactinNtificatin stred prcedure; usually this cde calls a dll that uses DI API methds t perfrm sme callback actins (please refer t the SDN dcument Using the SBO_SP_TransactinNtificatin Stred Prcedure which includes a cde sample). This apprach has the main drawback that several add-ns need t add cde int the SBO_SP_TransactinNtificatin stred prcedure and this can cause cnfusin and difficulty when add-ns need t interwrk. T avid this issue and prpse a mre usable interface we have develped the SAP Business One DI Event Service. This service ffers an easy t use high-level interface integrated with the SDK. In this article we prpse then a listener-based interface fr data event ntificatin tgether with a sample reference implementatin. This cde is delivered as a sample and it is nt supprted; yu can change it in rder t imprve the quality f service f the prpsed implementatin accrding t the needs yu have in yur slutins. Interface The bjective f this service is t prvide a high-level interface integrated with the SDK and allw several add-ns t share the service in charge f the events ntificatin. The prpsed interface ffers the pssibility t cnnect t the service and t register a methd fr every event yur add-n wants t be ntified. Once yu register a methd fr an event, this methd will be called every time the crrespnding transactin is perfrmed in the Database. Let s suppse yu want t write a new line in a file every time a new Item is added in the database. T d that yu nly need t cnnect t the B1DIEventService and t register the methd adding the line in the file as a listener fr the Add Items transactin. After registratin, yur methd will be called autmatically every time a new Item is added. // Cnnect t the B1DIEventsService B1DIEventsService dieventsservice = new B1DIEventsService(Cmpany); dieventsservice.cnnect(cnnectinlst_listener); // Add a listener fr the transactin Add Items dieventsservice.addlistener(sapbbscom.bobjecttypes.items.tstring(), B1DIEventTransactinTypes.Add.TString(), AddItems_Listener) // Declaratin f the listener methd adding a line in the file public vid AddItems_Listener(B1DIEventService.B1DIEventArgs eventinf) {... } 2011 SAP AG 3

4 Fllwing subsectins explain ne by ne the main methds ffered by this interface. B1DIEventsListener Cnstructr public B1DIEventsService(SAPbbsCOM.Cmpany Cmpany) In rder t cnnect t the service yu need t create a reference f the B1DIEventsListener bject. B1DIEvents cnstructr receives the current cmpany yu are cnnected t as a parameter; it will use this cmpany reference t btain the database name and the lcatin f the server. The use f this reference als cntrls the user has the authrizatin t access DI bjects. If yu need t be ntified fr the transactins taking place in mre than ne database yu need t create ne instance f the B1DIEventsService class per each database yu need t be ntified. Cnnect Methd public vid Cnnect(B1DIEventsCnnectinLstListenerDelegate listener) Cnnects t the B1DIEventServer lcated in the machine where the Cmpany database is lcated. As a parameter yu must specify the methd t be called if a prblem arrives and the cnnectin with the server is lst. This methd must fllw the mdel fixed by the B1DIEventsCnnectinLstDelegate. Next figure shws an example: // Declaratin f the listener methd t be called if cnnectin lst public vid CnnectinLst_Listener() {... } AddListener Methd public vid AddListener( string bjtype, string transtype, B1DIEventsListenerDelegate listener) The AddListener methd allws yu t register the methd t be called by the B1DIEventService when the crrespnding event ccurs. The required parameters are: 1. A string representing the bject type. Yu can btain this string frm the SBObbsCOM.BObjectTypes enum. Example: SAPbbsCOM.BObjectTypes.BusinessPartners.TString() Ntes: * T register a listener fr all bject types yu need t pass an empty string. * If yu want t add a listener fr an bject type nt defined by BObjectTypes yu can directly use a string enclsing the number identifying the bject type. * If yu want t add a listener fr an existing UDO yu can place directly the cde f the UDO as bject type SAP AG 4

5 2. A string representing the transactin type. Yu can btain this string frm the B1DIEventsService.B1DIEventsTransactinTypes enum. Example: B1DIEventsService.B1DIEventsTransactinTypes.Add.TString() In rder t register a listener fr all transactin types yu need t pass an empty string. 3. A pinter t a delegate methd defined in the add-n cde by fllwing the mdel fixed by the B1DIEventsListenerDelegate. Example: // Declaratin f the listener methd t be called fr Items Add transactin public vid AddItems_Listener(B1DIEventsService.B1DIEventArgs eventinf) {... // Delegate methd mdel public delegate vid B1DIEventListenerDelegate(B1DIEventArgs eventinf); RemveListener Methd public vid RemveListener( string bjtype, string transtype) Yu can stp receiving ntificatins n a specific event by calling the RemveListener methd. The parameters are: 1. A string representing the bject type, see AddListener first parameter. 2. A string representing the transactin type, see AddListener secnd parameter. Discnnect Methd public vid Discnnect() T stp receiving all events and discnnect frm the B1DIEventService yu have t call the Discnnect methd. Please d nt frget t call this methd befre yu stp yur add-n, therwise the resurces allcated fr the cnnectin will nt be crrectly freed SAP AG 5

6 Architecture We prpse here a sample reference implementatin f this service. This implementatin is based n a client-server architecture where: A server is in charge f cllecting transactins infrmatin frm the database and sending ntificatins t the registered clients. Add-ns that want t receive ntificatins use a client dll. This client dll expses the listener based interface described abve, and interact with the server hiding all the cmmunicatin details t the add-ns This implementatin sample has been develped in C# and the interface allws using it by prgramming in.net languages. Tgether with the service implementatin we prvide a cuple f sample f add-ns; ne in C# and anther VB.NET. The technlgy emplyed t cmmunicate between client/server applicatins are:.net Remting. MSMQ Yu can dwnlad the cde sample f this implementatin and change/custmize the technlgies used fr yur specific need. With this sample we want t shw hw easy is t create a generic server that can be used by several add-ns. Yu can dwnlad the setup ready t be installed and the whle surce cde as well SAP AG 6

7 Next figure shws the different mdules cmpsing the B1DIEventService prpsed. The mdules clred in blue represent the cmpnents f the B1DIEventsService, the mdules in range are external cmpnents and the light blue mdule represents a partner add-n using the service thrugh the B1DIEventService interface. Partner add-n B1DIEventService Cnnect AddListener RemveListener Discnnect Call listeners MSMQ.NET Remting Client Server B1DIEventServer DB SBO_SP_TransactinNtificatin B1DIEventSender 2011 SAP AG 7

8 Server The server is cmpsed f 2 mdules: B1DIEventServer. Windws service applicatin called SAP Business One DI Event Service that Creates a.net Remting service. All clients will cnnect t the same.net Remting singletn. Cntrls per each client the keep-alive messages. Each client sends peridically a keep-alive message by calling a.net Remting methd ffered by the server; the server cnsiders a client as dead and remves all its listeners after a perid f time defined in the cnfiguratin file by the element keepalivemax (cf. Client and Server Cnfiguratin File). Per each database transactin (infrmatin received frm the B1DIEventSender), psts a new message n the MSMQ f each registered client. Each client has a separate MSMQ lcally, when the client reads a message it is autmatically remved frm the queue. If the netwrk cnnectin breaks dwn fr a shrt perid f time, the messages are autmatically kept by MSMQ in the server side and will be sent t the client queue when the cnnectin is re-established. N messages are then lst if the time the cnnectin is dwn is inferir t the keepalivemax parameter defined in the cnfiguratin file (cf. Client and Server Cnfiguratin File). The messages will remain in the MSMQ fr a maximum number f hurs defined in the cnfiguratin file by the element messagelife (cf. Client and Server Cnfiguratin File), after this time elapsed the messages are autmatically destryed. B1DIEventSender. Library autmatically called frm the SBO_SP_TransactinNtificatin stred prcedure (cf. SBO_SP_TransactinNtificatin Cde) inside the B1 database per each database transactin. This library will send the transactin infrmatin t the B1DIEventServer Windws Service thrugh sckets SAP AG 8

9 B1DIEventService The B1DIEventService is a library that bth client and server must cmpile with (nthing t be changed by the partner). It acts as a filter taking simple cmmands frm the client applicatin and implementing the technical part f the cnnectin with the B1DIEventServer. This library ffers the B1DIEventListener interface and is in charge f: Cnnect t the B1DIEventServer in the DB machine using.net Remting interface, a cnfiguratin file cntains the registered server prt number. Create a MSMQ lcally where the server will pst all events infrmatin. When called frm the Add-On, call an equivalent functin in the B1DIEventServer. Per each message received in the MSMQ (frm the server) call the registered methd in the add-n cde (registering is dne with AddListener methd). Sends keep-alive messages peridically t the server. T avid keeping in the server listeners that are nt anymre needed (ex: client applicatin stpped), the B1DIEventService will autmatically send keep-alive messages t the server. The perid between tw keep-alive messages is fixed in the client and server cnfiguratin file by the keepalive element. The server will cnsider the client applicatin as dead after a maximum perid f time fixed by the element keepalivemax cnfiguratin file. T send the keep-alive messages the service calls a.net Remting methd defined by the B1DIEventsServer. Tracks the number f keep-alive messages failed and alerts the client applicatin when the number exceeds a maximum defined by keepalivemax / keepalive (bth values defined in the cnfiguratin file). T alert the client the service calls the listener methd given at the cnnectin. Yu can have a lk t the B1DIEventsService.dll interface n annex B1DIEventService.dll, B1DIEventsService Interface SAP AG 9

10 Installatin B1DIEvents service installatin is separated in tw packages: ne fr the server and ne fr the client. Installing the Server T install B1DIEventsService server yu need t run the Setup.exe inside the B1DIEventsServerSetup. Once installed yu will have a directry called B1DIEventsService/B1DIEventsServer (in the place yu chse during installatin) cntaining: A directry called B1DIEventsServerService. This directry cntains a windws service executable. Nte: The service is nly registered; yu need t start it frm the services windw (Cntrl Panel->Administrative Tls- >Services). The server takes sme secnds t stp running after stpping the service; please wait until the server is stpped t try t run it ne mre time (B1DIEventsServer.exe prcess). If between the Start/Stp service the server is nt cmpletely stpped an errr message will prmpt ( Cannt start the SAP Business One DI Event Service service n Lcal Cmputer. ). A directry called SBO_SP_TransactinNtificatin. This directry cntains: A txt file named SBO_SP_TransactinNtificatin. Yu need t cpy the cntent f this txt file int the SBO_SP_TransactinNtificatin already existing in yur B1 database. A library called B1DIEventsSender.dll. Once the SBO_SP_TransactinNtificatin mdified, per each db transactin this library will be called. Yu dn t need t d anything with this library; it is already registered and cnnects autmatically t the server windws service SAP AG 10

11 Installing the Client T have the B1DIEventsService client side installed yu need t run the Setup.exe inside the B1DIEventsClientSetup. Once the setup run yu will have a directry called B1DIEventsService/B1DIEventsClient (in the place yu chse during installatin) cntaining: A directry called B1DIEventsService cntaining The library called B1DIEventsLibrary.dll. Yur add-ns must add a reference t this library in rder t use the prpsed interface and register yur add-n t the B1DIEventsServerService. A cnfiguratin xml file mdel enclsing infrmatin abut the netwrk cnnectin plus settings n the traces files. If B1DIEventsClient is installed the registry key HKEY_LOCAL_MACHINE/Sftware/SAP/SAP Business One DIEventsService/B1DIEventsClient will pint t the cnfiguratin file lcatin. If yu haven t installed B1DIEventsClient in a machine where yur add-n will run yu have tw ptins: create this registry entry during yur add-n installatin pinting t the right directry r put the cnfiguratin file in the same directry as yur add-n executable. A Samples directry. Inside it yu will find tw cde samples, ne in Vb.NET and anther in C#. Yu can use these samples in rder t guide yu n hw t use the B1DIEventsService. As the events will be sent by using MSMQ technlgy yu need t install the MSMQ Windws service in bth client and server machine. The steps t fllw are: Inside cntrl panel select Add r Remve prgrams Click n Add/Remve Windws Cmpnents Select Message Queuing check bx and fllw the standard installatin SAP AG 11

12 Cnfiguratin In rder t be able t run the B1DIEventsService yu need t cnfigure bth client and server machines and t add sme cde int yur add-n. The fllwing sectins explain in detail what needs t be dne. Server Befre being able t use the B1DIEventsService sme steps must be fllwed: 1. Cpy the cde inside the text file SBO_SP_TransactinNtificatin.txt (Figure 2) int the SBO_SP_TransactinNtificatin stred prcedure f the B1 database yu want t wrk with. The SBO_SP_TransactinNtificatin stred prcedure is created autmatically when yu create a new cmpany in SAP Business One. If yu need mre infrmatin please have a lk t the SDN CdeSample called Using the SBO_SP_TransactinNtificatin Stred Prcedure. 2. Start the SAP Business One DI Event Service windws service frm the Services windw list (Cntrl Panel -> Administrative Tls -> Services). Yu can change the Startup type prperty n the service t have it aut started when OS starts. 3. Change the cnfiguratin file if needed; cf. Client and Server Cnfiguratin File t have mre infrmatin. Server cnfiguratin file sets the server cnfiguratin and it is lcated inside the B1DIEventsServerService directry. The default parameters are defined t wrk withut any changes, if yu change smething in the server side please be careful and cmpare it t the client cnfiguratin. A traces file is autmatically created while server is running. The settings defining this file are in the cnfiguratin file. The default lcatin f the traces file is the directry defined by the registry HKEY_LOCAL_MACHINE/Sftware/SAP/SAP Business One DIEventsService/B1DIEventsServer. Client In rder t cnnect t the B1DIEventsServerService yu need t add sme cde in yur add-n t cnnect t the server and register the events yu want t be ntified. After B1DIEventsClient installed yu have tw samples resuming hw t cnnect and register t the server, ne cded in Vb.Net and anther in C#. As a first step yu can have a lk t these samples and run them, they will shw yu hw t use the interface. Once yu understand hw the client samples are wrking yu shuld be ready t add the needed cde in yur add-ns t manage the B1DIEventsService. Here yu have the basic steps t fllw: 1. Add a reference t the B1DIEventsService.dll 2. Implement the cde needed t create an instance f the B1DIEventsService class. Please remember yu need ne instance f B1DIEventsService per each different database yu want t receive the B1DIEvents frm. The cnstructr f the B1DIEventsService class receives the SAPbbsCOM.Cmpany reference the add-n is cnnected t as parameter; the server lcatin will be btained frm the Cmpany reference. 3. Add a methd fllwing the delegate mdel B1DIEventsCnnectinLstDelegate (Figure 7: Delegate methd mdel fr the CnnectinLst event.). 4. Call the Cnnect methd n the B1DIEventsService instance yu have just created. Yu need t specify the methd defined in pint Add a methd fllwing the delegate mdel n the B1DIEventsService class per each event yu want t be ntified (Figure 5: Delegate methd mdel fr the DB transactins events.) SAP AG 12

13 6. Add a listener t the B1DIEventsListener instance per each event yu want t be ntified by calling AddListener methd. Yu will need t specify: a. The bject type. b. The transactin type. c. One f the methds yu have defined in pint Add a call t the Discnnect methd n the B1DIEventsService befre the client applicatin stps. It is very imprtant t call this methd befre stpping yur add-n, the server receives a peridically keep alive message frm each client. The server cnsiders a client as discnnected after keepalivemax time is elapsed. The client cnsiders a server as dead after a time equivalent t keepalivemax / keepalive times the keep alive hasn t been received. Nevertheless during this time the server will cntinue sending requests t the client and will lse perfrmance if the client is stpped withut sending a discnnect message. Als cnnectins will nt be prperly clsed and perfrmances can be highly affected in bth client and server machines. 8. There is a cnfiguratin file fr the client applicatin, please have a lk t sectin Client and Server Cnfiguratin File. This cnfiguratin file is lcated after B1DIEventsService installatin n the SAP Business One DI Event Service/ SAP Business One DI Event Client/B1DIEventsService directry. The default parameters are already set t wrk withut any changes, if yu change smething in the client side please be careful and check it is cmpatible with the server cnfiguratin. The B1DIEventsService searches fr the cnfiguratin file inside the installatin directry defined by the registry HKEY_LOCAL_MACHINE/Sftware/SAP/SAP Business One DIEventsService/B1DIEventsClient. If this registry des nt exist it searches in the directry where the client applicatin runs. If yu haven t installed B1DIEventsClient in a machine where yur add-n will run yu have tw ptins: create this registry entry during yur add-n installatin with the right directry r put the cnfiguratin file in the same directry as yur add-n executable. A traces file will be autmatically created while yur applicatin using the B1DIEventsService.dll is running. The settings defining this file are in the cnfiguratin file. The default lcatin f the traces file is the directry defined by the registry HKEY_LOCAL_MACHINE/Sftware/SAP/SAP Business One DIEventsService/B1DIEventsClient if yu have installed the B1DIEventsService in the client machine r the directry where yur applicatin runs. Sme cde lines resuming the client cding steps are lcated in annex Client cde sample. Trubleshting If yu have prblems while installing/cnfiguring the DIEventService yu can tell us thrugh the SAP Business One Develpment Frum with the prefix B1DIEventService:. There are already several messages talking abut DIEventService in the SDK frum. There is als a sectin in the B1 FAQs wiki page; yu can cntribute t this page by sharing yur tips and tricks SAP AG 13

14 Hw t Dwnlad Frm this article yu can dwnlad the surce cde f the B1DIEventService and als the installatin packages f the B1DIEventService fr SAP Business One versins 2004 and Fr each setup versin yu have the setup fr the client and server installatin. SAP Business One DI Event Service - Setup package fr B SP01 SAP Business One DI Event Service - Setup package fr B SAP Business One DI Event Service Setup package 32 bit fr B1 8.8 SAP Business One DI Event Service Setup package 64 bit fr B1 8.8 SAP Business One DI Event Service Surce Cde The B1DIEventService is given as a free surce cde and therefre there is n supprt by SAP fr the prvided tls. If yu have any cmments regarding this service please create a new message int the SAP Business One Develpment Frum with the prefix B1DIEventService: in the title t be able t easily identify it SAP AG 14

15 Annexe B1DIEventService.dll, B1DIEventsService Interface /// Manages the cnnectin t the B1DIEventsServer. /// Yu must create ne instance per Cmpany yu want t be ntified public B1DIEventsService(SAPbbsCOM.Cmpany Cmpany) { } /// Creates a netwrk channel and cnnects t the B1DIEventServer public vid Cnnect(B1DIEventsCnnectinLstDelegate listener) { } /// Adds a listener fr an bjecttype tgether with a transactin type public vid AddListener( string bjtype, string transtype, B1DIEventsListenerDelegate listener) { } /// Remves the listener fr an bjecttype and a transactin type public vid RemveListener( string bjtype, string transtype) { } /// Remves all listeners and discnnects frm the Server public vid Discnnect() { } Figure 1: B1DIEventsService interface 2011 SAP AG 15

16 SBO_SP_TransactinNtificatin Cde int --declare the bject variable int --declare the hresult variable nvarchar(120) -- database name = db_name() = sp_oacreate OUT = <> 0 BEGIN EXEC RETURN END Figure 2: Cde t be placed in SBO_SP_TransactinNtificatin. Nte: The lgdb methd expects parameter f type nvarchar(20). Check that yur SBO_SP_TransactinNtificatin stred prcedure has it declared as nvarchar(20), change it if it is nt the case. Client cde sample Cnnectin // Create an instance f the listener service evtservice = new B1DIEventService(Cmpany) evtservice.cnnect(cnnectinlst_listener) // Add a listener methd per each grup: bjtype + transactin Type evtservice.addlistener(sapbbscom.bobjecttypes.items.tstring(), B1DIEventTransactinTypes.Add.TString(), AddItems_Listener) Discnnectin // Remve a listener evtservice.remvelistener(sapbbscom.bobjecttypes.items.tstring(), B1DIEventTransactinTypes.Add.TString()) // Discnnect the service evtservice.discnnect() Figure 3: Client Cde sample, hw t register a listener SAP AG 16

17 // AddItems Delegate implementatin in the add-ns side public vid AddItems_Listener(B1DIEventService.B1DIEventArgs eventinf) { Figure 4: Client Cde sample, hw t declare a listener methd fr the DB transactins events. // Delegate methd mdel public delegate vid B1DIEventListenerDelegate(B1DIEventArgs eventinf); Figure 5: Delegate methd mdel fr the DB transactins events. // CnnectinLst Delegate implementatin in the add-ns side public vid CnnectinLst_Listener() { Figure 6: Client Cde sample, hw t declare a listener methd fr the CnnectinLst event. // Delegate methd mdel public delegate vid B1DIEventsCnnectinLstDelegate(); Figure 7: Delegate methd mdel fr the CnnectinLst event. Client and Server Cnfiguratin File Partners can change several parameters fr the executin f the server and client applicatins. The default cnfiguratin values are set t wrk withut any changes, if yu change smething in the client side please be careful and check it is cmpatible with the server cnfiguratin. The cnfigurable parameters are the same fr bth client and server: Relating t the.net Remting cnfiguratin channelprt: Prt number the server registers fr.net Remting service and the client cnnects t. keepalive: Time elapsed between tw keep-alive messages sent by the client applicatin. keepalivemax: Maximum perid f time the server will wait between 2 keep-alives messages frm a client. The server cnsiders a client as discnnected after this time elapsed. The client cnsiders the server as dead after keepalivemax/keepalive times the call t the keep-alive methd in the server fails SAP AG 17

18 messagelife: Number f hurs the event messages are kept in the MSMQ while waiting t be read. After this number f hurs elapsed the event will be autmatically destryed if the client hasn t read it befre (messages are autmatically remved when read frm the client). Relating t the traces file dirpath: Directry where the traces file will be created ( a Lg directry will be autmatically created inside it). When n directry specified the Lgs directry is created inside the directry where the service/server is installed. level: Level t trace: Verbse, Inf r Warning csvseparatr: Traces files will be text files with csv separatrs in case yu want t read them with excel. The partner can chse whether they want t have a, r a ; separatr. maxfilesize: Maximum size f the traces file after which a new file will be created r the actual ne will be emptied. maxsizeactin: After the traces file pass the maxfilesize parameter there are tw pssibilities: create a new file with the actual date/time and leave the ld ne r replace the ld ne with a new empty ne. <?xml versin="1.0"?> <cnfiguratin> <remting> <channelprt>4334</channelprt> <!-- same fr client and server (default 4334) --> <keepalive> </keepalive> <!-- millisecnds between 2 keepalive (df )--> <keepalivemax> </keepalivemax> <!-- max between 2 keepalive (df )--> <messagelife>36</messagelife> <!-- nb hurs messages kept in msmq (df. 36h)--> </remting> <tracer> <dirpath></dirpath> <!-- Cmplete path (default "" = cnfigdir/lgs) --> <level>warning</level> <!-- "Verbse" "Inf" "Warning" (default Warning)--> <csvseparatr>;</csvseparatr> <!-- "," ";" (default ";")--> <maxfilesize> </maxfilesize> <!-- traces file max size (df. 6M)--> <maxsizeactin>replace</maxsizeactin> <!-- CreateNew, Replace (df. Replace)--> </tracer> </cnfiguratin> Figure 8: Client and Server Cnfiguratin file SAP AG 18

19 Related Cntent Fr mre infrmatin, visit the Business One hmepage SAP AG 19

20 Cpyright Cpyright 2011 SAP AG. All rights reserved. N part f this publicatin may be reprduced r transmitted in any frm r fr any purpse withut the express permissin f SAP AG. The infrmatin cntained herein may be changed withut prir ntice. Sme sftware prducts marketed by SAP AG and its distributrs cntain prprietary sftware cmpnents f ther sftware vendrs. Micrsft, Windws, Excel, Outlk, and PwerPint are registered trademarks f Micrsft Crpratin. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PwerVM, Pwer Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPwer, PwerPC, BatchPipes, BladeCenter, System Strage, GPFS, HACMP, RETAIN, DB2 Cnnect, RACF, Redbks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivli and Infrmix are trademarks r registered trademarks f IBM Crpratin. Linux is the registered trademark f Linus Trvalds in the U.S. and ther cuntries. Adbe, the Adbe lg, Acrbat, PstScript, and Reader are either trademarks r registered trademarks f Adbe Systems Incrprated in the United States and/r ther cuntries. Oracle is a registered trademark f Oracle Crpratin. UNIX, X/Open, OSF/1, and Mtif are registered trademarks f the Open Grup. Citrix, ICA, Prgram Neighbrhd, MetaFrame, WinFrame, VideFrame, and MultiWin are trademarks r registered trademarks f Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks r registered trademarks f W3C, Wrld Wide Web Cnsrtium, Massachusetts Institute f Technlgy. Java is a registered trademark f Sun Micrsystems, Inc. JavaScript is a registered trademark f Sun Micrsystems, Inc., used under license fr technlgy invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and ther SAP prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f SAP AG in Germany and ther cuntries. Business Objects and the Business Objects lg, BusinessObjects, Crystal Reprts, Crystal Decisins, Web Intelligence, Xcelsius, and ther Business Objects prducts and services mentined herein as well as their respective lgs are trademarks r registered trademarks f Business Objects S.A. in the United States and in ther cuntries. Business Objects is an SAP cmpany. All ther prduct and service names mentined are the trademarks f their respective cmpanies. Data cntained in this dcument serves infrmatinal purpses nly. Natinal prduct specificatins may vary. These materials are subject t change withut ntice. These materials are prvided by SAP AG and its affiliated cmpanies ("SAP Grup") fr infrmatinal purpses nly, withut representatin r warranty f any kind, and SAP Grup shall nt be liable fr errrs r missins with respect t the materials. The nly warranties fr SAP Grup prducts and services are thse that are set frth in the express warranty statements accmpanying such prducts and services, if any. Nthing herein shuld be cnstrued as cnstituting an additinal warranty SAP AG 20