Receivables

HZ_PARTY_SITES
==============

HZ_PARTY_SITES stores information about the relationship between Parties and Locations. The same party can have multiple party sites.Physical addresses are stored in HZ_LOCATIONS.

To Query Customer Details
=========================

SELECT  ROLE_ACCT.ACCOUNT_NUMBER,HZP.PARTY_NAME,HL.ADDRESS1,HL.ADDRESS2, HL.CITY,
 HL.STATE, HL.POSTAL_CODE,CONT_PARTY.PERSON_LAST_NAME,

CONT_PARTY.PERSON_FIRST_NAME,  DECODE(HCP.PHONE_LINE_TYPE,'GEN',

HCP.PHONE_AREA_CODE||HCP.PHONE_NUMBER,NULL)               PHONE_NUMBER,
 HCP.PHONE_EXTENSION,
DECODE(HCP.PHONE_LINE_TYPE,'FAX',HCP.PHONE_AREA_CODE||HCP.PHONE_NUMBER,NULL)    

FAX_NUMBER, CONT.ORIG_SYSTEM_REFERENCE
FROM 
 HZ_CUST_ACCOUNT_ROLES CONT, 
 HZ_PARTIES CONT_PARTY, 
 HZ_RELATIONSHIPS CONT_REL,
 HZ_ORG_CONTACTS CONT_ORG,
 HZ_PARTIES CONT_REL_PARTY ,
 AR_LOOKUPS L,
 AR_LOOKUPS L1,
 HZ_CONTACT_RESTRICTIONS CONT_RES, 
 HZ_PERSON_LANGUAGE PER_LANG,
 HZ_CONTACT_POINTS CONT_POINT, 
 HZ_CUST_ACCOUNT_ROLES ACCT_ROLE,
 HZ_PARTIES PARTY, 
 HZ_PARTIES REL_PARTY, 
 HZ_RELATIONSHIPS REL, 
 HZ_ORG_CONTACTS ORG_CONT ,
 HZ_CUST_ACCOUNTS ROLE_ACCT,
 HZ_CUST_ACCOUNTS CONT_ROLE_ACCT,
 HZ_CONTACT_POINTS HCP,
 HZ_PARTIES HZP,
 HZ_PARTY_SITES HPS,
 HZ_CUST_ACCT_SITES_ALL HCAS,
 HZ_LOCATIONS HL
WHERE CONT_ORG.TITLE = L.LOOKUP_CODE(+) 
 AND L.LOOKUP_TYPE(+) = 'CONTACT_TITLE' 
 AND CONT_ORG.JOB_TITLE_CODE = L1.LOOKUP_CODE(+) 
 AND L1.LOOKUP_TYPE(+) = 'RESPONSIBILITY' 
 AND CONT.CUST_ACCOUNT_ROLE_ID = ACCT_ROLE.CUST_ACCOUNT_ROLE_ID 
 AND CONT.PARTY_ID = CONT_REL.PARTY_ID AND CONT.ROLE_TYPE = 'CONTACT' 
 AND CONT_ORG.PARTY_RELATIONSHIP_ID = CONT_REL.RELATIONSHIP_ID 
 AND CONT_REL.SUBJECT_ID = CONT_PARTY.PARTY_ID 
 AND CONT_REL.PARTY_ID = CONT_REL_PARTY.PARTY_ID 
 AND ACCT_ROLE.PARTY_ID = REL.PARTY_ID 
 AND ACCT_ROLE.ROLE_TYPE = 'CONTACT' 
 AND ORG_CONT.PARTY_RELATIONSHIP_ID = REL.RELATIONSHIP_ID 
 AND REL.SUBJECT_ID = PARTY.PARTY_ID 
 AND REL_PARTY.PARTY_ID = REL.PARTY_ID 
 AND PARTY.PARTY_ID = PER_LANG.PARTY_ID(+) 
 AND PER_LANG.NATIVE_LANGUAGE(+) = 'Y' 
 CONT_POINT.OWNER_TABLE_ID(+) = REL_PARTY.PARTY_ID 
 CONT_POINT.CONTACT_POINT_TYPE(+) = 'EMAIL' AND CONT_POINT.PRIMARY_FLAG(+) = 'Y' 
 PARTY.PARTY_ID = CONT_RES.SUBJECT_ID(+) AND CONT_RES.SUBJECT_TABLE(+) = 'HZ_PARTIES' 
 AND CONT.CUST_ACCOUNT_ID = CONT_ROLE_ACCT.CUST_ACCOUNT_ID 
 AND CONT_ROLE_ACCT.PARTY_ID = CONT_REL.OBJECT_ID 
 AND ACCT_ROLE.CUST_ACCOUNT_ID = ROLE_ACCT.CUST_ACCOUNT_ID AND ROLE_ACCT.PARTY_ID = REL.OBJECT_ID
 AND REL_PARTY.PARTY_ID=HCP.OWNER_TABLE_ID(+)
 AND HZP.PARTY_ID=ROLE_ACCT.PARTY_ID
 AND ROLE_ACCT.PARTY_ID=HPS.PARTY_ID
 AND HPS.PARTY_SITE_ID=HCAS.PARTY_SITE_ID
 AND HL.LOCATION_ID=HPS.LOCATION_ID
 AND CONT_ORG.PARTY_SITE_ID=HCAS.PARTY_SITE_ID
ORDER BY ROLE_ACCT.ACCOUNT_NUMBER, CONT.CUST_ACCOUNT_ROLE_ID

API for creating MISC Receipt
=============================

DECLARE
   l_return_status             VARCHAR2 (255);
   l_msg_count                 NUMBER;
   l_msg_data                  VARCHAR2 (255);
l_misc_receipt_id   NUMBER;
l_receipt_number  varchar2(50);
                                 

BEGIN

l_receipt_number := '5052121';

ar_receipt_api_pub.Create_misc
                                 (p_api_version            => 1.0,
                                  p_init_msg_list          => fnd_api.g_true,
                                  p_commit                 => fnd_api.g_true,
                                  p_currency_code          => 'USD',
                                  p_receipt_number         => l_receipt_number
                                  p_receipt_date           => sysdate,
                                  p_amount                 => 2000,
                                  p_receipt_method_id      => 1067,
                                  p_misc_payment_source => 'from sat',
                                  p_activity => 'Misc-x',
                                  p_misc_receipt_id        => l_misc_receipt_id,
                                  x_return_status          => l_return_status,
                                  x_msg_count              => l_msg_count,
                                  x_msg_data               => l_msg_data
                                 );


DBMS_OUTPUT.PUT_LINE('x_return_status ='||L_return_status);
DBMS_OUTPUT.PUT_LINE('l_msg_count ='||l_msg_count);
DBMS_OUTPUT.PUT_LINE('l_msg_data ='||l_msg_data);
END;

Misc Receipts
=============

Miscellaneous Receipts cann't be imported into Oracle Receivables using Auto Lockbox.

Accounting/Invoicing rule
=========================

Accounting rule is used for calculating Revenue,it is attached to standard memo line or Items in the inventory.

Invoice Flexfields
==================

Invoice Transaction Flexfield

Line Transaction Flexfield

Invoice Line Information

Transaction Information

Invoice Transaction Flexfield
=============================

Why we are unable to update the 'Invoice Transaction Flexfield' in 11.5.10 for imported transactions?

 

This is intended. i.e.This bug was resolved in 11.5.10 and this flexfield should no longer be updateable for imported transactions.This flexfield should be non-updateable as it is used as a reference back to original system. 

Invoice & Line Transaction Flexfield
====================================

Through Autoinvoice we cannot have different information in "Invoice Transaction Flexfield" and "Line Transaction Flexfield".basically if there are more than one line then the attributes of the first line from the ordered lines will appear in the Invoice Transaction Flexfield.



If a transaction has only one line, then the Invoice Transaction Flexfield will be the same as the Line Transaction Flexfield.This is standard functionality. The data loaded in RA_INTERFACE_LINES_ALL.header_attribute1 is showed in "Transaction information flexfield" The data loaded in RA_INTERFACE_LINES_ALL.Interface_line_attribute1 is showed in "Line Transaction FlexField"

Conversion Rate
===============

RA_INTERFACE_LINES_ALL.Conversion rate can't be used for MRC

RA_INTERFACE_LINES_ALL.CONVERSION_TYPE  --> RA_CUSTOMER_TRX_ALL.EXCHANGE_TYPE

Conversion type should be "User" if the conversion_rate has value.

RA_INTERFACE_LINES_ALL.CONVERSION_RATE  --> RA_CUSTOMER_TRX_ALL.EXCHANGE_RATE

RA_INTERFACE_LINES_ALL.CONVERSION_DATE  --> RA_CUSTOMER_TRX_ALL.EXCHANGE_RATE(It can be null,if null then trx_date will be considered as Exchange_date)

Item Validation Organization
============================

Item Validation Organization should be defined in OM System parameters

Receipt Class
=============

Receipt class Accounts(cash,unapplied etc) cann't be updated.

Receipt Source
==============

Receipt source used to attach receipt class and put batch numbering for the source.

AUTOINVOICE - DATE DERIVATION
=============================

This article has been submitted in a bid to help clear up how dates in
autoinvoice are derived.


The only truly required date as far as Autoinvoice is concerned is
the default date entered at the time of running the Autoinvoice program.
ALL OTHER DATE COLUMNS COULD BE CONSIDERED OPTIONAL.

However, should a date exist in Autoinvoice then how it will be used
- and where else it will be used as a relevant date comes into play.



Rules for Deriving GL Date:

1.  Gl_date will be used if it is exists in the table.

2.  If transactions are set up with accounting rules then
    Autoinvoice will use the rule_start_date for the gl_date -
    as long as the invoicing rule is bill in advance.
    If it is bill in arrears then accounting rule needs to be
    of fixed duration in order for the end date to be worked
    out for that to be the gl date of the transaction.


    If numerous rule start dates exist the earliest will be used
    for the overall invoice.



3.  The default date entered at the time of running autoinvoice will
    be used if no gl_date exists and the field 'derive date?' on the
    batch source definition is set to 'No' and no rules exist.



4.  If the derive date field is set to 'yes', this will override
    the default date use and Autoinvoice will search the following
    columns for a date to use as the Gl Date, stopping at the first
    one to provide a date:


    a.  ship_date_actual

    b.  sales_order_date

    c.  If no date exists in either the previous two columns then
        Autoinvoice goes back and uses the default date entered
        at the time of running the program.



The batch source definition can be set up such that a transaction
will fail and be rejected by validation if the relevant gl date
does not fall in an open period or is not defined.  The relevant
period has to be open in AR, GL and INV if INV is fully installed.
The transaction will also fail if there are overlapping open periods.


If the close period field on the batch source is set to 'adjust'
instead of 'reject' then Autoinvoice will try and create the
gl_date as follows:


a.  It will try and use the last day of the prior period if it is
    still open.

b.  If there is no prior period with a status of open it will try
    and use the first subsequent period that is open - however,

    if there is more than one it will reject the transaction.

c.  If there are no subsequent open periods it will use the first
    subsequent 'future' status period - although if more than
    one exists it will reject the transaction.

The transaction date will default to the same date as the gl date and
the due date will be worked out accordingly.  In the case of Order
Entry it is advised that date be set to derived and shipment date
used as this is passed into the interface by OE.


Date with reference to Rules:

Accounting and Invoicing rules entered in the interface tend the
be a source of problems all on their own.

Accounting rules determine the accounting period(s) in which the
REVENUE for an invoice is to be recording whilst invoicing rules
determine the accounting period in which the RECEIVABLE amount is
recorded.  There are two invoicing rules - advance (the normal
one) and arrears.  With advance rules the receivable amount is
recognised in the same period as the accounting rule start date.
With arrears rules the receivables amount is viewed as unbilled
until the last accounting rule date.

You can't enter an accounting rule without an attached invoicing
rule.  It is the accounting rule that carries the dating details.
An accounting rule can be either a fixed term or variable term

- if it is for a fixed term you enter the number of periods over
which revenue is to be recognised at the time of defining the
rule.  If it is a variable you determine the number of periods
to be covered at the time of entering the transaction.
(accounting_rule_duration column).

The periods covered by the rule have to be defined (though not
necessarily open).  The validation issues attached to gl date
are the same for rule start date.

The date from which the rule is to come into effect is entered
in rule_start_date in ra_interface_lines, but the default date
entered on running Autoinvoice can be used instead as the rule
start date, or, if the derive date field on the batch source
definition is set to 'Yes' then the shipment or sales order
date columns can be used for the rule start date derivation
instead - the same as for the gl_date.

RA_CUSTOMERS_INTERFACE_ALL
==========================

orig_system_customer_ref
site_use_code
orig_system_address_ref
insert_update_flag        -- I for Insert,U for update
customer_name
customer_number
customer_status           -- 'A' for active
customer_type             -- 'I' for Internal, 'R' for external
primary_site_use_flag     -- 'Y' 
location
Address1
Address2
city
state
postal_code
country
customer_category_code
customer_class_code
...who columns

Customer update through Interface
=================================

While updating customer details values for the following fields should be null.

SITE_USE_CODE
PRIMARY_SITE_USE_FLAG
LOCATION

The following columns cannot be update through customer interface
CUSTOMER_ATTRIBUTE1-15
SITE_USE_ATTRIBUTE1-15
ADDRESS_ATTRIBUTE1-15

Sales person information cannot be imported through the customer interface.

To query open balance
=====================

SELECT 
  hca.account_number,
  rct.trx_number,
  rct.trx_date,
  amount_due_remaining
FROM 
  ra_customer_trx_all rct,
  ra_customer_trx_lines_all rctl,
  ar_payment_schedules_all aps,  
  apps.hz_cust_accounts_all hca
WHERE 
  hca.cust_account_id=aps.customer_id
  AND rct.customer_trx_id=rctl.customer_trx_id
  AND aps.customer_trx_id = rct.customer_trx_id
  AND rctl.org_id=285 
  AND aps.status='OP' 
GROUP BY rct.trx_number,
      rct.trx_date,
      amount_due_remaining,
      hca.account_number
ORDER BY hca.account_number

To delete invoice from database
===============================

DELETE FROM ra_batches_all WHERE org_id=1 AND creation_Date > sysdate-2
/
DELETE FROM ra_customer_trx_all WHERE org_id=1 AND creation_Date > sysdate-2
/
DELETE FROM ra_customer_trx_lines_all WHERE org_id=1 AND creation_Date > sysdate-2
/
DELETE FROM ra_cust_trx_line_gl_dist_all WHERE org_id=1 AND creation_Date > sysdate-2
/
DELETE FROM ar_payment_schedules_all WHERE org_id=1 AND creation_Date > sysdate-2
/

Orig Customer and Address Reference
===================================

SELECT   

               ca.orig_system_reference,cas.orig_system_reference
           FROM 
               hz_cust_accounts ca,
               hz_cust_acct_sites_all cas,
               hz_cust_site_uses_all csu
          WHERE ca.cust_account_id     = cas.cust_account_id
            AND cas.cust_acct_site_id  = csu.cust_acct_site_id
            AND ca.account_number= :customer_number
            AND csu.location=:location_code
            AND ca.status = 'A'
            AND cas.status = 'A'
            AND csu.status = 'A';

Batch Source
============

Invoice sources are used to control transaction and transaction batch numbering, to specify default transaction type and to select validation option for imported transactions

Setup --> Transactions --> Sources

Table --> AR_BATCH_SOURCES_ALL

Replicate Seed Data Issue
=========================

Subject:  REPLICATE SEED DATA APP-969 APP-1126 

  Doc ID:  Note:1070549.6 Type:  PROBLEM 
  Last Revision Date:  16-MAY-2000 Status:  PUBLISHED 

Problem Summary Line: 
===================== 

running AKXMOSED module: Replicate Seed Data

gets errors below:
APP-00969 Program exited with status 1
APP-01126 Concurrent Manager got error running SQL*Plus for request
392109

From the concurrent manager report the ct will also have the following errors:

ERROR at line 1:

ORA-20000: ORA-00001: unique constraint (AR.RA_BATCH_SOURCES_U1)

violated:ad_morg.replicate_table_data(RA_BATCH_SOURCES_ALL,512):


Solution Summary: 
================= 

Note: be sure to have the ct send you the report from the concurrent manager
process this will lead you to the two ora errors mentioned above.

This is Bug 747322. Send the ct the following SQL:

Please perform the following check.

SQL> select batch_source_id, name 
     from ra_batch_sources_all 
     where org_id = -3113


Perform the same select for every org in the system. It is highly likely that
a batch source with the same name but different id exists.

update ra_batch_sources_all
set    BATCH_SOURCE_ID = -1
where  BATCH_SOURCE_ID = 
and    org_id = 

Then,

execute ad_morg.replicate_seed_data(NULL, 'AR', NULL);

You should be able to replicate seed data now.

-1126, ora-20000, ora-00001, AR.RA_BATCH_SOURCES_U1, ad_morg.replicate_table_data

How AutoInvoice Grouping Works
==============================

Grouping is used to prevent autoinvoice lines from combining in a single 
invoice.  Other words you use grouping rules to determine how you want 
autoinvoice lines to split into individual transactions.  For example, you 
may want to prevent order lines from two different sales orders from grouping 
on the same invoice.

Receipt Amount
================

Receipt Amount cann't be updated R12 due to Reconcilation Issues

To update customer profiles 
===========================

DECLARE
   v_collector_id                  NUMBER;
   v_credit_checking               VARCHAR2 (1);
   v_tolerance                     NUMBER;
   v_discount_terms                VARCHAR2 (1);
   v_dunning_letters               VARCHAR2 (1);
   v_interest_charges              VARCHAR2 (1);
   v_statements                    VARCHAR2 (1);
   v_credit_balance_statements     VARCHAR2 (1);
   v_dunning_letter_set_id         NUMBER;
   v_standard_terms                NUMBER;
   v_override_terms                VARCHAR2 (1);
   v_interest_period_days          NUMBER;
   v_payment_grace_days            NUMBER;
   v_discount_grace_days           NUMBER;
   v_statement_cycle_id            NUMBER;
   v_autocash_hierarchy_id         NUMBER;
   v_tax_printing_option           VARCHAR2 (30);
   v_charge_on_finance             VARCHAR2 (1);
   v_grouping_rule_id              NUMBER;
   v_auto_rec_incl_disputed_flag   VARCHAR2 (1);
   v_attribute_category            VARCHAR2 (30);
   v_autocash_hierarchy            NUMBER (15);
   v_lockbox_matching_option       VARCHAR2 (20);
   v_attribute1                    VARCHAR2 (150);
   v_attribute2                    VARCHAR2 (150);
   v_attribute3                    VARCHAR2 (150);
   v_attribute4                    VARCHAR2 (150);
   v_attribute5                    VARCHAR2 (150);
   v_attribute6                    VARCHAR2 (150);
   v_attribute7                    VARCHAR2 (150);
   v_attribute8                    VARCHAR2 (150);
   v_attribute9                    VARCHAR2 (150);
   v_attribute10                   VARCHAR2 (150);
   v_attribute11                   VARCHAR2 (150);
   v_attribute12                   VARCHAR2 (150);
   v_attribute13                   VARCHAR2 (150);
   v_attribute14                   VARCHAR2 (150);
   v_attribute15                   VARCHAR2 (150);
   v_cons_inv_type                 VARCHAR2 (150);
   v_cons_inv_flag                 VARCHAR2 (150);
   v_credit_analyst_id             NUMBER;
   v_review_cycle                  VARCHAR2 (150);
   v_profile_class_id              NUMBER;
   v_prof_id                       NUMBER;
BEGIN
   SELECT collector_id, credit_checking, tolerance, discount_terms,
          dunning_letters, interest_charges, statements,
          credit_balance_statements, dunning_letter_set_id,
          standard_terms, override_terms, interest_period_days,
          payment_grace_days, discount_grace_days, statement_cycle_id,
          autocash_hierarchy_id, tax_printing_option,
          charge_on_finance_charge_flag, grouping_rule_id,
          auto_rec_incl_disputed_flag, attribute_category,
          autocash_hierarchy_id_for_adr, lockbox_matching_option,
          attribute1, attribute2, attribute3, attribute4,
          attribute5, attribute6, attribute7, attribute8,
          attribute9, attribute10, attribute11, attribute12,
          attribute13, attribute14, attribute15, cons_inv_flag,
          cons_inv_type, credit_analyst_id, review_cycle,
          profile_class_id
     INTO v_collector_id, v_credit_checking, v_tolerance, v_discount_terms,
          v_dunning_letters, v_interest_charges, v_statements,
          v_credit_balance_statements, v_dunning_letter_set_id,
          v_standard_terms, v_override_terms, v_interest_period_days,
          v_payment_grace_days, v_discount_grace_days, v_statement_cycle_id,
          v_autocash_hierarchy_id, v_tax_printing_option,
          v_charge_on_finance, v_grouping_rule_id,
          v_auto_rec_incl_disputed_flag, v_attribute_category,
          v_autocash_hierarchy, v_lockbox_matching_option,
          v_attribute1, v_attribute2, v_attribute3, v_attribute4,
          v_attribute5, v_attribute6, v_attribute7, v_attribute8,
          v_attribute9, v_attribute10, v_attribute11, v_attribute12,
          v_attribute13, v_attribute14, v_attribute15, v_cons_inv_flag,
          v_cons_inv_type, v_credit_analyst_id, v_review_cycle,
          v_profile_class_id
     FROM hz_cust_profile_classes
    WHERE NAME IN ('ORACLE-100');

   SELECT profile_class_id
     INTO v_prof_id
     FROM hz_cust_profile_classes
    WHERE NAME IN ('ORACLE-200');

   UPDATE hz_customer_profiles
      SET last_update_date = SYSDATE,
          collector_id = v_collector_id,
          credit_checking = v_credit_checking,
          tolerance = v_tolerance,
          discount_terms = v_discount_terms,
          dunning_letters = v_dunning_letters,
          interest_charges = v_interest_charges,
          send_statements = v_statements,
          credit_balance_statements = v_credit_balance_statements,
          dunning_letter_set_id = v_dunning_letter_set_id,
          standard_terms = v_standard_terms,
          override_terms = v_override_terms,
          interest_period_days = v_interest_period_days,
          payment_grace_days = v_payment_grace_days,
          discount_grace_days = v_discount_grace_days,
          statement_cycle_id = v_statement_cycle_id,
          autocash_hierarchy_id = v_autocash_hierarchy_id,
          tax_printing_option = v_tax_printing_option,
          charge_on_finance_charge_flag = v_charge_on_finance,
          grouping_rule_id = v_grouping_rule_id,
          auto_rec_incl_disputed_flag = v_auto_rec_incl_disputed_flag,
          attribute_category = v_attribute_category,
          autocash_hierarchy_id_for_adr = v_autocash_hierarchy,
          lockbox_matching_option = v_lockbox_matching_option,
          attribute1 = v_attribute1,
          attribute2 = v_attribute2,
          attribute3 = v_attribute3,
          attribute4 = v_attribute4,
          attribute5 = v_attribute5,
          attribute6 = v_attribute6,
          attribute7 = v_attribute7,
          attribute8 = v_attribute8,
          attribute9 = v_attribute9,
          attribute10 = v_attribute10,
          attribute11 = v_attribute11,
          attribute12 = v_attribute12,
          attribute13 = v_attribute13,
          attribute14 = v_attribute14,
          attribute15 = v_attribute15,
          cons_inv_flag = v_cons_inv_flag,
          cons_inv_type = v_cons_inv_type,
          credit_analyst_id = v_credit_analyst_id,
          review_cycle = v_review_cycle,
          profile_class_id = v_profile_class_id
    WHERE profile_class_id = v_prof_id
      AND cust_account_id IN (SELECT cust_account_id
                                FROM hz_cust_accounts
                               WHERE account_number LIKE 'ORACLE%');
EXCEPTION
   WHEN OTHERS
   THEN
      NULL;
END;

OIR: Bill Presentment Architecture 
==================================

OIR: Bill Presentment Architecture Enabled determines whether iReceivables 
will use BPA to present invoices. If set to Yes, the BPA bill is displayed 
from iReceivables. If set to No, the standard iReceivables bill is displayed. 
Default is set to Yes.

How Receivables Selects Invoices for Consolidated Billing
=========================================================

Invoices are included on a consolidated billing invoice based on a cutoff date and the customer's payment terms. When printing consolidated billing invoices, you enter a cutoff date. This date determines the payment terms,which determine the bill-to sites the program selects for consolidated billing.To find the payment terms that will be used for the consolidated billing invoices, Receivables matches the cutoff date you specify in the report parameters with the cutoff day in the payment terms. For example, if you enter a cutoff date of 01-20-97, the system searches for all payment terms whose Cutoff Day is set to 20. Receivables then finds all bill-to sites assigned to that payment term, and looks at the customer's profile (first at the site level, then at the customer level) to determine if the site or customer is set up to use consolidated billing.


Once the customers are selected, Receivables selects individual invoices dated before the cutoff date that have not been included on a previous consolidated billing invoice.

Address Style
==============

DFF-->Receivable-->Address

How can a credit memo (from legacy) be applied against an invoice using AutoInvoice?
======================================================================

A: To link a credit memo to an invoice there are 2 options: 


i) Populate REFERENCE_LINE_ID on RA_INTERFACE_LINES_ALL with the CUSTOMER_TRX_LINE_ID of the invoice. 

OR 

ii) Populate REFERENCE_LINE_ATTRIBUTE1 to 15 with the INTERFACE_LINE_ATTRIBUTE1 to 15 of the invoice. 

You also need to populate REFERENCE_LINE_CONTEXT with INTERFACE_LINE_CONTEXT of the invoice. INTERFACE_LINE_CONTEXT and INTERFACE_LINE_ATTRIBUTE1 to 15 are stored in RA_CUSTOMER_TRX_LINES_ALL. 

To create an on-account credit (i.e. not linked to an invoice) do not populate REFERENCE_LINE_ID, REFERENCE_LINE_ATTRIBUTES or REFERENCE_LINE_CONTEXT. 


3. I have entered a tax line for my invoice in the RA_INTERFACE_LINES
   table, but when I run Autoinvoice it is being ignored. Why ?

   A tax line will only be processed if it can be successfully linked to
   it's Invoice line. It will be ignored if it cannot be linked. The 
   linking is done via the Line Transaction Flexfield. The segment values
   of the line transaction flexfield uniquely identify any given line in
   the interface table. An example of how this linking is achieved is 

   shown below:-

                                    Invoice Line       Tax Line
   INTERFACE_LINE_CONTEXT           'ORDER SYSTEM'     'ORDER SYSTEM'
   INTERFACE_LINE_ATTRIBUTE1        '10023'            '10023'
   INTERFACE_LINE_ATTRIBUTE2        '01'               '01'
   INTERFACE_LINE_ATTRIBUTE3        'LINE'             'TAX'
   LINK_TO_LINE_CONTEXT             null               'ORDER SYSTEM'               LINK_TO_LINE_ATTRIBUTE1          null               '10023'
   LINK_TO_LINE_ATTRIBUTE2          null               '01'
   LINK_TO_LINE_ATTRIBUTE3          null               'LINE'

   In this example attribute 1 is an order number, 2 is the line number   and attribute 3 is simply used to differentiate between invoice lines and tax lines. The combination of the three attributes is unique, and  the Invoice line attributes have been repeated on the tax line in the link to line attribute fields.

Cut of date
===========
Should match payment terms cut of date 

For deriving county ===================

select DISTINCT GEOGRAPHY_ELEMENT3 COUNTY from HZ_GEOGRAPHIES where GEOGRAPHY_ELEMENT2_CODE='NJ'  and GEOGRAPHY_NAME='08054'

Bill in Advance:

Use this rule to recognize your receivable immediately.

Bill in Arrears:

Use this rule to recognize the receivable at the end of the revenue recognition schedule.