Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Stiven Oliveira Bezerra
    Problem with Submit a requisition for approval (Rest...Answered
    Topic posted October 10, 2019 by Stiven Oliveira BezerraBlue Ribbon: 750+ Points, tagged Requisition Web Services 
    42 Views, 6 Comments
    Title:
    Problem with Submit a requisition for approval (Rest Service)
    Summary:
    REST Service
    Content:

    Hi, 

    I'm trying to do a Submit a requisition for approval but i don't understand the return error. 

    This is my Body:

    {
    "name":"submitRequisition",
    "parameters":[]
    }
     
    I need some parameters? 
     
    This is my Header: application/vnd.oracle.adf.action+json.
    Have other Header? When i use this Header he returns something like this:
    • The requisition contains projects-related attributes that aren't supported by the REST Service. (POR-2010837)
    • The requisition contains tax determinant attributes that aren't supported by the REST Service. (POR-2010835)
    • The requisition attribute SupplierContactId isn't supported by the REST Service. (POR-2010832)
    • The requisition contains descriptive flexfields that aren't supported by the REST Service. (POR-2010838)
    • This requisition can't be submitted using the REST service. (POR-2010830)
    Thanks.
     
     
    Version:
    https://docs.oracle.com/en/cloud/saas/procurement/19c/fapra/op-purchaserequisitions-requisitionheaderid-x-operations-0.html

    Best Comment

    Ashok

    Stiven

    The messages seem fairly self explanatory. I don't want to miss the purpose of your question. Could you clarify some details for me? Are you trying to submit a requisition that you created through the UI? Or are you submitting a requisition that you created using REST POST?

    Currently there is no support through REST for requisitions that contain DFFs, Project details etc. It appears that the requisition you are submitting contains these details and hence the errors. We don't have validations in place for these features and that is the reason the system is rejecting the REST SUBMIT.

     

    Comment

     

    • Ashok

      Stiven

      The messages seem fairly self explanatory. I don't want to miss the purpose of your question. Could you clarify some details for me? Are you trying to submit a requisition that you created through the UI? Or are you submitting a requisition that you created using REST POST?

      Currently there is no support through REST for requisitions that contain DFFs, Project details etc. It appears that the requisition you are submitting contains these details and hence the errors. We don't have validations in place for these features and that is the reason the system is rejecting the REST SUBMIT.

       

      • Stiven Oliveira Bezerra

        We created this requisition for SOAP and don't have project details there. We are trying use the Submit because the InitialApprove on SOAP didn't work.

    • Sumana Sarkar

      Due to current limited scope of REST services, we wouldn't recommend invoking REST SUBMIT operation on a requisition that was not created from REST POST.

      Instead you may want to investigate why the initiate approval did not work from SOAP services, what is the issue you are facing when submitting requisitions from SOAP?

      • Stiven Oliveira Bezerra

        I was calling the initiate approval in the wrong place it was within the payload scope, but it's in the header. Now works the submitting in REST and SOAP.

        Thanks.

    • Ashok

      Good to know. Can you explain for the benefit of others what you fixed (as in what exactly was not being done correctly before)?

      • Stiven Oliveira Bezerra

        Sure. 

        When you use SOAP and need use the Initiate Approval, you put the tag into the Header like this:

        <soapenv:Header/>
        <soapenv:Body>
        <typ:createRequisition>
        <typ:interfaceSourceCode>TEST</typ:interfaceSourceCode>
        <typ:requisitioningBUId>1234</typ:requisitioningBUId>
        <typ:groupBy>SUP</typ:groupBy>
        <typ:initiateApprovalAfterRequisitionImport>N</typ:initiateApprovalAfterRequisitionImport>
        <typ:errorProcessingLevel>ALL</typ:errorProcessingLevel>

        <typ:purchaseRequestPayload>

        ---Some Code

         

        My mistake was put the Initiate Approval into the Payload like this:

        <soapenv:Header/>
        <soapenv:Body>
        <typ:createRequisition>
        <typ:interfaceSourceCode>TEST</typ:interfaceSourceCode>
        <typ:requisitioningBUId>1234</typ:requisitioningBUId>
        <typ:groupBy>SUP</typ:groupBy>
        <typ:errorProcessingLevel>ALL</typ:errorProcessingLevel>

        <typ:purchaseRequestPayload>

        <typ:initiateApprovalAfterRequisitionImport>N</typ:initiateApprovalAfterRequisitionImport>

         

        Other Hint i can explain is, when you use the Initiate Approval the value you need to put is Y or N.