AR Accounting Date Derived Based On The Default Date

Document 201241.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...
Copyright (c) 2018, Oracle. All rights reserved.
Troubleshooting AutoInvoice Date Derivation: GL Date, Invoice Date, Due Date, Ship Date, Billing Date,
Rule Date (Doc ID 201241.1)
In this Document
Purpose
Troubleshooting Steps
1. Date Derivation In AutoInvoince: How It Works
2. General Ledger Date
a. Invoice Without Rules
b. Invoice With Rules
i. Bill In Advance Invoicing Rules
ii. Bill in Arrears Invoicing Rules
iii. How Accounting Rule Start Dates Are Derived
c. Credit Memos (RMAs)
d. General Ledger Date Handling For Closed Periods
e. GL Date Validation In AutoInvoice
3. Transaction Date & Ship Date
a. Invoice
b. Credit Memo
4. Billing Date (Balance Forward Billing)
5. Due Date
6. Receivables Transaction Source Setup Impacting Date Derivation
a. Date Derivation In Transaction Batch Source Window
b. Adjust GL Date In Closed Period Setup In Transaction Batch Source Window
7. AutoInvoice Execution/Validation Report Date Errors And Steps To Resolve
8. Known Bugs And Fixes For AutoInvoice Date Derivation Issues
9. Brazil Transaction and GL Date Derivation

10. Still Have Questions?
References
APPLIES TO:
Oracle Order Management - Version 11.5.1 and later

Oracle Receivables - Version 11.5.10.0 and later
Information in this document applies to any platform.
PURPOSE
Oracle Receivables (AR): AutoInvoice Information Center >Troubleshooting AutoInvoice for Oracle Receivables Release
11.5 Through 12 > Note 201241.1
The purpose of this note is to provide a clear explanation of the logic used by AutoInvoice to derive the General Ledger Date and the
Transaction Date while processing transactions.
It is intended as a resource to assist you in identifying why a date is not what you expected. It can also be used to influence setup during
an implementation so that dates default as intended.
This note should be used in conjunction with the following two articles:
Note 1067402.1, AutoInvoice Setup for Release 12: A Case Study Using a Simple Script
1 of 16 21-02-2018 19:15
Note 1075757.1, Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12
TROUBLESHOOTING STEPS
1. Date Derivation In AutoInvoince: How It Works
During the process of AutoInvoice you can enter the General Ledger (GL) date and the Transaction date for a particular
transaction explicitly in the relevant columns of the RA_INTERFACE_LINES_ALL table or you can allow the AutoInvoice
process to derive the dates.
If the dates are provided, AutoInvoice will typically use them. There are a few scenarios where dates cannot be provided as
input parameters; these scenarios are discussed in section 2.e titled GL Date Validation.
If the dates are not provided, they will be derived. Date Derivation of the General Ledger date and Transaction date during
the process of AutoInvoice depends on the following:
1. The columns that are populated in the RA_INTERFACE_LINES_ALL table, namely:
GL_DATE
TRX_DATE
SHIP_DATE_ACTUAL
SALES_ORDER_DATE
RULE_START_DATE
2. Selection of the Derive Date Option in the Accounting Information Tab of the Transaction Sources
window.
3. Whether or not Invoicing Rules and Accounting Rules are used.
4. Setting of the GL Date in a Closed Period option in the AutoInvoice Options tab of the particular
Transaction Batch Source.
5. Default Date entered while submitting the AutoInvoice Program.
Once imported as a transaction in receivables, the GL date used by AutoInvoice is stored in the table.column:
RA_CUST_TRX_LINE_GL_DIST_ALL.GL_DATE.
Note: The GL date discussed in this note is for the initial accounting entry booked to record the creation of the invoice.
For invoices with rules, Revenue Recognition will generate additional accounting entries and may impact the dates seen by
users when reviewing transactions in Receivables.
2. General Ledger Date
Start by determining if your invoice has rules or not. If it does not start in section a below. If it does have rules, refer to section b.
a. Invoice Without Rules
Table shows how AutoInvoice selects a GL date when an invoice without rules is imported.
Order Criteria GL Date Source
1 Interface Lines GL Date exists = Yes GL Date from the interface table
Interface GL Date in Open Period = Yes
2 of 16 21-02-2018 19:15
2 Interface Lines GL Date exists = No Default date parameter for this AutoInvoice submission
Derive Date = No
3 Transaction Date (TRX_DATE)

Interface Lines GL Date exists = No
Derive Date = Yes Note: Transaction date was added as to this logic as part of the fix for Bug 9683887
Transaction Date Exists = Yes
4 Interface Lines GL Date exists = No Ship date

Derive Date = Yes
Transaction Date Exists = No
Ship Date Exists = Yes
5 Interface Lines GL Date exists = No Sales order date

Derive Date = Yes
Ship Date Exists = No
Sales Order Date Exists = Yes
6 Interface Lines GL Date exists = No Default date parameter provided for the AutoInvoice request
Derive Date = Yes
3 of 16 21-02-2018 19:15
Ship Date Exists = No

Sales Order Date Exists = No
The following flow shows the GL Date derivation logic for invoices without rules.
The default date from the parameters window is shown in the example below:
4 of 16 21-02-2018 19:15
This table shows examples of GL Date Derivation for invoices without rules:
# GL Date Trx_Date Ship_Date_Actual Sales_Order Default_Date

_Parameter
1 11-Mar-2010 10-Mar-2010 20-Mar-2010 13-Mar-2010 01-Apr-2010
2 11-Mar-2010 10-Mar-2010 20-Mar-2010 13-Mar-2010 01-Apr-2010
3 10-Mar-2010 20-Mar-2010 13-Mar-2010 01-Apr-2010
4 10-Mar-2010 20-Mar-2010 13-Mar-2010 01-Apr-2010
5 13-Mar-2010 01-Apr-2010
6 01-Apr-2010
b. Invoice With Rules
When an invoice with rules is processed, the GL date derivation process is impacted by your choice of rules. Both the
Invoicing Rule and the Accounting Rule influence the GL date.
i. Bill In Advance Invoicing Rules
If you use Bill in Advance as the invoicing rule, AutoInvoice uses the earliest start date* of the accounting rules
associated with your invoice lines as the GL date of the invoice.
*See section iii. below for logic used to derive the start date.
ii. Bill in Arrears Invoicing Rules
If you use Bill in Arrears as the invoicing rule then the GL date is derived slightly different depending upon your
accounting rule type/period (i.e., Specific date) and Batch Source setups. Rule Start Date is an important driver
in determining the GL date.
5 of 16 21-02-2018 19:15
Accounting Rule Type Period Gl Date Derivation
Fixed Schedule Specific AutoInvoice sets the GL and Transaction dates equal to the latest Specific Date of the accou
Date
All Other Bill in Arrears AutoInvoice first computes an ending date for each invoice line based on the accounting rul
Accounting Rule Types start date, and duration. AutoInvoice then uses the latest available date for the invoice GL d
iii. How Accounting Rule Start Dates Are Derived
The following sequential logic is used to find the start date for the accounting rules. Use this matrix to find the
rule date on your transaction and then use the logic for your specific situation from the sections above to
determine which value is used as the GL date.
Order Criteria Rule Start Date Source
1 Accounting Rule Type = Fixed duration Specific Date from the Accounting Rule Setup
Period = Specific Date
2 RULE_START_DATE column is populated in Use value from AutoInvoice interface table

RA_INTERFACE_LINES_ALL
3 Derive Date Checked in Batch Source Option is checked (see 1. Use the Ship Date if it is populated and in an open/enter
section 6 in this note) 2. If no Ship Date exists, then use Sales Order Date if it is
period.
3. If there is no Ship Date and no Sales Order Date, use th
the AutoInvoice submission.
4 Derive Date = Unchecked Default Date specified in the Run AutoInvoice Window
Here is the flow for Rule Start Derivation.
This table shows various examples of Rule Start Date Derivation.
6 of 16 21-02-2018 19:15
# Rule_Start Ship_Date Sales_Order Default_ Derive Accounting Rule Start Date Used
_Date _Date Parameter Date Rule Used
_Date
1 01-Mar-2010 15-FEB-2010 01-Feb-2010 01-Apr-2010 Checked Fixed Duration, + 01-Mar-2010

% or
Variable Duration
2 01-Mar-2010 15-FEB-2010 01-Feb-2010 01-Apr-2010 Not Fixed Duration, + 01-Mar-2010

Checked % or
Variable Duration
3 15-FEB-2010 01-Feb-2010 01-Apr-2010 Checked Fixed Duration, + 15-FEB-2010

% or
Variable Duration
4 01-Feb-2010 01-Apr-2010 Checked Fixed Duration, + 01-Feb-2010

% or
Variable Duration
5 15-FEB-2010 01-Feb-2010 01-Apr-2010 Not Fixed Duration, + 01-Apr-2010

Checked % or
Variable Duration
6 01-Feb-2010 01-Apr-2010 Not Fixed Duration, + 01-Apr-2010

Checked % or
Variable Duration
7 01-Apr-2010
8 01-Apr-2010 Not Fixed Duration, + 01-Apr-2010

Checked % or
Variable Duration
9 Fixed Duration Earliest accounting rule date

Accounting is chosen as Rule Start Date
Specific Date
c. Credit Memos (RMAs)
For credit memos, AutoInvoice defaults the dates as follows:
1. GL Date passed in the interface table (assuming period is open/enterable)

2. Greater of the default date or the date of the transaction being credited.
Note: The Ship Date is not used for GL dates on Credit Memos and should not be passed as part of a credit memo
interface. AutoInvoice uses the logic described above to derive the GL date. The Ship date is also derived for credit
memos using the earliest shipment date from the transaction you are crediting.
@See Bugs 9382022 and 3050872
d. General Ledger Date Handling For Closed Periods
Whether the General Ledger date is derived or specifically entered, the system validates whether it falls within a period which
is Closed or Not Opened. If the GL date falls within a period which is Closed or Not Opened, the Transaction Batch Source
controls what occurs next. As shown in Section 6. of this note, the 'General Ledger Date in a Closed Period' option can be set
to 'Adjust' or 'Reject' with the following consequences:
Reject = AutoInvoice rejects the line.

Adjust = AutoInvoice adjusts the General Ledger date, to that of a period with status Open or Future Enterable as
indicated below:
For invoice with rules:
1. The last day of the latest prior period that has an Open status is picked up as the General Ledger date.
2. If a prior period with an Open status does not exist, AutoInvoice uses the first day of the first subsequent period that
has a status of Open.
3. If there are no prior or subsequent Open periods, AutoInvoice uses the first day of the first subsequent period that
7 of 16 21-02-2018 19:15
has a status of Future.

4. If it cannot find a future period, AutoInvoice cannot adjust the GL date, and the line is rejected.
For invoice without rules:
1. The last day of the latest prior period with an Open status is picked up as the General Ledger date.
2. If a prior period with an Open status does not exist, AutoInvoice uses the first day of a subsequent Open period.
However, if there is more than one subsequent period with a status of Open, AutoInvoice rejects the line.
3. If there are no prior period or subsequent Open periods, AutoInvoice uses the first day of the first subsequent period
with a status of Future. If there is more than one subsequent period with a status of Future, AutoInvoice rejects the
transaction.
The following table provides examples of adjusting GL dates.
8 of 16 21-02-2018 19:15
# Jan Feb Mar Apr May Option GL GL Date Invoice Uses Action by GL Date
Date in a Entered or Rules AutoInvoice Used
Closed Derived
Period
1 Closed Open Closed Closed Closed Adjust 01-FEB-10 With/Without 01-Feb-10

Rules
2 Closed Open Closed Closed Closed Reject 01-FEB-10 With/Without 01-Feb-10

Rules
3 Open Closed Open Closed Closed Adjust 01-FEB-10 With/Without Adjust date 31-Jan-10
Rules
4 Open Closed Open Closed Closed Reject 01-FEB-10 With/Without Reject Line
Rules
5 Closed Closed Open Closed Closed Adjust 01-FEB-10 With/Without Adjust Date 01-Mar-10
Rules
6 Closed Closed Open Closed Closed Reject 01-FEB-10 With/Without Reject Line
Rules
7 Closed Closed Open Open Open Adjust 01-FEB-10 With Rules Reject Line
8 Closed Closed Open Open Open Reject 01-FEB-10 With Rules Reject Line
9 Closed Closed Open Open Open Adjust 01-FEB-10 Without Rules Adjust Date 01-Mar-10
10 Closed Closed Open Open Open Reject 01-FEB-10 Without Rules Reject Line
11 Closed Closed Future Closed Closed Adjust 01-FEB-10 With/Without Adjust Date 01-Mar-10
Rules
12 Closed Closed Future Closed Closed Reject 01-FEB-10 With/Without Reject Line
Rules
13 Closed Closed Future Future Future Adjust 01-FEB-10 With Rules Reject Line
14 Closed Closed Future Future Future Reject 01-FEB-10 With Rules Reject Line
15 Closed Closed Future Future Future Adjust 01-FEB-10 Without Rules Adjust Date 01-Mar-10
16 Closed Closed Future Future Future Reject 01-FEB-10 Without Rules Reject Line
17 Open Never Never Never Never Adjust 01-FEB-10 Bill in Advance or Adjust Date 31-Jan-10
Opened Opened Opened Opened Bill in Arrears rule
e. GL Date Validation In AutoInvoice
1. The entered or derived GL date must be in an Open or Future enterable accounting period.
2. The GL date cannot be in a Closed, Closed Pending, or Not Opened period if the GL Date in a Closed Period field for
your batch source is set to 'Reject.' (For invoices that use Bill in Arrears rules, AutoInvoice always rejects lines that have
a general ledger date in a closed period.)
3. The period must exist in GL_PERIOD_STATUSES.
4. If Accounting Rules are used, all periods must be defined for the duration of the accounting rule in
GL_PERIOD_STATUSES.
5. If 'Post To GL' is set to No on the transaction type of the transaction being passed, the GL_DATE column must be NULL.
6. If your invoice uses Bill in Arrears as the invoicing rule, then the GL_DATE column should be NULL.
7. If the Line Type being processed is Tax or Freight, the GL_DATE column should be NULL.
8. The GL date of a credit memo cannot be before the GL date of the associated invoice and/or the invoice date.
You can specify whether AutoInvoice will reject or partially create transactions that have a GL date in a closed period. For
example, you import an invoice with three invoice lines and one of the lines is invalid. If the value of the Invalid Line option for
this batch source is set to 'Create Invoice,' AutoInvoice will create the invoice with only the two valid lines. You can then use
the Transactions Workbench to add the line that was rejected.
If Invalid Line is set to 'Reject Invoice,' AutoInvoice will not import this transaction or any of its lines into the interface tables.
Transactions that fail validation appear in the AutoInvoice Validation report. The values you enter in the AutoInvoice
Processing Options tabbed region of the Transaction Sources window determine how AutoInvoice will process transactions
with invalid data. See Section 6 on Transaction Batch Sources.
9 of 16 21-02-2018 19:15
3. Transaction Date & Ship Date
a. Invoice
1. If the transaction date is explicitly passed in the interface, it is used by AutoInvoice.

2. If a transaction date is not entered for an invoice or debit memo, AutoInvoice uses the General Ledger date as the
transaction date.
Fulfillment Sets
If you are using fulfillment sets in Order Management (OM), you should be careful about which setup option you choose. If
you have your system set up to use the Ship Date, the system will assign the earliest ship date possible. If you have significant
lags between shipments this could result in invoice dates equal to the first shipment, which will throw off your aging, discount
calculations, etcetera. If you find yourself in this situation, you can change your setup to use the system date as the date
default.
Refer to section 1 of this note for setup necessary to map the ship date to system date.
Assuming AutoInvoice is run daily, this would have the net effect of assigning the GL/transaction date that matches the last
shipment date. Alternately, you can invoice each line as it is shipped by not using fulfillment sets. (For 11i, apply the latest
version of OEXPINVB.pls to avoid known problems. Presently this is 115.221.11510.55 available through Patch 9477748).
Shippable and Non-Shippable Items

If you are processing a combination of shippable and non-shippable items in Order Management, please review the options
available in OM to group non-shippable items together with shippable items. Also review the profile option OM Set Receivables
Transaction Date as Current for Non-Shippable Lines. (For 11i, Apply the latest version of OEXPINVB.pls to avoid known
problems. Presently this is 115.221.11510.55 available through Patch 9477748).
TIP: If you use Oracle Inventory and Oracle Order Management for sales order shipments, you should elect to derive your
dates and use the shipment date for your invoice GL date. This way, you can ensure that you have booked your revenue
and cost to the same accounting period. If you do not match revenue and cost in the same period, you violate basic GAAP
principles and may distort your profit. In addition, you cannot run a meaningful Margin Analysis report. This report
summarizes your revenue and cost of goods sold transactions by item and customer order, and specifies a transaction date
range. If your transactions are booked in the wrong period, the Margin Analysis report reflects those incorrect
transactions.
Ship Date and Grouping

If multiple lines with different ship dates are grouped together into a single invoice, the SHIP_DATE_ACTUAL of the invoice will
be the minimum of the SHIP_DATE_ACTUAL from the lines that are grouped to create that invoice. This is consistent with the
GL Date derivation logic used and described in the section above titled How Accounting Rule Start Dates Are Derived.
b. Credit Memo
If a transaction date is not passed for your credit memo, AutoInvoice uses the following hierarchy to determine the credit
memo's transaction date:
1. The credit memo GL date.

2. The GL date for the invoice's Receivable Distribution, or the Default Date in the Run AutoInvoice window, whichever is
later.
4. Billing Date (Balance Forward Billing)
There are 2 types of billing cycles:
RECURRING - this is the type users can create when they define their own billing cycles. In AutoInvoice, if the billing
cycle associated to the payment term is of type RECURRING, AutoInvoice will derive the Billing Date. The logic to derive
billing date is to find the first billable date on or after the transaction date and to use that as the billing date on the
invoice.
EVENT - Oracle seeds only one billing cycle for this type, named EXTERNAL. Users cannot create additional EVENT type
10 of 16 21-02-2018 19:15
billing cycles. In AutoInvoice, if the billing cycle associated to the payment term is of type EVENT, you are required to
pass in a value for the Billing Date.
See section 8 on Bug fixes for a Release 12 issue with this logic.
From Bug 7165627 the following logic is used to derive the billing date
UPDATE RA_CUSTOMER_TRX trx

SET billing_date = (
select MIN(bcd.billable_date)
from ar_cons_bill_cycle_dates bcd,
ar_cons_bill_cycles_b bc,
ra_terms t
where trx.term_id = t.term_id
and t.billing_cycle_id = bc.billing_cycle_id
and bc.bill_cycle_type = 'RECURRING'
and bcd.billing_cycle_id = t.billing_cycle_id
and bcd.billable_date >= nvl(trx.billing_date, trx.trx_date))
WHERE trx.request_id = :request_id
AND trx.term_id is not null;
5. Due Date
When submitting AutoInvoice, users enter two parameters that influence Due Date derivation. They are:
1. Base Due Date on Trx Date: Use this parameter to indicate whether you want AutoInvoice to calculate invoice due
dates based on transaction dates or based on either the ship date, sales order date, or default date. The default for this
parameter is Yes, which prompts AutoInvoice to use the transaction dates as the due dates for your invoices. If you
change the value to No, then AutoInvoice looks at the setting of the Derive Date option on a transaction's batch source
to determine the due date. Depending on the Derive Date setting, AutoInvoice derives the due date in a different way
Additionally, if the value of this parameter is No, then AutoInvoice uses the Due Date Adjustment Days parameter to
determine the final due date.
Note:
When Base Due Date on Trx Date = Yes, and you are interfacing Balance Forward invoices via AutoInvoice, the
process has logic to first check for the value in BILLING_DATE:
if BILLING_DATE is not null, use it to calculate the due date

if BILLING_DATE is null, use TRX_DATE instead to calculate the due date
2. Due Date Adjustment Days: Use this parameter to adjust your invoice due date calculations. You can enter any
integer between the range of -9999 and 9999. AutoInvoice uses this parameter only when the Base Due Date on Trx
Date parameter is set to No. When Base Due Date on Trx Date is No, AutoInvoice compares the due date that it
derived against the transaction date plus the number of days that you enter. AutoInvoice uses whichever date is later
as the final due date.
Terms setup also drives due date derivation as does Balance Forward Billing . When Balance Forward Billing is in use the
Billing Date can also be considered in deriving the Due Date.
Several bugs have been reported on Due Date handling and are covered in Section 8 of this document.
Also refer to the following documents:
Note 1069049.1 How To Define Transaction Payment Terms In Receivables

Note 1083494.1 Troubleshooting Payment Terms In AutoInvoice
6. Receivables Transaction Source Setup Impacting Date Derivation
For more on Transaction Source (Batch Source) Setup, refer to:
Note 1068008.1, Creating Transaction Sources Used For AutoInvoice

Note1088132.1, Troubleshooting Transaction Batch Sources For AutoInvoice
a. Date Derivation In Transaction Batch Source Window
Receivables Responsibility
Navigation: Setup > Transactions > Sources > Accounting Information
11 of 16 21-02-2018 19:15
The Accounting Information tab of the Transaction Sources (RAXSUMSC) window is where you select the criteria for validation
regarding accounting information. The fields that impact date derivation are:
Invoicing Rule
Accounting Rule
Derive Date check box
Select the Derive Date check box to derive the default Rule Start Date and default using the logic explained in section 2b.
TIP: If you use Oracle Inventory and Oracle Order Management for sales order shipments, you should select to derive
your dates and use the shipment date for your transaction GL date. This way, you can ensure that you have booked your
revenue and cost to the same accounting period.
b. Adjust GL Date In Closed Period Setup In Transaction Batch Source Window
Receivables Responsibility
Navigation: Setup > Transactions > Sources >AutoInvoice Options
12 of 16 21-02-2018 19:15
The value entered in the GL Date in a Closed Period field determines how AutoInvoice handles imported transactions that have
lines with a General Ledger date that is in a closed period.
Select Adjust to automatically adjust the General Ledger date to the first GL date of the next Open or Future enterable
period.
Select Reject to reject these transactions from being processed by AutoInvoice.
7. AutoInvoice Execution/Validation Report Date Errors And Steps To Resolve
Error Message Cause Action
Numerous A consolidation of all known issues and fixes h

Please define all periods in which revenue
is to be recognized or credited.
455691.1
Note that revenue cannot be recognized or credited in
closed and close pending periods.
GL Period is not open or Open the appropriate period.

Unable to derive a GL date for your transaction.
Please ensure that your transaction is in a GL period
enterable or
which you have defined 1 Go to Receivables > Control > Autoinvoice >
2 Click menu 'Folder' > Show field > GL Date.
3 Update the value for this field to a date whic
GL date was not passed as Correct your setup to increment the date and p
Unable to derive a GL date for your transaction.
request parameter and Derive scheduling AutoInvoice. (This can occur if the
which you have defined Date was unchecked in Batch and the request submission was not set to incr
source or
Pass GL date as a parameter to interface table
or
Modify you Batch Source setup to allow GL dat
Credit Memo was created in the ACCOUNTING_RULE_NAME: For credit memos

Unable to derive a gl date for your transaction.
interface table with an invoice column. AutoInvoice uses the accounting rule
which you have defined and/or accounting rule crediting.
specified.
8. Known Bugs And Fixes For AutoInvoice Date Derivation Issues
Release / Symptom Cause
13 of 16 21-02-2018 19:15
Release: 12.0 Bug 7165627

Symptoms: Billing Date is incorrectly derived using system date instead of Transaction Date
Release: 12.0 - 12.1 BUG 7670265

Symptoms: AutoInvoice completes, fails to import the records and shows no error message in the
AutoInvoice Import Execution report. After the fix the billing dates defaults dates
properly and display the
Log file shows the following error correct error message when the billing date
is not found.
AR_TAPI_ECB_BILLING_DATE_REQD
Release: 12.0 - 12.1 Bug 7394261

Symptoms: Due Date is calculated using transaction date for balance forward billing payment term
when it should use billing date. (Base due date on Trx Date is set to "N")
Bug 8667653
Release: 12.0 - 12.1
Symptoms: Autoinvoice rejects lines with erroneous messages about Invalid warehouse_id when
batch source setup has Accounting/Invoicing Rule = None and GL date to be derived from shipping or
order date.
Release: 11.5 11g database upgrade step was missed.

Symptoms: After database 11g upgrade customer is facing issue with a standard AR table has a
column filled with an abnormal date (year 0020 instead of 2010) Bug 9739305
and
Different values of TRX_DATE in the 2 tables : Bug 9406422
--------------------------------------------------------- cr9idata.pl - A perl script to assist creating
SELECT 9idata/ under $ORACLE_HOME/nls/data/
aaa.trx_date The script copies every nlb files under
,bbb.trx_date $ORACLE_HOME/nls/data and
# $ORACLE_HOME/nls/data/old to
FROM directory $ORACLE_HOME/nls/data/9idata
RA_CUSTOMER_TRX_ALL aaa # for customer needs to revert back to 9i
,AR_PAYMENT_SCHEDULES_ALL bbb locale behavior.
WHERE 1=1 .
Please see note Oracle Applications Release
AND aaa.TRX_NUMBER = '100884001' 11i with Oracle 11g Release 2 Note
AND bbb.TRX_NUMBER = '100884001' 881505.1
In this note see step 9:
--------------------------------------------------------- Create nls/data/9idata directory
On the database server node, as the owner
RA_CUSTOMER_TRX_ALL .TRX_DATE = 29.03.2010 of the Oracle RDBMS file system and
AR_PAYMENT_SCHEDULES_ALL = 29.03.0020 database instance, run the
$ORACLE_HOME/nls/data/old/cr9idata.pl
script to
create the $ORACLE_HOME/nls/data/9idata
directory.
.
After creating the directory, make sure that
the ORA_NLS10 environment
variable is set to the full path of the 9idata
directory whenever you enable
the 11g Oracle home.
Release: 11.5 - CRITICAL FIX Most common reason is upgrade RDBMS to

9.2.0.7, however we have also seen this
When importing invoices via Autoinvoice, data corruption is created with one or more of the issue in older RDBMS releases like 9.2.0.5
following symptoms in RA_CUST_TRX_LINE_GL_DIST : and 9.2.0.6
1) Incorrect RA_CUST_TRX_LINE_GL_DIST.GL_DATE, with the following variations : This is RDBMS Bug 4483951
a) RA_CUST_TRX_LINE_GL_DIST.GL_DATE <> RA_CUSTOMER_TRX.TRX_DATE
14 of 16 21-02-2018 19:15
b) mismatched GL_DATE between REC, REV, UNEARN, TAX, ROUND

c) GL_DATE is null for ACCOUNT_SET_FLAG = 'N' records
d) Distributions for various periods all have same GL_DATE
e) GL_DATE for various periods precedes RULE_START_DATE
f) GL_DATE incorrectly defaults to first day of open period
g) GL_DATE is missing for transactions with POST_TO_GL = Y, and is populated
for transactions where POST_TO_GL = N
Release: 11.5 Unpublished Bug 6636953

Due date for proxima payment term not calculated properly via AutoInvoice.
For example: Terms of 45 Days from end of month are not calculated correctly.
Release: 11.5 Unpublished Bug 3672087

Symptoms: Invoices brought in through AutoInvoice are being assigned a GL_DATE that is in a
never opened period when the batch source is set to 'Derive Date' and the GL_DATE option is set to
'Adjust' and the RULE_START_DATE is in a never / not / unopened period.
Release: 11.5 Bug 4636072

Symptoms: Credit Memos fail with the following error:
Errors:
1) Unable to derive a GL date for your transaction.
which you have defined.
*NOTE: Fixed files are often not the most current versions available. This table recommends the patch that contains THE MOST
CURRENT release of the fixed file. For this reason the patch readme file may not make specific mention of the symptoms described on
the lines above.
9. Brazil Transaction and GL Date Derivation
Due to Brazil Regulations, when a Transaction in Autoinvoice is processed, any day after it was inserted into Autoinvoice, the Invoice Date
should be the day it was processed and will not consider the trx_date value entered in the autoinvoice interface table.
Also, the GL_DATE should be same as the Transaction Date.
So, the TRX_DATE and GL_DATE will be the SYSDATE.

Please review Doc ID 2020631.1 for more details.
10. Still Have Questions?
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the
My Oracle Support Receivables Community.
To provide feedback on this note, click on the Rate this document link.
If you feel that a Service Request is needed, please be sure to provide the information listed below:
1. Clearly explain what date you are having problems deriving
15 of 16 21-02-2018 19:15
2. Provide the values for all variables that can influence the date from the section above
3. Document any troubleshooting steps you have performed
4. Provide a debug log and diagnostics as discussed in Note 1079666.1 How to Obtain an AutoInvoice Debug Log or Trace File for 11i and
R12
Didn't find what you are looking for?
16 of 16 21-02-2018 19:15

AR Accounting Date Derived Based On The Default Date

Uploaded by

Copyright:

Available Formats

You might also like

AR Accounting Date Derived Based On The Default Date

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AR Accounting Date Derived Based On The Default Date

Uploaded by

Copyright:

Available Formats

Document 201241.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-stat...

Copyright (c) 2018, Oracle. All rights reserved.

9. Brazil Transaction and GL Date Derivation

Oracle Order Management - Version 11.5.1 and later

1. Date Derivation In AutoInvoince: How It Works

1. The columns that are populated in the RA_INTERFACE_LINES_ALL table, namely:

2. General Ledger Date

a. Invoice Without Rules

Order Criteria GL Date Source

3 Transaction Date (TRX_DATE)

4 Interface Lines GL Date exists = No Ship date

5 Interface Lines GL Date exists = No Sales order date

Ship Date Exists = No

# GL Date Trx_Date Ship_Date_Actual Sales_Order Default_Date

1 11-Mar-2010 10-Mar-2010 20-Mar-2010 13-Mar-2010 01-Apr-2010

2 11-Mar-2010 10-Mar-2010 20-Mar-2010 13-Mar-2010 01-Apr-2010

3 10-Mar-2010 20-Mar-2010 13-Mar-2010 01-Apr-2010

4 10-Mar-2010 20-Mar-2010 13-Mar-2010 01-Apr-2010

b. Invoice With Rules

i. Bill In Advance Invoicing Rules

ii. Bill in Arrears Invoicing Rules

Accounting Rule Type Period Gl Date Derivation

iii. How Accounting Rule Start Dates Are Derived

Order Criteria Rule Start Date Source

2 RULE_START_DATE column is populated in Use value from AutoInvoice interface table

Here is the flow for Rule Start Derivation.

This table shows various examples of Rule Start Date Derivation.

1 01-Mar-2010 15-FEB-2010 01-Feb-2010 01-Apr-2010 Checked Fixed Duration, + 01-Mar-2010

2 01-Mar-2010 15-FEB-2010 01-Feb-2010 01-Apr-2010 Not Fixed Duration, + 01-Mar-2010

3 15-FEB-2010 01-Feb-2010 01-Apr-2010 Checked Fixed Duration, + 15-FEB-2010

4 01-Feb-2010 01-Apr-2010 Checked Fixed Duration, + 01-Feb-2010

5 15-FEB-2010 01-Feb-2010 01-Apr-2010 Not Fixed Duration, + 01-Apr-2010

6 01-Feb-2010 01-Apr-2010 Not Fixed Duration, + 01-Apr-2010

8 01-Apr-2010 Not Fixed Duration, + 01-Apr-2010

9 Fixed Duration Earliest accounting rule date

c. Credit Memos (RMAs)

For credit memos, AutoInvoice defaults the dates as follows:

1. GL Date passed in the interface table (assuming period is open/enterable)

@See Bugs 9382022 and 3050872

d. General Ledger Date Handling For Closed Periods

Reject = AutoInvoice rejects the line.

For invoice with rules:

has a status of Future.

For invoice without rules:

The following table provides examples of adjusting GL dates.

1 Closed Open Closed Closed Closed Adjust 01-FEB-10 With/Without 01-Feb-10

2 Closed Open Closed Closed Closed Reject 01-FEB-10 With/Without 01-Feb-10

e. GL Date Validation In AutoInvoice

3. Transaction Date & Ship Date

1. If the transaction date is explicitly passed in the interface, it is used by AutoInvoice.

Shippable and Non-Shippable Items

Ship Date and Grouping

1. The credit memo GL date.

4. Billing Date (Balance Forward Billing)

There are 2 types of billing cycles:

UPDATE RA_CUSTOMER_TRX trx

if BILLING_DATE is not null, use it to calculate the due date

Note 1069049.1 How To Define Transaction Payment Terms In Receivables