SAP Program RFTP_RAIL_PORTAL_SYNC - Report RFTP_RAIL_PORTAL_SYNC

Offline Synchronization with Order Data in Rail Reservation System
Offline synchronization, which can be run on a regular basis (forexample, using a batch job), compares modifications made to order datain the rail reservation system outside of the SAP system with theinternal SAP Travel Planning data and updates the information asrequired.
IDoc technology is available to you for this purpose. IDocs arecontainers for data exchange between SAP systems and third-partysystems. This new data is then used later to update or create travelplans for the orders in the rail reservation system.

Prerequisites
There must be an active connection to the return interface of theDeutsche Bahn Corporate Portal.

Importing Order Data from the Rail Reservation System and Creating theIDocs
To import the order data from the rail reservation system, use theprogram RFTP_RAIL_PORTAL_SYNC. This saves the data as an IDoc in atemporary buffer.

  • All orders created or modified on a specific date in the rail
    • reservation system can be accessed. Dates up to 10 days in the past canbe queried. It is not possible to query the current date. It istherefore recommended that you run at least one synchronization duringthis time.
    • You must also specify the grouping for office determination under which
      • the access to the rail reservation system is set up.
      • The option Display Only, No Synchronization has the effect that no
        • synchronization of the order data with the travel plans via IDoc is madeand only an overview of the order data for the specified date isdisplayed.

        Procedure for Setting Up the IDoc Control Parameters
        To set up the control parameters for IDocs, you need to make thefollowing settings:

        Define IDoc type and segment types (transaction WE30):
        Check that the entry TRPL_RAIL_PORTAL_ORDER_IDOC exists and that itcontains all segment types whose technical name begins withE1TRPL_RAIL_PORTAL_*.

        Define inbound process codes (transaction WE42):
        Create process code TRPL_RPO_IN using the button New Entries.

        Define characteristics of inbound function modules for processing theIDocs (transaction BD51):
        Use the button New Entries to create function moduleIDOC_INPUT_FITP_RAIL_PORTAL_O with input type 1. Activate the fieldDialog Allowed.

        Define EDI logical message types (transaction WE81):
        Create message type TRPL_RAIL_PORTAL_ORDER_MSG under New Entries andenter a short text such as "Inbound Rail Reservation System Orders".

        Assign message types to IDoc types (transaction WE82):
        Enter the following under New Entries:
        Message type: TRPL_RAIL_PORTAL_ORDER_MSG
        Basic type: TRPL_RAIL_PORTAL_ORDER_IDOC
        Release: 46C

        Assign inbound function module to message type and IDoc type(transaction WE57):
        Enter the following under New Entries:
        Module: IDOC_INPUT_FITP_RAIL_PORTAL_O
        TYP: F
        Basic type: TRPL_RAIL_PORTAL_ORDER_IDOC
        Message type: TRPL_RAIL_PORTAL_ORDER_MSG
        Direction: 2 (Inbound)

        Define function modules for inbound ALE-EDI (transaction BD67):
        Enter the following under New Entries:
        Process code: TRPL_RPO_IN
        Module: IDOC_INPUT_FITP_RAIL_PORTAL_O

        Define port for IDoc processing (transaction WE21):
        Define a port for the type Transactional RFC.

        Define partner profiles (transaction WE20):
        Since the IDocs are created and processed by the SAP system, you mustdefine both inbound and outbound parameters.
        Create a logical system (Partner type LS) with the following parameters:
        Outbound parameters:
        Message type: TRPL_RAIL_PORTAL_ORDER_MSG
        Receiver port: as defined in WE21
        Inbound parameters:
        Message type: TRPL_RAIL_PORTAL_ORDER_MSG
        Process code: TRPL_RPO_IN

        Processing the IDocs
        When processing the generated IDocs, the SAP system either updatesexisting travel plans or creates new ones. The IDocs can be processedmanually or automatically.

        Automatic Processing:
        This type of processing is recommended for live operation. You cancreate a batch job for the processing which then runs on a regularbasis. To do this you must activate the option Transfer IDoc immediatelyfor both the inbound and outbound parameters when setting up the controlparameters using transaction Partner Profiles (WE20).

        Manual Processing:
        Manual processing allows you to complete specific tests.
        If the parameter Collect IDocs is set for the outbound parameters, youmust start IDoc processing manually. Manual processing uses the programRBDAPP01 to send the IDocs to SAP Travel Planning, and therefore toupdate the rail order data in the SAP database.

        Error Control:
        You can display the status of the IDocs. To do this, choose Tools ->Business Communication -> IDoc Basis -> IDoc -> IDoc Lists (WE05). Youcan select any IDoc segments with errors and process them here.
        If you change any IDocs, save your changes and send them to SAP TravelPlanning using program RBDAGAIE.

        See also:
        For more information on IDoc Technology, see the SAP Library under IDocInterface / Electronic Data Interchange (BC-SRV-EDI).