Opportunity.wsdl

I have a requirement in which I need to create appointment in Oracle CRM on demand.
For that I need to first query Opportunity data but I am not able to find Opportunity.wsdl in Admin section of Oracle CRM Application. Not sure if this is a permission issue or there is any other way to query and update opportunity data.
Would be thankful if I could get any help on this.
-Best Regards,
Agraj Nema

Hi,
check if the record type was not renamed. If you renamed Opportunities to ,let's say, TEST, the WSDL will be for the TEST record type.
If this is not the case, check whether you have access to the Oppotunity record type.

Similar Messages

Issue with Opportunity schema contained in Opportunity.wsdl and Integration

There is Opportunity XML schema object defined for Siebel web-service with URI “urn:/crmondemand/xml/opportunity” in opportunity.wsdl and opportunity.xsd contained in integrationevent.zip. Please find attached the schema files.
If you check the diff, the opportunity schema is different, which is actually a conflict from Siebel side since it is the same object identified by URI “urn:/crmondemand/xml/opportunity”. Can we get some information about the discrepancy from Siebel OD team?
Following compiler error comes for the BPEL process, where both Opportunity wsdl and integration event being used:
Error:
[Error ORABPEL-10903]: failed to read wsdl
[Description]: in "bpel.xml", Global Type declaration/definition of name '{urn:/crmondemand/xml/opportunity}Opportunity' are duplicated at the following locations:
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.wsdl [line#: 89]
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.xsd [line#: 12]
There are at least two of them looking different:
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.wsdl [difference starting at line#:635]
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.xsd [difference starting at line#:558]
Global Type declaration/definition of name '{urn:/crmondemand/xml/opportunity}Team' are duplicated at the following locations:
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.wsdl [line#: 2602]
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.xsd [line#: 2524]
There are at least two of them looking different:
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.wsdl [difference starting at line#:2602]
file:/C:/Bhavnesh/Work/SiebelPoll/SourceCode/SiebelPoll/JDSU_SiebelToODSOpportunityTransfer/bpel/opportunity.xsd [difference starting at line#:2524]
[Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
Following is the difference between two schema:
New line in opportunity.wsdl
<xsd:element name="ListOfOpportunityContactRole" maxOccurs="1" minOccurs="0" type="xsdLocal1:ListOfOpportunityContactRole"></xsd:element>
Difference between the sequence of elements in both schema:
<xsd:complexType name="Team"><xsd:sequence><xsd:element name="OpportunityAccessId" maxOccurs="1" minOccurs="0" type="xsdLocal1:string30"></xsd:element>
<xsd:element name="OpportunityTeamId" maxOccurs="1" minOccurs="0" type="xsd:string"></xsd:element>
Thanks and regards,
Bhavnesh Patel.
Edited by: bhavnesh_p on Oct 9, 2008 1:24 PM

Hello Bhavnesh,
we just got into the same issue with the differing Opportunity-XSD/WSDL you have mentioned in your posting.
Following is the difference between two schema:
New line in opportunity.wsdl
<xsd:element name="ListOfOpportunityContactRole" maxOccurs="1" minOccurs="0" type="xsdLocal1:ListOfOpportunityContactRole"></xsd:element>
Difference between the sequence of elements in both schema:
<xsd:complexType name="Team"><xsd:sequence><xsd:element name="OpportunityAccessId" maxOccurs="1" minOccurs="0" type="xsdLocal1:string30"></xsd:element>
<xsd:element name="OpportunityTeamId" maxOccurs="1" minOccurs="0" type="xsd:string"></xsd:element>Did you get any update on this problem?
Thanks in adavance & Best regards..
Andre

[URGENT] Opportunity.wsdl - how to query the opportunity revenue?

Hi All,
I need to write a web services (opportunity.wsdl) to query the Item Revenue from the opportunity. How can be done? Refer the screenshot below,
The code as below,
Dim lstOfOppQuery As New ListOfOpportunityQuery
Dim lstOfProdRevQuery As New ListOfProductRevenueQuery
lstOfOppQuery.Opportunity = myOppQuery
lstOfProdRevQuery.ProductRevenue = myProdRevQuery
'Number of records to fetch
lstOfOppQuery.pagesize = "100"
lstOfProdRevQuery.pagesize = "100"
'Set OpportunityQueryPage_Input
Dim myOppInput As New OpportunityQueryPage_Input
'Dim myOppInput1 As New reven
myOppInput.ListOfOpportunity = lstOfOppQuery
'myOppInput.ListOfOpportunity = lstOfProdRevQuery
'Get the output
Dim myOutput As OpportunityQueryPage_Output
'Dim myOutput As
myOutput = accntPrxy.OpportunityQueryPage(myOppInput)
I able to query the opportunity data but failed to input and output the revenue, please help.
Please have a guide. Thanks :)
Edited by: 911468 on 09-Apr-2012 00:32

This is how I query opportunity & product revenue:
Opportunity prxySrvc = new Opportunity();
OpportunityQueryPage_Input objQryParam = new OpportunityQueryPage_Input();
OpportunityQueryPage_Output objQryOut = new OpportunityQueryPage_Output();
ListOfOpportunityQuery ListOfOpptyQuery = new ListOfOpportunityQuery();
OpportunityQuery myOpptyQuery = new OpportunityQuery();
ListOfProductRevenueQuery ListOfProdRevQuery = new ListOfProductRevenueQuery();
ProductRevenueQuery myProdRevQuery = new ProductRevenueQuery();
(query values to return)
myOpptyQuery.Id = query_field;
myProdRevQuery.Id = query_field;
ListOfProdRevQuery.ProductRevenue = myProdRevQuery;
myOpptyQuery.ListOfProductRevenue = ListOfProdRevQuery;
ListOfOpptyQuery.Opportunity = myOpptyQuery;
objQryParam.ListOfOpportunity = ListOfOpptyQuery;
prxySrvc.Url = mSession.GetURL();
objQryOut = prxySrvc.OpportunityQueryPage(objQryParam);
(output data)
objQryOut.ListOfOpportunity.Opportunity[index].Id
objQryOut.ListOfOpportunity.Opportunity[index].ListOfProductRevenue.ProductRevenue[childIndex].Id

Opportunity Product Revenue

Hello,
I can`t find a report called Opportunity Product Revenue, the near report is Opportunity Product.
My problem is when I go to second Step called Create Layout i can't see the item Accumulated Revenue related to Revenue?
Could someone help me?
Thanks

Hi Shilei G,
As product Revenue is pure child object you can find it under Opportunity WSDL document.
Its named as Product in WS 1.0 WSDLs of Opportunity
and ProductRevenue in WS 2.0 WSDLs of Opportunity
Regards,
Deepak H Andeli

Insert Opportunity - Product Revenue Child using WS2 - SBL-EAI-04316 error

Hello,
I´ve got the following error message trying to insert a product revenue child object to opportunity using WS2.
Fehler beim Übertragen der Daten ins CRM on Demand!
Tue Apr 26 08:06:21 CEST 2011 :: Fehler bei der Verarbeitung von Argument (Error while processing argument) urn:/crmondemand/xml/Opportunity/Data:ListOfOpportunity für Operation OpportunityInsert(SBL-EAI-04316) :: Error at thread 27334345
Using SOAPUI the insert are successful.
<soapenv:Body>
<ns:OpportunityInsert_Input>
<data:ListOfOpportunity lastpage="" recordcount="">
<data:Opportunity operation="">
          <data:ExternalSystemId>0010110107664043232</data:ExternalSystemId>
          <data:ListOfProductRevenue lastpage="" recordcount="">
<data:ProductRevenue operation="">
<data:Id></data:Id>
<data:CurrencyCode>EUR</data:CurrencyCode>
<data:StartCloseDate>00:00:00</data:StartCloseDate>
<data:OpportunityName>4043232</data:OpportunityName>
<data:AccountName></data:AccountName>
<data:stpvstums010>ÖLSERVICE ALL INKL. 5W-40</data:stpvstums010>
<data:PurchasePrice>4960</data:PurchasePrice>
<data:ProductName>Filter/Oel</data:ProductName>
<data:ProductPartNumber>09XXXX</data:ProductPartNumber>
<data:OpportunityExternalSystemId>0010110107664043232</data:OpportunityExternalSystemId>
<data:ipvzahlums002>100</data:ipvzahlums002>
<data:ipvzahlums001>1</data:ipvzahlums001>
          <data:ExternalSystemId>0010110107664043232001</data:ExternalSystemId>
<data:cpvwhrums002>0</data:cpvwhrums002>
<data:cpvwhrums003>4960</data:cpvwhrums003>
</data:ProductRevenue>
</data:ListOfProductRevenue>
</data:Opportunity>
</data:ListOfOpportunity>
<ns:Echo></ns:Echo>
</ns:OpportunityInsert_Input>
</soapenv:Body>
</soapenv:Envelope>
Trying to insert the child via webservice 2.0 the request fails (see error message above)
I'm running out of ideas because I'm using the same values with the webservice request.
thx in advance
kind regards
Klaus

Hello,
I've solved the problem. It seems to be that the axis framwork has some problems to handle the complex structure of the opportunity object respectively the containing array structures (Lists). We rebuild the webservice client after deleting the unnecessary elements from the opportunity wsdl file. Doing so the webservice client works as expected. Be careful to not delete required fields which are necessary for the response message, e.g.:
- ModifiedBy+
- ModifiedByID+
- ModifiedDate+
- CreatedBy+
- CreatedByID+
- CreatedDate+
- ModId+
- Id+
I`m sure that this cannot be the preferred way to solve the problem - but it works for me.
regards
Klaus

Cannot create opportunity lines for an opportunity using Web Services 2.0

When working with Web Services 2.0 API every object is exposed without any child objects, this means that if we want to query/update/create/delete child objects that child object has to be exposed via WSDL.
I searched for the opportunity lines child object (also known as revenue lines) in the available WSDL's in the application and also in the documentation and I can’t find it anywhere.
I also checked the opportunity WSDL and it does not contain any reference to the opportunity lines?
How do I create opportunity lines for an opportunity using the Web Services 2.0 API???

When working with Web Services 2.0 API every object is exposed without any child objects, this means that if we want to query/update/create/delete child objects that child object has to be exposed via WSDL.
I searched for the opportunity lines child object (also known as revenue lines) in the available WSDL's in the application and also in the documentation and I can’t find it anywhere.
I also checked the opportunity WSDL and it does not contain any reference to the opportunity lines?
How do I create opportunity lines for an opportunity using the Web Services 2.0 API???

How delete one product of a opportunity with WebService?

Hi
I know to insert a new product in a opportunity with webservice (with ListOfProducts of opportunity.wsdl) but, how i can delete one product of a opportunity?
Thanks,
Ivan

This is my code:
crm.oportunidad.Opportunity oportunidad = new crm.oportunidad.Opportunity();
OpportunityWS_OpportunityDeleteChild_Input qbe = new OpportunityWS_OpportunityDeleteChild_Input();
OpportunityWS_OpportunityDeleteChild_Output qRet;
qbe.ListOfOpportunity = new Opportunity1[1];
qbe.ListOfOpportunity[0] = new Opportunity1();
qbe.ListOfOpportunity[0].ListOfProduct = new crm.oportunidad.Product[1];
qbe.ListOfOpportunity[0].ListOfProduct[0] = new crm.oportunidad.Product();
qbe.ListOfOpportunity[0].ListOfProduct[0].ProductId = psProductoID;
oportunidad.Url = string.Format(surl, getInstancia(),sSessionID);
oportunidad.CookieContainer = GetCookieContainer();
qRet = oportunidad.OpportunityDeleteChild(qbe);
And this is the error:
No se puede utilizar una clave de usuario para la instancia de componente de integración 'Opportunity_Product'.(SBL-EAI-04397)
When i try to add products i have the same error code
Any idea?

How do you query activity data for accounts?

I need to extract account activity data. When I try to use the Activity WSDL it doesn't seem to provide any account information even though I do see fields like AccountId, AccountName. They are blank. Also it looks like there is way to do a activity query using the Account WSDL. Does anyone have an example of this?
We are using Release 18 with V2 WSDL.
Thank you,
Dan
Edited by: dansshin on Oct 14, 2010 2:33 PM

I'm not sure what you mean by XML string but I'm trying to extract to CSV file using this code. It provides activity data but looks like account information fields are blank.
Thank you,
Dan
private static void ExtractGrowerAccountActivity(String sessionID, String csvFileName)
try
// Download the opportunity wsdl from the Admin section of the CRM application
// Add web reference to the wsdl
// Create the instance of the account entity
Activity myAcctAct = new Activity();
myAcctAct.Url = ConfigurationManager.AppSettings["OnDemandURL"] + "/Services/Integration;jsessionid=" + sessionID;
// Set the query
// To find the record with account type as grower
Activity_WS.queryType myAcctName = new Activity_WS.queryType();
myAcctName.Value = "";
// Create query instance and set the appropriate parameters
Activity_WS.ActivityQuery myAcctActQuery = new Activity_WS.ActivityQuery();
myAcctActQuery.AccountId = new Activity_WS.queryType();
myAcctActQuery.AccountName = myAcctName;
myAcctActQuery.AccountExternalSystemId = new Activity_WS.queryType();
myAcctActQuery.Id = new Activity_WS.queryType();
myAcctActQuery.Activity = new Activity_WS.queryType();
myAcctActQuery.CreatedByFullName = new Activity_WS.queryType();
myAcctActQuery.CreatedDate = new Activity_WS.queryType();
myAcctActQuery.DueDate = new Activity_WS.queryType();
myAcctActQuery.Completed = new Activity_WS.queryType();
myAcctActQuery.CompletedDatetime = new Activity_WS.queryType();
myAcctActQuery.Subject = new Activity_WS.queryType();
myAcctActQuery.Type = new Activity_WS.queryType();
// Set ListOfAccountQuery
Activity_WS.ListOfActivityQuery lstOfAcctActQuery = new Activity_WS.ListOfActivityQuery();
lstOfAcctActQuery.Activity = myAcctActQuery;
// Number of records to fetch
lstOfAcctActQuery.pagesize = "100";
// set ActivityQueryPage_Input
ActivityQueryPage_Input myActInput = new ActivityQueryPage_Input();
myActInput.ListOfActivity = lstOfAcctActQuery;
// Get the output
ActivityQueryPage_Output myOutput = myAcctAct.ActivityQueryPage(myActInput);
// Get ListOfAccountData
Activity_WS.ListOfActivityData myAcctActData = myOutput.ListOfActivity;
Activity_WS.ActivityData[] acctActData = myAcctActData.Activity;
// Write to output file
if (acctActData.Length > 0)
using (var sw = new StreamWriter(csvFileName))
// Write header
sw.WriteLine("AccountID, AccountName, AccountType, ExternalID, ActivityID, ActivityType, CreatedBy, CreatedDate, DueDate, IsCompleted, CompletedDate, Subject, Type");
for (int i = 0; i < acctActData.Length; i++)
// Write detail
sw.WriteLine(string.Format("{0}, {1}, {2}, {3}, {4}, {5}, {6}, {7}, {8}, {9}, {10}, {11}, {12}",
acctActData.AccountId,
acctActData[i].AccountName,
"Account Type",
acctActData[i].AccountExternalSystemId,
acctActData[i].Id,
acctActData[i].Activity,
acctActData[i].CreatedByFullName,
acctActData[i].CreatedDate,
acctActData[i].DueDate,
acctActData[i].Completed == true ? "Y" : "N",
acctActData[i].CompletedDatetime,
acctActData[i].Subject,
acctActData[i].Type));
// Write to log
log.Message = string.Format("INFO: {0} Grower account activity record(s) extracted.", acctActData.Length);
log.Categories.Add(Category.General);
log.Priority = Priority.Normal;
writer.Write(log);
catch (Exception ex)
log.Message = string.Format("ERROR: " + ex.ToString());
log.Categories.Add(Category.Error);
log.Priority = Priority.High;
writer.Write(log);

Web Services 1.0 vs. 2.0

Is 2.0 recommended over 1.0? Or either one is preferrable? I am aware that you can only access child objects via 1.0 and each version has features that the other doesn't.

Well I would be have been if your assumption of 2.0 was preferred over 1.0 but unfortunately that not true entirely.
Though in most of the cases 2.0 is great it doesn't answer all of our basic reqt (at least till Release 17)
Well I don't really have a document for the differences but here are some of them I can think of
In 2.0
we can query both Parent and Children,
It provides us feature with querying OR on multiple fields which is not possible in 1.0 using SearchSpec feature
Gives us Sorting and Record Count features that helps us iterate through the records better unlike 1.0
But
Does not support Opportunity Team under Opportunity WSDL unlike 1.0 (haven't verified under Contact and Account Team)
Does not support ListOfBook under Account WSDL unlike 1.0 (haven't verified under Other Objects)
Creates trouble while generating Java Proxies using many Axis2 tools
Regards,
Deepak H Andeli

Php - Method cant Insert

Hi, I attempt to insert new data
but i method dont return any value...
this is my code
$crmdomain="https://secure-xxxxxxx.crmondemand.com";
function wslogin() {
global $crmdomain;
$url = $crmdomain."/Services/Integration?command=login";
$page = "/Services/Integration?command=login";
$headers = array(
"GET ".$page." HTTP/1.0",
"UserName: username",
"Password: password",
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL,$url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, FALSE);
curl_setopt($ch, CURLOPT_HEADER, true);
$data = curl_exec($ch);
if (!curl_errno($ch)) {
// Show me the result
$sessionid = substr($data,(strpos($data,"Set-Cookie:")+23),(strpos($data,";")-strpos($data,"Set-Cookie:")-23));
curl_close($ch);
return $sessionid;
else
return curl_error($ch);
$sessionid=wslogin();
$lead = array();
$lead = "John ";
$lead = "Smith";
$listOfLead = array('Lead' => $lead);
$leadWS = array('ListOfLead' => $listOfLead);
include_once 'lib/nusoap.php';
$Clase= new SoapClient("lead.wsdl" , true);
$Clase->setcookie("JSESSIONID", $sessionid);
// Error check
$err = $Clase->getError();
if ($err) {
// Show error
echo 'Error with soapclient creation' . $err . '</pre>';
// call won't work
$leadResult=$Clase->call('LeadInsert',array('LeadWS_LeadInsert_Input' => $leadWS));
print_r($leadResult);
Edited by: user10786927 on 19-ene-2009 6:38
Edited by: user10786927 on 19-ene-2009 6:47

If you check out [this other thread|http://forums.oracle.com/forums/thread.jspa?messageID=3417337#3474141] you'll see I posted a utility function that can be used to query, insert, and update any object you have a WSDL for.
Using that function this is how you create an Opportunity and then re-query for it.
$createOpportunity = array(
     "OpportunityWS_OpportunityInsert_Input" => array(
          "ListOfOpportunity" => array(
               "Opportunity" => array(
                    "OpportunityName" => htmlspecialchars("Some Company", ENT_NOQUOTES, "ISO-8859-1"),
                    "AccountId" => "1-ZX429",
                    "Probability" => "10",
                    "SalesStage" => "Lead",
                    "CloseDate" => date("m/d/Y", strtotime("+90 days")),
                    "OpportunityType" => "New Customer-Initial Sale"
$createOpportunityResult = sodCall('wsdl/opportunity.wsdl','OpportunityInsert',$createOpportunity);
$findOpportunity = array(
     "OpportunityWS_OpportunityQueryPage_Input" => array(
          "ListOfOpportunity" => array(
               "Opportunity" => array(
                    "OpportunityName" => "='Some Company'",
                    "AccountId" => "",
                    "Probability" => "",
                    "SalesStage" => "",
                    "CloseDate" => "",
                    "OpportunityType" => ""
$findOpportunityResult = sodCall('wsdl/opportunity.wsdl','OpportunityQueryPage',$findOpportunity);

Retrieve account privilege

Hello,
I would like to retrieve accounts privileges for the current external user
(and in option, for an internal user) when he is logged in.
How to do that in Idoc script ?
Thank you in advance

Hi AspnetDeveloper,
Thanks a lot for posting the exact steps.
I was actually using WebServices 2.0 and that is why these examples were not working for me. I have the webservice up and running now with 1.0
There is 1 more thing I need to ask.
I have 4 files that I am compiling in a single DLL (which becomes the Assembly in SQL Server)
1- File having Login/Logout code
2- SourceCodeFile that was generated by WSDL.exe for Accounts --<<<<<< this is has namespace ClrWebservices.Accounts
3- SourceCodeFile that was generated by WSDL.exe for Opportunities --<<<<<< this is has namespace ClrWebservices.Opportunity
4- File having my code that calls the QueryPage methods to get data and then INSERTs into SQL Server table.
As I read and tried that SQL Server doesn't support dynamically generated libraries, one has to do SGEN to generate serialization code. I did it and it was going perfect for only Accounts data. By the time I added code for retrieving opportunity data, the sgen.exe started giving error:
Error: The top XML element 'Opportunity' from namespace ' ' references distinct types ClrWebservices.Accounts.Opportunity and ClrWebservices.Opportunity.Opportunity1. Use XML attributes to specify another XML name or namespace for the element or types.
Even if I comment out all of my code that extracts Opportunity data, the error is same ..... but the error GOES AWAY if I don't compile the 3rd file in above list.
Looks to me as if there is some conflict between Opportunity as a separate entity and as a child of Account.
WSDL generated code for Accounts says:
[System.Xml.Serialization.XmlTypeAttribute(Namespace="urn:/crmondemand/xml/account")]
public partial class Opportunity {
WSDL generated code for Opportunity says:
[System.Xml.Serialization.XmlTypeAttribute(TypeName="Opportunity", Namespace="urn:/crmondemand/xml/opportunity")]
public partial class Opportunity1 {
Can anyone please pass on some pointers regarding the mistake I am making ...
Thanks in advance

Problem generating proxy class

hi,
i am using Axis to generate java proxy classes from wsdl as follow
D:\Axis>java -cp .;d:\axis\lib\wsdl4j-1.5.1.jar;d:\axis\lib\saaj.jar;d:\axis\lib
\jaxrpc.jar;d:\axis\lib\axis-ant.jar;d:\axis\lib\log4j-1.2.8.jar;d:\axis\lib\com
mons-discovery-0.2.jar;d:\axis\lib\commons-logging-1.0.4.jar;d:\axis\lib\axis.ja
r;d:\axis\lib\activation.jar;d:\axis\lib\mailapi.jar org.apache.axis.wsdl.WSDL2J
ava -N"urn:crmondemand/ws/ecbs/opportunity/10/2004"="crmondemand.ws.ecbs.opportu
nity.10.2004"
- Unable to find required classes (javax.activation.DataHandler and javax.mail.i
nternet.MimeMultipart). Attachment support is disabled.
Exception in thread "main" java.lang.NoClassDefFoundError: org/xml/sax/helpers/D
efaultHandler
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
no. of other such error
at org.apache.axis.wsdl.toJava.Emitter.<init>(Emitter.java:144)
at org.apache.axis.wsdl.WSDL2Java.createParser(WSDL2Java.java:209)
at org.apache.axis.wsdl.gen.WSDL2.<init>(WSDL2.java:96)
at org.apache.axis.wsdl.WSDL2Java.<init>(WSDL2Java.java:194)
at org.apache.axis.wsdl.WSDL2Java.main(WSDL2Java.java:371)
D:\Axis>-N"urn:/crmondemand/xml/Opportunity/Data"="crmondemand.xml.opportunity.D
ata"
The filename, directory name, or volume label syntax is incorrect.
D:\Axis>-N"urn:/crmondemand/xml/Opportunity/Query"=crmondemand.xml.opportunity.Q
uery Opportunity.wsdl
The filename, directory name, or volume label syntax is incorrect.
i have all the classes but still getting error...please help ....searching over net i found wsdl2java require url of web service... i downloaded wsdl file from CRM OD admin....

Hi, you need to add activation.jar and mail.jar to your project, classpath settings.
Regards
SL

How to query a custom picklist from Opportunity's revenue?

Hello,
I would like to query a custom picklist from Opportunity's revenue. I am using Picklist.wsdl:
myPort.getPicklistValues(myPicklist, Revenue, "");
With this operation I have the following message: denied acces. (SBL-ODS-50085).
I have tested with another entity and it works perfectlly:
myPort.getPicklistValues(myPicklist, Opportunity, "");
So, I think the problem is in the entity name, so can I access to Opportunity's revenue¿?
I am very confusing, because in Web Services documentation I have seen:
NOTE: The Revenue child object of Opportunity is actually called Product.
I have tested with:
myPort.getPicklistValues(myPicklist, Product, "");
But it isn't exists in this entity: SBL-SBL-00000
The role has access to do the query via Web Service, because it is the administrator and with it I can do any other operation via Web Service...
What I am doing wrong?
Thank you and regards.

I have found the answer:
Objects Supported with getPicklistValues operation:
GetPicklistValues is supported for all Web Services v1.0 and v2.0 accessible parent-level objects.
Revenue is a child object, so I can interact with this operation :(

WSDL, custom datatypes, fault element name issues

Hello all,
I am having a LOT of problems with BEAs webservices. I am posting
this here in the hope that someone can help me and tell me what I am
doing incorrectly. I am running
WebLogic Server 7.0 SP1 Mon Sep 9 22:46:58 PDT 2002 206753
WebLogic XMLX Module 7.0 SP1 Mon Sep 9 22:54:41 PDT 2002 206753
Background:
My goal is to make my company's product web services aware. I take an
EJB, try to run it through the standard ant tasks and generate a web
services accessible EJB. Sounds pretty easy, but complex types seem
to make this quite difficult.
I have been able to create a web service accessible EJB (only since
7.0.1), but I am quite unhappy with the quality of what I am able to
produce.
I have a datatype which acts as a key, but it does not follow the
javabeans idiom - i.e. it does not have a default constructor or
accessor methods and I am not in the position to change it. I have
created a codec for this class which works and an xml schema (both by
hand). Its name is AgentKey. I have also had to use the autotyper to
create codecs and typemapping entries for java.util.Properties,
I can connect using the WebLogic classes and I am now trying to
interact using MS Excel and Apache's Axis as my test clients.
Issues:
My first question deals with generating a client. There seem to be
two ways to generate a client. Firstly via the <client> subtask of
<servicegen><service>, the second way via <clientgen> task. Since I
am using a custom data type (AgentKey) I have to manually insert the
AgentKey schema into the web-services.xml file generated by
servicegen. When I try to generate a client via the
servicegen/service/client task there is no opportunity for me to
insert this datatype schema information and I therefore get the
following messages (lots of them, but I'm only including one):
[servicegen] WARNINIG: Unable to find a javaType for the xmlType:['java:net.agentis.apml.runtime']:AgentKey.
Make sure that you have registered this xml type in the type mapping
[servicegen] Using SOAPElement instead
BTW: I am also receiving the same problem with java.util.Properties.
BTW: WARNING is misspelt
If I attempt to generate a client class via the <clientgen> task, I
need to supply either a wsdl or ear file as a parameter. I cannot
supply a wsdl file because I haven't deployed the EAR yet (and I don't
want to until the EAR has the client classes in it), and I can't
supply the EAR because I want the ear to include the client classes.
It is a bit of a catch 22 situation. Is there a solution I can't see?
NOTE: it would be very, very nice if you added a schemaMapping
attribute to the <servicegen/service> task so the web-services.xml
file didn't have to be manually hacked. Something similar to the
typemapping attribute already in the servicegen/service task would do
it.
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?
Another problem with the WSDL (once you have cleansed the multiple
exception messages) is that the fault elements of the
binding/operation elements require names and they don't have any. For
example, this is straight from the deployed EJB WSDL file:
<binding name="ExampleAgentPortSoapBinding" type="tns:ExampleAgentPort">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="serviceWithPrimitiveDatatypes">
<soap:operation soapAction="" style="rpc"/>
<input>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
<fault>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</fault>
</operation>
<operation ...
The schema definition at http://schemas.xmlsoap.org/wsdl/ says the
fault element require a name attribute:
<complexType name =" tBindingOperationFault">
<complexContent>
<extension base="wsdl:tExtensibleDocumented">
<attribute name="name" type="NCName" use="required"/>
</extension>
</complexContent>
</complexType>
The name of the fault should be the same name as the fault in the
portType definition. In my example the name is "AgentisException" as
evidenced by this snippet:
<portType name="ExampleAgentPort">
<operation name="serviceWithPrimitiveDatatypes">
<input message="tns:serviceWithPrimitiveDatatypes"/>
<output message="tns:serviceWithPrimitiveDatatypesResponse"/>
<fault name="AgentisException" message="tns:AgentisException"/>
</operation>
Once these changes have been made then the WSDL will validate. Are
there plans to fix these bugs?
On a different note, when I try to interact with a method that uses a
custom data type, such as AgentKey, via the "WebLogic Webservice
standard testing home page" the custom data type without a default
constructor cannot be rendered correctly. For instance, the AgentKey
value is:

<agentKey/>
Since I can't deploy a valid WSDL, I can't get either Axis or Excel to
connect to my web services.
When I attempt to invoke Axis' (beta 1.1) wsdl2java I recieve the
following message.
java.io.IOException: ERROR: Fault is missing a name= attribute in operation
"serviceWithPrimitiveDatatypes", in binding {http://sillyurl.com/reallysilly}ExampleAgentPortSoapBinding.
This seems understandable considering the issues I mentioned earlier.
Unfortunately Excel doesn't really give me anything to go with. If I
type in the WSDL URI then it will give me a list of methods I can
invoke, but if I try to add the service I get the very unhelpful "The
Web Service References Tool could not generate the requested code.
Any changes that were made to your project have been rolled back."
Any help with those two issues would be greatly appreciated also.
One final issue is that I cannot seem to fix is taskdef'ing
<servicegen> properly from Ant. I can do the actual taskdef but then
it cannot find classes from within the weblogic.jar. If I run the
setExamplesEnv.cmd first the I don't need to do the taskdef and
everything works fine. Has anyone else had this issue? (we can't run
that command on our clients desktops before we build our build scripts
- anyway, I've put it down to one of those weird Ant classpath
issues.)
In summary:
Problems I can see and would like some help on are:
- multiple exception messages
- fault operations with no name
- the ability to generate client code with complex data types before
the EAR is deployed.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
I know this has been quite a long email, but it has been months in the
making. Anyone's time would be greatly appreciated.
Mark Mansour
Agentis Software
[email protected]

Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDL seems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late this quarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a look at this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people too.
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the exceptionmessages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty( "weblogic.webservice.servicenamechecking","false" );
This is not a client issue. The WSDL is generating incorrect WSDL. Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey" xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal" xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL it is redefined
every time a method has the AgentisException in its interface (which in my case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed in the upcomingrelease that will be
available for beta testing shortly. Contact [email protected] if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types before
the EAR is deployed.
There is an example to show how to do this: http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
Unfortunately this doesn't solve my problem. I still don't have an EAR or WSDL
file from which I can generate a client to be included in the final EAR file that
gets deployed to the server. My original post explains this a bit better.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50 and others
in this area.
This was more in reference to the building of the web services in the first place
rather than registering custom datatypes at runtime. The manual procedure is
documented at http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

Trying to change Opportunity SalesStage with WebServices Update

I have successfully updated a custom field in an opportunity, but when I try to update the SalesStage to "Closed/Won", I get the error: Cannot find entry ''Closed/Won'' in the bounded picklist for the field 'Sales Stage - Translation' in integration component 'Opportunity'(SBL-EAI-04401).
Closed/Won is a valid choice in the dropdown list, but I am wondering if I need to update with a value or object that is different that the display term.
Here is the C#/.Net code I use that references the opportunity.cs created from the WSDL for our schema.
WebServices.Opportunity.Opportunity webService = new WebServices.Opportunity.Opportunity();
// WebServices.Opportunity.Opportunity1 oppUpdate = queryOutput.ListOfOpportunity[0];
WebServices.Opportunity.OpportunityWS_OpportunityUpdate_Input updateInput = new WebServices.Opportunity.OpportunityWS_OpportunityUpdate_Input();
WebServices.Opportunity.Opportunity1 updateOpp = new WebServices.Opportunity.Opportunity1();
initializeStrings(updateOpp);
updateOpp.OpportunityId = opportunityID;
updateOpp.SalesStage = "Closed/Won";
updateInput.ListOfOpportunity = new WebServices.Opportunity.Opportunity1[] { updateOpp };
          WebServices.Opportunity.OpportunityWS_OpportunityUpdate_Output updateOutput = null;
          lock (requestLock) {
               prepRequest(webService);
               updateOutput = webService.OpportunityUpdate(updateInput);
               lastRequestEnd = DateTime.Now;
// I am not sure what comes back from this update query
          if (updateOutput != null && updateOutput.ListOfOpportunity != null && updateOutput.ListOfOpportunity.Length > 0)
               result = true;
I'd appreciate your help if you know what to do or have an example to share.

Thanks for your response.
We have 8 values of SalesStage defined. Stage1 through Stage 6 are custom stages added to the built-in Closed/Won and Closed Lost stages.
I think I see what you are saying is that if the SalesProcess and SalesProcessId are not set, the web service API does not know what picklist of SalesStage values to refer to. Is that right? I've changed my code to first read the opportunity and get the values in those 2 fields (SalesProcess and SalesProcessId), then set these values in the update record along with the SalesStage and run the update. I still get the same error that Closed/Won is not in the picklist for 'Sales Stage - Translation'. Is the 'Translation' an indication of the mapping to a sales process?
It appears that the SalesStageID also changes with each stage selected. Do I have to set that as well or will it be changed by the server when I change SalesStage? If so, I will have to do some debugging to find the values of the SalesStageID associated with each SalesStage.

Opportunity.wsdl

Similar Messages

Maybe you are looking for