SAP-samples/abap-platform-refscen-flight-soap-client

ABAP Flight Reference Scenario for SOAP-Based Integration – Client System (SAP BTP ABAP Environment)

This repository contains the client-side implementation of the SOAP-based ABAP Flight Reference Scenario. The sample scenario demonstrates how to consume and expose SOAP services in ABAP Cloud (SAP BTP ABAP Environment).

The client system consumes services provided by a remote server system to create and cancel flight tickets. SOAP service consumption models are used for the outgoing SOAP messages, and a SOAP provider model is used for handling an asynchronous confirmation message. The source code is provided as abapGit repository.

The client triggers ticket creation synchronously (FlightTicketCreate) and ticket cancellation asynchronously (FlightTicketCancelRequestIn). The server replies asynchronously 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 client side of the scenario. For the corresponding server side implementation, see the Server System Repository.

Prerequisites

Make sure to fulfill the following requirements:

• ABAP System: SAP S/4HANA Cloud Public Edition or SAP BTP ABAP Environment
• User with the required business roles (SAP_BR_ADMINISTRATOR, SAP_BR_DEVELOPER, SAP_BR_CONF_EXPERT_BUS_NET_INT)
• Log on to the system with logon language English
• SAP Cloud Connector configuration
• ABAP Development Tools (ADT)
• Installed abapGit plugin for ADT (update site: http://eclipse.abapgit.org/updatesite/)
• An ABAP Cloud Project connected to your target system

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

Setup

1. In your ABAP cloud project, create the ABAP package /DMO/SP_TKTFLIGHT as the target package for the demo content. We recommend assigning a dedicated transport request for the import.
2. Open the abapGit Repositories view in your ABAP cloud project, then clone and pull this repository:
   1. Go to Window > Show View > Other... and choose abapGit > abapGit Repositories.
   2. In the abapGit Repositories view, choose the + icon (Clone abapGit Repository).
   3. Enter the repository URL https://github.com/SAP-samples/abap-platform-refscen-flight-soap-client.git and proceed.
   4. Select the package /DMO/SP_TKTFLIGHT as target package and assign a transport request.
   5. After the clone wizard finishes, right-click the new repository entry and choose Pull to import the repository contents.
3. Create the SOAP Service Consumption Models and the SOAP Provider Model by downloading the WSDL files from this repository and uploading each in ADT:
   1. DOC_INTF__DMO_II_SP_FLIGHT_TICKET_MANAG.wsdl → Service Consumption Model /DMO/SP_SOAP_TICKET_MANAGE (synchronous FlightTicketCreate)
   2. DOC_INTF__DMO_II_SP_FLIGHT_TICKET_CANCE.wsdl → Service Consumption Model /DMO/SP_SOAP_TICKET_CANCEL_REQ (asynchronous FlightTicketCancelRequestIn)
   3. DOC_CLAS__DMO_CO_SP_FLIGHT_TICKET_CANCE.wsdl → SOAP Provider Model /DMO/SP_SOAP_TICKET_CANCELCONF (asynchronous FlightTicketCancelConfirmOut)
   4. Copy the method implementations into the generated implementation class of the SOAP Provider Model, save and activate the class. For the source code, see Importing the Scenario to the Client System Using abapGit page of the Sample Scenario for SOAP-Based Integration.
4. Manually publish the communication scenarios after import.
5. Set up the Communication User, Communication System, and Communication Arrangements in the client system, using the two Communication Scenarios shipped with the repository:
   • /DMO/SP_TICKET_SOAP_CANCEL – outbound cancel request and inbound confirm; uses additional property TARGET with value TKT_CANCEL.
   • /DMO/SP_TICKET_SOAP_Manage – outbound create; uses additional property TARGET with value TKT_MANAGE.
6. Verify the setup by running the test console applications: /DMO/SP_TICKET_MANAGE_CONSOLE to create a ticket, then /DMO/SP_TICKET_CANCEL_CONSOLE to cancel and confirm.

ℹ️ The asynchronous FlightTicketCancelRequestIn request supports the additional property PROCESSING_ERROR to simulate transient failures so you can exercise the restart path from message monitoring.

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

• During the abapGit repository pull, the status may show Pulled with Errors because Service Consumption Models and the SOAP Provider Model have not yet been created. After creating these artifacts, activate all inactive objects in package /DMO/SP_TKTFLIGHT and try to pull objects with Action Add local object again. Repeat these steps until objects are imported and activated successfully. Do not delete generated proxy objects.
• Uploading the same WDSL file twice will cause an error. Ensure that all file names, object names, and properties match this documentation.
• Activation warnings for unsupported object types in abapGit (e.g., AIFD, AIFI, SPRV, SPRX, SUSI, WEBI, SRVC) can be ignored.
• Communication scenarios are not published automatically after import using abapGit → Publish locally.
• If the connection of the communication arrangement for flight ticket cancellation confirmation is not successful, update the logical port by updating the user and password. To do this, in the server system call transaction SOAMANAGER, search for the consumer proxy, and edit the corresponding outbound logical port. Then save the communication arrangement in client system to make the changes effective.

ℹ️ Connectivity issues related to Cloud Connector configuration are tracked in SAP Note 3583377.

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

How to obtain support

If you find a bug or have questions during setup, report an incident for the BC-DWB-PRX application component.

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.