EBS中客户表的关系

该是两个目的：< /p>

1

，灵活，

2

， 减少冗余。

整理了从

Oracle< /p>

官网上的表说明如下：

/*

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

------- ----------------------------------------------*/

/* ------------------------------------ --------------------- AR

-------------- -------------------------------------------------- ---*/

/* ------------------------------ ---------------------------*/

/*--

客户题头表

,The HZ_CUST_ACCOUNTS table stores information about customer

accounts , or business relationships that the deploying company

establishes with a party of type Organization or Person. This table focuses on

business relationships and how transactions are conducted

in

the

a

party

can

have

multiple

customer

accounts,

this

table

might contain several records for a single party.

For example, an individual person can establish a personal account, family

account, and a professional account for a consulting practice. */

select * from _CUST_ACCOUNTS;

/*--

客户地址表

The HZ_CUST_ACCT_SITES_ALL table stores all customer account

sites across all operating units. Customer account sites are

addresses,

for

customer

accounts,

where

the

deploying

company

does

business

with

its customers. One customer account can have multiple

customer

account

sites,

and

customer

account

sites

for

one

customer

account

can

belong to multiple operating units. */

select * from _CUST_ACCT_SITES_ALL;

/*--

客户业务目的表

The HZ_CUST_SITE_USES_ALL table stores business purposes

assigned to customer account sites, for example Bill-To, Ship-To, and

Statements. Each customer account site can have one or more purposes.

This table is a child of the HZ_CUST_ACCT_SITES_ALL table, with the foreign

key CUST_ACCT_SITE_ID. The HZ_CUST_SITE_USES_ALL table also stores operating

unit identifier, though the HZ_CUST_ACCT_SITES_ALL table itself stores the

operating unit for customer account sites.*/

select * from _CUST_SITE_USES_ALL;

/*The HZ_LOCATIONS table

stores information

about a delivery or postal

address

such as building number, street address, postal code,

and

directions

to

a

location.

This

table

provides

physical

location

information

about parties (organizations and people) and customer

accounts.

For

example,

you

can

store

information

such

as

Building

300,

500

Oracle

Parkway, 94065, and

from highway 101, go east on Twin Dolphins Drive, turn left on Oracle Parkway,

watch for the Building 300 sign on your right.

Records

in

the

HZ_LOCATIONS

table

can

store

delivery

and

postal

information

about

a location through columns such as the LOCATION_DIRECTIONS,

POST_OFFICE, and TIME_ZONE columns. You can also use the HZ_LOCATIONS table to

store latitude and longitude information. Data in the

HZ_LOCATIONS table is also used to determine the appropriate tax authority and

tax rates for sales tax and VAT calculations..

The primary key for this table is LOCATION_ID. */

select * from _locations;

/*The HZ_PARTY_SITES table links a party (see HZ_PARTIES) and a location (see

HZ_LOCATIONS. in hz_locations, there is no column of part_id) and stores

location-specific party information

such

as

MAILSTOP

and

ADDRESSEE.

One

party

can

optionally

have

one

or

more

party

sites. One location can optionally be used by one or more

parties. For example, 500 Oracle Parkway can be specified as a party site for

Oracle Corporation. This party site can then be used for

multiple customer accounts within the same party.

The primary key for this table is PARTY_SITE_ID.*/

select * from _PARTY_SITES;