Source: http://www.google.com/patents/US20020019778?dq=7,453,150
Timestamp: 2017-03-27 09:55:03
Document Index: 12003133

Matched Legal Cases: ['art 17', 'art 17', 'art 17', 'art 17', 'art 17', 'art 17']

Patent US20020019778 - System and method for placing on-line orders - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA system and method permitting the placement of orders and the accumulation of free product credits, wherein a user can select from a vendor's most commonly ordered products; recreate and/or edit past orders to expedite the placement of similar orders; transfer a large number of selected purchases to...http://www.google.com/patents/US20020019778?utm_source=gb-gplus-sharePatent US20020019778 - System and method for placing on-line ordersAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20020019778 A1Publication typeApplicationApplication numberUS 09/826,298Publication dateFeb 14, 2002Filing dateApr 4, 2001Priority dateApr 4, 2000Also published asCA2342971A1Publication number09826298, 826298, US 2002/0019778 A1, US 2002/019778 A1, US 20020019778 A1, US 20020019778A1, US 2002019778 A1, US 2002019778A1, US-A1-20020019778, US-A1-2002019778, US2002/0019778A1, US2002/019778A1, US20020019778 A1, US20020019778A1, US2002019778 A1, US2002019778A1InventorsLarry Isaacson, Matthew IsaacsonOriginal AssigneeLarry Isaacson, Matthew IsaacsonExport CitationBiBTeX, EndNote, RefManPatent Citations (6), Referenced by (49), Classifications (12), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetSystem and method for placing on-line orders
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS [0033] The ordering systems described herein are directed to managing an inventory of office and computer supplies. However, it will be apparent to one skilled in the art that these systems can be applicable to any electronic purchasing-vending relationship. [0034] System Configuration [0035] [0035]FIG. 1 shows a preferred embodiment of an ordering system, referred to herein inclusively as the System. The System includes a Past Order Tracking Module 10, a Purchase Order Module 14, a Requisition Pad template, referred to herein as Reqpad 12, a Purchase Order template 15, a Free Product Pad template 16, a Cart 17 template and a Credit Tracking Module 18. The role of each of these components is further described below. [0036] [0036]FIG. 2 illustrates the database structure behind the System. Databases 20 are, generally speaking, global databases that are shared by, or whose records are freely accessible by, all users of the System. The global databases include a Shared Main Catalog Database 22, a Shared Reqpad database 24, a Sessions Database 28, an Accounts Database 30, a Free Products database 32, and a Keywords Database 34. [0037] The Shared Main Catalog Database 22 contains information, including pricing, regarding the complete list of products sold by a vendor through the System. If desired, a Private Main Catalog Database 23 may be created for certain users with special discounts or other distinguishing considerations and may contain a customized list of products, prices and any other desired product information. The Private Main Catalog Database 23 is visible only to the specific user. In practice, the Private Main Catalog Database may be constructed from the Shared Main Catalog Database 22, e.g., by allowing access to certain fields or records based on user identification, or a completely separate database may be constructed. [0038] The Shared Reqpad Database 24 contains information regarding products most commonly ordered by all users of the system. The information preferably includes product categories for the most commonly ordered products, product item number, product description, product measurements, price and any other relevant information, including product image if available. The Shared Reqpad Database 24 is preferably relationally linked or indexed to the Shared Main Catalog Database 22 by item number, such as, for example, a prefix number or an item stock number. Preferably, a Private Reqpad Database 25 is created so as to contain customized information regarding products most commonly ordered by a specific user (or account) of the System, including custom pricing and categories. The Private Reqpad Database 25 is visible only to the specific user or account. In practice, Private Reqpad Database 25 may be constructed from the Shared Reqpad Database 24, e.g., by allowing access to certain fields or records based on user identification, or a completely separate database may be used. [0039] The Sessions Database 28 contains a unique record for each user in which the user's logon ID and password, as well as the current status of that user, e.g., valid, expired, guest visitor, and the like, are stored. The System also keeps tracks of each user's “session” and assigns or associates an identification code to each such session. Each unique record in the Session Database 28 stores the corresponding user's last session identification and whether the pending session is still valid. The unique user record also stores the number of free product credits accumulated by the user, last open order, and any other user-related information that a vendor would like to keep track of. [0040] The Accounts Database 30 contains information specific to a user's account, such as, for example, any specific discounts or credits or any other account-related information. The Accounts Database 30 also contains paths that indicate file names or URL locations of each user's private databases such as, for example, a Shopping Cart Database 38 (discussed below), the Private Reqpad Database 25, the Private Main Catalog Database 23, and any other databases specific to a given user. [0041] The Free Products Database 32 contains or points to a list of currently available products that a user can choose from to redeem accumulated free product credits. The Keywords Database 34 contains a list of search keywords to enable a user to search for a particular product if necessary. Preferably, the keywords are customized for each user or account, facilitating a user's familiarity with and ability to choose the right keywords to search for products. [0042] Whereas the Main Catalog Databases and the Reqpad Databases can be shared or private, depending on the arrangement between the user and the vendor, certain databases of the System are private for each account (or particular records thereof are only accessible by users associated with a particular account) and are referred to herein as Private Databases 26. Referring to FIG. 2, the Private Databases 26 include a Company Database 36 which contains users' billing addresses; Shopping Cart Database 38 which contains “shopping cart” data for each user, as explained in greater detail below, such that, preferably, each user has its own shopping cart file; DeptShip Database 40, which contains information regarding department shipping locations (if the user is a company) and alternate billing addresses for each user account; Forwd Database 42, containing information regarding orders currently pending approval for each account; and History Database 46, containing private history information for each account, including past order history. Each Private Database 26 is preferably relationally linked or indexed to the Session Database via the account identification. [0043] The System an be accessed remotely through a network connection or locally through a storage device such as a CD ROM disk installed on the user's computer or server, a magnetic medium or an EIP disk. [0044] [0044]FIG. 3A shows one implementation of the System where it is accessed through the Internet. A user connects to a website 200 via a network connection. The website 200 resides in a memory 202 (comprising volatile and non-volatile memory), where the System databases are located. The web application for the website 200 is run by a webserver 204. In a preferred implementation, the databases in the memory 202 are created in xBase iii format and the code for the client-side device or browser 205 is generated using a combination of Miva Script, HTML and JavaScript. Those skilled in the art will recognize that any suitable database product can be used. In this implementation the System can be used to generate a “remote” purchase order, the data of which resides on the server and can be immediately processed by the vendor. [0045] [0045]FIG. 3B shows another implementation of the System where it is accessed from a storage device, such as a CD-ROM 206. In this case, a user accesses the system through an input/output device 208, such as a graphic user interface (GUI), connected to the user's computer or server 210, which comprises a processor 212 to run the CD ROM 206. The databases on the CD-ROM 206 are preferably loaded into a memory 203, for example, by transfer from the CD-ROM 206 during installation. The CD-ROM 206 may be removably incorporated in the memory 203, for example, via a CD ROM drive or changer. In a preferred implementation, the databases in memory 202 are created in Visual Basic and MS Access, although those skilled in the art will recognize that any suitable database product can be used. In this implementation the System can be used to generate a “local” purchase order on the computer which can then be communicated as known in the art to the vendor over a communications network, or generate a paper copy of the purchase order which can be transmitted to the vendor via post or facsimile. [0046] Placing a Purchase Order Using a Reqpad [0047] Referring additionally to the flowchart of FIG. 4A, a user accesses the System by providing a member identification and password, step 302, which is verified against the Session Database 28, step 304, or by any other means known in the art. Once a user has accessed the System, it generates a main menu 310 that can contain a variety of options, but for the purposes of describing the System includes at least the following selections: [0048] option 312 for creating or using a Reqpad 12 to purchase products; [0049] option 314 for reviewing past order histories as a basis for purchasing products; and [0050] option 316 for ordering free products. [0051] Referring additionally to FIG. 4B, when the user selects the Reqpad option 312 the Purchase Order Module 14 generates and displays a Reqpad menu 220; steps 320, 322. FIG. 5A shows an example of the Reqpad menu 220, which lists or displays various categories of products. Preferably, the list is encapsulated in a scroll box 222. The user may scroll through the categories and choose to view a given category of products stored in the Shared Reqpad Database 22 (or, as the case may be, a Private Reqpad Database 23) or choose to view all products in all categories. The Reqpad menu categories can include, but are not limited to “show all categories,” batteries, binders, calculators, calendars/refills/bases, cartridges/laser/ink jet, clips, computer accessories; correction fluid; desk accessories; diskettes; envelopes & pockets; fans; folders; frames; indexes; labels; notebooks; pads; paper; paper supplies; pens/pencils/markers, POST-IT™ products, punches, ribbons, rolodexes/cards, rubber bands, rulers, shears, sheet protectors, staples/staplers, storage boxes, and tape/tape dispensers. The above categories are listed for illustrational purposes only and it will be understood that a variety of other categories can be included in addition to or instead of the categories listed above. [0052] The Reqpad menu 220 allows a user who has not yet decided upon a specific product to browse through all commonly ordered products in a given category. Additionally and/or alternatively, the user may review all products commonly ordered from a particular vendor. These tasks can be accomplished without having to utilize a search engine and having to continually devise queries, wait for the queries to be processed by the webserver 204 or computer 210 and wait for the responses to come back. The commonly ordered products stored in the Shared Reqpad Database 24 are selected using any number of criteria, such as, for example, a vendor's past experience with client preferences. Alternatively, the ordering system can track all purchases and store the data in a central database. The central database is dynamically updated with each subsequent purchase and a counter is activated and dynamically updated, keeping track of the number of times a given product was ordered and, optionally, the total monetary value expended on a given product over time. Based on the counter and in response to predetermined cut-off criteria, the most commonly ordered products are selected for placement into the Shared Reqpad Database 24. In addition to the criteria described above, the Private Reqpad Database 25 further can be customized based on customer preference; for example, a user may specify which categories, products and quantities of each product are most commonly ordered from the user's account. This information will be stored in the private Reqpad Database 25 and the Reqpad 12 for the customized account will be populated accordingly. Other criteria for selecting the most commonly ordered products for both shared and private accounts will be apparent to one skilled in the art. [0053] [0053]FIG. 5B shows an example screen display of a Reqpad 12 actuated from the Reqpad menu 220. More specifically, referring additionally to the flowchart of FIG. 4C, once the user actuates a category from the Reqpad menu 220, step 330, the selected category is used to query the Shared Reqpad Database 24, step 332. Based on the results of the query the System generates and displays a Reqpad 12 populated with information about the most commonly ordered products in the selected category, step 334. Some users may have a special account with the vendor, such as discounts based on bulk orders, custom pricing on a product-by-product bases or other price and product variances. For a user with a special account, the Reqpad 12 is populated with data from a Private Reqpad Database 23 and the System displays information for products most commonly ordered by that user (or account) as well as any applicable custom products and custom product categories. Unlike other ordering systems that require the user to do extensive searches to find the desired products, the user of the Reqpad 12 has ready access to the products that are most commonly ordered by all users of the system or by that particular user of the System. Preferably, the products are listed in alphabetical order although the products also can be listed in the order of increasing or decreasing price. [0054] As shown in FIG. 5B, the Reqpad 12 preferably comprises the following fields: [0055] Item Number 500; [0056] Description 502; [0057] Unit of Measure (UM) 504, such as a case, a box, a package, a carton, etc.; [0058] Price 506; [0059] a Quantity (QTY) 508 input field or box; and [0060] More 510, which provides icons and/or links or hyperlinks to other webpages or data, such as the suggested retail price as compared to the system's product list price, a picture of the product, if a picture is available, and any other useful information. [0061] A variety of other fields can be used in addition to or instead of the fields discussed above in order to carry out the purpose of the ordering program and system described herein. [0062] The user can select any desired product in any category by entering the amount of each product that he or she desires to purchase or contemplates purchasing in the Quantity input field or box 508, step 336. For example, the user can select one or more products in the “Binders” category by entering the desired quantity of each product in the corresponding Quantity input fields or boxes 508, then switch to the “Clips” category and select one or more products there by inputting the desired quantity and then switch to the “Computer Accessories” category and so on until the user has selected all desired products in all categories of interest to the user. Each time the user enters a number or value in a Quantity input field or boxes 508, the server captures the quantity, step 338 and updates the Shopping Cart Database 38, step 340. In this manner, the System eliminates the use of an “enter” button or similar mechanism, and in fact it should be noticed from FIG. 5B that the Reqpad 12 does not have such a button on it. Similarly, each time a user changes the number value in a Quantity input field or boxes 508, the server captures the new quantity and updates the Shopping Cart Database 38. Finally, each time a user changes the number value in a Quantity input field or boxes 508 to zero (0), the server captures the new quantity and updates the Shopping Cart Database 38 to remove the nulled product from the user's selections. The automated quantity capture is preferably implemented using a server-side script or program, e.g., a Miva Script, which controls the input field or boxes 508. [0063] If a user wishes to purchase a product that is not listed on the Reqpad 12, the Reqpad menu 220 preferably offers the user access to a search engine for searching the Shared Main Catalog Database 22 or, as the case may be, the Private Main Catalog Database 23. The user then selects the desired products by inputting the quantity as described above. [0064] Once the selection process is complete, the user has a choice to complete the purchase order or first to review and, if necessary, edit the order. Referring to FIG. 5B, if the user chooses to complete the purchase order, he or she clicks or otherwise activates a “next” button 514 or other graphic user interface (GUI) element. Referring additionally to the flowchart of FIG. 4D, the Purchase Order Module 14 then generates a purchase order form, referred to herein as a Purchase Order template 15, based on the data previously captured from the user and stored in the Shopping Cart Database 38, step 350. The Purchase Order Module preferably also obtains shipping and account information, step 352, and any other desired information which the merchant wishes to display, step 354, on the purchase order. This enables a user to select as many products in as many categories as the user may desire and then perform only a single action to place all of the desired products on the Purchase Order template 15. [0065] [0065]FIG. 6 shows an example screen display of the Purchase Order template 15. The illustrated Purchase Order template 15 includes the following fields for each product entry: [0066] Item Number 600; [0067] Product Description 602; [0068] Quantity (QTY) 604; [0069] Unit of Measure (UM) 606; [0070] List Price 608 for one product; [0071] Sell Price 610 for one product; [0072] Total 612, indicating the total price for the selected quantity of each product; and [0073] Remarks 614, which can include a special notice regarding a product or its delivery information, where appropriate. [0074] It will be understood that the Purchase Order template 15 shown in FIG. 6 is used for illustration purposes only and that many other representations are possible. [0075] After viewing the Requisition Order 15, the user can print and approve or cancel the order by use of known GUI icons and functions. When the order is submitted, step 360, the Forwd Database 42, the Session Database 28, Account Database 30 and History Database 46 are updated, steps 362, 364, 366, and 368. [0076] Referring back to FIG. 5B, the user need not go directly to the Purchase Order template 15 after completing the Reqpad 12 selection process. Instead, the user first can choose to review and, if necessary, edit the selected products and quantities. To do this, the user clicks or otherwise activates a “cart” button 512 or similar GUI. Referring additionally to the flowchart of FIG. 4E, the Purchase Order Module 14 then generates a virtual shopping cart, also referred to herein as a Cart template 17, based on the data previously captured from the user and stored in the Shopping Cart Database 38, steps 370 and 372. Again, a user can select as many products in as many categories as the user may desire and then perform only a single action to place all of the desired products on the Cart 17. [0077] Referring to FIG. 7, an embodiment of the Cart 17 can include the following fields for each product entry: [0078] Item Number 700; [0079] product description 702; [0080] Unit of Measure (UM) 704, such as a case, a box, a package, a carton, etc; [0081] Price 706 per product; [0082] Quantity (Qty) 708; [0083] Total Price 710, indicating the total price for the selected quantity of each product; [0084] Edit 712; [0085] Delete (Del) 714; and [0086] Remarks 716, which can include a special notice regarding a product or its delivery information, where appropriate. [0087] The Edit 712 and Delete 714 fields are associated with GUI buttons allowing a user to interact with the program. If the user activates the Edit 712 GUI button, the System allows the user to change the selected quantity of the entry being edited and to enter any remarks, steps 374, 376 and 378. If the user activates the Delete 714 GUI button, the System deletes the selected entry, step 375. [0088] If, after reviewing and, if necessary, editing the information displayed in the Cart 17, the user would like to purchase the displayed items, the user activates the “send” GUI button and the Purchase Order Module 14 generates the Purchase Order 15 and transfers all of the user entries thereto, step 380. The user can then print and accept or cancel the order as described above. [0089] Alternatively, from Cart 17, the System allows a user to return to the main menu or to Reqpad 12, or to search the system for other products of interest, among many other options. Until the final purchase is approved, the System provides the user with options to return to the main menu, search the Reqpad 12 or the entire system and order nonstock products as well as any other desired options. [0090] Free Product Credits [0091] Each time a user approves a Purchase Order 15, the Purchase Order Module 14 transfers the order data to the Credit Tracking Module 18, which generates a specific amount of free product credits that are stored in the Accounts Database 30. The number of credits earned towards free products can, for example, be based on the total dollar value of the purchase order. The free product credits can be redeemed for selected items of the vendor's merchandise, which are stored in the Free Products Database 32. The credits can, but do not need to be, redeemed at the time of placing the order entitling the user to such credits. The Credit Tracking Module 18 accumulates the free product credits, up to a predefined maximum amount allowed by the System, deducts the amount of free-product credits redeemed in exchange for products, and adjusts the available credit balance accordingly. A user can, but does not have to redeem all of the accumulated free product credits at one time; if the user redeems only some of the credits, the Credit Tracking Module 18 adjusts the available credit balance accordingly, and the user can redeem some or all of the remaining credits at a subsequent time. [0092] If desired for practical purposes, the system Credit Tracking Module 18 can be programmed to cause the expiration of all credits remaining unredeemed after a given time limit, such as months or years. Accumulating free product credits for use at a later time allows users that place multiple but small dollar value orders to make the best use of their credits. [0093] When a user is ready to redeem some or all of the free-product credits, the Credit Tracking Module 18 generates a page referred to herein as a Free Product Pad 16. The Free Product Pad 16 is populated with data from the Accounts Database 30 and the Free Products Database 32. The Free Product Pad 16 displays the total amount of credits available to the user. Preferably the total amount of available credits is represented as a dollar amount. Preferably, the Free Product Pad 16 also displays a free product list which is similar to the list of Reqpad 12, except that the products are listed in the order or increasing dollar value rather than alphabetically. The user can scroll through the list to determine the value of and further information about each product on the list and can follow links leading to yet further information and, if available, pictures of each product. The user can select to purchase a product or products in exchange for all or a part of the accumulated free product credits. The selection and purchasing process for the free products are preferably similar to the selection and purchasing processes described above in connection with placing a purchase order. [0094] For example, the Free Product Pad 16, can include the following fields: Item Number; Description; Unit of Measure (UM), such as a case, a box, a package, a carton, etc.; Credits, representing the dollar value of the product; and More. Clicking on the More field will link the user to a further description and picture of the product. The user can select to order a given quantity of each free product, as long as the cost of the order does not exceed the amount of accumulated credits. [0095] In order to maximize the user's options, the Free Products Database 32 also can be searched by means of a search engine, a browser or any other means known in the art. [0096] Thus, the System enables the user to quickly and conveniently order products while at the same time accumulating free product credits redeemable either at the time of purchase or at a later point in time, for the same merchandize that the user is willing to spend money to buy in the first place. [0097] Placing a Purchase Order by Recreating a Past Order [0098] The information from each order processed by the Purchase Order Module 14 is transferred to the Past Order Tracking Module 10 which stores the data in the History Database 46. A user can choose to recreate a portion or all of a previously placed order, and if so, the user selects from the main menu the option 314 to review past order histories. Referring additionally to the flowchart of FIG. 4F, the System allows a user to review and browse through all of the user's past orders or to perform a search for specific past orders, step 390. If the user chooses to perform a search, it can be performed by one or more filters, such as, for example, by purchase order number, department, item number, manufacturer, product description, and any other filter programmed into the System for the convenience of the user. [0099] Once the search is performed, step 394, the Purchase Order Module 14 displays a list of all previous purchase orders stored in the History Database 46 which match the search criteria, step 396. The user can select one of these, step 398, in which case the Purchase Order Module 14 generates a historical order form, step 400, based on information retrieved from the History Database 46. An example historical order form 800 is shown in FIG. 8. The form 800 enables the user to select any or all previously ordered products, as provided by an Add to Cart checkbox 802. If the user activates the “Re-Create” GUI button 804, the Purchase Order Module 14 captures the selected products and adds the data to the Cart 17, step 402. The user can then review and edit the information as necessary, as described above. If the user is satisfied with the re-created and/or edited order, the user can proceed to the Purchase Order Pad 15 as described above and complete the purchase in the usual manner. [0100] In one embodiment of the invention, the user can recreate a past order for the purpose of returning products listed in that order. To do so, preferably the user enters a preassigned Return Materials Authorization Number, confirming that the user is authorized to return the goods. The return order is then submitted in the same way that a new order is submitted. [0101] Those skilled in the art will understand that numerous variations and modifications may be made to the specific embodiments described herein without departing from the spirit and scope of the invention. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5056019 *Aug 29, 1989Oct 8, 1991Citicorp Pos Information Servies, Inc.Automated purchase reward accounting system and methodUS5774870 *Dec 14, 1995Jun 30, 1998Netcentives, Inc.Fully integrated, on-line interactive frequency and award redemption programUS6009412 *Jun 25, 1998Dec 28, 1999Netcentives, Inc.Fully integrated on-line interactive frequency and award redemption programUS6061660 *Mar 18, 1998May 9, 2000York EgglestonSystem and method for incentive programs and award fulfillmentUS6134557 *Nov 20, 1998Oct 17, 2000Matlink, Inc.Materials and supplies ordering systemUS6829586 *Aug 25, 2003Dec 7, 2004Richard PostrelMethod and system for aggregation of reward points for payment of auctioned items* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS6937999 *Nov 10, 2000Aug 30, 2005Hewlett-Packard Development Company L.P.Reorder-assistance functionality levelsUS7225146 *Sep 27, 2001May 29, 2007I2 Technologies Us, Inc.Method, system and article of manufacturing for dynamic database redirection using semantic taxonomy informationUS7263499 *Jan 24, 2002Aug 28, 2007Sony Computer Entertainment Inc.Electronic commerce system in which commodities are displayed in combination with background imagesUS7548350 *Mar 20, 2003Jun 16, 2009International Business Machines CorporationMethod and apparatus for interactively scanning images into a logical structureUS7647250 *Mar 4, 2005Jan 12, 2010Sap AgMethod and program product for event monitoringUS7660742Sep 2, 2004Feb 9, 2010Sap AktiengesellschaftMethod of and system for processing purchase ordersUS7725358 *Dec 28, 2005May 25, 2010United Services Automobile Association (Usaa)System and method for providing multiple real-time pricing quotes based on optional consumer variablesUS7734601Oct 31, 2005Jun 8, 2010Sap AgIntegration of digital asset management with intellectual property managementUS7747471Dec 28, 2005Jun 29, 2010United Services Automobile Association (Usaa)System and method for providing multiple real-time pricing quotes based on optional consumer variablesUS7761313 *Dec 28, 2005Jul 20, 2010United Services Automobile Association (Usaa)System and method for providing multiple real-time pricing quotes based on optional consumer variablesUS7805335Jul 30, 2004Sep 28, 2010Sap AgPurchase list having status indicatorsUS7813949Mar 8, 2005Oct 12, 2010Sap AgMethod and system for flexible budgeting in a purchase order systemUS7840534 *Oct 31, 2005Nov 23, 2010Sap AgIntegration of a digital asset management system with a network sales systemUS7962377Jan 31, 2005Jun 14, 2011Sap AktiengesellschaftComputer program product for purchase order processingUS7983962Mar 7, 2005Jul 19, 2011Sap AktiengesellschaftMethod and system for purchase order data entryUS8027886Aug 10, 2004Sep 27, 2011Sap AktiengesellschaftProgram product for purchase order processingUS8046273Mar 8, 2005Oct 25, 2011Sap AgSystem and method for purchase order creation, procurement, and controllingUS8050956Mar 7, 2005Nov 1, 2011Sap AgComputer-readable medium, program product, and system for providing a schedule bar with event dates to monitor procurement of a productUS8050990Nov 4, 2004Nov 1, 2011Sap AgMethod of and system for generating purchase orders using an auction processUS8117078Nov 3, 2009Feb 14, 2012Sap AgMethod and program product for event monitoringUS8171050Jul 8, 2008May 1, 2012Datavine Research ServicesMethod and apparatus for access, integration, and analysis of heterogeneous data sources via the manipulation of metadata objectsUS8185417 *Jul 16, 2010May 22, 2012United Services Automobile Association (Usaa)System and method for providing multiple real-time pricing quotes based on optional consumer variablesUS8423428Aug 10, 2004Apr 16, 2013Sap AgMethod for allocation of budget to order periods and delivery periods in a purchase order systemUS9390420 *Dec 19, 2008Jul 12, 2016At&T Intellectual Property I, L.P.System and method for wireless ordering using speech recognitionUS20020046132 *Jul 30, 2001Apr 18, 2002Raye Julie A.Method of selecting feminine care products and processing orders thereforUS20020111882 *Jan 24, 2002Aug 15, 2002Hisayuki KunigitaElectronic commerce system, commodity purchase assistance method, and commodity purchase assistance apparatusUS20020165832 *Dec 13, 2001Nov 7, 2002Fujitsu LimitedProduct information management systemUS20030061060 *Sep 27, 2001Mar 27, 2003I2 Technologies Us, Inc.Dynamic database redirection using semantic taxonomy informationUS20030097316 *Nov 18, 2002May 22, 2003American Management SystemsMethod and system of managing procurement processes by manipulating line itemsUS20030197896 *Mar 20, 2003Oct 23, 2003International Business Machines CorporationMethod and apparatus for interactively scanning images into a logical structureUS20030220850 *Apr 1, 2003Nov 27, 2003Te-Mei ChuMethod and system for online managing product deliveryUS20050197914 *Aug 10, 2004Sep 8, 2005Sap AktiengesellschaftSystem for and method of purchase order processingUS20050203817 *Mar 4, 2005Sep 15, 2005Sap AktiengesellschaftEvent management method and systemUS20050216325 *Mar 7, 2005Sep 29, 2005Sap AktiengesellschaftProcurement workbenchUS20050216357 *Jul 30, 2004Sep 29, 2005Sap AktiengesellschaftPurchase list having status indicatorsUS20050216375 *Mar 8, 2005Sep 29, 2005Sap AktiengesellschaftMethod and system for flexible budgeting in a purchase order systemUS20050240488 *Jan 31, 2005Oct 27, 2005Sap AktiengesellschaftMethod and apparatus for purchase order processingUS20060015417 *Mar 7, 2005Jan 19, 2006Sap AktiengesellschaftMethod and system for purchase order data entryUS20060179062 *Oct 31, 2005Aug 10, 2006Jutta WeberIntegration of a digital asset management system with a network sales systemUS20060218148 *Oct 31, 2005Sep 28, 2006Jutta WeberIntegration of digital asset management with intellectual property managementUS20070106560 *Nov 10, 2005May 10, 2007Ford Motor CompanyElectronic, computer-implemented method and system of tracking purchase order historyUS20070226155 *Mar 29, 2002Sep 27, 2007Jai-Jein YuExtended attribute-based pricing system and methodUS20080249656 *Mar 31, 2008Oct 9, 2008Parag GokhaleSystems and methods of media management, such as management of media to and from a media storage libraryUS20080270456 *Jul 8, 2008Oct 30, 2008David EpsteinMethod and Apparatus for Access, Integration, and Analysis of Heterogeneous Data Sources Via the Manipulation of Metadata ObjectsUS20100049582 *Nov 3, 2009Feb 25, 2010Sap AgMethod and program product for event monitoringUS20100161446 *Dec 19, 2008Jun 24, 2010At&T Intellectual Property I, L.P.System and method for wireless ordering using speech recognitionUS20100235274 *Mar 3, 2006Sep 16, 2010Yu-Chiuan ChenAnti-terror platform for securing a community against terrorismsUS20130030847 *Jul 30, 2012Jan 31, 2013The Crawford Group, Inc.Method and Apparatus for Expedited Rental Vehicle Reservation Creation Following a Previous ReservationUS20140095335 *Feb 20, 2013Apr 3, 2014Interactive Memories, Inc.Method for Dynamic Invoicing of Print Vendors at Real-Time Negotiated or Advertised Pricing for Online Printing Services* Cited by examinerClassifications U.S. Classification705/26.1, 705/28, 709/217International ClassificationG06Q10/08, G06Q30/02, G06Q30/06Cooperative ClassificationG06Q30/0601, G06Q10/087, G06Q30/02European ClassificationG06Q30/02, G06Q10/087, G06Q30/0601Legal EventsDateCodeEventDescriptionJun 25, 2001ASAssignmentOwner name: ROSIE & MIKE LLC, NEW YORKFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ISAACSON, LARRY;ISAACSON, MATTHEW;REEL/FRAME:011925/0142Effective date: 20010615Aug 30, 2001ASAssignmentOwner name: ROSY & MIKE LLC, NEW YORKFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ISAACSON, LARRY;ISAACSON, MATTHEW;REEL/FRAME:012126/0172Effective date: 20010824RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services