IDOC Schema Documentation for WPDWGR01

We would like to get schema definition for WPDWGR01 IDoc Type.
We tried to get the same from ifr.sap.com. We are not able to find it. URL ifr.sap.com goes to some other page.
Please help us in getting schema definition for WPDWGR01.
Regards
NS Rajagopal

Hi!
Try transaction WE60. In Goto - User settings you can activate additional documentation for the field values.
Regards,
Christian

Similar Messages

  • Configuration documentation for idoc type PEXR2001 & idoc type FIDCCH01

    Is there any documentation for SAP configuration that needs to be done to get an outgoing PEXR2001 Idoc created?  This is the payment file Idoc.  We are trying to send this IDoc to a 3rd party, and I don't know how to get it created from the payment run.
    Also, the FIDCCH01 is an incoming IDoc that would change discount dates and amounts on posted financial documents (vendor invoices).  Is there any documentation regarding this IDoc and what incoming RFC is used to actually post the changes?

    resolved the problem/question ourselves

  • Documentation for Idoc view

    Hi All ,
    i have created a idoc view from basic type DELVRY03 . But i  am not able to get the Documentation for this . I have tried we63 but it does not provide documentation for Idoc views .
    Regards
    Saurabh

    resolved the problem/question ourselves

  • How to get IDOC schema in XML

    Please tell me how to get an Idoc schema into XML from SAP.
    I want all the details of an Idoc, i.e Segments and fields in one file.
    Quick response will be appriciated.
    Thanks
    Kiran

    WE60 enter the IDoc type then menu path Documentation->XML Schema. This may depend on what version of SAP you are on.

  • Warning Messages - Could not find schema information for the element applicationSettings - App.Config of a console app

    This is my app.config file
    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
        <configSections>
            <sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
                <section name="IntelBrandFX.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
            </sectionGroup>
        </configSections>
      <appSettings>
        <add key="connStr" value="Data Source=tmvnasql1.tmvn.com;Initial Catalog=brandplan;Integrated Security=True"/>
      </appSettings>
      <applicationSettings>
        <IntelBrandFX.Properties.Settings>
          <setting name="IntelBrandFX_rollupViewerService_extract" serializeAs="String">
            <value>https://viewer.rollup.com/omdsp2008/extract.asmx</value>
          </setting>
        </IntelBrandFX.Properties.Settings>
      </applicationSettings>
    </configuration>
    And the Warning messages  are
    Message 1 Could not find schema information for the element 'applicationSettings'.
    Message 2 Could not find schema information for the element 'IntelBrandFX.Properties.Settings'.
    Message 3 Could not find schema information for the element 'setting'.
    Message 4 Could not find schema information for the attribute 'name'.
    Message 5 Could not find schema information for the attribute 'serializeAs'.
    Message 6 Could not find schema information for the element 'value'.
    Althought they do no hinder me from successfully running the project. these messages are annoying. I have seen many articles on the web but could nowhere find the exact schemas for that the above elements that I could add to the  DotNetConfig.xsd file.
    Could somebody give me an idea how to create xsds for the elements above and include in the dotnetConfig.xsd.
    I understand what needs to be done but not sure of the exact way to do it.
    Thanks,

    You don't need to modify the dotnetconfig.xsd.  All you need to do is generate an XSD for your section and let VS know where it is at.
    1) Create your XSD using any of the various tools available or by hand.
    2) Copy your XSD into the <VSDir>\Xml\Schemas directory.
    3) Create a catalog file for your schema.
    4) Restart VS and it'll load the XSD and give you Intellisense.
    Here's the MSDN documentation for it: http://msdn.microsoft.com/en-us/library/ms255821.aspx
    Michael Taylor - 8/18/09
    http://p3net.mvps.org

  • IDOC status 53 for HRMD_07 but no data uploaded

    Hi,
    We are trying to load the HR  reocrd from etl to R/3.
    I have created an iDoc through WE19 for message type hrmd_a and basic type hrmd_a07.
    Populated infotypes for 0000, 0001, 0002 and 0105.
    idoc created with status 53 (green light) 'Application documention posted' and information note 'HR: ALE inbound processing for HR master data'.
    HOWEVER, when I go to transaction PA30 or tsbles the personnel record is not being created in R/3.
    Please kindly help on this. THANK YOU SO MUCH!
    Its really urgent

    Hi Rajan,
    I am also facing the same problem. Did you got any solution. Please let me know.
    Regards
    Praveen

  • Idoc Schema issue

    Hi,
    We added a new field in Idoc schema, and now we can see the new field at we02/we05 idoc list, however, we don't receive it in XI.
    I already imported the Idoc schema in XI again, updated the mappings, and it still with the same issue.
    Do you guys know where is the problem?
    Thanks,
    Luí

    Hi,
    I was facing the same problem from other point (I saw the error on the trfc queue in the sender system).
    After reading your posts I have tried with IDX2 and same problem than you, so I began to debug in XI (newbie in XI, olddie in ABAP ).
    I have seen that the message is raised when trying to do the  RFC call <i>IDX_META_SYNTAX_READ</i>. I tried with se37 in r/3 and it worked so only the user could be.
    I have changed the user in the RFC destination in XI to my dialogue R/3 user and now XI has received the first idoc from R/3. The previous user was a service user with sapall/sapnew profiles  so it doesn't makes sense but... <b>it works for me! </b>
    hope it helps you,
    David R.

  • Need the Documentation for "Log4PLSQL"

    Hi
    Recently i came across to implement the logging feature "Log4PLSql". I have Installed the feature to one of the schema user. I am not fully aware of the feature and been trying for the right documentation for the same but am not finding anywhere and am require to get fully aware of the same and make the developers to utilise the same in full fledged.
    Can any one please send the link for the Concern documentation.
    Sekhar

    Hi
    I hope this will help you
    LOG4PLSQL

  • Plz help me ALE/IDOC Scinario documentation

    hi and all,
    plz help me ale/idoc scinarios documentation plz send to me.
    thanking u one and all.

    Hi
    ALE:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    Outbound:
    Step 1.  Application document is created when transaction is saved.
             2.  Message control is invoked.
             3.  Messages are processed by system.
             4.  Messages are Edited (if desired).
             5.  Output (ALE /  EDI) is checked
             6.  Validate against Message control record from Partner Profile
             7.  Application Document is saved.
             8.  Entry NAST table is created for every selected output program
                  along with Medium & Timing.
             9.  Check for Process Immediately .
                     If (yes)
                       Determine Processing Program from TNAPR Table.
                     ELSE
                       Execute RSNASTED Program.
           10.  Read Partner Profile to determine Process Code.
           11.  Process Code points to the Function Module & Invoked.
           12.  IDoc is generated. 
           13.  Check for ALE Request.
                        if (Yes)
                            Perform Filters, Conversions, Version Changes etc.
                        Else.
                            IDoc is stored in DATABASE.
    INBOUND:
    Step 1.  EDI Subsystem creates an IDoc file from EDI Messages
            2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from
    startRFC program.
             3.  Data in Control Record is validate against the Partner                       Profile.
            4. IDoc is generated in Database and syntax check is                      carried out.
            5. IDoc file is deleted once file read.
            6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow. 
                       7.  Check for Process Immediately.
                   If NO
                     Execute RBDAPP01 Program
                   Else
                      Read Process Code from Partner Profile        
                           Process Code Points to  Function Module
                     Application Document Posted.     
    IDOC
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Check these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Need Schema Diagram For Adobe Campaign Management

    Hi Guys,
    I am new comer for Adobe Campaign Management. I just started to exploring the ACM.
    I am using the Neolane client to learn ACM. I just want to understand the ACM internal database/table structure, how exactly designed it.
    I have product doc but it is more around UI and functional reference.         
    It is very helpful to me/new beginner that any one provide the schema diagram for Adobe Campaign Management.
    Please share me any material/document which explain the database stuff (schema,tables,data-dictionary,etc ....) then just forward me.
    Thank's in advance,

    This link to the product documentation describes the key tables in Adobe Campaign:
    Description of the main tables

  • Cannot find documentation for MRCA

    Now that the new MRCA tool version 10.1.2.0.3 is available where is the documentation for it? I have only been able to find docs that were last updated in August. I'm going to install in a 10.2.0.1 db and I need the pre-install info.
    Thanks,
    Denise

    Hi Denise,
    The information in the August versions of the RepCA guides applies to the
    10.1.2.0.3 version of RepCA:
    Oracle® Application Server Metadata Repository Creation Assistant User's Guide
    10g Release 2 (10.1.2) for UNIX
    B14129-03
    Oracle® Application Server Metadata Repository Creation Assistant User's Guide
    10g Release 2 (10.1.2) for Microsoft Windows
    B14130-03
    There are 3 updates/caveats having to do with running 10.1.2.0.3 RepCA on
    a 10.2 database. These will be in the January version of the 10.1.2 release
    notes which will be posted on OTN soon. In the meantime, I have cut and
    pasted them below.
    We are working on a better way to coordinate certification updates with the
    release notes.
    Thanks!
    Beth
    3.1.17 Oracle Ultra Search Required (Oracle Database 10g Release 2 (10.2.x) only)
    If you plan to install the OracleAS Metadata Repository on Oracle Database 10g Release 2 (10.2.x), then you must install Oracle Ultra Search on the database.
    OracleAS Metadata Repository Creation Assistant checks if your database contains the WKSYS and WKPROXY schema. If your database does not contain them, OracleAS Metadata Repository Creation Assistant displays the following warning:
    "The Database does not contain Ultra Search Schemas WKSYS and/or WKPROXY. Please install them and try again. Refer to the Database Install Guide and Ultra Search User Guide for more information."
    If your database does not have Oracle Ultra Search installed, you can install it from the Oracle Database 10g Companion CD-ROM. See the Oracle Database Companion CD Installation Guide for details.
    After installing Oracle Ultra Search, you need to load the schemas onto the database using the Database Configuration Assistant (DBCA). Refer to Oracle MetaLink (http://www.metalink.oracle.com) Note.337992.1 for loading Ultra Search schemas.
    3.1.18 Patch Required Prior to Running the Metadata Repository Creation Assistant on a 10.2 Real Application Cluster Database
    You must install ARU patch 7993184 before running the Metadata Repository Creation Assistant on a 10.2 Real Application Cluster Database. If you do not apply the patch, you will receive an error message during Oracle Ultra Search configuration.
    To apply the patch:
    Install the 10.2 Real Application Cluster database.
    Create the database using the DBCA or during the installation.
    Stop all Oracle Processes.
    Install Oracle Ultra Search in the same Oracle home from the companion CD.
    Apply ARU patch 7993184. Go to Oracle MetaLink (http://www.metalink.oracle.com) to obtain the ARU patch.
    Invoke the DBCA to configure Oracle Ultra Search.
    Run the Metadata Repository Creation Assistant.
    3.1.19 Populate DB_DOMAIN Before Running Oracle Metadata Repository Creation Assistant on an Oracle 10.2 Database
    The default installation option for Oracle Database 10g (Release 2) 10.2 does not populate the DB_DOMAIN. The OracleAS Metadata Repository Creation Assistant uses the value of DB_DOMAIN to construct the Oracle Application Server farm name as $SID.$DB_DOMAIN. You should ensure that the DB_DOMAIN is populated in the database with a valid value prior to running OracleAS Metadata Repository Creation Assistant. Failure to do will result in the default farm name of REGRESS.RDBMS.DEV.US.ORACLE.COM.

  • Where is the documentation for Oracle Spatial Relational Model?

    Hi,
    I'm working with Oracle Spatial for my schema model. In the documentation "Oracle Spatial User's Guide and Reference" there is a note about what this is in OTN but i don't find it!!
    Can anybody help me, where I find the "Oracle Spatial Relational Model Guide and Reference"?

    Thanks! But just i have read this information. And in the documentation for spatial 9.0.1 there is one document only, and in this document there is a Note that reference to nonexistent document with title "Oracle Spatial Relational Model Guide and Reference" this is the document that i'm searching.
    Thank you for your help!

  • Documentation for wscompile?

    I finally got around to updating to jwsdp-1_0_01 and was surprised to find that xrpcc was replaced by wscompile in many build.xml files. Except for a few very general remarks in the Tutorial, I can't find any documentation for wscompile at all (Google returns only 4 pages for "wscompile"!).
    Is xrpcc deprecated? (When my old build.xml runs xrpcc, it gives a warning that "sun.tools.javac.Main is deprecated".) Is there a man page, etc., for wscompile?
    Thanks,
    Mike

    Oops, the format of my last message got munged. Here's anoter try:
    Date: 28 Aug 2002
    Title: The JAX-RPC wscompile and wsdeploy Tools
    1 The wscompile Tool
    The wscompile tool generates stubs, ties, serializers,
    and WSDL files used in JAX-RPC clients and services.
    The tool reads as input a configuration file and either
    a WSDL file or an RMI interface that defines the service.
    1.1 Syntax
    wscompile [options] <configuration-file>
    By convention, the configuration file is named config.xml,
    but this is not a requirement.
    The following table lists the wscompile options.
    Note that exactly one of the -import, -define,
    or -gen options must be specified.
      Option                    Description
      -classpath <path>         specify where to find input class files
      -cp <path>                same as -classpath <path>
      -d <directory>            specify where to place generated output files
      -define                   read the service's RMI interface,
                                define a service
      -f:<features>             enable the given features (See the below
                                table for a list of features.  When
                                specifying multiple features, separate
                                them with commas.)
      -features:<features>      same as -f:<features>
      -g                        generate debugging info
      -gen                      same as -gen:client
      -gen:client               generate client artifacts (stubs, etc.)
      -gen:server               generate server artifacts (ties, etc.) and
                                the WSDL file (If you are using wsdeploy
                                you do not specify this option.)
      -gen:both                 generate both client and server artifacts
      -httpproxy:<host>:<port>  specify a HTTP proxy server (port defaults to 8080)
      -import                   read a WSDL file, generate the service's RMI
                                interface and a template of the class that
                                implements the interface
      -keep                     keep generated files
      -model <file>             write the internal model to the given file
      -nd <directory>           specify where to place non-class generated files
      -O                        optimize generated code
      -s <directory>            specify where to place generated source files
      -verbose                  output messages about what the compiler is doing
      -version                  print version information
    The following table lists the features (delimited by commas) that
    may follow the -f option.
      Feature                   Description
      datahandleronly           always map attachments to the DataHandler type
      explicitcontext           turn on explicit service context mapping
      infix=<name>              specify an infix to use for generated serializers
      nodatabinding             turn off data binding for literal encoding
      noencodedtypes            turn off encoding type information
      nomultirefs               turn off support for multiple references
      novalidation              turn off full validation of imported WSDL documents
      searchschema              search schema aggressively for subtypes
      serializeinterfaces       turn on direct serialization of interface types
    1.2 Configuration File
    The wscompile tool reads the configuration file (config.xml),
    which contains information that describes the web service.
    The basic structure of config.xml follows:
    <?xml version="1.0" encoding="UTF-8"?>
    <configuration 
        xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
       <service> or <wsdl> or <modelfile>
    </configuration>
    The <configuration> element may contain exactly one
    <service>, <wsdl>, or <modelfile> element.
    1.2.1 The <service> Element
    If you specify this element, wscompile reads the
    RMI interface that describes the service and
    generates a WSDL file.
    In the <interface> subelement, the name attribute specifies the
    service's RMI interface, and
    the servantName attribute specifies the class that implements
    the interface.
    For example:
    <service name="CollectionIF_Service"
             targetNamespace="http://echoservice.org/wsdl"
             typeNamespace="http://echoservice.org/types"
             packageName="stub_tie_generator_test">
         <interface name="stub_tie_generator_test.CollectionIF"
          servantName="stub_tie_generator_test.CollectionImpl"/>
    </service>
    1.2.2 The <wsdl> Element
    If you specify this element, wscompile
    reads the service's WSDL file and generates
    the service's RMI interface.
    The location attribute specifies the URL of the WSDL
    file, and the packageName attribute specifies
    the package of the classes generated by wscompile.
    For example:
    <wsdl    
        location="http://tempuri.org/sample.wsdl"
        packageName="org.tempuri.sample" />
    1.2.3 The <modelfile> Element
    This element is for advanced users.
    If config.xml contains a <service> or <wsdl> element,
    wscompile generates a model file that
    contains the internal data structures that describe
    the service.
    If you've already generated a model file in
    this manner, then you can reuse it the
    next time you run wscompile.  For example:
    <modelfile location="mymodel.xml.gz"/>
    2.0 The wsdeploy Tool
    The wsdeploy tool reads a WAR file and the jaxrpc-ri.xml
    file and then generates another WAR file that is ready for
    deployment.
    Behind the scenes, wsdeploy runs wscompile with the -gen:server option.
    The wscompile command generates classes and a
    WSDL file which wsdeploy includes
    in the generated WAR file.
    2.1 Syntax
    The syntax for wsdeploy follows:
    wsdeploy <options> <input-war-file>
    The following table lists the tool's options.
    Note that the -o option is required.
      Option                    Description
      -classpath <path>         specify an optional classpath
      -keep                     keep temporary files
      -o <output-war-file>      specify where to place the generated war file
      -tmpdir <directory>       specify the temporary directory to use
      -verbose                  output messages about what the compiler is doing
      -version                  print version information
    2.2 The Input WAR File
    Typically, you create the input WAR file with a
    development tool or with the ant war task.
    Here are the contents of a simple input WAR file:
    META-INF/MANIFEST.MF
    WEB-INF/classes/hello/HelloIF.class
    WEB-INF/classes/hello/HelloImpl.class
    WEB-INF/jaxrpc-ri.xml
    WEB-INF/web.xml
    In this example, HelloIF is the service's RMI interface
    and HelloImpl is the class that implements the interface.
    The web.xml file is the deployment descriptor of a
    web component.  The jaxrpc-ri.xml file is described
    in the next section.
    2.2.2 The jaxrpc-ri.xml File
    The listing that follows shows a jaxrpc-ri.xml file
    for a simple HelloWorld service.
    <?xml version="1.0" encoding="UTF-8"?>
    <webServices
        xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
        version="1.0"
        targetNamespaceBase="http://com.test/wsdl"
        typeNamespaceBase="http://com.test/types"
        urlPatternBase="/ws">
        <endpoint
            name="MyHello"
            displayName="HelloWorld Service"
            description="A simple web service" 
            interface="hello.HelloIF"  
            implementation="hello.HelloImpl"/> 
        <endpointMapping
            endpointName="MyHello"
            urlPattern="/hello"/>
    </webServices>
    The <webServices> element must contain one or more <endpoint>
    elements.  In this example, note that the interface and
    implementation attributes of <endpoint> specify the
    service's interface and implementation class.
    The <endpointMapping> element associates the service
    port with an element of the endpoint URL path
    that follows the urlPatternBase.
    3 Advanced Topics
    This section is for developers who are familiar with
    WSDL, SOAP, and the JAX-RPC specifications.
    3.1 Namespace Mappings
    Here is a schema type name example:
    schemaType="ns1:SampleType"
    xmlns:ns1="http://echoservice.org/types"
    When generating a Java type from a schema type,
    wscompile gets the class name from the local part of
    the schema type name.
    To specify the package name of the generated
    Java classes, you define a mapping between
    the schema type namespace and the package name.
    You define this mapping by adding a <namespaceMappingRegistry>
    element to the config.xml file.  For example:
    <service>
        <namespaceMappingRegistry>
                <namespaceMapping            
                namespace="http://echoservice.org/types"
                packageName="echoservice.org.types"/>
         </namespaceMappingRegistry>
    </service>
    3.5 Handlers
    A handler accesses a
    SOAP message that represents
    an RPC request or response.
    A handler class must implement
    the javax.xml.rpc.handler interface.
    Because it accesses a SOAP message,
    a handler can manipulate the message with
    the APIs of the javax.xml.soap package.
    Examples of handler tasks:
    * Encryption and decryption
    * Logging and auditing
    * Caching
    * Application-specific SOAP header processing
    A handler chain is a list of handlers.
    You may specify one handler chain for the client
    and one for the server.
    On the client, you include the <handlerChains> element
    in the jaxrpc-ri.xml file.  On the server, you
    include this element in the config.xml file.
    Here is an example of the <handlerChains> element
    in config.xml:
    <handlerChains>
      <chain runAt="server"
         roles=
          "http://acme.org/auditing 
           http://acme.org/morphing"
           xmlns:ns1="http://foo/foo-1">
        <handler className="acme.MyHandler"
          headers ="ns1:foo ns1:bar"/>
          <property 
            name="property" value="xyz"/>
        </handler>
      </chain>
    </handlerChains>
    For more information on handlers, see the SOAP Message Handlers chapter
    of the JAX-RPC specifications.

  • 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_currency

    Then 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).

  • Any Function module or BAPIs are available to get scheme name for the inter

    I have internal order no value in table  AUFK-AUFNR ,  and the internal order corresponding Scheme value is available in IMPR-PRNAM . Now I want to inner join both the tables to extract the data , but there is no common field . Is there any Function module or BAPIs are available to get scheme name for the internal orders?

    look at DB-VIEW  "V_IVP_OR".
    Regards,
    Laurent

Maybe you are looking for

  • Putting more than 1 movie into iDVD

    This may seem a stupid question but I have made one movie with English subtitles in it for my company, what I would like to do now is copy the original iMovie and insert say German and French subtitles so I would end up with maybe 3 or 4 iMovies (eac

  • Facetime call between Macbook and Iphone 4 failing.

    I'm using OSX 10.6.4 and placing a facetime call to an Iphone 4 using iOS 4.1. The call goes through and connects and we are able to talk for 15 seconds or so. Then it freezes and I get a call failed notification. Any fixes for this? My firewall is o

  • Displaying conditional gif in report

    for a column in a report, is it possible to display a picture dependent on the column value ( i.e. checkmark for yes values)

  • MIDI piano keypress detection

    Hi all I am totally lost with this problem. MIDI really confuses me and im doing it as my final year project (i didnt realise how hard it was when i picked the project). If anyone has successfully connected an external MIDI interface device (a midi k

  • When is the next update expected for Engage?

    Post Author: DHAG CA Forum: Xcelsius and Live Office Based on my own experience and from reading this board, there clearly seems to be a need for a service pack/bug fix release. Can someone kindly let us know when (roughly) we might expect such a rel