US20100153297A1

Movatterモバイル変換

Info

Publication number: US20100153297A1
Application number: US12/334,175
Authority: US
Inventors: Hermann Haaf; Markus Kahn; Oliver Klueglich; Dirk Vogel; Manfred Wanninger
Original assignee: SAP SE
Current assignee: SAP SE
Priority date: 2008-12-12
Filing date: 2008-12-12
Publication date: 2010-06-17
Also published as: US20140143178A1; US20120117000A1; US8671041B2

Abstract

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a credit portfolio model, a credit portfolio analytical result, a credit portfolio management process control, a financial instrument exposure profile analytical result, and/or a material supply and demand allocation business object.

Description

TECHNICAL FIELD

The subject matter described herein relates generally to the generation and use of consistent interfaces (or services) derived from a business object model. More particularly, the present disclosure relates to the generation and use of consistent interfaces or services that are suitable for use across industries, across businesses, and across different departments within a business.

BACKGROUND

Transactions are common among businesses and between business departments within a particular business. During any given transaction, these business entities exchange information. For example, during a sales transaction, numerous business entities may be involved, such as a sales entity that sells merchandise to a customer, a financial institution that handles the financial transaction, and a warehouse that sends the merchandise to the customer. The end-to-end business transaction may require a significant amount of information to be exchanged between the various business entities involved. For example, the customer may send a request for the merchandise as well as some form of payment authorization for the merchandise to the sales entity, and the sales entity may send the financial institution a request for a transfer of funds from the customer's account to the sales entity's account.

Exchanging information between different business entities is not a simple task. This is particularly true because the information used by different business entities is usually tightly tied to the business entity itself. Each business entity may have its own program for handling its part of the transaction. These programs differ from each other because they typically are created for different purposes and because each business entity may use semantics that differ from the other business entities. For example, one program may relate to accounting, another program may relate to manufacturing, and a third program may relate to inventory control. Similarly, one program may identify merchandise using the name of the product while another program may identify the same merchandise using its model number. Further, one business entity may use U.S. dollars to represent its currency while another business entity may use Japanese Yen. A simple difference in formatting, e.g., the use of upper-case lettering rather than lower-case or title-case, makes the exchange of information between businesses a difficult task. Unless the individual businesses agree upon particular semantics, human interaction typically is required to facilitate transactions between these businesses. Because these “heterogeneous” programs are used by different companies or by different business areas within a given company, a need exists for a consistent way to exchange information and perform a business transaction between the different business entities.

Currently, many standards exist that offer a variety of interfaces used to exchange business information. Most of these interfaces, however, apply to only one specific industry and are not consistent between the different standards. Moreover, a number of these interfaces are not consistent within an individual standard.

SUMMARY

In a first aspect, a tangible computer readable medium includes program code for providing a message-based interface for performing a credit portfolio model service. The service exposes at least one service as defined in a service registry. Upon execution, the program code executes in an environment of computer systems providing message-based services. The program code receives, from a service consumer, a first message for processing a model-based risk analysis of a credit portfolio. The program code invokes a credit portfolio model business object. The business object is a logically centralized, semantically disjointed object representing a model-based risk analysis of a credit portfolio. The business object includes data logically organized as a credit portfolio model root node, and an input data subordinate node. The input data node contains a stock subordinate node, a credit spread matrix subordinate node, a bond subordinate node, a probability of default calibration matrix subordinate node, a rating transition matrix subordinate node, a traditional off balance sheet item subordinate node, an OTC derivative subordinate node, a securities financing transaction subordinate node, a loan subordinate node, a credit derivative subordinate node, a business partner subordinate node, an exchange rate subordinate node, a yield curve subordinate node, a credit portfolio analysis data subordinate node, and a securitization subordinate node. The credit portfolio analysis data node contains a credit portfolio assignment subordinate node. The credit portfolio node contains a financial instrument exposure subordinate node. The program code initiates transmission of a message to a heterogeneous second application, executing in the environment of computer systems providing message-based services. The message is based on the data in the credit portfolio model business object. The message includes a credit portfolio model entity and a credit portfolio model package.

In a second aspect, a tangible computer readable medium includes program code for providing a message-based interface for performing a credit portfolio model service. The service exposes at least one service as defined in a service registry. Upon execution, the program code executes in an environment of computer systems providing message-based services. The program code initiates transmission of a message to a heterogeneous second application, executing in the environment of computer systems providing message-based services. The message is based on data in a credit portfolio model business object invoked by the second application. The business object is a logically centralized, semantically disjointed object representing a model-based risk analysis of a credit portfolio. The business object includes data logically organized as a credit portfolio model root node, and an input data subordinate node. The input data node contains a stock subordinate node, a credit spread matrix subordinate node, a bond subordinate node, a probability of default calibration matrix subordinate node, a rating transition matrix subordinate node, a traditional off balance sheet item subordinate node, an OTC derivative subordinate node, a securities financing transaction subordinate node, a loan subordinate node, a credit derivative subordinate node, a business partner subordinate node, an exchange rate subordinate node, a yield curve subordinate node, a credit portfolio analysis data subordinate node, and a securitization subordinate node. The credit portfolio analysis data node contains a credit portfolio assignment subordinate node. The credit portfolio node contains a financial instrument exposure subordinate node. The message includes a credit portfolio model entity and a credit portfolio model package. The program code receives a second message from the second application. The second message is associated with the invoked credit portfolio model business object and is in response to the first message.

In a fourth aspect, a tangible computer readable medium includes program code for providing a message-based interface for performing a credit portfolio analytical result service. The service exposes at least one service as defined in a service registry. Upon execution, the program code executes in an environment of computer systems providing message-based services. The program code receives, from a service consumer, a first message for processing an analytical result for a credit portfolio. The program code invokes a credit portfolio analytical result business object. The business object is a logically centralized, semantically disjointed object representing an analytical result for a credit portfolio. The business object includes data logically organized as a credit portfolio analytical result root node and an item subordinate node. The item node contains a property subordinate node. The program code initiates transmission of a message to a heterogeneous second application, executing in the environment of computer systems providing message-based services. The message is based on the data in the credit portfolio analytical result business object. The message includes a credit portfolio analytical result entity and a credit portfolio analytical result package.

In a fifth aspect, a tangible computer readable medium includes program code for providing a message-based interface for performing a credit portfolio analytical result service. The service exposes at least one service as defined in a service registry. Upon execution, the program code executes in an environment of computer systems providing message-based services. The program code initiates transmission of a message to a heterogeneous second application, executing in the environment of computer systems providing message-based services. The message is based on data in a credit portfolio analytical result business object invoked by the second application. The business object is a logically centralized, semantically disjointed object representing an analytical result for a credit portfolio. The business object includes data logically organized as a credit portfolio analytical result root node and an item subordinate node. The item node contains a property subordinate node. The message includes a credit portfolio analytical result entity and a credit portfolio analytical result package. The program code receives a second message from the second application. The second message is associated with the invoked credit portfolio analytical result business object and is in response to the first message.

In a sixth aspect, a distributed system operates in a landscape of computer systems providing message-based services. The system processes business objects involving processing an analytical result for a credit portfolio. The system includes memory and a graphical user interface remote from the memory. The memory stores a business object repository storing a plurality of business objects. Each business object is a logically centralized, semantically disjointed object of a particular business object type. At least one of the business objects represents an analytical result for a credit portfolio. The business object includes data logically organized as a credit portfolio analytical result root node and an item subordinate node. The item node contains a property subordinate node. The graphical user interface presents data associated with an invoked instance of the credit portfolio analytical result business object. The user interface includes tangible computer readable instructions embodied on tangible media.

In a ninth aspect, a distributed system operates in a landscape of computer systems providing message-based services. The system processes business objects involving processing the selection of data relevant for credit portfolio management, and the transformation of these data into the credit portfolio management specific view format. The system includes memory and a graphical user interface remote from the memory. The memory stores a business object repository storing a plurality of business objects. Each business object is a logically centralized, semantically disjointed object of a particular business object type. At least one of the business objects represents the selection of data relevant for credit portfolio management, and the transformation of these data into the credit portfolio management specific view format. The business object includes data logically organized as a credit portfolio management process control root node, a data transfer subordinate node, and a credit portfolio analysis run subordinate node. The graphical user interface presents data associated with an invoked instance of the credit portfolio management process control business object. The user interface includes tangible computer readable instructions embodied on tangible media.

In an eleventh aspect, a tangible computer readable medium includes program code for providing a message-based interface for performing a financial instrument exposure profile analytical result service. The service exposes at least one service as defined in a service registry. Upon execution, the program code executes in an environment of computer systems providing message-based services. The program code initiates transmission of a message to a heterogeneous second application, executing in the environment of computer systems providing message-based services. The message is based on data in a financial instrument exposure profile analytical result business object invoked by the second application. The business object is a logically centralized, semantically disjointed object representing an analytical result of an exposure profile calculation of a financial instrument. The business object includes data logically organized as a financial instrument exposure profile analytical result root node and an item subordinate node. The item node contains a property subordinate node. The message includes a financial instrument exposure profile analytical result entity and a financial instrument exposure profile analytical result package. The program code receives a second message from the second application. The second message is associated with the invoked financial instrument exposure profile analytical result business object and is in response to the first message.

In a twelfth aspect, a distributed system operates in a landscape of computer systems providing message-based services. The system processes business objects involving processing an analytical result of an exposure profile calculation of a financial instrument. The system includes memory and a graphical user interface remote from the memory. The memory stores a business object repository storing a plurality of business objects. Each business object is a logically centralized, semantically disjointed object of a particular business object type. At least one of the business objects represents an analytical result of an exposure profile calculation of a financial instrument. The business object includes data logically organized as a financial instrument exposure profile analytical result root node and an item subordinate node. The item node contains a property subordinate node. The graphical user interface presents data associated with an invoked instance of the a financial instrument exposure profile analytical result business object. The user interface includes tangible computer readable instructions embodied on tangible media.

In a thirteenth aspect, a tangible computer readable medium includes program code for providing a message-based interface for performing a material supply and demand allocation service. The service exposes at least one service as defined in a service registry. Upon execution, the program code executes in an environment of computer systems providing message-based services. The program code receives, from a service consumer, a first message for processing allocation to optimally allocate the available quantities to open requirements. The program code invokes a material supply and demand allocation business object. The business object is a logically centralized, semantically disjointed object representing allocation to optimally allocate the available quantities to open requirements. The business object includes data logically organized as a material supply and demand allocation root node, a system administrative data subordinate node, and an item subordinate node. The item node contains a demand reference subordinate node, a supply reference subordinate node, and a quantity subordinate node. The program code initiates transmission of a message to a heterogeneous second application, executing in the environment of computer systems providing message-based services. The message is based on the data in the material supply and demand allocation business object. The message includes a material supply and demand allocation entity, a message header package, a material supply and demand allocation package, a processing conditions package, and a log package.

In a fourteenth aspect, a tangible computer readable medium includes program code for providing a message-based interface for performing a material supply and demand allocation service. The service exposes at least one service as defined in a service registry. Upon execution, the program code executes in an environment of computer systems providing message-based services. The program code initiates transmission of a message to a heterogeneous second application, executing in the environment of computer systems providing message-based services. The message is based on data in a material supply and demand allocation business object invoked by the second application. The business object is a logically centralized, semantically disjointed object representing allocation to optimally allocate the available quantities to open requirements. The business object includes data logically organized as a material supply and demand allocation root node, a system administrative data subordinate node, and an item subordinate node. The item node contains a demand reference subordinate node, a supply reference subordinate node, and a quantity subordinate node. The message includes a material supply and demand allocation entity, a message header package, a material supply and demand allocation package, a processing conditions package, and a log package. The program code receives a second message from the second application. The second message is associated with the invoked material supply and demand allocation business object and is in response to the first message.

In a fifteenth aspect, a distributed system operates in a landscape of computer systems providing message-based services. The system processes business objects involving processing allocation to optimally allocate the available quantities to open requirements. The system includes memory and a graphical user interface remote from the memory. The memory stores a business object repository storing a plurality of business objects. Each business object is a logically centralized, semantically disjointed object of a particular business object type. At least one of the business objects represents allocation to optimally allocate the available quantities to open requirements. The business object includes data logically organized as a material supply and demand allocation root node, a system administrative data subordinate node, and an item subordinate node. The item node contains a demand reference subordinate node, a supply reference subordinate node, and a quantity subordinate node. The graphical user interface presents data associated with an invoked instance of the material supply and demand allocation business object. The user interface includes tangible computer readable instructions embodied on tangible media.

In some implementations, processing business objects includes creating, updating and/or retrieving information associated with the business objects.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a flow diagram of the overall steps performed by methods and systems consistent with the subject matter described herein.

FIG. 2 depicts a business document flow for an invoice request in accordance with methods and systems consistent with the subject matter described herein.

FIGS. 3A-B illustrate example environments implementing the transmission, receipt, and processing of data between heterogeneous applications in accordance with certain embodiments included in the present disclosure.

FIG. 4 illustrates an example application implementing certain techniques and components in accordance with one embodiment of the system ofFIG. 1.

FIG. 5A depicts an example development environment in accordance with one embodiment ofFIG. 1.

FIG. 5B depicts a simplified process for mapping a model representation to a runtime representation using the example development environment ofFIG. 5A or some other development environment.

FIG. 6 depicts message categories in accordance with methods and systems consistent with the subject matter described herein.

FIG. 7 depicts an example of a package in accordance with methods and systems consistent with the subject matter described herein.

FIG. 8 depicts another example of a package in accordance with methods and systems consistent with the subject matter described herein.

FIG. 9 depicts a third example of a package in accordance with methods and systems consistent with the subject matter described herein.

FIG. 10 depicts a fourth example of a package in accordance with methods and systems consistent with the subject matter described herein.

FIG. 11 depicts the representation of a package in the XML schema in accordance with methods and systems consistent with the subject matter described herein.

FIG. 12 depicts a graphical representation of cardinalities between two entities in accordance with methods and systems consistent with the subject matter described herein.

FIG. 13 depicts an example of a composition in accordance with methods and systems consistent with the subject matter described herein.

FIG. 14 depicts an example of a hierarchical relationship in accordance with methods and systems consistent with the subject matter described herein.

FIG. 15 depicts an example of an aggregating relationship in accordance with methods and systems consistent with the subject matter described herein.

FIG. 16 depicts an example of an association in accordance with methods and systems consistent with the subject matter described herein.

FIG. 17 depicts an example of a specialization in accordance with methods and systems consistent with the subject matter described herein.

FIG. 18 depicts the categories of specializations in accordance with methods and systems consistent with the subject matter described herein.

FIG. 19 depicts an example of a hierarchy in accordance with methods and systems consistent with the subject matter described herein.

FIG. 20 depicts a graphical representation of a hierarchy in accordance with methods and systems consistent with the subject matter described herein.

FIGS. 21A-B depict a flow diagram of the steps performed to create a business object model in accordance with methods and systems consistent with the subject matter described herein.

FIGS. 22A-F depict a flow diagram of the steps performed to generate an interface from the business object model in accordance with methods and systems consistent with the subject matter described herein.

FIG. 23 depicts an example illustrating the transmittal of a business document in accordance with methods and systems consistent with the subject matter described herein.

FIG. 24 depicts an interface proxy in accordance with methods and systems consistent with the subject matter described herein.

FIG. 25 depicts an example illustrating the transmittal of a message using proxies in accordance with methods and systems consistent with the subject matter described herein.

FIG. 26A depicts components of a message in accordance with methods and systems consistent with the subject matter described herein.

FIG. 26B depicts IDs used in a message in accordance with methods and systems consistent with the subject matter described herein.

FIGS. 27A-E depict a hierarchization process in accordance with methods and systems consistent with the subject matter described herein.

FIG. 28 illustrates an example method for service enabling in accordance with one embodiment of the present disclosure.

FIG. 29 is a graphical illustration of an example business object and associated components as may be used in the enterprise service infrastructure system of the present disclosure.

FIG. 30 illustrates an example method for managing a process agent framework in accordance with one embodiment of the present disclosure.

FIG. 31 illustrates an example method for status and action management in accordance with one embodiment of the present disclosure.

FIG. 32 illustrates an exemplary Credit Portfolio Model Message Choreography.

FIGS. 33-1 through33-3 illustrate an exemplary Credit Portfolio Model Object Model.

FIGS. 34-1 through34-3 illustrate an exemplary CreditPortfolioModelFSInputDataRequest Message Data Type.

FIGS. 35-1 through35-2 illustrate an exemplary CrdtPrtfoModFSInDatLoanCrteReqMsg Message Data Type.

FIGS. 36-1 through36-2 illustrate an exemplary CrdtPrtfoModFSInDatBondCrteReqMsg Message Data Type.

FIG. 37 illustrates an exemplary CrdtPrtfoModFSInDatTOBSItmCrteReqMsg Message Data Type.

FIG. 38 illustrates an exemplary CrdtPrtfoModFSInDatCrdtDeriCrteReqMsg Message Data Type.

FIG. 39 illustrates an exemplary CrdtPrtfoModFSInDatPrtfoAnlysDatCrteReqMsg Message Data Type.

FIG. 40 illustrates an exemplary CrdtPrtfoModFSInDatYldCrvCrteReqMsg Message Data Type.

FIG. 41 illustrates an exemplary CrdtPrtfoModFSInDatExchRateCrteReqMsg Message Data Type.

FIG. 42 illustrates an exemplary CrdtPrtfoModFSInDatPDClbrtMtxCrteReqMsg Message Data Type.

FIG. 43 illustrates an exemplary CrdtPrtfoModFSInDatCrdtSprdCrteReqMsg Message Data Type.

FIG. 44 illustrates an exemplary CrdtPrtfoModFSInDatRatgMtxCrteReqMsg Message Data Type.

FIGS. 45-1 through45-2 illustrate an exemplary CrdtPrtfoModFSInDatOTCDeriCrteReqMsg Message Data Type.

FIGS. 46-1 through46-2 illustrate an exemplary CrdtPrtfoModFSInDatSecFTCrteReqMsg Message Data Type.

FIGS. 47-1 through47-2 illustrate an exemplary CrdtPrtfoModFSInDatStockCrteReqMsg Message Data Type.

FIGS. 48-1 through48-2 illustrate an exemplary CrdtPrtfoModFSInDatBuPaCrteReqMsg Message Data Type.

FIG. 49 illustrates an exemplary CrdtPrtfoModFSInDatYldCrvBulkCrteReqMsg Message Data Type.

FIG. 50 illustrates an exemplary CrdtPrtfoModFSInDatExchRateCrteReqMsg Message Data Type.

FIG. 51 illustrates an exemplary CrdtPrtfoModFSInDatPDClbrtMtxBulkCrteReqMsg Message Data Type.

FIG. 52 illustrates an exemplary CrdtPrtfoModFSInDatCrdtSprdBulkCrteReqMsg Message Data Type.

FIG. 53 illustrates an exemplary CrdtPrtfoModFSInDatRatgMtxBulkCrteReqMsg Message Data Type.

FIG. 54 illustrates an exemplary CrdtPrtfoModFSInDatTOBSItmBulkCrteReqMsg Message Data Type.

FIG. 55 illustrates an exemplary CrdtPrtfoModFSInDatLoanBulkCrteReqMsg Message Data Type.

FIG. 56 illustrates an exemplary CrdtPrtfoModFSInDatOTCDeriBulkCrteReqMsg Message Data Type.

FIG. 57 illustrates an exemplary CrdtPrtfoModFSInDatSecFTBulkCrteReqMsg Message Data Type.

FIG. 58 illustrates an exemplary CrdtPrtfoModFSInDatStockBulkCrteReqMsg Message Data Type.

FIG. 59 illustrates an exemplary CrdtPrtfoModFSInDatCrdtDeriBulkCrteReqMsg Message Data Type.

FIG. 60 illustrates an exemplary CrdtPrtfoModFSInDatBondBulkCrteReqMsg Message Data Type.

FIG. 61 illustrates an exemplary CrdtPrtfoModFSInDatBuPaBulkCrteReqMsg Message Data Type.

FIG. 62 illustrates an exemplary CrdtPrtfoModFSInDatPrtfoAnlysDatBulkCrteReqMsg Message Data Type.

FIGS. 63-1 through63-135 illustrate an exemplary CreditPortfolioModelFSInputDataRequest Element Structure.

FIGS. 64-1 through64-25 illustrate an exemplary CreditPortfolioModelFSInputDataLoanRequestMessage Element Structure.

FIGS. 65-1 through65-24 illustrate an exemplary CreditPortfolioModelFSInputDataBondRequestMessage Element Structure.

FIGS. 66-1 through66-25 illustrate an exemplary CrdtPrtfoModFSInDatTOBSItmCrteReqMsg Element Structure.

FIGS. 67-1 through67-23 illustrate an exemplary CrdtPrtfoModFSInDatCrdtDeriCrteReqMsg Element Structure.

FIGS. 68-1 through68-5 illustrate an exemplary CrdtPrtfoModFSInDatPrtfoAnlysDatCrteReqMsg Element Structure.

FIGS. 69-1 through69-3 illustrate an exemplary CrdtPrtfoModFSInDatYldCrvCrteReqMsg Element Structure.

FIGS. 70-1 through70-3 illustrate an exemplary CrdtPrtfoModFSInDatExchRateCrteReqMsg Element Structure.

FIGS. 71-1 through71-4 illustrate an exemplary CrdtPrtfoModFSInDatPDClbrtMtxCrteReqMsg Element Structure.

FIGS. 72-1 through72-4 illustrate an exemplary CreditPortfolioModelFSInputDataCreditSpreadMatrixRequestMessage Element Structure.

FIGS. 73-1 through73-3 illustrate an exemplary CrdtPrtfoModFSInDatRatgTmstnMtxCrteReqMsg Element Structure.

FIGS. 74-1 through74-10 illustrate an exemplary CrdtPrtfoModFSInDatOTCDeriCrteReqMsg Element Structure.

FIGS. 75-1 through75-11 illustrate an exemplary CrdtPrtfoModFSInDatSecFTCrteReqMsg Element Structure.

FIGS. 76-1 through76-9 illustrate an exemplary CrdtPrtfoModFSInDatStockCrteReqMsg Element Structure.

FIGS. 77-1 through77-10 illustrate an exemplary CrdtPrtfoModFSInDatBuPaCrteReqMsg Element Structure.

FIG. 78 illustrates an exemplary CrdtPrtfoModFSInDatBuPaCrteReqMsg Element Structure.

FIG. 79 illustrates an exemplary CrdtPrtfoModFSInDatYldCrvBulkCrteReqMsg Element Structure.

FIG. 80 illustrates an exemplary CreditPortfolioModelFSInputDataExchangeRateCreateBulkRequestMessage Element Structure.

FIG. 81 illustrates an exemplary CrdtPrtfoModFSInDatPDClbrtMtxBulkCrteReqMsg Element Structure.

FIG. 82 illustrates an exemplary CreditPortfolioModelFSInputDataCreditSpreadMatrixCreateBulkRequestMessage Element Structure.

FIG. 83 illustrates an exemplary CrdtPrtfoModFSInDatRatgMtxBulkCrteReqMsg Element Structure.

FIG. 84 illustrates an exemplary CrdtPrtfoModFSInDatTOBSItmBulkCrteReqMsg Element Structure.

FIG. 85 illustrates an exemplary CrdtPrtfoModFSInDatLoanBulkCrteReqMsg Element Structure.

FIG. 86 illustrates an exemplary CrdtPrtfoModFSInDatOTCDeriBulkCrteReqMsg Element Structure.

FIG. 87 illustrates an exemplary CrdtPrtfoModFSInDatSecFTBulkCrteReqMsg Element Structure.

FIG. 88 illustrates an exemplary CrdtPrtfoModFSInDatStockBulkCrteReqMsg Element Structure.

FIG. 89 illustrates an exemplary CrdtPrtfoModFSInDatCrdtDeriBulkCrteReqMsg Element Structure.

FIG. 90 illustrates an exemplary CrdtPrtfoModFSInDatBuPaBulkCrteReqMsg Element Structure.

FIG. 91 illustrates an exemplary CrdtPrtfoModFSInDatPrtfoAnlysDatBulkCrteReqMsg Element Structure.

FIG. 92 illustrates an exemplary Credit Portfolio Analytical Result Message Choreography.

FIG. 93 illustrates an exemplary Credit Portfolio Analytical Result Object Model.

FIGS. 94-1 through94-10 illustrate an exemplary CreditPortfolioAnalyticalResultFSCreateRequestMessage Element Structure.

FIGS. 95-1 through95-6 illustrate an exemplary CreditPortfolioAnalyticalResultFSLossValueCreateRequestMessage Element Structure.

FIGS. 96-1 through96-7 illustrate an exemplary CreditPortfolioAnalyticalResultFSItemCreateRequestMessage Element Structure.

FIG. 97 illustrates an exemplary CrdtPrtfoAnlytRsltFSLossValueBulkCrteReqMsg Element Structure.

FIG. 98 illustrates an exemplary CreditPortfolioAnalyticalResultFSItemBulkCreateRequestMessage Element Structure.

FIGS. 99-1 through99-3 illustrate an exemplary CreditPortfolioManagementProcessControlMessage Object Model.

FIGS. 100-1 through100-11 show an exemplary CrdtPrtfoMgmtProcCtrlFSReqMsg Element Structure.

FIGS. 101-1 through101-3 illustrate an exemplary CrdtPrtfoMgmtProcCtrlFSReqMsg Element Structure.

FIG. 102 illustrates an exemplary CrdtPrtfoMgmtProcCtrlFSConfMsg Element Structure.

FIGS. 103-1 through103-6 illustrate an exemplary CrdtPrtfoMgmtProcCtrlFSDataTransfStsChgdNotifMsg Element Structure.

FIG. 104 illustrates an exemplary Financial Instrument Exposure Profile Analytical Result Message Choreography.

FIG. 105 shows an exemplary Financial Instrument Exposure Profile Analytical Result Object Model.

FIGS. 106-1 through106-3 show an exemplary FinInstrExpsrPrflAnlytlRsltFSCrteReqMsg Element Structure.

FIGS. 107-1 through107-4 show an exemplary FinancialInstrumentsExposureProfileAnalyticalResultFSCreateRequestMessage Element Structure.

FIG. 108 shows an exemplary FinancialInstrumentsExposureProfileAnalyticalResultFSCreateRequestMessage Element Structure.

FIGS. 109-1 through109-11 show an exemplary MaterialSupplyAndDemandAllocationERPCreateRequestMessage_sync Element Structure.

FIGS. 110-1 through110-3 show an exemplary MaterialSupplyAndDemandAllocationERPCreateConfirmationMessage_sync Element Structure.

FIGS. 111-1 through111-9 show an exemplary MaterialSupplyAndDemandAllocationERPCancelRequestMessage_sync Element Structure.

FIGS. 112-1 through112-4 show an exemplary MaterialSupplyAndDemandAllocationERPCancelConfirmationMessage_sync Element Structure.

FIG. 113 shows an exemplary MaterialSupplyAndDemandAllocationERPCancelConfirmationMessage_sync Element Structure.

FIG. 114 shows an exemplary MaterialSupplyAndDemandAllocationERPByIDQueryMessage_sync Element Structure.

FIGS. 115-1 through115-9 show an exemplary MaterialSupplyAndDemandAllocationERPByElementsQueryMessage_sync Element Structure.

FIGS. 116-1 through116-13 show an exemplary MaterialSupplyAndDemandAllocationERPByElementsResponseMessage_sync Element Structure.

FIGS. 117-1 through117-6 show an exemplary MaterialSupplyAndDemandAllocationERPUpdateRequestMessage_sync Element Structure.

FIGS. 118-1 through118-4 show an exemplary MaterialSupplyAndDemandAllocationERPUpdateConfirmationMessage_sync Element Structure.

FIG. 119 shows an exemplary MaterialSupplyAndDemandAllocationERPUpdateConfirmationMessage_sync Element Structure.

FIGS. 120-1 through120-3 show an exemplary MaterialSupplyAndDemandAllocationERPCreateCheckResponseMessage_sync Element Structure.

FIGS. 121-1 through121-9 show an exemplary MaterialSupplyAndDemandAllocationERPCreateCheckResponseMessage_sync Element Structure.

DETAILED DESCRIPTION

A. Overview

Methods and systems consistent with the subject matter described herein facilitate e-commerce by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. To generate consistent interfaces, methods and systems consistent with the subject matter described herein utilize a business object model, which reflects the data that will be used during a given business transaction. An example of a business transaction is the exchange of purchase orders and order confirmations between a buyer and a seller. The business object model is generated in a hierarchical manner to ensure that the same type of data is represented the same way throughout the business object model. This ensures the consistency of the information in the business object model. Consistency is also reflected in the semantic meaning of the various structural elements. That is, each structural element has a consistent business meaning. For example, the location entity, regardless of in which package it is located, refers to a location.

From this business object model, various interfaces are derived to accomplish the functionality of the business transaction. Interfaces provide an entry point for components to access the functionality of an application. For example, the interface for a Purchase Order Request provides an entry point for components to access the functionality of a Purchase Order, in particular, to transmit and/or receive a Purchase Order Request. One skilled in the art will recognize that each of these interfaces may be provided, sold, distributed, utilized, or marketed as a separate product or as a major component of a separate product. Alternatively, a group of related interfaces may be provided, sold, distributed, utilized, or marketed as a product or as a major component of a separate product. Because the interfaces are generated from the business object model, the information in the interfaces is consistent, and the interfaces are consistent among the business entities. Such consistency facilitates heterogeneous business entities in cooperating to accomplish the business transaction.

Generally, the business object is a representation of a type of a uniquely identifiable business entity (an object instance) described by a structural model. In the architecture, processes may typically operate on business objects. Business objects represent a specific view on some well-defined business content. In other words, business objects represent content, which a typical business user would expect and understand with little explanation. Business objects are further categorized as business process objects and master data objects. A master data object is an object that encapsulates master data (i.e., data that is valid for a period of time). A business process object, which is the kind of business object generally found in a process component, is an object that encapsulates transactional data (i.e., data that is valid for a point in time). The term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies.

The architectural elements also include the process component. The process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions. In general, the process component contains one or more semantically related business objects. Often, a particular business object belongs to no more than one process component. Interactions between process component pairs involving their respective business objects, process agents, operations, interfaces, and messages are described as process component interactions, which generally determine the interactions of a pair of process components across a deployment unit boundary. Interactions between process components within a deployment unit are typically not constrained by the architectural design and can be implemented in any convenient fashion. Process components may be modular and context-independent. In other words, process components may not be specific to any particular application and as such, may be reusable. In some implementations, the process component is the smallest (most granular) element of reuse in the architecture. An external process component is generally used to represent the external system in describing interactions with the external system; however, this should be understood to require no more of the external system than that able to produce and receive messages as required by the process component that interacts with the external system. For example, process components may include multiple operations that may provide interaction with the external system. Each operation generally belongs to one type of process component in the architecture. Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below. The operation is often the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters serving as a signature.

The architectural elements may also include the service interface, referred to simply as the interface. The interface is a named group of operations. The interface often belongs to one process component and process component might contain multiple interfaces. In one implementation, the service interface contains only inbound or outbound operations, but not a mixture of both. One interface can contain both synchronous and asynchronous operations. Normally, operations of the same type (either inbound or outbound) which belong to the same message choreography will belong to the same interface. Thus, generally, all outbound operations to the same other process component are in one interface.

The architectural elements also include the message. Operations transmit and receive messages. Any convenient messaging infrastructure can be used. A message is information conveyed from one process component instance to another, with the expectation that activity will ensue. Operation can use multiple message types for inbound, outbound, or error messages. When two process components are in different deployment units, invocation of an operation of one process component by the other process component is accomplished by the operation on the other process component sending a message to the first process component.

The architectural elements may also include the process agent. Process agents do business processing that involves the sending or receiving of messages. Each operation normally has at least one associated process agent. Each process agent can be associated with one or more operations. Process agents can be either inbound or outbound and either synchronous or asynchronous. Asynchronous outbound process agents are called after a business object changes such as after a “create”, “update”, or “delete” of a business object instance. Synchronous outbound process agents are generally triggered directly by business object. An outbound process agent will generally perform some processing of the data of the business object instance whose change triggered the event. The outbound agent triggers subsequent business process steps by sending messages using well-defined outbound services to another process component, which generally will be in another deployment unit, or to an external system. The outbound process agent is linked to the one business object that triggers the agent, but it is sent not to another business object but rather to another process component. Thus, the outbound process agent can be implemented without knowledge of the exact business object design of the recipient process component. Alternatively, the process agent may be inbound. For example, inbound process agents may be used for the inbound part of a message-based communication. Inbound process agents are called after a message has been received. The inbound process agent starts the execution of the business process step requested in a message by creating or updating one or multiple business object instances. Inbound process agent is not generally the agent of business object but of its process component. Inbound process agent can act on multiple business objects in a process component. Regardless of whether the process agent is inbound or outbound, an agent may be synchronous if used when a process component requires a more or less immediate response from another process component, and is waiting for that response to continue its work.

The architectural elements also include the deployment unit. Each deployment unit may include one or more process components that are generally deployed together on a single computer system platform. Conversely, separate deployment units can be deployed on separate physical computing systems. The process components of one deployment unit can interact with those of another deployment unit using messages passed through one or more data communication networks or other suitable communication channels. Thus, a deployment unit deployed on a platform belonging to one business can interact with a deployment unit software entity deployed on a separate platform belonging to a different and unrelated business, allowing for business-to-business communication. More than one instance of a given deployment unit can execute at the same time, on the same computing system or on separate physical computing systems. This arrangement allows the functionality offered by the deployment unit to be scaled to meet demand by creating as many instances as needed.

Since interaction between deployment units is through process component operations, one deployment unit can be replaced by other another deployment unit as long as the new deployment unit supports the operations depended upon by other deployment units as appropriate. Thus, while deployment units can depend on the external interfaces of process components in other deployment units, deployment units are not dependent on process component interaction within other deployment units. Similarly, process components that interact with other process components or external systems only through messages, e.g., as sent and received by operations, can also be replaced as long as the replacement generally supports the operations of the original.

Services (or interfaces) may be provided in a flexible architecture to support varying criteria between services and systems. The flexible architecture may generally be provided by a service delivery business object. The system may be able to schedule a service asynchronously as necessary, or on a regular basis. Services may be planned according to a schedule manually or automatically. For example, a follow-up service may be scheduled automatically upon completing an initial service. In addition, flexible execution periods may be possible (e.g. hourly, daily, every three months, etc.). Each customer may plan the services on demand or reschedule service execution upon request.

FIG. 1 depicts a flow diagram100 showing an example technique, perhaps implemented by systems similar to those disclosed herein. Initially, to generate the business object model, design engineers study the details of a business process, and model the business process using a “business scenario” (step102). The business scenario identifies the steps performed by the different business entities during a business process. Thus, the business scenario is a complete representation of a clearly defined business process.

After creating the business scenario, the developers add details to each step of the business scenario (step104). In particular, for each step of the business scenario, the developers identify the complete process steps performed by each business entity. A discrete portion of the business scenario reflects a “business transaction,” and each business entity is referred to as a “component” of the business transaction. The developers also identify the messages that are transmitted between the components. A “process interaction model” represents the complete process steps between two components.

After creating the process interaction model, the developers create a “message choreography” (step106), which depicts the messages transmitted between the two components in the process interaction model. The developers then represent the transmission of the messages between the components during a business process in a “business document flow” (step108). Thus, the business document flow illustrates the flow of information between the business entities during a business process.

FIG. 2 depicts an examplebusiness document flow200 for the process of purchasing a product or service. The business entities involved with the illustrative purchase process includeAccounting202,Payment204,Invoicing206, Supply Chain Execution (“SCE”)208, Supply Chain Planning (“SCP”)210, Fulfillment Coordination (“FC”)212, Supply Relationship Management (“SRM”)214, Supplier216, andBank218. Thebusiness document flow200 is divided into four different transactions: Preparation of Ordering (“Contract”)220,Ordering222, Goods Receiving (“Delivery”)224, and Billing/Payment226. In the business document flow,arrows228 represent the transmittal of documents. Each document reflects a message transmitted between entities. One of ordinary skill in the art will appreciate that the messages transferred may be considered to be a communications protocol. The process flow follows the focus of control, which is depicted as a solid vertical line (e.g.,229) when the step is required, and a dotted vertical line (e.g.,230) when the step is optional.

During theContract transaction220, theSRM214 sends a Source ofSupply Notification232 to theSCP210. This step is optional, as illustrated by theoptional control line230 coupling this step to the remainder of thebusiness document flow200. During theOrdering transaction222, theSCP210 sends aPurchase Requirement Request234 to theFC212, which forwards aPurchase Requirement Request236 to theSRM214. TheSRM214 then sends aPurchase Requirement Confirmation238 to theFC212, and theFC212 sends aPurchase Requirement Confirmation240 to theSCP210. TheSRM214 also sends aPurchase Order Request242 to the Supplier216, and sendsPurchase Order Information244 to theFC212. TheFC212 then sends a PurchaseOrder Planning Notification246 to theSCP210. The Supplier216, after receiving thePurchase Order Request242, sends aPurchase Order Confirmation248 to theSRM214, which sends a Purchase OrderInformation confirmation message254 to theFC212, which sends amessage256 confirming the Purchase Order Planning Notification to theSCP210. TheSRM214 then sends anInvoice Due Notification258 toInvoicing206.

During theDelivery transaction224, theFC212 sends aDelivery Execution Request260 to theSCE208. The Supplier216 could optionally (illustrated at control line250) send a DispatchedDelivery Notification252 to theSCE208. TheSCE208 then sends amessage262 to theFC212 notifying theFC212 that the request for the Delivery Information was created. TheFC212 then sends amessage264 notifying theSRM214 that the request for the Delivery Information was created. TheFC212 also sends amessage266 notifying theSCP210 that the request for the Delivery Information was created. TheSCE208 sends amessage268 to theFC212 when the goods have been set aside for delivery. TheFC212 sends amessage270 to theSRM214 when the goods have been set aside for delivery. TheFC212 also sends amessage272 to theSCP210 when the goods have been set aside for delivery.

TheSCE208 sends amessage274 to theFC212 when the goods have been delivered. TheFC212 then sends amessage276 to theSRM214 indicating that the goods have been delivered, and sends amessage278 to theSCP210 indicating that the goods have been delivered. TheSCE208 then sends an InventoryChange Accounting Notification280 toAccounting202, and anInventory Change Notification282 to theSCP210. TheFC212 sends anInvoice Due Notification284 toInvoicing206, andSCE208 sends aReceived Delivery Notification286 to the Supplier216.

During the Billing/Payment transaction226, the Supplier216 sends anInvoice Request287 toInvoicing206. Invoicing206 then sends a Payment DueNotification288 toPayment204, a Tax DueNotification289 toPayment204, anInvoice Confirmation290 to the Supplier216, and anInvoice Accounting Notification291 toAccounting202.Payment204 sends a Payment Request292 to theBank218, and a Payment RequestedAccounting Notification293 toAccounting202.Bank218 sends aBank Statement Information296 toPayment204.Payment204 then sends aPayment Done Information294 toInvoicing206 and a Payment DoneAccounting Notification295 toAccounting202.

Within a business document flow, business documents having the same or similar structures are marked. For example, in thebusiness document flow200 depicted inFIG. 2, Purchase Requirement Requests234,236 and

Purchase Requirement Confirmations

238,240 have the same structures. Thus, each of these business documents is marked with an “O6.” Similarly,Purchase Order Request242 andPurchase Order Confirmation248 have the same structures. Thus, both documents are marked with an “O1.” Each business document or message is based on a message type.

From the business document flow, the developers identify the business documents having identical or similar structures, and use these business documents to create the business object model (step110). The business object model includes the objects contained within the business documents. These objects are reflected as packages containing related information, and are arranged in a hierarchical structure within the business object model, as discussed below.

Methods and systems consistent with the subject matter described herein then generate interfaces from the business object model (step112). The heterogeneous programs use instantiations of these interfaces (called “business document objects” below) to create messages (step114), which are sent to complete the business transaction (step116). Business entities use these messages to exchange information with other business entities during an end-to-end business transaction. Since the business object model is shared by heterogeneous programs, the interfaces are consistent among these programs. The heterogeneous programs use these consistent interfaces to communicate in a consistent manner, thus facilitating the business transactions.

Standardized Business-to-Business (“B2B”) messages are compliant with at least one of the e-business standards (i.e., they include the business-relevant fields of the standard). The e-business standards include, for example, RosettaNet for the high-tech industry, Chemical Industry Data Exchange (“CIDX”), Petroleum Industry Data Exchange (“PIDX”) for the oil industry, UCCnet for trade, PapiNet for the paper industry, Odette for the automotive industry, HR-XML for human resources, and XML Common Business Library (“xCBL”). Thus, B2B messages enable simple integration of components in heterogeneous system landscapes. Application-to-Application (“A2A”) messages often exceed the standards and thus may provide the benefit of the full functionality of application components. Although various steps ofFIG. 1 were described as being performed manually, one skilled in the art will appreciate that such steps could be computer-assisted or performed entirely by a computer, including being performed by either hardware, software, or any other combination thereof.

B. Implementation Details

As discussed above, methods and systems consistent with the subject matter described herein create consistent interfaces by generating the interfaces from a business object model. Details regarding the creation of the business object model, the generation of an interface from the business object model, and the use of an interface generated from the business object model are provided below.

Turning to the illustrated embodiment inFIG. 3A,environment300 includes or is communicably coupled (such as via a one-, bi- or multi-directional link or network) withserver302, one ormore clients304, one or more orvendors306, one ormore customers308, at least some of which communicate acrossnetwork312. But, of course, this illustration is for example purposes only, and any distributed system or environment implementing one or more of the techniques described herein may be within the scope of this disclosure.Server302 comprises an electronic computing device operable to receive, transmit, process and store data associated withenvironment300. Generally,FIG. 3A provides merely one example of computers that may be used with the disclosure. Each computer is generally intended to encompass any suitable processing device. For example, althoughFIG. 3A illustrates oneserver302 that may be used with the disclosure,environment300 can be implemented using computers other than servers, as well as a server pool. Indeed,server302 may be any computer or processing device such as, for example, a blade server, general-purpose personal computer (PC), Macintosh, workstation, Unix-based computer, or any other suitable device. In other words, the present disclosure contemplates computers other than general purpose computers as well as computers without conventional operating systems.Server302 may be adapted to execute any operating system including Linux, UNIX, Windows Server, or any other suitable operating system. According to one embodiment,server302 may also include or be communicably coupled with a web server and/or a mail server.

As illustrated (but not required), theserver302 is communicably coupled with a relativelyremote repository335 over a portion of thenetwork312. Therepository335 is any electronic storage facility, data processing center, or archive that may supplement or replace local memory (such as327). Therepository335 may be a central database communicably coupled with the one ormore servers302 and theclients304 via a virtual private network (VPN), SSH (Secure Shell) tunnel, or other secure network connection. Therepository335 may be physically or logically located at any appropriate location including in one of the example enterprises or off-shore, so long as it remains operable to store information associated with theenvironment300 and communicate such data to theserver302 or at least a subset of plurality of theclients304.

Illustrated server

302 includeslocal memory327.Memory327 may include any memory or database module and may take the form of volatile or non-volatile memory including, without limitation, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), removable media, or any other suitable local or remote memory component.Illustrated memory327 includes an exchange infrastructure (“XI”)314, which is an infrastructure that supports the technical interaction of business processes across heterogeneous system environments.XI314 centralizes the communication between components within a business entity and between different business entities. When appropriate,XI314 carries out the mapping between the messages.XI314 integrates different versions of systems implemented on different platforms (e.g., Java and ABAP).XI314 is based on an open architecture, and makes use of open standards, such as eXtensible Markup Language (XML)™ and Java environments.XI314 offers services that are useful in a heterogeneous and complex system landscape. In particular,XI314 offers a runtime infrastructure for message exchange, configuration options for managing business processes and message flow, and options for transforming message contents between sender and receiver systems.

XI

314

stores data types

316, abusiness object model318, and interfaces320. The details regarding the business object model are described below.Data types316 are the building blocks for thebusiness object model318. Thebusiness object model318 is used to deriveconsistent interfaces320.XI314 allows for the exchange of information from a first company having one computer system to a second company having a second computer system overnetwork312 by using the standardized interfaces320.

While not illustrated,memory327 may also include business objects and any other appropriate data such as services, interfaces, VPN applications or services, firewall policies, a security or access log, print or other reporting files, HTML files or templates, data classes or object interfaces, child software applications or sub-systems, and others. This stored data may be stored in one or more logical or physical repositories. In some embodiments, the stored data (or pointers thereto) may be stored in one or more tables in a relational database described in terms of SQL statements or scripts. In the same or other embodiments, the stored data may also be formatted, stored, or defined as various data structures in text files, XML documents, Virtual Storage Access Method (VSAM) files, flat files, Btrieve files, comma-separated-value (CSV) files, internal variables, or one or more libraries. For example, a particular data service record may merely be a pointer to a particular piece of third party software stored remotely. In another example, a particular data service may be an internally stored software object usable by authenticated customers or internal development. In short, the stored data may comprise one table or file or a plurality of tables or files stored on one computer or across a plurality of computers in any appropriate format. Indeed, some or all of the stored data may be local or remote without departing from the scope of this disclosure and store any type of appropriate data.

Server

302 also includesprocessor325.Processor325 executes instructions and manipulates data to perform the operations ofserver302 such as, for example, a central processing unit (CPU), a blade, an application specific integrated circuit (ASIC), or a field-programmable gate array (FPGA). AlthoughFIG. 3A illustrates asingle processor325 inserver302,multiple processors325 may be used according to particular needs and reference toprocessor325 is meant to includemultiple processors325 where applicable. In the illustrated embodiment,processor325 executes atleast business application330.

At a high level,business application330 is any application, program, module, process, or other software that utilizes or facilitates the exchange of information via messages (or services) or the use of business objects. For example,application330 may implement, utilize or otherwise leverage an enterprise service-oriented architecture (enterprise SOA), which may be considered a blueprint for an adaptable, flexible, and open IT architecture for developing services-based, enterprise-scale business solutions. This example enterprise service may be a series of web services combined with business logic that can be accessed and used repeatedly to support a particular business process. Aggregating web services into business-level enterprise services helps provide a more meaningful foundation for the task of automating enterprise-scale business scenarios Put simply, enterprise services help provide a holistic combination of actions that are semantically linked to complete the specific task, no matter how many cross-applications are involved. In certain cases,environment300 may implement acomposite application330, as described below inFIG. 4. Regardless of the particular implementation, “software” may include software, firmware, wired or programmed hardware, or any combination thereof as appropriate. Indeed,application330 may be written or described in any appropriate computer language including C, C++, Java, Visual Basic, assembler, Perl, any suitable version of 4GL, as well as others. For example, returning to the above mentioned composite application, the composite application portions may be implemented as Enterprise Java Beans (EJBs) or the design-time components may have the ability to generate run-time implementations into different platforms, such as J2EE (Java 2 Platform, Enterprise Edition), ABAP (Advanced Business Application Programming) objects, or Microsoft's .NET. It will be understood that whileapplication330 is illustrated inFIG. 4 as including various sub-modules,application330 may include numerous other sub-modules or may instead be a single multi-tasked module that implements the various features and functionality through various objects, methods, or other processes. Further, while illustrated as internal toserver302, one or more processes associated withapplication330 may be stored, referenced, or executed remotely. For example, a portion ofapplication330 may be a web service that is remotely called, while another portion ofapplication330 may be an interface object bundled for processing atremote client304. Moreover,application330 may be a child or sub-module of another software module or enterprise application (not illustrated) without departing from the scope of this disclosure. Indeed,application330 may be a hosted solution that allows multiple related or third parties in different portions of the process to perform the respective processing.

Returning toFIG. 3A, illustratedserver302 may also includeinterface317 for communicating with other computer systems, such asclients304, overnetwork312 in a client-server or other distributed environment. In certain embodiments,server302 receives data from internal or external senders throughinterface317 for storage inmemory327, for storage inDB335, and/or processing byprocessor325. Generally,interface317 comprises logic encoded in software and/or hardware in a suitable combination and operable to communicate withnetwork312. More specifically,interface317 may comprise software supporting one or more communications protocols associated withcommunications network312 or hardware operable to communicate physical signals.

Network

312 facilitates wireless or wireline communication betweencomputer server302 and any other local or remote computer, such asclients304.Network312 may be all or a portion of an enterprise or secured network. In another example,network312 may be a VPN merely betweenserver302 andclient304 across wireline or wireless link. Such an example wireless link may be via 802.11a, 802.11b, 802.11g, 802.20, WiMax, and many others. While illustrated as a single or continuous network,network312 may be logically divided into various sub-nets or virtual networks without departing from the scope of this disclosure, so long as at least portion ofnetwork312 may facilitate communications betweenserver302 and at least oneclient304. For example,server302 may be communicably coupled to one or more “local” repositories through one sub-net while communicably coupled to aparticular client304 or “remote” repositories through another. In other words,network312 encompasses any internal or external network, networks, sub-network, or combination thereof operable to facilitate communications between various computing components inenvironment300.Network312 may communicate, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, and other suitable information between network addresses.Network312 may include one or more local area networks (LANs), radio access networks (RANs), metropolitan area networks (MANs), wide area networks (WANs), all or a portion of the global computer network known as the Internet, and/or any other communication system or systems at one or more locations. In certain embodiments,network312 may be a secure network associated with the enterprise and certain local orremote vendors306 andcustomers308. As used in this disclosure,customer308 is any person, department, organization, small business, enterprise, or any other entity that may use or request others to useenvironment300. As described above,vendors306 also may be local or remote tocustomer308. Indeed, aparticular vendor306 may provide some content tobusiness application330, while receiving or purchasing other content (at the same or different times) ascustomer308. As illustrated,customer308 and vendor06 each typically perform some processing (such as uploading or purchasing content) using a computer, such asclient304.

Client

304 is any computing device operable to connect or communicate withserver302 ornetwork312 using any communication link. For example,client304 is intended to encompass a personal computer, touch screen terminal, workstation, network computer, kiosk, wireless data port, smart phone, personal data assistant (PDA), one or more processors within these or other devices, or any other suitable processing device used by or for the benefit ofbusiness308,vendor306, or some other user or entity. At a high level, eachclient304 includes or executes atleast GUI336 and comprises an electronic computing device operable to receive, transmit, process and store any appropriate data associated withenvironment300. It will be understood that there may be any number ofclients304 communicably coupled toserver302. Further, “client304,” “business,” “business analyst,” “end user,” and “user” may be used interchangeably as appropriate without departing from the scope of this disclosure. Moreover, for ease of illustration, eachclient304 is described in terms of being used by one user. But this disclosure contemplates that many users may use one computer or that one user may use multiple computers. For example,client304 may be a PDA operable to wirelessly connect with external or unsecured network. In another example,client304 may comprise a laptop that includes an input device, such as a keypad, touch screen, mouse, or other device that can accept information, and an output device that conveys information associated with the operation ofserver302 orclients304, including digital data, visual information, orGUI336. Both the input device and output device may include fixed or removable storage media such as a magnetic computer disk, CD-ROM, or other suitable media to both receive input from and provide output to users ofclients304 through the display, namely the client portion of GUI orapplication interface336.

GUI

336 comprises a graphical user interface operable to allow the user ofclient304 to interface with at least a portion ofenvironment300 for any suitable purpose, such as viewing application or other transaction data. Generally,GUI336 provides the particular user with an efficient and user-friendly presentation of data provided by or communicated withinenvironment300. For example,GUI336 may present the user with the components and information that is relevant to their task, increase reuse of such components, and facilitate a sizable developer community around those components.GUI336 may comprise a plurality of customizable frames or views having interactive fields, pull-down lists, and buttons operated by the user. For example,GUI336 is operable to display data involving business objects and interfaces in a user-friendly form based on the user context and the displayed data. In another example,GUI336 is operable to display different levels and types of information involving business objects and interfaces based on the identified or supplied user role.GUI336 may also present a plurality of portals or dashboards. For example,GUI336 may display a portal that allows users to view, create, and manage historical and real-time reports including role-based reporting and such. Of course, such reports may be in any appropriate output format including PDF, HTML, and printable text. Real-time dashboards often provide table and graph information on the current state of the data, which may be supplemented by business objects and interfaces. It should be understood that the term graphical user interface may be used in the singular or in the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Indeed, reference toGUI336 may indicate a reference to the front-end or a component ofbusiness application330, as well as the particular interface accessible viaclient304, as appropriate, without departing from the scope of this disclosure. Therefore,GUI336 contemplates any graphical user interface, such as a generic web browser or touchscreen, that processes information inenvironment300 and efficiently presents the results to the user.Server302 can accept data fromclient304 via the web browser (e.g., Microsoft Internet Explorer or Netscape Navigator) and return the appropriate HTML or XML responses to thebrowser using network312.

More generally inenvironment300 as depicted inFIG. 3B, aFoundation Layer375 can be deployed on multiple separate and distinct hardware platforms, e.g.,System A350 andSystem B360, to support application software deployed as two or more deployment units distributed on the platforms, includingdeployment unit352 deployed on System A anddeployment unit362 deployed on System B. In this example, the foundation layer can be used to support application software deployed in an application layer. In particular, the foundation layer can be used in connection with application software implemented in accordance with a software architecture that provides a suite of enterprise service operations having various application functionality. In some implementations, the application software is implemented to be deployed on an application platform that includes a foundation layer that contains all fundamental entities that can used from multiple deployment units. These entities can be process components, business objects, and reuse service components. A reuse service component is a piece of software that is reused in different transactions. A reuse service component is used by its defined interfaces, which can be, e.g., local APIs or service interfaces. As explained above, process components in separate deployment units interact through service operations, as illustrated by messages passing between

service operations

356 and366, which are implemented in

process components

354 and364, respectively, which are included in

deployment units

352 and362, respectively. As also explained above, some form of direct communication is generally the form of interaction used between a business object, e.g.,

business object

358 and368, of an application deployment unit and a business object, such asmaster data object370, of theFoundation Layer375.

Various components of the present disclosure may be modeled using a model-driven environment. For example, the model-driven framework or environment may allow the developer to use simple drag-and-drop techniques to develop pattern-based or freestyle user interfaces and define the flow of data between them. The result could be an efficient, customized, visually rich online experience. In some cases, this model-driven development may accelerate the application development process and foster business-user self-service. It further enables business analysts or IT developers to compose visually rich applications that use analytic services, enterprise services, remote function calls (RFCs), APIs, and stored procedures. In addition, it may allow them to reuse existing applications and create content using a modeling process and a visual user interface instead of manual coding.

FIG. 5A depicts an example modeling environment516, namely a modeling environment, in accordance with one embodiment of the present disclosure. Thus, as illustrated inFIG. 5A, such a modeling environment516 may implement techniques for decoupling models created during design-time from the runtime environment. In other words, model representations for GUIs created in a design time environment are decoupled from the runtime environment in which the GUIs are executed. Often in these environments, a declarative and executable representation for GUIs for applications is provided that is independent of any particular runtime platform, GUI framework, device, or programming language.

According to some embodiments, a modeler (or other analyst) may use the model-driven modeling environment516 to create pattern-based or freestyle user interfaces using simple drag-and-drop services. Because this development may be model-driven, the modeler can typically compose an application using models of business objects without having to write much, if any, code. In some cases, this example modeling environment516 may provide a personalized, secure interface that helps unify enterprise applications, information, and processes into a coherent, role-based portal experience. Further, the modeling environment516 may allow the developer to access and share information and applications in a collaborative environment. In this way, virtual collaboration rooms allow developers to work together efficiently, regardless of where they are located, and may enable powerful and immediate communication that crosses organizational boundaries while enforcing security requirements. Indeed, the modeling environment516 may provide a shared set of services for finding, organizing, and accessing unstructured content stored in third-party repositories and content management systems acrossvarious networks312. Classification tools may automate the organization of information, while subject-matter experts and content managers can publish information to distinct user audiences. Regardless of the particular implementation or architecture, this modeling environment516 may allow the developer to easily model hosted business objects140 using this model-driven approach.

In certain embodiments, the modeling environment516 may implement or utilize a generic, declarative, and executable GUI language (generally described as XGL). This example XGL is generally independent of any particular GUI framework or runtime platform. Further, XGL is normally not dependent on characteristics of a target device on which the graphic user interface is to be displayed and may also be independent of any programming language. XGL is used to generate a generic representation (occasionally referred to as the XGL representation or XGL-compliant representation) for a design-time model representation. The XGL representation is thus typically a device-independent representation of a GUI. The XGL representation is declarative in that the representation does not depend on any particular GUI framework, runtime platform, device, or programming language. The XGL representation can be executable and therefore can unambiguously encapsulate execution semantics for the GUI described by a model representation. In short, models of different types can be transformed to XGL representations.

The XGL representation may be used for generating representations of various different GUIs and supports various GUI features including full windowing and componentization support, rich data visualizations and animations, rich modes of data entry and user interactions, and flexible connectivity to any complex application data services. While a specific embodiment of XGL is discussed, various other types of XGLs may also be used in alternative embodiments. In other words, it will be understood that XGL is used for example description only and may be read to include any abstract or modeling language that can be generic, declarative, and executable.

Turning to the illustrated embodiment inFIG. 5A,modeling tool340 may be used by a GUI designer or business analyst during the application design phase to create amodel representation502 for a GUI application. It will be understood that modeling environment516 may include or be compatible with variousdifferent modeling tools340 used to generatemodel representation502. Thismodel representation502 may be a machine-readable representation of an application or a domain specific model.Model representation502 generally encapsulates various design parameters related to the GUI such as GUI components, dependencies between the GUI components, inputs and outputs, and the like. Put another way,model representation502 provides a form in which the one or more models can be persisted and transported, and possibly handled by various tools such as code generators, runtime interpreters, analysis and validation tools, merge tools, and the like. In one embodiment,model representation502 maybe a collection of XML documents with a well-formed syntax.

ThisXGL representation506 that is created from a model representation may then be used for processing in the runtime environment. For example, theXGL representation506 may be used to generate a machine-executable runtime GUI (or some other runtime representation) that may be executed by a target device. As part of the runtime processing, theXGL representation506 may be transformed into one or more runtime representations, which may indicate source code in a particular programming language, machine-executable code for a specific runtime environment, executable GUI, and so forth, which may be generated for specific runtime environments and devices. Since theXGL representation506, rather than the design-time model representation, is used by the runtime environment, the design-time model representation is decoupled from the runtime environment. TheXGL representation506 can thus serve as the common ground or interface between design-time user interface modeling tools and a plurality of user interface runtime frameworks. It provides a self-contained, closed, and deterministic definition of all aspects of a graphical user interface in a device-independent and programming-language independent manner. Accordingly,abstract representation506 generated for amodel representation502 is generally declarative and executable in that it provides a representation of the GUI ofmodel representation502 that is not dependent on any device or runtime platform, is not dependent on any programming language, and unambiguously encapsulates execution semantics for the GUI. The execution semantics may include, for example, identification of various components of the GUI, interpretation of connections between the various GUI components, information identifying the order of sequencing of events, rules governing dynamic behavior of the GUI, rules governing handling of values by the GUI, and the like. Theabstract representation506 is also not GUI runtime-platform specific. Theabstract representation506 provides a self-contained, closed, and deterministic definition of all aspects of a graphical user interface that is device independent and language independent.

Abstract representation

506 is such that the appearance and execution semantics of a GUI generated from the XGL representation work consistently on different target devices irrespective of the GUI capabilities of the target device and the target device platform. For example, the same XGL representation may be mapped to appropriate GUIs on devices of differing levels of GUI complexity (i.e., the same abstract representation may be used to generate a GUI for devices that support simple GUIs and for devices that can support complex GUIs), the GUI generated by the devices are consistent with each other in their appearance and behavior.

Abstract representation generator

504 may be configured to generateabstract representation506 for models of different types, which may be created usingdifferent modeling tools340. It will be understood that modeling environment516 may include some, none, or other sub-modules or components as those shown in this example illustration. In other words, modeling environment516 encompasses the design-time environment (with or without the abstract generator or the various representations), a modeling toolkit (such as340) linked with a developer's space, or any other appropriate software operable to decouple models created during design-time from the runtime environment.Abstract representation506 provides an interface between the design time environment and the runtime environment. As shown, thisabstract representation506 may then be used by runtime processing.

As part of runtime processing, modeling environment516 may include variousruntime tools508 and may generate different types of runtime representations based upon theabstract representation506. Examples of runtime representations include device or language-dependent (or specific) source code, runtime platform-specific machine-readable code, GUIs for a particular target device, and the like. Theruntime tools508 may include compilers, interpreters, source code generators, and other such tools that are configured to generate runtime platform-specific or target device-specific runtime representations ofabstract representation506. Theruntime tool508 may generate the runtime representation fromabstract representation506 using specific rules that mapabstract representation506 to a particular type of runtime representation. These mapping rules may be dependent on the type of runtime tool, characteristics of the target device to be used for displaying the GUI, runtime platform, and/or other factors. Accordingly, mapping rules may be provided for transforming theabstract representation506 to any number of target runtime representations directed to one or more target GUI runtime platforms. For example, XGL-compliant code generators may conform to semantics of XGL, as described below. XGL-compliant code generators may ensure that the appearance and behavior of the generated user interfaces is preserved across a plurality of target GUI frameworks, while accommodating the differences in the intrinsic characteristics of each and also accommodating the different levels of capability of target devices.

For example, as depicted in exampleFIG. 5A, an XGL-to-Java compiler508A may takeabstract representation506 as input and generateJava code510 for execution by a target device comprising aJava runtime512.Java runtime512 may executeJava code510 to generate or display aGUI514 on a Java-platform target device. As another example, an XGL-to-Flash compiler508B may takeabstract representation506 as input and generateFlash code526 for execution by a target device comprising aFlash runtime518.Flash runtime518 may execute Flash code516 to generate or display a GUI520 on a target device comprising a Flash platform. As another example, an XGL-to-DHTML (dynamic HTML) interpreter508C may takeabstract representation506 as input and generate DHTML statements (instructions) on the fly which are then interpreted by a DHTML runtime522 to generate or display aGUI524 on a target device comprising a DHTML platform.

It should be apparent thatabstract representation506 may be used to generate GUIs for Extensible Application Markup Language (XAML) or various other runtime platforms and devices. The sameabstract representation506 may be mapped to various runtime representations and device-specific and runtime platform-specific GUIs. In general, in the runtime environment, machine executable instructions specific to a runtime environment may be generated based upon theabstract representation506 and executed to generate a GUI in the runtime environment. The same XGL representation may be used to generate machine executable instructions specific to different runtime environments and target devices.

According to certain embodiments, the process of mapping amodel representation502 to anabstract representation506 and mapping anabstract representation506 to some runtime representation may be automated. For example, design tools may automatically generate an abstract representation for the model representation using XGL and then use the XGL abstract representation to generate GUIs that are customized for specific runtime environments and devices. As previously indicated, mapping rules may be provided for mapping model representations to an XGL representation. Mapping rules may also be provided for mapping an XGL representation to a runtime platform-specific representation.

Since the runtime environment usesabstract representation506 rather thanmodel representation502 for runtime processing, themodel representation502 that is created during design-time is decoupled from the runtime environment.Abstract representation506 thus provides an interface between the modeling environment and the runtime environment. As a result, changes may be made to the design time environment, including changes to modelrepresentation502 or changes that affectmodel representation502, generally to not substantially affect or impact the runtime environment or tools used by the runtime environment. Likewise, changes may be made to the runtime environment generally to not substantially affect or impact the design time environment. A designer or other developer can thus concentrate on the design aspects and make changes to the design without having to worry about the runtime dependencies such as the target device platform or programming language dependencies.

FIG. 5B depicts an example process for mapping amodel representation502 to a runtime representation using the example modeling environment516 ofFIG. 5A or some other modeling environment.Model representation502 may comprise one or more model components and associated properties that describe a data object, such as hosted business objects and interfaces. As described above, at least one of these model components is based on or otherwise associated with these hosted business objects and interfaces. Theabstract representation506 is generated based uponmodel representation502.Abstract representation506 may be generated by theabstract representation generator504.Abstract representation506 comprises one or more abstract GUI components and properties associated with the abstract GUI components. As part of generation ofabstract representation506, the model GUI components and their associated properties from the model representation are mapped to abstract GUI components and properties associated with the abstract GUI components. Various mapping rules may be provided to facilitate the mapping. The abstract representation encapsulates both appearance and behavior of a GUI. Therefore, by mapping model components to abstract components, the abstract representation not only specifies the visual appearance of the GUI but also the behavior of the GUI, such as in response to events whether clicking/dragging or scrolling, interactions between GUI components and such.

One or moreruntime representations550a,including GUIs for specific runtime environment platforms, may be generated fromabstract representation506. A device-dependent runtime representation may be generated for a particular type of target device platform to be used for executing and displaying the GUI encapsulated by the abstract representation. The GUIs generated fromabstract representation506 may comprise various types of GUI elements such as buttons, windows, scrollbars, input boxes, etc. Rules may be provided for mapping an abstract representation to a particular runtime representation. Various mapping rules may be provided for different runtime environment platforms.

Methods and systems consistent with the subject matter described herein provide and useinterfaces320 derived from thebusiness object model318 suitable for use with more than one business area, for example different departments within a company such as finance, or marketing. Also, they are suitable across industries and across businesses.Interfaces320 are used during an end-to-end business transaction to transfer business process information in an application-independent manner. For example the interfaces can be used for fulfilling a sales order.

1. Message Overview

To perform an end-to-end business transaction, consistent interfaces are used to create business documents that are sent within messages between heterogeneous programs or modules.

a) Message Categories

As depicted inFIG. 6, the communication between a sender602 and a recipient604 can be broken down into basic categories that describe the type of the information exchanged and simultaneously suggest the anticipated reaction of the recipient604. A message category is a general business classification for the messages. Communication is sender-driven. In other words, the meaning of the message categories is established or formulated from the perspective of the sender602. The message categories include information606,notification608,query610, response612,request614, and confirmation616.

(1) Information

Information606 is a message sent from a sender602 to a recipient604 concerning a condition or a statement of affairs. No reply to information is expected. Information606 is sent to make business partners or business applications aware of a situation. Information606 is not compiled to be application-specific. Examples of “information” are an announcement, advertising, a report, planning information, and a message to the business warehouse.

(2) Notification

Anotification608 is a notice or message that is geared to a service. A sender602 sends thenotification608 to a recipient604. No reply is expected for a notification. For example, a billing notification relates to the preparation of an invoice while a dispatched delivery notification relates to preparation for receipt of goods.

(3) Query

Aquery610 is a question from a sender602 to a recipient604 to which a response612 is expected. Aquery610 implies no assurance or obligation on the part of the sender602. Examples of aquery610 are whether space is available on a specific flight or whether a specific product is available. These queries do not express the desire for reserving the flight or purchasing the product.

(4) Response

A response612 is a reply to aquery610. The recipient604 sends the response612 to the sender602. A response612 generally implies no assurance or obligation on the part of the recipient604. The sender602 is not expected to reply. Instead, the process is concluded with the response612. Depending on the business scenario, a response612 also may include a commitment, i.e., an assurance or obligation on the part of the recipient604. Examples of responses612 are a response stating that space is available on a specific flight or that a specific product is available. With these responses, no reservation was made.

(5) Request

Arequest614 is a binding requisition or requirement from a sender602 to a recipient604. Depending on the business scenario, the recipient604 can respond to arequest614 with a confirmation616. Therequest614 is binding on the sender602. In making therequest614, the sender602 assumes, for example, an obligation to accept the services rendered in therequest614 under the reported conditions. Examples of arequest614 are a parking ticket, a purchase order, an order for delivery and a job application.

(6) Confirmation

A confirmation616 is a binding reply that is generally made to arequest614. The recipient604 sends the confirmation616 to the sender602. The information indicated in a confirmation616, such as deadlines, products, quantities and prices, can deviate from the information of the precedingrequest614. Arequest614 and confirmation616 may be used in negotiating processes. A negotiating process can consist of a series ofseveral request614 and confirmation616 messages. The confirmation616 is binding on the recipient604. For example, 100 units of X may be ordered in a purchase order request; however, only the delivery of 80 units is confirmed in the associated purchase order confirmation.

b) Message Choreography

A message choreography is a template that specifies the sequence of messages between business entities during a given transaction. The sequence with the messages contained in it describes in general the message “lifecycle” as it proceeds between the business entities. If messages from a choreography are used in a business transaction, they appear in the transaction in the sequence determined by the choreography. This illustrates the template character of a choreography, i.e., during an actual transaction, it is not necessary for all messages of the choreography to appear. Those messages that are contained in the transaction, however, follow the sequence within the choreography. A business transaction is thus a derivation of a message choreography. The choreography makes it possible to determine the structure of the individual message types more precisely and distinguish them from one another.

2. Components of the Business Object Model

The overall structure of the business object model ensures the consistency of the interfaces that are derived from the business object model. The derivation ensures that the same business-related subject matter or concept is represented and structured in the same way in all interfaces.

The business object model defines the business-related concepts at a central location for a number of business transactions. In other words, it reflects the decisions made about modeling the business entities of the real world acting in business transactions across industries and business areas. The business object model is defined by the business objects and their relationship to each other (the overall net structure).

Each business object is generally a capsule with an internal hierarchical structure, behavior offered by its operations, and integrity constraints. Business objects are semantically disjoint, i.e., the same business information is represented once. In the business object model, the business objects are arranged in an ordering framework. From left to right, they are arranged according to their existence dependency to each other. For example, the customizing elements may be arranged on the left side of the business object model, the strategic elements may be arranged in the center of the business object model, and the operative elements may be arranged on the right side of the business object model. Similarly, the business objects are arranged from the top to the bottom based on defined order of the business areas, e.g., finance could be arranged at the top of the business object model with CRM below finance and SRM below CRM.

To ensure the consistency of interfaces, the business object model may be built using standardized data types as well as packages to group related elements together, and package templates and entity templates to specify the arrangement of packages and entities within the structure.

a) Data Types

Data types are used to type object entities and interfaces with a structure. This typing can include business semantic. Such data types may include those generally described at pages 96 through 1642 (which are incorporated by reference herein) of U.S. patent application Ser. No. 11/803,178, filed on May 11, 2007 and entitled “Consistent Set Of Interfaces Derived From A Business Object Model”. For example, the data type BusinessTransactionDocumentID is a unique identifier for a document in a business transaction. Also, as an example, Data type BusinessTransactionDocumentParty contains the information that is exchanged in business documents about a party involved in a business transaction, and includes the party's identity, the party's address, the party's contact person and the contact person's address. BusinessTransactionDocumentParty also includes the role of the party, e.g., a buyer, seller, product recipient, or vendor.

The data types are based on Core Component Types (“CCTs”), which themselves are based on the World Wide Web Consortium (“W3C”) data types. “Global” data types represent a business situation that is described by a fixed structure. Global data types include both context-neutral generic data types (“GDTs”) and context-based context data types (“CDTs”). GDTs contain business semantics, but are application-neutral, i.e., without context. CDTs, on the other hand, are based on GDTs and form either a use-specific view of the GDTs, or a context-specific assembly of GDTs or CDTs. A message is typically constructed with reference to a use and is thus a use-specific assembly of GDTs and CDTs. The data types can be aggregated to complex data types.

To achieve a harmonization across business objects and interfaces, the same subject matter is typed with the same data type. For example, the data type “GeoCoordinates” is built using the data type “Measure” so that the measures in a GeoCoordinate (i.e., the latitude measure and the longitude measure) are represented the same as other “Measures” that appear in the business object model.

b) Entities

Entities are discrete business elements that are used during a business transaction. Entities are not to be confused with business entities or the components that interact to perform a transaction. Rather, “entities” are one of the layers of the business object model and the interfaces. For example, a Catalogue entity is used in a Catalogue Publication Request and a Purchase Order is used in a Purchase Order Request. These entities are created using the data types defined above to ensure the consistent representation of data throughout the entities.

c) Packages

Packages group the entities in the business object model and the resulting interfaces into groups of semantically associated information. Packages also may include “sub”-packages, i.e., the packages may be nested.

Packages may group elements together based on different factors, such as elements that occur together as a rule with regard to a business-related aspect. For example, as depicted inFIG. 7, in a Purchase Order, different information regarding the purchase order, such as the type ofpayment702, andpayment card704, are grouped together via thePaymentInformation package700.

Packages also may combine different components that result in a new object. For example, as depicted inFIG. 8, thecomponents wheels804,motor806, anddoors808 are combined to form a composition “Car”802. The “Car”package800 includes the wheels, motor and doors as well as the composition “Car.”

Another grouping within a package may be subtypes within a type. In these packages, the components are specialized forms of a generic package. For example, as depicted inFIG. 9, thecomponents Car904,Boat906, andTruck908 can be generalized by the generic term Vehicle902 inVehicle package900. Vehicle in this case is thegeneric package910, whileCar912,Boat914, andTruck916 are thespecializations918 of thegeneralized vehicle910.

Packages also may be used to represent hierarchy levels. For example, as depicted inFIG. 10, theItem Package1000 includesItem1002 with subitem xxx1004, subitem yyy1006, andsubitem zzz1008.

Packages can be represented in the XML schema as a comment. One advantage of this grouping is that the document structure is easier to read and is more understandable. The names of these packages are assigned by including the object name in brackets with the suffix “Package.” For example, as depicted inFIG. 11,Party package1100 is enclosed by <PartyPackage>1102 and </PartyPackage>1104.Party package1100 illustratively includes aBuyer Party1106, identified by <BuyerParty>1108 and </BuyerParty>1110, and aSeller Party1112, identified by <SellerParty>1114 and </SellerParty>, etc.

d) Relationships

Relationships describe the interdependencies of the entities in the business object model, and are thus an integral part of the business object model.

(1) Cardinality of Relationships

FIG. 12 depicts a graphical representation of the cardinalities between two entities. The cardinality between a first entity and a second entity identifies the number of second entities that could possibly exist for each first entity. Thus, a 1:c cardinality1200 between entities A1202 andX1204 indicates that for eachentity A1202, there is either one or zero1206

entity X

1204. A 1:1cardinality1208 between entities A1210 andX1212 indicates that for eachentity A1210, there is exactly one1214

entity X

1212. A 1:n cardinality1216 between entities A1218 andX1220 indicates that for eachentity A1218, there are one or more1222

entity Xs

1220. A 1:cn cardinality1224 between entities A1226 andX1228 indicates that for eachentity A1226, there are any number1230 of entity Xs1228 (i.e., 0 through n Xs for each A).

(2) Types of Relationships

(a) Composition

A composition or hierarchical relationship type is a strong whole-part relationship which is used to describe the structure within an object. The parts, or dependent entities, represent a semantic refinement or partition of the whole, or less dependent entity. For example, as depicted inFIG. 13, thecomponents1302, wheels1304, and doors1306 may be combined to form the composite1300 “Car”1308 using thecomposition1310.FIG. 14 depicts a graphical representation of the composition1410 betweencomposite Car1408 and components wheel1404 and door1406.

(b) Aggregation

An aggregation or an aggregating relationship type is a weak whole-part relationship between two objects. The dependent object is created by the combination of one or several less dependent objects. For example, as depicted inFIG. 15, the properties of acompetitor product1500 are determined by aproduct1502 and acompetitor1504. Ahierarchical relationship1506 exists between theproduct1502 and thecompetitor product1500 because thecompetitor product1500 is a component of theproduct1502. Therefore, the values of the attributes of thecompetitor product1500 are determined by theproduct1502. An aggregatingrelationship1508 exists between thecompetitor1504 and thecompetitor product1500 because thecompetitor product1500 is differentiated by thecompetitor1504. Therefore the values of the attributes of thecompetitor product1500 are determined by thecompetitor1504.

(c) Association

An association or a referential relationship type describes a relationship between two objects in which the dependent object refers to the less dependent object. For example, as depicted inFIG. 16, aperson1600 has a nationality, and thus, has a reference to itscountry1602 of origin. There is anassociation1604 between thecountry1602 and theperson1600. The values of the attributes of theperson1600 are not determined by thecountry1602.

(3) Specialization

Entity types may be divided into subtypes based on characteristics of the entity types. For example,FIG. 17 depicts an entity type “vehicle”1700 specialized1702 into subtypes “truck”1704, “car”1706, and “ship”1708. These subtypes represent different aspects or the diversity of the entity type.

Subtypes may be defined based on related attributes. For example, although ships and cars are both vehicles, ships have an attribute, “draft,” that is not found in cars. Subtypes also may be defined based on certain methods that can be applied to entities of this subtype and that modify such entities. For example, “drop anchor” can be applied to ships. If outgoing relationships to a specific object are restricted to a subset, then a subtype can be defined which reflects this subset.

As depicted inFIG. 18, specializations may further be characterized ascomplete specializations1800 orincomplete specializations1802. There is acomplete specialization1800 where each entity of the generalized type belongs to at least one subtype. With anincomplete specialization1802, there is at least one entity that does not belong to a subtype. Specializations also may be disjoint1804 or nondisjoint1806. In a disjoint specialization1804, each entity of the generalized type belongs to a maximum of one subtype. With anondisjoint specialization1806, one entity may belong to more than one subtype. As depicted inFIG. 18, four specialization categories result from the combination of the specialization characteristics.

e) Structural Patterns

(1) Item

An item is an entity type which groups together features of another entity type. Thus, the features for the entity type chart of accounts are grouped together to form the entity type chart of accounts item. For example, a chart of accounts item is a category of values or value flows that can be recorded or represented in amounts of money in accounting, while a chart of accounts is a superordinate list of categories of values or value flows that is defined in accounting.

The cardinality between an entity type and its item is often either 1:n or 1:cn. For example, in the case of the entity type chart of accounts, there is a hierarchical relationship of the cardinality 1:n with the entity type chart of accounts item since a chart of accounts has at least one item in all cases.

(2) Hierarchy

A hierarchy describes the assignment of subordinate entities to superordinate entities and vice versa, where several entities of the same type are subordinate entities that have, at most, one directly superordinate entity. For example, in the hierarchy depicted inFIG. 19,entity B1902 is subordinate toentity A1900, resulting in the relationship (A,B)1912. Similarly,entity C1904 is subordinate toentity A1900, resulting in the relationship (A,C)1914.Entity D1906 andentity E1908 are subordinate toentity B1902, resulting in the relationships (B,D)1916 and (B,E)1918, respectively.Entity F1910 is subordinate toentity C1904, resulting in the relationship (C,F)1920.

Because each entity has at most one superordinate entity, the cardinality between a subordinate entity and its superordinate entity is 1:c. Similarly, each entity may have 0, 1 or many subordinate entities. Thus, the cardinality between a superordinate entity and its subordinate entity is 1:cn.FIG. 20 depicts a graphical representation of a Closing ReportStructure Item hierarchy2000 for a ClosingReport Structure Item2002. The hierarchy illustrates the 1:c cardinality2004 between a subordinate entity and its superordinate entity, and the 1:cn cardinality2006 between a superordinate entity and its subordinate entity.

3. Creation of the Business Object Model

FIGS. 21A-B depict the steps performed using methods and systems consistent with the subject matter described herein to create a business object model. Although some steps are described as being performed by a computer, these steps may alternatively be performed manually, or computer-assisted, or any combination thereof. Likewise, although some steps are described as being performed by a computer, these steps may also be computer-assisted, or performed manually, or any combination thereof.

As discussed above, the designers create message choreographies that specify the sequence of messages between business entities during a transaction. After identifying the messages, the developers identify the fields contained in one of the messages (step2100,FIG. 21A). The designers then determine whether each field relates to administrative data or is part of the object (step2102). Thus, the first eleven fields identified below in the left column are related to administrative data, while the remaining fields are part of the object.


	MessageID	Admin
	ReferenceID
	CreationDate
	SenderID
	AdditionalSenderID
	ContactPersonID
	SenderAddress
	RecipientID
	AdditionalRecipientID
	ContactPersonID
	RecipientAddress
	ID	Main Object
	AdditionalID
	PostingDate
	LastChangeDate
	AcceptanceStatus
	Note
	CompleteTransmission Indicator
	Buyer
	BuyerOrganisationName
	Person Name
	FunctionalTitle
	DepartmentName
	CountryCode
	StreetPostalCode
	POBox Postal Code
	Company Postal Code
	City Name
	DistrictName
	PO Box ID
	PO Box Indicator
	PO Box Country Code
	PO Box Region Code
	PO Box City Name
	Street Name
	House ID
	Building ID
	Floor ID
	Room ID
	Care Of Name
	AddressDescription
	Telefonnumber
	MobileNumber
	Facsimile
	Email
	Seller
	SellerAddress
	Location
	LocationType
	DeliveryItemGroupID
	DeliveryPriority
	DeliveryCondition
	TransferLocation
	NumberofPartialDelivery
	QuantityTolerance
	MaximumLeadTime
	TransportServiceLevel
	TranportCondition
	TransportDescription
	CashDiscountTerms
	PaymentForm
	PaymentCardID
	PaymentCardReferenceID
	SequenceID
	Holder
	ExpirationDate
	AttachmentID
	AttachmentFilename
	DescriptionofMessage
	ConfirmationDescriptionof Message
	FollowUpActivity
	ItemID
	ParentItemID
	HierarchyType
	ProductID
	ProductType
	ProductNote
	ProductCategoryID
	Amount
	BaseQuantity
	ConfirmedAmount
	ConfirmedBaseQuantity
	ItemBuyer
	ItemBuyerOrganisationName
	Person Name
	FunctionalTitle
	DepartmentName
	CountryCode
	StreetPostalCode
	POBox Postal Code
	Company Postal Code
	City Name
	DistrictName
	PO Box ID
	PO Box Indicator
	PO Box Country Code
	PO Box Region Code
	PO Box City Name
	Street Name
	House ID
	Building ID
	Floor ID
	Room ID
	Care Of Name
	AddressDescription
	Telefonnumber
	MobilNumber
	Facsimile
	Email
	ItemSeller
	ItemSellerAddress
	ItemLocation
	ItemLocationType
	ItemDeliveryItemGroupID
	ItemDeliveryPriority
	ItemDeliveryCondition
	ItemTransferLocation
	ItemNumberofPartialDelivery
	ItemQuantityTolerance
	ItemMaximumLeadTime
	ItemTransportServiceLevel
	ItemTranportCondition
	ItemTransportDescription
	ContractReference
	QuoteReference
	CatalogueReference
	ItemAttachmentID
	ItemAttachmentFilename
	ItemDescription
	ScheduleLineID
	DeliveryPeriod
	Quantity
	ConfirmedScheduleLineID
	ConfirmedDeliveryPeriod
	ConfirmedQuantity

Next, the designers determine the proper name for the object according to the ISO 11179 naming standards (step2104). In the example above, the proper name for the “Main Object” is “Purchase Order.” After naming the object, the system that is creating the business object model determines whether the object already exists in the business object model (step2106). If the object already exists, the system integrates new attributes from the message into the existing object (step2108), and the process is complete.

If atstep2106 the system determines that the object does not exist in the business object model, the designers model the internal object structure (step2110). To model the internal structure, the designers define the components. For the above example, the designers may define the components identified below.


ID	Purchase
AdditionalID	Order
PostingDate
LastChangeDate
AcceptanceStatus
Note
CompleteTransmission
Indicator
Buyer		Buyer
BuyerOrganisationName
Person Name
FunctionalTitle
DepartmentName
CountryCode
StreetPostalCode
POBox Postal Code
Company Postal Code
City Name
DistrictName
PO Box ID
PO Box Indicator
PO Box Country Code
PO Box Region Code
PO Box City Name
Street Name
House ID
Building ID
Floor ID
Room ID
Care Of Name
AddressDescription
Telefonnumber
MobileNumber
Facsimile
Email
Seller		Seller
SellerAddress
Location		Location
LocationType
DeliveryItemGroupID		DeliveryTerms
DeliveryPriority
DeliveryCondition
TransferLocation
NumberofPartialDelivery
QuantityTolerance
MaximumLeadTime
TransportServiceLevel
TranportCondition
TransportDescription
CashDiscountTerms
PaymentForm		Payment
PaymentCardID
PaymentCardReferenceID
SequenceID
Holder
ExpirationDate
AttachmentID
AttachmentFilename
DescriptionofMessage
ConfirmationDescriptionof
Message
FollowUpActivity
ItemID		Purchase Order
ParentItemID		Item
HierarchyType
ProductID			Product
ProductType
ProductNote
ProductCategoryID			Product-
			Category
Amount
BaseQuantity
ConfirmedAmount
ConfirmedBaseQuantity
ItemBuyer			Buyer
ItemBuyerOrganisation
Name
Person Name
FunctionalTitle
DepartmentName
CountryCode
StreetPostalCode
POBox Postal Code
Company Postal Code
City Name
DistrictName
PO Box ID
PO Box Indicator
PO Box Country Code
PO Box Region Code
PO Box City Name
Street Name
House ID
Building ID
Floor ID
Room ID
Care Of Name
AddressDescription
Telefonnumber
MobilNumber
Facsimile
Email
ItemSeller			Seller
ItemSellerAddress
ItemLocation			Location
ItemLocationType
ItemDeliveryItemGroupID
ItemDeliveryPriority
ItemDeliveryCondition
ItemTransferLocation
ItemNumberofPartial
Delivery
ItemQuantityTolerance
ItemMaximumLeadTime
ItemTransportServiceLevel
ItemTranportCondition
ItemTransportDescription
ContractReference			Contract
QuoteReference			Quote
CatalogueReference			Catalogue
ItemAttachmentID
ItemAttachmentFilename
ItemDescription
ScheduleLineID
DeliveryPeriod
Quantity
ConfirmedScheduleLineID
ConfirmedDeliveryPeriod
ConfirmedQuantity

During the step of modeling the internal structure, the designers also model the complete internal structure by identifying the compositions of the components and the corresponding cardinalities, as shown below.


PurchaseOrder				1
	Buyer			0 . . . 1
		Address		0 . . . 1
		ContactPerson		0 . . . 1
			Address	0 . . . 1
	Seller			0 . . . 1
	Location			0 . . . 1
		Address		0 . . . 1
	DeliveryTerms			0 . . . 1
		Incoterms		0 . . . 1
		PartialDelivery		0 . . . 1
		QuantityTolerance		0 . . . 1
		Transport		0 . . . 1
	CashDiscount			0 . . . 1
	Terms
		MaximumCashDiscount
		0 . . . 1
		NormalCashDiscount		0 . . . 1
	PaymentForm			0 . . . 1
		PaymentCard		0 . . . 1
	Attachment			0 . . .n
	Description
			0 . . . 1
	Confirmation			0 . . . 1
	Description
	Item
			0 . . .n
		HierarchyRelationship
		0 . . . 1
		Product		0 . . . 1
		ProductCategory		0 . . . 1
		Price		0 . . . 1
			NetunitPrice	0 . . . 1
		ConfirmedPrice		0 . . . 1
			NetunitPrice	0 . . . 1
		Buyer		0 . . . 1
		Seller		0 . . . 1
		Location		0 . . . 1
		DeliveryTerms		0 . . . 1
		Attachment		0 . . .n
		Description
		0 . . . 1
		ConfirmationDescription		0 . . . 1
		ScheduleLine		0 . . .n
			DeliveryPeriod
	1
		ConfirmedScheduleLine		0 . . . n

After modeling the internal object structure, the developers identify the subtypes and generalizations for all objects and components (step2112). For example, the Purchase Order may have subtypes Purchase Order Update, Purchase Order Cancellation and Purchase Order Information. Purchase Order Update may include Purchase Order Request, Purchase Order Change, and Purchase Order Confirmation. Moreover, Party may be identified as the generalization of Buyer and Seller. The subtypes and generalizations for the above example are shown below.


Purchase					1
Order
	PurchaseOrder
	Update
		PurchaseOrder Request
		PurchaseOrder Change
		PurchaseOrder
		Confirmation
	PurchaseOrder
	Cancellation
	PurchaseOrder
	Information
	Party
		BuyerParty
			0 . . . 1
			Address		0 . . . 1
			ContactPerson		0 . . . 1
				Address	0 . . . 1
		SellerParty			0 . . . 1
	Location
		ShipToLocation
			0 . . . 1
			Address		0 . . . 1
		ShipFromLocation			0 . . . 1
			Address		0 . . . 1
	DeliveryTerms				0 . . . 1
		Incoterms			0 . . . 1
		PartialDelivery			0 . . . 1
		QuantityTolerance			0 . . . 1
		Transport			0 . . . 1
	CashDiscount				0 . . . 1
	Terms
		MaximumCash Discount
			0 . . . 1
		NormalCashDiscount			0 . . . 1
	PaymentForm				0 . . . 1
		PaymentCard			0 . . . 1
	Attachment				0 . . .n
	Description
				0 . . . 1
	Confirmation				0 . . . 1
	Description
	Item
				0 . . .n
		HierarchyRelationship
			0 . . . 1
		Product			0 . . . 1
		ProductCategory			0 . . . 1
		Price			0 . . . 1
			NetunitPrice		0 . . . 1
		ConfirmedPrice			0 . . . 1
			NetunitPrice		0 . . . 1
		Party
			BuyerParty
		0 . . . 1
			SellerParty		0 . . . 1
		Location
			ShipTo
		0 . . . 1
			Location
			ShipFrom		0 . . . 1
			Location
		DeliveryTerms
			0 . . . 1
		Attachment			0 . . .n
		Description
			0 . . . 1
		Confirmation			0 . . . 1
		Description
		ScheduleLine
			0 . . .n
			Delivery
		1
			Period
		ConfirmedScheduleLine
			0 . . . n

After identifying the subtypes and generalizations, the developers assign the attributes to these components (step2114). The attributes for a portion of the components are shown below.


Purchase				1
Order
	ID
			1
	SellerID			0 . . . 1
	BuyerPosting			0 . . . 1
	DateTime
	BuyerLast
			0 . . . 1
	ChangeDate
	Time
	SellerPosting
			0 . . . 1
	DateTime
	SellerLast
			0 . . . 1
	ChangeDate
	Time
	Acceptance
			0 . . . 1
	StatusCode
	Note
			0 . . . 1
	ItemList			0 . . . 1
	Complete
	Transmission
	Indicator
	BuyerParty
			0 . . . 1
		StandardID		0 . . .n
		BuyerID
		0 . . . 1
		SellerID		0 . . . 1
		Address		0 . . . 1
		ContactPerson		0 . . . 1
			BuyerID	0 . . . 1
			SellerID	0 . . . 1
			Address	0 . . . 1
	SellerParty			0 . . . 1
	Product			0 . . . 1
	RecipientParty
	VendorParty
			0 . . . 1
	Manufacturer			0 . . . 1
	Party
	BillToParty
			0 . . . 1
	PayerParty			0 . . . 1
	CarrierParty			0 . . . 1
	ShipTo			0 . . . 1
	Location
		StandardID
		0 . . .n
		BuyerID
		0 . . . 1
		SellerID		0 . . . 1
		Address		0 . . . 1
	ShipFrom			0 . . . 1
	Location

The system then determines whether the component is one of the object nodes in the business object model (step2116,FIG. 21B). If the system determines that the component is one of the object nodes in the business object model, the system integrates a reference to the corresponding object node from the business object model into the object (step2118). In the above example, the system integrates the reference to the Buyer party represented by an ID and the reference to the ShipToLocation represented by an into the object, as shown below. The attributes that were formerly located in the PurchaseOrder object are now assigned to the new found object party. Thus, the attributes are removed from the PurchaseOrder object.


PurchaseOrder
	ID
	SellerID
	BuyerPostingDateTime
	BuyerLastChangeDateTime
	SellerPostingDateTime
	SellerLastChangeDateTime
	AcceptanceStatusCode
	Note
	ItemListComplete
	TransmissionIndicator
	BuyerParty
		ID
	SellerParty
	ProductRecipientParty
	VendorParty
	ManufacturerParty
	BillToParty
	PayerParty
	CarrierParty
	ShipToLocation
		ID
	ShipFromLocation

During the integration step, the designers classify the relationship (i.e., aggregation or association) between the object node and the object being integrated into the business object model. The system also integrates the new attributes into the object node (step2120). If at step2116, the system determines that the component is not in the business object model, the system adds the component to the business object model (step2122).

Regardless of whether the component was in the business object model at step2116, the next step in creating the business object model is to add the integrity rules (step2124). There are several levels of integrity rules and constraints which should be described. These levels include consistency rules between attributes, consistency rules between components, and consistency rules to other objects. Next, the designers determine the services offered, which can be accessed via interfaces (step2126). The services offered in the example above include PurchaseOrderCreateRequest, PurchaseOrderCancellationRequest, and PurchaseOrderReleaseRequest. The system then receives an indication of the location for the object in the business object model (step2128). After receiving the indication of the location, the system integrates the object into the business object model (step2130).

4. Structure of the Business Object Model

The business object model, which serves as the basis for the process of generating consistent interfaces, includes the elements contained within the interfaces. These elements are arranged in a hierarchical structure within the business object model.

5. Interfaces Derived from Business Object Model

Interfaces are the starting point of the communication between two business entities. The structure of each interface determines how one business entity communicates with another business entity. The business entities may act as a unified whole when, based on the business scenario, the business entities know what an interface contains from a business perspective and how to fill the individual elements or fields of the interface. As illustrated inFIG. 27A, communication between components takes place via messages that contain business documents (e.g., business document27002). Thebusiness document27002 ensures a holistic business-related understanding for the recipient of the message. The business documents are created and accepted or consumed by interfaces, specifically by inbound and outbound interfaces. The interface structure and, hence, the structure of the business document are derived by a mapping rule. This mapping rule is known as “hierarchization.” An interface structure thus has a hierarchical structure created based on the leadingbusiness object27000. The interface represents a usage-specific, hierarchical view of the underlying usage-neutral object model.

As illustrated inFIG. 27B, several business document objects27006,27008, and27010 as overlapping views may be derived for a given leadingobject27004. Each business document object results from the object model by hierarchization.

To illustrate the hierarchization process,FIG. 27C depicts an example of an object model27012 (i.e., a portion of the business object model) that is used to derive a service operation signature (business document object structure). As depicted, leading object X27014 in theobject model27012 is integrated in a net of object A27016,object B27018, andobject C27020. Initially, the parts of the leading object27014 that are required for the business object document are adopted. In one variation, all parts required for a business document object are adopted from leading object27014 (making such an operation a maximal service operation). Based on these parts, the relationships to the superordinate objects (i.e., objects A, B, and C from which object X depends) are inverted. In other words, these objects are adopted as dependent or subordinate objects in the new business document object.

For example, object A27016,object B27018, andobject C27020 have information that characterize object X. Because object A27016,object B27018, andobject C27020 are superordinate to leading object X27014, the dependencies of these relationships change so that object A27016,object B27018, andobject C27020 become dependent and subordinate to leading object X27014. This procedure is known as “derivation of the business document object by hierarchization.”

Relationships of object X to external objects that are referenced and whose information characterizes object X are added to the operation signature. Such a structure can be quite complex (see, for example,FIG. 27D). The cardinality to these referenced objects is adopted as 1:1 or 1:C, respectively. By this, the direction of the dependency changes. The required parts of this referenced object are adopted identically, both in their cardinality and in their dependency arrangement.

The newly created business document object contains all required information, including the incorporated master data information of the referenced objects. As depicted inFIG. 27D, components Xi in leadingobject X27022 are adopted directly. The relationship ofobject X27022 to object A27024,object B27028, andobject C27026 are inverted, and the parts required by these objects are added as objects that depend fromobject X27022. As depicted, all ofobject A27024 is adopted. B3 and B4 are adopted fromobject B27028, but B1 is not adopted. Fromobject C27026, C2 and C1 are adopted, but C3 is not adopted.

FIG. 27E depicts the businessdocument object X27030 created by this hierarchization process. As shown, the arrangement of the elements corresponds to their dependency levels, which directly leads to a corresponding representation as anXML structure27032.

The following provides certain rules that can be adopted singly or in combination with regard to the hierarchization process. A business document object always refers to a leading business document object and is derived from this object. The name of the root entity in the business document entity is the name of the business object or the name of a specialization of the business object or the name of a service specific view onto the business object. The nodes and elements of the business object that are relevant (according to the semantics of the associated message type) are contained as entities and elements in the business document object.

The name of a business document entity is predefined by the name of the corresponding business object node. The name of the superordinate entity is not repeated in the name of the business document entity. The “full” semantic name results from the concatenation of the entity names along the hierarchical structure of the business document object.

The structure of the business document object is, except for deviations due to hierarchization, the same as the structure of the business object. The cardinalities of the business document object nodes and elements are adopted identically or more restrictively to the business document object. An object from which the leading business object is dependent can be adopted to the business document object. For this arrangement, the relationship is inverted, and the object (or its parts, respectively) are hierarchically subordinated in the business document object.

Nodes in the business object representing generalized business information can be adopted as explicit entities to the business document object (generally speaking, multiply TypeCodes out). When this adoption occurs, the entities are named according to their more specific semantic (name of TypeCode becomes prefix). Party nodes of the business object are modeled as explicit entities for each party role in the business document object. These nodes are given the name <Prefix><Party Role>Party, for example, BuyerParty, ItemBuyerParty. BTDReference nodes are modeled as separate entities for each reference type in the business document object. These nodes are given the name <Qualifier><BO><Node>Reference, for example SalesOrderReference, OriginSalesOrderReference, SalesOrderItemReference. A product node in the business object comprises all of the information on the Product, ProductCategory, and Batch. This information is modeled in the business document object as explicit entities for Product, ProductCategory, and Batch.

Entities which are connected by a 1:1 relationship as a result of hierarchization can be combined to a single entity, if they are semantically equivalent. Such a combination can often occurs if a node in the business document object that results from an assignment node is removed because it does not have any elements.

The message type structure is typed with data types. Elements are typed by GDTs according to their business objects. Aggregated levels are typed with message type specific data types (Intermediate Data Types), with their names being built according to the corresponding paths in the message type structure. The whole message type structured is typed by a message data type with its name being built according to the root entity with the suffix “Message”. For the message type, the message category (e.g., information, notification, query, response, request, confirmation, etc.) is specified according to the suited transaction communication pattern.

In one variation, the derivation by hierarchization can be initiated by specifying a leading business object and a desired view relevant for a selected service operation. This view determines the business document object. The leading business object can be the source object, the target object, or a third object. Thereafter, the parts of the business object required for the view are determined. The parts are connected to the root node via a valid path along the hierarchy. Thereafter, one or more independent objects (object parts, respectively) referenced by the leading object which are relevant for the service may be determined (provided that a relationship exists between the leading object and the one or more independent objects).

Once the selection is finalized, relevant nodes of the leading object node that are structurally identical to the message type structure can then be adopted. If nodes are adopted from independent objects or object parts, the relationships to such independent objects or object parts are inverted. Linearization can occur such that a business object node containing certain TypeCodes is represented in the message type structure by explicit entities (an entity for each value of the TypeCode). The structure can be reduced by checking all 1:1 cardinalities in the message type structure. Entities can be combined if they are semantically equivalent, one of the entities carries no elements, or an entity solely results from an n:m assignment in the business object.

After the hierarchization is completed, information regarding transmission of the business document object (e.g., CompleteTransmissionIndicator, ActionCodes, message category, etc.) can be added. A standardized message header can be added to the message type structure and the message structure can be typed. Additionally, the message category for the message type can be designated.

Invoice Request and Invoice Confirmation are examples of interfaces. These invoice interfaces are used to exchange invoices and invoice confirmations between an invoicing party and an invoice recipient (such as between a seller and a buyer) in a B2B process. Companies can create invoices in electronic as well as in paper form. Traditional methods of communication, such as mail or fax, for invoicing are cost intensive, prone to error, and relatively slow, since the data is recorded manually. Electronic communication eliminates such problems. The motivating business scenarios for the Invoice Request and Invoice Confirmation interfaces are the Procure to Stock (PTS) and Sell from Stock (SFS) scenarios. In the PTS scenario, the parties use invoice interfaces to purchase and settle goods. In the SFS scenario, the parties use invoice interfaces to sell and invoice goods. The invoice interfaces directly integrate the applications implementing them and also form the basis for mapping data to widely-used XML standard formats such as RosettaNet, PIDX, xCBL, and CIDX.

The invoicing party may use two different messages to map a B2B invoicing process: (1) the invoicing party sends the message type InvoiceRequest to the invoice recipient to start a new invoicing process; and (2) the invoice recipient sends the message type InvoiceConfirmation to the invoicing party to confirm or reject an entire invoice or to temporarily assign it the status “pending.”

An InvoiceRequest is a legally binding notification of claims or liabilities for delivered goods and rendered services—usually, a payment request for the particular goods and services. The message type InvoiceRequest is based on the message data type InvoiceMessage. The InvoiceRequest message (as defined) transfers invoices in the broader sense. This includes the specific invoice (request to settle a liability), the debit memo, and the credit memo.

InvoiceConfirmation is a response sent by the recipient to the invoicing party confirming or rejecting the entire invoice received or stating that it has been assigned temporarily the status “pending.” The message type InvoiceConfirmation is based on the message data type InvoiceMessage. An InvoiceConfirmation is not mandatory in a B2B invoicing process, however, it automates collaborative processes and dispute management.

Usually, the invoice is created after it has been confirmed that the goods were delivered or the service was provided. The invoicing party (such as the seller) starts the invoicing process by sending an InvoiceRequest message. Upon receiving the InvoiceRequest message, the invoice recipient (for instance, the buyer) can use the InvoiceConfirmation message to completely accept or reject the invoice received or to temporarily assign it the status “pending.” The InvoiceConfirmation is not a negotiation tool (as is the case in order management), since the options available are either to accept or reject the entire invoice. The invoice data in the InvoiceConfirmation message merely confirms that the invoice has been forwarded correctly and does not communicate any desired changes to the invoice. Therefore, the InvoiceConfirmation includes the precise invoice data that the invoice recipient received and checked. If the invoice recipient rejects an invoice, the invoicing party can send a new invoice after checking the reason for rejection (AcceptanceStatus and ConfirmationDescription at Invoice and InvoiceItem level). If the invoice recipient does not respond, the invoice is generally regarded as being accepted and the invoicing party can expect payment.

FIGS. 22A-F depict a flow diagram of the steps performed by methods and systems consistent with the subject matter described herein to generate an interface from the business object model. Although described as being performed by a computer, these steps may alternatively be performed manually, or using any combination thereof. The process begins when the system receives an indication of a package template from the designer, i.e., the designer provides a package template to the system (step2200).

Package templates specify the arrangement of packages within a business transaction document. Package templates are used to define the overall structure of the messages sent between business entities. Methods and systems consistent with the subject matter described herein use package templates in conjunction with the business object model to derive the interfaces.

The system also receives an indication of the message type from the designer (step2202). The system selects a package from the package template (step2204), and receives an indication from the designer whether the package is required for the interface (step2206). If the package is not required for the interface, the system removes the package from the package template (step2208). The system then continues this analysis for the remaining packages within the package template (step2210).

If, atstep2206, the package is required for the interface, the system copies the entity template from the package in the business object model into the package in the package template (step2212,FIG. 22B). The system determines whether there is a specialization in the entity template (step2214). If the system determines that there is a specialization in the entity template, the system selects a subtype for the specialization (step2216). The system may either select the subtype for the specialization based on the message type, or it may receive this information from the designer. The system then determines whether there are any other specializations in the entity template (step2214). When the system determines that there are no specializations in the entity template, the system continues this analysis for the remaining packages within the package template (step2210,FIG. 22A).

Atstep2210, after the system completes its analysis for the packages within the package template, the system selects one of the packages remaining in the package template (step2218,FIG. 22C), and selects an entity from the package (step2220). The system receives an indication from the designer whether the entity is required for the interface (step2222). If the entity is not required for the interface, the system removes the entity from the package template (step2224). The system then continues this analysis for the remaining entities within the package (step2226), and for the remaining packages within the package template (step2228).

If, atstep2222, the entity is required for the interface, the system retrieves the cardinality between a superordinate entity and the entity from the business object model (step2230,FIG. 22D). The system also receives an indication of the cardinality between the superordinate entity and the entity from the designer (step2232). The system then determines whether the received cardinality is a subset of the business object model cardinality (step2234). If the received cardinality is not a subset of the business object model cardinality, the system sends an error message to the designer (step2236). If the received cardinality is a subset of the business object model cardinality, the system assigns the received cardinality as the cardinality between the superordinate entity and the entity (step2238). The system then continues this analysis for the remaining entities within the package (step2226,FIG. 22C), and for the remaining packages within the package template (step2228).

The system then selects a leading object from the package template (step2240,FIG. 22E). The system determines whether there is an entity superordinate to the leading object (step2242). If the system determines that there is an entity superordinate to the leading object, the system reverses the direction of the dependency (step2244) and adjusts the cardinality between the leading object and the entity (step2246). The system performs this analysis for entities that are superordinate to the leading object (step2242). If the system determines that there are no entities superordinate to the leading object, the system identifies the leading object as analyzed (step2248).

The system then selects an entity that is subordinate to the leading object (step2250,FIG. 22F). The system determines whether any non-analyzed entities are superordinate to the selected entity (step2252). If a non-analyzed entity is superordinate to the selected entity, the system reverses the direction of the dependency (step2254) and adjusts the cardinality between the selected entity and the non-analyzed entity (step2256). The system performs this analysis for non-analyzed entities that are superordinate to the selected entity (step2252). If the system determines that there are no non-analyzed entities superordinate to the selected entity, the system identifies the selected entity as analyzed (step2258), and continues this analysis for entities that are subordinate to the leading object (step2260). After the packages have been analyzed, the system substitutes the BusinessTransactionDocument (“BTD”) in the package template with the name of the interface (step2262). This includes the “BTD” in the BTDItem package and the “BTD” in the BTDItemScheduleLine package.

6. Use of an Interface

The XI stores the interfaces (as an interface type). At runtime, the sending party's program instantiates the interface to create a business document, and sends the business document in a message to the recipient. The messages are preferably defined using XML. In the example depicted inFIG. 23, theBuyer2300 uses anapplication2306 in its system to instantiate aninterface2308 and create an interface object orbusiness document object2310. The Buyer'sapplication2306 uses data that is in the sender's component-specific structure and fills thebusiness document object2310 with the data. The Buyer'sapplication2306 then addsmessage identification2312 to the business document and places the business document into amessage2302. The Buyer'sapplication2306 sends themessage2302 to the Vendor2304. The Vendor2304 uses anapplication2314 in its system to receive themessage2302 and store the business document into its own memory. The Vendor'sapplication2314 unpacks themessage2302 using the correspondinginterface2316 stored in its XI to obtain the relevant data from the interface object orbusiness document object2318.

From the component's perspective, the interface is represented by an interface proxy2400, as depicted inFIG. 24. The proxies2400 shield thecomponents2402 of the sender and recipient from the technical details of sending messages2404 via XI. In particular, as depicted inFIG. 25, at the sending end, the Buyer2500 uses anapplication2510 in its system to call an implementedmethod2512, which generates theoutbound proxy2506. Theoutbound proxy2506 parses the internal data structure of the components and converts them to the XML structure in accordance with the business document object. Theoutbound proxy2506 packs the document into amessage2502. Transport, routing and mapping the XML message to the recipient28304 is done by the routing system (XI, modeling environment516, etc.).

When the message arrives, the recipient'sinbound proxy2508 calls its component-specific method2514 for creating a document. Theproxy2508 at the receiving end downloads the data and converts the XML structure into the internal data structure of therecipient component2504 for further processing.

As depicted inFIG. 26A, amessage2600 includes amessage header2602 and abusiness document2604. Themessage2600 also may include anattachment2606. For example, the sender may attach technical drawings, detailed specifications or pictures of a product to a purchase order for the product. Thebusiness document2604 includes a businessdocument message header2608 and thebusiness document object2610. The businessdocument message header2608 includes administrative data, such as the message ID and a message description. As discussed above, thestructure2612 of thebusiness document object2610 is derived from thebusiness object model2614. Thus, there is a strong correlation between the structure of the business document object and the structure of the business object model. Thebusiness document object2610 forms the core of themessage2600.

In collaborative processes as well as Q&A processes, messages should refer to documents from previous messages. A simple business document object ID or object ID is insufficient to identify individual messages uniquely because several versions of the same business document object can be sent during a transaction. A business document object ID with a version number also is insufficient because the same version of a business document object can be sent several times. Thus, messages require several identifiers during the course of a transaction.

As depicted inFIG. 26B, themessage header2618 inmessage2616 includes a technical ID (“ID4”)2622 that identifies the address for a computer to route the message. The sender's system manages thetechnical ID2622.

The administrative information in the businessdocument message header2624 of the payload orbusiness document2620 includes a BusinessDocumentMessageID (“ID3”)2628. The business entity orcomponent2632 of the business entity manages and sets theBusinessDocumentMessageID2628. The business entity orcomponent2632 also can refer to other business documents using theBusinessDocumentMessageID2628. Thereceiving component2632 requires no knowledge regarding the structure of this ID. TheBusinessDocumentMessageID2628 is, as an ID, unique. Creation of a message refers to a point in time. No versioning is typically expressed by the ID. Besides theBusinessDocumentMessageID2628, there also is a businessdocument object ID2630, which may include versions.

Thecomponent2632 also adds its owncomponent object ID2634 when the business document object is stored in the component. Thecomponent object ID2634 identifies the business document object when it is stored within the component. However, not all communication partners may be aware of the internal structure of thecomponent object ID2634. Some components also may include a versioning in theirID2634.

7. Use of Interfaces Across Industries

Methods and systems consistent with the subject matter described herein provide interfaces that may be used across different business areas for different industries. Indeed, the interfaces derived using methods and systems consistent with the subject matter described herein may be mapped onto the interfaces of different industry standards. Unlike the interfaces provided by any given standard that do not include the interfaces required by other standards, methods and systems consistent with the subject matter described herein provide a set of consistent interfaces that correspond to the interfaces provided by different industry standards. Due to the different fields provided by each standard, the interface from one standard does not easily map onto another standard. By comparison, to map onto the different industry standards, the interfaces derived using methods and systems consistent with the subject matter described herein include most of the fields provided by the interfaces of different industry standards. Missing fields may easily be included into the business object model. Thus, by derivation, the interfaces can be extended consistently by these fields. Thus, methods and systems consistent with the subject matter described herein provide consistent interfaces or services that can be used across different industry standards.

For example,FIG. 28 illustrates anexample method2800 for service enabling. In this example, the enterprise services infrastructure may offer one common and standard-based service infrastructure. Further, one central enterprise services repository may support uniform service definition, implementation and usage of services for user interface, and cross-application communication. Instep2801, a business object is defined via a process component model in a process modeling phase. Next, instep2802, the business object is designed within an enterprise services repository. For example,FIG. 29 provides a graphical representation of one of the business objects2900. As shown, an innermost layer orkernel2901 of the business object may represent the business object's inherent data. Inherent data may include, for example, an employee's name, age, status, position, address, etc. Asecond layer2902 may be considered the business object's logic. Thus, thelayer2902 includes the rules for consistently embedding the business object in a system environment as well as constraints defining values and domains applicable to the business object. For example, one such constraint may limit sale of an item only to a customer with whom a company has a business relationship. Athird layer2903 includes validation options for accessing the business object. For example, thethird layer2903 defines the business object's interface that may be interfaced by other business objects or applications. Afourth layer2904 is the access layer that defines technologies that may externally access the business object.

Accordingly, thethird layer2903 separates the inherent data of thefirst layer2901 and the technologies used to access the inherent data. As a result of the described structure, the business object reveals only an interface that includes a set of clearly defined methods. Thus, applications access the business object via those defined methods. An application wanting access to the business object and the data associated therewith usually includes the information or data to execute the clearly defined methods of the business object's interface. Such clearly defined methods of the business object's interface represent the business object's behavior. That is, when the methods are executed, the methods may change the business object's data. Therefore, an application may utilize any business object by providing the information or data without having any concern for the details related to the internal operation of the business object. Returning tomethod2800, a service provider class and data dictionary elements are generated within a development environment atstep2803. Instep2804, the service provider class is implemented within the development environment.

FIG. 30 illustrates anexample method3000 for a process agent framework. For example, the process agent framework may be the basic infrastructure to integrate business processes located in different deployment units. It may support a loose coupling of these processes by message based integration. A process agent may encapsulate the process integration logic and separate it from business logic of business objects. As shown inFIG. 30, an integration scenario and a process component interaction model are defined during a process modeling phase in step3001. Instep3002, required interface operations and process agents are identified during the process modeling phase also. Next, instep3003, a service interface, service interface operations, and the related process agent are created within an enterprise services repository as defined in the process modeling phase. Instep3004, a proxy class for the service interface is generated. Next, instep3005, a process agent class is created and the process agent is registered. Instep3006, the agent class is implemented within a development environment.

FIG. 31 illustrates an example method3100 for status and action management (S&AM). For example, status and action management may describe the life cycle of a business object (node) by defining actions and statuses (as their result) of the business object (node), as well as, the constraints that the statuses put on the actions. Instep3101, the status and action management schemas are modeled per a relevant business object node within an enterprise services repository. In step3102, existing statuses and actions from the business object model are used or new statuses and actions are created. Next, in step3103, the schemas are simulated to verify correctness and completeness. In step3104, missing actions, statuses, and derivations are created in the business object model with the enterprise services repository. Continuing with method3100, the statuses are related to corresponding elements in the node instep3105. Instep3106, status code GDT's are generated, including constants and code list providers. Next, in step3107, a proxy class for a business object service provider is generated and the proxy class S&AM schemas are imported. In step3108, the service provider is implemented and the status and action management runtime interface is called from the actions.

Regardless of the particular hardware or software architecture used, the disclosed systems or software are generally capable of implementing business objects and deriving (or otherwise utilizing) consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business in accordance with some or all of the following description. In short,system100 contemplates using any appropriate combination and arrangement of logical elements to implement some or all of the described functionality.

Moreover, the preceding flowcharts and accompanying description illustrate example methods. The present services environment contemplates using or implementing any suitable technique for performing these and other tasks. It will be understood that these methods are for illustration purposes only and that the described or similar techniques may be performed at any appropriate time, including concurrently, individually, or in combination. In addition, many of the steps in these flowcharts may take place simultaneously and/or in different orders than as shown. Moreover, the services environment may use methods with additional steps, fewer steps, and/or different steps, so long as the methods remain appropriate. The message choreography ofFIG. 32 describes a possible logical sequence of massages that can be used to realize a Credit Portfolio Management business scenario.

Credit Portfolio Model Interfaces

A “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of a credit portfolio management process control from a “Credit Portfolio Management”system32002, using a Credit Portfolio Management Process ControlFS Request message32004 as shown, for example, inFIG. 32. The Credit Portfolio Management Process ControlFS Request message32004 can be sent by a Request Credit Portfolio Management Process Control operation that is included in a Credit Portfolio Management Process Control Out interface.

The “Credit Portfolio Management”system32002 can request the confirmation of the creation of the credit portfolio management process control from the “Financial Instruments Calculation and Valuation Process Management”system32000, using a Credit Portfolio management Process ControlFS Confirmation message32006 as shown, for example, inFIG. 32. The Credit Portfolio management Process ControlFS Confirmation message32006 is received by the Request Credit Portfolio Management Process Control operation.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the notification of a transfer status change of the credit portfolio management process control from the “Credit Portfolio Management”system32002, using a Credit Portfolio Management Process Control FS Data Transfer Status Changed Notifymessage32008 as shown, for examples, inFIG. 32. The Credit Portfolio Management Process Control FS Data Transfer Status Changed Notifymessage32008 can be sent by a Notify of Data Transfer Status Change operation that is included in the Credit Portfolio Management Process Control Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several stocks from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data StockBulk Request message32010 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data StockBulk Request message32010 can be sent by a Request Input Data Stock as Bulk operation that is included in a Credit Portfolio Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several credit spread matrices from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data Credit Spread MatrixBulk Request message32012 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data Credit Spread MatrixBulk Request message32012 can be sent by a Request Input Data Credit Spread Matrix as Bulk operation included in the Credit Portfolio Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several PD calibration matrices from the “Credit Portfolio Management”system32002, using a Credit Model FS Input Data PD Calibration MatrixBulk Request message32014 as shown, for example, inFIG. 32. The Credit Model FS Input Data PD Calibration MatrixBulk Request message32014 can be sent by a Request Input Data Probability of Default Calibration Matrix as Bulk operation included in the Credit Portfolio Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several rating transition matrices from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data Rating Transition MatrixBulk Request message32016 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data Rating Transition MatrixBulk Request message32016 can be sent by a Request Input Data Rating Transition Matrix as Bulk operation included in the Credit Portfolio Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several traditional off balance sheets from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data Traditional Off Balance SheetBulk Request message32018 as shown, for example, inFIG. 32. The Portfolio Model FS Input Data Traditional Off Balance SheetBulk Request message32018 can be sent by a Request Input Data Traditional Off Balance Sheet Item as Bulk operation included in the Credit Portfolio Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several OTC derivatives from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data OTC DerivativeBulk Request message32020 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data OTC DerivativeBulk Request message32020 can be sent by a Request Input Data OTC Derivative as Bulk operation included in the Credit Portfolio Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several securities financing transactions from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data Securities Financing TransactionBulk Request message32022 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data Securities Financing TransactionBulk Request message32022 can be sent by a Request Input Data Securities Financing Transaction as Bulk operation included in the Credit Portfolio Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several credit derivatives from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data Credit DerivativeBulk Request message32024 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data Credit DerivativeBulk Request message32024 can be sent by a Request Input Data Credit Derivative as Bulk operation included in the Credit Portfolio Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several bonds from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data BondBulk Request message32026 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data BondBulk Request message32026 can be sent by a Request Input Data Bond as Bulk operation included in the Credit Portfolio Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several business partners from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data Business PartnerBulk Request message32028 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data Business PartnerBulk Request message32028 can be sent by a Request Input Data Business Partner as Bulk operation included in the Credit Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several exchange rates from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data Exchange RateBulk Request message32030 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data Exchange RateBulk Request message32030 can be sent by a Request Input Data Exchange Rate as Bulk operation included in the Credit Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several yield curves from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data Yield CurveBulk Request message32032 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data Yield CurveBulk Request message32032 can be sent by a Request Input Data Yield Curve as Bulk operation included in the Credit Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several credit portfolio analyses from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data Credit Portfolio Analysis DataBulk Request message32032 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data Credit Portfolio Analysis DataBulk Request message32032 can be sent by a Request Input Data Credit Portfolio Analysis Data as Bulk operation included in the Credit Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several securitizations from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data SecuritizationBulk Request message32036 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data SecuritizationBulk Request message32036 can be sent by a Request Input Data Securitization as Bulk operation included in the Credit Model Out interface.

The “Financial Instruments Calculation and Valuation Process Management”system32000 can request the creation of several loans from the “Credit Portfolio Management”system32002, using a Credit Portfolio Model FS Input Data LoanBulk Request message32038 as shown, for example, inFIG. 32. The Credit Portfolio Model FS Input Data LoanBulk Request message32038 can be sent by a Request Input Data Loan as Bulk operation included in the Credit Portfolio Model Out interface.

FIGS. 33-1 through33-3 illustrate an example Credit Portfolio Modelbusiness object model33000. Specifically, this model depicts interactions among various components of the Credit Portfolio Model, as well as external components that interact with the Credit Portfolio Model (shown here as33002 through33006 and33046 through33054).Credit Portfolio Model33000 includeselements33008 through33044.Credit Portfolio Model33000 includes for example, aCredit Spread Matrix33014.

FIGS. 34-1 through34-3 illustrate one example logical configuration of aCreditPortfolioModelFSInputDataRequest message34000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as34002 through34066. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCreditPortfolioModelFSInputDataRequest message34000 includes, among other things, aCreditPortfolioModel34010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIGS. 35-1 through35-2 illustrate one example logical configuration of aCrdtPrtfoModFSInDatLoanCreteReqMsg message35000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as35002 through35034. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatLoanCreteReqMsg message35000 includes, among other things, aCreditPortfolioModel35010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIGS. 36-1 through36-2 illustrate one example logical configuration of aCrdtPrtfoModlFSInDatBondCrteReqMsg message36000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as36002 through36030. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModlFSInDatBondCrteReqMsg message36000 includes, among other things, aCreditPortfolioModel36010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 37 illustrates one example logical configuration of aCrdtPrtfoModFSInDatTOBSItmCreteReqMsg message37000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as37002 through37030. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatTOBSItmCreteReqMsg message37000 includes, among other things, aCreditPortfolioModel37008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 38 illustrates one example logical configuration of aCrdtPrtfoModFSInDatCrdtDeriCrteReqMsg message38000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as38002 through37034. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatCrdtDeriCrteReqMsg message38000 includes, among other things, aCreditPortfolioModel38010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 39 illustrates one example logical configuration of aCrdtPrtfoModFSInDatPrtfoAnlysDatCrteReqMsg message39000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as39002 through39026. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatPrtfoAnlysDatCrteReqMsg message39000 includes, among other things, aCreditPortfolioModel39010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 40 illustrates one example logical configuration of aCrdtPrtfoModFSInDatYldCrvCrteReqMsg message40000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as40002 through40022. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatYldCrvCrteReqMsg message40000 includes, among other things, aCreditPortfolioModel40010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 41 illustrates one example logical configuration of aCrdtPrtfoModFSInDatExchRateCrteReqMsg message41000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as41002 through41018. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatExchRateCrteReqMsg message41000 includes, among other things, aCreditPortfolioModel41010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 42 illustrates one example logical configuration of aCrdtPrtfoModFSInDatPDClbrtMtxCrteReqMsg message42000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as42002 through42022. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatPDClbrtMtxCrteReqMsg message42000 includes, among other things, aCreditPortfolioModel42010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 43 illustrates one example logical configuration of aCrdtPrtfoModFSInDatCrdtSprdCrteReqMsg message43000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as43002 through43022. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatCrdtSprdCrteReqMsg message43000 includes, among other things, aCreditPortfolioModel43010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 44 illustrates one example logical configuration of aCrdtPrtfoModFSInDatRatgMtxCrteReqMsg message44000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as44002 through44022. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatRatgMtxCrteReqMsg message44000 includes, among other things, aCreditPortfolioModel44010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 45 illustrates one example logical configuration of aCrdtPrtfoModFSInDatOTCDeriCrteReqMsg message45000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as45002 through45050. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatOTCDeriCrteReqMsg message45000 includes, among other things, aCreditPortfolioModel45010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 46 illustrates one example logical configuration of aCrdtPrtfoModFSInDatSecFTCrteReqMsg message46000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as46002 through46050. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatSecFTCrteReqMsg message46000 includes, among other things, aCreditPortfolioModel46010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 47 illustrates one example logical configuration of aCrdtPrtfoModFSInDatStockCrteReqMsg message47000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as47002 through47042. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatStockCrteReqMsg message47000 includes, among other things, aCreditPortfolioModel47010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 48 illustrates one example logical configuration of aCrdtPrtfoModFSInDatBuPaCrteReqMsg message48000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as48002 through48038. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatBuPaCrteReqMsg message48000 includes, among other things, aCreditPortfolioModel48010. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 49 illustrates one example logical configuration of aCrdtPrtfoModFSInDatYldCrvBulkCrteReqMsg message49000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as49002 through49010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatYldCrvBulkCrteReqMsg message49000 includes, among other things, aMessageHeader49008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 50 illustrates one example logical configuration of aCrdtPrtfoModFSInDatExchRateCrteReqMsg message50000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as50002 through50010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatExchRateCrteReqMsg message50000 includes, among other things, aMessageHeader50008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 51 illustrates one example logical configuration of aCrdtPrtfoModFSInDatPDClbrtMtxBulkCrteReqMsg message51000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as51002 through51010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatPDClbrtMtxBulkCrteReqMsg message51000 includes, among other things, aMessageHeader51008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 52 illustrates one example logical configuration of aCrdtPrtfoModFSInDatCrdtSprdBulkCrteReqMsg message52000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as52002 through52010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatCrdtSprdBulkCrteReqMsg message52000 includes, among other things, aMessageHeader52008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 53 illustrates one example logical configuration of aCrdtPrtfoModFSInDatRatgMtxBulkCrteReqMsg message53000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as53002 through53010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatRatgMtxBulkCrteReqMsg message53000 includes, among other things, aMessageHeader53008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 54 illustrates one example logical configuration of aCrdtPrtfoModFSInDatTOBSItmBulkCrteReqMsg message54000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as54002 through54010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatTOBSItmBulkCrteReqMsg message54000 includes, among other things, aMessageHeader54008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 55 illustrates one example logical configuration of aCrdtPrtfoModFSInDatLoanBulkCrteReqMsg message55000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as55002 through55010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatLoanBulkCrteReqMsg message55000 includes, among other things, aMessageHeader55008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 56 illustrates one example logical configuration of aCrdtPrtfoModFSInDatOTCDeriBulkCrteReqMsg message56000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as56002 through56010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatOTCDeriBulkCrteReqMsg message56000 includes, among other things, aMessageHeader56008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 57 illustrates one example logical configuration of aCrdtPrtfoModFSInDatSecFTBulkCrteReqMsg message57000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as57002 through57010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatSecFTBulkCrteReqMsg message57000 includes, among other things, aMessageHeader57008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 58 illustrates one example logical configuration of aCrdtPrtfoModFSInDatStockBulkCrteReqMsg message58000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as58002 through58010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatStockBulkCrteReqMsg message58000 includes, among other things, aMessageHeader58008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 59 illustrates one example logical configuration of aCrdtPrtfoModFSInDatCrdtDeriBulkCrteReqMsg message59000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as59002 through59010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatCrdtDeriBulkCrteReqMsg message59000 includes, among other things, aMessageHeader59008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 60 illustrates one example logical configuration of aCrdtPrtfoModFSInDatBondBulkCrteReqMsg message60000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as60002 through60010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatBondBulkCrteReqMsg message60000 includes, among other things, aMessageHeader60008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 61 illustrates one example logical configuration of aCrdtPrtfoModFSInDatBuPaBulkCrteReqMsg message61000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as61002 through61010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatBuPaBulkCrteReqMsg message61000 includes, among other things, aMessageHeader61008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 62 illustrates one example logical configuration of aCrdtPrtfoModFSInDatPrtfoAnlysDatBulkCrteReqMsg message62000. Specifically, this figure depicts the arrangement and hierarchy of various component such as one or more levels of packages, entities, and datatypes, shown here as62002 through62010. As describes above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatPrtfoAnlysDatBulkCrteReqMsg message62000 includes, among other things, aMessageHeader62008. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

A credit portfolio model requires input data. In particular, these include the following: Financial Instrument and counterparty data for a given credit portfolio; Correlation data, rating transition matrices; and Financial market data (e.g., interest rate and spread curves).

TheCreditPortfolioManagementProcessControl630020 entity includes aDataTransferID630022 attribute. TheDataTransferID630022 attribute is aPDT_CreditPortfolioManagementProcessControIDataTransferID630024 data type. TheCreditPortfolio630026 entity includes anID630028 attribute. TheID630028 attribute is aPDT_CreditPortfolioID630030 data type. TheInputData630032 package includes anInputData630034 entity. TheInputData630032 package includes various packages, namely aYieldCurve630036, anExchangeRateItem630064, aRatingTransitionMatrix630080, aCreditSpreadMatrix630112, aProbabilityOfDefaultCalibrationMatrix630150, aTraditionalOffBalanceSheetItem630184, aLoan630580, anOTCDerivative630996, aSecuritiesFinancingTransaction631186, aStock631376, aCreditDerivative631536, aSecuritization631886, aBond631960, aBusinessPartner632340 and aPortfolioAnalysisData632486. TheYieldCurve630036 package includes a YieldCurve630038 entity. TheYieldCurve630036 package includes anItem630052 package. TheYieldCurve630038 entity includes various attributes, namely anID630040, aYieldCurveModelID630044 and aValidityDate630048. TheID630040 attribute is aYieldCurveID630042 data type. TheYieldCurveModelID630044 attribute is aPDT YieldCurveModelID630046 data type. TheValidityDate630048 attribute is aDate630050 data type. TheItem630052 package includes anItem630054 entity. TheItem630054 entity includes various attributes, namely aTenorDuration630056 and anInterestRateDoubleValue630060. TheTenorDuration630056 attribute is aDuration630058 data type. TheInterestRateDoubleValue630060 attribute is aDoubleValue630062 data type.

TheExchangeRateItem630064 package includes anExchangeRate630066 entity. TheExchangeRate630066 entity includes various attributes, namely anID630068, aValidityDate630072 and anExchangeRate630076. TheID630068 attribute is aPDT_ExchangeRateID630070 data type. TheValidityDate630072 attribute is aDate630074 data type. TheExchangeRate630076 attribute is anExchangeRate630078 data type.

FIGS. 64-1 through64-25 show an example configuration of an Element Structure that includes a CrdtPrtfoModFSInDatLoanCrteReqMsg64000 package. The CrdtPrtfoModFSInDatLoanCrteReqMsg64000 package includes aCrdtPrtfoModFSInDatLoanCrteReqMsg64002 entity. The CrdtPrtfoModFSInDatLoanCrteReqMsg64000 package includes various packages, namely aMessageHeader64004 and aCreditPortfolioModel64010.

TheMessageHeader64004 package includes aMessageHeader64006 entity. TheMessageHeader64006 entity has a cardinality of 164008 meaning that for each instance of theMessageHeader64004 package there is oneMessageHeader64006 entity.

TheCreditPortfolioModel64010 package includes aCreditPortfolioModel64012 entity. TheCreditPortfolioModel64010 package includes anInputData64036 package. TheCreditPortfolioModel64012 entity has a cardinality of 164014 meaning that for each instance of theCreditPortfolioModel64010 package there is oneCreditPortfolioModel64012 entity. TheCreditPortfolioModel64012 entity includes anID64016 attribute. TheCreditPortfolioModel64012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl64020 and aCreditPortfolio64028. TheID64016 attribute has a cardinality of 164018 meaning that for each instance of theCreditPortfolioModel64012 entity there is oneID64016 attribute.

TheCreditPortfolioManagementProcessControl64020 entity has a cardinality of 164022 meaning that for each instance of theCreditPortfolioModel64012 entity there is oneCreditPortfolioManagementProcessControl64020 entity. TheCreditPortfolioManagementProcessControl64020 entity includes aDataTransferID64024 attribute. TheDataTransferID64024 attribute has a cardinality of 164026 meaning that for each instance of theCreditPortfolioManagementProcessControl64020 entity there is oneDataTransferID64024 attribute.

TheCreditPortfolio64028 entity has a cardinality of 164030 meaning that for each instance of theCreditPortfolioModel64012 entity there is oneCreditPortfolio64028 entity. TheCreditPortfolio64028 entity includes anID64032 attribute. TheID64032 attribute has a cardinality of 164034 meaning that for each instance of theCreditPortfolio64028 entity there is oneID64032 attribute.

TheInputData64036 package includes anInputData64038 entity. TheInputData64036 package includes aLoan64040 package. TheLoan64040 package includes aLoan64042 entity. TheLoan64040 package includes various packages, namely aCounterparty64074, aGuarantorParty64084, aCreditExposureData64096, aFinancialCondition64166, aCashFlowItem64240, aProbabilityOfDefault64252, aRating64270, aProbabilityOfDefaultPriceMatrix64308, aRatingPriceMatrix64342, aPrepayment64388, aSpreadCurve64414 and aProperty64436.

TheCounterparty64074 package includes aCounterparty64076 entity. TheCounterparty64076 entity has a cardinality of 164078 meaning that for each instance of theCounterparty64074 package there is oneCounterparty64076 entity. TheCounterparty64076 entity includes anInternalID64080 attribute. TheInternalID64080 attribute has a cardinality of 164082 meaning that for each instance of theCounterparty64076 entity there is oneInternalID64080 attribute.

TheGuarantorParty64084 package includes aGuarantorParty64086 entity. TheGuarantorParty64086 entity has a cardinality of 0..164088 meaning that for each instance of theGuarantorParty64084 package there may be one GuarantorParty64086 entity. TheGuarantorParty64086 entity includes anInternalID64090 attribute. TheInternalID64090 attribute has a cardinality of 0..164092 meaning that for each instance of theGuarantorParty64086 entity there may be oneInternalID64090 attribute.

ThePriceAtHorizon64138 entity has a cardinality of 0..164140 meaning that for each instance of theCreditExposureData64098 entity there may be onePriceAtHorizon64138 entity. ThePriceAtHorizon64138 entity includes various attributes, namely aDuration64142, anAmount64146 and aDecimalValue64150. TheDuration64142 attribute has a cardinality of 0..164144 meaning that for each instance of thePriceAtHorizon64138 entity there may be oneDuration64142 attribute. TheAmount64146 attribute has a cardinality of 0..164148 meaning that for each instance of thePriceAtHorizon64138 entity there may be oneAmount64146 attribute. TheDecimalValue64150 attribute has a cardinality of 0..164152 meaning that for each instance of thePriceAtHorizon64138 entity there may be one DecimalValue64150 attribute.

TheCurrentPrice64154 entity has a cardinality of 0..164156 meaning that for each instance of theCreditExposureData64098 entity there may be one CurrentPrice64154 entity. TheCurrentPrice64154 entity includes various attributes, namely anAmount64158 and aDecimalValue64162. TheAmount64158 attribute has a cardinality of 0..164160 meaning that for each instance of theCurrentPrice64154 entity there may be oneAmount64158 attribute. TheDecimalValue64162 attribute has a cardinality of 0..164164 meaning that for each instance of theCurrentPrice64154 entity there may be one DecimalValue64162 attribute.

TheFinancialCondition64166 package includes aFinancialCondition64168 entity. TheFinancialCondition64168 entity has a cardinality of 0..n64170 meaning that for each instance of theFinancialCondition64166 package there may be one or more FinancialCondition64168 entities. TheFinancialCondition64168 entity includes various subordinate entities, namely anInterestCondition64172, aFeeCondition64204 and aPaymentCondition64222. TheInterestCondition64172 entity includes aBankContractFinancialConditionSpecification64174 subordinate entity. TheBankContractFinancialConditionSpecification64174 entity includes various subordinate entities, namely aCalculation64178, anAmountSpecification64184 and anInterestSpecification64190. TheCalculation64178 entity includes aRecurrenceSpecification64180 subordinate entity. TheInterestSpecification64190 entity includes aVariableInterest64194 subordinate entity. TheFeeCondition64204 entity includes aBankContractFinancialConditionSpecification64206 subordinate entity. TheBankContractFinancialConditionSpecification64206 entity includes various subordinate entities, namely aCalculation64210 and anAmountSpecification64216. TheCalculation64210 entity includes aRecurrenceSpecification64212 subordinate entity. ThePaymentCondition64222 entity includes aBankContractFinancialConditionSpecification64224 subordinate entity. TheBankContractFinancialConditionSpecification64224 entity includes various subordinate entities, namely aCalculation64228 and anAmountSpecification64234. TheCalculation64228 entity includes aRecurrenceSpecification64230 subordinate entity. TheCashFlowItem64240 package includes aCashFlowItem64242 entity.

TheProbabilityOfDefault64252 package includes aProbabilityOfDefault64254 entity. TheProbabilityOfDefault64254 entity has a cardinality of 0..n64256 meaning that for each instance of theProbabilityOfDefault64252 package there may be one or more ProbabilityOfDefault64254 entities. TheProbabilityOfDefault64254 entity includes various attributes, namely aValidityDatePeriod64258, aCode64262 and aDoubleValue64266. TheValidityDatePeriod64258 attribute has a cardinality of 164260 meaning that for each instance of theProbabilityOfDefault64254 entity there is oneValidityDatePeriod64258 attribute. TheCode64262 attribute has a cardinality of 164264 meaning that for each instance of theProbabilityOfDefault64254 entity there is oneCode64262 attribute. TheDoubleValue64266 attribute has a cardinality of 164268 meaning that for each instance of theProbabilityOfDefault64254 entity there is oneDoubleValue64266 attribute.

TheProbabilityOfDefaultPriceMatrix64308 package includes aProbabilityOfDefaultPriceMatrix64310 entity. TheProbabilityOfDefaultPriceMatrix64310 entity has a cardinality of 0..164312 meaning that for each instance of theProbabilityOfDefaultPriceMatrix64308 package there may be one ProbabilityOfDefaultPriceMatrix64310 entity. TheProbabilityOfDefaultPriceMatrix64310 entity includes anItem64314 subordinate entity.

TheItem64314 entity has a cardinality of 1..n64316 meaning that for each instance of theProbabilityOfDefaultPriceMatrix64310 entity there are one ormore Item64314 entities. TheItem64314 entity includes various attributes, namely aValidityDate64318, aProbabilityOfDefaultDecimalValue64322, anUsageDecimalValue64326, aCommitmentFeeDecimalValue64330, aFacilityFeeDecimalValue64334 and aSpreadDecimalValue64338. TheValidityDate64318 attribute has a cardinality of 164320 meaning that for each instance of theItem64314 entity there is oneValidityDate64318 attribute. TheProbabilityOfDefaultDecimalValue64322 attribute has a cardinality of 164324 meaning that for each instance of theItem64314 entity there is oneProbabilityOfDefaultDecimalValue64322 attribute. TheUsageDecimalValue64326 attribute has a cardinality of 164328 meaning that for each instance of theItem64314 entity there is oneUsageDecimalValue64326 attribute. TheCommitmentFeeDecimalValue64330 attribute has a cardinality of 0..164332 meaning that for each instance of theItem64314 entity there may be one CommitmentFeeDecimalValue64330 attribute. TheFacilityFeeDecimalValue64334 attribute has a cardinality of 0..164336 meaning that for each instance of theItem64314 entity there may be one FacilityFeeDecimalValue64334 attribute. TheSpreadDecimalValue64338 attribute has a cardinality of 0..164340 meaning that for each instance of theItem64314 entity there may be one SpreadDecimalValue64338 attribute.

TheRatingPriceMatrix64342 package includes aRatingPriceMatrix64344 entity. TheRatingPriceMatrix64344 entity has a cardinality of 0..164346 meaning that for each instance of theRatingPriceMatrix64342 package there may be one RatingPriceMatrix64344 entity. TheRatingPriceMatrix64344 entity includes anItem64348 subordinate entity.

ThePrepayment64388 package includes aPrepayment64390 entity. ThePrepayment64390 entity has a cardinality of 0..n64392 meaning that for each instance of thePrepayment64388 package there may be one ormore Prepayment64390 entities. ThePrepayment64390 entity includes aPrepayableIndicator64394 attribute. ThePrepayment64390 entity includes anItem64398 subordinate entity. ThePrepayableIndicator64394 attribute has a cardinality of 164396 meaning that for each instance of thePrepayment64390 entity there is onePrepayableIndicator64394 attribute.

TheItem64398 entity has a cardinality of 0..n64400 meaning that for each instance of thePrepayment64390 entity there may be one ormore Item64398 entities. TheItem64398 entity includes various attributes, namely aPaymentDate64402, aCostsOfPrepaymentFractionDecimalValue64406 and aPenaltyOfPrepaymentFractionDecimalValue64410. ThePaymentDate64402 attribute has a cardinality of 164404 meaning that for each instance of theItem64398 entity there is onePaymentDate64402 attribute. TheCostsOfPrepaymentFractionDecimalValue64406 attribute has a cardinality of 0..164408 meaning that for each instance of theItem64398 entity there may be one CostsOfPrepaymentFractionDecimalValue64406 attribute. ThePenaltyOfPrepaymentFractionDecimalValue64410 attribute has a cardinality of 0..164412 meaning that for each instance of theItem64398 entity there may be one PenaltyOfPrepaymentFractionDecimalValue64410 attribute.

TheSpreadCurve64414 package includes aSpreadCurve64416 entity. TheSpreadCurve64416 entity has a cardinality of 0..164418 meaning that for each instance of theSpreadCurve64414 package there may be one SpreadCurve64416 entity. TheSpreadCurve64416 entity includes anItem64420 subordinate entity.

TheItem64420 entity has a cardinality of 1..n64422 meaning that for each instance of theSpreadCurve64416 entity there are one ormore Item64420 entities. TheItem64420 entity includes various attributes, namely aValidityDate64424, aDuration64428 and aSpreadDoubleValue64432. TheValidityDate64424 attribute has a cardinality of 164426 meaning that for each instance of theItem64420 entity there is oneValidityDate64424 attribute. TheDuration64428 attribute has a cardinality of 164430 meaning that for each instance of theItem64420 entity there is oneDuration64428 attribute. TheSpreadDoubleValue64432 attribute has a cardinality of 164434 meaning that for each instance of theItem64420 entity there is oneSpreadDoubleValue64432 attribute.

TheProperty64436 package includes aProperty64438 entity. TheProperty64438 entity has a cardinality of 0..n64440 meaning that for each instance of theProperty64436 package there may be one ormore Property64438 entities. TheProperty64438 entity includes various attributes, namely anID64442 and aValue64446. TheID64442 attribute has a cardinality of 164444 meaning that for each instance of theProperty64438 entity there is oneID64442 attribute. TheValue64446 attribute has a cardinality of 164448 meaning that for each instance of theProperty64438 entity there is oneValue64446 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 65-1 through65-24 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatBondCrteReqMsg65000 package. TheCrdtPrtfoModFSInDatBondCrteReqMsg65000 package includes aCrdtPrtfoModFSInDatBondCrteReqMsg65002 entity. TheCrdtPrtfoModFSInDatBondCrteReqMsg65000 package includes various packages, namely aMessageHeader65004 and aCreditPortfolioModel65010.

TheMessageHeader65004 package includes aMessageHeader65006 entity. TheMessageHeader65006 entity has a cardinality of 165008 meaning that for each instance of theMessageHeader65004 package there is oneMessageHeader65006 entity.

TheCreditPortfolioModel65010 package includes aCreditPortfolioModel65012 entity. TheCreditPortfolioModel65010 package includes anInputData65036 package. TheCreditPortfolioModel65012 entity has a cardinality of 165014 meaning that for each instance of theCreditPortfolioModel65010 package there is oneCreditPortfolioModel65012 entity. TheCreditPortfolioModel65012 entity includes anID65016 attribute. TheCreditPortfolioModel65012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl65020 and aCreditPortfolio65028. TheID65016 attribute has a cardinality of 165018 meaning that for each instance of theCreditPortfolioModel65012 entity there is oneID65016 attribute.

TheCreditPortfolioManagementProcessControl65020 entity has a cardinality of 165022 meaning that for each instance of theCreditPortfolioModel65012 entity there is oneCreditPortfolioManagementProcessControl65020 entity. TheCreditPortfolioManagementProcessControl65020 entity includes aDataTransferID65024 attribute. TheDataTransferID65024 attribute has a cardinality of 165026 meaning that for each instance of theCreditPortfolioManagementProcessControl65020 entity there is oneDataTransferID65024 attribute. TheCreditPortfolio65028 entity has a cardinality of 165030 meaning that for each instance of theCreditPortfolioModel65012 entity there is oneCreditPortfolio65028 entity. TheCreditPortfolio65028 entity includes anID65032 attribute. TheID65032 attribute has a cardinality of 165034 meaning that for each instance of theCreditPortfolio65028 entity there is oneID65032 attribute. TheInputData65036 package includes anInputData65038 entity. TheInputData65036 package includes aBond65042 package. TheInputData65038 entity has a cardinality of 165040 meaning that for each instance of theInputData65036 package there is oneInputData65038 entity.

TheCounterparty65076 package includes aCounterparty65078 entity. TheCounterparty65078 entity has a cardinality of 165080 meaning that for each instance of theCounterparty65076 package there is oneCounterparty65078 entity. TheCounterparty65078 entity includes various attributes, namely anInternalID65082 and aGuarantorSubstitutionCategoryCode65086. TheInternalID65082 attribute has a cardinality of 165084 meaning that for each instance of theCounterparty65078 entity there is oneInternalID65082 attribute. TheGuarantorSubstitutionCategoryCode65086 attribute has a cardinality of 0..165088 meaning that for each instance of theCounterparty65078 entity there may be oneGuarantorSubstitutionCategoryCode65086 attribute.

TheGuarantorParty65090 package includes aGuarantorParty65092 entity. TheGuarantorParty65092 entity has a cardinality of 0..165094 meaning that for each instance of theGuarantorParty65090 package there may be one GuarantorParty65092 entity. TheGuarantorParty65092 entity includes anInternalID65096 attribute. TheInternalID65096 attribute has a cardinality of 0..165098 meaning that for each instance of theGuarantorParty65092 entity there may be oneInternalID65096 attribute.

ThePriceAtHorizon65122 entity has a cardinality of 0..165124 meaning that for each instance of theCreditExposureData65102 entity there may be onePriceAtHorizon65122 entity. ThePriceAtHorizon65122 entity includes various attributes, namely aDuration65126, anAmount65130 and aDecimalValue65134. TheDuration65126 attribute has a cardinality of 0..165128 meaning that for each instance of thePriceAtHorizon65122 entity there may be oneDuration65126 attribute. TheAmount65130 attribute has a cardinality of 0..165132 meaning that for each instance of thePriceAtHorizon65122 entity there may be oneAmount65130 attribute. TheDecimalValue65134 attribute has a cardinality of 0..165136 meaning that for each instance of thePriceAtHorizon65122 entity there may be one DecimalValue65134 attribute.

TheCurrentPrice65138 entity has a cardinality of 0..165140 meaning that for each instance of theCreditExposureData65102 entity there may be one CurrentPrice65138 entity. TheCurrentPrice65138 entity includes various attributes, namely aDuration65142, anAmount65146 and aDecimalValue65150. TheDuration65142 attribute has a cardinality of 0..165144 meaning that for each instance of theCurrentPrice65138 entity there may be oneDuration65142 attribute. TheAmount65146 attribute has a cardinality of 0..165148 meaning that for each instance of theCurrentPrice65138 entity there may be oneAmount65146 attribute. TheDecimalValue65150 attribute has a cardinality of 0..165152 meaning that for each instance of theCurrentPrice65138 entity there may be one DecimalValue65150 attribute.

TheFinancialCondition65162 package includes aFinancialCondition65164 entity. TheFinancialCondition65164 entity includes various subordinate entities, namely anInterestCondition65166, aFeeCondition65198 and aPaymentCondition65216. TheInterestCondition65166 entity includes aBankContractFinancialConditionSpecification65168 subordinate entity. TheBankContractFinancialConditionSpecification65168 entity includes various subordinate entities, namely aCalculation65172, anAmountSpecification65178 and anInterestSpecification65184. TheCalculation65172 entity includes aRecurrenceSpecification65174 subordinate entity. TheInterestSpecification65184 entity includes aVariableInterest65188 subordinate entity. TheFeeCondition65198 entity includes aBankContractFinancialConditionSpecification65200 subordinate entity. TheBankContractFinancialConditionSpecification65200 entity includes various subordinate entities, namely aCalculation65204 and anAmountSpecification65210. TheCalculation65204 entity includes aRecurrenceSpecification65206 subordinate entity. ThePaymentCondition65216 entity includes aBankContractFinancialConditionSpecification65218 subordinate entity. TheBankContractFinancialConditionSpecification65218 entity includes various subordinate entities, namely aCalculation65222 and anAmountSpecification65228. TheCalculation65222 entity includes aRecurrenceSpecification65224 subordinate entity. TheCashFlowItem65234 package includes aCashFlowItem65236 entity.

TheProbabilityOfDefault65246 package includes aProbabilityOfDefault65248 entity. TheProbabilityOfDefault65248 entity has a cardinality of 0..n65250 meaning that for each instance of theProbabilityOfDefault65246 package there may be one or more ProbabilityOfDefault65248 entities. TheProbabilityOfDefault65248 entity includes various attributes, namely aValidityDatePeriod65252, aCode65256 and aDoubleValue65260. TheValidityDatePeriod65252 attribute has a cardinality of 165254 meaning that for each instance of theProbabilityOfDefault65248 entity there is oneValidityDatePeriod65252 attribute. TheCode65256 attribute has a cardinality of 165258 meaning that for each instance of theProbabilityOfDefault65248 entity there is oneCode65256 attribute. TheDoubleValue65260 attribute has a cardinality of 165262 meaning that for each instance of theProbabilityOfDefault65248 entity there is oneDoubleValue65260 attribute.

TheSinkData65302 package includes aSinkData65304 entity. TheSinkData65304 entity has a cardinality of 0..165306 meaning that for each instance of theSinkData65302 package there may be oneSinkData65304 entity. TheSinkData65304 entity includes anItem65308 subordinate entity. TheItem65308 entity has a cardinality of 1..n65310 meaning that for each instance of theSinkData65304 entity there are one ormore Item65308 entities. TheItem65308 entity includes various attributes, namely aRepaymentDate65312, aRepaymentAmount65316 and aPriceOfRepaymentFractionDecimalValue65320. TheRepaymentDate65312 attribute has a cardinality of 165314 meaning that for each instance of theItem65308 entity there is oneRepaymentDate65312 attribute. TheRepaymentAmount65316 attribute has a cardinality of 165318 meaning that for each instance of theItem65308 entity there is oneRepaymentAmount65316 attribute. ThePriceOfRepaymentFractionDecimalValue65320 attribute has a cardinality of 165322 meaning that for each instance of theItem65308 entity there is onePriceOfRepaymentFractionDecimalValue65320 attribute.

TheOption65324 package includes anOption65326 entity. TheOption65326 entity has a cardinality of 1..n65328 meaning that for each instance of theOption65324 package there are one ormore Option65326 entities. TheOption65326 entity includes various attributes, namely aValidityPeriod65330, aCategoryCode65334, aStyleCode65338, aMutualRightOfNoticePurchaseIndicator65342, aQuotationCode65346 and aSingleExerciseIndicator65350. TheOption65326 entity includes various subordinate entities, namely anItem65354 and anExerciseDateSpecification65374. TheValidityPeriod65330 attribute has a cardinality of 165332 meaning that for each instance of theOption65326 entity there is oneValidityPeriod65330 attribute. TheCategoryCode65334 attribute has a cardinality of 165336 meaning that for each instance of theOption65326 entity there is oneCategoryCode65334 attribute. TheStyleCode65338 attribute has a cardinality of 165340 meaning that for each instance of theOption65326 entity there is oneStyleCode65338 attribute. TheMutualRightOfNoticePurchaseIndicator65342 attribute has a cardinality of 0..165344 meaning that for each instance of theOption65326 entity there may be one MutualRightOfNoticePurchaseIndicator65342 attribute. TheQuotationCode65346 attribute has a cardinality of 0..165348 meaning that for each instance of theOption65326 entity there may be oneQuotationCode65346 attribute. TheSingleExerciseIndicator65350 attribute has a cardinality of 0..165352 meaning that for each instance of theOption65326 entity there may be one SingleExerciseIndicator65350 attribute.

TheItem65354 entity has a cardinality of 1..n65356 meaning that for each instance of theOption65326 entity there are one ormore Item65354 entities. TheItem65354 entity includes various attributes, namely aValidityPeriod65358, anExercisePriceFractionDecimalValue65362, aStrikePercent65366 and aStrikeAmount65370. TheValidityPeriod65358 attribute has a cardinality of 0..165360 meaning that for each instance of theItem65354 entity there may be oneValidityPeriod65358 attribute. TheExercisePriceFractionDecimalValue65362 attribute has a cardinality of 0..165364 meaning that for each instance of theItem65354 entity there may be one ExercisePriceFractionDecimalValue65362 attribute. TheStrikePercent65366 attribute has a cardinality of 0..165368 meaning that for each instance of theItem65354 entity there may be one StrikePercent65366 attribute. TheStrikeAmount65370 attribute has a cardinality of 0..165372 meaning that for each instance of theItem65354 entity there may be one StrikeAmount65370 attribute.

TheExerciseDateSpecification65374 entity has a cardinality of 0..n65376 meaning that for each instance of theOption65326 entity there may be one or more ExerciseDateSpecification65374 entities. TheExerciseDateSpecification65374 entity includes anExcerciseValidityPeriod65378 attribute. TheExcerciseValidityPeriod65378 attribute has a cardinality of 165380 meaning that for each instance of theExerciseDateSpecification65374 entity there is oneExcerciseValidityPeriod65378 attribute.

TheSpreadCurve65382 package includes aSpreadCurve65384 entity. TheSpreadCurve65384 entity has a cardinality of 0..165386 meaning that for each instance of theSpreadCurve65382 package there may be one SpreadCurve65384 entity. TheSpreadCurve65384 entity includes anItem65388 subordinate entity. TheItem65388 entity has a cardinality of 1..n65390 meaning that for each instance of theSpreadCurve65384 entity there are one ormore Item65388 entities. TheItem65388 entity includes various attributes, namely aValidityDate65392, aDuration65396 and aSpreadDoubleValue65400. TheValidityDate65392 attribute has a cardinality of 165394 meaning that for each instance of theItem65388 entity there is oneValidityDate65392 attribute. TheDuration65396 attribute has a cardinality of 165398 meaning that for each instance of theItem65388 entity there is oneDuration65396 attribute. TheSpreadDoubleValue65400 attribute has a cardinality of 165402 meaning that for each instance of theItem65388 entity there is oneSpreadDoubleValue65400 attribute.

TheProperty65404 package includes aProperty65406 entity. TheProperty65406 entity has a cardinality of 0..n65408 meaning that for each instance of theProperty65404 package there may be one ormore Property65406 entities. TheProperty65406 entity includes various attributes, namely anID65410 and aValue65414. TheID65410 attribute has a cardinality of 165412 meaning that for each instance of theProperty65406 entity there is oneID65410 attribute. TheValue65414 attribute has a cardinality of 165416 meaning that for each instance of theProperty65406 entity there is oneValue65414 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 66-1 through66-25 show an example configuration of an Element Structure that includes a CrdtPrtfoModFSInDatTOBSItmCrteReqMsg66000 package. The CrdtPrtfoModFSInDatTOBSItmCrteReqMsg66000 package includes aCrdtPrtfoModFSInDatTOBSItmCrteReqMsg66002 entity. The CrdtPrtfoModFSInDatTOBSItmCrteReqMsg66000 package includes various packages, namely aMessageHeader66004 and aCreditPortfolioModel66010.

TheMessageHeader66004 package includes aMessageHeader66006 entity. TheMessageHeader66006 entity has a cardinality of 166008 meaning that for each instance of theMessageHeader66004 package there is oneMessageHeader66006 entity.

TheCreditPortfolioModel66010 package includes aCreditPortfolioModel66012 entity. TheCreditPortfolioModel66010 package includes anInputData66036 package. TheCreditPortfolioModel66012 entity has a cardinality of 166014 meaning that for each instance of theCreditPortfolioModel66010 package there is oneCreditPortfolioModel66012 entity. TheCreditPortfolioModel66012 entity includes anID66016 attribute. TheCreditPortfolioModel66012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl66020 and aCreditPortfolio66028. TheID66016 attribute has a cardinality of 166018 meaning that for each instance of theCreditPortfolioModel66012 entity there is oneID66016 attribute.

TheCreditPortfolioManagementProcessControl66020 entity has a cardinality ofb166022 meaning that for each instance of theCreditPortfolioModel66012 entity there is oneCreditPortfolioManagementProcessControl66020 entity. TheCreditPortfolioManagementProcessControl66020 entity includes aDataTransferID66024 attribute. TheDataTransferID66024 attribute has a cardinality of 166026 meaning that for each instance of theCreditPortfolioManagementProcessControl66020 entity there is oneDataTransferID66024 attribute.

TheCreditPortfolio66028 entity has a cardinality of 166030 meaning that for each instance of theCreditPortfolioModel66012 entity there is oneCreditPortfolio66028 entity. TheCreditPortfolio66028 entity includes anID66032 attribute. TheID66032 attribute has a cardinality of 166034 meaning that for each instance of theCreditPortfolio66028 entity there is oneID66032 attribute.

TheInputData66036 package includes anInputData66038 entity. TheInputData66036 package includes aTraditionalOffBalanceSheetItem66040 package.

TheTraditionalOffBalanceSheetItem66040 package includes aTraditionalOffBalanceSheetItem66042 entity. TheTraditionalOffBalanceSheetItem66040 package includes various packages, namely aCounterparty66074, aGuarantorParty66086, aCreditExposureData66096, aFinancialCondition66170, aProbabilityOfDefault66242, aRating66260, aProbabilityOfDefaultPriceMatrix66298, aRatingPriceMatrix66332, aPrepayment66378, aSpreadCurve66404 and aProperty66426.

TheCounterparty66074 package includes aCounterparty66076 entity. TheCounterparty66076 entity has a cardinality of 166078 meaning that for each instance of theCounterparty66074 package there is oneCounterparty66076 entity. TheCounterparty66076 entity includes anInternalID66080 attribute. TheInternalID66080 attribute has a cardinality of 166082 meaning that for each instance of theCounterparty66076 entity there is oneInternalID66080 attribute.

TheGuarantorParty66086 package includes aGuarantorParty66088 entity. TheGuarantorParty66088 entity has a cardinality of 0..166090 meaning that for each instance of theGuarantorParty66086 package there may be one GuarantorParty66088 entity. TheGuarantorParty66088 entity includes anInternalID66092 attribute. TheInternalID66092 attribute has a cardinality of 0..166094 meaning that for each instance of theGuarantorParty66088 entity there may be oneInternalID66092 attribute.

ThePriceAtHorizon66138 entity has a cardinality of 0..166140 meaning that for each instance of theCreditExposureData66098 entity there may be onePriceAtHorizon66138 entity. ThePriceAtHorizon66138 entity includes various attributes, namely aDuration66142, anAmount66146 and aDecimalValue66150. TheDuration66142 attribute has a cardinality of 0..166144 meaning that for each instance of thePriceAtHorizon66138 entity there may be oneDuration66142 attribute. TheAmount66146 attribute has a cardinality of 0..166148 meaning that for each instance of thePriceAtHorizon66138 entity there may be oneAmount66146 attribute. TheDecimalValue66150 attribute has a cardinality of 0..166152 meaning that for each instance of thePriceAtHorizon66138 entity there may be one DecimalValue66150 attribute.

TheCurrentPrice66154 entity has a cardinality of 0..166156 meaning that for each instance of theCreditExposureData66098 entity there may be one CurrentPrice66154 entity. TheCurrentPrice66154 entity includes various attributes, namely aDuration66158, anAmount66162 and aDecimalValue66166. TheDuration66158 attribute has a cardinality of 0..166160 meaning that for each instance of theCurrentPrice66154 entity there may be oneDuration66158 attribute. TheAmount66162 attribute has a cardinality of 0..166164 meaning that for each instance of theCurrentPrice66154 entity there may be oneAmount66162 attribute. TheDecimalValue66166 attribute has a cardinality of 0..166168 meaning that for each instance of theCurrentPrice66154 entity there may be one DecimalValue66166 attribute.

TheFinancialCondition66170 package includes aFinancialCondition66172 entity. TheFinancialCondition66172 entity includes various subordinate entities, namely anInterestCondition66174, aFeeCondition66206 and aPaymentCondition66224. TheInterestCondition66174 entity includes aBankContractFinancialConditionSpecification66176 subordinate entity. TheBankContractFinancialConditionSpecification66176 entity includes various subordinate entities, namely aCalculation66180, anAmountSpecification66186 and anInterestSpecification66192. TheCalculation66180 entity includes aRecurrenceSpecification66182 subordinate entity. TheInterestSpecification66192 entity includes aVariableInterest66196 subordinate entity. TheFeeCondition66206 entity includes aBankContractFinancialConditionSpecification66208 subordinate entity. TheBankContractFinancialConditionSpecification66208 entity includes various subordinate entities, namely aCalculation66212 and anAmountSpecification66218. TheCalculation66212 entity includes aRecurrenceSpecification66214 subordinate entity. ThePaymentCondition66224 entity includes aBankContractFinancialConditionSpecification66226 subordinate entity. TheBankContractFinancialConditionSpecification66226 entity includes various subordinate entities, namely aCalculation66230 and anAmountSpecification66236. TheCalculation66230 entity includes aRecurrenceSpecification66232 subordinate entity.

TheProbabilityOfDefault66242 package includes aProbabilityOfDefault66244 entity. TheProbabilityOfDefault66244 entity has a cardinality of 0..n66246 meaning that for each instance of theProbabilityOfDefault66242 package there may be one or more ProbabilityOfDefault66244 entities. TheProbabilityOfDefault66244 entity includes various attributes, namely aValidityDatePeriod66248, aCode66252 and aDoubleValue66256. TheValidityDatePeriod66248 attribute has a cardinality of 166250 meaning that for each instance of theProbabilityOfDefault66244 entity there is oneValidityDatePeriod66248 attribute. TheCode66252 attribute has a cardinality of 166254 meaning that for each instance of theProbabilityOfDefault66244 entity there is oneCode66252 attribute. TheDoubleValue66256 attribute has a cardinality of 166258 meaning that for each instance of theProbabilityOfDefault66244 entity there is oneDoubleValue66256 attribute.

TheProbabilityOfDefaultPriceMatrix66298 package includes aProbabilityOfDefaultPriceMatrix66300 entity. TheProbabilityOfDefaultPriceMatrix66300 entity has a cardinality of 0..166302 meaning that for each instance of theProbabilityOfDefaultPriceMatrix66298 package there may be one ProbabilityOfDefaultPriceMatrix66300 entity. TheProbabilityOfDefaultPriceMatrix66300 entity includes anItem66304 subordinate entity.

TheItem66304 entity has a cardinality of 1..n66306 meaning that for each instance of theProbabilityOfDefaultPriceMatrix66300 entity there are one ormore Item66304 entities. TheItem66304 entity includes various attributes, namely aValidityDate66308, aProbabilityOfDefaultDecimalValue66312, anUsageDecimalValue66316, aCommitmentFeeDecimalValue66320, aFacilityFeeDecimalValue66324 and aSpreadDecimalValue66328. TheValidityDate66308 attribute has a cardinality of 166310 meaning that for each instance of theItem66304 entity there is oneValidityDate66308 attribute. TheProbabilityOfDefaultDecimalValue66312 attribute has a cardinality of 166314 meaning that for each instance of theItem66304 entity there is oneProbabilityOfDefaultDecimalValue66312 attribute. TheUsageDecimalValue66316 attribute has a cardinality of 166318 meaning that for each instance of theItem66304 entity there is oneUsageDecimalValue66316 attribute. TheCommitmentFeeDecimalValue66320 attribute has a cardinality of 0..166322 meaning that for each instance of theItem66304 entity there may be one CommitmentFeeDecimalValue66320 attribute. TheFacilityFeeDecimalValue66324 attribute has a cardinality of 0..166326 meaning that for each instance of theItem66304 entity there may be one FacilityFeeDecimalValue66324 attribute. TheSpreadDecimalValue66328 attribute has a cardinality of 0..166330 meaning that for each instance of theItem66304 entity there may be one SpreadDecimalValue66328 attribute.

TheRatingPriceMatrix66332 package includes aRatingPriceMatrix66334 entity. TheRatingPriceMatrix66334 entity has a cardinality of 0..166336 meaning that for each instance of theRatingPriceMatrix66332 package there may be one RatingPriceMatrix66334 entity. TheRatingPriceMatrix66334 entity includes anItem66338 subordinate entity.

ThePrepayment66378 package includes aPrepayment66380 entity. ThePrepayment66380 entity has a cardinality of 0..n66382 meaning that for each instance of thePrepayment66378 package there may be one ormore Prepayment66380 entities. ThePrepayment66380 entity includes aPrepayableIndicator66384 attribute. ThePrepayment66380 entity includes anItem66388 subordinate entity. ThePrepayableIndicator66384 attribute has a cardinality of 166386 meaning that for each instance of thePrepayment66380 entity there is onePrepayableIndicator66384 attribute.

TheItem66388 entity has a cardinality of 0..n66390 meaning that for each instance of thePrepayment66380 entity there may be one ormore Item66388 entities. TheItem66388 entity includes various attributes, namely aPaymentDate66392, aCostsOfPrepaymentFractionDecimalValue66396 and aPenaltyOfPrepaymentFractionDecimalValue66400. ThePaymentDate66392 attribute has a cardinality of 166394 meaning that for each instance of theItem66388 entity there is onePaymentDate66392 attribute. TheCostsOfPrepaymentFractionDecimalValue66396 attribute has a cardinality of 0..166398 meaning that for each instance of theItem66388 entity there may be one CostsOfPrepaymentFractionDecimalValue66396 attribute. ThePenaltyOfPrepaymentFractionDecimalValue66400 attribute has a cardinality of 0..166402 meaning that for each instance of theItem66388 entity there may be one PenaltyOfPrepaymentFractionDecimalValue66400 attribute.

TheSpreadCurve66404 package includes aSpreadCurve66406 entity. TheSpreadCurve66406 entity has a cardinality of 0..166408 meaning that for each instance of theSpreadCurve66404 package there may be one SpreadCurve66406 entity. TheSpreadCurve66406 entity includes anItem66410 subordinate entity.

TheItem66410 entity has a cardinality of 1..n66412 meaning that for each instance of theSpreadCurve66406 entity there are one ormore Item66410 entities. TheItem66410 entity includes various attributes, namely aValidityDate66414, aDuration66418 and aSpreadDoubleValue66422. TheValidityDate66414 attribute has a cardinality of 166416 meaning that for each instance of theItem66410 entity there is oneValidityDate66414 attribute. TheDuration66418 attribute has a cardinality of 166420 meaning that for each instance of theItem66410 entity there is oneDuration66418 attribute. TheSpreadDoubleValue66422 attribute has a cardinality of 166424 meaning that for each instance of theItem66410 entity there is oneSpreadDoubleValue66422 attribute.

TheProperty66426 package includes aProperty66428 entity. TheProperty66428 entity has a cardinality of 0..n66430 meaning that for each instance of theProperty66426 package there may be one ormore Property66428 entities. TheProperty66428 entity includes various attributes, namely anID66432 and aValue66436. TheID66432 attribute has a cardinality of 166434 meaning that for each instance of theProperty66428 entity there is oneID66432 attribute. TheValue66436 attribute has a cardinality of 166438 meaning that for each instance of theProperty66428 entity there is oneValue66436 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 67-1 through67-23 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatCrdtDeriCrteReqMsg67000 package. TheCrdtPrtfoModFSInDatCrdtDeriCrteReqMsg67000 package includes aCrdtPrtfoModFSInDatCrdtDeriCrteReqMsg67002 entity. TheCrdtPrtfoModFSInDatCrdtDeriCrteReqMsg67000 package includes various packages, namely aMessageHeader67004 and aCreditPortfolioModel67010.

TheMessageHeader67004 package includes aMessageHeader67006 entity. TheMessageHeader67006 entity has a cardinality of 167008 meaning that for each instance of theMessageHeader67004 package there is oneMessageHeader67006 entity.

TheCreditPortfolioModel67010 package includes aCreditPortfolioModel67012 entity. TheCreditPortfolioModel67010 package includes anInputData67036 package. TheCreditPortfolioModel67012 entity has a cardinality of 167014 meaning that for each instance of theCreditPortfolioModel67010 package there is oneCreditPortfolioModel67012 entity. TheCreditPortfolioModel67012 entity includes anID67016 attribute. TheCreditPortfolioModel67012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl67020 and aCreditPortfolio67028. TheID67016 attribute has a cardinality of 167018 meaning that for each instance of theCreditPortfolioModel67012 entity there is oneID67016 attribute.

TheCreditPortfolioManagementProcessControl67020 entity has a cardinality of 167022 meaning that for each instance of theCreditPortfolioModel67012 entity there is oneCreditPortfolioManagementProcessControl67020 entity. TheCreditPortfolioManagementProcessControl67020 entity includes aDataTransferID67024 attribute. TheDataTransferID67024 attribute has a cardinality of 167026 meaning that for each instance of theCreditPortfolioManagementProcessControl67020 entity there is oneDataTransferID67024 attribute.

TheCreditPortfolio67028 entity has a cardinality of 167030 meaning that for each instance of theCreditPortfolioModel67012 entity there is oneCreditPortfolio67028 entity. TheCreditPortfolio67028 entity includes anID67032 attribute. TheID67032 attribute has a cardinality of 167034 meaning that for each instance of theCreditPortfolio67028 entity there is oneID67032 attribute.

TheInputData67036 package includes anInputData67038 entity. TheInputData67036 package includes aCreditDerivative67040 package.

TheCreditDerivative67040 package includes aCreditDerivative67042 entity. TheCreditDerivative67040 package includes various packages, namely aCounterparty67084, aGuarantorParty67094, aCreditExposureData67106, aReferenceAssetItem67170, aFinancialCondition67222, aProbabilityOfDefault67294, aRating67312, aSpreadCurve67350 and aProperty67372.

TheCounterparty67084 package includes aCounterparty67086 entity. TheCounterparty67086 entity has a cardinality of 167088 meaning that for each instance of theCounterparty67084 package there is oneCounterparty67086 entity. TheCounterparty67086 entity includes anInternalID67090 attribute. TheInternalID67090 attribute has a cardinality of 167092 meaning that for each instance of theCounterparty67086 entity there is oneInternalID67090 attribute.

TheGuarantorParty67094 package includes aGuarantorParty67096 entity. TheGuarantorParty67096 entity has a cardinality of 0..167098 meaning that for each instance of theGuarantorParty67094 package there may be one GuarantorParty67096 entity. TheGuarantorParty67096 entity includes anInternalID67100 attribute. TheInternalID67100 attribute has a cardinality of 0..167102 meaning that for each instance of theGuarantorParty67096 entity there may be oneInternalID67100 attribute.

ThePriceAtHorizon67128 entity has a cardinality of 0..167130 meaning that for each instance of theCreditExposureData67108 entity there may be onePriceAtHorizon67128 entity. ThePriceAtHorizon67128 entity includes various attributes, namely aDuration67132, anAmount67136 and aDecimalValue67140. TheDuration67132 attribute has a cardinality of 0..167134 meaning that for each instance of thePriceAtHorizon67128 entity there may be oneDuration67132 attribute. TheAmount67136 attribute has a cardinality of 0..167138 meaning that for each instance of thePriceAtHorizon67128 entity there may be oneAmount67136 attribute. TheDecimalValue67140 attribute has a cardinality of 0..167142 meaning that for each instance of thePriceAtHorizon67128 entity there may be one DecimalValue67140 attribute.

TheCurrentPrice67144 entity includes various attributes, namely aDuration67146, anAmount67150 and aDecimalValue67154. TheDuration67146 attribute has a cardinality of 0..167148 meaning that for each instance of theCurrentPrice67144 entity there may be oneDuration67146 attribute. TheAmount67150 attribute has a cardinality of 0..167152 meaning that for each instance of theCurrentPrice67144 entity there may be oneAmount67150 attribute. TheDecimalValue67154 attribute has a cardinality of 0..167156 meaning that for each instance of theCurrentPrice67144 entity there may be one DecimalValue67154 attribute.

TheCounterparty67184 entity has a cardinality of 167186 meaning that for each instance of theReferenceAssetItem67172 entity there is oneCounterparty67184 entity. TheCounterparty67184 entity includes anInternalID67188 attribute. TheInternalID67188 attribute has a cardinality of 167190 meaning that for each instance of theCounterparty67184 entity there is oneInternalID67188 attribute.

TheGuarantorParty67194 entity has a cardinality of 0..167196 meaning that for each instance of theReferenceAssetItem67172 entity there may be one GuarantorParty67194 entity. TheGuarantorParty67194 entity includes anInternalID67198 attribute. TheInternalID67198 attribute has a cardinality of 0..167200 meaning that for each instance of theGuarantorParty67194 entity there may be oneInternalID67198 attribute.

TheCreditExposureData67202 entity has a cardinality of 167204 meaning that for each instance of theReferenceAssetItem67172 entity there is oneCreditExposureData67202 entity. TheCreditExposureData67202 entity includes various attributes, namely aLossGivenDefaultDecimalValue67206, aShapeBetaDistributionDecimalValue67210, anExpectedLossGivenDefaultDecimalValue67214 and aSeniorityCode67218. TheLossGivenDefaultDecimalValue67206 attribute has a cardinality of 0..167208 meaning that for each instance of theCreditExposureData67202 entity there may be one LossGivenDefaultDecimalValue67206 attribute. TheShapeBetaDistributionDecimalValue67210 attribute has a cardinality of 0..167212 meaning that for each instance of theCreditExposureData67202 entity there may be one ShapeBetaDistributionDecimalValue67210 attribute. TheExpectedLossGivenDefaultDecimalValue67214 attribute has a cardinality of 0..167216 meaning that for each instance of theCreditExposureData67202 entity there may be one ExpectedLossGivenDefaultDecimalValue67214 attribute. TheSeniorityCode67218 attribute has a cardinality of 0..167220 meaning that for each instance of theCreditExposureData67202 entity there may be oneSeniorityCode67218 attribute.

TheFinancialCondition67222 package includes aFinancialCondition67224 entity. TheFinancialCondition67224 entity includes various subordinate entities, namely anInterestCondition67226, aFeeCondition67258 and aPaymentCondition67276. TheInterestCondition67226 entity includes aBankContractFinancialConditionSpecification67228 subordinate entity. TheBankContractFinancialConditionSpecification67228 entity includes various subordinate entities, namely aCalculation67232, anAmountSpecification67238 and anInterestSpecification67244. TheCalculation67232 entity includes aRecurrenceSpecification67234 subordinate entity. TheInterestSpecification67244 entity includes aVariableInterest67248 subordinate entity. TheFeeCondition67258 entity includes aBankContractFinancialConditionSpecification67260 subordinate entity. TheBankContractFinancialConditionSpecification67260 entity includes various subordinate entities, namely aCalculation67264 and anAmountSpecification67270. TheCalculation67264 entity includes aRecurrenceSpecification67266 subordinate entity. ThePaymentCondition67276 entity includes aBankContractFinancialConditionSpecification67278 subordinate entity. TheBankContractFinancialConditionSpecification67278 entity includes various subordinate entities, namely aCalculation67282 and anAmountSpecification67288. TheCalculation67282 entity includes aRecurrenceSpecification67284 subordinate entity.

TheProbabilityOfDefault67294 package includes aProbabilityOfDefault67296 entity. TheProbabilityOfDefault67296 entity has a cardinality of 0..n67298 meaning that for each instance of theProbabilityOfDefault67294 package there may be one or more ProbabilityOfDefault67296 entities. TheProbabilityOfDefault67296 entity includes various attributes, namely aValidityDatePeriod67300, aCode67304 and aDoubleValue67308. TheValidityDatePeriod67300 attribute has a cardinality of 167302 meaning that for each instance of theProbabilityOfDefault67296 entity there is oneValidityDatePeriod67300 attribute. TheCode67304 attribute has a cardinality of 167306 meaning that for each instance of theProbabilityOfDefault67296 entity there is oneCode67304 attribute. TheDoubleValue67308 attribute has a cardinality of 167310 meaning that for each instance of theProbabilityOfDefault67296 entity there is oneDoubleValue67308 attribute.

TheSpreadCurve67350 package includes aSpreadCurve67352 entity. TheSpreadCurve67352 entity has a cardinality of 0..167354 meaning that for each instance of theSpreadCurve67350 package there may be one SpreadCurve67352 entity. TheSpreadCurve67352 entity includes anItem67356 subordinate entity.

TheItem67356 entity has a cardinality of 1..n67358 meaning that for each instance of theSpreadCurve67352 entity there are one ormore Item67356 entities. TheItem67356 entity includes various attributes, namely aValidityDate67360, aDuration67364 and aSpreadDoubleValue67368. TheValidityDate67360 attribute has a cardinality of 167362 meaning that for each instance of theItem67356 entity there is oneValidityDate67360 attribute. TheDuration67364 attribute has a cardinality of 167366 meaning that for each instance of theItem67356 entity there is oneDuration67364 attribute. TheSpreadDoubleValue67368 attribute has a cardinality of 167370 meaning that for each instance of theItem67356 entity there is oneSpreadDoubleValue67368 attribute.

TheProperty67372 package includes aProperty67374 entity. TheProperty67374 entity has a cardinality of 0..n67376 meaning that for each instance of theProperty67372 package there may be one ormore Property67374 entities. TheProperty67374 entity includes various attributes, namely anID67378 and aValue67382. TheID67378 attribute has a cardinality of 167380 meaning that for each instance of theProperty67374 entity there is oneID67378 attribute. TheValue67382 attribute has a cardinality of 167384 meaning that for each instance of theProperty67374 entity there is oneValue67382 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 68-1 through68-5 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatPrtfoAnlysDatCrteReqMsg68000 package. TheCrdtPrtfoModFSInDatPrtfoAnlysDatCrteReqMsg68000 package includes aCrdtPrtfoModFSInDatPrtfoAnlysDatCrteReqMsg68002 entity. TheCrdtPrtfoModFSInDatPrtfoAnlysDatCrteReqMsg68000 package includes various packages, namely aMessageHeader68004 and aCreditPortfolioModel68010.

TheMessageHeader68004 package includes aMessageHeader68006 entity. TheMessageHeader68006 entity has a cardinality of 168008 meaning that for each instance of theMessageHeader68004 package there is oneMessageHeader68006 entity.

The CreditPortfolio68024 entity has a cardinality of 168026 meaning that for each instance of the CreditPortfolioModel68012 entity there is one CreditPortfolio68024 entity. The CreditPortfolio68024 entity includes anID68028 attribute. TheID68028 attribute has a cardinality of 168030 meaning that for each instance of the CreditPortfolio68024 entity there is oneID68028 attribute.

The InputData68032 package includes an InputData68034 entity. The InputData68032 package includes a PortfolioAnalysisData68038 package. The InputData68034 entity has a cardinality of 168036 meaning that for each instance of the InputData68032 package there is one InputData68034 entity.

The PortfolioAnalysisData68038 package includes a PortfolioAnalysisData68040 entity. The PortfolioAnalysisData68038 package includes various packages, namely a FinancialInstrumentExposure68056 and aProperty68082. The PortfolioAnalysisData68040 entity has a cardinality of 168042 meaning that for each instance of the PortfolioAnalysisData68038 package there is one PortfolioAnalysisData68040 entity. The PortfolioAnalysisData68040 entity includes anID68044 attribute. The PortfolioAnalysisData68040 entity includes aCreditPortfolioAssignment68050 subordinate entity. TheID68044 attribute has a cardinality of 168046 meaning that for each instance of thePortfolioAnalysisData68040 entity there is oneID68044 attribute.

TheCreditPortfolioAssignment68050 entity has a cardinality of 168052 meaning that for each instance of the PortfolioAnalysisData68040 entity there is oneCreditPortfolioAssignment68050 entity.

TheProperty68082 package includes aProperty68084 entity. TheProperty68084 entity has a cardinality of 0..n68086 meaning that for each instance of theProperty68082 package there may be one ormore Property68084 entities. TheProperty68084 entity includes various attributes, namely anID68088 and aValue68092. TheID68088 attribute has a cardinality of 168090 meaning that for each instance of theProperty68084 entity there is oneID68088 attribute. TheValue68092 attribute has a cardinality of 168094 meaning that for each instance of theProperty68084 entity there is oneValue68092 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 69-1 through69-3 show an example configuration of an Element Structure that includes a CrdtPrtfoModFSInDatYldCrvCrteReqMsg69000 package. The CrdtPrtfoModFSInDatYldCrvCrteReqMsg69000 package includes a CrdtPrtfoModFSInDatYldCrvCrteReqMsg69002 entity. The CrdtPrtfoModFSInDatYldCrvCrteReqMsg69000 package includes various packages, namely aMessageHeader69004 and a CreditPortfolioModel69010.

The MessageHeader69004 package includes aMessageHeader69006 entity. TheMessageHeader69006 entity has a cardinality of 169008 meaning that for each instance of theMessageHeader69004 package there is oneMessageHeader69006 entity.

The CreditPortfolioManagementProcessControl69020 entity has a cardinality of 169022 meaning that for each instance of the CreditPortfolioModel69012 entity there is one CreditPortfolioManagementProcessControl69020 entity. The CreditPortfolioManagementProcessControl69020 entity includes a DataTransferID69024 attribute. The DataTransferID69024 attribute has a cardinality of 169026 meaning that for each instance of the CreditPortfolioManagementProcessControl69020 entity there is oneDataTransferID69024 attribute.

The CreditPortfolio69028 entity has a cardinality of 169030 meaning that for each instance of the CreditPortfolioModel69012 entity there is one CreditPortfolio69028 entity. The CreditPortfolio69028 entity includes anID69032 attribute. TheID69032 attribute has a cardinality of 169034 meaning that for each instance of the CreditPortfolio69028 entity there is oneID69032 attribute.

The InputData69036 package includes an InputData69038 entity. The InputData69036 package includes a YieldCurve69042 package. The InputData69038 entity has a cardinality of 169040 meaning that for each instance of the InputData69036 package there is one InputData69038 entity.

The YieldCurve69042 package includes a YieldCurve69044 entity. The YieldCurve69042 package includes anItem69058 package. The YieldCurve69044 entity has a cardinality of 169046 meaning that for each instance of the YieldCurve69042 package there is one YieldCurve69044 entity. The YieldCurve69044 entity includes various attributes, namely anID69048 and a VailidityDate69054. TheID69048 attribute has a cardinality of 169050 meaning that for each instance of the YieldCurve69044 entity there is oneID69048 attribute. The VailidityDate69054 attribute has a cardinality of 169056 meaning that for each instance of the YieldCurve69044 entity there is one VailidityDate69054 attribute.

TheItem69058 package includes anItem69060 entity. TheItem69060 entity has a cardinality of 1..n69062 meaning that for each instance of theItem69058 package there are one ormore Item69060 entities. TheItem69060 entity includes various attributes, namely aTenorDuration69064 and an InterestRateDoubleValue69068. TheTenorDuration69064 attribute has a cardinality of 169066 meaning that for each instance of theItem69060 entity there is oneTenorDuration69064 attribute. The InterestRateDoubleValue69068 attribute has a cardinality of 169070 meaning that for each instance of theItem69060 entity there is one InterestRateDoubleValue69068 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 70-1 through70-3 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatExchRateCrteReqMsg70000 package. TheCrdtPrtfoModFSInDatExchRateCrteReqMsg70000 package includes aCreditPortfolioModelFSInputDataExchangeRateRequestMessage70002 entity. TheCrdtPrtfoModFSInDatExchRateCrteReqMsg70000 package includes various packages, namely aMessageHeader70004 and aCreditPortfolioModel70010.

TheMessageHeader70004 package includes aMessageHeader70006 entity. TheMessageHeader70006 entity has a cardinality of 170008 meaning that for each instance of theMessageHeader70004 package there is oneMessageHeader70006 entity.

TheCreditPortfolioModel70010 package includes aCreditPortfolioModel70012 entity. TheCreditPortfolioModel70010 package includes anInputData70036 package. TheCreditPortfolioModel70012 entity has a cardinality of 170014 meaning that for each instance of theCreditPortfolioModel70010 package there is oneCreditPortfolioModel70012 entity. TheCreditPortfolioModel70012 entity includes anID70016 attribute. TheCreditPortfolioModel70012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl70020 and aCreditPortfolio70028. TheID70016 attribute has a cardinality of 170018 meaning that for each instance of theCreditPortfolioModel70012 entity there is oneID70016 attribute.

TheCreditPortfolioManagementProcessControl70020 entity has a cardinality of 170022 meaning that for each instance of theCreditPortfolioModel70012 entity there is oneCreditPortfolioManagementProcessControl70020 entity. TheCreditPortfolioManagementProcessControl70020 entity includes aDataTransferID70024 attribute. TheDataTransferID70024 attribute has a cardinality of 170026 meaning that for each instance of theCreditPortfolioManagementProcessControl70020 entity there is oneDataTransferID70024 attribute.

TheCreditPortfolio70028 entity has a cardinality of 170030 meaning that for each instance of theCreditPortfolioModel70012 entity there is oneCreditPortfolio70028 entity. TheCreditPortfolio70028 entity includes anID70032 attribute. TheID70032 attribute has a cardinality of 170034 meaning that for each instance of theCreditPortfolio70028 entity there is oneID70032 attribute.

TheInputData70036 package includes anInputData70038 entity. TheInputData70036 package includes anExchangeRateItem70042 package.

TheInputData70038 entity has a cardinality of 170040 meaning that for each instance of theInputData70036 package there is oneInputData70038 entity.

TheExchangeRateItem70042 package includes anExchangeRateItem70044 entity. TheExchangeRateItem70044 entity has a cardinality of 1..n70046 meaning that for each instance of theExchangeRateItem70042 package there are one or more ExchangeRateItem70044 entities. TheExchangeRateItem70044 entity includes various attributes, namely anID70048, aValidityDate70052 and anExchangeRate70056. TheID70048 attribute has a cardinality of 170050 meaning that for each instance of theExchangeRateItem70044 entity there is oneID70048 attribute. TheValidityDate70052 attribute has a cardinality of 170054 meaning that for each instance of theExchangeRateItem70044 entity there is oneValidityDate70052 attribute. TheExchangeRate70056 attribute has a cardinality of 170058 meaning that for each instance of theExchangeRateItem70044 entity there is oneExchangeRate70056 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 71-1 through71-4 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatPDClbrtMtxCrteReqMsg71000 package. TheCrdtPrtfoModFSInDatPDClbrtMtxCrteReqMsg71000 package includes aCrdtPrtfoModFSInDatPDClbrtMtxCrteReqMsg71002 entity. TheCrdtPrtfoModFSInDatPDClbrtMtxCrteReqMsg71000 package includes various packages, namely a MessageHeader7l004 and aCreditPortfolioModel71010.

TheMessageHeader71004 package includes aMessageHeader71006 entity. TheMessageHeader71006 entity has a cardinality of 171008 meaning that for each instance of theMessageHeader71004 package there is oneMessageHeader71006 entity.

TheCreditPortfolioModel71010 package includes aCreditPortfolioModel71012 entity. TheCreditPortfolioModel71010 package includes anInputData71036 package. TheCreditPortfolioModel71012 entity has a cardinality of 171014 meaning that for each instance of theCreditPortfolioModel71010 package there is oneCreditPortfolioModel71012 entity. TheCreditPortfolioModel71012 entity includes anID71016 attribute. TheCreditPortfolioModel71012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl71020 and aCreditPortfolio71028. TheID71016 attribute has a cardinality of 171018 meaning that for each instance of theCreditPortfolioModel71012 entity there is one ID71016 attribute.

TheCreditPortfolioManagementProcessControl71020 entity has a cardinality of 171022 meaning that for each instance of theCreditPortfolioModel71012 entity there is oneCreditPortfolioManagementProcessControl71020 entity. TheCreditPortfolioManagementProcessControl71020 entity includes aDataTransferID71024 attribute. TheDataTransferID71024 attribute has a cardinality of 171026 meaning that for each instance of theCreditPortfolioManagementProcessControl71020 entity there is oneDataTransferID71024 attribute.

TheCreditPortfolio71028 entity has a cardinality of 171030 meaning that for each instance of theCreditPortfolioModel71012 entity there is oneCreditPortfolio71028 entity. TheCreditPortfolio71028 entity includes anID71032 attribute. TheID71032 attribute has a cardinality of 171034 meaning that for each instance of theCreditPortfolio71028 entity there is oneID71032 attribute.

TheInputData71036 package includes anInputData71038 entity. TheInputData71036 package includes aProbabilityOfDefaultCalibrationMatrix71042 package. TheInputData71038 entity has a cardinality of 171040 meaning that for each instance of theInputData71036 package there is oneInputData71038 entity.

TheItem71060 package includes anItem71062 entity. TheItem71062 entity has a cardinality of 1..n71064 meaning that for each instance of theItem71060 package there are one or more Item71062 entities. TheItem71062 entity includes aCreditRatingCode71066 attribute. TheItem71062 entity includes aProbabilityOfDefault71070 subordinate entity. TheCreditRatingCode71066 attribute has a cardinality of 171068 meaning that for each instance of theItem71062 entity there is oneCreditRatingCode71066 attribute.

TheProbabilityOfDefault71070 entity has a cardinality of 1..n71072 meaning that for each instance of theItem71062 entity there is one or more ProbabilityOfDefault71070 entities. TheProbabilityOfDefault71070 entity includes various attributes, namely aTermDuration71074 and aDoubleValue71078. TheTermDuration71074 attribute has a cardinality of 171076 meaning that for each instance of theProbabilityOfDefault71070 entity there is oneTermDuration71074 attribute. TheDoubleValue71078 attribute has a cardinality of 171080 meaning that for each instance of theProbabilityOfDefault71070 entity there is oneDoubleValue71078 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 72-1 through72-4 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatCrdtSprdCrteReqMsg72000 package. TheCrdtPrtfoModFSInDatCrdtSprdCrteReqMsg72000 package includes aCrdtPrtfoModFSInDatCrdtSprdCrteReqMsg72002 entity. TheCrdtPrtfoModFSInDatCrdtSprdCrteReqMsg72000 package includes various packages, namely aMessageHeader72004 and aCreditPortfolioModel72010.

TheMessageHeader72004 package includes aMessageHeader72006 entity. TheMessageHeader72006 entity has a cardinality of 172008 meaning that for each instance of theMessageHeader72004 package there is oneMessageHeader72006 entity.

TheCreditPortfolioModel72010 package includes aCreditPortfolioModel72012 entity. TheCreditPortfolioModel72010 package includes anInputData72034 package. TheCreditPortfolioModel72012 entity has a cardinality of 172014 meaning that for each instance of theCreditPortfolioModel72010 package there is oneCreditPortfolioModel72012 entity. TheCreditPortfolioModel72012 entity includes anID72016 attribute. TheCreditPortfolioModel72012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl72020 and aCreditPortfolio72026. TheID72016 attribute has a cardinality of 172018 meaning that for each instance of theCreditPortfolioModel72012 entity there is oneID72016 attribute.

TheCreditPortfolioManagementProcessControl72020 entity includes aDataTransferID72022 attribute. TheDataTransferID72022 attribute has a cardinality of 172024 meaning that for each instance of theCreditPortfolioManagementProcessControl72020 entity there is oneDataTransferID72022 attribute.

TheCreditPortfolio72026 entity has a cardinality of 172028 meaning that for each instance of theCreditPortfolioModel72012 entity there is oneCreditPortfolio72026 entity. TheCreditPortfolio72026 entity includes anID72030 attribute. TheID72030 attribute has a cardinality of 172032 meaning that for each instance of theCreditPortfolio72026 entity there is oneID72030 attribute.

TheInputData72034 package includes anInputData72036 entity. TheInputData72034 package includes aCreditSpreadMatrix72040 package. TheInputData72036 entity has a cardinality of 172038 meaning that for each instance of theInputData72034 package there is oneInputData72036 entity.

TheItem72058 entity has a cardinality of 1..n72060 meaning that for each instance of theCreditSpreadMatrix72042 entity there are one ormore Item72058 entities. TheItem72062 package includes various entities, namely aCreditRatingCode72064, aYieldCurveModelID72068 and aCreditSpread72070.

TheCreditRatingCode72064 entity has a cardinality of 172066 meaning that for each instance of theItem72062 package there is oneCreditRatingCode72064 entity. TheCreditSpread72070 entity has a cardinality of 1..n72072 meaning that for each instance of theItem72062 package there are one ormore CreditSpread72070 entities. TheCreditSpread72070 entity includes various attributes, namely aTermDuration72074 and aDecimalValue72078. TheTermDuration72074 attribute has a cardinality of 172076 meaning that for each instance of theCreditSpread72070 entity there is oneTermDuration72074 attribute. TheDecimalValue72078 attribute has a cardinality of 172080 meaning that for each instance of theCreditSpread72070 entity there is oneDecimalValue72078 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 73-1 through73-3 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatRatgMtxCrteReqMsg73000 package. TheCrdtPrtfoModFSInDatRatgMtxCrteReqMsg73000 package includes aCrdtPrtfoModFSInDatRatgMtxCrteReqMsg73002 entity. TheCrdtPrtfoModFSInDatRatgMtxCrteReqMsg73000 package includes various packages, namely aMessageHeader73004 and aCreditPortfolioModel73010.

TheMessageHeader73004 package includes aMessageHeader73006 entity. TheMessageHeader73006 entity has a cardinality of 173008 meaning that for each instance of theMessageHeader73004 package there is oneMessageHeader73006 entity.

TheCreditPortfolioModel73010 package includes aCreditPortfolioModel73012 entity. TheCreditPortfolioModel73010 package includes anInputData73036 package. TheCreditPortfolioModel73012 entity has a cardinality of 173014 meaning that for each instance of theCreditPortfolioModel73010 package there is oneCreditPortfolioModel73012 entity. TheCreditPortfolioModel73012 entity includes anID73016 attribute. TheCreditPortfolioModel73012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl73020 and aCreditPortfolio73028. TheID73016 attribute has a cardinality of 173018 meaning that for each instance of theCreditPortfolioModel73012 entity there is oneID73016 attribute.

TheCreditPortfolioManagementProcessControl73020 entity has a cardinality of 173022 meaning that for each instance of theCreditPortfolioModel73012 entity there is oneCreditPortfolioManagementProcessControl73020 entity. TheCreditPortfolioManagementProcessControl73020 entity includes aDataTransferID73024 attribute. TheDataTransferID73024 attribute has a cardinality of 173026 meaning that for each instance of theCreditPortfolioManagementProcessControl73020 entity there is oneDataTransferID73024 attribute.

TheCreditPortfolio73028 entity has a cardinality of 173030 meaning that for each instance of theCreditPortfolioModel73012 entity there is oneCreditPortfolio73028 entity. TheCreditPortfolio73028 entity includes anID73032 attribute. TheID73032 attribute has a cardinality of 173034 meaning that for each instance of theCreditPortfolio73028 entity there is oneID73032 attribute. TheInputData73036 package includes anInputData73038 entity. TheInputData73036 package includes aRatingTransitionMatrix73040 package.

TheItem73058 package includes anItem73060 entity. TheItem73060 entity has a cardinality of 1..n73062 meaning that for each instance of theItem73058 package there are one ormore Item73060 entities. TheItem73060 entity includes various attributes, namely aPeriodBeginCreditRatingCode73064, aPeriodEndCreditRatingCode73068 and aProbabilityOfFransitionDoubleValue73072. ThePeriodBeginCreditRatingCode73064 attribute has a cardinality of 173066 meaning that for each instance of theItem73060 entity there is onePeriodBeginCreditRatingCode73064 attribute. ThePeriodEndCreditRatingCode73068 attribute has a cardinality of 173070 meaning that for each instance of theItem73060 entity there is onePeriodEndCreditRatingCode73068 attribute. TheProbabilityOfFransitionDoubleValue73072 attribute has a cardinality of 173074 meaning that for each instance of theItem73060 entity there is oneProbabilityOfFransitionDoubleValue73072 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 74-1 through74-10 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatOTCDeriCrteReqMsg74000 package. TheCrdtPrtfoModFSInDatOTCDeriCrteReqMsg74000 package includes aCrdtPrtfoModFSInDatOTCDeriCrteReqMsg74002 entity. TheCrdtPrtfoModFSInDatOTCDeriCrteReqMsg74000 package includes various packages, namely aMessageHeader74004 and aCreditPortfolioModel74010.

TheMessageHeader74004 package includes aMessageHeader74006 entity. TheMessageHeader74006 entity has a cardinality of 174008 meaning that for each instance of theMessageHeader74004 package there is oneMessageHeader74006 entity.

TheCreditPortfolioModel74010 package includes aCreditPortfolioModel74012 entity. TheCreditPortfolioModel74010 package includes anInputData74036 package. TheCreditPortfolioModel74012 entity has a cardinality of 174014 meaning that for each instance of theCreditPortfolioModel74010 package there is oneCreditPortfolioModel74012 entity. TheCreditPortfolioModel74012 entity includes anID74016 attribute. TheCreditPortfolioModel74012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl74020 and aCreditPortfolio74028. TheID74016 attribute has a cardinality of 174018 meaning that for each instance of theCreditPortfolioModel74012 entity there is oneID74016 attribute.

TheCreditPortfolioManagementProcessControl74020 entity has a cardinality of 174022 meaning that for each instance of theCreditPortfolioModel74012 entity there is oneCreditPortfolioManagementProcessControl74020 entity. TheCreditPortfolioManagementProcessControl74020 entity includes aDataTransferID74024 attribute. TheDataTransferID74024 attribute has a cardinality of 174026 meaning that for each instance of theCreditPortfolioManagementProcessControl74020 entity there is oneDataTransferID74024 attribute.

TheCreditPortfolio74028 entity has a cardinality of 174030 meaning that for each instance of theCreditPortfolioModel74012 entity there is oneCreditPortfolio74028 entity. TheCreditPortfolio74028 entity includes anID74032 attribute. TheID74032 attribute has a cardinality of 174034 meaning that for each instance of theCreditPortfolio74028 entity there is oneID74032 attribute.

TheInputData74036 package includes anInputData74038 entity. TheInputData74036 package includes anOTCDerivative74042 package. TheInputData74038 entity has a cardinality of 174040 meaning that for each instance of theInputData74036 package there is oneInputData74038 entity.

TheCounterparty74068 package includes aCounterparty74070 entity. TheCounterparty74070 entity has a cardinality of 174072 meaning that for each instance of theCounterparty74068 package there is oneCounterparty74070 entity. TheCounterparty74070 entity includes anInternalID74074 attribute. TheInternalID74074 attribute has a cardinality of 174076 meaning that for each instance of theCounterparty74070 entity there is oneInternalID74074 attribute.

TheGuarantorParty74080 package includes aGuarantorParty74082 entity. TheGuarantorParty74082 entity has a cardinality of 0..174084 meaning that for each instance of theGuarantorParty74080 package there may be one GuarantorParty74082 entity. TheGuarantorParty74082 entity includes anInternalID74086 attribute. TheInternalID74086 attribute has a cardinality of 0..174088 meaning that for each instance of theGuarantorParty74082 entity there may be oneInternalID74086 attribute.

ThePriceAtHorizon74112 entity has a cardinality of 0..174114 meaning that for each instance of theCreditExposureData74092 entity there may be onePriceAtHorizon74112 entity. ThePriceAtHorizon74112 entity includes various attributes, namely aDuration74116, anAmount74120 and aDecimalValue74124. TheDuration74116 attribute has a cardinality of 0..174118 meaning that for each instance of thePriceAtHorizon74112 entity there may be oneDuration74116 attribute. TheAmount74120 attribute has a cardinality of 0..174122 meaning that for each instance of thePriceAtHorizon74112 entity there may be oneAmount74120 attribute. TheDecimalValue74124 attribute has a cardinality of 0..174126 meaning that for each instance of thePriceAtHorizon74112 entity there may be one DecimalValue74124 attribute.

TheCurrentPrice74128 entity includes various attributes, namely aDuration74130, anAmount74134 and aDecimalValue74138. TheDuration74130 attribute has a cardinality of 0..174132 meaning that for each instance of theCurrentPrice74128 entity there may be oneDuration74130 attribute. TheAmount74134 attribute has a cardinality of 0..174136 meaning that for each instance of theCurrentPrice74128 entity there may be oneAmount74134 attribute. TheDecimalValue74138 attribute has a cardinality of 0..174140 meaning that for each instance of theCurrentPrice74128 entity there may be one DecimalValue74138 attribute.

TheProbabilityOfDefault74146 package includes aProbabilityOfDefault74148 entity. TheProbabilityOfDefault74148 entity has a cardinality of 0..n74150 meaning that for each instance of theProbabilityOfDefault74146 package there may be one or more ProbabilityOfDefault74148 entities. TheProbabilityOfDefault74148 entity includes various attributes, namely aValidityDatePeriod74152, aCode74156 and aDoubleValue74160. TheValidityDatePeriod74152 attribute has a cardinality of 174154 meaning that for each instance of theProbabilityOfDefault74148 entity there is oneValidityDatePeriod74152 attribute. TheCode74156 attribute has a cardinality of 174158 meaning that for each instance of theProbabilityOfDefault74148 entity there is oneCode74156 attribute. TheDoubleValue74160 attribute has a cardinality of 174162 meaning that for each instance of theProbabilityOfDefault74148 entity there is oneDoubleValue74160 attribute.

TheExposureProfile74202 package includes anExposureProfile74204 entity. TheExposureProfile74204 entity has a cardinality of 0..174206 meaning that for each instance of theExposureProfile74202 package there may be one ExposureProfile74204 entity. TheExposureProfile74204 entity includes anItem74208 subordinate entity.

TheItem74208 entity has a cardinality of 0..n74210 meaning that for each instance of theExposureProfile74204 entity there may be one ormore Item74208 entities. TheItem74208 entity includes various attributes, namely aDate74212, aNegativeExposureAmount74216 and aPositiveExposureAmount74220. TheDate74212 attribute has a cardinality of 174214 meaning that for each instance of theItem74208 entity there is oneDate74212 attribute. TheNegativeExposureAmount74216 attribute has a cardinality of 0..174218 meaning that for each instance of theItem74208 entity there may be one NegativeExposureAmount74216 attribute. ThePositiveExposureAmount74220 attribute has a cardinality of 0..174222 meaning that for each instance of theItem74208 entity there may be one PositiveExposureAmount74220 attribute.

TheRiskFreeProfile74224 package includes aRiskFreeProfile74226 entity. TheRiskFreeProfile74226 entity has a cardinality of 0..174228 meaning that for each instance of theRiskFreeProfile74224 package there may be one RiskFreeProfile74226 entity. TheRiskFreeProfile74226 entity includes anItem74230 subordinate entity.

TheItem74230 entity has a cardinality of 0..n74232 meaning that for each instance of theRiskFreeProfile74226 entity there may be one ormore Item74230 entities. TheItem74230 entity includes various attributes, namely aDate74234 and aRiskFreeAmount74238. TheDate74234 attribute has a cardinality of 174236 meaning that for each instance of theItem74230 entity there is oneDate74234 attribute. TheRiskFreeAmount74238 attribute has a cardinality of 174240 meaning that for each instance of theItem74230 entity there is oneRiskFreeAmount74238 attribute.

TheProperty74242 package includes aProperty74244 entity. TheProperty74244 entity has a cardinality of 0..n74246 meaning that for each instance of theProperty74242 package there may be one ormore Property74244 entities. TheProperty74244 entity includes various attributes, namely anID74248 and aValue74252. TheID74248 attribute has a cardinality of 174250 meaning that for each instance of theProperty74244 entity there is oneID74248 attribute. TheValue74252 attribute has a cardinality of 174254 meaning that for each instance of theProperty74244 entity there is oneValue74252 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 75-1 through75-11 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatSecFTCrteReqMsg75000 package. TheCrdtPrtfoModFSInDatSecFTCrteReqMsg75000 package includes aCrdtPrtfoModFSInDatSecFTCrteReqMsg75002 entity. TheCrdtPrtfoModFSInDatSecFTCrteReqMsg75000 package includes various packages, namely aMessageHeader75004 and aCreditPortfolioModel75010.

TheMessageHeader75004 package includes aMessageHeader75006 entity. TheMessageHeader75006 entity has a cardinality of 175008 meaning that for each instance of theMessageHeader75004 package there is oneMessageHeader75006 entity.

TheCreditPortfolioModel75010 package includes aCreditPortfolioModel75012 entity. TheCreditPortfolioModel75010 package includes anInputData75036 package. TheCreditPortfolioModel75012 entity has a cardinality of 175014 meaning that for each instance of theCreditPortfolioModel75010 package there is oneCreditPortfolioModel75012 entity. TheCreditPortfolioModel75012 entity includes anID75016 attribute. TheCreditPortfolioModel75012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl75020 and aCreditPortfolio75028. TheID75016 attribute has a cardinality of 175018 meaning that for each instance of theCreditPortfolioModel75012 entity there is oneID75016 attribute.

TheCreditPortfolioManagementProcessControl75020 entity has a cardinality of 175022 meaning that for each instance of theCreditPortfolioModel75012 entity there is oneCreditPortfolioManagementProcessControl75020 entity. TheCreditPortfolioManagementProcessControl75020 entity includes aDataTransferID75024 attribute. TheDataTransferID75024 attribute has a cardinality of 175026 meaning that for each instance of theCreditPortfolioManagementProcessControl75020 entity there is oneDataTransferID75024 attribute.

TheCreditPortfolio75028 entity has a cardinality of 175030 meaning that for each instance of theCreditPortfolioModel75012 entity there is oneCreditPortfolio75028 entity. TheCreditPortfolio75028 entity includes anID75032 attribute. TheID75032 attribute has a cardinality of 175034 meaning that for each instance of theCreditPortfolio75028 entity there is oneID75032 attribute.

TheInputData75036 package includes anInputData75038 entity. TheInputData75036 package includes aSecuritiesFinancingTransaction75042 package. TheInputData75038 entity has a cardinality of 175040 meaning that for each instance of theInputData75036 package there is oneInputData75038 entity.

TheSecuritiesFinancingTransaction75042 package includes aSecuritiesFinancingTransaction75044 entity. TheSecuritiesFinancingTransaction75042 package includes various packages, namely aCounterparty75068, aGuarantorParty75080, aCreditExposureData75090, aProbabilityOfDefault75146, aRating75164, anExposureProfile75202, aRiskFreeProfile75224 and aProperty75242.

TheSecuritiesFinancingTransaction75044 entity has a cardinality of 175046 meaning that for each instance of theSecuritiesFinancingTransaction75042 package there is oneSecuritiesFinancingTransaction75044 entity. TheSecuritiesFinancingTransaction75044 entity includes various attributes, namely anID75048, aGuaranteeID75052, aDescription75056, aCurrencyCode75060 and aValidityPeriod75064. TheID75048 attribute has a cardinality of 175050 meaning that for each instance of theSecuritiesFinancingTransaction75044 entity there is oneID75048 attribute. TheGuaranteeID75052 attribute has a cardinality of 0..175054 meaning that for each instance of theSecuritiesFinancingTransaction75044 entity there may be oneGuaranteeID75052 attribute. TheDescription75056 attribute has a cardinality of 0..175058 meaning that for each instance of theSecuritiesFinancingTransaction75044 entity there may be oneDescription75056 attribute. TheCurrencyCode75060 attribute has a cardinality of 175062 meaning that for each instance of theSecuritiesFinancingTransaction75044 entity there is oneCurrencyCode75060 attribute. TheValidityPeriod75064 attribute has a cardinality of 175066 meaning that for each instance of theSecuritiesFinancingTransaction75044 entity there is oneValidityPeriod75064 attribute.

TheCounterparty75068 package includes aCounterparty75070 entity. TheCounterparty75070 entity has a cardinality of 175072 meaning that for each instance of theCounterparty75068 package there is oneCounterparty75070 entity. TheCounterparty75070 entity includes anInternalID75074 attribute. TheInternalID75074 attribute has a cardinality of 175076 meaning that for each instance of theCounterparty75070 entity there is oneInternalID75074 attribute.

TheGuarantorParty75080 package includes aGuarantorParty75082 entity. TheGuarantorParty75082 entity has a cardinality of 0..175084 meaning that for each instance of theGuarantorParty75080 package there may be one GuarantorParty75082 entity. TheGuarantorParty75082 entity includes anInternalID75086 attribute. TheInternalID75086 attribute has a cardinality of 0..175088 meaning that for each instance of theGuarantorParty75082 entity there may be oneInternalID75086 attribute.

ThePriceAtHorizon75112 entity has a cardinality of 0..175114 meaning that for each instance of theCreditExposureData75092 entity there may be onePriceAtHorizon75112 entity. ThePriceAtHorizon75112 entity includes various attributes, namely aDuration75116, anAmount75120 and aDecimalValue75124. TheDuration75116 attribute has a cardinality of 0..175118 meaning that for each instance of thePriceAtHorizon75112 entity there may be oneDuration75116 attribute. TheAmount75120 attribute has a cardinality of 0..175122 meaning that for each instance of thePriceAtHorizon75112 entity there may be oneAmount75120 attribute. TheDecimalValue75124 attribute has a cardinality of 0..175126 meaning that for each instance of thePriceAtHorizon75112 entity there may be one DecimalValue75124 attribute.

TheCurrentPrice75128 entity includes various attributes, namely aDuration75130, anAmount75134 and aDecimalValue75138. TheDuration75130 attribute has a cardinality of 0..175132 meaning that for each instance of theCurrentPrice75128 entity there may be oneDuration75130 attribute. TheAmount75134 attribute has a cardinality of 0..175136 meaning that for each instance of theCurrentPrice75128 entity there may be oneAmount75134 attribute. TheDecimalValue75138 attribute has a cardinality of 0..175140 meaning that for each instance of theCurrentPrice75128 entity there may be one DecimalValue75138 attribute.

TheProbabilityOfDefault75146 package includes aProbabilityOfDefault75148 entity. TheProbabilityOfDefault75148 entity has a cardinality of 0..n75150 meaning that for each instance of theProbabilityOfDefault75146 package there may be one or more ProbabilityOfDefault75148 entities. TheProbabilityOfDefault75148 entity includes various attributes, namely aValidityDatePeriod75152, aCode75156 and aDoubleValue75160. TheValidityDatePeriod75152 attribute has a cardinality of 175154 meaning that for each instance of theProbabilityOfDefault75148 entity there is oneValidityDatePeriod75152 attribute. TheCode75156 attribute has a cardinality of 175158 meaning that for each instance of theProbabilityOfDefault75148 entity there is oneCode75156 attribute. TheDoubleValue75160 attribute has a cardinality of 175162 meaning that for each instance of theProbabilityOfDefault75148 entity there is oneDoubleValue75160 attribute.

TheExposureProfile75202 package includes anExposureProfile75204 entity. TheExposureProfile75204 entity has a cardinality of 0..175206 meaning that for each instance of theExposureProfile75202 package there may be one ExposureProfile75204 entity. TheExposureProfile75204 entity includes anItem75208 subordinate entity.

TheItem75208 entity has a cardinality of 0..n75210 meaning that for each instance of theExposureProfile75204 entity there may be one ormore Item75208 entities. TheItem75208 entity includes various attributes, namely aDate75212, aNegativeExposureAmount75216 and aPositiveExposureAmount75220. TheDate75212 attribute has a cardinality of 175214 meaning that for each instance of theItem75208 entity there is oneDate75212 attribute. TheNegativeExposureAmount75216 attribute has a cardinality of 0..175218 meaning that for each instance of theItem75208 entity there may be one NegativeExposureAmount75216 attribute. ThePositiveExposureAmount75220 attribute has a cardinality of 0..175222 meaning that for each instance of theItem75208 entity there may be one PositiveExposureAmount75220 attribute.

TheRiskFreeProfile75224 package includes aRiskFreeProfile75226 entity. TheRiskFreeProfile75226 entity has a cardinality of 0..175228 meaning that for each instance of theRiskFreeProfile75224 package there may be one RiskFreeProfile75226 entity. TheRiskFreeProfile75226 entity includes anItem75230 subordinate entity.

TheItem75230 entity has a cardinality of 0..n75232 meaning that for each instance of theRiskFreeProfile75226 entity there may be one ormore Item75230 entities. TheItem75230 entity includes various attributes, namely aDate75234 and aRiskFreeAmount75238. TheDate75234 attribute has a cardinality of 175236 meaning that for each instance of theItem75230 entity there is oneDate75234 attribute. TheRiskFreeAmount75238 attribute has a cardinality of 175240 meaning that for each instance of theItem75230 entity there is oneRiskFreeAmount75238 attribute.

TheProperty75242 package includes aProperty75244 entity. TheProperty75244 entity has a cardinality of 0..n75246 meaning that for each instance of theProperty75242 package there may be one ormore Property75244 entities. TheProperty75244 entity includes various attributes, namely anID75248 and aValue75252. TheID75248 attribute has a cardinality of 175250 meaning that for each instance of theProperty75244 entity there is oneID75248 attribute. TheValue75252 attribute has a cardinality of 175254 meaning that for each instance of theProperty75244 entity there is oneValue75252 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 76-1 through76-9 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatStockCrteReqMsg76000 package. TheCrdtPrtfoModFSInDatStockCrteReqMsg76000 package includes aCrdtPrtfoModFSInDatStockCrteReqMsg76002 entity. TheCrdtPrtfoModFSInDatStockCrteReqMsg76000 package includes various packages, namely aMessageHeader76004 and aCreditPortfolioModel76010.

TheMessageHeader76004 package includes aMessageHeader76006 entity. TheMessageHeader76006 entity has a cardinality of 176008 meaning that for each instance of theMessageHeader76004 package there is oneMessageHeader76006 entity.

TheCreditPortfolioModel76010 package includes aCreditPortfolioModel76012 entity. TheCreditPortfolioModel76010 package includes anInputData76036 package. TheCreditPortfolioModel76012 entity has a cardinality of 176014 meaning that for each instance of theCreditPortfolioModel76010 package there is oneCreditPortfolioModel76012 entity. TheCreditPortfolioModel76012 entity includes anID76016 attribute. TheCreditPortfolioModel76012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl76020 and aCreditPortfolio76028. TheID76016 attribute has a cardinality of 176018 meaning that for each instance of theCreditPortfolioModel76012 entity there is oneID76016 attribute.

TheCreditPortfolioManagementProcessControl76020 entity has a cardinality of 176022 meaning that for each instance of theCreditPortfolioModel76012 entity there is oneCreditPortfolioManagementProcessControl76020 entity. TheCreditPortfolioManagementProcessControl76020 entity includes aDataTransferID76024 attribute. TheDataTransferID76024 attribute has a cardinality of 176026 meaning that for each instance of theCreditPortfolioManagementProcessControl76020 entity there is oneDataTransferID76024 attribute.

TheCreditPortfolio76028 entity has a cardinality of 176030 meaning that for each instance of theCreditPortfolioModel76012 entity there is oneCreditPortfolio76028 entity. TheCreditPortfolio76028 entity includes anID76032 attribute. TheID76032 attribute has a cardinality of 176034 meaning that for each instance of theCreditPortfolio76028 entity there is oneID76032 attribute.

TheInputData76036 package includes anInputData76038 entity. TheInputData76036 package includes aStock76042 package. TheInputData76038 entity has a cardinality of 176040 meaning that for each instance of theInputData76036 package there is oneInputData76038 entity.

TheStock76042 package includes aStock76044 entity. TheStock76042 package includes various packages, namely anIssuerParty76066, aGuarantorParty76080, aCreditExposureData76090, aProbabilityOfDefault76152, aRating76170 and aProperty76208. TheStock76044 entity includes various attributes, namely anID76046, aGuaranteeID76050, aDescription76054, aCurrencyCode76058 and aValidityPeriod76062. TheID76046 attribute has a cardinality of 176048 meaning that for each instance of theStock76044 entity there is oneID76046 attribute. TheGuaranteeID76050 attribute has a cardinality of 0..176052 meaning that for each instance of theStock76044 entity there may be oneGuaranteeID76050 attribute. TheDescription76054 attribute has a cardinality of 0..176056 meaning that for each instance of theStock76044 entity there may be oneDescription76054 attribute. TheCurrencyCode76058 attribute has a cardinality of 176060 meaning that for each instance of theStock76044 entity there is oneCurrencyCode76058 attribute. TheValidityPeriod76062 attribute has a cardinality of 176064 meaning that for each instance of theStock76044 entity there is oneValidityPeriod76062 attribute.

TheIssuerParty76066 package includes anIssuerParty76068 entity. TheIssuerParty76068 entity has a cardinality of 176070 meaning that for each instance of theIssuerParty76066 package there is oneIssuerParty76068 entity. TheIssuerParty76068 entity includes various attributes, namely anInternalID76072 and aGuarantorSubstitutionCode76076. TheInternalID76072 attribute has a cardinality of 176074 meaning that for each instance of theIssuerParty76068 entity there is oneInternalID76072 attribute. TheGuarantorSubstitutionCode76076 attribute has a cardinality of 0..176078 meaning that for each instance of theIssuerParty76068 entity there may be oneGuarantorSubstitutionCode76076 attribute.

TheGuarantorParty76080 package includes aGuarantorParty76082 entity. TheGuarantorParty76082 entity has a cardinality of 0..176084 meaning that for each instance of theGuarantorParty76080 package there may be one GuarantorParty76082 entity. TheGuarantorParty76082 entity includes anInternalID76086 attribute. TheInternalID76086 attribute has a cardinality of 0..176088 meaning that for each instance of theGuarantorParty76082 entity there may be oneInternalID76086 attribute.

ThePriceAtHorizon76112 entity has a cardinality of 0..176114 meaning that for each instance of theCreditExposureData76092 entity there may be onePriceAtHorizon76112 entity. ThePriceAtHorizon76112 entity includes various attributes, namely aDuration76116, anAmount76120 and aDecimalValue76124. TheDuration76116 attribute has a cardinality of 0..176118 meaning that for each instance of thePriceAtHorizon76112 entity there may be oneDuration76116 attribute. TheAmount76120 attribute has a cardinality of 0..176122 meaning that for each instance of thePriceAtHorizon76112 entity there may be oneAmount76120 attribute. TheDecimalValue76124 attribute has a cardinality of 0..176126 meaning that for each instance of thePriceAtHorizon76112 entity there may be one DecimalValue76124 attribute.

TheCurrentPrice76128 entity has a cardinality of 0..176130 meaning that for each instance of theCreditExposureData76092 entity there may be one CurrentPrice76128 entity. TheCurrentPrice76128 entity includes various attributes, namely aDuration76132, anAmount76136 and aDecimalValue76140. TheDuration76132 attribute has a cardinality of 0..176134 meaning that for each instance of theCurrentPrice76128 entity there may be oneDuration76132 attribute. TheAmount76136 attribute has a cardinality of 0..176138 meaning that for each instance of theCurrentPrice76128 entity there may be oneAmount76136 attribute. TheDecimalValue76140 attribute has a cardinality of 0..176142 meaning that for each instance of theCurrentPrice76128 entity there may be one DecimalValue76140 attribute.

TheProbabilityOfDefault76152 package includes aProbabilityOfDefault76154 entity. TheProbabilityOfDefault76154 entity has a cardinality of 0..n76156 meaning that for each instance of theProbabilityOfDefault76152 package there may be one or more ProbabilityOfDefault76154 entities. TheProbabilityOfDefault76154 entity includes various attributes, namely aValidityDatePeriod76158, aCode76162 and aDoubleValue76166. TheValidityDatePeriod76158 attribute has a cardinality of 176160 meaning that for each instance of theProbabilityOfDefault76154 entity there is oneValidityDatePeriod76158 attribute. TheCode76162 attribute has a cardinality of 176164 meaning that for each instance of theProbabilityOfDefault76154 entity there is oneCode76162 attribute. TheDoubleValue76166 attribute has a cardinality of 176168 meaning that for each instance of theProbabilityOfDefault76154 entity there is oneDoubleValue76166 attribute.

TheProperty76208 package includes aProperty76210 entity. TheProperty76210 entity has a cardinality of 0..n76212 meaning that for each instance of theProperty76208 package there may be one ormore Property76210 entities. TheProperty76210 entity includes various attributes, namely anID76214 and aValue76218. TheID76214 attribute has a cardinality of 176216 meaning that for each instance of theProperty76210 entity there is oneID76214 attribute. TheValue76218 attribute has a cardinality of 176220 meaning that for each instance of theProperty76210 entity there is oneValue76218 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIGS. 77-1 through77-10 show an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatBuPaCrteReqMsg77000 package. TheCrdtPrtfoModFSInDatBuPaCrteReqMsg77000 package includes aCrdtPrtfoModFSInDatBuPaCrteReqMsg77002 entity. TheCrdtPrtfoModFSInDatBuPaCrteReqMsg77000 package includes various packages, namely aMessageHeader77004 and aCreditPortfolioModel77010.

TheMessageHeader77004 package includes aMessageHeader77006 entity. TheMessageHeader77006 entity has a cardinality of 177008 meaning that for each instance of theMessageHeader77004 package there is oneMessageHeader77006 entity.

TheCreditPortfolioModel77010 package includes aCreditPortfolioModel77012 entity. TheCreditPortfolioModel77010 package includes anInputData77036 package. TheCreditPortfolioModel77012 entity has a cardinality of 177014 meaning that for each instance of theCreditPortfolioModel77010 package there is oneCreditPortfolioModel77012 entity. TheCreditPortfolioModel77012 entity includes anID77016 attribute. TheCreditPortfolioModel77012 entity includes various subordinate entities, namely aCreditPortfolioManagementProcessControl77020 and aCreditPortfolio77028. TheID77016 attribute has a cardinality of 177018 meaning that for each instance of theCreditPortfolioModel77012 entity there is oneID77016 attribute.

TheCreditPortfolioManagementProcessControl77020 entity has a cardinality of 177022 meaning that for each instance of theCreditPortfolioModel77012 entity there is oneCreditPortfolioManagementProcessControl77020 entity. TheCreditPortfolioManagementProcessControl77020 entity includes aDataTransferID77024 attribute. TheDataTransferID77024 attribute has a cardinality of 177026 meaning that for each instance of theCreditPortfolioManagementProcessControl77020 entity there is oneDataTransferID77024 attribute.

TheCreditPortfolio77028 entity has a cardinality of 177030 meaning that for each instance of theCreditPortfolioModel77012 entity there is oneCreditPortfolio77028 entity. TheCreditPortfolio77028 entity includes anID77032 attribute. TheID77032 attribute has a cardinality of 177034 meaning that for each instance of theCreditPortfolio77028 entity there is oneID77032 attribute.

TheInputData77036 package includes anInputData77038 entity. TheInputData77036 package includes aBusinessPartner77042 package. TheInputData77038 entity has a cardinality of 177040 meaning that for each instance of theInputData77036 package there is oneInputData77038 entity.

TheBusinessPartner77042 package includes aBusinessPartner77044 entity. TheBusinessPartner77042 package includes various packages, namely aProbabilityOfDefault77068, aRating77086, aFinancialData77124, aFactorCorrelationModelData77154 and aProperty77192. TheBusinessPartner77044 entity has a cardinality of 177046 meaning that for each instance of theBusinessPartner77042 package there is oneBusinessPartner77044 entity. TheBusinessPartner77044 entity includes various attributes, namely anID77048, aName77052, aCountryCode77056, aSegmentCode77060 and aValidityDate77064. TheID77048 attribute has a cardinality of 177050 meaning that for each instance of theBusinessPartner77044 entity there is oneID77048 attribute. TheName77052 attribute has a cardinality of 0..177054 meaning that for each instance of theBusinessPartner77044 entity there may be oneName77052 attribute. TheCountryCode77056 attribute has a cardinality of 0..177058 meaning that for each instance of theBusinessPartner77044 entity there may be oneCountryCode77056 attribute. TheSegmentCode77060 attribute has a cardinality of 0..177062 meaning that for each instance of theBusinessPartner77044 entity there may be oneSegmentCode77060 attribute. TheValidityDate77064 attribute has a cardinality of 177066 meaning that for each instance of theBusinessPartner77044 entity there is oneValidityDate77064 attribute.

TheProbabilityOfDefault77068 package includes aProbabilityOfDefault77070 entity. TheProbabilityOfDefault77070 entity has a cardinality of 0..n77072 meaning that for each instance of theProbabilityOfDefault77068 package there may be one or more ProbabilityOfDefault77070 entities. TheProbabilityOfDefault77070 entity includes various attributes, namely aValidityDatePeriod77074, aCode77078 and aDoubleValue77082. TheValidityDatePeriod77074 attribute has a cardinality of 177076 meaning that for each instance of theProbabilityOfDefault77070 entity there is oneValidityDatePeriod77074 attribute. TheCode77078 attribute has a cardinality of 177080 meaning that for each instance of theProbabilityOfDefault77070 entity there is oneCode77078 attribute. TheDoubleValue77082 attribute has a cardinality of 177084 meaning that for each instance of theProbabilityOfDefault77070 entity there is oneDoubleValue77082 attribute.

TheFinancialData77124 package includes aFinancialData77126 entity. TheFinancialData77126 entity has a cardinality of 0..177128 meaning that for each instance of theFinancialData77124 package there may be oneFinancialData77126 entity. TheFinancialData77126 entity includes anItem77130 subordinate entity.

TheItem77130 entity has a cardinality of 1..n77132 meaning that for each instance of theFinancialData77126 entity there are one ormore Item77130 entities. TheItem77130 entity includes various attributes, namely aFiscalYear77134, aFiscalValidityDatePeriod77138, aBalanceSheetCurrencyCode77142, aTotalAssetsAmount77146 and anAnnualSalesAmount77150. TheFiscalYear77134 attribute has a cardinality of 177136 meaning that for each instance of theItem77130 entity there is oneFiscalYear77134 attribute. TheFiscalValidityDatePeriod77138 attribute has a cardinality of 177140 meaning that for each instance of theItem77130 entity there is oneFiscalValidityDatePeriod77138 attribute. TheBalanceSheetCurrencyCode77142 attribute has a cardinality of 177144 meaning that for each instance of theItem77130 entity there is oneBalanceSheetCurrencyCode77142 attribute. TheTotalAssetsAmount77146 attribute has a cardinality of 177148 meaning that for each instance of theItem77130 entity there is oneTotalAssetsAmount77146 attribute. TheAnnualSalesAmount77150 attribute has a cardinality of 177152 meaning that for each instance of theItem77130 entity there is oneAnnualSalesAmount77150 attribute.

TheFactorCorrelationModelData77154 package includes aFactorCorrelationModelData77156 entity. TheFactorCorrelationModelData77156 entity has a cardinality of 0..177158 meaning that for each instance of theFactorCorrelationModelData77154 package there may be oneFactorCorrelationModelData77156 entity. TheFactorCorrelationModelData77156 entity includes anItem77160 subordinate entity.

TheItem77160 entity has a cardinality of 1..n77162 meaning that for each instance of theFactorCorrelationModelData77156 entity there are one ormore Item77160 entities. TheItem77160 entity includes various attributes, namely aCorrelationModel77164 and aRSquaredDoubleValue77168. TheItem77160 entity includes a FactorWeight77172 subordinate entity. TheCorrelationModel77164 attribute has a cardinality of 177166 meaning that for each instance of theItem77160 entity there is oneCorrelationModel77164 attribute. TheRSquaredDoubleValue77168 attribute has a cardinality of 177170 meaning that for each instance of theItem77160 entity there is oneRSquaredDoubleValue77168 attribute.

TheFactorWeight77172 entity has a cardinality of 1..n77174 meaning that for each instance of theItem77160 entity there are one or more FactorWeight77172 entities. TheFactorWeight77172 entity includes various attributes, namely aValidityDate77176, aFactorTypeCode77180, aFactorName77184 and aWeightingFactorValue77188. TheValidityDate77176 attribute has a cardinality of 177178 meaning that for each instance of theFactorWeight77172 entity there is oneValidityDate77176 attribute. TheFactorTypeCode77180 attribute has a cardinality of 177182 meaning that for each instance of theFactorWeight77172 entity there is oneFactorTypeCode77180 attribute. TheFactorName77184 attribute has a cardinality of 177186 meaning that for each instance of theFactorWeight77172 entity there is oneFactorName77184 attribute. TheWeightingFactorValue77188 attribute has a cardinality of 177190 meaning that for each instance of theFactorWeight77172 entity there is oneWeightingFactorValue77188 attribute.

TheProperty77192 package includes aProperty77194 entity. TheProperty77194 entity has a cardinality of 0..n77196 meaning that for each instance of theProperty77192 package there may be one ormore Property77194 entities. TheProperty77194 entity includes various attributes, namely anID77198 and aValue77202. TheID77198 attribute has a cardinality of 177200 meaning that for each instance of theProperty77194 entity there is oneID77198 attribute. TheValue77202 attribute has a cardinality of 177204 meaning that for each instance of theProperty77194 entity there is oneValue77202 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 63-1 through63-135.

FIG. 78 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatYldCrvBulkCrteReqMsg78000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as78000 through78020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatYldCrvBulkCrteReqMsg78000 includes, among other things, aCrdtPrtfoModFSInDatYldCrvBulkCrteReqMsg78002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 79 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatExchRateCrteReqMsg79000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as79000 through79020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatExchRateCrteReqMsg79000 includes, among other things, aCrdtPrtfoModFSInDatExchRateCrteReqMsg79002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 80 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatPDClbrtMtxBulkCrteReqMsg80000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as80000 through80020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatPDClbrtMtxBulkCrteReqMsg80000 includes, among other things, aCrdtPrtfoModFSInDatPDClbrtMtxBulkCrteReqMsg80002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 81 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatCrdtSprdBulkCrteReqMsg81000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as81000 through81020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatCrdtSprdBulkCrteReqMsg81000 includes, among other things, aCrdtPrtfoModFSInDatCrdtSprdBulkCrteReqMsg81002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 82 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatRatgMtxBulkCrteReqMsg82000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as82000 through82020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatRatgMtxBulkCrteReqMsg82000 includes, among other things, aCrdtPrtfoModFSInDatRatgMtxBulkCrteReqMsg82002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 83 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatTOBSItmBulkCrteReqMsg83000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as83000 through83020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatTOBSItmBulkCrteReqMsg83000 includes, among other things, aCrdtPrtfoModFSInDatTOBSItmBulkCrteReqMsg83002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 84 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatLoanBulkCrteReqMsg84000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as84000 through84020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatLoanBulkCrteReqMsg84000 includes, among other things, aCrdtPrtfoModFSInDatLoanBulkCrteReqMsg84002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 85 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatOTCDeriBulkCrteReqMsg85000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as85000 through85020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatOTCDeriBulkCrteReqMsg85000 includes, among other things, aCrdtPrtfoModFSInDatOTCDeriBulkCrteReqMsg85002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 86 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatSecFTBulkCrteReqMsg86000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as86000 through86020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatSecFTBulkCrteReqMsg86000 includes, among other things, aCrdtPrtfoModFSInDatSecFTBulkCrteReqMsg86002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 87 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatStockBulkCrteReqMsg87000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as87000 through87020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatStockBulkCrteReqMsg87000 includes, among other things, aCrdtPrtfoModFSInDatStockBulkCrteReqMsg87002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 88 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatCrdtDeriBulkCrteReqMsg88000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as88000 through88020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatCrdtDeriBulkCrteReqMsg88000 includes, among other things, aCrdtPrtfoModFSInDatCrdtDeriBulkCrteReqMsg88002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 89 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatBondBulkCrteReqMsg89000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as89000 through89020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatBondBulkCrteReqMsg89000 includes, among other things, aCrdtPrtfoModFSInDatBondBulkCrteReqMsg89002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 90 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatBuPaBulkCrteReqMsg90000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as90000 through90020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatBuPaBulkCrteReqMsg90000 includes, among other things, aCrdtPrtfoModFSInDatBuPaBulkCrteReqMsg90002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 91 shows an example configuration of an Element Structure that includes aCrdtPrtfoModFSInDatPrtfoAnlysDatBulkCrteReqMsg91000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as91000 through91020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoModFSInDatPrtfoAnlysDatBulkCrteReqMsg91000 includes, among other things, aCrdtPrtfoModFSInDatPrtfoAnlysDatBulkCrteReqMsg91002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

Credit Portfolio Analytical Result Interfaces

The message choreography ofFIG. 92 describes a possible logical sequence of messages that can be used to realize a Credit Portfolio Management business scenario.

A “Financial Instruments Analytical Results Management”system92002 can request the creation of several loss value analytical results from a “Credit Portfolio Management”system92000, using a Credit Portfolio Analytical Result FS Loss Value BulkCreate Request message92004 as shown, for example, inFIG. 92. The Credit Portfolio Analytical Result FS Loss Value BulkCreate Request message92004 is received by a Create Result Loss Value as Bulk operation included in a Credit Portfolio Analytical Result In interface.

The “Financial Instruments Analytical Results Management”system92002 can request the creation of several item analytical results from the “Credit Portfolio Management”system92000, using a Credit Portfolio Analytical Result FS Item BulkCreate Request message92006 as shown, for example, inFIG. 92. The Credit Portfolio Analytical Result FS Item BulkCreate Request message92006 is received by a Create Result Item as Bulk operation included in the Create Portfolio Analytical Result In interface.

FIG. 93 illustrates an example Credit Portfolio Analytical Resultbusiness object model93000. Specifically, this model depicts interactions among various components of the Credit Portfolio Analytical Result, as well as external components that interact with the Credit Portfolio Analytical Result (shown here as93002 through93010 and93018 through93032). CreditPortfolio Analytical Result93000 includeselements93012 through93016. CreditPortfolio Analytical Result93000 includes for example, aProperty93016.

Credit Portfolio Analytical Result is an analytical result for a credit portfolio. It is produced by a credit portfolio risk modeling and analysis tool and relevant for the measurement and management of credit portfolio risk. For example, the Credit Portfolio Analytical Result is composed of the following figures: Credit Value-at-Risk for a credit portfolio, Expected Shortfall for a credit portfolio, Economic Capital for a credit portfolio, Standard Deviation for a credit portfolio, Expected Loss for a credit portfolio, and Risk Contributions with regard to a subset of a credit portfolio for the Credit Value at Risk, Expected Shortfall, and Standard Deviation risk measures.

FIGS. 94-1 through94-10 show an example configuration of an Element Structure that includes aCreditPortfolioAnalyticalResultFSCreateRequestMessage94000 package. TheCreditPortfolioAnalyticalResultFSCreateRequestMessage94000 package is aCrdtPortfolioAnlytlRsltFSLossValueCrteReqMsg94004 data type. TheCreditPortfolioAnalyticalResultFSCreateRequestMessage94000 package includes aCreditPortfolioAnalyticalResultFSCreateRequestMessage94002 entity. TheCreditPortfolioAnalyticalResultFSCreateRequestMessage94000 package includes various packages, namely aMessageHeader94006 and aCreditPortfolioAnalyticalResult94012.

TheMessageHeader94006 package is aBusinessDocumentMessageHeader94010 data type. TheMessageHeader94006 package includes aMessageHeader94008 entity.

TheCreditPortfolioAnalyticalResult94012 package includes aCreditPortfolioAnalyticalResult94014 entity. TheCreditPortfolioAnalyticalResult94012 package includes various packages, namely aCreditPortfolioManagementProcessControl94056 and anItem94128. A CreditPortfolioAnalyticalResult creates the request for Credit Portfolio Management results on instrument level. TheCreditPortfolioAnalyticalResult94014 entity includes various attributes, namely anID94016, aCreationDateTime94020, anExpectedLossAmount94024, anUnexpectedLossAmount94028, anExpectedShortfallAmount94032, aCreditValueAtRiskAmount94036, anEconomicCapitalAmount94040, aTotalExposureAmount94044, aMeanValueofLossesAmount94048 and aPortfolioDiversificationDecimalValue94052.

TheID94016 attribute is aPDT_CreditPortfolioAnalyticalResult94018 data type. A CreditPortfolioAnalyticalResult is a unique identification for a credit portfolio analytical result. TheCreationDateTime94020 attribute is aGLOBAL_DateTime94022 data type. A CreationDateTime is the specification of an exact day and time.

TheExpectedLossAmount94024 attribute is anAmount94026 data type. In order to consider stochastic LGDs the Expected LGD is the expected value of the LGD value distribution. Together with the LGD Shape Parameter it determines the density function of LGD when assuming that LGD is beta distributed. TheUnexpectedLossAmount94028 attribute is anAmount94030 data type. An UnexpectedLossAmount is the standard deviation of Loss Distribution. TheExpectedShortfallAmount94032 attribute is anAmount94034 data type. An ExpectedShortfallAmount is the expected shortfall of the portfolio. TheCreditValueAtRiskAmount94036 attribute is anAmount94038 data type. A CreditValueAtRiskAmount is the credit value at risk for the portfolio. TheEconomicCapitalAmount94040 attribute is anAmount94042 data type. An EconomicCapitalAmount is the economic loss amount. TheTotalExposureAmount94044 attribute is anAmount94046 data type. A TotalExposureAmount is the total exposure amount of all portfolio instruments. Different evaluation approaches for different portfolio instruments are possible. TheMeanValueofLossesAmount94048 attribute is anAmount94050 data type. A MeanValueofLossesAmount is the mean value of the losses. ThePortfolioDiversificationDecimalValue94052 attribute is aDecimalValue94054 data type.

TheCreditPortfolioManagementProcessControl94056 package includes various entities, namely aCreditPortfolioManagementProcessControl94058 and aLossDistribution94110. TheCreditPortfolioManagementProcessControl94056 package includes various packages, namely aCreditPortfolioModel94094 and aLossDistribution94108. TheCreditPortfolioManagementProcessControl94058 entity includes various attributes, namely anID94060, aDataTransferID94064 and aValidityDate94068. TheCreditPortfolioManagementProcessControl94058 entity includes aCreditPortfolioAnalysisRun94072 subordinate entity. TheID94060 attribute is aPDT_CreditPortfolioManagementProcessControlID94062 data type. TheDataTransferID94064 attribute is aPDT_CreditPortfolioManagementProcessControIDataTransferID94066 data type. TheValidityDate94068 attribute is aDate94070 data type. TheCreditPortfolioAnalysisRun94072 entity includes various attributes, namely anID94074, aLossDefinitionParadigmCode94078, aDuration94082, aSimulationTrialsNumberValue94086 and aConfidenceLevelCode94090. TheID94074 attribute is aPDT_CreditPortfolioAnalysisRunID94076 data type. TheLossDefinitionParadigmCode94078 attribute is aCode94080 data type. A LossDefinitionParadigmCode is the code of the loss definition paradigm, e.g., a credit migration approach vs a default-only approach. TheDuration94082 attribute is aDuration94084 data type. A Duration is a period of time of a particular length without a fixed start or end time. This period of time is expressed, for example, in years or months. TheSimulationTrialsNumberValue94086 attribute is aNumberValue94088 data type. A SimulationTrialsNumberValue is the number of simulation trials of the credit portfolio model analysis. TheConfidenceLevelCode94090 attribute is aCode94092 data type. A ConfidenceLevelCode is the code of the confidence level. TheLossDistribution94110 entity includes various attributes, namely aLossAmount94112, aLossPercent94116, aNumberOfSimulatedLossesNumberValue94120 and aRelativeNumberOfSimulatedLossesDecimalValue94124. TheLossAmount94112 attribute is anAmount94114 data type. A LossAmount is the amount of losses for a given loss interval.

TheLossPercent94116 attribute is aPercentage94118 data type. A LossPercent is the relative loss of the given loss interval according to the total loss. TheNumberOfSimulatedLossesNumberValue94120 attribute is aNumberValue94122 data type. A NumberOfSimulatedLossesNumberValue is the number of simulated losses for the given loss interval. TheRelativeNumberOfSimulatedLossesDecimalValue94124 attribute is aDecimalValue94126 data type. A RelativeNumberOfSimulatedLossesDecimalValue is the relative number of simulated losses for the given loss interval.

TheCreditPortfolioModel94094 package includes aCreditPortfolioModel94096 entity. TheCreditPortfolioModel94096 entity includes anID94098 attribute. TheCreditPortfolioModel94096 entity includes aCreditPortfolio94102 subordinate entity.

TheID94098 attribute is aPDT_CreditPortfolioModelID94100 data type. TheCreditPortfolio94102 entity includes anID94104 attribute. TheID94104 attribute is aPDT_CreditPortfolioID94106 data type.

TheLossDistribution94108 package includes aLossDistribution94110 entity. TheLossDistribution94110 entity includes various attributes, namely aLossAmount94112, aLossPercent94116, aNumberOfSimulatedLossesNumberValue94120 and aRelativeNumberOfSimulatedLossesDecimalValue94124. TheLossAmount94112 attribute is anAmount94114 data type. A LossAmount is the amount of losses for a given loss interval.

TheItem94128 package includes anItem94130 entity. A CreditPortfoliolAnalyticalResultItem creates the request for Credit Portfolio Management results on instrument level. TheItem94130 entity includes various attributes, namely anID94132, aFinancialInstrumentID94136, aFinancialInstrumentCategoryCode94140, aStandardisedFinancialInstrumentAccountID94144, aGuaranteeID94148, anExposureID94152, anAggregationID94156, anExpectedLossAmount94160, anUnexpectedLossAmount94164, aDiversificationDecimalValue94170, aContributionToExpectedShortfallAmount94174, aContributionToCreditValueAtRiskAmount94178, aContributionToEconomicCapitalAccordingToExpectedShortfallAmount94182, aContributionToEconomicCapitalAccordingToCreditValueAtRiskAmount94186 and anExposureAmount94190. TheID94132 attribute is aPDT_CreditPortfolioAnalyticalResultItemID94134 data type. A CreditPortfoliolAnalyticalResultItemID is a unique identification for a credit portfolio analytical result item. TheFinancialInstrumentID94136 attribute is aBusinessTransactionDocumentID94138 data type. A BusinessTransactionDocumentID is a unique identifier for a business transaction document. TheFinancialInstrumentCategoryCode94140 attribute is aFinancialInstrumentCategoryCode94142 data type. A FinancialInstrumentCategoryCode is the coded representation of the category of a financial instrument. TheStandardisedFinancialInstrumentAccountID94144 attribute is aFinancialInstrumentAccountID94146 data type. A FinancialInstrumentAccountID is the unique identifier of an account for financial instruments. TheGuaranteeID94148 attribute is anIdentifier94150 data type. A GuaranteeID is an unique identification for guarantee. TheExposureID94152 attribute is anIdentifier94154 data type. An ExposureID is a unique identification for an exposure. TheAggregationID94156 attribute is anIdentifier94158 data type. An AggregationID is a unique identification for an aggregation ID. TheExpectedLossAmount94160 attribute is anAmount94162 data type. In order to consider stochastic LGDs the Expected LGD is the expected value of the LGD value distribution. Together with the LGD Shape Parameter it determines the density function of LGD when assuming that LGD is beta distributed. TheUnexpectedLossAmount94164 attribute is anAmount94166 data type. An UnexpectedLossAmount is the standard deviation of the loss distribution with regard to the loss item. A ContributionToUnexpectedLossAmount is the contribution of the loss item to the unexpected loss amount of the portfolio. TheDiversificationDecimalValue94170 attribute is aDecimalValue94172 data type. TheContributionToExpectedShortfallAmount94174 attribute is anAmount94176 data type. A ContributionToExpectedShortfallAmount is the contribution of the loss item to the expected shortfall amount of the portfolio. TheContributionToCreditValueAtRiskAmount94178 attribute is anAmount94180 data type. A ContributionToCreditValueAtRiskAmount is the contribution of the loss item to the credit value at risk amount. TheContributionToEconomicCapitalAccordingToExpectedShortfallAmount94182 attribute is anAmount94184 data type. A ContributionToEconomicCapitalAccordingToExpectedShortfallAmount is the contribution of the loss item to the economic capital according to the expected shortfall amount.

TheContributionToEconomicCapitalAccordingToCreditValueAtRiskAmount94186 attribute is anAmount94188 data type. A ContributionToEconomicCapitalAccordingToCreditValueAtRiskAmount is the contribution of the loss item to the economic capital according to the credit value at risk amount. TheExposureAmount94190 attribute is anAmount94192 data type. An ExposureAmount is the exposure amount of the loss item.

FIGS. 95-1 through95-6 show an example configuration of an Element Structure that includes aCrdtPrtfoAnlytRsltFSLossValueCrteReqMsg95000 package. TheCrdtPrtfoAnlytRsltFSLossValueCrteReqMsg95000 package includes aCrdtPrtfoAnlytRsltFSLossValueCrteReqMsg95002 entity. TheCrdtPrtfoAnlytRsltFSLossValueCrteReqMsg95000 package includes various packages, namely aMessageHeader95004 and aCreditPortfolioAnalyticalResult95010.

TheMessageHeader95004 package includes aMessageHeader95006 entity. TheMessageHeader95006 entity has a cardinality of 195008 meaning that for each instance of theMessageHeader95004 package there is oneMessageHeader95006 entity.

TheCreditPortfolioAnalysisRun95074 entity has a cardinality of 195076 meaning that for each instance of theCreditPortfolioManagementProcessControl95058 entity there is oneCreditPortfolioAnalysisRun95074 entity. TheCreditPortfolioAnalysisRun95074 entity includes various attributes, namely anID95078, aLossDefinitionParadigmCode95082, aDuration95086, aSimulationTrialsNumberValue95090 and aConfidenceLevelCode95094. TheID95078 attribute has a cardinality of 195080 meaning that for each instance of theCreditPortfolioAnalysisRun95074 entity there is oneID95078 attribute. TheLossDefinitionParadigmCode95082 attribute has a cardinality of 0..195084 meaning that for each instance of theCreditPortfolioAnalysisRun95074 entity there may be oneLossDefinitionParadigmCode95082 attribute. TheDuration95086 attribute has a cardinality of 0..195088 meaning that for each instance of theCreditPortfolioAnalysisRun95074 entity there may be oneDuration95086 attribute. TheSimulationTrialsNumberValue95090 attribute has a cardinality of 0..195092 meaning that for each instance of theCreditPortfolioAnalysisRun95074 entity there may be one SimulationTrialsNumberValue95090 attribute. TheConfidenceLevelCode95094 attribute has a cardinality of 0..195096 meaning that for each instance of theCreditPortfolioAnalysisRun95074 entity there may be oneConfidenceLevelCode95094 attribute.

TheCreditPortfolioModel95098 entity has a cardinality of 195100 meaning that for each instance of theCreditPortfolioManagementProcessControl95058 entity there is oneCreditPortfolioModel95098 entity. TheCreditPortfolioModel95098 entity includes anID95102 attribute. TheCreditPortfolioModel95098 entity includes aCreditPortfolio95106 subordinate entity. TheID95102 attribute has a cardinality of 195104 meaning that for each instance of theCreditPortfolioModel95098 entity there is oneID95102 attribute.

TheCreditPortfolio95106 entity has a cardinality of 195108 meaning that for each instance of theCreditPortfolioModel95098 entity there is oneCreditPortfolio95106 entity. TheCreditPortfolio95106 entity includes anID95110 attribute. TheID95110 attribute has a cardinality of 195112 meaning that for each instance of theCreditPortfolio95106 entity there is oneID95110 attribute.

FIGS. 96-1 through96-7 show an example configuration of an Element Structure that includes aCrdtPrtfoAnlytRsltFSItmCrteReqMsg96000 package. TheCrdtPrtfoAnlytRsltFSItmCrteReqMsg96000 package includes aCrdtPrtfoAnlytRsltFSItmCrteReqMsg96002 entity. TheCrdtPrtfoAnlytRsltFSItmCrteReqMsg96000 package includes various packages, namely aMessageHeader96004 and aCreditPortfolioAnalyticalResult96010.

TheMessageHeader96004 package includes aMessageHeader96006 entity. TheMessageHeader96006 entity has a cardinality of 196008 meaning that for each instance of theMessageHeader96004 package there is oneMessageHeader96006 entity.

TheCreditPortfolioAnalyticalResult96010 package includes aCreditPortfolioAnalyticalResult96012 entity. TheCreditPortfolioAnalyticalResult96010 package includes various packages, namely aCreditPortfolioManagementProcessControl96024 and anItem96082. TheCreditPortfolioAnalyticalResult96012 entity has a cardinality of 196014 meaning that for each instance of theCreditPortfolioAnalyticalResult96010 package there is oneCreditPortfolioAnalyticalResult96012 entity. TheCreditPortfolioAnalyticalResult96012 entity includes various attributes, namely anID96016 and aCreationDateTime96020. TheID96016 attribute has a cardinality of 196018 meaning that for each instance of theCreditPortfolioAnalyticalResult96012 entity there is oneID96016 attribute. TheCreationDateTime96020 attribute has a cardinality of 196022 meaning that for each instance of theCreditPortfolioAnalyticalResult96012 entity there is oneCreationDateTime96020 attribute.

TheCreditPortfolioAnalysisRun96042 entity has a cardinality of 196044 meaning that for each instance of theCreditPortfolioManagementProcessControl96026 entity there is oneCreditPortfolioAnalysisRun96042 entity. TheCreditPortfolioAnalysisRun96042 entity includes various attributes, namely anID96046, aLossDefinitionParadigmCode96050, aDuration96054, aSimulationTrialsNumberValue96058 and aConfidenceLevelCode96062. TheID96046 attribute has a cardinality of 196048 meaning that for each instance of theCreditPortfolioAnalysisRun96042 entity there is oneID96046 attribute. TheLossDefinitionParadigmCode96050 attribute has a cardinality of 196052 meaning that for each instance of theCreditPortfolioAnalysisRun96042 entity there is oneLossDefinitionParadigmCode96050 attribute. TheDuration96054 attribute has a cardinality of 196056 meaning that for each instance of theCreditPortfolioAnalysisRun96042 entity there is oneDuration96054 attribute. TheSimulationTrialsNumberValue96058 attribute has a cardinality of 196060 meaning that for each instance of theCreditPortfolioAnalysisRun96042 entity there is oneSimulationTrialsNumberValue96058 attribute. TheConfidenceLevelCode96062 attribute has a cardinality of 196064 meaning that for each instance of theCreditPortfolioAnalysisRun96042 entity there is oneConfidenceLevelCode96062 attribute.

TheCreditPortfolioModel96066 entity has a cardinality of 196068 meaning that for each instance of theCreditPortfolioManagementProcessControl96026 entity there is oneCreditPortfolioModel96066 entity. TheCreditPortfolioModel96066 entity includes anID96070 attribute. TheCreditPortfolioModel96066 entity includes aCreditPortfolio96074 subordinate entity. TheID96070 attribute has a cardinality of 196072 meaning that for each instance of theCreditPortfolioModel96066 entity there is oneID96070 attribute. TheCreditPortfolio96074 entity has a cardinality of 196076 meaning that for each instance of theCreditPortfolioModel96066 entity there is oneCreditPortfolio96074 entity. TheCreditPortfolio96074 entity includes anID96078 attribute. TheID96078 attribute has a cardinality of 196080 meaning that for each instance of theCreditPortfolio96074 entity there is oneID96078 attribute.

TheContributionToEconomicCapitalAccordingToCreditValueAtRiskAmount96144 attribute has a cardinality of 0..196146 meaning that for each instance of theItem96084 entity there may be one ContributionToEconomicCapitalAccordingToCreditValueAtRiskAmount96144 attribute. TheExposureAmount96148 attribute has a cardinality of 0..196150 meaning that for each instance of theItem96084 entity there may be one ExposureAmount96148 attribute. The data types of the various packages, entities, and attributes shown inFIG. 96 are described with respect toFIGS. 94-1 through94-10.

FIG. 97 shows an example configuration of an Element Structure that includes aCrdtPrtfoAnlytRsltFSLossValueBulkCrteReqMsg97000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as97000 through97020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoAnlytRsltFSLossValueBulkCrteReqMsg97000 includes, among other things, aCrdtPrtfoAnlytRsltFSLossValueBulkCrteReqMsg97002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

FIG. 98 shows an example configuration of an Element Structure that includes aCrdtPrtfoAnlytRsltFSItmBulkCrteReqMsg98000 package. Specifically, this figure depicts the arrangement and hierarchy of various components such as one or more levels of packages, entities, and datatypes, shown here as98000 through98020. As described above, packages may be used to represent hierarchy levels. Entities are discrete business elements that are used during a business transaction. Data types are used to type object entities and interfaces with a structure. For example, theCrdtPrtfoAnlytRsltFSItmBulkCrteReqMsg98000 includes, among other things, aCrdtPrtfoAnlytRsltFSItmBulkCrteReqMsg98002. Accordingly, heterogeneous applications may communicate using this consistent message configured as such.

Credit Portfolio Management Process Control Interfaces

FIGS. 99-1 through99-3 illustrate an example Credit Portfolio Management Process Controlbusiness object model99000. Specifically, this model depicts interactions among various components of the Credit Portfolio Management Process Control, as well as external components that interact with the Credit Portfolio Management Process Control (shown here as99002 through99046 and99054). Credit PortfolioManagement Process Control99000 includeselements99048 through99052. Credit PortfolioManagement Process Control99000 includes for example, aData Transfer99050.

Credit Portfolio Management Process Control is the business object that is responsible for the selection of data relevant for Credit Portfolio Management, such as data from Financial Instruments Analytical Source Data, Financial Instruments Reference Data, Financial Market Data Management and Financial Instruments Results Data. It is also responsible for the transformation of these data into the Credit Portfolio Management specific view format.

FIGS. 100-1 through100-11 show an example configuration of an Element Structure that includes aCreditPortfolioManagementProcessControlMessage100000 package. TheCreditPortfolioManagementProcessControlMessage100000 package is aCreditPortfolioManagementProcessControlMessage100004 data type. TheCreditPortfolioManagementProcessControlMessage100000 package includes a CreditPortfolioManagementProcessControlMessage100002 entity. TheCreditPortfolioManagementProcessControlMessage100000 package includes various packages, namely aMessageHeader100006 and aCreditPortfolioManagementProcessControl100012.

TheMessageHeader100006 package is aBusinessDocumentMessageHeader100010 data type. TheMessageHeader100006 package includes aMessageHeader100008 entity.

TheCreditPortfolioManagementProcessControl100012 package is aCreditPortfolioManagementProcessControl100016 data type. TheCreditPortfolioManagementProcessControl100012 package includes various entities, namely aCreditPortfolioManagementProcessControl100014 and aLog100158. TheCreditPortfolioManagementProcessControl100014 entity includes various attributes, namely anID100018 and aValidityDate100022. TheID100018 attribute is aCreditPortfolioManagementProcessControlID100020 data type. TheValidityDate100022 attribute is aDate100024 data type. A ValidityDate is the specification of an exact day of the validity of a CreditPortfolioManagementProcessControl in the Gregorian calendar. A log is for informational purposes and is optional.

FIGS. 101-1 through101-3 show an example configuration of an Element Structure that includes aCrdtPrtfoMgmtProcCtrlFSReqMsg101000 package. TheCrdtPrtfoMgmtProcCtrlFSReqMsg101000 package includes aCrdtPrtfoMgmtProcCtrlFSReqMsg101002 entity. TheCrdtPrtfoMgmtProcCtrlFSReqMsg101000 package includes various packages, namely aMessageHeader101004 and aCreditPortfolioManagementProcessControl101010. TheMessageHeader101004 package includes aMessageHeader101006 entity. TheMessageHeader101006 entity has a cardinality of 1101008 meaning that for each instance of theMessageHeader101004 package there is oneMessageHeader101006 entity.

FIG. 102 shows an example configuration of an Element Structure that includes aCrdtPrtfoMgmtProcCtrlFSConfMsg102000 package. TheCrdtPrtfoMgmtProcCtrlFSConfMsg102000 package includes aCrdtPrtfoMgmtProcCtrlFSConfMsg102002 entity. TheCrdtPrtfoMgmtProcCtrlFSConfMsg102000 package includes various packages, namely aMessageHeader102004, aCreditPortfolioManagementProcessControl102010, and aLog102026.

TheMessageHeader102004 package includes aMessageHeader102006 entity. TheMessageHeader102006 entity has a cardinality of 1102008 meaning that for each instance of theMessageHeader102004 package there is oneMessageHeader102006 entity. TheCreditPortfolioManagementProcessControl102010 package includes aCreditPortfolioManagementProcessControl102012 entity. TheCreditPortfolioManagementProcessControl102010 package includes aDataTransfer102016 package.

TheCreditPortfolioManagementProcessControl102012 entity has a cardinality of 0..1102014 meaning that for each instance of theCreditPortfolioManagementProcessControl102010 package there may be oneCreditPortfolioManagementProcessControl102012 entity.

TheDataTransfer102016 package includes aDataTransfer102018 entity. TheDataTransfer102018 entity has a cardinality of 1102020 meaning that for each instance of theDataTransfer102016 package there is oneDataTransfer102018 entity. TheDataTransfer102018 entity includes anID102022 attribute. TheID102022 attribute has a cardinality of 1102024 meaning that for each instance of theDataTransfer102018 entity there is oneID102022 attribute.

TheLog102026 package includes aLog102028 entity. TheLog102028 entity has a cardinality of 1102030 meaning that for each instance of theLog102026 package there is oneLog102028 entity. The data types of the various packages, entities, and attributes are described with respect toFIG. 100.

FIGS. 103-1 through103-6 show an example configuration of an Element Structure that includes aCrdtPrtfoMgmtProcCtrlFSDataTransfStsChgdNotifMsg103000 package. TheCrdtPrtfoMgmtProcCtrlFSDataTransfStsChgdNotifMsg103000 package includes aCrdtPrtfoMgmtProcCtrlFSDataTransfStsChgdNotifMsg103002 entity. TheCrdtPrtfoMgmtProcCtrlFSDataTransfStsChgdNotifMsg103000 package includes various packages, namely aMessageHeader103004 and aCreditPortfolioManagementProcessControl103010.

TheMessageHeader103004 package includes aMessageHeader103006 entity. TheMessageHeader103006 entity has a cardinality of 1103008 meaning that for each instance of theMessageHeader103004 package there is oneMessageHeader103006 entity.

Financial Instrument Exposure Profile Analytical Result Interfaces

The message choreography ofFIG. 104 describes a possible logical sequence of messages that can be used to realize a Credit Portfolio Management business scenario.

A “Financial Instruments Exposure Profile Processing”system104002 can request the creation of several exposure profile results from a “Financial Instruments Analytical Results Management”system104000, using a Financial Instruments Exposure Profile Result FS BulkCreate Request message104004 as shown, for example, inFIG. 104. The Financial Instruments Exposure Profile Result FS BulkCreate Request message104004 is received by a Create Result as Bulk operation included in a Financial Instruments Exposure Profile Analytical Result In interface.

FIG. 105 illustrates an example Financial Instrument Exposure Profile Analytical Resultbusiness object model105000. Specifically, this model depicts interactions among various components of the Financial Instrument Exposure Profile Analytical Result, as well as external components that interact with the Financial Instrument Exposure Profile Analytical Result (shown here as105002 through105004 and105012 through105014). Financial Instrument ExposureProfile Analytical Result105000 includeselements105006 through105010. Financial Instrument ExposureProfile Analytical Result105000 includes for example, anItem105008.

Financial Instrument Exposure Profile Analytical Result is an analytical result of an exposure profile calculation of a financial instrument. The exposure profile itself is a sequence of future, discrete credit exposure amounts for pre-defined time bands up to the final maturity of the financial instrument. Exposure profiles are generated by means of an exposure profile processing, possibly provided by a third party. The Financial Instrument Exposure Profile Analytical Result interface performs various operations, namely a Create Result and a Create Result as Bulk. The Create Result operation creates the request for exposure profile data. This inbound operation is a request for creating exposure profiles. The Create Result operation includes a FinancialInstrumentExposureProfileResultFSCreateRequest message type. The structure of the FinancialInstrumentExposureProfileResultFSCreateRequest message type is specified by a FinInstrExpsrPrflAnlytlRsltFSCrteReqMsg message data type. The Create Result as Bulk operation creates the request for exposure profile data. This inbound operation is a request for creating exposure profiles. The Create Result as Bulk operation includes a FinancialInstrumentExposureProfileResultFSBulkCreateRequest message type. The structure of the FinancialInstrumentExposureProfileResultFSBulkCreateRequest message type is specified by a FinInstrExpsrPrflAnlytlRsltFSBulkCrteReqMsg message data type.

FIGS. 106-1 through106-3 show an example configuration of an Element Structure that includes aFinancialInstrumentExposureProfileAnalyticalResultFSMessage106000 package. TheFinancialInstrumentExposureProfileAnalyticalResultFSMessage106000 package is aFinInstrsExposureProfileResultFSCrteReqMsg106004 data type. TheFinancialInstrumentExposureProfileAnalyticalResultFSMessage106000 package includes a FinancialInstrumentExposureProfileAnalyticalResultFSMessage106002 entity. TheFinancialInstrumentExposureProfileAnalyticalResultFSMessage106000 package includes various packages, namely aMessageHeader106006 and aFinancialInstrumentExposureProfileAnalyticalResult106014.

TheMessageHeader106006 package is aBusinessDocumentMessageHeader106012 data type. TheMessageHeader106006 package includes aMessageHeader106008 entity. TheMessageHeader106008 entity has a cardinality of 1106010 meaning that for each instance of theMessageHeader106006 package there is oneMessageHeader106008 entity.

TheID106022 attribute is aPDT_FinancialInstrumentExposureProfileAnalyticalResultID106026 data type. TheID106022 attribute has a cardinality of 1106024 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult106016 entity there is oneID106022 attribute. A FinInstrsExposureProfileResultID is a unique identification for an exposure profile result ID.

TheGroupID106028 attribute is aBusinessTransactionDocumentGroupID106032 data type. TheGroupID106028 attribute has a cardinality of 1106030 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult106016 entity there is oneGroupID106028 attribute. A BusinessTransactionDocumentGroupID uniquely identifies a group of business documents that are to be considered as one group within a business process.

TheFinancialInstrumentID106034 attribute is aBusinessTransactionDocumentID106038 data type. TheFinancialInstrumentID106034 attribute has a cardinality of 0..1106036 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult106016 entity there may be oneFinancialInstrumentID106034 attribute. A BusinessTransactionDocumentID is a unique identifier for a business transaction document.

TheFinancialInstrumentCategoryCode106040 attribute is aFinancialInstrumentCategoryCode106044 data type. TheFinancialInstrumentCategoryCode106040 attribute has a cardinality of 0..1106042 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult106016 entity there may be one FinancialInstrumentCategoryCode106040 attribute. A FinancialInstrumentCategoryCode is the coded representation of the category of a financial instrument.

TheStandardisedFinancialInstrumentAccountID106046 attribute is aFinancialInstrumentAccountID106050 data type. TheStandardisedFinancialInstrumentAccountID106046 attribute has a cardinality of 0..1106048 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult106016 entity there may be oneStandardisedFinancialInstrumentAccountID106046 attribute. A FinancialInstrumentAccountID is the unique identifier of an account for financial instruments.

TheKeyDate106052 attribute is aDate106056 data type. TheKeyDate106052 attribute has a cardinality of 1106054 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult106016 entity there is oneKeyDate106052 attribute. A Date is the specification of an exact day in the Gregorian calendar. TheCreationDateTime106058 attribute is aGLOBAL_DateTime106062 data type. TheCreationDateTime106058 attribute has a cardinality of 1106060 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult106016 entity there is oneCreationDateTime106058 attribute. A GLOBAL_DateTime is an accurate-to-the-second time-point of a calendar day in timezone UTC.

TheMaximumOriginalMaturityDuration106064 attribute is aDAY_Duration106068 data type. TheMaximumOriginalMaturityDuration106064 attribute has a cardinality of 0..1106066 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult106016 entity there may be one MaximumOriginalMaturityDuration106064 attribute.

TheItem106070 package is aFinInstrsExposureProfileResultItem106076 data type. TheItem106070 package includes anItem106072 entity. TheItem106072 entity has a cardinality of 0..n106074 meaning that for each instance of theItem106070 package there may be one ormore Item106072 entities. TheItem106072 entity includes various attributes, namely aDate106078, aPositiveExposureAmount106084, aNegativeExposureAmount106090 and aProperty106096.

TheDate106078 attribute is aDate106082 data type. TheDate106078 attribute has a cardinality of 1106080 meaning that for each instance of theItem106072 entity there is oneDate106078 attribute. A Date is the specification of an exact day of a risk-free profile in the Gregorian calendar.

ThePositiveExposureAmount106084 attribute is anAmount106088 data type. ThePositiveExposureAmount106084 attribute has a cardinality of 0..1106086 meaning that for each instance of theItem106072 entity there may be one PositiveExposureAmount106084 attribute. A PositiveExposureAmount is the positive exposure amount of an exposure profile analytical result item. TheNegativeExposureAmount106090 attribute is anAmount106094 data type. TheNegativeExposureAmount106090 attribute has a cardinality of 0..1106092 meaning that for each instance of theItem106072 entity there may be one NegativeExposureAmount106090 attribute. A NegativeExposureAmount is the negative exposure amount of an exposure profile analytical result item.

TheProperty106096 attribute is aProperty106100 data type. TheProperty106096 attribute has a cardinality of 0..n106098 meaning that for each instance of theItem106072 entity there may be one ormore Property106096 attributes. A property is an object attribute.

FIGS. 107-1 through107-4 show an example configuration of an Element Structure that includes aFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg107000 package. TheFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg107000 package is aFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg107004 data type. TheFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg107000 package includes aFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg107002 entity. TheFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg107000 package includes various packages, namely aMessageHeader107006 and aFinancialInstrumentExposureProfileAnalyticalResult107014.

TheMessageHeader107006 package is aBusinessDocumentMessageHeader107012 data type. TheMessageHeader107006 package includes aMessageHeader107008 entity. TheMessageHeader107008 entity has a cardinality of 1107010 meaning that for each instance of theMessageHeader107006 package there is oneMessageHeader107008 entity.

TheID107022 attribute is aPDT_FinancialInstrumentExposureProfileAnalyticalResultID107026 data type. TheID107022 attribute has a cardinality of 1107024 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult107016 entity there is oneID107022 attribute. A FinInstrsExposureProfileResultID is a unique identification for an exposure profile result ID.

TheGroupID107028 attribute is aBusinessTransactionDocumentGroupID107032 data type. TheGroupID107028 attribute has a cardinality of 1107030 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult107016 entity there is oneGroupID107028 attribute. A BusinessTransactionDocumentGroupID uniquely identifies a group of business documents that are to be considered as one group within a business process.

TheFinancialInstrumentID107034 attribute is aBusinessTransactionDocumentID107038 data type. TheFinancialInstrumentID107034 attribute has a cardinality of 0..1107036 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult107016 entity there may be oneFinancialInstrumentID107034 attribute. A BusinessTransactionDocumentID is a unique identifier for a business transaction document.

TheFinancialInstrumentCategoryCode107040 attribute is aFinancialInstrumentCategoryCode107044 data type. TheFinancialInstrumentCategoryCode107040 attribute has a cardinality of 0..1107042 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult107016 entity there may be one FinancialInstrumentCategoryCode107040 attribute. The FinancialInstrumentCategoryCode is the coded representation of the category of a financial instrument.

TheStandardisedFinancialInstrumentAccountID107046 attribute is aFinancialInstrumentAccountID107050 data type. TheStandardisedFinancialInstrumentAccountID107046 attribute has a cardinality of 0..1107048 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult107016 entity there may be oneStandardisedFinancialInstrumentAccountID107046 attribute. A FinancialInstrumentAccountID is the unique identifier of an account for financial instruments.

TheKeyDate107052 attribute is aDate107056 data type. TheKeyDate107052 attribute has a cardinality of 1107054 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult107016 entity there is oneKeyDate107052 attribute. A Date is the specification of an exact day in the Gregorian calendar.

TheCreationDateTime107058 attribute is aGLOBAL_DateTime107062 data type. TheCreationDateTime107058 attribute has a cardinality of 1107060 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult107016 entity there is oneCreationDateTime107058 attribute. A GLOBAL_DateTime is the accurate-to-the-second time-point of a calendar day in timezone UTC.

TheMaximumOriginalMaturityDuration107064 attribute is aDAY_Duration107068 data type. TheMaximumOriginalMaturityDuration107064 attribute has a cardinality of 0..1107066 meaning that for each instance of theFinancialInstrumentExposureProfileAnalyticalResult107016 entity there may be one MaximumOriginalMaturityDuration107064 attribute. A Duration is a period of time of a particular length without a fixed start or end time. This period of time is expressed in years, months, days, hours, minutes, seconds, and fractions of a second. A MaximumOriginalMaturityDuration is the maximum original duration of all considered financial instruments in case of netting agreements.

TheItem107070 package is aFinInstrExpsrPrflAnlytlRsltFSCrteReqMsgAnltlRsltItm107076 data type. TheItem107070 package includes anItem107072 entity. TheItem107070 package includes aProperty107096 package. TheItem107072 entity has a cardinality of 0..n107074 meaning that for each instance of theItem107070 package there may be one ormore Item107072 entities. TheItem107072 entity includes various attributes, namely aDate107078, aPositiveExposureAmount107084 and aNegativeExposureAmount107090.

TheDate107078 attribute is aDate107082 data type. TheDate107078 attribute has a cardinality of 1107080 meaning that for each instance of theItem107072 entity there is oneDate107078 attribute. A Date is the specification of an exact day of a risk-free profile in the Gregorian calendar.

ThePositiveExposureAmount107084 attribute is anAmount107088 data type. ThePositiveExposureAmount107084 attribute has a cardinality of 0..1107086 meaning that for each instance of theItem107072 entity there may be one PositiveExposureAmount107084 attribute. A PositiveExposureAmount is the positive exposure amount of an exposure profile analytical result item. TheNegativeExposureAmount107090 attribute is anAmount107094 data type. TheNegativeExposureAmount107090 attribute has a cardinality of 0..1107092 meaning that for each instance of theItem107072 entity there may be one NegativeExposureAmount107090 attribute. A NegativeExposureAmount is the negative exposure amount of an exposure profile analytical result item.

TheProperty107096 package is aFinInstrExpsrPrflAnlytlRsltFSCrteReqMsgAnltlRsltItmProp107102 data type. TheProperty107096 package includes aProperty107098 entity. TheProperty107098 entity has a cardinality of 0..n107100 meaning that for each instance of theProperty107096 package there may be one ormore Property107098 entities. A property is an object attribute. TheProperty107098 entity includes various attributes, namely anID107104 and aValue107110. TheID107104 attribute is aPropertyID107108 data type. TheID107104 attribute has a cardinality of 1107106 meaning that for each instance of theProperty107098 entity there is oneID107104 attribute. TheValue107110 attribute is aPropertyValue107114 data type. TheValue107110 attribute has a cardinality of 1107112 meaning that for each instance of theProperty107098 entity there is oneValue107110 attribute.

FIG. 108 shows an example configuration of an Element Structure that includes aFinInstrExpsrPrflAnlytlRsltFSBulkCrteReqMsg108000 package. TheFinInstrExpsrPrflAnlytlRsltFSBulkCrteReqMsg108000 package is aFinInstrExpsrPrflAnlytlRsltFSBulkCrteReqMsg108004 data type. TheFinInstrExpsrPrflAnlytlRsltFSBulkCrteReqMsg108000 package includes a FinancialInstrumentsExposureProfileAnalyticalResultFSCreateRequestMessage108002 entity. TheFinInstrExpsrPrflAnlytlRsltFSBulkCrteReqMsg108000 package includes various packages, namely aMessageHeader108006 and aFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg108014.

TheMessageHeader108006 package is aBusinessDocumentMessageHeader108012 data type. TheMessageHeader108006 package includes aMessageHeader108008 entity. TheMessageHeader108008 entity has a cardinality of 1108010 meaning that for each instance of theMessageHeader108006 package there is oneMessageHeader108008 entity.

TheFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg108014 package is aFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg108020 data type. TheFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg108014 package includes aFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg108016 entity. TheFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg108016 entity has a cardinality of 1..n108018 meaning that for each instance of theFinInstrExpsrPrflAnlytlRsltFSCrteReqMsg108014 package there are one or more FinInstrExpsrPrflAnlytlRsltFSCrteReqMsg108016 entities. A FinancialInstrumentExposureProfileResultFSCreateRequest creates the request for exposure profile data.

MaterialSupplyAndDemandAllocation Interfaces

In the fashion industry there are several weeks or months between the order creation and the delivery of the goods to the customer. In this time period, there could be shortage in supply due to several reasons. Material Supply and Demand allocation will be used to optimally allocate the available quantities to open requirements. The MaterialSupplyAndDemandAllocation interface performs various operations, namely a MaterialSupplyAndDemandAllocationERPCreateRequestConfirmation_In, a MaterialSupplyAndDemandAllocationERPCancelRequestConfirmation_In, a MaterialSupplyAndDemandAllocationERPByIDQueryResponse_In, a MaterialSupplyAndDemandAllocationERPItemUpdateRequestConfirmation_In, a MaterialSupplyAndDemandAllocationERPByElementsQueryResponse_In, and a MaterialSupplyAndDemandAllocationERPCreateCheckQueryResponse_In.

FIGS. 109-1 through109-11 show an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationMessage109000 package. TheMaterialSupplyAndDemandAllocationMessage109000 package is aMatlSupAndDmndAllocMsg109004 data type. TheMaterialSupplyAndDemandAllocationMessage109000 package includes a MaterialSupplyAndDemandAllocationMessage109002 entity. TheMaterialSupplyAndDemandAllocationMessage109000 package includes various packages, namely aMessageHeader109006, aMaterialSupplyAndDemandAllocationERP109012, aProcessingConditions109198 and aLog109214.

The message data type MaterialSupplyAndDemandAllocationMessage is used as an abstract maximal message data type, which unifies all packages and entities for the following concrete message data types.

TheMessageHeader109006 package is aBasicBusinessDocumentMessageHeader109010 data type. TheMessageHeader109006 package includes aMessageHeader109008 entity. A BasicBusinessDocumentMessageHeader is a collection of identification data of an instance of a business document message, or reference data to another instance of a business document message, or both. The subject of the identification data is the message instance that conveys them, whereas the reference data are related to a different message instance previously exchanged between the same interaction parties.

TheItem109046 entity includes various attributes, namely a @actionCode109048, aProductInternalID109052, aPhysicalPropertyValueCombinationID109056, aPlantID109060, aMaterialSupplyAndDemandAllocationStatusCode109064, aMaterialSupplyAndDemandAllocationStatusName109068, aMaterialSupplyAndDemandAllocationUserStatusCode109072 and aMaterialSupplyAndDemandAllocationUserStatusName109076. TheItem109046 entity includes various subordinate entities, namely aDemandReference109080, aSupplyReference109122 and aQuantity109180. The @actionCode109048 attribute is anActionCode109050 data type. An ActionCode is an operation to be performed (e.g., Allocate, Release, Block). TheProductInternalID109052 attribute is aProductInternalID109054 data type. A ProductInternalID is an identifier specified for a product. ThePhysicalPropertyValueCombinationID109056 attribute is aPropertyValueCombinationID109058 data type. A PhysicalPropertyValueCombinationID is an identifier for value combination of values of different properties of product configuration which are represented by matrix-defining properties and allowed values for a matrix material or product (e.g., Color, Size). It is a concatenated value of characteristic values which define structural properties (e.g., Color, Size) defined for a Matrix Material. The combination can include up to three characteristic values in one grid. ThePlantID109060 attribute is aPlantID109062 data type. A PlantID is a proprietary identifier for a location.

TheDemandReference109080 entity includes various attributes, namely anID109082, anItemID109086, anAlternateItemID109090, aMaterialSupplyAndDemandTypeCode109094, aMaterialSupplyAndDemandTypeName109098, aRequirementSegmentationPropertyValueCombinationID109102, aSoldtoPartyInternalID109106, aShiptoPartyInternalID109110, aProductAvailabilityDate109114 and aSalesOrderItemScheduleLineDate109118. TheID109082 attribute is aBusinessTransactionDocumentID109084 data type. An ID is a unique identifier assigned by the buyer for a SalesOrder. TheItemID109086 attribute is aBusinessTransactionDocumentItemID109088 data type. An ItemID is a unique identifier assigned by the buyer for a SalesOrderItem. TheAlternateItemID109090 attribute is aBusinessTransactionDocumentItemID109092 data type. An AlternateItemID is a unique identifier assigned by the buyer for a SalesOrderItem. TheMaterialSupplyAndDemandTypeCode109094 attribute is aMaterialSupplyAndDemandTypeCode109096 data type. TheMaterialSupplyAndDemandTypeName109098 attribute is aLONG Name109100 data type.

TheRequirementSegmentationPropertyValueCombinationID109102 attribute is aPropertyValueCombinationID109104 data type. A RequirementSegmentationPropertyValueCombinationID is an identifier for value combination of Values of different segmentation properties of a matrix material or product when used in a requirement item (e.g., Sales Order Item). It is a concatenated value of characteristic values which define segmentation properties (e.g., Country of Origin, Quality) defined for a Matrix Material. TheSoldtoPartyInternalID109106 attribute is aPartyInternalID109108 data type. A PartyInternalID is a proprietary identifier for a party. TheShiptoPartyInternalID109110 attribute is aPartyInternalID109112 data type. A PartyInternalID is a proprietary identifier for a party.

TheProductAvailabilityDate109114 attribute is aDate109116 data type. A ProductAvailabilityDate is an Availability Time Point. TheSalesOrderItemScheduleLineDate109118 attribute is aDate109120 data type. A SalesOrderItemScheduleLineDate is a Date of a ScheduleLine, such as a Confirmed Delivery Date for a Schedule Line (e.g., Sales Order). TheSupplyReference109122 entity includes various attributes, namely anID109124, anItemID109128, anAlternateItemID109132, aBatchID109136, anInventoryManagedLocationInternalID109140, aMaterialSupplyAndDemandTypeCode109144, aMaterialSupplyAndDemandTypeName109148, anInventorySpecialStockTypeCode109152, anInventorySpecialStockTypeName109156, aStockSegmentationAllowedPropertyValueCombinationID109160, aVendorPartyInternalID109164, aReceiptdate109168, aPurchaseOrderItemScheduleLineDeliveryDate109172 and aPurchaseOrderItemConfirmationDeliveryDate109176. TheID109124 attribute is aBusinessTransactionDocumentID109126 data type. A BusinessTransactionDocumentID is a unique identifier for a business transaction document. TheItemID109128 attribute is aBusinessTransactionDocumentItemID109130 data type. An ItemID is a unique identifier assigned by the buyer for a SalesOrderItem. TheAlternateItemID109132 attribute is aBusinessTransactionDocumentItemID109134 data type. An AlternateItemID is a unique identifier assigned by the buyer for a SalesOrderItem. TheBatchID109136 attribute is aBatchID109138 data type. A BatchID is a unique identifier for a batch in the context of a material number. TheInventoryManagedLocationInternalID109140 attribute is aLocationInternalID109142 data type. An InventoryManagedLocationInternalID is the storage location at which materials are stored. TheMaterialSupplyAndDemandTypeCode109144 attribute is aMaterialSupplyAndDemandTypeCode109146 data type. A MaterialSupplyAndDemandTypeCode is a StockType (e.g., Batch, Purchase Order). TheMaterialSupplyAndDemandTypeName109148 attribute is aLONG_Name109150 data type. A MaterialSupplyAndDemandTypeName is a Name of StockTypeCode. TheInventorySpecialStockTypeCode109152 attribute is anInventorySpecialStockTypeCode109154 data type. An InventorySpecialStockTypeCode is the coded representation of an inventory special stock type. A special stock is a separate stock within inventory management and is a stock of a material that is managed separately due to the ownership situation or the location where it is held (e.g., consignment stock of the vendor). TheInventorySpecialStockTypeName109156 attribute is aMEDIUM_Name109158 data type. An InventorySpecialStockTypeName is a Name of Inventory Special StockType code. TheStockSegmentationAllowedPropertyValueCombinationID109160 attribute is aPropertyValueCombinationID109162 data type. A PropertyValueCombinationID is an identifier for combination of values of different properties. It can contain concatenated value of characteristic values which define properties (e.g., color, size, quality, country of origin) of a matrix material. TheVendorPartyInternalID109164 attribute is aPartyInternalID109166 data type. A PartyInternalID is a proprietary identifier for a party. TheReceiptdate109168 attribute is aDate109170 data type. A Receiptdate is a Receipt Time Point. ThePurchaseOrderItemScheduleLineDeliveryDate109172 attribute is aDate109174 data type. A PurchaseOrderItemScheduleLineDeliveryDate is a Delivery Time Point, such as a Confirmed Delivery Date for Schedule Line (e.g., Purchase Order). ThePurchaseOrderItemConfirmationDeliveryDate109176 attribute is aDate109178 data type. A PurchaseOrderItemConfirmationDeliveryDate is a Delivery Time Point, such as a Notified Delivery Date for Schedule Line (e.g., Purchase Order). TheQuantity109180 entity includes various attributes, namely anOpenQuantity109182, aReleasedAllocatedQuantity109186, aReservedAllocatedQuantity109190 and aDeliveredQuantity109194. TheOpenQuantity109182 attribute is aQuantity109184 data type. An OpenQuantity is a Quantity that has not yet been delivered, moved, produced, checked or packed. TheReleasedAllocatedQuantity109186 attribute is aQuantity109188 data type. A ReleasedAllocatedQuantity is an Allocated quantity which is released for delivery. TheReservedAllocatedQuantity109190 attribute is aQuantity109192 data type. A ReservedAllocatedQuantity is an Allocated quantity which is not released. TheDeliveredQuantity109194 attribute is aQuantity109196 data type. A DeliveredQuantity is an Acknowledged or Delivered Quantity. TheProcessingConditions109198 package includes aProcessingConditions109200 entity. TheProcessingConditions109200 entity includes various attributes, namely aQueryHitsMaximumNumberValue109202, aReturnedQueryHitsNumberValue109206 and aMoreElementsAvailableIndicator109210. TheQueryHitsMaximumNumberValue109202 attribute is aNumberValue109204 data type. TheReturnedQueryHitsNumberValue109206 attribute is aNumberValue109208 data type. TheMoreElementsAvailableIndicator109210 attribute is anIndicator109212 data type. TheLog109214 package is aLOG109218 data type. TheLog109214 package includes aLog109216 entity. A Log is a sequence of messages that result when an application executes a task.

FIGS. 110-1 through110-3 show an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPCreateRequestMessage_sync110000 package. TheMaterialSupplyAndDemandAllocationERPCreateRequestMessage_sync110000 package includes aMaterialSupplyAndDemandAllocationERPCreateRequestMessage_sync110002 entity. TheMaterialSupplyAndDemandAllocationERPCreateRequestMessage_sync110000 package includes various packages, namely aMessageHeader110004 and aMaterialSupplyAndDemandAllocationERP110010.

TheMessageHeader110004 package includes aMessageHeader110006 entity. TheMessageHeader110006 entity has a cardinality of 0..1110008 meaning that for each instance of theMessageHeader110004 package there may be one MessageHeader110006 entity.

FIGS. 111-1 through111-9 show an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPCreateConfirmationMessage_sync111000 package. TheMaterialSupplyAndDemandAllocationERPCreateConfirmationMessage_sync111000 package includes aMaterialSupplyAndDemandAllocationERPCreateConfirmationMessage_sync111002 entity. TheMaterialSupplyAndDemandAllocationERPCreateConfirmationMessage_sync111000 package includes various packages, namely aMessageHeader111004, aMaterialSupplyAndDemandAllocationERP111010 and aLog111200.

TheMessageHeader111004 package includes aMessageHeader111006 entity. TheMessageHeader111006 entity has a cardinality of 0..1111008 meaning that for each instance of theMessageHeader111004 package there may be one MessageHeader111006 entity.

TheSystemAdministrativeData111028 entity has a cardinality of 1111030 meaning that for each instance of theMaterialSupplyAndDemandAllocation111012 entity there is oneSystemAdministrativeData111028 entity. TheSystemAdministrativeData111028 entity includes various attributes, namely aCreationDate111032, aCreationUserAccountID111036 and aLastChangeDate111040. TheCreationDate111032 attribute has a cardinality of 0..1111034 meaning that for each instance of theSystemAdministrativeData111028 entity there may be one CreationDate111032 attribute. TheCreationUserAccountID111036 attribute has a cardinality of 1111038 meaning that for each instance of theSystemAdministrativeData111028 entity there is oneCreationUserAccountID111036 attribute. TheLastChangeDate111040 attribute has a cardinality of 0..1111042 meaning that for each instance of theSystemAdministrativeData111028 entity there may be one LastChangeDate111040 attribute.

TheDemandReference111076 entity has a cardinality of 1111078 meaning that for each instance of theItem111044 entity there is oneDemandReference111076 entity. TheDemandReference111076 entity includes various attributes, namely anID111080, anItemID111084, anAlternateItemID111088, aMaterialSupplyAndDemandTypeCode111092, aMaterialSupplyAndDemandTypeName111096, aRequirementSegmentationPropertyValueCombinationID111100, aSoldtoPartyInternalID111104, aShiptoPartyInternalID111108, aProductAvailabilityDate111112 and aSalesOrderItemScheduleLineDate111116. TheID111080 attribute has a cardinality of 1111082 meaning that for each instance of theDemandReference111076 entity there is oneID111080 attribute. TheItemID111084 attribute has a cardinality of 1111086 meaning that for each instance of theDemandReference111076 entity there is oneItemID111084 attribute. TheAlternateItemID111088 attribute has a cardinality of 1111090 meaning that for each instance of theDemandReference111076 entity there is oneAlternateItemID111088 attribute. TheMaterialSupplyAndDemandTypeCode111092 attribute has a cardinality of 1111094 meaning that for each instance of theDemandReference111076 entity there is oneMaterialSupplyAndDemandTypeCode111092 attribute. TheMaterialSupplyAndDemandTypeName111096 attribute has a cardinality of 1111098 meaning that for each instance of theDemandReference111076 entity there is oneMaterialSupplyAndDemandTypeName111096 attribute. TheRequirementSegmentationPropertyValueCombinationID111100 attribute has a cardinality of 0..1111102 meaning that for each instance of theDemandReference111076 entity there may be oneRequirementSegmentationPropertyValueCombinationID111100 attribute. TheSoldtoPartyInternalID111104 attribute has a cardinality of 0..1111106 meaning that for each instance of theDemandReference111076 entity there may be oneSoldtoPartyInternalID111104 attribute. TheShiptoPartyInternalID111108 attribute has a cardinality of 0..1111110 meaning that for each instance of theDemandReference111076 entity there may be oneShiptoPartyInternalID111108 attribute. TheProductAvailabilityDate111112 attribute has a cardinality of 0..1111114 meaning that for each instance of theDemandReference111076 entity there may be one ProductAvailabilityDate111112 attribute. TheSalesOrderItemScheduleLineDate111116 attribute has a cardinality of 0..1111118 meaning that for each instance of theDemandReference111076 entity there may be one SalesOrderItemScheduleLineDate111116 attribute.

TheQuantity111180 entity has a cardinality of 0..1111182 meaning that for each instance of theItem111044 entity there may be oneQuantity111180 entity. TheQuantity111180 entity includes various attributes, namely anOpenQuantity111184, aReleasedAllocatedQuantity111188, aReservedAllocatedQuantity111192 and aDeliveredQuantity111196. TheOpenQuantity111184 attribute has a cardinality of 0..1111186 meaning that for each instance of theQuantity111180 entity there may be one OpenQuantity111184 attribute. TheReleasedAllocatedQuantity111188 attribute has a cardinality of 0..1111190 meaning that for each instance of theQuantity111180 entity there may be one ReleasedAllocatedQuantity111188 attribute. TheReservedAllocatedQuantity111192 attribute has a cardinality of 0..1111194 meaning that for each instance of theQuantity111180 entity there may be one ReservedAllocatedQuantity111192 attribute. TheDeliveredQuantity111196 attribute has a cardinality of 0..1111198 meaning that for each instance of theQuantity111180 entity there may be one DeliveredQuantity111196 attribute.

TheLog111200 package includes aLog111202 entity. TheLog111202 entity has a cardinality of 1111204 meaning that for each instance of theLog111200 package there is oneLog111202 entity. The data types of the various packages, entities, and attributes are described with respect toFIGS. 109-1 through109-11.

FIGS. 112-1 through112-4 show an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPCancelRequestMessage_sync112000 package. TheMaterialSupplyAndDemandAllocationERPCancelRequestMessage_sync112000 package includes aMaterialSupplyAndDemandAllocationERPCancelRequestMessage_sync112002 entity. TheMaterialSupplyAndDemandAllocationERPCancelRequestMessage_sync112000 package includes various packages, namely aMessageHeader112004 and aMaterialSupplyAndDemandAllocationERP112010.

TheMessageHeader112004 package includes aMessageHeader112006 entity. TheMessageHeader112006 entity has a cardinality of 0.1112008 meaning that for each instance of theMessageHeader112004 package there may be one MessageHeader112006 entity.

TheItem112024 entity has a cardinality of 1..n112026 meaning that for each instance of theMaterialSupplyAndDemandAllocation112012 entity there are one ormore Item112024 entities. TheItem112024 entity includes various attributes, namely aProductInternalID112028, aPlantID112032 and aMaterialSupplyAndDemandAllocationStatusCode112036. TheItem112024 entity includes various subordinate entities, namely aDemandReference112040, aSupplyReference112060 and aQuantity112092. TheProductInternalID112028 attribute has a cardinality of 0..1112030 meaning that for each instance of theItem112024 entity there may be oneProductInternalID112028 attribute. ThePlantID112032 attribute has a cardinality of 0..1112034 meaning that for each instance of theItem112024 entity there may be onePlantID112032 attribute. TheMaterialSupplyAndDemandAllocationStatusCode112036 attribute has a cardinality of 0..1112038 meaning that for each instance of theItem112024 entity there may be one MaterialSupplyAndDemandAllocationStatusCode112036 attribute.

TheDemandReference112040 entity has a cardinality of 1112042 meaning that for each instance of theItem112024 entity there is oneDemandReference112040 entity. TheDemandReference112040 entity includes various attributes, namely anID112044, anItemID112048, anAlternateItemID112052 and aSoldtoPartyInternalID112056. TheID112044 attribute has a cardinality of 1112046 meaning that for each instance of theDemandReference112040 entity there is oneID112044 attribute. TheItemID112048 attribute has a cardinality of 0..1112050 meaning that for each instance of theDemandReference112040 entity there may be oneItemID112048 attribute. TheAlternateItemID112052 attribute has a cardinality of 0..1112054 meaning that for each instance of theDemandReference112040 entity there may be oneAlternateItemID112052 attribute. TheSoldtoPartyInternalID112056 attribute has a cardinality of 0..1112058 meaning that for each instance of theDemandReference112040 entity there may be oneSoldtoPartyInternalID112056 attribute.

TheQuantity112092 entity has a cardinality of 0..1112094 meaning that for each instance of theItem112024 entity there may be oneQuantity112092 entity. TheQuantity112092 entity includes anOpenQuantity112096 attribute. TheOpenQuantity112096 attribute has a cardinality of 0..1112098 meaning that for each instance of theQuantity112092 entity there may be one OpenQuantity112096 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 109-1 through109-11.

FIG. 113 shows an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPCancelConfirmationMessage_sync113000 package. TheMaterialSupplyAndDemandAllocationERPCancelConfirmationMessage_sync113000 package includes aMaterialSupplyAndDemandAllocationERPCancelConfirmationMessage_sync113002 entity. TheMaterialSupplyAndDemandAllocationERPCancelConfirmationMessage_sync113000 package includes various packages, namely aMessageHeader113004 and aLog113010.

TheMessageHeader113004 package includes aMessageHeader113006 entity. TheMessageHeader113006 entity has a cardinality of 0..1113008 meaning that for each instance of theMessageHeader113004 package there may be one MessageHeader113006 entity.

TheLog113010 package includes aLog113012 entity. TheLog113012 entity has a cardinality of 1113014 meaning that for each instance of theLog113010 package there is oneLog113012 entity. The data types of the various packages, entities, and attributes are described with respect toFIGS. 109-1 through109-11.

FIG. 114 shows an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPByIDQueryMessage_sync114000 package. TheMaterialSupplyAndDemandAllocationERPByIDQueryMessage_sync114000 package includes aMaterialSupplyAndDemandAllocationERPByIDQueryMessage_sync114002 entity. TheMaterialSupplyAndDemandAllocationERPByIDQueryMessage_sync114000 package includes aMaterialSupplyAndDemandAllocationERP114004 package.

FIGS. 115-1 through115-9 show an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPByIDResponseMessage_sync115000 package. TheMaterialSupplyAndDemandAllocationERPByIDResponseMessage_sync115000 package includes aMaterialSupplyAndDemandAllocationERPByIDResponseMessage_sync115002 entity. TheMaterialSupplyAndDemandAllocationERPByIDResponseMessage_sync115000 package includes various packages, namely aMaterialSupplyAndDemandAllocationERP115004 and aLog115190.

TheMaterialSupplyAndDemandAllocationERP115004 package includes aMaterialSupplyAndDemandAllocation115006 entity. TheMaterialSupplyAndDemandAllocation115006 entity has a cardinality of 1115008 meaning that for each instance of theMaterialSupplyAndDemandAllocationERP115004 package there is oneMaterialSupplyAndDemandAllocation115006 entity. TheMaterialSupplyAndDemandAllocation115006 entity includes various attributes, namely anID115010 and aChangeStateID115014. TheMaterialSupplyAndDemandAllocation115006 entity includes various subordinate entities, namely aSystemAdministrativeData115018 and anItem115034. TheID115010 attribute has a cardinality of 1115012 meaning that for each instance of theMaterialSupplyAndDemandAllocation115006 entity there is oneID115010 attribute. TheChangeStateID115014 attribute has a cardinality of 1115016 meaning that for each instance of theMaterialSupplyAndDemandAllocation115006 entity there is oneChangeStateID115014 attribute.

TheSystemAdministrativeData115018 entity has a cardinality of 1115020 meaning that for each instance of theMaterialSupplyAndDemandAllocation115006 entity there is oneSystemAdministrativeData115018 entity. TheSystemAdministrativeData115018 entity includes various attributes, namely aCreationDate115022, aCreationUserAccountID115026 and aLastChangeDate115030. TheCreationDate115022 attribute has a cardinality of 0..1115024 meaning that for each instance of theSystemAdministrativeData115018 entity there may be one CreationDate115022 attribute. TheCreationUserAccountID115026 attribute has a cardinality of 1115028 meaning that for each instance of theSystemAdministrativeData115018 entity there is oneCreationUserAccountID115026 attribute. TheLastChangeDate115030 attribute has a cardinality of 0..1115032 meaning that for each instance of theSystemAdministrativeData115018 entity there may be one LastChangeDate115030 attribute.

TheDemandReference115066 entity has a cardinality of 1115068 meaning that for each instance of theItem115034 entity there is oneDemandReference115066 entity. TheDemandReference115066 entity includes various attributes, namely anID115070, anItemID115074, anAlternateItemID115078, aMaterialSupplyAndDemandTypeCode115082, aMaterialSupplyAndDemandTypeName115086, aRequirementSegmentationPropertyValueCombinationID115090, aSoldtoPartyInternalID115094, aShiptoPartyInternalID115098, aProductAvailabilityDate115102 and aSalesOrderItemScheduleLineDate115106. TheID115070 attribute has a cardinality of 1115072 meaning that for each instance of theDemandReference115066 entity there is oneID115070 attribute. TheItemID115074 attribute has a cardinality of 1115076 meaning that for each instance of theDemandReference115066 entity there is oneItemID115074 attribute. TheAlternateItemID115078 attribute has a cardinality of 1115080 meaning that for each instance of theDemandReference115066 entity there is oneAlternateItemID115078 attribute. TheMaterialSupplyAndDemandTypeCode115082 attribute has a cardinality of 1115084 meaning that for each instance of theDemandReference115066 entity there is oneMaterialSupplyAndDemandTypeCode115082 attribute. TheMaterialSupplyAndDemandTypeName115086 attribute has a cardinality of 1115088 meaning that for each instance of theDemandReference115066 entity there is oneMaterialSupplyAndDemandTypeName115086 attribute. TheRequirementSegmentationPropertyValueCombinationID115090 attribute has a cardinality of 0..1115092 meaning that for each instance of theDemandReference115066 entity there may be oneRequirementSegmentationPropertyValueCombinationID115090 attribute. TheSoldtoPartyInternalID115094 attribute has a cardinality of 0..1115096 meaning that for each instance of theDemandReference115066 entity there may be oneSoldtoPartyInternalID115094 attribute. TheShiptoPartyInternalID115098 attribute has a cardinality of 0..1115100 meaning that for each instance of theDemandReference115066 entity there may be oneShiptoPartyInternalID115098 attribute. TheProductAvailabilityDate115102 attribute has a cardinality of 0..1115104 meaning that for each instance of theDemandReference115066 entity there may be one ProductAvailabilityDate115102 attribute. TheSalesOrderItemScheduleLineDate115106 attribute has a cardinality of 0..1115108 meaning that for each instance of theDemandReference115066 entity there may be one SalesOrderItemScheduleLineDate115106 attribute.

TheQuantity115170 entity has a cardinality of 0..1115172 meaning that for each instance of theItem115034 entity there may be oneQuantity115170 entity. TheQuantity115170 entity includes various attributes, namely anOpenQuantity115174, aReleasedAllocatedQuantity115178, aReservedAllocatedQuantity115182 and aDeliveredQuantity115186. TheOpenQuantity115174 attribute has a cardinality of 0..1115176 meaning that for each instance of theQuantity115170 entity there may be one OpenQuantity115174 attribute. TheReleasedAllocatedQuantity115178 attribute has a cardinality of 0..1115180 meaning that for each instance of theQuantity115170 entity there may be one ReleasedAllocatedQuantity115178 attribute. TheReservedAllocatedQuantity115182 attribute has a cardinality of 0..1115184 meaning that for each instance of theQuantity115170 entity there may be one ReservedAllocatedQuantity115182 attribute. TheDeliveredQuantity115186 attribute has a cardinality of 0..1115188 meaning that for each instance of theQuantity115170 entity there may be one DeliveredQuantity115186 attribute.

TheLog115190 package includes aLog115192 entity. TheLog115192 entity has a cardinality of 1115194 meaning that for each instance of theLog115190 package there is oneLog115192 entity. The data types of the various packages, entities, and attributes are described with respect toFIGS. 109-1 through109-11.

FIGS. 116-1 through116-13 show an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPByElementsQueryMessage_sync116000 package. TheMaterialSupplyAndDemandAllocationERPByElementsQueryMessage_sync116000 package includes aMaterialSupplyAndDemandAllocationERPByElementsQueryMessage_sync116002 entity. TheMaterialSupplyAndDemandAllocationERPByElementsQueryMessage_sync116000 package includes aSelection116004 package.

TheSelection116004 package includes various entities, namely anItemBasicDataSelectionByElements116006 and aProcessingConditions116292. TheItemBasicDataSelectionByElements116006 entity has a cardinality of 1116008 meaning that for each instance of theSelection116004 package there is one ItemBasicDataSelectionByElements116006 entity. TheItemBasicDataSelectionByElements116006 entity includes various subordinate entities, namely aSelectionByID116010, aSelectionByRequirementDocumentID116030, aSelectionByRequirementSegmentationPropertyValueCombinationID116050, aSelectionByProductionOrderID116070, aSelectionByPurchaseOrderID116090, aSelectionByBatchD116110, aSelectionByVendorID116130, aSelectionByStockSegmentationAllowedPropertyValueCombinationID116150, aSelectionByMaterialSupplyAndDemandAllocationStatusCode116170, aSelectionByProductID116190, aSelectionByPhysicalPropertyValueCombinationID116210, aSelectionByLocationID116230, aSelectionBySoldtoParty116250 and aSelectionByProductAvailabilityDate116270.

TheSelectionByID116010 entity has a cardinality of 0..N116012 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionByID116010 entities. TheSelectionByID116010 entity includes various attributes, namely anInclusionExclusionCode116014, anIntervalBoundaryTypeCode116018, aLowerBoundaryMaterialSupplyAndDemandAllocationID116022 and anUpperBoundaryMaterialSupplyAndDemandAllocationID116026. TheInclusionExclusionCode116014 attribute has a cardinality of 0..1116016 meaning that for each instance of theSelectionByID116010 entity there may be one InclusionExclusionCode116014 attribute. TheIntervalBoundaryTypeCode116018 attribute has a cardinality of 0..1116020 meaning that for each instance of theSelectionByID116010 entity there may be one IntervalBoundaryTypeCode116018 attribute. TheLowerBoundaryMaterialSupplyAndDemandAllocationID116022 attribute has a cardinality of 0..1116024 meaning that for each instance of theSelectionByID116010 entity there may be oneLowerBoundaryMaterialSupplyAndDemandAllocationID116022 attribute. TheUpperBoundaryMaterialSupplyAndDemandAllocationID116026 attribute has a cardinality of 0..1116028 meaning that for each instance of theSelectionByID116010 entity there may be oneUpperBoundaryMaterialSupplyAndDemandAllocationID116026 attribute.

TheSelectionByRequirementDocumentID116030 entity has a cardinality of 0..N116032 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionByRequirementDocumentID116030 entities. TheSelectionByRequirementDocumentID116030 entity includes various attributes, namely anInclusionExclusionCode116034, anIntervalBoundaryTypeCode116038, aLowerBoundaryBusinessTransactionDocumentID116042 and anUpperBoundaryBusinessTransactionDocumentID116046. TheInclusionExclusionCode116034 attribute has a cardinality of 0..1116036 meaning that for each instance of theSelectionByRequirementDocumentID116030 entity there may be one InclusionExclusionCode116034 attribute. TheIntervalBoundaryTypeCode116038 attribute has a cardinality of 0..1116040 meaning that for each instance of theSelectionByRequirementDocumentID116030 entity there may be one IntervalBoundaryTypeCode116038 attribute. TheLowerBoundaryBusinessTransactionDocumentID116042 attribute has a cardinality of 0..1116044 meaning that for each instance of theSelectionByRequirementDocumentID116030 entity there may be oneLowerBoundaryBusinessTransactionDocumentID116042 attribute. TheUpperBoundaryBusinessTransactionDocumentID116046 attribute has a cardinality of 0..1116048 meaning that for each instance of theSelectionByRequirementDocumentID116030 entity there may be oneUpperBoundaryBusinessTransactionDocumentID116046 attribute.

TheSelectionByProductionOrderID116070 entity has a cardinality of 0..N116072 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionByProductionOrderID116070 entities. TheSelectionByProductionOrderID116070 entity includes various attributes, namely anInclusionExclusionCode116074, anIntervalBoundaryTypeCode116078, aLowerBoundaryBusinessTransactionDocumentID116082 and anUpperBoundaryBusinessTransactionDocumentID116086. TheInclusionExclusionCode116074 attribute has a cardinality of 0..1116076 meaning that for each instance of theSelectionByProductionOrderID116070 entity there may be one InclusionExclusionCode116074 attribute. TheIntervalBoundaryTypeCode116078 attribute has a cardinality of 0..1116080 meaning that for each instance of theSelectionByProductionOrderID116070 entity there may be one IntervalBoundaryTypeCode116078 attribute. TheLowerBoundaryBusinessTransactionDocumentID116082 attribute has a cardinality of 0..1116084 meaning that for each instance of theSelectionByProductionOrderID116070 entity there may be oneLowerBoundaryBusinessTransactionDocumentID116082 attribute. TheUpperBoundaryBusinessTransactionDocumentID116086 attribute has a cardinality of 0..1116088 meaning that for each instance of theSelectionByProductionOrderID116070 entity there may be oneUpperBoundaryBusinessTransactionDocumentID116086 attribute.

TheSelectionByPurchaseOrderID116090 entity has a cardinality of 0..N116092 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionByPurchaseOrderID116090 entities. TheSelectionByPurchaseOrderID116090 entity includes various attributes, namely anInclusionExclusionCode116094, anIntervalBoundaryTypeCode116098, aLowerBoundaryBusinessTransactionDocumentID116102 and anUpperBoundaryBusinessTransactionDocumentID116106. TheInclusionExclusionCode116094 attribute has a cardinality of 0..1116096 meaning that for each instance of theSelectionByPurchaseOrderID116090 entity there may be one InclusionExclusionCode116094 attribute. TheIntervalBoundaryTypeCode116098 attribute has a cardinality of 0..1116100 meaning that for each instance of theSelectionByPurchaseOrderID116090 entity there may be one IntervalBoundaryTypeCode116098 attribute. TheLowerBoundaryBusinessTransactionDocumentID116102 attribute has a cardinality of 0..1116104 meaning that for each instance of theSelectionByPurchaseOrderID116090 entity there may be oneLowerBoundaryBusinessTransactionDocumentID116102 attribute. TheUpperBoundaryBusinessTransactionDocumentID116106 attribute has a cardinality of 0..1116108 meaning that for each instance of theSelectionByPurchaseOrderID116090 entity there may be oneUpperBoundaryBusinessTransactionDocumentID116106 attribute.

TheSelectionByBatchD116110 entity has a cardinality of 0..N116112 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionByBatchD116110 entities. TheSelectionByBatchD116110 entity includes various attributes, namely anInclusionExclusionCode116114, anIntervalBoundaryTypeCode116118, aLowerBoundaryBusinessTransactionDocumentID116122 and anUpperBoundaryBusinessTransactionDocumentID116126. TheInclusionExclusionCode116114 attribute has a cardinality of 0..1116116 meaning that for each instance of theSelectionByBatchD116110 entity there may be one InclusionExclusionCode116114 attribute.

TheIntervalBoundaryTypeCode116118 attribute has a cardinality of 0..1116120 meaning that for each instance of theSelectionByBatchD116110 entity there may be one IntervalBoundaryTypeCode116118 attribute. TheLowerBoundaryBusinessTransactionDocumentID116122 attribute has a cardinality of 0..1116124 meaning that for each instance of theSelectionByBatchD116110 entity there may be oneLowerBoundaryBusinessTransactionDocumentID116122 attribute. TheUpperBoundaryBusinessTransactionDocumentID116126 attribute has a cardinality of 0..1116128 meaning that for each instance of theSelectionByBatchD116110 entity there may be oneUpperBoundaryBusinessTransactionDocumentID116126 attribute.

TheSelectionByVendorID116130 entity has a cardinality of 0..N116132 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionByVendorID116130 entities. TheSelectionByVendorID116130 entity includes various attributes, namely anInclusionExclusionCode116134, anIntervalBoundaryTypeCode116138, aLowerBoundaryBusinessTransactionDocumentID116142 and anUpperBoundaryBusinessTransactionDocumentID116146. TheInclusionExclusionCode116134 attribute has a cardinality of 0..1116136 meaning that for each instance of theSelectionByVendorID116130 entity there may be one InclusionExclusionCode116134 attribute.

TheIntervalBoundaryTypeCode116138 attribute has a cardinality of 0..1116140 meaning that for each instance of theSelectionByVendorID116130 entity there may be one IntervalBoundaryTypeCode116138 attribute. TheLowerBoundaryBusinessTransactionDocumentID116142 attribute has a cardinality of 0..1116144 meaning that for each instance of theSelectionByVendorID116130 entity there may be oneLowerBoundaryBusinessTransactionDocumentID116142 attribute. TheUpperBoundaryBusinessTransactionDocumentID116146 attribute has a cardinality of 0..1116148 meaning that for each instance of theSelectionByVendorID116130 entity there may be oneUpperBoundaryBusinessTransactionDocumentID116146 attribute.

TheSelectionByProductID116190 entity has a cardinality of 0..N116192 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionByProductID116190 entities. TheSelectionByProductID116190 entity includes various attributes, namely anInclusionExclusionCode116194, anIntervalBoundaryTypeCode116198, aLowerBoundaryProductInternalID116202 and anUpperBoundaryProductInternalID116206. TheInclusionExclusionCode116194 attribute has a cardinality of 0..1116196 meaning that for each instance of theSelectionByProductID116190 entity there may be one InclusionExclusionCode116194 attribute. TheIntervalBoundaryTypeCode116198 attribute has a cardinality of 0..1116200 meaning that for each instance of theSelectionByProductID116190 entity there may be one IntervalBoundaryTypeCode116198 attribute. TheLowerBoundaryProductInternalID116202 attribute has a cardinality of 0..1116204 meaning that for each instance of theSelectionByProductID116190 entity there may be oneLowerBoundaryProductInternalID116202 attribute. TheUpperBoundaryProductInternalID116206 attribute has a cardinality of 0..1116208 meaning that for each instance of theSelectionByProductID116190 entity there may be oneUpperBoundaryProductInternalID116206 attribute.

TheSelectionByLocationID116230 entity has a cardinality of 0..N116232 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionByLocationID116230 entities. TheSelectionByLocationID116230 entity includes various attributes, namely anInclusionExclusionCode116234, anIntervalBoundaryTypeCode116238, aLowerBoundaryLocationInternalID116242 and anUpperBoundaryLocationInternalID116246. TheInclusionExclusionCode116234 attribute has a cardinality of 0..1116236 meaning that for each instance of theSelectionByLocationID116230 entity there may be one InclusionExclusionCode116234 attribute. TheIntervalBoundaryTypeCode116238 attribute has a cardinality of 0..1116240 meaning that for each instance of theSelectionByLocationID116230 entity there may be one IntervalBoundaryTypeCode116238 attribute. TheLowerBoundaryLocationInternalID116242 attribute has a cardinality of 0..1116244 meaning that for each instance of theSelectionByLocationID116230 entity there may be oneLowerBoundaryLocationInternalID116242 attribute. TheUpperBoundaryLocationInternalID116246 attribute has a cardinality of 0..1116248 meaning that for each instance of theSelectionByLocationID116230 entity there may be oneUpperBoundaryLocationInternalID116246 attribute.

TheSelectionBySoldtoParty116250 entity has a cardinality of 0..N116252 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionBySoldtoParty116250 entities. TheSelectionBySoldtoParty116250 entity includes various attributes, namely anInclusionExclusionCode116254, anIntervalBoundaryTypeCode116258, aLowerBoundaryPartyInternalID116262 and anUpperBoundaryPartyInternalID116266. TheInclusionExclusionCode116254 attribute has a cardinality of 0..1116256 meaning that for each instance of theSelectionBySoldtoParty116250 entity there may be one InclusionExclusionCode116254 attribute. TheIntervalBoundaryTypeCode116258 attribute has a cardinality of 0..1116260 meaning that for each instance of theSelectionBySoldtoParty116250 entity there may be one IntervalBoundaryTypeCode116258 attribute. TheLowerBoundaryPartyInternalID116262 attribute has a cardinality of 0..1116264 meaning that for each instance of theSelectionBySoldtoParty116250 entity there may be oneLowerBoundaryPartyInternalID116262 attribute. TheUpperBoundaryPartyInternalID116266 attribute has a cardinality of 0..1116268 meaning that for each instance of theSelectionBySoldtoParty116250 entity there may be oneUpperBoundaryPartyInternalID116266 attribute.

TheSelectionByProductAvailabilityDate116270 entity has a cardinality of 0..N116272 meaning that for each instance of theItemBasicDataSelectionByElements116006 entity there may be one or more SelectionByProductAvailabilityDate116270 entities. TheSelectionByProductAvailabilityDate116270 entity includes various attributes, namely anInclusionExclusionCode116274, anIntervalBoundaryTypeCode116278, aLowerBoundaryDate116282 and anUpperBoundaryDate116286. TheInclusionExclusionCode116274 attribute has a cardinality of 0..1116276 meaning that for each instance of theSelectionByProductAvailabilityDate116270 entity there may be one InclusionExclusionCode116274 attribute. TheIntervalBoundaryTypeCode116278 attribute has a cardinality of 0..1116280 meaning that for each instance of theSelectionByProductAvailabilityDate116270 entity there may be one IntervalBoundaryTypeCode116278 attribute. TheLowerBoundaryDate116282 attribute has a cardinality of 0..1116284 meaning that for each instance of theSelectionByProductAvailabilityDate116270 entity there may be one LowerBoundaryDate116282 attribute. TheUpperBoundaryDate116286 attribute has a cardinality of 0..1116288 meaning that for each instance of theSelectionByProductAvailabilityDate116270 entity there may be one UpperBoundaryDate116286 attribute.

TheProcessingConditions116292 entity has a cardinality of 0..1116294 meaning that for each instance of theSelection116004 package there may be one ProcessingConditions116292 entity. TheProcessingConditions116292 entity includes aQueryHitsMaximumNumberValue116296 attribute. TheQueryHitsMaximumNumberValue116296 attribute has a cardinality of 1116298 meaning that for each instance of theProcessingConditions116292 entity there is oneQueryHitsMaximumNumberValue116296 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 109-1 through109-11.

FIGS. 117-1 through117-6 show an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPByElementsResponseMessage_sync117000 package. TheMaterialSupplyAndDemandAllocationERPByElementsResponseMessage_sync117000 package includes aMaterialSupplyAndDemandAllocationERPByElementsResponseMessage_sync117002 entity. TheMaterialSupplyAndDemandAllocationERPByElementsResponseMessage_sync117000 package includes various packages, namely aMaterialSupplyAndDemandAllocationERP117004, aProcessingConditions117102 and aLog117116.

TheMaterialSupplyAndDemandAllocationERP117004 package includes aMaterialSupplyAndDemandAllocation117006 entity. TheMaterialSupplyAndDemandAllocation117006 entity has a cardinality of 0..n117008 meaning that for each instance of theMaterialSupplyAndDemandAllocationERP117004 package there may be one or more MaterialSupplyAndDemandAllocation117006 entities. TheMaterialSupplyAndDemandAllocation117006 entity includes anID117010 attribute. TheMaterialSupplyAndDemandAllocation117006 entity includes anItem117014 subordinate entity.

TheID117010 attribute has a cardinality of 1117012 meaning that for each instance of theMaterialSupplyAndDemandAllocation117006 entity there is oneID117010 attribute. TheItem117014 entity has a cardinality of 1117016 meaning that for each instance of theMaterialSupplyAndDemandAllocation117006 entity there is oneItem117014 entity. TheItem117014 entity includes various attributes, namely aProductInternalID117018, aPlantID117022, aMaterialSupplyAndDemandAllocationStatusCode117026 and aMaterialSupplyAndDemandAllocationStatusName117030. TheItem117014 entity includes various subordinate entities, namely aDemandReference117034 and aSupplyReference117062.

TheProductInternalID117018 attribute has a cardinality of 1117020 meaning that for each instance of theItem117014 entity there is oneProductInternalID117018 attribute. ThePlantID117022 attribute has a cardinality of 1117024 meaning that for each instance of theItem117014 entity there is onePlantID117022 attribute. TheMaterialSupplyAndDemandAllocationStatusCode117026 attribute has a cardinality of 1117028 meaning that for each instance of theItem117014 entity there is oneMaterialSupplyAndDemandAllocationStatusCode117026 attribute. TheMaterialSupplyAndDemandAllocationStatusName117030 attribute has a cardinality of 1117032 meaning that for each instance of theItem117014 entity there is oneMaterialSupplyAndDemandAllocationStatusName117030 attribute.

TheLog117116 package includes aLog117118 entity. TheLog117118 entity has a cardinality of 1117120 meaning that for each instance of theLog117116 package there is oneLog117118 entity. The data types of the various packages, entities, and attributes are described with respect toFIGS. 109-1 through109-11.

FIGS. 118-1 through118-4 show an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPUpdateRequestMessage_sync118000 package. TheMaterialSupplyAndDemandAllocationERPUpdateRequestMessage_sync118000 package includes aMaterialSupplyAndDemandAllocationERPUpdateRequestMessage_sync118002 entity. TheMaterialSupplyAndDemandAllocationERPUpdateRequestMessage_sync118000 package includes various packages, namely aMessageHeader118004 and aMaterialSupplyAndDemandAllocationERP118010.

TheMessageHeader118004 package includes aMessageHeader118006 entity. TheMessageHeader118006 entity has a cardinality of 0..1118008 meaning that for each instance of theMessageHeader118004 package there may be one MessageHeader118006 entity.

TheItem118024 entity has a cardinality of 1..n118026 meaning that for each instance of theMaterialSupplyAndDemandAllocation118012 entity there are one ormore Item118024 entities. TheItem118024 entity includes various attributes, namely aProductInternalID118028, aPlantID118032 and aMaterialSupplyAndDemandAllocationStatusCode118036. TheItem118024 entity includes various subordinate entities, namely aDemandReference118040 and aSupplyReference118060. TheProductInternalID118028 attribute has a cardinality of 0..1118030 meaning that for each instance of theItem118024 entity there may be oneProductInternalID118028 attribute. ThePlantID118032 attribute has a cardinality of 0..1118034 meaning that for each instance of theItem118024 entity there may be onePlantID118032 attribute. TheMaterialSupplyAndDemandAllocationStatusCode118036 attribute has a cardinality of 1118038 meaning that for each instance of theItem118024 entity there is oneMaterialSupplyAndDemandAllocationStatusCode118036 attribute.

TheDemandReference118040 entity has a cardinality of 1118042 meaning that for each instance of theItem118024 entity there is oneDemandReference118040 entity. TheDemandReference118040 entity includes various attributes, namely anID118044, anItemID118048, anAlternateItemID118052 and aSoldtoPartyInternalID118056. TheID118044 attribute has a cardinality of 1118046 meaning that for each instance of theDemandReference118040 entity there is oneID118044 attribute. TheItemID118048 attribute has a cardinality of 0..1118050 meaning that for each instance of theDemandReference118040 entity there may be oneItemID118048 attribute. TheAlternateItemID118052 attribute has a cardinality of 0..1118054 meaning that for each instance of theDemandReference118040 entity there may be oneAlternateItemID118052 attribute. TheSoldtoPartyInternalID118056 attribute has a cardinality of 0..1118058 meaning that for each instance of theDemandReference118040 entity there may be oneSoldtoPartyInternalID118056 attribute.

FIG. 119 shows an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPUpdateConfirmationMessage_sync119000 package. TheMaterialSupplyAndDemandAllocationERPUpdateConfirmationMessage_sync119000 package includes aMaterialSupplyAndDemandAllocationERPUpdateConfirmationMessage_sync119002 entity. TheMaterialSupplyAndDemandAllocationERPUpdateConfirmationMessage_sync119000 package includes various packages, namely aMessageHeader119004 and aLog119010.

TheMessageHeader119004 package includes aMessageHeader119006 entity. TheMessageHeader119006 entity has a cardinality of 0..1119008 meaning that for each instance of theMessageHeader119004 package there may be one MessageHeader119006 entity.

TheLog119010 package includes aLog119012 entity. TheLog119012 entity has a cardinality of 1119014 meaning that for each instance of theLog119010 package there is oneLog119012 entity. The data types of the various packages, entities, and attributes are described with respect toFIGS. 109-1 through109-11.

FIGS. 120-1 through120-3 show an example configuration of an Element Structure that includes aMaterialSupplyAndDemandAllocationERPCreateCheckQueryMessage_sync120000 package. TheMaterialSupplyAndDemandAllocationERPCreateCheckQueryMessage_sync120000 package includes aMaterialSupplyAndDemandAllocationERPCreateCheckQueryMessage_sync120002 entity. TheMaterialSupplyAndDemandAllocationERPCreateCheckQueryMessage_sync120000 package includes aMaterialSupplyAndDemandAllocationERP120004 package.

TheItem120014 entity has a cardinality of 1..n120016 meaning that for each instance of theMaterialSupplyAndDemandAllocation120006 entity there are one ormore Item120014 entities. TheItem120014 entity includes various subordinate entities, namely aDemandReference120018, aSupplyReference120034 and aQuantity120058.

TheDemandReference120018 entity has a cardinality of 1120020 meaning that for each instance of theItem120014 entity there is oneDemandReference120018 entity. TheDemandReference120018 entity includes various attributes, namely anID120022, anItemID120026 and anAlternateItemID120030. TheID120022 attribute has a cardinality of 1120024 meaning that for each instance of theDemandReference120018 entity there is oneID120022 attribute. TheItemID120026 attribute has a cardinality of 0..1120028 meaning that for each instance of theDemandReference120018 entity there may be oneItemID120026 attribute. TheAlternateItemID120030 attribute has a cardinality of 0..1120032 meaning that for each instance of theDemandReference120018 entity there may be oneAlternateItemID120030 attribute.

TheSupplyReference120034 entity has a cardinality of 0..1120036 meaning that for each instance of theItem120014 entity there may be one SupplyReference120034 entity. TheSupplyReference120034 entity includes various attributes, namely anID120038, aBatchID120042, anInventoryManagedLocationInternalID120046, aMaterialSupplyAndDemandTypeCode120050 and anInventorySpecialStockTypeCode120054. TheID120038 attribute has a cardinality of 0..1120040 meaning that for each instance of theSupplyReference120034 entity there may be oneID120038 attribute. TheBatchID120042 attribute has a cardinality of 0..1120044 meaning that for each instance of theSupplyReference120034 entity there may be oneBatchID120042 attribute. TheInventoryManagedLocationInternalID120046 attribute has a cardinality of 0..1120048 meaning that for each instance of theSupplyReference120034 entity there may be oneInventoryManagedLocationInternalID120046 attribute. TheMaterialSupplyAndDemandTypeCode120050 attribute has a cardinality of 0..1120052 meaning that for each instance of theSupplyReference120034 entity there may be one MaterialSupplyAndDemandTypeCode120050 attribute. TheInventorySpecialStockTypeCode120054 attribute has a cardinality of 0..11120056 meaning that for each instance of theSupplyReference120034 entity there may be one InventorySpecialStockTypeCode120054 attribute.

TheQuantity120058 entity has a cardinality of 0..1120060 meaning that for each instance of theItem120014 entity there may be oneQuantity120058 entity. TheQuantity120058 entity includes anOpenQuantity120062 attribute. TheOpenQuantity120062 attribute has a cardinality of 0..1120064 meaning that for each instance of theQuantity120058 entity there may be one OpenQuantity120062 attribute. The data types of the various packages, entities, and attributes are described with respect toFIGS. 109-1 through109-11.

FIGS. 121-1 through121-9 show an example configuration of an Element Structure that includes a MaterialSupplyAndDemandAllocationERPCreateCheckResponseMessage_sync121000 package. The MaterialSupplyAndDemandAllocationERPCreateCheckResponseMessage_sync121000 package includes aMaterialSupplyAndDemandAllocationERPCreateCheckResponseMessage_sync121002 entity. The MaterialSupplyAndDemandAllocationERPCreateCheckResponseMessage_sync121000 package includes various packages, namely aMaterialSupplyAndDemandAllocationERP121004 and aLog121190.

TheSystemAdministrativeData121018 entity has a cardinality of 1121020 meaning that for each instance of theMaterialSupplyAndDemandAllocation121006 entity there is oneSystemAdministrativeData121018 entity. TheSystemAdministrativeData121018 entity includes various attributes, namely aCreationDate121022, aCreationUserAccountID121026 and aLastChangeDate121030. TheCreationDate121022 attribute has a cardinality of 0..1121024 meaning that for each instance of theSystemAdministrativeData121018 entity there may be one CreationDate121022 attribute. TheCreationUserAccountID121026 attribute has a cardinality of 1121028 meaning that for each instance of theSystemAdministrativeData121018 entity there is oneCreationUserAccountID121026 attribute. TheLastChangeDate121030 attribute has a cardinality of 0..1121032 meaning that for each instance of theSystemAdministrativeData121018 entity there may be one LastChangeDate121030 attribute.

TheDemandReference121066 entity has a cardinality of 1121068 meaning that for each instance of theItem121034 entity there is oneDemandReference121066 entity. TheDemandReference121066 entity includes various attributes, namely anID121070, anItemID121074, anAlternateItemID121078, aMaterialSupplyAndDemandTypeCode121082, aMaterialSupplyAndDemandTypeName121086, aRequirementSegmentationPropertyValueCombinationID121090, aSoldtoPartyInternalID121094, aShiptoPartyInternalID121098, aProductAvailabilityDate121102 and aSalesOrderItemScheduleLineDate121106. TheID121070 attribute has a cardinality of 1121072 meaning that for each instance of theDemandReference121066 entity there is oneID121070 attribute. TheItemID121074 attribute has a cardinality of 1121076 meaning that for each instance of theDemandReference121066 entity there is oneItemID121074 attribute. TheAlternateItemID121078 attribute has a cardinality of 1121080 meaning that for each instance of theDemandReference121066 entity there is oneAlternateItemID121078 attribute. TheMaterialSupplyAndDemandTypeCode121082 attribute has a cardinality of 1121084 meaning that for each instance of theDemandReference121066 entity there is oneMaterialSupplyAndDemandTypeCode121082 attribute. TheMaterialSupplyAndDemandTypeName121086 attribute has a cardinality of 1121088 meaning that for each instance of theDemandReference121066 entity there is oneMaterialSupplyAndDemandTypeName121086 attribute. TheRequirementSegmentationPropertyValueCombinationID121090 attribute has a cardinality of 0..1121092 meaning that for each instance of theDemandReference121066 entity there may be oneRequirementSegmentationPropertyValueCombinationID121090 attribute. TheSoldtoPartyInternalID121094 attribute has a cardinality of 0..1121096 meaning that for each instance of theDemandReference121066 entity there may be oneSoldtoPartyInternalID121094 attribute. TheShiptoPartyInternalID121098 attribute has a cardinality of 0..1121100 meaning that for each instance of theDemandReference121066 entity there may be oneShiptoPartyInternalID121098 attribute. TheProductAvailabilityDate121102 attribute has a cardinality of 0..1121104 meaning that for each instance of theDemandReference121066 entity there may be one ProductAvailabilityDate121102 attribute. TheSalesOrderItemScheduleLineDate121106 attribute has a cardinality of 0..1121108 meaning that for each instance of theDemandReference121066 entity there may be one SalesOrderItemScheduleLineDate121106 attribute.

TheQuantity121170 entity has a cardinality of 0..1121172 meaning that for each instance of theItem121034 entity there may be oneQuantity121170 entity. TheQuantity121170 entity includes various attributes, namely anOpenQuantity121174, aReleasedAllocatedQuantity121178, aReservedAllocatedQuantity121182 and aDeliveredQuantity121186. TheOpenQuantity121174 attribute has a cardinality of 0..1121176 meaning that for each instance of theQuantity121170 entity there may be one OpenQuantity121174 attribute. TheReleasedAllocatedQuantity121178 attribute has a cardinality of 0..1121180 meaning that for each instance of theQuantity121170 entity there may be one ReleasedAllocatedQuantity121178 attribute. TheReservedAllocatedQuantity121182 attribute has a cardinality of 0..1121184 meaning that for each instance of theQuantity121170 entity there may be one ReservedAllocatedQuantity121182 attribute. TheDeliveredQuantity121186 attribute has a cardinality of 0..1121188 meaning that for each instance of theQuantity121170 entity there may be one DeliveredQuantity121186 attribute.

TheLog121190 package includes aLog121192 entity. TheLog121192 entity has a cardinality of 1121194 meaning that for each instance of theLog121190 package there is oneLog121192 entity. The data types of the various packages, entities, and attributes are described with respect toFIG. 121.

A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the disclosure. Accordingly, other implementations are within the scope of the following claims.