OData Experts in Berlin
in minutes from over 15,000 CVs with the power of AI.Hire experts who design OData services, connect SAP and Microsoft systems, and expose clean data models for apps and integrations. Get fast, precise matching with vetted, available freelancers.
Meet FRATCH Experts in Berlin, who have recently used OData
Egon Maier
Last position:
SAP S/4HANA Integration Consultant – MES / Siemens Opcenter Integration at Metso Corporation
- Supported an integration project between SAP S/4HANA and a MES / Siemens Opcenter system via Azure Middleware.
- Responsible for SAP-side analysis, mapping and provisioning of relevant data objects such as material master data, production orders and process orders using SAP standard APIs and OData services.
- SAP-side mapping for Material Master, Production Orders and Process Orders
- Usage of API_PRODUCT, API_PRODUCTION_ORDER_2_SRV and API_PROCESS_ORDER_2_SRV
- Consideration of SAP S/4HANA Advanced Available-to-Promise for order confirmation, production availability and downstream MES execution
- Support for SAP Gateway and OData service topics
- Interface coordination between SAP S/4HANA, Azure Middleware and MES / Siemens Opcenter
- Support for testing, monitoring and error analysis
- Worked with BTC Cockpit and Deloitte ASADEV Tool
Heiko Krain
Last position:
SAP development, Adobe form development at Arvato SE
- conversion of a function-group-based Adobe Interactive Forms framework to an object-oriented Adobe framework for documents in transport/logistics and dunning (FI)
- Adobe Lifecycle Designer 11.0.1 for SAP
- creating new and troubleshooting existing forms, function modules, programs, classes, and methods
- maintaining Smart Forms
- document printing, email sending, and file archiving
- message control for deliveries, orders, invoices, proforma invoices, and transports
- ticket system: Jira
- communication: Microsoft Teams
- migrating customers to a new SAP framework
- handling incident and change request tickets
- software: SAP ERP 6.0, SAP_ABA 7.5G, S4CORE 1.05
Beserithan Malabakan
Last position:
SD Development and CRM Interaction Center Development at Sanner GmbH
- Part-time 2-3 days/week
- Developments in the SD module and CRM Interaction Center
- Consulting, customizing in SD module
- Adapting Fiori applications in the SD module
- Approval workflow for credit memos: design, concept, implementation, customizing
- Credit memo request: object type BUS 2094
- If the credit memo request value is below a certain threshold -> automatic release and removal of billing block
- If the credit memo request value is above a certain threshold -> automatic determination of the responsible employee
- The employee receives a work item in their integrated inbox or in My Inbox (Fiori) -> the employee can reject, approve, or edit the credit memo request
- UML modeling in technical documentation
- Creating a Z-table for customer sample line items
- Merging COA1 (delivery) + COA2 (CAQ) forms and adding to the spool request as a single PDF
- Correcting workflow title according to NACE, fixing message "ZBMA title is displayed incorrectly in SBWP (Workplace)"
- Receiving PLM documents from an external PLM system, creating an RFC function module, storing PLM documents in the material master as GOS objects
- On releasing a production order, reading PLM documents from MM and saving them in a shared folder for the MES system
- Displaying the number of inspection methods in a popup when creating an order -> VA01/VA02
- Automatic stock reconciliation LVS IDOC INVCON
- Performing AQUA tests
- IDOC archiving for old IDOCs
- NL_PM_drawings and storing print output, informing MES via ZPPORDER IDOC, writing technical documents
- Using SD user exits, BADIs for various requirements
- Extending screens for customer requests via screen exits
- Creating message types for sales orders, purchase orders, and invoices
- Extending CRM Interaction Center Business Partner -> Overview -> Contract with customer-specific requirements
- New Fiori application departure control with data from Z-table and standard equipment tables, displaying a pie chart, calculating "vehicles in operation"
- Extending Interaction Center Business Partner -> Overview -> new tab on Overview Page with list tables for performance feedback, attachments from GOS objects
- Extending Interaction Center Business Partner -> Overview -> new tab on Overview Page with list tables for PM quality notifications, attachments from GOS objects
- Implementing BADIs in CRM
- File storage on SAP server/UNIX server
- Using BOL/GENIL architecture in CRM development
- Project language: German
Matthias Oehme
Last position:
Freelance Collaboration at Etengo (for Syna AG)
Consulting in the SAP EAM module as part of the migration to EON's oneERP S/4HANA system
Reviewing and cost estimation of customer-developed solutions (e.g., cockpit for EAM orders, document flow visualization)
Preparing EAM classification data for technical objects (technical locations, equipment) for migration to new classes
Georgi Litvinov
Last position:
Techno-functional MM/SD Consultant at GLIT Circle GmbH
- Implementation of the S/4HANA transformation (Brownfield) at CLAAS Agricultural Technology
- Implementation of the new supplier evaluation in S/4HANA including custom technical adjustments to customer-specific processes
- Conducting workshops with business units on technical and functional changes in S/4HANA, focusing on P2P processes and approval processes
- Preparing the new system, including customizing and converting customer-specific ABAP developments to Clean ABAP
Gopal Khandelwal
Last position:
SAP ABAP & Cloud Architect at parasus GmbH
- Concept and re-implementation of customer application over cloud and make the source code cloud ready
- Re-designing and putting a new architecture to overcome all the Team Scale findings and push ABAP code to ABAP cloud
- Converted the existing custom application code to ABAP cloud code and used ABAP Clean code guidelines
- Create a dynamic framework to call old vs new implementation from a Table maintenance to validate both implementations
- Utilized Key User Extensibility to seamlessly integrate multiple custom fields into a standard Fiori application, enhancing both the front-end and back-end GUI
Discover over 15,000 top freelancers
Statistics of experts using OData
Aggregated from the professional profiles of matched freelancers.
Experience
26 years (Germany: 19 years)
Position duration
1.3 years (Germany: 2.1 years)
Positions per freelancer
33 (Germany: 18)
Top business areas
Information Technology, Supply Chain Management, Procurement
Top industries
Information Technology, Professional Services, Healthcare
Certification focus areas
Information Technology, Operations, Procurement
Bachelor's degree or higher
100% (Germany: 80%)
Master's degree or higher
80% (Germany: 55%)
Doctorate
40% (Germany: 15%)
Certifications per freelancer
2 (Germany: 3)
Most common languages
German, English, Russian
Speak two or more languages
100% (Germany: 91%)
Based on our profile pool as of 30 Aug 2026.
Daily rate distribution
The chart shows how the daily rates of freelancers in this technology in Berlin are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows how many freelancers charge within that range.
Average rates of experts in Berlin using OData
Rates are based on recent contracts and do not include FRATCH margin.
The average daily rate is the mean of all daily rates from recent contracts of comparable freelancers on our platform.
The median daily rate is the middle value of all daily rates — half of comparable freelancers charge less, half charge more. Unlike the average, it is barely affected by outliers.
Calculated based on our freelancers’ daily rates as of 30 Aug 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
About the technology
OData basics
OData, short for Open Data Protocol, is a standard for building and consuming data APIs. It lets clients query, filter, sort, and expand data in a consistent way. Companies use it when they need structured access to business data across web apps, portals, and integrations.
Where it fits
OData is common in SAP landscapes, Microsoft environments, and enterprise integration work. It helps teams expose ERP, CRM, and master data in a controlled format.
- API design for business entities
- Data access for dashboards and portals
- Integration between systems and services
- OData v2 and OData v4 service work
What strong specialists do
Strong OData professionals know entity sets, navigation properties, metadata, and query options. They also understand pagination, authorization, and how to keep services stable under real application traffic. Clear modeling matters more than just making the endpoint work.
Typical project needs
Companies bring in freelance expertise when a service needs cleanup, a new data model, or a bridge between SAP and custom software. Berlin teams often need help for mixed local and remote delivery, especially when business stakeholders work in German but technical collaboration stays in English.
Ecosystem and tools
OData work often sits next to SAP Gateway, Microsoft Dataverse, Power Platform, ASP.NET, and Java-based service layers. Good specialists can trace issues across the data source, service layer, and client consumption. They also document filters, annotations, and version behavior so other teams can use the service correctly.
When to hire
If your team is struggling with slow queries, broken metadata, version mismatches, or unclear service contracts, it is time to bring in outside help. The same is true when you need to extend an existing OData service without breaking current consumers. Experienced specialists can fix the model, clean up the API, and leave a setup your team can maintain.
Frequently asked questions
Key details about OData, drawn from the questions we get asked most.
OData is used to expose structured business data through a standard API style. Companies use it for enterprise apps, reporting tools, portals, and system integration where clients need to query data in a predictable way. It is especially useful when many consumers must share the same service contract.
OData is often chosen when teams want standard query capabilities, metadata, and a strong data model out of the box. REST is usually more flexible in design, while GraphQL gives clients more control over the response shape. OData is a strong fit when enterprise systems need consistency more than custom endpoint design.
A strong OData specialist usually knows API design, data modeling, authentication, and the backend stack behind the service. In SAP or Microsoft environments, knowledge of SAP Gateway, Dataverse, Power Platform, or ASP.NET is often useful. They should also be able to read metadata and debug client queries.
OData work does not always need a large team, but it does need someone who understands the full service lifecycle. Simple fixes may be enough for small changes, while complex models, version upgrades, or SAP integrations need deeper expertise. The right person should have worked with real consumers, not just sample endpoints.
Yes, OData specialists often work well remotely because most tasks center on service design, debugging, and documentation. For Berlin-based teams, remote collaboration is common as long as access to systems, stakeholders, and test data is clear. On-site sessions can still help when business rules or legacy systems are hard to map.
A good OData implementation has a clear model, stable metadata, sensible filtering, and secure access control. It should be easy for clients to consume and simple for other experts to maintain. Good service design also avoids overcomplicated queries that hurt performance.
No, OData is common in SAP work, but it is not limited to SAP. It is also used in Microsoft ecosystems and in custom enterprise software where teams want standardized data access. The Open Data Protocol can fit many internal and external data-sharing use cases.
Look for someone who can explain service metadata, query behavior, authorization, and versioning in plain language. A strong OData freelancer should show real examples of fixing broken models, improving consumption patterns, or integrating with existing enterprise systems. Clear documentation and thoughtful trade-offs are good signs.
The average hourly rate of freelancers in Berlin, Germany who have used OData in their recent projects is 94 €, which corresponds to a daily rate of about 749 € based on an 8-hour working day.
Of the freelancers in Berlin, Germany who have used OData in their recent projects, 100% hold at least a Bachelor's degree, 80% hold at least a Master's degree, and 40% hold a doctorate.
On average, freelancers in Berlin, Germany who have used OData in their recent projects have 26 years of professional experience, with a single engagement typically lasting around 1.3 years.
The most common languages among freelancers in Berlin, Germany who have used OData in their recent projects are German (100%), English (100%), and Russian (17%).
The most common industries among freelancers in Berlin, Germany who have used OData in their recent projects are Information Technology (100%), Professional Services (100%), and Healthcare (83%).
The most common business areas among freelancers in Berlin, Germany who have used OData in their recent projects are Information Technology (100%), Supply Chain Management (100%), and Procurement (83%).
Main locations of FRATCH Experts, who have recently used OData
Our freelancers and interim experts are at home across the DACH region — available on-site in the major business hubs or fully remote. Choose a location to discover matched specialists, local market insights and up-to-date availability.
Request a free demo
Get in touch with the FRATCH team and we will get back to you within 4 hours.
Would you rather directly get in touch?
We always have the time for a call or email!

Munich