SAP BTP – Salesforce integration

*Please note: the service contract for this position will not be concluded with Henkel AG & Co. KGaA but with an external party”.

Project Name: 

SAP BTP – Salesforce integration

Project description

As part of the project ServiceCloud Integration, we plan to introduce the Salesforce Service Cloud for Adhesives. This includes, among other things, the (further) development of the API Mgmt solution to analyse, configure, develop template APIs (Application programming interface) on the SAP API Mgmt to ensure a proper secure, compliant and robust integration of the salesforce ServiceCloud into the global SAP systems. Consequently, we do not have our own employees with sufficient expertise in connection with the programming of additional APIs / oData Services and for this reason requires external expertise. The contractor used by us has extensive experience with projects that require development services in the SAP API Mgmt and is aware about the “api-fication” of services including enrichment of proper policies, therefore the contractor has a unique position and provides significantly different services than the internal staff. The service is requested to analyse the requirements, configure, develop template APIs (Application programming interface) on the SAP API Mgmt to ensure a proper integration of the salesforce ServiceCloud into the SAP Horizon systems.
 

Task description
 

The services shall be provided within the framework of an agile development method. The concrete activities required in each case to implement the services commissioned shall be agreed iteratively between the parties within the framework of sprint meetings and implemented by the Contractor within the respective sprints following the sprint meetings. Prior to each sprint meeting, the contractor shall independently check, on the basis of its professional expertise, which individual services are reasonable and feasible within the scope of the assignment in the respective sprint. The sprints each have a duration of 3 weeks, so that the sprint meetings take place at intervals of 3 weeks. Within the individual sprints, the contracting parties shall coordinate the respective technical requirements for the services to be provided in daily meetings in order to achieve the compatibility of the individual components of the API Mgmt integration. The technical requirements for the services to be provided are assessed by the Contractor on the basis of its own technical assessment. After completion of a Sprint, the Parties shall conduct a "Sprint Review'' in which the Contractor reports on the feasibility and status of the services performed by it in the previous Sprint and makes a recommendation on how to proceed with regard to the services that proved to be unfeasible in the respective Sprint. All of the meetings and exchanges described above shall take place exclusively in the presence of a central contact person named by us, who shall coordinate the project on our internal side. The organisation and scheduling of the meetings described above in which the Contractor is involved shall be organised and carried out by the Contractor and coordinated with us. 

Tasks:

• Technical consulting and analysis of the planned interfaces to be established – Defining data models and policies for the API Management environment. In order to run a proper analysis and detailing out the right policies to be introduced, the required interfaces to be built are written down in a data catalogue. The analysis shall including direction, source / target object, transmission method and data volume plus the information of the desired interface technology.
• In total 14 interfaces have to be setup and developed from the Service Cloud towards our global SAP system for multiple data objects from Material Master Data, Customer Data, Use Cases (in case required upfront,  we are able to share the list of currently to be planned interfaces)
• Unit Testing, Functional testing and regression testing has to be applied accordingly in order to ensure proper functionality before the productive deployment. 

The documentation of the applied changes will be signed off afterwards by Henkel. As a tool for documentation we use AzureDevOps. The contractor gets access to the tool.

The service of the contractor has the goal to establish a secure and robust interface between the Salesfoce Service Cloud and the Henkel on premise systems including proper logging for incident resolution.