Skip to end of metadata
Go to start of metadata
Key Principles
Principle | Decision / Discussion |
---|
Portfolio Level | |
Mandate/Client Level | |
Consolidation Level | If a reporting should be producing a consolidated view over multiple mandates, the master data call should also deliver information on the consolidation level in the same format Additionally the structure of the consolidation (list of portfolios / mandates) should be contained in the data
|
Interface "PortfolioMasterData"
Usage & Contents | Used to Report covers (client name), headers/footers Portfolio information blocks (e.g. PI001) Performance charts (determination of performance periods, see below) Footers/Header of report
Contains information like performanceMeasurementStartDate portfolio strategies (different types, including target weight, bandwiths, index/benchmark) reporting legal entity -> controls disclaimer-text Portfolio contacts for pm (portfolio manager), cpm, rm (including pictures) Information about sub-portfolios (for consolidation of mandates or mandates implemented by multiple custody portfolios) etc.
|
---|
Reporting Business Logic | |
---|
Consistency Rules | |
---|
Path | /portfolio/masterdata
|
---|
Parameters | |
---|
Example Call | /portfolio/masterdata?portfolioId=E0002&reportingDate=2019-03-31
|
---|
Schema | |
---|
Response | |
---|
Interface "PortfolioFundData"
Usage & Contents | Used to Contains information like list of shareclasses list of sales registrations (country, investor type, etc.) fund facts (e.g. fund management company, custodian, etc.) etc.
|
---|
Reporting Business Logic | |
---|
Consistency Rules | |
---|
Path | /portfolio/funddata
|
---|
Parameters | |
---|
Example Call | /portfolio/funddata?portfolioId=E0002&reportingDate=2019-03-31
|
---|
Schema | |
---|
Response | |
---|
Add Comment