A/P Documents on Service Call

Suggest that we have A/P Documents on Service calls. Very common for a service team to buy third party services on site to complete a job. These bills need to be connected to the service call other wise it very easy to lose track of expenses occurring on a visit.
Reza

Could be done with sdk but it will quite difficult.

Similar Messages

Linking expense document to service calls

Hello
Can anyone tell me if it is possible to link expense documents to service calls, after they are created in Sales A/R module or after an approval procedure?
I have found de following note (1052012) that says that is possible, but i can not see how.
Thanks in advance.
Miguel Machado

Hi Miguel,
I'm not entirely sure where this conversation is going and why you are querying tables.
From your original post you asked is it possible to link expenses that have already been added to the system, the simple answer is yes.
When you are creating a service call, go to the Expenses tab and click on the Expense Details button. From here click New Document. Select the type of document you want to add such as Sales Order. This automatically opens up the Sales Order form in Add mode, from here you can go in to Find mode (Cntrl & F), enter the Sales Order number that you want to add, when that is on the screen click OK. This will move that sales order number to the Service Call expenses screen where you can update.
Regards,
Adrian

Series Primary overlaps object Service Call

hI SAP gurus,
i am trying to create new series in Document Numbering for 'Service Call' , it doesn't allow me to create Series Numbering and following Error is showing ...
Series Primary overlaps object Service Call
Does any one know how should i create a new Series for Service Call..?
i appreciate your help.
Thanks and Regards,
kaviprashu

hi,
ok i will quote this for you
Symptom
It is a legal requirement in Brazil that service calls are numbered.
Solution
To facilitate the legal requirement that users can trace and manage service calls efficiently, it is now possible to assign service calls to sequential series numbering. All marketing document numbering rules (search, overlapping numbers, manual series, and etc.) are also applied on service calls. The following fields and objects are added:
In the Document Numbering - Setup window, the service calls object is added.
To access the Document Numbering - Setup window, choose Administration -> System Initialization -> Document Numbering.
In the Series - Service Calls - Setup window, the 'Primary' series is added.
For new and upgraded companies, the application automatically creates the 'Primary' series for service calls.
In the Numbering Series - Setup window, the 'Primary' series is added.
In the Service Call window, the No. fields (selection of series and number) are added.
To access the Service Call window, choose Service -> Service Call.
In the Relate Series to Document - Setup window, the service calls object is added.
For the service reports (Service Calls, Service Calls by Queue, Response Time by Assigned to, Average Closure Time, Service Monitor, My Service Calls, My Open Service Calls and My overdue Service Calls, Service Contract document - subtab Service Calls and Customer Equipment Card - subtab Service Calls):
Call No. (label text) is changed to Call ID.
The Document No. field represents the new call no. field.
Series column is added to service reports.
The Check Document Numbering - Selection Criteria window also includes checking of the service calls sequence.
To access the Check Document Numbering - Selection Criteria window, choose Administration -> Utilities -> Check Document Numbering.
For new created service calls, no record will be written to History Change Log when you add service calls (the same as the system behavior in the marketing documents).
Only after the actual update on an already added service call, a history record will be added.
There is no change in the already existing Call ID field, the behavior of this field stays the same.
Other terms
service calls, series, numbering, B1, sequential
Header Data
Released on     15.08.2011 15:48:33
Release status     Released for Customer
Component     SBO-SER-SCL Service Call
Priority     Recommendations/additional info
Category     Advance development
References
This document is referenced by:
SAP Business One Notes
1606253           Overview Note for SAP Business One 8.81 patch 07
Validity
Software Component
Version
SAP BUSINESS ONE
8.81
regards,
Fidel

Example for calling document type service using a XML

Hi,
Can anybody give me some pointers to any examples about Document type webservice
that is passed an XML document? The service expects a custom java object.
I am running WLS 7.0 with sp2.
This is what i have done so far:
I have created a document type web-service with the following signature
public CustomReturnObject provideService(customParameter) { }
The 'customParameter' is based on a "CustomParameter.xsd" and 'CustomReturnObject'
is based on its schema. I ran the "autotype" to generate the java classes for
the schema.
Now, we would like to invoke the service by passing an XML document instead of
calling it by creating instances of "CustomParameter" java class. Also we would
like to get the XML represented by "CustomReturnObject" in the client program
instead of the java object.
Can anybody help?
Thanks
Raghu

The latest version of WLS is 8.1.
I think the the "endpoint" needs to be string.
String endpoint =
http://RASUBR-2K:7001/SubscriptionServicesWS/SSApplicationService.jws;
Regards,
-manoj.
http://manojc.com
"Raghu Subramaniam" <[email protected]> wrote in message
news:[email protected]...
>
SAAJ did work!
But it is not working with the BEA client libraries (WLS 8.0 Beta). I amgetting
the following exception
exception ejava.lang.IllegalArgumentException: endpoint shou
ld be String or URL
java.lang.IllegalArgumentException: endpoint should be String or URL
atweblogic.webservice.core.soap.SOAPConnectionImpl.call(SOAPConnectionI
mpl.java:43)
at TestMain.main(TestMain.java:51)
Attached is my test file.
I used the libraries from Sun's web services kit and it works.
Is it a known problem? Any fixes?
Raghu
"manoj cheenath" <[email protected]> wrote:
SAAJ will work. You can also use DII client with
generic type mapping. Check this out:
http://manojc.com/tutorial/sample27/Main.java
Regards,
-manoj
http://manojc.com
"Raghu Subramaniam" <[email protected]> wrote in message
news:[email protected]...
But how did you call the web service. Did you use the stubs in yourclient
code?
We don't want to use the stubs generated from "clientgen". Rather wantto
call
the service by passing a XML string that adheres to our schema expectedby
our
service. Our service is document-style.
I am trying to use the SAAJ api to generate a SOAPMessage and callthe
service.
Anybody has tried this before. Does it work?
Raghu
"Mike DeAngelo" <[email protected]> wrote:
I just did this the first time a few weeks ago, but I had some
gotchas...
>>>>
First, run the autotype ant task against your xsd file to generateyour
value
objects (I think you already did this).
Second, write your java class or EJB to use the value objects asparameter/return
type. (I think you did this too.) If you are going to invoke anEJB,
create
the EJB-Jar file.
Third, use the servicegen ant task to create the an ear file. Theear
file will
contain both the ejb-jar and file webservice.war which is generatedby
weblogic.
Fourth, unbundle the ear file, then unbundle the war file. Edit the
file WEB-INF/web-service.xml
Add the contents of your original xsd under the <types> element (iftypes
doesn't
exist, it should be the first subelement under the root element).Add
the contents
of types.xml (generated by autotype) to the <type-mapping> element(It
should
be the second element under the root element.
Rebundle the war file, rebundle the ear file, and deploy it.
Here is a fragment of the ant stuff...
<taskdef name="servicegen"
classname="weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask"/>
<target name="check-servicegen" depends="stage">
<uptodate property="servicegen.notRequired"
targetfile="${stage}/my_webservice.ear"
srcfile="${stage}/my_ejb.jar">
</uptodate>
</target>
<target name="servicegen"
depends="check-servicegen"
unless="servicegen.notRequired">
<servicegen destEar="${stage}/my_webservice.ear"
warName="my_webservice.war">
<classpath refid="compile.classpath"/>
<service ejbJar="${stage}/my_ejb.jar"
targetNamespace="http://foo/bar/baz"
serviceName="process"
serviceURI="/process"
generateTypes="False"
expandMethods="True"
style="document">
</service>
</servicegen>
</target>
Mike
"Raghu Subramaniam" <[email protected]> wrote:
Hi,
Can anybody give me some pointers to any examples about Document
type
webservice
that is passed an XML document? The service expects a custom javaobject.
I am running WLS 7.0 with sp2.
This is what i have done so far:
I have created a document type web-service with the following
signature
>>>>>
public CustomReturnObject provideService(customParameter) { }
The 'customParameter' is based on a "CustomParameter.xsd" and'CustomReturnObject'
is based on its schema. I ran the "autotype" to generate the javaclasses
for
the schema.
Now, we would like to invoke the service by passing an XML documentinstead
of
calling it by creating instances of "CustomParameter" java class.
Also
we would
like to get the XML represented by "CustomReturnObject" in the client
program
instead of the java object.
Can anybody help?
Thanks
Raghu

781084 - Cannot add document which needs approval to a Service Call

Hi Experts,
Is there any update on this error per SAP Note 781084?
Symptom:
When linking a sales document, which needs to be approved via an
approval procedure, to a Service Call under the Expenses tab page, the
document will not be displayed in the Service Call window after its
approval.
Cause
Definition problem.
Solution
A DRQ number 3383528 was opened.
IM 2653636.
I am now using 8.82 version and the issue still exist. Any help would be greatly appreciated.
Thanks,
Don

You can add the document to the service call once it has been approved. For instance:
1) Create service call
2) go to Expense tab, create a new Sales Order
3) Sales Order goes to Approver (at this point, the sales order doesn't appear on the expense tab)
4) When the Sales Order has been approved and added to the system, go back to the Service Call > Expense Tab > > Expense Details > New Document > Order
5) At this point, the Sales Order window opens in Add Mode. Press Ctrl-F, and go to the Approved Sales Order. Click OK.
6) the Sales Order should appear on the expenses tab in the Service Call.
Hope this helps.
Reza

Expenses document problem in service calls

Hi,
In the service call document we have the expenses tab under which we can view all the documents (Inventory transfers,deliveries..etc) related to that call. Well now my problem is as follows...
I create a service call and later i add many expenses to it.. say i added 3 Inventory transfers and as long as the service call is OPEN I'm able to see the documents added in the Expenses tab when the Display all documents is checked.
Now when i close the service call the contents in the Expenses tab become inactive and I'm not able to view the expenses documents and the Display all documents check box is also disabled.
Hope I'm clear.
Thanks in advance,
Vasu Natari.

Hi Jeyakathan,
Thanks for ur quick reply, the details are as follows,
Q1. I'm logged in as manager and I have full authorization.
Q2. I'm using 2007 B PL SP:00 PL:10
Q3. Even after closing and reopening the service call if the status is Closed the expenses tab is inactive(I mean that the tab is active but all the matrix are inactive) and the Display all documents is also inactive.
Thanks,
Vasu Natari.
Edited by: vasu natari on May 15, 2009 10:31 AM

Link between Service Call and Marketing documents not working

Hello all,
I found a field in Marketing Documents - Rows data - that should be the link between a Service Call and the Marketing Documents.
The field is for example "INV1.isSrvCall" but, even if I create an Invoice from the Service Call, the field will be populated with the value "N".
Dows anyone knows how to make this field work? Or any workarround to make the connection between a Service Call and the generated documents?
Thanks in advance,
Kind Regards

The problem with SCL4 is that SAP updates it way too late in the process to be meaningful while in the module. You create a service order, then go into the expense document. That is when we need to know the service call id and the internalsn of the equipment being worked on Only when you get out of the service module do SAP post to SCL4.
The data (before writing to SCL$) exists as a veriable on the original service form. But can we access it from the expense document?
The question is how to access the data (service id) on the original service form from an expense document within the servide module. It is the service form, and that is currently not in focus, so I do not know if you can access it as a varaible, while in the expense document (sales order or invoice) that is in focus.
Can any one help with this/
David

Service Call documents can't be read from B1 DI SERVER

Dear All,
Service Call documents can't be read from B1 DI SERVER using B1WS (wsdl) for service calls (OSCL) which has column/ field "IsEntitled" = "C".
Based on REFDB.chm, SAP B1 Technical Documentation, field IsEntitled can only be filled by two values:
"C" = Valid contract exist
and
"N" = No
But ... in wsdl B1WS file, ServiceCallService.wsdl only allows "Y" and "N" values. The XML is as below:
     <s:element minOccurs="0" name="EntitledforService">
              <s:simpleType>
                <s:restriction base="s:string">
                  <s:enumeration value="tNO" />
                  <s:enumeration value="tYES" />
                </s:restriction>
              </s:simpleType>
            </s:element>
Consequently, Service Call which has IsEntitled value "N" CAN be read because tNO means "N" ("N" and "N" are equal). Coversely, "C" CAN NOT be read because tYES means "Y" ("C" and "Y" are not equal).
We looked at the DI Server log, the problem occurs when DI Server receives getByParam commands which retrieve service call with "C" value on its IsEntitled field. So, the problem happens when we read from the DI Server, not when we update the service call. (the error message is Invalid valid value 'C' in Enum 'BoYesNoEnum', the valid values are 'N', 'Y')
The log is as follow:
<?xml version='1.0' ?><S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">
<S:Header>
    <MsgHeader xmlns="http://www.sap.com/SBO/DIS" xmlns:ns2="ServiceCallsService">
      <SessionID>4FD32D48-47B0-4ECB-9E23-0DE4A5576CDE</SessionID>
      <ServiceName>ServiceCallsService</ServiceName>
    </MsgHeader>
</S:Header>
<S:Body>
    <ns2:GetByParams xmlns="http://www.sap.com/SBO/DIS" xmlns:ns2="ServiceCallsService">
      <ServiceCallParams>
        <ServiceCallID>52</ServiceCallID>
      </ServiceCallParams>
    </ns2:GetByParams>
</S:Body>
</S:Envelope>
08/07/2011 14:31:40 Response (Fault)
<?xml version="1.0"?><env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Body>
    <env:Fault>
      <env:Code>
        <env:Value>env:Sender</env:Value>
        <env:Subcode>
          <env:Value>-1013</env:Value>
        </env:Subcode>
      </env:Code>
      <env:Reason>
        <env:Text xml:lang="en">Invalid valid value 'C' in Enum 'BoYesNoEnum', the valid values are 'N', 'Y'</env:Text>
      </env:Reason>
      <env:Detail>
        <Service>ServiceCallsService</Service>
        <Command>GetByParams</Command>
        <SessionID>4FD32D48-47B0-4ECB-9E23-0DE4A5576CDE</SessionID>
      </env:Detail>
    </env:Fault>
</env:Body>
</env:Envelope>
Any solution?
Edited by: Alfa Ryano Yohanis on Jul 8, 2011 3:02 PM

Hi Alfa
I am experiencing the exact same issue as described above.
Did you solve it? And if so, how?
Thank You,
Marco Muller

How to make Service call document web enabled

A technician would be accessing Service call form through the web browser over the internet. He would be mentioning the CALLID and will be entering the user defined fields that are dispatch date, technician out date and time to name a few from the web browser through a web page, which should get populated into SAP Business One database. We are going for SAP Business One 2007B version with SQL server 2005 database. I went through the web tools web services and I could not find a web service related to service module. Can you please advise me how to go about with this scenario?

Hello,
Look at the thread on page two with the name: Join a service call and one serial number?
Hopefully this will help you further
Tim

Weblogic app server wsdl web service call with SSL Validation error = 16

Weblogic app server wsdl web service call with SSL Validation error = 16
I need to make wsdl web service call in my weblogic app server. The web service is provided by a 3rd party vendor. I keep getting error
Cannot complete the certificate chain: No trusted cert found
Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure
Validation error = 16
From the SSL debug log, I can see 3 verisign hierarchy certs are correctly loaded (see 3 lines in the log message starting with “adding as trusted cert”). But somehow after first handshake, I got error “Cannot complete the certificate chain: No trusted cert found”.
Here is how I load trustStore and keyStore in my java program:
     System.setProperty("javax.net.ssl.trustStore",”cacerts”);
     System.setProperty("javax.net.ssl.trustStorePassword", trustKeyPasswd);
     System.setProperty("javax.net.ssl.trustStoreType","JKS");
System.setProperty("javax.net.ssl.keyStoreType","JKS");
System.setProperty("javax.net.ssl.keyStore", keyStoreName);
     System.setProperty("javax.net.ssl.keyStorePassword",clientCertPwd);      System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump","true");
Here is how I create cacerts using verisign hierarchy certs (in this order)
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignClass3G5PCA3Root.txt -alias "Verisign Class3 G5P CA3 Root"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediatePrimary.txt -alias "Verisign C3 G5 Intermediate Primary"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediateSecondary.txt -alias "Verisign C3 G5 Intermediate Secondary"
Because my program is a weblogic app server, when I start the program, I have java command line options set as:
-Dweblogic.security.SSL.trustedCAKeyStore=SSLTrust.jks
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.SSL.enforceConstraints=strong
That SSLTrust.jks is the trust certificate from our web server which sits on a different box. In our config.xml file, we also refer to the SSLTrust.jks file when we bring up the weblogic app server.
In addition, we have working logic to use some other wsdl web services from the same vendor on the same SOAP server. In the working web service call flows, we use clientgen to create client stub, and use SSLContext and WLSSLAdapter to load trustStore and keyStore, and then bind the SSLContext and WLSSLAdapter objects to the webSerive client object and make the webservie call. For the new wsdl file, I am told to use wsimport to create client stub. In the client code created, I don’t see any way that I can bind SSLContext and WLSSLAdapter objects to the client object, so I have to load certs by settting system pramaters. Here I attached the the wsdl file.
I have read many articles. It seems as long as I can install the verisign certs correctly to web logic server, I should have fixed the problem. Now the questions are:
1.     Do I create “cacerts” the correct order with right keeltool options?
2.     Since command line option “-Dweblogic.security.SSL.trustedCAKeyStore” is used for web server jks certificate, will that cause any problem for me?
3.     Is it possible to use wsimport to generate client stub that I can bind SSLContext and WLSSLAdapter objects to it?
4.     Do I need to put the “cacerts” to some specific weblogic directory?
---------------------------------wsdl file
<wsdl:definitions name="TokenServices" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
     <wsp:Policy wsu:Id="TokenServices_policy">
          <wsp:ExactlyOne>
               <wsp:All>
                    <sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
                         <wsp:Policy>
                              <sp:TransportToken>
                                   <wsp:Policy>
                                        <sp:HttpsToken RequireClientCertificate="true"/>
                                   </wsp:Policy>
                              </sp:TransportToken>
                              <sp:AlgorithmSuite>
                                   <wsp:Policy>
                                        <sp:Basic256/>
                                   </wsp:Policy>
                              </sp:AlgorithmSuite>
                              <sp:Layout>
                                   <wsp:Policy>
                                        <sp:Strict/>
                                   </wsp:Policy>
                              </sp:Layout>
                         </wsp:Policy>
                    </sp:TransportBinding>
                    <wsaw:UsingAddressing/>
               </wsp:All>
          </wsp:ExactlyOne>
     </wsp:Policy>
     <wsdl:types>
          <xsd:schema targetNamespace="http://tempuri.org/Imports">
               <xsd:import schemaLocation="xsd0.xsd" namespace="http://tempuri.org/"/>
               <xsd:import schemaLocation="xsd1.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
          </xsd:schema>
     </wsdl:types>
     <wsdl:message name="ITokenServices_GetUserToken_InputMessage">
          <wsdl:part name="parameters" element="tns:GetUserToken"/>
     </wsdl:message>
     <wsdl:message name="ITokenServices_GetUserToken_OutputMessage">
          <wsdl:part name="parameters" element="tns:GetUserTokenResponse"/>
     </wsdl:message>
     <wsdl:message name="ITokenServices_GetSSOUserToken_InputMessage">
          <wsdl:part name="parameters" element="tns:GetSSOUserToken"/>
     </wsdl:message>
     <wsdl:message name="ITokenServices_GetSSOUserToken_OutputMessage">
          <wsdl:part name="parameters" element="tns:GetSSOUserTokenResponse"/>
     </wsdl:message>
     <wsdl:portType name="ITokenServices">
          <wsdl:operation name="GetUserToken">
               <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetUserToken" message="tns:ITokenServices_GetUserToken_InputMessage"/>
               <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetUserTokenResponse" message="tns:ITokenServices_GetUserToken_OutputMessage"/>
          </wsdl:operation>
          <wsdl:operation name="GetSSOUserToken">
               <wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserToken" message="tns:ITokenServices_GetSSOUserToken_InputMessage"/>
               <wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserTokenResponse" message="tns:ITokenServices_GetSSOUserToken_OutputMessage"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="TokenServices" type="tns:ITokenServices">
          <wsp:PolicyReference URI="#TokenServices_policy"/>
          <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="GetUserToken">
               <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetUserToken" style="document"/>
               <wsdl:input>
                    <soap12:body use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <soap12:body use="literal"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="GetSSOUserToken">
               <soap12:operation soapAction="http://tempuri.org/ITokenServices/GetSSOUserToken" style="document"/>
               <wsdl:input>
                    <soap12:body use="literal"/>
               </wsdl:input>
               <wsdl:output>
                    <soap12:body use="literal"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="TokenServices">
          <wsdl:port name="TokenServices" binding="tns:TokenServices">
               <soap12:address location="https://ws-eq.demo.i-deal.com/PhxEquity/TokenServices.svc"/>
               <wsa10:EndpointReference>
                    <wsa10:Address>https://ws-eq.demo.xxx.com/PhxEquity/TokenServices.svc</wsa10:Address>
               </wsa10:EndpointReference>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
----------------------------------application log
adding as trusted cert:
Subject: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x641be820ce020813f32d4d2d95d67e67
Valid from Sun Feb 07 19:00:00 EST 2010 until Fri Feb 07 18:59:59 EST 2020
adding as trusted cert:
Subject: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x3c9131cb1ff6d01b0e9ab8d044bf12be
Valid from Sun Jan 28 19:00:00 EST 1996 until Wed Aug 02 19:59:59 EDT 2028
adding as trusted cert:
Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x250ce8e030612e9f2b89f7054d7cf8fd
Valid from Tue Nov 07 19:00:00 EST 2006 until Sun Nov 07 18:59:59 EST 2021
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Cipher: SunPKCS11-Solaris version 1.6 for algorithm DESede/CBC/NoPadding>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Cipher for algorithm DESede>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSetup: loading trusted CA certificates>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 28395435>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
     at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
     at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
     at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at com.certicom.tls.record.WriteHandler.write(Unknown Source)
     at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
     at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
     at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
     at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
     at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
     at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
     at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
     at javax.xml.ws.Service.<init>(Service.java:56)
     at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
     at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
     at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
     at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
     at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 22803607>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 14640403>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - 12.29.210.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
     at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
     at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
     at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
     at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
     at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
     at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
     at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
     at com.certicom.tls.record.WriteHandler.write(Unknown Source)
     at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
     at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
     at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
     at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
     at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
     at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
     at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
     at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
     at javax.xml.ws.Service.<init>(Service.java:56)
     at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
     at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
     at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
     at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
     at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 16189141>

I received a workaround by an internal message.
The how to guide is :
-Download the wsdl file (with bindings, not the one from ESR)
-Correct it in order that the schema corresponds to the answer (remove minOccurs or other things like this)
-Deploy the wsdl file on you a server (java web project for exemple). you can deploy on your local
-Create a new logicial destination that point to the wsdl file modified
-Change the metadata destination in your web dynpro project for the corresponding model and keep the execution desitnation as before.
Then the received data is check by the metadata logical destination but the data is retrieved from the correct server.

How can I associate an A/P invoice to a service call?

Hi,
Customer wants this:
1. They (Co. A) gets a service call from their customer say for lump sum of 400 dollars.
2. They (Co. A) give out a contract to technician say at 45 dollars an hours and travel expenses. This is SERVICE ITEM for a total expense of say 45*2+120=210.
3. Technician (A Vendor BP in SAP Business one) produces a PO. Co. A pays off the Technician.
How can I create a Service Call to show both ends of incoming revenue and outgoing expense in the service call?
Appreciate your help.
Thank you.

Dear Syed Aleem,
I have described some ideas, but if these ideas do not help you, please come back to us with more details of what you need.
1. They (Co. A) gets a service call from their customer say for lump sum of 400 dollars.
Here you can create the servce call with the information in the General Tab and in the Remark and in the subject. If this is not enough I would suggest to create an activity and write your remark and content in the activity.
You can create an activity clicking on the Activity tab. In the activity there is a tab called linked documents and you can add documents linked to the activity and service call.
2. They (Co. A) give out a contract to technician say at 45 dollars an hours and travel expenses. This is SERVICE ITEM for a total expense of say 45*2+120=210.
You can use anothe activity or you can add Return from Technician under the Expenses tab of the Service call.
3. Technician (A Vendor BP in SAP Business one) produces a PO. Co. A pays off the Technician.
Now, create another activity (or your first one) and add the Purchase order and the payment to it.
Please, let me know if my suggestions help you.
Regards,
Marcella Rivi
SAP Business One Forums Team

How can I use web service call for edit a report with SSRS in Java Struts2 web application

Hello im new in SSRS technologie and I would like make web service call at my SSRS server. Is sombody can help me ?
- What API should I import in my project ? I use Maven can I found this API on Maven repository ?
- I would like have an sample of code which initialize the ReportingService, do the call and process result.
We use the SQL Server ReportingService 2008 R2 and currently we made HTTP call like this : http://<ssr_server>/ReportServer/Pages/ReportViewer.aspx?%2fSSRS_OMB%2fMyReport&rs:Command=Render&MyParam=<value>
Regards

Hi ombinte,
SQL Server Reporting Services provides access to the full functionality of the report server through the Report Server Web service. Because the Report Server Web service is an XML Web service which uses Simple Object Access Protocol (SOAP) over Hypertext Transfer
Protocol (HTTP), any SOAP-aware application or development tool can communicate with the SSRS web service.
There are three primary ways to develop Reporting Services applications based on the Web service, please see:
Develop applications using Microsoft Visual Studio and the Microsoft .NET Framework SDK.
Develop applications using the rs utility (RS.exe), the Reporting Services script environment.
Develop applications using any SOAP-enabled set of development tools.
For more information about Report Server Web Service, you can refer to the following document:
http://technet.microsoft.com/en-us/library/ms152787.aspx
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call

Hi experts,
I just installed and configured ADS in NW04-Java SP20 and tested the URL http://host:portal/AdobeDocumentServices/Config. it shows the version information in the response.
When I try to run the Java-Webdynpro interactive form I am getting below messages. I also tried SDN sample project, I got the same message.
I installed ACF for NW04, it shows in the control panel, but not in the IE add-ons list.
Error Message:
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:282)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:224)
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:282)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:224)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
Could you please tell me is any thing missing???
Thanks in advance,
Ramana.

Hi Ramana,
If you are on NW '04 SP11 or lower, try upgrading to a later version. SP 12 (and higher) contains a newer version of Adobe document services that renders much faster.
By default the Web service client socket timeout is set to 60. Try changing this parameter in the Visual Administrator: Server -> Services -> Web Services Container on the Settings tab.
In online scenarios with large context performance issues are seen. It may make more sense to create smaller PDFs with a stricter data selection.
Also refer to this note:
[Note 811342 - Time Out exception when rendering to Adobe document service|https://websmp230.sap-ag.de/sap/support/notes/811342]
Hope this helps!!
Cheers,
Arafat

Need Information regarding Service Call creation in SAP R/3

Hello,
I need the Transaction code or BAPI to create a service call in sap. Please provide the database table name for the service calls.
We want to develop service call management in our server.So please send me the Business data model for service call management in SAP.(All related objects to the service call and their data models.)
Regards,
Kiran.

Hi
Invoice list is basically SD configuration.
<b>Invoice List</b>
<b>Purpose</b>
The invoice list lets you create, at specified time intervals or on specific dates, a list of billing documents (invoices, credit and debit memos) to send to a particular payer.
The billing documents in the invoice list can be single or collective documents (collective invoices combine items from more than one delivery).
The standard version of the SAP R/3 System includes two types of invoice lists:
1.for invoices and debit memos
2.for credit memos
If you wish, you can process invoices, debit memos, and credit memos at the same time. The system automatically creates a separate invoice list for credit memos.
A payer may be the head office of a buying group, which pays all the invoices for goods that are shipped to individual members. The group payer takes responsibility for paying the invoice lists and then collecting payment from the individual members. In return for these services, the group payer usually earns a factoring or del credere discount.
Depending on the tax structure of the payer's country, the payer may be liable to pay taxes on factoring discounts that he earns. In Germany, for example, factoring discounts are taxed at the standard rate of 15%. During invoice list processing, you can reimburse the payer in advance for this tax liability by creating special condition records
Regards
Ramakrishna

OSB11g - Business Services - Calling WS throwing reader() error.

I have an OSB11g Proxy and business services.
my requirement is to get a WS SOAP request from a BPEL application on to my Proxy services. this proxy service will identify the URI to invoke and make a call on to BES via this business service with the exactly same request which i received in Proxy.
I m getting the request xml as
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ " xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/ " xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance " xmlns:xsd="http://www.w3.org/2001/XMLSchema ">
<SOAP-ENV:Body>
<RootTAG>
<Name>Galvin</Name>
<Age>12</Age>
</RootTAG>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I have chosen service call-out to make a call to BS.
Option 1 In service call-out i have chosen request with SOAP body.
XML which is sent to BS is looking as below.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ ">
     <soapenv:Header/>
     <soapenv:Body>
          <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ " xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/ " xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance " xmlns:xsd="http://www.w3.org/2001/XMLSchema ">
               <SOAP-ENV:Body>
                    <RootTAG>
<Name>Galvin</Name>
<Age>12</Age>
                    </RootTAG>
               </SOAP-ENV:Body>
          </SOAP-ENV:Envelope>
     </soapenv:Body>
</soapenv:Envelope>
Option 2 In service call-out i have chosen request with document.
XML which is sent to BS is looking as below.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ ">
<soapenv:Header/>
<soapenv:Body>
<soapenv:Body>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ " xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/ " xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance " xmlns:xsd="http://www.w3.org/2001/XMLSchema ">
<SOAP-ENV:Body>
<RootTAG>
<Name>Galvin</Name>
<Age>12</Age>
</RootTAG>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
</soapenv:Body>
</soapenv:Body>
</soapenv:Envelope>
For both the request i am getting error as below .
java.lang.IllegalStateException: getReader() called after getInputStream()
But when i test the BS using WS tools (netTool) with the same request XML (which i receive in Proxy), i am getting proper response.
> I have no clue where is the problem actually in my OSB application. Do i miss some header or some additional thing i need to do before setting in request xml in service call-out.
> Also Webservice which BS invokes runs on a weblogic 8.1 application server. Will that be a problem?
Thanks
Sesha
Edited by: 784261 on Jul 25, 2010 4:03 AM

Anuj
I found one discrepency in the call made from OSB and netTool(WS testing tool)
The content length in the request to WS stub from OSB is - "content length =-1" . kindly help how to set the content length in the request.?
when BES call is made from OSB
####<Jul 26, 2010 1:22:49 PM BST> <Info> <******STUB********> <hwwhapp4> <> <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'>
<<anonymous>> <> <000000> *<Entered get operation, content length =-1,content typetext/xml; charset=utf-8>*
####<Jul 26, 2010 1:22:49 PM BST> <Error> <HTTP> <> <managed1_hlluwli1> <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <>
<BEA-101020> <[ServletContext(id=6879348,name=getWebServiceXML,context-path=/getWebServiceXML)] Servlet failed with Exception
java.lang.IllegalStateException: getReader() called after getInputStream() called
at weblogic.servlet.internal.ServletRequestImpl.getReader(ServletRequestImpl.java:1831)
at Startservlet.doPost(Startservlet.java:78)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1077)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7047)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3902)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2773)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
>
when BES call is invoked from netTool
####<Jul 26, 2010 1:55:12 PM BST> <Info> <******STUB********> <hwwhapp4> <> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'>
<<anonymous>> <> <000000> <Servlet Started>
####<Jul 26, 2010 1:55:12 PM BST> <Info> <******STUB********> <hwwhapp4> <> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'>
<<anonymous>> <> <000000> *<Entered get operation, content length =737,content typenull>*
Thanks
Sesha

A/P Documents on Service Call

Similar Messages

Maybe you are looking for