JP2012203778A - Transaction management system, transaction management method, and transaction information relay program - Google Patents

Abstract

An object of the present invention is to realize data linkage with an internal system without modifying the external system, and to centralize a transaction information input / output screen on the external system side, thereby reducing a user's input burden.
A transaction management system includes an internal system having an internal database for managing transaction information, and a terminal. The terminal registers the transaction information in the external database of the external system, and the internal system acquires the transaction information registered in the external database from the external system and registers the acquired transaction information in the internal database. The registration process result is registered in the external database in association with the transaction information acquired from the external system, and the terminal displays the registration process result associated with the transaction information registered in the external database from the external system. get.
[Selection] Figure 1

Description

  The present invention relates to a transaction management system, a transaction management method, and a transaction information relay program, and in particular, a transaction management system, a transaction management method, and a transaction information relay that manage transaction information via an external system using an internal system and a terminal. Regarding the program.

  Generally, financial institutions independently develop and operate an information system for managing financial transactions (hereinafter referred to as “internal system”). For this reason, financial transactions conducted between financial institutions are managed by inputting transaction information to their own internal systems individually at each financial institution. In other words, data is usually not shared between financial institutions even in the same financial transaction. Therefore, Patent Document 1 focuses on a transaction system used by a global dealer-type financial institution, and a customer dealer-type financial institution refers to the transaction system to share information on mutual financial institutions, Techniques for conducting effective transactions are disclosed.

JP 2002-329074 A

  By the way, in recent years, introduction of information systems (hereinafter referred to as “external systems”) for centralized management of financial transactions performed between financial institutions has been promoted in each financial institution. On the other hand, a large amount of past transaction information is managed in the existing internal system, and it is necessary to maintain it in the future. For this reason, it is not realistic to replace all the operations that have been performed using the internal system with the external system. Therefore, when introducing an external system, it is desired to perform data linkage with an existing internal system and operate the internal system and the external system together. In addition, unification of input / output screens is also required. However, the internal system and the external system usually have their own management items.

  Here, the specification change of the external system cannot be performed by a financial institution alone. Therefore, it is conceivable to modify the input / output screen of the internal system. However, drastic modifications to internal systems that have been used for many years have a risk of function degradation, which requires a long development period and high development costs. In addition, even if a large-scale renovation of the internal system is performed, it is also meaningful to match the input / output interface with other financial institutions through the introduction of the external system. is there.

  That is, the user manages the financial transaction using both the external system and the input / output screen of the internal system. For this reason, there is a problem that the operation becomes complicated such that the user inputs overlapping contents on both screens, and the burden on the user is large.

  In Patent Document 1, since the dealer-dealer financial institution only refers to the transaction system of the global dealer-type financial institution without using its own internal system, the above-mentioned problems are solved. It is not possible.

  The present invention has been made to solve such problems, realizes data linkage with an internal system without modifying the external system, and unifies the input / output screen of transaction information on the external system side. An object of the present invention is to provide a transaction management system, a transaction management method, and a transaction information relay program for reducing the input burden on the user.

  The transaction management system concerning the 1st mode of the present invention is a transaction management system provided with an internal system which has an internal database which manages transaction information, and a terminal, and the above-mentioned terminal is in an external database which an external system has. The transaction information is registered for the internal system, the transaction information registered in the external database is acquired from the external system, and a registration process for registering the acquired transaction information in the internal database is executed. The result of registration processing is registered in the external database in association with the transaction information acquired from the external system, and the terminal displays the result of registration processing associated with the transaction information registered in the external database. It is acquired from.

  Moreover, it is desirable that the internal system registers the registration processing result in an accompanying information area provided in advance in the external database.

  Further, the internal system acquires the transaction information registered in the external database from the external system, performs conversion for registering the transaction information in the internal database, and performs the registration process on the converted transaction information. It is desirable to further include a relay server that executes.

  Moreover, when the relay server detects an error during conversion of the transaction information, it is desirable that error information indicating the error is registered in the external database in association with the transaction information as the registration processing result.

  Furthermore, when the relay server detects an error when storing the converted transaction information in the internal database, the relay server associates the error information indicating the error with the transaction information as the registration processing result, and Register in the database.

  The relay server may add a countermeasure according to the content of the detected error to the error information.

  In addition, the internal database manages the transaction information for each of a plurality of product information, and when the internal system executes the registration process for the acquired transaction information, the product to which the transaction information belongs in the internal database When it is determined that batch processing for the information is in progress and before the batch processing for the entire internal database, registration of the transaction information is suspended so that the transaction information is registered after the batch processing for the entire internal database. The fact that registration is performed after batch processing for the whole may be registered in the external database in association with the transaction information as the registration processing result.

  In addition, the transaction management system further includes a subsequent system that performs processing according to the notification from the internal system, and the internal system executes the registration processing for the transaction information and performs notification based on the transaction information. It is desirable to transmit to the subsequent system, include the processing result from the subsequent system in the registration processing result, and register it in the external database in association with the transaction information acquired from the external system.

  A transaction management method according to a second aspect of the present invention is a transaction management method for managing transaction information via an external system using an internal system and a terminal, wherein the terminal is an external device included in the external system. Registration for registering the transaction information in the database, the internal system acquiring the transaction information registered in the external database from the external system, and registering the acquired transaction information in the internal database of the internal system Registration, the result of the registration process is registered in the external database in association with the transaction information acquired from the external system, and the terminal is registered in association with the transaction information registered in the external database. A processing result is obtained from the external system.

  A transaction information relay program according to a third aspect of the present invention is a transaction information relay program for causing a computer to execute a process for relaying transaction information between an external system and an internal system, the external system having An acquisition process for acquiring transaction information registered from a terminal with respect to an external database from the external system, a conversion process for registering the acquired transaction information in an internal database of the internal system, and the converted transaction A first registration process for registering information in the internal database; a second registration process for registering the result of the first registration process in the external database in association with transaction information acquired from the external system; Is executed by the computer.

  According to the present invention, it is possible to realize data linkage with an internal system without modifying the external system, and to centralize a transaction information input / output screen on the external system side, thereby reducing the transaction burden on the user. A management system, a transaction management method, and a transaction information relay program can be provided.

It is a block diagram which shows the whole structure of the transaction management system concerning Embodiment 1 of this invention. It is a sequence diagram which shows the flow of the transaction information registration process concerning Embodiment 1 of this invention. It is a flowchart which shows the flow of the relay registration process concerning Embodiment 1 of this invention. It is a flowchart which shows the flow of the registration availability determination processing concerning Embodiment 1 of this invention. It is a figure which shows the example of the registration screen and registration content of the transaction information in the external system concerning Embodiment 1 of this invention. It is a figure which shows the example of the registration content of the transaction information in the internal system concerning Embodiment 1 of this invention. It is a figure which shows the example of the registration process result in the external system concerning Embodiment 1 of this invention. It is a block diagram which shows the whole structure of the transaction management system concerning Embodiment 2 of this invention. It is a sequence diagram which shows the flow of the transaction information registration process concerning Embodiment 2 of this invention.

  Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings. In the drawings, the same elements are denoted by the same reference numerals, and redundant description will be omitted as necessary for the sake of clarity.

<Embodiment 1 of the Invention>
FIG. 1 is a block diagram showing an overall configuration of a transaction management system 100 according to the first embodiment of the present invention. The transaction management system 100 is an information system that manages transaction information using the internal system 3 and the terminal 1 via the external system 2. The internal system 3 is an information system that manages financial transactions in a specific financial institution. The terminal 1 is a computer device operated by a user belonging to a financial institution that owns the internal system 3.

  The external system 2 is an information system for performing centralized management of financial transactions performed between financial institutions. The external system 2 has an external DB (DataBase) 20 that manages transaction information. The external DB 20 stores at least transaction information 21. Here, the transaction information 21 is information for managing financial transactions concluded between a plurality of financial institutions. The transaction information 21 includes, for example, information such as identification information in the external DB 20 of the financial transaction, a type of financial product, a transaction source, a business partner, an amount, an interest rate, a currency, and various contract conditions. Note that identification information such as a login ID used for access authentication to the external system 2 can be used for the transaction source. Further, it is assumed that the external DB 20 is provided with an accompanying information area 22 in advance. The accompanying information area 22 is an area for storing at least identification information of the transaction information 21 and text data of a predetermined size in association with each other. As the accompanying information area 22, for example, a description column of character information such as a comment column is applicable. That is, the accompanying information area 22 is a default data storage area of the external system 2. For this reason, the external system 2 can register arbitrary data of a predetermined size without changing the specification of the external DB 20.

  The external system 2 operates a server program for controlling processing to the external DB 20, and responds by access from a corresponding client application. For this reason, the external system 2 accepts various processing requests from the above-mentioned client application operating on an information system (not shown) or a terminal device (not shown) of a plurality of financial institutions via a network (not shown), and performs transactions. Information 21 is registered, updated, and deleted. When the various processing requests are data registration requests for the accompanying information area 22, the external system 2 stores the data designated by the registration request in the accompanying information area 22. Further, the external system 2 accepts various data acquisition requests from the client application, reads the transaction information 21 stored in the external DB 20 and the data registered in the accompanying information area 22, and returns the data to the request source. The external system 2 is operated by an organization other than the specific financial institution that owns the internal system 3 and the terminal 1. Further, various known information systems can be applied to the external system 2 as long as they have the above-described features. Therefore, detailed description of other functions and configurations is omitted.

  The terminal 1 is a computer device connected to the external system 2 via a network. Two or more terminals 1 may be used. The terminal 1 registers the transaction information 21 with the external DB 20. The terminal 1 includes at least an input unit 11, a display unit 12, and a control unit 13. The input unit 11 is an input device such as a keyboard or a mouse. The display unit 12 is a display device such as a screen. The control unit 13 is a control device such as a CPU (Central Processing Unit). In addition, the terminal 1 includes a memory such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a hard disk, and a communication unit for transmitting and receiving data to and from the external system 2 via a network. . The hard disk stores an OS (Operating System) and the client application for accessing the external system 2. The client application is a computer program for executing processing for registering transaction information 21 with the external system 2 and processing for acquiring information in the accompanying information region 22 corresponding to the registered transaction information 21. The OS is a well-known computer program and will not be described.

  The control unit 13 controls various processes in the terminal 1, access to the memory, the communication unit, the hard disk, and the like. In the terminal 1, the control unit 13 reads and executes the OS and client application stored in the hard disk. Thereby, the terminal 1 receives the input of transaction information from the user via the input unit 11, and transmits the received transaction information to the external system 2 via the communication unit. Further, the terminal 1 receives an instruction to browse the contents of the accompanying information area 22 corresponding to the transaction information input by the user via the input unit 11 and transmits an acquisition request to the external system 2 via the communication unit. To do. When the terminal 1 accepts the content of the accompanying information area 22 from the external system 2, the terminal 1 displays it on the display unit 12. Therefore, if the progress information about the transaction information registered from the terminal 1 is stored in the accompanying information area 22, the terminal 1 can browse the progress information corresponding to the transaction information. In particular, if the process information other than the external system 2, for example, the registration process result of the transaction information 21 in the internal DB 323 is stored as the progress information, the terminal 1 is registered by the client application corresponding to the external system 2. The registration processing result associated with the requested transaction information can be acquired. Therefore, the user who operates the terminal 1 can confirm the registration processing result of the transaction information input by the user via the input / output screen of the external system 2 without directly accessing the internal system 3.

  The internal system 3 acquires the transaction information 21 registered in the external DB 20 from the external system 2. Then, the internal system 3 executes a registration process for registering the acquired transaction information 21 in the internal DB 323. Subsequently, the internal system 3 registers the registration process result, which is the result of the registration process, in the external DB 20 in association with the transaction information 21 acquired from the external system 2. At this time, the internal system 3 registers the registration processing result in the accompanying information area 22 in the external DB 20.

  The internal system 3 includes a relay server 31 and an internal server 32. The internal server 32 is a computer device that manages transaction information in a specific financial institution. The internal server 32 may be realized using a plurality of computer devices. The internal server 32 includes a WSS (Web Service Server) 321, a storage control unit 322, and an internal DB 323.

  The internal DB 323 is a database system having a storage area for managing transaction information. The internal DB 323 has an area for managing the transaction information 324 for at least each of the plurality of product information 325. The product information 325 is information related to the type of financial product in the financial transaction. The transaction information 324 includes, for example, information such as identification information in the internal DB 323 of the financial transaction, a type of financial product, a transaction source, a business partner, an amount, an interest rate, a currency, and various contract conditions. For the transaction source, identification information such as a user ID used for access authentication to the internal server 32 can be used. However, although the transaction information 21 and the transaction information 324 are common in concept, specific data items and code systems are different.

  The storage control unit 322 is a control device such as a CPU, for example. The storage controller 322 receives a transaction information storage request from the outside of the internal server 32 and controls a storage process for storing the transaction information in the internal DB 323 based on the storage request. Further, the storage control unit 322 receives the storage processing result corresponding to the storage processing from the internal DB 323 and returns it to the request source of the storage request. As the storage processing result, the transaction information includes storage processing in the internal DB 323, that is, success or failure such as addition or update of transaction information. The storage processing result is, for example, a return value from the internal DB 323 such as a message code or an error code. Further, when there is no response from the internal DB 323 for a predetermined time, the storage control unit 322 may make the storage processing result. However, the storage processing result is not limited to this. The storage control unit 322 may be able to accept a transaction information storage request from the terminal 1.

  The WSS 321 is a Web service server that receives a processing request based on a predetermined data format from the outside of the internal server 32 and performs processing on the internal DB 323 via the storage control unit 322 based on the processing request. Here, the predetermined data format is, for example, information defined in a Web Services Description Language (WSDL) file. In addition, since the technique regarding Web service is a well-known thing, detailed description is abbreviate | omitted.

  Moreover, the internal server 32 includes a communication unit for transmitting / receiving data to / from the terminal 1 and the relay server 31 via a network as a configuration (not shown), such as a RAM and a ROM, a hard disk, and a network. The hard disk stores an OS, a control program for accessing the internal DB 323, a Web service server program, and the like.

  The storage control unit 322 controls various processes in the internal server 32, access to the memory, the communication unit, the hard disk, and the like. In the internal server 32, the storage control unit 322 reads and executes the OS and control program stored in the hard disk. Thereby, the storage control part 322 implement | achieves the storage process mentioned above at least.

  The internal server 32 periodically performs batch update processing (hereinafter referred to as “batch processing”) on the data in the internal DB 323. For example, it is assumed that the internal server 32 executes batch processing for each product information unit on a daily basis. Moreover, the internal server 32 shall perform the batch process with respect to the whole internal DB323, after the batch process about all the merchandise information is completed on a daily basis.

  As long as the internal server 32 has the above-described features, an information system that manages transaction information closed in an existing financial institution can be used. Therefore, detailed description of other functions and configurations is omitted.

  The relay server 31 relays transaction information between the external system 2 and the internal server 32. Specifically, the relay server 31 acquires the transaction information 21 registered in the external DB 20 from the external system 2, performs a conversion process that is a conversion for registering the transaction information 21 in the internal DB 323, and after the conversion It is a computer apparatus which performs the registration process for registering in the internal DB323 about transaction information. Further, the relay server 31 registers the registration processing result from the internal DB 323 in the external DB 20.

  Here, the relay server 31 performs mapping from the data item of the transaction information 21 in the external DB 20 to the data item such as the transaction information 324 in the internal DB 323 as the conversion process. For example, attribute values corresponding to attributes existing only in the internal DB 323 cannot be registered in the external DB 20. Therefore, the relay server 31 generates the attribute value by complementing the predetermined value as the attribute value or performing predetermined processing on the value in the transaction information 21 by the conversion process. Further, attribute values corresponding to attributes existing only in the external DB 20 cannot be registered in the internal DB 323. Therefore, the relay server 31 deletes the attribute value by the conversion process. That is, it is excluded from the converted transaction information. Furthermore, the relay server 31 combines the values of a plurality of items in the external DB 20 by conversion processing to generate one item value in the internal DB 323. Further, the relay server 31 divides one item value in the external DB 20 according to a predetermined standard by the conversion process, and sets the item value in the internal DB 323 as a plurality of item values.

  In addition, it is assumed that a list in which the login ID used for access authentication for the external system 2 and the user ID used for access authentication for the internal server 32 are registered in the relay server 31 in advance. Therefore, the relay server 31 converts the login ID included in the transaction information 21 into the associated user ID by referring to the list by the conversion process.

  Further, when the conversion process cannot be performed normally due to the transaction information 21 or the contents of the list, the relay server 31 detects an error in the conversion process. For example, even when values of a plurality of items are combined, values may not be registered in items that can be arbitrarily input in the external system 2. In that case, it is detected as an error in the conversion process. Further, when the login ID included in the transaction information 21 does not exist in the list, it is detected as an error.

  Here, when the relay server 31 detects an error during conversion of the transaction information 21, it is desirable to register the error information indicating the error in the external DB 20 in association with the transaction information 21 as a registration processing result. For example, when the transaction information 21 includes illegal data that cannot be stored in the internal DB 323, when registration processing in the internal DB 323 is executed, error information indicating registration failure is returned from the internal DB 323. However, since the specifications of the internal DB 323 are known in advance, when changing the data format of the transaction information 21, it is not necessary to execute registration processing in the internal DB 323 by detecting illegal data or the like. Therefore, the processing load of the internal DB 323 can be reduced.

  Further, when the relay server 31 detects an error when storing the converted transaction information in the internal DB 323, the error information indicating the error is registered in the external DB 20 in association with the transaction information 21 as a registration processing result. Good. Thereby, the terminal 1 can acquire error information regarding storage in the internal DB 323 from the external system 2 without directly accessing the internal DB 323. Therefore, the burden of investigating the cause of the error by the user who uses the terminal 1 can be reduced.

  Further, the relay server 31 may add a countermeasure according to the content of the detected error to the error information. Thereby, the user who uses the terminal 1 can take measures according to the error more quickly, and can make the registration work more efficient.

  Here, the relay server 31 includes an external system IF unit 311, a WSC (Web Service Client) 312, and a relay control unit 313. The external system IF unit 311 periodically transmits an acquisition request for the transaction information 21 to the external DB 20 and receives the transaction information 21 as a response. Further, the external system IF unit 311 transmits a registration processing result registration request to the external DB 20. The external system IF unit 311 can be realized using, for example, an API (Application Program Interface) provided from the external system 2. The API has a client application function corresponding to a server program running on the external system 2. Further, the transaction information that is the target of the acquisition request is data that has been successfully registered in the external DB 20 and has not been acquired by the relay server 31 or data that has been updated after the relay server 31 has been acquired previously.

  The WSC 312 is a Web service client that can communicate with the WSS 321 described above. That is, the WSC 312 transmits to the WSS 321 a processing request based on a predetermined data format including the converted transaction information.

  The relay control unit 313 is a control device that controls the relay of transaction information and registration processing results using the external system IF unit 311 and the WSC 312. The storage control unit 322 is a control device such as a CPU.

  Further, the relay server 31 includes a memory and a hard disk such as a RAM and a ROM, and a communication unit for transmitting and receiving data to and from the external system 2 via a network, as a configuration (not shown). The hard disk stores an OS, a transaction information relay program, a Web service client program, an API provided from the external system 2, and the like. Here, the transaction information relay program is a computer program that causes the relay server 31 to execute processing for relaying transaction information between the external system 2 and the internal system 3. And a transaction information relay program acquires the transaction information 21 registered from the terminal 1 with respect to the external DB 20 from the external system 2, a conversion process for registering the acquired transaction information 21 in the internal DB 323, The first registration process for registering the converted transaction information in the internal DB 323 and the registration process result that is the result of the first registration process are registered in the external DB 20 in association with the transaction information 21 acquired from the external system 2. The relay server 31 is caused to execute the second registration process.

  The relay control unit 313 controls various processes in the relay server 31, access to the memory, the communication unit, the hard disk, and the like. In the relay server 31, the relay control unit 313 reads and executes the OS and the transaction information relay program stored in the hard disk. Thereby, the relay control unit 313 realizes at least the acquisition process, the conversion process, the first registration process, and the second registration process described above.

  FIG. 2 is a sequence diagram showing a flow of transaction information registration processing according to the first exemplary embodiment of the present invention. First, the terminal 1 transmits a transaction information registration request to the external system 2 (S101). For example, first, the terminal 1 transmits a registration start request to the external system 2, and the external system 2 includes a registration screen including input fields for various items of transaction information and a registration button in response to the registration start request. Is returned to the requesting terminal 1. Then, the terminal 1 displays the received registration screen on the display unit 12, receives input from the user in each input field for transaction information, and includes each information in the input field in response to the user pressing the registration button. The registration request is transmitted to the external system 2.

  Next, the external system 2 registers the received transaction information in the external DB 20 (S102). For example, the external system 2 stores information corresponding to each input field included in the received registration request as transaction information 21 in the external DB 20.

  Here, the relay server 31 transmits an acquisition request for the transaction information 21 to the external system 2 (S103). For example, the relay server 31 may transmit the acquisition request periodically at a predetermined interval. As described above, the acquisition request corresponds to the function of the client application corresponding to the server program running on the external system 2. Therefore, the external system 2 reads the target transaction information 21 from the external DB 20 in response to the acquisition request, and transmits the read transaction information 21 to the relay server 31 (S104).

  Then, the relay server 31 performs conversion processing on the received transaction information 21 (S105). For example, the login ID of the external system 2 included in the relay server 31 and the transaction information 21 is converted into a user ID that can access the internal server 32. Further, the relay server 31 appropriately converts the information input in the sale transaction column 56, the purchase transaction column 57, and the condition column 58 shown in FIG. 5 into a format that can be stored in the internal DB 323. Here, it is assumed that no error is detected by the conversion process. Therefore, the relay server 31 performs registration permission / inhibition determination processing (S106). The registration availability determination process will be described later with reference to FIG. Here, it is assumed that registration is determined by the registration availability determination process.

  Subsequently, the relay server 31 transmits a conversion information storage request to the internal server 32 (S107). Specifically, the WSC 312 transmits the storage request to the WSS 321 based on a predetermined data format.

  Then, the internal server 32 performs an internal DB storage process (S108). That is, the internal server 32 executes a process for storing the transaction information included in the received storage request in the internal DB 323. Thereafter, the internal server 32 returns the storage processing result received from the internal DB 323 to the relay server 31 (S109). Specifically, the WSS 321 transmits the storage processing result to the WSC 312 based on a predetermined data format. Here, it is assumed that the storage process is successful and the storage process result includes that effect.

  Then, the relay server 31 transmits a registration request to the external system 2 using the received storage processing result as a registration processing result (S110). Specifically, the relay server 31 transmits a registration request for registering the registration processing result in the accompanying information area 22 in the external DB 20 in association with the transaction information 21.

  Thereafter, the external system 2 registers the received registration processing result in the external DB 20 (S111). Specifically, the external system 2 stores the registration processing result in association with the transaction information 21 in the accompanying information area 22 in the external DB 20.

  Then, after a predetermined time, the terminal 1 transmits an acquisition request for a registration processing result corresponding to the transaction information for which the registration request is made in step S101 (S112). Then, the external system 2 transmits a corresponding registration processing result to the terminal 1 in response to the acquisition request (S113).

  Thus, the terminal 1 can register the transaction information in both the external DB 20 and the internal DB 323 only by accessing the external system 2. In particular, the terminal 1 can acquire the registration processing result for the internal DB 323 without directly referring to the internal DB 323. Since the registration process result is stored in the accompanying information area 22 set in advance in the external DB 20, it is not necessary to change the specification to correspond to the internal DB 323 for the external DB 20. Therefore, it is possible to continue to use the existing internal server 32 and internal DB 323 without any modification while sharing financial transaction information with other financial institutions and sharing input / output screens.

  FIG. 3 is a flowchart showing a flow of relay registration processing according to the first exemplary embodiment of the present invention. The relay registration process includes the processes of steps S103 to S107, S109, and S110 in FIG.

  First, the relay server 31 transmits a transaction information acquisition request as in step S103 (S201). Next, the relay server 31 receives the transaction information as in step S104 (S202). And the relay server 31 converts transaction information similarly to step S105 (S203). Here, the relay server 31 determines whether or not an error is detected by the conversion (S204). When an error is detected, the relay server 31 transmits error information corresponding to the detected error to the external system 2 as a registration processing result (S210). Specifically, the relay server 31 transmits a registration request for registering in the accompanying information area 22 of the external DB 20 an error code or an error message indicating that the conversion has failed as error information. If no error is detected in step S204, the relay server 31 performs a registration process (S200). Here, the registration process corresponds to, for example, the following steps S205 to S207.

  First, the relay server 31 performs registration permission / inhibition determination processing in the same manner as in step S106 (S205). Here, FIG. 4 is a flowchart showing a flow of registration permission / inhibition determination processing according to the first exemplary embodiment of the present invention. First, the relay server 31 determines whether or not the current time is after the business start time and before starting the product closing batch processing of the corresponding product information (S301). It is assumed that the business start time in the financial institution operating the internal system 3 has been registered in the relay server 31 or the internal server 32 in advance. In addition, it is assumed that the batch processing for product closing of each product information managed by the internal DB 323 is started periodically or manually.

  If it is determined in step S301 that the current time is after the business start time and before starting the batch processing for the corresponding product information, the relay server 31 determines that the transaction information can be registered as a current day transaction. (S302). If it is determined in step S301 that the current time is after the business start time and before starting the batch processing for the corresponding product information, the relay server 31 adds the acquired transaction information, that is, the transaction information to be registered. It is determined whether or not the corresponding product information is being batch processed for product tightening (S303). Specifically, the relay server 31 uses the WSC 312 or the like to check whether or not batch processing is being performed on the product information corresponding to the transaction information to be registered based on information such as processes in the internal server 32. To do.

  If it is determined in step S303 that the corresponding product information is in the process of batch closing the product, the relay server 31 determines whether the entire system is in the process of closing (S304). Here, the whole system indicates a database system of the internal DB 323. Note that that the entire system is being tightened indicates that batch processing is being executed on the entire internal DB 323. When the entire system is in the closing process, it is determined that the batch process for each product information is also being executed.

  If it is determined in step S304 that the entire system is in the closing process, the relay server 31 determines that the transaction information cannot be registered (S305). If it is determined in step S304 that the entire system is not in the closing process, the relay server 31 determines that the transaction information can be registered as an after transaction (S306). Here, “after transaction” means that registration is requested within business hours, but registration is temporarily suspended and registered after the closing process of the entire system.

  If it is determined in step S303 that the corresponding product information is not in the closing process, in this case, since the entire system is not in the closing process, the relay server 31 determines that registration is possible as the next day transaction (S307).

  Returning to FIG. Subsequently, the relay server 31 determines whether the transaction information to be registered is registerable as a result of the registration permission determination process (S206). When it is determined that registration is possible, the relay server 31 transmits a storage information storage request after conversion to the internal server 32 as in step S107 (S207).

  Thereafter, the relay server 31 receives the storage processing result for the internal DB 323 from the internal server 32 as in step S109 (S208). Then, the relay server 31 determines whether an error is detected from the storage processing result (S209). When an error is detected, the relay server 31 transmits error information corresponding to the detected error to the external system 2 as a registration processing result (S210). Specifically, the relay server 31 transmits a registration request for registering in the accompanying information area 22 of the external DB 20 an error code or an error message indicating that registration has failed as error information. Here, the error code or the like from the internal DB 323 may be transferred as it is.

  If no error is detected in step S209, the relay server 31 transmits a registration success result to the external system 2 as a registration processing result, as in step S110 (S211). Specifically, the relay server 31 is used for registering a code or a message indicating that the registration has been successful as the current day transaction or that the registration has been suspended as the after transaction or the next day transaction in the accompanying information area 22 of the external DB 20. Send a registration request. Here, the return value of normal termination from the internal DB 323 may be transferred as it is.

  In the case of an after transaction, it can be paraphrased as follows. That is, when executing the registration process for the acquired transaction information 21, the internal system 3 determines that the internal DB 323 is in the process of batch processing for the product information to which the transaction information belongs and is before the batch process for the entire internal DB 323. The registration of transaction information is suspended so that the transaction information is registered after the batch processing for the whole, and the fact that the transaction information is registered after the batch processing for the whole is associated with the transaction information as a registration processing result and externally registered. Register in DB20. Thereby, when an error is not detected in the conversion process of transaction information, that is, when there is no problem in the transaction information itself, it is possible to reduce a case of an error due to a reason on the internal DB 323 side. Therefore, the number of times that the user re-registers is reduced, and the business can be made more efficient.

  If it is determined in step S206 that registration is not possible, the relay server 31 transmits a registration processing result to the external system 2 as a registration processing result (S212). Specifically, the relay server 31 transmits a registration request for registering a code or a message indicating that the storage process could not be performed in the accompanying information area 22 of the external DB 20.

  Note that the internal server 32 may execute the conversion process (S105) and the registration availability determination process (S106) executed by the relay server 31 according to the first embodiment of the present invention. In this case, the relay server 31 transfers the transaction information 21 acquired in step S104 to the internal server 32 as it is, instead of the storage request transmission process in step S107. Then, the internal server 32 performs the conversion process and the registration availability determination process on the transaction information 21 received from the relay server 31, and executes the storage process of the converted transaction information when registration is possible. The processing result is returned to the relay server 31. Thereby, the processing logic in the relay server 31 can be minimized, and the degree of dependence on the specifications of the internal DB 323 can be reduced. Therefore, when the specification of the internal DB 323 is changed, the influence on the relay server 31 can be reduced.

  FIG. 5 is a diagram showing an example of a transaction information registration screen and registered contents in the external system 2 according to the first embodiment of the present invention. The external system transaction information registration screen 5 shows the content displayed on the display part 12 of the terminal 1, for example. External system transaction information registration screen 5 includes login ID column 51, transaction ID column 52, supplier column 53, portfolio column 54, transaction holder column 55, sell transaction column 56, purchase transaction column 57, condition column 58 and internal transaction. An ID field 59 is provided as an example of an input display field for management items, and a registration button 50 for transmitting a registration request is provided. However, the management items and screen layout of the external system transaction information registration screen 5 are not limited to this. The login ID column 51 is a display column for a login ID used for access authentication to the external system 2. The login ID may be a transaction source of the financial transaction. The transaction ID column 52 is an input display column for identification information in the external DB 20 of the financial transaction. The transaction ID may be automatically issued by the external system 2. The supplier column 53 to the condition column 58 are input columns for various information related to the financial transaction. Therefore, the terminal 1 includes at least a customer, a portfolio, a transaction holder, a sale transaction, a purchase transaction, conditions, and the like in the registration request. Since the internal transaction ID field 59 is identification information in the internal DB 323, it may not be input at the time of registration in the external system 2. In addition, when the registration button 50 receives a pressing instruction from the terminal 1, the registration button 50 calls a process of including the contents input in the login ID field 51 to the internal transaction ID field 59 and transmitting them to the external system 2.

  FIG. 6 is a diagram showing an example of registered contents of transaction information in the internal system 3 according to the first exemplary embodiment of the present invention. Note that FIG. 6 is a diagram illustrating the concept of the registered content items, and is not limited to the arrangement position of each item.

  The registered contents of the transaction information in the internal system 3 include, for example, a user ID 611, a transaction number 612, a business partner 613, a portfolio 614, a transaction holder 615, sell transaction information 621, and purchase transaction information 622. The user ID 611 is a user ID converted from the login ID of the external system 2 in step S105. The transaction number 612 is identification information issued when transaction information is newly registered in the internal DB 323. The supplier 613, portfolio 614, and transaction holder 615 are input to the supplier column 53, portfolio column 54, and transaction holder column 55, respectively, and the information included in the transaction information 21 corresponds as it is.

  In addition, the sales transaction information 621 and the purchase transaction information 622 have respective item values corresponding to the amount item 631, the interest item 632, the period item 633, and the like. The item values of the sale transaction information 621 and the purchase transaction information 622 are values appropriately converted in step S105.

  FIG. 7 is a diagram illustrating an example of a registration process result in the external system 2 according to the first embodiment of the present invention. The external system transaction information management screen 7 shows the content displayed on the display part 12 of the terminal 1, for example. The external system transaction information management screen 7 includes a comment column 71 and a selected transaction information column 72 as examples of management item input display columns. The comment column 71 includes a transaction ID item 711 and a comment item 712. A transaction ID item 711 displays a list of transaction IDs, and a comment item 712 displays text data of a predetermined size. Here, as an example, a case where the images are displayed in time series from the top is shown. That is, the comment column 71 displays a list of comments about a plurality of transaction information.

  Here, in the first embodiment of the present invention, the registration processing result registered in association with the transaction ID by the registration request from the relay server 31 is displayed in the comment item 712. The first “ERR001” indicates that the registration process has an error for the transaction ID “BBB” because there is no user ID corresponding to the login ID. The second “INF001” indicates that the registration process to the internal DB 323 has been normally completed for the transaction ID “BBB”.

  In this case, for example, since it is not registered in the list in which the login ID and the user ID of the internal server 32 are associated with each other, an error is detected at the time of conversion, and “ERR001: USERID not defined” is displayed as the registration processing result. This corresponds to registration in the external DB 20. In this case, the user who operates the terminal 1 can take measures such as requesting the update of the list of correspondence between the login ID and the user ID in the relay server 31 by checking the comment field 71. Thereafter, the registration request to the internal DB 323 is normally completed by making a registration request again for the transaction ID “BBB” from the terminal 1. At this time, “INF001: Registered (Booking)” is registered in the external DB 20 as a registration processing result.

  Similarly, the third item “INF001” indicates that registration processing in the internal DB 323 has been normally completed for the transaction ID “BBC”. On the other hand, the fourth item “INF002” indicates that registration for the transaction ID “BBD” in the internal DB 323 is suspended as an after transaction.

  The selection area 713 indicates that the second item in the comment column 71 is selected on the external system transaction information management screen 7 by a user operation via the input unit 11 of the terminal 1.

  The selected transaction information column 72 displays the contents of the transaction information corresponding to the transaction ID in the selection area 713. The selected transaction information column 72 is equivalent to each input display column of the external system transaction information registration screen 5, but the internal transaction ID column 59 is issued by the internal DB 323 as a part of the registration processing result to the internal DB 323. Display transaction number. Thereby, the terminal 1 can acquire the association of transaction information between the external system 2 and the internal system 3 from the input / output screen of the external system 2.

  From the above, the first embodiment of the present invention realizes data linkage with the internal system without modifying the external system, and unifies the input / output screen of transaction information on the external system side, thereby The input burden can be reduced.

<Embodiment 2 of the Invention>
FIG. 8 is a block diagram showing the overall configuration of the transaction management system 200 according to the second exemplary embodiment of the present invention. The transaction management system 200 is an information system that manages transaction information via the external system 2 using the internal system 3a, the terminal 1, and the subsequent system 4. In addition, about the structure equivalent to FIG. 1, the same code | symbol is attached | subjected and description is abbreviate | omitted suitably.

  The rear system 4 is an information system connected to the rear stage of the internal system 3a. The latter system 4 performs processing according to the notification based on the transaction information 324 from the internal system 3a. As the latter stage system 4, for example, an information system that manages a credit limit for each customer who is a business partner in the transaction information 324 can be cited. In this case, the latest possible transaction amount and the like are managed for each customer in the latter-stage DB 40 included in the latter-stage system 4. Therefore, the latter stage system 4 determines whether or not the transaction exceeds the transaction possible amount of the corresponding customer based on the notification from the internal system 3a. Then, the post-stage system 4 returns a post-process result that is the determination result to the internal system 3a. The latter system 4 is not limited to an information system that manages a credit frame.

  The internal system 3a is different from the internal system 3 in that the internal server 32a includes a storage control unit 322a. The storage control unit 322a performs registration processing on the transaction information in the internal DB 323, and transmits a notification based on the transaction information to the subsequent system 4. Then, the storage control unit 322a includes the post-processing result from the post-system 4 in the registration processing result and registers it in the external DB 20 in association with the transaction information 21.

  FIG. 9 is a sequence diagram showing a flow of transaction information registration processing according to the second embodiment of the present invention. Note that illustration and description of processing equivalent to that in FIG. 2 is omitted. In FIG. 9, the process up to step S108 is the same as that in FIG.

  The internal server 32a notifies transaction information to the post-stage system 4 after the process of step S108 (S114). Then, the rear system 4 performs the rear process (S115). For example, the latter stage system 4 specifies the customer corresponding to the customer included in the transaction information. Then, the latter stage system 4 determines whether or not the customer can make a transaction in consideration of the current possible transaction amount of the customer and the amount and transaction conditions included in the transaction information. Then, the result of transaction availability is returned to the internal server 32a as a post-processing result (S116).

  The internal server 32a returns the storage process result in step S108 to the relay server 31 including the subsequent process result acquired from the subsequent system 4 (S109a). Since step S110 and subsequent steps are the same as those in FIG.

  As described above, the existing internal system 3a is often operated by being connected to the subsequent system 4 which is a plurality of other internal systems. Therefore, when data linkage with the external system 2 is performed, it is necessary to consider the consistency with the subsequent DB 40 included in the subsequent system 4. Here, it is conceivable to separately link data between the rear system 4 and the external system 2, but this is not practical because the system becomes complicated. Therefore, in the second embodiment of the present invention, the internal server 32a notifies the post-stage system 4 and registers the post-process result together with the storage process result in the external DB 20 as a registration process result. Thereby, maintenance efficiency can be improved by maintaining the consistency of data with a plurality of existing information systems and unifying the contact point with the external system 2 in the relay server 31 in the internal system 3a.

<Other embodiments of the invention>
The external system 2 is used by a plurality of financial institutions, and is owned by an organization other than a specific financial institution. Therefore, it is difficult to change the specifications of the external system 2 due to circumstances on the internal system 3 side. In other words, since the specifications of the external system 2 are limited, it is difficult for the external system 2 to handle errors or the like due to the internal system 2. Therefore, the internal system 3 according to the first embodiment of the present invention registers the registration process result including the success or failure of the registration process in the internal DB 323 in the accompanying information area 22 in the external DB 20. For this reason, the terminal 1 can acquire the registration processing result in the internal DB 323 from the external system 2 without requiring modification or the like for receiving the registration processing result on the external system 2 side.

  Further, the internal system 3 according to the first embodiment of the present invention does not use the relay server 31 and the internal server 32 may directly communicate with the external system 2. In that case, it can be realized by providing the external system IF unit 311 in the internal server 32.

  However, the relay server 31 is effective in the following cases. This is a case where the API provided by the external system 2 has restrictions such as a platform. For example, if the API is compatible only with a specific OS, but the existing internal server 32 is operated by a different OS, it is necessary to provide the external system IF unit 311 in the internal server 32. There are difficulties. In this case, a relay server 31 that is operated by an OS corresponding to the API is added separately, and the external system 2 and the internal server 32 are relayed, so that both the external system 2 and the existing internal server 32 need to be modified. Instead, the effects of the first embodiment of the present invention can be achieved.

  1 may be an area for storing data disclosed only to a specific user (hereinafter referred to as “disclosure restriction data”). For example, it is assumed that the transaction information 21 is a financial transaction concluded between the financial institutions A and B, and the user who registers the transaction information 21 belongs to the financial institution A. At this time, the user belonging to the financial institution A inputs disclosure restriction data for restricting disclosure to other than the financial institution A as part of the transaction information 21 at the time of registration of the transaction information 21 via the terminal 1 or after registration. . Then, the external system 2 registers the disclosure restriction data in the accompanying information area 22 corresponding to the transaction information 21. And when the acquisition request of the transaction information 21 is received from the internal system 3 owned by the financial institution A, the disclosure restriction data is returned together with the transaction information 21. Alternatively, when the registration processing result of the transaction information 21 is received from the internal system 3, it is registered in the accompanying information area 22 corresponding to the transaction information 21. On the other hand, when receiving an acquisition request for transaction information 21 from a user belonging to financial institution B or an internal system owned by financial institution B, external system 2 returns transaction information 21 excluding disclosure restriction data to the request source. For example, the internal transaction ID field 59 in FIGS. 5 and 7 may correspond to the accompanying information area 22 in which the disclosure restriction data is registered.

  Further, the disclosure restriction data may include an instruction for starting a predetermined process in the internal system 3. At that time, as the disclosure restriction data, it is possible to use small data such as a flag. Examples of the predetermined process include a process of processing the transaction information 21 and a process of newly generating a related transaction based on the transaction information 21 and registering it as the transaction information 324 in the internal DB 323. An example of the related transaction is a transaction opposite to the transaction information 21. In this case, it is assumed that the internal server 32 can execute a process for generating a counter transaction from the transaction information 324 stored in the internal DB 323. That is, first, the terminal 1 registers an activation instruction for activating a predetermined process in the accompanying information area 22 corresponding to the transaction information 21 when or after the transaction information 21 is registered. Next, the relay server 31 acquires the activation instruction stored in the accompanying information area 22 from the external DB 20 and transfers it to the internal server 32. And the internal server 32 produces | generates the opposite transaction corresponding to the transaction information 21 based on a starting instruction | indication, and registers into internal DB323. At this time, the operation of the external system 2 is not affected by the content of the disclosure restriction data. Thereby, the user who operates the terminal 1 can register two or more transaction information in the internal DB 323 only by inputting data for one transaction and disclosure restriction data such as a flag. Further reduction can be achieved. Further, a user belonging to the financial institution can control predetermined processing in the internal system 3 via the input / output screen of the external system 2. Therefore, even if you want to execute processing specific to the internal system 3, you can perform business using the input / output screen of the external system 2, and centralize the input / output screen of transaction information on the external system side, The input burden can be reduced.

  Furthermore, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the gist of the present invention described above.

DESCRIPTION OF SYMBOLS 100 Transaction management system 200 Transaction management system 1 Terminal 11 Input part 12 Display part 13 Control part 2 External system 20 External DB
21 Transaction Information 22 Attached Information Area 3 Internal System 3a Internal System 31 Relay Server 311 External System IF Unit 312 WSC (Web Service Client)
313 Relay Control Unit 32 Internal Server 32a Internal Server 321 WSS (Web Service Server)
322 Storage control unit 322a Storage control unit 323 Internal DB
324 Transaction information 325 Product information 4 Subsequent system 40 Subsequent DB
5 External System Transaction Information Registration Screen 50 Registration Button 51 Login ID Field 52 Transaction ID Field 53 Customer Field 54 Portfolio Field 55 Transaction Holder Field 56 Sell Transaction Field 57 Purchase Discount Field 58 Condition Field 59 Internal Transaction ID Field 611 User ID
612 Transaction number 613 Business partner 614 Portfolio 615 Transaction holder 621 Sales transaction information 622 Purchase information 631 Amount item 632 Interest rate item 633 Period item 7 External system transaction information management screen 71 Comment column 711 Transaction ID item 712 Comment item 713 Selection area 72 Optional transaction information column

Claims (10)

An internal system having an internal database for managing transaction information;
A terminal,
A transaction management system comprising:
The terminal
Register the transaction information in an external database of an external system,
The internal system is
Obtaining transaction information registered in the external database from the external system;
Execute registration processing to register the acquired transaction information in the internal database,
The result of the registration process is registered in the external database in association with the transaction information acquired from the external system,
The terminal
A transaction management system, wherein a registration processing result associated with transaction information registered in the external database is acquired from the external system.   The transaction management system according to claim 1, wherein the internal system registers the registration processing result in an accompanying information area provided in advance in the external database.   The internal system acquires transaction information registered in the external database from the external system, performs conversion for registering the transaction information in the internal database, and executes the registration processing for the converted transaction information The transaction management system according to claim 1, further comprising a relay server that performs the processing.   The relay server registers error information indicating the error in the external database in association with the transaction information as the registration processing result when an error is detected during conversion of the transaction information. 3. The transaction management system according to 3.   When the relay server detects an error when storing the converted transaction information in the internal database, the relay server associates the error information indicating the error with the transaction information as the registration processing result to the external database. The transaction management system according to claim 3 or 4, wherein the transaction management system is registered.   The transaction management system according to claim 4, wherein the relay server adds a countermeasure according to the content of the detected error to the error information. The internal database manages the transaction information for each of a plurality of product information,
When the internal system executes the registration process for the acquired transaction information, the internal system is in a batch process for the product information to which the transaction information belongs and before the batch process for the entire internal database. If determined, the registration of the transaction information is suspended so that the transaction information is registered after the batch processing for the whole, and the transaction information is registered as a result of the registration processing that the transaction information is registered after the batch processing for the whole. The transaction management system according to any one of claims 1 to 6, wherein the transaction management system is additionally registered in the external database. The transaction management system includes:
It further comprises a subsequent system that performs processing according to the notification from the internal system,
The internal system is
While performing the registration process for the transaction information, sending a notification based on the transaction information to the subsequent system,
The processing result from the subsequent system is included in the registration processing result and registered in the external database in association with transaction information acquired from the external system. The transaction management system described. A transaction management method for managing transaction information via an external system using an internal system and a terminal,
The terminal is
Register the transaction information in an external database that the external system has,
The internal system is
Obtaining transaction information registered in the external database from the external system;
Execute the registration process to register the acquired transaction information in the internal database of the internal system,
The result of the registration process is registered in the external database in association with the transaction information acquired from the external system,
The terminal is
A transaction management method characterized in that a registration processing result associated with transaction information registered in the external database is acquired from the external system. A transaction information relay program that causes a computer to execute processing for relaying transaction information between an external system and an internal system,
An acquisition process for acquiring transaction information registered from a terminal with respect to an external database included in the external system;
A conversion process for registering the acquired transaction information in an internal database of the internal system;
A first registration process for registering the converted transaction information in the internal database;
A transaction information relay program that causes the computer to execute a second registration process for registering the result of the first registration process in the external database in association with the transaction information acquired from the external system. .

Images