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 Corporation Person for example, Jane Doe Group for example, World Wide Web Consortium Relationship 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_CUST_TRX_LINE_SALESREPS_ALL. and unbilled receivables for each invoice or credit memo line. commitment. a mapping exists between the sales credit assignments in this table with the RA_CUST_TRX_LINE_GL_DIST_ALL table. AR_PAYMENT_SCHEDULES_ALL ( All Populated by post quick cash) 3. AR_INTERIM_POSTING Base Tables : AR_CASH_RECEIPTS_ALL. 4. credit memo. and commitment lines (LINE. debit memo. Each row in this table includes general invoice information such as customer. bills receivable. RA_CUST_TRX_LINE_GL_DIST_ALL. debit memo.RA_INTERFACE_SALESCREDITS_ALL. What are the tables in which Invoices/transactions information is stored? A) RA_CUSTOMER_TRX_ALL. The RA_CUSTOMER_TRX_ALL table stores invoice. Each row in this table includes the General Ledger account and the amount of the accounting entry. What are the tables In which Receipt information is stored? A) AR_PAYMENT_SCHEDULES_ALL. RA_CUSTOMER_TRX_LINES_ALL. The RA_CUSTOMER_TRX_LINES_ALL table stores information about invoice. and at least one accounting distribution must exist for each invoice or credit memo line. unearned revenue. Oracle Receivables creates one row for each accounting distribution. credit memo. debit memo. FREIGHT and TAX). on-account credit. and credit memo header information. The RA_CUST_TRX_LINE_GL_DIST_ALL table stores the accounting records for revenue. RA_CUST_TRX_LINE_SALESREPS_ALL. or receipt. a mapping exists between the sales credit assignments in this table with the RA_CUST_TRX_LINE_GL_DIST_ALL table. Populated by Submit Validation) . and printing instructions. If Receivables bases your invoice distributions on sales credits. The RA_CUST_TRX_LINE_SALESREPS_ALL table stores sales credit assignments for invoice lines. Oracle Receivables updates this table when activity occurs against an invoice. RA_CUSTOMER_TRX_LINES_ALL. bills receivable. The AR_PAYMENT_SCHEDULES_ALL table stores all transactions except adjustments and miscellaneous cash receipts. AR_RECEIVABLE_APPLICATIONS_ALL. RA_CUST_TRX_TYPES_ALL C) AutoLockBox: Interface Tables Interim tables : AR_PAYMENTS_INTERFACE_ALL (POPULATED BY IMPORT PROCESS) : AR_INTERIM_CASH_RECEIPTS_ALL (All : AR_INTERIM_CASH_RCPT_LINES_ALL. RA_INTERFACE_ERRORS_ALL Base Tables : RA_CUSTOMER_TRX_ALL. The RA_CUST_TRX_LINE_SALESREPS_ALL table stores sales credit assignments for invoice lines. chargeback. If Receivables bases your invoice distributions on sales credits. transaction type.

Cash receipts proceed through the confirmation. debit memos. Validation(Validates the data and then Populates data into Interim Tables). It involves three steps • • Import (Formats data from bank file and populates the Interface Table). the AR_PAYMENT_SCHEDULES_ALL table joins to the RA_CUSTOMER_TRX_ALL table for non-payment transaction entries. AR_CASH_RECEIPTS_ALL. and Reversed receipt. It eliminates manual data entry by automatically processing receipts that are sent directly to banks. What are the tables in which Accounts information is stored? RA_CUST_TRX_LINE_GL_DIST_ALL 6. Stop Payment. such as miscellaneous receipts. Using the CASH_RECEIPT_ID foreign key column. For receipts that are not related to invoices. remittance.Invoice Number) Applied – When all the required information is provided. For receipts that are not related to invoices. 5. Using the CUSTOMER_TRX_ID foreign key column. Oracle Receivables concurrently creates records in the AR_CASH_RECEIPT_HISTORY_ALL. chargebacks. Each step creates rows in the AR_CASH_RECEIPT_HISTORY table. Oracle Receivables concurrently creates records in the AR_CASH_RECEIPT_HISTORY_ALL. On-Account. invoices. AR_RECEIVABLE_APPLICATIONS_ALL. such as the creation of credit memos. such as miscellaneous receipts. . Non-Sufficient Funds.Transaction classes determine if a transaction relates to either the RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALL table. What Customization that you have done for Autolockbox? 8. Receivables creates records in the AR_MISC_CASH_DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ALL table. and clearance steps. 7. The AR_CASH_RECEIPTS_ALL table stores one record for each receipt that you enter. the AR_PAYMENT_SCHEDULES_ALL table joins to the AR_CASH_RECEIPTS_ALL table for invoicerelated payment transactions. What are the different statuses for Receipts? A) Unidentified – Lack of Customer Information Unapplied – Lack of Transaction/Invoice specific information (Ex. Receivables creates records in the AR_MISC_CASH_DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ALL table. AR_PAYMENT_SCHEDULES_ALL. Auto lockbox can also be used to transfer receivables from previous accounting systems into current receivables. AR_PAYMENT_SCHEDULES_ALL. and AR_RECEIVABLE_APPLICATIONS_ALL tables for invoice-related receipts. and AR_RECEIVABLE_APPLICATIONS_ALL tables for invoice-related receipts. or deposits. The AR_CASH_RECEIPTS_ALL table stores one record for each receipt that you enter. 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.

Convert. debit-memos. Example. 11. and credit memos. Autocash Rule Sets are used to determine the sequence of Autocash rules that Post Quickcash uses to update the customers account balances. freight. Autolockbox and Auto Invoice? A) Autoinvoice program Needs AutoAccounting to be defined prior to its execution. 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. What are the Mandatory Interface Tables in Auto Invoice? RA_INTERFACE_LINES_ALL. Receivables automatically creates default accounts(Accounting Flex field values) for revenue. Transactions with invalid information are rejected by receivables and are stored in RA_INTERFACE_ERRORS_ALL interface table. Using Custom Feeder programs transaction data is imported into the autoinvoice interface tables. and on account credits in Oracle receivables. What are Autocash rules? A) Autocash rules are used to determine how to apply the receipts to the customers outstanding debit items. unbilled receivable. tax. credit memos. Cross Currency. 12. 15. 9. After the grouping rules are defined autoinvoice uses them to group revenues and credit transactions into invoices debit memos. Autoinvoice interface program then selects data from interface tables and creates transactions in receivables (Populates receivable base tables) . What is Auto Invoice? A) Autoinvoice is a tool used to import and validate transaction data from other financial systems and create invoices. 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. Zengen are some of the standard formats provided by oracle. RA_INTERFACE_DISTRIBUTIONS_ALL RA_INTERFACE_SALESCREDITS_ALL. financial charge. . 10. 14. 13. What are the Set up required for Custom Conversion. 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.• Post Quick Cash(Applies Receipts and updates Balances in BaseTables). Default. and unearned revenue accounts using the AutoAccounting information.

What are the available Key Flex Fields in Oracle Receivables? A) Sales Tax Location Flex field.16. What are Transaction types? Types of Transactions in AR? A) Transaction types are used to define accounting for different transactions such as Debit Memo. For instance if transactions are being imported from oracle order management . Territory Flex field is used for capturing address information. debit memos and credit memos by autoinvoice program. the PREVIOUS_CUSTOMER_TRX_ID column is null. In RA_CUSTOMER_TRX_ALL. On-Account Credits. If you entered a credit memo. the PREVIOUS_CUSTOMER_TRX_ID column stores the customer transaction ID of the invoice that you credited. which are not related to any invoice when the credits are created. How do you tie Credit Memo to the Invoice? At table level. It’s used for sales tax calculations. What are the issues you faced in AutoInvoice and Autolockbox? . Charge Backs. Credit Memo. 21. 19. 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. In the case of on-account credits. What is AutoAssociating? 22. What are Line Ordering Rules? (Used by Autoinvoice) A) Line ordering rules are used to order transaction lines when grouping the transactions into invoices. 20. 17. Commitments and invoices. In which table you can see the amount due of a customer? A) AR_PAYMENT_SCHEDULES_ALL 18.

PARTY_ID: Identifier for the party. Organization. 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. Foreign key to the HZ_PARTIES table. 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. ADDRESSEE: Addressee information. HZ_LOCATIONS: . Few Important Columns are • • • • • • PARTY_SITE_ID: Party site identifier. PARTY_SITE_NUMBER: Party site number. The primary key for this table is PARTY_ID. 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. Group or Relationship. One location can optionally be used by one or more parties. HZ_PARTY_SITES: The HZ_PARTY_SITES table links a party (HZ_PARTIES) and a location (HZ_LOCATIONS) and stores location-specific party information. The primary key for this table is PARTY_SITE_ID.HZ tables in Oracle Receivables July 1. PARTY_SITE_NAME: User-defined name for the site. LOCATION_ID: Identifier for the party site. One party can optionally have one or more party sites. Foreign key to the HZ_LOCATIONS table.

One customer account can have multiple customer account sites. The primary key for this table is LOCATION_ID. and directions to a location. This table focuses on business relationships and how transactions are conducted in the relationship. or business relationships that the deploying company establishes with a party of type Organization or Person. where the deploying company does business with its customers. street address. 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 . 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. This table provides physical location information about parties (organizations and people) and customer accounts. Few Important Columns are • • • • • CUST_ACCOUNT_ID: Customer account identifier PARTY_ID: A foreign key to the HZ_PARTY table. postal code. The primary key for this table is CUST_ACCT_SITE_ID. and a professional account for a consulting practice. . Since a party can have multiple customer accounts. and customer account sites for one customer account can belong to multiple operating units. R for revenue generating external customers. I for internal customers. family account. this table might contain several records for a single party. an individual person can establish a personal account. ACCOUNT_NUMBER: Account Number CUSTOMER_TYPE: Receivables lookup code for the CUSTOMER_TYPE attribute. for customer accounts. The primary key for this table is CUST_ACCOUNT_ID. For example. Customer account sites are addresses.The HZ_LOCATIONS table stores information about a delivery or postal address such as building number.

SHIP_TO_FLAG: Indicates if this is a Ship-To site. 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. Foreign key to the HZ_CUST_ACCOUNTS table PARTY_SITE_ID: Identifier for a party site. Foreign key to the HZ_CUST_ACCT_SITES_ALL table SITE_USE_CODE: Business purpose assigned to customer site account. Each customer account site can have one or more purposes. MARKET_FLAG: Indicates if this is a Marketing site. and Statements. and Statements. PRIMARY_FLAG: Indicates if this site is the primary site for this customer account. . Foreign key to the HZ_PARTY_SITES table BILL_TO_FLAG: Indicates if this is a Bill-To site. with the foreign key CUST_ACCT_SITE_ID. The primary key for this table is SITE_USE_ID. for example Bill-To. though the HZ_CUST_ACCT_SITES_ALL table itself stores the operating unit for customer account sites. Few Important Columns are • • CUST_ACCOUNT_PROFILE_ID: Unique identifier of this customer profile CUST_ACCOUNT_ID: Identifier for the Customer Account. The primary key for this table is CUST_ACCOUNT_PROFILE_ID. Market. The HZ_CUST_SITE_USES_ALL table also stores operating unit identifier. N for other customer account sites. Few Important Columns are • • • • SITE_USE_ID: Site use identifier CUST_ACCT_SITE_ID: Identifier for the customer account site. This table is a child of the HZ_CUST_ACCT_SITES_ALL table. HZ_CUST_SITE_USES_ALL: The HZ_CUST_SITE_USES_ALL table stores business purposes assigned to customer account sites. Y for the primary customer account site. Foreign key to the HZ_CUST_ACCOUNTS table. Ship-To.Few Important Columns are • • • • • • CUST_ACCT_SITE_ID: Customer site identifier CUST_ACCOUNT_ID: Identifier for a customer account. such as Bill-To. A profile class defined in the HZ_CUSTOMER_PROFILE_CLASSES table can be used to provide default values for the attributes in this table.

hz_party_sites hps. The primary key for this table is PROFILE_CLASS_ID. hz_parties hp where hcsua. hz_cust_accounts hca. hz_cust_acct_sites_all hcasa. HZ_PARTY_RELATIONSHIPS: The HZ_PARTY_RELATIONSHIPS table stores information about relationships between parties.site_use_code = 'BILL_TO' / 'SHIP_TO' .• 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. SELECT * from hz_cust_site_uses_all hcsua. The characteristics specified in this table can be used as default characteristics for similar customer accounts.

cust_account_id = hca. loading data into all interface tables and running the customer interface 2. Check is customer header is already created.party_site_id = hcasa. . Check if customer address site is already created. validate customer status. Check if customer site use is already created.and hcsua. running through API’s priovided by oracle Below are some of the useful tables and API’s for customer interface. Check if the location already exists in HZ_LOCATIONS.cust_acct_site_id = hcasa.cust_acct_site_id and hps. Customer API 1. Profile amounts validation: validate cust_account_id.party_id. The Customer conversion can be done in 2 ways: 1.party_id = hps.cust_account_id and hp. Concurrent program: Customer Interface Validations: Check if legacy values fetched are valid. Check whether the ship_to_site has associated bill_to_site Check whether associated bill_to_site is created or not. create new location. 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.party_site_id and hcasa. If does not exist. Set the organization id .

HZ_PARTY_SITE_V2PUB.Exec dbms_application_info. Check is customer header is already created.PARTY_SITE_REC_TYPE 5.set_client_info(‘204’). HZ_CUST_ACCOUNT_SITE_V2PUB. Check if customer site use is already created.CUST_ACCOUNT_REC_TYPE HZ_PARTY_V2PUB. 2.CREATE_CUST_ACCOUNT() HZ_CUST_ACCOUNT_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’. validate customer status. Check if customer address site is already created.CREATE_PARTY_SITE() HZ_PARTY_SITE_V2PUB. If does not exist. Create a party site using party_id you get from step 2 and location_id from step 3. Check if the location already exists in HZ_LOCATIONS.CREATE_CUST_ACCT_SITE() HZ_CUST_ACCOUNT_SITE_V2PUB.LOCATION_REC_TYPE 4. HZ_CUST_ACCOUNT_SITE_V2PUB. .CUSTOMER_PROFILE_REC_TYPE 3.CREATE_CUST_SITE_USE() HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_LOCATION() HZ_LOCATION_V2PUB. Create a physical location HZ_LOCATION_V2PUB. Create a party and an account HZ_CUST_ACCOUNT_V2PUB.ORGANIZATION_REC_TYPE HZ_CUSTOMER_PROFILE_V2PUB. Profile amounts validation: validate cust_account_id.CUST_SITE_USE_REC_TYPE HZ_CUSTOMER_PROFILE_V2PUB. Create an account site using account_id you get from step 2 and party_site_id from step 4. create new location. Check whether the ship_to_site has associated bill_to_site Check whether associated bill_to_site is created or not.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.

Sign up to vote on this title
UsefulNot useful