PI 7.3 AEX Error - BPM

[former_member183906]

Hi,

http://scn.sap.com/docs/DOC-28803

I am following this BPM document and doing development in PI 7.3 Single stack and NWDS of equivalent version.

But I am getting below error.

Scenario is Sender sends request to SAP PI and PI executes XSLT map and send it to BPM. Message is reaching BPM and giving this error :

Message could not be processed. Reason: com.sap.aii.proxy.xiruntime.core.ESPXISystemFaultException: Error encountered during processing of XI request message in

inbound ESP; Hint: com.sap.engine.services.webservices.espbase.server.additions.exceptions.ProcessException: com.sap.SOA.wsr.030106 - No operation found using soap

keys [], [cXML]. InterfaceMapping Object class: com.sap.engine.services.webservices.espbase.mappings.InterfaceMapping mappings: {BindingType=Soap, SEIName=Si_ReqMsg,

PortTypeQName={urn:name}Si_ReqMsg, Galaxy_SDO=true, InterfaceMappingID=57b8b8ac:13e1952d207:-7f62, SoapVersion=SOAP11, BindingQName={urn:name}Si_ReqMsgBinding}

Any clue to solve this ?

Regards

[MichalKrawczyk · Accepted solution]

Hi,

just to check - operations mappings don't work with BPM with SP0 (and there are some limitations

for using them with external definitions even with SP6) on which SP are you on ?

Regards,

Michal Krawczyk

[former_member183906 · Accepted solution]

Hi,

I am using this PI version :

Make Release	NW731EXT_07_REL
SP Stack Number	07
JDK Version	jdk16

and NWDS version is as below :

nwds-extsoa-7.3-EHP1-SP07-PAT0000-win32

But I am not able to import any operation mapping from ESR - Error is "Unable to display WSDL".

And the error mentioned above still persists.

Regards

Message was edited by: SAP PI

[former_member184948]

Hi ,

I have solved this issue. I received the same issue .

https://answers.sap.com/questions/12735535/sap-po-nw-bpm-receiver-soap-channel-error-no-opera.html?c...

Cause of the issue : I had used ED (external definition) in the receiver service interface , which was used to invoke the NW BPM. And this Service interface was also, of-course , imported in NW BPM NWDS in the start step. Lately , I had changed the ED in the Service interface and imported that in NWDS as well, but did not use the newer version of ED in Message mapping and had not refreshed my OM (with read operation) , which resulted in this error.

Solution : I used everywhere the new version of ED and this issue is gone .PI can invoke BPM perfectly well.

[former_member591291]

Hello Experts ,

I am getting exactly the same issue ..Did anyone get solution for this ? If yes , please share!!!

Thanks.

[former_member186851]

Did the issue get resolved?

[Former Member]

Were you able to resolve this ,i am facing a similar issue.Thanks

[adam_smith7]

No Reply since 2013....

Pravithra, if you are getting the same error then check the following:

When communicating between AEX and BPM using the Xi3 protocol you have the restriction that the name of the operation which the BPM process is implementing must be the same as the name of the interface which starts the process.

So if your service interface on which your BPM message trigger is based is called "SI_SOMEHTING", then operation in the service interface must also be called "SI_SOMEHTING". Furthermore, there can only be one operation and the service interface should be marked as XI3 stateless.

[Former Member]

Thanks for the reply Adam.

I have got my service interface imported to my NWDS and they are marked as XI3.0 stateless . The service and operation appear to have the same name as that of the inboud interface which i have mentioned , with service group being added additionally to the operation within brackets. Further, it doesnot manually allow me to edit the operation i have picked up from the list it suggested.

I even changed the name of the trigger to that of the service interface name .It did not help any other inputs?