Skip to Content
avatar image
Former Member

PR to PO conversion error


I have created a service interface for PRtoPO conversion with 3 operations [Query, Read and Create(or Conversion) ]. In the Query operation I get a list of open PRs. In the Read operation I get the details of a single PR (like PR no, item no, material, quantity etc).

In the Create/Conversion operation I pass only the PR number so that a PO is created with the details from the PR which I pass.

We tested by executing the service interface in the SCL system and everything is working perfectly fine. In the SharePoint end we are able to do the Query and Read operations but not the conversion. The error message we are getting is- 'Value cannot be null. Parameter name: methodInstance"

Please let me know a solution for this.

PS: I have built a custom BAPI in the backend SAP system to create a PO using a PR. The BAPI requires only the PR number as input. I re-checked all the field attributes as well in the ESR. All the fields are made optional except the PR number.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jan 20, 2012 at 07:38 PM

    Hi Pranil,

    Can you please provide more information?

    - Did you create the ECT manually or through the BDC Browser?

    - Did you check the Create operation of the ECT? Are there any errors in the ECT?

    - How do you trigger the Create operation (via External List or via your custom custom coding)?

    - How did you model the Create operation in ESR? It looks like your RFC requires only the PR# to do the conversion, but BCS still needs you to keep the Input of Create the same as the Output of Read. Does your Create operation comply with this requirement?

    - In the error message parameter methodInstance is mentioned. Is any of your parameters in the Create or Read operation named methodInstance?

    Cheers, Alex

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Pranil,

      I hope the Microsoft experts in this forum can chime in here.

      In the meantime you might want to take a look at some of the pre-delivered content for samples on how the create operation has been build there. The pre-delivered ECTs for Contact or AccountDocuments have a create operation. Maybe you can spot a difference between the sample and your ECT.

      Cheers, Alex