Scribd
Upload
9 views

oracle_a_Part4

Uploaded by

Ali Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
9 views

oracle_a_Part4

Uploaded by

Ali Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

How to Define An Importer Returning Error Messages to the Oracle Web Applications Desktop Integrator Document

Introduction
This document explains with an example how to define an integrator whose importer returns
error messages for any spreadsheet rows that failed to import.

The intended audience of this document is custom integrator developers who are familiar with
Oracle E-Business Suite, and Oracle Web Applications Desktop Integrator. Developers should
also have good knowledge of the business area for which they are designing the integrator.

Integrator developers should review the following documentation:


 Oracle Web Applications Desktop Integrator Implementation and Administration Guide,
Release 12.1.3, Part No. E12902-04
 Oracle E-Business Suite Desktop Integration Framework Developer's Guide,
Release 12.1.3, Part Number E15877-02

Custom integrators are defined using Oracle E-Business Suite Desktop Integration Framework
.

The integrator will be defined in three phases:


 Preparing database and application objects
 Phase A: Defining an integrator that downloads and uploads data
 Phase B: Defining an integrator importer that returns error messages

The reason for the three-phase strategy is to divide the integrator definition into smaller sub-
tasks, test the integrator after each phase is completed to ensure it works, and increase its
complexity in the next phase. This strategy simplifies the analysis and resolution of possible
errors while running the integrator.

Integrator Purpose
The Integrator defined in this example performs these operations:
 Creates a data document as a formatted spreadsheet on the desktop
 Downloads data from BNE_VIEWERS_B into the document that was created
 Uploads data from the document to the test table BNE_TEST_IMPR_INTERFACE
 Processes data in the BNE_TEST_IMPR_INTERFACE table, marking some of the
rows uploaded as having errors during import
 Returns errors to the desktop application
 Displays the errors for the rows that failed to import

At the end of Phase A, the integrator will be able to create the template document, download
data, and upload data. Once Phase B is completed, the integrator will be able to perform the
import data processing.

Preparing Database and Application Objects


For this sample integrator you must create a new database table, include this database table in
FND tables, create a sequence, and grant privileges on the new objects to the APPS user.
This integrator will define a PL/SQL API procedure importer. The errors reported by the

You might also like