Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 48 views

    Interface: Types of Interfaces

    Uploaded by

    ashibek
    There are two types of interfaces: inbound and outbound. Inbound interfaces transfer data from external or legacy systems to Oracle Applications, while outbound interfaces transfer data from Oracle Applications to external systems. The document then outlines 8 steps to set up an interface, including getting data files, mapping columns between the systems, loading to staging and pre-interface tables with validation, and executing SQL to load and validate the data.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Interface: Types of Interfaces

    Uploaded by

    ashibek
    48 views3 pages
    There are two types of interfaces: inbound and outbound. Inbound interfaces transfer data from external or legacy systems to Oracle Applications, while outbound interfaces transfer data from Oracle Applications to external systems. The document then outlines 8 steps to set up an interface, including getting data files, mapping columns between the systems, loading to staging and pre-interface tables with validation, and executing SQL to load and validate the data.

    Original Description:

    23083094-INTERFACE-V2

    Original Title

    23083094-INTERFACE-V2

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    There are two types of interfaces: inbound and outbound. Inbound interfaces transfer data from external or legacy systems to Oracle Applications, while outbound interfaces transfer data from Oracle Applications to external systems. The document then outlines 8 steps to set up an interface, including getting data files, mapping columns between the systems, loading to staging and pre-interface tables with validation, and executing SQL to load and validate the data.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    48 views3 pages

    Interface: Types of Interfaces

    Uploaded by

    ashibek
    There are two types of interfaces: inbound and outbound. Inbound interfaces transfer data from external or legacy systems to Oracle Applications, while outbound interfaces transfer data from Oracle Applications to external systems. The document then outlines 8 steps to set up an interface, including getting data files, mapping columns between the systems, loading to staging and pre-interface tables with validation, and executing SQL to load and validate the data.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 3

    INTERFACE

    INTERFACE

    Legacy VS Apps

    Inbound
    LA

    Within Apps

    Outbound
    A L

    Open

    API

    Types of Interfaces
    There are two types of Interfaces in general:
    1.)
    Inbound Interfaces
    2.)
    Outbound Interfaces

    Tools required:
    -

    SQL Loader
    UTL File

    Inbound Interfaces They are designed to transfer data from external or legacy
    system to Oracle Applications.
    Outbound Interfaces They are designed to transfer data from Oracle Applications
    to external or legacy system.

    Detailed Steps
    STEP 1:
    Using FTP get the file having the data related to the transactions entered without
    including the header and tail section. (STRINGS COMMAND UNIX can be used)
    Get the file in .DAT or EXCEL format.
    INTERFACE FORMATS:
    - Single File
    - Multiple Files.

    STEP 2:
    Example Payroll to GL
    Go to Oracle Apps set the trace on.
    Enter 10-12 unique transactions manually in Oracle Apps GL (Through Front End)
    and Check for:
    1.)
    Mandatory columns (Through Front End)
    2.)
    Columns automatically updated by Oracle Apps.
    3.)
    Columns from legacy system, which are to be omitted.
    4.)
    Columns to be added in Oracle APPS not included in the
    External or legacy system.

    Take the journal listing of journals, which have been entered.


    Post the entries in GL (or whatever module).
    Make a note of all the form names and base table names, which have been
    affected by the above entries from trace file using TKPROF.

    Generate some reports from Oracle APPS for the above entries.
    STEP 3:
    Make an Out Bound Interface to collect data from APPS and check for the entries
    from the external or legacy system.
    Use PL/SQL to write an Out Bound Interface.
    Verify the results of the Out Bound Interface with an Functional expert.
    There are two types of interfaces within Oracle Apps
    - OPEN Interface
    - Interface using API
    STEP 4:
    Using AIM Documentation prepare a mapping document to check how the columns
    from legacy system and Oracle APPS are to be mapped.
    Example: COLXX of legacy will map to column COLYY of table TT in APPS.
    WHO columns in APPS like REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION,
    PROGRAM_UPDATE_DATE, which are not there in the legacy system, are to be
    included in APPS.
    STEP 5:
    After mapping create a stage area (staging table, without constraints and for the
    staging table the data type for all columns should be varchar2).
    Transfer data from .DAT file to this table.
    Maintain an ERROR table.

    STEP 6:
    After that load the data from staging table to pre interface table. This pre interface
    table will be as per the one in the module (GL_INTERFACE). In pre- interface 95%
    validation has to be done.
    (The tables should be populated in apps schema OR CUS schema with synonym in
    APPS)
    Here also an error table has to be maintained and also
    Exceptions have to be defined for handling all errors.
    STEP 7:
    After that the data should be loaded from pre interface table to interface table. Here
    we will have to trap the
    remaining 5% errors, which are mainly due to constraints that were not handled
    from staging to pre interface.
    STEP 8:
    Take the trace file using TKPROF and execute the various SQLs individually in SQL
    plus environment, check the
    output of individual SQLs with the entries made in apps and the data in the legacy
    system.

    You might also like