SYSTEMS AND METHODS FOR MANAGING TREASURY TRADE REQUESTS
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
BACKGROUND OF THE INVENTION
This invention relates generally to managing trade requests of a business entity involved in multi-national transactions and, more specifically, to tracking and reporting of various trade requests.
A treasury operation of a large corporation typically manages money for many different divisions within the corporation as well as for affiliates and other related entities. The treasury operation is also involved in coordinating and managing risks associated with currency fluctuations by hedging currencies. Hedging involves identification of risks and deciding how much to hedge and further deciding where and how to hedge.
Known document management methods and systems have several disadvantages since these methods and systems are largely paper-based and time consuming to complete. The problem is more acute in large organizations having multiple divisions, and especially organizations with globally distributed divisions where managing treasury functions such as hedging requires immediate attention, review, and approval at various levels across the globe. Some unintended consequences include institutionalization of meetings, reviews, approvals and re- approvals, and others, all of which require significant time and resources. Additionally, even the organizations which use web technology to streamline the process, are unable to manage this intra-organizational information rapidly and
efficiently because of their inability to organize and present the data in a meaningful way to different users having different needs.
Managing and tracking compliance with various accounting and tax standards is also a challenge when activities such as hedging is decentralized at the divisional level. Many times, there is no functional expertise available to manage and track the risk involved.
Therefore, it would be desirable to streamline the process and make electronically available the information for processing treasury trade requests. In addition, it would be desirable to implement systems and processes to minimize internal meetings, reduce corporate travel, streamline the treasury interaction, eliminate multiple functional reviews and improve management efficiency.
BRIEF SUMMARY OF THE INVENTION
The present invention facilitates efficient credit line monitoring which includes tracking borrowings as well as posting journal entries automatically for financial reporting.
In one embodiment, the present invention is a method for managing and tracking treasury trade requests on-line using a web-based system including a server system coupled to a centralized interactive database and at least one client system. The method involves receiving information from a client system regarding a trade request, storing the trade request information into a centralized database, updating the centralized database periodically to maintain the trade request information, and providing the up-to-date trade request information in response to an inquiry. The method further involves downloading a specific form out of several predefined forms when the user selects a specific type of trade request.
In another aspect, the present invention is a system for computer-based management and tracking of treasury trade requests. In an exemplary embodiment, the system includes at least one server system, a client system configured with a browser, a centralized database coupled to the server system to implement, manage
and monitor various types of trade requests, receive and store data from the user against these trade requests and facilitate consolidation and reporting of these trade requests to improve efficiency and reduce risks.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is a simplified block diagram of a Treasury Trade Request System (TTRS) for tracking and managing treasury trade requests;
Figure 2 is an expanded version block diagram of an exemplary embodiment of server architecture of TTRS;
Figure 3 shows a configuration of database within database server of server system shown in Figure 1 ;
Figure 4 is an exemplary embodiment of a user interface depicting a
Treasury Trade Request Menu to the user when the user logs onto the system;
Figure 5 is an exemplary embodiment of a user interface displaying header information and trade request information utilized;
Figure 6 is an exemplary embodiment of a user interface downloaded and displayed by server system when the user has selected "Order Transactions" shown in Figure 4 and selected "Go To Transaction" button shown in Figure 4;
Figure 7 is an exemplary embodiment of a user interface downloaded and displayed by server system when the user has selected "Settlement/Rollover Transactions" shown in Figure 4 and selected "Go To Transaction" button shown in Figμre 4;
Figure 8 is an exemplary embodiment of a user interface downloaded and displayed by server system when the user has selected "Spot/Forward Transactions" shown in Figure 4 and selected "Go To Transaction" button shown in Figure 4;
Figure 9 is an exemplary embodiment of a user interface downloaded and displayed by server system when the user has selected "Swap Transactions" shown in Figure 4 and selected "Go To Transaction" button shown in Figure 4;
Figure 10 is an exemplary embodiment of a Option Trade Request Form user interface;
Figure 11 is an exemplary embodiment of a user interface downloaded and displayed by server system when the user has selected hypertext link entitled "View Requests" under "Administrative Options" shown in Figure 4;
Figure 12 is an exemplary embodiment of a User Profile Administration user interface;
Figure 13 is an exemplary embodiment of a Help Content Management user interface;
Figure 14 is an exemplary embodiment of a Business Validity user interface;
Figure 15 is an exemplary embodiment of a Fund Validity user interface;
Figure 16 is an exemplary embodiment of a Saved Trade Requests user interface; and
Figure 17 is an algorithm of TTRS.
DETAILED DESCRIPTION OF THE INVENTION
The present invention, in one aspect, is a computer-based method for managing treasury trade requests.
Exemplary embodiments of systems and processes that facilitate integrated network-based electronic reporting and workflow process management related to treasury trade -requests are described below in detail. The systems and
processes facilitate, for example, electronic submission of information using a client system automated extraction of information and windows-based assessment reporting.
The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independent and separate from other components and processes described herein. Each component and process also can be used in combination with other components and processes.
The application resides on an IIS Server with a SQL Server 7.0 database. In an exemplary embodiment, the application is web-enabled and runs on a business entity's intranet. In yet another embodiment, the application is fully accessed by individuals having authorized access outside the firewall of the business entity through the Internet. The system manages security control based on predetermined criteria. For example, the system is set up with pre-determined threshold amounts, which a particular user may not exceed without authorization from the management. If the user exceeds the threshold criteria, system 10 sends a warning message to the user that the requested trade exceeds the pre-determined limit. In a third exemplary embodiment, the application is runs in a Windows NT environment. The application is flexible and designed to run in a various different environments without compromising any major functionality.
Figure 1 is a simplified block diagram of a Treasury Trade Request
System (TTRS) 10 for tracking and managing treasury trade requests. System 10 includes a server system 12 and a plurality of client systems 14 connected to server system 12. In one embodiment, client systems 14 are computers including a web browser, and server system 12 is accessible to client systems 14 via the Internet. Client systems 14 are interconnected to the Internet through many interfaces including a network, such as a local area network (LAN) or a wide area network (WAN), dial-in-connections, cable modems and special high-speed ISDN lines. In another embodiment, client systems 14 could be any device capable of interconnecting to the Internet including a web-based telephone or other web-based connectable equipment. A database server 16 is connected to a centralized database
20 containing information on different divisions of the business entity, as described below in greater detail, is stored on server system 12 and can be accessed by potential users at one of client systems 14 by logging onto server system 12 through one of client systems 14.
In one embodiment, server system 12 is coupled to computers 14 via a
WAN or LAN. A user may dial or directly log on to an intranet or the Internet to gain access. Each computer 14 includes an interface for communicating with server system 12. The interface allows a user to input data and to receive data relating to the request. A computer-based tool for credit line assessment, as described below in more detail, is stored in server system 12 and can be accessed by a user at server 12 or any one of computers 14.
Server system 12 is configured to receive a request relating to treasury trade through one of a pre-determined form. Server system 12 is further configured to report the status of the request and provide notification of the status of the request to the user. The interface allows the user or applicant to input data relating to the request and to receive feedback. In one embodiment, the user or applicant is a division, company, organization or an individual department.
Figure 2 is an expanded version block diagram of an exemplary embodiment of server architecture of a Treasury Trade Request System (TTRS) 22. Components in system 22 identical to components of system 10 (shown in Figure 1) are identified in Figure 2 using the same reference numerals as used in Figure 1. System 22 includes server system 12 and client system 14. Server system 12 includes database server 16 and further includes an application server 24, a web server 26, a fax. server 28, a directory server 30, and a mail server 32. A disk storage unit 34 is coupled to database server 16 and directory server 30. Servers 16, 24, 26, 28, 30, and
32 are coupled in a local area network (LAN) 36. In addition, a system administrator's workstation 38, a user or credit analyst's workstation 40, and a supervising officer's workstation 42 are coupled to LAN 36. Alternatively, workstations 38, 40, and 42 are coupled to LAN 36 via an Internet link or are connected through an intranet.
Each workstation, 38, 40, and 42 is a personal computer including a web browser. Although the functions performed at the workstations typically are illustrated as being performed at respective workstations 38, 40, and 42, such functions can be performed at one of many personal computers coupled to LAN 36. Work stations 38, 40, and 42 are illustrated as being associated with separate functions only to facilitate an understanding of the different types of functions that can be performed by individuals having access to LAN 36.
In another embodiment, server system 12 is configured to be communicatively coupled to various banks 44 and to third parties, e.g., internal or external auditors 46 via an ISP Internet connection 48. The communication in the exemplary embodiment is illustrated as being performed via the Internet, however, any other wide area network (WAN) 50 type communication can be utilized in other embodiments, i.e., the systems and processes are not limited to being practiced via the Internet. In addition, and rather than a WAN, a local area network could be used in place of the WAN.
In the exemplary embodiment, each outside bank or a business entity 44 has a workstation 54. One of the client systems includes a senior manager's workstation 56 located at a remote location or located overseas. Work stations 54 and 56 are personal computers including a web browser. Also, work stations 54 and 56 are configured to communicate with server system 12. Furthermore, fax server 28 communicates with outside banks 44 and any of the remotely located client systems including a client system 56 via a telephone link. Fax server 28 is configured to communicate with other client systems 38, 40, and 42 as well.
Figure 3 shows a configuration of database 20 within database server 16 of server system 12 shown in Figure 1. Database 20 is coupled to several separate components within server system 12, which perform specific tasks.
Server system 12 includes a collection component 64 for collecting information from users into centralized database 20, a tracking component 66 for tracking information, a displaying component 68 to display information, a receiving
component 70 to receive a specific query from client system 14, and an accessing component 72 to access centralized database 20. Receiving component 70 is programmed for receiving a specific query from one of a plurality of users. Server system 12 further includes a processing component 76 for searching and processing received queries against data storage device 34 containing a variety of information collected by collection component 64. An information fulfillment component 78, located in server system 12, downloads the requested information to the plurality of users in the order in which the requests were received by receiving component 70. Information fulfillment component 78 downloads the information after the information is retrieved from data storage device 34 by a retrieving component 80.
Retrieving component 80 retrieves, downloads and sends information to client system 14 based on a query received from client system 14 regarding various alternatives.
Retrieving component 80 further includes a display component 84 configured to download information to be displayed on a client system's graphical user interface and a printing component 88 configured to print information.
Retrieving component 80 generates various reports requested by the user through client system 14 in a pre-determined format. System 10 is flexible to provide various types of reports and is not constrained to particular options set forth in any particular embodiment.
TTRS 10 is a searchable database 20 built in SQL server, which is divided into several main sections that interconnect. The first section is a User Information Section (UIS) 90. UIS 90 contains basic information regarding the user and the division with which the user is associated. The second section is an Administrative Information Section (AIS) 94 containing all relevant information relating to administrative functions. It also contains information on user profiles, password, organizational information and other relevant information to manage the security of the system. A third section is a Transaction Information Section (TIS) 96 containing information relating to various transactions including Order Transactions, Settlement/Rollover Transactions, Spot/Forward Transactions, Swap Transactions, and Options Transactions. UIS 90, AIS 94, and TIS 96 are all integrated together to
provide comprehensive information. Updating information within one section also automatically updates the relevant information in other sections of the database to maintain integrity.
The architectures of system 10 as well as various components of system 10 are exemplary only. Other architectures are possible and can be utilized in connection with practicing the processes described below.
Figures 4 through 17 are exemplary embodiments of screen displays depicting the TTRS functionality. These various embodiments describe one specific way of practicing the invention, displaying data or printing reports. However, one skilled in the art will recognize that there are multiple possible combinations of organizing the data, displaying the data on the screen as well as printing the data in various reporting formats, which express the same essential material and process steps.
Figure 4 is an exemplary embodiment of a user interface 150 depicting a Treasury Trade Request Menu to the user when the user logs onto the system. The user is prompted to enter the user identification and password associated with the user identification upon login (not shown). TTRS 10 authenticates the user before allowing the access. The TTRS is a secured system. There is often specific security on a document-by-document basis. The site in the present embodiment is only utilized as an intranet but is fully capable to be utilized across various networks on the Internet. The password utilized by the TTRS may be case sensitive and requires that it be matched completely before the user is provided access to the system.
Through a plurality of fields displayed on user interface 150, the user selects an input type from one of an Excel Trade Request (Spot/Forward non- recurring) 154, a Recurring Trade Requests 160 and an Individual Trade Request Form 164. Excel Trade Request 154 allows the user to upload the entire Excel generated files of Spot/Forward non-recurring files to Treasury Trade Request System 10. Recurring Trade Requests 160 option allows the user to enter, for example, 6 monthly requests with repeating information, but different Hedge Maturity Dates and
amounts. The user enters one request, enters the number of copies and selects a generate button (not shown). TTRS 10 creates the specified number of requested copies. For each request, the Hedge Maturity Date and Trade Amount is changed by the user. After the user selects Individual Trade Request Form 164, system 10 downloads and displays individual trade request forms.
User interface 150 further offers an option to the user to select a specific transaction type form for making a particularized request. In an exemplary embodiment of the invention, the options include, Order Transaction(s) 170, Settlement/ RolloverTransaction(s) 174, Spot/Forward Transaction(s) 180, Swap Transaction(s) 184, and Options Transaction(s) 190. Once the user selects a specific transaction type form through a plurality of fields and selects a "Go To Transaction" button 194, server system 12 downloads and displays the specific form relating to that particular transaction for the user input.
In one exemplary embodiment, user interface 150 displays alternatives to a user through various hypertext links, including a hypertext link to Log Out 200, a hypertext link to Help Tutorial 202, a hypertext link to Retrieve Saved Trade Requests 204, and a hypertext link to Excel Setup 210. Under administrative functions, user interface 150 displays various Administrative Options 212 pertaining to the management of administrative functions, including an alternative to View Requests 220, Rejects Processing 222, User Profiles 224, Send Trade Requests 226, Create Reports 228, Add/Edit Help Content 230, and Validity Tables for Businesses 232 and for Funds 234. User interface 150, also known as a home page, is linked to database 20. Database 20 is often referred to as the trade request database or the interactive database. User interface 150 is the entry point for users trying to access trade request database 20 via the Web. The first step in accessing information is to. select an option listed on user interface 150 and exercise that selection by selecting that specific hypertext link or selecting "Go To Transaction" button 194. Log out 200 as well as returning to main menu (i.e. back to user interface 150) are options available to the user from all user interfaces. The computer code defining the TTRS functionality as described in Figure 4 is set forth in Appendix A.
Figure 5 is an exemplary embodiment of a user interface 250 displaying header information and trade request information utilized by all forms when downloaded by the system. A user's information is populated from the user table. Form Spot/Forward also has selection of the Instrument (Forward or Non- deliverable-Forward, Spot Contract). Header information 252 is entered once on the form. Header information 252 includes a Name 254, an Email address 256, a Phone number 260, a Fax number 264, a User's location (for example, London, Fairfield, or Singapore) 270, an identification of a Hedge Instrument 274 through a pull down menu denoting whether the hedge instrument is an Options form, a Swap form, a Settlement form, a Spot/Forward, (which is the same as Non-deliverable forward) form, or a Spot Contract form. Header information 252 may include information relating to Trading Business (not shown) and a name of the Business (not shown) to which the user is functionally assigned to for budgeting purpose. Through user interface 250, the user may also select a specific file 280 and edit the same by double clicking the same. The computer code defining the TTRS functionality as described in Figure 5 is set forth in Appendix B.
Figure 6 is an exemplary embodiment of a user interface 300 downloaded and displayed by server system 12 when the user has selected "Order Transaction(s)" 170 (shown in Figure 4) and selected "Go To Transaction" button 194 (shown in Figure 4). User interface 300 displays header information 252 (shown in
Figure 5) and further includes a plurality of pull down menus to be utilized when supplying information to system 10 (shown in Figure 1). User interface 300 is populated with the fields that directly relate to the user's profile, which has been retrieved by the system upon log in authentication. Pull down menus 308 are supplied for selecting a Date to Execute the transaction 310, a Buy/Sell 312, a Trade
Amount 314, a Trade Currency 316, an Against Currency 318, a Hedge Maturity Date 320 which may be between 2 business days from the date of entry up to 10 years, a Stop Loss Level 330, and a Take Profit Level 332. The user must enter at least one of a field out of Stop Loss Level 330 or Take Profit Level 332. Pull down menus 308 are also supplied for inputting a date until the transaction is valid 340, a name of the project 342, Transaction Exposure Type 344, a name of the Customer 346, a name of
the Supplier 348, and a Fund type 350. Inter-company transaction 354 is denoted by a drop down window with either a "Yes" or "No" response. The user is further requested to supply the information denoting whether Corporate Accounting Approval 360 is required or not. The user enters a Number of copies 364 required and selects a "Generate" button 370 to generate and submit a request electronically to the corporate treasury department. Each of the pull down menu field is defined to accept the data in a specified format. Also, the system administrator has an option to define certain fields to be mandatory fields, if necessary, based on business needs to obtain that specific information. These criteria are often referred to as business validation rules and may vary for each form. The user is offered on-line help as well as printed manuals, which guides the user through the business validation rules. The computer code defining the TTRS functionality as described in Figure 6 is set forth in Appendix C.
Figure 7 is an exemplary embodiment of a user interface 380 downloaded and displayed by server system 12 when the user has selected
"Settlement/Rollover Transactions" 174 (shown in Figure 4) and selected "Go To Transaction" button 194 (shown in Figure 4). User interface 380 displays header information 252 (shown in Figure 5) and further includes a plurality of pull down menus 390 to be utilized when supplying information to system 10 (shown in Figure 1). Pull down menus 390 are supplied for selecting a FXPress Contract Number 392, a Buy/Sell 394, a Trade Currency 396, an Against Currency 398, a Compensation Type 400, an Amount 402, a Notes 404, a Rollover Amount 408, a Rollover Date 410, and an Option Type 412. Intercompany transaction 420 is denoted by a drop down window with either a "Yes" or "No" response. The user is further requested to supply the information denoting whether or not Corporate Accounting Approval 424 is required. The user enters a number of copies 430 required and selects a "Generate" button 434 to generate and submit a request electronically to the corporate treasury department. Each of the pull down menu field is defined to accept the data in a specified format. Also, the system administrator has an option to define certain fields to be mandatory fields, if necessary, based on business needs to obtain that specific information. These criteria are often referred to as business validation rules and may
vary for each form. The user is offered on-line help as well as printed manuals, which guides the user through the business validation rules. The computer code defining the TTRS functionality as described in Figure 7 is set forth in Appendix D.
Figure 8 is an exemplary embodiment of a user interface 450 downloaded and displayed by server system 12 when the user has selected
"Spot/Forward Transaction(s)" 180 (shown in Figure 4) and selected "Go To Transaction" button 194 (shown in Figure 4). User interface 450 displays header information 252 (shown in Figure 5). Through various fields, the user is prompted to enter required data into the system efficiently and effectively. User interface 450 further includes a plurality of pull down menus 452 to be utilized when supplying information to system 10 (shown in Figure 1). Through user interface 450, the user is requested to supply a Date to Execute the transaction 460, a Buy/Sell 462, a Trade Amount 464, a Trade Currency 466, an Against Currency 468, and a Hedge Maturity Date 470 which may be between 2 business days from the date of entry up to 10 years. Pull down menus 452 or pre-determined empty fields are also supplied for inputting a name of the project 482, Transaction Exposure Type 484, a name of the Customer 486, a name of the Supplier 488, a Fund type 490, an Approver's name 492 and an Approver's Password 494, Payment Details 496, Beneficiary Bank's Name 510 and it's complete address 512, Intermediary Bank's Name 514, complete address 518, Intermediary Bank Swift Code 520, and Intermediary Bank Federal ABA
Number 522 and account number 524.
The user is prompted to supply information on additional Intermediary Bank 2 which may include all relevant information 530 about this bank including, but not limited to, a Swift Code, ABA Number and an Account Number. In one embodiment of the invention, system 10 does not process the information unless the user has supplied a Wire Number 540 for tracking purpose, a Beneficiary Supplier Name 542, and an address 544. Intercompany transaction 550 is denoted by a drop down window with either a "Yes" or "No" response. The user is further requested to supply the information denoting whether or not Corporate Accounting Approval 556 is required. The user enters a number of copies 560 required and selects a "Generate"
button 570 to generate and submit a request electronically to the corporate treasury department. The computer code defining the TTRS functionality as described in Figure 8 is set forth in Appendix E.
Figure 9 is an exemplary embodiment of a user interface 590 downloaded and displayed by server system 12 when the user has selected "Swap
Transaction(s)" 184 (shown in Figure 4) and selected "Go To Transaction" button 194 (shown in Figure 4). User interface 590 displays header information 252 (shown in Figure 5). Through various fields, the user is prompted to enter required data into the system efficiently and effectively. User interface 590 further includes a plurality of pull down menus 596 to be utilized when supplying information to system 10 (shown in Figure 1). Through user interface 590, the user is requested to supply a Date to Execute the transaction 600, a Buy/Sell 602, a Trade Amount 604, a Trade Currency 606, an Against Currency 608, and a Hedge Maturity Date 610 which may be between 2 business days from the date of entry up to 10 years. Pull down menus 596 or pre-determined empty fields are also supplied for inputting a name of a project
612, a Transaction Exposure Type 614, a name of the Customer 616, a name of the Supplier 618, and a Fund type 620.
The user is prompted to supply information on a Far Trade Amount 624 and a Far Hedge Maturity Date 630. Intercompany transaction 638 is denoted by a drop down window with either a'Υes" or "No" response. The user is further requested to supply the information denoting whether or- not Corporate Accounting Approval 646 is required. The user enters a number of copies 650 required and selects a "Generate" button 660 to generate and submit a request electronically to the corporate treasury department. The computer code defining the TTRS functionality as described in Figure 9 is set forth in Appendix F.
Figure 10 is an exemplary embodiment of a Option Trade Request
Form user interface 670 downloaded and displayed by server system 12 when the user has selected "Swap Transaction(s)" 184 (shown in Figure 4) and selected "Go To
Transaction" button 194 (shown in Figure 4). User interface 670 displays header information 252 (shown in Figure 5). Through various fields, the user is prompted to
enter required data into the system efficiently and effectively. User interface 670 further includes a plurality of pull down menus 676 to be utilized when supplying information to system 10 (shown in Figure 1). Through user interface 670, the user is requested to supply a Date to Execute the transaction 674, a Buy/Sell 676, a Trade Amount 680, a Trade Currency 682, an Against Currency 684, a Premium Currency
686, a Hedge Type 688, an Expiry Date 690, a Pricing Notes 692, and a Strike Price 694. Pull down menus 670 or pre-determined empty fields are also supplied for inputting a name of the project 700, a Transaction Exposure Type 704, a name of the Customer 706, a name of the Supplier 710, and a Fund type 716.
The user is prompted to supply information on Intercompany transaction 720, which requires either a "Yes" or "No" response through a drop down window. The user is further requested to supply the information denoting whether or not Corporate Accounting Approval 726 is required. The user enters a Number of copies 730 required and selects a "Generate" button 740 to generate and submit a request electronically to the corporate treasury department. The computer code defining the TTRS functionality as described in Figure 10 is set forth in Appendix G.
Figure 11 is an exemplary embodiment of a user interface 750 downloaded and displayed by server system 12 when the user has selected a hypertext link entitled "View Requests" 220 under "Administrative Options" 212 (shown in Figure 4). User, interface 750 displays a summary of all view requests including a
Name of the person making a request 754, a Date on which the request was made 756, a brief summary of the Transaction 758, a type of the Hedge Instrument 760, and a Request Number 762. View Requests user interface 750 allows the user to delete a specific record 770, clear records 776, or view history 780. The user may log out 784 or return to main menu 790 from this user interface. Log out 784 as well as return to main menu 790 are options available to the user from all user interfaces. The computer code defining the TTRS functionality as described in Figure 11 is set forth in Appendix H.
Figure 12 is an exemplary embodiment of a User Profile Administration user interface 800 downloaded and displayed by server system 12
when the user has selected a hypertext link entitled "User Profiles" 224 under "Administrative Options" 212 (shown in Figure 4). User Profile Administration user interface 800 displays a summary of all user profiles including a Login Identification Number 810, a name of the person authorized access 814, a Phone Number 816, a Fax Number 818, and an E-mail Address 820. User Profile Administration user interface
800 allows the user to delete a specific record 826, Edit records 830, or Add a New User 834. The user may Log Out 840 or Return to Main Menu 844 from user interface 800. The computer code defining the TTRS functionality as described in Figure 12 is set forth in Appendix I.
Figure 13 is an exemplary embodiment of a Help Content Management user interface 850. Help Content Management user interface 850 displays a template the user may utilize to submit issues to the administrative management. Through Help Content Management user interface 850, the user may input information regarding a specific transaction 862, Search a Database for fields to Edit or Delete 866, Add a Transaction Name 870, or Edit/Delete a Transaction Name 876. The user may log out 880 or return to main menu 884 from user interface 850. The computer code defining the TTRS functionality as described in Figure 13 is set forth in Appendix J.
Figure 14 is an exemplary embodiment of a Business Validity user interface 890 downloaded and displayed by server system 12 when the user has selected hypertext link entitled "Validity Tables - Businesses" 232 under "Administrative Options" 212 (shown in Figure 4). Business Validity user interface 890 displays a list of Business Names 894 that the system will recognize and for which the user has a capability to Edit 896 or Delete 898 a specific business name and all associated records. The computer code defining the TTRS functionality as described in Figure 14 is set forth in Appendix K.
Figure 15 is an exemplary embodiment of a Fund Validity user interface 910 downloaded and displayed by server system 12 when the user has selected hypertext link entitled "Validity Tables - Funds" 234 under "Administrative Options" 212 (shown in Figure 4). Fund Validity user interface 910 displays a list of
Fund Names 916 that the system will recognize and for which the user has a capability to Delete 918 or Edit 920 a specific fund name and all associated records. The user may add a new fund by selecting "Add a New Fund" button 924 and following specific instructions displayed (not shown) on user interface. The computer code defining the TTRS functionality as described in Figure 15 is set forth in
Appendix L.
Figure 16 is an exemplary embodiment of a Saved Trade Requests user interface 940. Saved Trade Requests user interface 940 displays all saved trade requests in a summarized table format which includes a Transaction Number 950, a Name 952 of the person associated with the transaction, a Date 954 the transaction was submitted, a Transaction Type 956, and whether the transaction is Recurring or a Non-recurring transaction 958. The user has an option to delete the transaction through a "Delete" hypertext link 960. The user may log out 970 or return to main menu 974 from user interface 940. The computer code defining the TTRS functionality as described in Figure 16 is set forth in Appendix M.
Figure 17 is an algorithm 1000 of TTRS 10. Under the web-based system 10 (shown in Figure 1), the user accesses 1010 home page of the web site through client system 14 (shown in Figure 1). Server system 12 (shown in Figure 1) downloads 1020 and displays 1030 several options. Once the user selects 1040 a specific option out of various hypertext links or selecting an option through a plurality of fields, the request is sent to server system 12. Transmitting the request 1060 is accomplished either by click of a mouse or by a voice command. Once server system 12 receives 1070 the request, server system 12 accesses 1080 the database server 16 and retrieves 1090 pertinent information from database 20 (shown in Figure 1). The requested information is downloaded 1092 and provided 1100 to client system 14 from server 12. Server system 12 provides 1100 the requested information to the user by either displaying 1110 the information on the user's display or by printing 1112 it on an attached or remote printer. The user continues to search database 20 for other information, updates 1130 database 20 with new or revised information or exits 1150 from system 10. In another embodiment of the invention, the retrieved 1090
information is downloaded as a "Form" to help the user to input/submit information 1154 in a specified format regarding a specific transaction. The inputted information 1154 is received 1156 by server system 12 for storing 1158 in database 20. The user also updates 1130 the database by adding, deleting or modifying the information regarding the transaction. In another embodiment, client system 14, as well as server system 12, are protected from access by unauthorized individuals. As described, TTRS 10 is an interactive searchable database 20 for all treasury transaction related information and provides flexibility to users as well executives to stay current with the treasury operations/hedging related information to date. The system provides the ability for managers, users, and database administrators to directly update, review and generate reports of current information.
While the invention has been described in terms of various specific embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the claims.
APPENDIX A
Execution Time
125 milliseconds
Parameters
URL Parameters :
CFTOKEN=56699449 CFID=973
CGI Variables :
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST= eb06. corporate . ge . com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT_ISSUER=
CONTENT_TYPE=application/x- ww-form-urlencoded
AUTH_PASS ORD=
HTTP_REFERER=http : // eb06. corporate . ge . com/tradedev/requestforms/index. cfm?CFID=973
SERVER_PROTOCOL=HTTP/1.1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT_LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB SERVER API=ISAPI
CF_TEMP ATE_PATH=d: \Inetpub\ww root\tradedev\requestforms\treasurymenu. cfm
REQUEST_METHOD=GET
PATH_INFO=/tradedev/requestforms/treasurymenu.cfm
HTTP_USER_AGENT=Mozilla/ .0 (compatible; MSIE 5.01; Windows 95)
REM0TE_H0ST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE=
SERVER_SOFTWARE=Microsoft-IIS/4.0
SERVER_NAME=web06. corporate . ge . com
QUERY_STRING=CFID=973&CFTOKEN=56699449
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/requestforms/treasurymenu. cfm
REMOTE_USER-
GATEWAY_INTERFACE=CGI/1.1
HTTP_CONTENT_TYPE=application/x-www-form-urlencoded
HTTP_COOKlE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POL =false;
CERT_KEYSIZE=
HTTP_CONNECTION=Keep-Alive
PATH_TRANSLATED=d;\Inetpub\wwwroot\tradedev\requestforms\treasurymenu.cfm
HTTPS_SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE=
APPENDIX B
Queries
BusiriesεQuery ( Records=135, Time=250ms )
SQL =
Select BusinessName, BusID from Business
WHERE Location =' Fairfield'
AND BusinessName <> '_'
AND BusinessName <> ' '
AND Bus_ActiveSW = 1
ORDER BY BusinessName user (Records=l, Time=31ms)
SQL = select Name, Phone, Email, Fax, BusID, TradingBusID, Location from Users where User
BusIDName (Records=l, Time=31ms)
SQL = select BusinessName from Business where BusID = 222 and Location= 'Fairfield' tradBusIDName (Records=l, Time=16ms)
SQL = select BusinessName from Business where BusID = 220 and Location= 'Fairfield' hedge (Records=0, Time=203ms)
SQL =
SELECT Hedgelnstrument FROM TradeTable
WHERE TransactionNo = '40'
AND Tran_Count='l' headerinfo (Records=0, Time=15ms) SQL =
SELECT BusinessID, TradingBusinessID, Hedgelnstrument FROM
TradeTable WHERE
TransactionNo = '40' AND Tran_Count = '1' getApprover (Records=l, Time=16ms)
SQL =
SELECT Approver FROM Users
WHERE
UserID= ' sophia '
Execution Time
1203 milliseconds
Parameters
URL Parameters :
STATUS=new TRAN C0UNT=1 TRANSACTI0NN0=40 NON=yes TYPE=3
MAX_TRAN_COUNT=l EDITFLAG=No CFT0KEN=56699449 CFID=973
CGI Variables:
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate . ge . com
REM0TE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT_ISSUER=
CONTENT_TYPE=application/x-www-form-urlencoded
AUTH_PASSWORD=
HTTP_REFERER=http : //web06. corporate . ge . com/tradedev/requestforms/treasurymenu . cfm?C
SERVER PROTOCOL=HTTP/l .1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT_LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB__SERVER_API=ISAPI
CF_TEMPLATE_PATH=d:\Inetpub\wwwroot\tradedev\requestforms\forwardform_r.cfm
REQUEST_METHOD=GET
PATH_INFO=/tradedev/requestforms/forwardform_r. cfm
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 5.01; Windows 95)
REM0TE_H0ST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE=
SERVER_SOFTWARE=Microsoft-IIS/4.0
SERVER_NAME=web06. corporate . ge . com
QUERY_STRING=Non=yes&Max_Tran_Count=l&Tyρe=3&Status=new&TransactionNo=40&editflag=N
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/requestforms/forwardform_r.cfm
REMOTE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP_CONTENT_TYPE=application/x-www-form-urlencoded
HTTP_COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL= alse;
CERT_KEYSIZE=
HTTP_CONNECTION=Keep-Alive
PATH_TRANSLATED=d: \Inetpub\wwwroot\tradedev\requestforms\ orwardform_r. cfm
HTTPS_SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE=
APPENDIX C
Quenes
GetFunds (Records=51, Time=203ms)
SQL =
SELECT * FROM Funds
WHERE Location = 'Fairfield'
AND FundNa e <> '_•
AND FundName <> ' '
ORDER BY FundName
CurrencyQuery (Records=71, Time=31ms)
SQL =
SELECT CurrencyCode, CurlD FROM CurrencyTable
WHERE Cur_ActiveSW = 1
ORDER BY CurrencyCode
ContractClassQuery (Records=39, Time=31ms)
SQL =
SELECT ContractClass, CCID FROM ContractClass
WHERE CC_ActiveSW = 1
ORDER BY ContractClass
Business uer (Records=135, Time=62ms)
SQL =
Select BusinessName, BusID from Business
WHERE Location =' Fairfield'
AND BusinessName <> '_'
AND BusinessName <> ' '
AND Bus_ActiveSW = 1
ORDER BY BusinessName user (Records=l, Time=16ms)
SQL = . select Name, Phone, Email, Fax, BusID, TradingBusID, Location from Users where User
BusIDHame (Records=l, Time=31ms)
SQL = select BusinessName from Business where BusID = 222 and Location= ' Fairfield ' tradBusIDNa-ne (Records=l, Time=16ms)
SQL = select BusinessName from Business where BusID = 220 and Location= 'Fairfield' headerinfo (Records=0, Time=172ms) SQL =
SELECT BusinessID, TradingBusinessID, Hedgelnstrument FROM
TradeTable WHERE
TransactionNo = '41' AND Tran_Count = '1'
Execution Time
2406 milliseconds
Parameters
URL Parameters:
STATUS=new
TRAN_COUNT=l
TRANSACTIONNO= 1
NON=no
TYPE=2
MAX_TRAN_COUNT=l EDITFLAG=No CFTOKEN=56699449 CFI D=973
CGI Variables :
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate . ge . com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT_ISSUER= CONTENT_TYPE=application/x-www-form-urlencoded
AUTH PASSWORD=
HTTP~REFERER=http : //web06. corporate . ge . com/tradedev/requestforms/treasurymenu . crm?C
SERVER_PROTOCOL=HTTP/l .1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT_LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB_SERVER_API=ISAPI
CF TEMPLATE PATH=d: \Inetpub\wwwroot\tradedev\requestforms\ordersform_2. cfm
REQUEST_METHOD=GET
PATH_INFO=/tradedev/requestforms/ordersform_2.cfm
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 5.01; Windows 95)
REM0TE_H0ST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE=
SERVER_S0FTWARE=Microsoft-IIS/4.0
SERVER NAME=webO6. corporate. ge.com QUERY_STRING=Non=noSMax_Tran_Count=l&Type=2&Status=new&TransactionNo=41&edιt lag-No
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/requestforms/ordersform_2.cfe
REMOTE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP CONTENT TYPE=application/x-www-form-urlencoded
HTTP~COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL=false;
CERT~KEYSIZE=
HTTP_CONNECTION=Keep-Alive PATH_TRANSLATED=d:\Inetpub\wwwroot\tradedev\requestforms\ordersform_2.cfm
HTTPS_SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE=
Queries
CurrencyOuery (Records=71, Time=203ms)
SQL =
SELECT CurrencyCode, CurlD FROM CurrencyTable
WHERE Cur_ActiveSW = 1
ORDER BY CurrencyCode
BusinessCjuery (Records=135 , Time=63ms )
SQL =
Select BusinessName, BusID from Business
WHERE Location =' Fairfield'
AND BusinessName <> '_'
AND BusinessName <> ' '
AND Bus_ActiveSW = 1 ORDER BY BusinessName user (Records=l, Time=15ms)
SQL = select Name, Phone, Email, Fax, BusID, TradingBusID, Location from Users where User
BusIDName (Records=l, Time=15ms)
SQL = select BusinessName from Business where BusID = 222 and Location= 'Fairfield' tradBusIDName (Records=l, Time=16ms)
SQL <= select BusinessName from Business where BusID = 220 and Location= 'Fairfield' headerinfo (Records=0, Time=156ms) SQL =
SELECT BusinessID, TradingBusinessID, Hedgelnstrument FROM
TradeTable WHERE
TransactionNo = '42'
AND Tran_Count = '1'
Execution Time
1812 milliseconds
Parameters
URL Parameters :
STATUS=new
TRAN_COUNT=l
TRANSACTIONNO=4.
N0N=no
TYPE=1
MAX_TRAN_COUNT=l
EDITFLAG=No
CFTOKEN=56699449
CFID=973
CGI Variables:
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate . ge . com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSI ZE=
CERT_ISSUER=
CONTENT_TYPE=application/x-www-form-urlencoded
AUTH_PASSWORD=
HTTP_REFERER=http: / /webO6. corporate. ge. com/tradedev/requestforms/treasurymenu.cfm?C
SERVER_PROTOCOL=HTTP/1.1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT_LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB_SERVER_API=ISAPI
CF_TEMPLATE_PATH=d:\Inetpub\wwwroot\tradedev\requestforms\settlementform_2.cfm
REQUEST_METHOD=GET
PATH_INFO=/tradedev/requestforms/settlementform_2.cfm
HTTP_USER_AGENT=Mozilla/ .0 (compatible; MSIE 5.01; Windows 95)
REMOTE_HOST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE=
SERVER_SOFTWARE=Microsoft-IIS/4.0
SERVER_NAME=web06. corporate. ge.com
QUERY_STRING=Non=no&Max_Tran_Count=l&Type=l&Status=new&TransactionNo=42&editflag=No
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/requestforms/settle entform_2. cfm
REM0TE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP_CONTENT_TYPE=application/x-www-form-urlencoded
HTTP_COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL=false;
CERT_KEYSIZE=
HTTP_CONNECTION=Keep-Alive
PATH_TRANSLATED=d: \Inetpub\wwwroot\tradedev\.requestforms\settlementform_2. cfm
HTTPS_SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE=
APPENDIX E
Queries
GetFunds (Records=51, Time=203ms)
SQL =
SELECT *
FROM Funds
WHERE Location = 'Fairfield'
AND FundName <> '_'
AND FundName <> • '
ORDER BY FundName
CurrencyQuery (Records=71, Time=31ms)
SQL =
SELECT CurrencyCode, CurID FROM CurrencyTable
WHERE Cur_ActiveSW = 1
ORDER BY CurrencyCode
ContractClassQuery (Records=39, Time=32ms)
SQL =
SELECT ContractClass, CCID FROM ContractClass
WHERE CC_ActiveSW = 1
ORDER BY ContractClass
BusinessCuery (Records=135, Time=63ms)
SQL =
Select BusinessName, BusID from Business
WHERE Location =' Fairfield'
AND BusinessName <> '_'
AND BusinessName <> ' '
AND Bus_ActiveSW = 1
ORDER BY BusinessName user (Records=l, Tιme=16ms)
SQL = select Name, Phone, Email, Fax, BusID, TradingBusID, Location from Users where User
BusIDName (Records=l, Time=16ms)
SQL = select BusinessName from Business where BusID = 222 and Location= 'Fairfield' tradBusIDName (Records=l, Time=16ms)
SQL = select BusinessName from Business where BusID = 220 and Location= 'Fairfield' hedge (Records=0, Time=187ms)
SQL =
SELECT Hedgelnstrument FROM TradeTable
WHERE TransactionNo = '43'
AND Tran_Count='l' headerinfo (Records=0, Time=16ms) SQL =
SELECT BusinessID, radingBusinessID, Hedgelnstrument FROM
TradeTable WHERE
TransactionNo = '43' AND Tran Count - '1'
Executipn Time
2531 milliseconds
Parameters
URL Parameters :
STATUS=new
TRAN_COUNT=l
TRANSACTIONNO=43
NON=no
TYPE=3
MAX_TRAN_COUNT=l
EDITFLAG=No
CFTOKEN=56699449
CFID=973
CGI Variables:
■ 21 ■
APPENDIX F
Queries ~ ~ - ~ -=°
GetFunds (Records=51, Time=188ms) SQL =
SELECT * FROM Funds
WHERE Location = 'Fairfield' AND FundName <> '_'
AND FundName <> ' '
ORDER BY FundName
CurrencyQuery (Records=71, Time=32ms)
SQL =
SELECT CurrencyCode, CurlD FROM CurrencyTable
WHERE Cur_ActiveSW = 1
ORDER BY CurrencyCode
ContractClassQuery (Records=39, Time=31ms)
SQL =
SELECT ContractClass, CCID FROM ContractClass
WHERE CC_ActiveSW = 1
ORDER BY ContractClass
BusinessQuery (Records=135, Time=62ms)
SQL =
Select BusinessName, BusID from Business
WHERE Location =' Fairfield'
AND BusinessName <> '_'
AND BusinessName <> ' '
AND Bus_ActiveSW = 1
ORDER BY BusinessName user (Records=l, Time=47ms)
SQL = select Name, Phone, Email, Fax, BusID, TradingBusID, Location from Users where User
BusIDName (Records=l, Time=31ms)
SQL - select BusinessName from Business where BusID = 222 and Location= 'Fairfield' tradBusIDName (Records=l, Time=16ms)
SQL = select BusinessName from Business where BusID = 220 and Location= 'Fairfield' headerinfo (Records=0, Time=171ms) SQL =
SELECT BusinessID, TradingBusinessID, Hedgelnstrument FROM
TradeTable WHERE
TransactionNo = '44' AND Tran_Count = '1'
Execution Time
2359 milliseconds
Parameters
URL Parameters :
STATUS=new'
TRAN_COUNT=l
TRANSACTIONNO=44
NON=no
TYPE=4
MAX_TRAN_COUNT=l
EDITFLAG=No CFTOKEN=56699449 CFID=973
CGI Variables :
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate, ge . com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT_ISSUER=
CONTENT_TYPE=application/x-www-form-urlencoded
AUTH_PASSWORD=
HTTP_REFERER=http: //web06. corporate . ge . com/tradedev/requestforms/treasurymenu . cfm?C
SERVER_PROTOCOL=HTTP/l .1
HTTPS_SECRETKEYSIZE=
HTTPS=off
Queries
GetFunds (Records=51, Time=219ms)
SQL =
SELECT * FROM Funds
WHERE Location = 'Fairfield'
AND FundName <> '_'
AND FundName <> ' '
ORDER BY FundName
CurrencyQuery (Records=71, Time=31ms)
SQL =
SELECT CurrencyCode, CurlD FROM CurrencyTable
WHERE Cur_ActiveSW = 1
ORDER BY CurrencyCode
ContractClassCjuery (Records=39, Time=31ms )
SQL =
SELECT ContractClass, CCID FROM ContractClass
WHERE CC_ActiveSW = 1
ORDER BY ContractClass
BusinessQuery (Records=135, Time=62ms)
SQL =
Select BusinessName, BusID from Business
WHERE Location =' airfield'
AND BusinessName <> '_'
AND BusinessName <> ' '
AND Bus_ActiveSW = 1
ORDER BY BusinessName user (Records=l, Time=16ms)
SQL = select Name, Phone, Email, Fax, BusID, TradingBusID, Location from Users where User
BusIDName (Records=l, Time=16ms)
SQL = select BusinessName from Business where BusID = 222 and Location= 'Fairfield' tradBusIDName (Records=l, Time=16ms)
SQL = select BusinessName from Business where BusID = 220 and Location= 'Fairfield' headerinfo (Records=0, Time=172ms) SQL =
SELECT BusinessID, radingBusinessID, Hedgelnstrument FROM
TradeTable WHERE
TransactionNo = '45' AND Tran_Count = '1'
Execution Time
2437 milliseconds
Parameters
URL Parameters : STATUS=new
TRAN_COUNT=l
TRANSACTIONNO=45
NON=no
TYPE=5
MAX_TRAN_COUNT=l
EDITFLAG=No
CFTOKEN=56699449
CFID=973
CGI Variables :
SERVER_PORT=80
CONTENT_LENGTH=0
•SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate . ge . com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT_ISSUER=
CONTENT_TYPE=application/x-www-form-urlencoded
AUTH_PASSWORD=
HTTP_REFERER=http: //webOβ . corporate . ge . com/tradedev/requestforms/treasurymenu. cfm?C
SERVER_PROTOCOL=HTTP/l .1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT_LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB_SERVER_API=ISAPI
CF_TEMPLATE_PATH=d : \Inetpub\wwwroot\tradedev\requestforms\optionsform_2.cfm
REQUEST_METHOD=GET
PATH_INFO=/tradedev/requestforms/optionsform_2. cfm
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 5.01; Windows 95)
REMOTE_HOST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE=
SERVER_SOFTWARE=Microsoft-IIS/4.0
SERVER_NAME=web06. corporate . ge . com
QUERY_STRING=Non=no&Max_Tran_Count=l&Type=5&Status=new&TransactionNo=45&editflag=No
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/requestforms/optionsform_2. cfm
REMOTE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP_CONTENT_TYPE=application/x-www-form-urlencoded
HTTP_COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL=false;
CERT_KEYSIZE=
HTTP_CONNECTION=Keep-Alive
PATH_TRANSLATED=d:\Inetpub\wwwroot\tradedev\requestforms\optionsform_2.cfm
HTTPS_^SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE=
APPENDIX H
Queries
GetRequests (Records=4, Time=203ms) SQL =
SELECT T.RequestNo, UserNa e, DateRequested, BuySell, TradeCurrencylD, TradeAmt, Completed, Hedgelnstrument,
(SELECT CurrencyCode FROM CurrencyTable WHERE CurlD = TradeCurrency FROM TradeTable T
WHERE Location = 'Fairfield' AND Tradelmported = 0 AND (Bank_Indicator is NULL OR (Bank_Indicator is not NULL AND
EXISTS (SELECT B.RequestNo FROM BankExchange B WHERE T.RequestNo = B.RequestNo AND B.Execut.ion_ID is not NULL))) ORDER BY UserName, DateRequested, TradeAmt, T.RequestNo
Execution Time
484 milliseconds
Parameters
CGI Variables:
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HT P_HOST=web06. corporate . ge . com
REMOTE_ADDR=3 - 122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT_ISSUER=
CONTENT_TYPE=
AUTH_PASSWORD=
HTTP_REFERER=http: //web06. corporate . ge . com/tradedev/requestforms/treasurymenu. cfm?C
SERVER_PROTOCOL=HTTP/l .1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT__LANGUAGE=en-US
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB_SERVER_API=ISAPI
CF_TEMPLATE_PATH=d:\Inetpub\wwwroot\tradedev\Admin\requests.cfm
REQUEST_METHOD=GET
PATH_INFO=/tradedev/Admin/requests . cf
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 5.01; Windows 95)
REMOTE_HOST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE=
SERVER_SOFTWARE=Microsoft-IIS/4.0
SERVER_NAME=web06. corporate . ge . com
QUERY_STRING=
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/Admin/'requests . cfm
REMOTE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP_COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL=false;
CERT~KEYSIZE=
HTTP_CONNECTION=Keep-Alive
PATH_TRANSLATED=d:\Inetpub\wwwroot\tradedev\Admin\requests.cfm
HTTPS_SERVER_ISSUER=
CERT_FLAGS=
CERT_COOKIE= _32_
APPENDIX I
Queries
Jεers ( Records=9, Time=188ms )
5QL =
SELECT UID, UserlD, Name, Phone, Fax, Email, DelFlag
FROM Users
WHERE Location = 'Fairfield'
ORDER BY UserlD
Execution Time
469 milliseconds
Parameters
CGI Variables :
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate. ge.com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT_ISSUER=
CONTENT_TYPE=
AUTH_PASSWORD=
HTTP_REFERER=http: //webO6. corporate. ge . com/tradedev/requestforms/treasurymenu . cfm?C
SERVER_PR0T0C0L=HTTP/1.1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT_LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_ EYSIZE=
WEB_SERVER_API=ISAPI
CF_TEMPLATE_PATH=d : \Inetpub\wwwroot\tradedev\Admin\Users . cfm
REQUEST_METHOD=GET
PATH_INFO=/tradedev/Admin/Users . cfm
HTTP_USER_AGENT=Mozilla/ .0 (compatible; MSIE 5.01; Windows 95)
REM0TE_H0ST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE=
SERVER_S0FTWARE=Microsoft-IIS/4.0
SERVER_NAME=web06. corporate . ge . com
QUERY_STRING=
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING_-gzip, deflate
SCRIPT_NAME=/tradedev/Admin/Users . cfm
REMOTE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP_COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL=false;
CERT_KEYSIZE=
HTTP_CONNECTION=Keep-Alive
PATH_TRANS ATED=d: \Inetpub\wwwroot\tradedev\Admin\Users . cfm
HTTPS_SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE*-
APPENDIX J
Queries cat ( Records=5 , Time=281ms )
SQL = select * from TransactionlD
Execution Time
609 milliseconds
Parameters
CGI Variables:
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate . ge . com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSI E=
CERT_ISSUER=
CONTENT_TYPE=
AUTH_PASSWORD=
HTTP_REFERER=http : //webO6. corporate . ge . com/tradedev/requestforms/treasurymen . cfm?C
SERVER_PROTOCOL=HTTP/l .1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT_LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB_SERVER_API=ISAPI
CF_TEMPLATE_PATH=d: \Inetpub\wwwroot\tradedev\helpcontent\Admin_index. cfm
REQUEST_METHOD=GET
PATH_INFO=/trade'dev/helpcontent/Admin_index.cfm
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 5.01; Windows 95)
REMOTE_HOST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE-
SERVER_SOFTWARE=Microsoft-IIS/4.0
SERVER_NAME=web06. corpora e . ge . com
QUERY_STRING=
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/helpcontent/Admin_index.cfm
REMOTE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP_COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL=false;
CERT_KEYSIZE=
HTTP_CONNECTION=Keep-Alive
PATH_TRANSLATED=d:\Inetpub\wwwroot\tradedev\helpcontent\Admin_index.cfm
HTTPS_1SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE=
APPENDIX K
Queries
Businessdata (Records=135, Time=469ms)
SQL =
SELECT * FROM Business
WHERE Location = 'Fairfield' AND Bus_ActiveSW = 1
ORDER BY BusinessName
Execution Time
1093 milliseconds Parameters
CGI Variables :
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate . ge . com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT_ISSUER=
CONTENT_TYPE=
AUTH_PASSWORD=
HTTP_REFERER=http: /'/webO6. corporate . ge. com/tradedev/requestforms/treasurymenu. cfm
SERVER_PROTOCOL=HTTP/l .1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT__LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB_SERVER_API=ISAPI
CF_TEMPLATE_PATH=d:\Inetpub\wwwroot\tradedev\Admin\Businesses.cfm
REQUEST_METHOD=GET
PATH_INFO=/tradedev/Admin/Businesses . cfm
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 5.01; Windows 95)
REMOTE_HOST=3.122.98.19
HTTPS_SERVER_SUBϋ (T=
AUTH_USER=
AUTH_TYPE=
SERVER_SOFTWARE=Microsoft-IIS/4.0
SERVER_NAME=web06. corporate . ge . com
QUERY_STRING=
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/Admin/Businesses.cfm
REMOTE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP_COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL=false;
CERT_KEYSIZE=
HTTP_CONNECTION=Keep-Alive
PATH_TRANSLATED=d: \Inetpub\wwwroot\tradedev\Admin\Businesses . cfm
HTTPS_SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE=
APPENDIX L
Queries ~ funddata (Records=51 , Time=204ms )
SQL =
SELECT FundName, Location, FundID FROM Funds
WHERE Location = 'Fairfield'
ORDER BY FundName
Execution Time
657 milliseconds
Parameters
CGI Variables:
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate . ge . com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT__ISSUER=
CONTENT_TYPE=
AUTH_PASSWORD=
HTTP_REFERER=http: //webO6. corporate . ge. com/tradedev/requestforms/treasurymenu. cfm
SERVER_PROTOCOL=HTTP/l .1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP__ACCEPT_LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB_SERVER_API=ISAPI
CF_TEMPLATE_PATH=d: \Inetpub\wwwroot\tradedev\Admin\Funds . cfm
REQUEST_METHOD=GET
PATH_INFO=/tradedev/Admin/Funds . cfm
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 5.01; Windows 95)
REMOTE_HOST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE=
SERVER_SOFTWARE=Microsoft-IIS/ .0
SERVER_NAME=webO6. corporate . e . com
QUERY_STRING=
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/Admin/Funds . cfm
REMOTE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP_COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL=false;
CERT_KEYSI E=
HTTP_CONNECTION=Keep-Alive
PATH_TRANSLATED=d : \Inetpub\wwwroot\tradedev\Admin\Funds . cfm
HTTPS_SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE=
APPENDIX M
Queries
GetRequests (Records=l, Time=266ms)
SQL =
SELECT RequestNo, TransactionNo, UserName, Status, Tran_Count,
BuySell, TradeCurrencylD, DateRequested, Non,Max_Tran_Count, Completed, Hedgelnstrument, Type,
(SELECT CurrencyCode FROM CurrencyTable WHERE CurlD = TradeCurrency AS TradeCurrency FROM TradeTable WHERE Location = 'Fairfield' AND Tran_Count='l' AND UserlD = 'sophia' ORDER BY UserName, RequestNo
Execution Time
718 milliseconds Parameters
CGI Variables:
SERVER_PORT=80
CONTENT_LENGTH=0
SERVER_PORT_SECURE=0
HTTP_ACCEPT=image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/pdf, a
HTTP_HOST=web06. corporate . ge . com
REMOTE_ADDR=3.122.98.19
CERT_SERIALNUMBER=
CERT_SECRETKEYSIZE=
CERT_ISSUER=
CONTENT_TYPE=
AUTH_PASSWORD=
HTTP_REFERER=http: //webO6. corporate . ge . com/tradedev/requestforms/treasurymenu. cfm
SERVER_PROTOCOL=HTTP/l .1
HTTPS_SECRETKEYSIZE=
HTTPS=off
HTTP_ACCEPT_LANGUAGE=en-us
CERT_SUBJECT=
HTTPS_KEYSIZE=
WEB__SERVER_API=ISAPI
CF_TEMPLATE_PATH=d: \Inetpub\wwwroo \tradedev\requestforms\Retreive . cfm
REQUEST^_METHOD=GET
PATH_INFO=/tradedev/requestforms/Retreive . cfm
HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 5.01; Windows 95)
REMOTE_HOST=3.122.98.19
HTTPS_SERVER_SUBJECT=
AUTH_USER=
AUTH_TYPE=
SERVER_SOFTWARE=Microsoft-IIS/ .0
SERVER_NAME=web06. corporate . ge . com
QUERY_STRING=
CERT_SERVER_SUBJECT=
CERT_SERVER_ISSUER=
HTTP_ACCEPT_ENCODING=gzip, deflate
SCRIPT_NAME=/tradedev/requestforms/Retreive. cfm
REMOTE_USER=
GATEWAY_INTERFACE=CGI/1.1
HTTP_COOKIE=SITESERVER=ID=dc7ale4bf8db91e329bee7086cd4df8f; myGEDisplay=POLL=false;
CERT_KEYSIZE=
HTTP_CONNECTION=Keep-Alive
PATH_TRANSLATED=d:\Inetpub\wwwroot\tradedev\requestforms\Retreive.cfm
HTTPS_SERVER_ISSUER=
CERT_FLAGS=
CERT COOKIE= ~ ά l '