TDS quaterly revise returns

HI,
if any thing mistake in quaterly returns, how we revise in sap, which t code we want to use.
please reply
Regards,
Prema.d

If you did any changes in the period like J1INJV, then you have to run the rest of the cycle and run the J1INQEFILE again. This should pick up the updated values. There is nothing like Revised Return in SAP.
Ravi.

Similar Messages

EWT revised return

Hi,
Is there any mapping for filing revised return for TDS in SAP? if so where?
regards,
smriti

Hi Smriti
You can use T code J1INQEFILE for quarterly E-Return process.
Dipak

TDS Quaterly return for Foreign Payments

Hi,
For Withholding tax quarterly returns we use t.code j1inqefile, but this does not generate quarterly returns for W.Tax u/s 195.
Please advise which t.code can be used for section 195.
Thanks and regards,
Achal rajpal

Hi Rakesh,
The liability towards TDS is the amount you have deducted in INR.You have to calcuate TDS based on INR_value and pay as such.
Here you have deducted Rs.2693 and have paid Rs.2356.40.The balance[ Excess deducted ] being 336.60[2693-2356.40] should be paid to the IT dept.
Pass the following entries and close the account as under::
1st entry: Dr::TDS clearing>336.60:::Cr:IT payable>336.60.[ The clearing acct.is now balanced]
The next entry > Dr::IT payable>336.60:::Cr--->. Bank:336.60 [upon actual payment]
This resolves the problem in full.
Regards,
Ramesh.

Error in TDS Return file

Hi
We are processing the quaterly e returns for TDS. The out put generated by the system for Delhi is wrong. As per the notification from Income Tax, the code for Delhi is 09, where as the system is generating .xls file in which it is taking 30. I have updated table J_1ISTATECD and table J_1ISTATECDM despite of that it is taking value which is in vendor master.
please suggest me how to do this.
Regards
Shiv

Hi
Thanks for your prompt reply, i have checked note no. 743340, it is saying the same thing to update the table which i have already mentioned only the difference is i have maintained this table through T code SE16.
Regards
Shiv

Withholding Tax Calculation Error for Vendor Down Payment Clearing:Oct '09

Hi,
We are trying to incorporate the new Withholding Tax Structure w.e.f. 01-Oct-09.
There were 3 scenarios possible:
a. Invoice = Down Payment
b. Invoice < Down Payment
c. Invoice > Down Payment
While 1 & 2 were taken care of effectively, the third scenario did not work as expected. The scenario is as follows:
1. Down Payment (Date : 30/09/09)
Amt : Rs. 40000/-;
Withholding Tax @ 15% : Rs. 6000/- (40000 * 15%)
Surcharge @ 10% : Rs. 600/- (6000 * 10%)
Edu Cess @ 2% : Rs. 132 (Rs. 6600*2%)
Higher Edu Cess @ 1% : Rs. 66 (Rs. 6600*2%)
2. Invoice (Date : 02/09/09) - As per new TDS Rates
Amt : Rs. 50000/-
Withholding Tax @ 10% : Rs. 5000/- (50000 * 10%)
Surcharge : NIL
Edu Cess : NIL
Higher Edu Cess : NIL
3. DPC (Date : 02/09/09) - Reversal of TDS calculated in Down Payment (Step 1) above.
Issue:
While making J1INCHLN, amount is adjusted as Rs. -1000/- (hence zero) not payable.
Also, the Surcharge, Edu Cess & Higher Edu Cess are also getting reversed in DPC.
As suggested by SAP Note No. 1372734 - Handling of downpayment clearing scenarios after budget '09, the scenario does not seem to work.
Actual payable should be worked out as under:
Invoice : Rs. 50,000/-
DP : Rs. 40,000/-
Bal : Rs. 10,000/-
TDS @ 10% : Rs. 1,000/-
All TDS Challans, Certificates & Returns must reflect Rs. 1000/- in the Challan.
Require assistance.
Regards,
Kapil Tilwani

Hi Kapil,
The following needs to be taken care of -
The message controls settings as the note suggests must be set as W.
When entering the details the logic is Vendor Debit amount is Tax amount + 1
The Vendor credit line, the tax code has to be assigned with the advance amount (amount for which the challan has been created) as the tax base amount and the tax amount will be the extra liability that needs to be created.
In your example -
The tax amount will be - 2000 ( the debit at the time of downpayment clearing should have been 4000 instead of 6000)
Tax base amount - 40000 (Challan for this amount has already been made at the time of downpayment made)
The vendor Debit - 2001 (2000 + 1)
The vendor credit - 1
Note - Tax amount and base amount has to be made manually in the withholding Tax tab for the credit entry.
Please revert for any clarification.
Thanks and Regards,
Anit

Need help with formating numbers

public void returnDollars()
          double dollar;
          dollar=amountr-amount;
NumberFormat fmt = NumberFormat.getNumberInstance();
          System.out.println(fmt.fomat(dollar));
there is my code.....now lets say
amountr = 10
amount 8.5
now when i print my dollar amount i want it to show up as 1 not 1.5 or 2. So in other words format it with no decimals and not round up at the same time.
Help would be appriciated...thanks

well...after 8 hours of trying to get it working i did it.....here it is ...........I'm sure there are many ways to make it smaller.
import java.text.*;
import java.io.*;
import java.io.BufferedReader;
import java.io.InputStreamReader;
import java.io.IOException;
public class Cashier
double amount;
double amountr;
double dollar;
double amountleft;
double quaters;
double test;
double dimes;
double pennies;
public void getAmount()throws IOException
     BufferedReader console = new BufferedReader(new InputStreamReader(System.in));
          System.out.println("Please enter amount due:");
          String input = console.readLine();
     amount = Double.parseDouble(input);
System.out.println("Amount due = " + amount);
     public void recieve()throws IOException
BufferedReader console = new BufferedReader(new InputStreamReader(System.in));
          System.out.println("Please enter amount recieved :");
          String input = console.readLine();
     amountr = Double.parseDouble(input);
System.out.println("Amount recieved = " + amountr);
     public void returnDollars()throws IOException
          double check = amountr-amount;
          dollar=amountr-amount;
DecimalFormat fmt = new DecimalFormat("##");
String s = fmt.format((double)(long)dollar);
double d = Double.valueOf(s).doubleValue();
amountleft=check-d;
     System.out.println("Dollars to return " + s);
public void returnQuaters()
     quaters= amountleft/.25;
     double check = quaters;
DecimalFormat fmt = new DecimalFormat("##");
String s = fmt.format((double)(long)quaters);
double d = Double.valueOf(s).doubleValue();
fmt.setMaximumFractionDigits(2);
String dol = fmt.format(amountleft);
          //System.out.println(dol);
          double e =Double.valueOf(dol).doubleValue();
e= e-2*(.25);
amountleft=e;
     System.out.println("Quaters to return: " + s);
     public void returnDimes()
     dimes= amountleft/.1;
     double check = dimes;
DecimalFormat fmt = new DecimalFormat("##");
String s = fmt.format((double)(long)dimes);
System.out.println("Dimes to return: " + s);
double d = Double.valueOf(s).doubleValue();
fmt.setMaximumFractionDigits(2);
String dol = fmt.format(amountleft);
          double e =Double.valueOf(dol).doubleValue();
e= e-1*(.1);
fmt.setMaximumFractionDigits(2);
String dola = fmt.format(e);
          double t =Double.valueOf(dola).doubleValue();
amountleft=t;
          public void returnNickles()
     double nickles = amountleft/.05;
          double check = nickles;
DecimalFormat fmt = new DecimalFormat("##");
String s = fmt.format((double)(long)nickles);
System.out.println("Niclkles to return: " + s);
double d = Double.valueOf(s).doubleValue();
fmt.setMaximumFractionDigits(2);
String dol = fmt.format(amountleft);
          double e =Double.valueOf(dol).doubleValue();
e= e-1*(.05);
fmt.setMaximumFractionDigits(2);
String dola = fmt.format(e);
          double t =Double.valueOf(dola).doubleValue();
amountleft=t;
     public void returnPennies()
          double pennies = amountleft/.01;
DecimalFormat fmt = new DecimalFormat("##");
String s = fmt.format((double)(long)pennies);
System.out.println("Pennies to return: " + s);
     public static void main(String[] a) throws IOException
          Cashier cash = new Cashier();
          cash.getAmount();
          cash.recieve();
          cash.returnDollars();
          cash.returnQuaters();
          cash.returnDimes();
          cash.returnNickles();
          cash.returnPennies();

ONHAND QUANTITY SETUP을 확인하는 방법

제품: Applications
작성날짜 : 2006-05-30
ONHAND QUANTITY SETUP을 확인하는 방법
==============================
PURPOSE
Onhand quantity setup을 확인하는 방법
Explanation
script을 통해, 여러 setup사항들 및 onhand수량을 check할 수 있다.
1. Check Organization controls
2. Check Subinventory controls
3. Check item attributes and controls for lot, locator, serial and
revision.
4. Check onhand quantity stock records a) non lot control
b) lot controlled
5. Check that stock records agree with attribute settings including
the following:
- Check that stock has a lot number if under lot control.
- Check expiration date, lots which have expired still show in
transaction screen
- LPN containerized items
6. Show reservations for the item
7. Show overall quantities (from an internal routine called qtytree)
8. Check that cost groups are correct.
9. Check that quantities agree.
아래의 script을 onhand.sql로 생성하여 수행하시기 바랍니다.
$Header: onhand.sql 115.9 2005/05/25 $
FILE
onhand.sql
DESCRIPTION
Gives information regarding quantity values for an item within an organization,
subinventory, revision and lot to determine why the system does not find
available stock.
Quantity on hand
Reservable quantity on hand
Quantity reserved
Quantity suggested
Quantity available to transact
Quantity available to reserve
The retrieved information will be written to an O/S file called: onhand.lst
This script should be used for Release 11.5 only.
BASE
Bug 3089073, 4349223
ARGUMENTS
Organization_id
Inventory_item_id
lot_number => return over this if item is not lot controlled
revision => return over this if item is not revision controlled
subinventory_code
/*WHENEVER SQLERROR EXIT FAILURE;*/
spool onhand.lst
set linesize 125;
set pagesize 200;
set verify off;
set serveroutput on
PROMPT 1/ To check Organization controls
SELECT organization_id ORG_ID,
primary_cost_method CST_TYP,
cost_organization_id CST_ORG,
master_organization_id MAST_ORG,
default_cost_group_id DEF_CST_GRP,
project_reference_enabled PROJ_FLG,
wms_enabled_flag WMS
FROM mtl_parameters
WHERE organization_id = &&org_id;
PROMPT 2/ To check Subinventory controls
SELECT secondary_inventory_name, organization_id org_id, default_cost_group_id DEF_CST_GRP,
locator_type LOC, asset_inventory ASSET_INV
FROM mtl_secondary_inventories
where organization_id = &&org_id;
PROMPT 3/ To check item attributes
select LOT_CONTROL_CODE LOT, REVISION_QTY_CONTROL_CODE REV, LOCATION_CONTROL_CODE LOC,
SERIAL_NUMBER_CONTROL_CODE SER
from mtl_system_items_b
where organization_id= &&org_id
and inventory_item_id = &&item_id;
prompt control = 2 for on
prompt serial_number_control 1-No serial number, 2-Predefined serial number, 5-Dynamic entry at inventory receipt
prompt 6-Dynamic entry at sales order issue
PROMPT 4/ To check onhand quantity stock records a) non lot control b) lot controlled
select moqd.inventory_item_id ITEM_ID, moqd.organization_id ORG_ID,
moqd.primary_transaction_quantity PRIM_QTY, moqd.subinventory_code, moqd.revision REV,
moqd.locator_id, moqd.lot_number,
moqd.cost_group_id CST_GRP_ID, moqd.project_id, moqd.task_id, moqd.lpn_id,
moqd.CONTAINERIZED_FLAG CONT_FLG
from mtl_onhand_quantities_detail moqd
where moqd.organization_id = &&org_id
and moqd.inventory_item_id = &&item_id;
select moqd.inventory_item_id ITEM_ID, moqd.organization_id ORG_ID,
moqd.primary_transaction_quantity PRIM_QTY, moqd.subinventory_code,moqd.revision REV,
moqd.locator_id, moqd.lot_number, mln.expiration_date EXPIRE_DATE,
moqd.cost_group_id CST_GRP_ID, moqd.project_id, moqd.task_id, moqd.lpn_id,
moqd.CONTAINERIZED_FLAG CONT_FLG
from mtl_onhand_quantities_detail moqd, mtl_lot_numbers mln
where moqd.organization_id = &&org_id
and moqd.inventory_item_id = &&item_id
and moqd.inventory_item_id = mln.inventory_item_id
and moqd.organization_id = mln.organization_id
and moqd.lot_number = mln.lot_number;
PROMPT Check that stock records agree with attribute settings ie. stock has a lot
PROMPT number if under lot control. Also check expiration date, lots which have expired
PROMPT still show in transaction screen but cannot be reserved (bug 3818166) and for
PROMPT negative balances, if found apply patch 3747966.
PROMPT Also check for LPN containerised items will not show as available on forms need
PROMPT unpack the material and then try to issue out from desktop or Perform the Misc
PROMPT issue of the LPN from the Mobile (bug 4349223).
PROMPT
PROMPT 5/ Show reservations for item
select organization_id, inventory_item_id, demand_source_name, demand_source_header_id,
demand_source_line_id, primary_reservation_quantity, revision, subinventory_code,
locator_id, lot_number
from mtl_reservations
where organization_id = &&org_id
and inventory_item_id = &&item_id;
PROMPT 6/ Show overall quantities from qtytree
SELECT
x.organization_id organization_id
, x.inventory_item_id inventory_item_id
, x.revision revision
, x.lot_number lot_number
, To_date(NULL) lot_expiration_date
, x.subinventory_code subinventory_code
, sub.reservable_type reservable_type
, x.locator_id locator_id
, x.primary_quantity primary_quantity
, x.date_received date_received
, x.quantity_type quantity_type
, x.cost_group_id cost_group_id
, x.containerized containerized
FROM (
SELECT
x.organization_id organization_id
, x.inventory_item_id inventory_item_id
, NULL revision
, NULL lot_number
, x.subinventory_code subinventory_code
, x.locator_id locator_id
, SUM(x.primary_quantity) primary_quantity
, MIN(x.date_received) date_received
, x.quantity_type quantity_type
, x.cost_group_id cost_group_id
, x.containerized containerized
FROM (
-- reservations
SELECT
mr.organization_id organization_id
, mr.inventory_item_id inventory_item_id
, mr.revision revision
, mr.lot_number lot_number
, mr.subinventory_code subinventory_code
, mr.locator_id locator_id
, mr.primary_reservation_quantity
- Nvl(mr.detailed_quantity,0) primary_quantity
, To_date(NULL) date_received
, 3 quantity_type
, to_number(NULL) cost_group_id
, 0 containerized
FROM mtl_reservations mr
WHERE
Nvl(mr.supply_source_type_id, 13) = 13
AND mr.primary_reservation_quantity > Nvl(mr.detailed_quantity,0)
UNION ALL
-- onhand quantities
SELECT
moq.organization_id organization_id
, moq.inventory_item_id inventory_item_id
, moq.revision revision
, moq.lot_number lot_number
, moq.subinventory_code subinventory_code
, moq.locator_id locator_id
, decode(NULL, NULL, moq.transaction_quantity, nvl(pjm_ueff_onhand.onhand_quantity
(NULL,moq.inventory_item_id,moq.organization_id
,moq.revision,moq.subinventory_code,moq.locator_id,moq.lot_number)
,moq.transaction_quantity))
, nvl(moq.orig_date_received,
moq.date_received) date_received
, 1 quantity_type
, moq.cost_group_id cost_group_id
, decode(moq.containerized_flag,
1, 1, 0) containerized
FROM
mtl_onhand_quantities_detail moq
UNION ALL
-- pending transactions in mmtt
--changed by jcearley on 12/8/99
--added 1 to decode statement so that we make sure the
--issue qtys in mmtt are seen as negative.
--This problem arose because create_suggestions stores
--the suggested transactions in mmtt as a positive number.
-- added 5/23/00
-- if quantity is in an lpn, then it is containerized
SELECT
mmtt.organization_id organization_id
, mmtt.inventory_item_id inventory_item_id
, mmtt.revision revision
, NULL lot_number
, mmtt.subinventory_code subinventory_code
, mmtt.locator_id locator_id
, Decode(mmtt.transaction_status, 2, 1
, Decode(mmtt.transaction_action_id
, 1, -1, 2, -1, 28, -1, 3, -1, Sign(mmtt.primary_quantity))
* Abs( decode(NULL, NULL, mmtt.primary_quantity, Nvl(apps.pjm_ueff_onhand.txn_quantity(NULL,mmtt.transaction_temp_id,mmtt.lot_number,
'N',mmtt.inventory_item_id, mmtt.organization_id, mmtt.transaction_source_type_id,
mmtt.transaction_source_id, mmtt.rcv_transaction_id,
sign(mmtt.primary_quantity)
),mmtt.primary_quantity)) )
, Decode(mmtt.transaction_action_id
, 1, To_date(NULL)
, 2, To_date(NULL)
, 28, To_date(NULL)
, 3, To_date(NULL)
, Decode(Sign(mmtt.primary_quantity)
, -1, To_date(NULL)
, mmtt.transaction_date)) date_received
, Decode(mmtt.transaction_status, 2, 5, 1) quantity_type
, mmtt.cost_group_id cost_group_id
, decode(mmtt.lpn_id, NULL, 0, 1) containerized
FROM
mtl_material_transactions_temp mmtt
WHERE
mmtt.posting_flag = 'Y'
AND mmtt.subinventory_code IS NOT NULL
AND (Nvl(mmtt.transaction_status,0) <> 2 OR -- pending txns
-- only picking side of the suggested transactions are used
Nvl(mmtt.transaction_status,0) = 2 AND
mmtt.transaction_action_id IN (1,2,28,3,21,29,32,34)
-- dont look at scrap and costing txns
AND mmtt.transaction_action_id NOT IN (24,30)
UNION ALL
-- receiving side of transfers
-- added 5/23/00
-- if quantity is in an lpn, then it is containerized
SELECT
Decode(mmtt.transaction_action_id
, 3, mmtt.transfer_organization
, mmtt.organization_id) organization_id
, mmtt.inventory_item_id inventory_item_id
, mmtt.revision revision
, NULL lot_number
, mmtt.transfer_subinventory subinventory_code
, mmtt.transfer_to_location locator_id
, Abs( decode(NULL, NULL, mmtt.primary_quantity, Nvl(apps.pjm_ueff_onhand.txn_quantity(NULL,mmtt.transaction_temp_id,mmtt.lot_number,
'N',mmtt.inventory_item_id, mmtt.organization_id, mmtt.transaction_source_type_id,
mmtt.transaction_source_id, mmtt.rcv_transaction_id,
sign(mmtt.primary_quantity)
),mmtt.primary_quantity)) )
, mmtt.transaction_date date_received
, 1 quantity_type
, mmtt.transfer_cost_group_id cost_group_id
, decode(mmtt.transfer_lpn_id, NULL, 0, 1) containerized
FROM
mtl_material_transactions_temp mmtt
WHERE
mmtt.posting_flag = 'Y'
AND Nvl(mmtt.transaction_status,0) <> 2 -- pending txns only
AND mmtt.transaction_action_id IN (2,28,3)
) x
WHERE x.organization_id = &&org_id
AND x.inventory_item_id = &&item_id
GROUP BY
x.organization_id, x.inventory_item_id, x.revision
, x.subinventory_code, x.locator_id
, x.quantity_type, x.cost_group_id, x.containerized
) x
, mtl_secondary_inventories sub
WHERE
x.organization_id = sub.organization_id (+)
--AND Nvl(sub.availability_type, 1) = 1
AND x.subinventory_code = sub.secondary_inventory_name (+) ;
PROMPT Check that cost groups are correct see Bug 4222079
PROMPT 7/ To find stock values from system nb.<cr> over lot and revision if item
PROMPT is not under lot or revision control, <cr> over subinventory for all subinvs
DECLARE
L_api_return_status VARCHAR2(1);
l_qty_oh NUMBER;
l_qty_res_oh NUMBER;
l_qty_res NUMBER;
l_qty_sug NUMBER;
l_qty_att NUMBER;
l_qty_atr NUMBER;
l_msg_count NUMBER;
l_msg_data VARCHAR2(1000);
l_rev varchar2(100):=NULL;
l_lot VARCHAR2(100):=NULL;
l_loc VARCHAR2(100):=NULL;
l_lot_control BOOLEAN :=false;
l_revision_control BOOLEAN :=false;
l_lot_control_code NUMBER;
l_revision_qty_control_code NUMBER;
l_location_control_code NUMBER;
l_org_id NUMBER;
l_item_id NUMBER;
l_subinv VARCHAR2(10);
BEGIN
select LOT_CONTROL_CODE ,REVISION_QTY_CONTROL_CODE, LOCATION_CONTROL_CODE
into l_lot_control_code, l_revision_qty_control_code, l_location_control_code
from mtl_system_items_b
where organization_id= &&org_id
and inventory_item_id = &&item_id;
if l_lot_control_code = 2 then
l_lot_control :=true;
l_lot:='&lotnumber';
end if;
if l_revision_qty_control_code =2 then
l_revision_control:=true;
l_rev:='&revision';
end if;
inv_quantity_tree_grp.clear_quantity_cache;
dbms_output.put_line('Transaction Mode');
apps.INV_Quantity_Tree_PUB.Query_Quantities (
p_api_version_number => 1.0
, p_init_msg_lst => apps.fnd_api.g_false
, x_return_status => L_api_return_status
, x_msg_count => l_msg_count
, x_msg_data => l_msg_data
, p_organization_id => &&org_id
, p_inventory_item_id => &&item_id
, p_tree_mode => apps.INV_Quantity_Tree_PUB.g_transaction_mode
, p_onhand_source => NULL
, p_is_revision_control=> l_revision_control
, p_is_lot_control => l_lot_control
, p_is_serial_control => NULL
, p_revision => l_rev
, p_lot_number => l_lot
, p_subinventory_code => '&&subinv_code'
, p_locator_id => NULL
, x_qoh => l_qty_oh
, x_rqoh => l_qty_res_oh
, x_qr => l_qty_res
, x_qs => l_qty_sug
, x_att => l_qty_att
, x_atr => l_qty_atr );
dbms_output.put_line('Quantity on hand --> '||to_char(l_qty_oh));
dbms_output.put_line('Reservable quantity on hand --> '||to_char(l_qty_res_oh));
dbms_output.put_line('Quantity reserved --> '||to_char(l_qty_res));
dbms_output.put_line('Quantity suggested --> '||to_char(l_qty_sug));
dbms_output.put_line('Quantity available to transact --> '||to_char(l_qty_att));
dbms_output.put_line('Quantity available to reserve --> '||to_char(l_qty_atr));
end;
PROMPT Check that quantities agree with script 4 and 5.
Spool off;
PROMPT *** Print file onhand.lst created ***
exit
Reference Documents
Bug 4529874

Precedence: Procedure or Function

I have a package that contains function revise and procedure revise.
(this package is over a decade old)
Inside the package, some code reads:
if jobtype is not null
then
my_custom_package.revise;
end if;
Which "revise" is called?
Is it the procedure or the function?
CODE:
--Package Header
create or replace package my_custom_package as
function import_structure(salesid in number, jobtype in varchar2) return varchar2;
procedure revise;
function revise return number;
end reco_takeoff;
--Package function import_structure
function import_structure( salesid in number, structid in number,
importid in number, jobtype in varchar2,
uom in varchar2 ) return varchar2
IS
BEGIN
if jobtype is not null
then
reco_takeoff.revise;
end if;
END;
(Let me know if there is a better way to format code in these forums).
Thanks

(Let me know if there is a better way to format code in these forums).Enclose code snippets between {code} tags.
I have a package that contains function revise and procedure revise.
(this package is over a decade old)
Inside the package, some code reads:
if jobtype is not null
then
my_custom_package.revise;
end if;
Which "revise" is called?
Is it the procedure or the function?A function returns a value.
It's not the case here, so it is a procedure call.

Digital signature in form 16

Hi All,
Is there any options to display the digital signatures in employee's form 16. I have checked the hressin_f16. But, there was no digital signatures in it.
Is there anyway to do ? Please share your experiences. Thanks for your inputs in advance.
Regards,
Anil Kumar

Check note # 1168740
Symptom
It is now permitted to use Digital Signature on Form 16. Current Form 16
print program does not support this functionality.
Important Note:
This Note contains corrections to digitally sign Form 16 in Adobe output technology. It is currently applicable for SAP Release ECC 6.00 only.
Other terms
Form 16, TDS certificate, Tax return, digital signature, signature, person responsible, Form 12BA, Annexure to Form 16, HINCF160, PC00_M40_F16
Reason and Prerequisites
Supporting a business practice which is approved by legal notification
Prerequisites
SAP Note 1156084 - Sum of serial no. 18(a) & 18(b) incorrect on Form 16 PDF
Solution
How to apply the Note:
This Note requires manifold changes. These changes will be part of next HRSP (SP 31) planned for Release ECC 6.00. Alternatively, you can perform following steps to get the changes in the system for only Release ECC 6.00 and ECC 604 release:
--more at marketplace.....
Also refer to the following link:
http://www.saptechies.com/digital-signature-for-form-16/
Hope this helps!!

J1INQEFILE - Quarterly TDS Returns

Hi Experts,
When I am excuting the quaterly returns, we are not getting all the documents in the list.
Reason: Challan number (J_1IINTCHLN) is not updated in the with_item table. But already accounting document is cleared.
How to update this challan number in order to get the missing documents in the quaterly returns
Please guide
Thanks and Regards,
Ram

Thank you Praveen,
I have done everything which are mentioned in the doc.
We have done J1INCHLN - Create Remittance Challan then J1INBANK - Enter Bank Challan.
When I am taking report by using t code J1INQEFILE - Quarterly TDS Returns, I am not getting these documents in the report.
I check the with_item table, there the internal challan number is not updated.
How do I reconstruct this number to get all items in the report
Regards,
Ram

Regarding TDS E Return.

Pls Help,
Any body create logic of TDS E Return .which is quaterly basis.
Pls do the needfull.
*Assign full mark.
regards,
mahi

Hi Dear.....
Basically Cin is divided in to two types:
1. TAXINJ - Is a Routine Based that is used in the condition types. it will work on the logic what ever is there in the Routine.
2. TAXINN: - Is a condition Record based. Means we have to create condition records for each and every condition type that you are going to use in the Pricing Procedure.
Since Version 4.7 this TAXINN came into picture and start using this.
And one of the important points is since 4.6 c CIN comes a separate package. But after introduction of 4.7 Version, CIN is coming the SAP Package itself and even in the Customer Master Record also we will find the CIN Icon.
Basically 4 types of Pricing Procedures are used in CIN and are as follows:
1.JDEPOT - Depot Sales
2.JEXPOR - Export Sales
3.JFACT - Factory Sales
4.JSTKTR - Stock Transfer
Country Version India comes with four pricing procedures as follows:
JINFAC (Sales from manufacturing plants)
JINEXP (Export sales)
JINDEP (Sales from depots)
JINSTK (Stock transfers)
CIN:
IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
Maintain Excise Registrations
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
enter each of your excise registrations, specifying a four-character code for each
Excise Registration IDs
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
Activities
For each excise registration in your business create a registration ID, and state:
Which taxes the registration covers (additional excise duty, special excise duty, and cess)
Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
The maximum number of items to be printed on each excise invoice
Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
ECC Number
Specifies the organization's ECC number.
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division
Specifies the excise division in whose area the excise registration is located.
Excise Collectorate
The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming AED usage
Additional Excise duty Percentage. These are leviable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty.
Example
Additional Excise duty is leviable in case of textile products, tobacco and sugar.
Similarly for SED CESS
Number of Items in Excise Invoice
Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies
This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description
Description of the excise registers set.
Partial CENVAT Credit
Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account.
Dependencies
When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator
Excise year start month
The calendar month marking the beginning of the excise year
Use
this start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure
Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received.
Number of excise invoices to be selected
indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection
Number of days from document date for excise invoice selection.
Example
If the value of this field is 20 and today is 28-03-97. The excise
invoice selection will show the related invoices only for the
period 08-03-97 to 28-03-97.
Document type for TDS FI posting
Financial accounting document type for TDS posting.
Document type for FI posting on Utilization
Financial accounting document type for TDS posting.
Indicator for item level excise duty round off
This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice
You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods
Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account
Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type
Key representing a type of exchange rate in the system.
Use
you enter the exchange rate type to store different exchange rates.
Example
you can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts
when you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Plant Settings
In this activity, you maintain excise information relating to your plants.
Activities
For each plant:
Specify whether it is a manufacturing site or a depot.
Assign it an excise registration ID.
You can assign the same ID to more than one plant, if required.
Depot
indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
Number of goods receipt per excise invoice.
Multiple GR for one excise invoice, Single credit
Multiple GR for one excise invoice, multiple credits
Maintain Excise Groups
Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Excise Groups
In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation
Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
Activities
1. Create one excise group for each set of registers that you need to keep.
1. Assign the excise groups to plants.
2. Maintain whether this Excise group is for a depot or not.
3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to avail the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no creates' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock.
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
Excise Group
Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration.
Dependencies
In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to.
At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
GR Per Excise Invoice
Multiple GR for one excise invoice , Multiple credit
Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically
Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background.
Dependencies
If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option
RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step.
If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting.
If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR
If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo
Posting
If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
Blocked stock
Stock transport order
Consignment stock
Maintain Series Groups
Use
In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
Activities
Define excise series groups based on type of outgoing document
Assign series group to excise registration ID
If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
No account postings for CENVAT in sales cycle
No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
IF the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT
Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators
Use
In this IMG activity; you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Select Tax Calculation Procedure
Use
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
Specify the conditions in the sales order that are used for excise rates.
Specify the countervailing duty condition type used for import purchase orders.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
Use
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features
The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Activities
Customizing
Make for Logistics General, by India the settings in Customizing Basic Excise Duties Usingchoosing Taxes on Goods Movements Account Settings Determination.Condition Technique and
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data
Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities
When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for.
On the dialog box, Control Code means "chapter ID."
So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose.
5. Enter data as required.
In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination
Use
When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
Prerequisites
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate access from the SAP EasyMaintenance screen, which you can Master Data Access screen by choosing Indirect Taxes Excise Rate Maintenance.
You maintain the following types of data:
Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
Customer master data
similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
Material master data
each material is assigned a chapter ID.
Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Activities
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant.
Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Lets assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
Define Tax Code for Purchasing Documents
Use: In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
Only carry out this activity if you use condition-based excise determination.
Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
Assign Tax Code to Company Codes
Use
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types
Use
In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
For taxes on purchases, use the condition types contained in the tax procedure.
For taxes on sales, use the condition types contained in the pricing procedures.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax on Goods Movement > India > Account Determination
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
you have set up G/L accounts for each of the processing keys listed below.
Activities
Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
VS1 (basic excise duty)
VS2 (additional excise duty)
VS3 (special excise duty)
VS5 (sales tax setoff)
MWS (central sales tax)
MW3 (local sales tax)
ESA (service tax)
ESE (service tax expense)
Specify Excise Accounts per Excise Transaction
Use
In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
If you use sub transaction types, enter the accounts for each sub transaction type as well.
Activities
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example
Excise TT DC ind Account name
GRPO CR CENVAT clearing account
GRPO CR RG 23 BED account
GRPO DR CENVAT on hld account
Specify G/L Accounts per Excise Transaction
Use
In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
Excise group
Company code
Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
Defined the G/L accounts
Defined the excise groups
Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for all transactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
 1. Go to IMG Define Structure of Logistics General Material Master Configuring the Material master Screen Sequence.Data Screen for each
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is Foreign Trade: Import Data. Select the same and click on Subscreens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade Import, Excise related subscreen appears.
INDIAN TRANSACTION CODES CIN
Transaction Codes for India
Transaction
Action
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challans
J1IFR
List subcontracting challans
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
Please Reward If Really Helpful,
Thanks and Regards,
Sudarsan

Error in TDS Returns

Hi
We are processing the quaterly returns for TDS. The out put generated by the system for Delhi is wrong. As per the notification from Income Tax, the code for Delhi is 09, where as the system is not showing Delhi against the code 09. Pls suggest.
Regards
shelia

Hi,
Please go through this menu path and assign the Code for Country and Place :
Financial Accounting(New)> Financial Accounting Global Settings(New)>Tax on Sales/Purchase>
Basic Settings>Fiscal Regional Codes>Define Fiscal Regional Codes for Other Countries.
Sometimes in SM30 you may find the maintainance dialog box for the tables as mentioned by
our friends may not be defined or incomplete. Hope this path may help you.
Sadashivan

TDS return excluding WCT line items

Hi Experts,
According to my understanding TDS return in sap are taken by selecting section codes in J1INQEFILE. By using a validation it is required in my system to fill business place\section code in vendor invoice hence section code is updated in TDS wHT codes and WCT codes line items.
Please help me to understand that what setting i have to do so that section codes should not updated in WCT WHT line items so that WCT line items can be excluded in TDS return.
This is the case where TDS and WCT both are applicable in same invoice and WCT is also treated by WHT codes and WHT keys.
Please help..
Regards,
Kuldeep Dubey

Hello,
Generally I suggest clients not to do the payment of open WCT items through J1INCHLN, hence it is not picked in the quarterly returns.
The payment can be done through a G/L payment transaction like f-07.
Regards,
Sam

Quarterly TDS Return generation-Text file problem

Hi
I am working in 4.7 and doing with the TDS Quartrly return. In the text file generation, nothing is coming except some '^' s and 0s. I applied note 873149. Still the problem is not over.
Any help would be highly appreciated.
Regards

Hi
I have maintained the section codes and recipient types as well. At the time of quarterly return generation, the excel file is OK. Whereas the text file is having only 0s and ^s. I applied a note for this already. Still it is not resolved.

Quarterly return of tds

Hi,
while i am executing the quarterly return for tds through the t.code J1INQEFILE system gives a message of enter a valid withholding tax section still after giving the tds section. so can anybody suggest me for the solution also prior to J1INQEFILE what are the things to be verified ? Points will be assigned.
regards
Babu

Hi
The foll needs to be done:
- Create Remittance Challan (J1INCHLN): U can do for selected vendors, for selected TDS Section, for particular posting dates, TDS remittance entry happens here. Ensure U configure necessary settings for Challan Number (Number range etc)
- Enter Bank Challan (J1INBANK): Whatever internal challan number generated in above step is mapped to the Physical Bank Challan number
- Print Certificate (J1INCERT): Self-explanatory (U can print for selected Challans, vendors, dates)
- Quarterlt TDS Returns (J1INQEFILE): Generate File for returns
Regards
Srini

TDS quaterly revise returns

Similar Messages

Maybe you are looking for