Let us now understand who is a Supplier with the help of a simple example:
We consider us as a business, who sells dry fruits on a large scale, now all the Vendors who intend to consume dry fruits would be contacting us. So with this perspective we become the Supplier to all the vendors and these vendors are our Customers.
Now to automate this process at the Vendors perspective the Supplier information are to be recorded so for this we have a suppliers window to record information about individuals and companies that provides goods or services from whom a vendor purchases those goods and services in return for payment. The information about the Supplier, Supplier Site, Supplier Contacts & Banks are recorded and these are created as one time setups and are not the daily activities which are later updated when ever required.
Change in the approach for Supplier on R12 when compare to 11i:
Release 11iRelease R12
In 11i Suppliers were defined in AP
In R12 Suppliers have been moved into the TCA Data Model.
a) Creation of a vendor/supplier record in eBusiness suite largely meant insertion of records in PO_VENDORS.a) Supplier becomes as TCA Party.
b) Suppliers Sites as TCA Party Site for each distinct address.
c) Contacts for each supplier/address , it means Single supplier address and contact can be leveraged by multiple sites, for each OU.
Banks/Branches defined in AP
Banks and Branches are defined as Parties in TCA
Suppliers in R12:
When compare to the earlier release, in R12 Suppliers and Banks are also part of TCA. Suppliers Sites are as TCA Party Site for each distinct address. A single change to an address can be seen instantly by all OUs, this has an added advantage we no longer need to manually ‘push’ updates across OUs.
This is best illustrated below:
Going further Bank Accounts are classified into Internal & External Bank Accounts
The typical data model for bank can be summarized as below:
Note: Adding to the above information, more details on the supplier when related to TCA (Trading Community Architecture) have been mentioned in my blog “R12 TCA (Trading Community Architecture)”, Request you to please do refer my blog for more details.
We now move further on how a supplier can be created in R12.
Supplier Creation
Supplier in R12 can be created in the below ways:
  • Front End (OAF Screen)
  • Using API
  • Using Standard Interface
 Below is the Step by Step approach for creation Supplier, we can observe that all the screens are been designed using Oracle Application Framework (OAF)
  • Navigation
  •  Create New Supplier Record: It is best to search first to ensure that duplicate suppliers are not being created.
  •  Create New Supplier: Enter the supplier organization information as displayed below. Fields with an asterisk (*) are required.
  •  Create Supplier – Organization Region <additional optional fields>
  • Create Supplier – Address Book Region to add supplier sites
  • Create Supplier – Address Book Region to add supplier sites
  • Create Supplier – Address Book Region to add supplier sites
  • Create Supplier – Add site to Operating Unit
  • Create Supplier – Contact Directory region – Add supplier contact
  • Create Supplier – Contact Directory region – Add supplier contact
  • Create Supplier – Banking Details region – Add/Create bank accounts. This is a change from R11i.
  • Create Supplier – Banking Details region – To Add/Create bank accounts
  • Create Supplier – Tax and reporting region captures the transaction tax information for the supplier.
  • Create Supplier – Payment Details region identifies default payment methods.
Technical details about the tables that stores the Supplier Information and the list of API’s that can be used in creating the Supplier from backend would be provided in my next post soon. keep watching this Space………


Suppliers in TCA - A dive into Vendor Tables in R12

Prior to R12, creation of a vendor/supplier record in eBusiness suite largely meant insertion of record in PO_VENDORS.
However, from R12 onwards, records are inserted into at least half a dozen tables when a single Supplier record is created.
This is largely due to the fact that Suppliers have been moved into the TCA DataModel.

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.
This is purely for your understanding of the new data model for Suppliers in R12 TCA.
Of course this will be helpful to you when developing reports in R12.

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.

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.

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.

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.

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 ! ].

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  effectively belong  the same HZ_Party Record.

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.

Post a Comment