R12 How To Bring In (and Troubleshoot) Manual Tax Lines Through Autoinvoice and E-Business Tax (EBTax) [ID

731149.1]
Modified: 10-Jul-2011 Type: TROUBLESHOOTING Status: PUBLISHED Priority: 3

In this Document
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
1. Definition of a Manual Tax Line
2. Interface data fields required to pass a Manual Tax Line
3. Sample Scripts for Invoice and Credit Memo with Manual Tax Lines
4. Troubleshooting Issues when passing Manual Tax Lines for Invoices
5. Troubleshooting Issues when passing Manual Tax Lines for Credit Memos
6. Troubleshooting Issues when passing Manual Tax Lines With Latin Tax Engine
References

Applies to:
Oracle Financials for the Americas - Version: 12.0.1 and later [Release: 12 and later ]
Oracle E-Business Tax - Version: 12.0 to 12.1 [Release: 12.0 to 12.1]
Oracle Receivables - Version: 12.0.0 to 12.1 [Release: 12.0 to 12.0]
Information in this document applies to any platform.
EXECUTABLE:RAXTRX - Autoinvoice Import Program

Purpose

E-Business Tax (EBTax) Information Center > EBTax Integration With EBS Modules > Receivables > Troubleshooting AutoInvoice Tax Issues with R12 E-Business Tax > Note 731149.1

This document summarizes how manual tax lines can be passed into Oracle Receivables with Release 12 E-Business Tax. Also covered are basic troubleshooting and common problems reported when p
lines.

This note was created as an extension of the following notes:

Note 1067402.1, AutoInvoice Setup for Release 12: A Case Study Using a Simple Script
This note provides a comprehensive list of setup steps required to successfully import a transaction via AutoInvoice.

Note 1075757.1, Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12
This notes walks through the possible areas of AutoInvoice wherein you may encounter errors and provides detailed steps on what to check to self-service the resolution of an AutoInvoice issue

Note 745968.1, Troubleshooting AutoInvoice Tax Issues with R12 E-Business Tax (EBTax)
This note assists in diagnosing problems with the calculation or creation of tax lines on invoices where the invoices are created through AutoInvoice.

Last Review Date

February 17, 2011

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

1. Definition of a Manual Tax Line

A Manual tax line is used when taxes are calculated in an external application and the invoice passed to Oracle Receivables is not re-calculating taxes. This is most common when migrating data or when
application to Oracle Receivables.

How is this done? In release 12 this is accomplished by passing a specific set of columns to the interface tables. These columns are used to create a tax record in AR but, more importantly, create all th

2. Interface data fields required to pass a Manual Tax Line

The columns required to create a manual tax line for an invoice include:

Column Name Validation

Amount Required

Batch_source_name Required

Conversion_type Required
Conversion_Rate Required if conversion type = 'USER'

Currency_code Required

Cust_trx_type_id Required
Description Required

Interface_line_attribute(1..X) Multiple lines required - # depends upon setup of trx source

Interface_line_context Set based upon transaction setup

Line_type TAX

Link_to_line_Attribute(1..x) Value from line type of line that this trx is linked

Link_to_line_context Value from line type of line that this trx is linked
Org_id Required

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 1/14
 Tax_code Conditionally required if tax setup uses tax classification code to derive ta

Tax_rate_code Required: Fields below are not required if tax_rate_code is unique acros
tax_rate Conditionally required - set if tax_rate_code is not unique

tax_Jurisdiction_code Conditionally required - set if tax_rate_code is not unique

Tax_Regime_code Conditionally required - set if tax_rate_code is not unique

Tax Conditionally required - set if tax_rate_code is not unique

Tax_Status_code Conditionally required - set if tax_rate_code is not unique

In addition to setting these columns on the tax line, the line type of "Line" should have the taxable flag set to "N" to avoid having additional taxes calculated.

Note: the AR Reference Manual released for Receivables was not accurate when referencing manual tax. It does not include all mandatory fields and has fields listed as mandatory that are not requir
should be corrected in the next documentation patch.

3. Sample Scripts for Invoice and Credit Memo with Manual Tax Lines

The following scripts illustrate how you can pass manual tax lines for an Invoice and an Applied Credit Memo.

TIP: When building scripts to insert data into the Interface tables for AutoInvoice, it is always a good idea to first create a similar transaction manually using the Transactions form. Then you can review
use this when you write the script to manually insert the data. This helps confirm that the data you are using has at least passed the validation in the manual form and will save you several iterations o

Invoice Script

The scripts below are to insert an Invoice with Manual Tax lines using the standard US Sales Tax. Hence it contains 1 record for LINE and 3 records for TAX (State, County, City):

-- Insert record for LINE

INSERT INTO ra_interface_lines_all
(interface_line_context, interface_line_attribute1, interface_line_attribute2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,
quantity, unit_selling_price,
term_id, taxable_flag, amount_includes_tax_flag,
set_of_books_id, org_id)
VALUES
('TIP', 'TIP TAX INVOICE 2', 'INVOICE LINE',
1000.00, 'TIP BATCH SOURCE', 1,
'User', 'USD', 3627,
'TIP TAX INVOICE 2 - ITEM #1', '10-AUG-2010', 'LINE',
11145, 117751,
10, 100.00,
1514, 'N', 'N',
1, 204);

-- Insert Record for State Tax

INSERT INTO ra_interface_lines_all
(interface_line_context, interface_line_attribute1, interface_line_attribute2,
LINK_TO_LINE_CONTEXT, LINK_TO_LINE_ATTRIBUTE1, LINK_TO_LINE_ATTRIBUTE2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,
quantity, unit_selling_price,
term_id, taxable_flag, amount_includes_tax_flag,
set_of_books_id, org_id,
tax_regime_code, tax, tax_status_code,
tax_rate_code, tax_jurisdiction_code, tax_rate)
VALUES
('TIP', 'TIP TAX INVOICE 2', 'TAX LINE ST',
'TIP', 'TIP TAX INVOICE 2', 'INVOICE LINE',
60.00, 'TIP BATCH SOURCE', 1,
'User', 'USD', 3627,
'State Tax', '10-AUG-2010', 'TAX',
11145, 117751,
null, null,
1514, null, null,
1, 204,
'US-SALES-TAX-101', 'STATE', 'STANDARD',
'STANDARD', 'ST-CA-11651', 6.0);

-- Insert Record for County Tax

INSERT INTO ra_interface_lines_all
(interface_line_context, interface_line_attribute1, interface_line_attribute2,
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 2/14
 LINK_TO_LINE_CONTEXT, LINK_TO_LINE_ATTRIBUTE1, LINK_TO_LINE_ATTRIBUTE2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,
quantity, unit_selling_price,
term_id, taxable_flag, amount_includes_tax_flag,
set_of_books_id, org_id,
tax_regime_code, tax, tax_status_code,
tax_rate_code, tax_jurisdiction_code, tax_rate)
VALUES
('TIP', 'TIP TAX INVOICE 2', 'TAX LINE CO',
'TIP', 'TIP TAX INVOICE 2', 'INVOICE LINE',
20.00, 'TIP BATCH SOURCE', 1,
'User', 'USD', 3627,
'County Tax', '10-AUG-2010', 'TAX',
11145, 117751,
null, null,
1514, null, null,
1, 204,
'US-SALES-TAX-101', 'COUNTY', 'STANDARD',
'STANDARD','CO-CA-SAN FRANCISC-11760', 2.0);

-- Insert Record for City Tax

INSERT INTO ra_interface_lines_all
(interface_line_context, interface_line_attribute1, interface_line_attribute2,
LINK_TO_LINE_CONTEXT, LINK_TO_LINE_ATTRIBUTE1, LINK_TO_LINE_ATTRIBUTE2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,
quantity, unit_selling_price,
term_id, taxable_flag, amount_includes_tax_flag,
set_of_books_id, org_id,
tax_regime_code, tax, tax_status_code,
tax_rate_code, tax_jurisdiction_code, tax_rate)
VALUES
('TIP', 'TIP TAX INVOICE 2', 'TAX LINE CI',
'TIP', 'TIP TAX INVOICE 2', 'INVOICE LINE',
30.00, 'TIP BATCH SOURCE', 1,
'User', 'USD', 3627,
'City Tax', '10-AUG-2010', 'TAX',
11145, 117751,
null, null,
1514, null, null,
1, 204,
'US-SALES-TAX-101', 'CITY', 'STANDARD',
'STANDARD','CI-CA-SAN FRANCISC-11761', 3.0);

COMMIT;

For some fields, we pass constant values and for other fields we need to provide values that tie in with the setup created and explained in Note 1067402.1, AutoInvoice Setup for Release 12: A Case Stud
to the various task numbers from Note 1067402.1, wherein the setup was created.

Interface Field Name Explanation Value used in Value used in Value used in
Insert Statement 1 Insert Statement 2 Insert Statem
(for LINE_TYPE = LINE) (for LINE_TYPE = TAX) (for LINE_TYP

INTERFACE_LINE_CONTEXT Identifies the Transaction Flexfield used by the interface data; this helps 'TIP' 'TIP' 'TIP'
AutoInvoice understand what data is being passed in the
INTERFACE_LINE_ATTRIBUTE* fields. The value here ties in with the setup
created in Task 2, where we created the Line Transaction Flexfield 'TIP'.

INTERFACE_LINE_ATTRIBUTE1 The combination of values in these two fields uniquely identify the transaction 'TIP TAX INVOICE 2' and 'TIP TAX INVOICE 2' and 'TAX 'TIP TAX INVOI
and lines you are creating. No 2 rows should have the same combination of values in 'INVOICE LINE' LINE ST' LINE CO'
INTERFACE_LINE_ATTRIBUTE2 these fields.

In Task 7, we defined the grouping rule that indicated that data is to be grouped
by the value in these two fields. Hence, records in the interface table that have
identical information in these two fields will be grouped into one transaction.

LINK_TO_LINE_CONTEXT Identifies the Transaction Flexfield used by the LINE record to which this TAX n/a 'TIP' 'TIP'
line is associated to. It should match INTERFACE_LINE_CONTEXT for LINE_TYPE
= LINE.

LINK_TO_LINE_ATTRIBUTE1 The combination of values in these two fields uniquely identify the LINE record to n/a 'TIP TAX INVOICE 2' and 'TIP TAX INVOI
and which this TAX record is associated. It should match the values used in 'INVOICE LINE' 'INVOICE LINE'
LINK_TO_LINE_ATTRIBUTE2 INTERFACE_LINE_ATTRIBUTE1 and INTERFACE_LINE_ATTRIBUTE2 from the
record for LINE_TYPE = LINE

AMOUNT This field contains the amount value of your transaction; pass in a number This value should be the This value should be the product This value shou
constant. product of the numbers you of the numbers you pass in for of the numbers
pass in for QUANTITY * AMOUNT * TAX_RATE AMOUNT * TAX
UNIT_SELLING_PRICE.
60.00 20.00
1000.00
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 3/14
 BATCH_SOURCE_NAME The value you specify here identifies the transaction batch source to be used by 'TIP BATCH SOURCE' 'TIP BATCH SOURCE' 'TIP BATCH SO
AutoInvoice when interfacing this transaction. In Task 9, we created the Batch
Source 'TIP BATCH SOURCE'.

CONVERSION_RATE For non-functional currency transactions, this field would contain the exchange 1 1 1
rate value. For our test case, we are creating a transaction in the functional
currency = USD, so the rate is 1.

CONVERSION_TYPE Specify the conversion rate type, for our test case we will use 'User'. 'User' 'User' 'User'

CURRENCY_CODE Indicate the currency code of the transaction, for our test case we will use 'USD' 'USD' 'USD'
'USD'.

CUST_TRX_TYPE_ID Identifies the ID associated to the transaction type we created in Task 4 where 3627 3627 3627
we defined 'TIP INVOICE'.

To determine the ID associated to this transaction type, run the following:

Please note that the ID may be different in your instance.

select cust_trx_type_id
from ra_cust_trx_types_all
where name = 'TIP INVOICE';

DESCRIPTION Contains a line item description. 'TIP TAX INVOICE 2 - ITEM When transactions are created When transacti
#1' Manually, the TAX line Manually, the T
DESCRIPTION = null, however DESCRIPTION =
the RA_INTERFACE_LINES_ALL the RA_INTERF
table will not allow this field to table will not al
be inserted as null, so we use be inserted as

'State Tax' 'County Tax'

note that whatever value you note that whate

populate here will not get populate here w
transferred into core AR tables. transferred into

GL_DATE The value you specify here will be used by AutoInvoice as the GL_DATE of your '10-AUG-2010' '10-AUG-2010' '10-AUG-2010'
transaction. Typically the period in which this GL_DATE value falls should be an
open period.

LINE_TYPE Indicates the type of line this interface data defines 'LINE' 'TAX' 'TAX'

ORIG_SYSTEM_BILL_ADDRESS_ID Identifies the Address ID and Customer ID associated to the invoice. 11145 and 117751 11145 and 117751 11145 and 117
and
ORIG_SYSTEM_BILL_CUSTOMER_ID To determine the ID values to use, run the following:
Please note that the ID may be different in your instance.

select c.cust_acct_site_id
orig_system_bill_address_id,
b.cust_account_id
orig_system_bill_customer_id
from hz_parties a,
hz_cust_accounts b,
hz_cust_acct_sites_all c,
hz_cust_site_uses_all d
where a.party_name = 'TIP CUSTOMER 1'
and a.party_id = b.party_id
and c.cust_account_id = b.cust_account_id
and c.cust_acct_site_id =
d.cust_acct_site_id
and d.site_use_code = 'BILL_TO';

QUANTITY Specifies the number of items. 10 null null

UNIT_SELLING_PRICE Specifies the price of each item. 100.00 null null

TERM_ID Identifies the term ID associated with the setup created in Task 8 1514 1514 1514

To determine the ID value to use, run the following:

Please note that the ID may be different in your instance.

select term_id
from ra_terms
where name = 'TIP TERM';

TAXABLE_FLAG Indicates whether or not the transaction is taxable. n/a n/a

IMPORTANT: To
enable passing a
manual tax line, this
flag must be N

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 4/14
 N

AMOUNT_INCLUDES_TAX_FLAG Indicates whether or not the amount is inclusive of taxes. N null null

SET_OF_BOOKS_ID Identifies the Set of Books ID associated to the Operating Unit you are 1 1 1
processing your transaction in

The set of books id is associated to your Operating Unit. If you know your
operating unit ID, you can run the following:
Please note that the ORG_ID in your instance may be different.

select set_of_books_id
from ar_system_parameters_all
where org_id = &org_id;

ORG_ID Indicates the ID of the Operating Unit against which this transaction is created 204 204 204
If you do not know your ORG_ID or SET_OF_BOOKS_ID value, you can use
General Setup diagnostics (e.g. in R 12.0.6 this is Note 732193.1). This will
show the value of ORG_ID beside the Operating Unit Name, and
SET_OF_BOOKS_ID beside the Ledger Name.

TAX_REGIME_CODE Identifies the Tax Regime to be used by the transaction. n/a US-SALES-TAX-101 US-SALES-TAX

TAX Identifies the TAX code. n/a 'STATE' COUNTY'

TAX_STATUS_CODE Identifies the TAX STATUS code. n/a 'STANDARD' 'STANDARD'

TAX_RATE_CODE identifies the TAX RATE code n/a 'STANDARD' 'STANDARD'

TAX_JURISDICTION_CODE identifies the Jurisdiction n/a 'ST-CA-11651' 'CO-CA-SAN FR

TAX_RATE identifues the numeric tax rate n/a 6.0 2.0

WARNING:

It is important to note that when passing manual tax lines, AutoInvoice does limited validation on the Tax information you pass in.

AutoInvoice will check that the Regime, Tax, Status, Rate and Jurisdiction you provided exists and are valid for your Operating Unit. But it will not validate the AMOUNT against the Invoice Line amount a
ensure that you are passing in correct data, as AutoInvoice will simply use the values you pass in without further validation. Also it will not enforce the tax configuration rules, for example in the case o
County and City. If you happen to pass only the State tax and forgot to pass in County and State, AutoInvoice will just take whatever Tax record you provided and will not raise any validation errors.

This can be a very powerful tool as well as a dangerous one, as you may end up inadvertently interfacing incomplete taxes, or taxes with incorrect amounts. You are advised to use this feature with ca

The values used for the TAX_* fields above are from an upgraded instance wherein the Sales Tax setup from Release 11.5, is migrated onto the US-SALES-TAX-101 Regime in Release 12.0. Please refe

Note 810443.1, Overview of the R12 E-Business Tax (EBTax) Upgrade for Order to Cash, the section How Tax Setup Data Migrates from 11i to R12, explains in detail the above TAX* fields.

Note 885225.1, Setting Up and Troubleshooting Tax Accounting for R12 E-Business Tax (EBTax) and Oracle Receivables, if you use AutoAccounting for TAX GL Accounts, this note provides details
segments from.

After inserting the data using the script above, run the AutoInvoice process. Upon completion of the process, check the transaction created:

Responsibility: Receivables Manager

Navigation: Transactions > Transactions

Then run a Query using View > Query By Example

Enter the following filters:

Batch Source name = 'TIP BATCH SOURCE'

Reference = 'TIP TAX INVOICE 2'

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 5/14
 Click on Tax button to review Tax details for the Invoice:

This demonstrates that although the E-Business Tax engine was not invoked the transaction has the 3 standard taxes for US Sales Tax.

Applied Credit Memo Script

The scripts below are to insert an Applied Credit Memo with Manual Tax lines using the standard US Sales Tax. Hence it contains 1 record for LINE and 3 records for TAX (State, County, City). This credi
created with the script above.

-- Insert record for LINE

INSERT INTO ra_interface_lines_all
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 6/14
 (interface_line_context, interface_line_attribute1, interface_line_attribute2,
reference_line_context, reference_line_attribute1, reference_line_attribute2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,
quantity, unit_selling_price,
term_id, taxable_flag, amount_includes_tax_flag,
set_of_books_id, org_id)
VALUES
('TIP', 'TIP TAX CM 2', 'CM LINE',
'TIP', 'TIP TAX INVOICE 2', 'INVOICE LINE',
-100.00, 'TIP BATCH SOURCE', 1,
'User', 'USD', 3628,
'TIP TAX CM 2 - ITEM #1', '10-AUG-2010', 'LINE',
11145, 117751,
-1, 100.00,
null, 'N', 'N',
1, 204);

-- Insert Record for State Tax

INSERT INTO ra_interface_lines_all
(interface_line_context, interface_line_attribute1, interface_line_attribute2,
reference_line_context, reference_line_attribute1, reference_line_attribute2,
LINK_TO_LINE_CONTEXT, LINK_TO_LINE_ATTRIBUTE1, LINK_TO_LINE_ATTRIBUTE2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,
quantity, unit_selling_price,
set_of_books_id, org_id,
tax_regime_code, tax, tax_status_code,
tax_rate_code, tax_jurisdiction_code, tax_rate)
VALUES
('TIP', 'TIP TAX CM 2', 'TAX LINE ST',
'TIP', 'TIP TAX INVOICE 2', 'TAX LINE ST',
'TIP', 'TIP TAX CM 2', 'CM LINE',
-6.00, 'TIP BATCH SOURCE', 1,
'User', 'USD', 3628,
'Credit State Tax', '10-AUG-2010', 'TAX',
11145, 117751,
null, null,
1, 204,
'US-SALES-TAX-101', 'STATE', 'STANDARD',
'STANDARD', 'ST-CA-11651', 6.0);

-- Insert Record for County Tax

INSERT INTO ra_interface_lines_all
(interface_line_context, interface_line_attribute1, interface_line_attribute2,
reference_line_context, reference_line_attribute1, reference_line_attribute2,
LINK_TO_LINE_CONTEXT, LINK_TO_LINE_ATTRIBUTE1, LINK_TO_LINE_ATTRIBUTE2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,
quantity, unit_selling_price,
set_of_books_id, org_id,
tax_regime_code, tax, tax_status_code,
tax_rate_code, tax_jurisdiction_code, tax_rate)
VALUES
('TIP', 'TIP TAX CM 2', 'TAX LINE CO',
'TIP', 'TIP TAX INVOICE 2', 'TAX LINE CO',
'TIP', 'TIP TAX CM 2', 'CM LINE',
-2.00, 'TIP BATCH SOURCE', 1,
'User', 'USD', 3628,
'Credit County Tax', '10-AUG-2010', 'TAX',
11145, 117751,
null, null,
1, 204,
'US-SALES-TAX-101', 'COUNTY', 'STANDARD',
'STANDARD','CO-CA-SAN FRANCISC-11760', 2.0);

-- Insert Record for City Tax

INSERT INTO ra_interface_lines_all
(interface_line_context, interface_line_attribute1, interface_line_attribute2,
reference_line_context, reference_line_attribute1, reference_line_attribute2,
LINK_TO_LINE_CONTEXT, LINK_TO_LINE_ATTRIBUTE1, LINK_TO_LINE_ATTRIBUTE2,
amount, batch_source_name, conversion_rate,
conversion_type, currency_code, cust_trx_type_id,
description, gl_date, line_type,
orig_system_bill_address_id, orig_system_bill_customer_id,

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 7/14
 quantity, unit_selling_price,
set_of_books_id, org_id,
tax_regime_code, tax, tax_status_code,
tax_rate_code, tax_jurisdiction_code, tax_rate)
VALUES
('TIP', 'TIP TAX CM 2', 'TAX LINE CI',
'TIP', 'TIP TAX INVOICE 2', 'TAX LINE CI',
'TIP', 'TIP TAX CM 2', 'CM LINE',
-3.00, 'TIP BATCH SOURCE', 1,
'User', 'USD', 3628,
'Credit City Tax', '10-AUG-2010', 'TAX',
11145, 117751,
null, null,
1, 204,
'US-SALES-TAX-101', 'CITY', 'STANDARD',
'STANDARD','CI-CA-SAN FRANCISC-11761', 3.0);

commit;

For some fields, we pass constant values and for other fields we need to provide values that tie in with the setup created and explained in Note 1067402.1, AutoInvoice Setup for Release 12: A Case Stud
to the various task numbers from Note 1067402.1, wherein the setup was created.

Interface Field Name Explanation Value used in Value used in Value used
Insert Statement 1 Insert Statement 2 Insert Sta
(for LINE_TYPE = LINE) (for LINE_TYPE = TAX) (for LINE_

INTERFACE_LINE_CONTEXT Identifies the Transaction Flexfield used by the interface data; this helps AutoInvoice 'TIP' 'TIP' 'TIP'
understand what data is being passed in the INTERFACE_LINE_ATTRIBUTE* fields. The
value here ties in with the setup created in Task 2, where we created the Line
Transaction Flexfield 'TIP'.

INTERFACE_LINE_ATTRIBUTE1 The combination of values in these two fields uniquely identify the transaction you are 'TIP TAX CM 2' and 'CM 'TIP TAX CM 2' and 'TAX LINE 'TIP TAX CM
and creating. No 2 rows should have the same combination of values in these fields. LINE' ST' CO'
INTERFACE_LINE_ATTRIBUTE2
In Task 7, we defined the grouping rule that indicated that data is to be grouped by the
value in these two fields. Hence, records in the interface table that have identical
information in these two fields will be grouped into one transaction.

LINK_TO_LINE_CONTEXT Identifies the Transaction Flexfield used by the LINE record to which this TAX line is n/a 'TIP' 'TIP'
associated to, should match INTERFACE_LINE_CONTEXT for LINE_TYPE = LINE.

LINK_TO_LINE_ATTRIBUTE1 The combination of values in these two fields uniquely identify the LINE record to which n/a 'TIP TAX CM 2' and 'CM LINE' 'TIP TAX CM
and this TAX record is associated. It should match the values used in
LINK_TO_LINE_ATTRIBUTE2 INTERFACE_LINE_ATTRIBUTE1 and INTERFACE_LINE_ATTRIBUTE2 from the record for
LINE_TYPE = LINE

REFERENCE_LINE_CONTEXT Identifies the Transaction Flexfield of the Invoice line this credit memo line is being 'TIP' 'TIP' 'TIP'
applied to.

REFERENCE_LINE_ATRIBUTE1 The combination of values in these two fields uniquely identify the record you want to 'TIP TAX INVOICE 2' and 'TIP TAX INVOICE 2' and 'TIP TAX IN
apply this credit memo to. The values in these fields need to match the 'INVOICE LINE' 'TAX LINE ST' 'TAX LINE C
INTERFACE_LINE* fields of the invoice line being credited, because this is how you are
telling Autoinvoice which Invoice lines you want to apply this Credit memo to.

AMOUNT This field contains the value of your transaction; pass in a number constant. This value should be the This value should be the This value s
product of the numbers product of the numbers you product of t
you pass in for QUANTITY pass in for AMOUNT * pass in for
* UNIT_SELLING_PRICE. TAX_RATE TAX_RATE

-100 -6.00 -2.00

BATCH_SOURCE_NAME The value you specify here identifies the transaction batch source to be used by 'TIP BATCH SOURCE' 'TIP BATCH SOURCE' 'TIP BATCH
AutoInvoice when interfacing this transaction. In Task 9, we created the Batch Source
'TIP BATCH SOURCE'.

CONVERSION_RATE For non-functional currency transactions, this field would contain the exchange rate 1 1 1
value. For our test case, we are creating a transaction in the functional currency =
USD, so the rate is 1.

CONVERSION_TYPE Specify the conversion rate type, for our test case we will use 'User'. 'User' 'User' 'User'

CURRENCY_CODE Indicate the currency code of the transaction, for our test case we will use 'USD'. 'USD' 'USD' 'USD'

CUST_TRX_TYPE_ID Identifies the ID associated to the transaction type we created in Task 4 where we 3628 3628 3628
defined 'TIP INVOICE'.

To determine the ID associated to this transaction type, run the following:

Please note that the ID may be different in your instance.

select cust_trx_type_id
from ra_cust_trx_types_all
where name = 'TIP CM';

DESCRIPTION Contains a line item description. 'TIP TAX CM 2 - ITEM #1' When transactions are created When trans
Manually, the TAX lines Manually, th
DESCRIPTION = null, however DESCRIPTIO
the RA_INTERFACE_LINES_ALL the RA_INT

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 8/14
 table will not allow this field to table will no
be inserted as null, so we use be inserted

'Credit State Tax' 'Credit Coun

note that whatever value you note that w

populate here will not get populate he
transferred into core AR tables. transferred
tables.

GL_DATE The value you specify here will be used by AutoInvoice as the GL_DATE of your '10-AUG-2010' '10-AUG-2010' '10-AUG-20
transaction. Typically the period in which this GL_DATE value falls should be an open
period.

LINE_TYPE Indicates the type of line this interface data defines 'LINE' 'TAX' 'TAX'

ORIG_SYSTEM_BILL_ADDRESS_ID Identifies the Address ID and Customer ID associated to the invoice. 11145 and 117751 11145 and 117751 11145 and
and
ORIG_SYSTEM_BILL_CUSTOMER_ID To determine the ID values to use, run the following:
Please note that the ID may be different in your instance.

select c.cust_acct_site_id
orig_system_bill_address_id, b.cust_account_id
orig_system_bill_customer_id
from hz_parties a,
hz_cust_accounts b,
hz_cust_acct_sites_all c,
hz_cust_site_uses_all d
where a.party_name = 'TIP CUSTOMER 1'
and a.party_id = b.party_id
and c.cust_account_id = b.cust_account_id
and c.cust_acct_site_id = d.cust_acct_site_id
and d.site_use_code = 'BILL_TO';

QUANTITY Specifies the number of items. -1 null null

UNIT_SELLING_PRICE Specifies the price of each item. 100.00 null null

TERM_ID A credit memo has no payment terms so this is Null null null null

TAXABLE_FLAG Indicates whether or not the transaction is taxable. n/a n/a

IMPORTANT: To
enable passing a
manual tax line,
this flag must be N

AMOUNT_INCLUDES_TAX_FLAG Indicates whether or not the amount is inclusive of taxes. N n/a n/a

SET_OF_BOOKS_ID Identifies the Set of Books ID associated to the Operating Unit you are processing your 1 1 1
transaction in

The set of books id is associated to your Operating Unit. If you know your operating unit
ID, you can run the following:
Please note that the ORG_ID in your instance may be different.

select set_of_books_id
from ar_system_parameters_all
where org_id = &org_id;

ORG_ID Indicates the ID of the Operating Unit against which this transaction is created 204 204 204
If you do not know your ORG_ID or SET_OF_BOOKS_ID value, you can use General
Setup diagnostics (e.g. in R 12.0.6 this is Note 732193.1). This will show the value of
ORG_ID beside the Operating Unit Name, and SET_OF_BOOKS_ID beside the Ledger
Name.

TAX_REGIME_CODE Identifies the Tax Regime to be used by the transaction. n/a US-SALES-TAX-101 US-SALES-T

TAX Identifies the TAX code. n/a 'STATE' COUNTY'

TAX_STATUS_CODE Identifies the TAX STATUS code. n/a 'STANDARD' 'STANDARD

TAX_RATE_CODE identifies the TAX RATE code n/a 'STANDARD' 'STANDARD

TAX_JURISDICTION_CODE identifies the Jurisdiction n/a 'ST-CA-11651' 'CO-CA-SAN

TAX_RATE identifues the numeric tax rate n/a 6.0 2.0

After inserting the data using the script above, run the AutoInvoice process. Upon completion of the process, check the transaction created:

Responsibility: Receivables Manager

Navigation: Transactions > Transactions

Then run a Query using View > Query By Example

Enter the following filters:

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 9/14
 Batch Source name = 'TIP BATCH SOURCE'
Reference = 'TIP TAX CM 2'

Click on Tax button to review Tax details for the Credit Memo:

This demonstrates that although the E-Business Tax engine was not invoked the transaction has the 3 standard taxes for US Sales Tax.

View the Application of this Credit Memo to the Invoice created earlier.
Navigation: from the toolbar menu, Actions > Applications

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 10/14
 This shows that Credit Memo#130 was applied to Invoice #129 which caused a partial credit against the Invoice balance, bringing it down to 999.00.

4. Troubleshooting Issues when passing Manual Tax Lines for Invoices

* The following patches refer to the latest available file as of the last update date for this note. Use this section as follows:
1) Check your versions of the files shown.
2) If you are on a lower version then apply the recommended patches.
3) If you are on a higher version then review other fixes in this note.

Be aware that the patch often refers to a higher version of the fixed file than was originally noted in the bug fix. For this reason, the patch read-me file will not mention the exact issue discussed.
discovered by customers who patch to fix one problem but find that they must again patch the same file later on when another known issue is uncovered.

Several issues have been reported with Invoices containing Manual Tax lines. The issues and fixes include:

Issue Cause 12.0 Fix 12.1 Fix

AutoInvoice log file returns the error: Multiple Please review Note 1159503.1, Autoinvoice Same as
Import Error: ERROR from eBusiness Tax - return 12.0
ERROR: from eBusiness Tax - return code = 2
code = 2

Autoinvoice Ignoring Manual Tax Line bug 6509803 Fixed Files/Versions: Included in
With Wrong Tax Code Without Any Error AREBTAIB.pls 120.25.12000000.5 Baseline
Message Tax Calculation errors out for some invoices, but the ZX_ERRORS_GT is not zxifsrvctypspkgs.pls 120.27.12000000.2 12.1
populated correctly. Also aftererroring out the Tax Calculation should continue for the zxifsrvctypspkgb.pls 120.230.12000000.12
next transaction. zxifpubsrvcspubb.pls 120.275.12000000.11

Recommended Patch*:
Patch 9249841
Patch 9067492

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 11/14
 ERROR Multiple See Note 751126.1
ORA-28115: policy with check option
violation
FRM-40508:ORACLE error: unable to
insert record

ERROR: Multiple Please review Note 1316691.1, Autoinvoice Same as

from eBusiness Tax - return code = 1 Import Error: ERROR from eBusiness Tax - return 12.0
code = 1

5. Troubleshooting Issues when passing Manual Tax Lines for Credit Memos

Several Issues have been reported with Credit Memo's being processed for Manual Tax invoices. The issues and fixes include:

Issue Cause 12.0 Fix 12.1 Fix

When Importing manual tax lines on credit memos, the tax distribution lines are Bug 8669930 & Bug 8502340 Fixed Files: Fixed Files:
not being created in Receivables. zxdiprodintgpkgb.pls zxdiprodintgpkgb.pls
120.47.12000000.18 120.48.12010000.13
zxditaxapplipkgb.pls zxapdefvalpkgb.pls
120.227.12000000.54 120.80.12010000.8
zxditaxlndetpkgb.pls zxdiimpdocmtpkgb.pls
120.82.12000000.25 120.61.12010000.6
zxapdefvalpkgb.pls zxditaxapplipkgb.pls
120.73.12000000.23 120.260.12010000.15
zxdiimpdocmtpkgb.pls zxditaxlndetpkgb.pls
120.58.12000000.11 120.91.12010000.7

Recommended Patches*: Recommended Patches*:

Patch 8901069 Patch 9337544
Patch 8502340 Patch 8502340

When Importing manual tax lines on credit memos, get an error: The tax line of Bug 9980968 Fixed Files: Fixed Files:
the credit memo does not have a link to the invoice. This is a controlled release patch you will need to AREBTAIB.pls AREBTAIB.pls
contact Support for the patch password. 120.25.12000000.40 120.31.12010000.22

6. Troubleshooting Issues when passing Manual Tax Lines With Latin Tax Engine

Latin Tax Engine customers on release 12.0 should ensure that they are on zxdiprodintgpkgb.pls 120.47.12000000.10 or higher code

Issue Cause 12.0 Fix 12.1 Fix

Tax Debug Log Shows: In the case of Latin Tax Engine, the subscription details are Check this as Same as 12.0
ZX_TDS_UTILITIES_PKG.get_tax_cache_info(-)return_status = E automatically created when the LTE setup is completed. Due to some follows:
ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.create_detail_tax_line Incorrect code issue, the same was not happening in earlier versions of R12. -> Navigate to Tax
return_status after calling This is was fixed as part of Bug 6320613. If this did not happen, users Managers / Tax
ZX_TDS_UTILITIES_PKG.get_tax_cache_info() manually subscribed the operating unit to the regime using the "Tax Regimes / Query for
ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.create_detail_tax_line Managers" responsibility. Regime
RETURN_STATUS = E -> Click on Update /
ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.create_detail_tax_line.END In the case of Bug 7948225, the user incorrectly subscribed the Continue
ZX_PRODUCT_INTEGRATION_PKG.create_detail_tax_line(-) operating unit to the regime. The Latin Tax subscription requires that -> Please check
ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.import_trx_line_with_taxes the parties use "Common Configuration Owners with Party Overrides". 'Configuration for
Incorrect return_status after calling create_detail_tax_line() Taxes and Rules'
ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.import_trx_line_with_taxes column.
RETURN_STATUS = E -> Parties/LEs must
ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.import_trx_line_with_taxes.END be created with
ZX_PRODUCT_INTEGRATION_PKG.import_trx_line_with_taxes(-) 'Common
ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.import_document_with_tax Configuration with
Errored out when calling import_trx_line_with_taxes(). Party Overrides'
ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.import_document_with_tax.END
ZX_PRODUCT_INTEGRATION_PKG: import_document_with_tax(-)
ZX.PLSQL.ZX_SRVC_TYP_PKG.CALL_LTE LTE calculate tax returned errors
ZX.PLSQL.ZX_API_PUB.DUMP_MSG.BEGIN ZX_API_PUB: DUMP_MSG()+
ZX.PLSQL.ZX_API_PUB.DUMP_MSG.BEGIN ZX_API_PUB: DUMP_MSG()-
ZX.PLSQL.ZX_SRVC_TYP_PKG.IMPORT status returned from LTE: E

Latin Tax: Wrong Taxable Base in the Transaction with Manual Tax Bug 9467888 Fixed File: Fixed File:
Imported Through AutoInvoice zxdiprodintgpkgb.pls zxdiprodintgpkgb.pls
120.47.12000000.23 120.48.12010000.18

Recommended Recommended
patch: Patch:

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 12/14
 Patch 9467888 Patch 9467888

Manual Tax Lines are not importing Setup incomplete via Receivables to Same as 12.0
setup ->
transactions ->
transaction types ->
query
back transaction
type in question and
check the default
tax classification
code or setup a new
transaction type and
check the box

Attempts to cancel (Credit) an invoice generated via AutoInvoice with Bug 8776916 Fixed File: Fixed File:
manual tax lines returns an unexpected error and record is not saved. This zxdiprodintgpkgb.pls zxdiprodintgpkgb.pls
occurs only if the Latin Tax Engine is in use. 120.47.12000000.19 120.48.12010000.14

Recommended Recommended
Patch Patch:
Patch 9467888 Patch 9467888

This Tax Rate Percentage is invalid As per Bug 8585391 Correct Tax Rate Same as R12
The Tax Rate Percentage overriding is allowed only if the value of Setup to allow ad-
'Allow Ad Hoc Rate' flag is hoc rate
'Y' for the Tax Rate Code.

References

NOTE:745968.1 - Troubleshooting AutoInvoice Tax Issues with R12 E-Business Tax (EBTax)

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 13/14
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 14/14