Skip to Content
Technical Articles

checklist for AEX -> BPM integration

As I have just struggled for some time to get a BPM process instance started from either web services navigator, from the NWA process repository or by means of a triggering message from AEX I thought I might save you some time by posting this short write up of the two technical issues that cost me most time to resolve:

When you get exception:

com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: Unexpected uriID ‘/{urn:pnp:itservcostmanage}ITServicesCostDocumentReceive_In’. Found: BindingData ‘null’, interfaceMapping ‘null’ interfaceDefinition ‘null’

do ensure that the service interface you are using for the BPM message trigger has the correct interface pattern ‘Stateless (XI30-Compatible)’ here:

In case you are adjusting the interface pattern AFTER importing the service interface into the process definition ensure to reimport the service interface definition in the process development perspective by right clicking and choosing option ‘Reimport’ here:

Don’t forget to re-deploy your development component that contains the process definition.

When you get exception:

“com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: Technical difficulties were experienced during process execution.”

do ensure that your process development component in NetWeaver Developer Studio has release status ‘Release to Build’ (as highlighted in the following process properties view):

Without this (i.e. in release status ‘Draft’) only your ‘human activity’ tasks will be exposed with the result that your BPM cannot be started by a PI message trigger event, the web service navigator or manually from the NWA ‘Process Repository’. The (highlighted) ‘Process definition’ entry in the ‘Processes and Tasks’ view will be missing and the ‘Start process’ button will be greyed out.

That’s it for now.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.