Académique Documents
Professionnel Documents
Culture Documents
/* CUSTOMER INFORMATION :
Not quite sure why two different sets of tables are maintained.?? Actually
historically all the customer information is owned and stored by AR.So the data
is stored in tables like ra_customers, ra_contacts etc.
However since customer information is shared universally by all products a
central common repository of customer data is needed which is what is TCA.
All the tca tables start with hz_ i.e hz_parties, hz_party_sites etc. And the
ra_customers etc tables converted now into view from tables and these views
will now base on these hz related tables.
1
optional information like taxpayerid, profile, freight terms(shipping
terms). A profile class basically gives us the informationn about how
good a customer is (from customers menu), who should be the collector,
where the dunning letters and statements to be sent,payment terms,
finance charges for overdue invoices etc.
Now for each customer we can enter more than one addresses
or multiple addresses.The communication and contact information entered
for the customer is different from the comm and contact information for
each of the customer addresses. Now suppose say we have entered all the
information for a customer,like comm,contact etc and also two addresses.
Now we open one of these addresses and create a business purpose for
this address i.e whether this business should be used as a bill_to or
ship_to etc and enter the corresponding sales territory information
for the bill to address. */
/* Party_sites stores the relation ship between the parties and locations
and the relation ship is a many-many relationship. i.e 1 party can
have many locations(or addresses) and 1 address can be used by
many parties.*/
select party_site_id, party_site_number, party_site_name, party_id,
location_id, orig_system_reference,
creation_date, status
from hz_party_sites
order by creation_date desc
2
site is used. Party sites can have multiple
uses, for example Ship-To and Bill-To.*/
select party_site_use_id, party_site_id,site_use_type,application_id,
creation_date
from hz_party_site_uses
begin
fnd_client_info.set_org_context(fnd_profile.value('ORG_ID'));
end;
/*So having done all the above stuff, we should be able to succesfully
create an transaction batch and an invoice in it. The data goes
into the "ra_customer_trx_all" and if the lines are also created,
the info goes into "ra_customer_trx_lines_all"
Internal Customers : Internal means you can define your own company
as a customer,so that we can place internal sales orders.
3
Whether it is internal or external customer, when we are creating a
ship_to purpose for a particular address we can associate it to a
location which is inventory location. That is we can understand it as,
this particular customer will be shipped from this particular inventory
location.
*/
I believe the contacts are only defined for the sites, i.e for the
bill-to and ship-to sites.
*/
Relationship Manager :
4
Import Batch to TCA registry : this program basically imports the data at the
party level and NOT the customer level. If you want tcustomer level data to be
imported, use the customer interface.
There are two kinds of import Party Import and Customer Import. The import that you
do in the TCA is Party Import. Customer Import is what you do in AR Receivables.
Some of the interface tables that are used in the Bulk data import are
hz_imp_parties_int
hz_imp_contacts_int
After the data is loaded into the interface tables, we run the Import program.
One thing we need to remember is that the customer import that we run in the AR
does not care about this import.
So when the customer import runs, it will create a customer and whenever it
creates a new customer, it also creates a new party, even though if there is an
associated party existing. This can result in the duplication of the parties. And
for the same reason, we have the de-duplication programs.
Customer Interface