Skip to main content

Integrating Ariba B2I & SCC with S4 HANA for Service Costing

Client is one of the largest TMT enterprise involved in manufacturing Storage Devices, Servers and Switches

S4 HANA for Service Costing

Client is one of the largest TMT enterprise involved in manufacturing Storage Devices, Servers, and Switches. It also performs repairs, maintenance and installation of the servers etc. Purpose of the project was standardising Service Costing and Project Costing by consolidating the systems, automating the processes and removing redundant processes. Deloitte was selected to partner with client on this engagement to integrate the solution with several different transformation initiatives by adopting S4 HANA, Ariba SCC, Ariba Buying and Invoicing, Concur, EAP and boundary application e.g., Salesforce (SFDC), Legacy system (GCSN-Global Channel Service Network) Client is engaged in repair, installation, break fix and preventive operation of the servers and electronic components which encompass Service Costing. Client does not have their presence in every country hence they have third party service providers who take care of service repairs. Third party service provider has access to Legacy system (GCSN - Global Channel Service Network) and Salesforce (SFDC) where they can request part and claim labour on completing the activity. Client is consolidating all SAP ECC systems to one S4 HANA system, objective of the programme was to capture all cost related Services in Service Order and integrate with different transformation initiatives.

 

Client is one of the largest TMT enterprise involved in manufacturing Storage Devices, Servers and Switches. It also performs repairs, maintenance and installation of the servers etc. Purpose of the project was standardising Service Costing and Project Costing by consolidating the systems, automating the processes and removing redundant processes. Deloitte was selected to partner with client on this engagement to integrate the solution with several different transformation initiatives by adopting S4 HANA, Ariba SCC, Ariba Buying and Invoicing, Concur, EAP and boundary application e.g., Salesforce (SFDC), Legacy system (GCSN-Global Channel Service Network) Client is engaged in repair, installation, break fix and preventive operation of the servers and electronic components which encompass Service Costing. Client does not have their presence in every country hence they have third party service providers who take care of service repairs. Third party service provider has access to Legacy system (GCSN - Global Channel Service Network) and Salesforce (SFDC) where they can request part and claim labour on completing the activity. Client is consolidating all SAP ECC systems to one S4 HANA system, objective of the program was to capture all cost related Services in Service Order and integrate with different transformation initiatives.

Problem statement


Currently, SAP ECC is integrated with boundary application with limited functionality. Two ECC systems are used to handle Service Costing and Project Costing. All the service cost are charged against the cost centre which results in time consuming reconciliation of the balances and often results in audit issues. Due to this, the individual costs related to break fix, installation and deployment, resident labour charges, miscellaneous charges etc. are difficult to track and capture. Additionally, the existing processes aren't scalable and involve a lot of manual activity.

Integrating Ariba B2I & SCC with S4 HANA for Service Costing

Problem statement
Currently, SAP ECC is integrated with boundary application with limited functionality. Two ECC systems are used to handle Service Costing and Project Costing. All the service cost are charged against the cost centre which results in time consuming reconciliation of the balances and often results in audit issues. Due to this, the individual costs related to break fix, installation and deployment, resident labour charges, miscellaneous charges etc. are difficult to track and capture. Additionally, the existing processes aren't scalable and involve a lot of manual activity.