Purchasing

Get Involved. Join the Conversation.

Topic

    Janak Mehta
    Difference in WSDL for PurchaseOrderServiceV2 between 2...
    Topic posted May 21, 2019 by Janak MehtaGreen Ribbon: 100+ Points, tagged Web Services 
    82 Views, 9 Comments
    Title:
    Difference in WSDL for PurchaseOrderServiceV2 between 2 environments
    Summary:
    Difference in WSDL for PurchaseOrderServiceV2 between 2 environments
    Content:

    Hi, We have 2 Oracle Cloud Fusion environments. We are using PurchaseOrderServiceV2 Webservice to create/edit POs.

    I see a small difference when I compare wsdl files for PurchaseOrderServiceV2 Websrvice from 2 environments we have.

    One of the environment have following 3 extra entries.

    <sp:Header Name="SignatureConfirmation" Namespace="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"/>
    <sp:Header Name="SignatureConfirmation" Namespace="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"/>
    <sp:Header Name="SignatureConfirmation" Namespace="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"/>
     
    Does anyone know what could be the reason ? 
     

    Comment

     

    • Swati Gupta
      1. Which release are both environments on?
      2. Please copy both the wsdl to the post
      3. Are these tags showing up in the request payload?
      • Janak Mehta

        Both instances are on following versions

        Oracle Cloud Application
        19A (11.13.19.01.0)
         
           
        Oracle Application Development Framework JDEVADF_11.1.1.9.2ADF-REL131901-PROD-BP_GENERIC_190227.0910.7241
         
        Oracle Middleware Extensions for Applications ATGPF_PT.REL13.19.01_GENERIC_190305.0524.REL13BP18.7A
        Database Compatibility TRUE (REL13BP18.7)

         

      • Janak Mehta

        Uploaded release info and wsdl file from both environment.

         

        • Swati Gupta

          Thanks. Checking with the internal team and update you as soon as possible

        • Swati Gupta

          The tags you are noticing difference with are added by security framework and should be seen or not seen for all the external webservices.
          It is not specific to PO Webservice.

          I would like to understand what is the problem caused by the tag that customer has found to be different in two PODs?

          • Janak Mehta

            Hi,

            The issue customer is facing they are not able to use the code that is build on Test POD and then point it to Dev1 POD due to WSDL difference.

            Thanks

            JAnak

          • Janak Mehta

            Hi,

            The issue customer is facing they are not able to use the code that is build on Test POD and then point it to Dev1 POD due to WSDL difference.

            Thanks

            JAnak