Ansicht
Dokumentation

SAPBC_REPLICATE_FLIGHTS - Replicate Flight Data in Travel Agency Systems (in Distributed Case)

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Title

Replicating Flight Data in Travel Agency Systems (in the distributed example)

Purpose

This report is used exclusively as part of the flight data model for demonstration and training purposes. It is notintended for productive operation.

This report enables the system to replicate changed flights (entries in SFLIGHT) in a distributed environment (ALE) to the other systems.

In a distributed environment, there is exactly one original system for every airline. (Here, multiple airlines can work in a single system. Travel agency systems, where no airline has an original system, can also exist.)

All flights for the airline (SFLIGHT) exist in its original system. In all other systems, only copies exist.

If certain flights are changed in the original system, you can then use this report to replicate the changed flights and therefore guarantee the consistency of the data. (The data for the flight data model is not connected to a change pointer. If flights are changed manually, then the person making these changes must also execute the report manually.)

Comment: The reports SAPBC_DATA_GENERATOR and SAPBC_DATA_GENERATOR_ALE must be used when generating an initial and consistent dataset for the flight data model. This report (SAPBC_REPLICATE_FLIGHTS) must only be used when replicating a later change to individual flights.

Integration

Prerequisites

- The flight data model is used in a distributed environment (ALE). The ALE distribution model and all other ALE settings (logical receivers, partner profiles, ALE outbound processing, ALE inbound processing) are entered correctly.

- Flight data is generated in all the systems involved, using the data generator (SAPBC_DATA_GENERATOR and SAPBC_DATA_GENERATOR_ALE).

- In the system, flights are changed at a later time. This involves flights from airlines that have their original in this system. No changes can be made to the flight plan (SPFLI), merely changes to the flights themselves (SFLIGHT). In this way, existing flights can be changed and new flights can be added. However, no existing flight can be deleted.

Features

Selection

In the input template, the flights that are to be replicated can be specified by airline, flight number, and flight data. Due to performance reasons, we recommend that you make the selection as precise as possible. (However, it is not necessarily a problem if unchanged flights are replicated.)

Standard Variants

Output

The flight data is replicated in all other systems. The receivers are determined from the ALE distribution model.

Activities

Example

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 2965 Date: 20240520 Time: 054449     sap01-206 ( 52 ms )