Sei sulla pagina 1di 12

REFERENCE

Tax Interfacing solution


approach for Receivables
Invoice in Financials for
India

Prepared by
Author: Krishna Surapaneni Financials for India
Support
Creation Date: 13-Feb-2010
Last Updated:
Control Number: 1
Version: 1
Copyright (C) 2010 Oracle Corporation
All Rights Reserved
Product Design and Architecture

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

TABLE OF CONTENTS

1. SCOPE .......................................................................................................................... 3
2. OVERVIEW................................................................................................................... 4
3. SOLUTION APPROACH ........................................................................................... 5
4. SUMMARY ................................................................................................................. 12

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

1. SCOPE
This paper is intended for an audience familiar with Oracle Financials for India and seeking an
insight into how to interface tax lines to receivables invoice.
This paper is functional in nature keeping in sight Oracles existing literature that has adequate
details on the technical aspect of the Oracle Financials for India, though adequate insight is given
to the table level details relevant to the topic. This is more so, in the light of the diagnostic scripts
available in metalink note # 472679.1, thus making table level details easily accessible to the
user. Thus we have tried to handle the topic from the available functionality as well as the data
perspective level.
To prevent this document from becoming too bulky, and also to maintain focus throughout the
paper, the scope of this paper is limited to the interfacing the tax lines to receivables invoice. It is
assumed that the audiences are aware of the basics of Financials for India, as only the behavior
peculiar to tax interfaces is handled in the paper.
This document is intended to be supplementary in nature and does not in any way, purport to be
a substitute for any official literature being drafted or currently published.

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

2. OVERVIEW
In Receivables, Invoices can be entered using the transactions form or alternatively data can be
interfaced to Receivables by populating the data in ra_interfaces_all table and running
Autoinvoice import concurrent program. However only invoice line information can only be
populated using this alternate approach. If any India related taxes need to be attached to these
invoice lines, additional steps need to be followed as ra_interfaces_all table does not have link to
the Oracle Financials for India tables.
This paper attempts to provide the steps to be followed for interfacing the tax lines as well for the
invoice lines imported to receivables using the alternative approach.

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

3. Solution Approach
After populating the data into ra_interface_all table, data need to be inserted into the below
mentioned Oracle Financials for India tables as well to interface the tax data:
1. JAI_AR_TRXS - Stores the header level information for the Invoice.
2. JAI_AR_TRX_LINES - Stores the line level information for the Invoice.
3. JAI_AR_TRX_TAX_LINES - Stores the tax information for the Invoice.
The above tables need to updated if Users wish to see the AR invoice and tax information for the
invoice in AR transaction localized form. Unless data is populated into the above tables, Users
will not be able to view /query the invoice in transactions localization form.
4. JAI_AR_TRX_INS_LINES_T - This the temp table which stores the tax information until they
are processed to AR Invoice distributions. After populating the data into this table, Concurrent
program India Local Concurrent for processing order lines to AR need to be run so that taxes
information will get processed to the AR Invoice distributions. It has to be noted that scope of
Oracle Financials for India is only to populate the tax lines and account codes for the taxes to
Invoice distributions. Accounting for the Invoice lines as well as taxes will get processed by
running the Create accounting program in core receivables.

Detailed description of the above tables and values to be populated in each of the columns in the
tables are explained below:

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

1. JAI_AR_TRXS Stores the header level information for the AR Invoice

Column Name
CUSTOMER_TRX_ID
ORGANIZATION_ID
LOCATION_ID
UPDATE_RG_FLAG
ONCE_COMPLETED_FLAG

Data Type
NUMBER(15,0)
NUMBER
NUMBER
VARCHAR2(1 BYTE)
VARCHAR2(1 BYTE)

Nullable
No
Yes
Yes
Yes
Yes

TOTAL_AMOUNT
NUMBER
Yes
LINE_AMOUNT
NUMBER
Yes
TAX_AMOUNT
NUMBER
Yes
TRX_NUMBER
VARCHAR2(20 BYTE) No
BATCH_SOURCE_ID
NUMBER(15,0)
Yes
CREATION_DATE
DATE
Yes
CREATED_BY
NUMBER(15,0)
Yes
LAST_UPDATE_DATE
DATE
Yes
LAST_UPDATED_BY
NUMBER(15,0)
Yes
LAST_UPDATE_LOGIN
NUMBER(15,0)
Yes
SET_OF_BOOKS_ID
NUMBER(15,0)
Yes
PRIMARY_SALESREP_ID
NUMBER(15,0)
Yes
INVOICE_CURRENCY_CODE VARCHAR2(15 BYTE) Yes
EXCHANGE_RATE_TYPE
VARCHAR2(30 BYTE) Yes
EXCHANGE_DATE
DATE
Yes
EXCHANGE_RATE
NUMBER
Yes
CREATED_FROM
VARCHAR2(30 BYTE) Yes
UPDATE_RG23D_FLAG
VARCHAR2(1 BYTE) Yes
TAX_INVOICE_NO
VARCHAR2(100 BYTE) Yes
VAT_INVOICE_NO
VARCHAR2(240 BYTE) Yes
VAT_INVOICE_DATE
DATE
Yes

Description
Customer transaction identifier
Organization identifier
Location identifier
Update RG Flag identifier
Once complete flag for transactions
Sum of the total tax amount and line amounts for the
transaction
Amount corresponding to a line.
Amount indicating the tax to be paid.
Transaction Number.
Batch source Identifier for transaction.
Standard Who column
Standard Who column
Standard Who column
Standard Who column
Standard Who column
Ledger identifier
Primary Sales representative Identifier.
Invoice Currency Code.
Exchange Rate Type.
Exchange Date.
Exchange rate.
Created from.
Update RG23D Flag Indicator.
Tax Invoice Number.
VAT invoice number.
VAT Invoice Date.

Points to be noted:
1. Even though organization_id and location_id are nullable values in the table, Unless this
information is populated, User will not be able to query the invoice and also account codes may
not get picked up for Regimes like Service tax, VAT and Excise as the account codes are defined
specific to Inventory organization and location.
2. Update_rg_flag column in the table will get populated automatically from the code if excise
taxes exist for the invoice even if it is left as null.
3. Once_completed_flag column in the table will get populated automatically from the code once
invoice is completed from Core transactions form.
4. Customer_trx_id should be the same value populated in ra_interfaces_all table and existing in
the AR tables.

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

2. JAI_AR_TRX_LINES Stores the Line level information for the AR Invoice

Column Name
CUSTOMER_TRX_LINE_ID

Data Type
NUMBER(15,0)

Nullable Description
No
Customer Transaction line identifier
Transaction identifier. Uniquely
relates a record in this table to that
CUSTOMER_TRX_ID
NUMBER
No
of the ja_in_ra_customer_trx.
LINE_NUMBER
NUMBER
Yes
Line Number
INVENTORY_ITEM_ID
NUMBER(15,0)
Yes
Inventory item identifier
DESCRIPTION
VARCHAR2(240 BYTE) Yes
Description
UNIT_CODE
VARCHAR2(3 BYTE) Yes
Unit Code
QUANTITY
NUMBER
Yes
Quantity of Inventory items taken
Unit Selling price of the Inventory
UNIT_SELLING_PRICE
NUMBER
Yes
item
TAX_CATEGORY_ID
NUMBER(15,0)
Yes
Tax category Identifier
Total Amount for the quantity taken
LINE_AMOUNT
NUMBER
Yes
for a line
Tax amount associated with the
TAX_AMOUNT
NUMBER
Yes
inventory item
Sum of amount for the tax amount
TOTAL_AMOUNT
NUMBER
Yes
and the line amount
GL_DATE
DATE
Yes
GL Date for Invoice
AUTO_INVOICE_FLAG
VARCHAR2(1 BYTE) Yes
Auto Invoice Flag
ASSESSABLE_VALUE
NUMBER
Yes
Value for calculating excise
PAYMENT_REGISTER
VARCHAR2(30 BYTE) Yes
Payment register used
Excise Invoice Number, to identify
the excise records related to this
record from the table
EXCISE_INVOICE_NO
VARCHAR2(200 BYTE) Yes
ja_in_excise_invoice
Date when the excise Invoice for
EXCISE_INVOICE_DATE
DATE
Yes
this line was created
CREATION_DATE
DATE
Yes
Standard Who column
CREATED_BY
NUMBER(15,0)
Yes
Standard Who column
LAST_UPDATE_DATE
DATE
Yes
Standard Who column
LAST_UPDATED_BY
NUMBER(15,0)
Yes
Standard Who column
LAST_UPDATE_LOGIN
NUMBER(15,0)
Yes
Standard Who column
PREPRINTED_EXCISE_INV_NO VARCHAR2(50 BYTE) Yes
Preprinted Excise Invoice Number
Identifies Excise Exempted type
EXCISE_EXEMPT_TYPE
VARCHAR2(60 BYTE) Yes
like CT2, CT3 etc.,.
EXCISE_EXEMPT_REFNO
VARCHAR2(30 BYTE) Yes
Excise Exempt reference number
EXCISE_EXEMPT_DATE
DATE
Yes
Excise Exempt reference date
AR3_FORM_NO
VARCHAR2(30 BYTE) Yes
AR3 form number
AR3_FORM_DATE
DATE
Yes
AR3 form date
Flag to indicate if the line is
VAT_EXEMPTION_FLAG
VARCHAR2(1 BYTE) Yes
exempted from VAT type of taxes
VAT_EXEMPTION_TYPE
VARCHAR2(30 BYTE) Yes
VAT exemption type
VAT_EXEMPTION_DATE
DATE
Yes
VAT exemption Date

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

VAT_EXEMPTION_REFNO

VARCHAR2(100 BYTE) Yes

VAT_ASSESSABLE_VALUE

NUMBER

SERVICE_TYPE_CODE

VARCHAR2(30 BYTE) Yes

VAT exemption refund


Assessable value to be used for
calulating VAT taxes
Service type code applicable if
service taxes are used in
transaction

VAT_REVERSAL_PRICE

NUMBER

VAT reversal price in case VAT


reversal taxes are used

Yes

Yes

Points to be Noted:
1. Customer_trx_line_id value should be same as the value existing in the AR tables.
2. Customer_trx_id should be the same value populated in ra_interfaces_all table and existing in
the AR tables.

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

3. JAI_AR_TRX_TAX_LINES Stores taxes information for the tax lines

Column Name
TAX_LINE_NO

Data Type
NUMBER(15,0)

Nullable Description
No
Line No Of the tax line
Indicates the Customer Transaction Line
CUSTOMER_TRX_LINE_ID
NUMBER(15,0)
No
Identifier
Link records in this table to that of records
LINK_TO_CUST_TRX_LINE_ID NUMBER(15,0)
No
in table JAI_AR_TRX_LINES
PRECEDENCE_1
NUMBER
Yes
Precedence Level 1
PRECEDENCE_2
NUMBER
Yes
Precedence Level 2
PRECEDENCE_3
NUMBER
Yes
Precedence Level 3
PRECEDENCE_4
NUMBER
Yes
Precedence Level 4
PRECEDENCE_5
NUMBER
Yes
Precedence Level 5
Tax identifier attached to the customer
TAX_ID
NUMBER(15,0)
No
transaction line
TAX_RATE
NUMBER
Yes
Tax Rate
QTY_RATE
NUMBER
Yes
Quantity Rate
UOM
VARCHAR2(3 BYTE) Yes
Unit of Measure
Tax amount attached to the customer
TAX_AMOUNT
NUMBER
Yes
transaction line
INVOICE_CLASS
VARCHAR2(3 BYTE) Yes
Transaction class (INV/ CM/ DM)
FUNC_TAX_AMOUNT
NUMBER
Yes
Tax amount in functional currency
Tax amount based on which the tax is
BASE_TAX_AMOUNT
NUMBER
Yes
calculated
CREATION_DATE
DATE
Yes
Standard Who column
CREATED_BY
NUMBER(15,0)
Yes
Standard Who column
LAST_UPDATE_DATE
DATE
Yes
Standard Who column
LAST_UPDATED_BY
NUMBER(15,0)
Yes
Standard Who column
LAST_UPDATE_LOGIN
NUMBER(15,0)
Yes
Standard Who column
PRECEDENCE_6
NUMBER
Yes
Precedence Level 6
PRECEDENCE_7
NUMBER
Yes
Precedence Level 7
PRECEDENCE_8
NUMBER
Yes
Precedence Level 8
PRECEDENCE_9
NUMBER
Yes
Precedence Level 9
PRECEDENCE_10
NUMBER
Yes
Precedence Level 10

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

4. JAI_AR_TRX_INS_LINES_T This is a temporary table which stores tax


related information until they are processed to AR Invoice distributions

Name

Nullable Type

PADDR

Yes

EXTENDED_AMOUNT

Yes

CUSTOMER_TRX_LINE_ID

Yes

CUSTOMER_TRX_ID
LINE_NUMBER
SET_OF_BOOKS_ID

Yes
Yes
Yes

LINK_TO_CUST_TRX_LINE_ID

Yes

LINE_TYPE

Yes

ORG_ID

Yes

UOM_CODE

Yes

VAT_TAX_ID
ACCTD_AMOUNT

Yes
Yes

AMOUNT

Yes

CUST_TRX_LINE_SALES_REP_ID Yes
GL_DATE
Yes
INSERT_UPDATE_FLAG
Yes
CREATION_DATE
No
CREATED_BY
No
LAST_UPDATE_DATE
No
LAST_UPDATED_BY
No
LAST_UPDATE_LOGIN
Yes
TAX_RATE

Yes

ERROR_FLAG

Yes

ERR_MESG

Yes

Description
Holds the Process Address. This
RAW(32)
column is not used in any logic
Tax amount in transaction
NUMBER
currency
Customer transaction identifier of
the tax record. This is unique for
NUMBER(15)
every record
Unique identifer that identifies an
NUMBER(15)
invoice
NUMBER
Tax line number of the tax record
NUMBER(15)
Ledger identifer for the tax record
Link records in this table to that of
records in table
JAI_AR_TRX_LINES
NUMBER(15)
Identifies whether this is a TAX
VARCHAR2(20) record or FREIGHT record
Operating unit identifier for the
NUMBER(15)
invoice
UOM for the item on which the
VARCHAR2(3) tax record is attached
Tax identifier of the Localization
NUMBER(15)
tax code
NUMBER
Tax amount in functional currency
Tax amount in transaction
NUMBER
currency
Sales representative identifier
NUMBER(15)
associated with the invoice
DATE
GL Date for Invoice
VARCHAR2(1) Always holds the value U
DATE
Standard Who Column
NUMBER(15)
Standard Who Column
DATE
Standard Who Column
NUMBER(15)
Standard Who Column
NUMBER(15)
Standard Who Column
The rate based on which tax
NUMBER
amount is calculated
Holds the error status of the tax
record. Possible values are Null,
P, R, D. P indicates Pending, R
Indicates Errored. Err_mesg
column indicates the error
VARCHAR2(1) message. D indicates deleted.
Holds the reason why the tax
record was not processed. The
VARCHAR2(250) Error_flag will be R for these

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

10

records

SOURCE
CODE_COMBINATION_ID

No
Yes

This Column holds the source of


the invoice, whether it is an
Autoinvoice or a manual Invoice.
Possible values are RAXTRX
(meaning autoinvoice) and
ARXTWMAI(meaning manual
VARCHAR2(30) invoice)
NUMBER(15)
Account code combination code

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

11

4. Summary
Summary of the steps to be followed are mentioned below:

1. Populate the data into the below mentioned tables in the same order:
JAI_AR_TRXS
JAI_AR_TRX_LINES
JAI_AR_TRX_TAX_LINES
JAI_AR_TRX_INS_LINES_T
2. Run the India local concurrent for processing order lines to AR concurrent program
3. Below mentioned query can be used to check if any of the tax records did not get imported or
strucked up in temp table with any error:

Select * from JAI_AR_TRX_INS_LINES_T


Where err_flag in (R, P)

Tax Interfacing solution approach for Receivables Invoice in Financials for India
White Paper Ver 1.0

12

Potrebbero piacerti anche