Transaction Support System

Abstract

To automatize generation of transaction data in a transaction among a plurality of business operators and thereby reduce labor of transaction related people.SOLUTION: A transaction support system includes: a transaction information processing unit 1 for communicating with a plurality of business operator terminals via the Internet; a generation rule storage unit 4 storing correspondence relation between a data item of order data and a data item of delivery data in a transaction; and a transaction information storage unit 2 for storing the order data and the delivery data. The transaction information processing unit 1 automatically generates delivery data from order data occurring due to a transaction among the plurality of business operators on the basis of the correspondence relation stored in the generation rule storage unit 4, and stores it in the transaction information storage unit 2.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a transaction support system that supports transactions between multiple traders. [Background technology]

[0002] The applicant of the present application has disclosed Patent Document 1. Patent Document 1 discloses a system in which multiple parties involved in a series of transactions proceed with the transactions while sharing transaction data. However, With conventional systems, it was difficult to accurately consider product inventory status and supplier delivery periods, and to determine and present delivery dates. Between all parties involved in the transaction There was an issue that determining delivery dates took time and effort. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-196550 Summary of the Invention [Problem to be solved by the invention]

[0004] The present invention is applicable to transactions between multiple businesses. , take The objective is to reduce the workload of those involved. In particular, the purpose is to reduce the burden on those involved in determining and presenting delivery periods that take into account product inventory status and information on suppliers. [Means for solving the problem]

[0005] In order to solve this problem, the present invention has the following configuration: A transaction support system that notifies a terminal of a delivery period for a product in response to a product order, A transaction information processing unit of the transaction support system When the trader C who sells the product does not have the product in stock, a process of reading out the delivery period of the product registered in advance in the product list of the trader C, and also reading out the delivery period of the product registered in advance in the product list of the trader A who is the supplier of the product; A process of calculating a total delivery period based on the respective delivery periods of these suppliers C and A, and notifying the terminal of the total delivery period; A trading support system that executes the above. [Effects of the Invention]

[0006] According to the present invention, It is possible to calculate and notify the total delivery period based on the availability of the product and the delivery period of the supplier, so information regarding the delivery period can be properly grasped. This can reduce the workload of the parties involved in the transaction. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a configuration diagram showing an embodiment of the present invention. [Figure 2] The structure diagram of the product list shown in Figure 1. [Figure 3] Figure 1 shows the structure of traceability information. [Figure 4] Structural diagram of vendor database. [Figure 5] FIG. 1 is a scheme diagram showing an example of a transaction format. [Figure 6] A diagram of the trade connection system incorporated in the transaction support system of Figure 1. [Figure 7] 2 is a diagram illustrating the configuration of a data migration system incorporated in the transaction support system of FIG. 1. [Figure 8] Figure 1 shows the configuration of the data integration system incorporated into the trading support system. DETAILED DESCRIPTION OF THE INVENTION

[0008] <Transaction form> An embodiment of the present invention will be described below. Fig. 1 shows one form of commercial transaction between a plurality of traders and consumers, and a configuration diagram of a transaction support system that supports the transaction.

[0009] In Figure 1, a consumer (or downstream trader) who is a buyer places an order with a seller, Trader C, for a product handled by Trader C. If the ordered product is an item in Trader C's inventory, Trader C uses a shipping company, Trader D, to deliver the inventory item to the consumer (or downstream trader) who is a buyer.

[0010] Furthermore, when seller Trader C receives an order for a product that Trader A handles and that should be shipped directly from Trader A to the consumer (or downstream trader), Trader C places an order for the product with Trader A and instructs Trader A to ship the product directly to the consumer (or downstream trader). Trader A, following Trader C's instructions, delivers the ordered product to the buyer, the consumer (or downstream trader), using Trader B, a shipping company.

[0011] Furthermore, when Trader C purchases a product handled by Trader A, it places an order for that product with Trader A, the seller. Trader A then uses Trader B, a shipping company, to deliver the ordered product to Trader C, the buyer.

[0012] In this application, a seller is referred to as "upstream" relative to a buyer, and conversely, a buyer is referred to as "downstream" relative to a seller.

[0013] Here, the transaction format shown in Fig. 1 is merely an example. The transaction support system of this embodiment is not limited to the transaction format shown in Fig. 1 and can support various types of transactions between multiple traders.

[0014] <Configuration of the transaction support system> The transaction support system according to this embodiment supports transactions between multiple traders as described above. In this embodiment, the transaction support system includes a transaction information processing unit 1 that transmits and receives data to and from the terminals of each seller, buyer, and carrier via the Internet, and a transaction information database (transaction information DB2) that stores the transaction information handled by this transaction information processing unit 1.

[0015] The transaction information processing unit 1 includes a transaction data generation unit 3 that automatically generates other transaction data based on one transaction data. The transaction data generation unit 3, for example, automatically generates delivery data based on order data. It also automatically generates sales data from purchase data. Reference numeral 4 denotes a generation rule storage unit that stores the correspondence between data items in one transaction data and data items in other transaction data.

[0016] The transaction information processing unit 1 communicates with the terminals of the buyer, seller, and carrier using, for example, the WWW (World Wide Web) system on the Internet. For this purpose, the transaction information processing unit 1 is equipped with a web server, and each terminal of the seller, buyer, and carrier is equipped with a web client.

[0017] The transaction information DB 2 stores a list of products sold by each trader (product list 5) and traceability information 6 that records the distribution route of each product between traders. The transaction information processing unit 1 also accesses a trader database (not shown).

[0018] <Product list structure> An example of the product list 5 in this embodiment is shown in Figure 2. The product list 5 includes a product list for each vendor. Figure 2 shows the product list for vendor C. The product list for each vendor associates a product identifier with a supplier, selling price, product introduction information, shipping category, inventory, and delivery period.

[0019] "Product identifier" is an identifier used to distinguish each product from other products. "Supplier" is the identifier of the supplier of the product in question. "Selling price" is the price at which our company, the seller, sells the product to the buyer. "Product introduction information" is the file name of the file that describes the product introduction information. It may include a file path. "Shipping category" specifies which of our company's locations the product will be shipped from, or whether it will be shipped directly to the buyer from an upstream supplier. "Inventory" is the number of items in our inventory for the product in question. "Delivery period" is the normal delivery period for delivering the product from our company to the buyer. "Vendor identifier" is an identifier used to distinguish one vendor from another.

[0020] <Structure of traceability information> The structure of the traceability information 6 in this embodiment is shown in Figure 3. The traceability information 6 is composed of a product identifier and the identifiers of each dealer that handled the product linked in chronological order. The "product identifier" is data that distinguishes one product from other products. The "dealer identifier" is the aforementioned dealer identifier and has a certain data length. The overall data length of the traceability information 6 is extended by adding dealer identifier data to the product identifier data. For example, if the product identifier is "ABCD," the first dealer identifier is "abc," the second dealer identifier is "123," and the third dealer identifier is "def," the traceability information for an item whose product identifier is "ABCD" is represented by the single data "ABCDabc123def."

[0021] <Structure of vendor database> The structure of the vendor database (vendor DB) in this embodiment is shown in Figure 4. The vendor DB associates, for each vendor's base, a vendor identifier, a base identifier, an address, a name, contact information, a vendor profile, an authentication key, the vendor's product list, and the shipping company used by the vendor for deliveries. The "vendor identifier" is an identifier used to identify a vendor from other vendors. A vendor also includes shipping companies. The "base identifier" is an identifier used to identify a vendor's base from other bases. Bases include administrative bases such as head offices and branches, manufacturing bases such as factories, and logistics bases such as warehouses. The "address" is the address of the vendor's base. The "name" is the name of the vendor's base. This may include the department name, job title, and name of the person in charge. The "contact information" is the contact information for the vendor's base. The contact information includes an email address. The "vendor profile" is information used to introduce the vendor to other vendors. The "authentication key" is used in the connection system described below. "Product List" is identified by the identifier of the product list of the relevant supplier. "Carrier" is identified by the carrier identifier of the carrier.

[0022] <Automatic generation of transaction data> In FIG. 1, the transaction data generation unit 3 automatically generates various transaction data required in the transaction process in accordance with generation instructions from a terminal. For example, delivery data is automatically generated based on purchase order data entered by a buyer (or their agent). The transaction data generation unit 3 also automatically generates sales data based on input purchase data. In the field of EDI (Electronic Data Interchange), purchase order data and delivery data are generally known to be two sides of the same coin, with the values ​​of their data items being the same. Similarly, purchase data and sales data are also two sides of the same coin, with the values ​​of their data items being the same. Therefore, the transaction data generation unit 3 automatically generates delivery data by inserting the values ​​of each data item in the input purchase order data into the corresponding data item in the delivery data. Similarly, the transaction data generation unit 3 automatically generates sales data by inserting the values ​​of each data item in the input purchase data into the corresponding data item in the sales data. In this way, the transaction data generation unit 3 automatically generates one transaction data based on another transaction data whose data item values ​​correspond.

[0023] The correspondence between the data items of the one transaction data and the data items of the other transaction data is pre-registered in the generation rule storage unit 4. The transaction data generation unit 3 refers to the correspondence between the data items registered in the generation rule storage unit 4 and automatically generates the other transaction data from the one transaction data that is the flip side of the other transaction data. According to this embodiment, in transactions between multiple traders, the generation of transaction data can be automated, thereby reducing the workload of the parties involved in the transaction.

[0024] <Automatic generation of traceability information> The delivery data generated by the transaction data generation unit 3 includes information on the seller and buyer of a specific product. Based on the delivery data generated by the transaction data generation unit 3, the transaction information processing unit 1 generates traceability information 6 by chronologically linking the trader identifiers of the traders who are the seller and buyer of the product to the product individual identifier, and stores the information in the transaction information DB2. According to this embodiment, in transactions between multiple traders, the generation of traceability information can be automated, thereby reducing the workload of the parties involved in the transaction.

[0025] <Example of a transaction using this system> In Figure 5, a consumer obtains a product list of products handled by trader C and places an order with trader C for trader A1's products (products provided by trader A1) and trader A2's products (products provided by trader A2) included in the product list. The ordered products are brought to trader B1 (shipping center) by traders A1 and A2, packed together at the shipping center, and then shipped directly to the consumer by trader B2, a carrier. During this transaction process, the transaction support system stores in transaction information DB2 order data corresponding to the transaction between the consumer and trader C, order data corresponding to the transaction between trader C and trader A1, and order data corresponding to the transaction between trader C and trader A2.

[0026] The transaction data generation unit 3 generates delivery data corresponding to each order data based on the order data. The transaction information processing unit 1 stores the delivery data generated by the transaction data generation unit 3 in the transaction information DB2. The transaction information processing unit 1 also generates traceability information 6 based on each delivery data generated by the transaction data generation unit 3 and stores it in the transaction information DB2. In this transaction example, the consumer's terminal may be a tablet terminal, a mobile phone terminal, or the like.

[0027] <Connecting systems between businesses> Figure 6 shows the configuration of a connection system between traders using the transaction support system. This connection system makes it easy to start new trade-to-trade transactions. A trader (searcher) who wants to find a trading partner inputs a search query from the WUI (Web User Interface) on his / her terminal. The trader search engine 11 searches the trader DB 12 for traders that match the search query input from the WUI and displays the search results on the WUI. The searcher selects a trader with whom he / she wants to start trading from the search results displayed on the WUI and performs an operation to send a trade request to that trader (the person being searched). Upon receiving this operation, the WUI transmits the trader identifier of the searcher and the trader identifier of the person being searched to the connection processing unit 13.

[0028] The connection processing unit 13 receives the searcher's trader identifier from the searcher WUI, and reads out the trader profile of the trader corresponding to the trader identifier from the trader DB 12. Then, the connection processing unit 13 causes the WUI of the terminal corresponding to the trader identifier of the person being searched (searched person WUI) to display the trader profile of the searcher, and also displays a question asking whether or not to start a transaction with the searcher.

[0029] When the searched person responds to the question by performing an operation to start a transaction, the searched person's WUI sends this information to the connection processing unit 13. Upon receiving this information, the connection processing unit 13 associates the searcher's trader identifier with the searched person's trader identifier and stores them in the connection DB 14, and adds the product included in the product list 5 corresponding to the searched person's trader identifier to the product list 5 corresponding to the searcher's trader identifier. At this time, the connection processing unit 13 sets the searched person's trader identifier as the supplier of the product added to the product list 5. This allows the searcher to start a transaction for the product with the searched person as the supplier. While the above describes a case where the buyer is the searcher and the seller is the searched person, the opposite is also possible: the seller is the searcher and the buyer is the searched person. In this case, the product included in the product list 5 corresponding to the searcher's trader identifier is added to the product list 5 corresponding to the searched person's trader identifier, and the connection processing unit 13 sets the searcher's trader identifier as the supplier of the product added to the product list 5. This allows the searched person to start a transaction for the product with the searcher as the supplier.

[0030] Here, if the person being searched has registered an authentication key in the dealer DB 12, the connection processing unit 13 requests the searcher WUI to input the authentication key of the person being searched. The searcher WUI transmits the authentication key of the person being searched input by the searcher to the connection processing unit 13. If the input authentication key does not match the authentication key of the person being searched, the connection processing unit 13 rejects the transaction request from the searcher. The connection processing unit 13 proceeds with the above process only if the authentication keys match. The person being searched can distribute the authentication key to acquaintance dealers in advance by email, etc., and by using the authentication key, it is possible to accept transaction requests on this system only from limited parties such as acquaintances.

[0031] <System to support data migration to trading support system> FIG. 7 is a diagram illustrating the configuration of the data migration system. When a trader becomes a new user of the trading support system, the data migration system assists the trader in importing data with different specifications from their existing trading information system into the trading support system. The operator operates the WUI on the terminal to upload data from the existing trading information system to the server. The data conversion unit 21 receives the uploaded data and converts the data from the existing system to conform to the data specifications of the trading information DB2 according to conversion rules registered in the conversion rule storage unit 22. The conversion rule storage unit 22 contains conversion rules for each of multiple data specifications known as the data specifications of the existing system to the data specifications of the trading information DB2. The terminal operator operates the WUI in advance to notify the data conversion unit 21 of the type of data specifications of the existing system. The data conversion unit 21 then reads and uses the conversion rule corresponding to the type of data specification of the existing system notified by the WUI from the conversion rule storage unit 22. The trading information processing unit 1 stores the data converted by the data conversion unit 21 in the trading information DB2. This allows traders who wish to use the transaction support system to easily transfer data from their existing systems to the transaction support system.

[0032] Furthermore, when this system is operated bidirectionally in real time, the function of converting trade information input from a first existing trade information system into data usable by the trade support system of the present application and storing the converted data in the trade information DB2, and the function of converting trade information requested by a second existing trade information system into data usable by the requesting existing trade information system and providing the converted data, are constantly in operation. This enables the first trader and the second trader using the trade support system of the present application to exchange trade information while using their respective existing trade information systems.

[0033] <Data integration system using semantic technology> Conventionally, when companies A, B, and C, which manage transaction information using their own data specifications, integrate data, they perform separate data integrations, such as integrating data between company A's system and company B's system, integrating data between company B's system and company C's system, and integrating data between company C's system and company A's system, and even doing so, it is difficult to integrate data from all of company A's, company B's, and company C's systems into one. The embodiment described below makes it easy to integrate data from multiple companies' systems into one.

[0034] In Figure 8, data from existing comprehensive shopping mall sites A and B built on the Internet and data from a transaction information management system C operated independently by a business connected to the Internet are integrated into one data set by the transaction support system of the present application.

[0035] The transaction support system includes a data acquisition unit 41, a site-specific metadata setting unit 42, and a user interaction unit 43. The data acquisition unit 41 and the user interaction unit 43 are provided in the transaction information processing unit 1. The site-specific metadata setting unit 42 and the metadata candidates are stored in a storage device.

[0036] "Site-specific metadata settings" are pre-registered for each website the location of each piece of data managed by existing websites, including general shopping mall sites A and B, and the metadata to be added to each piece of data. These site-specific metadata settings are created manually after analyzing the website's data structure in advance. "Metadata candidates" are a list of selectable metadata candidates.

[0037] When data is imported from general shopping mall site A, the data import unit 41 refers to the site-specific metadata setting 42 of general shopping mall site A, adds metadata corresponding to the location of the data to the data imported from each data location of the same site A, and stores the data in the transaction information DB 2. The same applies to general shopping mall site B.

[0038] Furthermore, when importing data from the transaction information management system C, the user interaction unit 43 provides the WUI to the transaction information management system C. The user interaction unit 43 also reads out metadata candidates that can be displayed on the WUI from the storage device and displays them on the WUI of the system C. The user interaction unit 43 then instructs the user of the system C, via the WUI, to specify the location of each piece of data managed by the system C and select metadata to be added to each piece of data from the metadata candidates. Alternatively, the user interaction unit 43 instructs the user of the system C, via the WUI, to specify the location of each piece of data managed by the system C and enter the metadata to be added to each piece of data in an input field of the WUI. After the user of the system C has completed linking the location of each piece of data with the metadata, the data import unit 41 operates an import button displayed on the WUI. The data import unit 41 retrieves each piece of data stored in the system C and the metadata associated with that piece of data, adds the corresponding metadata to each piece of data, and stores the data in the transaction information DB2.

[0039] This allows for integrated management of data based on the meaning of the data, even if the data specifications of each company differ. The functions of this embodiment allow businesses operating existing transaction information management systems to easily migrate to the transaction support system of the present application. By becoming a user of the transaction support system of the present application, businesses can easily begin transactions with other users of the transaction support system of the present application. In other words, simply connecting an existing transaction information management system to the transaction support system of the present application allows users to connect with all other users of the transaction support system of the present application. Users who operate stores on multiple comprehensive shopping mall sites can easily manage their transactions by integrating the transaction information of each store into the transaction support system of the present application. Furthermore, when the transaction support system of the present application manages each company's data in an integrated manner, transaction information is used regardless of the size of the business. For example, when a search is performed for the price of a specific product, prices of products offered by large businesses and small businesses are presented equally in the search results, emphasizing the content of the product or service offered and preventing monopoly. This also eliminates the need for users searching for product transaction information to browse multiple websites. Furthermore, data integration no longer requires a large amount of manpower, as was previously the case. Furthermore, because the meaning of the data is understood through metadata, it is possible to compile cross-sectional statistics on data that has a common meaning across multiple businesses. This makes it possible to compile comprehensive statistics, such as which products are popular among all businesses participating in the transaction support system.

[0040] <Notification of delivery period to buyer> The transaction support system of this embodiment can display the delivery period of a product to a buyer. In FIG. 1, when a consumer orders a product from Trader C, if Trader C has the product in stock, the transaction information processing unit 1 reads the delivery period of the product from Trader C's product list and notifies the consumer's terminal. On the other hand, if Trader C is out of stock of the product, the transaction information processing unit 1 reads the delivery period of the product from Trader C's product list and also reads the delivery period of Trader A, the supplier of the product, from Trader C's product list. Based on both the delivery period of Trader C (the seller) and the delivery period of Trader A (the supplier), the transaction information processing unit 1 calculates the total delivery period and notifies the consumer's terminal. For example, the total delivery period is calculated by adding the delivery period of Trader A and the delivery period of Trader C. Furthermore, if the product is shipped directly from Trader A to the consumer, the transaction information processing unit 1 reads the delivery period of the product from Trader A's product list and notifies the consumer's terminal.

[0041] <Hardware configuration> In the above embodiment, the transaction information processing unit 1, transaction data generation unit 3, trader search engine 11, connection processing unit 13, and data conversion unit 21 are realized by a computer executing a program. The transaction information DB 2, trader DB 12, and connection DB 14 are constructed inside a storage device. The generation rule storage unit 4 and conversion rule storage unit 22 are provided in the storage area of ​​the storage device. Data handled by the computer is read from or stored in the storage device.

[0042] The scope of the present invention is not limited to the scope of the embodiments described above, but is the scope of the invention set forth in the claims. [Explanation of symbols]

[0043] 1. Transaction information processing section 2. Transaction Information DB 3. Transaction data generation unit 4 Production rule storage 5 Product List 6 Traceability Information 11. Vendor Search Engine 12 Vendor DB 13 Connection processing section 14 Connection DB 21 Data conversion section 22 Conversion rule memory 41 Data acquisition section 42 Site-specific metadata settings 43 User interaction section

Claims

1. A transaction support system that notifies a terminal of a delivery period for a product in response to a product order, A transaction information processing unit of the transaction support system When the trader C who sells the product does not have the product in stock, a process of reading out the delivery period of the product registered in advance in the product list of the trader C, and also reading out the delivery period of the product registered in advance in the product list of the trader A who is the supplier of the product; A process of calculating a total delivery period based on the respective delivery periods of these suppliers C and A, and notifying the terminal of the total delivery period; A trading support system that executes the above.

2. A transaction support method for a transaction support system that notifies a terminal of a delivery period for a product in response to a product order, comprising: A transaction information processing unit of the transaction support system When the trader C who sells the product does not have the product in stock, a process of reading out the delivery period of the product registered in advance in the product list of the trader C, and also reading out the delivery period of the product registered in advance in the product list of the trader A who is the supplier of the product; A process of calculating a total delivery period based on the respective delivery periods of these suppliers C and A, and notifying the terminal of the total delivery period; A transaction support method for carrying out the above.

3. A transaction support program for a transaction support system that notifies a terminal of a delivery period for a product in response to a product order, The transaction information processing unit of the transaction support system When the trader C who sells the product does not have the product in stock, a process of reading out the delivery period of the product registered in advance in the product list of the trader C, and also reading out the delivery period of the product registered in advance in the product list of the trader A who is the supplier of the product; A process of calculating a total delivery period based on the respective delivery periods of these suppliers C and A, and notifying the terminal of the total delivery period; A trading support program that executes the above.

Images