AR:

1. What is TCA? Tables?

A) Trading Community Architecture. It is a centralized repository of business entities such as

Partners, Customers, and Organizations etc. It is a new framework developed in Oracle 11i.

HZ_PARTIES: The HZ_PARTIES table stores basic information about parties that can be shared with any relationship that the party might establish with another party. Although a record in the HZ_PARTIES table represents a unique party, multiple parties can have the same name. The parties can be one of four types:Organization for example, Oracle CorporationPerson for example, Jane DoeGroup for example, World Wide Web ConsortiumRelationship for example, Jane Doe at Oracle Corporation.

HZ_LOCATIONS: 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.

HZ_PARTY_SITES: The HZ_PARTY_SITES table links a party (see HZ_PARTIES) and a location (see HZ_LOCATIONS) and stores location-specific party information. One party can optionally have one or more party sites. One location can optionally be used by one or more parties. This party site can then be used for multiple customer accounts within the same party.

HZ_CUST_ACCT_SITES_ALL

HZ_CUST_SITE_USES_ALL

HZ_CUST_CONTACT_POINTS etc.

2. What are Base Tables or Interface Tables for Customer Conversions, Autolockbox, Auto

Invoice?

A) Customer Conversion:

Interface Tables : RA_CUSTOMERS_INTERFACE_ALL,

RA_CUSTOMER_PROFILES_INT_ALL,

RA_CONTACT_PHONES_INT_ALL,

RA_CUSTOMER_BANKS_INT_ALL,

RA_CUST_PAY_METHOD_INT_ALL

Base Tables : RA_CUSTOMERS, RA_ADDRESSES, RA_SITE_USES_ALL,

RA_CUSTOMER_PROFILES_ALL, RA_PHONES etc

B) Auto Invoice:

Interface Tables : RA_INTERFACE_LINES_ALL, RA_INTERFACE_DISTRIBUTIONS_ALL

RA_INTERFACE_SALESCREDITS_ALL,

RA_INTERFACE_ERRORS_ALL

Base Tables : RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL,

RA_CUST_TRX_LINE_GL_DIST_ALL,

RA_CUST_TRX_LINE_SALESREPS_ALL,

RA_CUST_TRX_TYPES_ALL

C) AutoLockBox:

Interface Tables : AR_PAYMENTS_INTERFACE_ALL (POPULATED BY IMPORT PROCESS)

Interim tables : AR_INTERIM_CASH_RECEIPTS_ALL (All Populated by Submit Validation)

: AR_INTERIM_CASH_RCPT_LINES_ALL,

AR_INTERIM_POSTING

Base Tables : AR_CASH_RECEIPTS_ALL, AR_RECEIVABLE_APPLICATIONS_ALL,

AR_PAYMENT_SCHEDULES_ALL ( All Populated by post quick cash)

3. What are the tables in which Invoices/transactions information is stored?

A) RA_CUSTOMER_TRX_ALL, The RA_CUSTOMER_TRX_ALL table stores invoice, debit memo, commitment, bills receivable, and credit memo header information. Each row in this table includes general invoice information such as customer, transaction type, and printing instructions.

RA_CUSTOMER_TRX_LINES_ALL, The RA_CUSTOMER_TRX_LINES_ALL table stores information about invoice, debit memo, credit memo, bills receivable, and commitment lines (LINE, FREIGHT and TAX).

RA_CUST_TRX_LINE_SALESREPS_ALL, The RA_CUST_TRX_LINE_SALESREPS_ALL table stores sales credit assignments for invoice lines. If Receivables bases your invoice distributions on sales credits, a mapping exists between the sales credit assignments in this table with the RA_CUST_TRX_LINE_GL_DIST_ALL table.

The RA_CUST_TRX_LINE_GL_DIST_ALL table stores the accounting records for revenue, unearned revenue, and unbilled receivables for each invoice or credit memo line. Oracle Receivables creates one row for each accounting distribution, and at least one accounting distribution must exist for each invoice or credit memo line. Each row in this table includes the General Ledger account and the amount of the accounting entry.

The RA_CUST_TRX_LINE_SALESREPS_ALL table stores sales credit assignments for invoice lines. If Receivables bases your invoice distributions on sales credits, a mapping exists between the sales credit assignments in this table with the RA_CUST_TRX_LINE_GL_DIST_ALL table.

4. What are the tables In which Receipt information is stored?

A)

AR_PAYMENT_SCHEDULES_ALL, The AR_PAYMENT_SCHEDULES_ALL 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.Transaction classes determine if a transaction relates to either the RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALL table. Using the CUSTOMER_TRX_ID foreign key column, the AR_PAYMENT_SCHEDULES_ALL table 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. Using the CASH_RECEIPT_ID foreign key column, the AR_PAYMENT_SCHEDULES_ALL table joins to the AR_CASH_RECEIPTS_ALL table for invoice-related payment transactions.

AR_CASH_RECEIPTS_ALL, The AR_CASH_RECEIPTS_ALL table stores one record for each receipt that you enter. Oracle Receivables concurrently creates records in the AR_CASH_RECEIPT_HISTORY_ALL, AR_PAYMENT_SCHEDULES_ALL, and AR_RECEIVABLE_APPLICATIONS_ALL tables for invoice-related receipts. For receipts that are not related to invoices, such as miscellaneous receipts, Receivables creates records in the AR_MISC_CASH_DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ALL table.

AR_RECEIVABLE_APPLICATIONS_ALL, The AR_CASH_RECEIPTS_ALL table stores one record for each receipt that you enter. Oracle Receivables concurrently creates records in the AR_CASH_RECEIPT_HISTORY_ALL, AR_PAYMENT_SCHEDULES_ALL, and AR_RECEIVABLE_APPLICATIONS_ALL tables for invoice-related receipts. For receipts that are not related to invoices, such as miscellaneous receipts, Receivables creates records in the AR_MISC_CASH_DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ALL table. Cash receipts proceed through the confirmation, remittance, and clearance steps. Each step creates rows in the AR_CASH_RECEIPT_HISTORY table.

5. What are the tables in which Accounts information is stored?

RA_CUST_TRX_LINE_GL_DIST_ALL

6. What are the different statuses for Receipts?

A) Unidentified – Lack of Customer Information

Unapplied – Lack of Transaction/Invoice specific information (Ex- Invoice Number)

Applied – When all the required information is provided.

On-Account, Non-Sufficient Funds, Stop Payment, and Reversed receipt.

7. What Customization that you have done for Autolockbox?

8. What is Autolockbox?

A) Auto lockbox is a service that commercial banks offer corporate customers to enable them to

out source their account receivable payment processing. Auto lockbox can also be used to

transfer receivables from previous accounting systems into current receivables. It eliminates

manual data entry by automatically processing receipts that are sent directly to banks. It involves

three steps

Import (Formats data from bank file and populates the Interface Table),

Validation(Validates the data and then Populates data into Interim Tables),

Post Quick Cash(Applies Receipts and updates Balances in BaseTables).

9. What is Transmission Format?

A) Transmission Format specifies how data in the lockbox bank file should be organized such that

it can be successfully imported into receivables interface tables. Example, Default, Convert,

Cross Currency, Zengen are some of the standard formats provided by oracle.

10. What is Auto Invoice?

A) Autoinvoice is a tool used to import and validate transaction data from other financial systems

and create invoices, debit-memos, credit memos, and on account credits in Oracle receivables.

Using Custom Feeder programs transaction data is imported into the autoinvoice interface tables.

Autoinvoice interface program then selects data from interface tables and creates transactions in

receivables (Populates receivable base tables) . Transactions with invalid information are rejected

by receivables and are stored in RA_INTERFACE_ERRORS_ALL interface table.

11. What are the Mandatory Interface Tables in Auto Invoice?

RA_INTERFACE_LINES_ALL, RA_INTERFACE_DISTRIBUTIONS_ALL

RA_INTERFACE_SALESCREDITS_ALL.

12. What are the Set up required for Custom Conversion, Autolockbox and Auto Invoice?

A) Autoinvoice program Needs AutoAccounting to be defined prior to its execution.

13. What is AutoAccounting?

A) By defining AutoAccounting we specify how the receivables should determine the general

ledger accounts for transactions manually entered or imported using Autoinvoice. Receivables

automatically creates default accounts(Accounting Flex field values) for revenue, tax, freight,

financial charge, unbilled receivable, and unearned revenue accounts using the AutoAccounting

information.

14. What are Autocash rules?

A) Autocash rules are used to determine how to apply the receipts to the customers outstanding

debit items. Autocash Rule Sets are used to determine the sequence of Autocash rules that Post

Quickcash uses to update the customers account balances.

15. What are Grouping Rules? (Used by Autoinvoice)

A) Grouping rules specify the attributes that must be identical for lines to appear on the same

transaction. After the grouping rules are defined autoinvoice uses them to group revenues and

credit transactions into invoices debit memos, and credit memos.

16. What are Line Ordering Rules? (Used by Autoinvoice)

A) Line ordering rules are used to order transaction lines when grouping the transactions into

invoices, debit memos and credit memos by autoinvoice program. For instance if transactions are

being imported from oracle order management , and an invoice line ordering rule for sales_order

_line is created then the invoice lists the lines in the same order of lines in sales order.

17. In which table you can see the amount due of a customer?

A) AR_PAYMENT_SCHEDULES_ALL

18. How do you tie Credit Memo to the Invoice?

At table level, In RA_CUSTOMER_TRX_ALL, If you entered a credit memo, the PREVIOUS_CUSTOMER_TRX_ID column stores the customer transaction ID of the invoice that you credited. In the case of on-account credits, which are not related to any invoice when the credits are created, the PREVIOUS_CUSTOMER_TRX_ID column is null.

19. What are the available Key Flex Fields in Oracle Receivables?

A) Sales Tax Location Flex field, It’s used for sales tax calculations.

Territory Flex field is used for capturing address information.

20. What are Transaction types? Types of Transactions in AR?

A) Transaction types are used to define accounting for different transactions such as Debit

Memo, Credit Memo, On-Account Credits, Charge Backs, Commitments and invoices.

21. What is AutoAssociating?

22. What are the issues you faced in AutoInvoice and Autolockbox?

HZ tables in Oracle ReceivablesJuly 1, 20106 Comments

15 Votes

HZ(TCA) tables in Oracle Receivables

This article describes few important HZ tables in AR and their relationships with each other.

HZ_PARTIES:

The HZ_PARTIES table stores basic information about parties that can be shared with any relationship that the party might establish with another party. The primary key for this table is PARTY_ID.

Few Important Columns are

PARTY_ID: Party identifier PARTY_NUMBER: Unique identification number for this party PARTY_NAME: Name of the party PARTY_TYPE: The party type can only be Person, Organization, Group or

Relationship.

HZ_PARTY_SITES:

The HZ_PARTY_SITES table links a party (HZ_PARTIES) and a location (HZ_LOCATIONS) and stores location-specific party information. One party can optionally have one or more party sites. One location can optionally be used by one or more parties. The primary key for this table is PARTY_SITE_ID.

Few Important Columns are

PARTY_SITE_ID: Party site identifier. PARTY_ID: Identifier for the party. Foreign key to the HZ_PARTIES table. LOCATION_ID: Identifier for the party site. Foreign key to the

HZ_LOCATIONS table. PARTY_SITE_NUMBER: Party site number. PARTY_SITE_NAME: User-defined name for the site. ADDRESSEE: Addressee information.

HZ_LOCATIONS:

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. The primary key for this table is LOCATION_ID.

Few Important Columns are

LOCATION_ID: Unique identifier for this location COUNTRY: Country code from the TERRITORY_CODE column in the

FND_TERRITORY table ADDRESS1: First line for address ADDRESS2: Second line for address ADDRESS3: Third line for address ADDRESS4: Fourth line for address CITY: City POSTAL_CODE: Postal Code STATE: State ADDRESS_KEY: Derived key that facilitates fuzzy searches

HZ_CUST_ACCOUNTS:

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 relationship. Since 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. The primary key for this table is CUST_ACCOUNT_ID.

Few Important Columns are

CUST_ACCOUNT_ID: Customer account identifier PARTY_ID: A foreign key to the HZ_PARTY table. ACCOUNT_NUMBER: Account Number CUSTOMER_TYPE: Receivables lookup code for the CUSTOMER_TYPE

attribute. I for internal customers, R for revenue generating external customers. CUSTOMER_CLASS_CODE: Customer class identifier

HZ_CUST_ACCT_SITES_ALL:

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. The primary key for this table is CUST_ACCT_SITE_ID.

Few Important Columns are

CUST_ACCT_SITE_ID: Customer site identifier CUST_ACCOUNT_ID: Identifier for a customer account. Foreign key to the

HZ_CUST_ACCOUNTS table PARTY_SITE_ID: Identifier for a party site. Foreign key to the

HZ_PARTY_SITES table BILL_TO_FLAG: Indicates if this is a Bill-To site. SHIP_TO_FLAG: Indicates if this is a Ship-To site. MARKET_FLAG: Indicates if this is a Marketing site.

HZ_CUST_SITE_USES_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 foreignkey 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. The primary key for this table is SITE_USE_ID.

Few Important Columns are

SITE_USE_ID: Site use identifier CUST_ACCT_SITE_ID: Identifier for the customer account site. Foreign key to

the HZ_CUST_ACCT_SITES_ALL table SITE_USE_CODE: Business purpose assigned to customer site account, such as

Bill-To, Market, and Statements. PRIMARY_FLAG: Indicates if this site is the primary site for this customer

account. Y for the primary customer account site. N for other customer account sites.

HZ_CUSTOMER_PROFILES:

The HZ_CUSTOMER_PROFILES table stores information about the credit characteristics of a single customer account or a customer account site or a party. A profile class defined in theHZ_CUSTOMER_PROFILE_CLASSES table can be used to provide default values for the attributes in this table. The primary key for this table is CUST_ACCOUNT_PROFILE_ID.

Few Important Columns are

CUST_ACCOUNT_PROFILE_ID: Unique identifier of this customer profile CUST_ACCOUNT_ID: Identifier for the Customer Account. Foreign key to the

HZ_CUST_ACCOUNTS table. STATUS: Indicates whether the profile is active or inactive

HZ_CUST_PROFILE_CLASSES:

The HZ_CUST_PROFILE_CLASSES table stores information about the credit characteristics that are common across a group of customer accounts. The characteristics specified in this table can be used as default characteristics for similar customer accounts. The primary key for this table is PROFILE_CLASS_ID.

HZ_PARTY_RELATIONSHIPS:

The HZ_PARTY_RELATIONSHIPS table stores information about relationships between parties.

SELECT * from hz_cust_site_uses_all hcsua, hz_cust_acct_sites_all hcasa, hz_party_sites hps,

hz_cust_accounts hca, hz_parties hp

where hcsua.site_use_code = 'BILL_TO' / 'SHIP_TO'

and hcsua.cust_acct_site_id = hcasa.cust_acct_site_id

and hps.party_site_id = hcasa.party_site_id

and hcasa.cust_account_id = hca.cust_account_id

and hp.party_id = hps.party_id;

The Customer conversion can be done in 2 ways:1. loading data into all interface tables and running the customer interface 2. running through API’s priovided by oracle

Below are some of the useful tables and API’s for customer interface.

Interface tables: RA_CUSTOMERS_INTERFACE_ALL

RA_CUSTOMER_PROFILES_INT_ALL

RA_CONTACT_PHONES_INT_ALL

RA_CUSTOMER_BANKS_INT_ALL

RA_CUST_PAY_METHOD_INT_ALL

Base tables: HZ_PARTIES

HZ_CONTACTS

HZ_PROFILES

HZ_LOCATIONS

Base tables for RA_CUSTOMERS_INTERFACE_ALL

RA_CUSTOMERS

RA_ADDRESSES_ALL

RA_CUSTOMER_RELATIONSHIPS_ALL

RA_SITE_USES_ALL

Uses TCA APIs.

Concurrent program: Customer Interface

Validations: Check if legacy values fetched are valid.

; Check if customer address site is already created.

Check if customer site use is already created.

Check is customer header is already created.

Check whether the ship_to_site has associated bill_to_site

Check whether associated bill_to_site is created or not.

Profile amounts validation: validate cust_account_id, validate customer status.

Check if the location already exists in HZ_LOCATIONS. If does not exist, create new location.

Customer API

1. Set the organization id

Exec dbms_application_info.set_client_info(‘204’);

2. Create a party and an account

HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT()

HZ_CUST_ACCOUNT_V2PUB.CUST_ACCOUNT_REC_TYPE

HZ_PARTY_V2PUB.ORGANIZATION_REC_TYPE

HZ_CUSTOMER_PROFILE_V2PUB.CUSTOMER_PROFILE_REC_TYPE

3. Create a physical location

HZ_LOCATION_V2PUB.CREATE_LOCATION()

HZ_LOCATION_V2PUB.LOCATION_REC_TYPE

4. Create a party site using party_id you get from step 2 and location_id from step 3.

HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE()

HZ_PARTY_SITE_V2PUB.PARTY_SITE_REC_TYPE

5. Create an account site using account_id you get from step 2 and party_site_id from step 4.

HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_ACCT_SITE()

HZ_CUST_ACCOUNT_SITE_V2PUB.CUST_ACCT_SITE_REC_TYPE

6. Create an account site use using cust_acct_site_id you get from step 5 ans site_use_code = ‘BILL_TO’.

HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_SITE_USE()

HZ_CUST_ACCOUNT_SITE_V2PUB.CUST_SITE_USE_REC_TYPE

HZ_CUSTOMER_PROFILE_V2PUB.CUSTOMER_PROFILE_REC_TYPE

Base table:

· HZ_PARTIES

· HZ_PARTY_SITES

· HZ_LOCATIONS

· HZ_CUST_ACCOUNTS

· HZ_CUST_SITE_USES_ALL

· HZ_CUST_ACCT_SITES_ALL

· HZ_PARTY_SITE_USES

Validations: Check if legacy values fetched are valid.

Check if customer address site is already created.

Check if customer site use is already created.

Check is customer header is already created.

Check whether the ship_to_site has associated bill_to_site

Check whether associated bill_to_site is created or not.

Profile amounts validation: validate cust_account_id, validate customer status.

Check if the location already exists in HZ_LOCATIONS. If does not exist, create new location.