Skip to Content
author's profile photo
Former Member

Problem calling SAP standard Bapi via Nco 2.0 with this specific customer.

Mar 10, 2005 at 05:09 AM | 8 Views

Hi there,

I am having problem when calling BAPI_PO_RELEASE from VB.NET via NCo 2.0 whereas i can successfully release a PO with the same user and with the same parameter input values via SAPGui's SE37

However, when i call BAPI_PO_GETITEMSREL from VB.NET via NCo 2.0 with the same user there is no problem, i can get the returns. and of course i can do it via SAPGui's SE37.

The error i get via NCo 2.0 when calling BAPI_PO_RELEASE is :-

'SAP.Connector.RfcSystemException' occured in sap.connector.rfc.dll

Additional Information: "Screen output without connection to user"

So, what does the error mean? why does the error only happen when calling BAPI_PO_RELEASE? Is there anyway i can work around this issues and call it via NCo 2.0 normally? Does it have anything to do with authorization or other security concerns? Because i can do it with other SAP customer also via NCo 2.0...

please advise. Thanks!

Regards,

Derek Tan

SAP NetWeaver
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • author's profile photo
    Reiner Hille-Doering
    Mar 10, 2005 at 09:05 AM

    I'm not sure, but the error message sounds as if the function tries to bring up some SAPGUI screen. Perhaps this is just an error popup for this special user. You could try to temporarily enable SAPGUI using the USE_SAPGUI connection string parameter ("SAPGui" property in Destination). If SAPGUI is installed and my guess is right, you would see the screen.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member
      Mar 10, 2005 at 10:21 AM

      Derek,

      What Reiner said is correct. Can you please check if your SAP system is up to date with patches. If I am not mistaken there are quite a number of OSS fixes for that particular BAPI and it should be included in the hot fixes. I remembered that it is also related to function calling up screens which will crash in NCo's case.

      Please check the OSS or with your Basis guy and revert.

      Cheers