Transactions of account receivables will be created
automatically by ' Autoinvoice Master program ' or manually by the business
user. In
automatic process, the autoinvoice master program will do all the validations
from interface table and the valid transactions will get created in Receivables
as Invoice or credit memo etc based on its transaction type. Once the
transaction is created in AR, it will possibly affect the tables listed below.
RA_CUSTOMER_TRX_ALL
Each of this table description will be stated in this
website:
http://knoworacle.wordpress.com/2009/03/07/useful-oracle-11i-receivable-tables-informations/
RA_CUSTOMER_TRX_ALL
àThis
table stores invoice, debit memo, commitment, and credit memo header information. Each
row includes general invoice information such as customer, transaction type,
and printing instructions.
àInvoices, debit memos,
credit memos, and commitments are all distinguished by their transaction types
stored in RA_CUST_TRX_TYPES_ALL.
à If you entered a
credit memo, PREVIOUS_CUSTOMER_TRX_ID stores the customer transaction identifier
of the invoice you credited. In the case of on account credits, which are not
related to any invoice at creation, PREVIOUS_CUSTOMER_TRX_ID is null.
à If
you created an invoice against a commitment, Oracle Receivables stores the
customer transaction identifier of the commitment in INITIAL_CUSTOMER_TRX_ID,
otherwise it is null.
àCOMPLETE_FLAG
stores ’Y’ for Yes and ’N’ for No to indicate if your invoice is complete. When
you complete an invoice, Oracle Receivables creates your payment schedules and
updates any commitments against this invoice.
àBefore
an invoice can be completed, it must have at least one invoice line, revenue
records must exist for each line and add up to the line amount, and a sales tax
record must exist for each line.
Required
Columns:
RA_CUSTOMER_TRX_LINES_ALL
This table stores
information about invoice, debit memo, credit memo, and commitment lines.
QUANTITY_ORDERED stores the amount of product ordered. QUANTITY_INVOICED stores
the amount of product invoiced. For invoices entered through the window,
QUANTITY_ORDERED and QUANTITY_INVOICED must be the same. For invoices imported
through AutoInvoice, QUANTITY_ORDERED and QUANTITY_INVOICED can be different.
UOM_CODE stores the unit of measure code as defined in MTL_UNITS_OF_MEASURE.
UNIT_STANDARD_PRICE stores the list price per unit for this transaction line.
UNIT_SELLING_PRICE stores the selling price per unit for this transaction line.
LINE_TYPE differentiates between the different types of lines that are stored in this table.
LINE points to regular invoice lines that normally refer to an item. TAX signifies that this is a tax line.
There must be at least one row in the table RA_CUST_TRX_LINE_GL_DIST
(which stores accounting information), even for non–postable transactions.
The primary key for this table is CUST_TRX_LINE _ID.
RA_CUST_TRX_LINE_GL_DIST_ALL
This table stores the accounting records for revenue,
unearned revenue and unbilled receivables for each invoice or credit memo line.
Each row includes the GL(Receivables uses this information to post the proper amounts to your general ledger) account and the amount of the accounting entry.
ACCOUNT_CLASS
defines which type of distribution row you are on. The ACCOUNT_CLASS REC
represents the receivable account and is for the total amount of the invoice.
There can be at most two REC rows. One that has a ACCOUNT_SET_FLAG set to Y and
the other has ACCOUNT_SET_FLAG set to N.
Using account class column we can identify that either
‘REC’,’REV’,TAX etc.
AR_PAYMENT_SCHEDULES_ALL
This table stores all transactions except adjustments and
miscellaneous cash receipts. Oracle Receivables updates this table when
activity occurs against an invoice, debit memo, chargeback, credit memo, on
account credit, or receipt.
AMOUNT_DUE_REMAINING, amount_due_original,
due_date
are available in in this table.
Transaction classes determine which columns in this table Oracle Receivables updates when a transaction occurs, and whether a transaction relates to either the RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALLtable. AR_PAYMENT_SCHEDULES_ALL joins to the RA_CUSTOMER_TRX_ALL table for non–payment transaction entries such as the creation of credit memos, debit memos, invoices, chargebacks, or deposits. AR_PAYMENT_SCHEDULES_ALL uses the foreign key CUSTOMER_TRX_ID to join to the RA_CUSTOMER_TRX_ALL table for these transactions. AR_PAYMENT_SCHEDULES_ALL joins to the AR_CASH_RECEIPTS_ALL table for invoice–related payment transactions using the foreign key CASH_RECEIPT_ID.
When a receipt is applied, Oracle Receivables updates
AMOUNT_APPLIED, STATUS and AMOUNT_DUE_REMAINING. STATUS changes from ’OP’ to
’CL’for any transaction that has an AMOUNT_DUE_REMAINING value of 0(Zero). ACTUAL_DATE_CLOSED and GL_DATE_CLOSED
are populated with the date of the latest transaction.
AR_RECEIVABLES_TRX_ALL
This table links accounting information with your Receivables
Activities. Possible types of activities include Adjustment, Miscellaneous
Cash, and Finance Charges.
AR_RECEIVABLE_APPLICATIONS_ALL
This table stores all accounting entries for your cash and
credit memo applications. Each row includes the amount applied, status, and
accounting flexfield information. Possible statuses of your applications
include APP, UNAPP, ACC, and UNID.
http://knoworacle.wordpress.com/2009/03/07/useful-oracle-11i-receivable-tables-informations/
This table stores
information about invoice, debit memo, credit memo, and commitment lines.
QUANTITY_ORDERED stores the amount of product ordered. QUANTITY_INVOICED stores
the amount of product invoiced. For invoices entered through the window,
QUANTITY_ORDERED and QUANTITY_INVOICED must be the same. For invoices imported
through AutoInvoice, QUANTITY_ORDERED and QUANTITY_INVOICED can be different.
UNIT_STANDARD_PRICE stores the list price per unit for this transaction line.
UNIT_SELLING_PRICE stores the selling price per unit for this transaction line.
LINE_TYPE differentiates between the different types of lines that are stored in this table.
LINE points to regular invoice lines that normally refer to an item. TAX signifies that this is a tax line.
There must be at least one row in the table RA_CUST_TRX_LINE_GL_DIST
(which stores accounting information), even for non–postable transactions.
Transaction classes determine which columns in this table Oracle Receivables updates when a transaction occurs, and whether a transaction relates to either the RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALLtable. AR_PAYMENT_SCHEDULES_ALL joins to the RA_CUSTOMER_TRX_ALL table for non–payment transaction entries such as the creation of credit memos, debit memos, invoices, chargebacks, or deposits. AR_PAYMENT_SCHEDULES_ALL uses the foreign key CUSTOMER_TRX_ID to join to the RA_CUSTOMER_TRX_ALL table for these transactions. AR_PAYMENT_SCHEDULES_ALL joins to the AR_CASH_RECEIPTS_ALL table for invoice–related payment transactions using the foreign key CASH_RECEIPT_ID.
Oracle Receivables Module Technical Details
Oracle Accounts Receivable uses the following tables for recording customer account 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 this 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 geographical Indicators such as latitude or longitude.
• This table stores information about an address such as: street address and postal code.
• This table provides physical location information about parties (organizations and people) and customer accounts.
• Records in HZ_LOCATIONS can store delivery and postal code information about a location, store latitude and longitude, and can be used to determine the appropriate 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 location-Specific party information such as a person’s mail stops at their work address.
• 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 for a many-to-many relationship between the two.
HZ_RELATIONSHIPS
This table stores information about relationships between two entities, for example, one party and another party.
• The SUBJECT_ID and OBJECT_ID columns specify the relationship that exists between two parties. For example, if the party relationship type is “Parent Of,” then a holding company could be the “SUBJECT_ID” in the relationship while one of its subsidiaries could be the OBJECT_ID. Creating a party contact causes a party relationship 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 pronunciation 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 job title, rank, and department.
• This table is not used to store information about a specific person or organization. For example, this table may include a record for the position of Vice President 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 several records for a single party. For example, an individual person may establish a personal account, a family account, and a professional account for a consulting 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 table only specifies one purpose for a customer account site. For example, a customer 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 party 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 sites 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 example, the attributes of a complete telephone number connection should be stored 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 create 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 receivable, and commitment lines. It describes to the customer the charges that appear on these documents.
AR_PAYMENT_SCHEDULES_ALL
This table stores all transactions except adjust-ments and miscellaneous cash receipts. 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, chargeback, 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 transactions, 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 this table is CUST_TRX_TYPE_ID.
AR_TRANSACTION_HISTORY_ALL
This table is a Bills Receivable-specific table containing the history of a transaction’s lifecycle.
• A new row is created each time there is activity on the transaction or the status 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_ APPLICA-TIONS_ALL tables for invoice-related receipts.
• For receipts that are not related to invoices, records are created in the AR_MISC_CASH_ DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ ALL table.
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 information.
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, and investment income.
• AR_CASH_RECEIPTS_ALL stores one record for each payment, and this table stores one 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 created manually or automatically, and whether the receipts go through the different 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 applications.
• For automatically created receipts, a Payment Method defines the rules for creating these receipts.
• For manually created receipts, a Payment Method defines a user-definable type for the receipt.
• Each Payment Method is associated with a set of bank accounts, which forms the set of bank accounts you can assign to your receipt.
AR_ADJUSTMENTS_ALL
This table stores information about the adjustment applied to the Invoices.
No comments:
Post a Comment