Helping the World’s Largest Fitness Community with FMS Rollout
Who is the Client?
The client is a globally known supplier of footwear, sports and casual apparel. An American company with global operations, their products are known world-wide for their moisture-free fabrics. They sell online, by catalog and through retail.
What was the client trying to achieve?
The client implemented a global template in the USA (SAP FMS 2.2 – SAP ECC 6.0/EHP 8/Service Pack 2) which then had to be rolled out to China and South Korea in addition to an upgrade (SAP FMS 2.10 / SAP ECC 6.0/EHP 8/Service Pack 10). China and South Korea were running business on SAP Business One while the US was using SAP Business Suite on HANA and SAP S/4 HANA 1605.
International Rollout
What services did Data-Core provide?
- Gathered requirements from functional consultants and Business Process owners
- Prepared the TSD (Technical Specification Document) that included the technical solution in line with FSD (Functional Specification Document)
- Identified type of SAP ABAP on HANA developments, such as Reports, Interfaces, Conversions, Enhancements, and Forms (RICEF) using HANA Optimization techniques (ABAP Golden rules, Enhanced Open SQL, CDS Views and AMDP – ABAP Managed Database procedures)
- Developed new Enhancements, Proxy Interfaces, VOFM Routines and RFC objects
- Made changes to Existing IDOCs to incorporate CHIKO (China and Korea) changes
- Developed ASN Delivery Enhancements and Webservices (to Minisoft) in SAP Supplier Network Collaboration (SAP SNC) systems
- Supported OData Services in P2P Fiori Applications
- Supported P2P, OTC, RTR and SNC Modules of SAP FMS 2.10 Package
- Performed code Performance optimization using tools such as SCI, ST05 and SAT
- Performed code Review of self and offshore team using SAP ABAP Extended Program check tool & Code Inspector (SCI)
- Post-Development performed Unit testing of solution in Development landscape called TUT (Technical Unit Testing) and confirmed that it did not deviate from FSD
- Once objects were moved to Quality Landscape, performed sanity check to make sure it did not impact existing business processes
- Functional Unit Testing (FUT)
- ITC1 (Integration Testing Cycle 1 in Parallel Quality System dedicated to CHIKO)
- ITC2 (Integration Testing Cycle 2 in Parallel Quality System dedicated to CHIKO)
- Retrofit Issues while adjusting the regular changes in CHIKO Environment
- UAT (User Acceptance testing in actual Quality System US + CHIKO)
- Performance Testing
- Regression Testing>/li>
- Used HP Incident/Defect Management tool HP Application Life Cycle Management for Defects raised from above testing
- Resolved all technical issues arising from Testing with utmost priorityResolved some of the long pending issues that was appreciated
- Post resolving the defects, made sure it did not impact other objects and transport the solution
- Reviewed the defect solutions provided by other team members
- Supported issues after go-live i.e., Hyper Care Support
- Addressed all priority issues immediately during Hype Care Period
- Provided 24 /7 support during Hyper Care Period to address any Business-Critical Issues
- Daily Defect Review Meeting with all stake holders to provide the current status and highlight Blockers/Dependencies, if any
- Code Review meeting with offshore team to check if code is complaint with standards
- Supported the offshore team in reviewing the solutions and guide them in their developments
- Daily TCCB meetings (Transport Change Control Board) and reviewed the objects being transported and made sure it did not impact the existing functionality
- Supported Migration of all CHIKO TRs to Global Landscape, checked the dependencies and resolved post-migration issues
In Summary…
Data-Core’s services in the SAP FMS and SOH rollout was of huge satisfaction to the Client. The client acknowledged the competency of our resources and appreciated that the development and issues were fixed well within the time specified. The projects resulted in avoiding unnecessary burden to the database. Only processes, not data were moved to the database layer, which greatly saved on cost and increased agility. The contract was extended for post-go-live support and ultimately to support future go-lives.