Supplier Due Payment / Ageing report

Dear All ,
Can i have a report in SAP about supplier due for payments in SAP ?
Pl guide
Regards

hi,
In addition to the above the ageing reports are:
MC50 - Dead stock
MC46 - Slow moving stock
Hope it helps...
Regards
Priyanka.P

Similar Messages

  • Customer Aging Report Query (without invoices offset by incoming payment)

    Hi All Experts,
    May I know is there any field from JDT1 mention which invoices is already offset by the Incoming payment or AR Credit note? Because I do not want those invoices that already offset by incoming payment appear at the Customer Aging Report. Meaning, the data appear in the Customer Aging Report is only show those invoices that yet to pay by the customer. Kindly give some advise on it. Thanks a lot.
    Thanks and regards,
    Angie Ng

    Hi David,
    Thanks for your suggestion. I have try it, but all of my JDT1.IntrnMatch is in 0 value. Meaning in my situation it is none of any reconcilliation making. But from my SBO window, i manage to see that actually this incoming payment is pay for which invoices. Problem is it is difficult for me to do the possiblity logic that might be happen in my Customer Aging Report Query. Please give some advise that how to show only those invoices yet to pay? The current query will show all the data no matter the invoices or credit memo has been offset.
    select OCRD.cardcode 'Supplier Code',OCRD.cardname 'Name',sysdeb  'Debit GBP',syscred 'Credit GBP',
    case JDT1.transtype
    when '13' then 'INV'
    when '14' then 'AR CN'
    when '24' then 'INCOMING'
    else 'Other'
    end 'Type',
    Ref1,
    fccurrency 'BP Currency',
    CONVERT(VARCHAR(10), refdate, 103)'Posting Date' ,
    CONVERT(VARCHAR(10), duedate, 103) 'Due Date',
    CONVERT(VARCHAR(10), taxdate, 103) 'Doc Date' ,
    CASE
    when (DATEDIFF(dd,refdate,current_timestamp))+1 < 31
    then
    case
    when syscred <> 0 then syscred * - 1
    else sysdeb
    end
    end "0-30 days",
    case when ((datediff(dd,refdate,current_timestamp))+1 > 30
    and (datediff(dd,refdate,current_timestamp))+1< 61)
    then
    case
    when syscred <> 0 then syscred * - 1
    else sysdeb
    end
    end "31 to 60 days",
    case when ((datediff(dd,refdate,current_timestamp))+1 > 60
    and (datediff(dd,refdate,current_timestamp))+1< 91)
    then
    case
    when syscred <> 0 then syscred * - 1
    else sysdeb
    end
    end "61 to 90 days",
    CASE
    when (DATEDIFF(dd,refdate,current_timestamp))+1 > 90
    then
    case
    when syscred= 0 then sysdeb
    when sysdeb= 0 then syscred * - 1
    end
    end "90 + days"
    from JDT1,OCRD where JDT1.shortname = OCRD.cardcode and cardtype = 'c' and intrnmatch = '0'
    ORDER BY OCRD.CARDCODE, taxdate

  • Vendor ageing report for down payment bucketwise

    Hi
    I have paid many downpayment to various vendors. Now i want the ageing report for the same (i.e. bucket wise i.e. 0-30 days, 31-60 days and so on).
    This i am getting for vendor invoices in TCode: S_ALR_87012085 (Vendor payment history with OI sorted list).
    Please let me know if the bucketwise report is possible for the downpayment too.

    Hi,
    Vendor ageing for down payments as well as invoice i use to see from T.code FBL1N by creating layouts.
    Choose Arreas after net due date from layout and for that column you can apply a rule that from 0 to Lessthan or equal to 30.
    Like that you can create the layouts. In FBL1N you can give this layout (down) so information come in that format.
    The one disadvantage is that you have to select manually the layouts and you can see only one ageing information at a time.
    Regards,
    Sankar

  • How to handle partial payment in A/R Aging report buckets

    Hello ALL,
             In FIAR_C03 cube we have Item status field and only two values are comming there
             O or C.
              But in R/3 there are some partial payment concept. BI considering partial payment as a open item.
               Example
           We have a invoice of 10,000 USD
           now one payment of 5,000 came from customer side and we settled 5,000 against above invoice
          now remaining is 5,000.
          means 5,000 of payment and 5,000 of invioce should be closed or cleared . But this is not the case becuase of invoice
          is not fully settled. When invoice will settled fully then it will become cleared.
       using open item we are making our AR aging buckets but now 5,000 payment is still open actually its
      cleared and net due date of this payment is different then net due date of invoice thats why
      these two entries are coming in two different aging buckets so the balances are coming different.
    How can we handle this scenario in SAP BI during making of AR aging.
    Any help highly appreciated.
    Thanks,
    Sneha

    There is an OSS note dealing with this 522235 - its shows how to use a virtual char to do this (ie change the due date at runtime)
    This tends to be viewed more as a business process problem - the users woul dlike the part payment to be aged the same as the invoice it's against (like the std R3 aging reports) - I actually like the BW way as it highlights the fact the cach collectors are not doing their jobs of clearing down the debt - problem is now they will all go and create resicual items

  • Business Content for "payment history and ageing report"

    Hi,
    We have AP and AR modules implemented in R/3. And recently the client is implementing Collections Management module in R/3. There is a requirement which has come in which we need to provide the a report by customer the past payments made for the last 6 months and the recievables ageing for 1-30 days, more than 30 days and 90 days. A  sample is:
    Division                 Past-due payment history                                            Receivables Ageing
    Customer         CM-5  CM-4  CM-3  CM-2  CM-1  CM                               1-30days   >30 days  90 days
    A                     04/10  05/10  06/10  07/10  08/10  09/10                            150          200       300
    etc, where CM = Current Month
    After going through the requirement we have found that data for this requirement can be taken from AR module itself as Collections Management data is not being used. In this scenario, if I want to develop a payment history and recievables aging report in BW from AR module, which data sources can be used. I am new the finanace module so if any links to good stuff is greatly appreciated.
    Thanks and Regards
    Vijay

    0FI_AR_4 datasource is the BSID/BSAD line items from R3 and the standard DSOs and Content will give you the ability to do aged debtor reports
    You will have to create your own aged debtor reports in WB as the std ones are pants.
    You create an aging bucket for each aging based on the following example criteria..
    CKF 0-30 days = RKF 0-30 Days Open + RKF 0-30 Days subsequently cleared
    (ie you are tryign to restate the ledger to a point in time)
    RKF 0-30 Open is..
       posting date <= key date
       item status = 0
       net due date on a constant selection of 0 and -30
    RKF 0-30 Subsequently cleared is..
       cleared date > key date
       posting date <- key date
       net due date on a constant selection of 0 and -30
    For payment History - I wouldn;t bother with the standard KNB5 extractor (although you can have a look at ti) _ I find it a bit too high a level
    I would create a realised payment terms report which looks at the following calculations:
      cleared date - net due date (realised payment terms)
      net due date - doc date (offered payment terms)
    And then create a query for all item status = C transactions which aren't payments (ie not equal to doc type DZ) and show the above calculations weighted per Customer Payment Term
    Many ways to skin a cat - the two above will help you on your way
    and

  • F-32 residual payment is affecting my ageing report.

    When I am doing the residual payment using f-32 then we are getting two document generated out this, one for the incoming payment and the other for the balance amount as new invoice with new posting date, this is affecting my ageing report.
    For Example: My old invoice is 01.01.2010 with 1000 USD, when I am applying the residual payment method on 08.03.2010 with 500 USD then two documents are generated out this, one for the incoming payment i.e. for 500 USD and the other for the balance amount as new invoice with new posting date i.e. 500 USD on 08.03.2010.
    My original invoice ageing is under over 81 days, but when we applied the residual payment method then it got changed to less than 21 days, which is incorrect. When we analysis the issue and found that due the residual payment method we are getting this problem i.e. during this process new invoice which is generated ahs replaced my original invoice with the new invoice with new posting date, system is taking that as base and doing the ageing analysis. Which is incorrect?
    We just want to have the original invoice date 01.01.2010 in the new document which is generated on 08.03.2010, so that this may not affect my ageing report.
    Thanks a lot in advance.
    Rajesh Kumar Mantri.

    When you post a residual payment, SAP creates 1 document with 2 line items for the customer.  One line item clears the original invoice and the other posts the difference (residual) as a new open item on the customer.  With the settings in OBA3, you can transfer the baseline date and payment terms from the original invoice to the residual item.  The baseline date is normally used for aging, so with the baseline date and payment terms transfer, the residual will have the same aging as the original invoice.  Also, since the original invoice is cleared when a residual payment is created, it will not show on the aging.
    If you want the original invoice to remain open, not cleared, after the payment, then you need to do a partial payment instead of a residual payment.  With a partial payment, the original invoice and the payment will both be open items on the customer.  The payment will reference the original invoice so that when the remaining payment is made, the two items will be cleared together.
    Regards,
    Shannon

  • Oracle Business Intelligence - Past Due Schedule Value Aging report

    Hi,
    I am a beginner in Oracle Business Intelligence. There is an issue with 'Past Due Schedule Value Aging' report
    [this report displays order lines that are booked, but not yet fulfilled, and the date past the schedule ship date.].
    Actually, the report is supposed to ignore the order lines that have been 'cancelled' (having a quantity of '0').
    But, it is displaying the 'cancelled' lines as well.
    I am supposed to analyze entire logic for 'Past Due Schedule Value Aging' report (Oracle Supply Chain - Release 12).
    So, could anybody please provide the list of the steps to get the entire code? Also, please let me know if I am supposed
    to install any specifc tool to look into the content of this report.
    Thanks in advance.
    Regards,
    Mantha

    Hi Mantha;
    Please check below thread and see its helpful for your issue:
    How to customize the seeded Purchase Order PDF report
    http://kr.forums.oracle.com/forums/thread.jspa?threadID=952782 *<< Posted by Hussein Sawwan*
    Customize standard report using BI Publisher.
    http://kr.forums.oracle.com/forums/thread.jspa?threadID=1074572 *<< Posted by Hussein Sawwan*
    Regard
    Helios

  • AR Aging report... partial payment Report

    Dear Experts,
                   In the Aging Report i have  the Scenario that partial payment's record should not fell on the bucket based on Net Value of that record, instead it should refer some reference field. which field it has to refer?
                  How we can find the record is partial payment record ie what condition it will have?  like open status etc...
                  where i should   apply the logic whether in the datasource level or at the report level.
                  Please note that Dataflow is in 3.5 version
    Thanks in Advance

    Hi,
    You can have a info object to represent the status  in the datatarget and then you can use it in the filter level to filter out open records.
    Regards,
    Anil Kumar Sharma .P

  • 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.

  • (Invoice register Report – Payment Register report = Aging Report)

    Hi,
    The total balance for Invoice registers report “minus” the balance for Payment register report not give me the balance of Invoice aging report
    The expected behavior:
    It must minus the balance between the two reports equal to invoice aging report
    (Invoice register Report – Payment Register report = Aging Report) But this not happen
    What the issue causing for that ?
    Thanks

    Hello.
    I think you cannot expect that calculation to be correct. Just to mention Payment Register, this report does not have a total in the functional currency.
    The following excercise is true:
    Ending Balance of Accounts Payable Trial Balance on period 1 + Posted Invoice Register on period2 - Posted Payment Register on period2 = Ending Balance of Accounts Payable Trial Balance on period 2
    Octavio

  • Apps Report Error(Supplier Payment History Report)

    Hi team,
    APXPPHIS module: Supplier Payment History
    Iam getting below error and unable get report Output.
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.WE8MSWIN1252
    Enter Password:
    MSG-00001: After SRWINIT
    ORA-24324: service handle not initialized
    ==> SELECT V . vendor_name C_VENDOR_NAME , upper ( V . vendor_name ) C_SORT_VENDOR_NAME , V . segment1 C_VENDOR_NUMBER , VS . vendor_site_code C_VENDOR_SITE_CODE , decode ( VS . address_line1 , null , '' , VS . address_REP-0069: Internal error
    REP-57054: In-process job terminated:Terminated with error:
    REP-300: service handle not initialized
    ==> SELECT V . vendor_name C_VENDOR_NAME , upper ( V . vendor_name ) C_SORT_VENDOR_NAME , V . segment1 C_VENDOR_NUMBER , VS . vendor_site_code C_VENDOR_SITE_CODE , decode ( VS . address_line1 , null , '' , VS . address_Report Builder: Release 10.1.2.3.0 - Production on Wed Oct 2 16:30:25 2013
    Thanks & Regards
    San

    San,
    Please see (Supplier Payment History Report Completing With Error (Doc ID 1409467.1)).
    Thanks,
    Hussein

  • Due date in Detail Aging report

    Dear all,
    I would like to ask if it is possible to add the Due date for each document displayed in the Detailed Customer Receivable Againg report ?
    I tried, but it seems impossible to do so, even I set the field as System Variable (as the Due date in Dunning module).
    Thanks a lot

    Hi,
    'Due Date' column of the documents is available in:
    Aging Report - 'Customer Statement Report (One Page per Customer)'
    The same is unavailable in the Details Aging Report.
    Regards,
    Jitin

  • [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

  • Supplier Wise Aging Report As of Date

    Hi,
    We are on 12.1.3
    I have wrote a query to find the Supplier Wise Aging Report .But it is not working for back date i.e if we applied Amount 1000  today, in report patameter if a pass the value from to yesterday date - report should display sum of all aging. If we gave till today.. the value should be 1000 less
    My Query:
    SELECT   yy.vendor_name, yy.vendor_id vendor_num, yy.segment1,
             yy.SUM remaining_advance_amount, yy.less30, yy.greater30,
             yy.greater60, yy.greater90, yy.greater120
    --         (SELECT COUNT (1)
    --            FROM ap_invoices_all aia
    --           WHERE aia.cancelled_date IS NULL
    --             AND aia.vendor_id = yy.vendor_id
    --             AND TRUNC (aia.invoice_date) BETWEEN :p_from_date AND :p_to_date
    --             AND aia.amount_paid <> aia.invoice_amount) out_stnd_bill,
    --         (SELECT SUM (NVL (apd.prepay_amount_remaining, 0))
    --            FROM ap_invoices_all aib,
    --                 ap_invoice_distributions_all apd
    --           WHERE aib.cancelled_date IS NULL
    --             AND aib.vendor_id = yy.vendor_id
    --             AND aib.invoice_id = apd.invoice_id
    --             AND apd.reversal_flag = 'N'
    --             AND TRUNC (aib.invoice_date) BETWEEN :p_from_date AND :p_to_date
    --             AND aib.invoice_type_lookup_code = 'PREPAYMENT') on_ac_amount
    FROM     (SELECT   xx.vendor_name, xx.vendor_id, xx.segment1,
                       SUM (NVL (xx.less_30, 0)) less30,
                       SUM (NVL (xx.greater_30, 0)) greater30,
                       SUM (NVL (xx.greater_60, 0)) greater60,
                       SUM (NVL (xx.greater_90, 0)) greater90,
                       SUM (NVL (xx.greater_120, 0)) greater120,
                       (  SUM (NVL (xx.less_30, 0))
                        + SUM (NVL (xx.greater_30, 0))
                        + SUM (NVL (xx.greater_60, 0))
                        + SUM (NVL (xx.greater_90, 0))
                        + SUM (NVL (xx.greater_120, 0))
                       ) SUM
                  FROM (SELECT   c.vendor_name, c.vendor_id, c.segment1,
                                 (CASE
                                     WHEN ((SYSDATE) - TRUNC (b.invoice_date) <=
                                                                                30
                                        THEN NVL ((  NVL (b.invoice_amount, 0)
                                                   - NVL (b.prepay_amount_applied,
                                                          0
                                                  0
                                     ELSE 0
                                  END
                                 ) less_30,
                                 (CASE
                                     WHEN ((SYSDATE) - TRUNC (b.invoice_date)
                                              BETWEEN 31
                                                  AND 60
                                        THEN NVL ((  NVL (b.invoice_amount, 0)
                                                   - NVL (b.prepay_amount_applied,
                                                          0
                                                  0
                                     ELSE 0
                                  END
                                 ) greater_30,
                                 (CASE
                                     WHEN ((SYSDATE) - TRUNC (b.invoice_date)
                                              BETWEEN 61
                                                  AND 90
                                        THEN NVL ((  NVL (b.invoice_amount, 0)
                                                   - NVL (b.prepay_amount_applied,
                                                          0
                                                  0
                                     ELSE 0
                                  END
                                 ) greater_60,
                                 (CASE
                                     WHEN ((SYSDATE) - TRUNC (b.invoice_date)
                                              BETWEEN 91
                                                  AND 120
                                        THEN NVL ((  NVL (b.invoice_amount, 0)
                                                   - NVL (b.prepay_amount_applied,
                                                          0
                                                  0
                                     ELSE 0
                                  END
                                 ) greater_90,
                                 (CASE
                                     WHEN ((SYSDATE) - TRUNC (b.invoice_date) >
                                                                               120
                                        THEN NVL ((  NVL (b.invoice_amount, 0)
                                                   - NVL (b.prepay_amount_applied,
                                                          0
                                                  0
                                     ELSE 0
                                  END
                                 ) greater_120
                            FROM ap_payment_schedules_all a,
                                 ap_invoices_v b,
                                 po_vendors c
                           WHERE a.invoice_id = b.invoice_id
                             AND b.vendor_id = c.vendor_id
                             AND b.invoice_type_lookup_code = 'PREPAYMENT'
                             -- AND a.amount_remaining <> 0
                             AND TRUNC (b.invoice_date) BETWEEN :p_from_date
                                                            AND :p_to_date
                             AND b.cancelled_date IS NULL
                        --AND c.segment1 = 837
                        ORDER BY c.vendor_name) xx
              GROUP BY xx.vendor_name, xx.vendor_id, xx.segment1) yy
    ORDER BY yy.vendor_name;

    Hi Octavio,
    As per this note 1290116.1.
    There is no replacement for this table
    Thanks
    Vishwa

  • AR Aging Report by Due Date

    Hello:
    I did the OB transfer from another database. I transferred all the invoices by due date. After the transfer I tried to run an aging report. The aging report does not show the AR by age. I just see the total. Any help to resolve this will be much appreciated
    Thanks,
    Satish

    Hi Rahul:
    I entered them at Feb 01 date with the due date of the respective invoices. When I run the aging report by posting date all the transactions fall under < 30 days. But when I choose aging report by due date all the balances show under Balance due and there is no aging available. I tried doing this in the test data base and it worked fine there. But not in the active/production database. Please let me know why is this?
    Thanks,
    Satish

Maybe you are looking for