KR102592225B1 - Electronic purchasing system and method connected with erp - Google Patents

Abstract

The present invention includes a buyer system employing an ERP system including an ERP ERP (Enterprise Resource Planning) server and a plurality of connected client terminals, and a transaction service system that provides product transaction services between buyers and suppliers through a public communication network. , In an ERP-linked electronic purchasing system, in a transaction method in a transaction system, the process of registering items to be purchased in the buyer system or a relay server linked to the buyer system and managing and updating the product list, and the buyer system or relay server When purchase request information is received from the company, the process of registering an announcement about the purchase request information, and in response to the registered announcement, receiving bidding information through multiple supplier systems and transmitting information about the bidding results to the buyer system or relay server Process, when purchase decision information corresponding to the bidding result is received from the purchaser system or relay server, a process of confirming whether the bid is successful or unsuccessful from the purchase decision information, and the result of confirming whether the bid is successful or unsuccessful, if the bid is unsuccessful, the bid is processed. , and if the bid is successful, the successful bid process is performed and the contract conclusion operation is performed.

Description

ERP linked electronic purchasing system and method {ELECTRONIC PURCHASING SYSTEM AND METHOD CONNECTED WITH ERP}

The present invention relates to an electronic purchasing method, and particularly to an electronic purchasing system and method linked to an enterprise resource planning system.

The enterprise resource planning (ERP) system integrates the company's business systems across all corporate activities, such as accounting, human resources, purchasing, sales, production management, and logistics, and unifies data to enable planned operation and management of business resources. It is an information management system. In particular, in various business fields including manufacturing, ERP systems can be implemented by integrated application software consisting of multiple modules related to major processes such as production, purchasing, inventory, ordering, transactions with suppliers, and customer service provision, and a relational database. It can be implemented as an integrated client/server system based on . As technology related to the ERP system, domestic patent publication No. 10-2017-0014338 (name: “ERP system with modular structure”, publication date: February 8, 2017, applicant: LoginSoft), or domestically registered Examples include those disclosed in Patent Publication No. 10-1157876 (name: “Electronic device for electronic contract conclusion”, registration date: June 13, 2012, patent holder: Business on Communication).

In each company that adopts the ERP system, internal personnel can use the ERP system to perform purchasing tasks to purchase various items needed by the business. However, when purchasing various goods (for example, consumable goods) required by a company, the e-commerce site or Internet shopping mall that sells the goods and the ERP system are composed of independent systems and are not interrelated, so the company It was difficult to proceed with the automated process of purchasing goods for each person in charge of purchasing goods. For example, a company's product purchase manager had to access the e-commerce site or Internet shopping mall for each product, log in, and then purchase the necessary product. Moreover, it was difficult for the company's purchasing manager to check and manage in real time the various products in various categories that the company wanted to purchase, and it was also difficult to select the appropriate product in terms of cost and performance among a variety of similar products. .

Accordingly, the present invention seeks to provide an ERP-linked electronic purchasing system and method to enable each company to proceed with the purchase of goods through an automated process.

In addition, the present invention provides an ERP-linked electronic purchasing system and method that allows each company to easily check and manage various products in various categories and select and purchase appropriate products when purchasing products. We would like to provide

In order to achieve the above object, according to an embodiment of the present invention, the present invention is an ERP (Enterprise Resource Planning) linked electronic purchasing system, a transaction service that provides a product transaction service between a buyer and a supplier through a public communication network. system; A buyer system employing an ERP system including an ERP server and a plurality of client terminals connected to the ERP server; a relay server that connects with the ERP server of the buyer system and the transaction service system through the public communication network and relays operations related to product purchase; And it may include a plurality of provider systems connected to the transaction service system through the public communication network.

In the above, when there is a purchase request for a product selected from among the registered products from the client terminal, the ERP server transmits purchase request information for the purchase request to the transaction service system through the relay server, and When the transaction service system receives purchase request information from the relay server, it registers an announcement about the purchase request information, receives bidding information from the plurality of supplier systems, and sends information about bidding results to the relay server through the ERP. The ERP server sends the information about the purchase decision to the relay server when there is an input from the client terminal about the purchase decision including information about a successful bid or a failed bid corresponding to the bidding result. It is transmitted to the transaction service system through the transaction service system, and the transaction service system receives the purchase decision information transmitted from the relay server to confirm whether the bid is successful or not. If the bid is lost, the bid is processed, and if the bid is successful, the contract related information is received. Information can be generated and transmitted to the ERP server through the relay server.

In the above, the transaction service system pre-registers products subject to purchase in the relay server and manages and updates the product list, and the relay server performs a synchronization operation through the ERP server and agent to synchronize the information of the registered products. It is characterized by:

In the above, the transaction service system may encrypt the information of suppliers participating in the bidding until the purchase request announcement closes and decrypt it after the announcement closes.

In the above, when there is an input for delivery and inspection confirmation of the purchased product, the ERP server transmits information about delivery confirmation and inspection confirmation from the relay server to the transaction service system, and the transaction service system When delivery and inspection confirmation information is received, an invoice issuance processing operation is performed, and the issued invoice can be transmitted to the ERP server through the relay server.

According to another embodiment of the present invention, a buyer system employing an ERP system including an ERP ERP (Enterprise Resource Planning) server and a plurality of connected client terminals, and a product transaction service between the buyer and the supplier through a public communication network. In an ERP-linked electronic purchasing system including a transaction service system, a transaction method in the transaction system,

The process of registering items to be purchased in the buyer system or a relay server linked to the buyer system and managing and updating the item list, and when purchase request information is received from the buyer system or the relay server, an announcement of the purchase request information is made. A process of registering, in response to the registered announcement, receiving bidding information through a plurality of supplier systems and transmitting information about bidding results to the buyer system or the relay server, and transmitting the bid information from the buyer system or the relay server to the buyer system or the relay server. When purchase decision information corresponding to the bidding result is received, a process of confirming whether the bid is successful or unsuccessful from the purchase decision information is performed; if the bid is successful or not, processing is performed if the bid is successful, and if the bid is successful, The process of performing a contract conclusion operation can be performed by performing successful bid processing.

As described above, the ERP-linked electronic purchasing method of the present invention allows each company to proceed with the purchase of goods through an automated process, makes it easy to check and manage various goods in various categories, and selects appropriate goods. It can be easy to purchase.

1 is an overall block diagram of an ERP-linked electronic purchasing system according to an embodiment of the present invention.
Figure 2 is an overall operational flowchart of the ERP-linked electronic purchase method according to an embodiment of the present invention.
Figure 3 is an operation flow chart of a transaction service system that provides ERP-linked electronic purchasing according to an embodiment of the present invention.

Hereinafter, a preferred embodiment according to the present invention will be described in detail with reference to the attached drawings. In the following description, specific details such as specific components are provided, but this is provided to facilitate a more general understanding of the present invention, and these specific details may be subject to certain modifications or changes within the scope of the present invention. It will be self-evident to those with ordinary knowledge.

Figure 1 is an overall block diagram of an ERP-linked electronic purchasing system according to an embodiment of the present invention. Referring to FIG. 1, the electronic purchasing system according to an embodiment of the present invention basically includes a transaction service system 30 that provides product transaction services between buyers and sellers (suppliers) through a public communication network (e.g., the Internet). ; Buyer system employing ERP system (10); A relay server 20 that performs a relay operation with the transaction service system 30 through the ERP server 12 of the buyer system 10 and a public communication network; It is configured to include a plurality of supplier (seller) systems (40A, 40B) connected to the transaction service system (30) through a public communication network.

The public communication network is a common connection between the relay server 20, the transaction service system 30, and the supplier system 40 to perform data communication with each other, and is a wired/wireless Internet network and a mobile communication network that includes an Internet access function. It can be implemented as follows.

The buyer system 10 basically includes an ERP server 12 and a plurality of client terminals (i.e., buyer terminals) 14 (14a, 14b, 14c) connected to the ERP server. The ERP server 12 is a large-capacity computer system that includes a central processing unit, RAM, ROM, terminal interface, and ERP DB for data storage to provide ERP services. A traditional personal computer or workstation with a significant amount of memory and processing power can be implemented as a server computer. The client terminal 14 is a terminal operated by each person in charge of the company, and is connected to the ERP server 12 through the company's internal network, which can be implemented as a wired or wireless network, and is a PC or laptop computer or smart phone that provides ERP services. It could be a terminal. In addition, the client terminal 14 may be implemented to be connected to the ERP server 12 through wired or wireless Internet.

The relay server 20 is provided in consideration of the characteristics of the ERP server 12, which is usually used in a company's internal network. It connects the ERP server 12 and an external public communication network (e.g., the Internet) and relates to product purchases. Relay the action. The relay server 20 includes, for example, a web service unit for connection to the Internet and a relay DB that stores transaction information related to product purchases. In the example of FIG. 1, the relay server 20 is shown as being implemented separately outside the buyer system 10, but it can be implemented as included in the buyer system 10 in hardware within the relevant company.

The supplier system 40 is a system employed by a seller company that sells goods, and may be a PC, laptop computer, or smart terminal that can be connected to the transaction service system 30 through a public communication network. In addition, the supplier system 40, like the buyer system 12, may have a configuration that employs an ERP system.

The transaction service system 30 may include an API (Application Programming Interface) server to provide transaction services between buyers and sellers over the Internet, and a transaction DB to store transaction-related information, and is implemented as a large-capacity computer system. It can be.

Figure 2 is an overall operational flowchart of an ERP-linked electronic purchase method according to an embodiment of the present invention, and can be performed, for example, in the system shown in Figure 1. Looking at the electronic purchase operation according to an embodiment of the present invention with reference to FIG. 2, first, in step 200, the API server of the transaction service system 30 registers various items to be purchased in advance on the relay server 20 and Manage and update lists. Registering various products in the transaction service system 30 can be done by automatically registering them in the relay server 20 by receiving separate product registration request information transmitted from time to time from each supplier. Alternatively, the manager of the transaction service system 30 may register various product information provided online or offline from each supplier into the system by directly entering it into the system. Each product can be registered by dividing it into various preset categories. At this time, the operation of registering an item in the relay server 20 in the transaction service system 30 can be performed by requesting the transaction service system 30 from the relay server 20 periodically or whenever connected. In step 202, the relay server 20 performs a synchronization operation through the ERP server 12 and the agent to synchronize registered product information.

In step 204, the company's purchasing manager connects to the ERP server 12 through the buyer (client) terminal 14, checks the registered product information, selects the desired purchase item from the product list, and registers a purchase request. In step 206, the ERP server 12 transmits purchase request information to the relay server 20 through an internal agent. The contents of the purchase request information may include, for example, a product list, delivery conditions, contract conditions, and person in charge information. In step 208, the agent of the relay server 20 transmits purchase request information to the transaction service system 30.

In step 210, the transaction service system 30, which receives purchase request information from the relay server 20, automatically registers a purchase request information notice on the corresponding website. In steps 212 and 214, the purchase request announcement of the transaction service system 30 is confirmed by the plurality of supplier systems 40 and a bidding operation is performed. The bidding operation of the plurality of supplier systems 40 is performed by the administrator of the plurality of supplier systems 40 accessing the website of the transaction service system 30 and entering the quotation input items preset for each purchase request notice online. This can be done through tasks such as entering the estimate amount. For this purpose, the transaction system 30 prepares a separate quotation input window in advance.

When the quotation input is completed in the plurality of supplier system 40, it is considered that the supplier has made a bid, and when the announcement is closed, the transaction service system 30 sends the bid result information to the relay server 20 in step 216. ) and send it to At this time, the transaction service system 30 may automatically generate the quotation input for each supplier system 40 in a preset file format (for example, PDF) and transmit it to the relay server 20 in step 216. At this time, the transaction service system 30 can update the announcement result and attached file URL information on the website after the announcement closes, and upon request for bidding result information from the relay server 20, that is, a call from the agent of the relay server 20. The information can be transmitted by synchronizing the data with the relay server 20. In the above, the announcement deadline may be closed when, for example, the announcement deadline that may be included in the purchase request information elapses at the time of the relevant purchase request announcement.

Meanwhile, the transaction service system 30 may encrypt information (eg, company information, quotation information) of suppliers participating in the bidding until the purchase request notice closes, and then perform an operation of decrypting it after the close. In some cases, only the quote information may be encrypted. Basically, this is to ensure fair competition between suppliers participating in the bidding by keeping the bidding information of the suppliers participating in the bidding private. At this time, by encrypting the bidding information, suppliers participating in the bidding, including the manager of the transaction service system 30, cannot confirm the quote information until the announcement is closed. Through this method, a third party can obtain account information or be hacked. Even if there is an external attack by , the transparency of competition can be maximized by thoroughly protecting the quote information.

In step 218, the relay server 20 transmits the bidding result information to the ERP server 12, and the internal agent of the ERP server 12 updates the result data. In step 220, the purchasing person in charge connects to the ERP server 12 through the internal network using the client terminal 14, checks the bidding results, and decides whether to purchase. When the purchase decision is made, the purchase decision information is provided to the relay server 20 through the ERP server 12 in step 222, and is then provided from the relay server 20 to the transaction service system 30 in step 224. . The purchase decision information may be successful bid decision or rejected bid decision information. At this time, the successful bid decision may be made by each purchasing manager directly in the purchaser system 10, but the purchasing manager may submit the successful purchase bid approval through the ERP internal approval network and obtain approval of the approval from the approval authority. .

In addition, information on the reason for rejecting a bid may be additionally entered and transmitted as information on the reason for rejecting the bid. The ERP server 12 is prepared in advance with a number of items for reasons for a failed bid, and is configured to receive appropriate items from among the items selected by the purchasing manager through the client terminal 14, and the selected items are used as information on the reasons for a failed bid. can be provided. Alternatively, the ERP server 12 may be configured to directly receive information on the reason for a failed bid from a purchasing manager through the client terminal 14 and provide the input information as information on the reason for a failed bid.

Thereafter, the transaction service system 30 receives the purchase decision information transmitted from the relay server 20 in step 224 and confirms whether the bid is successful or not in step 226. In case of a failed bid, the bid is automatically processed. The action to process a failed bid can immediately change the status of the relevant notice from, for example, 'waiting for successful bid' to 'successful bid' status, and information on the reason for the failed bid can be additionally displayed in the relevant notice. Accordingly, the notice is closed without a contractor. If the confirmation result in step 226 indicates that the bid is successful, automatic successful bid processing is performed in step 230 to perform a contract conclusion operation. That is, the transaction service system 30 changes the status of the announcement to, for example, 'successful bid' upon confirmation of successful bid, and automatically creates a file for the contract documents (e.g., PDF format) to the relay server (20). ), and the relay server 20 transmits the contract information to the ERP server 12 in step 232. Accordingly, the contract is automatically attached from the ERP server 12.

Thereafter, in step 240, if the purchasing manager completes the delivery confirmation and inspection of the purchased product according to the above procedure and confirms the inspection through the client terminal 14 if there are no problems, the ERP server 12 in step 242 Transmits the inspection confirmation information to the relay server 12, and the relay server transmits the inspection confirmation information to the transaction service system 30 in step 244. The transaction service system 30, which has received the inspection confirmation information, performs automatic invoice issuance processing on the website in step 246. At this time, the invoice issuance process is configured so that the supplier confirms the inspection confirmation information on the transaction service system 30 and issues a pre-set menu button, for example, 'Invoice Issuance', on the transaction service system 30. It may be possible.

Then, in step 248, the transaction service system 30 generates an invoice and transaction statement file (e.g., PDF format) and transmits it to the relay server 20, and in step 249, the relay server 20 sends the bill to the ERP server ( Send the invoice and transaction statement file to 12). Thereafter, in step 250, each purchase manager checks the bill (and transaction statement) through the client terminal 14 and performs final payment processing. The transaction statement may be identical to the contents of the ‘product statement’ usually submitted at the delivery stage.

FIG. 3 is an operation flowchart of a transaction service system that provides ERP-linked electronic purchasing according to an embodiment of the present invention. For example, it may be an operation performed in the transaction service system 30 shown in FIG. 1. . Looking at the electronic purchasing operation in the transaction service system in Figure 3, first, in step 300, various items to be purchased are registered in advance in the external buyer system or a relay server linked to the external buyer system, and the item list is managed and updated. Item list management and update operations are performed constantly, and if purchase request information is received from the external buyer system or a relay server linked to the external buyer system during the operation in step 300, it is confirmed in step 302 and proceeds to step 304. The contents of the purchase request information may include, for example, a product list, delivery conditions, contract conditions, and person in charge information.

In step 304, a purchase request information notice is automatically registered on the relevant website. Afterwards, in step 306, bidding information transmitted from a plurality of supplier systems that have received the purchase request notice of the corresponding transaction service system is received. Thereafter, in step 306, the bidding information is transmitted to the external buyer system or a relay server linked to the external buyer system. At this time, the information of suppliers participating in the bidding (for example, company information, quotation information) can be encrypted until the purchase request notice is closed, and then decrypted after the deadline.

The external buyer system receives the bidding information, internally decides whether to purchase, and transmits the purchase decision information to the transaction service system. When purchase decision information is received from an external buyer system or a relay server linked to an external buyer system, the transaction service system confirms it in step 312 and proceeds to step 314. The purchase decision information may be information about a successful bid or a failed bid for a specific supplier.

In step 314, purchase decision information is checked to determine whether the bid is successful or rejected. In the case of a failed bid, the bid is automatically processed, and in case of a successful bid, automatic successful bid processing is performed in step 314 to perform a contract conclusion operation. In other words, upon confirmation of successful bid, the transaction service system automatically creates a file for the contract documents (for example, PDF format) and transmits it to the external buyer system or a relay server linked to the external buyer system.

In the external purchaser system, when the product decided to purchase is delivered, confirmation and inspection are completed, and if there are no problems, the inspection confirmation information is transmitted to the transaction service system. When the transaction service system receives inspection confirmation information from the external buyer system or a relay server linked to the external buyer system, it confirms it in step 322 and proceeds to step 324.

In step 324, the transaction service system performs automatic invoice issuance processing on the website. In step 326, the transaction service system 30 generates an invoice and transaction statement file (e.g., PDF format) and transmits it to the buyer system or a relay server linked to the buyer system.

As described above, the ERP-linked electronic purchasing system and its method according to an embodiment of the present invention can be implemented, and on the other hand, there may be various other embodiments or modifications in the present invention. Therefore, the scope of the present invention should not be determined by the described embodiments, but by the claims and their equivalence.

Claims (7)

In an ERP (Enterprise Resource Planning) linked electronic purchasing system,
A transaction service system that provides goods transaction services between buyers and suppliers through a public communication network;
A buyer system employing an ERP system that includes an ERP server that provides ERP services to the buyer company and a plurality of client terminals connected to the ERP server through the company's internal network;
a relay server that connects with the ERP server of the buyer system and the transaction service system through the public communication network and relays operations related to product purchase; and
It includes a plurality of provider systems connected to the transaction service system through the public communication network,
When there is a purchase request for a product selected from among the products registered from the client terminal, the ERP server transmits purchase request information for the purchase request to the transaction service system through the relay server,
When the transaction service system receives purchase request information from the relay server, it registers an announcement about the purchase request information, receives bidding information from the plurality of supplier systems, and sends information about bidding results to the relay server. Transmitted to ERP server,
When there is an input from the client terminal about a purchase decision including information about a successful bid or a failed bid corresponding to the bidding result, the ERP server sends information about the purchase decision to the transaction service system through the relay server. send to,
The transaction service system receives the purchase decision information transmitted from the relay server, confirms whether the bid is successful or not, processes the bid if the bid is lost, and if the bid is successful, generates contract-related information and transmits it through the relay server. Transmitted to the ERP server,
The transaction service system pre-registers products subject to purchase in the relay server, manages and updates the product list, and the relay server performs a synchronization operation through the ERP server and agent to synchronize information on registered products,
When there is an input for delivery and inspection confirmation of purchased goods, the ERP server transmits information about delivery confirmation and inspection confirmation from the relay server to the transaction service system,
The transaction service system performs an invoice issuance processing operation upon receiving the delivery and inspection confirmation information, and transmits the issued invoice to the ERP server through the relay server. delete The electronic purchasing system according to claim 1, wherein the transaction service system encrypts the information of suppliers participating in the bidding until the purchase request notice closes and decrypts it after the notice closes. delete A buyer system employing an ERP system including an ERP (Enterprise Resource Planning) server that provides EPR services to the buyer company and a plurality of client terminals connected to the ERP server through the company's internal network, and a buyer and supplier through a public communication network In an ERP-linked electronic purchasing system that includes a transaction service system that provides product transaction services between people, a transaction method in the transaction service system,
By registering items subject to purchase in the buyer system or a relay server linked to the buyer system and managing and updating the item list, the relay server performs a synchronization operation through the ERP server and agent to synchronize the information of the registered items. process,
When purchase request information is received from the buyer system or the relay server, registering a notice about the purchase request information;
In response to the registered announcement, receiving bidding information through a plurality of supplier systems and transmitting information about bidding results to the buyer system or the relay server;
When purchase decision information corresponding to the bidding result is received from the buyer system or the relay server, a process of confirming whether the bid is successful or unsuccessful based on the purchase decision information;
As a result of checking whether the bid is successful or not, if the bid is successful, processing the bid is canceled, and if the bid is successful, processing the successful bid, and performing a contract conclusion operation,
When delivery and inspection confirmation information for purchased goods is received from the buyer system or the relay server, performing an invoice issuance processing operation;
A transaction method comprising transmitting the issued invoice to the buyer system or the relay server. The transaction method according to claim 5, wherein when the purchase request information is announced, information on suppliers participating in the bidding is encrypted until the purchase request announcement is closed and decrypted after the announcement is closed. delete

Images