1. Oracle EBS Training Customer WebADI Oracle EBS
Global Version 16-Jan-2019
Oracle EBS

2. Customer WebADI Features
The Customer WebADI is used for the following purpose 1. To create new customer 2. To add new site to existing customer (for cases where other entity already created the customer) 3. To add new site use to existing customer (for cases where previously customer is a Bill To only, and now a Ship To site need to be added

3. Customer WebADI Limitations
The Customer WebADI will NOT support the following 1. Creation of a new account within the same customer (even with different profile class) – eg. Trying to upload customer that has already been assigned to the organization 2. Creation of multiple Bill To site use for the same customer site 3. Changes / update to existing customer’s information or attribute

4. Customer WebADI Guide XXXX_AR_Customers > Customers > WebADI ① ③
1) Navigate to (R) XXX_AR_Customer > Customers > SEA WebADI Customer
Download WebADI Customer template, save as Excel Macro-Enabled Workbook (*.xlsm) ① ③ ②
2) Fill in all the necessary information, checked the Upl field to indicate this row is ready for upload.
Refer to next slide for more guidelines on the required fields
3) Run the Upload from the Add-Ins menu

5. Customer WebADI Important Fields
Fields to Take Note:
Operating Unit – defaulted to your responsibility profile, you can change if you are holding more than one company access (example TH_AR_Customer)
Customer Name, Customer Alias, Profile Class – these fields determine the customer, especially essential if customer already exist, please use the same name to add site or site use to existing customer.
Digitpin Contact Name, , Number – only for Digitpin customer, tag these information for Bill To
Purpose – Bill To or Ship To
Payment Term, Receivables & Revenue Account – Mandatory for Bill To
Tax Registration Number & Tax Code – Please fill in for Bill To. This will be set at site level only
Order Type & Price List – For companies using Order Management only

6. Create New Customer Customers > WebADI
Enter a unique, not-exist Customer Name. When the customer name already exist in the system, WebADI will error
New customer should be created with at least one site with purpose is Bill To, to enable it for usage in AR transaction

7. Add Site to Existing Customer
Customers > WebADI
This applies to existing customer that has already been created by other companies
The customer name must follow the existing customer name’s exactly. The alias, profile class, and other customer/account level information (such as DFF) will not be considered (existing data will not be changed if it is different, nor will the webADI data be rejected).

8. Add Site Use to Existing Customer Site
Customers > WebADI
This applies to existing customer site that wish to be added with another site use. Primarily, this is useful when existing customer is a bill-to only, and now wish to be set as ship-to also. Please note that standard Oracle validation will reject more than one site use for the same purpose (eg. One site 2 records of ship to will not be allowed)
Customer name and address will be used to validate the existing customer, other information that resides not in the site use level will not be considered.