Interfaces Basics

Interfaces Basics

 

Interfaces are used to integrate external systems and data conversion in Oracle Applications.

è  These can be used to either transfer data from Oracle Applications to a flat file or data from legacy system to Oracle Applications.

è Used extensively at the time of data conversion from legacy/old systems to a fresh implementation of Oracle Applications.

è  Used also at regular intervals when data transfer is from live systems if the system is not represented in Oracle Applications implementation.

 

TYPES OF INTERFACES

 

 Two major types of Interfaces

·         Inbound: To transfer data from external systems to Oracle Applications.

·         Outbound: To transfer data from Oracle Applications to external systems.

 

  Two other distinctions of Interfaces

·         Open Interface: If interface logic is provided by Oracle Applications, it is called an Open Interface.

·         Custom Interface: If the interface logic needs to be developed by the implementation team it is called Custom Interface.

 

OPEN INTERFACE LOGIC

 

  The data from source application is loaded into a database table (called Interface Table).

  The provided program logic validates the records.

  Any errors are transferred into another table (called Error Table).

  The correct records are then transferred through a process into destination application table.

 

INTERFACE COMPONENTS

 

Picture

 

  Source Application

·         You obtain data from a source application to pass on to a destination application for further processing and/or storage.

 

  Source Data Issues

·         Type of file, Size, Frequency of upload, Record length (variable or fixed), Delimiter, Data type of each field, Any unwanted data, Naming convention, Unique ness of file, Location of file and access on the file.

 

  Destination Application

·         You send data to destination application so that the application can perform further processing and/or storage.

 

  Interface Table

·         For inbound interfaces, the interface table is the intermediary table where the data temporarily resides until it is validated and processed into the destination application.

  Identifier Columns

·         Uniquely identify rows in the interface table and provide foreign key reference to both the source and destination applications.

 

  Control Columns

·         Control columns track the status of each row in the interface table, as it is inserted, validated, rejected, processed, and ultimately deleted.

·         WHO Columns are also called control columns.

 

  Data Columns

·         Stores the data that is being converted.

 

  Required Columns

·         Required Columns store the minimum information needed by the destination application to successfully process the interface row.

 

  Derived Columns

·         Derived columns are created by the destination application from information in the required columns

Oracle Cash Management: Internal Bank Creation API's

Oracle Cash Management: Internal Bank Creation

Oracle Internal Banks Conversions

Validations:
1)Country code
2)Operating Units
3)Currency
4)Different Code Combination id

API used

CE_BANK_PUB.CREATE_BANK
              (p_init_msg_list            => p_init_msg_list,
               p_country_code             => c2.country_code,
               p_bank_name                => c2.bank_name,
              -- p_bank_number              => '10202',
               x_bank_id                  => x_bank_id,
               x_return_status            => x_return_status,
               x_msg_count                => x_msg_count,
               x_msg_data                 => x_msg_data
              );
once bank is created bank_id will be returned as X_BANK_ID

we have to use this BANK_ID for creating bracnch

 CE_BANK_PUB.CREATE_BANK_BRANCH
            (p_init_msg_list              => p_init_msg_list,
             p_bank_id                    => p_branch_id,
             p_branch_name                => c2.branch_name,
             p_branch_type                => c2.acc_type,
             p_description                => c2.acc_desc,
             x_branch_id                  => x_branch_id,
             x_return_status              => x_return_status,
             x_msg_count                  => x_msg_count,
             x_msg_data                   => x_msg_data
            );

We will get branch_id as out paramter and this branch_id will be used
in creating bank accounts

   ce_bank_pub.create_bank_acct (p_init_msg_list      => p_init_msg_list,
                                 p_acct_rec           => p_acct_rec,
                                 x_acct_id            => x_acct_id,
                                 x_return_status      => x_return_status,
                                 x_msg_count          => x_msg_count,
                                 x_msg_data           => x_msg_data
                                );
here acct_id will be return as out paramter

Hope you understood the Internal bank increaion using API


Note:This document can be used only for refernece