The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Oct. 22, 2013
Filed:
Dec. 15, 2006
Abhinava Pratap Singh, Uttarpara, IN;
Andreas Esau, Oestringen, DE;
Andreas Huber-buschbeck, Heiligkreuzsteinach, DE;
Andreas Seibel, Rauenberg, DE;
Astrid Doppenschmidt, Muhlhausen, DE;
Bleickard Langendoerfer, Heidelberg, DE;
Chandramohan Reddy Yengoti, Heidelberg, DE;
Christian Hissler, Nonnweiler, DE;
Cornel Leinenkugel, Dossenheim, DE;
Devasena Rajamohan, Santa Clara, CA (US);
Gerd Egen, Dossenheim, DE;
Gerold Wellenhofer, Heidelberg, DE;
Gregor Arlt, Heidelberg, DE;
Hans-peter Thienel, Wiesloch, DE;
Heiko Theissen, Heidelberg, DE;
Jens-martin Wolle, Leimen, DE;
Jerome Poulin, Montreal, CA;
Kerstin Hambrecht, Heidelberg, DE;
Klaus Zumbach, Schoenbrunn-Allemuhl, DE;
Madhavi Koujalagi, Bangalore, IN;
Moghaddam Masoumeh, Trippstadt, DE;
Oliver Vonderheid, Ludwigshafen, DE;
Ralf Wagenknecht, Boehl-Iggelheim, DE;
Siarhei Ulasenka, Mannheim, DE;
Stefan Christian Boehm, Bruhl, DE;
Susanne Doenig, Puettlingen, DE;
Svetlana Rebholz, Rhein, DE;
Thiemo Lindemann, Spechbach, DE;
Thomas Schneider, Heidelberg, DE;
Udo Herbst, Pfedelbach, DE;
Uwe Oehler, Offenburg-Zunsweier, DE;
Rolf Waltemathe, Blieskastel, DE;
Carsten Pluder, Spiesen-Elversberg, DE;
Harsh Panwar, Bangalore, IN;
Eberhard Schick, Heidelberg, DE;
Corinne Reisert, Mannheim, DE;
Juergen Hollberg, Wiesloch, DE;
Peter Wadewitz, Hockenheim, DE;
Shankar V, Bangalore, IN;
Christof Rausse, Heidelberg, DE;
Abhinava Pratap Singh, Uttarpara, IN;
Andreas Esau, Oestringen, DE;
Andreas Huber-Buschbeck, Heiligkreuzsteinach, DE;
Andreas Seibel, Rauenberg, DE;
Astrid Doppenschmidt, Muhlhausen, DE;
Bleickard Langendoerfer, Heidelberg, DE;
Chandramohan Reddy Yengoti, Heidelberg, DE;
Christian Hissler, Nonnweiler, DE;
Cornel Leinenkugel, Dossenheim, DE;
Devasena Rajamohan, Santa Clara, CA (US);
Gerd Egen, Dossenheim, DE;
Gerold Wellenhofer, Heidelberg, DE;
Gregor Arlt, Heidelberg, DE;
Hans-Peter Thienel, Wiesloch, DE;
Heiko Theissen, Heidelberg, DE;
Jens-Martin Wolle, Leimen, DE;
Jerome Poulin, Montreal, CA;
Kerstin Hambrecht, Heidelberg, DE;
Klaus Zumbach, Schoenbrunn-Allemuhl, DE;
Madhavi Koujalagi, Bangalore, IN;
Moghaddam Masoumeh, Trippstadt, DE;
Oliver Vonderheid, Ludwigshafen, DE;
Ralf Wagenknecht, Boehl-Iggelheim, DE;
Siarhei Ulasenka, Mannheim, DE;
Stefan Christian Boehm, Bruhl, DE;
Susanne Doenig, Puettlingen, DE;
Svetlana Rebholz, Rhein, DE;
Thiemo Lindemann, Spechbach, DE;
Thomas Schneider, Heidelberg, DE;
Udo Herbst, Pfedelbach, DE;
Uwe Oehler, Offenburg-Zunsweier, DE;
Rolf Waltemathe, Blieskastel, DE;
Carsten Pluder, Spiesen-Elversberg, DE;
Harsh Panwar, Bangalore, IN;
Eberhard Schick, Heidelberg, DE;
Corinne Reisert, Mannheim, DE;
Juergen Hollberg, Wiesloch, DE;
Peter Wadewitz, Hockenheim, DE;
Shankar V, Bangalore, IN;
Christof Rausse, Heidelberg, DE;
SAP AG, Walldorf, DE;
Abstract
A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction.