TDS Information

Hi
In my client company we have uploaded vendors masters through LSMW  at that time we did not give TDS information(TDS codes and Type) in the master record
Till now we have not uploaded vendor balances from legacy to SAP
Now my client are giving onlynvendor final balances (i.e after deduction of TDS in legacy system)
Now please suggest on below points,
1) before uploading vendor final balances we have to give TDS information (TDS codes and Type) in the vendor master record or not
2) without vendors final balances upload in the SAP they are making payments in F-53 is it correct or not?
3) while entering payments in F-53 they want to deduct TDS,  without vendor invoice upload they are making payment in F-53
    If i will give TDS information in the vendor master is there any effect while uploading vendor final balances
Please suggest me
Regards
Srini

Hi Srini,
1. In the cut over activities, you first need to upload vendor master. There are two ways it can be uploaded.
     - 1) Upload complete Vendor master even with witholding tax data and then upload Vendor balances. In this case, while uploading vendor balances, you can create a "ZZ" posting key and in that posting key you need to suppress all fields related to witholding tax. This posting key will only be used at the time of cut over and will not be used later on
     - 2) Second approach would be upload vendor master without Witholding tax data, then upload vendor balances and then upload Vendor master witholding tax data
2. Even if they are making payment without creating/clearing off liability, the entry would be Vendor -Dr. To bank A/c..cr.. The subsequent clearing of Vendor is to be done in T-Code F-44
3. You can deduct TDS at the time of Payment also.. You just need to have correct TDS Tax type and code for Payment in vendor master, but you said that balances are net of TDS, so if the payment is related to old Invoices, there is no need to deduct TDS again.. it will amount to duplication. But if they are fresh payments as advances, then use F-48 for Down payment and TDS can be deducted
You need to sequence all the activities in the system..
1. Upload vendor Master with TDS
2. Upload Vendor Legacy balances with ZZ posting Key
3. Even if Payments are made in SAP, Clear off Vendor DR. and CR. after uplaoding Vendor Legacy balances
4. If fresh payments are being made and TDS need to be deducted, then you need to update TDS info in the master (Note in this case, you can use ZZ posting key to upload vendor balances where you do not want to give effect of TDS)
Hope this helps.
Regards,
Kavita

Similar Messages

  • Tds information  in J1INQWEFILE

    Hi,
    I have posted one doc as given bellow
    Document No:1
    Expenses A/c Dr     100000
       To.Party A/c                             75074
       To.TDS Sec-194c                        2200
       To.TDS Sec-194c                           66
       To.TDS-Sec-194I                       22000
       To.TDS Sec-194I                          660   
    My problem is that we are not able to get Section Code wise  information in this particular Document in T.Code J1INQEFILE.System gives total tax amount under one section.Please advise me what should i do ? we have to devlop any report or is there any standard report?
    Please advise me ,
    Thanks in Advance.

    Hai,
    J1inqefile will provide the output based on section code only.
    Raghav

  • * Information to All

    hi all.
    SAP Tickets - What Is That?
    Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.
    The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant.
    The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants.
    The work process in support projects are given below for your reference.
    1.  The customer or the end user logs a call through any tool or by mail (RADIX).
    2.  Each one of the support team is a part of support group.
    3. Whenever a customer logs a call he /she  has to mention to which work group (by name).
    4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)
    5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin)
    6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process.
    These are the process.  In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client.
    An example:
    Tickets in SD can be considered as the problems which the end user or the employee in the company faces while working on R/3.  Tickets usually occur during the implementation or after the implementation of the project.  There can be numerous problems which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.
    To begin with, we should give "TICKET" to you for not knowing it. 
    Here is an eg of a ticket raise:
    End user is not able to 
    1. Create Sales order for a customer from a New plant, since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING). 
    He raises a ticket and the priority is set in one of the below:
    1. Low  2. Medium  3. High.
    Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.
    You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.
    Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed.  What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.
    What Is Maintaining SLA - Service Level Agreement
    What is maintaining SLA in production support?
    SLA is an abbreviation for "Service Level Agreement". It means to have guaranteed reaction or resolving times for incidents (= trouble tickets).
    For instance you could have defined the following SLA levels For example:
    Gold: Reaction time = 30 minutes, resolving time = 4 hours
    Silver: Reaction time = 4 hours, resolving time = 24 hours
    SLAs normally are part of a contract between a customer and a service provider.
    Or in details description:
    SLA are Service Level Agreements to resolve the tickets by the market. SLA means Service Level agreement. It is the service agreement between a Company and a service provider. For example an IT Organization providing support of SAP / other software / hardware has a agreement. This can be for example categorized based on criticality of the incident. High priority incident has to be resolved on 10 hours. Medium priority incident has a 3 days time to resolve etc
    SLA's are nothing but Service level agreements.
    These are defined in project preparation phase and client would have made an agreement with the company for the level of service. The SLA's are applicable in Production as well as maintanence support projects. For example: if your company follows a ticketing process(a ticket is nothing but an environment contains complete description of the problem which contains Short description, problem, customer contact details, sreen shots of the error etxc.,) and for each ticket there will be a severity for example business critical issues or problems may be treated as high or top severitie's. In those case your company or your team has to deliver the solution to the customer in agreed time limit or otherwise you might end up missing SLA's.
    SLA's has two important time specifications
    1. IPRT --- initial problem response time --- this is nothing but time taken to respond to the problem.
    2. PRT --- Problem response time -
    this is nothing but time taken to solve the issue or problem.
    Both IPRT and PRT will be different for different severitie's.  
    What Are Functional Specification in SAP?
    To speak at macro level that is at projet manager or at senior levels.  The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.
    The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the  data needed for the design and developement. 
    The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
    The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed. 
    The functional specification translates the Software Requirements template into a technical description which
    a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement  process. 
    b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
    At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
    Let me throw some light on documentation which is prepared before and in a project:
    1) Templates
    2) Heat Analysis -
    3) Fit Gap or Gap Analysis
    4) Business Process Design
    5) Business Process Model
    6) Business Change & Impact
    7) Configuration Design, which is just 5 % of Total SAP- have different names -
    8) Future Impact & Change Assessement
    9) Functional Design (Module Wise)
    10) Risk Assessement
    11) Process Metrics and Many More-- Which has impact on Business and its work flow
    Note * This documents are preapared in Vanilla SAP Standards -- Things differ from one implementation to another, and it always depends on the type of business which is opting for SAP
    Role of a mySAP Functional Consultant
    What are the differences between a functional and business consultant?
    The difference between Functional consultant and Business consultant are as follows:
    1) A funcitonal consultant is able to configure the system unlike business consultant.
    2) Functional consultant know more about business process unlike Business consultant.
    3) A business consultant will bring business process knowledge and provide it to functional consultant who in turn used this knowledge to configure the system. 
    4) Functional consultant has more configuration knolwledge then Business consultant.          *-- Rocky
    The responsibilities of a support consultant are:
    - Primarily responsible for Handling tickets and application support to the endusers
    - When an issue comes diagnose, analyse and solve the issue
    - Responsible for any enhancements
    - Writing functional specs and interacting with Abapers to develop any user exits 
    - Training the end users and preparing end user training material                            *-- Sistla 
    For those who wished to know the role of a functional consultant.  Below is one view:
    A functional consultant evaluates the demands in talking with the customer's representatives, transforms the essence into an abstract and algorithmic business model. Hence, he identifies the use cases and transforms them into logical and technical views. 
    Then the main task starts: customizing the respective business area and making sure the system reacts in the manner according to the constraints of the requested use case. 
    The consultant documents the settings and prepares proper guidelines that allow other consultants to do further changes or repairs with due efforts. 
    The consultant takes care that proper training is given to the users and that the system is usable, performing appropriately and the business flow is complete and correct. 
    During go live he assists the technical staff by testing the behaviour of the system. 
    After go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enhancements. 
    The main duty of a consultant is to transfer external know-how to the client. It is not manpower that counts but intelligence, understanding of processes, a feeling for defects and general a common sense
    Role of SAP Consultant In Testing
    1. What is the role of SD Consultant in Testing while implementing the project?
    2. What is Unit testing and Integration Testing?
    Testing : the core team members along with endusers will test whether the postings done in SAP is resulting as per the requirements of the organisation.  They will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data.
    Unit testing is refer to the module which are going to implement. SD, MM, FICO etc. there will be test script based on that testing will be performed. 
    Integration testing will be cross the modules. MM-SD-FICO for example.  Integration testing is also called SIT ( System integration testing)
    Testing mathologies and types: there are 6 types of testings:
      1. Unit Testing
      2. System Testing
      3. System Integration security Testing
      4. Performance Testing
      5. User Acceptance testing
      6. Regression Testing
    Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice.  So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.
    Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice.
    Security testing you will be testing different roles and functionalities and will check and signoff.
    Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI.  If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second.  Usually it is done using software.
    Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality.  This will be done on each phase of testing.
    User Acceptance Testing:  Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.
    We use different software during testing. Most commonly use are
    Test Director:  which is used to record requirement, preparing test plan and then recording the progress.  We will be incorporating defects that are coming during these testings using different test cases.
    Mercury Load Runner:  is used for performance testing.  This is an automatic tool.
    What does the following terms means :
    - Technical Unit Testing
    - Functional Unit Testing
    - IntegrationTesting
    - Volume Testing
    - Parallel Testing?
    Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program.  A successful test only proves the developed code works and that it performed the process as as designed.
    Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.
    IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.
    Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.
    Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.
    I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.
    What kind of testings that are carried out in testing server?
    1. Individual Testing ( Individually which we've created)
    2. Regressive Testing ( Entire Process)
    3. Integration Testing ( Along with other integrated modules)
    The 3 types of testing is as follows:-
    1. Unit testing (where an individual process relevant to a SD or MM etc is tested)
    2. Integration testing (where a process is tested that cuts across all areas of SAP).
    3. Stress testing (where lots of transactions are run to see if the system can handle the data)
    Roles and Responsibilities of End Users
    What is the Difference between Consultant & End users?
    SAP consultant role is to build the system, changes & modification/updation in currently installed SAP system for the end users.
    SAP End user only use the SAP system just to fetch some info, or to create new thing. So a end user is just using the final product which it is meant for and consultnat design the product/updation and modification.
    The roles and responsibilities of end users is working in easy access menu they will not have authorizations of using img settings if they get doubt they will send query to the implemented company and just entering day to day transactions.
    Roles and Responsibilities of End User:
    Using the software at the end or after the implementation is an End User.
    In sap HR , we do come across entire Org Management creation by an end user after the Personnel strucutre is created.  OM objects like creation of Org Unit means functional area or dpt , creation Job and Position and its occupancy is with in the limits of an enduser.  Initiallly the OM is created by sap consultant . In course of time a new department has appeared in the company of the client .. this has to be created by the enduser rather than depending up on the implementor... similarly new job and position..like this small things are always done by the enduser.
    The entire work of OM is purely depends upon the enduser.
    After from this running periodical payroll and Ensuring of the Time schedules ( Work Schedules) of each employee is done from sap easy access by an enduser and the show run of payroll everymonth is by the enduser only.  Like this lot of roles are there for an end user. 
    Whatever the problems come across during the enduser utilisation of sap ...that will reach as ticket to the support team
    What Are SAP End User Manual
    It is the same for every other modules although here I reference it mainly for SAP HR.
    1) You should understand which targeted group for the end-user training is for.  Do they have any computer background or not. 
    2) In what way they are going to make use of the manuals supplied to them during the course of training.
    Let us focus on how to prepare manuals:
    In the client side , End Users are not permanent. If they get any better job outside they will resign and go out. Even if you train them well, again the end-user team disappears after some time. That is why implementing company( Client ) expects SAP Consultants to prepare documents which are self explanatory (even to a layman in SAP) and study themselves and use the sap easy access very comfortably.
    Hence we should prepare a document which explains the following things comfortably:
    A) All the buttons and Screens we have in sap and its importance for an end-user.
    B) All the transaction codes used by end user.
    C) The STEP by STEP usage methodology with screen shots and explanatory foot notes for each Transaction code.
    D) Prepare a book a table and columns which should have the following information:
    - Sl.NO.
    - Transaction Code
    - Navigation path 
    - Use of the Code
    - Expected Result
    - Achieved Result
    - Remarks/Any Comment
    E) Highlight the common troubles during the usage of SAP by an end- user and give the solutions (ready to use)
    These problems you can come across while giving the in house training for the end-users.  You just place them at one place and publish it for their usage in future for any of their new joinees as an end-user.
    F) Every consultant is aware that the entire Organsiational Management is with end user only. Means consultant should train the end user in entire OM.
    G) We should inform the importance of info types and usage for our purposes at expert mode, PA30, PA40 etc.,
    H) Each field in the international infotypes should be explained very clearly and ensure that they are comfortable with the fields of infotypes which have been configured for their company.
    For example : info type 0001 Org Assignment insists about the three structures of the HR. We should explain each sub field like Emp Group, Emp Sub Group, Personnel Area and Sub Area and its importance and relevance to their company so as to understand while processing them from the end- user point of view . 
    When an employee is hired into the company , now the end-user in a position to understand which employee group and subgroup, Personnel Area And Sub Area etc., should allotted..
    Like this whatever comes across in SAP Easy Access should be insisted through the training of end users.
    I) Demo, exercises and solutions should be provided in the manuals.
    J) Glossary of terms and expansion of Acronyms, Abbreviations should be given.  Like this each consultant should focus on end user training and prepare the documents.
    Mini SAP System Requirement and How to Get it
    Mini SAP System Requirement
    The system Requirements are :
    General Requirements
    Operating System:
    Windows 2000 (Service Pack2  or higher);
    Windows XP (Home or Professional);
    Windows NT
    Linux
    Internet Explorer 5.01 or higher
    At least 192 MB RAM  (recommended to have 256 MB of RAM)
    At least 512 MB paging file
    At least 3.2 GB disk space (recommended to have 6 GB hard disk drive space)
    (120 MB DB software, 2.9 GB SAP data, 100 MB SAP GUI + temporary free space for the installation)
    The file  C:\WINNT\system32\drivers\etc\services (Windows 2000) or
    C:\Windows\system\32\drivers\etc\services (Windows XP)  must not include an entry for port 3600.
    A possible entry can be excluded by using the symbol '#'.
    No SAPDB must be installed on your PC.
    The hostname of the PC must not be longer than 13 characters.
    The Network must be configured for installation and
    the MS Loopback Adapter must be configured when you start the system without a network connection!
    Special Requirements for Installations on Windows XP
    In the  file C:\Windows\system\32\drivers\etc\hosts the current IP address and the host name must be defined as
    <IP address><Host name>
    Open the network connectivity definition with start->control panel->network connections for defining the network connection. Select  ->extended-> allow other users in network. Activate new configurations.
    Select remote desktop within extended configuration menu.
    Successfully Implementing SAP
    Implementing a package can be a traumatic affair for both the customer and the vendor.   Get it wrong and the vendor may get paid late or have to resort to lawyers to get paid and tarnish their reputation.   For the company the new package may not work the way they expected, be late or cost a more than budgeted for and take management will take their eye off running their business.
    Recently a client asked me what I would consider to be the five most important things one should consider before embarking on an implementation.   This isn't a simple question, although there are many factors to think about after some consideration for me the top five are way ahead of the others.
    My top five factors to consider would be:
    1. Set up a Project Board,
    2. Secure the resources,
    3. Complete the GAP Analysis,
    4. Have detailed Cut Over Plans,
    5. Train the users.
    Taking each one in turn:
    The Project Board
    The correct set up and operation of the Project Board in my view is major factor in the success failure of the project.   The Project Board will consist of the stakeholders, key users and the vendor.   The Project Board is part of the governance of the project.   The Project Board will meet regularly to ensure that the project plans are created and being executed as planned, moves from stage to stage with all the deliverables being signed off is resourced properly.
    The Resources
    Three types of resources are absolutely necessary -- end users, change team and technicians.
    Early involvement by the end users is absolutely necessary, as they will be the ones living with the system for hopefully many years to come.   They will want to feel involved in its implementation.   Buy in from the end users of the system is absolutely essential if the system is to have a long and stable life in any organisation.
    The Change Team will identify the gaps between the package and the business requirements, re-engineer some of the businesses process to cope with the package, train the users to ensure implementations is smooth as possible into the business.
    The Technical Team will prepare the systems environment for the package, apply any software fixes from the vendor, implement the software in the best way possible for the organisation set up and tune the software for the particular technical environment.
    GAP Analysis
    A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do.   For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
    In simple terms: Gap means small cracks. In SAP world.  In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
    Actual gap analysis is time consuming and it plays vital role in blue print stage.
    Cut Over Plans
    Detailed plans need to be developed for cutting over from the old system(s) to the new.   Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.
    Train Users
    Well trained users will support and defend the system on site.  Unsupportive users will continually undermine the system and eventually it will be replaced.   Therefore the more effort you put into helping the users master the system early the better.
    Explain Cutover Activities/Strategies in SAP FI.
    Cutover Activities or Master Data Uploading Strategies Depending upon the when we are going live.  As per that, you have to give the information to your core team.  If you goling live at the middle you have to upload the all P&L Account items and B/S Items.  If you going live at the financial year start, you have to only Upload the B/S Items. Activities for Golive: 
    1.   G/L Master Upload Thru BDC or LSMW (TC-Fs00 and extended one co code to another company code Fs01)
    2.   Vendor Master Upload Thru BDC Or LSMW (Will be Taken Care By MM) 
    3.   Customer Master Upload Thru BDC or LSMW (Will be Taken Care By SD) 
    4.   Asset Master Upload(Thru As90) 
    5.   Cost Element Master Upload 
    6.   Cost Center Master Upload 
    7.   Profit Center Master Upload 
    8.   G/L Balances Thru F-02 
    10. Vendor Balances thru F-43 
    11. Customer Balances thru F-22 
    12. Customer Advances thru f-29 
    13. Vendor Advances thryu F-48
    Before uploading Vendor Balances you have to take care of WHT(TDS) Information.
    Difference between the User Exit & Gap analysis.
    Both are quiet a different and has a small relation.
    User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench.   its not new functionality which we are trying to build in sap but its slight enhancement within the same code. 
    Gap analysis is start point of Realization and once blue print is finished we have to find the realization of sap system for client requirment and there will be certain gaps when compared to system fit.  Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.   *-- V. Sridhar
    What is roll out of SAP Project?
    As per dictionary, Rollout means “Inauguration or initial exhibition of a new product”. 
    As per SAP specific definition, rollout is the strategy for international SAP implementation. Rollout strategy normally include the following
    - Whether to implement SAP simultaneously (also known as big-bang) in all the countries, or 
    - Go live in sequence of phased manner
    - Or to go for the combination of both (phased manner implementation for some of the countries and big-bang for others).
    Rollout strategy  is the most important decision that a client can make during SAP implementation. Normally, steering committee decides the rollout strategy.
    ALL THE BEST

    Man, thanks a lot! I appreciate this.
    You think you could do me a favor? I listen to a lot of DCI songs (for those of you who don't know what that is, don't worry about it), anyways, DCI shows are average 0-2 mins. Could you give me the formula that you use for this so I can calculate it's

  • Vendor name not showing correctly in TDS GL line item display fbl3n

    Hi Gurus,
    I am facing an issue in regards to TDS. As you know that normally we make a cheque payment to a vendor, we issue one cheque for one vendor.
    But my client follows a slightly different practice. Suppose they have to pay an amount of 30000 to three vendor A B C equally 10000 each. They right a self cheque to the SBI bank and also send them the list of these 3 vendors who are also having their account in the same bank. They instruct the bank to take money from their  account and then credit in the respective vendors account.
    Now the transaction goes like this:
    Vendor A   10000
    Vendor B    10000
    Vendor C   10000
        To Bank                 29700
        To TDS on A              100
        To TDS on B              100
        To TDS on C              100
    Now when the user will go to FBL3N and check the TDS GL 100020196 and see the line items it should show like as per the client:
    Vendor A       100
    Vendor B       100
    Vendor C       100
    But it shows the below result:
    Vendor A   100
    Vendor A   100   ( should be vendor B)
    Vendor A   100   (should be vendor C)
    I believe that is the standard behavior of the system to show the vendor line. They do not want to change the way of their posting and their concern is if it shows like the same at the time of return filing how will know vendor wise tds.
    Now either I need to resolve this situation in FBL3N or give them a report which should give them Vendor wise TDS information for the TDS filing.
    J1INMIS report is there but it shows only the TDS and the vendor number, it does not give the vendor name. I either want a solution of this issue in FBL3N or a report which shows vendor wise TDS with vendor number and name. Please let me know if there is a solution to this issue.
    Kindly consider this very urgent.  I am attaching the relevant screenshots.
    Thanks
    Urmila

    Hi
    Unfortunately there is no report in SAP other than J1INMIS which caters to Indian reporting requirements. You can think of enhancing the same.
    Also check your enhancement for FBL3N as to why it is not working as it should with the help of your ABAP Colleagues. It is not displaying the name correctly.
    Thanks & regards
    Sanil Bhandari

  • QBSHB not appearing in BSIK - TDS amount not appearing in BSIK Table.

    Hi Gurus,
    If I enter vendor invoice through FB60, QBSHB field is appearing in all relevant tables including BSIK. But when I am using MIRO, QBSHB field in BSIK (and also in other tables) is not updating. But in accounting document I can see correct amount going to the right GL account. When I am using FB60 T code the document type used is KR. When I am using MIRO document type used is RE.
    Please help me .
    Regards
    Santosh Hegde
    Cell: +91 99893 12365
    email : [email protected]

    hello,
    I think youuse Extended withholding tax. In extended withholding tax the table WITH_ITEM is the right place to look for TDS information. MIRO is a new transaction and directly updates the extended w/tax tables whereas the fi transactions update both the with_item as well as the older fields bseg-qbshb. The bseg fields for tds are valid only for classical w/tax and are not important in case of Extended withholding tax as they would not have the exact amount as extended w/tax can have more than 1 tax type per vendor line.
    Hope this clarifies your doubts.
    regards,
    pranav.

  • BP Ledger with TDS Details

    Dear All,
    My client is looking for a BP Ledger Report with TDS information as well. The Standard SAP B1 Report only shows the value after deuducting TDS but my client requiremment is to show the breakup for the TDS dedcuted in the report. Does any have the query for this?
    Regards,
    Bharath S

    HI
    TPM13 basically provides for Subledger Cashflow and hence all entries through any CFM transaction will get reflect here. You can check this for any of CFM postings. This also gives additional details of FI Documents.
    Thanks n Rgds
    C C

  • TDS Amount in FBL1N

    Dear SAP Guru,
                               While deducting TDS thru T.code FB60, it is reflected in FBL1n like Tax amount and Tax base amount. While doing T.Code MIRO , i am not getting the Tax amount, But i am getting Tax base amount only.Client requirement is they need both the things.
    How to resolve this issues.
    Thanks & Regards
    Appan

    TDS posted from MIRO will not reflect in line item report, i have taken opinion from SAP for the same issue few days back, SAP has given the following opinion.
    *With reference to the difference in behaviour as compared to the document posted for example from MIRO which is an MM transaction and FB60 which is a FI transaction please note the following:
    The withholding tax amount that you are using i.e. Field BSEG-QBSHB is designed to fill for the classic withholding tax. And extended withholding tax information is stored exclusive in table WITH_ITEM.
    Also note that MIRO does not give the user the control in case of Classical withholding tax. It only supports Extended withholding tax. Hence it does not populate BSEG fields in case of Extended WT.
    So in MIRO, the data for extended withholding tax are saved within the table WITH_ITEM and not within the table entry BSEG-QBSHB. The latter isnot updated during the procedure. Furthermore it is not possible to select data from table WITH_ITEM
    within the transaction FBL1N in a transparent and unique way, as FBL1N only reads BSEG / BSIK / BSAK tables.
    In your line layout,you define a field BSEG-QBSHB. But actually the field of vendor/customer line item is filled with zero from FI. Thus,it shows zero in line item display*
    Please review note 363309 for detailed explanation and explains the functionality which is valid even for your release.
    So it is not possible to display withholding tax information in the line item display transactions, since this information is not
    held in the BSEG / BSIK / BSAK tables, but is instead stored in the WITH_ITEM table.
    Please convey to your client, standard SAP will not show the TDS information in line item reports, documents posted from MIRO and show the note 363309 for there easy understanding.

  • With holding tax information

    Hi Gurus,
    Can any one explain me Clearly how to execute J1INMIS.
    Thanks&Regards
    Varma

    Hi,
    Tcode J1INMIS gives you full tds information
    a) challan update status
    b)bankchallan status
    c)certificate status
    you have to enter the following parameters in tcode j1inmis
    Company Code
    Fiscal Year
    Posting Date
    Vendor
    Business Place/Section Code
    Official Withholding Tax Key
    Report selections to update internal,external challans and certificate printing.
    Regards,
    Shradha.

  • FBL1( VENDOR LEDGER REPORT)-  Withholding tax amount is not coming .

    in FBL1 ( vENDOR lEDGER rEPORT) - WITHHOLDING TAX AMOUNT IS NOT CMING IN COLUMN  QBSHB OF FBL1.
    Purchasing document number is not coming also.
    How these fields may appear in the above said report. Is any config missing ?
    Thanks in advance
    M K Agarwal
    9967029930

    TDS posted from MIRO will not reflect in line item report, i have taken opinion from SAP for the same issue few days back, SAP has given the following opinion.
    *With reference to the difference in behaviour as compared to the document posted for example from MIRO which is an MM transaction and FB60 which is a FI transaction please note the following:
    The withholding tax amount that you are using i.e. Field BSEG-QBSHB is designed to fill for the classic withholding tax. And extended withholding tax information is stored exclusive in table WITH_ITEM.
    Also note that MIRO does not give the user the control in case of Classical withholding tax. It only supports Extended withholding tax. Hence it does not populate BSEG fields in case of Extended WT.
    So in MIRO, the data for extended withholding tax are saved within the table WITH_ITEM and not within the table entry BSEG-QBSHB. The latter isnot updated during the procedure. Furthermore it is not possible to select data from table WITH_ITEM
    within the transaction FBL1N in a transparent and unique way, as FBL1N only reads BSEG / BSIK / BSAK tables.
    In your line layout,you define a field BSEG-QBSHB. But actually the field of vendor/customer line item is filled with zero from FI. Thus,it shows zero in line item display*
    Please review note 363309 for detailed explanation and explains the functionality which is valid even for your release.
    So it is not possible to display withholding tax information in the line item display transactions, since this information is not
    held in the BSEG / BSIK / BSAK tables, but is instead stored in the WITH_ITEM table.
    Please convey to your client, standard SAP will not show the TDS information in line item reports, documents posted from MIRO and refer  the note 363309.

  • Difference between form 16 &24

    hi experts,
    can any one explain me the difference between form 16 &24

    Hi,
    Form16 :- All the TDS information for an employee , Basic employee Info with the details of Gross Pay , Exemptionsu/s 10, u/s16, u/s 24 and the Chap VI-A deduction ( sec80C, Sec80D, Sec80DD) , Tax calculation challan details are been maintained this form.Thsi acts as an statutory document for your Annual retruns filing using ITR 1/2
    PC00_M40_F16
    Refer the thread realted to Form16 :-
    Error
    Form24 :- All the employees TDS details and the challan details for the Company is filed thru form27A ( file format as per NSDL, ETDS )
    Form24 Q :- The Quarterly details of the TDS and Challan filing for an company is filed using Form24Q
    (PC00_M40_F24Q)
    Challan mapping :- PC00_M40_CMAP.
    Regards
    Hemant V. Mahale
    Edited by: Hemant Mahale on Mar 6, 2009 12:44 PM
    Edited by: Hemant Mahale on Mar 23, 2009 5:36 PM

  • Golive

    Hi,
    Can anybody pls tell me what are that activities we need to perfirm during End user training,Cutover strategy & Golive
    Regards,
    Rahul

    End User Training:
    This means training the end users about running different business processes on SAP.
    Well trained users will support and defend the system on site.  Unsupportive users will continually undermine the system and eventually it will be replaced.   Therefore the more effort you put into helping the users master the system early the better.
    Cut Over Plans:Detailed plans need to be developed for cutting over from the old system(s) to the new.   Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.
    Cutover Activities or Master Data Uploading Strategies Depending upon the when we are going live.  As per that, you have to give the information to your core team.  If you goling live at the middle you have to upload the all P&L Account items and B/S Items.  If you going live at the financial year start, you have to only Upload the B/S Items.
    Cutover Activities/Strategies in SAP FI.
    1.   G/L Master Upload Thru BDC or LSMW (TC-Fs00 and extended one co code to another company code Fs01)
    2.   Vendor Master Upload Thru BDC Or LSMW (Will be Taken Care By MM) 
    3.   Customer Master Upload Thru BDC or LSMW (Will be Taken Care By SD) 
    4.   Asset Master Upload(Thru As90) 
    5.   Cost Element Master Upload 
    6.   Cost Center Master Upload 
    7.   Profit Center Master Upload 
    8.   G/L Balances Thru F-02 
    10. Vendor Balances thru F-43 
    11. Customer Balances thru F-22 
    12. Customer Advances thru f-29 
    13. Vendor Advances thryu F-48
    Before uploading Vendor Balances you have to take care of WHT(TDS) Information. 
    Go Live:
    It means cut-off from the legacy System. During this following tasks are followed:
    Production support facilities are defined, for example, checking system performance on a daily basis
    Validation of business processes and their configuration
    Follow-up training for users
    Signoffs, etc.
    Hope this helps you.
    Regards,
    Rakesh

  • TDS amount not getting updated in the table under the field QBSHB

    Dear Friends,
    The TDS amount entered while booking the vendor invoices through MIRO T-cde, is not getting updated in the table BSEG under the field QBSHB. 
    Kindly let me know the reason for the same and guide me to correct it
    TIA.
    Regards,
    Vincent

    HI Vincent,
    Bseg-QBSHB field is relavent for classic WT.
    I hope you are using the EWT.
    Hence if you post a document through MIRO it will not update
    (but if you post document FB60 it will update but wrongly).
    Reason is Miro document is posted through interface.
    Hence SAP is suggested to not refer the Bseg-QBSHB and etc., fields.
    refer only with_item table.
    Please refer the below replay from SAP
       Please refer the below note .363309
    Please review attached note 363309 for detailed explanation
    BSEG-QBSHB is designed to fill for the classic withholding tax. And
    extended withholding tax information is stored exclusive in table
    WITH_ITEM.
    You can check in table BSEG for the fields and will find that system
    do NOT update field BSEG-QBSHB.
    In your line layout,you define a field BSEG-QBSHB. But actully the field
    of vendor/customer line item is filled with zero from FI. Thus,it shows
    zero in line item display.
    And as note 363309 says,
    "Remove the field which contains the withholding tax information
    from your display variant.
    If you want to display the withholding tax information, double-click on
    the document number and subsequently choose 'Withholding tax' button."
    (BSEG-QSSKZ, BSEG-QSSHB, BSEG-QBSHB) field is not relavent for
    Extended withholding tax and not suppose to use in report FBL1N.
    It basically does not make any sense to use the withholding tax fields
    of the document line items (BSEG-QSSKZ, BSEG-QSSHB, BSEG-QBSHB) with the
    activated extended withholding tax.
    regards
    Madhu M
    Edited by: M Madhu on Jan 31, 2011 1:19 PM

  • TDS Amount on Vendor Advance Shows positive value in *QUERY* for TDS Report

    Hi Everybody,
    I have made a query for List of TDS Report with Vendor informations as required by my client. In which the value of TDS on Vendor Advance Payment appears as positive value instaead of negative value. Please suggest how to rectify.
    Thanks,
    Paul

    Dear,
    If you have cleared the advance in F-54, then this will reverse the tax amount. That could be the reason for tax amount in debit.

  • TDS for down payment is not comming in F-48

    HI,
    I am working on TDS and it is working fine in F-43 for vendor purchases. A pop is comming here for both the invoice and advance, I have removed the advance and TDS was calculating automatically.
    But when I check it in advance payment in F-48, I am unable to get the TDS pop p and no automatic calculation is done.
    I have checked the tax code and tax keys. I have checked the vendor master also every thing seems to be ok.
    Please suggest me were I should check it.
    Also please assist.
    Regards,
    Shilpa.

    Hi,
    As long as payment withohlding tax code is coming into pop up during invoice then it must have assigned to the company code.
    There could be only one reason...
    Check field status of the GL account attached to Special GL if Taxes information are optional.
    Regards,
    Chintan Joshi

  • TDS Deduction on Vendor Payment

    Hi
    While booking the invoice (through FB60) if I forget to delete the WTax Code for payment, then how can I rectify the same, so that TDS is not deducted again at the time of making payment.
    One way is to reverse the document through FB08. Is there any other way wherein I need not reverse the document.

    Hi Kapil,
    From FB02, open the particular invoice document. Double click on the vendor line item. Click on the 'Withholding Tax Data' pushbutton on top.
    The Change Withholding Tax Information screen opens. There, delete the tax codes and save the document.
    Regards,
    Mike

Maybe you are looking for