Error while triggering Synchrous outbound proxy

Hi,
While triggering synchronous outbound proxy from a abap program,it is throwing an system fault message. the system fault message is "Application Integration system error".
Please help me how to avoid this error.
My code is as below.
TRY.
    CALL METHOD proxy=>execute_synchronous
      EXPORTING
        output     = op_message
      IMPORTING
        input      = ip_message.
    CATCH cx_ai_system_fault into LO_SYS_EXCEPTION.
      CALL METHOD LO_SYS_EXCEPTION->IF_MESSAGE~GET_TEXT
        RECEIVING
          RESULT = TECHNICAL_EXCP_MESSAGE.
    CATCH cx_ai_application_fault .
ENDTRY.

Hi Ashwini,
Quite possible, there is something missing in the partner profile. There are several threads already in SCN with the same problem. Please refer below and see if it is helpful:
http://scn.sap.com/thread/319852
Entry in outbound table not found: Error Status... | SCN
Idoc Error Status "Entry in outbound table not found "
Regards,
Abhishek

Similar Messages

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

Error While connecting for ABAP Proxy

Hi All,
i am getting the connection error while creating the proxy connection from PI server to R3 System . I have checked the SLD configuration but did not find any wrong parameters there.
I am getting the below error.
"Error while reading ID of own business system from the SLD for system UDX and client 200", Also the software component of PI box is not getting reflected in SPROXY transaction of R3 system

Hi,
Do you see RFC created for /rep of desired PI system?This could be potential issue in your case:
Please check this:
In order to connect to an ESR, you have to maintain the RFC destination "SAP_PROXY_ESR". This RFC destination will then be used by proxy generation / Transaction SPROXY. It has to be set up using transaction SM59 and should look like this:
RFC Destination: SAP_PROXY_ESR
Connection Type: G (HTTP Connection to External Serv)
Description1: ESR for Proxy Generation
Target Host: esr_host
Service No: 1080
Path Prefix: /rep
Logon and Security:
Basic Authentication: active
User: esr_user
Password: esr_password
Regards,
Ashutosh

Getting Error While Triggered the Internal Service Request Process Accelerator

Hi
I installed Oracle Process Accelerators(Internal Service Request and Employee On Boarding) PS6 in windows7.Installation was successful and I checked the installpa.log file there its showing "Build Successful" and then we assign the roles in BPM workspace and also put the security relams in in enterprise manager as per installation Document provided by the Oracle after that everything was fine to test the Internal Service Request(ISR) I triggered few instances but they terminated abruptly and giving these Errors in EnterpriseManager(EM)
while triggered ISR Error message that was shown in EM is
Non Recoverable Business Fault :
<bpelFault><faultType>1</faultType><operationErroredFault xmlns="http://xmlns.oracle.com/bpel/workflow/taskService"><part name="payload"><operationErroredFault xmlns="http://xmlns.oracle.com/bpel/workflow/taskService"><faultInfo>ORABPEL-30082 WorkflowServiceEngine request to another component failed. Request operation CallFunctionStateless from default/InternalServiceRequest!1.0/ManagerApproveRequest to ManagerApproveRequestRules_ManagementChainRuleSet failed with Business Fault: null. Check the underlying fault. Check target SOA component for cause. </faultInfo></operationErroredFault></part></operationErroredFault></bpelFault>
Non Recoverable Business Fault :
Attempted to access property 'id' in class 'oracle.bpel.services.identity.hierarchy.HierarchyPrincipal' with a null object reference. at line 292 column 34 in /Ruleset(ManagerApproveRequestRulesBase)/Function(CreateSupervisoryList)/Action[11]
if anybody who did this ever and facing the same issue can you please let me know as early as possible
Thanks and Regards
Rajesh.

Hi Phani,
Are you able to reproduce issue as below:
1. Login to Application as sysadmin.
2. Navigate to Intergrated SOA Gateway > Integration Repository.
3. Click on search on right hand side of the page.
4. In the Internal Name type "FND_USER_PKG" and click Go.
5. Click on the User link.
6. Under the "Web Service - SOA Provider", click in the "View WSDL". Copy the complete URL "http://test:8003/webservices/SOAProvider/plsql/fnd_user_pkg/?wsdl"
7. Open the soapUI.
8. Click File > new soapUI Project.
9. Test the web service.
If yes,
I think you might be need to execute a patch:
solution:
To implement the solution, please execute the following steps:
1. Download and review the readme and pre-requisites for iAS Patch 18855074.
Note: Above Merge Label Request (MLR) is build for EBS 12.1.3 having OC4J 10.1.3.5.
2. Enable the profile option "EBS Adapter for BPEL, Function Security Enabled".
a. Login as SYSADMIN user and Navigate to System >Profile and Search for "EBS Adapter for BPEL, Function Security Enabled" (Internal name :EBS_ADAPTER_FUNCTION_SEC_ENABLED)
b. Set the Value to 'Y' at SITE level . This means function security feature is enabled and all API calls for PL/SQL APIs, Oracle e-Commerce Gateway, and concurrent programs will be checked for user security before they are invoked.
3. Retest the issue by Generating and Deploying the required package.
4. Migrate the solution as appropriate to other environments.
Thanks
Ranjan

Error while activating webservice-consumer-proxy

Hi,
I'm trying to generate a webservice-consumer-proxy from a Salesforce.com-WSDL-File. When trying to activate the proxy I receive an error-message from class CX_ESD_EXCEPTION stating "Beim Aktivieren des Proxys ist ein Fehler aufgetreten." (in english: "Error occured when activating the proxy"). The WSDL-File is SOAP-Version 1.1, Document/Literal.
Thank you very much in advance,
Olli
[SAP Consulting by mindsquare|http://mindsquare.de]

I have a similar issue and it says that the reason is one of the exception classes in XML in not derived from either cx_static_check or cx_dynamic_check.
Please let me know if anyone have ideas how to resolve this

Http500 error while triggering Gateway Service Get

Hi
I believe this is a known issue on the forums.. I get an HTTP500 error while posting a GET to a RFC Gen Gateway Service
?xml version="1.0" encoding="utf-8"?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code>/IWFND/CM_IFL/003</code><message xml:lang="en">GW Business Data Provider failed</message><innererror>GW Business Data Provider failed.</innererror></error><?xml version="1.0" encoding="utf-8"?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code>/IWFND/CM_IFL/003</code><message xml:lang="en">GW Business Data Provider failed</message><innererror>GW Business Data Provider failed.</innererror></error>
I have checked and found the Gateway Service is activated in ICF. Installation checks look ok including the BGRFC connections to/from backend.
Is there something we have overlooked? Any help is appreciated.
Regards
Sriram Vasudevan

Check the Gateway logs using transaction /IWFND/VIEW_LOG
If there's not enough detail in the logs, check the log configuration - SPRO in the SAP Reference IMG under SAP NetWeaver Gateway > Administration > Logging Settings
Paul

Error while creating a web proxy service using wsdl

Hi folks,
In my use case I should create a web service proxy using the wsdl. While I am creating the
web service proxy I am getting some error like the binding method does not have the SOAP extension.
I am giving the error below for more clarity
Caused by: oracle.j2ee.ws.common.tools.api.WsdlValidationException: input message of binding operation "createReference" does not have a SOAP body extensionCaused by: oracle.j2ee.ws.common.tools.api.WsdlValidationException: input message of binding operation "createReference" does not have a SOAP body extension
What could be the problem? Kindly help me on this.
Thanks,
Phani

Hi,
I guess wsdl URL for Data source is not working as expected
See
http://blogs.oracle.com/middleware/entry/calling_web_services_using_adf_11g
http://st-curriculum.oracle.com/obe/jdev/obe11jdev/ps1/webservices/ws.html

CALL_NOT_FLUSHED error while opening word document proxy

Hello Gurus,
We are using DMS application for uploading word documents in SAP system.
We are using the following code to open a document from SAP database
CALL METHOD CONTROL->GET_DOCUMENT_PROXY
EXPORTING
DOCUMENT_TYPE = '207'
DOCUMENT_FORMAT = ''
IMPORTING
DOCUMENT_PROXY = PROXY
RETCODE = RETCODE.
IF RETCODE NE C_OI_ERRORS=>RET_OK.
EXIT.
ENDIF.
CALL METHOD PROXY->OPEN_DOCUMENT
EXPORTING
DOCUMENT_URL = DOC_URL
OPEN_INPLACE = 'X'
open_readonly = 'X'
protect_document = 'X'
IMPORTING RETCODE = RETCODE.
IF RETCODE NE C_OI_ERRORS=>RET_OK.
EXIT.
ENDIF.
Above code open a document proxy and with help of macros we are changing some of the variables in the document.
Problem is when we are trying to print this proxy with help of below code.
CALL METHOD proxy->print_document
                  EXPORTING
                   NO_FLUSH    = ''
                    prompt_user = 'X'
                  IMPORTING
                    error       = error
                      retcode     = retcode .
In the above code if prompt_user parameter is passed then while execution a new window session is opened for printer selection but this methods gives an error as CONTROL_INTERNAL_ERROR. when i debugged it , it was giving error as CALL_NOT_FLUSHED.
But when we are commenting prompt_user as below
CALL METHOD proxy->print_document
                 EXPORTING
                   NO_FLUSH    = ''
                   prompt_user = 'X'
                  IMPORTING
                    error       = error
                      retcode     = retcode .
While execution printer selection window is open in the same window and nor error is passed by the method.
And print comes.
Kindly suggest how CALL_NOT_FLUSHED error can be eliminated.
Thanks in Advance
Sahadev Abhyankar

Just try with below before printing & opening the document. Refer to the examples SAPREDIT*
                 Call Method cl_gui_cfw=>Flush
                    Exceptions
                      Others = 0.

Error while calling secured OSB proxy from BPEL

Hi,
I have a OSB Proxy service to which I have applied OWSM Policy:
oracle/wss_username_token_service_policy
In the Setting:
Process WS-Security Header is set to Yes
While calling this Proxy from BPEL I tried to append binding properties, I tried the following options:
option1:
wsseHeaders=credentials
wssePassword=welcome1
wsseUsername=weblogic
option2:
oracle.webservices.auth.password=welcome1
oracle.webservices.auth.username=weblogic
But neither of them work and I get the following error:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-386200</con:errorCode>
<con:reason>General web service security error</con:reason>
<con:location>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
<Sep 21, 2010 9:49:30 AM PDT> <Error> <OSB Security> <BEA-387022> <An error ocur
red during web service security inbound request processing [error-code: Security
HeaderUnmarshallingError, message-id: 3659922647318344420--645cdd1d.12b2fe0c158.
-7e45, proxy: OSBTest/Proxy Services/PrivatePersonnelDB_PS, operation: null]
--- Error message:
oracle.wsm.security.SecurityException: WSM-00069 : The security header is missin
g.
at oracle.wsm.security.policy.scenario.processor.UsernameTokenProcessor.
verify(UsernameTokenProcessor.java:218)
at oracle.wsm.security.policy.scenario.executor.WssUsernameTokenScenario
Executor.receiveRequest(WssUsernameTokenScenarioExecutor.java:123)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor
.execute(SecurityScenarioExecutor.java:530)
at oracle.wsm.policyengine.impl.runtime.AssertionExecutor.execute(Assert
ionExecutor.java:41)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.executeS
impleAssertion(WSPolicyRuntimeExecutor.java:608)
Truncated. see log file for complete stacktrace
I have even tried to enable HTTP basic Authentication for the service, but did not work.
Any help is highly appreciated.
Thanks.

Hi,
I have applied oracle/wss_username_token_service_policy for my proxy service and trying to test that from OSB Test Console. I am getting below error,
"[OSB Security - OWSM:387253]Failed to initialize Owsm Credential Manager. Please validate the Keystore Configuration"
When i have launched Test Console for this proxy, i have observed in Security part, oracle/wss_username_token_client_policy is appearing. I am not sure why oracle/wss_username_token_client_policy is appearing there when i applied oracle/wss_username_token_service_policy to my proxy service.
Also do i have to need to configure any Keystore for oracle/wss_username_token_service_policy, If so please tell me the process.
If no key store is required where will the credentials be stored.
Thanks
Rajesh

Error while deploying Web Service Proxy

Hi guys
i have developed Deployable Proxy from WebService ans trying to deploy it on the server. When i deploy it through NWDI, it gives following error.
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/XXXX_proxy.ear.
20110526134643 Info   :                     Reason: None of the available containers recognized the components of application YYYY.com/XXXX_proxy; it is not possible to make deploy. Additional info:
20110526134643 Info   :                     The archive contains files normally handled by containers that are not currently operational on the server:
20110526134643 Info   :                     XXXX_proxy.wsar is normally handled by the following container(s) [webservices_container provided by webservices service]
20110526134643 Info   :                     Make sure the services that provide the required containers are deployed and started.
Please help me to resolve this issue.Thanks in Advance.
Deepak

Hi,
You can go to the Visual Administrator -> <SID> -> Server -> Services -> Deploy -> Runtime tab -> option Container at the bottom and see if everything is correct and running in the webservices_container.
If something necessary to the deployment is not started you can select it and click in start.
I hope it helps.
Thanks,
Anderson

Error while triggering program through output type while saving invoice

Hi,
I have a scenario where in my Z program needs to be triggered when saving a invoice.
For that we have attached out Z program to output type which gets picked while saving invoice.
In the Z program we have written the entire code in Form Entry subroutine.
In the Z program we have called a FM "SD_SALESDOCUMENT_CREATE", to create a sales order.
After sales order is created we have used a Commit statement.
If I run the Z program individually, Salesorder gets created perfectly.
How ever as per scenario when trying to save the invoice, output type gets picked. But program doesn't get called.
and when I go to the saved the invoice I get the following error immediately:
"Error document - Update was terminated"
I have found that the problem is with COMMIT statement through transaction SM13.
Can anybody help me with this. I cannot save the sales order without COMMIT, so I have to use it.
Thanks in Advance,
Rohan.

Hi Rohan,
I have worked on almost similar kind of requirement as you.
"Error document - Update was terminated" is because saving of invoice is done in u201CUpdate Tasku201D. Again in that work process, FM also calls for update task, which is not allowed and give short dump.
Here are two different approaches to cope up in this scenario.
1.Call FM in NEW TASK.
Calling Function module in new task will assign new work process and will use different update task.
Use:
CALL FUNCTION 'SD_SALESDOCUMENT_CREATE' STARTING NEW TASK 'task'
This will not give update termination error.
Call of FM in this way will work, but as this will be asynchronies call you will be not able to get status/message out of the FM call result.
If capturing return message is mandatory, use below approach
2, Process output type via Job
Set output type, dispatch time u201CSend with periodically scheduled jobu201D in u201CDefault valueu201D tab.
Run batch job for program u201CRSNAST00u201D with appropriate variant.
Please let me know if you need any further details.
Best Regards,
Nisarg

Getting error while testing a outbound file in oracle B2B11g

Hi,
I am trying to configuare a outbound scenario in oracle B2B 11g.
I have created .ecs file and .xsd file and created a document type also and i am using generic file 1.0 as a lintening channel protocol and trying to read the input xml document from a perticular path.
I had setup partner and agreement also. everything is working fine and also file is succesfully polling from the source folder but i am getting error in B2B as :
B2B-50083
Error Description Machine Info: (infva0325) Description: Document protocol identification error.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Document protocol identification error.
Can anyone guide me how to resolve this error?
I had tried everything but of no use.
Please do reply me with your suggestions.

Hi Anuj,
Please find below xml data which will be saved as .txt file for outbound processing. Let me know if there are any changes i have to do. Please let me know if you need any further information. Listening channel is reading the file but in agreement level it is failing.
<?xml version="1.0" encoding="UTF-8"?><Transaction-DESADV XDataVersion="1.0" Standard="EDIFACT" Version="D93A" CreatedBy="ECXEngine_837" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" CreatedDate="2011-12-14T12:59:40" GUID="{2d323135-3336-3630-3232-313938393033}" xmlns="urn:oracle:integration:b2b:099C29D4C4ED419194917C20ADF8ABC3">
<Internal-Properties>
<Data-Structure Name="Interchange">
<Property Name="InterchangeSenderID">senderID</Property>
<Property Name="InterchangeSenderQual">senderQuali</Property>
<Property Name="InterchangeReceiverID">RecieverID</Property>
<Property Name="InterchangeReceiverQual">RecieverQuali</Property>
<Property Name="RepeatingSeparator"/>
<Property Name="InterchangeApplicationRef">DESADV</Property>
<Data-Structure Name="Transaction">
<Property Name="TransactionID">DESADV</Property>
<Property Name="TransactionControllingAgency"/>
<Property Name="TransactionMessageVersionNumber">D</Property>
<Property Name="TransactionMessageReleaseNumber">93A</Property>
<Property Name="TransactionAssociationAssignedCode"/>
</Data-Structure>
</Data-Structure>
</Internal-Properties>
<Segment-UNH>
<Element-0062>#ControlNumber#</Element-0062>
<Composite-S009>
<Element-0065>DESADV</Element-0065>
<Element-0052>D</Element-0052>
<Element-0054>93A</Element-0054>
<Element-0051>UN</Element-0051>
<Element-0057>EDIT30</Element-0057>
</Composite-S009>
</Segment-UNH>
<Segment-BGM>
<Composite-C002>
<Element-1001>351</Element-1001>
</Composite-C002>
<Element-1004>3364382</Element-1004>
</Segment-BGM>
<Segment-DTM>
<Composite-C507>
<Element-2005>137</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
<Loop-Group_2>
<Segment-NAD>
<Element-3035>SH</Element-3035>
<Composite-C082>
<Element-3039>7393142020009</Element-3039>
<Element-1131 xsi:nil="true"/>
<Element-3055>9</Element-3055>
</Composite-C082>
</Segment-NAD>
</Loop-Group_2>
<Loop-Group_2>
<Segment-NAD>
<Element-3035>CN</Element-3035>
<Composite-C082>
<Element-3039>7350056030012</Element-3039>
<Element-1131 xsi:nil="true"/>
<Element-3055>9</Element-3055>
</Composite-C082>
</Segment-NAD>
</Loop-Group_2>
<Loop-Group_10>
<Segment-CPS>
<Element-7164>1</Element-7164>
</Segment-CPS>
<Loop-Group_15>
<Segment-LIN>
<Element-1082>1</Element-1082>
<Element-1229 xsi:nil="true"/>
</Segment-LIN>
<Segment-PIA>
<Element-4347>5</Element-4347>
<Composite-C212_1>
<Element-7140>210587</Element-7140>
<Element-7143>BP</Element-7143>
</Composite-C212_1>
</Segment-PIA>
<Segment-QTY>
<Composite-C186>
<Element-6063>12</Element-6063>
<Element-6060>3</Element-6060>
</Composite-C186>
</Segment-QTY>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>PK</Element-1153>
<Element-1154>1</Element-1154>
</Composite-C506>
</Segment-RFF>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>VN</Element-1153>
<Element-1154>6152310</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>171</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_23>
<Segment-QVA>
<Composite-C279>
<Element-6064>0</Element-6064>
<Element-6063_1>83</Element-6063_1>
</Composite-C279>
<Element-4221>CP</Element-4221>
</Segment-QVA>
</Loop-Group_23>
</Loop-Group_15>
<Loop-Group_15>
<Segment-LIN>
<Element-1082>2</Element-1082>
<Element-1229 xsi:nil="true"/>
</Segment-LIN>
<Segment-PIA>
<Element-4347>5</Element-4347>
<Composite-C212_1>
<Element-7140>210510</Element-7140>
<Element-7143>BP</Element-7143>
</Composite-C212_1>
</Segment-PIA>
<Segment-QTY>
<Composite-C186>
<Element-6063>12</Element-6063>
<Element-6060>3</Element-6060>
</Composite-C186>
</Segment-QTY>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>PK</Element-1153>
<Element-1154>1</Element-1154>
</Composite-C506>
</Segment-RFF>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>VN</Element-1153>
<Element-1154>6152310</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>171</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_23>
<Segment-QVA>
<Composite-C279>
<Element-6064>0</Element-6064>
<Element-6063_1>83</Element-6063_1>
</Composite-C279>
<Element-4221>CP</Element-4221>
</Segment-QVA>
</Loop-Group_23>
</Loop-Group_15>
<Loop-Group_15>
<Segment-LIN>
<Element-1082>3</Element-1082>
<Element-1229 xsi:nil="true"/>
</Segment-LIN>
<Segment-PIA>
<Element-4347>5</Element-4347>
<Composite-C212_1>
<Element-7140>081349</Element-7140>
<Element-7143>BP</Element-7143>
</Composite-C212_1>
</Segment-PIA>
<Segment-QTY>
<Composite-C186>
<Element-6063>12</Element-6063>
<Element-6060>1</Element-6060>
</Composite-C186>
</Segment-QTY>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>PK</Element-1153>
<Element-1154>2</Element-1154>
</Composite-C506>
</Segment-RFF>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>VN</Element-1153>
<Element-1154>6152310</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>171</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>NB</Element-1153>
<Element-1154>JF074</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>21E</Element-2005>
<Element-2380>20160905</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_23>
<Segment-QVA>
<Composite-C279>
<Element-6064>0</Element-6064>
<Element-6063_1>83</Element-6063_1>
</Composite-C279>
<Element-4221>CP</Element-4221>
</Segment-QVA>
</Loop-Group_23>
</Loop-Group_15>
<Loop-Group_15>
<Segment-LIN>
<Element-1082>4</Element-1082>
<Element-1229 xsi:nil="true"/>
</Segment-LIN>
<Segment-PIA>
<Element-4347>5</Element-4347>
<Composite-C212_1>
<Element-7140>051596</Element-7140>
<Element-7143>BP</Element-7143>
</Composite-C212_1>
</Segment-PIA>
<Segment-QTY>
<Composite-C186>
<Element-6063>12</Element-6063>
<Element-6060>1</Element-6060>
</Composite-C186>
</Segment-QTY>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>PK</Element-1153>
<Element-1154>2</Element-1154>
</Composite-C506>
</Segment-RFF>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>VN</Element-1153>
<Element-1154>6152310</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>171</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>NB</Element-1153>
<Element-1154>116812505</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>21E</Element-2005>
<Element-2380>20150131</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_23>
<Segment-QVA>
<Composite-C279>
<Element-6064>0</Element-6064>
<Element-6063_1>83</Element-6063_1>
</Composite-C279>
<Element-4221>CP</Element-4221>
</Segment-QVA>
</Loop-Group_23>
</Loop-Group_15>
</Loop-Group_10>
<Segment-CNT>
<Composite-C270>
<Element-6069>2</Element-6069>
<Element-6066>4</Element-6066>
</Composite-C270>
</Segment-CNT>
<Segment-UNT>
<Element-0074>#SegmentCount#</Element-0074>
<Element-0062>#ControlNumber#</Element-0062>
</Segment-UNT>
</Transaction-DESADV>

Error while creating a deployable proxy for a URL in NWDS

Hi ,
There is a requirement for calling a webservice in the .NET platform from JAVA using NWDS. The webservice of the server is pinged using the URL of the webservice. when the URL is passed in the WS navigator of CRD ( that is Development Server) , the response is retreived successfully . The version of NWDS is 7.0.23.
we are facing problem when we are trying to create a Deployable proxy in NWDS by using the following steps :
1) Create a Development Component
2) Select the Deployable Proxy
3) Create the Client Proxy Defintion of the created DC
At step 3 , when we giving the url or WSDL link like "http:// www3.authoring.syngenta/newswebservice.asmx?WSDL" (this is just for example) , it is showing as "Invalid wsdl or wsdl not found " . so that we are not able to procees further.
When we are trying to create proxy the for the WSDL link like " http:// www.authoring.syngenta/newswebservice.asmx?WSDL" , we are able to create successfully.
can anyone suggest why we are able to create the proxy for the URL "http:// www.authoring.syngenta/newswebservice.asmx?WSDL" and not for the other URL.
Any pointers or suggestions are very helpful.
Thanks and Regards,
Sreedevi

Late response I know, but I have solved a similar problem recently and thought I would share.
Firstly, the problem is not with the namespace. The "Namespace ..." part is just stating the namespace the "Incorrect Value" has. So this error is complaining about the value "Unknown" - which isn't very helpful.
It appears the SAP SE80 importer does not like elements like the following because it can't understand <s:element ref="s:schema" />. It appears this is a common thing to be included in .NET generated WSDLs.
<s:element minOccurs="0" maxOccurs="1" name="GetCursDynamicResult">      <s:complexType>          <s:sequence>               <s:element ref="s:schema" />               <s:any />          </s:sequence>     </s:complexType></s:element>
SAP will also not like this example as it does not support mixed content (see: http://www.w3schools.com/schema/schema_complex_mixed.asp)
<s:element minOccurs="0" maxOccurs="1" name="SaldoXMLResult">
     <s:complexType mixed="true">
          <s:sequence>
               <s:any />
          </s:sequence>
     </s:complexType>
</s:element>
You can "Fix" the problem in both cases by removing the offending text in a local copy of the WSDL file so remove line 4 in the first example and change line 2 in the second to <s:complexType> the proxy can then be generated. No idea if the resulting service will be fully operational though!

Error while creating a client proxy for CBR.RU

Hi!
I need to consume web service. Here is the link: http://www.cbr.ru/DailyInfoWebServ/DailyInfo.asmx?WSDL
I tried to make an own client proxy with SE80 transaction. (edit object->enterprise services -> client proxy -> create) After completing wizard an error occurs with text:
Incorrect value: Unknown Namespace http://www.w3.org/2001/XMLSchema
The same schema works perfecrly with this web service:
http://www.deeptraining.com/webservices/wsStrings.asmx?WSDL
In this case proxy class is created with no errors and everything is fine.
Could anybody let me know what's the reason of such bug, please? I'm not competent with XML schemas so it's kind of difficult to understand what's wrong with WSDL file from CBR.RU

Late response I know, but I have solved a similar problem recently and thought I would share.
Firstly, the problem is not with the namespace. The "Namespace ..." part is just stating the namespace the "Incorrect Value" has. So this error is complaining about the value "Unknown" - which isn't very helpful.
It appears the SAP SE80 importer does not like elements like the following because it can't understand <s:element ref="s:schema" />. It appears this is a common thing to be included in .NET generated WSDLs.
<s:element minOccurs="0" maxOccurs="1" name="GetCursDynamicResult">      <s:complexType>          <s:sequence>               <s:element ref="s:schema" />               <s:any />          </s:sequence>     </s:complexType></s:element>
SAP will also not like this example as it does not support mixed content (see: http://www.w3schools.com/schema/schema_complex_mixed.asp)
<s:element minOccurs="0" maxOccurs="1" name="SaldoXMLResult">
     <s:complexType mixed="true">
          <s:sequence>
               <s:any />
          </s:sequence>
     </s:complexType>
</s:element>
You can "Fix" the problem in both cases by removing the offending text in a local copy of the WSDL file so remove line 4 in the first example and change line 2 in the second to <s:complexType> the proxy can then be generated. No idea if the resulting service will be fully operational though!

Error while creating web services proxy in Jdev. 10.1.3

Hello,
I created a web service using jdev.10.1.2 and created successfully a ws proxy with the the same version.
However when I try to generate a ws proxy using 10.1.3, I am getting error:
The WSDL document is invalid for the following reason:
the wsdl contains a mixture of uses- "literal" and "encoded" Only literal OR encoded is supported in a wsdl, not both.
What is the problem and how can I resolve this?
Thanks in advance.

I followed like what is mentioned in the document, however my return type is still object.
Below is my message part. Pasted at the bottom is my complete wsdl.
<message name="getEmpInfoXML0Response">
<part name="result" type="xsd:anyType" />
</message>
****************************** WSDL**************************************
<?xml version="1.0" encoding="UTF-8" ?>
- 
- 
- <definitions name="Portalws" targetNamespace="http://ws/bs/ew/EmpInfo.wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ws/bs/ew/EmpInfo.wsdl" xmlns:ns1="http://ws.bs.ew/IPortalws.xsd">
- <types>
<schema targetNamespace="http://ws.bs.ew/IPortalws.xsd" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://www.w3.org/2001/XMLSchema" />
</types>
- <message name="getEmpInfoXML0Request">
<part name="empno" type="xsd:string" />
</message>
- <message name="getEmpInfoXML0Response">
<part name="result" type="xsd:anyType" />
</message>
- <portType name="EmpInfoPortType">
- <operation name="getEmpInfoXML">
<input name="getEmpInfoXML0Request" message="tns:getEmpInfoXML0Request" />
<output name="getEmpInfoXML0Response" message="tns:getEmpInfoXML0Response" />
</operation>
</portType>
- <binding name="EmpInfoBinding" type="tns:EmpInfoPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="getEmpInfoXML">
<soap:operation soapAction="" style="rpc" />
- <input name="getEmpInfoXML0Request">
<soap:body use="encoded" namespace="Portalws" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
- <output name="getEmpInfoXML0Response">
<soap:body use="encoded" namespace="Portalws" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
- <service name="Portalws">
- <port name="EmpInfoPort" binding="tns:EmpInfoBinding">
<soap:address location="http://host:portt/WebService-PortalWS-context-root/Portalws" />
</port>
</service>
</definitions>

Error while triggering Synchrous outbound proxy

Similar Messages

Maybe you are looking for