供应商导入

分享一下我老师大神的人工智能教程！零基础，通俗易懂！http://blog.csdn.net/jiangjunshow

也欢迎大家转载本篇文章。分享知识，造福人民，实现我们中华民族伟大复兴！

               

转载几篇关于供应商导入的文章

供应商导入简例

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

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 not
provided 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','','','','[email protected]');

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: