US20060280302A1 - Systems and methods for calculating specified matrices - Google Patents
Systems and methods for calculating specified matrices Download PDFInfo
- Publication number
- US20060280302A1 US20060280302A1 US11/443,096 US44309606A US2006280302A1 US 20060280302 A1 US20060280302 A1 US 20060280302A1 US 44309606 A US44309606 A US 44309606A US 2006280302 A1 US2006280302 A1 US 2006280302A1
- Authority
- US
- United States
- Prior art keywords
- data
- matrices
- predetermined
- key figures
- aggregation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/03—Credit; Loans; Processing thereof
Definitions
- the present invention generally relates to electronic data processing. More particularly, the invention relates to computer-implemented methods, computer systems, and computer program products for determining specified matrices.
- the specified matrices may be associated with financial institutions and with financial affairs in banking practice, for example.
- SAP SAP proprietary software tools
- Basel Capital Accord Basel II (Basel II) (commercially available from SAP AG, Waldorf, Germany), which enhances the capabilities of the SAP banking solution portfolio.
- the SAP solution for the Basel II represents a risk-sensitive framework that provides capabilities for calculating risk exposure, calculating capital, managing market risk, managing interest risk, managing liquidity risk, calculating and managing all areas of credit risk, and facilitating the handling of mass data.
- Basel II may serve the economic interests associated with financial institutions and associated with financial affairs in banking practice.
- matrices such as matrices associated with financial institutions and with financial affairs and banking practice.
- Embodiments of the invention can be easily integrated into existing credit risk platforms as, for example, the above-mentioned SAP solution Basel II.
- a computer readable medium may be provided for storing a plurality of instructions implemented by a computer program to execute a computer-implemented method.
- the computer-implemented method may optionally perform an automated generic aggregation of data in either a linear or a parallel processing mode, thereby improving the computer power of software, particularly when using mass data.
- a computer-implemented method for determining specified matrices, such as matrices associated with financial institutions and financial affairs in banking practice.
- the method may include receiving mass data from one or more databases of one or more different data sources associated with banking practice, the mass data including sets of rows and sets of columns, each row corresponding to a record, and the columns including fields of predetermined granularity characteristics and fields of predetermined key figures.
- the method may also include selecting predetermined granularity characteristics and predetermined key figures, selecting predetermined aggregation operations to be performed, and reading input data packages from the one or more databases.
- the method may also include processing the data packages by identifying the customized granularity characteristics, identifying the predetermined key figures, and aggregating the records in each data package for key figures by using aggregation operations.
- the method may include forming at least one base matrix comprising the aggregated records of the customized granularity characteristics and key figures by saving the results of processing each data package and using the base matrix to calculate the specified matrices.
- the aggregation may be computed on at least one of predetermined key figures using predetermined aggregation operations selected from a function pool and customer-defined aggregation operations to be defined with input using the predetermined aggregation operations.
- the aggregation may be computed on customer-defined key figures to be defined with input using the predetermined aggregation operations selected from a function pool and using at least one of the predetermined aggregation operations and the customer-defined aggregation operations.
- FIG. 1 illustrates a flowchart of an exemplary method for calculating matrices, consistent with an embodiment of the invention
- FIG. 2 illustrates a block diagram of an exemplary system, consistent with an embodiment of the invention.
- computer-implemented methods may be provided for determining specified matrices, such as matrices associated with financial institutions and with financial affairs and banking practice.
- specified matrices such as matrices associated with financial institutions and with financial affairs and banking practice.
- data processing systems, computer program products that can be stored on a computer-readable medium, and a computer-readable medium may be provided.
- Data processing systems may include a single data processor or a plurality of data processors via inter-computer network, each data processor including processing means (processor), storage means (memory), bus means (bus), network means (network), interface means, input means, and output means (input and output devices).
- the computer system may comprise a server.
- the data processor may be, for example, a conventional desktop computer, a multiprocessor computer, or the like.
- the processor may be, for example, a Central Processing Unit (CPU), a Micro Controller Unit (MCU), Digital Signal Processor (DSP), or the like.
- Storage means may store the specified mass data.
- Storage means may be memory for temporarily or permanently storing data and instructions.
- memory may also be implemented in network, in computers and in a processor itself, such as in a cache or a register.
- Memory can be, for example, Read Only Memory (ROM), Random Access Memory (RAM), or memory with other access options.
- Memory may be implemented by computer-readable media, for example: (a) magnetic media, such as hard disk, floppy disk or other magnetic disk, tape or cassette tape; (b) optical media, such as optical disk (CD-ROM, DVD); and/or (c) semiconductor media, like DRAM, SRAM, EPROM, EEPROM, or the like.
- Memory may also store support modules, such as a Basic Input Output System (BIOS), an Operating system (OS), a program library, a compiler or interpreter, and a text processing tool.
- BIOS Basic Input Output System
- OS Operating system
- program library such as a program library, a compiler or interpreter, and a text processing
- Input means may be any device for providing data and instructions for processing by computer, such as a keyboard or pointing device such as a mouse, trackball, or cursor direction key.
- Output means may be any device for presenting results of aggregated data packages, such as a printer, monitor, or a display (e.g., a Cathode Ray Tube (CRT), Flat Panel Display, Liquid Crystal Display (LCD)).
- CTR Cathode Ray Tube
- LCD Liquid Crystal Display
- Computer bus and networks may provide logical and physical connections by conveying data and instruction signals. Connections inside computer may be referred to as “bus” connections, and connections between computers may be referred to as “inter-computer network.”
- a network may include gateways, which may be devices (computers) that specialize in data transmission and protocol conversion and allow users working in one network to access another network.
- Networking environments are common in offices, enterprise-wide computer networks, intranets and the Internet (i.e. world wide web).
- a network can be a wired or wireless.
- Exemplary network implementations include a local area network (LAN), a wide area network (WAN), a public switched telephone network (PSTN), an Integrated Services Network (ISDN), an infra-red (IR) link, a radio link, like Universal Mobile Tele-communications System (UMTS), Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), and a satellite link.
- LAN local area network
- WAN wide area network
- PSTN public switched telephone network
- ISDN Integrated Services Network
- IR infra-red
- UMTS Universal Mobile Tele-communications System
- GSM Global System for Mobile Communication
- CDMA Code Division Multiple Access
- Exemplary transmission protocols and data formats include transmission control protocol/internet protocol (TCP/IP), hyper text transfer protocol (HTTP), secure HTTP, wireless application protocol, unique resource locator (URL), unique resource identifier (URI), hyper text markup language (HTML), extensible markup language (XML), extensible hyper text markup language (XHTML), and wireless application markup language (WML), etc.
- TCP/IP transmission control protocol/internet protocol
- HTTP hyper text transfer protocol
- HTTP secure HTTP
- wireless application protocol unique resource locator
- URL unique resource locator
- URI unique resource identifier
- HTML hyper text markup language
- XML extensible markup language
- XHTML extensible hyper text markup language
- WML wireless application markup language
- Interfaces for linking together the data processing units of a data processing system may be, for example, a serial port interface, a parallel port interface, a universal serial bus (USB) interface, an internal modem, or an external modem.
- serial port interface a serial port interface
- parallel port interface a parallel port interface
- USB universal serial bus
- USB universal serial bus
- Computer program products may be provided that include a plurality of instructions for causing a processor of a computer system to execute methods consistent with the present invention.
- Computer program products may define the operation of computer and its interaction in inter-computer network.
- Computer program products may be available as source code in any programming language and as object code (binary code) in a compiled form.
- Computer program products may be used in connection with support modules, such as compilers, interpreters, and operating systems.
- the computer program products may be stored in memory, such as a data carrier or a computer-readable medium.
- a data carrier may be conveniently inserted into input device.
- the data carrier may be implemented as any computer readable medium.
- a carrier may be an article of manufacture including a computer readable medium having readable program code embodied therein for executing a method.
- program signals may embody a computer program and be transmitted via inter-computer network to a data processor.
- FIG. 1 illustrates a flowchart 100 of an exemplary method for calculating specified matrices associated with, for example, financial institutions and/or financial affairs in banking practice.
- a list with the rated entities may be provided. According to that list, at step 120 , ratings and utilizations for T0 and T1 may be read from a historical database. A base matrix before aggregation may be created at step 120 by reading the mass data as a selection according to the rating entities.
- the mass data may be aggregated to create a base matrix after aggregation.
- the aggregated base matrix may be used to calculate different result matrices ( 140 a - d ).
- Exemplified result matrices may be T0-portfolio matrix ( 140 a ), T1-portfolio matrix ( 140 b ), a migration matrix ( 140 c ), and a combined matrix such as an acquisition and migration data (acquisition and migration matrix 140 d ).
- mass data may be used which may be stored in a historical database including, for example, a database with hundreds or millions of records.
- the mass data (“input data”) may include a plurality of M data records, wherein M represents a large amount of data records to be selected and aggregated that can not be handled in the main memory of a data processor.
- Mass data (“input data”) may include packetized blocks of data provided by different databases of different accessible data sources, and including sets of rows and sets of columns. Each row may correspond to a record, and the columns may include fields of predetermined granularity characteristics and fields of predetermined key figures. The generic aggregation of characteristics and key figures may reduce the mass data according to a given customized granularity. Due to the plurality of M data records, the mass data may be customized as packages including M p ⁇ M data records.
- Computer-implemented methods consistent with the invention may begin with a selection of mass data (“input data”), including the plurality of M data records, to aggregate.
- the mass data may be provided by different accessible primary databases of different accessible data sources.
- the selected blocks of packetized mass data may be assigned among each other, and the result of each assignment may be stored to a global database.
- Customization of the selected mass data may be required for defining granularity characteristics and aggregation operations to be carried out by a processor in a data processing system for computing fields of key figures.
- the granularity characteristics and predetermined key figures may include, for example, data regarding the financial sector, such as rating methods, rating classes, rating class dates, identifiers for inflows and outflows, utilization (e.g. drawing of a loan (monetary amount)), utilization dates, and a segment identifier.
- the selected mass data may be prepared as data packages according to a customer-defined package size including M p ⁇ M data records in a pre-processing step before reading the mass data.
- the packaged data may be enriched in parallel pre-processing with data from an accessible single secondary database or from accessible secondary databases.
- the results of enrichment may be saved to local databases of the respective data processors where the data may be processed.
- the selected data records may be stored in a database (base matrix before aggregation) or may be directly aggregated into a base matrix after aggregation.
- the selection and/or aggregation can be performed as jobs.
- a job or a plurality of jobs can be processed in a parallel processing mode, thus improving the computing power and run time performance of software either using a single data processor or a network of data processors.
- the processing of an aggregation algorithm can optionally run in a linear processing mode to sequentially aggregate and merge packages within a job.
- An aggregated base matrix may be obtained from the selection and aggregation processes ( FIG. 1 , step 130 ).
- the base matrix after aggregation may be stored in a database.
- the base matrix after aggregation may contain all the data necessary to calculate migration matrices for a credit risk analysis and reporting according to, for example, the Basel II Capital Accord.
- the base matrix after aggregation may contain significantly less data than the originally used mass data.
- the base matrix after aggregation may contain at most a few thousand data entries depending on the predetermined granularity characteristics, such as the rating method used.
- the base matrix after aggregation may include 1000 or fewer records, 500 or fewer records, etc.
- the base matrix after aggregation may include 100 or fewer columns, 20 or fewer columns, etc., wherein the columns include fields of predetermined granularity characteristics and fields of predetermined key figures.
- Storing the aggregated base matrix permits an examination of the evaluations over a long time, without having to store many different matrices. Time and use of computer power for recalculation based on a historical database can also be avoided. Furthermore, different aggregated base matrices for all the needs of a financial institution can be calculated and provided to the different users of the financial institution.
- the different aggregated base matrices may have varying granularity characteristics and/or varying customer-defined key figures, such as a segment identifier, a rating method, a business partner identifier, a rating given by the rating method, a rating date, an identifier for inflows, an identifier for outflows, an utilization (e.g. drawing of a credit loan), and a currency of the utilization.
- the obtained base matrix after aggregation may be processed into the specified matrices ( 140 a - d ). Because of the low amount of data, the processing of the base matrix after aggregation may be performed in the main memory of a computer.
- a specified matrix may be a matrix that may be customized by the users and/or prescribed by other institutions or requirements, such as Basel II.
- the specified matrices may also be referred to as result matrices and may include, for example, portfolio matrices at specified times, migration matrices, acquisition matrices, matrices concerning inflows and outflows, matrices concerning changes of volume and/or combinations of two or more of these matrices, such as an acquisition and migration matrix.
- Specified result matrices may also be calculated in batch modes (background processing), and the results may be stored to a database. The results can be stored in a database or alternatively displayed in a screen reporting (step 150 ).
- the data of the aggregated base matrix and/or the result matrices may also be enriched in a post-processing step with data from an accessible secondary database or from accessible secondary databases.
- the results of the enrichment may be stored in a database.
- FIG. 2 illustrates at a block diagram of an exemplary system 200 , consistent with an embodiment of the invention.
- System 200 may include a user 210 , one or more application servers 220 , and one or more database servers 230 .
- Mass data may be stored in a database with rated entities 232 .
- Application server 220 may read the rated entities 224 and process the rated entities to calculate the base matrix, as illustrated at 226 .
- the base matrix may be stored in a database for temporary data 234 .
- the base matrix may be read into the main memory to calculate the result matrices.
- the results can be stored in an additional database 236 .
- the methods performed by application server 220 may be scheduled and executed by run control 222 .
- a bank may have business partner ratings modules of its own, or may obtain external ratings. These ratings may be stored in a database for time series of the bank analyzer component called historical database. The time series can be assumed to contain mass data (millions of business partner ratings).
- Table 1 illustrates some exemplary entities of a historical database. Some or all of the business partners may be rated with all rating methods. Furthermore, the business partners may obtain more than one rating a year. Therefore, the present working example is very simple.
- the granularity level of Table 1 includes the fields SID, RM, BUPA and RDAT.
- the first step of the calculation may be to read the database with the time series of ratings ( FIG. 1 , step 110 ).
- SID Segment Identifier
- RM Raster Identifier
- BUPA business partner identifier
- the time series with rating data may be transformed into a new list where rating at t0 and rating at t1 may be given in one row of the table to obtain a base matrix before aggregation.
- the transformation may be done by, for example, the following operations:
- step 120 may be performed by the software using efficient parallel processing algorithms.
- the results of step 120 may be a matrix, such as the matrix illustrated in Table 3 below.
- the granularity level of Table 3 may include the fields SID, RM, and BUPA.
- all values for FX may be 0 because the initial currency and the evaluation currency are identical.
- the matrix obtained in step 120 may be aggregated to a basic matrix after aggregation ( FIG. 1 , step 130 ). While the matrices previously used in step 110 and step 120 (such as “time series with rating data” and “basic matrix before aggregation”) may be used only once in the process, the “basic matrix after aggregation” may be the starting point for several additional matrices and may be re-used several times.
- the business partners (belonging to the same SID and RM) having the same ratings RT 0 and RT 1 may be counted, and the fields UT 0 and UT 1 may be summed for the business partners having the same ratings RT 0 and RT 1 .
- the granularity level of Table 4 includes the fields SID, RM, RT 0 , RT 1 , and IO.
- the number of ratings is 1 for each granularity, that is, for each combination of the values SID, RM, RT 0 , RT 1 , and IO.
- the values in the columns CNT, UT 0 , and UT 1 may be sums.
- the “basic matrix after aggregation” may be re-used repeatedly.
- T0-portfolio matrix 140 a may require key information, such as the structure of the portfolio at the beginning of the period.
- the structure may be defined by rating categories.
- the key measure may be the “key date utilization” (e.g., a monetary amount of loans UT 0 and UT 1 ).
- the portfolio matrix may be calculated by summing the fields UT 0 , UT 1 , CNT, and FX for the different ratings at T0 (RT 0 ).
- the base matrix after aggregation obtained in step 130 (Table 4) may thus be modified to create Table 5, as illustrated below.
- the granularity level of Table 5 may include the fields SID, RM, and RT 0 . Granularities RT 1 and IO may be eliminated.
- T1-portfolio matrix 140 b may require transparent information on the portfolio structure at the end of the period under consideration based on consistent dimensions and measures.
- the portfolio matrix 140 b may be calculated by, for example, summing the fields UT 0 , UT 1 , CNT, and FX for the different ratings at T1 (RT 1 ).
- Table 6 may be created, which may represent T1-portfolio matrix 140 b .
- the granularity level of Table 6 may include the fields SID, RM, and RT 1 . Granularities RT 0 and IO may be eliminated.
- Migration matrix 140 c may include information about a change of ratings. Migration matrix 140 c may determine in which rating categories the customers show up at the end of a period given a specific rating at the beginning of the period.
- the key figures CNT and UT 0 (UT 1 ) may be used to calculate rating transitions (e.g., weighted or unweighted frequencies or probabilities).
- the migration matrix may be calculated by summing up the fields UT 0 , UT 1 , CNT, and FX for the different rating transitions RT 0 ⁇ RT 1 on the specified granularity.
- Table 7 may be created.
- the granularity level of Table 7 may include the fields SID, RM, RT 0 , and RT 1 .
- the acquisition and migration matrix 140 b may be assembled by the single matrices described before. Furthermore, the acquisition and migration matrix 140 b can contain additional data based on the base matrix as mentioned above, for example, data of inflows and outflows of customers, customer acquisitions, changes in volume, acquisition performance, and the portfolio after migrations.
- the data of inflows and outflows of customers may be calculated by applying an appropriate filter based on the base matrix.
- the customer acquisition may arise from the total of customer wins and customer losses.
- the calculation of the portfolio after migration to t1 may also be based on the already determined data, the portfolio at t0, as well as the migration matrix.
- the changed volume may be calculated as volume of the portfolio at t1 minus volume of the portfolio after migration to t1 minus customer acquisition.
- the acquisition performance may be calculated as the total of customer acquisition and changed volume.
- Table 8 may be achieved for the acquisition and migration matrix 140 d .
- risk management may be provided with better information to adequately adjust the customer acquisition strategy, focus on customer retention, and react on unfavorable rating migration effects.
- the consistent information basis provided above may ensure that consistent actions can be initiated.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- Development Economics (AREA)
- General Physics & Mathematics (AREA)
- Human Resources & Organizations (AREA)
- Technology Law (AREA)
- Entrepreneurship & Innovation (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Description
- The present invention generally relates to electronic data processing. More particularly, the invention relates to computer-implemented methods, computer systems, and computer program products for determining specified matrices. The specified matrices may be associated with financial institutions and with financial affairs in banking practice, for example.
- As international financial markets expand, global concerns over the soundness of banking practices are driving stringent new requirements for bank-level management, regulatory control, and market disclosure. Data processing systems may use software tools, such as SAP proprietary software tools, to meet these banking requirements. One example of such a SAP software tool is Basel Capital Accord (Basel II) (commercially available from SAP AG, Waldorf, Germany), which enhances the capabilities of the SAP banking solution portfolio.
- The SAP solution for the Basel II represents a risk-sensitive framework that provides capabilities for calculating risk exposure, calculating capital, managing market risk, managing interest risk, managing liquidity risk, calculating and managing all areas of credit risk, and facilitating the handling of mass data. Basel II may serve the economic interests associated with financial institutions and associated with financial affairs in banking practice.
- In view of prior software tool solutions for banking systems, there still remains the need to improve the software performance (e.g., runtime performance). According to the Basel II capital record rating, data must be analyzed regularly in the form of portfolio and migration matrices. One problem is calculating the rating portfolio and migration matrices efficiently. Usually, the underlying mass data may not allow computer-based main memory processing since the large amount of data may exceed the memory limits of the computer.
- Therefore, there exists a need to provide methods and systems for reducing the processing time needed to calculate data necessary to assess the risks according to Basel II, as mentioned above. There also exists a need to provide methods and systems for guarantying the data and process integrity.
- Consistent with embodiments of the invention, methods and systems are provided to determine specified matrices, such as matrices associated with financial institutions and with financial affairs and banking practice. Embodiments of the invention can be easily integrated into existing credit risk platforms as, for example, the above-mentioned SAP solution Basel II.
- In accordance with embodiments of the invention, computer systems and computer program products may be provided for determining specified matrices. Further, a computer readable medium may be provided for storing a plurality of instructions implemented by a computer program to execute a computer-implemented method. The computer-implemented method may optionally perform an automated generic aggregation of data in either a linear or a parallel processing mode, thereby improving the computer power of software, particularly when using mass data.
- Consistent with an embodiment of the invention, a computer-implemented method is provided for determining specified matrices, such as matrices associated with financial institutions and financial affairs in banking practice. The method may include receiving mass data from one or more databases of one or more different data sources associated with banking practice, the mass data including sets of rows and sets of columns, each row corresponding to a record, and the columns including fields of predetermined granularity characteristics and fields of predetermined key figures. The method may also include selecting predetermined granularity characteristics and predetermined key figures, selecting predetermined aggregation operations to be performed, and reading input data packages from the one or more databases. The method may also include processing the data packages by identifying the customized granularity characteristics, identifying the predetermined key figures, and aggregating the records in each data package for key figures by using aggregation operations. In addition, the method may include forming at least one base matrix comprising the aggregated records of the customized granularity characteristics and key figures by saving the results of processing each data package and using the base matrix to calculate the specified matrices.
- In accordance with an embodiment of the invention, the aggregation may be computed on at least one of predetermined key figures using predetermined aggregation operations selected from a function pool and customer-defined aggregation operations to be defined with input using the predetermined aggregation operations.
- In another embodiment of the invention, the aggregation may be computed on customer-defined key figures to be defined with input using the predetermined aggregation operations selected from a function pool and using at least one of the predetermined aggregation operations and the customer-defined aggregation operations.
- Additional objects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of embodiments of the invention. The objects and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
- It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
- The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. In the drawings:
-
FIG. 1 illustrates a flowchart of an exemplary method for calculating matrices, consistent with an embodiment of the invention; and -
FIG. 2 illustrates a block diagram of an exemplary system, consistent with an embodiment of the invention. - Reference will now be made in detail to the present invention, examples of which are illustrated in the accompanying drawings in which like reference numbers refer to corresponding elements.
- Consistent with an aspect of the invention, computer-implemented methods may be provided for determining specified matrices, such as matrices associated with financial institutions and with financial affairs and banking practice. In addition, data processing systems, computer program products that can be stored on a computer-readable medium, and a computer-readable medium may be provided.
- Data processing systems (computer systems) consistent with the invention may include a single data processor or a plurality of data processors via inter-computer network, each data processor including processing means (processor), storage means (memory), bus means (bus), network means (network), interface means, input means, and output means (input and output devices). The computer system may comprise a server. The data processor may be, for example, a conventional desktop computer, a multiprocessor computer, or the like. The processor may be, for example, a Central Processing Unit (CPU), a Micro Controller Unit (MCU), Digital Signal Processor (DSP), or the like.
- Storage means may store the specified mass data. Storage means may be memory for temporarily or permanently storing data and instructions. Although memory is conveniently illustrated as part of computer, memory may also be implemented in network, in computers and in a processor itself, such as in a cache or a register. Memory can be, for example, Read Only Memory (ROM), Random Access Memory (RAM), or memory with other access options. Memory may be implemented by computer-readable media, for example: (a) magnetic media, such as hard disk, floppy disk or other magnetic disk, tape or cassette tape; (b) optical media, such as optical disk (CD-ROM, DVD); and/or (c) semiconductor media, like DRAM, SRAM, EPROM, EEPROM, or the like. Memory may also store support modules, such as a Basic Input Output System (BIOS), an Operating system (OS), a program library, a compiler or interpreter, and a text processing tool.
- Input means may be any device for providing data and instructions for processing by computer, such as a keyboard or pointing device such as a mouse, trackball, or cursor direction key. Output means may be any device for presenting results of aggregated data packages, such as a printer, monitor, or a display (e.g., a Cathode Ray Tube (CRT), Flat Panel Display, Liquid Crystal Display (LCD)).
- Computer bus and networks may provide logical and physical connections by conveying data and instruction signals. Connections inside computer may be referred to as “bus” connections, and connections between computers may be referred to as “inter-computer network.” Optionally, a network may include gateways, which may be devices (computers) that specialize in data transmission and protocol conversion and allow users working in one network to access another network.
- Networking environments (also referred to as a network) are common in offices, enterprise-wide computer networks, intranets and the Internet (i.e. world wide web). A network can be a wired or wireless. Exemplary network implementations include a local area network (LAN), a wide area network (WAN), a public switched telephone network (PSTN), an Integrated Services Network (ISDN), an infra-red (IR) link, a radio link, like Universal Mobile Tele-communications System (UMTS), Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), and a satellite link. Exemplary transmission protocols and data formats include transmission control protocol/internet protocol (TCP/IP), hyper text transfer protocol (HTTP), secure HTTP, wireless application protocol, unique resource locator (URL), unique resource identifier (URI), hyper text markup language (HTML), extensible markup language (XML), extensible hyper text markup language (XHTML), and wireless application markup language (WML), etc.
- Interfaces for linking together the data processing units of a data processing system may be, for example, a serial port interface, a parallel port interface, a universal serial bus (USB) interface, an internal modem, or an external modem.
- Consistent with an embodiment of the invention, computer program products may be provided that include a plurality of instructions for causing a processor of a computer system to execute methods consistent with the present invention. Computer program products may define the operation of computer and its interaction in inter-computer network. For example, computer program products may be available as source code in any programming language and as object code (binary code) in a compiled form. Computer program products may be used in connection with support modules, such as compilers, interpreters, and operating systems. The computer program products may be stored in memory, such as a data carrier or a computer-readable medium.
- For the communication of a computer program product and a computer, a data carrier may be conveniently inserted into input device. The data carrier may be implemented as any computer readable medium. A carrier may be an article of manufacture including a computer readable medium having readable program code embodied therein for executing a method. Furthermore, program signals may embody a computer program and be transmitted via inter-computer network to a data processor.
-
FIG. 1 illustrates aflowchart 100 of an exemplary method for calculating specified matrices associated with, for example, financial institutions and/or financial affairs in banking practice. - At
step 110, a list with the rated entities may be provided. According to that list, atstep 120, ratings and utilizations for T0 and T1 may be read from a historical database. A base matrix before aggregation may be created atstep 120 by reading the mass data as a selection according to the rating entities. - At
step 130, the mass data may be aggregated to create a base matrix after aggregation. The aggregated base matrix may be used to calculate different result matrices (140 a-d). Exemplified result matrices may be T0-portfolio matrix (140 a), T1-portfolio matrix (140 b), a migration matrix (140 c), and a combined matrix such as an acquisition and migration data (acquisition andmigration matrix 140 d). - In more detail, mass data may be used which may be stored in a historical database including, for example, a database with hundreds or millions of records. The mass data (“input data”) may include a plurality of M data records, wherein M represents a large amount of data records to be selected and aggregated that can not be handled in the main memory of a data processor. Mass data (“input data”) may include packetized blocks of data provided by different databases of different accessible data sources, and including sets of rows and sets of columns. Each row may correspond to a record, and the columns may include fields of predetermined granularity characteristics and fields of predetermined key figures. The generic aggregation of characteristics and key figures may reduce the mass data according to a given customized granularity. Due to the plurality of M data records, the mass data may be customized as packages including Mp<M data records.
- Computer-implemented methods consistent with the invention may begin with a selection of mass data (“input data”), including the plurality of M data records, to aggregate. The mass data may be provided by different accessible primary databases of different accessible data sources. After selecting mass data due to selection criteria, the selected blocks of packetized mass data may be assigned among each other, and the result of each assignment may be stored to a global database.
- Customization of the selected mass data may be required for defining granularity characteristics and aggregation operations to be carried out by a processor in a data processing system for computing fields of key figures. The granularity characteristics and predetermined key figures may include, for example, data regarding the financial sector, such as rating methods, rating classes, rating class dates, identifiers for inflows and outflows, utilization (e.g. drawing of a loan (monetary amount)), utilization dates, and a segment identifier.
- If necessary, the selected mass data may be prepared as data packages according to a customer-defined package size including Mp<M data records in a pre-processing step before reading the mass data.
- The packaged data may be enriched in parallel pre-processing with data from an accessible single secondary database or from accessible secondary databases. The results of enrichment may be saved to local databases of the respective data processors where the data may be processed.
- The selected data records may be stored in a database (base matrix before aggregation) or may be directly aggregated into a base matrix after aggregation. The selection and/or aggregation can be performed as jobs. A job or a plurality of jobs can be processed in a parallel processing mode, thus improving the computing power and run time performance of software either using a single data processor or a network of data processors. Depending on the capacity utilization of a data processing system, the processing of an aggregation algorithm can optionally run in a linear processing mode to sequentially aggregate and merge packages within a job.
- An aggregated base matrix may be obtained from the selection and aggregation processes (
FIG. 1 , step 130). The base matrix after aggregation may be stored in a database. The base matrix after aggregation may contain all the data necessary to calculate migration matrices for a credit risk analysis and reporting according to, for example, the Basel II Capital Accord. - The base matrix after aggregation may contain significantly less data than the originally used mass data. In one embodiment consistent with the invention, the base matrix after aggregation may contain at most a few thousand data entries depending on the predetermined granularity characteristics, such as the rating method used. For example, the base matrix after aggregation may include 1000 or fewer records, 500 or fewer records, etc. The base matrix after aggregation may include 100 or fewer columns, 20 or fewer columns, etc., wherein the columns include fields of predetermined granularity characteristics and fields of predetermined key figures.
- Storing the aggregated base matrix permits an examination of the evaluations over a long time, without having to store many different matrices. Time and use of computer power for recalculation based on a historical database can also be avoided. Furthermore, different aggregated base matrices for all the needs of a financial institution can be calculated and provided to the different users of the financial institution. The different aggregated base matrices may have varying granularity characteristics and/or varying customer-defined key figures, such as a segment identifier, a rating method, a business partner identifier, a rating given by the rating method, a rating date, an identifier for inflows, an identifier for outflows, an utilization (e.g. drawing of a credit loan), and a currency of the utilization.
- Consequently, different users of a financial institute do not require access to a historical database. Therefore, the administration of the system, the data integrity, and the performance of the system can be improved with low system requirements.
- The obtained base matrix after aggregation may be processed into the specified matrices (140 a-d). Because of the low amount of data, the processing of the base matrix after aggregation may be performed in the main memory of a computer. A specified matrix may be a matrix that may be customized by the users and/or prescribed by other institutions or requirements, such as Basel II. The specified matrices may also be referred to as result matrices and may include, for example, portfolio matrices at specified times, migration matrices, acquisition matrices, matrices concerning inflows and outflows, matrices concerning changes of volume and/or combinations of two or more of these matrices, such as an acquisition and migration matrix. Specified result matrices may also be calculated in batch modes (background processing), and the results may be stored to a database. The results can be stored in a database or alternatively displayed in a screen reporting (step 150).
- The data of the aggregated base matrix and/or the result matrices may also be enriched in a post-processing step with data from an accessible secondary database or from accessible secondary databases. The results of the enrichment may be stored in a database.
-
FIG. 2 illustrates at a block diagram of anexemplary system 200, consistent with an embodiment of the invention.System 200 may include auser 210, one ormore application servers 220, and one ormore database servers 230. Mass data may be stored in a database with ratedentities 232.Application server 220 may read the ratedentities 224 and process the rated entities to calculate the base matrix, as illustrated at 226. The base matrix may be stored in a database fortemporary data 234. The base matrix may be read into the main memory to calculate the result matrices. The results can be stored in anadditional database 236. The methods performed byapplication server 220 may be scheduled and executed byrun control 222. - Exemplary embodiments of the present invention will now be explained in more detail with a working example.
- In a first step, all information of the period to be analyzed may be brought together. A bank may have business partner ratings modules of its own, or may obtain external ratings. These ratings may be stored in a database for time series of the bank analyzer component called historical database. The time series can be assumed to contain mass data (millions of business partner ratings).
- The database may have the following fields:
-
- SID: Segment Identifier (e.g., 01=Automotive);
- RM: Rating method (e.g., INTERNAL=in-house rating model of the bank);
- BUPA: Business partner identifier;
- RAT: Rating given by the rating method;
- RDAT: Rating date (date with the meaning “rating is valid from . . . ”)
- IO: Identifier for inflows and outflows (e.g. 1=inflow, 2=outflow);
- UTIL: Utilization (e.g. drawing of a credit loan); and
- CURR: Currency of the utilization.
- Table 1 illustrates some exemplary entities of a historical database. Some or all of the business partners may be rated with all rating methods. Furthermore, the business partners may obtain more than one rating a year. Therefore, the present working example is very simple. The granularity level of Table 1 includes the fields SID, RM, BUPA and RDAT.
TABLE 1 Rating Business Inflow/ Segment ID Method Partner Rating Valid Rating Outflow Utilization Currency SID RM BUPA From RDAT RAT IO UTIL CURR 1 INTERNAL BUPA_01 21.04.1999 A 100.000,00 USD 1 INTERNAL BUPA_01 26.04.2000 A 80.000,00 USD 1 INTERNAL BUPA_02 14.05.1999 B 100.000,00 USD 1 INTERNAL BUPA_02 12.08.2000 C 50.000,00 USD 1 INTERNAL BUPA_03 01.08.1999 A 50.000,00 USD 1 INTERNAL BUPA_03 01.08.2000 B 2 50.000,00 USD 1 INTERNAL BUPA_04 14.02.1999 C 200.000,00 USD 1 INTERNAL BUPA_04 18.09.2000 C 150.000,00 USD 1 INTERNAL BUPA_05 19.01.2000 D 1 100.000,00 USD 1 INTERNAL BUPA_06 04.11.1999 B 150.000,00 USD 1 INTERNAL BUPA_06 23.05.2000 A 200.000,00 USD 1 INTERNAL BUPA_07 25.09.1999 B 50.000,00 USD 1 INTERNAL BUPA_07 23.12.2000 B 30.000,00 USD - The first step of the calculation may be to read the database with the time series of ratings (
FIG. 1 , step 110). In one embodiment consistent with the invention, only the granularity fields SID (Segment Identifier), RM (Rating method), and BUPA (business partner identifier) may be retrieved. As a result of reading the database, table 2 may be obtained.TABLE 2 Segment ID Rating Method Business Partner SID RM BUPA 1 INTERNAL BUPA_01 1 INTERNAL BUPA_02 1 INTERNAL BUPA_03 1 INTERNAL BUPA_04 1 INTERNAL BUPA_05 1 INTERNAL BUPA_06 1 INTERNAL BUPA_07 - At step 120 (
FIG. 1 ), the time series with rating data may be transformed into a new list where rating at t0 and rating at t1 may be given in one row of the table to obtain a base matrix before aggregation. The transformation may be done by, for example, the following operations: -
- RT0: a rating of the time series (formerly field RAT) which was most recently assigned before t0 may be copied to the field RT0;
- RT 1: a rating of the time series (formerly field RAT) which was most recently assigned before t1 may be copied to the field RT1;
- UTO: a utilization of the time series (formerly field UTIL) which was previously assigned to the rating which is now in field RTO;
- UT1: a utilization of the time series (formerly field UTIL) which was previously assigned to the rating which is now in field RT1;
- FX: the utilizations may be converted to the evaluation currency with the evaluation times t0 and t1 (different market data and interest rates); differences in the utilizations of t0 and t1 that may be caused by foreign exchange may be stored in the new field FX; and
- CURR: evaluation currency.
- In one embodiment consistent with the invention, step 120 may be performed by the software using efficient parallel processing algorithms.
- The results of
step 120 may be a matrix, such as the matrix illustrated in Table 3 below. The granularity level of Table 3 may include the fields SID, RM, and BUPA. In this example, all values for FX may be 0 because the initial currency and the evaluation currency are identical.TABLE 3 SID RM BUPA RT0 RT1 UT0 UT1 FX CURR IO 1 INTERNAL BUPA_01 A A 100.000,00 80.000,00 0 USD 1 INTERNAL BUPA_02 B C 100.000,00 50.000,00 0 USD 1 INTERNAL BUPA_03 A 50.000,00 0 USD 2 1 INTERNAL BUPA_04 C C 200.000,00 150.000,00 0 USD 1 INTERNAL BUPA_05 D 100.000,00 0 USD 1 1 INTERNAL BUPA_06 B A 150.000,00 200.000,00 0 USD 1 INTERNAL BUPA_07 B B 50.000,00 30.000,00 0 USD - The matrix obtained in
step 120 may be aggregated to a basic matrix after aggregation (FIG. 1 , step 130). While the matrices previously used instep 110 and step 120 (such as “time series with rating data” and “basic matrix before aggregation”) may be used only once in the process, the “basic matrix after aggregation” may be the starting point for several additional matrices and may be re-used several times. - To aggregate the base matrix of
step 120, the business partners (belonging to the same SID and RM) having the same ratings RT0 and RT1 may be counted, and the fields UT0 and UT1 may be summed for the business partners having the same ratings RT0 and RT1. - The present working example is very simple. Therefore, the resulting Table 4 (illustrated below) is very similar to Table 3. However, if more business partners are used that have the same rating combinations, a significant data reduction may be achieved. There may be thousands of rating combinations with RT0=B and RT1=B, although these thousands of data may be reduced to one record as illustrated in Table 4. To include the numbers of the business partners being aggregated, a new field CNT may be created including the number of ratings for the given granularity. The granularity level of Table 4 includes the fields SID, RM, RT0, RT1, and IO.
TABLE 4 SID RM RT0 RT1 IO CNT UT0 UT1 FX CURR 1 INTERNAL A A 1 100.000,00 80.000,00 0 USD 1 INTERNAL B A 1 150.000,00 200.000,00 0 USD 1 INTERNAL B B 1 50.000,00 30.000,00 0 USD 1 INTERNAL B C 1 100.000,00 50.000,00 0 USD 1 INTERNAL C C 1 200.000,00 150.000,00 0 USD 1 INTERNAL D 1 1 100.000,00 0 USD 1 INTERNAL A 2 1 50.000,00 0 USD - In this example, the number of ratings is 1 for each granularity, that is, for each combination of the values SID, RM, RT0, RT1, and IO. The values in the columns CNT, UT0, and UT1 may be sums. The sequence “time series with rating data”=>“basic matrix before aggregation”=>“basic matrix after aggregation” may be performed using efficient parallel processing algorithms.
- To calculate result matrices (
FIG. 1, 140 a-d), the “basic matrix after aggregation” may be re-used repeatedly. - T0-
portfolio matrix 140 a may require key information, such as the structure of the portfolio at the beginning of the period. The structure may be defined by rating categories. The key measure may be the “key date utilization” (e.g., a monetary amount of loans UT0 and UT1). - The portfolio matrix may be calculated by summing the fields UT0, UT1, CNT, and FX for the different ratings at T0 (RT0). In one embodiment consistent with the invention, a filter (RT0=“not empty”) may be applied. The base matrix after aggregation obtained in step 130 (Table 4) may thus be modified to create Table 5, as illustrated below. The granularity level of Table 5 may include the fields SID, RM, and RT0. Granularities RT1 and IO may be eliminated.
TABLE 5 SID RM DESCRIPTION RT0 RT1 CNT UT0 UT1 FX CURR 1 INTERNAL 01 Portfolio zu t0 A 2 80.000,00 150.000,00 0 USD 1 INTERNAL 01 Portfolio zu t0 B 3 280.000,00 300.000,00 0 USD 1 INTERNAL 01 Portfolio zu t0 C 1 150.000,00 200.000,00 0 USD - T1-
portfolio matrix 140 b may require transparent information on the portfolio structure at the end of the period under consideration based on consistent dimensions and measures. Theportfolio matrix 140 b may be calculated by, for example, summing the fields UT0, UT1, CNT, and FX for the different ratings at T1 (RT1). In one embodiment consistent with the invention, a filter (RT1=“not empty”) may be applied. Based on Table 4 as mentioned above (base matrix after aggregation,FIG. 1 , step 130), Table 6 may be created, which may represent T1-portfolio matrix 140 b. The granularity level of Table 6 may include the fields SID, RM, and RT1. Granularities RT0 and IO may be eliminated.TABLE 6 SID RM DESCRIPTION RT0 RT1 CNT UT0 UT1 FX CURR 1 INTERNAL 01 Portfolio zu t0 A 2 250.000,00 280.000,00 0 USD 1 INTERNAL 01 Portfolio zu t0 B 1 50.000,00 30.000,00 0 USD 1 INTERNAL 01 Portfolio zu t0 C 2 300.000,00 200.000,00 0 USD 1 INTERNAL 01 Portfolio zu t0 D 1 0 100.000,00 0 USD -
Migration matrix 140 c (FIG. 1 ) may include information about a change of ratings.Migration matrix 140 c may determine in which rating categories the customers show up at the end of a period given a specific rating at the beginning of the period. The key figures CNT and UT0 (UT1) may be used to calculate rating transitions (e.g., weighted or unweighted frequencies or probabilities). - The migration matrix may be calculated by summing up the fields UT0, UT1, CNT, and FX for the different rating transitions RT0→RT1 on the specified granularity. In one embodiment consistent with the invention, a filter (RT0=“not empty” and RT1=“not empty”) may be applied. Based on Table 4 (base matrix after aggregation,
FIG. 1 , step 130), Table 7 may be created. The granularity level of Table 7 may include the fields SID, RM, RT0, and RT1.TABLE 7 SID RM DESCRIPTION RT0 RT1 CNT UT0 UT1 FX CURR 1 INTERNAL 11 Migrationsmatrix A A 1 100.000,00 80.000,00 0 USD 1 INTERNAL 11 Migrationsmatrix B A 1 150.000,00 200.000,00 0 USD 1 INTERNAL 11 Migrationsmatrix B B 1 50.000,00 30.000,00 0 USD 1 INTERNAL 11 Migrationsmatrix B C 1 100.000,00 50.000,00 0 USD 1 INTERNAL 11 Migrationsmatrix C C 1 200.000,00 150.000,00 0 USD - The acquisition and
migration matrix 140 b may be assembled by the single matrices described before. Furthermore, the acquisition andmigration matrix 140 b can contain additional data based on the base matrix as mentioned above, for example, data of inflows and outflows of customers, customer acquisitions, changes in volume, acquisition performance, and the portfolio after migrations. - The data of inflows and outflows of customers may be calculated by applying an appropriate filter based on the base matrix. The customer acquisition may arise from the total of customer wins and customer losses. The calculation of the portfolio after migration to t1 may also be based on the already determined data, the portfolio at t0, as well as the migration matrix. An exemplary calculation step is:
volume of the portfolio after migration to t1=portfolio at t0+inflows and outflows for each rating class with volumes of t1+outflows for each rating class with volumes of t1. - The changed volume may be calculated as volume of the portfolio at t1 minus volume of the portfolio after migration to t1 minus customer acquisition. The acquisition performance may be calculated as the total of customer acquisition and changed volume.
- In the present working example, Table 8 may be achieved for the acquisition and
migration matrix 140 d.TABLE 8 SID RM KEY DESCRIPTION RTNG RT0 RT1 CNT UTLZ UT0 UT1 FX CURR 1 INTERNAL 1 01 portfolio at t0 A 2 150000 80000 0 USD 1 INTERNAL 1 01 portfolio at t0 B 3 300000 280000 0 USD 1 INTERNAL 1 01 portfolio at t0 C 1 200000 150000 0 USD 1 INTERNAL 2 02 portfolio at t1 A 2 250000 280000 0 USD 1 INTERNAL 2 02 portfolio at t1 B 1 50000 30000 0 USD 1 INTERNAL 2 02 portfolio at t1 C 2 300000 200000 0 USD 1 INTERNAL 2 02 portfolio at t1 D 1 0 100000 0 USD 1 INTERNAL 3 03 in-migrations B A 1 150000 200000 0 USD from . . . to . . . 1 INTERNAL 3 03 in-migrations B C 1 100000 50000 0 USD from . . . to . . . 1 INTERNAL 4 04 out-migrations A B 1 150.000− 200.000− 0 USD to . . . from . . . 1 INTERNAL 4 04 out-migrations C B 1 100.000− 50.000− 0 USD to . . . from . . . 1 INTERNAL 5 05 customers lost A 1 50.000− 0 USD (after t0) 1 INTERNAL 6 06 customers won D 1 100000 0 USD (at t1) 1 INTERNAL 7 07 customer A 1 50.000− 0 USD acquisitions 1 INTERNAL 7 07 customer D 1 100000 0 USD acquisitions 1 INTERNAL 8 08 changed volume A 20.000− 0 USD 1 INTERNAL 8 08 changed volume B 20.000− 0 USD 1 INTERNAL 8 08 changed volume C 50.000− 0 USD 1 INTERNAL 8 08 changed volume D 100.000− 0 USD 1 INTERNAL 9 09 acquisition A 70.000− 0 USD performance 1 INTERNAL 9 09 acquisition B 20.000− 0 USD performance 1 INTERNAL 9 09 acquisition C 50.000− 0 USD performance 1 INTERNAL 9 09 acquisition D 100000 0 USD performance 1 INTERNAL 10 10 portfolio A 3 350000 0 USD after migrations at t1 1 INTERNAL 10 10 portfolio B 1 50000 0 USD after migrations at t1 1 INTERNAL 10 10 portfolio C 2 250000 0 USD after migrations at t1 - Bringing all the different aspects together, the actions and events which lead to the changed risk profile within the period under consideration has been described. Based on this information, risk management may be provided with better information to adequately adjust the customer acquisition strategy, focus on customer retention, and react on unfavorable rating migration effects.
- As all these actions may be taken by different parties within the financial institutions, the consistent information basis provided above may ensure that consistent actions can be initiated.
- Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of embodiments and features of the invention disclosed herein. It is intended, therefore, that the specification and embodiments be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/345,216 US8311918B2 (en) | 2005-06-08 | 2012-01-06 | Systems and methods for calculating specified matrices |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05012313.2 | 2005-06-08 | ||
EP05012313 | 2005-06-08 | ||
EP20050012313 EP1732014A1 (en) | 2005-06-08 | 2005-06-08 | Calculation of specifed matrices |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/345,216 Division US8311918B2 (en) | 2005-06-08 | 2012-01-06 | Systems and methods for calculating specified matrices |
Publications (2)
Publication Number | Publication Date |
---|---|
US20060280302A1 true US20060280302A1 (en) | 2006-12-14 |
US8095442B2 US8095442B2 (en) | 2012-01-10 |
Family
ID=35985453
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/191,985 Active 2029-11-16 US8200557B2 (en) | 2005-06-08 | 2005-07-29 | Systems and methods for providing migration and performance matrices |
US11/443,096 Active 2030-08-28 US8095442B2 (en) | 2005-06-08 | 2006-05-31 | Systems and methods for calculating specified matrices |
US13/345,216 Expired - Fee Related US8311918B2 (en) | 2005-06-08 | 2012-01-06 | Systems and methods for calculating specified matrices |
US13/475,410 Active US8498917B2 (en) | 2005-06-08 | 2012-05-18 | Systems and methods for providing migration and performance matrices |
US13/928,417 Abandoned US20130290168A1 (en) | 2005-06-08 | 2013-06-27 | Systems and methods for providing migration and performance matrices |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/191,985 Active 2029-11-16 US8200557B2 (en) | 2005-06-08 | 2005-07-29 | Systems and methods for providing migration and performance matrices |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/345,216 Expired - Fee Related US8311918B2 (en) | 2005-06-08 | 2012-01-06 | Systems and methods for calculating specified matrices |
US13/475,410 Active US8498917B2 (en) | 2005-06-08 | 2012-05-18 | Systems and methods for providing migration and performance matrices |
US13/928,417 Abandoned US20130290168A1 (en) | 2005-06-08 | 2013-06-27 | Systems and methods for providing migration and performance matrices |
Country Status (2)
Country | Link |
---|---|
US (5) | US8200557B2 (en) |
EP (1) | EP1732014A1 (en) |
Cited By (63)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060282360A1 (en) * | 2005-06-08 | 2006-12-14 | Kahn Markus H | Systems and methods for providing migration and performance matrices |
US8364608B2 (en) | 2010-06-15 | 2013-01-29 | Sap Ag | Managing consistent interfaces for export declaration and export declaration request business objects across heterogeneous systems |
US8364715B2 (en) | 2008-03-31 | 2013-01-29 | Sap Ag | Managing consistent interfaces for automatic identification label business objects across heterogeneous systems |
US8370233B2 (en) | 2008-03-31 | 2013-02-05 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8370272B2 (en) | 2010-06-15 | 2013-02-05 | Sap Ag | Managing consistent interfaces for business document message monitoring view, customs arrangement, and freight list business objects across heterogeneous systems |
US8374931B2 (en) | 2006-03-31 | 2013-02-12 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8392364B2 (en) | 2006-07-10 | 2013-03-05 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8396768B1 (en) | 2006-09-28 | 2013-03-12 | Sap Ag | Managing consistent interfaces for human resources business objects across heterogeneous systems |
US8396751B2 (en) | 2009-09-30 | 2013-03-12 | Sap Ag | Managing consistent interfaces for merchandising business objects across heterogeneous systems |
US8413165B2 (en) | 2008-03-31 | 2013-04-02 | Sap Ag | Managing consistent interfaces for maintenance order business objects across heterogeneous systems |
US8412603B2 (en) | 2010-06-15 | 2013-04-02 | Sap Ag | Managing consistent interfaces for currency conversion and date and time business objects across heterogeneous systems |
US8417588B2 (en) | 2010-06-15 | 2013-04-09 | Sap Ag | Managing consistent interfaces for goods tag, production bill of material hierarchy, and release order template business objects across heterogeneous systems |
US8417593B2 (en) | 2008-02-28 | 2013-04-09 | Sap Ag | System and computer-readable medium for managing consistent interfaces for business objects across heterogeneous systems |
US8423418B2 (en) | 2008-03-31 | 2013-04-16 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8433585B2 (en) | 2008-03-31 | 2013-04-30 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8463666B2 (en) | 2008-11-25 | 2013-06-11 | Sap Ag | Managing consistent interfaces for merchandise and assortment planning business objects across heterogeneous systems |
US8473317B2 (en) | 2008-03-31 | 2013-06-25 | Sap Ag | Managing consistent interfaces for service part business objects across heterogeneous systems |
US8515794B2 (en) | 2010-06-15 | 2013-08-20 | Sap Ag | Managing consistent interfaces for employee time event and human capital management view of payroll process business objects across heterogeneous systems |
US8521838B2 (en) | 2011-07-28 | 2013-08-27 | Sap Ag | Managing consistent interfaces for communication system and object identifier mapping business objects across heterogeneous systems |
US8521621B1 (en) | 2012-06-28 | 2013-08-27 | Sap Ag | Consistent interface for inbound delivery request |
US8554586B2 (en) | 2008-06-26 | 2013-10-08 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8560392B2 (en) | 2011-07-28 | 2013-10-15 | Sap Ag | Managing consistent interfaces for a point of sale transaction business object across heterogeneous systems |
US8566185B2 (en) | 2008-06-26 | 2013-10-22 | Sap Ag | Managing consistent interfaces for financial instrument business objects across heterogeneous systems |
US8566193B2 (en) | 2006-08-11 | 2013-10-22 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8577760B2 (en) | 2008-11-25 | 2013-11-05 | Sap Ag | Managing consistent interfaces for tax authority business objects across heterogeneous systems |
US8577991B2 (en) | 2008-03-31 | 2013-11-05 | Sap Ag | Managing consistent interfaces for internal service request business objects across heterogeneous systems |
US8589263B2 (en) | 2008-03-31 | 2013-11-19 | Sap Ag | Managing consistent interfaces for retail business objects across heterogeneous systems |
US8601490B2 (en) | 2011-07-28 | 2013-12-03 | Sap Ag | Managing consistent interfaces for business rule business object across heterogeneous systems |
US8606723B2 (en) | 2004-06-04 | 2013-12-10 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8615451B1 (en) | 2012-06-28 | 2013-12-24 | Sap Ag | Consistent interface for goods and activity confirmation |
US8645228B2 (en) | 2008-06-26 | 2014-02-04 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8655756B2 (en) | 2004-06-04 | 2014-02-18 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8666845B2 (en) | 2011-07-28 | 2014-03-04 | Sap Ag | Managing consistent interfaces for a customer requirement business object across heterogeneous systems |
US8671041B2 (en) | 2008-12-12 | 2014-03-11 | Sap Ag | Managing consistent interfaces for credit portfolio business objects across heterogeneous systems |
US8671064B2 (en) | 2008-06-26 | 2014-03-11 | Sap Ag | Managing consistent interfaces for supply chain management business objects across heterogeneous systems |
US8694397B2 (en) | 2004-06-18 | 2014-04-08 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8725654B2 (en) | 2011-07-28 | 2014-05-13 | Sap Ag | Managing consistent interfaces for employee data replication business objects across heterogeneous systems |
US8732083B2 (en) | 2010-06-15 | 2014-05-20 | Sap Ag | Managing consistent interfaces for number range, number range profile, payment card payment authorisation, and product template template business objects across heterogeneous systems |
US8744937B2 (en) | 2005-02-25 | 2014-06-03 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8756274B2 (en) | 2012-02-16 | 2014-06-17 | Sap Ag | Consistent interface for sales territory message type set 1 |
US8756135B2 (en) | 2012-06-28 | 2014-06-17 | Sap Ag | Consistent interface for product valuation data and product valuation level |
US8762454B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for flag and tag |
US8762453B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for feed collaboration group and feed event subscription |
US8775280B2 (en) | 2011-07-28 | 2014-07-08 | Sap Ag | Managing consistent interfaces for financial business objects across heterogeneous systems |
US20140330751A1 (en) * | 2013-05-04 | 2014-11-06 | Ferdinand Mager | Method and system to capture credit risks in a portfolio context |
US8924269B2 (en) | 2006-05-13 | 2014-12-30 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8930248B2 (en) | 2008-03-31 | 2015-01-06 | Sap Se | Managing consistent interfaces for supply network business objects across heterogeneous systems |
US8949855B2 (en) | 2012-06-28 | 2015-02-03 | Sap Se | Consistent interface for address snapshot and approval process definition |
US8984050B2 (en) | 2012-02-16 | 2015-03-17 | Sap Se | Consistent interface for sales territory message type set 2 |
US9043236B2 (en) | 2012-08-22 | 2015-05-26 | Sap Se | Consistent interface for financial instrument impairment attribute values analytical result |
US9076112B2 (en) | 2012-08-22 | 2015-07-07 | Sap Se | Consistent interface for financial instrument impairment expected cash flow analytical result |
US9135585B2 (en) | 2010-06-15 | 2015-09-15 | Sap Se | Managing consistent interfaces for property library, property list template, quantity conversion virtual object, and supplier property specification business objects across heterogeneous systems |
US9191357B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for email activity business object |
US9191343B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for appointment activity business object |
US9232368B2 (en) | 2012-02-16 | 2016-01-05 | Sap Se | Consistent interface for user feed administrator, user feed event link and user feed settings |
US9237425B2 (en) | 2012-02-16 | 2016-01-12 | Sap Se | Consistent interface for feed event, feed event document and feed event type |
US9246869B2 (en) | 2012-06-28 | 2016-01-26 | Sap Se | Consistent interface for opportunity |
US9261950B2 (en) | 2012-06-28 | 2016-02-16 | Sap Se | Consistent interface for document output request |
US9367826B2 (en) | 2012-06-28 | 2016-06-14 | Sap Se | Consistent interface for entitlement product |
US9400998B2 (en) | 2012-06-28 | 2016-07-26 | Sap Se | Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule |
US9547833B2 (en) | 2012-08-22 | 2017-01-17 | Sap Se | Consistent interface for financial instrument impairment calculation |
US11036471B2 (en) | 2018-06-06 | 2021-06-15 | Sap Se | Data grouping for efficient parallel processing |
US12271365B2 (en) | 2017-03-17 | 2025-04-08 | Sap Se | Table schema providing improved database system performance |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7739203B2 (en) | 2004-03-08 | 2010-06-15 | Sap Aktiengesellschaft | Method and system for classifying retail products and services using price band categories |
US8788372B2 (en) * | 2004-03-08 | 2014-07-22 | Sap Aktiengesellschaft | Method and system for classifying retail products and services using characteristic-based grouping structures |
US8655697B2 (en) | 2004-04-16 | 2014-02-18 | Sap Aktiengesellschaft | Allocation table generation from assortment planning |
US7617501B2 (en) | 2004-07-09 | 2009-11-10 | Quest Software, Inc. | Apparatus, system, and method for managing policies on a computer having a foreign operating system |
US7724890B1 (en) | 2005-09-07 | 2010-05-25 | Sap Ag | Focused retrieval of selected data in a call center environment |
US7904949B2 (en) | 2005-12-19 | 2011-03-08 | Quest Software, Inc. | Apparatus, systems and methods to provide authentication services to a legacy application |
US8087075B2 (en) | 2006-02-13 | 2011-12-27 | Quest Software, Inc. | Disconnected credential validation using pre-fetched service tickets |
US7853945B2 (en) | 2006-02-22 | 2010-12-14 | Michael Kramer | Integrated computer server imaging |
US20070234345A1 (en) * | 2006-02-22 | 2007-10-04 | Microsoft Corporation | Integrated multi-server installation |
US8429712B2 (en) | 2006-06-08 | 2013-04-23 | Quest Software, Inc. | Centralized user authentication system apparatus and method |
US8086710B2 (en) * | 2006-10-30 | 2011-12-27 | Quest Software, Inc. | Identity migration apparatus and method |
US7895332B2 (en) | 2006-10-30 | 2011-02-22 | Quest Software, Inc. | Identity migration system apparatus and method |
US8099337B2 (en) * | 2007-06-19 | 2012-01-17 | Sap Ag | Replenishment planning management |
US8452681B2 (en) * | 2009-02-13 | 2013-05-28 | Thomson Financial, LLC | System and method for improved rating and modeling of asset backed securities |
US8255984B1 (en) | 2009-07-01 | 2012-08-28 | Quest Software, Inc. | Single sign-on system for shared resource environments |
CN101604437A (en) * | 2009-07-22 | 2009-12-16 | 阿里巴巴集团控股有限公司 | Account is real time processing system and account batch real-time processing method in batches |
US20130304671A1 (en) * | 2012-05-11 | 2013-11-14 | Axioma, Inc. | Factor Risk Models with Multiple Specific Risk Estimates |
US10467207B2 (en) | 2013-05-24 | 2019-11-05 | Sap Se | Handling changes in automatic sort |
US9311124B2 (en) | 2013-11-07 | 2016-04-12 | Sap Se | Integrated deployment of centrally modified software systems |
US12135824B2 (en) * | 2022-04-01 | 2024-11-05 | Hong Kong Applied Science And Technology Research Institute Co., Ltd. | System and methods for auditable data management |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030088492A1 (en) * | 2001-08-16 | 2003-05-08 | Damschroder James Eric | Method and apparatus for creating and managing a visual representation of a portfolio and determining an efficient allocation |
US20030144945A1 (en) * | 2002-01-31 | 2003-07-31 | Opsahl-Ong Lorinda R. | Systems and methods to automatically generate a return target for a potential real estate deal based on supplemental deal information |
US20050071266A1 (en) * | 2001-02-05 | 2005-03-31 | Eder Jeff Scott | Value and risk management system |
US20060015425A1 (en) * | 2004-07-15 | 2006-01-19 | Brooks Kent F | System and method for providing customizable investment tools |
US20060069635A1 (en) * | 2002-09-12 | 2006-03-30 | Pranil Ram | Method of buying or selling items and a user interface to facilitate the same |
US20060229963A1 (en) * | 2005-04-11 | 2006-10-12 | Jennifer Creager | Portfolio performance tracking |
US7383219B1 (en) * | 2000-07-13 | 2008-06-03 | C4Cast.Com, Inc. | Asset portfolio tracking |
US7469227B2 (en) * | 2000-02-22 | 2008-12-23 | Strategic Analytics, Inc. | Retail lending risk related scenario generation |
US20090018891A1 (en) * | 2003-12-30 | 2009-01-15 | Jeff Scott Eder | Market value matrix |
US7530490B1 (en) * | 2003-11-12 | 2009-05-12 | Goldman Sachs & Co | Systems and methods to perform credit valuation adjustment analyses |
US7720729B2 (en) * | 2001-07-27 | 2010-05-18 | Golman Sachs & Co. | Systems and methods for facilitating agreement generation and negotiation via an agreement modeling system |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5884287A (en) * | 1996-04-12 | 1999-03-16 | Lfg, Inc. | System and method for generating and displaying risk and return in an investment portfolio |
US5893069A (en) * | 1997-01-31 | 1999-04-06 | Quantmetrics R&D Associates, Llc | System and method for testing prediction model |
US6078904A (en) * | 1998-03-16 | 2000-06-20 | Saddle Peak Systems | Risk direct asset allocation and risk resolved CAPM for optimally allocating investment assets in an investment portfolio |
US7539637B2 (en) * | 1998-04-24 | 2009-05-26 | Starmine Corporation | Security analyst estimates performance viewing system and method |
US7707091B1 (en) * | 1998-12-22 | 2010-04-27 | Nutech Solutions, Inc. | System and method for the analysis and prediction of economic markets |
US6484152B1 (en) * | 1999-12-29 | 2002-11-19 | Optimumportfolio.Com, Llc | Automated portfolio selection system |
US7139723B2 (en) * | 2000-01-13 | 2006-11-21 | Erinmedia, Llc | Privacy compliant multiple dataset correlation system |
US7571130B2 (en) * | 2002-06-17 | 2009-08-04 | Nyse Alternext Us Llc | Hedging exchange traded mutual funds or other portfolio basket products |
US20050262013A1 (en) * | 2001-10-16 | 2005-11-24 | Guthner Mark W | System and method for analyzing risk and profitability of non-recourse loans |
CA2367091A1 (en) * | 2002-01-10 | 2003-07-10 | Algorithmics International Corp. | System and methods for valuing and managing the risk of credit instrument portfolios |
US20050027645A1 (en) * | 2002-01-31 | 2005-02-03 | Wai Shing Lui William | Business enterprise risk model and method |
US7587352B2 (en) * | 2002-04-10 | 2009-09-08 | Research Affiliates, Llc | Method and apparatus for managing a virtual portfolio of investment objects |
US7702556B2 (en) * | 2002-08-14 | 2010-04-20 | Water Street Advisers, Inc. | Process for the selection and evaluation of investment portfolio asset allocation strategies |
US20040059589A1 (en) * | 2002-09-19 | 2004-03-25 | Moore Richard N. | Method of managing risk |
US7366653B2 (en) * | 2003-12-22 | 2008-04-29 | Siebel Systems, Inc. | Methods and apparatuses for string translation |
US20060173772A1 (en) * | 2005-02-02 | 2006-08-03 | Hayes John B | Systems and methods for automated processing, handling, and facilitating a trade credit transaction |
EP1732014A1 (en) * | 2005-06-08 | 2006-12-13 | Sap Ag | Calculation of specifed matrices |
US20080065522A1 (en) * | 2005-09-28 | 2008-03-13 | Keith Bayley Diffenderffer | Low volatility asset allocation strategy for income and method |
US7761354B2 (en) * | 2006-06-13 | 2010-07-20 | Sap Ag | Banking software design generator |
-
2005
- 2005-06-08 EP EP20050012313 patent/EP1732014A1/en not_active Ceased
- 2005-07-29 US US11/191,985 patent/US8200557B2/en active Active
-
2006
- 2006-05-31 US US11/443,096 patent/US8095442B2/en active Active
-
2012
- 2012-01-06 US US13/345,216 patent/US8311918B2/en not_active Expired - Fee Related
- 2012-05-18 US US13/475,410 patent/US8498917B2/en active Active
-
2013
- 2013-06-27 US US13/928,417 patent/US20130290168A1/en not_active Abandoned
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7469227B2 (en) * | 2000-02-22 | 2008-12-23 | Strategic Analytics, Inc. | Retail lending risk related scenario generation |
US7383219B1 (en) * | 2000-07-13 | 2008-06-03 | C4Cast.Com, Inc. | Asset portfolio tracking |
US20050071266A1 (en) * | 2001-02-05 | 2005-03-31 | Eder Jeff Scott | Value and risk management system |
US7720729B2 (en) * | 2001-07-27 | 2010-05-18 | Golman Sachs & Co. | Systems and methods for facilitating agreement generation and negotiation via an agreement modeling system |
US20030088492A1 (en) * | 2001-08-16 | 2003-05-08 | Damschroder James Eric | Method and apparatus for creating and managing a visual representation of a portfolio and determining an efficient allocation |
US20030144945A1 (en) * | 2002-01-31 | 2003-07-31 | Opsahl-Ong Lorinda R. | Systems and methods to automatically generate a return target for a potential real estate deal based on supplemental deal information |
US20060069635A1 (en) * | 2002-09-12 | 2006-03-30 | Pranil Ram | Method of buying or selling items and a user interface to facilitate the same |
US7530490B1 (en) * | 2003-11-12 | 2009-05-12 | Goldman Sachs & Co | Systems and methods to perform credit valuation adjustment analyses |
US20090018891A1 (en) * | 2003-12-30 | 2009-01-15 | Jeff Scott Eder | Market value matrix |
US20060015425A1 (en) * | 2004-07-15 | 2006-01-19 | Brooks Kent F | System and method for providing customizable investment tools |
US20060229963A1 (en) * | 2005-04-11 | 2006-10-12 | Jennifer Creager | Portfolio performance tracking |
Cited By (74)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8655756B2 (en) | 2004-06-04 | 2014-02-18 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8606723B2 (en) | 2004-06-04 | 2013-12-10 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8694397B2 (en) | 2004-06-18 | 2014-04-08 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8744937B2 (en) | 2005-02-25 | 2014-06-03 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8095442B2 (en) | 2005-06-08 | 2012-01-10 | Sap Ag | Systems and methods for calculating specified matrices |
US8200557B2 (en) | 2005-06-08 | 2012-06-12 | Sap Ag | Systems and methods for providing migration and performance matrices |
US8311918B2 (en) | 2005-06-08 | 2012-11-13 | Sap Ag | Systems and methods for calculating specified matrices |
US8498917B2 (en) | 2005-06-08 | 2013-07-30 | Sap Ag | Systems and methods for providing migration and performance matrices |
US20060282360A1 (en) * | 2005-06-08 | 2006-12-14 | Kahn Markus H | Systems and methods for providing migration and performance matrices |
US8374931B2 (en) | 2006-03-31 | 2013-02-12 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8924269B2 (en) | 2006-05-13 | 2014-12-30 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8392364B2 (en) | 2006-07-10 | 2013-03-05 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8566193B2 (en) | 2006-08-11 | 2013-10-22 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8396768B1 (en) | 2006-09-28 | 2013-03-12 | Sap Ag | Managing consistent interfaces for human resources business objects across heterogeneous systems |
US8402473B1 (en) | 2006-09-28 | 2013-03-19 | Sap Ag | Managing consistent interfaces for demand business objects across heterogeneous systems |
US8606639B1 (en) | 2006-09-28 | 2013-12-10 | Sap Ag | Managing consistent interfaces for purchase order business objects across heterogeneous systems |
US8571961B1 (en) | 2006-09-28 | 2013-10-29 | Sap Ag | Managing consistent interfaces for financial business objects across heterogeneous systems |
US8468544B1 (en) | 2006-09-28 | 2013-06-18 | Sap Ag | Managing consistent interfaces for demand planning business objects across heterogeneous systems |
US8799115B2 (en) | 2008-02-28 | 2014-08-05 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8417593B2 (en) | 2008-02-28 | 2013-04-09 | Sap Ag | System and computer-readable medium for managing consistent interfaces for business objects across heterogeneous systems |
US8589263B2 (en) | 2008-03-31 | 2013-11-19 | Sap Ag | Managing consistent interfaces for retail business objects across heterogeneous systems |
US8433585B2 (en) | 2008-03-31 | 2013-04-30 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8423418B2 (en) | 2008-03-31 | 2013-04-16 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8413165B2 (en) | 2008-03-31 | 2013-04-02 | Sap Ag | Managing consistent interfaces for maintenance order business objects across heterogeneous systems |
US8930248B2 (en) | 2008-03-31 | 2015-01-06 | Sap Se | Managing consistent interfaces for supply network business objects across heterogeneous systems |
US8364715B2 (en) | 2008-03-31 | 2013-01-29 | Sap Ag | Managing consistent interfaces for automatic identification label business objects across heterogeneous systems |
US8577991B2 (en) | 2008-03-31 | 2013-11-05 | Sap Ag | Managing consistent interfaces for internal service request business objects across heterogeneous systems |
US8370233B2 (en) | 2008-03-31 | 2013-02-05 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8473317B2 (en) | 2008-03-31 | 2013-06-25 | Sap Ag | Managing consistent interfaces for service part business objects across heterogeneous systems |
US8554586B2 (en) | 2008-06-26 | 2013-10-08 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US9047578B2 (en) | 2008-06-26 | 2015-06-02 | Sap Se | Consistent set of interfaces for business objects across heterogeneous systems |
US8645228B2 (en) | 2008-06-26 | 2014-02-04 | Sap Ag | Managing consistent interfaces for business objects across heterogeneous systems |
US8671064B2 (en) | 2008-06-26 | 2014-03-11 | Sap Ag | Managing consistent interfaces for supply chain management business objects across heterogeneous systems |
US8566185B2 (en) | 2008-06-26 | 2013-10-22 | Sap Ag | Managing consistent interfaces for financial instrument business objects across heterogeneous systems |
US8463666B2 (en) | 2008-11-25 | 2013-06-11 | Sap Ag | Managing consistent interfaces for merchandise and assortment planning business objects across heterogeneous systems |
US8577760B2 (en) | 2008-11-25 | 2013-11-05 | Sap Ag | Managing consistent interfaces for tax authority business objects across heterogeneous systems |
US8671041B2 (en) | 2008-12-12 | 2014-03-11 | Sap Ag | Managing consistent interfaces for credit portfolio business objects across heterogeneous systems |
US8554637B2 (en) | 2009-09-30 | 2013-10-08 | Sap Ag | Managing consistent interfaces for merchandising business objects across heterogeneous systems |
US8396751B2 (en) | 2009-09-30 | 2013-03-12 | Sap Ag | Managing consistent interfaces for merchandising business objects across heterogeneous systems |
US8732083B2 (en) | 2010-06-15 | 2014-05-20 | Sap Ag | Managing consistent interfaces for number range, number range profile, payment card payment authorisation, and product template template business objects across heterogeneous systems |
US8412603B2 (en) | 2010-06-15 | 2013-04-02 | Sap Ag | Managing consistent interfaces for currency conversion and date and time business objects across heterogeneous systems |
US8370272B2 (en) | 2010-06-15 | 2013-02-05 | Sap Ag | Managing consistent interfaces for business document message monitoring view, customs arrangement, and freight list business objects across heterogeneous systems |
US8417588B2 (en) | 2010-06-15 | 2013-04-09 | Sap Ag | Managing consistent interfaces for goods tag, production bill of material hierarchy, and release order template business objects across heterogeneous systems |
US9135585B2 (en) | 2010-06-15 | 2015-09-15 | Sap Se | Managing consistent interfaces for property library, property list template, quantity conversion virtual object, and supplier property specification business objects across heterogeneous systems |
US8515794B2 (en) | 2010-06-15 | 2013-08-20 | Sap Ag | Managing consistent interfaces for employee time event and human capital management view of payroll process business objects across heterogeneous systems |
US8364608B2 (en) | 2010-06-15 | 2013-01-29 | Sap Ag | Managing consistent interfaces for export declaration and export declaration request business objects across heterogeneous systems |
US8775280B2 (en) | 2011-07-28 | 2014-07-08 | Sap Ag | Managing consistent interfaces for financial business objects across heterogeneous systems |
US8666845B2 (en) | 2011-07-28 | 2014-03-04 | Sap Ag | Managing consistent interfaces for a customer requirement business object across heterogeneous systems |
US8601490B2 (en) | 2011-07-28 | 2013-12-03 | Sap Ag | Managing consistent interfaces for business rule business object across heterogeneous systems |
US8725654B2 (en) | 2011-07-28 | 2014-05-13 | Sap Ag | Managing consistent interfaces for employee data replication business objects across heterogeneous systems |
US8560392B2 (en) | 2011-07-28 | 2013-10-15 | Sap Ag | Managing consistent interfaces for a point of sale transaction business object across heterogeneous systems |
US8521838B2 (en) | 2011-07-28 | 2013-08-27 | Sap Ag | Managing consistent interfaces for communication system and object identifier mapping business objects across heterogeneous systems |
US8756274B2 (en) | 2012-02-16 | 2014-06-17 | Sap Ag | Consistent interface for sales territory message type set 1 |
US8984050B2 (en) | 2012-02-16 | 2015-03-17 | Sap Se | Consistent interface for sales territory message type set 2 |
US9237425B2 (en) | 2012-02-16 | 2016-01-12 | Sap Se | Consistent interface for feed event, feed event document and feed event type |
US8762453B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for feed collaboration group and feed event subscription |
US8762454B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for flag and tag |
US9232368B2 (en) | 2012-02-16 | 2016-01-05 | Sap Se | Consistent interface for user feed administrator, user feed event link and user feed settings |
US9261950B2 (en) | 2012-06-28 | 2016-02-16 | Sap Se | Consistent interface for document output request |
US8949855B2 (en) | 2012-06-28 | 2015-02-03 | Sap Se | Consistent interface for address snapshot and approval process definition |
US8756135B2 (en) | 2012-06-28 | 2014-06-17 | Sap Ag | Consistent interface for product valuation data and product valuation level |
US9400998B2 (en) | 2012-06-28 | 2016-07-26 | Sap Se | Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule |
US8615451B1 (en) | 2012-06-28 | 2013-12-24 | Sap Ag | Consistent interface for goods and activity confirmation |
US9367826B2 (en) | 2012-06-28 | 2016-06-14 | Sap Se | Consistent interface for entitlement product |
US8521621B1 (en) | 2012-06-28 | 2013-08-27 | Sap Ag | Consistent interface for inbound delivery request |
US9246869B2 (en) | 2012-06-28 | 2016-01-26 | Sap Se | Consistent interface for opportunity |
US9043236B2 (en) | 2012-08-22 | 2015-05-26 | Sap Se | Consistent interface for financial instrument impairment attribute values analytical result |
US9076112B2 (en) | 2012-08-22 | 2015-07-07 | Sap Se | Consistent interface for financial instrument impairment expected cash flow analytical result |
US9547833B2 (en) | 2012-08-22 | 2017-01-17 | Sap Se | Consistent interface for financial instrument impairment calculation |
US9191343B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for appointment activity business object |
US9191357B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for email activity business object |
US20140330751A1 (en) * | 2013-05-04 | 2014-11-06 | Ferdinand Mager | Method and system to capture credit risks in a portfolio context |
US12271365B2 (en) | 2017-03-17 | 2025-04-08 | Sap Se | Table schema providing improved database system performance |
US11036471B2 (en) | 2018-06-06 | 2021-06-15 | Sap Se | Data grouping for efficient parallel processing |
Also Published As
Publication number | Publication date |
---|---|
US20060282360A1 (en) | 2006-12-14 |
US20130290168A1 (en) | 2013-10-31 |
US8095442B2 (en) | 2012-01-10 |
US8200557B2 (en) | 2012-06-12 |
US20120233091A1 (en) | 2012-09-13 |
EP1732014A1 (en) | 2006-12-13 |
US20120110034A1 (en) | 2012-05-03 |
US8498917B2 (en) | 2013-07-30 |
US8311918B2 (en) | 2012-11-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8095442B2 (en) | Systems and methods for calculating specified matrices | |
US8150749B2 (en) | Systems and methods for general aggregation of characteristics and key figures | |
US6904411B2 (en) | Multi-processing financial transaction processing system | |
US8626702B2 (en) | Method and system for validation of data extraction | |
US20200334748A1 (en) | System and method for providing an aggregation tool | |
US7930230B2 (en) | Methods and systems for risk evaluation | |
US20060241923A1 (en) | Automated systems and methods for generating statistical models | |
US20020069102A1 (en) | Method and system for assessing and quantifying the business value of an information techonology (IT) application or set of applications | |
US20050010454A1 (en) | System and process for electronic subrogation, inter-organization workflow management, inter-organization transaction processing and optimized web-based user interaction | |
US20090112753A1 (en) | Application processing and decision systems and processes | |
US20030182337A1 (en) | Methods and systems for risk evaluation | |
US7627554B2 (en) | Uniform financial reporting system interface utilizing staging tables having a standardized structure | |
WO2005064491A1 (en) | Detection and correction of data quality problems | |
US20140032393A1 (en) | System and method for reporting and analyzing mortgage information | |
US20210390618A1 (en) | Financial Risk Assessment | |
US20060074710A1 (en) | Healthcare revenue cycle management system | |
CN117557395B (en) | Research and development cost management and control method, system, electronic equipment and storage medium | |
AU2003200483B2 (en) | Method and system for risk evaluation | |
CN118551898A (en) | Service data processing method, device, computer equipment and storage medium | |
CN114677223A (en) | Information acquisition method, apparatus, device, medium, and program product | |
Saeed et al. | Operational Business Intelligence–A key to Just-in-Time Decision Making (JDM) | |
CN112967129A (en) | Financial data measuring and calculating method and device, computer equipment and storage medium | |
GB2362483A (en) | Method and apparatus for calculating the magnitude of a task | |
Lin | A unified accounting information framework to modeling bank accounting systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SAP AG, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAUMANN, MARCUS;KAHN, MARKUS;REEL/FRAME:017938/0474 Effective date: 20060524 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: SAP SE, GERMANY Free format text: CHANGE OF NAME;ASSIGNOR:SAP AG;REEL/FRAME:033625/0334 Effective date: 20140707 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |