HR Analytics Star Schema Definitions
All--
We currently report on PeopleSoft data by extracting it into a data mart. ( The data store's configuration is not in a star schema format). We use it for day to day operational reporting needs. We are researching on HR Analytics and want to know more details about the data elements covered in the schemas, is there any document that explains the details of the various star schemas and the mappings to the original PeopleSoft database elements ?
We need this to perform a gap analysis. Any help would be much appreciated.
Thanks,
Ajit
Apparently on eDelivery they have finally made available the Source to Staging Mappings in spreadsheet form.
Check that out.
Bob Murching posted about it a few cycles ago on this forum as well.
To clarify the document does not exactly detail the stars. You need to download the Data Model Reference Guide from Metalink3 to see those details.
Similar Messages
-
Extended Analytics for star schema creation from HFM application
Hi,
I'm trying to create star schema via extended analytics from HFM application but facing below error
3/21/2013 12:30:07 PM : Status : Extracting Metadata
Schema did not previously exist.
Metadata update has failed. : (-2147217900) (One or more errors occurred during processing of command.)
Processing status change: (-2147217900)
Data processing failed. : (-2147217900) (One or more errors occurred during processing of command.)
3/21/2013 12:30:10 PM : Status : Processing completed with errors
Extended Analytics export completed with errors for Application GCS using Label GCS CON.
What could be the possible reason for it?
Also can someone please provide any suitable references or links to learn this EA for star schema creation.
Thanks,
Ravi AgrawalThe error you pasted here is incomplete. Look in the system messages and you will find more complete information that will lead you to the error's cause. Very often this is an error in the database, though sometimes it is caused by a metadata member with an invalid character. To determine whether it is data or metadata that causes the error, you could generate a schema with metadata only and see if the error appears.
-- Chris -
Star schema versus snowflake schema
I have a question regarding dimensional data modeling. My question here is, when star schema model would be useful and when snowflake schema model would be useful.
In star schema, we have only fact and it is connected with dimensions. But in snowflake schema, we are normalizing dimension into one more level. Let us say, we have dimension product. Product can be normalized into another table called supplier. Let us take another example, customer dimension. Customer dimension can be normalized into country…
Advantage of star schema is, easy to write the query since we have only less tables. You do not need to join multiple tables when we write the query. It would improve the performance some time.
Advantage of snowflake schema is, it is little complex to write the query, since we have to join multiple tables. Performance might improve some time when we join smaller tables…
My question is, at what circumstances, we can use star and snowflake schema? I am not able to define the word sometime_
Any help is highly appreciated…Hi,
There is a trade off on the availability and the Complex analytics.
A star schema is good if you have the functional requirements really simple. Like the dimension is not SCD Type2 (slowly changing dimension) and you don't need to do "AS IS" vs "AS WAS" reporting.
In modern Analytics in any domain dimensions are SCD Type 2 as business keep on evolving. In a star schema structure this will cause explosion of data if there are frequent changes at the higher levels of the dimensional hierarchy. That anyway will hit the performance.
As far as my experience goes, at the data model level it is better to have snow flaked dimensions. and while managing the metadata (in a BI reporting tool) you can consolidate the snowflaked dimensions in star schema structures. That will make ah hoc analytics much simple for the business users.
A lot of performance measure can be taken to improve the end user experience.
In short the trend in BI analytics demands to have a snowflaked structure rather than a simple star schema structure.
Hope this helps. -
BMM layer creation (Star Schema Physical Layer) - What to add/not add?
Hi All,
I am just looking for any general feedback on the thought/question below.
I am setting out on creating my first BMM layer and trying to determine what I need to do in this layer that will be different and add value from what I already did in the physical layer. My data model is already defined as a star schema within my data mart source. So in the physical layer I have my facts imported along with the dimensions and I have joined them together as needed. Here is what I think I will setup as I move into the BMM layer:
1. I will add heirarchies as needed to enable drill down within my reports
2. I will need to add my calculations/measures to allow for any type of metric to be returned through a request in Answers
3. I do not see a large need to create logical tables (at least not yet) based on multiple physical source tables as my source is already a star schema and dimensionally modeled. For users that also already source a star schema at the physical layer .. do you find that you do a lot of logical table creation/mapping to add functionality or does your BMM look a lot like you Physical Layer?
Other than steps 1 and 2, I am not really sure how much additional manipulation I might do from the Physical to BMM layer since my Physical is already a star schema. Am I missing anything? Obviously everyone's data model and circumstances are different but I wasn't sure if maybe there were some good thoughts on what I might be missing (if anything)?
One last question .. I am not currently planning to use any aliases at the Physical Layer but I do plan to rename the tables at the presentation layer to be more business verbage like. Why are others using aliases?
Thanks in advance for the help.
KAlastair, thanks for the advice. I'll definitely keep that in mind as I start to build out the BMM.
One question/issue I just ran into as I was wrapping up my Physical Layer mapping. When I check for global consistency, I am getting an error that is complaining that I have multiple joins defined between the same two tables (which I do). This is because I have the following setup:
TBL_A_FACT
F_ID_HIT
F_HIT_DESC
F_ID_MISSED
F_MISSED_DESC
TBL_B_DIM
F_ID
F_DESC
Table A joins to Table B in two ways:
TBL_A_FACT.F_ID_HIT = TBL_B_DIM.F_ID
TBL_A._FACT.F_ID_MISSED = TBL_B_DIM.F_ID
The F_IDs can be either hit or missed on any given fact record and the total distinct set exist in the dimension.
When I define two foreign key joins in the physical layer based on the relationship above and check Global Consistency, I get an error saying that "TBL_A and TBL_B have multiple joins define. Delete duplicate foreign keys if they exist" and it is listed as an error. I guess this makes sense because when the two tables are used in a request OBIEE would need to know how to join them (using the hit or missed field). What is the best approach for handling this..
- Should I define TBL_A twice in the physical layer as:
TBL_A (Alias TBL_A_HIT)
F_ID_HIT
F_ID_HIT_DESC
TBL_A (Alias TBL_A_MISSED)
F_ID_MISSED
F_ID_MISSED_DESC
Or do something like the above in the BMM layer?
Thanks for the help!
K
And then establish the relationships using these separate tables? -
Dimensions and facts related to all BI Apps Financials Star Schemas
I am kind of new to BI Apps and was wondering whether there is a list of tables/dimension names/ facts that constitute each star schema in Financial Analytics?
I know there are star schemas like AP Aging, AR Aging, AP Transactions, AR Transactions and so on.
How do I get the OBAW dimension and fact table names that are in each of these star schemas?
Oracle BI Apps presentations take me only to the business name of the dimensions and does not give me the original dimension name used in OBAW.
Thanks in advance!Hi Sid
I am in Data Model Reference that you have mentioned. All the star schemas over here are pictures and are not searchable. Also, the ppt that Oracle gave us just says AP Aging as the fact name and I dont know how I can find the fact table corresponding to that.
If someone can point me for that piece of work, I will go though the star schema pictures in the documentation and find relevant dimensions and facts.
Is there any naming convention that we can use like W_APAging_F table or something like that??
Thanks in advance !
Edited by: user566193 on Jan 21, 2010 2:43 PM -
Do we use direct star schema concept anywhere in sap bw
i know about extended star schema,and where sap uses this concept.
my question is do we use normal star schema concept any where in sap bw, apart from extended star schema concept.
if yes specify the answer briefly .
thanks in advance
with regards
yash.bHi,
If I'm not mistaken an Analytic view in Hana is more like the normal star schema, it is definitely not extended and can be consumed by BW for OLAP processing.
Regards,
Michael Devine -
How to document your star-schemas and dashboards?
Hello practitioners,
We are new to OBIEE and started some weeks ago. We are a two-men team. One guy doing all the data design and the other for everything around Answers.
So it happens regularly that the other guy has to ask the one guy, about the exact definition and meaning of data-fields, he wants to use in Answers.
Being a real programmer the one guy only needs a proper, self-explainary field name as documentation, of course (or so he thought).
Question:
What tools and methods do you use to document the star-schemas and dashboards?
Being the other guy, it is important, that I pick the correct fields, while on the other hand I do not want to disect a dashboard I built a while back, everytime somebody wants something simular, just to figure out what I actually did, back then...
Thank you for your help
Turalf
Edited by: Turalf on Mar 24, 2010 12:03 PMHi Turalf,
Have you looked at the OBIEE Metadata Dictionary ? A method to allow answers users to gain access to column definitions, and you can view the mapping from Presentation, through BMM to Physical layer.
Im pretty sure you can expose comments from the RPD into this also.
http://obiee101.blogspot.com/2008/12/obiee-metadata-dictionary.html
Maybe you could look at the ODI - OBIEE data lineage also, it provides "report to source" mapping info :
http://www.oracle.com/technology/obe/fusion_middleware/ODI/OBI-ODI_Lineage/OBI-ODI_Lineage.htm
Hope this helps. -
Hi,
I'm working with BI Apps (OBIEE) uploaded on PeopleSoft HCM 9.1 source system. I'm using pre built ETL task to load the pre designed Datawarehouse.I want to know where can I found the Datawarehouse star schema description?What you are looking for the DMR (Datawarehouse Model Reference) Doc. I believe they have this on Metalink for the BI Apps releases. This provides the physcial star schemas and details on the DW tables. Here is the metalink note:
Oracle Business Analytics Warehouse Data Model Reference Version 7.9.6, 7.9.6.1 and 7.9.6.2 [ID 819373.1
If this was helpful, please mark the response as correct. -
Unable to run a star schema in HFM. Error message below.
We are currently unable to run an existing star schema in our HFM 9.3.3 application. This has never caused an issue in the past and is causing a disruption in our montly close process.
Any assitance would be greatly appreciated!
I've attempted to delete the Star Schema but still receive same error message.
Error message below:
Thank you,
Brian Riedel
==================================================================================================================
8/1/2012 1:34:24 PM : Status : Extracting Metadata
Metadata update has failed. : (-2147220903) (Attention: One or more processes are currently using the Star Schema specified by the DSN and Prefix. You must wait until all other processing is completed before attempting to create the specified Star Schema.)
Processing status change: (-2147220903)
Data processing failed. : (-2147220903) (Attention: One or more processes are currently using the Star Schema specified by the DSN and Prefix. You must wait until all other processing is completed before attempting to create the specified Star Schema.)
8/1/2012 1:34:24 PM : Status : Processing completed with errors
Extended Analytics export completed with errors for Application BSCPROD using Label PL. Error code is:The message means another process has a lock on the EA tables, so you have to wait until that processis complete before proceeding. This could happen if you are trying to execute more than 1 concurrent EA exports.
--Chris -
Hello,
I have a simple question on why the Star Schema is used ? Getting an answer from Wiki is not what I wanted , some response from the Gurus would be great to hear. Every time when there is a Metadata Update in HFM during Monthly Change and Maintenance a New Star Schema should be created and only then I run the Dimension Update Job in Essbase, what is the real reason for that. If you say that it Updates the New Dimension changes in HFM to Essbase , then for that we already have an EAL taking care of Updating the Essbase Metadata in Tandem with HFM.
Any comments.
Thanks !!I was on a Extended Analytics project in 2008. There was no EAL. EA was it.
Regards,
Cameron Lackpour
P.S. Thankfully, I can't remember the functionality other than it was like being cooked, slowly, over a roaring fire.
Edited by: CL on Jan 9, 2013 3:42 PM -
ORA-30937: No schema definition for
Here are the steps I followed to load the xml
DBMS_XMLSCHEMA.REGISTERSCHEMA(
SCHEMAURL => 'security.xsd',
SCHEMADOC => BFILENAME('XML_DIR', 'security.xsd')
LOCAL => TRUE
CREATE TABLE TMP_XML_TABLES
xml_document XMLType
XMLType COLUMN xml_document
XMLSchema "security.xsd"
ELEMENT "security"
INSERT INTO TMP_XML_TABLES
VALUES
xmltype
BFILENAME('XML_CLOB_DIR', 'sec.xml'),
nls_charset_id('AL32UTF8')
I am getting below error.
ORA-30937: No schema definition for 'fido_flag' (namespace '##local') in parent '/security/security_
ORA-06512: at "SYS.XMLTYPE", line 295
ORA-06512: at line 1
Below is the XSD and XML file. Please let me know what is wrong with it.
security.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v2004 rel. 4 U (http://www.xmlspy.com) by Cary Liu (Cary Liu) -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="security">
<xs:complexType>
<xs:sequence>
<xs:element ref="security_row" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="variable_rate_row" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="security_count" type="xs:long" use="optional"/>
<xs:attribute name="variable_rate_count" type="xs:long" use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="security_row">
<xs:complexType>
<xs:all>
<xs:element ref="security_id"/>
<xs:element ref="primary_asset_id"/>
<xs:element ref="delay_days"/>
<xs:element ref="arm_indicator"/>
<xs:element ref="camra_abs_und_coll"/>
<xs:element ref="camra_abs_und_coll_cpn"/>
<xs:element ref="initial_principal_pay_date"/>
<xs:element ref="final_principal_pay_date"/>
<xs:element ref="mtg_term"/>
<xs:element ref="original_face"/>
<xs:element ref="pool_number"/>
<xs:element ref="principal_pay_frequency"/>
<xs:element ref="pay_down_date"/>
<xs:element ref="principal_pay_bus_day_rule"/>
<xs:element ref="seasoned_mbs"/>
<xs:element ref="tba_stlmt_month"/>
<xs:element ref="accrual_flag"/>
<xs:element ref="accrual_rule"/>
<xs:element ref="base_payment_date"/>
<xs:element ref="day_count"/>
<xs:element ref="ex_interest_bond_code"/>
<xs:element ref="ex_days"/>
<xs:element ref="ex_div_date"/>
<xs:element ref="last_coupon_date"/>
<xs:element ref="for_bond_security_type"/>
<xs:element ref="dated_date"/>
<xs:element ref="issue_date"/>
<xs:element ref="first_coupon_date"/>
<xs:element ref="second_coupon_date"/>
<xs:element ref="mat_date"/>
<xs:element ref="interest_accrual_method"/>
<xs:element ref="odd_first_coupon_date"/>
<xs:element ref="odd_last_coupon_date"/>
<xs:element ref="payment_eom_rule"/>
<xs:element ref="pay_frequency"/>
<xs:element ref="pay_business_day_rule"/>
<xs:element ref="yield_day_count"/>
<xs:element ref="zero_coupon_type"/>
<xs:element ref="analyst"/>
<xs:element ref="analyst_recomm"/>
<xs:element ref="approval_flag"/>
<xs:element ref="camra_sec_type"/>
<xs:element ref="class"/>
<xs:element ref="comments"/>
<xs:element ref="holding_style"/>
<xs:element ref="issued_capital"/>
<xs:element ref="issued_capital_currency"/>
<xs:element ref="min_denomination"/>
<xs:element ref="price_multiplier"/>
<xs:element ref="pricing_identifier"/>
<xs:element ref="quantity_issued"/>
<xs:element ref="shares_outstanding"/>
<xs:element ref="quantity_type"/>
<xs:element ref="redemption_value"/>
<xs:element ref="scb_industry"/>
<xs:element ref="issue_desc1"/>
<xs:element ref="issue_desc2"/>
<xs:element ref="issue_desc3"/>
<xs:element ref="issue_short_name"/>
<xs:element ref="trading_lot_size"/>
<xs:element ref="unit_factor"/>
<xs:element ref="camra_exercise_date"/>
<xs:element ref="camra_expiration_date"/>
<xs:element ref="alliance_sector"/>
<xs:element ref="alliance_industry"/>
<xs:element ref="apace_security_type"/>
<xs:element ref="camra_gl_type"/>
<xs:element ref="emerg_mkt_ind"/>
<xs:element ref="form_13f_flag"/>
<xs:element ref="instrument_class"/>
<xs:element ref="issue_type"/>
<xs:element ref="mortgage_sector"/>
<xs:element ref="naic_code"/>
<xs:element ref="performance_segment"/>
<xs:element ref="program_type"/>
<xs:element ref="camra_sic_code2"/>
<xs:element ref="camra_sched_d_group"/>
<xs:element ref="camra_sched_d_state"/>
<xs:element ref="security_form"/>
<xs:element ref="security_type_distrib"/>
<xs:element ref="camra_sic_code"/>
<xs:element ref="structured_note_flag"/>
<xs:element ref="underlying_category"/>
<xs:element ref="primary_asset_id_type"/>
<xs:element ref="superticker"/>
<xs:element ref="default_status"/>
<xs:element ref="default_date"/>
<xs:element ref="accrue_in_default_ind"/>
<xs:element ref="ctd_bond"/>
<xs:element ref="contract_size"/>
<xs:element ref="derivative_type"/>
<xs:element ref="delivery_method"/>
<xs:element ref="conversion_factor"/>
<xs:element ref="flex_option_ind"/>
<xs:element ref="leap_option_ind"/>
<xs:element ref="orig_strike_price"/>
<xs:element ref="otc_flag"/>
<xs:element ref="part_paid_percent"/>
<xs:element ref="strike_price"/>
<xs:element ref="put_call_flag"/>
<xs:element ref="strike_price_type"/>
<xs:element ref="pay_currency"/>
<xs:element ref="rec_currency"/>
<xs:element ref="premium_amount"/>
<xs:element ref="warrant_style"/>
<xs:element ref="pay_status"/>
<xs:element ref="tick_amount"/>
<xs:element ref="right_warrant_option_type"/>
<xs:element ref="underlying_cusip"/>
<xs:element ref="var_margin_rule"/>
<xs:element ref="nominal_annual_income"/>
<xs:element ref="dividend_frequency"/>
<xs:element ref="dividend_reinvestment_ind"/>
<xs:element ref="dr_sponsoring"/>
<xs:element ref="dr_sponsor"/>
<xs:element ref="claim_type"/>
<xs:element ref="dated_date_cpi"/>
<xs:element ref="when_issued_ind"/>
<xs:element ref="series"/>
<xs:element ref="tranche"/>
<xs:element ref="guarantee_type"/>
<xs:element ref="deep_discount_ind"/>
<xs:element ref="perpetual_flag"/>
<xs:element ref="maturity_override"/>
<xs:element ref="camra_index_desc"/>
<xs:element ref="camra_index_spread"/>
<xs:element ref="coupon"/>
<xs:element ref="rate_benchmark"/>
<xs:element ref="rate_multiplier"/>
<xs:element ref="spread_to_benchmark"/>
<xs:element ref="rate_reset_frequency"/>
<xs:element ref="rate_base_reset_date"/>
<xs:element ref="reset_lag_days"/>
<xs:element ref="reset_lockout_days"/>
<xs:element ref="next_reset_date"/>
<xs:element ref="rate_calculate_switch"/>
<xs:element ref="rate_reset_bus_day_rule"/>
<xs:element ref="rate_reset_eom_rule"/>
<xs:element ref="rate_type"/>
<xs:element ref="mutual_fund_sponsor"/>
<xs:element ref="regulated_flag"/>
<xs:element ref="tia_1961_flag"/>
<xs:element ref="accumulation_income_flag"/>
<xs:element ref="fsa_indicator"/>
<xs:element ref="income_dist_policy"/>
<xs:element ref="mutual_fund_charge_type"/>
<xs:element ref="holdings_flag"/>
<xs:element ref="issuer_type"/>
<xs:element ref="issuer_id"/>
<xs:element ref="parent_issuer_id"/>
<xs:element ref="country"/>
<xs:element ref="currency"/>
<xs:element ref="country_of_origin"/>
<xs:element ref="risk_country"/>
<xs:element ref="currency_of_earnings"/>
<xs:element ref="currency_of_income"/>
<xs:element ref="currency_of_trade"/>
<xs:element ref="principal_currency"/>
<xs:element ref="exchange"/>
<xs:element ref="state_code"/>
<xs:element ref="muni_insurance"/>
<xs:element ref="conduit"/>
<xs:element ref="muni_note_type"/>
<xs:element ref="muni_issuer"/>
<xs:element ref="obligation_type"/>
<xs:element ref="oes_next_call_date"/>
<xs:element ref="offering_yield"/>
<xs:element ref="remarketing_agent"/>
<xs:element ref="tax_exempt_region"/>
<xs:element ref="fed_wire"/>
<xs:element ref="oid_flag"/>
<xs:element ref="oid_number"/>
<xs:element ref="oi_price"/>
<xs:element ref="camra_moody_sector"/>
<xs:element ref="restricted"/>
<xs:element ref="camra_class_144"/>
<xs:element ref="foreign_restriction_ind"/>
<xs:element ref="foreign_restriction_req"/>
<xs:element ref="sec_144a"/>
<xs:element ref="reg_s"/>
<xs:element ref="prvt_place_ind"/>
<xs:element ref="liquid_flag"/>
<xs:element ref="call_protection_period"/>
<xs:element ref="call_protection_type"/>
<xs:element ref="camra_make_whole_ind"/>
<xs:element ref="camra_conversion_price"/>
<xs:element ref="convertible_flag"/>
<xs:element ref="nra_tax_code"/>
<xs:element ref="tax_relief_at_source_ind"/>
<xs:element ref="tax_withholding_code"/>
<xs:element ref="tax_status"/>
<xs:element ref="voting_rights"/>
<xs:element ref="votes_per_share"/>
<xs:element ref="cum_voting_flag"/>
<xs:element ref="coupon_cap"/>
<xs:element ref="coupon_floor"/>
<xs:element ref="cross_currency_country"/>
<xs:element ref="cross_currency_fwd_rate"/>
<xs:element ref="cross_rate"/>
<xs:element ref="fwd_base_rate"/>
<xs:element ref="fwd_rate"/>
<xs:element ref="fwd_reset_date"/>
<xs:element ref="spot_base_rate"/>
<xs:element ref="spot_cross_rate"/>
<xs:element ref="fwd_point_difference"/>
<xs:element ref="fwd_broker_code"/>
<xs:element ref="fwd_side"/>
<xs:element ref="redemption_currency"/>
<xs:element ref="redenomination_date"/>
<xs:element ref="redenomination_flag"/>
<xs:element ref="amt_flag"/>
<xs:element ref="orig_entrydate"/>
<xs:element ref="orig_enteredby"/>
<xs:element ref="last_entrydate"/>
<xs:element ref="last_enteredby"/>
<xs:element ref="credit_family_id"/>
<xs:element ref="cusip"/>
<xs:element ref="isin"/>
<xs:element ref="sedol"/>
<xs:element ref="ticker"/>
<xs:element ref="apace_accrual_type"/>
<xs:element ref="capital_income_flag"/>
<xs:element ref="wal_date"/>
<xs:element ref="cfb_level_pay"/>
<xs:element ref="pending_corp_action"/>
<xs:element ref="pending_proxy_vote"/>
<xs:element ref="pms_live_indicator"/>
<xs:element ref="pms_price_type"/>
<xs:element ref="spark_flag"/>
<xs:element ref="whittingdale_debt_cat"/>
<xs:element ref="whittingdale_rating"/>
<xs:element ref="whittingdale_code"/>
<xs:element ref="expiration_date"/>
<xs:element ref="maturity_price"/>
<xs:element ref="commencement_date"/>
<xs:element ref="declared_payment_date"/>
<xs:element ref="drawer"/>
<xs:element ref="fv_volatility"/>
<xs:element ref="mv_volatility"/>
<xs:element ref="settle_period"/>
<xs:element ref="trading_margin"/>
<xs:element ref="compound_frequency"/>
<xs:element ref="coupon_rounding"/>
<xs:element ref="duration_to_reset"/>
<xs:element ref="float_rate_index_location"/>
<xs:element ref="periodic_basis_point_cap"/>
<xs:element ref="weighted_average_coupon"/>
<xs:element ref="whittingdale_issuer"/>
<xs:element ref="settlement_location"/>
<xs:element ref="attachment_lower"/>
<xs:element ref="attachment_upper"/>
<xs:element ref="exposure_type"/>
<xs:element ref="nth2default"/>
<xs:element ref="restruct_doc_clause"/>
<xs:element ref="swap_counterparty"/>
<xs:element ref="swaption_issue_date"/>
<xs:element ref="swaption_mat_date"/>
<xs:element ref="apace_call_price"/>
<xs:element ref="apace_call_date"/>
<xs:element ref="apace_callable_flag"/>
<xs:element ref="apace_put_price"/>
<xs:element ref="apace_put_date"/>
<xs:element ref="apace_putable_flag"/>
<xs:element ref="apace_day_count"/>
<xs:element ref="apace_io_ind"/>
<xs:element ref="apace_pass_thru_flag"/>
<xs:element ref="apace_price_method"/>
<xs:element ref="apace_price_source"/>
<xs:element ref="apace_depository_type"/>
<xs:element ref="apace_conv_ratio"/>
<xs:element ref="apace_floating_rate"/>
<xs:element ref="apace_frn_reset_code"/>
<xs:element ref="apace_frn_reset_date"/>
<xs:element ref="apace_step_conversion_date"/>
<xs:element ref="apace_step_conversion_rate"/>
<xs:element ref="apace_accrual_date_code"/>
<xs:element ref="apace_payment_date_code"/>
<xs:element ref="apace_payment_cycle_code"/>
<xs:element ref="apace_par_call_date"/>
<xs:element ref="apace_prerefund_price"/>
<xs:element ref="apace_prerefund_date"/>
<xs:element ref="apace_sink_fund_flag"/>
<xs:element ref="make_whole_call_flag"/>
<xs:element ref="fido_security_type_jvst"/>
<xs:element ref="fido_security_type_jstp"/>
<xs:element ref="fido_issuer_id"/>
<xs:element ref="fido_guarantor_id"/>
<xs:element ref="fido_name"/>
<xs:element ref="draft_id"/>
<xs:element ref="bbsw_at_last_reset"/>
<xs:element ref="delta"/>
<xs:element ref="price"/>
<xs:element ref="benchmark_index_sec"/>
<xs:element ref="index_multiplier"/>
<xs:element ref="index_spread"/>
<xs:element ref="index_link_location"/>
<xs:element ref="index_lag"/>
<xs:element ref="benchmark_rounding"/>
<xs:element ref="index_link_bus_day_rule"/>
<xs:element ref="calculation_type"/>
<xs:element ref="start_day_of_month"/>
<xs:element ref="pms_issue"/>
<xs:element ref="pms_name"/>
<xs:element ref="camra_cusip"/>
<xs:element ref="infoexpress_id"/>
<xs:element ref="issuer_desc"/>
<xs:element ref="parent_issuer_desc"/>
<xs:element ref="lead_mgr"/>
<xs:element ref="co_mgr"/>
<xs:element ref="superticker_desc"/>
<xs:element ref="fmc_id"/>
<xs:element ref="spintl_id"/>
<xs:element ref="tranche_type"/>
<xs:element ref="collateral_type"/>
<xs:element ref="ab_fund_desc"/>
<xs:element ref="adp_number"/>
<xs:element ref="underlying_account_id"/>
</xs:all>
</xs:complexType>
</xs:element>
<xs:element name="variable_rate_row">
<xs:complexType>
<xs:all>
<xs:element ref="security_id"/>
<xs:element ref="primary_asset_id"/>
<xs:element ref="sedol"/>
<xs:element ref="rate_type"/>
<xs:element ref="coupon"/>
<xs:element ref="effective_date"/>
<xs:element ref="delete_flag"/>
<xs:element ref="update_flag"/>
<xs:element ref="last_enteredby"/>
<xs:element ref="last_entrydate"/>
<xs:element ref="pms_live_indicator"/>
</xs:all>
</xs:complexType>
</xs:element>
<xs:element name="security_id" type="xs:string"/>
<xs:element name="primary_asset_id" type="xs:string"/>
<xs:element name="delay_days" type="xs:double" nillable="true"/>
<xs:element name="arm_indicator" type="xs:string" nillable="true"/>
<xs:element name="camra_abs_und_coll" type="xs:string" nillable="true"/>
<xs:element name="camra_abs_und_coll_cpn" type="xs:double" nillable="true"/>
<xs:element name="initial_principal_pay_date" type="xs:date" nillable="true"/>
<xs:element name="final_principal_pay_date" type="xs:date" nillable="true"/>
<xs:element name="mtg_term" type="xs:int" nillable="true"/>
<xs:element name="original_face" type="xs:double" nillable="true"/>
<xs:element name="pool_number" type="xs:string" nillable="true"/>
<xs:element name="principal_pay_frequency" type="xs:string" nillable="true"/>
<xs:element name="pay_down_date" type="xs:string" nillable="true"/>
<xs:element name="principal_pay_bus_day_rule" type="xs:string" nillable="true"/>
<xs:element name="seasoned_mbs" type="xs:string" nillable="true"/>
<xs:element name="tba_stlmt_month" type="xs:string" nillable="true"/>
<xs:element name="accrual_flag" type="xs:string" nillable="true"/>
<xs:element name="accrual_rule" type="xs:string" nillable="true"/>
<xs:element name="base_payment_date" type="xs:string" nillable="true"/>
<xs:element name="day_count" type="xs:string" nillable="true"/>
<xs:element name="ex_interest_bond_code" type="xs:string" nillable="true"/>
<xs:element name="ex_days" type="xs:int" nillable="true"/>
<xs:element name="ex_div_date" type="xs:date" nillable="true"/>
<xs:element name="last_coupon_date" type="xs:date" nillable="true"/>
<xs:element name="for_bond_security_type" type="xs:string" nillable="true"/>
<xs:element name="dated_date" type="xs:date" nillable="true"/>
<xs:element name="issue_date" type="xs:date" nillable="true"/>
<xs:element name="first_coupon_date" type="xs:date" nillable="true"/>
<xs:element name="second_coupon_date" type="xs:date" nillable="true"/>
<xs:element name="mat_date" type="xs:date" nillable="true"/>
<xs:element name="interest_accrual_method" type="xs:string" nillable="true"/>
<xs:element name="odd_first_coupon_date" type="xs:date" nillable="true"/>
<xs:element name="odd_last_coupon_date" type="xs:date" nillable="true"/>
<xs:element name="payment_eom_rule" type="xs:string" nillable="true"/>
<xs:element name="pay_frequency" type="xs:string" nillable="true"/>
<xs:element name="pay_business_day_rule" type="xs:string" nillable="true"/>
<xs:element name="yield_day_count" type="xs:string" nillable="true"/>
<xs:element name="zero_coupon_type" type="xs:string" nillable="true"/>
<xs:element name="analyst" type="xs:string" nillable="true"/>
<xs:element name="analyst_recomm" type="xs:string" nillable="true"/>
<xs:element name="approval_flag" type="xs:string" nillable="true"/>
<xs:element name="camra_sec_type" type="xs:string" nillable="true"/>
<xs:element name="class" type="xs:string" nillable="true"/>
<xs:element name="comments" type="xs:string" nillable="true"/>
<xs:element name="holding_style" type="xs:string" nillable="true"/>
<xs:element name="issued_capital" type="xs:double" nillable="true"/>
<xs:element name="issued_capital_currency" type="xs:string" nillable="true"/>
<xs:element name="min_denomination" type="xs:double" nillable="true"/>
<xs:element name="price_multiplier" type="xs:double" nillable="true"/>
<xs:element name="pricing_identifier" type="xs:string" nillable="true"/>
<xs:element name="quantity_issued" type="xs:double" nillable="true"/>
<xs:element name="shares_outstanding" type="xs:decimal" nillable="true"/>
<xs:element name="quantity_type" type="xs:string" nillable="true"/>
<xs:element name="redemption_value" type="xs:double" nillable="true"/>
<xs:element name="scb_industry" type="xs:string" nillable="true"/>
<xs:element name="issue_desc1" type="xs:string" nillable="true"/>
<xs:element name="issue_desc2" type="xs:string" nillable="true"/>
<xs:element name="issue_desc3" type="xs:string" nillable="true"/>
<xs:element name="issue_short_name" type="xs:string" nillable="true"/>
<xs:element name="trading_lot_size" type="xs:double" nillable="true"/>
<xs:element name="unit_factor" type="xs:double" nillable="true"/>
<xs:element name="camra_exercise_date" type="xs:date" nillable="true"/>
<xs:element name="camra_expiration_date" type="xs:date" nillable="true"/>
<xs:element name="alliance_sector" type="xs:string" nillable="true"/>
<xs:element name="alliance_industry" type="xs:string" nillable="true"/>
<xs:element name="apace_security_type" type="xs:string" nillable="true"/>
<xs:element name="camra_gl_type" type="xs:string" nillable="true"/>
<xs:element name="emerg_mkt_ind" type="xs:string" nillable="true"/>
<xs:element name="form_13f_flag" type="xs:string" nillable="true"/>
<xs:element name="instrument_class" type="xs:string"/>
<xs:element name="issue_type" type="xs:string"/>
<xs:element name="mortgage_sector" type="xs:string" nillable="true"/>
<xs:element name="naic_code" type="xs:string" nillable="true"/>
<xs:element name="performance_segment" type="xs:string" nillable="true"/>
<xs:element name="program_type" type="xs:string" nillable="true"/>
<xs:element name="camra_sic_code2" type="xs:string" nillable="true"/>
<xs:element name="camra_sched_d_group" type="xs:string" nillable="true"/>
<xs:element name="camra_sched_d_state" type="xs:string" nillable="true"/>
<xs:element name="security_form" type="xs:string" nillable="true"/>
<xs:element name="security_type_distrib" type="xs:string" nillable="true"/>
<xs:element name="camra_sic_code" type="xs:string" nillable="true"/>
<xs:element name="structured_note_flag" type="xs:string" nillable="true"/>
<xs:element name="underlying_category" type="xs:string" nillable="true"/>
<xs:element name="primary_asset_id_type" type="xs:string"/>
<xs:element name="superticker" type="xs:string" nillable="true"/>
<xs:element name="default_status" type="xs:string" nillable="true"/>
<xs:element name="default_date" type="xs:date" nillable="true"/>
<xs:element name="accrue_in_default_ind" type="xs:string" nillable="true"/>
<xs:element name="ctd_bond" type="xs:string" nillable="true"/>
<xs:element name="contract_size" type="xs:double" nillable="true"/>
<xs:element name="derivative_type" type="xs:string" nillable="true"/>
<xs:element name="delivery_method" type="xs:string" nillable="true"/>
<xs:element name="conversion_factor" type="xs:double" nillable="true"/>
<xs:element name="flex_option_ind" type="xs:string" nillable="true"/>
<xs:element name="leap_option_ind" type="xs:string" nillable="true"/>
<xs:element name="orig_strike_price" type="xs:double" nillable="true"/>
<xs:element name="otc_flag" type="xs:string" nillable="true"/>
<xs:element name="part_paid_percent" type="xs:double" nillable="true"/>
<xs:element name="strike_price" type="xs:double" nillable="true"/>
<xs:element name="put_call_flag" type="xs:string" nillable="true"/>
<xs:element name="strike_price_type" type="xs:string" nillable="true"/>
<xs:element name="pay_currency" type="xs:string" nillable="true"/>
<xs:element name="rec_currency" type="xs:string" nillable="true"/>
<xs:element name="premium_amount" type="xs:double" nillable="true"/>
<xs:element name="warrant_style" type="xs:string" nillable="true"/>
<xs:element name="pay_status" type="xs:string" nillable="true"/>
<xs:element name="tick_amount" type="xs:double" nillable="true"/>
<xs:element name="right_warrant_option_type" type="xs:string" nillable="true"/>
<xs:element name="underlying_cusip" type="xs:string" nillable="true"/>
<xs:element name="var_margin_rule" type="xs:int" nillable="true"/>
<xs:element name="nominal_annual_income" type="xs:double" nillable="true"/>
<xs:element name="dividend_frequency" type="xs:string" nillable="true"/>
<xs:element name="dividend_reinvestment_ind" type="xs:string" nillable="true"/>
<xs:element name="dr_sponsoring" type="xs:string" nillable="true"/>
<xs:element name="dr_sponsor" type="xs:string" nillable="true"/>
<xs:element name="claim_type" type="xs:string" nillable="true"/>
<xs:element name="dated_date_cpi" type="xs:double" nillable="true"/>
<xs:element name="when_issued_ind" type="xs:string" nillable="true"/>
<xs:element name="series" type="xs:string" nillable="true"/>
<xs:element name="tranche" type="xs:string" nillable="true"/>
<xs:element name="guarantee_type" type="xs:string" nillable="true"/>
<xs:element name="deep_discount_ind" type="xs:string" nillable="true"/>
<xs:element name="perpetual_flag" type="xs:string" nillable="true"/>
<xs:element name="maturity_override" type="xs:string" nillable="true"/>
<xs:element name="camra_index_desc" type="xs:string" nillable="true"/>
<xs:element name="camra_index_spread" type="xs:double" nillable="true"/>
<xs:element name="coupon" type="xs:double" nillable="true"/>
<xs:element name="rate_benchmark" type="xs:string" nillable="true"/>
<xs:element name="rate_multiplier" type="xs:double" nillable="true"/>
<xs:element name="spread_to_benchmark" type="xs:double" nillable="true"/>
<xs:element name="rate_reset_frequency" type="xs:string" nillable="true"/>
<xs:element name="rate_base_reset_date" type="xs:date" nillable="true"/>
<xs:element name="reset_lag_days" type="xs:double" nillable="true"/>
<xs:element name="reset_lockout_days" type="xs:double" nillable="true"/>
<xs:element name="next_reset_date" type="xs:date" nillable="true"/>
<xs:element name="rate_calculate_switch" type="xs:string" nillable="true"/>
<xs:element name="rate_reset_bus_day_rule" type="xs:string" nillable="true"/>
<xs:element name="rate_reset_eom_rule" type="xs:string" nillable="true"/>
<xs:element name="rate_type" type="xs:string" nillable="true"/>
<xs:element name="mutual_fund_sponsor" type="xs:string" nillable="true"/>
<xs:element name="regulated_flag" type="xs:string" nillable="true"/>
<xs:element name="tia_1961_flag" type="xs:string" nillable="true"/>
<xs:element name="accumulation_income_flag" type="xs:string" nillable="true"/>
<xs:element name="fsa_indicator" type="xs:string" nillable="true"/>
<xs:element name="income_dist_policy" type="xs:string" nillable="true"/>
<xs:element name="mutual_fund_charge_type" type="xs:string" nillable="true"/>
<xs:element name="holdings_flag" type="xs:string" nillable="true"/>
<xs:element name="issuer_type" type="xs:string" nillable="true"/>
<xs:element name="issuer_id" type="xs:string" nillable="true"/>
<xs:element name="parent_issuer_id" type="xs:string" nillable="true"/>
<xs:element name="country" type="xs:string" nillable="true"/>
<xs:element name="currency" type="xs:string" nillable="true"/>
<xs:element name="country_of_origin" type="xs:string" nillable="true"/>
<xs:element name="risk_country" type="xs:string" nillable="true"/>
<xs:element name="currency_of_earnings" type="xs:string" nillable="true"/>
<xs:element name="currency_of_income" type="xs:string" nillable="true"/>
<xs:element name="currency_of_trade" type="xs:string" nillable="true"/>
<xs:element name="principal_currency" type="xs:string" nillable="true"/>
<xs:element name="exchange" type="xs:string" nillable="true"/>
<xs:element name="state_code" type="xs:string" nillable="true"/>
<xs:element name="muni_insurance" type="xs:string" nillable="true"/>
<xs:element name="conduit" type="xs:string" nillable="true"/>
<xs:element name="muni_note_type" type="xs:string" nillable="true"/>
<xs:element name="muni_issuer" type="xs:string" nillable="true"/>
<xs:element name="obligation_type" type="xs:string" nillable="true"/>
<xs:element name="oes_next_call_date" type="xs:date" nillable="true"/>
<xs:element name="offering_yield" type="xs:double" nillable="true"/>
<xs:element name="remarketing_agent" type="xs:string" nillable="true"/>
<xs:element name="tax_exempt_region" type="xs:string" nillable="true"/>
<xs:element name="fed_wire" type="xs:string" nillable="true"/>
<xs:element name="oid_flag" type="xs:string" nillable="true"/>
<xs:element name="oid_number" type="xs:int" nillable="true"/>
<xs:element name="oi_price" type="xs:double" nillable="true"/>
<xs:element name="camra_moody_sector" type="xs:string" nillable="true"/>
<xs:element name="restricted" type="xs:string" nillable="true"/>
<xs:element name="camra_class_144" type="xs:string" nillable="true"/>
<xs:element name="foreign_restriction_ind" type="xs:string" nillable="true"/>
<xs:element name="foreign_restriction_req" type="xs:double" nillable="true"/>
<xs:element name="sec_144a" type="xs:string" nillable="true"/>
<xs:element name="reg_s" type="xs:string" nillable="true"/>
<xs:element name="prvt_place_ind" type="xs:string" nillable="true"/>
<xs:element name="liquid_flag" type="xs:string" nillable="true"/>
<xs:element name="call_protection_period" type="xs:int" nillable="true"/>
<xs:element name="call_protection_type" type="xs:string" nillable="true"/>
<xs:element name="camra_make_whole_ind" type="xs:string" nillable="true"/>
<xs:element name="camra_conversion_price" type="xs:double" nillable="true"/>
<xs:element name="convertible_flag" type="xs:string" nillable="true"/>
<xs:element name="nra_tax_code" type="xs:string" nillable="true"/>
<xs:element name="tax_relief_at_source_ind" type="xs:string" nillable="true"/>
<xs:element name="tax_withholding_code" type="xs:string" nillable="true"/>
<xs:element name="tax_status" type="xs:string" nillable="true"/>
<xs:element name="voting_rights" type="xs:string" nillable="true"/>
<xs:element name="votes_per_share" type="xs:int" nillable="true"/>
<xs:element name="cum_voting_flag" type="xs:string" nillable="true"/>
<xs:element name="coupon_cap" type="xs:double" nillable="true"/>
<xs:element name="coupon_floor" type="xs:double" nillable="true"/>
<xs:element name="cross_currency_country" type="xs:string" nillable="true"/>
<xs:element name="cross_currency_fwd_rate" type="xs:double" nillable="true"/>
<xs:element name="cross_rate" type="xs:double" nillable="true"/>
<xs:element name="fwd_base_rate" type="xs:double" nillable="true"/>
<xs:element name="fwd_rate" type="xs:double" nillable="true"/>
<xs:element name="fwd_reset_date" type="xs:date" nillable="true"/>
<xs:element name="spot_base_rate" type="xs:double" nillable="true"/>
<xs:element name="spot_cross_rate" type="xs:double" nillable="true"/>
<xs:element name="fwd_point_difference" type="xs:double" nillable="true"/>
<xs:element name="fwd_broker_code" type="xs:string" nillable="true"/>
<xs:element name="fwd_side" type="xs:string" nillable="true"/>
<xs:element name="redemption_currency" type="xs:string" nillable="true"/>
<xs:element name="redenomination_date" type="xs:date" nillable="true"/>
<xs:element name="redenomination_flag" type="xs:string" nillable="true"/>
<xs:element name="amt_flag" type="xs:string" nillable="true"/>
<xs:element name="orig_entrydate" type="xs:dateTime" nillable="true"/>
<xs:element name="orig_enteredby" type="xs:string" nillable="true"/>
<xs:element name="last_entrydate" type="xs:dateTime" nillable="true"/>
<xs:element name="last_enteredby" type="xs:string" nillable="true"/>
<xs:element name="credit_family_id" type="xs:string" nillable="true"/>
<xs:element name="cusip" type="xs:string" nillable="true"/>
<xs:element name="isin" type="xs:string" nillable="true"/>
<xs:element name="sedol" type="xs:string" nillable="true"/>
<xs:element name="ticker" type="xs:string" nillable="true"/>
<xs:element name="apace_accrual_type" type="xs:string" nillable="true"/>
<xs:element name="capital_income_flag" type="xs:string" nillable="true"/>
<xs:element name="wal_date" type="xs:date" nillable="true"/>
<xs:element name="cfb_level_pay" type="xs:double" nillable="true"/>
<xs:element name="pending_corp_action" type="xs:string" nillable="true"/>
<xs:element name="pending_proxy_vote" type="xs:string" nillable="true"/>
<xs:element name="pms_live_indicator" type="xs:string" nillable="true"/>
<xs:element name="pms_price_type" type="xs:string" nillable="true"/>
<xs:element name="spark_flag" type="xs:string" nillable="true"/>
<xs:element name="whittingdale_debt_cat" type="xs:int" nillable="true"/>
<xs:element name="whittingdale_rating" type="xs:int" nillable="true"/>
<xs:element name="whittingdale_code" type="xs:string" nillable="true"/>
<xs:element name="expiration_date" type="xs:date" nillable="true"/>
<xs:element name="maturity_price" type="xs:double" nillable="true"/>
<xs:element name="commencement_date" type="xs:date" nillable="true"/>
<xs:element name="declared_payment_date" type="xs:date" nillable="true"/>
<xs:element name="drawer" type="xs:string" nillable="true"/>
<xs:element name="fv_volatility" type="xs:double" nillable="true"/>
<xs:element name="mv_volatility" type="xs:double" nillable="true"/>
<xs:element name="settle_period" type="xs:double" nillable="true"/>
<xs:element name="trading_margin" type="xs:double" nillable="true"/>
<xs:element name="compound_frequency" type="xs:string" nillable="true"/>
<xs:element name="coupon_rounding" type="xs:double" nillable="true"/>
<xs:element name="duration_to_reset" type="xs:string" nillable="true"/>
<xs:element name="float_rate_index_location" type="xs:string" nillable="true"/>
<xs:element name="periodic_basis_point_cap" type="xs:decimal" nillable="true"/>
<xs:element name="weighted_average_coupon" type="xs:double" nillable="true"/>
<xs:element name="whittingdale_issuer" type="xs:int" nillable="true"/>
<xs:element name="settlement_location" type="xs:string" nillable="true"/>
<xs:element name="attachment_lower" type="xs:double" nillable="true"/>
<xs:element name="attachment_upper" type="xs:double" nillable="true"/>
<xs:element name="exposure_type" type="xs:string" nillable="true"/>
<xs:element name="nth2default" type="xs:double" nillable="true"/>
<xs:element name="restruct_doc_clause" type="xs:string" nillable="true"/>
<xs:element name="swap_counterparty" type="xs:string" nillable="true"/>
<xs:element name="swaption_issue_date" type="xs:date" nillable="true"/>
<xs:element name="swaption_mat_date" type="xs:date" nillable="true"/>
<xs:element name="apace_call_price" type="xs:double" nillable="true"/>
<xs:element name="apace_call_date" type="xs:date" nillable="true"/>
<xs:element name="apace_callable_flag" type="xs:string" nillable="true"/>
<xs:element name="apace_put_price" type="xs:double" nillable="true"/>
<xs:element name="apace_put_date" type="xs:date" nillable="true"/>
<xs:element name="apace_putable_flag" type="xs:string" nillable="true"/>
<xs:element name="apace_day_count" type="xs:string" nillable="true"/>
<xs:element name="apace_io_ind" type="xs:string" nillable="true"/>
<xs:element name="apace_pass_thru_flag" type="xs:string" nillable="true"/>
<xs:element name="apace_price_method" type="xs:string" nillable="true"/>
<xs:element name="apace_price_source" type="xs:string" nillable="true"/>
<xs:element name="apace_depository_type" type="xs:string" nillable="true"/>
<xs:element name="apace_conv_ratio" type="xs:double" nillable="true"/>
<xs:element name="apace_floating_rate" type="xs:string" nillable="true"/>
<xs:element name="apace_frn_reset_code" type="xs:string" nillable="true"/>
<xs:element name="apace_frn_reset_date" type="xs:date" nillable="true"/>
<xs:element name="apace_step_conversion_date" type="xs:date" nillable="true"/>
<xs:element name="apace_step_conversion_rate" type="xs:double" nillable="true"/>
<xs:element name="apace_accrual_date_code" type="xs:string" nillable="true"/>
<xs:element name="apace_payment_date_code" type="xs:string" nillable="true"/>
<xs:element name="apace_payment_cycle_code" type="xs:string" nillable="true"/>
<xs:element name="apace_par_call_date" type="xs:date" nillable="true"/>
<xs:element name="apace_prerefund_price" type="xs:double" nillable="true"/>
<xs:element name="apace_prerefund_date" type="xs:date" nillable="true"/>
<xs:element name="apace_sink_fund_flag" type="xs:string" nillable="true"/>
<xs:element name="make_whole_call_flag" type="xs:string" nillable="true"/>
<xs:element name="effective_date" type="xs:date"/>
<xs:element name="delete_flag" type="xs:string" nillable="true"/>
<xs:element name="update_flag" type="xs:string" nillable="true"/>
<xs:element name="fido_security_type_jvst" type="xs:int" nillable="true"/>
<xs:element name="fido_security_type_jstp" type="xs:string" nillable="true"/>
<xs:element name="fido_issuer_id" type="xs:int" nillable="true"/>
<xs:element name="fido_guarantor_id" type="xs:int" nillable="true"/>
<xs:element name="fido_name" type="xs:string" nillable="true"/>
<xs:element name="draft_id" type="xs:string" nillable="true"/>
<xs:element name="bbsw_at_last_reset" type="xs:double" nillable="true"/>
<xs:element name="delta" type="xs:double" nillable="true"/>
<xs:element name="price" type="xs:double" nillable="true"/>
<xs:element name="benchmark_index_sec" type="xs:string" nillable="true"/>
<xs:element name="index_multiplier" type="xs:double" nillable="true"/>
<xs:element name="index_spread" type="xs:double" nillable="true"/>
<xs:element name="index_link_location" type="xs:string" nillable="true"/>
<xs:element name="index_lag" type="xs:double" nillable="true"/>
<xs:element name="benchmark_rounding" type="xs:int" nillable="true"/>
<xs:element name="index_link_bus_day_rule" type="xs:string" nillable="true"/>
<xs:element name="calculation_type" type="xs:int" nillable="true"/>
<xs:element name="start_day_of_month" type="xs:int" nillable="true"/>
<xs:element name="pms_issue" type="xs:string" nillable="true"/>
<xs:element name="pms_name" type="xs:string" nillable="true"/>
<xs:element name="camra_cusip" type="xs:string" nillable="true"/>
<xs:element name="infoexpress_id" type="xs:string" nillable="true"/>
<xs:element name="issuer_desc" type="xs:string" nillable="true"/>
<xs:element name="parent_issuer_desc" type="xs:string" nillable="true"/>
<xs:element name="lead_mgr" type="xs:string" nillable="true"/>
<xs:element name="co_mgr" type="xs:string" nillable="true"/>
<xs:element name="superticker_desc" type="xs:string" nillable="true"/>
<xs:element name="fmc_id" type="xs:string" nillable="true"/>
<xs:element name="spintl_id" type="xs:string" nillable="true"/>
<xs:element name="tranche_type" type="xs:string" nillable="true"/>
<xs:element name="collateral_type" type="xs:string" nillable="true"/>
<xs:element name="ab_fund_desc" type="xs:string" nillable="true"/>
<xs:element name="adp_number" type="xs:string" nillable="true"/>
<xs:element name="underlying_account_id" type="xs:string" nillable="true"/>
</xs:schema>
sec.xml
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<security security_count="1" variable_rate_count="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="security.xsd">
<security_row><security_id>LZ002359750</security_id><primary_asset_id>B2479G9</primary_asset_id><delay_days xsi:nil="true"></delay_days><arm_indicator xsi:nil="true"></arm_indicator><camra_abs_und_coll xsi:nil="true"></camra_abs_und_coll><camra_abs_und_coll_cpn xsi:nil="true"></camra_abs_und_coll_cpn><initial_principal_pay_date xsi:nil="true"></initial_principal_pay_date><final_principal_pay_date xsi:nil="true"></final_principal_pay_date><mtg_term xsi:nil="true"></mtg_term><original_face xsi:nil="true"></original_face><pool_number xsi:nil="true"></pool_number><principal_pay_frequency xsi:nil="true"></principal_pay_frequency><pay_down_date xsi:nil="true"></pay_down_date><principal_pay_bus_day_rule xsi:nil="true"></principal_pay_bus_day_rule><seasoned_mbs xsi:nil="true"></seasoned_mbs><tba_stlmt_month xsi:nil="true"></tba_stlmt_month><accrual_flag>Y</accrual_flag><accrual_rule>1</accrual_rule><base_payment_date>0831</base_payment_date><day_count>ACT/ACT</day_count><ex_interest_bond_code xsi:nil="true"></ex_interest_bond_code><ex_days xsi:nil="true"></ex_days><ex_div_date xsi:nil="true"></ex_div_date><last_coupon_date>2017-08-31</last_coupon_date><for_bond_security_type>GER</for_bond_security_type><dated_date>2007-08-31</dated_date><issue_date>2007-08-31</issue_date><first_coupon_date>2008-08-31</first_coupon_date><second_coupon_date>2009-08-31</second_coupon_date><mat_date>2017-08-31</mat_date><interest_accrual_method>PER</interest_accrual_method><odd_first_coupon_date xsi:nil="true"></odd_first_coupon_date><odd_last_coupon_date xsi:nil="true"></odd_last_coupon_date><payment_eom_rule>Y</payment_eom_rule><pay_frequency>A</pay_frequency><pay_business_day_rule>BD</pay_business_day_rule><yield_day_count>ACT/ACT</yield_day_count><zero_coupon_type xsi:nil="true"></zero_coupon_type><analyst>SH</analyst><analyst_recomm xsi:nil="true"></analyst_recomm><approval_flag>Y</approval_flag><camra_sec_type xsi:nil="true"></camra_sec_type><class xsi:nil="true"></class><comments xsi:nil="true"></comments><holding_style>BE</holding_style><issued_capital xsi:nil="true"></issued_capital><issued_capital_currency>EUR</issued_capital_currency><min_denomination>50000</min_denomination><price_multiplier>0.01</price_multiplier><pricing_identifier xsi:nil="true"></pricing_identifier><quantity_issued>2250000</quantity_issued><shares_outstanding>2250000</shares_outstanding><quantity_type>PAR</quantity_type><redemption_value>100</redemption_value><scb_industry xsi:nil="true"></scb_industry><issue_desc1>DEUTSCHE BANK AG</issue_desc1><issue_desc2 xsi:nil="true"></issue_desc2><issue_desc3 xsi:nil="true"></issue_desc3><issue_short_name>DEUTSCHE BANK AG</issue_short_name><trading_lot_size>50000</trading_lot_size><unit_factor>1</unit_factor><camra_exercise_date xsi:nil="true"></camra_exercise_date><camra_expiration_date xsi:nil="true"></camra_expiration_date><alliance_sector>230</alliance_sector><alliance_industry>23030</alliance_industry><camra_gl_type xsi:nil="true"></camra_gl_type><emerg_mkt_ind xsi:nil="true"></emerg_mkt_ind><form_13f_flag xsi:nil="true"></form_13f_flag><instrument_class>FI</instrument_class><issue_type>BOND</issue_type><mortgage_sector>ZZ</mortgage_sector><naic_code xsi:nil="true"></naic_code><performance_segment>3</performance_segment><program_type xsi:nil="true"></program_type><camra_sic_code2 xsi:nil="true"></camra_sic_code2><camra_sched_d_group xsi:nil="true"></camra_sched_d_group><camra_sched_d_state xsi:nil="true"></camra_sched_d_state><security_form xsi:nil="true"></security_form><security_type_distrib xsi:nil="true"></security_type_distrib><camra_sic_code xsi:nil="true"></camra_sic_code><structured_note_flag>N</structured_note_flag><underlying_category xsi:nil="true"></underlying_category><primary_asset_id_type>aPACE</primary_asset_id_type><superticker>B2479G9</superticker><default_status>N</default_status><default_date xsi:nil="true"></default_date><accrue_in_default_ind>N</accrue_in_default_ind><ctd_bond xsi:nil="true"></ctd_bond><contract_size xsi:nil="true"></contract_size><derivative_type xsi:nil="true"></derivative_type><delivery_method xsi:nil="true"></delivery_method><conversion_factor xsi:nil="true"></conversion_factor><flex_option_ind xsi:nil="true"></flex_option_ind><leap_option_ind xsi:nil="true"></leap_option_ind><orig_strike_price xsi:nil="true"></orig_strike_price><otc_flag xsi:nil="true"></otc_flag><part_paid_percent xsi:nil="true"></part_paid_percent><strike_price xsi:nil="true"></strike_price><put_call_flag xsi:nil="true"></put_call_flag><strike_price_type xsi:nil="true"></strike_price_type><pay_currencyThen you hit a bug in your version of Oracle. You may want to investigate and update to a newer version. I get the following error when trying to register your schema in 10.2.0.1
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LSX-00246: invalid QNAME "***_voting_flag"
This error is consistent with Spy 2008 as well (I didn't try Xerces but I've got two that agree so it's good for me). -
Using two facts of two different star schemas and conformed dimensions
Hi,
I've been working as developer and database designer for years and I'm new to Business Objects. Some people says you can not use two facts of two different star schemas in the same query because of conformed dimensions and loop problems in BO.
For example I have a CUSTOMER_SALE_fACT table containing customer_id and date_id as FK, and some other business metrics about sales. And there is another fact table CUSTOMER_CAMPAIGN_FACT which also contains customer_id and date_id as FK, and some other business metrics about customer campaigns. SO I have two stars like below:
DIM_TIME -- SALE_FACT -- DIM_CUSTOMER
DIM_TIME -- CAMPAIGN_FACT -- DIM_CUSTOMER
Business metrics are loaded into fact tables and facts can be used together along conformed dimensions . This is one of the fundamentals of the dimensional modeling. Is it really impossible to use SALE_FACT and CAMPAIGN_FACT together? If the answer is No, what is the solution?
Saying "you cannot do that because of loops" is very interesting.
Thank you..When you join two facts together with a common dimension you have created what is called a "chasm trap" which leads to invalid results because of the way SQL is processed. The query rows are first retrieved and then aggregated. Since sales fact and campaign fact have no direct relationship, the rows coming from either side can end up as a product join.
Suppose a customer has 3 sales fact rows and 2 campaign fact rows. The result set will have six rows before any aggregation is performed. That would mean that sales measures are doubled and campaign measures are tripled.
You can report on them together, using multiple SQL passes, but you can't query them together. Does that distinction make sense? -
JPA: how to organize multiple databases having the same schema definition?
Hi there,
I'm new to Java EE but I could finish some test projects on GlassFish 3 / Java EE 6 platform.
Now it's time to build the actual system and I need some help in that.
So, I can't really tell you the exact purpose of this system but let's look at the following example which is very close to what I need.
Say there is a database schema definition (DDL) for Oracle 11g and this schema is storing the inventory of a shop. So tables like product, category, price etc
Say there are 50 shops, and I'm getting a new database for each shop every month holding their inventory.
So every month I'm receiving a SQL file with INSERTs (DML) for every shop for the DDL I mentioned above.
I'm getting 50 SQL files for the 50 shops every month, so in a year you're talking about 600 SQL files to import.
If it was php/MySQL I could import them into a separate database each, call it shop1_May11, shop2_May11 etc reflecting the shop name and the month in the database name.
This is my question how you guys think I should achieve this in Jave EE / Oracle.
As the DDL is the same I thought to create an Entity for each table and use the Java Persistance API to create the databases and then I'd import the month/shop specific SQL files.
But this means I'm gonna create 50 new schemas in Oracle every month?
Or what's the best way to achieve this?
Thanks in advance
Edited by: 833519 on May 18, 2011 5:28 AM
Edited by: 833519 on May 18, 2011 5:29 AM
Edited by: 833519 on May 18, 2011 5:31 AMJPA helps a lot in persisting and retrieving data that has relationships without having to worry about the relationships at a sQL level.
So you get a java programmer that builds relationships using Java classes (the entities) and a persistence provider worries about the sql required to materialize those relationships.
You seem to be using SQL inserts for persisting the data and you want to generate the reports from SQL as well.
You can use it but you won't be gaining much of its advantages for this project.
Consider reporting applications like the jasperserver for the reports.
Also, I have seen people get away with using one database for this type of thing and just adding a clientid (and optionally branchid) to each table. -
Injecting data into a star schema from a flat staging table
I'm trying to work out a best approach for getting data from a very flat staging table and then loading it into a star schema - I take a row from a table with for example 50 different attributes about a person and then load these into a host of different tables, including linking tables.
One of the attibutes in the staging table will be an instruction to either insert the person and their new data, or update a person and some component of their data or maybe even to terminate a persons records.
I plan to use PL/SQL but I'm not sure on the best approach.
The staging table data will be loaded every 10 minutes and will contain about 300 updates.
I'm not sure if I should just select the staging records into a cursor then insert into the various tables?
Has anyone got any working examples based on a similar experience?
I can provide a working example if required.The database has some elements that make SQL a tad harder to use?
For example:
CREATE TABLE staging
(person_id NUMBER(10) NOT NULL ,
title VARCHAR2(15) NULL ,
initials VARCHAR2(5) NULL ,
forename VARCHAR2(30) NULL ,
middle_name VARCHAR2(30) NULL ,
surname VARCHAR2(50) NULL,
dial_number VARCHAR2(30) NULL,
Is_Contactable CHAR(1) NULL);
INSERT INTO staging
(person_id, title, initials, forename, middle_name, surname, dial_number)
VALUES ('12345', 'Mr', 'NULL', 'Joe', NULL, 'Bloggs', '0117512345','Y')
CREATE TABLE person
(person_id NUMBER(10) NOT NULL ,
title VARCHAR2(15) NULL ,
initials VARCHAR2(5) NULL ,
forename VARCHAR2(30) NULL ,
middle_name VARCHAR2(30) NULL ,
surname VARCHAR2(50) NULL);
CREATE UNIQUE INDEX XPKPerson ON Person
(Person_ID ASC);
ALTER TABLE Person
ADD CONSTRAINT XPKPerson PRIMARY KEY (Person_ID);
CREATE TABLE person_comm
(person_id NUMBER(10) NOT NULL ,
comm_type_id NUMBER(10) NOT NULL ,
comm_id NUMBER(10) NOT NULL );
CREATE UNIQUE INDEX XPKPerson_Comm ON Person_Comm
(Person_ID ASC,Comm_Type_ID ASC,Comm_ID ASC);
ALTER TABLE Person_Comm
ADD CONSTRAINT XPKPerson_Comm PRIMARY KEY (Person_ID,Comm_Type_ID,Comm_ID);
CREATE TABLE person_comm_preference
(person_id NUMBER(10) NOT NULL ,
comm_type_id NUMBER(10) NOT NULL
Is_Contactable CHAR(1) NULL);
CREATE UNIQUE INDEX XPKPerson_Comm_Preference ON Person_Comm_Preference
(Person_ID ASC,Comm_Type_ID ASC);
ALTER TABLE Person_Comm_Preference
ADD CONSTRAINT XPKPerson_Comm_Preference PRIMARY KEY (Person_ID,Comm_Type_ID);
CREATE TABLE comm_type
comm_type_id NUMBER(10) NOT NULL ,
NAME VARCHAR2(25) NULL ,
description VARCHAR2(100) NULL ,
comm_table_name VARCHAR2(50) NULL);
CREATE UNIQUE INDEX XPKComm_Type ON Comm_Type
(Comm_Type_ID ASC);
ALTER TABLE Comm_Type
ADD CONSTRAINT XPKComm_Type PRIMARY KEY (Comm_Type_ID);
insert into comm_type (comm_type_id, NAME, description, comm_table_name) values ('23456','HOME PHONE','Home Phone Number','PHONE');
CREATE TABLE phone
(phone_id NUMBER(10) NOT NULL ,
dial_number VARCHAR2(30) NULL);
Take the record from Staging then update:
'person'
'Person_Comm_Preference' Based on a comm_type of 'HOME_PHONE'
'person_comm' Derived from 'Person' and 'Person_Comm_Preference'
Then update 'Phone' with the number based on a link derived from 'Phone' which is made up of Person_Comm Primary_Key where 'Comm_ID' (part of that composite key)
relates to the Phone table Primary_Key which is Phone_ID.
Does you head hurt as much as mine? -
Hi Experts,
Please tell me the places in OBIEE 11G where i can design the start schema.is it only in Physical Layer or In BBM too?
Thanks-BhaskarFinal point, for performance reasons you should also try to model data into star schema in the physical layer.
If the data is modelled as a true star then there are database features which optimise query performance. These features are set by a DBA when the Warehouse is configured (e.g. enable_star_transformations). The results with this parameter on/off can be staggering (query time reduced from minutes to seconds), showing the power of star schema.
When snowflakes occur, these performance features will not work as designed, and performance will be degraded. There are certain criteria that have to be met by the data e.g. bitmap indices on all of the foreign key columns in the fact.
Please mark if helpful / correct,
Andy
www.project.eu.com
Maybe you are looking for
-
I never had a problem with ios 4. I add an issue with my last iphone 4, my fault. Apple sent me a new phone with ios 5. Worked great for a couple of weeks. Then my wifi started dropping. Not a huge deal. Picked it up again. Then it happened mo
-
Need help on how to use conference facility within adobe connect
I need some help on how to use conference facility within adobe connect?
-
Features missing from Adobe Connect 9, 16x9
I saw a preview of Adobe Connect 9 at the Adobe Connect Federal User's Group meeting yesterday. Product looks great and well worth the trouble to upgrade. Unfortunately, two of my wish list items weren't addressed. For Adobe Connect 9, it's still a 4
-
Date picker not showing up in iOS Reader with multiple dates?
Hi all, The date picker for iOS shows up for forms with a single date box. However, with multiple forms, the keyboard pops up instead of the date picker. It still handles correctly formatting-wise, but it's become a bit of hassle with having to type
-
TS3694 Error occurred while backing up this iPod (-43)
I have been attempting to update my iPod Touch to ios 5 from version 4.3.5. I have followed all suggestions. My Windows 7 Ultimate OS is current. I am running the latest version of iTunes. I have disabled my anti-virus software and disconnected al