Skip to Content

Enterprise Services and Proxy

A SAP Enterprise Service and a SAP PO ABAP Proxy are different things aren't they ?

Is this true below >?

  • SAP PO ABAP Proxy created in the SAP PO ESR and then generated via SAP ERP SPROXY transaction
  • a SAP Enterprise Service is SAP provided content that is on the SAP ERP server and accessed via SOAMANAGER transaction. And so SAP Enterprise Services must be exposed on the SAP ERP server so that SAP PO can consume them?

I want to send a standard Purchase Order from SAP ECC to another system. An IDOC will 100% work out of the box - no ABAP coding effort required on my part. Not sure if an Enterprise Service will be in the same boat.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Feb 14 at 09:50 AM

    You can think of the 2 being similar:

    Proxy

    Create data type/message type/service interface in ESR

    In ECC use SPROXY trans to create a class based on the ESR design

    write ABAP code in the class

    SAP Enterprise Service

    SAP delivers prewritten classes you can see in SPROXY

    From SAP support downloads can download the associated ESR objects and import into PI/PO ESR

    Can then call from PI as you would for proxy objects using XI adapter or the newer SOAP XI adapter

    Add comment
    10|10000 characters needed characters exceeded

    • Out of the box it seems that the Enterprise Services that are loaded into SAP PO ESR and then seen exposed in the SAP ECC SPROXY are only ready to go for inbound messages (SAP PO to ECC). The outbound messages come with no ABAP code to actually fill them or guidelines on what if any classes/BAPIs etc that need to be coded together with ABAP to make them useful. Unlike an outbound IDOC that is useful out of the box and ready to go.

      Seems that SAP have only done half the job here - I would need an ABAPer to spend weeks of coding effort to achieve the same result that an IDOC already does - or am I missing something here.?