Oracle Web Services On Demand Troubleshooting Guide > Error Codes: Causes and Solutions >

SBL-EAI-04397


This error code has the error symbol: IDS_ERR_EAI_SA_NO_USERKEY.

Generic Error Message

No user key can be used for the Integration Component instance 'ObjectName' (SBL-EAI-04397).

Causes and Solutions

User keys are missing from the Web Service request.

Error Message

No user key can be used for the Integration Component instance 'Contact'.(SBL-EAI-04397).

Incorrect SOAP Request

The following incorrect SOAP request does not contain any user key fields, for example, <ContactEmail> is not a user key:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

   <soap:Header>

      <wsse:Security>

         <wsse:UsernameToken>

            <wsse:Username>%%%USERNAME%%%</wsse:Username>

            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">%%%PASSWORD%%%</wsse:Password>

         </wsse:UsernameToken>

      </wsse:Security>

   </soap:Header>

   <soap:Body>

      <ContactUpdate_Input xmlns="urn:crmondemand/ws/ecbs/contact/">

         <Echo>On</Echo>

         <LOVLanguageMode>LIC</LOVLanguageMode>

         <ListOfContact>

            <Contact>

               <ContactEmail>d@d.com</ContactEmail>

            </Contact>

         </ListOfContact>

      </ContactUpdate_Input>

   </soap:Body>

</soap:Envelope>

Resolving Error SBL-EAI-04397

You must incorporate user keys for each record in your Web Service request.

To resolve error SBL-EAI-04397

  1. Ensure each record in the request is identified by the user keys of the object type.
  2. Ensure that if the user key is made up of a combination of fields, then all of these fields must be specified in the request with values that exist in Oracle CRM On Demand to identify the unique record. For more information on user keys for each record type, see Oracle Web Services On Demand Guide.
Correcting the SOAP Request

To correct the SOAP request, add a user key, for example, <Id>, to identify which record to update:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

   <soap:Header>

      <wsse:Security>

         <wsse:UsernameToken>

            <wsse:Username>%%%USERNAME%%%</wsse:Username>

            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">%%%PASSWORD%%%</wsse:Password>

         </wsse:UsernameToken>

      </wsse:Security>

   </soap:Header>

   <soap:Body>

      <ContactUpdate_Input xmlns="urn:crmondemand/ws/ecbs/contact/">

         <Echo>On</Echo>

         <LOVLanguageMode>LIC</LOVLanguageMode>

         <ListOfContact>

            <Contact>

               <Id>ADSA-9MZ8OK</Id>

               <ContactEmail>d@d.com</ContactEmail>

            </Contact>

         </ListOfContact>

      </ContactUpdate_Input>

   </soap:Body>

</soap:Envelope>

Oracle Web Services On Demand Troubleshooting Guide Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.