Executive Summary
Organizations adopting SAP RISE often want to validate downstream integrations before obtaining access to production SAP systems. One common requirement is extracting SAP master and transactional data into AWS for analytics, lakehouse, and AI workloads.
This article documents the design and implementation of a SAP RISE mock environment using ASP.NET Core OData hosted on AWS EC2 and evaluates its compatibility with the AWS Glue SAP OData Connector.
The objective was to determine whether a standards-compliant OData service could be used to validate AWS Glue SAP OData integration without requiring access to a live SAP landscape.
Business Challenge
Many customers face the following challenges:
Delayed SAP environment provisioning
Restricted access to SAP RISE systems
Integration testing dependencies
Need for early data engineering validation
Without access to SAP systems, data engineering teams are unable to validate:
AWS Glue connectivity
Incremental extraction patterns
Data lake ingestion
Metadata discovery
Security configurations
To overcome these limitations, a mock SAP environment was developed.
Solution Architecture
Components:
Amazon EC2
ASP.NET Core 8
OData V4
Route53
SSL/TLS
AWS Glue
Amazon S3
Valid Public Domain
LetsEncrypt
Mock SAP Data Model
The implementation exposed SAP-style entities.
Customer Master (KNA1)
| Field | Description |
|---|---|
| KUNNR | Customer Number |
| NAME1 | Customer Name |
| LAND1 | Country |
| ModifiedDate | CDC Timestamp |
Material Master (MARA)
| Field | Description |
|---|---|
| MATNR | Material Number |
| MAKTX | Material Description |
| ModifiedDate | CDC Timestamp |
OData Service Design
The mock service exposed standard OData endpoints.
/odata
/odata/$metadata
/odata/KNA1Set
/odata/MARASet
Authentication was implemented using Basic Authentication to simulate SAP Gateway security.
AWS Glue Integration
A SAP OData Connection was configured in AWS Glue using:
HTTPS endpoint
Basic Authentication
OData metadata endpoint
SAP-style entity definitions
Connection validation completed successfully.
The connector successfully:
Established HTTPS connectivity
Authenticated against the service
Retrieved OData metadata
Queried service discovery APIs
Observed Connector Behavior
During testing, it became evident that the AWS Glue SAP OData Connector performs more than standard OData metadata discovery.
The connector attempted to invoke SAP Gateway-specific catalog APIs:
/odata/ServiceGroups('/IWBEP/ALL')/DefaultSystem/Services
This endpoint is typically exposed by SAP Gateway Catalog Services and is not part of the OData V4 specification.
Compatibility Enhancements
Several SAP-specific enhancements were introduced:
SAP Naming Conventions
KNA1Set
MARASet
SAP Business Keys
KUNNR
MATNR
SAP Service Discovery APIs
Custom catalog endpoints were developed to emulate SAP Gateway behavior.
HTTPS and Route53
A public endpoint was configured using Route53 and TLS certificates to replicate enterprise deployment patterns.
Results
The mock environment successfully validated:
- HTTPS Connectivity
- Authentication
- Metadata Retrieval
- AWS Glue Connectivity
- Service Discovery Invocation
However, the AWS Glue SAP OData Connector continued to expect SAP Gateway Catalog Service payloads beyond standard OData metadata.
The final validation error occurred during SAP catalog object parsing.
Key Finding
The AWS Glue SAP OData Connector should be viewed as a SAP Gateway-aware connector rather than a generic OData connector.
While standards-compliant OData services satisfy metadata requirements, complete compatibility appears to require SAP Gateway catalog services and SAP-specific metadata structures.
AWS Glue SAP OData Connector is tightly coupled with SAP Gateway Catalog Services and cannot be fully validated using a generic OData V4 service.
Recommendations
For Production Validation
Use:
SAP RISE
SAP S/4HANA
SAP Gateway
SAP BTP OData Services
for final certification testing.
For Development and POC Activities
A mock OData environment remains highly valuable for:
API development
Security validation
Incremental load testing
CDC implementation
S3 ingestion testing
Data pipeline development
Conclusion
This exercise demonstrated that AWS Glue SAP OData Connector integration can be partially validated using a custom OData service. However, complete validation requires SAP Gateway-compatible service catalogs and metadata structures.
For organizations awaiting SAP environment availability, a mock OData platform provides a practical approach for accelerating data engineering development while reducing dependency on SAP provisioning timelines.
0 Comments