Query to get Oracle Receivables Details

 /*Query to get Oracle Receivables Details

==========================================*/

SELECT rcta.trx_number "INVOICE NUMBER",

rctta.name "TRANSACTION TYPE",

rcta.trx_date "INVOICE DATE",

apsa.due_date "DUE DATE",

apsa.invoice_currency_code "CURRENCY",

apsa.amount_due_original "AMOUNT",

apsa.amount_due_remaining "AMOUNT DUE",

hp_b.party_name "BILL TO CUSTOMER NAME",

hcsua_b.site_use_id "BILL TO SITE USE ID",

hl_b.address1,

hl_b.address2,

hl_b.address3,

hl_b.address4,

hl_b.city,

hl_b.state,

hl_b.postal_code,

hp_s.party_name "SHIP TO CUSTOMER NAME",

hcsua_s.site_use_id "SHIP TO SITE USE ID",

hl_s.address1,

hl_s.address2,

hl_s.address3,

hl_s.address4,

hl_s.city,

hl_s.state,

hl_s.postal_code

FROM RA_TERMS RT,

RA_CUSTOMER_TRX_ALL RCTA,

--RA_CUSTOMER_TRX_LINES_ALL RCTLA,

RA_CUST_TRX_TYPES_ALL RCTTA,

HZ_CUST_ACCOUNTS_ALL HCAA,

HZ_CUST_ACCT_SITES_ALL HCASA_S,

HZ_CUST_SITE_USES_ALL HCSUA_S,

HZ_PARTIES HP_S,

HZ_PARTY_SITES HPS_S,

HZ_LOCATIONS HL_S,

HZ_CUST_ACCT_SITES_ALL HCASA_B,

HZ_CUST_SITE_USES_ALL HCSUA_B,

HZ_PARTIES HP_B,

HZ_PARTY_SITES HPS_B,

HZ_LOCATIONS HL_B,

AR_PAYMENT_SCHEDULES_ALL APSA,

HR_LEGAL_ENTITIES HLE

WHERE --RCTA.CUSTOMER_TRX_ID = RCTLA.CUSTOMER_TRX_ID

RCTA.CUST_TRX_TYPE_ID = RCTTA.CUST_TRX_TYPE_ID

AND RCTA.BILL_TO_CUSTOMER_ID = HCAA.CUST_ACCOUNT_ID

AND RCTA.ORG_ID = RCTTA.ORG_ID

AND APSA.CUSTOMER_TRX_ID = RCTA.CUSTOMER_TRX_ID

AND APSA.CUST_TRX_TYPE_ID = RCTTA.CUST_TRX_TYPE_ID

AND RCTA.TERM_ID = RT.TERM_ID(+)

AND HCAA.PARTY_ID = HP_S.PARTY_ID

AND HCAA.PARTY_ID = HP_B.PARTY_ID

--SHIP TO ADDRESS LINKS

AND RCTA.SHIP_TO_SITE_USE_ID = HCSUA_S.SITE_USE_ID

AND HCSUA_S.CUST_ACCT_SITE_ID = HCASA_S.CUST_ACCT_SITE_ID

AND HCASA_S.PARTY_SITE_ID = HPS_S.PARTY_SITE_ID

AND HPS_S.PARTY_ID = HP_S.PARTY_ID

AND HPS_S.LOCATION_ID = HL_S.LOCATION_ID

--------BILL TO ADDRESS LINKS

AND RCTA.BILL_TO_SITE_USE_ID = HCSUA_B.SITE_USE_ID

AND HCSUA_B.CUST_ACCT_SITE_ID = HCASA_B.CUST_ACCT_SITE_ID

AND HCASA_B.PARTY_SITE_ID = HPS_B.PARTY_SITE_ID

AND HPS_B.PARTY_ID = HP_B.PARTY_ID

AND HPS_B.LOCATION_ID = HL_B.LOCATION_ID

AND HLE.ORGANIZATION_ID = RCTA.LEGAL_ENTITY_ID

AND RCTA.TRX_NUMBER ='12149'

Transaction Sources

Transaction Source Overview

Transaction Source setup plays a key role in determining the behavior of the Transactions form as well as how AutoInvoice validates data to be imported. When you create a transaction, and associate it to a Transaction Source, several attributes of the Source are defaulted into the transaction The following functionality is controlled by your transaction source setup:

• Transaction Numbering – Automatic or Manual
• GL Date Derivation
• Grouping Rules
• Customer Information – Values Passed (ID, Value, Segment)
  • Bill To and Ship To
  • Address
  • Contact
  • Payment Method
• Accounting Information – Values Passed (ID, Value, Segment)
  • Invoicing Rule
  • Payment Terms
• Sales Credit Validation
• How to process Invalid Lines
• How to Process GL Dates in a Closed Period

Active transaction sources appear as list of values choices in the Transactions, Transactions Summary, and Credit Transactions windows.  For Bills Receivable, the transaction batch sources appear in the Bills Receivable and Bills Receivable Transaction Batches windows.

There are two types of transaction sources:

• Manual: Used for transactions created manually in the Transactions Workbench.
• Imported: Used for importing transactions using AutoInvoice.

The following lists the 6 tabbed regions in the Transaction Source form. Only the first tab is enabled when creating Manual  transaction sources. For Imported transaction sources, all 6 tabbed regions are enabled.

1. Batch Source
2. AutoInvoice Options
3. Customer Information
4. Accounting Information
5. Other Information
6. Sales Credit Validation

Oracle Receivables provides the following seeded Transaction Sources:

Imported:

• Global Intercompany
• INDIA INVOICES
• Intercompany
• Order Entry Delivery Invoicing
• PA Internal Invoices
• PROJECTS INVOICES
• Property Manager Batch Source
• SERVICE
• Trade Management
• Work Order Billing

Manual:

• Chargeback
• DM Reversal
• Loans
• MANUAL-OTHER

Batch sources define default information such as transaction type and automatic numbering. There are two types available: Manual and Imported. AutoInvoice requires a batch of type Imported.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Sources

• Batch Source Name –Tip: If you have installed multiple organization support (multi-org), define an imported batch source with the same name in each organization (these sources can have the same or different settings). This enables you to import  order lines that belong to different organizations in Oracle Order Management “into corresponding organizations” in Receivables.

Note:  The Batch Source parameter selected must match the value in the interface table.  For this reason, local language names are not displayed in the LOV when running AutoInvoice

• Automatic Batch Numbering
  • Checked – indicates batches are automatically numbered, using the sequence provided in Last Number
  • Unchecked – indicates batches will require users to enter a batch number manually

• Automatic Transaction Numbering
  • Checked – indicates the transactions within this batch will be numbered automatically from the sequence value provided in Last Number
  • Unchecked – indicates manual transaction numbering, which will require users to enter a transaction number manually during data entry

• Copy Document Number to Transaction Number – indicates whether you want the document number generated to overlay the transaction number. This feature is necessary to implement gapless transaction numbers
• • Allow Duplicate Transaction Numbers – indicates whether duplicate numbers should be prevented or not during data entry
  • Copy Transaction Information Flexfield to Credit Memo – indicates whether the descriptive flexfield information from an Invoice should be copied into the Credit memo that credits the transaction
  • Generate Line Level Balances – indicates whether you want transactions in this batch to maintain line level balances useful for Line Level Cash Applications
  • Receipt Handling for Credits – for cases where you are interfacing a credit memo against an Invoice that has already been fully paid, you have the option of unapplying the receipts so that AutoInvoice can continue crediting the transaction. Available options are:
    1) Refund – to issue a credit card refund for the receipt or
    2) On-Account – put the receipt in On-Account
  • Reference Field Default Value – indicates which line transaction flexfield segment, i.e. RA_INTERFACE_LINES_ALL.INTERFACE_* field, you want to appear in the Reference field in the Transaction form
  • Standard Transaction Type – is the default transaction type for transactions in this batch
  • Credit Memo Batch Source – is the default batch source Receivables will use when creating Credit Memos against transactions within this batch source

The AutoInvoice Options tab highlights the Grouping rule created earlier.  The setup indicates this batch will group data as specified in this grouping rule. The Payment Details Defaulting Hierarchy is set to Parent of Bill-To Customer.

• Invalid Line – indicates the action to take when an interface line has an error, valid values are:
  Reject Invoice and Create Invoice
• GL Date in a Closed Period – indcates the action to take when the GL date provided in interface falls in a closed period, valid values are: Adjust and Reject
• Grouping Rule – indicates the default Grouping rule to use for interface lines using this batch source.
• Payment Details Defaulting Hierarchy – this field has 2 possible values:

• Parent of Bill-To Customer – this is the default value and uses the defaulting hierarchy:
  1. Primary receipt method of the parent primary bill-to site
2. Primary receipt method of the parent customer

3. Primary receipt method of the bill-to site

4. Primary receipt method of the bill-to customer

• Bill-To Customer – this uses the following defaulting hierarchy:
  1. Primary receipt method of the bill-to site
  2. Primary receipt method of the bill-to customer
  3. Primary receipt method of the parent primary bill-to site
  4. Primary receipt method of the parent customer

• Create Clearing – when checked, any differences between the specified revenue amount and the price multiplied by the quantity for imported invoice lines are stored in a clearing account. You must define a clearing
  account if you enable this.
• Allow Sales Credit – when checked, indicates that sales credits can be entered for transactions using this source

The following screenshots show the rest of the sub-tabs of this form, including Customer, Accounting, Salescredit and other information. You need to define whether the data you will interface provides the Value or the ID so that AutoInvoice can validate the data.

Customer Information tab:

Accounting Information tab:

Other Information tab:

Sales Credit Validation tab:

Batch Source for use in the Transactions Workbench

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Sources

Reference: metalink.oracle.com

HZ(TCA) tables in Oracle Receivables

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 foreign
key 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 the
HZ_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.

Relationship between the tables