Inbound Service Interface without Input Request Message

Is it possible to create an Inbound Service Interface without Input Request Message? We are trying to create a web service to get all records from a database table hence no input parameter is needed. We have tried in both XI 7.0 and PI 7.1 but couldn't do it. Is this scenario not supported by ESR or am I missing something? Any hint will be appreciated.
Regards,
Jiannan

In the scenario I described in my initial post the table structure is only needed in the response message to receive the data.
For a web service generated from a RFC function module using the service creation wizard (SE80) a table parameter is automatically included in the request message. I can understand this as the wizard can not figure out if the table parameter is needed in the request message or not.
I have tried to use the service creation wizard to generate a web service from the function module RFCPING that has no input or output parameters. As shown in below WSDL segment the WSDL does allow not having any input or output parameters.
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style">
- <xsd:element name="Rfcping">
- <xsd:complexType>
<xsd:sequence />
</xsd:complexType>
</xsd:element>
- <xsd:element name="RfcpingResponse">
- <xsd:complexType>
<xsd:sequence />
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="Rfcping">
<wsdl:part name="parameters" element="tns:Rfcping" />
</wsdl:message>
- <wsdl:message name="RfcpingResponse">
<wsdl:part name="parameter" element="tns:RfcpingResponse" />
</wsdl:message>
Thanks,
Jiannan

Similar Messages

Any possiblity to use single Inbound Service Interface with multiple Receiver Agreements

Hi All,
Scenario: PROXY to FILE.
Requirement is to receive to two locations.
Is it possible to use single Inbound interface with multiple Receiver Agreements. I tried using two operation in the Inbound Service Interface, and Operation Specific in Determination. But couldnt proceed further. Do I need to use seperate Service Interface for two receiver locations?
Please suggest some solution.

Hi Naveen,
There is a possibility but in the case in the same server location with dynamic configuration: Placing file in two different directories using single receiver communication Channel
With different location you would need to develop a new adapter module as Amit Srivastava explains and develops here Send File to Two Different Locations using Adapter Module
Regards.

XI Adapter LOOP_IN_MESSAGE_ROUTING (Inbound service interface PI- ERP)

Hello,
my scenario:
PI is sending some data via XI Adapter to ERP (SAP ECC 6.0).
In PI SXMB_MONI shows us LOOP_IN_MESSAGE_ROUTING.
Some points:
- Proxy is generated and activated in ERP
- ERP is type of LOC (application system)
- Corresponding Integ. Server of ERP is our specific PI
- ERP HTTP port is running (SMICM->Services)
- XI Adapter is using messag protocol XI3.0
- XI Adapter refers to an HTTP RFC destination
- PI HTTP RFC destination to ERP uses /sap/xi/engine?type=entry as path prefix
- testing the PI HTTP RFC responses with: Empty HTTP request received (as suggested)
- calling ERPserver:HTTPport/sap/xi/engine?type=entry in local web browser results in: EMPTY_HTTP_REQUEST_RECEIVED (as suggested)
So why our message is send back from ERP to the sender PI integration engine and fails with LOOP_IN_MESSAGE_ROUTING?
Thanks in advance,
André

Hi,
error occours after calling the XI Adapter in CENTRAL pipeline:
HTTP-client: closing... External error header received Error exception return from pipeline processing! CENTRAL</SAP:P2>
<SAP:P3>XI</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack> Schleife im Nachrichtenfluss entdeckt: System is.00.sappi1a, Pipeline CENTRAL mit Inbound-Adapter XI bereits durchlaufen (siehe HopList-Header) </SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Many thanks,
André
Edited by: André Schillack on Dec 6, 2010 10:56 AM

How to create Endpoints for Inbound Service Interfaces in PI?

Hi Gurus,
we have to publish Endpoint URLs for third party system, which have to send us SOAP Messages via HTTP. For this we need to publish Endpoints (Incoming into PI) for the third Party Systems.
I already tried to publish it out of the Sender Agreement, but this is only for Outbound Service Interfaces and not incoming. I Also tried to publish the WSDL out of the Service Interface Design, but there are no Endpoints supplied.
What can i do, to get incoming endpoints?

>
Udo Buchter wrote:
> Hi Gurus,
>
> we have to publish Endpoint URLs for third party system, which have to send us SOAP Messages via HTTP. For this we need to publish Endpoints (Incoming into PI) for the third Party Systems.
>
> I already tried to publish it out of the Sender Agreement, but this is only for Outbound Service Interfaces and not incoming. I Also tried to publish the WSDL out of the Service Interface Design, but there are no Endpoints supplied.
>
> What can i do, to get incoming endpoints?
Once you generate the WSDL in that there will be an SOAP Action url where you can see the endpoint or the target to which message will be sent to...
only thing you need to provide them apart from WSDL is user credentials.. thats it..
they need to import the WSDL provided by PI in their application
Rajesh

RFC to SOAP Interface - Problem in Request Message Mapping

Dear All,
We are working on RFC to SOAP Scenario i.e. pulling out data from an WebService from SAP via PI.
In Request Message Mapping, when the wsdl file is uploaded as Target Message, the wsdl request shows the nested elements like below.
<Request>
   <Request_New>
      <PAR1>xyz</PAR1>
      <PAR2>123</PAR2>
   </Request_New>
</Request>
But the desired Request should go like below.
<Request>
   <PAR1>xyz</PAR1>
   <PAR2>123</PAR2>
</Request>
Hence it gives an error saying that the tag Request_New does not exist.

Dear All,
Our target webservice cotains multiple methods.
The every method contains its corresponding request, response and SQL ecxeption as messages.
In case of request structures, every method (except crmPaymentReceived) contains more than 1 root element.
So while calling those methods having more than 1 root element, the additional header tag will always appear(not avoidable) in the request coming from SAP PI.
For Example,
Request Structure for method u2018isLoginIdExistu2019 (having more than 1 root element)
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing">      -
>>>>> u201CThis Header tag will always appear u201D
<isLoginIdExistin0>asp</isLoginIdExistin0>
<isLoginIdExistin1>1</isLoginIdExistin1>
</ns1:isLoginIdExistRequest>
</soap:Body>
</soap:Envelope>
For this method, we get the error(saying that ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing" does not exists).
Request Structure for method u2018crmPaymentReceivedu2019 (having only 1 root element)
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=http://www.w3.org/2001/XMLSchema-instance xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<ns1:crmPaymentReceivedin0 xmlns:ns1="http://netpricing">false</ns1:crmPaymentReceivedin0>
</soap:Body>
</soap:Envelope>
For this method, we get the success response.
I tested their wsdl URL in XMLspy and wizdal(a wsdl testing tool), it shows request in the format having only root elements and not the header tags.
But header tags will always appear when header tag contains more than 1 root element.
Can anybody suggest me how do I tackle this?
Thanks in Advance.

Synchronous interface without Service Interface and Mapping

Hi all,
Short and simple question: Is it possible to set up a synchronous interface without using Service Interfaces and (Operation and Message) Mapping?
In my case I would like to create an interface with a SOAP and File adapter.
Cheers,
Mac

Hi Mac,
>>Short and simple question: Is it possible to set up a synchronous interface without using Service Interfaces and (Operation and Message) Mapping?
Yes possible provided you have both Sync adapter as sender and receiver. For eg: Soap sender --> PI --> HTTP adapter
>>In my case I would like to create an interface with a SOAP and File adapter.
Sync scenario using File adapter as receiver is not possible. Because File adapter works asynchronously.
Regards
Suraj

Not getting Service interface in receiver side

Hi,
I am working on a newly configured PI server.
Here, I am working on a synchronous SOAP to RFC scenario from third party to ISU.
From the Display WSDL option of ID I have created a wsdl file and testing the scenario by importing wsdl file into SOAP UI. When I am sending some request from SOAP UI , I am getting proper response message ; that's mean interface is working fine and properly hitting the RFC in ISU.
I can see the message in SXMB_MONI of my PI server . But I am not getting the message in SXMB_MONI of ISU server . Even in SXMB_MONI of ISU I am not getting the inbound service interface also .
What can be the possible reason . As I am working on a totally new server should I do any configuration in the server to get the SI in receiver side.
Please help.
Thanks in advance.

Hi,
Please check if Sync logging is enable in ISU. refer the below blog
XI: I cannot see some of my messages in the SXMB_MONI
regareds,
Harish

How to create Web Service based on PI WSDL message

Hi all,
we have following scenario:
Within PI (version 7.1) we set up a message type and inbound service interface. This service interface should send the PI message to a web service running on a SAP J2EE (version 7.01). As the PI message is sent as WSDL I thought it should be easy to build a web service on the SAP J2EE based on this WSDL from PI.
Unfortunately, I have problems creating the Web Service.
For my current project we integrated the NWDI to the SAP NetWeaver Developer Studio and I'm required to add the Web Service to an existing DC (Development Component) within the NWDI.
What I tried so far is:
- I created a Deployable Proxy Project and within this I created a Client Proxy Definition based on the WSDL from the PI. But I can't add this Proxy to the DCs of the NWDI and I don't know how to implement my own coding here in order execute specific functions.
- I created a new class within the NWDI DC and a public method. Based on this I created a Virtual Interface and a Web Service Definition (WSD). Then I added this to a Web Service Deployment Descriptor. I uploaded this to the SAP J2EE. But I'm not able to access this and I don't know hoe to assign the WSDL here.
I also tried here to create a client proxy based on this WSD as I thought I might assign the WSDL here. But I don't see the WSD in the list of Web Services uploaded to the SAP J2EE...
Can you please advice me how to create a Web Service in such an environment?
regards
René Jurmann

Hi Tahir,
sorry that you needed to wait this long - but this is how I created the web service:
The steps on how to create the web service in NetWeaver Developer studio are nearly the same as described in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5838. [original link is broken] [original link is broken] [original link is broken]
Some steps I just skipped and some others I added. Some of the steps I did the way I described it as I needed to connect the web service with the SAP PI.
Prerequisites:
Add Java Perspective and J2EE Development Perspective to the open perspectives.
Within "Window - Preferences - Web Services" check "Soap extensions visible in the virtual interface editor"
The SDM of the corresponding SAP J2EE is configured within "Window - Preferences"
Create a Development Component (DC) with type "J2EE -> EJB Module"
The business logic of the web service will be implemented in an Enterprise Java Bean (EJB). So first the EJB component must be created:
     Choose "File -> New -> Other"
     In opening PopUp choose "Development Component -> Development Component Project"
     Select the Software Component for which you want to add the DC (e.g. "Local Development -> MyComponents")
     Choose now vendor, name and type:
          vendor is an alpha-numeric string of 20 characters starting with a letter - all in lower case
          name is an alpha-numeric string starting with a letter - all in lower case
          vendor and name concatenated must not be longer then 40 characters
          the name can be separated into different part using "/" as separator
          each part of the name must not be longer than 8 characters
          the type is "J2EE - EJB Module"
          you can specify a Caption as general description for the web service
Create new EJB
To create the EJB itself:
     In J2EE DC Explorer of J2EE Development Perspective expand new DC and right-click on folder "ejbModule"
     Choose "New - EJB" with following details:
          EJB Name: <name as for PI service Interface to be created - starting in upper case>
          EJB Project: <pre selected>
          Bean Type: Stateless Session Bean
          Default EJB Package: <corresponds to namespace in PI>
          generate default interfaces: Checked
Regarding the "Default EJB Package" this should be created according the namespace in PI for which all PI objects will be created. This only applies if you have some naming conventions here.
Example:
Namespace in PI is: http://company.net/pi/SOFTWARE_COMP/Application
The corresponding package then is: net.company.pi.software_comp.application
Implement coding for web service
As the web service will be called via PI some transfer variables will be submitted. Most likely, those variables will not be standard type (e.g. String) but a complex type. Those types must be generated as Java classes. Below an example of a complex type I needed:
Data Type
net.company.pi.software_comp.application.types.MessageProcessingInformation
Structure:
     Element name          Element type
     sendingSystemID          String
     interfaceID               String
     businessProcessVariantCode     String
     testIndicator               Boolean
For every element described a public "get", "set" and "has" method must be created in the corresponding Java class:
package net.company.pi.software_comp.application.types;
import java.io.Serializable;
public class MessageProcessingInformation implements Serializable {
     protected String sendingSystemID;
     protected String interfaceID;
     protected String businessProcessVariantCode;
     protected Boolean testIndicator;
     public String getSendingSystemID() {
          return sendingSystemID;
     public void setSendingSystemID(String value) {
          this.sendingSystemID = value;
     public boolean hasSendingSystemID() {
          if(sendingSystemID != null && !sendingSystemID.equals("")){
               return true;
          return false;
All Java classes representing complex types and all classes referenced here (used for sub-types) must implement java.io.Serializable. Java standard types which do not implement this class must not be used as sub-types.
As soon as all data types are declared the real business logic can be implemented:
     In J2EE DC Explorer of J2EE Development Perspective expand DC - "ejb-jar.xml" - <Name> and double click on "ejbCreate"
     In detail view select folder "Business Methods" and click "Add"
     choose name of business method - this should be the same as the PI message type used for the service interface - starting lower case
     return type should be "void"
     add needed parameters fully qualified - including package (as specified in PI and created previously in DC)
     you can mark certain parameters as array if necessary
Remark:
It might be that after saving you get an error. This might be as the package name of one component is copied to the corresponding Java class at the very beginning (before the package declaration within the Java class). Simply delete the string here.
It also might be, that the new business method is only defined in the remote interface class but not in the bean class. Just create an according method in the bean class.
Within the newly created business method within the bean class you can now implement the business logic.
Create a DC with type "J2EE -> Enterprise Application"
In order to create the "real" web service and deploy it to the J2EE an Enterprise Application project has to be created. So create a new DC as for the EJB Module but choose as type "J2EE -> Enterprise Application".
After the DC is created right click on the EJB DC and choose "Add to EAR Project". Choose the new DC.
Create web service for EJB
As soon as you implemented the business logic you can create the "real" web service. Therefore:
     Right click on the EJB name below "ejb-jar.xml"
     Choose "New - Web Service"
     Choose proper "Web Service Name" and "Configuration Name" (probably oriented at the EJB name)
     Copy the URL of the web service - you'll need it later for PI configuration
     on the second next screen use the same name for "Virtual Interface" and "Web Service Definition" (the name should be the name of the "Endpoint")
     the "EAR Project" should be preselected
Unfortunately, the web service can't be used in its current configuration to be accessed by PI. Therefore the Virtual Interface must be changed. To do so, expand folder "Virtual Interfaces" and double click the virtual interface created.
Within the detail view expand in tabs "Mapping" and "Types" the complete folder structure. For any "SOAP Extension" where a namespace can be defined use as namespace the corresponding namespace in PI (e.g. http://corpintra.net/pi/CBFC_GLOBAL_SAP_APPL/BillerDirect) but do not change any "Soap Extension" of a standard Java type. (if you don't have any naming convetions for namespaces in PI you can leave the SOAP Extension here. But then the namespace in PI should be set accordingly.)
Probably it can be necessary on top level "Soap Extensions" in tab "Mapping" to leave "Use Namespaces for Parameters" unchecked. For some of my web services this parameter must be checked for others not - just try.
If you can define a "New Name", "Local Name" or "Item Label" for a Soap Extension then use a name with starting upper case letter. (For Java Naming conventions most of the data type names will start with lower case letters.) Especially the method name must be renamed this way in order to stick to the PI namings.
As a last point to change here check in tab "Mapping" all "Incoming Parameters" which you specified as array. Use for those as "New Name" a different name - do not just simply change from lower case to upper case. This is necessary as on PI we need to create two levels although here only one is specified.
For any own sub-type declared as array the name within the coding should also differ from the corresponding Java Class name the type refers to.
If all this is done you can deploy the web service to the J2EE:
     right click on "Enterprise Application" DC and choose "Development Component - Build..." and build all corresponding components
     right click on "Enterprise Application" DC and choose "Development Component - Deploy"
Test the new web service via <J2EE URL>/wsnavigator/enterwsdl.html
Create PI interface
After the web service is created successfully the PI integration can be started.
Therefore, within the Enterprise Services Builder create a data type according to the web service definition. All components defined on top-level for this data type should be declared as incoming parameter for the web service business method. Therefore it could be necessary to create some sub data types on PI first and add those to the "master" data type.
Ensure that the names of the components correspond to the names defined in the web service (see virtual interface here). Those names must exactly be the same - including lower/upper case. Also take care for the ordering of the components.
In case you need to include arrays following applies:
The upper level is of occurrence "1:1". This has only one sub-entry with occurrence "1:n". The names for upper and sub-level must not equal.
Based on the data type a message type is created. The name of the message type must be exactly the same as the name of the web service business method. (Hint: the name of the web service business method was most likely changed in the virtual interface. Then this name must correspond to the message type name.) Based on the message type an asynchronous inbound interface is to be created (which will be referred in the Integration Directory). The operation name for this interface (left panel) should be the same as the name for the web service business method.
Create PI mappings and routings
How to map (message mapping and operation mapping) from source to the web service message I wont explain here as this depends on the source message. The only important things here are:
     When creating the SOAP communication channel within the Integration Builder the "Target URL" is:
          <J2EE URL>/<Access URL as specified in web service creation>?wsdl&style=document
     The soap action is the name of the web service business method.
     Most likely the web service needs authentication to be executed.

OSB - How select variable used as request message in routing to buss. serv.

I' modelling a message flow for a proxy service.
Depending on the content of the incoming request message, a branch (conditional) is selected. In this branch the message needs to be routed to a business service.
This business service has a different request message definition than the proxy service. Some kind of transformation is probably necessary. (not implemented yet)
Question is how to select what variable structure (I've created a Service Interface variable for the business service) that'll be used when invoking the business service.
Only thing I can select, is the service and the operation.
How to continue?

The payload for the business service needs to be in the *$body* variable. There are also other predefined variables like $header and $attachments that could make sense if your need to send SOAP Headers or attachments to the business service.

No endpoint for Service Interface

Hi everybody,
I have published my Service Interface to the Service Registry but unfortunately without an endpoint.
How can i configure an endpoint for a Service Interface within ESR? Should i use a Model in ESR?
regards,
Sid

Hi Sid,
Your business logic has to be implemented in the system that will be providing (provider system) the data / info etc.
e.g. You want to create a web service that allows you to update a customer's address details in SAP ECC & this functionlaity should be triggered from a Webdynpro Java User Interface.
- Webdynpro Java is the consuming application (also called consumer)
- SAP ECC is the backend system OR provider system OR provider
In this case your business logic will be in SAP ECC.
If you choose to go with a point-to-point scenario:
You could first setup a connection between SAP ECC (provider) & SAP PI. You could then model your inbound service interface in SAP PI. Now because you have visibility between SAP ECC & SAP PI, the service interface modeled in SAP PI become visible in SAP ECC (TCode SPROXY). You would then generate a provider proxy from this service interface & implement the business logic in there. Once the proxy is activated you can then configure an endpoint for it using TCode SOAMANAGER (see lots of guides on how here in SDN). In this case SAP PI is only used at design time just to model the service interface. At runtime Webdynpro Java would talk to SAP ECC directly via the endpoint that you would configure.
For a mediated approach:
Pretty much the same concept as above except this time you would also model an outbound service interface & map the inbound & outbound interface. The call would then be routed as follows - Webdynpro Java -> SAP PI -> SAP ECC but the business logic would still be implemented in SAP ECC.
There are lots of technicalities around this but there are lots of guides on SDN relating to this.
Regards, Trevor

BPM 1:N split into different service interfaces

Hi everyone, just a quick question about multimapping scenarios.
If I want to make a 1:N message split in BPM I should use a transformation step and specify a multiline container element to get the result of the transformation. That multiline container element is bound to a single message type so, If I want to split my incoming interface into different service interfaces (based on different message types), how can I handle that in BPM? Or is it just not possible?
Thanks in advance.

Hi,
It is possible to specify more than one container element for the resulting messages of the transformation step
Its possible.
In operation mapping in IR if you add 3 interfaces in Target side and the same mapping if you select in BPM transform step then it will ask for three contaner.
Create 3 contaneir.
Select type as Abstract Interface.
Then select individual interface in those containers.

Publishing Service interfaces from SAP PI Repository

Hello All,
I am wondering is it possible to publish service interfaces from ESR in to repository? If so am I able to publish even outboud service interfaces along with inbound service interfaces? As in my ESR for Inbound I am unable to publish services in to Service registry... any reason? I want to get the concept behind it.
Thanks
Rajeev

Hi Rajeev,
The outbound web service invocation doesn't work like that. Refer to the guide below, see the section regarding developing a Web Service Consumer:
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06b6392-cde7-2c10-8f8b-bdea5d781dd9?quicklink=index&overridelayout=true]
You have the option of using SAP PI or not using PI for outbound Sync or Async Web Service calls. If you use PI then you would still need to generate the Consumer Proxy in the back-end & from there proceed with the SOAMANAGER route.
Regards, Trevor

Service interface with 2 operations

I have a service interface with 2 operations...
so i have 2 operation mappipngs..
but when i create the interface determaination....it shows only one mapping...
should i create 2 interface determaitions????one for each opeartion??
if yes what should be the sender interface in that case while creting the interface determination..as it is not coming in the F4 help

HI ,
-- Create one outbound service interface with mutiple operatiosn name on left hand side.
-- Create One Inbound service interface with mutiple operations on left side.
-- create two operation mappings..
-- while creating operation mapping drag and drop the outbound service interface on sender side and it will show you 2 opetions select one and same case while adding receiver service interface on operation mapping.
repeat the procedure for second operation mapping also.
-- now when you create interface determination on ID side you see two operations on left hand side of interface determination object select first and assign respected operation mapping then select second and assign second operation mapping..
Thanks,
Bhupesh

About process component , service interface

Hi all, what do process component and service interface mean? why and when do we need process component and service interface? when we generate the code in NWDS, it will generate a interface class that standing for service interface in ESB, do it? how can we use the third-party process component in ESB?thanks

-> I deleted RA and when I tried to create new RA, I was not able to see the new SI created. I went to the Business component to add the new SI but there also am not able to add.
Did you check the filter criteria as 'ALL' to list both outbound and inbound service interfaces in the pop up list?
Also check in ESR if you have properly activated the new SI and cache content is updated.
Regards,
Zameer
Edited by: Zameer Hamza on Jun 16, 2011 4:09 PM

Using inbound service to produce data for outbound interface

Hi,
with SAP Enterprise services, we have lots of functionnality provided by SAP which we can use to easily get information
without having too much custom development done in the backend.
In our cas for example, we want to use an erecruiting enterprise service to extract data and send it to an external provider in an xml file.
here are the constraints
1) Reduce development as much as possible
2) Use PI to interface with external systems.
3) External system canot initiate the process.
It would be nice to reuse SAP content (Enterprise services) in order to extract the data and replicate it to the external system.
One way to do this would be to have a program which calls the method of the proxy that implements the enterprise service.
Then the program can just call PI to create a file with the contents returned by the method.
This is not an elegant solution ... , I would have liked PI to initiate the call at a specific time and with the response of the call send the xml file to the provider... this seems to be the reverse of what PI does...
I'm sure there are other solutions... any ideas ?
This is more of an extract and transfer scenario with PI...
Thanks.

Hi Thierry,
we want to use an erecruiting enterprise service to extract data and send it to an external
provider in an xml file
Please consider that the Auto generated proxies in Enterprise services are mostly Inbound( to SAP)
and have request and response structure.
When you are bringing PI into picture then you will need to create outbound structures, which you need
to copy.You will face issues with work around as suggested above , the proxies are not editable
and to make it editable you will end up creating a copy which will add more work then reuse.
Also think if the customer wants to enhance few field in the Req/Resp strucutures
(we need to consider this for sure)enhancing the structure is possible using dependencies
but it required costom changes.If you are expecting enhancements then better don't use enterprise services.
As SAP standard is designed to accept request and send response , its always correct to
request third party (consumer) to ask/trigger for data,unlike trying to put PI as triggering agent.
Conclusion:
Regards,
$rinivas
Edited by: Srinivas on Aug 12, 2010 7:27 AM
Edited by: Srinivas on Aug 12, 2010 7:37 AM

Inbound Service Interface without Input Request Message

Similar Messages

Maybe you are looking for