Activate tax reporting date (VAT due date) Spain

Dear all,
My Spanish customer should start using electronic VAT book, Modelo 340. If I understood correct VAT due date (activate tax reporting date) is a prerequisite for this? If I activate this functionality in their system, what affect will this have except a new field?
Is it possible to do this during a year or should it be done in the beginning of a new year, from 1st of January? Does it matter?
What affect will it have on already existing documents?
If they start to use electronic VAT book, do they not need to use the ordinary Tax report, transaction S_ALR_87100833, then and use only this instead?
Please help me to understand how to tell the customer of how this will affect them.
BR L

Hi Paul,
I have already red these notes but don´t think that my questions are answered by these. Escpecially the question if ordinary tax report, program RFUMSV00 (transaction S_ALR_87100833) are replaced by Modelo 340, is not answered.
Could you please help?
BR L

Similar Messages

  • Query on fetching the no.of days between Invoice date and due date in rtf template embedded BI Publisher Report

    Hi Experts,
    We have a requirement to fetch the value of 'No of days' between Invoice date and due date (Two variable date fields on the template) in an Analysis.
    Please let me know the procedure of how to achieve the same.
    Regards,
    Rev

    it's good for ideas but implementation a bit different
    Oracle Business Intelligence Publisher Report Designer's Guide
    This function provides a method to get the difference between two dates in the given locale. The dates need to be in "yyyy-MM-dd" format. This function supports only the Gregorian calendar. The syntax is as follows:
    <?xdoxslt:date_diff(‘format’, ‘YYYY-MM-DD’, ‘YYYY-MM-DD’, $_XDOLOCALE, $_XDOTIMEZONE)?>
    where
    format is the time value for which the difference is to be calculated
    Example:
    <?xdoxslt:date_diff(‘d’, ‘2006-04-08’, ‘2006-04-01’, $_XDOLOCALE, ‘America/Los_Angeles’)?>
    returns
    -7

  • Post date and due date

    Hi all,
    can any  tell me what you mean by 'posting date' and 'net due date' and' clearing date'?
    what is the difference between them?
    Table is-BSID
    BUDAT-posting date
    ZFBDT-Baseline date for due date calculation
    AUGDT-clearing date.
    thank u
    sunny.

    BUDAT-posting date
    -> to determine the book-period (bkpf-monat)
    ZFBDT-Baseline date for due date calculation
    -> determine date when an obligation becomes due
    due date = zfbdt + bsik-zbd1t (or ZBD2t or ZBD3t)
    AUGDT-clearing date
    -> date when open-item becomes a cleared item
    by payment or reversal or...
    A.

  • Posting Date, Document Date and Due Date as same

    Hi All
    I would like to make Posing date , Document Date and Due date as same
    The movement i enter Posting date it should automatically carry the same value to Due date and Document date field . How can i make it
    Regards
    Rashid

    Dear Gordon
    Thanks, it is working for Marketing documents,
    I would like to have the same for JE and JV
    Regards
    Rashid

  • Baseline Date for Due Date Calculation required for S/L indicators

    Hello,
    Iu2019m facing the following problem
    Iu2019m trying to insert an invoice (using a customer master record) but the system blocks me because the field ZFBDT (Baseline Date for Due Date Calculation) is a Required entry.
    The strange thing is  that if I use a S/L indicators the field is mandatory, if not the date may be defaulted.
    I checked in OB41 but there are non differences between Special PK and normal PK.
    Any ideas?
    Thanks in advance
    Alberto

    Dear Alberto,
    the field "Due On (BSEG-ZFBDT)" cannot be controlled with field status.
    It is controlled by field attribute of screen painter (Tcd: SE51).  If
    you look at element attribute for "Due On" field, a flag for required
    entry is activated.  In this case, field status has no control over
    the field.
    As of release 3.1G, field BSEG-ZFBDT is hardcoded in most FI screens
    to be mandatory and cannot be influenced by any field status
    changes. This situation is only valid when posting with special G/L
    indicator (ie PK 29/39).
    SAP development team has determined that this is a critical field.  The
    reason behind this is that this special GL screen and the data entered
    here are very important to many other programs. This data affects
    liabilities and receivables where due date is necessary almost
    everytime. Thus, we changed this field in this screen in order to
    prevent problems in many other areas. The reason is explained further
    in note 95079.
    I hope this helps You.
    mauri

  • Ageing Report on posting date and due date

    Hi
    I want to get customer ageing report on the basis of posting date (bill date) as well as due date (30days after posting date).
    Please let me know how to get two reports.

    Hi,
       check with this reports.
       s_alr_87012178 and s_alr_87012168
    regards,
    Radhika.

  • Include Document Date & Doc Due Date in SAP B1 Aging Details Report

    We are not able to view the actual document date and document due date from the Aging details report, it should be an essential information that should be show in the aging report. It make no sense that user still have to manually drill into each document to just read the document date/ due date for their aging analysis!!!
    Try to imaging that how important this information to a business, for instance, to age the invoice which due for 1 - 30 days, the document date which due for 1 days is categorise into 1-30days aged, the documents due for 30days also categorise into 1-30days aged, however it bring the different meanings to user and user need these information to take the action decision! How useful for an aging report which could not equip user with these basic information to provide user with efficiency to make effective decision???
    I think it is necessary to incorporate this level of details to the SAP B1 Aging Report.

    Hi Theerawat,
    You may check these threads first:
    Document Date
    Posting / Due / Document date trouble
    Re: Posting Date
    Re: Difference between posting & system date in Inventory Audit Report
    Thanks,
    Gordon

  • Interest Calculation on posting date and due date

    Hi
    I want vendor interest calculation on due date as well as posting date. Let me know how to get it. According to me only its possible on the basis of one date only.

    HEllo!
    In the report RFINTITAR, you use the interest indicator customizing:                                                                               
    IMG   > Prepare Item Interest Calculation   > Ref. Date                                                                               
    (table V_T056UX)   >  field Ref.                                                                               
    (FI Item Interest Calculation: Reference Date)                                                                               
    You have the possibility to define what You need to be considered as 
    incoming payment due date, choosing between:                                                                               
    1 Value Date (or Baseline Date for Net Payment)                      
    2 Document Date                                                      
    3 Posting Date                                                       
    4 Payment Baseline Date                                                                               
    As you can use one interest indicator per customer/vendor you can use only of the dates is used. But, in this
    program you can use the BADI FI_INT_CUS01. Please, check if you can meet your business requirements using the methods
    of the BADI.
    REgards,
    REnan

  • Calendar date & net due date (FI) PAYMENT TERMS - OBB8 Vendor Invoice

    I read many posts on SDN forum about the topic.
    Anyway, I didn't find a simple solution for that.
    My aim is is to calculate a net due date based on working days.
    So, If I've got a 30 days document days payment term  ("Deafult for baseline date" = Document date ; Additional Months = '2'), a Vendor Invoice (document date = 12.05.2011), by standard net due date will be 12.06.2011.
    FROM 12.05.2011 to 12.06.2011 =
    32 CALENDAR  DAYS         
    22 WORKDAYS (32 minus  10 holyday - 2 weekends)
    WORKDAYS PAYMENT TERMS  Within 30 workdays Due net
    Vendor Invoice  document date = 12.05.2011
    plus   30 workdays   =  DUE DATE  22.06.2011  (and not 12.06.2011)
    Can I obtain that with a standard functionality?
    Edited by: Roberto Buono on Jul 1, 2011 2:29 PM

    Hi,
    Sadly this is not available as standard.  As per your need the Net due date should be worked out by using a factory calendar; but what this does is it delinks the direct correlation between the number of days in the payment terms with the difference between the due date and baseline date.  I hope you are aware that Net Due date is not stored but is a variable calculated during run time in reports.
    There are four things you can try:
    1.  The simplest to do is: As the number of weekends are fixed; and if the intention is to give a 30 working day term, then add on the number of weekends and make the payment term effectively for say 40 days.  There will be marginal variations over what you want. Best part here is that config remains standard.
    2. All the receivable reports will use a function module (usually the same one) to calculate the net due date; enhance the FM and make it consider a factory calendar for calculating due date.
    3. Enhance the accounting interface, and in runtime; modify the days that are coming from the payment term; based on a factory calendar, and update the accounting document. This delinks the days mentioned in the payment term and the accounting document and may not be palatable.
    4. Enhance the accounting interface, and in runtime; calculate the due date and update the baseline date with it and make the payment term as "Immediate" yielding the desired due date. Not very elegant.  Alternatively add to the baseline date days equivalent to holidays and weekends and keep the days from payment terms constant and update the accounting document. Better...
    All four options have somes pros and cons.  I do not see any other means of acheiving what you want.  Maybe you could restrict users to a custom receivables/due date/ageing report which delivers what you want and lock the standard reports.
    Cheers..

  • AR - New estimated payment date after due date

    Dear friends,
    In the event the Client is not paying within the expected due date that was calculated as "Net Due Date", we normally give the Client a grace period, and the need is to record this new estimated payment date in a date field, that the SAP user will manually introduce. The Net Due Date must not be affected as in case of having debt interests, they will be calculated on that basis. But I can not find a suitable way to implement it.
    Regards,
    Érika Iranzo
    (PS: Extra information: We calculate the "Net Due Date" (FAEDT) of the our clients and vendor's invoices from the "Baseline Date for payment" (ZFBDT) plus the highest number of days within the terms of payment "Cash discount days 1" (ZBD1T). So that the due date is calculated as FAEDT = ZFBDT + ZBD1T. Additionally we also consider a region-specific calendar)
    Edited by: EIranzo on May 14, 2009 10:14 AM

    I found the field Grace Days RFOPS-TOLER that seems to be useful for my purpose, does any one know how can I make it visible when editing a document?
    Thanks,
    EIranzo

  • Invoice Date, Create Date, and Due Date

    I have a customer who is entering invoices normally like any customer would.  They will have a few that will sit on someone's desk for a couple of days before it gets entered into the system.  As an example the invoice date is 2/6/2015.  The created one date is 2/13/2015.  The due date is 3/15/2015.  The terms for the supplier are 1/10 net 30 but the system appears to be using the created on date to drive the terms not the invoice date.
    Is this the system behavior?  Have I gotten a configuration set up incorrectly?

    Hello Schneck,
    Kindly find the below image steps, of configuration the "Supplier Payment Terms calculated based on Invoice Date"
    Best Regards,
    Vignesh Ravichandran.

  • [2007A] - [8.81] Aging report with passed due date invoices in 120+ column

    Hello,
    My database contains invoices due in october 2010.
    When I run the aging report, the amount of the invoice is not in column 0-30 but in column 120+
    When I run the dunning wizard, these invoice are not included.
    i tried to look all the parameter without success. Any idea why I have these invoice in this column ? Please let me know if you need more information to understand my issue.
    I also tried to run the report in 8.81, and teh problem remain the same
    Thank you for you help
    Sébastien

    Gordon,
    OK you're right, I didn't read well this report, and I was confused with the fact that these invoices were not in the dunning wizard result.
    So yes, the aging report is correct, but my issue was the dunning wizard, and I realize these invoices have a dunning level in the installment higher than the max dunning level of my dunning terms.
    So thank you for your answer, it lead me to look at the real problem!
    Sébastien

  • Need india based tax reports of VAT,Excise duty, etc seperately

    Hi All,
    I need India based reports like RG1, Input tax in the given time, output tax in the given time.

    Hi Nagaraju...
    You can try this one....Basicaly this report give you all the details regarding your purchase and all that...
    *Declare @DateFrom Datetime*
    *Declare @DateTo Datetime*
    *set @DateFrom = '20101001'*
    *set @DateTo = '20111005'*
    *SELECT T20.Cardcode,T20.CardName, T11.[TaxId11], T11.[AddrType], T20.[Address], T20.[BillToDef] INTO #TIN FROM OCRD T20  INNER JOIN CRD7 T11 ON T20.CardCode = T11.CardCode WHERE T11.Address IS NULL OR T11.Address = '' AND T11.AddrType='S' AND T20.Cardtype='S'*
    *Select *,*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(CST / (Basic + BED + SAD + ECess + HCess),2) = .02 THEN CST*
          *ELSE NULL*
    *END 'CST2%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(CST / (Basic + BED + SAD + ECess + HCess),2) = .03 THEN CST*
          *ELSE NULL*
    *END 'CST3%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(CST / (Basic + BED + SAD + ECess + HCess),2) = .04 THEN CST*
          *ELSE NULL*
    *END 'CST4%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(VAT / (Basic + BED + SAD + ECess + HCess),2) = .04 THEN VAT*
          *ELSE NULL*
    *END 'VAT4%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(VAT / (Basic + BED + SAD + ECess + HCess),2) = .125 THEN VAT*
          *ELSE NULL*
    *END 'VAT12.5%',*
    *CASE*
          *WHEN Basic <> 0 AND ROUND(BED / Basic ,2) = .08 THEN BED*
          *ELSE NULL*
    *END 'BED8%',*
    *CASE*
          *WHEN Basic <> 0 AND ROUND(BED / Basic ,2) = .10 THEN BED*
          *ELSE NULL*
    *END 'BED10%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(VAT / (Basic + BED + SAD + ECess + HCess),2) = .135 THEN VAT*
          *ELSE NULL*
    *END 'VAT13.5%'*
    *FROM*
    *SELECT DISTINCT*
    *(Select CompnyName from OADM) Company,*
    *T0.DocNum AS 'Invoice / Bill No.',*
    *T0.DocDate as ' Invoice / Bill Date',*
    *T0.CardName as 'Seller Name',*
    *(Convert(varchar,T6.Block) + ', '+Convert(Varchar,T6.Address)+', '+Convert(Varchar,T6.City)+', '+Convert(Varchar,T6.Zipcode)+' '+Convert(Varchar,T6.Country)) 'Seller Address',*
    *T7.Name 'State',*
    *SUM( T1.LineTotal )  as 'Basic' ,*
    *SUM(T1.[VatSum])   as 'TotalTax',*
    *SUM( T1.LineTotal +T1.[VatSum]) as 'InclTax',* 
    *T0.[TotalExpns] 'Freight Charge',*
    *T1.[TaxCode],*
    *T0.NumAtCard 'Vendor Ref. No',*
    *T5.DocNum as 'P.O/Memo No',*
    *T5.DocDate as 'P.O/Memo Date' ,*
    *T8.[SeriesName] 'Purpose',*
    *T17.Taxid11'Tin No',*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=-90 and PCH4.docentry=T0.Docentry  )BED,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=-60 and PCH4.docentry=T0.Docentry )ECess,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=10 and PCH4.docentry=T0.Docentry )SAD,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=1 and PCH4.docentry=T0.Docentry )VAT,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=4 and PCH4.docentry=T0.Docentry )CST,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=5 and PCH4.docentry=T0.Docentry )ServiceTax,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=6 and PCH4.docentry=T0.Docentry )ECessForService,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=7 and PCH4.docentry=T0.Docentry )HCess,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=8 and PCH4.docentry=T0.Docentry )Surcharge,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=25 and PCH4.docentry=T0.Docentry)Freight,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=15 and PCH4.docentry=T0.Docentry )ADC,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=16 and PCH4.docentry=T0.Docentry )CustomeECess,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=12 and PCH4.docentry=T0.Docentry )CVD,*
    *(Select distinct isnull(Sum(PCH4.taxsum),0) from PCH4 where PCH4.statype=22 and PCH4.docentry=T0.Docentry )CustomHECess*
    *FROM  OPCH  T0*
    *INNER JOIN PCH1 T1 ON T0.DocEntry = T1.DocEntry*
    *INNER JOIN PCH12  T3 ON T3.DocEntry = T0.DocEntry*
    *LEFT OUTER JOIN PDN1 T4 ON T4.TrgetEntry = T0.DocEntry*
    *LEFT OUTER JOIN OPOR T5 ON T5.DocEntry = T4.BaseEntry*
    *INNER JOIN OCRD T6 ON T0.Cardcode= T6.Cardcode*
    *Left Outer JOIN OCST T7 ON T7.Code =T3.State AND T7.Country=T6.Country*
    *INNER JOIN NNM1 T8 ON T8.Series = T0.Series*
    *LEFT OUTER JOIN #TIN T17 ON T0.CardCode=T17.Cardcode*
    *INNER JOIN PCH4 T13 ON T0.DocEntry=T13.DocEntry*
    *WHERE*
    *     T0.DocDate >= @DateFrom  AND  T0.DocDate <= @DateTo*
    *     AND T13.StaType=1     *
    *GROUP BY*
    *T0.DocEntry,*
    *T0.DocNum,*
    *T0.DocDate,*
    *T0.CardName,*
    *(Convert(varchar,T6.Block) + ', '+Convert(Varchar,T6.Address)+', '+Convert(Varchar,T6.City)+', '+Convert(Varchar,T6.Zipcode)+' '+Convert(Varchar,T6.Country)),*
    *T7.Name ,*
    *T1.[TaxCode],*
    *T0.NumAtCard,*
    *T5.DocNum,*
    *T5.DocDate,*
    *T8.[SeriesName],*
    *T17.Taxid11,*
    *T0.[TotalExpns]*
    *)#Purchase*
    *UNION ALL*
    *Select *,*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(CST / (Basic + BED + SAD + ECess + HCess),2) = .02 THEN CST*
          *ELSE NULL*
    *END 'CST2%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(CST / (Basic + BED + SAD + ECess + HCess),2) = .03 THEN CST*
          *ELSE NULL*
    *END 'CST3%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(CST / (Basic + BED + SAD + ECess + HCess),2) = .04 THEN CST*
          *ELSE NULL*
    *END 'CST4%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(VAT / (Basic + BED + SAD + ECess + HCess),2) = .04 THEN VAT*
          *ELSE NULL*
    *END 'VAT4%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(VAT / (Basic + BED + SAD + ECess + HCess),2) = .125 THEN VAT*
          *ELSE NULL*
    *END 'VAT12.5%',*
    *CASE*
          *WHEN Basic <> 0 AND ROUND(BED / Basic ,2) = .08 THEN BED*
          *ELSE NULL*
    *END 'BED8%',*
    *CASE*
          *WHEN Basic <> 0 AND ROUND(BED / Basic ,2) = .10 THEN BED*
          *ELSE NULL*
    *END 'BED10%',*
    *CASE*
          *WHEN (Basic + BED + SAD + ECess + HCess) <> 0 AND ROUND(VAT / (Basic + BED + SAD + ECess + HCess),2) = .135 THEN VAT*
          *ELSE NULL*
    *END 'VAT13.5%'*
    *FROM*
    *SELECT DISTINCT*
    *(Select CompnyName from OADM) Company,*
    *T0.DocNum AS 'Invoice / Bill No.',*
    *T0.DocDate as ' Invoice / Bill Date',*
    *T0.CardName as 'Seller Name',*
    *(Convert(varchar,T6.Block) + ', '+Convert(Varchar,T6.Address)+', '+Convert(Varchar,T6.City)+', '+Convert(Varchar,T6.Zipcode)+' '+Convert(Varchar,T6.Country)) 'Seller Address',*
    *T7.Name 'State',*
    *SUM( T1.LineTotal ) * -1 as 'Basic' ,*
    *SUM(T1.[VatSum]) * -1  as 'TotalTax',*
    *SUM( T1.LineTotal +T1.[VatSum]) * -1 as 'InclTax',* 
    *T0.[TotalExpns] * -1 'Freight Charge',*
    *T1.[TaxCode],*
    *T0.NumAtCard 'Vendor Ref. No',*
    *T1.Baseref as 'P.O/Memo No',*
    *T0.DocDate as 'P.O/Memo Date' ,*
    *T8.[SeriesName] 'Purpose',*
    *T17.Taxid11'Tin No',*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=-90 and RPC4.docentry=T0.Docentry  )* -1 BED,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=-60 and RPC4.docentry=T0.Docentry )* -1 ECess,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=10 and RPC4.docentry=T0.Docentry ) * -1 SAD,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=1 and RPC4.docentry=T0.Docentry ) * -1 VAT,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=4 and RPC4.docentry=T0.Docentry ) * -1 CST,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=5 and RPC4.docentry=T0.Docentry ) * -1 ServiceTax,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=6 and RPC4.docentry=T0.Docentry ) * -1 ECessForService,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=7 and RPC4.docentry=T0.Docentry ) * -1 HCess,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=8 and RPC4.docentry=T0.Docentry ) * -1 Surcharge,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=25 and RPC4.docentry=T0.Docentry) * -1 Freight,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=15 and RPC4.docentry=T0.Docentry ) * -1 ADC,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=16 and RPC4.docentry=T0.Docentry ) * -1 CustomeECess,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=12 and RPC4.docentry=T0.Docentry )* -1 CVD,*
    *(Select distinct isnull(Sum(RPC4.taxsum),0) from RPC4 where RPC4.statype=22 and RPC4.docentry=T0.Docentry )* -1 CustomHECess*
    *FROM  ORPC  T0*
    *INNER JOIN RPC1 T1 ON T0.DocEntry = T1.DocEntry*
    *INNER JOIN RPC12  T3 ON T3.DocEntry = T0.DocEntry*
    *INNER JOIN OCRD T6 ON T0.Cardcode= T6.Cardcode*
    *Left Outer JOIN OCST T7 ON T7.Code =T3.State AND T7.Country=T6.Country*
    *INNER JOIN NNM1 T8 ON T8.Series = T0.Series*
    *LEFT OUTER JOIN #TIN T17 ON T0.CardCode=T17.Cardcode*
    *INNER JOIN RPC4 T13 ON T0.DocEntry=T13.DocEntry*
    *WHERE*
    *     T0.DocDate >= @DateFrom  AND  T0.DocDate <= @DateTo*
    *     AND T13.StaType=1     *
    *GROUP BY*
    *T0.DocEntry,*
    *T0.DocNum,*
    *T0.DocDate,*
    *T0.CardName,*
    *(Convert(varchar,T6.Block) + ', '+Convert(Varchar,T6.Address)+', '+Convert(Varchar,T6.City)+', '+Convert(Varchar,T6.Zipcode)+' '+Convert(Varchar,T6.Country)),*
    *T7.Name ,*
    *T1.[TaxCode],*
    *T0.NumAtCard,*
    *T1.baseref,*
    *T8.[SeriesName],*
    *T17.Taxid11,*
    *T0.[TotalExpns]*
    *)#MEMO*
    *DROP TABLE #TIN*
    you can thet the table name for A/R Sales and get the salres report too for the same.
    Edited by: itskumaramit on Mar 19, 2011 3:43 AM

  • Issue In posting date and Due Date

    Hello All,
    my client is creating a GRPO and manually changing the Posting, And doc date. Then by using Copy to utility he is creating A/P Invoices
    There system automatically shows the Posting date, Document Date as of current date(That is what system behavior is ). But now he wants that system should pick all his dates from Base doc i.e GRPO
    So i want to know that is this possible through some query or FMS
    if yes then please suggest me for the same
    Regards,
    Bhushan

    Hi,
    I don't have $38.10.number in my query. Where did you get this field?
    please follow below steps:
    1. Run above query in generator. Sure it gives an error message and ignore this message.
    2. save it under query manager
    3. Assign this FMS at AP invoice posting date and set auto refresh when customer vendor refer is changed.
    Thanks & Regards,
    Nagarajan

  • Due Date Analysis in Report Painter

    Hi:
    I have a query regarding Report painter FKI1 to FKI6 for Vendor aging analysis. Aging reports build from report enable user to analyze all vendors invoices which are overdue by N of days you specify for every column e.g all invoices overdue btw 0-30, 30-60 and so on but client is requiring an aging report for AP & AR which shows how old an invoice is, our baseline date is document date for all payment terms. e.g we have four columns in report 0-30,30-60,60-90 and >120. If an invoice was created with a document date 25.12.2014 which though not due should appear in 0-30 days. I need to know if its possible within report painter to have such or i will have to go for ABAP.
    Thanks

    Hello Atif,
      Your requirement can be fulfilled by report painter
    1- build a form with structure one axis with key figure
    2- create required N days columns
    3- use characteristic (Due date analysis with value =1) for analysis of line items due.
    4- use characteristic (Days for net due date ) with value from/ to N days.
    5- define a report with desired characteristics ( vendor, document number ....)
    Regarding to you example
    define column 0-30 as a sum formula of the following 2 columns
    a column "0-30 due" with characteristics
    (Due date analysis with value = 1) and
    (Days for net due date with value from 0 to 30)
    define another one "not due" with characteristics
    (Due date analysis with value = 2) and
    (Days for net due date with value from 0 to 99999)
    for more information you can check the following standard reports delivered by SAP:
    AP/ FKI0 >> report 0SAPDUEAN-01 Due Date Analysis for Open Items
    AR/ FDI0 >> report 0SAPDUEAN-01 Due Date Analysis for Open Items
    Regards,
    Ibrahim

Maybe you are looking for

  • Dreamweaver wont start

    Hi I am not a happy bunny I have spent most of the day installing CS6 and yet it still does not load. I deleted cs5 installed cs6, nothing so I uninstalled CS6 and got the suite cleaner as I thought some old root files from cs5 may be causing a confl

  • Scripting: what can be done, what can't...

    Hello all, I have recently started the process of asking for InDesign Server. Before I complete this process, I would like to know whether Scripting for InDesign is the right way to go. Basically, I need to create an app that will: 1. Collect multi-l

  • Read SOAP Header Information

    Hello All, We want to read SOAP header from incoming message. We followed blog from William to use the option "Do not use SOAP Envelop". However, we are not sure if we need to modify Sender Interface to include Envelope / Header in the message struct

  • Font Book.............I give up!!!! Please help.....................

    PLEASE HELP!!! I've spent my day trying to resolve why I can't open my Helvetica Neue fonts. I'm working in Adobe Illustrator 12.0.3 (CS2) on a file that until today opened fine. My client had sent me a copy of OpenType Helvetica Neue last week askin

  • Getting Error in b2b.log AIP-50075: Cannot find Document Exchange Plugin

    Hi Gurus, I have a configuration in which Oracle B2B has to pick messages from a filesystem. I have created IDCs to pick messages from the path configured. But Oracle B2B is not picking up the file from the path specified. When I went to b2b.log to l