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 Amount Batch_source_name Conversion_type Conversion_Rate Currency_code Cust_trx_type_id Description Interface_line_attribute(1..X) Interface_line_context Line_type Link_to_line_Attribute(1..x) Link_to_line_context Org_id Validation Required Required Required Required if conversion type = 'USER' Required Required Required Multiple lines required - # depends upon setup of trx source Set based upon transaction setup TAX Value from line type of line that this trx is linked Value from line type of line that this trx is linked Required

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

1/14

Tax_code Tax_rate_code tax_rate tax_Jurisdiction_code Tax_Regime_code Tax Tax_Status_code

Conditionally required if tax setup uses tax classification code to derive ta

Required: Fields below are not required if tax_rate_code is unique acros Conditionally required - set if tax_rate_code is not unique Conditionally required - set if tax_rate_code is not unique Conditionally required - set if tax_rate_code is not unique Conditionally required - set if tax_rate_code is not unique 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):

-I n s e r tr e c o r df o rL I N E I N S E R TI N T Or a _ i n t e r f a c e _ l i n e s _ a l l ( i n t e r f a c e _ l i n e _ c o n t e x t ,i n t e r f a c e _ l i n e _ a t t r i b u t e 1 ,i n t e r f a c e _ l i n e _ a t t r i b u t e 2 , a m o u n t ,b a t c h _ s o u r c e _ n a m e ,c o n v e r s i o n _ r a t e , c o n v e r s i o n _ t y p e ,c u r r e n c y _ c o d e ,c u s t _ t r x _ t y p e _ i d , d e s c r i p t i o n ,g l _ d a t e ,l i n e _ t y p e , o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d ,o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d , q u a n t i t y ,u n i t _ s e l l i n g _ p r i c e , t e r m _ i d ,t a x a b l e _ f l a g ,a m o u n t _ i n c l u d e s _ t a x _ f l a g , s e t _ o f _ b o o k s _ i d ,o r g _ i d ) V A L U E S ( ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' I N V O I C EL I N E ' , 1 0 0 0 . 0 0 ,' T I PB A T C HS O U R C E ' ,1 , ' U s e r ' ,' U S D ' ,3 6 2 7 , ' T I PT A XI N V O I C E2-I T E M# 1 ' ,' 1 0 A U G 2 0 1 0 ' ,' L I N E ' , 1 1 1 4 5 ,1 1 7 7 5 1 , 1 0 ,1 0 0 . 0 0 , 1 5 1 4 ,' N ' ,' N ' , 1 ,2 0 4 ) ; -I n s e r tR e c o r df o rS t a t eT a x I N S E R TI N T Or a _ i n t e r f a c e _ l i n e s _ a l l ( i n t e r f a c e _ l i n e _ c o n t e x t ,i n t e r f a c e _ l i n e _ a t t r i b u t e 1 ,i n t e r f a c e _ l i n e _ a t t r i b u t e 2 , L I N K _ T O _ L I N E _ C O N T E X T ,L I N K _ T O _ L I N E _ A T T R I B U T E 1 ,L I N K _ T O _ L I N E _ A T T R I B U T E 2 , a m o u n t ,b a t c h _ s o u r c e _ n a m e ,c o n v e r s i o n _ r a t e , c o n v e r s i o n _ t y p e ,c u r r e n c y _ c o d e ,c u s t _ t r x _ t y p e _ i d , d e s c r i p t i o n ,g l _ d a t e ,l i n e _ t y p e , o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d ,o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d , q u a n t i t y ,u n i t _ s e l l i n g _ p r i c e , t e r m _ i d ,t a x a b l e _ f l a g ,a m o u n t _ i n c l u d e s _ t a x _ f l a g , s e t _ o f _ b o o k s _ i d ,o r g _ i d , t a x _ r e g i m e _ c o d e ,t a x ,t a x _ s t a t u s _ c o d e , t a x _ r a t e _ c o d e ,t a x _ j u r i s d i c t i o n _ c o d e ,t a x _ r a t e ) V A L U E S ( ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' T A XL I N ES T ' , ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' I N V O I C EL I N E ' , 6 0 . 0 0 ,' T I PB A T C HS O U R C E ' ,1 , ' U s e r ' ,' U S D ' ,3 6 2 7 , ' S t a t eT a x ' ,' 1 0 A U G 2 0 1 0 ' ,' T A X ' , 1 1 1 4 5 ,1 1 7 7 5 1 , n u l l ,n u l l , 1 5 1 4 ,n u l l ,n u l l , 1 ,2 0 4 , ' U S S A L E S T A X 1 0 1 ' ,' S T A T E ' ,' S T A N D A R D ' , ' S T A N D A R D ' ,' S T C A 1 1 6 5 1 ' ,6 . 0 ) ; -I n s e r tR e c o r df o rC o u n t yT a x I N S E R TI N T Or a _ i n t e r f a c e _ l i n e s _ a l l ( i n t e r f a c e _ l i n e _ c o n t e x t ,i n t e r f a c e _ l i n e _ a t t r i b u t e 1 ,i n t e r f a c e _ l i n e _ a t t r i b u t e 2 ,
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 2/14

L I N K _ T O _ L I N E _ C O N T E X T ,L I N K _ T O _ L I N E _ A T T R I B U T E 1 ,L I N K _ T O _ L I N E _ A T T R I B U T E 2 , a m o u n t ,b a t c h _ s o u r c e _ n a m e ,c o n v e r s i o n _ r a t e , c o n v e r s i o n _ t y p e ,c u r r e n c y _ c o d e ,c u s t _ t r x _ t y p e _ i d , d e s c r i p t i o n ,g l _ d a t e ,l i n e _ t y p e , o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d ,o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d , q u a n t i t y ,u n i t _ s e l l i n g _ p r i c e , t e r m _ i d ,t a x a b l e _ f l a g ,a m o u n t _ i n c l u d e s _ t a x _ f l a g , s e t _ o f _ b o o k s _ i d ,o r g _ i d , t a x _ r e g i m e _ c o d e ,t a x ,t a x _ s t a t u s _ c o d e , t a x _ r a t e _ c o d e ,t a x _ j u r i s d i c t i o n _ c o d e ,t a x _ r a t e ) V A L U E S ( ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' T A XL I N EC O ' , ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' I N V O I C EL I N E ' , 2 0 . 0 0 ,' T I PB A T C HS O U R C E ' ,1 , ' U s e r ' ,' U S D ' ,3 6 2 7 , ' C o u n t yT a x ' ,' 1 0 A U G 2 0 1 0 ' ,' T A X ' , 1 1 1 4 5 ,1 1 7 7 5 1 , n u l l ,n u l l , 1 5 1 4 ,n u l l ,n u l l , 1 ,2 0 4 , ' U S S A L E S T A X 1 0 1 ' ,' C O U N T Y ' ,' S T A N D A R D ' , ' S T A N D A R D ' , ' C O C A S A NF R A N C I S C 1 1 7 6 0 ' ,2 . 0 ) ; -I n s e r tR e c o r df o rC i t yT a x I N S E R TI N T Or a _ i n t e r f a c e _ l i n e s _ a l l ( i n t e r f a c e _ l i n e _ c o n t e x t ,i n t e r f a c e _ l i n e _ a t t r i b u t e 1 ,i n t e r f a c e _ l i n e _ a t t r i b u t e 2 , L I N K _ T O _ L I N E _ C O N T E X T ,L I N K _ T O _ L I N E _ A T T R I B U T E 1 ,L I N K _ T O _ L I N E _ A T T R I B U T E 2 , a m o u n t ,b a t c h _ s o u r c e _ n a m e ,c o n v e r s i o n _ r a t e , c o n v e r s i o n _ t y p e ,c u r r e n c y _ c o d e ,c u s t _ t r x _ t y p e _ i d , d e s c r i p t i o n ,g l _ d a t e ,l i n e _ t y p e , o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d ,o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d , q u a n t i t y ,u n i t _ s e l l i n g _ p r i c e , t e r m _ i d ,t a x a b l e _ f l a g ,a m o u n t _ i n c l u d e s _ t a x _ f l a g , s e t _ o f _ b o o k s _ i d ,o r g _ i d , t a x _ r e g i m e _ c o d e ,t a x ,t a x _ s t a t u s _ c o d e , t a x _ r a t e _ c o d e ,t a x _ j u r i s d i c t i o n _ c o d e ,t a x _ r a t e ) V A L U E S ( ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' T A XL I N EC I ' , ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' I N V O I C EL I N E ' , 3 0 . 0 0 ,' T I PB A T C HS O U R C E ' ,1 , ' U s e r ' ,' U S D ' ,3 6 2 7 , ' C i t yT a x ' ,' 1 0 A U G 2 0 1 0 ' ,' T A X ' , 1 1 1 4 5 ,1 1 7 7 5 1 , n u l l ,n u l l , 1 5 1 4 ,n u l l ,n u l l , 1 ,2 0 4 , ' U S S A L E S T A X 1 0 1 ' ,' C I T Y ' ,' S T A N D A R D ' , ' S T A N D A R D ' , ' C I C A S A NF R A N C I S C 1 1 7 6 1 ' ,3 . 0 ) ; C O M M I T ;

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 Insert Statement 1 (for LINE_TYPE = LINE) 'TIP' Value used in Insert Statement 2 (for LINE_TYPE = TAX) 'TIP'

Value used in Insert Statem (for LINE_TYP 'TIP'

INTERFACE_LINE_CONTEXT

Identifies the Transaction Flexfield used by the interface data; this helps 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 and INTERFACE_LINE_ATTRIBUTE2

The combination of values in these two fields uniquely identify the transaction 'TIP TAX INVOICE 2' and lines you are creating. No 2 rows should have the same combination of values in 'INVOICE LINE' 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.

'TIP TAX INVOICE 2' and 'TAX LINE ST'

'TIP TAX INVOI LINE CO'

LINK_TO_LINE_CONTEXT

Identifies the Transaction Flexfield used by the LINE record to which this TAX line is associated to. It should match INTERFACE_LINE_CONTEXT for LINE_TYPE = LINE.

n/a

'TIP'

'TIP'

LINK_TO_LINE_ATTRIBUTE1 and LINK_TO_LINE_ATTRIBUTE2 AMOUNT

The combination of values in these two fields uniquely identify the LINE record to n/a which this TAX record is associated. It should match the values used in INTERFACE_LINE_ATTRIBUTE1 and INTERFACE_LINE_ATTRIBUTE2 from the record for LINE_TYPE = LINE This field contains the amount value of your transaction; pass in a number constant. This value should be the product of the numbers you pass in for QUANTITY * UNIT_SELLING_PRICE. 1000.00

'TIP TAX INVOICE 2' and 'INVOICE LINE'

'TIP TAX INVOI 'INVOICE LINE'

This value should be the product of the numbers you pass in for AMOUNT * TAX_RATE 60.00

This value shou of the numbers AMOUNT * TAX 20.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 AutoInvoice when interfacing this transaction. In Task 9, we created the Batch Source 'TIP BATCH SOURCE'. For non-functional currency transactions, this field would contain the exchange rate value. For our test case, we are creating a transaction in the functional currency = USD, so the rate is 1. Specify the conversion rate type, for our test case we will use 'User'. Indicate the currency code of the transaction, for our test case we will use 'USD'. Identifies the ID associated to the transaction type we created in Task 4 where 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.

'TIP BATCH SOURCE'

'TIP BATCH SOURCE'

'TIP BATCH SO

CONVERSION_RATE

CONVERSION_TYPE CURRENCY_CODE

'User' 'USD'

'User' 'USD'

'User' 'USD'

CUST_TRX_TYPE_ID

3627

3627

3627

s e l e c tc u s t _ t r x _ t y p e _ i d f r o mr a _ c u s t _ t r x _ t y p e s _ a l l w h e r en a m e=' T I PI N V O I C E ' ;

DESCRIPTION

Contains a line item description.

'TIP TAX INVOICE 2 - ITEM #1'

When transactions are created Manually, the TAX line DESCRIPTION = null, however the RA_INTERFACE_LINES_ALL table will not allow this field to be inserted as null, so we use 'State Tax' note that whatever value you populate here will not get transferred into core AR tables.

When transacti Manually, the T DESCRIPTION = the RA_INTERF table will not al be inserted as 'County Tax'

note that whate populate here w transferred into '10-AUG-2010'

GL_DATE

The value you specify here will be used by AutoInvoice as the GL_DATE of your transaction. Typically the period in which this GL_DATE value falls should be an open period. Indicates the type of line this interface data defines

'10-AUG-2010'

'10-AUG-2010'

LINE_TYPE

'LINE' 11145 and 117751

'TAX' 11145 and 117751

'TAX'

ORIG_SYSTEM_BILL_ADDRESS_ID Identifies the Address ID and Customer ID associated to the invoice. 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.

11145 and 117

s e l e c tc . c u s t _ a c c t _ s i t e _ i d o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d , b . c u s t _ a c c o u n t _ i d o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d f r o mh z _ p a r t i e sa , h z _ c u s t _ a c c o u n t sb , h z _ c u s t _ a c c t _ s i t e s _ a l lc , h z _ c u s t _ s i t e _ u s e s _ a l ld w h e r ea . p a r t y _ n a m e=' T I PC U S T O M E R1 ' a n da . p a r t y _ i d=b . p a r t y _ i d a n dc . c u s t _ a c c o u n t _ i d=b . c u s t _ a c c o u n t _ i d a n dc . c u s t _ a c c t _ s i t e _ i d= d . c u s t _ a c c t _ s i t e _ i d a n dd . s i t e _ u s e _ c o d e=' B I L L _ T O ' ;

QUANTITY UNIT_SELLING_PRICE TERM_ID Specifies the number of items. Specifies the price of each item. Identifies the term ID associated with the setup created in Task 8 To determine the ID value to use, run the following: Please note that the ID may be different in your instance. 10 100.00 1514 null null 1514 null null 1514

s e l e c tt e r m _ i d f r o mr a _ t e r m s w h e r en a m e=' T I PT E R M ' ;
TAXABLE_FLAG Indicates whether or not the transaction is taxable. IMPORTANT: To enable passing a manual tax line, this flag must be N n/a n/a

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

4/14

N AMOUNT_INCLUDES_TAX_FLAG SET_OF_BOOKS_ID Indicates whether or not the amount is inclusive of taxes. Identifies the Set of Books ID associated to the Operating Unit you are 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. N 1 null 1 null 1

s e l e c ts e t _ o f _ b o o k s _ i d f r o ma r _ s y s t e m _ p a r a m e t e r s _ a l l w h e r eo r g _ i d=& o r g _ i d ;
ORG_ID Indicates the ID of the Operating Unit against which this transaction is created 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. Identifies the Tax Regime to be used by the transaction. Identifies the TAX code. Identifies the TAX STATUS code. identifies the TAX RATE code identifies the Jurisdiction identifues the numeric tax rate 204 204 204

TAX_REGIME_CODE TAX TAX_STATUS_CODE TAX_RATE_CODE TAX_JURISDICTION_CODE TAX_RATE

n/a n/a n/a n/a n/a n/a

US-SALES-TAX-101 'STATE' 'STANDARD' 'STANDARD' 'ST-CA-11651' 6.0

US-SALES-TAX COUNTY' 'STANDARD' 'STANDARD'

'CO-CA-SAN FR 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.

-I n s e r tr e c o r df o rL I N E I N S E R TI N T Or a _ i n t e r f a c e _ l i n e s _ a l l
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 6/14

( i n t e r f a c e _ l i n e _ c o n t e x t ,i n t e r f a c e _ l i n e _ a t t r i b u t e 1 ,i n t e r f a c e _ l i n e _ a t t r i b u t e 2 , r e f e r e n c e _ l i n e _ c o n t e x t ,r e f e r e n c e _ l i n e _ a t t r i b u t e 1 ,r e f e r e n c e _ l i n e _ a t t r i b u t e 2 , a m o u n t ,b a t c h _ s o u r c e _ n a m e ,c o n v e r s i o n _ r a t e , c o n v e r s i o n _ t y p e ,c u r r e n c y _ c o d e ,c u s t _ t r x _ t y p e _ i d , d e s c r i p t i o n ,g l _ d a t e ,l i n e _ t y p e , o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d ,o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d , q u a n t i t y ,u n i t _ s e l l i n g _ p r i c e , t e r m _ i d ,t a x a b l e _ f l a g ,a m o u n t _ i n c l u d e s _ t a x _ f l a g , s e t _ o f _ b o o k s _ i d ,o r g _ i d ) V A L U E S ( ' T I P ' ,' T I PT A XC M2 ' ,' C ML I N E ' , ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' I N V O I C EL I N E ' , 1 0 0 . 0 0 ,' T I PB A T C HS O U R C E ' ,1 , ' U s e r ' ,' U S D ' ,3 6 2 8 , ' T I PT A XC M2-I T E M# 1 ' ,' 1 0 A U G 2 0 1 0 ' ,' L I N E ' , 1 1 1 4 5 ,1 1 7 7 5 1 , 1 ,1 0 0 . 0 0 , n u l l ,' N ' ,' N ' , 1 ,2 0 4 ) ; -I n s e r tR e c o r df o rS t a t eT a x I N S E R TI N T Or a _ i n t e r f a c e _ l i n e s _ a l l ( i n t e r f a c e _ l i n e _ c o n t e x t ,i n t e r f a c e _ l i n e _ a t t r i b u t e 1 ,i n t e r f a c e _ l i n e _ a t t r i b u t e 2 , r e f e r e n c e _ l i n e _ c o n t e x t ,r e f e r e n c e _ l i n e _ a t t r i b u t e 1 ,r e f e r e n c e _ l i n e _ a t t r i b u t e 2 , L I N K _ T O _ L I N E _ C O N T E X T ,L I N K _ T O _ L I N E _ A T T R I B U T E 1 ,L I N K _ T O _ L I N E _ A T T R I B U T E 2 , a m o u n t ,b a t c h _ s o u r c e _ n a m e ,c o n v e r s i o n _ r a t e , c o n v e r s i o n _ t y p e ,c u r r e n c y _ c o d e ,c u s t _ t r x _ t y p e _ i d , d e s c r i p t i o n ,g l _ d a t e ,l i n e _ t y p e , o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d ,o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d , q u a n t i t y ,u n i t _ s e l l i n g _ p r i c e , s e t _ o f _ b o o k s _ i d ,o r g _ i d , t a x _ r e g i m e _ c o d e ,t a x ,t a x _ s t a t u s _ c o d e , t a x _ r a t e _ c o d e ,t a x _ j u r i s d i c t i o n _ c o d e ,t a x _ r a t e ) V A L U E S ( ' T I P ' ,' T I PT A XC M2 ' ,' T A XL I N ES T ' , ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' T A XL I N ES T ' , ' T I P ' ,' T I PT A XC M2 ' ,' C ML I N E ' , 6 . 0 0 ,' T I PB A T C HS O U R C E ' ,1 , ' U s e r ' ,' U S D ' ,3 6 2 8 , ' C r e d i tS t a t eT a x ' ,' 1 0 A U G 2 0 1 0 ' ,' T A X ' , 1 1 1 4 5 ,1 1 7 7 5 1 , n u l l ,n u l l , 1 ,2 0 4 , ' U S S A L E S T A X 1 0 1 ' ,' S T A T E ' ,' S T A N D A R D ' , ' S T A N D A R D ' ,' S T C A 1 1 6 5 1 ' ,6 . 0 ) ; -I n s e r tR e c o r df o rC o u n t yT a x I N S E R TI N T Or a _ i n t e r f a c e _ l i n e s _ a l l ( i n t e r f a c e _ l i n e _ c o n t e x t ,i n t e r f a c e _ l i n e _ a t t r i b u t e 1 ,i n t e r f a c e _ l i n e _ a t t r i b u t e 2 , r e f e r e n c e _ l i n e _ c o n t e x t ,r e f e r e n c e _ l i n e _ a t t r i b u t e 1 ,r e f e r e n c e _ l i n e _ a t t r i b u t e 2 , L I N K _ T O _ L I N E _ C O N T E X T ,L I N K _ T O _ L I N E _ A T T R I B U T E 1 ,L I N K _ T O _ L I N E _ A T T R I B U T E 2 , a m o u n t ,b a t c h _ s o u r c e _ n a m e ,c o n v e r s i o n _ r a t e , c o n v e r s i o n _ t y p e ,c u r r e n c y _ c o d e ,c u s t _ t r x _ t y p e _ i d , d e s c r i p t i o n ,g l _ d a t e ,l i n e _ t y p e , o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d ,o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d , q u a n t i t y ,u n i t _ s e l l i n g _ p r i c e , s e t _ o f _ b o o k s _ i d ,o r g _ i d , t a x _ r e g i m e _ c o d e ,t a x ,t a x _ s t a t u s _ c o d e , t a x _ r a t e _ c o d e ,t a x _ j u r i s d i c t i o n _ c o d e ,t a x _ r a t e ) V A L U E S ( ' T I P ' ,' T I PT A XC M2 ' ,' T A XL I N EC O ' , ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' T A XL I N EC O ' , ' T I P ' ,' T I PT A XC M2 ' ,' C ML I N E ' , 2 . 0 0 ,' T I PB A T C HS O U R C E ' ,1 , ' U s e r ' ,' U S D ' ,3 6 2 8 , ' C r e d i tC o u n t yT a x ' ,' 1 0 A U G 2 0 1 0 ' ,' T A X ' , 1 1 1 4 5 ,1 1 7 7 5 1 , n u l l ,n u l l , 1 ,2 0 4 , ' U S S A L E S T A X 1 0 1 ' ,' C O U N T Y ' ,' S T A N D A R D ' , ' S T A N D A R D ' , ' C O C A S A NF R A N C I S C 1 1 7 6 0 ' ,2 . 0 ) ; -I n s e r tR e c o r df o rC i t yT a x I N S E R TI N T Or a _ i n t e r f a c e _ l i n e s _ a l l ( i n t e r f a c e _ l i n e _ c o n t e x t ,i n t e r f a c e _ l i n e _ a t t r i b u t e 1 ,i n t e r f a c e _ l i n e _ a t t r i b u t e 2 , r e f e r e n c e _ l i n e _ c o n t e x t ,r e f e r e n c e _ l i n e _ a t t r i b u t e 1 ,r e f e r e n c e _ l i n e _ a t t r i b u t e 2 , L I N K _ T O _ L I N E _ C O N T E X T ,L I N K _ T O _ L I N E _ A T T R I B U T E 1 ,L I N K _ T O _ L I N E _ A T T R I B U T E 2 , a m o u n t ,b a t c h _ s o u r c e _ n a m e ,c o n v e r s i o n _ r a t e , c o n v e r s i o n _ t y p e ,c u r r e n c y _ c o d e ,c u s t _ t r x _ t y p e _ i d , d e s c r i p t i o n ,g l _ d a t e ,l i n e _ t y p e , o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d ,o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d ,
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=dm2ahno6_84 7/14

q u a n t i t y ,u n i t _ s e l l i n g _ p r i c e , s e t _ o f _ b o o k s _ i d ,o r g _ i d , t a x _ r e g i m e _ c o d e ,t a x ,t a x _ s t a t u s _ c o d e , t a x _ r a t e _ c o d e ,t a x _ j u r i s d i c t i o n _ c o d e ,t a x _ r a t e ) V A L U E S ( ' T I P ' ,' T I PT A XC M2 ' ,' T A XL I N EC I ' , ' T I P ' ,' T I PT A XI N V O I C E2 ' ,' T A XL I N EC I ' , ' T I P ' ,' T I PT A XC M2 ' ,' C ML I N E ' , 3 . 0 0 ,' T I PB A T C HS O U R C E ' ,1 , ' U s e r ' ,' U S D ' ,3 6 2 8 , ' C r e d i tC i t yT a x ' ,' 1 0 A U G 2 0 1 0 ' ,' T A X ' , 1 1 1 4 5 ,1 1 7 7 5 1 , n u l l ,n u l l , 1 ,2 0 4 , ' U S S A L E S T A X 1 0 1 ' ,' C I T Y ' ,' S T A N D A R D ' , ' S T A N D A R D ' , ' C I C A S A NF R A N C I S C 1 1 7 6 1 ' ,3 . 0 ) ; c o m m i t ;

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 Insert Statement 1 (for LINE_TYPE = LINE) 'TIP' Value used in Insert Statement 2 (for LINE_TYPE = TAX) 'TIP'

Value used Insert Sta (for LINE_ 'TIP'

INTERFACE_LINE_CONTEXT

Identifies the Transaction Flexfield used by the interface data; this helps 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'. The combination of values in these two fields uniquely identify the transaction you are creating. No 2 rows should have the same combination of values in 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.

INTERFACE_LINE_ATTRIBUTE1 and INTERFACE_LINE_ATTRIBUTE2

'TIP TAX CM 2' and 'CM LINE'

'TIP TAX CM 2' and 'TAX LINE ST'

'TIP TAX CM CO'

LINK_TO_LINE_CONTEXT LINK_TO_LINE_ATTRIBUTE1 and LINK_TO_LINE_ATTRIBUTE2 REFERENCE_LINE_CONTEXT REFERENCE_LINE_ATRIBUTE1

Identifies the Transaction Flexfield used by the LINE record to which this TAX line is associated to, should match INTERFACE_LINE_CONTEXT for LINE_TYPE = LINE. The combination of values in these two fields uniquely identify the LINE record to which this TAX record is associated. It should match the values used in INTERFACE_LINE_ATTRIBUTE1 and INTERFACE_LINE_ATTRIBUTE2 from the record for LINE_TYPE = LINE Identifies the Transaction Flexfield of the Invoice line this credit memo line is being applied to. The combination of values in these two fields uniquely identify the record you want to apply this credit memo to. The values in these fields need to match the 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. This field contains the value of your transaction; pass in a number constant.

n/a n/a

'TIP' 'TIP TAX CM 2' and 'CM LINE'

'TIP'

'TIP TAX CM

'TIP' 'TIP TAX INVOICE 2' and 'INVOICE LINE'

'TIP' 'TIP TAX INVOICE 2' and 'TAX LINE ST'

'TIP'

'TIP TAX IN 'TAX LINE C

AMOUNT

This value should be the product of the numbers you pass in for QUANTITY * UNIT_SELLING_PRICE. -100

This value should be the product of the numbers you pass in for AMOUNT * TAX_RATE -6.00 'TIP BATCH SOURCE'

This value s product of t pass in for TAX_RATE -2.00

BATCH_SOURCE_NAME

The value you specify here identifies the transaction batch source to be used by AutoInvoice when interfacing this transaction. In Task 9, we created the Batch Source 'TIP BATCH SOURCE'. For non-functional currency transactions, this field would contain the exchange rate value. For our test case, we are creating a transaction in the functional currency = USD, so the rate is 1. Specify the conversion rate type, for our test case we will use 'User'. Indicate the currency code of the transaction, for our test case we will use 'USD'. Identifies the ID associated to the transaction type we created in Task 4 where 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.

'TIP BATCH SOURCE'

'TIP BATCH

CONVERSION_RATE

CONVERSION_TYPE CURRENCY_CODE CUST_TRX_TYPE_ID

'User' 'USD' 3628

'User' 'USD' 3628

'User' 'USD' 3628

s e l e c tc u s t _ t r x _ t y p e _ i d f r o mr a _ c u s t _ t r x _ t y p e s _ a l l w h e r en a m e=' T I PC M ' ;

DESCRIPTION

Contains a line item description.

'TIP TAX CM 2 - ITEM #1'

When transactions are created Manually, the TAX lines DESCRIPTION = null, however the RA_INTERFACE_LINES_ALL

When trans Manually, th DESCRIPTIO 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 be inserted as null, so we use 'Credit State Tax'

table will no be inserted

'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 transaction. Typically the period in which this GL_DATE value falls should be an open period. Indicates the type of line this interface data defines

'10-AUG-2010'

'10-AUG-2010'

'10-AUG-20

LINE_TYPE

'LINE' 11145 and 117751

'TAX' 11145 and 117751

'TAX' 11145 and

ORIG_SYSTEM_BILL_ADDRESS_ID Identifies the Address ID and Customer ID associated to the invoice. 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.

s e l e c tc . c u s t _ a c c t _ s i t e _ i d o r i g _ s y s t e m _ b i l l _ a d d r e s s _ i d ,b . c u s t _ a c c o u n t _ i d o r i g _ s y s t e m _ b i l l _ c u s t o m e r _ i d f r o mh z _ p a r t i e sa , h z _ c u s t _ a c c o u n t sb , h z _ c u s t _ a c c t _ s i t e s _ a l lc , h z _ c u s t _ s i t e _ u s e s _ a l ld w h e r ea . p a r t y _ n a m e=' T I PC U S T O M E R1 ' a n da . p a r t y _ i d=b . p a r t y _ i d a n dc . c u s t _ a c c o u n t _ i d=b . c u s t _ a c c o u n t _ i d a n dc . c u s t _ a c c t _ s i t e _ i d=d . c u s t _ a c c t _ s i t e _ i d a n dd . s i t e _ u s e _ c o d e=' B I L L _ T O ' ;

QUANTITY UNIT_SELLING_PRICE TERM_ID TAXABLE_FLAG Specifies the number of items. Specifies the price of each item. A credit memo has no payment terms so this is Null Indicates whether or not the transaction is taxable. IMPORTANT: To enable passing a manual tax line, this flag must be N N AMOUNT_INCLUDES_TAX_FLAG SET_OF_BOOKS_ID Indicates whether or not the amount is inclusive of taxes. Identifies the Set of Books ID associated to the Operating Unit you are 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. N 1 n/a 1 n/a 1 -1 100.00 null null null null n/a null null null n/a

s e l e c ts e t _ o f _ b o o k s _ i d f r o ma r _ s y s t e m _ p a r a m e t e r s _ a l l w h e r eo r g _ i d=& o r g _ i d ;
ORG_ID Indicates the ID of the Operating Unit against which this transaction is created 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. Identifies the Tax Regime to be used by the transaction. Identifies the TAX code. Identifies the TAX STATUS code. identifies the TAX RATE code identifies the Jurisdiction identifues the numeric tax rate 204 204 204

TAX_REGIME_CODE TAX TAX_STATUS_CODE TAX_RATE_CODE TAX_JURISDICTION_CODE TAX_RATE

n/a n/a n/a n/a n/a n/a

US-SALES-TAX-101 'STATE' 'STANDARD' 'STANDARD' 'ST-CA-11651' 6.0

US-SALES-T COUNTY'

'STANDARD

'STANDARD

'CO-CA-SAN 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: ERROR: from eBusiness Tax - return code = 2

Multiple

Please review Note 1159503.1, Autoinvoice Same as Import Error: ERROR from eBusiness Tax - return 12.0 code = 2

Autoinvoice Ignoring Manual Tax Line With Wrong Tax Code Without Any Error Message

bug 6509803 Tax Calculation errors out for some invoices, but the ZX_ERRORS_GT is not populated correctly. Also aftererroring out the Tax Calculation should continue for the next transaction.

Fixed Files/Versions: AREBTAIB.pls 120.25.12000000.5 zxifsrvctypspkgs.pls 120.27.12000000.2 zxifsrvctypspkgb.pls 120.230.12000000.12 zxifpubsrvcspubb.pls 120.275.12000000.11 Recommended Patch*: Patch 9249841 Patch 9067492

Included in Baseline 12.1

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

11/14

ERROR ORA-28115: policy with check option violation FRM-40508:ORACLE error: unable to insert record

Multiple

See Note 751126.1

ERROR: from eBusiness Tax - return code = 1

Multiple

Please review Note 1316691.1, Autoinvoice Same as 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 When Importing manual tax lines on credit memos, the tax distribution lines are not being created in Receivables. Cause Bug 8669930 & Bug 8502340 12.0 Fix Fixed Files: zxdiprodintgpkgb.pls 120.47.12000000.18 zxditaxapplipkgb.pls 120.227.12000000.54 zxditaxlndetpkgb.pls 120.82.12000000.25 zxapdefvalpkgb.pls 120.73.12000000.23 zxdiimpdocmtpkgb.pls 120.58.12000000.11 Recommended Patches*: Patch 8901069 Patch 8502340 When Importing manual tax lines on credit memos, get an error: The tax line of the credit memo does not have a link to the invoice. Bug 9980968 This is a controlled release patch you will need to contact Support for the patch password. Fixed Files: AREBTAIB.pls 120.25.12000000.40 12.1 Fix Fixed Files: zxdiprodintgpkgb.pls 120.48.12010000.13 zxapdefvalpkgb.pls 120.80.12010000.8 zxdiimpdocmtpkgb.pls 120.61.12010000.6 zxditaxapplipkgb.pls 120.260.12010000.15 zxditaxlndetpkgb.pls 120.91.12010000.7 Recommended Patches*: Patch 9337544 Patch 8502340 Fixed Files: AREBTAIB.pls 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 Tax Debug Log Shows: ZX_TDS_UTILITIES_PKG.get_tax_cache_info(-)return_status = E ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.create_detail_tax_line Incorrect return_status after calling ZX_TDS_UTILITIES_PKG.get_tax_cache_info() ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.create_detail_tax_line RETURN_STATUS = E ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.create_detail_tax_line.END ZX_PRODUCT_INTEGRATION_PKG.create_detail_tax_line(-) ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.import_trx_line_with_taxes Incorrect return_status after calling create_detail_tax_line() ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.import_trx_line_with_taxes RETURN_STATUS = E ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.import_trx_line_with_taxes.END ZX_PRODUCT_INTEGRATION_PKG.import_trx_line_with_taxes(-) ZX.PLSQL.ZX_PRODUCT_INTEGRATION_PKG.import_document_with_tax Errored out when calling import_trx_line_with_taxes(). 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 Imported Through AutoInvoice Cause In the case of Latin Tax Engine, the subscription details are automatically created when the LTE setup is completed. Due to some code issue, the same was not happening in earlier versions of R12. This is was fixed as part of Bug 6320613. If this did not happen, users manually subscribed the operating unit to the regime using the "Tax Managers" responsibility. In the case of Bug 7948225, the user incorrectly subscribed the operating unit to the regime. The Latin Tax subscription requires that the parties use "Common Configuration Owners with Party Overrides". 12.0 Fix 12.1 Fix

Check this as Same as 12.0 follows: -> Navigate to Tax Managers / Tax Regimes / Query for Regime -> Click on Update / Continue -> Please check 'Configuration for Taxes and Rules' column. -> Parties/LEs must be created with 'Common Configuration with Party Overrides'

Bug 9467888

Fixed File: Fixed File: zxdiprodintgpkgb.pls zxdiprodintgpkgb.pls 120.47.12000000.23 120.48.12010000.18 Recommended patch: Recommended Patch:

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

12/14

Patch 9467888 Manual Tax Lines are not importing Setup incomplete

Patch 9467888

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 Fixed File: Fixed File: zxdiprodintgpkgb.pls zxdiprodintgpkgb.pls 120.47.12000000.19 120.48.12010000.14 Recommended Patch Patch 9467888 Recommended Patch: Patch 9467888 Same as R12

Attempts to cancel (Credit) an invoice generated via AutoInvoice with manual tax lines returns an unexpected error and record is not saved. This occurs only if the Latin Tax Engine is in use.

Bug 8776916

This Tax Rate Percentage is invalid

As per Bug 8585391 The Tax Rate Percentage overriding is allowed only if the value of 'Allow Ad Hoc Rate' flag is 'Y' for the Tax Rate Code.

Correct Tax Rate Setup to allow adhoc rate

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