Académique Documents
Professionnel Documents
Culture Documents
Introduction:
There are basically two ways to enter data into Oracle: by typing it into a user interface (Java Form or
Web Page) or by taking a file and programmatically interfacing the data. Web ADI falls into the second
category in that it takes an Excel file and programmatically loads the data into Oracle. If you find it easier
to enter data into Excel than Oracle forms, you should look into using Web ADI.
To download a template you will use the following components: integrator, viewer, layout, and
content. Based on how the menu is setup, some of these components may default for you.
Integrator
The integrator defines what data you will be uploading to Oracle. Each integrator serves a
specific purpose and cannot be used to enter other data.
Viewer
The viewer is the Microsoft program you will use to enter data into the template
Layout
The layout is how the data columns are organized on the template. You have two main sections
to a template: a header and lines. The header information applies to all the lines when the data is
uploaded to Oracle.
Content
The content is a text file that you can import into your template. You can use this feature if you
have an external system that outputs text file and you want to import that into the template.
Pre-requisites for working on Development or use of WEBADIs
1.Check the value for profile option named BNE Allow No Security Rule and set the value to Yes
Business requirement :
CREATE OR REPLACE PACKAGE BODY APPS.xx_supplier_creation
AS
PROCEDURE supplier_import_pr (
p_vendor_number VARCHAR2,
p_vendor_name VARCHAR2,
p_enabled_flag VARCHAR2,
p_vendor_type_code VARCHAR2,
p_invoice_currency VARCHAR2,
p_payment_currency VARCHAR2,
p_term_id NUMBER,
p_payment_method VARCHAR2
)
AS
l_vendor_rec ap_vendor_pub_pkg.r_vendor_rec_type;
l_vendor_rec l_vendor;
l_return_status VARCHAR (10);
l_msg_count NUMBER;
l_msg_data VARCHAR2 (240);
l_vendor_id NUMBER;
l_party_id NUMBER;
error_exp EXCEPTION;
err_payment EXCEPTION;
BEGIN
l_vendor_rec.segment1 := p_vendor_number;
l_vendor_rec.vendor_name := p_vendor_name;
l_vendor_rec.ext_payee_rec.default_pmt_method := pi_payment_method;
l_vendor_rec.enabled_flag := p_enabled_flag;
l_vendor_rec.vendor_type_lookup_code := p_vendor_type_code;
l_vendor_rec.start_date_active := SYSDATE;
l_vendor_rec.invoice_currency_code := p_invoice_currency;
l_vendor_rec.terms_id := p_term_id;
l_vendor_rec.payment_currency_code := p_payment_currency;
fnd_msg_pub.initialize;
ap_vendor_pub_pkg.create_vendor (p_api_version => 1.0,
p_init_msg_list => 'F',
p_commit => 'F',
x_return_status =>
l_return_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data,
p_vendor_rec => l_vendor_rec,
x_vendor_id => l_vendor_id,
x_party_id => l_party_id
);
If pi_payment_method NOT IN
('Check','Clearing','Electronic','Wire','PrePurchase Aggrement')
then
RAISE err_payment;
END IF;
IF l_return_status = 'E'
THEN
RAISE error_exp;
END IF;
EXCEPTION
WHEN err_payment
THEN
raise_application_error ( 20000, 'Please check the Payment
Method in the List of values');
WHEN error_exp
THEN
raise_application_error (20000, l_msg_data);
WHEN OTHERS
THEN
raise_application_error (20000, SQLERRM);
END;
END;
/
1. Creating Integrator:
By using WEB ADI we can Upload, Download and Update the records into the system.
We should create our custom integrator according to our business requirement. Here we
need to upload data so Choose CREATE has Metadata Type.
Similarly enter the below details for other columns
Enter below Details and click on Oracle -> Upload available under toolbar
Now all the available fields will be displayed which has been used in the Procedure
parameters
The layout is divided into two important sections-
1. Required fields, where all mandatory parameters need to be aligned as per the requirement.
Instruct parameters can be used to provide some tips to users who are using this WEBADI for
uploading data
2. Optional fields are non mandatory fields, we need to select the ones which needs to be
available in our custom integrator
Click Next – To define certain important layout features – This functionality is available only to R12
users
Data Entry Rows – Using this property we can define the default number of rows which the ADI
will create when initialized, in 11i we user had to insert the new row in case of access data
Read Only – Using this feature we can define that which of the columns in our integrator will be
available as read only
Width – Using this option we can define the width of each of the columns which will be
available under the custom ADI
Move Up/Down – we can re-arrange the order of display of column in our integrator
Click next and click on create the document which will now download your custom integrator
Click on Create Document and please wait till the document has been created.
In the above example Payment method should be entered only within the mentioned list ,
which we described in the procedure. If user enters any of the other values it has been
captured and the error message has been notified to user for that particular row
Now the error has been cleared by changing the payment type has Check and
AP_SUPPLIERS or PO_VENDORS(View)
Integrator user name can be derived from bne_integrators_vl table with help of following query:
Click next and Create document and your custom integrator is available to user for uploading data
Thank You