Sie sind auf Seite 1von 20

Database Diagrams

This section graphically represents most of the significant Oracle Receivables applications tables and the relationships between them, organized by building block. Use this section to quickly learn what tables each Oracle Receivables application building block uses, and how these tables interrelate.

This section contains a database diagram for each of the following Oracle Receivables application building blocks: Diagram 1: Diagram 2: Diagram 3: Diagram 4: Diagram 5: Diagram 6: Diagram 7: Diagram 8: Diagram 9: Diagram 10: Diagram 11: Diagram 12: Diagram 13: Diagram 14: Diagram 15: Diagram 16: Customer Interface Customers Customer Usage Tax Groups Transactions Bills Receivable Sales Tax Interface United States Sales Tax Receipts Posting Party Party Merge Classification Organization Person Contact Point

Some tables, especially important reference tables, appear in more than one database diagram. When several building blocks use a table, we show that table in each appropriate database diagram. Customer Interface Diagram 1 shows the tables and relationships that show imported customer data. This information includes original system customer

number, original address reference numbers, customer site, and interface status. Customers Diagram 2 shows the tables and relationships that store information about your customers, such as customer addresses, business purposes, contacts, telephone numbers, relationships, and classes. Customer Usage Diagram 3 shows the tables and relationships that store information about customers and transactions. The information includes customer calls, payment schedules, and correspondence. Tax Groups Diagram 4 shows the tables and relationships that store information about your tax groups. Tax groups let you calculate multiple, conditional taxes automatically based on the Ship To Province, State, Country, or Tax Classification of the Bill To customer. Transactions Diagram 5 shows the tables and relationships that store invoices, credit memos, deposits, and guarantees. You can see how shipment, salesperson, tax, general ledger distribution, receivable application, payment schedule, and adjustment records relate to the tables that store these transactions. Bills Receivable Diagram 6 shows the tables and relationships that store bills receivable. You can see how bills receivable batch, bills receivable, payment schedules and general ledger distributions relate to each other. Sales Tax Interface Diagram 7 shows the tables and relationships that store imported tax data. You can see how your customer address and transaction lines relate to sales tax rates and tax authorities.

United States Sales Tax Diagram 8 shows the tables and relationships associated with implementing Sales Tax in Oracle Receivables. You can see the tax information stored in the different tables and how they relate to each other to provide tax information for your transactions. Receipts Diagram 9 shows the tables and relationships associated with entering invoice and noninvoice related receipts. You can see how receipt batch, receipts, and payment schedules relate to each other. Posting Diagram 10 shows the tables and relationships that Oracle Receivables Applications uses to transfer batches of transaction records as journal entries from your receivables subledger to your general ledger or general ledger interface area. This information includes general ledger posted date, general ledger start and end dates, a summary or detail posting indicator, and a run journal import indicator. Party Diagram 11 shows the tables and relationships that store information about parties. The information includes party sites, locations, time zones, certifications, credit rating, and reference. Party Merge Diagram 12 shows the tables and relationships that store information about the party merge process. The information includes details about the batch that contains the parties to be merged, the tables affected by the merge process, the history of operations performed, and the details of the records affected by the process. Classification Diagram 13 shows the tables and relationships that store information about classifying entities. The information includes classification categories, the uses, entities using these categories, the codes for each of the categories, the relationships between codes, and the assignment of codes to the relevant entities.

Organization Diagram 14 shows the tables and relationships that store information about organizations, such as industrial classifications, security issued, financial reports, industrial reference, and organization indicators. Person Diagram 15 shows the tables and relationships that store information about people, such as citizenship, education, employment history, person language, and person interest. Contact Point Diagram 16 shows the tables and relationships that store contact points and contact restrictions. You can see how contact points and contact restrictions can be assigned to various entities.

How to Use These Database Diagrams


Following is an example of how you might use these database diagrams: Suppose you want to write a report that summarizes customer profile information for all of the customers that you have entered during the past six months. You turn to the Customers diagram to see the table structure for the Customers building block. You learn that customer profile information is stored in the table HZ_CUSTOMER_PROFILES. You see that information on the specific amount of money associated with each customer is stored in the HZ_CUST_PROFILE_AMTS table. Next, you turn to the Table and View Definitions section in the eTRM to learn about the columns in each of these tables. Using this information, you can write a report that shows a summary of customer profile and profile amount information for each customer.

Customer Interface

Customers

Customer Usage

Tax Groups

Transactions

Bills Receivable

Sales Tax Interface

United States Sales Tax

Receipts

Posting

Party

Party Merge

Classification

Organization

Person

Contact Point

Das könnte Ihnen auch gefallen