Concepts
This variant is technically an enhancement of the variant Single Flight Booking (Proxy-to-Proxy).
The variant Single Flight Booking (with IDoc) addresses most of the technical concepts that are addressed in the variant Single Flight Booking (with Proxy). See Concepts.
This variant also addresses additional concepts. This section gives you an overview of the additional technical concepts.
The table below contains the following information for each concept:
● A hyperlink to the general description of the concept
● A description of how the concept is implemented in the process integration scenario
The process integration scenario is in the ES Repository under the name SingleFlightBooking (in the software component version SAP Basis 7.10, namespace http://sap.com/xi/XI/Demo/Agency). Navigate forward to find all the objects used by the process integration scenario (interface objects, mapping objects).
The airline that is integrated into the process by the IDoc adapter uses IDocs to exchange messages.
The corresponding proxies for the message interfaces used are in the SAP system in ABAP proxy generation under the software component version SAP Basis 7.10. For the travel agency, the outbound interface is BookingOrderRequest_Out and the inbound interface is BookingOrderConfirmation_In in the namespace http://sap.com/xi/XI/Demo/Agency.
Design Time
Concept |
Description |
|
Multiple component views are defined for the process integration scenario SingleFlightBooking . The component view ABAP_Proxy_2_IDoc contains the definitions of the connections that are based on the message exchange between service interfaces and IDoc interfaces. |
The IDoc interfaces used are implemented in the SAP system. Descriptions of the IDoc interfaces are imported to the Enterprise Services Repository and are located in the software component version SAP Basis 7.10 underImported Objects. This means that the IDoc interfaces are also available in the Enterprise Services Repository and can be referenced by other design objects (for example, mapping objects). |
|
|
The mappings used in the process integration scenario map service interfaces to IDoc interfaces and the other way around. The IDoc adapter automatically fills the IDoc header. Therefore, it is not necessary to supply the IDoc header during mapping. |
Process Integration
ScenarioConfiguration Time
All descriptions for configuration time are based on the SAP standard configuration.
Concept |
Description |
Using
|
All configuration data for the process integration scenario is grouped into a configuration scenario in the Integration Directory. You can execute the whole configuration step-by-step by using the model configurator. Use the process integration scenario SingleFlightBooking as a template. |
Configuration Objects with an IDoc Interface in the Key |
The receiver determination and the interface determination use IDoc interfaces in the key. |
Receiver agreements for all existing sender/receiver pairs are defined in the standard configuration. Each receiver agreement defines the technical details for outbound processing of the message by means of its assigned communication channel. Since a receiver expects the IDoc format, the corresponding receiver agreements are assigned a communication channel with the adapter type IDoc. Therefore, a sender agreement to specify inbound processing in more detail is not necessary for senders that send messages in IDoc format. |
Runtime
Concept |
Description |
Communication Based on the Adapter Runtime (IDoc Adapter) |
The SAP systems of the travel agency and an airline are based (in the standard configuration) on AS ABAP. Therefore, you can use ABAP proxies to connect them to the Integration Server. You connect the system of the other airline to the Integration Server by using IDocs. In the SAP standard configuration this system is also based on AS ABAP. |
|
The IDoc adapter provides additional message monitoring options. |