throbber
From:
`eernl'lard Neumann.
`Sent51l4!19971:07 .AM.
`:re-.························;;et"er"L~te.nz·:··iMiiiie~·M·~~.:;i:· ·· ····· · · ·-·············· ···················· · .. , ........................... ···· ······ ·····································································--··········w··················w·······
`c ;···· ··········-· ··H"~;;;;·c,i;;;h"·R;g9e r.k"~;n·;;n;: · "P;i;~-z;;;~;· ···-·····-········~··· ·--·· ·-· ··--···-· ··-··· ........................ -··--· ··········· ··· ............................... - .... ___ ............. ..
`8~~·.···· ....................................................................... ................................................................................................................ ___ ............................................................................. .
`.... · ......................... '·· . ......... ········-····"· .... ··············· '............ .
`. .............. .................. ' ................ _.,, ......... ·-·· ............................. - ~·-·· ·-· ·· ........ ~--· .............. .......
`. ... .
`Subject: Pricing Engine: Summary of telephone call.
`
`Page 1 of l
`
`Hello Wilfried,
`I would like to summarize again my response/suggestions to your
`question "How can the SCE Team support the development of the
`price engine?":
`
`Starting point:
`- SPE (Price Engine) is to be implemented in JAVA
`SPE is to interact closely with SCE
`- SPE is to interact closely with "SAP-SF A development results"
`SF A and SCE need SPE
`In WD, there is a price expert who can participate X% (50?), but
`hardly any other resources
`- The project is to be the responsibility of SD
`
`Suggestion/response:
`- We could enter into negotiations with Trilogy in order to
`purchase their code for the SC Pricer (Trilogy may continue to use
`it) and in order to then enhance it where necessary.
`or
`
`- I will take on the SPE development as an additional project, with
`reporting to SD (Wit fried)
`i.e. it is an SD development
`- The price expert spends 14-day periods here for explanation,
`verification of the price logic etc .• he can otherwise be contacted
`via ProShare and has access to all data. lie would be required to
`participate in developing formal algorithmic descriptions. He is
`part of the team, does not necessarily have to implement.
`- I will be able to procure 2 additional resources from IntelliCorp
`for the development and would try to involve another SAP
`America consultant (or someone from the GG Team?).
`- The Java/etc. experience of my team is accessible
`- The closer linking ofSPE & SCE is easier to do
`- The interaction of SFA & SPE is easier to do
`(data replication ... )
`- The work could start 2 weeks after the decision is made.
`
`In general, I am willing to provide the price expert (Wolfgang)
`with an impression of the Java development project, he can gladly
`spend some time here.
`However, I am convinced that we need at least 3-4 people in order
`to implement a solution swiftly.
`
`We are also gladly willing during our visits to WD approx. every 3
`months to provide on-site support, and otherwise by telephone.
`
`While there are 8 employees ( 4 SAP, l TDV, 3 I C) who work on
`the SCE, this is primarily so because otherwise we would launch
`too late.
`I.e. unfortunately I cannot just simply give up colleagues in order
`to support a project in WD.
`
`Regards,
`Bernhard
`
`PX 1089
`
`'I
`1
`
`CONFIDENTIAL- A ITORNEYS' EYES ONLY
`
`VSAP _02461044
`
`HIGHLY CONFIDENTIAL
`
`VERSATA EXHIBIT 2033
`SAP v. VERSATA
`CASE CBM2012-00001
`
`VER0002035243
`
`

`

`TRANSLATOR CERTIFICATION
`
`I, Kerstin Roland, a translator fluent in the German and English
`languages, on behalf of Morningside Translations, do solemnly and
`sincerely declare that the following is, to the best of my knowledge and
`belief, a true and correct translation of the document(s) listed below in a
`form that best reflects the intention and meaning of the original text.
`
`MORNINGSIDE TRANSLATIONS
`
`Signature of Translator
`
`Date: June 22, 2009
`
`Description of Documents Translated:
`
`MC~20-20090615 - ! - VSAP_02461044 - ]]nglish T~sl~on.doc
`
`HIGHLY CONFIDENTIAL
`
`VER0002035244
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket