Request Message field to Response Message

Hi Everyone,
I have a synchcronous scenario, where I have a special requirement that I want to  append a Request Message Field in Response Message Structure while sending response to Sender.
Could someone suggest me probable solution, I have come up with using Value mapping table, but I am restricted to use a proxy for dynamic updates to the table??
Regards,
Nipun

Hello,
I have a synchcronous scenario, where I have a special requirement that I want to append a Request Message Field in Response Message Structure while sending response to Sender.
Perhaps the easiest would to to try to ask the endpoint to modify the response such that it contains the request. Otherwise, you can use a logic such as saving into a table and then retrieve the values for the response message mapping.
Hope this helps,
Mark

Similar Messages

  • How to store the value of request message and use it in Response mapping

    Hi All,
    We have an requirement where we need to store the data coming in Request Mapping and use the stored value in Response Mapping. Can anybody help us in how to proceed?
    Thanks
    Sujata

    Hi!
    In Mapping you may use the RFC Lookup function to store values in database table during request mapping and to read values from database table during response mapping.
    You can also use an ABAP or Java Mapping "in front of your" message mapping to store/read the values.
    You can also use an Adapter Module (if applicable for the adapter type you use) and/or a UDF to store the data e.g. in Dynmaic Configuration Header of Request Message and to read these data from Dynamic Configuration Header of Response Message. But this works only for synchronous scenarios (and it means overhead in your message traffic).
    Hope these thinkings help you o find the most suitable way for your concrete scenario!
    Regards,
    Volker
    Note:
    These techniques help you to avoid using BPM.
    Edited by: Volker Kolberg on Aug 27, 2009 11:18 AM

  • I can no longer access Bejeweled Blitz through my facebook account.  I get the message that says, "your browser sent a request that this server could not understand. Size of a request header field exceeds server limit".  Help please.

    I can no longer access Bejeweled Blitz through facebook.  I get the message, "your browser sent a request that this server could not understand. Size of a request header field exceeds server limit". I can access Bejeweled through FB using my husband's log in so to me that suggests the problem is with my log in. Help please.

    Contact FB or use another browser. 

  • Store value from request message to be processed in response mapping

    Hi,
    I have the following synchronous scenario:
    R/3 (ABAP Proxy) <>  XI/PI <> 3rd party Web Service
    I need to reference a value in the sender (request) message in the response mapping.
    For example:
    A request with a user ID is received from R/3 to XI/PI.  I want to store the user ID in the request message.  A response is received from the web service.  I then want to use the user ID in the response mapping.
    I believe XI/PI can meet this requirement with a BPM using container or possibly using a custom table to store Message GUID and the variable value in the request message mapping.
    Are there any other methods that can be used to meet this scenario?
    Thanks and regards,
    Duke

    Hi All,
    This is the first time I've encountered such a requirement.  Most of the time we create our own programs that call the sender proxy, so to interogate the results and call another proxy would be the ideal solution.  But, in this case the standard LSO process controls the execution of the proxy.  We may look into doing an enhancement to the standard code, but I was looking for a way we can do this in PI with minimal effort.
    As Stefan stated, I also noticed that the DynamicConfiguration is emptied in the response.
    We will explore the use of BPM, but from what I can see, utilizing a custom table with the runtime constant MESSAGE_ID may be the simplest solution in PI.
    Thanks and regards,
    Duke

  • How to fill Request Message ID in SXMB_MONI

    Hi,
    I have Abap proxy inbound -outbound asynchronous communication between XI and ERP backend .
    XI sends a kind of requests messages and the backend sends back messages with a kind of response.
    In the Tc:SXMB_MONI  I want to see the correlation between these two messages - for instance, to have an entry in column u201COriginal Message IDu201D or u201CRequest Message IDu201D, like it is made in synchronous communication.
    I think I need to fill the message header (e.g. field Main/RefToMessageID) in the outbound proxy on the backend, but I donu2019t know how to do it. .
    Thanks for your help,
    Janos

    Hi janos
    Then i can suggest a way to meet this. There is no standard way to do it.
    To get the message ID from the message you need to capture that in mapping.
    This code should help you.
    java.util.Map map = container.getTransformationParameters();
    String msgid = (String) map.get ( StreamTransformationConstants.MESSAGE_ID);
    return msgid;
    Now Create a table either in Non SAP or SAP and do a lookup to write the values. I recommend create a Z table in XI and use RFC lookup to write values to it.
    Now just write simple ABAP report to fetch these and give it to any one.
    Moreover extend the report to get the values from SXMSMAST in XI to get payload attached to that Message ID.
    Thanks
    Gaurav

  • Individual entries cannot be put into the change request (message SV141)

    Hi,
    I am trying to save an activity that I have created for SOP (Production>SOP>Function>Mass Processing>Define Activities).
    When I click on the IMG node, I get the following message:
    "Individual entries cannot be put into the change request
    Message no. SV141
    Diagnosis
    For technical reasons, the entries cannot be fully specified in the change request. There are two possible reasons for this:
    1. The key of an entry is longer than 120 characters. All entries whose keys match up to character 119, are then copied into the change request, rather than an individual entry.
    2. The key of an entry contains fields of special data types, for example, packed numbers. The key can only be specified in the change request up to the first such field from the left.
    all entries whose keys match up to character 12 are copied into the change request, rather than a single entry.
    System Response
    The selected entry is copied into the change request correctly, but other entries may be copied as well."
    Can anyone explain why and if I have to do something to ensure it is captured in the CTS?
    Thanks,
    Lars

  • Synchronous message mapping - access to originating request message?

    Say you have a synchronous message - like a SOAP web service request - and you map it to an RFC call, is there any way for the message mapping from the RFC response message to the SOAP response message to access fields from the original SOAP request message?  Or even just a temporary storage area that I could store values from the originating request message?

    Hi Jonathon!
    First of all, why not access the original soap request message inside the RFC..you will be receiving this data in your RFC...is the RFC is standard, maybe you can make a wrapper with a Z RFC of your own to store the original data and use it later to build the RFC response.
    Another idea: you could call a RFC via JCO inside a UDF in mapping.. this RFC could write  some data in XI business system during the request mapping and another call to a "reading" RFC could read that data in the response mapping.
    Other idea: use BPM, you can use containers to store the request SOAP message, call synchronously the RFC and then use a transform step (mapping) to use the original request SOAP message and the RFC response message to "merge"/build the response for the SOAP.
    Regards,
    Matias.
    PD: please give points if useful.

  • Request Message mapping in SXMB_MONI for File - RFC - File without BPM

    Hi ,
    In my File-RFC-File scenario, the messages are processed successfully.
    but when i look into the SXMB_MONI for File to RFC step, the records are present only till the  Message split According to Receiver List and not able to see the records from Request Message mapping step onwards.it contains
    <?xml version="1.0" encoding="UTF-8" ?>
      <ns1:Z_PI_LOTUSNOTES_UNIFORM xmlns:ns1="urn:sap-com:document:sap:rfc:functions" />
    in my mapping for the receiver RFC i have not done the mapping for all the fields. few fields i have disabled. whether this could create a problem in message mapping. pls let me know what needs to be done.

    Is it only for this scenario that the above display issue is occuring or is it for all scenarios?
    If onlt a particular Pipeline steps are displayed then you can check what is the TRACE level set in SXMB_ADM --> Integration Engine Configuration --> and check if the TRACE parameter is set to at least 2 (max is 3 which will ensure that your DB will get full quickly)
    For more information refer: /people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
    Regards,
    Abhishek.

  • RFC_to_File scenario: error in request message mapping

    Hi!
    I am configuring RFC_to_File scenario.
    The error at the begining is:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_Z_RFB_MATERIALEINGABE_PBU_zu_MT
    : Fatal Error: com.sap.engine.lib.xml.parser.Parser
    Exception of class CX_XMS_SYSERR_MAPPING
    When I display the request message mapping are of the message I can see:
    <Trace level="1" type="T">Interface-Mapping http://www.sap-press.de/xi/training/PBU_00 IM_Z_RFB_MATERIALEINGABE_PBU_zu_MI_Material_Async_In</Trace>
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_Z_RFB_MATERIALEINGABE_PBU_zu_MT_Material_</Trace>
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:1, col:202) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest
    Can some one help me to solve this problem?
    Thank you very much!
    regards
    Holger

    Holger,
    Message Mapping Failed.
    >com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data >sections(:main:, row:1, col:202) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
    You are Passing Char to a field, which is not as per the Message Mapping rule
    Cheers
    Agasthuri Doss

  • Message getting struck at Request Message mapping

    Hi All,
    In our interface we have Proxy to HTTP scenario.  When we trigger data from R/3 system the data is getting blocked at SAP XI system.
    In SXMB_MONI when we see the status of the message it doesnot show any error status flag comes with a grey dot .
    Generally as per the XI Message process flow it should be some thing like this
    Inbound message
    Receiver Identification
    Interface determination
    Message Branch According to receiver list
    Request message Mapping
    Technical Routing
    Call Adapter
    Response
    When we expand and see the message monitoring it shows the following steps -
    Inbound message
    Receiver Identification
    Interface determination
    Message Branch According to receiver list
    there is no error messages and you dont see any steps in monitoring after this.
    Trace level is set to 3 and also set trace enable for sync interfaces.
    Please let me know if some one faced this issue and how to resolve this.
    Regards,
    Reddy
    Edited by: Nanda kishore Reddy Narapu Reddy on Apr 8, 2008 5:31 PM

    Hi Srinivas,
    If receiver determination gets fail then it should give a error in SXMB_MONI messages.
    In the trace messages of the "Message Branch According to Receiver list" step in SXMB_MONI we are getting the details of the receiver and also the Communication channel need to be used also correctly.
    I would like to stress that after this step in sxmb_moni it should trigger "Request message mapping" step  but it is got getting triggered.
    Pls let me know if some one faced this issue or is it because of some cache related issue which is stopping the call to trigger message mapping.
    Reagrds,
    Reddy

  • RFC Function module-With Only Request message

    Hi
    i need a RFC with only Request message and Response message is not required.
    please help me, how to create a RFC function module with out Response message, and it should contain only Request message.
    i have created RFC in this way:
    RFC doesn't contain neither import nor export parameters. and i have defined one table in TABLE tab which refers to a ztable created already.
    when i imported RFC into XI i came to know that RFC has both Request and Response messages, but i don't need Response message.
    Thanks in advance..help would be appreciated
    Regards,
    Rajesh

    Thankx Michal,
    I have written ZRFC this way:
    insert ZMM_AUTO_GR from INPUT_TABLE .
      if sy-subrc = 0.
        commit work.
      else.
       rollback work.
    im not using neither import nor export parameters..but using only tables parameters. but when imported in XI im getting same table  structure in both request an response.
    please suggest what changes required in above code to invoke my ZRFC in async way.
    you will not get any response in XI- what chages required in my code to dnt get .reponse in XI.
    appreciate your help.
    Regards,
    Rajesh.

  • RFC to SOAP Interface - Problem in Request Message Mapping

    Dear All,
    We are working on RFC to SOAP Scenario i.e. pulling out data from an WebService from SAP via PI.
    In Request Message Mapping, when the wsdl file is uploaded as Target Message, the wsdl request shows the nested elements like below.
    <Request>
       <Request_New>
          <PAR1>xyz</PAR1>
          <PAR2>123</PAR2>
       </Request_New>
    </Request>
    But the desired Request should go like below.
    <Request>
       <PAR1>xyz</PAR1>
       <PAR2>123</PAR2>
    </Request>
    Hence it gives an error saying that the tag Request_New does not exist.

    Dear All,
    Our target webservice cotains multiple methods.
    The every method contains its corresponding request, response and SQL ecxeption as messages.
    In case of request structures, every method (except crmPaymentReceived) contains more than 1 root element.
    So while calling those methods having more than 1 root element, the additional header tag will always appear(not avoidable) in the request coming from SAP PI.
    For Example,
    Request Structure for method u2018isLoginIdExistu2019 (having more than 1 root element)
    <?xml version="1.0" encoding="UTF-8"?>
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body>
    <ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing">      -
    >>>>>  u201CThis Header tag will always appear u201D
    <isLoginIdExistin0>asp</isLoginIdExistin0>
    <isLoginIdExistin1>1</isLoginIdExistin1>
    </ns1:isLoginIdExistRequest>
    </soap:Body>
    </soap:Envelope>
    For this method, we get the error(saying that ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing" does not exists).
    Request Structure for method u2018crmPaymentReceivedu2019 (having only 1 root element)
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=http://www.w3.org/2001/XMLSchema-instance xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soap:Body>
    <ns1:crmPaymentReceivedin0 xmlns:ns1="http://netpricing">false</ns1:crmPaymentReceivedin0>
    </soap:Body>
    </soap:Envelope>
    For this method, we get the success response.
    I tested their wsdl URL in XMLspy and wizdal(a wsdl testing tool), it shows request in the format having only root elements and not the header tags.
    But header tags will always appear when header tag contains more than 1 root element.
    Can anybody suggest me how do I tackle this?
    Thanks in Advance.

  • How to create a standard SOAP request message from a given WSDL file?

    Hello,
    If I have a WSDL file (either from a .net web service or from the famous Amazon web services), what is the best way to generate a SOAP compliant request message?
    I am having trouble understanding the role of WSDL file in a given web service.
    Question 1:
    If I have a web service that is implemented using jaxm, how do I create/publish a WSDL file that describes the web service?
    Assuming I can generate a wsdl file, can I recreate the SOAP request message from the WSDL file automatically (that matches the original request, which is hand build by me?)
    Question 2:
    If I have a web service that is implemented using JAX-RPC, based on the WSDL file, can I simply generate a valid SOAP message (by some JAVA api) and get the response message directly?
    thanks...

    I have the same question ("Assuming I can generate a wsdl file, can I recreate the SOAP request message from the WSDL file automatically (that matches the original request, which is hand build by me?)")
    Have you already found an answer to this?

  • Request Message Mapping Problem

    Hello friends,
    I am working in XI 2.0 and
    my senario is sap R/3->XI->File Adapter
    I take an idoc from the SAP R/3 system. and that comes properly to XI. I already created Data type, Message Type,
    Interface Type, Message Mapping and Interface Mapping in Desing. and all the configuration part.
    but when i send an idoc to XI system and check in SXMB_MONI at that time it shows me a green flag. means Inbound is Proper but It does not execute further steps.
    like Request Message Mapping, Call Adapter, Response.
    Can any one help me to solve this situation..
    Thanks in Advance.

    hi Shankar,
    I am able to solve the previous problem. by restarting my m/c.
    Now if any one know that how to configure RFC adapter.
    it always give me error like.
    <b>Attempt to start RFC adapter failed: com/sap/mw/jco/JCO$Record</b>
    And this is due to I am not able to connect to other R/3 system.
    In SM59 transaction
    <b>AI_RFCADAPTER_JCOSERVER</b> - TCP/IP connection
    when i register my program id to <b>Xmb2RfcService</b>
    then it gives me error when  i am testing my connection.
    <b>program Xmb2RfcService not registered / CPI-C error CM_ALLOCATE_FAILURE_RETRY</b>.
    so, can any one help me out to solve this problem.
    how to register Service in XI.
    Thanks,
    Gaurav Jain
    Message was edited by: Gaurav Jain

  • Wsdl validation fails for request message payload from custom schema

    Hello. I am having a problem which I cannot seem to work around. I have defined a schema to serve as a template for the request message payload of a bpel process. The schema is very simple:
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:logininfo="http://sru/logininfo" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sru="http://sru/profile" targetNamespace="http://sru/logininfo" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <xs:import namespace="http://sru/profile" schemaLocation="http://sru/profile.xsd"/>
         <xs:element name="logininfo" type="logininfo:logininfoType">
              <xs:annotation>
                   <xs:documentation>Needed information for SRU Login</xs:documentation>
              </xs:annotation>
         </xs:element>
         <xs:complexType name="logininfoType">
              <xs:all>
                   <xs:element name="email" type="sru:emailType"/>
                   <xs:element name="password">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="32"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="product" type="xs:string"/>
                   <xs:element name="ip" type="sru:ipType"/>
                   <xs:element name="timestamp" type="xs:dateTime"/>
                   <xs:element name="xpath" type="xs:string"/>
              </xs:all>
         </xs:complexType>
    </xs:schema>
    (The schema depends on another, which I have placed at the end of this message).
    I import it into the bpel process designer with no problems.
    Upon defining the payload of the request message type to be the {http://sru/logininfo}logininfoType, the WSDL file does not validate anymore:
    Validating WSDL...
    Validating E:\OraBPELPM_1\integration\jdev\jdev\mywork\SRU\BPELProcess5\BPELProcess5.wsdl
    Schema type not found: QName(http://sru/logininfo, logininfoType)
    Validate WSDL: has errors.
    Any ideas?
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns="http://sru/profile" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sru="http://sru" xmlns:xdb="http://xmlns.oracle.com/xdb" targetNamespace="http://sru/profile" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:schemaURL="http://sru/profile.xsd">
         <xs:annotation>
              <xs:documentation>Joel Salmerón Viver</xs:documentation>
              <xs:documentation xml:lang="en">General purpose internet profile schema</xs:documentation>
         </xs:annotation>
         <xs:simpleType name="emailType">
              <xs:restriction base="xs:string">
                   <xs:maxLength value="255"/>
                   <xs:pattern value="[a-z0-9]([a-z0-9\._][a-z0-9]+)*@[a-z0-9]([a-z0-9\.\-][a-z0-9]+)*\.[a-z]{2,6}"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="ipType">
              <xs:restriction base="xs:string">
                   <xs:pattern value="((\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])\.){3}(\d|[1-9]\d|1\d\d|2[0-4]\d|25[0-5])"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:simpleType name="labelType">
              <xs:restriction base="xs:string">
                   <xs:maxLength value="32"/>
              </xs:restriction>
         </xs:simpleType>
         <xs:complexType name="addressType" xdb:SQLType="ADDRESSTYPE" xdb:SQLSchema="SRU">
              <xs:all>
                   <xs:element name="lines" type="linesType" minOccurs="0" xdb:SQLName="lines" xdb:SQLType="LINESTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                        <xs:key name="linesKey">
                             <xs:selector xpath="line"/>
                             <xs:field xpath="@num"/>
                        </xs:key>
                   </xs:element>
                   <xs:element name="city" xdb:SQLName="city" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="64"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="postalcode" xdb:SQLName="postalcode" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="16"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="countrycode" xdb:SQLName="countrycode" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:length value="2"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
              </xs:all>
              <xs:attribute name="label" type="labelType" use="required" xdb:SQLName="label" xdb:SQLType="VARCHAR2"/>
              <xs:attribute name="verified" type="xs:boolean" use="required" xdb:SQLName="verified" xdb:SQLType="RAW"/>
         </xs:complexType>
         <xs:complexType name="lineType" xdb:SQLType="LINETYPE" xdb:SQLSchema="SRU">
              <xs:simpleContent>
                   <xs:extension base="xs:string">
                        <xs:attribute name="num" type="xs:positiveInteger" use="required" xdb:SQLName="num" xdb:SQLType="NUMBER"/>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="loginType" xdb:SQLType="LOGINTYPE" xdb:SQLSchema="SRU">
              <xs:all>
                   <xs:element name="registered_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="registered_date" xdb:SQLInline="true"/>
                   <xs:element name="lastlogin_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="lastlogin_date" xdb:SQLInline="true"/>
                   <xs:element name="lastlogin_ip" type="ipType" minOccurs="0" xdb:SQLName="lastlogin_ip" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
                   <xs:element name="lastlogin_time" type="xs:time" minOccurs="0" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="lastlogin_time" xdb:SQLInline="true"/>
              </xs:all>
              <xs:attribute name="product" use="required" xdb:SQLName="product" xdb:SQLType="VARCHAR2">
                   <xs:simpleType>
                        <xs:restriction base="xs:string">
                             <xs:maxLength value="32"/>
                        </xs:restriction>
                   </xs:simpleType>
              </xs:attribute>
              <xs:attribute name="status" type="xs:integer" use="required" xdb:SQLName="status" xdb:SQLType="NUMBER"/>
         </xs:complexType>
         <xs:complexType name="addressesType" xdb:SQLType="ADDRESSESTYPE" xdb:SQLSchema="SRU">
              <xs:sequence>
                   <xs:element name="address" maxOccurs="unbounded" xdb:defaultTable="PROFILE_ADDRESSES" xdb:SQLName="address" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:defaultTableSchema="SRU" xdb:SQLCollType="address360_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false">
                        <xs:complexType xdb:SQLType="address358_T" xdb:SQLSchema="SRU">
                             <xs:complexContent>
                                  <xs:extension base="addressType"/>
                             </xs:complexContent>
                        </xs:complexType>
                   </xs:element>
              </xs:sequence>
              <xs:attribute name="main" type="labelType" use="required" xdb:SQLName="main" xdb:SQLType="VARCHAR2"/>
         </xs:complexType>
         <xs:complexType name="phonesType" xdb:SQLType="PHONESTYPE" xdb:SQLSchema="SRU">
              <xs:sequence>
                   <xs:element name="phone" type="phoneType" maxOccurs="unbounded" xdb:SQLName="phone" xdb:SQLType="PHONETYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:SQLCollType="phone363_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false"/>
              </xs:sequence>
              <xs:attribute name="main" type="labelType" use="required" xdb:SQLName="main" xdb:SQLType="VARCHAR2"/>
         </xs:complexType>
         <xs:complexType name="loginsType" xdb:SQLType="LOGINSTYPE" xdb:SQLSchema="SRU">
              <xs:sequence>
                   <xs:element name="login" type="loginType" maxOccurs="unbounded" xdb:SQLName="login" xdb:SQLType="LOGINTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:SQLCollType="login366_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false">
                        <xs:key name="loginKey">
                             <xs:selector xpath="."/>
                             <xs:field xpath="@product"/>
                        </xs:key>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="phoneType" xdb:SQLType="PHONETYPE" xdb:SQLSchema="SRU">
              <xs:simpleContent>
                   <xs:extension base="phonenumberType"/>
              </xs:simpleContent>
         </xs:complexType>
         <xs:complexType name="profileType" xdb:SQLType="PROFILETYPE" xdb:SQLSchema="SRU">
              <xs:all>
                   <xs:element name="firstname" xdb:SQLName="firstname" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="64"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="surname1" xdb:SQLName="surname1" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="64"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="surname2" minOccurs="0" xdb:SQLName="surname2" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="64"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="gender">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:length value="1"/>
                                  <xs:enumeration value="M"/>
                                  <xs:enumeration value="F"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="alt_email" type="emailType" minOccurs="0" xdb:SQLName="alt_email" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
                   <xs:element name="addresses" type="addressesType" minOccurs="0" xdb:SQLName="addresses" xdb:SQLType="ADDRESSESTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                        <xs:key name="addressesKey">
                             <xs:selector xpath="address"/>
                             <xs:field xpath="@label"/>
                        </xs:key>
                        <xs:keyref name="addressRef" refer="addressesKey">
                             <xs:selector xpath="."/>
                             <xs:field xpath="@main"/>
                        </xs:keyref>
                   </xs:element>
                   <xs:element name="phones" type="phonesType" minOccurs="0" xdb:SQLName="phones" xdb:SQLType="PHONESTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                        <xs:key name="phoneKey">
                             <xs:selector xpath="phone"/>
                             <xs:field xpath="@label"/>
                        </xs:key>
                        <xs:keyref name="phoneRef" refer="phoneKey">
                             <xs:selector xpath="."/>
                             <xs:field xpath="@main"/>
                        </xs:keyref>
                   </xs:element>
                   <xs:element name="language" type="xs:language" xdb:SQLName="language" xdb:SQLType="VARCHAR2" xdb:SQLInline="true"/>
                   <xs:element name="logins" type="loginsType" minOccurs="0" xdb:SQLName="logins" xdb:SQLType="LOGINSTYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true">
                        <xs:key name="loginsKey">
                             <xs:selector xpath="login"/>
                             <xs:field xpath="@product"/>
                        </xs:key>
                   </xs:element>
                   <xs:element name="origin" minOccurs="0" xdb:SQLName="origin" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:annotation>
                             <xs:documentation>iso3166 a2 country code</xs:documentation>
                        </xs:annotation>
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:length value="2"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="creation_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="creation_date" xdb:SQLInline="true"/>
                   <xs:element name="modified_date" type="xs:dateTime" xdb:SQLType="TIMESTAMP WITH TIME ZONE" xdb:SQLName="modified_date" xdb:SQLInline="true"/>
                   <xs:element name="password" xdb:SQLName="password" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="32"/>
                                  <xs:pattern value="[a-zA-Z0-9]+"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="hint" minOccurs="0" xdb:SQLName="hint" xdb:SQLType="VARCHAR2" xdb:SQLInline="true">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:maxLength value="32"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="additional" type="xs:anyType" minOccurs="0">
                        <xs:annotation>
                             <xs:documentation>future expansion</xs:documentation>
                        </xs:annotation>
                   </xs:element>
              </xs:all>
              <xs:attribute name="email" type="emailType" use="required" xdb:SQLName="email" xdb:SQLType="VARCHAR2"/>
              <xs:attribute name="active" type="xs:boolean" use="required"/>
         </xs:complexType>
         <xs:complexType name="phonenumberType" xdb:SQLType="PHONENUMBERTYPE" xdb:SQLSchema="SRU">
              <xs:simpleContent>
                   <xs:extension base="xs:string">
                        <xs:attribute name="label" type="labelType" use="required" xdb:SQLName="label" xdb:SQLType="VARCHAR2"/>
                   </xs:extension>
              </xs:simpleContent>
         </xs:complexType>
         <xs:element name="profile" type="profileType" xdb:defaultTable="PROFILES" xdb:SQLName="profile" xdb:SQLType="PROFILETYPE" xdb:SQLSchema="SRU" xdb:defaultTableSchema="SRU"/>
         <xs:complexType name="linesType" xdb:SQLType="LINESTYPE" xdb:SQLSchema="SRU">
              <xs:sequence>
                   <xs:element name="line" type="lineType" maxOccurs="unbounded" xdb:SQLName="line" xdb:SQLType="LINETYPE" xdb:SQLSchema="SRU" xdb:SQLInline="true" xdb:SQLCollType="line354_COLL" xdb:SQLCollSchema="SRU" xdb:maintainOrder="false"/>
              </xs:sequence>
         </xs:complexType>
    </xs:schema>

    IT would help if the people that are working this issue would post the resolve of their problems. Every post I see with this problem someone from oracle replies with needing the source project to replicate the issue and the thread dies....

Maybe you are looking for