1) The Supplier, Sites/Locations, and their Contact information will be migrated to TCA.

As part of the migration, there are three new tables: AP_SUPPLIERS AP_SUPPLIER_SITES_ALL AP_SUPPLIER_CONTACTS The existing Suppliers tables are obsoleted and renamed as: PO_VENDORS --> PO_VENDORS_OBS PO_VENDOR_SITES_ALL --> PO_VENDOR_SITES_OBS PO_VENDOR_CONTACTS --> PO_VENDOR_CONTACTS_OBS 2) To minimize the impact to the other products, views are provided with the names PO_VENDORS PO_VENDOR_SITES_ALL PO_VENDOR_CONTACTS. These views will be based on the information from TCA and Payables Suppliers tables. 3) Supplier Sites The supplier sites table will store the Site account attributes per Operating Unit, which will default into transactions. Going forward, supplier site creation will involve either selecting an existing location for the supplier or creating a new location in HZ_LOCATIONS. The user will then have to select the Operating Unit based on the security profile, and enter the site attributes as they are entered today. 4) New Tables The following are the new tables added in Release 12 as a part of this initiative. Refer to the Oracle E-Business Suite Electronic Technical Reference Manual for the table and column descriptions. AP_SUPPLIERS AP_SUPPLIER_SITES_ALL AP_SUPPLIER_CONTACTS AP_SUPPLIER_INT_REJECTIONS 5) Concurrent Program : APXSUIMP --> Supplier Open Interface Import Supplier Open Interface Import program is extended to create Parties in TCA when creating the suppliers based on the information in AP_SUPPLIERS_INT. If records are populated in the IBY External Payee Accounts table, then the program will call the necessary APIs from Oracle Payments to create the Supplier Bank Accounts. APXSSIMP --> Supplier Sites Open Interface Import Supplier Sites Open Interface Import program is extended to create Locations, Party Sites, and Party Site Uses in TCA based on the information provided in AP_SUPPLIER_SITES_INT. If records are populated in the Payments External Payee Accounts table, then the program will call the necessary

APIs from O racle Payments to create the Supplier Bank Accounts for the site. APXSCIMP --> Supplier Site Contacts Open Interface Import Supplier Sites Contacts Open Interface Import program is extended to create Person Parties, Contact Relationships, Org Contacts, Contact Party Sites, and Contact Points in TCA based on the information provided in AP_SUPPLIER_SITES_ INT. 6) New or Modified APIs (Packages) Package File--> AP_VENDOR_PUB_PKG (apvndrs.pls and apvndrb.pls) AP_VENDOR_PUB_PKG. Create_Vendor --> This is the new public API to create new vendors in Release 12. This procedure takes a vendor record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_rec_type. If the TCA Party ID is provided in the record type, the system will validate and only create the record in AP_SUPPLIERS, otherwise the system will call the TCA API to create Party and then will create the record in AP_SUPPLIERS. AP_VENDOR_PUB_PKG. Update_Vendor --> This is the new public API to update vendors in Release 12. This procedure takes a vendor record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_rec_type. The Payables API will not update the party record in TCA. It will only update the supplier attributes in AP_SUPPLIERS. AP_VENDOR_PUB_PKG. Create_Vendor_Site --> This is the new public API to create new vendor sites in Release 12. This procedure takes a vendor site record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_site_rec_type. If the TCA LocationID/PartySiteID is provided in the record type, the system will validate and only create the record in AP_SUPPLIER_SITES_ALL, otherwise the system will call the TCA API to create Location and Party Site, and then will create the record in AP_SUPPLIER_SITES_ALL. AP_VENDOR_PUB_PKG. Update_Vendor_Site --> This is the new public API to update vendor sites in Release 12. This procedure takes a vendor site record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_site_rec_type. The Payables API will not update

the Location/Party Site records in TCA. It will only update the supplier site attributes in AP_SUPPLIER_SITES_ALL. AP_VENDOR_PUB_PKG. Create_Vendor_Contact --> This is the new public API to create new vendor site contacts in Release 12. This procedure takes a vendor site contact record as an input parameter which is based on the structure defined in AP_VENDOR_PUB_PKG. r_vendor_contact_rec_type. This API creates the necessary records in HZ_PERSON_PROFILES, HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, HZ_PARTY_SITES, and HZ_CONTACT_POINTS, and creates a record in AP_SUPPLIER_CONTACTS
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The method of storing information for supplier contacts is very much different in R12 than it is in 11i. Most of the information is stored in various TCA tables. The table AP_SUPPLIER_CONTACTS is a linking table between the supplier address and the various TCA tables if the contact is assigned to an address in the form or during Import. For Contacts created in R12 columns such as Name and Address elements are not populated in AP_SUPPLIER_CONTACTS. Contacts that were directly upgraded from 11i will have their legacy values in this table, but the form and other processes that use or display this information for contacts use the TCA tables. When a Contact is created, two rows are created in HZ_PARTIES (though it is possible that only one is created if the name already existed in the system when the contact was entered). One is of type PERSON, and the other is of type PARTY_RELATIONSHIP. The PERSON type party stores name information and the like, while address elements and contact information (phone number, for example) are stored in the PARTY_RELATIONSHIP type party. These are linked to the ORGANIZATION type Party of the Supplier by a row in HZ_RELATIONSHIPS. The kind of contact (Manager, Sales Rep, etc) is stored in HZ_ORG_CONTACTS. When you assign a contact to a supplier address you create a row in AP_SUPPLIER_CONTACTS that links all things together and maps it back to the party site created as the address. The link column in AP_SUPPLIER_CONTACTS map tp the following tables/columns Per_Party_ID = Party_ID of PERSON Party in HZ_PARTIES Relationship_ID = Relationship_ID of Rows in HZ_RELATIONHIPS Rel_Party_ID = Party_ID of PARTY_RELATIONSHIP Party in HZ_PARTIES Party_Site_ID = Maps to the Party Site created for the PARTY_RELATIONSHIP Party Org_Contact_ID = Org_Contact_ID from HZ_ORG_CONTACTS

Org_Party_Site_ID = Party_Site_ID of the Supplier Site row. Assuming you know the party_site_id for an address (which is the value in AP_SUPPLIER_SITES_ALL.party_Site_ID for a site that is associated with that address) you can use this query to get the contact for that address. SELECT PERSON.person_first_name, PERSON.person_last_name, PTY_REL.address1, PTY_REL.City, PTY_REL.state, PTY_REL.country, PTY_REL.Primary_phone_area_code, PTY_REL.primary_phone_number FROM hz_parties PERSON, hz_parties PTY_REL, ap_supplier_contacts APSC WHERE APSC.per_party_id = PERSON.party_id AND APSC.rel_party_id = PTY_REL.party_id AND APSC.org_party_site_id = <Party_Site_Address_ID>
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------