*Please note: the service contract for this position will not be concluded with Henkel AG & Co. KGaA but with an external party”.
P027953: Sparc, cloud solution in connection with SAP FSC
Enhancement for CPM topics
Refund Process via CPI (cloud interface via Paypal);
Refund Process via JP Morgan;
Connection finance to E-shops;
API interfacte for Bance Mercantil Venzuela;
Existing finance reports to be updated for S/4 Hana
BCM projects (waiting for management decision)
SAP Bank Communication Management is a new module of SAP’s Financial Supply Chain Management component. SAP Bank Communication Management can be used to efficiently manage inbound (current day reports, prior day reports, payment file, and transaction-level acknowledgments) and outbound (AP, HR, and Treasury payments) communications with banking partners. In addition, SAP Bank Communication Management provides additional capabilities such as payment batching, approval capabilities using SAP standard workflow, digital signature, and payment status tracking.
Sparc -> Sales Promotions And Revenue Cloud
Integrate a new cloud solution for Henkel worldwide for Promotion and Revenue Handling with Interface to SAP FSCM tool and SAP Finance.
Template for Sales and Revenue process world wide. Using only 1 system.
Enhancement for CPM topics: CPM Peparation for S/4 Hana, new change requests, legal requirements where CPM is involved
SAP integrated & multi-banks electronic bank transactions platform
Create payment batches & send them to different house banks
Ensure bank continuity/flexibility
Ability to import both file- and transaction-level acknowledgments into the SAP system
Payment fraud prevention
Bank statements integration dashboard
Increase the efficiency and automation of payment processing and payment reconciliation
BCM is a new tool from SAP special for finance Goal of BCM project is using SAP standard workflow, digital signature, and payment status tracking.
Hintergrund der Beauftragung
As part of the projects above, SAP ABAP development for financing purpose is needed. The development also requires Cloud and API solutions, Interfaces as well as creation of ‘old’ programs into updated versions. The client does not have employees with sufficient expertise in connection with the programming language SAP ABAP and therefore requires external expertise. The contractor has an outstanding position and provides significantly different services than the internal employees.
An agile development method is used for Sparc project. The specific activities required in each case for the implementation of the commissioned services are iteratively coordinated within the framework of sprint meetings between the parties and implemented by the contractor within the sprints that follow the sprint meetings.
The contractor is responsible for checking before a sprint meeting, based on his professional assessment, which individual services are appropriate and feasible in the context of the assignment in the respective sprint. The sprints each have a duration of a week. Within the individual sprints, the contracting parties agree daily in "daily meetings" on the respective technical requirements for the services to be executed.
The contractor assesses the technical requirements for the services to be provided on the basis of its own professional assessment. After completion of a sprint, the parties each carry out a "sprint review" in which the contractor reports on the feasibility and status of the services he has carried out in the previous sprint and makes a recommendation on how to proceed further in the services have found that the respective sprint is not feasible. All of the meetings and exchanges described above take place exclusively in the presence of a central contact person named by the client who coordinates the project on the client's internal side. The organization and scheduling of the meetings described above, in which the contractor is involved, will be organized and carried out by the contractor and coordinated with the client.
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 week, so that the sprint meetings take place at intervals 2-3 times per week. 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 software SAP FSCM and SAP cloud. 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.
For all projects workshop is planned to update the developer and to introduce in our systems which will be used for different projects like Azure Devops and Snow. Information to Developer will be handled via Excel and Word lists or changes requests will be directly put on her/his name so that working can be done on her/his own and indepentently from Contractor.
Development of Interfaces between Sparc Cloud solution and SAP P92. These are already live in Germany and additional countries will follow as per the timelines (see below).
The template solution is already in place, but updated country specific changes have to be developed and implemented.
The SAP FSCM system needs to be updated which is being handled by an external company for Sparc. Timelines and meetings are always communicated in the sprint meetings.
Changes and developments of the templates have to be tested together with the external Sparc provider. All dates and requirements are fixed and communicated in the sprint meetings. In case of negative tests, re-work and re-testing is to be performed until changes can be implemented into the live system.
The Sparc project has already started, and rollouts have to be done in other countries. Special country specific requirements have to be maintained and developed on SAP P92 and Sparc, too. All dates and requirements are fixed until mid-2022 being and communicated in the sprint meetings.
Documentation of every change within SNow as Henkel’s Change Request System on the Sparc sharepoint. All documentation is subject to approval and to validate by Henkel.
Cross-financial CPM/BCM Change Requests
Enhancements for CPM and BCM are dealt via change requests in SNow. The external contractor will choose, process and deliver the change requests independently and can decide on their own how and when these are to be done.
For all implemented changes and after the project go-live, a hand-over to our Accenture maintenance group including knowledge transfer and documentation is needed. The hand-over and documentation are also subject to approval by Henkel. Meetings will be always planned after go-live for all participants.