Although the use of web services is the standard communication technique using ActiveControl, as the product resides in the SAP Netweaver stack, other SAP standard communication techniques are available for integration if preferred.
All ActiveControl APIs exist as remote enabled function modules within the ABAP environment and can therefore be called using the standard tRFC calls through an appropriate RFC destination. If the external system integrating with ActiveControl is either another SAP system or able to call remote functions directly then this method of communication can be used.
For inbound scenarios, the standard API’s can be called directly. For outbound scenarios, new send methods would need to be developed to enable direct calling of the external system.
As with TRFC integration above, as the ActiveControl API’s are standard function modules, IDoc wrappers can be created to call them and standard IDoc processing configured to control the integration.
For inbound scenarios, the appropriate IDoc wrappers would need to be generated and any IDoc sub-system configuration completed. Once again, for outbound scenarios, new send methods would need to be developed for IDoc communication to be enabled.