In this article, I would like to show you the set of tables that are effected when a Supplier record

gets created in Release12. I will also touch base upon Supplier Sites and changes to taxation related tables.

End User Step 1 To begin with, we need to create a Supplier. Lets name it Go4Gold [which also happens to be the name of my old company]. Simply enter name of the Supplier in organization name field and click on Apply. This will create a Supplier.

End User Step 2. You can doublecheck the created Supplier, which has Supplier Number 20186. This supplier number comes from a table named AP_SUPPLIERS.

The registry id that you see is the Party_number field from hz_parties [TCA Party Table]

Now, lets have a look at the list of tables impacted by creating the above Supplier record. I am not saying that inserting into below listed tables is the way to create Suppliers in R12 TCA Model [Use API's for that]. This article is purely for your understanding of the new data model for Suppliers in R12 TCA.

Of course this will also be helpful to you when developing reports in R12.

Table HZ_PARTIES SELECT * FROM hz_parties WHERE party_name= 'Go4Gold' ; This happens to be the master table now instead of PO_VENDORS. You will notice that the PARTY_NUMBER below is the Registry id in the R12 supplier screen. Also, this party_id = 301934 will be referenced in the remainder set of tables.

Table HZ_PARTY_USG_ASSIGNMENTS SELECT party_id ,party_usg_assignment_id,party_usage_code FROM hz_party_usg_assignments WHERE party_id = 301934; This table stores the Party Usages, for example, in this case it captures the fact that the given party_id is of type SUPPLIER.

Table HZ_ORGANIZATION_PROFILES SELECT * FROM hz_organization_profiles WHERE party_id = 301934 This table captures additional Supplier information, for example, credit scoring details of Supplier or the Number of Employees working in Supplier Organization.

Table IBY_EXTERNAL_PAYEES_ALL SELECT * FROM iby_external_payees_all WHERE payee_party_id = 301934

This table captures Payment related details of the Supplier. For example :1. How should the supplier's remittance advice must be sent? 2. What is the default Payment method Code for this supplier? 3. Who bears the bank charges when lets say SWIFT payment is made? This information can be setup at either the Supplier level or at Supplier Site level.

Table AP_SUPPLIERS SELECT vendor_id, vendor_name,segment1,enabled_flag FROM ap_suppliers WHERE party_id = 301934 Alongside HZ_PARTIES, this is another master table that replaces the PO_VENDORS table of 11i. Instead of expanding the design of HZ_PARTIES, oracle decided to hold the supplier specific attributes in AP_SUPPLIERS [fair enough ! ].

Table POS_SUPPLIER_MAPPINGS SELECT * FROM pos_supplier_mappings WHERE party_id = 301934 This table holds the mapping between the AP_SUPPLIERS.VENDOR_ID and HZ_PARTIES.PARTY_ID. This is useful in cases whereby two vendors same HZ_Party Record. effectively belong the

Table ZX_PARTY_TAX_PROFILE SELECT party_type_code, party_tax_profile_id FROM zx_party_tax_profile WHERE party_id = 301934 The taxation related details like Tax Codes, and Tax Accounts etc have

been moved from AP into ZX. ZX is the name of a new Application "E-Business Tax".

Efectively this application is the Tax repository/Taxation Engine for eBusiness Suite starting from R12. Effectively this also means that our good old AP_TAX_CODES_ALL is no longer the master table for Taxes. Now we have a new tax rate table, i.e. ZX_RATES_B. ZX_ACCOUNTS is another table that has been introduced to capture accounting setup related to Tax Codes.

Database View PO_VENDORS select vendor_name, segment1, party_number from po_vendors WHERE party_id = 301934 PO_VENDORS is a view in R12, that joins AP_SUPPLIERS & HZ_PARTIES. Similarly, PO_VENDOR_SITES and PO_VENDOR_SITES_ALL are also views based upon AP_SUPPLIER_SITES_ALL.