How to call Soap API plsql package with ws security ?

Question

Hi all,
I want to consume a webservice which comes with the basic authentication (username and password in soap header).
By calling Soap api through a anonymous block shows this error
"Error report:
ORA-20000: wsse:InvalidSecurity - Missing <wsse:Security> in SOAP Header
ORA-06512: at "APPS.SOAP_API", line 124
ORA-06512: at "APPS.SOAP_API", line 157
ORA-06512: at line 76
20000. 00000 -  "%s"
*Cause:    The stored procedure 'raise_application_error'
           was called which causes this error to be generated.
*Action:   Correct the problem as described in the error message or contact
           the application administrator or DBA for more information."
My Anonymous Block is:
set serveroutput on
declare
  l_request   soap_api.t_request;
  l_response  soap_api.t_response;
  l_return    VARCHAR2(32767);
  l_url          VARCHAR2(32767);
  l_namespace    VARCHAR2(32767);
  l_method       VARCHAR2(32767);
  l_soap_action  VARCHAR2(32767);
  l_result_name  VARCHAR2(32767);
  l_envelope       VARCHAR2(32767);
BEGIN
   l_url         := 'my wsdl url';                                 -- i provided the original URL in my actual code
  l_namespace   := 'xmlns="my namespace"';       -- same here
  l_method      := 'get_details';                              -- same here
  l_soap_action := 'my soap action';                        -- same here
  l_result_name := 'REQUEST_STAT';
  l_request := soap_api.new_request(p_method       => l_method,
                                    P_Namespace    => L_Namespace);
   soap_api.add_parameter(p_request => l_request,
                         p_name    => 'Username',
                         p_type    => '',
                         p_value   => 'user1');
  soap_api.add_parameter(p_request => l_request,
                         p_name    => 'Password',
                         P_Type    => '',
                         p_value   => 'passwd');
  soap_api.add_parameter(p_request => l_request,
                         p_name    => 'empid',
                         p_type    => '',
                         p_value   => '9989');
  soap_api.add_parameter(p_request => l_request,
                         p_name    => 'emp_TYPE',
                         P_Type    => '',
                         p_value   => 'COCD');
  soap_api.add_parameter(p_request => l_request,
                         p_name    => 'name',
                         P_Type    => '',
                         p_value   => 'Danny');
  soap_api.add_parameter(p_request => l_request,
                         p_name    => 'STATUS',
                         P_Type    => '',
                         p_value   => 'pending');
  soap_api.add_parameter(p_request => l_request,
                         p_name    => 'mgr_name',
                         P_Type    => '',
                         P_Value   => 'Auditore');
  soap_api.add_parameter(p_request => l_request,
                         p_name    => 'ADDRESS',
                         P_Type    => '',
                         p_value   => '13 new street');
  soap_api.add_parameter(p_request => l_request,
                         p_name    => 'PHONE',
                         P_Type    => '',
                         p_value   => '123456');
  l_Response := Soap_Api.Invoke(P_Request => l_Request,
                                P_Url     => l_Url,
                               P_Action  => L_Soap_Action);
  l_return := soap_api.get_return_value(p_response  => l_response,
                                        p_name      => l_result_name,
                                        P_Namespace => Null);
-- DBMS_OUTPUT.put_line(l_return );                                    
END;
I have Two questions :
1) Where to give the soap header details ?
2) In my soap header am also having the header atributes like "Responsiblity" ,"Resp Application" ,"Security Group" ,"Language" ,"Org ID"
Where to give these values in my anonymous block?
My Request.xml looks like this:
<soapenv:Header>
    <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
         <wsse:UsernameToken wsu:Id="UsernameToken-4" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
            <wsse:Username>user1</wsse:Username>
            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">passwd</wsse:Password>
         </wsse:UsernameToken>
      </wsse:Security>
      <sr:SOAHeader>
         <!--Optional:-->
         <sr:Responsibility>PURCHASING_SUPER_USER</sr:Responsibility>
         <!--Optional:-->
         <sr:RespApplication>PO</sr:RespApplication>
         <!--Optional:-->
         <sr:SecurityGroup>standard</sr:SecurityGroup>
         <!--Optional:-->
         <sr:NLSLanguage>american</sr:NLSLanguage>
         <!--Optional:-->
         <sr:Org_Id></sr:Org_Id>
      </sr:SOAHeader>
   </soapenv:Header>
   <soapenv:Body>
      <get:InputParameters>
         <!--Optional:-->
         <get:EMP_NUMBER>9969</get:EMP_NUMBER>
         <!--Optional:-->
         <get:EMP_TYPE></get:EMP_TYPE>
         <!--Optional:-->
         <get:name></get:name>
         <!--Optional:-->
         <get:STATUS></get:STATUS>
         <!--Optional:-->
         <get:MGR_NAME></get:MGR_NAME>
         <!--Optional:-->
         <get:ADDRESS></get:ADDRESS>
         <!--Optional:-->
         <get:PHONE></get:PHONE>
      </get:InputParameters>
   </soapenv:Body>
</soapenv:Envelope>

Answer 1

Hi Arik,
Thanks for the reply. I got the solution by configuring a NonXA data source. The problem was with internal commits of the fnd_global.initialize api.
If the DB adapter is calling aPL/SQL procedure (written inside a pakcage) using the data source configured to support XA, will expect not to have any commits in side the procedure or anywhere, the XA driver will take of the commits and whole transactions. By default the FND_GLOBAL.INITIALIZE(...) procedure will have the internal commits, so it was throwing the errors.
The solution was configuring the a NonXA Data source in the databae adapter configuration will allow the commits inside the callings procedures. So we created Two data sources one for XA and another for NonXA and we are using the NonXA datasource whereever we are calling the EBS APIs which have the internal commits.
-- Khaleel