Built an Integrated SAP S/4HANA Core for a Growing Pharmaceutical Manufacturer
- Eitekh Marketing Team
- Mar 24
- 11 min read
Updated: 5 hours ago
Client Context
The client is a pharmaceutical manufacturer whose operating history began in 2005, with manufacturing of its own brands commencing in 2008. The company manufactures and markets medicines for domestic and international markets and has built its position around generic formulations, quality-controlled manufacturing and partnerships with international pharmaceutical companies. Its history includes a licensing relationship with F. Hoffmann-La Roche and manufacturing of Roche-licensed brands in its country.
Scale indicator | Publicly reported position |
Employees | More than 6,500 |
Registered brands | More than 100 |
Distribution centers | 42 |
Affiliate companies | 11 |
Global partners | 20 |
Certifications | 11 |
International presence | More than 25 countries |
The company's operating environment is particularly demanding. Its production facilities encompass dispensing, granulation, compression, coating, encapsulation, packaging and finished-goods handling. Raw materials, packaging materials and finished products move through integrated production and warehouse facilities, while separate physical, chemical and microbiological laboratories support quality control and environmental monitoring. The company reports compliance with WHO current Good Manufacturing Practices and local regulatory requirements, as well as ISO 9001:2015 certification.
Independent reporting also places the company among the country's top pharmaceutical businesses. In December 2024, A national daily described the company as a top ten domestic pharmaceutical player with annual turnover of approximately USD 180.4 million. The company subsequently completed the acquisition of Novartis AG’s majority interest in the country. That transaction post-dates the ERP program, but it illustrates the growth trajectory and organizational complexity that a scalable enterprise platform needed to support.
The client operates like a complex, multi-site process manufacturer: regulated products, controlled materials, quality-release requirements, a geographically distributed sales and distribution network, multiple business entities and a growing international footprint. That combination made enterprise integration a strategic requirement rather than an administrative IT upgrade.
This engagement involves implementing and providing ongoing support for SAP S/4HANA. The client relationship has been maintained for over six years till date.
Business Problem Before SAP S/4HANA Implementation
The company's growth had outpaced the systems supporting it. Business processes were spread across disparate legacy applications that lacked sufficient integration, regulatory-reporting support and a dependable enterprise reporting engine. Distribution operations were not adequately connected to the core systems, inventory visibility across distribution centers was unreliable, and fragmented financial processes slowed closing and management reporting.
Pre-implementation challenge | Executive impact |
Disconnected legacy applications | Departments worked from separate data sets, limiting enterprise-wide visibility and increasing reconciliation effort. |
Weak integration with distribution systems | Sales activity, orders, inventory movements and financial information could not flow consistently across the business. |
Inaccurate stock visibility | Leadership had limited visibility into inventory held across distribution centers, contributing to excess stock and inefficient working-capital deployment. |
Manual regulatory reporting | Compliance work required greater manual effort, increasing reporting burden and audit exposure. |
Fragmented finance systems | Financial closing, reconciliation, planning and consolidated management reporting were slower and more labor-intensive. |
Inconsistent user processes | Moving from local applications and workarounds to standardized enterprise workflows created a material adoption challenge across functions and locations. |
The inventory issue had strategic implications. A pharmaceutical company must coordinate raw and packaging materials, production requirements, quality status, finished-goods availability and distribution demand. Without current inventory information, purchasing can over-order, plants can plan against unreliable availability, distribution centers can accumulate excess stock, and finance cannot obtain a reliable view of working capital.
The reporting problem was similarly consequential. Multiple legal entities and operating locations required consistent accounting rules, transaction classifications and management reports. When finance teams had to reconcile fragmented source systems before planning or closing the books, executives received information later and with less confidence.
Change Management and Organizational Adoption
The transformation also required substantial changes in how employees performed their work. Standardizing procure-to-pay, plan-to-produce, order-to-cash and hire-to-retire processes affected procurement, finance, production, quality, maintenance, warehousing, sales, distribution and human resources. Users had to move from familiar local practices to common approval paths, data definitions and transaction controls.
The program’s breadth made organizational adoption a significant delivery risk. Eitekh introduced SAP Fiori applications intended to simplify transactional processing and improve the user experience.
Legacy Integration Complexity
The technology challenge was broader than migrating transactions into a new ERP. The new platform had to exchange information with the company’s distribution environment, CRM and sales applications while maintaining complete accounting integration. Eitekh specifically reports CRM integration, integration with a sale's mobile application, warehouse-management capabilities and SAP Business Planning and Consolidation.
The implementation had to reconcile operational and financial data across both SAP and non-SAP applications rather than replace a single isolated system.
The Scope for SAP S/4HANA
Eitekh implemented SAP S/4HANA as the organization’s integrated digital core. The scope was structured around complete business processes instead of just replacing the finance system.
Business area | Scope of the ERP transformation |
Finance and controlling | Integrated accounting, financial transactions, cost control, closing, consolidated management reporting and enterprise-wide financial visibility |
Financial planning | Planning, consolidation and reconciliation through SAP Business Planning and Consolidation |
Procurement | Purchase-to-pay processes connecting material requirements, purchasing, receipts, inventory and supplier accounting |
Inventory and warehousing | Visibility and control over raw materials, packaging materials and finished goods, including identification and tracking within warehouse operations |
Manufacturing | Plan-to-produce processes for pharmaceutical process manufacturing, production planning and accounting integration |
Quality management | Quality inspections, compliance-related controls and integration of quality activities with manufacturing and inventory |
Sales and distribution | Order-to-cash processing, distribution activities and improved access to sales and operational data |
CRM and field sales | Interfaces between SAP, CRM and the sales mobile application to improve visibility and reduce disconnected sales processes |
Plant maintenance | Maintenance planning and visibility for production assets and facilities |
Project management | Financial and operational control of projects and related expenditures |
Document management | Controlled management of enterprise and compliance-relevant documentation |
Human resources | Hire-to-retire processes and employee administration |
User experience | Standard and custom SAP Fiori applications to simplify transaction processing |
Technology platform | SAP S/4HANA deployed on Amazon Web Services using SAP Best Practices |
The scope’s strategic value lay in connecting the handoffs between functions. Purchasing transactions could update inventory and accounting; production activity could connect materials, quality and costs; sales and distribution activity could flow into receivables and reporting; and planning could use more consistent operational and financial information.
The solution integrated key processes including:
Procure-to-Pay
Plan-to-Produce
Order-to-Cash
Hire-to-Retire
Implemented Modules
SAP module | Business capability | Executive relevance |
FI — Financial Accounting | General ledger, accounts payable, accounts receivable, asset accounting and financial statements | Creates a common financial system of record and supports faster, more controlled closing |
CO — Controlling | Cost-center accounting, product and operational cost control, profitability and management reporting | Gives CFO and operating leaders better visibility into where costs are incurred |
MM — Materials Management | Purchasing, supplier transactions, material receipts and inventory management | Connects procurement decisions with material availability, inventory and working capital |
SD — Sales and Distribution | Customer orders, deliveries, billing and distribution transactions | Integrates commercial activity with inventory, fulfillment and finance |
PP-PI — Production Planning for Process Industries | Production planning and execution for formula- and process-oriented manufacturing | Aligns materials, production requirements and output in a pharmaceutical environment |
QM — Quality Management | Quality inspections, status controls and compliance-related quality processes | Integrates quality decisions with production and the release or movement of inventory |
PM — Plant Maintenance | Preventive and corrective maintenance planning, work execution and equipment records | Supports asset reliability and more predictable manufacturing capacity |
PS — Project System | Project planning, budgeting, expenditure tracking and reporting | Improves control over capital, expansion and other structured initiatives |
DMS — Document Management System | Controlled storage and management of business documents | Supports documentation discipline, auditability and access to approved information |
HCM — Human Capital Management | Employee administration and hire-to-retire processes | Connects workforce administration with the broader enterprise operating model |
Related capabilities included SAP Business Planning and Consolidation for financial planning, standard and custom SAP Fiori applications, integrated warehouse-management functionality, CRM integration, sales mobile integration and AWS infrastructure.
Additional Enhancements
Integration with Sales Mobile Application
CRM integration for improved sales visibility
Implementation of SAP Fiori for modern user experience
Deployment on AWS infrastructure
Implementation of SAP Business Planning & Consolidation (BPC) for financial planning
Ongoing SAP application maintenance and support
SAP S/4HANA Implementation Timeline
The broader client relationship has continued for more than six years and includes ongoing SAP application maintenance and support. The implementation phase was a 22-month-long engagement.
Program Stage | Milestone |
Enterprise transformation program | SAP S/4HANA 1909 implementation across manufacturing, finance, procurement, distribution and HR |
Core process enablement | Procure-to-pay, plan-to-produce, order-to-cash and hire-to-retire with accounting integration |
Functional deployment | FI, CO, MM, SD, PP-PI, QM, PM, PS, DMS and HCM |
Platform deployment | AWS-hosted SAP environment using SAP Best Practices |
Integration and extensions | CRM, sales mobile application, warehouse capabilities, SAP Fiori and BPC |
Transition to operations | Application maintenance, optimization and continuing support |
SAP S/4HANA Delivery Model
The implementation is a best-practice-led, AWS-hosted SAP S/4HANA deployment with connected external applications and continuing post-go-live support.
AWS-hosted enterprise core
Eitekh deployed SAP S/4HANA 1909 on Amazon Web Services and configured the platform using SAP Best Practices. This indicates a cloud-infrastructure model in which S/4HANA operated on AWS rather than remaining entirely on local data-center infrastructure.
Standardized core with targeted extensions
Eitekh combined SAP Best Practices with standard and custom SAP Fiori applications. The approach suggests that standard processes formed the core, while selected user-facing functions were adapted where the company required a more suitable transaction experience. Eitekh used Fiori to simplify and accelerate transaction processing.
Integrated application ecosystem
The ERP did not operate in isolation. Interfaces connected the S/4HANA environment with CRM and a sales mobile application, while BPC supported financial planning and consolidation. Warehouse-management capabilities connected physical material handling with ERP inventory records.
Continuing support model
Eitekh remained involved after implementation through application maintenance and support. For a multi-site manufacturer, this is important because ERP value realization continues after go-live through stabilization, incident resolution, process refinement, user support and controlled enhancements.
Business Outcomes
The SAP S/4HANA transformation delivered significant operational improvements across finance, manufacturing, and supply chain operations.
Business area | Reported result |
Financial planning and reconciliation | 75% reduction in the cycle time required for data reconciliation and financial planning in SAP BPC |
Financial close | Faster and more effective closing, more seamless financial transactions and consolidated management reporting |
Inventory management | Improved or real-time visibility across distribution centers |
Sales operations | Accelerated sales cycle and improved access to backend information, supported by CRM and mobile integration |
Regulatory reporting | Stronger reporting, audit readiness and compliance support |
Warehouse operations | Better identification and tracking of raw and packaging materials |
Enterprise integration | Procure-to-pay, plan-to-produce, order-to-cash and hire-to-retire processes connected with accounting |
Management decision-making | Faster access to integrated operational and financial information |
Scalability | AWS-hosted ERP foundation and continuing application support |
These improvements enabled leadership to make faster, data-driven decisions across the organization.
Finance impact
The most concrete result was the 75% reduction in reconciliation and financial-planning cycle time. That improvement matters because reconciliation is typically non-value-added work: finance teams spend time locating differences between systems instead of analyzing performance. A common transaction and reporting foundation reduced that burden and improved the timeliness of planning.
Faster closing and consolidated reporting also gave management a more current view across the organization.
Operations and working-capital impact
The new platform gave the company better visibility into inventory across its distribution network and connected warehouse activities with enterprise records. This created a foundation for better replenishment, purchasing and stock-allocation decisions.
Sales and distribution impact
CRM and mobile-sales integration gave commercial teams improved access to backend information and provided the enterprise with better visibility into sales activities.
Compliance and control impact
Quality management, document management, integrated accounting and more automated reporting improved audit readiness and reduced reliance on fragmented records. For a pharmaceutical manufacturer, that strengthened the connection between operations, quality and management reporting.
Strategic Value for Leadership
Leadership Role | Strategic Value |
CFO |
|
COO / Manufacturing Leaders |
|
Procurement Leaders |
|
CEO |
|
Implementation Challenges and Lessons Learned
The engagement illustrates several recurring lessons for mid-market manufacturers undertaking enterprise-wide ERP transformation.
Challenge | How it was addressed | Executive lesson |
Organizational adoption | Common end-to-end processes were introduced, Fiori applications simplified the transaction experience, and support continued after implementation | ERP adoption must be managed as an operating-model change. |
Legacy-system integration | S/4HANA was connected to CRM and the sales mobile application; warehouse and BPC capabilities were also incorporated | Interfaces must be governed as business processes, with ownership for data, reconciliation and exceptions. |
Multi-site process standardization | Core processes were integrated across five manufacturing plants and 38 distribution centers | Standardization must balance enterprise control with legitimate site requirements. |
Data consistency | Inventory visibility, consolidated reporting and reconciliation improved | ERP benefits depend on common master data and transaction discipline. |
Regulatory and quality requirements | PP-PI, QM and DMS were implemented, and reporting and audit readiness improved | Compliance requirements should be embedded in process design and testing rather than treated as post-go-live reporting tasks. |
User-experience complexity | Standard and custom Fiori applications were introduced to simplify processing | A technically correct system can still fail if users find it difficult to operate. UX decisions should reduce errors and make required controls easier to follow. |
Post-go-live sustainability | Eitekh continued to provide maintenance and support over a multi-year relationship | Go-live should be treated as the transition into a new operating model, not the end of the transformation. |
Legacy integration: what the engagement demonstrates
The program addressed the most visible integration gaps by connecting the SAP core to CRM, mobile sales, warehouse processes and financial planning. This reduced the separation between front-office activity, physical product movement and financial reporting.
The central lesson is that interface completion is not sufficient by itself. Management also needs controls that confirm:
Transactions are complete and processed once
Product, customer, supplier and location identifiers are consistent
Failed interfaces are detected and resolved
Operational totals reconcile to financial records
Changes to interfaces are tested across the full process
Legacy systems are retired or governed after go-live
Standardization before customization
Eitekh’s use of SAP Best Practices, combined with selected custom Fiori applications, reflects a sensible principle: standardize the transaction and data model wherever possible, then customize only where the user experience or a differentiated process justifies it.
For mid-market companies, this discipline reduces implementation risk and long-term maintenance burden. It also prevents historical workarounds from being rebuilt inside a more expensive platform.
Support is part of transformation value
The more-than-six-year relationship and continuing SAP support are strategically significant. Users require assistance as transaction volumes increase, new employees join, regulations change and the business adds locations, products or entities. Long-term value depends on controlled enhancement and process governance, not merely technical system availability.
Why Mid-Market Companies Choose SAP S/4HANA
For mid-market organizations, ERP modernization is often essential to support growth. SAP S/4HANA provides:
Real-time enterprise visibility
Integrated manufacturing and supply chain management
Strong regulatory compliance capabilities
Scalable architecture for expansion
Improved operational efficiency and working capital management
With the right implementation partner, companies can deploy enterprise-grade ERP systems while minimizing risk and disruption.
Why Eitekh Was Selected for SAP S/4HANA Implementation
The company outlines the following reasons why Eitekh was a credible fit.
End-to-end SAP capability
Eitekh is a North America-based technology consulting firm founded in 2013, with SAP, cloud infrastructure and enterprise integration among its principal capabilities. Its SAP practice covers advisory, readiness assessment, architecture, configuration, development, data migration, integration, testing, quality assurance, change management, user adoption, go-live support, optimization and ongoing application maintenance.
This lifecycle coverage aligned with the company’s needs. The engagement required more than ERP configuration: it required AWS deployment, legacy integration, user-experience design, planning and consolidation, manufacturing-process knowledge and post-go-live support.
Relevant manufacturing and pharmaceutical process depth
The client required integration across finance, materials, process manufacturing, quality, maintenance, sales, projects, documents and human resources. Eitekh’s implemented module set directly addressed those requirements, including PP-PI for process manufacturing and QM for quality operations.
That breadth matters in pharmaceutical manufacturing. A finance-focused implementation partner might produce reliable ledgers while leaving production, quality and inventory disconnected. Eitekh’s scope connected operational events to accounting and reporting.
Cloud and integration capability
Eitekh lists both SAP and AWS among its core areas of expertise. This supported an AWS-hosted S/4HANA environment integrated with CRM, mobile sales, warehouse processes and BPC. The ability to work across ERP, cloud infrastructure and connected applications reduced the risk of creating a modern ERP surrounded by the same unresolved system silos.
Experience with comparable mid-market transformations
For a mid-market packaged-food manufacturer, Eitekh implemented SAP Cloud ERP across procurement, production, quality, maintenance, sales, transportation and finance. These business areas closely comparable to a regulated consumer-products or pharmaceutical manufacturer.
For a diversified manufacturing conglomerate, Eitekh implemented SAP S/4HANA across 20 entities in an 11-month program, integrating finance, supply chain, production, projects and HR.
In another pharmaceutical engagement, Eitekh reports completing an SAP S/4HANA implementation in five months, covering finance, inventory and production.
These engagements demonstrate experience with the central risks the client faced: multi-entity governance, manufacturing integration, quality processes, supply-chain visibility, cloud deployment and legacy-system modernization.
Long-term partnership model
Eitekh’s continuing maintenance and support relationship was another relevant differentiator. A pharmaceutical ERP environment must remain stable while accommodating new reporting requirements, organizational expansion, process changes and application integrations. Eitekh’s reported relationship of more than six years suggests continuity from implementation through ongoing operations rather than a handoff immediately after go-live.
Taken together, Eitekh combined SAP process depth, manufacturing and quality experience, AWS and integration capability, a best-practice-led implementation approach, user-experience development and long-term application support. Those capabilities directly matched the operational scale, regulatory demands and integration complexity of the client's business.
Interested in transforming your ERP landscape with SAP S/4HANA?
Contact Eitekh to learn how SAP S/4HANA can help your organization scale, streamline operations, and gain real-time business intelligence.
Comments