abap-platform-refscen-flight-soap-server

ABAP Flight Reference Scenario for SOAP-Based Integration – Server System (S/4HANA On-Premise)

This repository contains the server-side implementation for the SOAP-based ABAP Flight Reference Scenario. The sample scenario demonstrates how to consume and expose SOAP services in ABAP Cloud.

The server system provides SOAP services to create or cancel flight tickets in the FlightTicket business object. It consumes a SOAP service in the client system to confirm successful ticket cancellation. The source code is provided as gCTS repository.

The server exposes ticket creation synchronously (FlightTicketCreate) and inbound ticket cancellation asynchronously (FlightTicketCancelRequestIn). It returns the cancellation confirmation asynchronously to the client via FlightTicketCancelConfirmOut. The ticket status moves I (Issued) → C (Cancelled).

The Sample Scenario for SOAP-Based Integration provides an overview of synchronous and asynchronous SOAP communication.

This repository contains the server side components of the scenario. For the corresponding client side implementation, see the Client System Repository.

Prerequisites

Make sure to fulfill the following requirements:

• ABAP System: SAP S/4HANA Private Cloud Edition or On-Premise System
• Git-Enabled Change and Transport System: Enabled gCTS in the server system
• Authorizations: This repository provides the PFCG roles ZDMO_SOAP_ADMIN and ZDMO_SOAP_DEVELOPER required for setup, configuration, and execution of the scenario. Download the roles from this repository, import them into transaction PFCG, and assign them to your user in the server system.

For more information, see the Prerequisites section in the SAP Help Portal documentation for this sample scenario.

Set Up Namespace

SAP uses a reserved namespace for the demo objects.

To enable the namespace in your customer system, follow the steps described in Setting Up a Namespace for Development. For step 8, enter the following values:

• Namespace: /DMO/
• Namespace Role : C
• Repair license: 32869948212895959389
• Short Text: Enter a suitable description for the namespace, for example SAP Demo Scenarios.
• Owner: SAP

Choose save and write the changes to a transport.

To be able to import /DMO/ objects into your system, set the system change option. Proceed as follows:

1. Go to Transport Organizer Tools (transaction SE03).
2. Go to Administration and start the program Set System Change Option.
3. In the Namespace/Name Range table search for the /DMO/ namespace.
4. In the column Modifiable change the entry to Modifiable.
5. Save the settings.

For more information, see Setting the System Change Option.

Setup SOAP Sample

1. Import the required trust certificates in transaction STRUST (GitHub server certificate, client-system server certificate). The certificates must land in the SSL Client (Anonymous) PSE.
2. Configure user-specific authentication in gCTS (Git API endpoint and personal access token).
3. Create the gCTS repository entry pointing to https://github.com/SAP-samples/abap-platform-refscen-flight-soap-server.git, then pull/import the scenario into the server system. Package /DMO/SP_TKTFLIGHT and its sub-packages will be created.
4. Configure Web Services in transaction SOAMANAGER:
   1. Activate the inbound service bindings DMO_FLIGHTTICKETMANAGEIN and DMO_FLIGHTTICKETCANCELREQUEST. Use HTTPS and User ID/Password authentication.
   2. Create the outbound logical port DMO_CO_SP_FLIGHT_TICKET_CANCEL for the asynchronous confirmation. Endpoint URL pattern: <Client API-URL>/sap/bc/srt/scs_ext/dmo/flightticketcancelconfirm.
5. Maintain the customizing table /DMO/SP_TKT_DEST in transaction SM30 to map the sender Business System ID (from incoming cancel requests) to the logical port created in the previous step. Without this mapping the server cannot route the asynchronous confirmation back to the correct client.
6. Create a technical user in SU01, create role ZDMO_SOAP_FLIGHT in PFCG, and assign the role to the technical user. The role grants the Web Service authorizations required to call the inbound bindings (entries /DMO/FLIGHTTICKETMANAGEIN/FLIGHT_TICKET_CREATE and /DMO/FLIGHTTICKETCANCELREQUEST/FLIGHT_TICKET_CANCEL_REQUEST_I).

For more information, see the Setting Up the SOAP Flight Reference Scenario section in the SAP Help Portal documentation for this sample scenario.

Known Issues

If the gCTS pull of the scenario into the server system fails, ABAP objects may not be created successfully due to errors. In this case, manually deploy the objects. For instructions, see Manually Deploy Objects.

For more information, see the Known Issues section in the SAP Help Portal documentation for this sample scenario.

How to obtain support

This project is provided "as-is": there is no guarantee that raised issues will be answered or addressed in future releases.

License

Copyright (c) 2026 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.