Couple quick notes:
- SAP is not designed for automated / programmatic access – their “BAPI”, or binary application programming interface, requiresÂ additional licensing beyond just the product to use
- HP Operations Orchestration requires an additional, ie not out-of-the-box, content pack and wizard to import SAP BAPIs to make operations
That said, the power of OOÂ can be brought to bear with SAP and imported BAPIs – with the followingÂ gotchas:
- You can only have one BAPI call in a given flow
- If you want to call more than one BAPI for a given task, you need to have them split into their own subflows, and call the subflows
Hopefully you won’t need to know this. But if you do, I’m happy to save you some of the headaches I have experienced interoperating with SAP & OO.
Comment on “sap bapis and hp oo”
Comments are closed.