转载几篇关于供应商导入的文章
供应商导入简例
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Oracle ERP最佳技术实践之AP模块供应商数据导入参考
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Vendor Interface
Existing and new vendors must be loaded into the Oracle Payables application to support payables activities. Two methods may be used to enter vendors into Oracle Applications, manual entry and direct loading using a customized loader program.
- Manual Vendor Loading: Use the Enter Vendor window. Using this functionality vendor header information as well as vendor site information can be entered.
- Vendor Interface: When interfacing vendors into Oracle Applications two tables must be loaded the PO_VENDORS and PO_VENDOR_SITES_ALL. The vendor table contains all header information and the site table contains information about each the vendor locations such as "ship to" and "bill to". Using this method makes sense when the volume of new vendors is large. Note: Interfacing this information is not supported by Oracle.
- Those who are in 11.5.10 they will find yet another method ie by interface.
You have to Load data into the staging tables first ie.AP_SUPPLIERS_INT - Supplier Information
AP_SUPPLIER_SITES_INT - Supplier Sites Information ,AP_SUP_SITE_CONTACT_INT - supplier Contact details This uses Vendor ID, Vendor Site Code to relate the contacts to specific vendor. Once data get loaded three interface program should be kicked out which is as- Supplier Open Interface Import.
- Supplier Sites Open Interface Import
- Supplier Site Contacts Open Interface Import
Supplier , Supplier site open interface
source:http://kutuboracle.blogspot.jp/2010/02/supplier-supplier-open-interface.html
Defaults:
The intent of the Supplier Open Interface Import is to emulate the entry of Suppliers, Sites, and Contacts through the Supplier Entry form as closely as possible. As such, there are many values that will be automatically defaulted if notprovided by the user.
These defaults for Suppliers can come from AP_SYSTEM_PARAMETERS_ALL, FINANCIALS_SYSTEM_PARAMS_ALL, PO_SYSTEM_PARAMETERS.ALL, RCV_PARAMETERS, or hard-coded values. As these source tables are organized by operating unit and the supplier data is not, the Suppliers Open Interface Import program assigns a default organization to each run based on the responsibility of the user initiating the concurrent request. This is necessary in order to determine which default values to
assign to supplier records.
The defaults for Supplier Sites generally come from the Supplier record. However, in certain cases due to multiple organizations considerations, it is necessary to default values for Supplier Sites from AP_SYSTEM_PARAMETERS_ALL or FINANCIALS_SYSTEM_PARAMS_ALL.
Validations:
As with defaults, the validations performed by the Open Interface programs are intended to emulate the processing done by the Supplier Entry form. In addition to checks done at the database level for correct data types, these validations include
checks performed against existing lookup values or values derived from other tables. When these types of validations are done, a check is performed to make sure that the value supplied is that of an active record, a record that has not been end-dated or disabled.
Details of the validations performed can be found in the descriptions for the AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT, and AP_SUP_SITE_CONTACT_INT tables.
Rejections:
If an invalid value is encountered when the concurrent process is evaluating each row, the ’REJECT_CODE’ column is populated with the relevant rejection message and the ’STATUS’ is updated to ’REJECTED’. Processing on that row then stops and the
program moves on to the next row.
1. Fisrt Create suppliers with minimum information as mentioned below:
Insert into AP_SUPPLIERS_INT(VENDOR_INTERFACE_ID,VENDOR_NAME)
2. Create Supplier site with minimum information as mentioned below:
Insert into AP_SUPPLIER_SITES_INT(VENDOR_ID,VENDOR_SITE_CODE,ORG_ID)
If using in multi org environment enter value for SHIP_TO_LOCATION_CODE, BILL_TO_LOCATION_CODE.
In our case we have used below info:
Note: I have selected many columns but these are not required. After payment_currency_code no coulmn is required except Org_id, supplier_notif_method, email_address
insert into AP_SUPPLIER_SITES_INT
(vendor_id,VENDOR_SITE_CODE,ATTENTION_AR_FLAG,ADDRESS_LINE1,ADDRESS_LINE2,ADDRESS_LINE3,CITY, STATE, ZIP,PROVINCE,COUNTRY,AREA_CODE, PHONE,FAX,FAX_AREA_CODE, PAYMENT_METHOD_LOOKUP_CODE,INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE,ATTRIBUTE1,ATTRIBUTE2,ATTRIBUTE3,ATTRIBUTE4,VAT_REGISTRATION_NUM,ORG_ID,ADDRESS_LINE4,COUNTY, SUPPLIER_NOTIF_METHOD,EMAIL_ADDRESS)
select * from XX_BCS_SITE
create table XX_BCS_SITE (
vendor_id VARCHAR2(200),
vendor_site_code VARCHAR2(200),
attention_ar_flag VARCHAR2(200),
address_line1 VARCHAR2(200),
address_line2 VARCHAR2(200),
address_line3 VARCHAR2(200),
city VARCHAR2(200),
state VARCHAR2(200),
zip VARCHAR2(200),
province VARCHAR2(200),
country VARCHAR2(200),
area_code VARCHAR2(200),
phone VARCHAR2(200),
fax VARCHAR2(200),
fax_area_code VARCHAR2(200),
payment_method_lookup_code VARCHAR2(200),
invoice_currency_code VARCHAR2(200),
payment_currency_code VARCHAR2(200),
attribute1 VARCHAR2(200),
attribute2 VARCHAR2(200),
attribute3 VARCHAR2(200),
attribute4 VARCHAR2(200),
vat_registration_num VARCHAR2(200),
org_id VARCHAR2(200),
address_line4 VARCHAR2(200),
county VARCHAR2(200),
supplier_notif_method VARCHAR2(200),
email_address VARCHAR2(200))
Insert into XX_BCS_SITE values
('1351','DAMMAM','N','PO BOX 1053, DAMMAM 31431','','',
'DAMMAM','','31431','','SA','+966 3','8472466','8471812',
'8471293','CHECK','SAR','SAR','8472466 8471812 8471293',
'','','TEL :8472466 8471812FAX 8471293',
'DA0108','126','','','','accounts@cmdc.com.sa');
3.Enter supplier contact information as below:
create table XX_BCS_SUP_CONTACT (
vendor_site_id VARCHAR2(200),
FIRST_NAME VARCHAR2(200),
MIDDLE_NAME VARCHAR2(200),
LAST_NAME VARCHAR2(200),
TITLE VARCHAR2(200),
area_code VARCHAR2(200),
phone VARCHAR2(200),
org_id VARCHAR2(200))
Insert into XX_BCS_SUP_CONTACT values ('517','','','MS. PAMELA VENGLAR','','','','292');
Insert into XX_BCS_SUP_CONTACT values ('1403','','','MR. OSAMA SAMI','','','','292');
INSERT INTO AP_SUP_SITE_CONTACT_INT VENDOR_SITE_ID,FIRST_NAME,MIDDLE_NAME,LAST_NAME, TITLE,AREA_CODE,PHONE,ORG_ID) SELECT * FROM XX_BCS_SUP_CONTACT
Update AP_SUP_SITE_CONTACT_INT
set STATUS = 'NEW'
Note: For all the above three tables STATUS must be NEW. While submitting the request Supplier Open Interface Import,Supplier
Sites Open Interface Import,Supplier Site Contacts Open Interface Import the Import Option in the parameter must be NEW.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Supplier & Supplier Sites Interface/Conversion
source:http://oraclemaniac.com/2012/09/03/supplier-supplier-sites-interfaceconversion/
In this article we shall discuss how to interface Supplier and Supplier Sites into Oracle using Open Interface tables and APIs.
Open Interface method
Application: Payables
Tables used:
AP_SUPPLIERS_INT (populates PO_VENDORS),
AP_SUPPLIER_SITE_INT (populates PO_VENDOR_SITES),
HR_ALL_ORGANIZATION_UNITS (cf organization_id) ,
GL_CODE_COMBINATIONS (cf code_combination_id)
PO_LOOKUP_CODES (cf LOOKUP_CODE)
PER_PEOPLE_F (cf PERSON_ID)
Step 1: Check for vendors that already exist
SELECT * FROM PO_VENDORS WHERE VENDOR_NAME = ‘ENTER VENDOR NAME’;
Step 2: Entering supplier / employee by classifying accordingly
For entering employee as supplier
|
1
2
3
4
5
6
7
8
9
|
INSERT
INTO
ap_suppliers_int
(vendor_name, segment1, vendor_interface_id, vendor_type_lookup_code, employee_id
)
VALUES
(
'VENDOR2'
,
--NAME OF VENDOR
'V02'
,
--SUPPLIER NUMBER
21,
-- UNIQUE SUPPLIER INTERFACE RECORD,
'Employee'
,
--LOOKUP_CODE
234
-- PERSON_ID OF EMPLOYEE
);
|
For entering supplier (who is not an employee)
|
1
2
3
4
5
6
7
8
|
INSERT
INTO
ap_suppliers_int
(vendor_name, segment1, vendor_interface_id, vendor_type_lookup_code
)
VALUES
(
'VENDOR2'
,
--NAME OF VENDOR
'V02'
,
--SUPPLIER NUMBER
21,
-- UNIQUE SUPPLIER INTERFACE RECORD,
'Supply'
--LOOKUP_CODE
);
|
Submit request Supplier Open Interface Import
Step 3: Query to retrieve vendor id
|
1
2
3
|
SELECT
po.vendor_id, po.vendor_name, po.segment1
FROM
po_vendors po, ap_suppliers_int supp
WHERE
supp.segment1 = po.segment1
|
Step 4: Entering the site information and account information for suppliers
|
1
2
3
4
5
6
7
8
9
|
INSERT
INTO
ap_supplier_sites_int
(vendor_interface_id, vendor_site_code, vendor_id, org_id, address_line1, address_line2, address_line3, city, state, zip,
country,
accts_pay_code_combination_id,
--LIABILITY ACCOUNT
prepay_code_combination_id
-- PREPAYMENT ACCOUNT
)
VALUES
(21,
'VENDOR23'
, 16044, 141,
NULL
,
NULL
,
NULL
,
NULL
,
NULL
, 123456,
NULL
, 1418, 1419
);
|
Submit request Supplier Sites Open Interface Import
After importing the suppliers you can check Supplier master.
Navigation: Suppliers > Entry
Click on Sites button
A sample interface script is given below:
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
|
DECLARE
--Cursor 1 which retieves data from header table to insert into receiving header table
p_header_id NUMBER;
p_counter NUMBER := 0;
p_header_error NUMBER := 0;
p_line_error NUMBER := 0;
p_header_sequence NUMBER;
p_org_id NUMBER;
p_message VARCHAR2 (200);
p_count NUMBER := 0;
p_pay_code_combination_id NUMBER := 1074;
p_prepay_code_combination_id NUMBER := 1075;
l_country VARCHAR2 (2);
CURSOR
c2
IS
SELECT
vendor_name, vendor_type_lookup_code, site, country, address1, address2, address3, city, state, pin, liability_account_id
FROM
xx_vendor_sites_others_b
WHERE
flag
IS
NULL
ORDER
BY
vendor_name;
FUNCTION
get_country_code (p_country
IN
VARCHAR2)
RETURN
VARCHAR2
IS
BEGIN
SELECT
territory_code
INTO
l_country
FROM
fnd_territories_vl
WHERE
territory_short_name = INITCAP (p_country);
RETURN
l_country;
EXCEPTION
WHEN
NO_DATA_FOUND
THEN
l_country :=
'IN'
;
END
;
BEGIN
FOR
c2_rec
IN
c2
LOOP
BEGIN
SELECT
COUNT
(*)
INTO
p_count
FROM
ap_suppliers_int
WHERE
vendor_name = c2_rec.vendor_name;
END
;
IF p_count = 0
THEN
BEGIN
INSERT
INTO
ap_suppliers_int
(vendor_interface_id, vendor_name, vendor_name_alt, segment1, summary_flag, enabled_flag,
vendor_type_lookup_code, one_time_flag, ship_to_location_id, bill_to_location_id, terms_id, set_of_books_id,
always_take_disc_flag, pay_date_basis_lookup_code, pay_group_lookup_code, payment_priority,
hold_all_payments_flag, hold_future_payments_flag, start_date_active, payment_method_lookup_code,
terms_date_basis, qty_rcv_tolerance, qty_rcv_exception_code, enforce_ship_to_location_code,
days_early_receipt_allowed, days_late_receipt_allowed, receipt_days_exception_code, receiving_routing_id,
allow_substitute_receipts_flag, allow_unordered_receipts_flag, bank_charge_bearer, match_option, allow_awt_flag
)
VALUES
(ap_suppliers_int_s.NEXTVAL,
UPPER
(c2_rec.vendor_name),
UPPER
(c2_rec.vendor_name), c2_rec.segment1,
'N'
,
'Y'
,
c2_rec.vendor_type_lookup_code,
'Sub-Contractor'
,
'N'
, 142, 142, 10000,
1001,
'N'
,
'DISCOUNT'
,
'HIGH PRIORITY'
,
99,
'N'
,
'N'
,
'15-AUG-2005'
,
'CHECK'
,
'Invoice'
, 10,
'WARNING'
,
'NONE'
, 2, 5,
'WARNING'
,
1,
'N'
,
'Y'
,
'I'
,
'R'
,
''
);
/*
UPDATE
XX_VENDOR_SITES_OTHERS_B
SET
FLAG=
'Y'
WHERE
VENDOR_NAME=C2_REC.VENDOR_NAME;
*/
COMMIT
;
SELECT
ap_suppliers_int_s.CURRVAL
INTO
p_header_sequence
FROM
DUAL;
EXCEPTION
WHEN
OTHERS
THEN
ROLLBACK
;
p_message := SUBSTR (SQLERRM,
1,
200
);
UPDATE
xx_vendor_sites_others_b
SET
flag =
'N'
,
error_message = p_message
WHERE
vendor_name = c2_rec.vendor_name
AND
vendor_type_lookup_code = c2_rec.vendor_type_lookup_code
AND
site = c2_rec.site;
COMMIT
;
p_header_error := 1;
END
;
END
IF;
BEGIN
SELECT
code_combination_id
INTO
p_pay_code_combination_id
FROM
gl_code_combinations
WHERE
segment1 ||
'.'
|| segment2 ||
'.'
|| segment3 ||
'.'
|| segment4 = c2_rec.lia_account_code;
SELECT
code_combination_id
INTO
p_prepay_code_combination_id
FROM
gl_code_combinations
WHERE
segment1 ||
'.'
|| segment2 ||
'.'
|| segment3 ||
'.'
|| segment4 = c2_rec.advances_account_code;
BEGIN
l_country := get_country_code (c2_rec.country);
EXCEPTION
WHEN
OTHERS
THEN
l_country :=
'IN'
;
END
;
INSERT
INTO
ap_supplier_sites_int
(vendor_interface_id, vendor_site_code, payment_method_lookup_code, terms_date_basis, accts_pay_code_combination_id,
prepay_code_combination_id, pay_group_lookup_code, payment_priority, terms_id, pay_date_basis_lookup_code, org_id,
purchasing_site_flag, rfq_only_site_flag, pay_site_flag, attention_ar_flag, allow_awt_flag, address_line1,
address_line2, address_line3, city, country, state, zip, address_lines_alt, ship_to_location_id,
bill_to_location_id
)
VALUES
(ap_suppliers_int_s.CURRVAL, c2_rec.site,
'SITE1'
,
'CHECK'
,
'Invoice'
,
c2_rec.liability_account_id, p_prepay_code_combination_id,
'SUPPLIER'
,
'HIGH PRIORITY'
, 99, 10000,
'DISCOUNT'
, 82,
'Y'
,
'N'
,
'Y'
,
'N'
,
'N'
, c2_rec.address1, c2_rec.address2, c2_rec.address3, c2_rec.city, l_country, c2_rec.state, c2_rec.pin,
c2_rec.contact_phones, 142, 142
);
UPDATE
xx_vendor_sites_others_b
SET
flag =
'Y'
WHERE
vendor_name = c2_rec.vendor_name
AND
vendor_type_lookup_code = c2_rec.vendor_type_lookup_code
AND
site = c2_rec.site;
COMMIT
;
EXCEPTION
WHEN
OTHERS
THEN
ROLLBACK
;
p_message := SUBSTR (SQLERRM,
1,
200
);
UPDATE
xx_vendor_sites_others_b
SET
flag =
'N'
,
error_message = p_message
WHERE
vendor_name = c2_rec.vendor_name
AND
vendor_type_lookup_code = c2_rec.vendor_type_lookup_code
AND
site = c2_rec.site;
COMMIT
;
END
;
END
LOOP;
EXCEPTION
WHEN
OTHERS
THEN
ROLLBACK
;
END
;
COMMIT
;
DECLARE
--Cursor 1 which retieves data from header table to insert into receiving header table
p_header_id NUMBER;
p_counter NUMBER := 0;
p_header_error NUMBER := 0;
p_line_error NUMBER := 0;
p_header_sequence NUMBER;
p_org_id NUMBER;
p_message VARCHAR2 (200);
p_count NUMBER := 0;
p_pay_code_combination_id NUMBER := 1074;
p_prepay_code_combination_id NUMBER := 1075;
l_country VARCHAR2 (2);
ln_req_id NUMBER;
-- Concurrent request parameters
lb_flag BOOLEAN;
lv_dev_phase VARCHAR2 (30);
lv_dev_status VARCHAR2 (30);
lv_phase VARCHAR2 (30);
lv_message VARCHAR2 (240);
CURSOR
c2
IS
SELECT
vendor_name, vendor_type_lookup_code, site, country, address1, address2, address3, city, state, pin, liability_account_id
FROM
xx_vendor_sites_others_b
WHERE
flag
IS
NULL
ORDER
BY
vendor_name;
FUNCTION
get_country_code (p_country
IN
VARCHAR2)
RETURN
VARCHAR2
IS
BEGIN
SELECT
territory_code
INTO
l_country
FROM
fnd_territories_vl
WHERE
territory_short_name = INITCAP (p_country);
RETURN
l_country;
EXCEPTION
WHEN
NO_DATA_FOUND
THEN
l_country :=
'IN'
;
END
;
BEGIN
FOR
c2_rec
IN
c2
LOOP
BEGIN
SELECT
COUNT
(*)
INTO
p_count
FROM
ap_suppliers_int
WHERE
vendor_name = c2_rec.vendor_name;
END
;
IF p_count = 0
THEN
BEGIN
INSERT
INTO
ap_suppliers_int
(vendor_interface_id, vendor_name, vendor_name_alt, segment1, summary_flag, enabled_flag,
vendor_type_lookup_code, one_time_flag, ship_to_location_id, bill_to_location_id, terms_id, set_of_books_id,
always_take_disc_flag, pay_date_basis_lookup_code, pay_group_lookup_code, payment_priority,
hold_all_payments_flag, hold_future_payments_flag, start_date_active, payment_method_lookup_code,
terms_date_basis, qty_rcv_tolerance, qty_rcv_exception_code, enforce_ship_to_location_code,
days_early_receipt_allowed, days_late_receipt_allowed, receipt_days_exception_code, receiving_routing_id,
allow_substitute_receipts_flag, allow_unordered_receipts_flag, bank_charge_bearer, match_option, allow_awt_flag
)
VALUES
(ap_suppliers_int_s.NEXTVAL,
UPPER
(c2_rec.vendor_name),
UPPER
(c2_rec.vendor_name), c2_rec.segment1,
'N'
,
'Y'
,
c2_rec.vendor_type_lookup_code,
'Sub-Contractor'
,
'N'
, 142, 142, 10000,
1001,
'N'
,
'DISCOUNT'
,
'HIGH PRIORITY'
,
99,
'N'
,
'N'
,
'15-AUG-2005'
,
'CHECK'
,
'Invoice'
, 10,
'WARNING'
,
'NONE'
, 2, 5,
'WARNING'
,
1,
'N'
,
'Y'
,
'I'
,
'R'
,
''
);
/*
UPDATE
XX_VENDOR_SITES_OTHERS_B
SET
FLAG=
'Y'
WHERE
VENDOR_NAME=C2_REC.VENDOR_NAME;
*/
COMMIT
;
SELECT
ap_suppliers_int_s.CURRVAL
INTO
p_header_sequence
FROM
DUAL;
EXCEPTION
WHEN
OTHERS
THEN
ROLLBACK
;
p_message := SUBSTR (SQLERRM,
1,
200
);
UPDATE
xx_vendor_sites_others_b
SET
flag =
'N'
,
error_message = p_message
WHERE
vendor_name = c2_rec.vendor_name
AND
vendor_type_lookup_code = c2_rec.vendor_type_lookup_code
AND
site = c2_rec.site;
COMMIT
;
p_header_error := 1;
END
;
END
IF;
BEGIN
SELECT
code_combination_id
INTO
p_pay_code_combination_id
FROM
gl_code_combinations
WHERE
segment1 ||
'.'
|| segment2 ||
'.'
|| segment3 ||
'.'
|| segment4 = c2_rec.lia_account_code;
SELECT
code_combination_id
INTO
p_prepay_code_combination_id
FROM
gl_code_combinations
WHERE
segment1 ||
'.'
|| segment2 ||
'.'
|| segment3 ||
'.'
|| segment4 = c2_rec.advances_account_code;
BEGIN
l_country := get_country_code (c2_rec.country);
EXCEPTION
WHEN
OTHERS
THEN
l_country :=
'IN'
;
END
;
INSERT
INTO
ap_supplier_sites_int
(vendor_interface_id, vendor_site_code, payment_method_lookup_code, terms_date_basis, accts_pay_code_combination_id,
prepay_code_combination_id, pay_group_lookup_code, payment_priority, terms_id, pay_date_basis_lookup_code, org_id,
purchasing_site_flag, rfq_only_site_flag, pay_site_flag, attention_ar_flag, allow_awt_flag, address_line1,
address_line2, address_line3, city, country, state, zip, address_lines_alt, ship_to_location_id,
bill_to_location_id
)
VALUES
(ap_suppliers_int_s.CURRVAL, c2_rec.site,
'SITE1'
,
'CHECK'
,
'Invoice'
,
c2_rec.liability_account_id, p_prepay_code_combination_id,
'SUPPLIER'
,
'HIGH PRIORITY'
, 99, 10000,
'DISCOUNT'
, 82,
'Y'
,
'N'
,
'Y'
,
'N'
,
'N'
, c2_rec.address1, c2_rec.address2, c2_rec.address3, c2_rec.city, l_country, c2_rec.state, c2_rec.pin,
c2_rec.contact_phones, 142, 142
);
UPDATE
xx_vendor_sites_others_b
SET
flag =
'Y'
WHERE
vendor_name = c2_rec.vendor_name
AND
vendor_type_lookup_code = c2_rec.vendor_type_lookup_code
AND
site = c2_rec.site;
COMMIT
;
EXCEPTION
WHEN
OTHERS
THEN
ROLLBACK
;
p_message := SUBSTR (SQLERRM,
1,
200
);
UPDATE
xx_vendor_sites_others_b
SET
flag =
'N'
,
error_message = p_message
WHERE
vendor_name = c2_rec.vendor_name
AND
vendor_type_lookup_code = c2_rec.vendor_type_lookup_code
AND
site = c2_rec.site;
COMMIT
;
END
;
END
LOOP;
-- Initialize APPS
fnd_global.apps_initialize (user_id => 12691,
resp_id => 50293,
resp_appl_id => 200
);
-- Submit Supplier Import program
BEGIN
ln_req_id :=
fnd_request.submit_request (application =>
'SQLAP'
,
program =>
'APXSUIMP'
,
argument1 =>
'ALL'
,
argument2 => 1000,
argument3 =>
'N'
,
argument4 =>
'N'
,
argument5 =>
'N'
,
argument6 =>
'-99'
);
COMMIT
;
IF ln_req_id = 0
THEN
-- Error while submitting Supplier import
fnd_file.put_line (fnd_file.LOG,
'Error while submitting Supplier Import. '
|| SQLERRM);
RETURN
;
ELSE
lb_flag :=
fnd_concurrent.wait_for_request (request_id => ln_req_id,
INTERVAL => 5,
phase => lv_phase,
status => lv_status1,
dev_phase => lv_dev_phase,
dev_status => lv_dev_status,
MESSAGE => lv_message
);
IF lv_dev_phase =
'COMPLETE'
AND
lv_dev_status =
'NORMAL'
THEN
fnd_file.put_line (fnd_file.LOG,
'Supplier Import program completed successfully'
|| ln_req_id);
ELSE
fnd_file.put_line (fnd_file.LOG,
'Error while running Supplier Import program'
);
ROLLBACK
;
END
IF;
END
IF;
END
;
-- Submit Supplier Sites Import program
BEGIN
ln_req_id :=
fnd_request.submit_request (application =>
'SQLAP'
,
program =>
'APXSSIMP'
,
argument1 =>
'NEW'
,
argument2 => 1000,
argument3 =>
'N'
,
argument4 =>
'N'
,
argument5 =>
'N'
,
argument6 =>
'-99'
);
COMMIT
;
IF ln_req_id = 0
THEN
-- Error while submitting Supplier sites import
fnd_file.put_line (fnd_file.LOG,
'Error while submitting Supplier sites Import. '
|| SQLERRM);
RETURN
;
ELSE
lb_flag :=
fnd_concurrent.wait_for_request (request_id => ln_req_id,
INTERVAL => 5,
phase => lv_phase,
status => lv_status1,
dev_phase => lv_dev_phase,
dev_status => lv_dev_status,
MESSAGE => lv_message
);
IF lv_dev_phase =
'COMPLETE'
AND
lv_dev_status =
'NORMAL'
THEN
fnd_file.put_line (fnd_file.LOG,
'Supplier sites Import program completed successfully'
|| ln_req_id);
ELSE
fnd_file.put_line (fnd_file.LOG,
'Error while running Supplier sites Import program'
);
ROLLBACK
;
END
IF;
END
IF;
END
;
EXCEPTION
WHEN
OTHERS
THEN
ROLLBACK
;
END
;
|
Application Programming Interface (API) method
You can also use an API for importing suppliers and their corresponding sites
| Function | Vendor | Vendor Sites |
| Create a record | ap_vendors_pkg.insert_row | ap_vendor_sites_pkg.insert_row |
| Update a record | ap_vendors_pkg.update_row | ap_vendor_sites_pkg.update_row |
A sample script using the API is given below. This script is used for updating supplier sites. You can use the other API’s in a similar way.
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
|
DECLARE
CURSOR
c_vendorsites (v_vendor_site_id NUMBER)
IS
SELECT
pvsa.*, pvsa.ROWID
FROM
po_vendor_sites_all pvsa
WHERE
1 = 1
AND
pvsa.vendor_site_id = v_vendor_site_id;
v_date
DATE
;
v_itemkey VARCHAR2 (100);
v_vendor_site_id NUMBER;
v_user_id NUMBER;
v_resp_id NUMBER;
BEGIN
v_user_id := fnd_profile.VALUE (
'USER_ID'
);
v_resp_id := fnd_profile.VALUE (
'RESP_ID'
);
v_vendor_site_id := 1034;
fnd_global.apps_initialize (user_id => v_user_id,
resp_id => v_resp_id,
resp_appl_id => 200
);
FOR
v_site
IN
c_vendorsites (v_vendor_site_id)
LOOP
ap_vendor_sites_pkg.update_row (x_rowid => v_site.ROWID,
x_vendor_site_id => v_site.vendor_site_id,
x_last_update_date => v_site.last_update_date,
x_last_updated_by => v_site.last_updated_by,
x_vendor_id => v_site.vendor_id,
x_vendor_site_code => v_site.vendor_site_code,
x_last_update_login => v_site.last_update_login,
x_creation_date => v_site.creation_date,
x_created_by => v_site.created_by,
x_purchasing_site_flag => v_site.purchasing_site_flag,
x_rfq_only_site_flag => v_site.rfq_only_site_flag,
x_pay_site_flag => v_site.pay_site_flag,
x_attention_ar_flag => v_site.attention_ar_flag,
x_address_line1 => v_site.address_line1,
x_address_line2 => v_site.address_line2,
x_address_line3 => v_site.address_line3,
x_city => v_site.city,
x_state => v_site.state,
x_zip => v_site.zip,
x_province => v_site.province,
x_country => v_site.country,
x_area_code => v_site.area_code,
x_phone => v_site.phone,
x_customer_num => v_site.customer_num,
x_ship_to_location_id => v_site.ship_to_location_id,
x_bill_to_location_id => v_site.bill_to_location_id,
x_ship_via_lookup_code => v_site.ship_via_lookup_code,
x_freight_terms_lookup_code => v_site.freight_terms_lookup_code,
x_fob_lookup_code => v_site.fob_lookup_code,
x_inactive_date => v_date,
--v_Site.inactive_date,
x_fax => v_site.fax,
x_fax_area_code => v_site.fax_area_code,
x_telex => v_site.telex,
x_payment_method_lookup_code => v_site.payment_method_lookup_code,
x_bank_account_name => v_site.bank_account_name,
x_bank_account_num => v_site.bank_account_num,
x_bank_num => v_site.bank_num,
x_bank_account_type => v_site.bank_account_type,
x_terms_date_basis => v_site.terms_date_basis,
x_current_catalog_num => v_site.current_catalog_num,
x_vat_code => v_site.vat_code,
x_distribution_set_id => v_site.distribution_set_id,
x_accts_pay_ccid => v_site.accts_pay_code_combination_id,
x_future_dated_payment_ccid => v_site.future_dated_payment_ccid,
x_prepay_code_combination_id => v_site.prepay_code_combination_id,
x_pay_group_lookup_code => v_site.pay_group_lookup_code,
x_payment_priority => v_site.payment_priority,
x_terms_id => v_site.terms_id,
x_invoice_amount_limit => v_site.invoice_amount_limit,
x_pay_date_basis_lookup_code => v_site.pay_date_basis_lookup_code,
x_always_take_disc_flag => v_site.always_take_disc_flag,
x_invoice_currency_code => v_site.invoice_currency_code,
x_payment_currency_code => v_site.payment_currency_code,
x_hold_all_payments_flag => v_site.hold_all_payments_flag,
x_hold_future_payments_flag => v_site.hold_future_payments_flag,
x_hold_reason => v_site.hold_reason,
x_hold_unmatched_invoices_flag => v_site.hold_unmatched_invoices_flag,
x_match_option => v_site.match_option,
x_create_debit_memo_flag => v_site.create_debit_memo_flag,
x_exclusive_payment_flag => v_site.exclusive_payment_flag,
x_tax_reporting_site_flag => v_site.tax_reporting_site_flag,
x_attribute_category => v_site.attribute_category,
x_attribute1 => v_site.attribute1,
x_attribute2 => v_site.attribute2,
x_attribute3 => v_site.attribute3,
x_attribute4 => v_site.attribute4,
x_attribute5 => v_site.attribute5,
x_attribute6 => v_site.attribute6,
x_attribute7 => v_site.attribute7,
x_attribute8 => v_site.attribute8,
x_attribute9 => v_site.attribute9,
x_attribute10 => v_site.attribute10,
x_attribute11 => v_site.attribute11,
x_attribute12 => v_site.attribute12,
x_attribute13 => v_site.attribute13,
x_attribute14 => v_site.attribute14,
x_attribute15 => v_site.attribute15,
x_validation_number => v_site.validation_number,
x_exclude_freight_from_disc => v_site.exclude_freight_from_discount,
x_vat_registration_num => v_site.vat_registration_num,
x_offset_tax_flag => v_site.offset_tax_flag,
x_check_digits => v_site.check_digits,
x_bank_number => v_site.bank_number,
x_address_line4 => v_site.address_line4,
x_county => v_site.county,
x_address_style => v_site.address_style,
x_language => v_site.LANGUAGE,
x_allow_awt_flag => v_site.allow_awt_flag,
x_awt_group_id => v_site.awt_group_id,
x_pay_on_code => v_site.pay_on_code,
x_default_pay_site_id => v_site.default_pay_site_id,
x_pay_on_receipt_summary_code => v_site.pay_on_receipt_summary_code,
x_bank_branch_type => v_site.bank_branch_type,
x_edi_id_number => v_site.edi_id_number,
x_edi_payment_method => v_site.edi_payment_method,
x_edi_payment_format => v_site.edi_payment_format,
x_edi_remittance_method => v_site.edi_remittance_method,
x_edi_remittance_instruction => v_site.edi_remittance_instruction,
x_edi_transaction_handling => v_site.edi_transaction_handling,
x_auto_tax_calc_flag => v_site.auto_tax_calc_flag,
x_auto_tax_calc_override => v_site.auto_tax_calc_override,
x_amount_includes_tax_flag => v_site.amount_includes_tax_flag,
x_ap_tax_rounding_rule => v_site.ap_tax_rounding_rule,
x_vendor_site_code_alt => v_site.vendor_site_code_alt,
x_address_lines_alt => v_site.address_lines_alt,
x_global_attribute_category => v_site.global_attribute_category,
x_global_attribute1 => v_site.global_attribute1,
x_global_attribute2 => v_site.global_attribute2,
x_global_attribute3 => v_site.global_attribute3,
x_global_attribute4 => v_site.global_attribute4,
x_global_attribute5 => v_site.global_attribute5,
x_global_attribute6 => v_site.global_attribute6,
x_global_attribute7 => v_site.global_attribute7,
x_global_attribute8 => v_site.global_attribute8,
x_global_attribute9 => v_site.global_attribute9,
x_global_attribute10 => v_site.global_attribute10,
x_global_attribute11 => v_site.global_attribute11,
x_global_attribute12 => v_site.global_attribute12,
x_global_attribute13 => v_site.global_attribute13,
x_global_attribute14 => v_site.global_attribute14,
x_global_attribute15 => v_site.global_attribute15,
x_global_attribute16 => v_site.global_attribute16,
x_global_attribute17 => v_site.global_attribute17,
x_global_attribute18 => v_site.global_attribute18,
x_global_attribute19 => v_site.global_attribute19,
x_global_attribute20 => v_site.global_attribute20,
x_bank_charge_bearer => v_site.bank_charge_bearer,
x_ece_tp_location_code => v_site.ece_tp_location_code,
x_pcard_site_flag => v_site.pcard_site_flag,
x_country_of_origin_code => v_site.country_of_origin_code,
x_calling_sequence =>
NULL
,
x_shipping_location_id =>
NULL
,
--v_Site.shipping_location_id, -- do not update shipping location information
x_supplier_notif_method => v_site.supplier_notif_method,
x_email_address => v_site.email_address,
x_remittance_email => v_site.remittance_email,
x_primary_pay_site_flag => v_site.primary_pay_site_flag,
x_shipping_control => v_site.shipping_control,
x_gapless_inv_num_flag => v_site.gapless_inv_num_flag,
x_selling_company_identifier => v_site.selling_company_identifier,
x_duns_number => v_site.duns_number,
x_tolerance_id => v_site.tolerance_id
);
END
LOOP;
COMMIT
;
END
;
|
The advantage to using the API over the interface tables is that the API enters the data into the base tables in a single call whereas the for an Open interface the data has to be inserted into the interface tables and then the seeded import program is called.
Cheers!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
External Bank Import Process
Process of importing external bank account data in R12
Or
acle supports many Open Interface Programs for importing data from any third party systems. For importing bank account information Oracle provides interface programs named ‘Customer Interface’ for importing Customer bank accounts and ‘Supplier Open Interface/Supplier site interface ’ for importing Supplier bank accounts.
This document helps in understanding the process of importing the external bank accounts data for customers or suppliers.
Importing Supplier bank accounts
The data to be imported is to be inserted in the interface tables first. After inserting the data in the interface tables,the ‘Supplier Open Interface Import’ program is run for inserting the data in the R12 tables.An important point to be noted with regard to the supplier bank accounts – the bank accounts data related to the suppliers can only be imported along with the supplier or supplier site. The bank account details cannot be imported individually. After creating the supplier or supplier site, the bank account can only be added from the user interface.
The supplier bank accounts can be assigned at the Supplier or Supplier Site or Address or Address Operating Unit level from the user interface. The import program supports assigning Supplier bank accounts at Supplier or at Supplier Site level only.
The main interface tables used for importing Suppliers, Supplier sites and Bank accounts data are as follows -
AP_SUPPLIERS_INT
IBY_TEMP_EXT_BANK_ACCTS.
AP_SUPPLIER_SITES_INT
The following scenarios are covered in this document –
a) Importing the bank account at Supplier level along with Supplier data
b) Importing the bank account at site level along with Supplier and Supplier site
i. Importing bank account at site along with supplier and site details.
ii. Importing bank account along with supplier site for an existing Supplier.
c) Importing the bank accounts for Employee type Supplier
The detailed steps for each of the scenarios have been mentioned below.
Importing the bank account at Supplier level along with Supplier data
Please follow the below mentioned steps for importing the bank account at supplier level.
Step 1 –
Insert the Suppliers data in the interface table AP_SUPPLIERS_INT.
Step 2 –
While inserting the data in the table AP_SUPPLIERS_INT, the data in the column
VENDOR_INTERFACE_ID should be generated sequentially. This is the unique identifier for
records in this table
The column AP_SUPPLIERS_INT.VENDOR_INTERFACE_ID is used to link the supplier with
the respective site or bank account details.
The sequence AP_SUPPLIERS_INT_S is used to generate the sequential number.
Step 3 –
The bank account details should be inserted in the interface table
IBY_TEMP_EXT_BANK_ACCTS
Step 4 –
While inserting the data in the table IBY_TEMP_EXT_BANK_ACCTS, as the bank account data is being assigned at supplier level, the column IBY_TEMP_EXT_BANK_ACCTS.CALLING_APP_UNIQUE_APP_REF1 should be updated
with the value from its corresponding suppliers
AP_SUPPLIERS_INT.VENDOR_INTERFACE_ID
Step 5 –
While inserting the data in IBY_TEMP_EXT_BANK_ACCTS and AP_SUPPLIERS_INT, the value for the column ‘Status’ should be updated as ‘NEW’ (case sensitive) in both the tables.After inserting the data in the tables AP_SUPPLIERS_INT and IBY_TEMP_EXT_BANK_ACCTS the data is ready to be imported.
Step 6 –
Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’. The following screen is displayed.
Step 7 –
Select ‘Single Request’ and select ‘OK’ button.
concurrent program name : supplier open interface import
Step 8
In the request name, search and select the program with name ‘Supplier Open Interface
Step 9 –
Navigate to the parameters LOV and select the options based on the imported data.
Step 10 –
Parameters: Batch size indicates the number of records to be imported in one import program.
The default value is 1000 and can be modified.
Step 11 –
Parameters: Print exceptions only indicate whether the log file should contain only the exception
details. Default value is ‘No’ and can be modified to ‘Yes’.
Step 12 –
Parameters: Debug switch indicate whether the log file should contain the debug details. Default
value is ‘No’ and can be modified to ‘Yes’.
Step 13 –
Parameters: Trace switch indicate whether the trace file of the program should be generated.
Default value is ‘No’ and can be modified to ‘Yes’.
Step 14 –
Import options LOV: Default value is ‘All’. If the program is to import only the records with the
status ‘New’, select the option ‘New’. If the program is run to import only the rejected
transactions of the earlier run, select the option ‘Rejected’. If the request program is to import all
the records in the table, select the option ‘All’.
Step 15 –
Select ‘Submit’ button.
Step 16 –
The program ‘Supplier Open Interface Import’ automatically calls the ‘Create external bank
account’ (IBY_EXT_BANKACCT_PUB.CREATE_EXT_BANK_ACCT) program and imports
the bank accounts data related to the supplier.
On successful import of the records the column ‘Status’ will be updated from ‘NEW’ to
‘PROCESSED’. If a record is not imported due to any error, the field will be updated as
‘REJECTED’.
Step 17 –
To track the status of the request program, navigate to the ‘View requests’ screen
Step 18 –
When the Phase column shows ‘Completed’ and the status column shows ‘Normal’, select the
‘View Output’ button to know the number of records that have been imported.
Step 19 –
Select the ‘View Log’ button to go through the error messages if any.
After Successful import of Supplier/Supplier Site with the bank account details, following IBY Tables are
being populated.
IBY_EXTERNAL_PAYEES_ALL
: A record is created in this table with Payee id (equivalent to
HZ_PARTIES.PARTY_ID).
IBY_EXT_BANK_ACCOUNTS
: A record is inserted in this table with the bank account details
provided in IBY_TEMP_EXT_BANK_ACCTS.
IBY_PMT_INSTR_USES_ALL:
For every external bank account created, a record is inserted in this
table. This table also holds relationship between External Payee and External Bank Account
Note:
2) While importing the bank account along with the supplier, if there is some error in the bank account
details, the supplier data will only be created without the bank details.
3) Bank account can be created without bank and branch details if the bank is not used for making
international payments. In other words bank account will be created without the bank and branch if
Bank_id and Branch_id is not inserted in IBY_TEMP_EXT_BANK_ACCTS table and
FOREIGN_PAYMENT_USE_FLAG is ‘No’.
Importing the bank account at site level along with Supplier and Supplier site
While importing the bank details for a supplier site, there are two scenarios –
a) Importing bank account at site along with supplier and site details.
b) Importing bank account along with supplier site for an existing Supplier.
Importing Bank account at site along with supplier and site details.
The additional interface table for storing the supplier sites data is AP_SUPPLIER_SITES_INT.
Step 1 –
Insert the data in the AP_SUPPLIERS_INT and AP_SUPPLIER_SITES_INT.
Step 2 –
While inserting the data in the table AP_SUPPLIERS_INT, the data in the column
VENDOR_INTERFACE_ID should be generated sequentially. This is the unique
identifier for records in this table
In the scenario, VENDOR_INTERFACE_ID is used to link the supplier with the
respective site details
Step 3 –
While inserting data in the table AP_SUPPLIER_SITES_INT, the column
AP_SUPPLIER_SITES_INT.VENDOR_INTERFACE_ID should be filled in with the
respective suppliers record value of the
AP_SUPPLIER_INT.VENDOR_INTERFACE_ID
Step 4 –
Insert the bank account details in the interface table IBY_TEMP_EXT_BANK_ACCTS.
Step 5 –
As the bank account data is being assigned at supplier site level, while inserting the data
in the table IBY_TEMP_EXT_BANK_ACCTS, the column
IBY_TEMP_EXT_BANK_ACCTS.CALLING_APP_UNIQUE_APP_
REF2 should be
updated with AP_SUPPLIER_SITES_INT.VENDOR_SITE_INTERFACE_ID.
VENDOR_SITE_INTERFACE_ID helps in linking the bank details with its corresponding Supplier site.
Step 6 –
While inserting the data in AP_SUPPLIERS_INT, AP_SUPPLIER_ SITES_INT and
IBY_TEMP_EXT_BANK_ACCTS, the value for the column ‘Status’ should be updated as ‘NEW’.
After inserting the data in the tables AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT and IBY_TEMP_EXT_BANK_ACCTS the data is ready to be imported.
Step 7 –
Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’ screen and run the program with name ‘Supplier Open Interface Import’.
The other steps to run the ‘Supplier Open Interface Import’ are same as explained for importing Bank accounts details at supplier level.
Importing bank account along with supplier site for an existing Supplier
The interface table for storing the supplier sites data is AP_SUPPLIER_SITES_INT and the bank
account data is IBY_TEMP_EXT_BANK_ACCTS.
Step 1 –
Insert the data in the AP_SUPPLIER_SITES_INT.
Step 2 –
While inserting the data in the AP_SUPPLIER_SITES_INT, the column VENDOR_ID
should be updated with the respective supplier for which the supplier site is being created.
The column VENDOR_ID is used to link the supplier with the respective Supplier site details.
Step 3 –
The bank account details should be inserted in the interface table IBY_TEMP_EXT_BANK_ACCTS.
Step 4 –
As the bank account data is being assigned at supplier site level, while inserting the data in the IBY_TEMP_EXT_BANK_ACCTS the column ‘CALLING_APP_UNIQUE_APP_REF2' should be updated with the respective
VENDOR_SITE_INTERFACE_ID.
The field AP_SUPPLIER_ SITES_INT is used to link the supplier site with the respective bank account details.
Step 5 –
While inserting the data in AP_SUPPLIER_ SITES_INT and IBY_TEMP_EXT_BANK_ACCTS, the value for the column ‘Status’ should be updated as ‘NEW’.
After inserting the data in the tables AP_SUPPLIER_ SITES_INT and IBY_TEMP_EXT_BANK_ACCTS the data is ready to be imported.
Step 6 –
Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’ screen and run
the program with name ‘Supplier Sites Open Interface Import’.
The other steps to run the ‘Supplier Open Interface Import’ are same as explained for importing Bank
accounts details at supplier level.
Importing the bank accounts for Employee type Supplier
External bank account can be imported for Employee type suppliers while importing the supplier data for the employee.
Prerequisite
Employee record should have been created in the HR.
The interface tables for storing the supplier, supplier site and the bank account details remain the same - AP_SUPPLIER_SITES_INT, AP_SUPPLIER_SITES_INT and IBY_TEMP_EXT_BANK_ACCTS respectively.
Step 1 –
Insert the data in the AP_SUPPLIERS_INT.
Step 2 –
As the data is inserted for an employee type of supplier, the AP_SUPPLIER_INT.EMPLOYEE_ID should be updated with employee Id and VENDOR_TYPE_LOOKUP_CODE should be updated as ‘EMPLOYEE’.
Step 3 –
Insert the data in the AP_SUPPLIER_SITES_INT.
Step 4 –
As the data is imported for an employee type supplier, the AP_SUPPLIER_SITES_INT.VENDOR_SITE_CODE should be updated as ‘HOME’ or ‘OFFICE’ or ‘PROVISIONAL’ (please note that values are case sensitive and should be
given in capitals).
Step 5 –
Insert the bank account details in the interface table IBY_TEMP_EXT_BANK_ACCTS.
Step 6 –
As the bank account data is being assigned at supplier site level, while inserting the data in the table IBY_TEMP_EXT_BANK_ACCTS, the column IBY_TEMP_EXT_BANK_ACCTS.CALLING_APP_UNIQUE_APP_
REF2
should be
updated with AP_SUPPLIER_SITES_INT.VENDOR_SITE_INTERFACE_ID.
VENDOR_SITE_INTERFACE_ID helps in linking the bank details with its
corresponding Supplier site.
Step 7 –
Navigate to the Payables >> Other: Requests >> Run -‘Submit Request’ screen and run the program with name ‘Supplier Open Interface Import’.
The other steps to run the ‘Supplier Open Interface Import’ are same as explained for importing Bank
accounts details at supplier level.
423
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
