A web client for subcontractors of one of state owned organizations of Moscow that interacts with the main SAP services, automating the organization work.

We had to create a web client that automates how the organization works with subcontractors. Core ERP stayed on SAP; external partners still needed one place to view contracts, raise material needs, exchange estimates and acts, and read reports without ERP credentials.
The solution had to generate and exchange documentation, consume REST APIs, and comply with safety standards. ESK worked closely with the main contractor; ABAP developers extended SAP on their side while we owned the SPA and integration layer — our first project touching SAP products.
Non-disclosure limits what we publish: we describe structure and outcomes, not sensitive domain specifics. Even under NDA the engagement added reusable integration patterns for OData-facing web frontends in regulated environments.
The SPA calls SAP-exposed REST endpoints documented and adjusted with the contractor’s ABAP team. We focused on safe data entry, consistent error handling, and UI flows that mirror how subcontractors already work on paper — without copying inefficient steps into software.
Security standards shaped transport, authentication, and hardening choices on the frontend build. Joint testing with SAP sandboxes kept integration defects out of production cutover.
Four months of delivery covered specification-aligned features plus change requests from the customer team. Because ABAP support was responsive, SAP-side blockers stayed manageable throughout implementation, UAT, and the move from pilot subcontractors to everyday production traffic.

The organization replaced ad hoc channels with one web client for subcontractor collaboration; documentation now moves through REST-connected SAP services instead of disconnected email threads and unsigned file exchanges.
ESK enriched its expertise in this vendor’s software stack — especially how to pair a modern React SPA with SAP-side API work under strict confidentiality, acceptance testing, and pilot rollout with real subcontractor focus groups.
Publicly we share only structure and facts: the project remains confidential under NDA, but it proved that a secure subcontractor portal on SAP services is deliverable with tight contractor cooperation, repeatable OData integration patterns, and production-grade document exchange workflows for future public-sector SAP clients.
Describe the task — we will name the timeline and price within an hour.