Oracle Financials for India, September 2013 Recommended Patch List Readme

Table of Contents
1. 2. Introduction ........................................................................................................................................3 Code Integration Points .......................................................................................................................4 2.1. 2.2. 2.3. 3. P2P Flows ..................................................................................................................................4 AR Flows ...................................................................................................................................4 O2C Flows .................................................................................................................................5

Statutory Changes ................................................................................................................................6 3.1. 3.2. File Validation Utility FVU 3.8 ..............................................................................................6 Service Tax Reverse Charge Settlement .................................................................................9

4. 5.

Performance Improvement ...........................................................................................................11 Bug Fixes ..........................................................................................................................................12

1. Introduction
For Oracle Applications 12.1.3 a number of very important fixes have been made to the Oracle Financials for India. Many of these fixes affect Critical Business Processes in areas of Procure to Pay Flows, Order to Cash Flows and are observed as re-occurring often in the Installed Base. Adoption of these important fixes is highly recommended, so consolidating them into a single Recommended Patch Collection has been done to facilitate this Proactive activity.

2. Code Integration Points

With the focus on stabilizing the product and enhance user experience, architectural improvements are made in the product. These changes will enhance the user experience and product stability. The code integration points will result in elimination of existing Oracle Database triggers, redundant concurrent programs and integrate OFI flows in synchronous with application flows. With the code integration points uptake there is no impact on the functionality. Code integration has been up taken in P2P and O2C flows.

2.1.

P2P Flows

At the time of PO Match or Receipt Match, India To Insert Tax Distributions is fired to copy the taxes from the PO or Receipt and insert the taxes on the Invoice as Misc lines. This concurrent will be replaced with a user interface and users have to click on the apply button to copy the taxes to invoice.

The new UI can be accessed from Tools (M) Matched Invoice Taxes UI. Triggers have also been eliminated for creation, modification and deletion of POs Requisitions. and

2.2.

AR Flows

For Standalone AR Invoice / Debit Memo and Credit Memos, OFI Taxes will be shown on the AR invoice after completion of the request India - AR Tax and Freight Defaultation successfully. Now the taxes will be saved directly to the AR distributions seamlessly.

2.3.

O2C Flows

In O2C flows triggers are being used in areas of tax computation, shipment and VAT Invoice generation, these triggers are replaced and syncretizatio happens with the base applications through code integration.

3. Statutory Changes
This section covers the details of the statutory changes announced during this period.

3.1.

File Validation Utility FVU 3.8

NSDL has introduced changes in the quarterly reporting for etds and etcs with effective from Q1 of the Financial Year 2013-14. These changes are announced through FVU 3.8. The following changes are announced by NSDL for FVU 3.8 impacting 26Q and 27 Q Change in data structure of quarterly TDS/TCS statement pertaining to FY 2013-14 onwards as below: 1. Alternate contact details like e-mail and contact no. of the deductor and responsible person may be provided. These changes have been added as new attributes in the Regime. Deductor's STD code (Alternate) Deductor 's Tel-Phone No. (Alternate) Deductor Email ID (Alternate) Responsible Person's STD Code (Alternate) Responsible Person's Tel-Phone No. (Alternate) Responsible Person's Email ID (Alternate) Account Office Identification Number (AIN) of PAO/ TO/ CDDO

2. Minor head code is to be provided in challan details. Changes have been made to the capture the Minor Head Code in the India TDS Details UI. A new lookup code has been provided and it is user extensible. 3. No details to be provided for cheque no. and section code in the challan details. All TDS payments have to be made through electronic gateway as a result there is no need to capture the same and show it in reports. 4. Section code to be provided in deductee/collectee details. As of now the section code is being shown in the challan details of the flat file. Now with this change the same will be shown in the deductee details. 5. Section 194I has been bifurcated as below: I. Select value 4IA from the section code drop down where tax has been deducted under section 194I (a) II. Select value 4IB from the section code drop down where tax has been deducted under section 194I (b) After application of the patch, the user has to execute the script b17042034.sql to replace the old section code with the new section code, for transactions created form 1st April 2013. This script can be executed in the combination of Supplier, Supplier Site and Invoice ID based on the requirement. 6. Lower/ No deduction certificate no. to be provided in the deductee details. As per the latest requirements for exceptional vendors, certificate details have to be shown against the transactions. To support this Assign Vendor India form has been modified to capture the Certificate Number, Start Date and End Date.

Tax will be computed based on the certificate validity. Remove check box has been disabled as tax is recovered based on the Certificate Start Date and End Date.

7. Introduction of value Z in the field Remarks for lower or no deduction. Applicable in case of no deduction on account of payment under section 197A (1F). Based on the nature of transactions falling under section 197A (1F), Z has to be entered as an attribute in the GDF at the transaction level.

8. Introduction of fields for quoting foreign remittance details in Form no. 27Q as below Nature of remittance Whether TDS rate of TDS is IT act (a) and DTAA (b) Unique acknowledgement of the corresponding form no 15CA (if available) This is required in case of 27Q for foreign remittances, Form 15CA details have to be shown in the returns. The details have to be entered by the users in GDF provided at the invoice distribution level. Form 15CA acknowledgement number has to be entered in the Invoice Distributions GDF after making the payment.

The values need to be entered /selected by the user manually as they can change from transaction to transaction. 9. Country to which remittance is made Country of remittance is required in case of 27Q for foreign remittance and the same will be entered by the users in the Invoice Distributions GDF.

3.2.

Service Tax Reverse Charge Settlement

The settlement process for payment to the tax authority for Service Tax Reverse Charge is given wide Notification No 28 /2012 Central Excise. As part of this notification, existing service tax credit cannot be utilized in making payment to the tax authority and only cash payment has to be made. To support the same changes have been introduced in the Settlement UI though a Check box Reverse Charge Settlement.

If this check box is checked at the time of settlement, existing credit will not be used for settlement and a separate tax authority invoice will be

generated on the tax authority directly. Once this invoice is paid and credit for this is can be availed.

4. Performance Improvement
As a part of providing better user experience, performance improvement has been made in areas of form and concurrent programs. India Local Purchase Order form Claim Cenvat on Receipts India Localization form Receipts India Localization form view accounting entries Claim Details VAT claims form India Local Sales Order form RG23D Register Entries India Localization form Service Tax Repository Review form India Service Tax Processing concurrent India - VAT Invoice Generation / Accounting program

5. Bug Fixes
Patch Number 16016037 Functionality Impact / Change Prepayment will be allowed for application on standard invoice successfully even if the status is Needs Re validation and having holds. India TDS Payment Review Report has been modified to enable the users to see data across sections. Users will be able to apply the pre payment invoice falling under single slab to a standard invoice. Now no error message will be shown if the un application is done after invoice validation. ST form will show correct tax target amount if inclusive CST taxes are there on the transaction. Item / Template Assignment form, users will be able to see only those organizations for which the user has access. India Receiving Transaction processor concurrent has been modified to update only the receipt number for which the concurrent is being submitted. Taxes will be computed correctly on the receipt if dual unit of measure is used, that is PO has one unit of measure and Receipt has another unit of measure. Bond Register will be updated correctly for Excise Cess and Excise Secondary Higher Education Cess for RMA transactions. Flexibility has been provided for to submit India Excise Invoice Generation program without entering delivery_id Sub inventory will be validated from the sub inventory given at the ship confirm. Users will not be able to ship items if the item is not classified as Excisable and if excise type of taxes are attached.

16435622 14657086

16628222 16579458 16994152

16561743

16668964 16308603 16975882 16861879