Aged debt report( account receivable)

Hi,
I am supposed to develope a aged debt report. Will anyone please give me the an example of aged debt report.Is there any business content aged debt report available ??
how will we find out the oustanding days, I mean between what date to what date.
Please provide me as much as information in this.
regards,
Bill

Hello Bill,
  Check  Business content FIAR, FIAP . where you have such reports.
These reports use Posting date of the document , Clearing date on the document and user entry  Key date for the analysis.
http://help.sap.com/saphelp_nw70/helpdata/en/ac/b2ae397f768c3ce10000000a11402f/content.htm
Jaya

Similar Messages

  • Aged Debt Reporting ( AR ) - help required

    Hi Guys,
    I need your help in one of the requirement I have at the moment for AR Reporting.
    My client wish to see the snap shot of the Debt on weekly and monthly basis since the day the system has gone live.
    I know how the Aged Debt Reports work in BW. It works on a key date and 3 variables.
    0P_KEYDT : For the characteristic NETDUEDATE: Key date for net payment
    0P_KEYD2 : For the characteristic 0PSTNG_DATE: Key date for posting.
    0P_KEYD3 : For the characteristic 0CLEAR_DATE: Key date of clearing
    We create restricted key on 0DEB_CRED_LC making use of the above 3 variables to find the Debt(oustanding amount) as on the key date. Then we create other key fiegures using offset on the above variables to defined the Debt in 1-15 days, 15-30 days, 30-45 days etc…
    But my requirement here is different.
    Now the user wants to see the Debt amount for every week and every month from the beginning of go-live. They require snapshot of the Debt in that week. If the invoice is  open in week 01.2014 and cleared in week 02.2014 then it should only get displayed in 01.2014 i.e. snapshot of outstanding amount for that week or month.
    Now the issue here asfollows
    1) By using the offset in the variable i.e. -7, -14, -21, -28 etc on key date I can go back to certain weeks not till the beginning of the system.
    2) If I use -30, -60, 90 to generate the snapshot I cannot get the month end outstanding always as certain months are 31 days and certain months are 28 days(feb). Also I cannot go back till beginning of the system
    I have a workaround. Weekend and month end  I can take backup of the open items 0FI_DOCSTAT = ‘O‘ and store this in an infocube.
    For this also I have few concerns
    1) The data volume will be too high. I have to find out what level the clinet wish to see the data so that it will display the aggregated Debt amount at the level
    2) This design can only be possible for now onwards but I cannot do that for past period
    3) What will happen if the load fails on weekend or month end then I will lose the snap shot as few of the open items would have been cleared. It would not give an exact picture.
    The problem here is for snapshot data i.e dent on that week/month.
    Can anybody help me with some idea to handle this situation?
    Regards,

    Hello,
    Try the below way outs
    1) If are you not having calendar week / month in the source then create a hierarchy on posting date for deriving calendar week and calendar month.
    2) Now in the query Keep the hierarchy in the rows and in the column add 0DEB_CRED_LC (without any restriction) . Maintain in the calculation as *cumulative. *This will give you balances on any week or month. Draw back is that the report may be huge.
    If your reporting requirement is not at Customer level then there is another way of doing it.
    The AR can also be determined using GL accounts. So you can use a FIGL data source which can give you Balance based on any fiscal year period.
    Let me know your comments
    Regards
    Gajesh

  • Help with Aged Debt report

    Hi,
    I have a good aged debt report, but I would like to also include the Notes text for each customer on the aged debt report my sql is as follows:
    SELECT a.trx_number doc_no,
    a.trx_date doc_date,
    a.status status,
    a.bs_batch_source_name Source,
    a.al_class_meaning Class,
    a.due_date Due_date,
    a.amount_due_original original_amount,
    a.amount_due_remaining amount_remaining,
    b.customer_name Customer_name,
    b.customer_number Customer_number,
    b.customer_class_code Customer_Class,
    b.profile_class_name Profile,
    nvl(a.days_past_due,0) days_past_due
    FROM apps.ar_payment_schedules_v a
    LEFT OUTER JOIN apps.ar_customers_v b
    ON a.customer_id = b.customer_id
    WHERE a.amount_due_remaining<>0
    UNION SELECT
    acr.receipt_number doc_no,
    acr.receipt_date doc_date,
    acr.receipt_status status,
    DECODE(acr.receipt_status_dsp,'Applied','On Account','Unapplied') Source,
    'Unapplied Cash' Class,
    acr.receipt_date Due_date,
    acr.amount *-1 original_amount,
    acr.applied_amount-acr.amount amount_remaining,
    acr.customer_name Customer_name,
    acr.customer_number Customer_number,
    'Unapplied Cash' Customer_Class,
    'Unapplied Cash' Profile,
    ROUND(SYSDATE- acr.receipt_date) Days_Past_Due
    FROM apps.ar_cash_receipts_v acr
    WHERE acr.amount <>0
    AND acr.type <> 'MISC'
    AND acr.receipt_status_dsp <> 'Reversal-User Error'
    The Notes Text is in table AR_Notes but I not sure how to link to this table.
    Any help would be great.

    Hi,
    As per oracle ETRM:
    "AR_NOTES" joins "RA_CUSTOMER_TRX_ALL" using "AR_NOTES.CUSTOMER_TRX_ID"
    the "CUSTOMER_TRX_ID" can also be found in the "apps.ar_payment_schedules_v"
    But you will not find it in the "apps.ar_cash_receipts_v"
    So you can join it to the first part of the select...

  • SAP Reports:  Accounts Receivable and Credit Management

    Good Afternoon Folks-
    Can anyone give me a listing of all the AR and Credit Management Reports and what they tell?
    I cannot find anything that tells me this report is good for DSO, etc.
    Thanks!

    Hi,
    To View the Reports in Accounts Receivable , here is the menu path
    Accounting - Financial Accounting - Customers - Information System - Reports for Accounts Receivable Accounting
    Customer Balances
    S_ALR_87012167 - Accounts Receivable Information System
    S_ALR_87012172 - Customer Balances in Local Currency
    S_ALR_87012186 - Customer Sales
    S_ALR_87012169 - Transaction Figures: Account Balance
    S_ALR_87012170 - Transaction Figures: Special Sales
    S_ALR_87012171 - Transaction Figures: Sales
    Customers: Items
    S_ALR_87012168 - Due Date Analysis for Open Items
    S_ALR_87012197 - List of Customer Line Items
    S_ALR_87012173 - List of Customer Open Items for Printing
    S_ALR_87012174 - List of Customer Open Items
    S_ALR_87012175 - Open Items - Customer Due Date Forecast
    S_ALR_87012176 - Customer Evaluation with OI Sorted List
    S_ALR_87012177 - Customer Payment History
    S_ALR_87012178 - Customer Open Item Analysis by Balance of Overdue Items
    S_ALR_87012198 - List of Cleared Customer Items for Printing
    S_ALR_87012199 - List Of Down Payments Open On Key Date - Customers 
    Master Data
    S_ALR_87012179 - Customer List
    S_ALR_87012180 - Address List
    S_ALR_87012182 - Display Changes to Customers
    S_ALR_87012183 - Display/Confirm Critical Customer Changes
    S_ALR_87012195 - Customer Master Data Comparison
    For Credit Management, the menu path is
    Accounting - Financial Accounting - Customers - Credit Management - Credit management info system
    F.31 - Overview
    F.33 - Brief overview
    F.32 - Missing data
    FCV3 - Early warning list
    FDK43 - Master data list
    S_ALR_87012215 - Display changes to credit management
    S_ALR_87012218 - Credit master sheet
    This is for Ecc 5.0. to know more about the particular report, click on the program documentation (Shift + F1). The icon is in blue color and  ' i ' is what u have to select to know more information about the report.
    Hope it helps.
    Regards
    M.S.Reddy

  • Age debt report

    Hi,
    Can anyone tell what is the standard report name of aged debtor report in ECC6 and 4.0B ?

    use :S_ALR_87012175 - for Open Items , Customer Due Date Forecast
           S_ALR_87012174 - for just list of Customer Open Items 
           S_ALR_87012178 - for Customer Open Item Analysis by Balance of Overdue Items
           FBL5N  to  Display/Change all Line Items for the debitor/customer
    hope this will help u
    thanks and regards
    Arjun

  • Age Analysis report for asset

    Hi All,
    I have to create a Age analysis report for FI documents
    which have line items with posting key 75 & 70 (Asset)
    Given logic is
    1 Selection screen has parameters  - Company code, Key date
    2 Need to take all line items with posting key 70 & 75
    (BSEG-BSCHL = 70 or 75)
    Layout of report is
    Asset no       0-30 31-60      61-90      91-120 . 151-360  (days)
    80000003     2000.00    3000.00    1000.00   4000.00    7000.0
    80000006     1000.00    5000.00     300.00    5000.00    4000.0
    Local curency amount should be categorised under the days
    diferences between key date (selection screen) & posting date
    of the accounting document.
    My problem is,
    Posting date of the document is not in the BSEG table. It is
    in the BKPF table.Therefore I have to extract all FI documents(Not only documents with posting key 75 or 70)  within  360 days from Key date in BKPF the table.
    I cannot join BSEG & BKPF. Because,  BSEG table is a cluster table.
    Can you please tell me the way how can i extract the data for this report with out any performance issues.
    Pra

    Great idea, but I dont think it is going to work.
    The 1st problem should be, how do you work out the key date... You will need some good code for that.
    Have a look at the customer aged debt reports for some help.
    After that, if you just want asset documents, do they have their own unique document type, if so, you could use the doc type from BKPF to reduce the number you want to select in BSEG.
    Have you looked at any of the standard Asset dep reports, perhaps there is something there you could use.

  • AR - Aging Bucket report Customisation

    I have a requirement from end users to be able to run an aged debt report for any date range in the past e.g. From 01-Jan-2008 to 01-Jan-2013.
    Aging Bucket report only has, "As of date" field in the parameters.
    Is it possible to add additional parameters to this report?

    Hi.
    I don't believe such parameter can be included in the Aging reports. According to the user manual, the design of the report is to:
    Receivables includes all open items whose GL date is before or the same as the date you enter, and whose GL date closed is after the date you enter. The default is the current date.
    Besides, such parameter would cause debts to be excluded from the balance.
    Octavio

  • Accounts receivable on Business Area level

    Hi,
    Is there a way to report accounts receivable on Business Area level?
    I want to use the InfoCube 0FIAR_C02 for reporting transactional A/R data - the customer has 1 company code and below this 7 business areas on which receivable reporting should be realized.
    Thanks in advance,
    Alex

    Hi Alexander,
    Its very easy to do on the line item cube/DSO. You need to customize the datasource 0FI_AR_4. Its a very simple activity because the field GSBER (Business Area) is already there AR line item tables so you dont need to write a routine to puplulate this field.
    Just go to RSA6, double click on 0FI_AR_4 and then open the extraction strucutre by double clicking on it. Click on 'Append Structure'. Add the field GSBER there and save and activate the structure. Go back to RSA6 and unhide this field if its hidden. Check this DS in RSA3 if it's populating the correct values.
    Now on the BI side just add this characteristic (0BUS_AREA) in your infoprovider and the remaining data flow (Transformations/update rules/transfer rules etc).
    Hope this will help. Thanks.
    Sumit

  • Accounts Receivable Report: Customer Wise Ageing Analysis report -FI module

    Hi Gurus,
                 Can anyone help me in providing standard report(source code) or already done sample report(source code) for Accounts Receivable Report: Customer Wise Ageing AnalysisThis is in FI Module. Though it is FI Module we need to fetch details related to Sales Module, and the days should be <0     30     60     90     120     180     365     >365     
    It is urgent I need to deliver this report by this week end.
    Please help me . Waiting for your reply.
    Points Rewarded for help rendered and I would personally send a good gift if you can help me
    Yours Truly,
    Rajiv Christopher.
    Edited by: Rajiv Christopher on Apr 2, 2008 11:33 AM

    Hi,
    i am attaching aging report.
    see if this is useful to you.
    REPORT ZFUS0102 MESSAGE-ID OA
                    LINE-SIZE 270.
    Title:      GR/IR AGING REPORT
    Date:       January 2001
    TABLES: DISVARIANT, EKPO.
    TYPE-POOLS: SLIS.
    Tables
    TABLES:
      BSIS,
      EKKO.
    working table
    DATA:  BEGIN OF RTAB OCCURS 0,
             HKONT   LIKE BSIS-HKONT,
             ZUONR   LIKE BSIS-ZUONR,
             BUDAT   LIKE BSIS-BUDAT,
             SHKZG   LIKE BSIS-SHKZG,
             DMBTR   LIKE BSIS-DMBTR,
             PRCTR   LIKE BSIS-PRCTR,
          END OF RTAB.
    DATA: BEGIN OF WTAB OCCURS 0,
             ZUONR(2) TYPE N,
             PRCTR   LIKE BSIS-PRCTR,
             DAYS(4)  TYPE P,
             DMBTR   LIKE BSIS-DMBTR,
          END OF WTAB.
    DATA: BEGIN OF PTAB OCCURS 0,
             ZUONR(2),
             PRCTR   LIKE BSIS-PRCTR,
             AMT30   LIKE BSIS-WRBTR,
             AMT60   LIKE BSIS-WRBTR,
             AMTPL   LIKE BSIS-WRBTR,
             TOTAL   LIKE BSIS-WRBTR,
          END OF PTAB.
    PARAMETERS:  COMPANY LIKE BSIS-BUKRS OBLIGATORY,
                 ACCT    LIKE BSIS-HKONT OBLIGATORY,
                 DATE    LIKE SY-DATUM OBLIGATORY.
    SELECT-OPTIONS: S_EKORG FOR EKKO-EKORG.
    PARAMETERS: P_VARI LIKE DISVARIANT-REPORT.
    DATA: WS-AMT30 LIKE BSIS-WRBTR.
    DATA: WS-AMT60 LIKE BSIS-WRBTR.
    DATA: WS-AMTPL LIKE BSIS-WRBTR.
    DATA: TITLE(21) VALUE 'GR/IR Aging Report'.
    DATA: LIN TYPE I.
    DATA: GX_VARIANT LIKE DISVARIANT,
          G_VARIANT LIKE DISVARIANT.
    DATA:  LAYOUT   TYPE SLIS_LAYOUT_ALV,
           L_F      TYPE SLIS_T_FIELDCAT_ALV   WITH HEADER LINE,
           GROUP    TYPE SLIS_T_SP_GROUP_ALV   WITH HEADER LINE,
           COLOR    TYPE SLIS_T_SPECIALCOL_ALV WITH HEADER LINE.
    DATA:  LT_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER,
           LS_LINE TYPE SLIS_LISTHEADER,
           T_EVENTS   TYPE SLIS_T_EVENT.
    CONSTANTS: FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE'.
    INITIALIZATION.
      PERFORM EVENTTAB_AUFBAUEN USING T_EVENTS[].
      PERFORM VARIANT_INIT.
    Get default variant
      GX_VARIANT = G_VARIANT.
      CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
           EXPORTING
                I_SAVE     = 'A'
           CHANGING
                CS_VARIANT = GX_VARIANT
           EXCEPTIONS
                NOT_FOUND  = 2.
      IF SY-SUBRC = 0.
        P_VARI = GX_VARIANT-VARIANT.
      ENDIF.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
      PERFORM VARIANT_INPUTHELP_F14.
    START-OF-SELECTION.
      LS_LINE-TYP  = 'S'.
      WRITE SY-DATUM TO LS_LINE-INFO DD/MM/YY.
      WRITE SY-UZEIT TO LS_LINE-INFO+10.
      WRITE SY-UNAME TO LS_LINE-INFO+20.
      WRITE TITLE    TO LS_LINE-INFO+30.
      APPEND LS_LINE TO LT_TOP_OF_PAGE.
      PERFORM FIELDS.
      IF NOT P_VARI IS INITIAL.
        PERFORM PAI_OF_SELECTION_SCREEN.
      ELSE.
        CALL FUNCTION 'REUSE_ALV_VARIANT_SELECT'
             EXPORTING
                  I_DIALOG            = ' '
                  I_USER_SPECIFIC     = 'A'
                  I_DEFAULT           = ' '
            I_TABNAME_HEADER    =
            I_TABNAME_ITEM      =
                  IT_DEFAULT_FIELDCAT = L_F[]
                  I_LAYOUT            = LAYOUT
             IMPORTING
            E_EXIT              =
                  ET_FIELDCAT         = L_F[]
            ET_SORT             =
            ET_FILTER           =
             CHANGING
                  CS_VARIANT          = DISVARIANT
             EXCEPTIONS
                  WRONG_INPUT         = 1
                  FC_NOT_COMPLETE     = 2
                  NOT_FOUND           = 3
                  PROGRAM_ERROR       = 4
                  OTHERS              = 5.
      ENDIF.
    Decide which tables to access.
      PERFORM MAIN_SELECT.
      MOVE TITLE  TO LAYOUT-WINDOW_TITLEBAR.
      CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
           EXPORTING
                I_CALLBACK_PROGRAM      = 'ZFUS0102'
                I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
                IS_LAYOUT               = LAYOUT
                IT_FIELDCAT             = L_F[]
                IT_SPECIAL_GROUPS       = GROUP[]
                I_SAVE                  = 'A'
                IS_VARIANT              = G_VARIANT
                IT_EVENTS               = T_EVENTS
           TABLES
                T_OUTTAB                = PTAB
           EXCEPTIONS
                PROGRAM_ERROR           = 1
                OTHERS                  = 2.
          FORM FIELDS                                                   *
    FORM FIELDS.
      L_F-FIELDNAME     = 'ZUONR'.
      L_F-OUTPUTLEN     = 6.
      L_F-SELTEXT_L     = 'SERIES'.
      L_F-REPTEXT_DDIC  = 'SERIES'.
      L_F-REF_TABNAME   = 'PTAB'.
      L_F-SP_GROUP      = 'A'.
      APPEND L_F. CLEAR L_F.
      L_F-FIELDNAME     = 'PRCTR'.
      L_F-OUTPUTLEN     = 10.
      L_F-SELTEXT_L     = 'PROFIT CTR.'.
      L_F-REPTEXT_DDIC  = 'PROFIT CTR.'.
      L_F-REF_TABNAME   = 'PTAB'.
      L_F-SP_GROUP      = 'A'.
      APPEND L_F. CLEAR L_F.
      L_F-FIELDNAME     = 'AMT30'.
      L_F-SELTEXT_L     = '30 DAYS'.
      L_F-REPTEXT_DDIC  = '30 DAYS'.
      L_F-REF_TABNAME   = 'PTAB'.
      L_F-SP_GROUP      = 'A'.
      L_F-REF_TABNAME   = 'BSIS'.
      L_F-REF_FIELDNAME = 'WRBTR'.
      L_F-DO_SUM        = 'X'.
      APPEND L_F. CLEAR L_F.
      L_F-FIELDNAME     = 'AMT60'.
      L_F-SELTEXT_L     = '60 DAYS'.
      L_F-REPTEXT_DDIC  = '60 DAYS'.
      L_F-REF_TABNAME   = 'PTAB'.
      L_F-SP_GROUP      = 'A'.
      L_F-REF_TABNAME   = 'BSIS'.
      L_F-REF_FIELDNAME = 'WRBTR'.
      L_F-DO_SUM        = 'X'.
      APPEND L_F. CLEAR L_F.
      L_F-FIELDNAME     = 'AMTPL'.
      L_F-SELTEXT_L     = '60+ DAYS'.
      L_F-REPTEXT_DDIC  = '60+ DAYS'.
      L_F-REF_TABNAME   = 'PTAB'.
      L_F-SP_GROUP      = 'A'.
      L_F-REF_TABNAME   = 'BSIS'.
      L_F-REF_FIELDNAME = 'WRBTR'.
      L_F-DO_SUM        = 'X'.
      APPEND L_F. CLEAR L_F.
      L_F-FIELDNAME     = 'TOTAL'.
      L_F-SELTEXT_L     = 'TOTAL'.
      L_F-REPTEXT_DDIC  = 'TOTAL'.
      L_F-REF_TABNAME   = 'PTAB'.
      L_F-SP_GROUP      = 'A'.
      L_F-REF_TABNAME   = 'BSIS'.
      L_F-REF_FIELDNAME = 'WRBTR'.
      L_F-DO_SUM        = 'X'.
      APPEND L_F. CLEAR L_F.
    ENDFORM.
          FORM MAIN_SELECT                                              *
    FORM MAIN_SELECT.
      SELECT HKONT ZUONR BUDAT SHKZG DMBTR PRCTR
           INTO TABLE RTAB
           FROM BSIS
           WHERE BUKRS = COMPANY
           AND   HKONT = ACCT.
      IF SY-SUBRC = 0.
        SORT RTAB.
        PERFORM PROCESS_RTAB.
        PERFORM PROCESS_WTAB.
      ENDIF.
    ENDFORM.                    " MAIN SELECT
          FORM VARIANT_INPUTHELP_F14                                    *
    FORM VARIANT_INPUTHELP_F14.
      DATA:  G_EXIT(1) TYPE C.
      CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
           EXPORTING
                IS_VARIANT          = G_VARIANT
                I_SAVE              = 'A'  " g_save
              it_default_fieldcat =
           IMPORTING
                E_EXIT              = G_EXIT
                ES_VARIANT          = GX_VARIANT
           EXCEPTIONS
                NOT_FOUND = 2.
      IF SY-SUBRC = 2.
        MESSAGE ID SY-MSGID TYPE 'S'      NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ELSE.
        IF G_EXIT = SPACE.
          P_VARI = GX_VARIANT-VARIANT.
        ENDIF.
      ENDIF.
    ENDFORM.
          FORM USER_COMMAND                                             *
    -->  UCOMM                                                         *
    -->  SELFIELD                                                      *
    FORM USER_COMMAND USING UCOMM LIKE SY-UCOMM SELFIELD TYPE
    SLIS_SELFIELD.
      IF UCOMM EQ '&IC1'.
        IF SELFIELD-TABINDEX <= 0.
          MESSAGE S108.
          EXIT.
        ENDIF.
      IF SELFIELD-SEL_TAB_FIELD CS 'LIFNR'.
        SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
        CALL TRANSACTION 'XK02'.
      ELSE.
        IF SELFIELD-SEL_TAB_FIELD CS 'VEND'.
          SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
          CALL TRANSACTION 'FBL1'.
        ENDIF.
      ENDIF.
        CLEAR SY-UCOMM. CLEAR UCOMM.
      ENDIF.
    ENDFORM.
          FORM TOP_OF_PAGE                                              *
    FORM TOP_OF_PAGE.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
           EXPORTING
                IT_LIST_COMMENTARY = LT_TOP_OF_PAGE.
    ENDFORM.
          FORM EVENTTAB_AUFBAUEN                                        *
    -->  P_T_EVENTS                                                    *
    FORM EVENTTAB_AUFBAUEN USING P_T_EVENTS TYPE SLIS_T_EVENT.
      DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
           EXPORTING
                I_LIST_TYPE = 0
           IMPORTING
                ET_EVENTS   = P_T_EVENTS.
      READ TABLE P_T_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                                                     INTO LS_EVENT.
      IF SY-SUBRC = 0.
        MOVE FORMNAME_TOP_OF_PAGE TO LS_EVENT-FORM.
        APPEND LS_EVENT TO P_T_EVENTS.
      ENDIF.
    ENDFORM.                               " EVENTTAB_AUFBAUEN
          FORM PAI_OF_SELECTION_SCREEN                                  *
    FORM PAI_OF_SELECTION_SCREEN.
      IF NOT P_VARI IS INITIAL.
        MOVE G_VARIANT TO GX_VARIANT.
        MOVE P_VARI TO GX_VARIANT-VARIANT.
        CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
             EXPORTING
                  I_SAVE     = 'A'  " g_save
             CHANGING
                  CS_VARIANT = GX_VARIANT.
        G_VARIANT = GX_VARIANT.
      ELSE.
        PERFORM VARIANT_INIT.
      ENDIF.
    ENDFORM.                               " PAI_OF_SELECTION_SCREEN
          FORM VARIANT_INIT                                             *
    FORM VARIANT_INIT.
      CLEAR G_VARIANT.
      G_VARIANT-REPORT = 'ZFUS0102'.
    ENDFORM.                               " VARIANT_INIT
    *&      Form  PROCESS_RTAB
          text
    -->  p1        text
    <--  p2        text
    FORM PROCESS_RTAB.
      DATA TLNS TYPE I.
      DESCRIBE TABLE S_EKORG LINES TLNS.
      LOOP AT RTAB.
        IF TLNS GT 0.
          SELECT SINGLE EKORG FROM EKKO INTO EKKO-EKORG
            WHERE EBELN = RTAB-ZUONR(10).
          CHECK EKKO-EKORG IN S_EKORG.
        ENDIF.
        IF NOT RTAB-BUDAT > DATE.
          MOVE RTAB-ZUONR(2) TO WTAB-ZUONR.
          COMPUTE WTAB-DAYS = DATE - RTAB-BUDAT.
          IF RTAB-SHKZG = 'H'.
            WTAB-DMBTR = RTAB-DMBTR * -1.
          ELSE.
            WTAB-DMBTR = RTAB-DMBTR * 1.
          ENDIF.
          MOVE RTAB-PRCTR TO WTAB-PRCTR.
          APPEND WTAB.
        ENDIF.
      ENDLOOP.
      FREE RTAB.
    ENDFORM.                    " PROCESS_RTAB
    *&      Form  PROCESS_WTAB
          text
    -->  p1        text
    <--  p2        text
    FORM PROCESS_WTAB.
      SORT WTAB BY ZUONR PRCTR DAYS.
      LOOP AT WTAB.
        PTAB-ZUONR = WTAB-ZUONR.
        PTAB-PRCTR = WTAB-PRCTR.
        AT END OF DAYS.
          SUM.
          IF WTAB-DAYS > 60.
            WS-AMTPL = WS-AMTPL + WTAB-DMBTR.
          ELSE.
            IF WTAB-DAYS > 30.
              WS-AMT60 = WS-AMT60 + WTAB-DMBTR.
            ELSE.
              WS-AMT30 = WS-AMT30 + WTAB-DMBTR.
            ENDIF.
          ENDIF.
        ENDAT.
        AT END OF PRCTR.
          PTAB-AMTPL = WS-AMTPL.
          PTAB-AMT30 = WS-AMT30.
          PTAB-AMT60 = WS-AMT60.
          COMPUTE PTAB-TOTAL = PTAB-AMTPL + PTAB-AMT30 + PTAB-AMT60.
          APPEND PTAB.
          WS-AMTPL = 0.
          WS-AMT30 = 0.
          WS-AMT60 = 0.
        ENDAT.
      ENDLOOP.
      SORT PTAB BY ZUONR PRCTR.
    ENDFORM.                    " PROCESS_WTAB
    regards,
    Sindhu

  • Currency problem in accounts receivables ageing report

    when i generated accounts receivables ageing report i got ageing in UAE DIRHAMS only and  i have receivables in two different currencies in UAE DIRHAMS AND IN EURO , i want to get all receivables in the ageing report in euro only but i couldn't please how to solve this currency problem
    thanks in advance

    Hi
    Please refer this transaction code for account receivable ageing report
    S_ALR_87012168 - Due Date Analysis for Open Items
    Regards
    Praveen

  • Accounts receivables ageing report

    i want to know how to generate accounts receivables ageing report,which T-codes to use

    Hi
    Please refer this transaction code for account receivable ageing report
    S_ALR_87012168 - Due Date Analysis for Open Items
    Regards
    Praveen

  • Mismatch in  Accounts Receivable Balance and A/R Aging Balance due

    Hi All,
    I am working on SAP 2007 A PL09 and facing a issue in which
    Balance in Accounts Receivable in chart of account does
    not matches with the total amount in Balance due field in
    Customer Receivables Aging report.
    Kindly help
    Thanks

    Hi,
    Please check the following link for the Aging RCA in order to understand the working and the various issues regarding the Aging Reports in SAP Business One.
    [RCA Aging Report|https://websmp110.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700001163372009E]
    Kind Regards,
    Jitin
    SAP Business One Forum Team

  • Accounts Receivable - Report which includes Volumetrics i.e. Material/Volume/Price

    Hello,
    What report can be used to obtain the following for Accounts Receivable (all in one report would be preferred):
         AR Aging
         Material Code
         Volume
         Price of material
    For example, AR has $1M due from a customer (its current/within 30 days)
         What material(s) does that cover? It covers x,y,z materials
         At what price per material? x price is $90.81 per bbl, y price is $100.79 per bbl and z price is $65.84 per bbl
         What is the volume of each? x volume is 5,000 bbls, y volume is 3,000 bbls and z volume is 3,700
    We need to be able to run a report that includes all the above data.
    Any help is greatly appreciated.
    Thanks!

    Please check report under Financial-> Financial report->Accounting->Aging- > Choose customer aging receivables.
    Also here is a list of other usual reports available:
    Accounting - Financial Accounting - Customers - Information System - Reports for Accounts Receivable Accounting
    Customer Balances
    S_ALR_87012167 - Accounts Receivable Information System
    S_ALR_87012172 - Customer Balances in Local Currency
    S_ALR_87012186 - Customer Sales
    S_ALR_87012169 - Transaction Figures: Account Balance
    S_ALR_87012170 - Transaction Figures: Special Sales
    S_ALR_87012171 - Transaction Figures: Sales
    Customers: Items
    S_ALR_87012168 - Due Date Analysis for Open Items
    S_ALR_87012197 - List of Customer Line Items
    S_ALR_87012173 - List of Customer Open Items for Printing
    S_ALR_87012174 - List of Customer Open Items
    S_ALR_87012175 - Open Items - Customer Due Date Forecast
    S_ALR_87012176 - Customer Evaluation with OI Sorted List
    S_ALR_87012177 - Customer Payment History
    S_ALR_87012178 - Customer Open Item Analysis by Balance of Overdue Items
    S_ALR_87012198 - List of Cleared Customer Items for Printing
    S_ALR_87012199 - List Of Down Payments Open On Key Date - Customers
    Master Data
    S_ALR_87012179 - Customer List
    S_ALR_87012180 - Address List
    S_ALR_87012182 - Display Changes to Customers
    S_ALR_87012183 - Display/Confirm Critical Customer Changes
    S_ALR_87012195 - Customer Master Data Comparison

  • Report on Account Receivable

    hi,
    can any one help regarding report on account receivable. the senario is ....
    i want to generate report on accounts receivable, that to based on aging
    so wht is aging n how to display it and is offset variable n how to create offset variable

    Hi,
    of the differences between account based CO-PA and costing-based CO-PA that there is no delta extraction. There is also 1 other rule. You can only select 1 fiscal-period. The set-up is similar to costing based CO-PA.
    The big difference between Account Based CO-AP and Costing Based CO-PA is of course the data is stored in the CO Modules.
    Account based CO-PA is part of the CO concept. This means when you post to a cost element the data is posted to a CO-module (CCA, OPA, PA, PS etc). The way the data is stored is also different from costing based PA.
    The CO tables like COEP, COBK (for the individual item are used and the COSS and COSP are used for the totals.
    The object where the posting are related to they are stored in the CE4... table. So if you want to analyse the data there is 1 keyfigure and the cost-element is a characteristic (account model).
    COsting Based CO-PA data is statistical data. This means that the update of CO-PA is not always equal to what is stored in the CO modules or in finance. The cost element is also not always updated and there are also more key-figures used to store info about the type of costs or revenues. Tables as CE1, CE2 , CE3 and CE4 are used.
    Extraction for Account Based CO-PA is only based on the total records (full loads are only possible). For costing based CO-PA there it is possible work with init and delta packages and also to select data from the individual postings databases (CE1, CE2).
    The way you generate the extractor is similar.
    Hopelfully this gives you a bit more background of the CO-PA module.
    CE1 *** , CE *** = Line Item Tables
    CE2 *** = Plan Line Item
    CE3 *** = Value Fields , Key Fig
    CE4 *** = Segment Table
    look at htis OSS Note to have more info (with example) about KF vs Account Mode: 407563
    The question of whether to have key fig mode or characterstic model come when you have a requirement to report on multiple key figures like plan commitment, actual, etc. In such a scenerio, you have the option of either having so many key figures in the cube ( and in the report) or just have one key fig and distinguish them with a characterisic. The first one if called key fig model and the second one is called characteristic model.
    If you have characteristic model you need to either have that may charactristic of that many values with in a characteristic , for example multiple values in version or value type
    Regards,
    Hareesh

  • Accounts Receivable and collections report project-wise

    Dear all,
    My client wants accounts receivable and collections reports project wise. are there any reports in PS which satify this requirements. If no, pls suggest me how to cater to this requirement.
    Pls help me on this issue.
    Thank you very much in advance.
    Regards,
    Vishnu.

    Hi,
    If your cash flow scenario is very complex with partial payments, deferred debt, down payments etc., none of the standard reports including FBL5N / FBL1N will be helpful. If the scenario is fairly simple , FBL5N / FBL1N  should work for you.
    In a complex scenario, you may have develop your own reports based on the basic logic of FBL5N.
    Regards
    Murali

Maybe you are looking for