Oracle Receivables Module Technical Details

Posted by Arun Kumar S.R at 11:33 AM

Oracle Accounts Receivable uses the following tables for recording customer acco
unt information:
The major tables containing parties and customer accounts information in Oracle
Receivables are grouped by business function.
HZ_PARTIES
HZ_CUST_ACCOUNTS
HZ_PARTY_SITES
HZ_CUST_ACCT_SITES_ALL
HZ_CUST_SITE_USES_ALL
HZ_LOCATIONS
HZ_PARTY_RELATIONSHIPS
HZ_ORGANIZATION_PROFILES
HZ_CONTACT_POINTS
HZ_CUST_ACCOUNT_ROLES
HZ_PERSON_PROFILES
HZ_ORG_CONTACTS
Transaction Tables
RA_CUSTOMER_TRX_ALL
RA_CUSTOMER_TRX_LINES_ALL
RA_CUST_TRX_LINE_GL_DIST_ALL
AR_PAYMENT_SCHEDULES_ALL
AR_CASH_RECEIPTS_ALL
AR_CASH_RECEIPT_HISTORY_ALL
AR_RECEIVABLE_APPLICATIONS_ALL
AR_ADJUSTMENTS_ALL
HZ_PARTIES
A party is an entity that can enter into a business relationship.
This table stores basic information about parties, which is true regardless of t
his relationship to the deploying company. Entities are modeled only once in HZ_
PARTIES, regardless of how many roles they play. For example, if an organization
is a customer, a distributor, and a partner, there is still only one record for
them in HZ_PARTIES.
Parties can be one of four types:
Organization - Oracle Corporation
Person - Jane Doe
Group Doc Household
Relationship - Jane Doe at Oracle Corporation
HZ_LOCATIONS
A location is a point in geographical space described by an address and/or geogr
aphical Indicators such as latitude or longitude.
This table stores information about an address such as: street address and posta
l code.
This table provides physical location information about parties (organizations a
nd people) and customer accounts.
Records in HZ_LOCATIONS can store delivery and postal code information about a l
ocation, store latitude and longitude, and can be used to determine the appropri
ate calculations and tax rates for sales tax and VAT calculations.
HZ_PARTY_SITES
This table links a party (HZ_PARTIES) and a location (HZ_LOCATIONS) and stores l
ocation-Specific party information such as a person s mail stops at their work add
ress.
 One party can point to one or more party sites.
One location can point to one or more party site.
Party sites serve as the intersection between parties and locations, allowing fo
r a many-to-many relationship between the two.
HZ_RELATIONSHIPS
This table stores information about relationships between two entities, for exam
ple, one party and another party.
The SUBJECT_ID and OBJECT_ID columns specify the relationship that exists betwee
n two parties. For example, if the party relationship type is Parent Of, then a ho
lding company could be the SUBJECT_ID in the relationship while one of its subsidi
aries could be the OBJECT_ID. Creating a party contact causes a party relationsh
ip to be created.
A party can have different relationships with one or more other parties that can
change over time.
HZ_ORGANIZATION_PROFILES
This table stores a variety of information about a party of type Organization.
This table gets populated when a party of type ORGANIZATION is created.
Historical data is also stored in this table.
HZ_PERSON_PROFILES
This table stores a variety of information about a party of type Person.
For example, this table could contain the correct spelling and phonetic pronunci
ation of the person s name.
Some information in this table may also be entered into the HZ_PARTIES table.
HZ_ORG_CONTACTS
This table stores a variety of information about an organization contact.
The records in this table provide information about a contact position such as j
ob title, rank, and department.
This table is not used to store information about a specific person or organizat
ion. For example, this table may include a record for the position of Vice Presi
dent of Manufacturing that indicates that the contact is a senior executive, but
it would not include the name of the person in that position.
HZ_CUST_ACCOUNTS
This table stores information about customer/financial relationships established
between a Party and the deploying company.
Because a party can have multiple customer accounts, this table may contain seve
ral records for a single party. For example, an individual person may establish
a personal account, a family account, and a professional account for a consultin
g practice.
HZ_CUST_ACCT_SITES_ALL
This table stores information about customer/financial account sites information
.
Stores information about customer sites. One customer account can have multiple
sites.
HZ_CUST_SITE_USES_ALL
This table stores information about the business purposes assigned to a customer
account site.
A customer account site can have multiple purposes, but each record in this tabl
e only specifies one purpose for a customer account site. For example, a custome
r account site may be assigned as a ship-to site in one record and as a bill-to
site in another record.
HZ_CUST_ACCOUNT_ROLES
This table stores information about a role or function that a party performs as
related to a customer account. For example, Jane Doe might be the Legal Contact
for a specific customer account of Corporation ABC. Note that account ownership
such as financial responsibility for an account is determined by the single part
y ID that is stored directly on the HZ_CUST_ACCOUNTS table.
HZ_CONTACT_POINTS
This table stores information about how to communicate with parties or party sit
es using electronic media or methods such as Electronic Data Interchange (EDI),
e-mail, telephone, telex, and the Internet.
Each medium or method should be stored as a separate method in this table. For e
xample, the attributes of a complete telephone number connection should be store
d in a record, while EDI information should be stored in a different record.
RA_CUSTOMER_TRX_ALL
This table stores invoice, debit memo, commit-ment, chargeback, bills receivable
, and credit memo header information.
Each row includes general invoice information such as customer, transaction type
, and printing instructions.
You need one row for each invoice, debit memo, commitment, and credit memo you c
reate in Oracle Receivables and these are all distinguished by their transaction
types stored in RA_CUST_ TRX_ TYPES_ALL.
RA_CUSTOMER_TRX_LINES_ALL
This table stores information about invoice, debit memo, credit memo, bills rece
ivable, and commitment lines. It describes to the customer the charges that appe
ar on these documents.
AR_PAYMENT_SCHEDULES_ALL
This table stores all transactions except adjust-ments and miscellaneous cash re
ceipts. A miscellaneous cash receipt is one that is not connected to a customer.
All customer-related activity is logged in this table.
This table is updated when an activity occurs against an invoice, debit memo, ch
argeback, credit memo, on-account credit, bills receivable,
receipt, or commitments.
RA_CUST_TRX_TYPES_ALL
This table stores information about each transaction type for all classes of tra
nsactions, for example, invoices, commitments, and credit memos.
Each row includes Auto Accounting information
as well as standard defaults for the resulting invoices. The primary key for thi
s table is CUST_TRX_TYPE_ID.
AR_TRANSACTION_HISTORY_ALL
This table is a Bills Receivable-specific table containing the history of a tran
saction s lifecycle.
A new row is created each time there is activity on the transaction or the statu
s of the transaction has changed.
This table stores the header for the Receivables posting information.
AR_DISTRIBUTIONS_ALL
This table stores the accounting distributions for cash receipts, miscellaneous
receipts, adjustments, credit memo applications, cash receipt applications, and
bills receivable transactions.
AR_CASH_RECEIPTS_ALL
This table stores one record for each receipt entry.
All cash receipts are logged in this table.
Oracle Receivables creates records concurrently in the AR_CASH _RECEIPT_ HISTORY
_ ALL, AR_PAYMENT_ SCHEDULES_ ALL, AR_DISTRI-BUTIONS_ALL, and AR_ RECEIVABLE_ AP
PLICA-TIONS_ALL tables for invoice-related receipts.
 For receipts that are not related to invoices, records are created in the AR_MIS
C_CASH_ DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ ALL t
able.
AR_CASH_RECEIPT_HISTORY_ALL
This table stores all of the activity that is contained for the life cycle of a
receipt.
Each row represents one step.
The status field for that row tells you which step the receipt has reached.
Possible statuses are Approved, Confirmed, Remitted, Cleared, and Reversed.
AR_RECEIVABLE_APPLICATIONS_ALL
This table stores all accounting entries for cash and credit memo applications.
Each row includes the amount applied, status, and accounting flex field informat
ion.
AR_MISC_CASH_DISTRIBUTIONS_ALL
This table stores all accounting entries for miscellaneous cash applications.
Miscellaneous cash cannot be invoiced, such as stock revenue, interest income, a
nd investment income.
AR_CASH_RECEIPTS_ALL stores one record for each payment, and this table stores o
ne record for each distribution of the receipt.
AR_RECEIPT_CLASSES
This table stores the different receipt classes that you define.
Receipt classes determine whether the receipt[s] belonging to this class are cre
ated manually or automatically, and whether the receipts go through the differen
t steps in a receipt s life-cycle.
AR_RECEIPT_METHODS
This table stores information about Payment Methods, receipt attributes that you
define and assign to Receipt Classes to account for receipts and their applicat
ions.
For automatically created receipts, a Payment Method defines the rules for creat
ing these receipts.
For manually created receipts, a Payment Method defines a user-definable type fo
r the receipt.
Each Payment Method is associated with a set of bank accounts, which forms the s
et of bank accounts you can assign to your receipt.
AR_ADJUSTMENTS_ALL
This table stores information about the adjustment applied to the Invoices.