SEGW — SAP Gateway Service Builder
SEGW is used to model and implement classic custom OData V2 services using entity types, associations and generated provider classes. It is most useful when maintaining an existing SEGW service or analyzing model-to-runtime behavior in a classic Gateway implementation. For reliable support work, start with the exact system, client, user and business context, then use the transaction's own status, document or log evidence before changing configuration or data.
This practitioner page covers SEGW, SAP Gateway Service Builder. It explains the transaction's operational purpose, the evidence to capture, the data or configuration objects that matter, and the failure patterns that commonly mislead SAP support teams.
Published 19 Sept 2026· 711 words
Esta página ainda não está disponível em português.
Purpose
model and implement classic custom OData V2 services using entity types, associations and generated provider classes. The useful way to think about SEGW is as part of an end-to-end business or technical flow, not as an isolated screen. Capture the exact organizational context, business object, user and timestamp before drawing conclusions, because those values determine which data and configuration the transaction reads.
When it is used
SEGW is typically used when maintaining an existing SEGW service or analyzing model-to-runtime behavior in a classic Gateway implementation. It is also valuable during test cycles because it provides a repeatable way to prove what SAP processed, selected or rejected. In production, narrow the selection to the affected population first and separate diagnostic/display actions from functions that can post, retry, clear or change system state.
How to use it in practice
- Open the existing project and understand its data model before regenerating runtime objects.
- Trace the entity set and operation to the DPC_EXT implementation used at runtime.
- Use $metadata to confirm the generated external contract.
- Regenerate only when the model changed and protect extension-class logic.
- For new development, evaluate CDS/RAP service exposure before creating another SEGW project.
Key data objects
These are the strongest anchors for a SEGW investigation. Record the values in the incident or test evidence so another consultant can reproduce the same conclusion and distinguish master data, configuration, authorization and transaction-state problems.
- project name — verify the exact value, organizational context and relationship to the affected document or interface.
- entity type/set — verify the exact value, organizational context and relationship to the affected document or interface.
- association — verify the exact value, organizational context and relationship to the affected document or interface.
- MPC/DPC classes — verify the exact value, organizational context and relationship to the affected document or interface.
- runtime artifacts — verify the exact value, organizational context and relationship to the affected document or interface.
How to prove it in the data
Use a three-part proof: first establish the source document or request and its exact keys; second show the status, accounting/interface record or runtime evidence produced by SAP; third show the corrected result using the same selection. Cross-check neighboring transactions and logs rather than relying on a single screen message. This prevents a successful retry, changed selection or unrelated master-data edit from being mistaken for the real fix.
ECC vs S/4HANA
SEGW is a legacy-but-common Gateway development tool on S/4HANA. Existing services remain supportable, while new clean-core development increasingly uses CDS and RAP service definitions/bindings. Availability does not automatically mean it is the preferred design for new work. On S/4HANA, pair familiar SAP GUI diagnostics with Fiori apps, Universal Journal, ODP, RAP/CDS or released APIs where those are the strategic surface for the process.
Common pitfalls and how to diagnose them
- Putting custom logic in generated base classes instead of *_EXT classes. Recheck the exact keys and chronology before changing configuration or reposting data.
- Regenerating and assuming custom code is safe without checking where it was placed. Recheck the exact keys and chronology before changing configuration or reposting data.
- Starting a new clean-core API in SEGW when a released/RAP approach is more appropriate. Recheck the exact keys and chronology before changing configuration or reposting data.
Whose problem this is
Primary ownership normally sits with the RAP CDS ODATA team. Bring in Basis for infrastructure/runtime issues, Security for authorization evidence, and ABAP or integration developers only when the transaction evidence points to custom logic or mapping. A useful escalation includes exact keys, timestamp, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/segwERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.