Our solution connexas process enables the client to access any SAP business object related meta-data within their current customer related workflows, built with the App-Designer of Alfresco Process Services. Having SAP related meta-data directly available in the current workflow task, empowers the user to manage their tasks faster, reduces the error rate and allows to view the latest available data from SAP to drive a decision. Furthermore, based on SAP meta-data decisions can be made automatically to drive the workflow. Finally, if there is a need to store documents during the workflow (like for a purchase order where the business object in SAP is already available), these files can be uploaded to Alfresco where they can be automatically connected to the related SAP business object (by using our product connexas content).
Because workflow processes are quite different based on customer and industry, even the data that should appear in the workflow process differs. It also depends on the used SAP modules in the company. Therefore, we offer connexas process as a solution and not as a finished product. The solution has to be adapted and additional function calls to SAP must be implemented based on the customer needs. However, our solution comes already with some pre-defined SAP standard calls, that are available in each SAP system. So you can easily start over with a proof of concept.
By choosing connexas process to extend your Alfresco Process Services workflows with SAP meta-data comes around with certain advantages:
connexas process allows to read data from SAP within the current workflow but it is also possible to trigger any SAP action from a workflow task (or the outcome of a task).
User inputs in workflow forms that are related to SAP data can be validated immediately against correct values in SAP.
To reduce error rates, connexas process can populate only SAP related meta-data to the user that are valid or that are relevant at the stage of the process.
SAP related meta-data that are retrieved through connexas process can be used to drive decisions in the workflow process even automatically.
Based on task outcomes or evaluated user-inputs or any other criteria, it is possible to trigger any SAP action via connexas process. For example, start a SAP workflow that can do any custom action on SAP side.
It is possible to create business objects in SAP via connexas process. For example: Collecting required information for a contract during a workflow, can result in the creation of this contract (business object) on SAP side.
By choosing connexas process as solution to introduce SAP meta-data in Alfresco Process Services (Activiti) comes with a couple of benefits:
Run with Alfresco Process Services
Run with Activiti
Run with ACS workflows
Extended Rest API
The solution already includes some pre-defined services that extend the current Rest API of Alfresco Process Services. For example, it is possible to read a list of all SAP company codes or even to get a list of SAP cost centers. This is achieved by using function modules in SAP that are available in each SAP system by default.
The solution was designed to connect to an unlimited number of SAP systems. By adapting a configuration file and provide all necessary data required to login to SAP, it is possible to connect to multiple SAP systems just by passing it's name as request path parameter.
One step beyond SAP default meta-data!
Is connexas content or connexas process already successfully up and running? Now you are struggling with the fact, that you have to introduce or to adapt new business-processes which requires additional meta-data from SAP? Or maybe business-cases has changed over time?
We can help you to manage this requirement on a project base and extend your current integration to replicate any additional meta-data that will match the new requirements.
This packages includes (dependent on use-case):
Implementing a new Alfresco job that invokes one SAP standard function module to replicate additional meta-data. The meta-data (up to 10) retrieved from the SAP function call will be matched with the Alfresco aspects keeping the meta-data on Alfresco side.
Enhance the Alfresco Process Services API to invoke another SAP function module and enable additional meta-data in the workflow.
We deliver the above mentioned by a fixed rate on a project basis.
The implementation as well as the configuration will be documented.