Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
  • G06Q40/02—Banking, e.g. interest calculation or account maintenance

Definitions

• the present invention relates to methods, apparatus and systems for doing business over a network, and more particularly to methods, apparatus and systems for performing network-based peer-to-peer business transactions.
• ERP Enterprise Resource Planning
• back-end processes are the business processes that support "doing business," that is, selling a company's products or services, and buying the goods and services that a company needs to produce its product or service.
• Back-end business processes include processes such as generating requisitions, searching supplier's catalogs, choosing products to purchase, generating purchase orders, generating sales orders, generating invoices, and paying invoices.
• orders do not get processed, goods do not get shipped, and invoices do not get generated or paid, unless they are channeled through an ERP system.
• FIG. 1 is a diagram of the information flow of a prior art business transaction, illustrating some of these problems.
• a buyer enters purchase information, such as price, quantity, and authorization to purchase, into a buyer's ERP system 105.
• Buyer's ERP system 105 automatically generates a purchase order (PO) 110 based on the purchase information, typically printing out a hardcopy to send to a seller 125.
• Purchase order 110 is generally a standard business form with the purchase information filled into the appropriate fields. The buyer takes the hardcopy PO and manually faxes it, using fax machine 115, to seller's fax machine 20. In some cases, PO 110 may be mailed to seller 125.
• Some modern ERP systems have a built-in fax capability such that they can directly fax PO 110 to the seller's fax machine 120, removing the need for the the buyer to manually feed the hardcopy into fax machine 115. In any case, problems often arise because the buyer has no way of knowing exactly when seller 25 actually received and took action on PO 110.
• seller's fax machine 120 If seller's fax machine 120 is out of paper, unattended, or in an out-of-the-way mail room, • or if PO 110 is lost in the mail, there can be significant delays before seller 125 receives it and takes action.
• seller 125 Upon receiving PO 115 on fax machine 120, seller 125 takes the fax hardcopy and enters the purchase information from it into personal computer 130. Problems often arise during this step of a conventional business transaction as data entry errors are common. Fax copies are frequently hard to read, especially if the print is small, making data entry of faxes prone to errors.
• Personal computer 130 transmits the entered purchase information to a seller's ERP system 135, which typically generates a sales order (not shown) and order confirmation (not shown).
• EDI Electronic Document Interchange
• An EDI system prescribes the format of the data that two entities exchange to complete a process so users must comply with the format.
• EDI systems use different document standards to exchange information.
• different EDI systems use different exchange mechanisms (for example, data networks) to transmit electronic documents between buyers and sellers.
• EDI standards are: X12, EDIFACT, and TRADACOM. Each standard has multiple versions. For example, ANSI X12 has over 20 versions. The first version 2000 was approved by ANSI on Feb. 1986. The most recent version is 4020. EDIFACT has about nine versions. The first one (98A) came out on May 1994. The most recent version is 98A on March 1998.
• ANSI X12 uses a three digit number to designate each document. For example, "850” is used for a purchase order and "810" for and invoice. There are more than 250 different documents specified in X12. The most commonly used documents are: 850, Purchase Order; 855, Purchase Order Response; 860, Purchase Order Change; 865, Purchase Order Change Response; 810, Invoice; 832, Sales Catalog; and 997, Acknowledgment.
• the most common EDI exchange mechanism is a point-to-point connection. A point-to-point connection is typically a dial up connection or a dedicated line between two businesses. Another common exchange mechanism is a "Value Added Network" (VAN).
• VAN is a private, closed EDI network that provides point-to-point communication with other previously subscribed businesses connected to the same closed network. Connectivity to the VAN hubs is via telephone lines, both dial-up and dedicated.
• Authentication is provided by the private nature of the network. Only prearranged users and data flows are allowed by the operator of the VAN hubs. Data security is provided by the telephone infrastructure. The protocols used for data communication must be determined in advance by trading parties and generally are neither open nor consistent between VANs.
• One objective of the present invention is to integrate the conventional digital marketplace with conventional ERP system technologies to create a system that enables users to perform complex business transactions over an open network, such as the Internet.
• Such a system connects a user's ERP system, as the buyer or the seller, to their business partner's ERP system.
• Another objective of the present invention is to provide a system that enables users and other market participants to virtually congregate, exchange information, and complete e-commerce transactions through an efficient electronic marketplace.
• a third objective of the present invention is to provide methods and systems with the ability to execute online the entire array of business transactions involved in traditional commerce.
• a related objective is to enable ERP systems, after organizations initiate a business transaction, to take care of the integrated flow of information, services, goods, and money automatically over the network. Additional objects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objects and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
• the present invention provides a method, system, and apparatus for exchanging electronic business information or documents over an open network between a first ERP system and a second ERP system.
• the present invention receives an electronic business information from the first ERP system and transmits the electronic business document to the second ERP system.
• the present invention determines whether the second data format is different from the first data format and translates, if the second data format is different from the first data format, the electronic business information from the first data format into the second data format before transmitting it to the second ERP system.
• the present invention may also store a copy of the electronic business information for later auditing.
• the present invention may also enforce a business information exchange process while electronic business documents and information are exchanged between the two ERP systems.
• the electronic business information contains a sender identification
• the present invention may determine whether the sender identification provides authorization to transmit the electronic business document and prevent transmission of the electronic business document to the second ERP system if the sender identification does not provide authorization.
• the open network is the Internet.
• Figure 1 is a diagram illustrating the information flow of a prior art business transaction
• Figure 2 is a flowchart showing the steps of a typical business transaction
• FIG. 3 is a block diagram illustrating the architecture of a system consistent with the principles of the present invention.
• Figures 4A and 4B are a flowchart showing the steps in a method for performing network-based peer-to-peer business transactions consistent with the principles of the present invention
• Figure 5 is a block diagram illustrating the information path of a business document exchange in a system consistent with the principles of the present invention
• Figure 6 is a flowchart showing the steps in a method for performing business document exchange consistent with the principles of the present invention.
• An ERP system is a system that integrates various business application areas within a company, such as financial accounting, controlling, asset management, materials management, production planning and production control, sales and distribution, quality management, plant maintenance, project management, service management, human resources, office communication, workflow functions, and industry solutions.
• An ERP system combines technology with comprehensive business functions to produce a high level of application integration, which ensures that all ERP system functions can be accessed directly throughout the system. For example, an ERP system holds the current date in a common database accessible to all applications supported by the system; thus, all applications consistently use the same date.
• An ERP system does not use independent and individual application modules to perform business processes. Instead, data and functions within the system are integrated with each other, which enables the system to smoothly perform cross-application business processes.
• An ERP system typically has a modular software architecture based upon a software-oriented client-server model. This architecture allows users to flexibly plan and operate their individual ERP system installations. Within this architecture, an ERP system may be configured centrally or as a distributed system with numerous dedicated servers. This architecture provides separate application logic, application presentations, and databases. Such separation allows the user to distribute loads in the client- server configuration and take advantage of the performance potential and various cost structures of present and future hardware generations. The ERP system's architecture also allows the user to adjust (scale) the performance of the installed host services if, for example, load profiles change as a result of increasing user numbers or because additional components are added.
• A. Overview FIG. 2 is a flow chart showing the steps of a typical method of doing business.
• a business entity desiring to do business first must find a potential business partner (step 205). Buyers must find sellers, and sellers must find buyers. For example, a buyer looking for a seller might use the yellow pages, referrals from other business partners, a World Wide Web search engine, or unsolicited advertisements to help find potential business partners.
• the business entity gains access to information about the potential business partner and exchanges information with the potential business partner (step 210). For example, a buyer may get information about a seller's reputation from the Better Business Bureau. A buyer may gain access to information about a seller's products and prices through a product catalog. And, the buyer may get information about a possible transaction by exchanging offer, counteroffer, delivery date, and other information with the seller.
• the business entity makes the decision whether or not to "do business" (step 215). For example, a buyer may decide to purchase 100 items from the seller at the seller's catalog price or the buyer may decide to buy from someone else.
• business entity decides not to do business, then it returns to step 205 to find other potential business partners. If the business entity decides to do business, then business documents are exchanged with the business partner to implement the transaction (step 220). For example, a buyer may give the seller a purchase order (PO) for 100 items at the catalog price. The seller responds by giving the buyer an order confirmation. When the items are shipped, the seller gives the buyer an invoice. And, when the items are accepted, the buyer responds by giving the seller payment.
• PO purchase order
• Systems, methods, and apparatus consistent with the principles of the present invention enable an organization to find a business partner, communicate with it, and automatically exchange business documents over an open network to complete a business transaction.
• the present invention integrates a network-based digital marketplace that is open to everyone, not just pre-arranged subscribers, with business document exchange between ERP systems.
• the present invention provides a World Wide Web portal comprising a business directory and a messaging engine.
• the business directory lists all the organizations participating in the "digital marketplace" provided by the portal.
• a portal user searches the business directory to find potential business partners (step 205). For example, a buyer may search the business directory by product sought, geographical location, price, availability, seller's name, or a combination of these attributes.
• the business directory contains comprehensive information concerning all the members of a business ecosystem, such as buyers, sellers, distributors, service providers, and manufacturers.
• the business directory also provides access to product catalogs, prices, websites, reputation assessments, and contact information for the businesses listed, among other things.
• a portal user can often get all the information needed to make a business decision (step 210) by using the business directory. And, with the contact information provided by the business directory, a portal user can easily establish communications with a prospective business partner and exchange additional information.
• both partners can complete the transaction using their existing back- end ERP systems to automatically exchange the necessary electronic business documents (step 220) through the portal's messaging engine.
• the messaging engine provides the services necessary for back-end ERP systems to communicate with each other across an open network, such as the Internet. For example, a buyer may enter purchase information into its ERP system, which generates a purchase order. The buyer's ERP system automatically transmits the PO to the web portal messaging engine. Upon receipt, the messaging engine translates the PO into a format that the seller's ERP system understands, if necessary, and retransmits it to the seller's ERP system.
• the seller's ERP system responds by transmitting an order confirmation back to the portal messaging engine, which, in turn, translates and retransmits the order confirmation to the buyer's ERP system.
• the portal messaging engine which, in turn, translates and retransmits the order confirmation to the buyer's ERP system.
• business documents continue to be exchanged automatically until the transaction is completed.
• steps according to the present invention are embodied in machine-executable software instructions and the present invention is carried out in a processing system or systems by a processor executing the instructions, as will be described in greater detail below.
• processor executing the instructions as will be described in greater detail below.
• other embodiments, for example hardwired circuitry may be used in place of, or in combination with, software instructions to implement the present invention.
• FIG. 3 is a block diagram illustrating the architecture of a system 305 consistent with the principles of the present invention.
• a buyer's system 310 comprises a procurement server 312 communicatively connected to a back-end ERP system 314, which itself is communicatively connected to a business communications connector 316.
• Business communications connector 316 is communicatively connected to a network 320, through a firewall 318.
• Procurement server 312 is also communicatively connected to network 320.
• Network 320 is a conventional, open digital network, such as the Internet (the World Wide Web).
• Procurement server 312 is preferably a high-speed workstation, such as a Sun (TM) workstation or a personal computer (PC) equipped with a Pentium III (TM) processor by Intel corporation, running business-to-business procurement software such as that produced by SAP AG, the assignee of the present invention.
• procurement server 312 includes a conventional web browser for gaining access to web page information, such as product catalogs, on the World Wide Web.
• a buyer uses procurement server 312 to find and purchase needed products and services. Its functions, among others, include finding sellers, selecting products, and inputting information for POs.
• Procurement server 312 communicates information, including purchase information, to back-end ERP system 314 for processing.
• Back-end ERP system 314 is also preferably a high-speed work station or server running full capability ERP system software, such as SAP AG's R/3 (TM) System.
• Back-end ERP system 314 automates business processes, tracks work flow, and generates business documents, among other things. For example, back-end ERP system 314 can receive purchase information from procurement server 312 and decide whether to reject the information or generate a valid purchase order.
• Business communications connector 316 is preferably a software module or program running on the same high-speed server hosting back-end ERP system 314.
• Business communications connector 316 is communicatively connected to an open network 320, such as the World Wide Web, through a conventional firewall 318.
• Business communications connector 316 includes the network connection information and protocols necessary to communicate with a secure message engine 340 included in a network portal 370 over network 320.
• Business communications connector 316's functions include receiving business documents from back-end ERP system 314 and transmitting them to secure messaging engine 340, and receiving business documents from secure messaging engine 340 and transmitting them to back-end ERP system 314.
• the system architecture includes a seller's system 350, which is similar to buyer's system 310 as just described.
• Seller's system 350 comprises an online store/catalog server 352 communicatively connected to a back-end ERP system 354, which itself is communicatively connected to a business communications connector 356.
• Business communications connector 356 is communicatively connected to a network 320, through a conventional firewall 358.
• Online store/catalog server 352 is also communicatively connected to network 320.
• Online store/catalog server 352 is preferably a high-speed workstation, such as a Sun (TM) workstation or a personal computer (PC) equipped with a Pentium III (TM) processor by Intel corporation, running online sales software such as the Online Store or Customer Relationship Management software packages produced by SAP AG.
• online store/catalog server 352's primary function, among other functions, is to offer customers a self-service browser-based interface that lets them purchase products via network 320.
• Online store/catalog server 352 communicates information, such as Sales Order information, to back-end ERP system 354 for processing.
• Back-end ERP system 354 is also preferably a high-speed work station or server running full capability ERP system software, such as SAP AG's R/3 (TM) System.
• Back-end ERP system 354 automates business processes, tracks work flow, and generates business documents, among other things.
• back-end ERP system 354 can receive sales order information from online store/catalog server 352 and decide whether to reject the information or generate a valid sales order.
• back-end ERP system 354 can communicate "available quantity" information for a product to online store/catalog server 352 for display in an online catalog.
• Business communications connector 356 is preferably a software module or program running on the same high-speed server hosting back-end ERP system 356.
• Business communications connector 356 is communicatively connected to a network 320, such as the World Wide Web, through a conventional firewall 358.
• Business communications connector 356 includes the network connection information and protocols necessary to communicate with a secure message engine 340, included in network portal 370, over network 320.
• Business communications connector 356's functions include receiving business documents from back-end ERP system 354 and transmitting them to secure messaging engine 340, and receiving business documents from secure messaging engine 340 and transmitting them to back-end ERP system 354.
• the system architecture of FIG. 3 shows a network portal 370, which includes a search engine 330, a business directory 335, and a secure messaging engine 340.
• Network portal 370 is communicatively connected to network 320, which is preferably the Internet.
• a user with access to network 320 can reach network portal 370 and its included components by conventional means, for example, by using a Universal Resource Locator.
• Secure messaging engine 340 is communicatively connected to business directory 335, and search engine 330 is also communicatively connected to business directory 335.
• Search engine 330, business directory 335, and secure messaging engine 340 are preferably all software modules or programs running on a high-performance server, such as those produced by Sun Microsystems Corp.
• secure messaging engine 340 is communicatively connected to network 320 and via network 320 can communicate with business communications connector 316 in buyer's system 310 and business communications connector 356 in seller's system 350.
• Secure messaging engine 340's functions include, among other things, providing a secure communications path for business document exchange between buyer's system 310 and seller's system 350. Buyers and sellers communicate with each other and exchange electronic business documents through secure messaging engine 340.
• secure messaging engine 340 gets information it needs to provide the communications path between seller's system 350 and buyer's system 310 from business directory 335.
• Business directory 335 contains information about business and organizations that are users of network portal 370. This information includes contact information, online catalog information, and network communication routing information. Using business directory 335, portal users can find each other and become business partners. Search engine 330 helps a user find information in business directory
• search engine 330 allows users to search business directory 335 based on product, service, business name, geography, industry- standard classifications, keywords, full-text searches, or a combination of these parameters. Search engine 330 helps buyers and sellers listed in business directory 335 find each other and helps them exchange and access information about each other. For example, as shown by arrow 360 in FIG. 3, a user at procurement server 312 can communicate with search engine 330 via network 320 using, for example, a conventional browser. The user may locate a promising-looking seller of a desired product in business directory 335 and follow a link from the seller's business directory entry to the seller's online catalog hosted on online store/catalog server 352, as shown by arrow 365. The user can then use the online catalog to get product, price, and availability information.
• network 320 may be two separate networks, one of which connects buyer's system 310 and web portal 370 and the other of which connects seller's system 350 and web portal 370.
• network 320 may be two separate networks, one of which connects buyer's system 310 and web portal 370 and the other of which connects seller's system 350 and web portal 370.
• aspects of one embodiment are depicted as being hosted on specific computers and servers, one skilled in the art will appreciate that all or some of these aspects may be stored or hosted on different computers remotely located from those shown.
• business directory 335 and secure messaging engine 340 could be hosted on separate servers communicatively connected to network 320.
• FIG. 4A depicts a flowchart of the steps in a process for performing network-based peer-to-peer business transactions consistent with the principles of the present invention.
• the process begins with a buyer searching business directory 335 for a seller offering a desired product or service (step 405).
• the buyer uses a conventional web browser executing on procurement server 312 to invoke search engine 330 and perform the search for a potential business partner.
• the buyer uses the seller's online interactive catalog to select the desired product or service, and places the selected product or service in an electronic shopping cart (step 410).
• the use, function, and implementation of an electronic shopping cart are well known in the art.
• the buyer uses a link from the seller's entry in business directory 335 to gain access to an online interactive catalog hosted on the seller's online/store catalog server 352.
• the buyer activates the "checkout" function for the items in the electronic shopping cart (step 415), as is well known in the art.
• the seller's system 350 transfers information describing the purchased product or service in the electronic shopping cart to the buyer's system 310 (step 420).
• the shopping cart information is transferred using the known HTTP protocol method POST. Specifically, when the buyer enters the seller's system 350, the location of the returning post (the buyer's system 310) is given to the seller. The seller's system 350 saves this location until the buyer is ready to checkout. At this point the seller's system 350 posts the shopping cart to the location it had saved.
• the buyer's system 310 Upon receiving the electronic shopping cart information, the buyer's system 310 generates an electronic purchase order and transmits it to the seller's system 350 (step 425).
• the buyer's back-end ERP system 314 generates the PO and transmits it, using business communications connector 316, to secure messaging engine 340, which in turn transmits it to the seller's business communications connector 356.
• the seller's system 350 Upon receiving the PO, the seller's system 350 generates a sales order, shipping documents and an electronic order confirmation (step 430). The seller's system 350 transmits the order confirmation to the buyer's system 310. In one embodiment of the present invention, the order confirmation is transmitted through network portal 370 on the same communications path used by the PO, but in the opposite direction. The seller's system 350 tracks the status of the sales order (step 435) to determine whether the ordered product shipped or whether the ordered service was completed. Referring now also to FIG. 4B, if the ordered product was shipped or the ordered service performed, seller's system 350 generates an invoice and transmits it to buyer's system 310 (steps 435 and 440). In one embodiment of the present invention, the invoice and all other electronic business documents exchanged between the buyer and seller are transmitted on a communications path that runs through network portal 370.
• the buyer's system 310 tracks the status of the product or service invoiced and if the product or service is accepted, the buyer's system 310 generates a payment authorization (steps 445 and 450). In one embodiment, buyer's system 310 generates a payment authorization by automatically causing a wire transfer of payment into the seller's bank account. If, however the product or service is not accepted, buyer's system 310 generates a rejection notice and transmits it to seller's system 350 (steps 445 and 455).
• buyer's system 310 generates a payment authorization by automatically causing a wire transfer of payment into the seller's bank account. If, however the product or service is not accepted, buyer's system 310 generates a rejection notice and transmits it to seller's system 350 (steps 445 and 455).
• the seller could adjust the catalog price based on rebates, based on a special contract price previously offered to the buyer and not available to the general public, or based on a volume discount.
• Another example is to add a step wherein the buyer and seller negotiate a price through email messages before the final buying decision is made.
• P. ERP-to-ERP Business Document Exchange The present invention allows ERP systems to directly communicate with each other, exchanging business documents through web portal 370 without human intervention. Using the present invention, once the decision is made to "do business," that is to buy something from, or sell something to, a business partner, the remainder of the transaction is handled automatically by the ERP systems.
• FIG. 5 is a block diagram illustrating the information path of a business document exchange in a system consistent with the principles of the present invention.
• a business document for example an electronic PO generated by a buyer's ERP system 314 is transmitted by a buyer's business communication connector 316 via network 320 to secure messaging engine 340.
• Buyer's business communication connector 316 transmits the business document in a format X 522, and secure messaging engine 340 receives the business document in format X 522.
• Format X may be any format used by buyer's ERP system 214.
• buyer's business communication connector 316 ultimately seeks to communicate with seller's business communication connector 356, to do so it need not know the network address of, or data format for, seller's business communication connector 356.
• Buyer's business communication connector 316 need only be able to communicate in its native format X 522 with secure messaging engine 340 and secure messaging engine 340 takes care of forwarding the message, translated to the proper format, to seller's business communication connector 356.
• a buyer can communicate with any number of sellers, and visa- versa, using a single interface provided by secure messaging engine 340.
• Buyers and sellers do not need to establish and maintain the details of each point-to-point connection in order to exchange electronic documents with all their business partners.
• Web portal 370 takes care of all the connection details. Buyers can purchase different products and services from different sellers using a single interface-the interface to web portal 370.
• secure messaging engine 340 Upon receiving an electronic business document from buyer's business communication connector 316, secure messaging engine 340 performs, among others, three basic functions; it reformats (if necessary) the business document to a format understood by seller's system 350, it retransmits the reformatted business document to seller's business communication connector 356, and it stores a copy of the electronic business document in message store 525.
• a mapping component 520 of secure messaging engine 340 performs these functions, which are explained in greater detail below. As shown in FIG. 5, mapping component 520 is communicatively connected to business directory 335, which contains information about the buyer and the seller who are exchanging electronic business documents.
• Mapping component 520 gets information it needs to create a communication link between the buyer's and seller's ERP systems from business directory 335, including information concerning data formats and routing information for connecting over a network. As shown in the example illustrated by FIG. 5, using the data format information from business directory 335, mapping component 520 translates the buyer's business document from format X 522 to format Z 524. Using the routing information, mapping component 520 transmits the translated data to seller's business communication connector 356 via network 320.
• Mapping component 520 is also communicatively connected to message store 525. Mapping component 520 stores a copy of every business document that passes through secure messaging engine 340 in message store 525. Thus, an audit trail of every business transaction is created and stored in message store 525. The audit trail provides proof, maintained by a third party who is neutral with respect to a business transaction, that a transaction occurred. Neither the buyer nor the seller can later repudiate an online commercial transaction by denying that it occurred.
• Figure 6 is a flowchart showing the steps to perform business document exchange in a manner consistent with the principles of the present invention.
• a system consistent with the principles of the present invention receives a business communication, which includes addressee (seller) information, from a buyer's system 310 in the buyer's system's data format.
• An electronic purchase order is an example of such a business communication.
• the system retrieves the addressee's data format information stored in business directory 335 (step 615). If the seller's data format is not the same as the buyer's data format (step 617), then the system translates the business communication from the buyer's format to the seller's format (step 620). Otherwise, no translation is needed and none takes place.
• the system retrieves the network routing address of seller's system 350 from the seller's information stored in business directory 335 (step 625). Then, the system transmits the translated business communication to the seller's routing address (step 630). The system also stores a copy of the business communication in message store 525, from which it can be retrieved later as necessary (step 635).
• systems consistent with the principles of the present invention define and enforce a business document exchange process or sequence, so that business partners' systems know what to expect and how to react during a business transaction.
• the system defines the business document exchange process as: buyer transmits a PO to seller, seller transmits an Order Acknowledgment in response, seller transmits an Invoice when the product is shipped, and buyer transmits a Payment Confirmation when the product is accepted, completing the transaction.
• web portal 370 provides visually-interactive electronic tools that help users implement automatic business document exchange.
• the system uses an Extensible Markup Language-formatted communications model for business document exchange.
• All Extensible Markup Language (XML) document definitions are preferably stored in open Internet-standard Lightweight Directory Access Protocol (LDAP) servers in a common information model repository.
• LDAP Lightweight Directory Access Protocol
• Users can use the repository's electronic business documents to establish communications and perform transactions with business partners. For example, a buyer can access the repository to find standard XML format document definitions for use in, for example, locating products, requesting quotes, and issuing purchase orders.
• a seller can use standard XML format repository definitions to, for example, upload catalog data, issue order confirmations, create sales orders, and create invoices.
• buyer's business communication connector 316 and seller's business communication connector 356 automatically translate ERP-system-generated electronic business documents directly into XML format before transmitting them to web portal 370.
• the present invention supports several current and emerging format standards for electronic business communication.
• the present invention can deliver and receive electronic documents using business formats such as EDI, XML, BizTalk, RosettaNet, and CXML.
• Systems, methods, and apparatus consistent with the principles of the present invention provide access to a business directory 335, which contains a list of potential business partners. Users use the directory to locate other businesses that offer desired products and services. Users must register their profiles in business directory 335. A user's profile contains information about the user and the user's products and/or services.
• Business directory 335 contains user information that includes, but is not limited to: business description and business category information; contact information such as email address, website address, and brick and mortar physical address; online catalog information such as product descriptions, service descriptions, prices, availability, and intelligent purchasing options; network routing information for electronic business document exchange; and application information for electronic business document exchange, such as vendor master data information, data format and other information for back-end ERP system integration, role information (manufacturer, distributor, etc), data mapping information for business document formats, and subscription service information.
• business directory 335 uses the Dun and Bradstreet Data Universal Numbering System (DUNS) ID number for keeping track of business information.
• DUNS Dun and Bradstreet Data Universal Numbering System
• business directory 335 also contains user system information such as: the name of the software package used to communicate with web portal 370, the communication software's release level, a list of business documents supported by the user's system, a list of the user's connectivity requirements , and the user's exception handling information.
• business directory 335 uses the Internet-standard Lightweight Directory Access Protocol (LDAP) to provide access to the directory service engine. Using this protocol, users can create, read, update, and delete information, and access the directory's event and replication services.
• LDAP Lightweight Directory Access Protocol
• search engine 330 Associated with the business directory is a search engine 330.
• Search engine 330 offers various search capabilities to help users find desired business partners.
• search engine 330 provides taxonomic indexing strategies using industry-standard classifications, browsing, keyword searches, geographic area searches, geographic radius searches, and full-text search functions.
• business directory 335 includes authentication information for each user's entry.
• the authentication information assures business partners that the entity they are doing business with is bona fide trading partner and not a hacker or other illicit entity.
• each organization listed in business directory 335 is investigated periodically, their authentication information is updated, and partners with whom they are doing business are notified of any changes in status.
• business directory 335 includes authorization information in each user's entry.
• the authorization information defines which persons within a user organization can use what services provided by the present invention. Users use authorization information to limit access to certain transactions so that only designated employees within a user company can perform them. For example, a company can designate that only the comptroller has authority to submit purchase orders over $10,000. After referencing this authorization information in business directory 335, the system will refuse to deliver to a seller any $10,000 or greater purchase order that was not initiated by the comptroller.

Landscapes

• Business, Economics & Management (AREA)
• Accounting & Taxation (AREA)
• Finance (AREA)
• Engineering & Computer Science (AREA)
• Technology Law (AREA)
• Economics (AREA)
• Marketing (AREA)
• Strategic Management (AREA)
• Development Economics (AREA)
• Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Storage Device Security (AREA)
• Computer And Data Communications (AREA)

Priority Applications (5)

Applications Claiming Priority (2)

Publications (2)

Family

ID=24460116

Family Applications (1)

Country Status (5)

Cited By (16)

Family Cites Families (6)

• 2001
  • 2001-07-06 IL IL15388001A patent/IL153880A0/xx unknown
  • 2001-07-06 AU AU7317601A patent/AU7317601A/xx active Pending
  • 2001-07-06 AU AU2001273176A patent/AU2001273176B2/en not_active Expired
  • 2001-07-06 JP JP2002509248A patent/JP5242878B2/ja not_active Expired - Lifetime
  • 2001-07-06 WO PCT/US2001/021228 patent/WO2002005508A2/en active IP Right Grant
  • 2001-07-06 CA CA002415571A patent/CA2415571A1/en not_active Abandoned

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events