With Process Orchestration 7.31 SP9, we plan to support abstract interfaces within BPM. Abstract Interfaces have been mainly introduced for ccBPM, and can be used for both on the inbound and outbound of your process. So far, BPM only supported inbound and outbound interfaces. For those of you who migrated from ccBPM to BPM, you had to copy the abstract interfaces used within your ccBPM process to either an inbound or an outbound interface. By supporting abstract interfaces in BPM, you can simply re-use the abstract interfaces used within ccBPM. Other than for ccBPM, BPM actually supports all kind of interfaces: abstract, inbound, and outbound.
By the way, Support Package 9 of 7.31 is planned to be shipped mid of September 2013. Of course, this is subject to changes.
Within the Process Composer perspective in NetWeaver Developer Studio, you can browse for abstract interfaces, and import the same:
Once imported, you can use the abstract interface either for message start event, intermediate message events or automated activities. Here, I have chosen an automated activity to send a message from BPM to PI:
For further tips and hints how to model common integration patterns in Process Orchestration, take a look at the blog series SAP Process Orchestration Integration Patterns.
If you plan to attend the SAP TechEd event this year, don’t miss the lecture session by Volker Stiehl about “How to Redesign ccBPM Processes Using SAP NetWeaver Process Orchestration” (session ID POP300).