Credits should be excluded from in the dunning letter

Hi,
Please suggest.
On my analysis I found only one way - payment terms for open credit items should be very high like 120 days so it will not be picked by dunning procedure.
Kindly advice me any other way to do this?
Please help me...
Thanks
Supriya

Hi Supriya,
The customer should be dunned on outstanding balance only(Dr - Cr)
However if you wish to exclude the credit items:
Step 1: F150
Ste 2: Free selections and you can exclude the values:
BSID-SHKZG - DR/CR indicator "H"
BSID-BSCHL - Posting Key 01
Try other options available also
Rgds
Harmees

Similar Messages

  • How can the dunning letter shows O/S amt and corresponding aging bucket?

    Hi,
    I am going to implement the dunning letter setup in R12. Our user request to have the dunnng letter layout which should show all regular dunning details but also the aging info of the outstanding invoices, i.e. which aging bucket the outstanding amount will be shown. Anybody have idea and help? Thanks a lot.
    Edmond

    Thank you Nagarajan.  I have a dunning letter created in Crystal Reports for our client.  It is fairly limited in scope, it just has the customer name and address, invoice numbers and dates, amounts due and the text they wanted in it.
    I can import it into B1 9.0 and set it as the default for Dunning Letter #1 and it runs, but unlike other formats where there is a DocEntry and/or ObjectID and a ?DocKey@ or ?ObjectId@ parameter, how do I limit the report to just one customer?  Typical document layouts run for the document that's on the screen.  In the dunning process, the report runs once for every customer when the Dunning Letter Method is set to "One Letter per BP".  I have to limit the report to one customer at a time.  Right now, each dunning letter based on the Crystal report is identical and it contains all the data for every customer.
    So, does anyone have any ideas for what selection criteria needs to be included in the Crystal report to have it select just one customer from the dunning wizard tables?  Thanks.
    Michael
    Edit: I created a ?WizardID@ parameter and a ?CardCode@ parameter to limit the report to a single dunning wizard event and a single customer.  While it works fine in Crystal itself, it doesn't work in B1 at all.  I had thought that by limiting the report in this way, it would only create dunning letters for a single customer.

  • Driver program for the Dunning letter SAP Script

    Hello All,
    Can someone please tell me how to find the "Driver program for the Dunning letter SAP Script". I checked the Transaction OB96 but I dont find any Dunning scripts here i.e., the standard Dunning letter SAP Script F150_DUNN_01.
    Is there any Transaction like NACE of logistics for FI module to find the Driver programs. My requirement is to find the Driver program for the Dunning letter SAP Script and have a new Driver program instead of the standard SAP given driver program. Example is in transaction NACE we can change the driver program for Invoice like from RVADIN01 to ZRVADIN01.
    Thanks and Regards,
    SNK.

    Yes you can, using FIBF, change the FM associated with event 1720 like when SapScript is replaced with SmartForms. Look at [Define Dunning Forms (with SAP Smart Forms)|http://help.sap.com/saphelp_46c/helpdata/es/7d/c7a0a535e1d311ba4d0800060d888b/content.htm] for reference.
    But notice
    - PRINT_DUNNING_NOTICE call many FM of the same FG which share the same global data area.
    - During following upgrades of your system you will have to manage a copy of standard.
    Regards,
    Raymond

  • What should be excluded from Time machine backups?

    I was looking at the Time Machine options and it is showing my external hard drive( Seagate) as being excluded from backups. Is that correct? If not, how do I correct. Seagate is grayed out & does not appear it can be changed. I recently added SuperDuper to my Mac, so not sure if that is the reason.
    I appreciate any help to my question. Thanks!

    For some guidance see:
    11. What should I exclude, and what should I not exclude?
    http://pondini.org/TM/11.html

  • How can I add a Website Project in a solution that should be excluded from source control?

    Using VS 2013 update 4
    I currently have a solution with a couple of Class Library Projects and Web Application Projects and all of these are bound to a source control (VS Online). Now I added an Existing Website Project in the same solution by choosing a Local IIS instance. However,
    I don't want this Website Project to be in source control.
    I have tried File > Source Control > Advanced > Change Source Control ... and then clicked on the website project and then clicked Unbind. By doing this, it seems that the project was unbound. However, as soon as I close the solution it asks me
    to save the .sln file and seems that it restored the Scc*** info in the file.
    I also tried editing the .sln file and set the SccProjectEnlistmentChoice* = 0 (of the website project, under GlobalSection) and then set the ProjectSection of the WebsiteProject to 
    SccProjectName = ""
    SccAuxPath = ""
    SccLocalPath = ""
    SccProvider = ""
    instead of "SAK". This actually worked for me but everytime I open the solution, Visual Studio alerts an error saying "Unspecified error". This is the closest I got into solving this.
    Is there a proper way of doing this? I think the proper way should be the "Unbind" method but it seems that it's not working as expected.
    Let me know of other solutions.
    Cheers!

    Hi Karlo Medallo,
    Since this issue is related to the VS Online, I am moving your thread into the
    Visual Studio Online
    Forum for dedicated support. Thanks for your understanding.
    Best Regards,
    Jack
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Something is preventing me from typing the small letter "S" while in netscape email.

    I have used Spybot to and have deleted cookies that are listed, which appear to clean up the problem for a short while, but then the problem returns. I am not sure if it happens while using other email providers I use.

    Do all other letters and keys work?
    Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Firefox/Tools > Add-ons > Appearance).
    *Do NOT click the Reset button on the Safe Mode start window or otherwise make changes.
    *https://support.mozilla.org/kb/Safe+Mode
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

  • Dunning letter

    hi experts,
    iam asked to modify one standard sapscript and respective print program of dunning letter , for fi module. for tcode f150. original object is displaying dunning letter output for each customer. when i copied the same object and tried to execute, output is nil. i activated each and every include program etc, but in vain. according to FI consultant they dont maintain application in NACE. so i dnt know how to interlink print program and sapscript, in the original print program form name is not mentioned, i dnt know how the output is displayed in the form of sapscript.
    my requirement is as follows
    The customer is sent the gentle reminder letter for the out standing balances to be received by them. When ever the dunning program is run based on the dunning procedure assigned in the customer master and the level in the customer master, F150 program should be able to print the dunning letter for the customer correspondence.
    MY STANDARD PROGRAM IS FOLLOWS
    REPORT RFMAHN20 MESSAGE-ID FM NO STANDARD PAGE HEADING.
    declaration for dunning lists
    INCLUDE RFMAHNXXTOP.
    tables declaration
    TABLES: T001.
    declaration for independend forms
    INCLUDE RFMAHNXXFORM.
    declaration
    DATA: BEGIN OF MHNK_ACC,
            KOART       LIKE MHNK-KOART,
            BUKRS       LIKE MHNK-BUKRS,
            KUNNR       LIKE MHNK-KUNNR,
            LIFNR       LIKE MHNK-LIFNR,
            KONTO       LIKE MHNK-KUNNR,
            SELKEY      LIKE SY-TABIX,
            L_INCL      LIKE F150V-L_INCL,
            HSORT1(16)  TYPE C,
            HSORT2(16)  TYPE C,
            HSORT3(16)  TYPE C,
            HSORT4(16)  TYPE C,
            HSORT5(16)  TYPE C,
          END OF MHNK_ACC.
    declaration
    DATA:   T_MHNK     LIKE MHNK     OCCURS 10 WITH HEADER LINE.
    DATA    T_MHNK_ACC LIKE standard table of MHNK_ACC
              with key koart bukrs konto  WITH HEADER LINE.
    parameters & select options
    SELECTION-SCREEN BEGIN OF BLOCK 1 WITH FRAME TITLE TEXT-001.
    SELECT-OPTIONS: P_KOART FOR MHNK-KOART,
                    P_BUKRS FOR MHNK-BUKRS,
                    P_KUNNR FOR MHNK-KUNNR,
                    P_LIFNR FOR MHNK-LIFNR.
    SELECTION-SCREEN END OF BLOCK 1.
    INITIALIZATION.
      H_REPID               = SY-REPID.
      H_ACTVT               = '13'.        "display dunning history
      H_TABNAME_HEADER      = 'MHNK_ACC'.
      H_TABNAME_ITEM        = 'MHNK_EXT'.
      H_SET_PF_STATUS       = 'SET_PF_STATUS'.
      H_USER_COMMAND        = 'USER_COMMAND_0001'.
      H_VARIANT-REPORT      = H_REPID.
      H_VARIANT-LOG_GROUP   = '0001'.
      H_VARIANT-HANDLE      = '0001'.
      H_LAYOUT-DETAIL_POPUP = 'X'.
    START-OF-SELECTION.
      select the information from MHNK
      SELECT * FROM MHNK INTO  TABLE T_MHNK
                         WHERE KOART IN P_KOART AND
                               BUKRS IN P_BUKRS AND
                               KUNNR IN P_KUNNR AND
                               LIFNR IN P_LIFNR.
      build the tables for the listviewer
      PERFORM CREATE_TABLES    TABLES   T_MHNK T_MHNK_ACC T_MHNK_EXT.
    END-OF-SELECTION.
      fill the fieldcatalog
      PERFORM FILL_FIELDCAT TABLES   T_FIELDCAT
                            USING    H_TABNAME_HEADER H_TABNAME_ITEM.
      determine the keyinfo
      PERFORM FILL_KEYINFO  CHANGING H_KEYINFO.
      register the list events
      PERFORM REGISTER_EVENTS TABLES T_EVENTS.
    Check if default-variant is existing (default or user-default )
    h_variant-variant has to be empty for this check, otherwise it is
    checked whether this variant is existing.
      H_VARIANT-VARIANT = SPACE.
      CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
           EXPORTING
                I_SAVE        = 'A'
           CHANGING
                CS_VARIANT    = H_VARIANT
           EXCEPTIONS
                WRONG_INPUT   = 1
                NOT_FOUND     = 2
                PROGRAM_ERROR = 3
                OTHERS        = 4.
      IF SY-SUBRC = 2.
      default-variant not existing, therefor get variant 0
        H_VARIANT-VARIANT = '0'.
      ELSEIF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE 'S' NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      display the list
      CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
           EXPORTING
                I_INTERFACE_CHECK        = ' '
                I_CALLBACK_PROGRAM       = H_REPID
                I_CALLBACK_PF_STATUS_SET = H_SET_PF_STATUS
                I_CALLBACK_USER_COMMAND  = H_USER_COMMAND
                IS_LAYOUT                = H_LAYOUT
                IT_FIELDCAT              = T_FIELDCAT[]
                IT_EXCLUDING             =
                IT_SPECIAL_GROUPS        =
                it_sort                  = t_sort[]
                IT_FILTER                =
                IS_SEL_HIDE              =
    *--              i_screen_start_column    = 5
    *--              i_screen_start_line      = 5
    *--              i_screen_end_column      = 80
    *--              i_screen_end_line        = 25
                I_DEFAULT                = 'X'
                I_SAVE                   = 'A'
                IS_VARIANT               = H_VARIANT
                  IT_EVENTS                = T_EVENTS[]
                IT_EVENT_EXIT            =
                I_TABNAME_HEADER         = H_TABNAME_HEADER
                I_TABNAME_ITEM           = H_TABNAME_ITEM
                I_STRUCTURE_NAME_HEADER  =
                I_STRUCTURE_NAME_ITEM    =
                IS_KEYINFO               = H_KEYINFO
                IS_PRINT                 =
           IMPORTING
                E_EXIT_CAUSED_BY_CALLER  =
                ES_EXIT_CAUSED_BY_USER   =
           TABLES
                T_OUTTAB_HEADER          = T_MHNK_ACC
                T_OUTTAB_ITEM            = T_MHNK_EXT
           EXCEPTIONS
                PROGRAM_ERROR            = 1
                OTHERS                   = 2.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    *&      Form  FILL_FIELDCAT
          text
         -->P_T_FIELDCAT  text                                           *
         -->P_H_TABNAME_HEADER  text                                     *
         -->P_H_TABNAME_ITEM  text                                       *
    FORM FILL_FIELDCAT TABLES TI_FIELDCAT STRUCTURE T_FIELDCAT
                       USING  I_HEADER TYPE SLIS_TABNAME
                              I_ITEM   TYPE SLIS_TABNAME.
    create the header fieldcat
      PERFORM APPEND_SEL_FIELDS  TABLES TI_FIELDCAT
                                 USING  I_HEADER.
      CLEAR TI_FIELDCAT.
      TI_FIELDCAT-TABNAME       = I_HEADER.
      TI_FIELDCAT-FIELDNAME     = 'KOART'.
      TI_FIELDCAT-SELTEXT_L     = TEXT-052.
      TI_FIELDCAT-SELTEXT_M     = TEXT-052.
      TI_FIELDCAT-SELTEXT_S     = TEXT-052.
      TI_FIELDCAT-REPTEXT_DDIC  = TEXT-052.
      TI_FIELDCAT-REF_FIELDNAME = 'KOART'.
      TI_FIELDCAT-REF_TABNAME   = 'MHNK'.
      APPEND TI_FIELDCAT.
      CLEAR TI_FIELDCAT.
      TI_FIELDCAT-TABNAME       = I_HEADER.
      TI_FIELDCAT-FIELDNAME     = 'BUKRS'.
      TI_FIELDCAT-SELTEXT_L     = TEXT-051.
      TI_FIELDCAT-SELTEXT_M     = TEXT-051.
      TI_FIELDCAT-SELTEXT_S     = TEXT-051.
      TI_FIELDCAT-REPTEXT_DDIC  = TEXT-051.
      TI_FIELDCAT-REF_FIELDNAME = 'BUKRS'.
      TI_FIELDCAT-REF_TABNAME   = 'MHNK'.
      APPEND TI_FIELDCAT.
      CLEAR TI_FIELDCAT.
      TI_FIELDCAT-TABNAME       = I_HEADER.
      TI_FIELDCAT-FIELDNAME     = 'KONTO'.
      TI_FIELDCAT-SELTEXT_L     = TEXT-050.
      TI_FIELDCAT-SELTEXT_M     = TEXT-050.
      TI_FIELDCAT-SELTEXT_S     = TEXT-050.
      TI_FIELDCAT-REPTEXT_DDIC  = TEXT-050.
      TI_FIELDCAT-REF_FIELDNAME = 'KONTO'.
      TI_FIELDCAT-REF_TABNAME   = 'F150V'.
      APPEND TI_FIELDCAT.
      CLEAR TI_FIELDCAT.
      TI_FIELDCAT-TABNAME       = I_HEADER.
      TI_FIELDCAT-FIELDNAME     = 'L_INCL'.
      TI_FIELDCAT-SELTEXT_L     =  TEXT-041.  " Kennz: Mahn. gedruckt
      TI_FIELDCAT-REPTEXT_DDIC  = 'L_INCL'.
      TI_FIELDCAT-REF_FIELDNAME = 'L_INCL'.
      TI_FIELDCAT-REF_TABNAME   = 'F150V'.
      APPEND TI_FIELDCAT.
      clear ti_fieldcat.
      ti_fieldcat-tabname       = 'MHNK_EXT'.
      ti_fieldcat-fieldname     = 'COMP_CURR'.
      ti_fieldcat-seltext_l     = text-053.
      ti_fieldcat-seltext_m     = text-053.
      ti_fieldcat-seltext_s     = text-053.
      ti_fieldcat-ref_fieldname = 'WAERS'.
      ti_fieldcat-ref_tabname   = 'MHNK'.
      append ti_fieldcat.
    perform append_sort_fields tables ti_fieldcat
                                using  i_header h_sort_info 'H'.
    create the item fieldcat
      PERFORM APPEND_SEL_FIELDS  TABLES TI_FIELDCAT
                                 USING  I_ITEM.
    generate fieldcat
      CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
           EXPORTING
                I_PROGRAM_NAME         = H_REPID
                I_INTERNAL_TABNAME     = I_ITEM
                I_STRUCTURE_NAME       = 'MHNK'
                I_CLIENT_NEVER_DISPLAY = 'X'
               i_inclname             = 'RFMAHNXXTOP'
           CHANGING
                CT_FIELDCAT            = TI_FIELDCAT[]
           EXCEPTIONS
                INCONSISTENT_INTERFACE = 1
                PROGRAM_ERROR          = 2
                OTHERS                 = 3.
    for amounts in company currency establish link to MHNK_EXT-COMP_CURR
    so that summation in ALV is possible
      loop at ti_fieldcat.
        if ti_fieldcat-fieldname = 'SALHW' or
           ti_fieldcat-fieldname = 'FAEHW' or
           ti_fieldcat-fieldname = 'ZINHW' or
           ti_fieldcat-fieldname = 'FAMSH' or
           ti_fieldcat-fieldname = 'MHNGH'.
              ti_fieldcat-cfieldname = 'COMP_CURR'.
              ti_fieldcat-ctabname = 'MHNK_EXT'.
              modify ti_fieldcat.
        endif.
      endloop.
      CLEAR TI_FIELDCAT.
      TI_FIELDCAT-TABNAME       = I_ITEM.
      TI_FIELDCAT-SELTEXT_L     = TEXT-042. " 'Nur gedruckte Posten'.
    ti_fieldcat-seltext_m     = text-'Nur gedr. Posten'.
    ti_fieldcat-seltext_s     = 'Nur gedr. Post.'.
      TI_FIELDCAT-FIELDNAME     = 'L_INCL'.
      TI_FIELDCAT-REPTEXT_DDIC  = 'L_INCL'.
      TI_FIELDCAT-REF_FIELDNAME = 'L_INCL'.
      TI_FIELDCAT-REF_TABNAME   = 'F150V'.
      APPEND TI_FIELDCAT.
    perform append_sort_fields tables ti_fieldcat
                                using  i_item h_sort_info 'H'.
    select the fields to be shown
      PERFORM HIDE_ALL_FIELDS TABLES TI_FIELDCAT USING I_HEADER.
    select the fields to be shown
      PERFORM HIDE_ALL_FIELDS TABLES TI_FIELDCAT USING I_ITEM.
    ENDFORM.                               " FILL_FIELDCAT
    *&      Form  CREATE_TABLES
          text
    -->  p1        text
    <--  p2        text
    FORM CREATE_TABLES TABLES TI_MHNK     STRUCTURE MHNK
                              TI_MHNK_ACC STRUCTURE MHNK_ACC
                              TI_MHNK_EXT STRUCTURE MHNK_EXT.
      data : begin of comp_curr,
             bukrs like mhnk-bukrs,
             waers like mhnk-waers,
           end of comp_curr.
      data bukrs_tab like comp_curr occurs 0 with header line.
    sort the table
      SORT TI_MHNK BY KOART BUKRS KUNNR LIFNR ASCENDING.
    build t_mhnk_ext
      LOOP AT TI_MHNK.
      check authority
        PERFORM CHECK_AUTHORITY USING    '13' TI_MHNK-KOART TI_MHNK-BUKRS
                                CHANGING H_AUTHORITY_OK.
        IF H_AUTHORITY_OK = SPACE.
          CONTINUE.
        ENDIF.
      save wa
        MHNK = TI_MHNK.
      create item entry
        MOVE-CORRESPONDING MHNK TO TI_MHNK_EXT.
        IF TI_MHNK_EXT-KOART = 'D'.
          TI_MHNK_EXT-KONTO = TI_MHNK_EXT-KUNNR.
        ELSE.
          TI_MHNK_EXT-KONTO = TI_MHNK_EXT-LIFNR.
        ENDIF.
        TI_MHNK_EXT-HSORT1 = <F1>.
        TI_MHNK_EXT-HSORT1 = <F2>.
        TI_MHNK_EXT-HSORT1 = <F3>.
        TI_MHNK_EXT-HSORT1 = <F4>.
        TI_MHNK_EXT-HSORT1 = <F5>.
      check if item has been printed already
        IF NOT TI_MHNK_EXT-PRNDT IS INITIAL.
          TI_MHNK_EXT-L_INCL = 'X'.
        ELSE.
          TI_MHNK_EXT-L_INCL = SPACE.
        endif.
        read table bukrs_tab with key bukrs = ti_mhnk_ext-bukrs.
        if sy-subrc <> 0.
          select single * from t001 where bukrs = ti_mhnk_ext-bukrs.
          if sy-subrc = 0.
            bukrs_tab-waers = t001-waers.
            bukrs_tab-bukrs = ti_mhnk_ext-bukrs.
            append bukrs_tab.
          endif.
        endif.
        ti_mhnk_ext-comp_curr = bukrs_tab-waers.
        APPEND TI_MHNK_EXT.
      create header entry
        MOVE-CORRESPONDING MHNK TO TI_MHNK_ACC.
        IF TI_MHNK_ACC-KOART = 'D'.
          TI_MHNK_ACC-KONTO = TI_MHNK_ACC-KUNNR.
        ELSE.
          TI_MHNK_ACC-KONTO = TI_MHNK_ACC-LIFNR.
        ENDIF.
        COLLECT TI_MHNK_ACC.
      ENDLOOP.
    determine if account has at least one printed dunning
      LOOP AT TI_MHNK_ACC.
        READ TABLE TI_MHNK_EXT WITH KEY  KOART  = TI_MHNK_ACC-KOART
                                         BUKRS  = TI_MHNK_ACC-BUKRS
                                         KUNNR  = TI_MHNK_ACC-KUNNR
                                         LIFNR  = TI_MHNK_ACC-LIFNR
                                         KONTO  = TI_MHNK_ACC-KONTO
                                         L_INCL = 'X'.
        IF SY-SUBRC = 0.
          TI_MHNK_ACC-L_INCL = 'X'.
          MODIFY TI_MHNK_ACC.
        ENDIF.
      ENDLOOP.
    ENDFORM.                               " CREATE_TABLES
    *&      Form  FILL_KEYINFO
          text
         <--P_H_KEYINFO  text                                            *
    FORM FILL_KEYINFO CHANGING E_KEYINFO TYPE SLIS_KEYINFO_ALV.
      MOVE 'KOART' TO : E_KEYINFO-HEADER01,E_KEYINFO-ITEM01.
      MOVE 'BUKRS' TO : E_KEYINFO-HEADER02,E_KEYINFO-ITEM02.
      MOVE 'KONTO' TO : E_KEYINFO-HEADER03,E_KEYINFO-ITEM03.
    ENDFORM.                               " FILL_KEYINFO
    *&      Form  SET_PF_STATUS
          text
         -->P_RT_EXTAB  text                                             *
         -->P_TYPE  text                                                 *
         -->P_SLIS_T_EXTAB  text                                         *
    FORM SET_PF_STATUS USING I_EXTAB TYPE SLIS_T_EXTAB.
      SET PF-STATUS 'HIST_MAX' EXCLUDING I_EXTAB.
    ENDFORM.                               " SET_PF_STATUS
    *&      Form  USER_COMMAND_0001
          text
    -->  p1        text
    <--  p2        text
    FORM USER_COMMAND_0001 USING I_UCOMM     LIKE SY-UCOMM
                                 I_SELFIELD  TYPE SLIS_SELFIELD.
      CASE I_UCOMM.
        WHEN 'DISP'.
          PERFORM COMMAND_DISP USING I_SELFIELD.
      ENDCASE.
    ENDFORM.
    *&      Form  COMMAND_DISP
          text
    -->  p1        text
    <--  p2        text
    FORM COMMAND_DISP CHANGING E_SELFIELD TYPE SLIS_SELFIELD.
    declaration
      DATA: TH_MHND     LIKE MHND OCCURS 10 WITH HEADER LINE,
            TH_MHNK     LIKE MHNK OCCURS 1 WITH HEADER LINE.
    determine the current line
      IF E_SELFIELD-TABNAME = H_TABNAME_ITEM.
        READ TABLE T_MHNK_EXT INDEX E_SELFIELD-TABINDEX.
        MOVE-CORRESPONDING T_MHNK_EXT TO TH_MHNK.
        APPEND TH_MHNK.
      ELSE.
        MESSAGE E481.
        EXIT.
      ENDIF.
    determine the mhnd entries for the actual mhnk
      SELECT * FROM  MHND INTO TABLE TH_MHND
             WHERE  LAUFD       = TH_MHNK-LAUFD
             AND    LAUFI       = TH_MHNK-LAUFI
             AND    KOART       = TH_MHNK-KOART
             AND    BUKRS       = TH_MHNK-BUKRS
             AND    KUNNR       = TH_MHNK-KUNNR
             AND    LIFNR       = TH_MHNK-LIFNR
             AND    CPDKY       = TH_MHNK-CPDKY
             AND    SKNRZE      = TH_MHNK-SKNRZE
             AND    SMABER      = TH_MHNK-SMABER
             AND    SMAHSK      = TH_MHNK-SMAHSK.
    change the dunning data
      CALL FUNCTION 'EDIT_DUNNING_DATA'
           EXPORTING
                I_MHNK     = TH_MHNK
                I_XDISPLAY = 'X'
           TABLES
                T_MHND     = TH_MHND
                T_MHNK     = TH_MHNK
           EXCEPTIONS
                OTHERS     = 1.
    ENDFORM.                               " COMMAND_DISP
    *&      Form  REGISTER_EVENTS
          text
         -->P_T_EVENT  text                                              *
    FORM REGISTER_EVENTS TABLES T_EVENT TYPE SLIS_T_EVENT.
    determine the events
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
           EXPORTING
                I_LIST_TYPE     = 1
           IMPORTING
                ET_EVENTS       = T_EVENT[]
           EXCEPTIONS
                LIST_TYPE_WRONG = 1
                OTHERS          = 2.
    set top of page form
      READ TABLE T_EVENT WITH KEY NAME = SLIS_EV_TOP_OF_PAGE.
      IF SY-SUBRC EQ 0.
        T_EVENT-FORM = 'TOP_OF_PAGE'. MODIFY T_EVENT INDEX SY-TABIX.
      ENDIF.
    set top of list form
      READ TABLE T_EVENT WITH KEY NAME = SLIS_EV_TOP_OF_LIST.
      IF SY-SUBRC EQ 0.
        T_EVENT-FORM = 'TOP_OF_LIST'. MODIFY T_EVENT INDEX SY-TABIX.
      ENDIF.
    set end of list
      READ TABLE T_EVENT WITH KEY NAME = SLIS_EV_END_OF_LIST.
      IF SY-SUBRC EQ 0.
        T_EVENT-FORM = 'END_OF_LIST'. MODIFY T_EVENT INDEX SY-TABIX.
      ENDIF.
    ENDFORM.                               " REGISTER_EVENTS
          FORM TOP_OF_PAGE                                              *
    FORM TOP_OF_PAGE.
      PERFORM BATCH-HEADING(RSBTCHH0).
    ENDFORM.                               " TOP_OF_PAGE
          FORM TOP_OF_LIST                                              *
    FORM TOP_OF_LIST.
    *- Standardseitenkopf fuellen -
      MOVE '0'      TO BHDGD-INIFL.
      MOVE SY-LINSZ TO BHDGD-LINES.
      MOVE SY-UNAME TO BHDGD-UNAME.
      MOVE SY-REPID TO BHDGD-REPID.
      CLEAR: LINE.
      WRITE TEXT-040 TO BHDGD-LINE2.
    ENDFORM.
          FORM END_OF_LIST                                              *
    FORM END_OF_LIST.
      WRITE: / TEXT-039.
    ENDFORM
    regards
    maaya

    Hi,
    I copied your program and executed it. First of all, I dont think its a print program for any script. Its a plain ALV report program. I think you mis-understood the requirement or I totally lost the question.
    Make sure you are changing the correct program.
    Regards
    Aneesh.

  • Dunning Letter Design & Aging report

    Hello Experts,
    I have a few doubts in B1 Sales AR -> Dunning and Aging Reports.
    1. How do we incorporate our own letter format for dunning letters? I looked for PLD's, but nothing was available in the print preview screen.
    2. When we execute Customer Receivables Aging report, what is the significance of the column "Future Remit"? In our B1 instance, the receivables that are due 60 or 90 days from current date are not appearing in their respective columns.
    Please advise on how to proceed
    With Regards,
    PS: We are running B1 2005-B / MS-SQL 2005

    Hi Kaatss,
    You should be able to find the Dunning letter formats by clicking on the layout designer button and then from the windows selecting the dunning letter formats from the 'Choose Document Type'.  They go by the ID of DUN0... DUN09.
    As for the columns the 60 and 90 columns show the invoices (values) that are overdue by 60 and 90 days respectively.
    The Future Remit column shows invoices that are still within the due date.  So if you raise two invoice with 60 and 90 day payment terms, but they are still within their due date, their values will appear in the future remit column.
    I hope this helps.  I use 2005A so I hope there are no differences.
    Damian

  • 'Dunning Letter Print from Dunning Letter Generate'

    hi,
    How can i run the "Dunning Letter Print from Dunning Letter Generate" standard program without runing the spwaned program called 'Dunning Letter Generate'.I mean i want to run the 'Dunning Letter Print from Dunning Letter Generate'(execution method: report) independently.
    I need to pass the parameters to the 'Dunning Letter Print from Dunning Letter Generate' directly instead of passing to the spwaned program ''Dunning Letter Generate".
    Thanks
    Devender

    Hi Gareth,
    New parameters to be add are:
    Tier : <xxxx>
    Service Segment: <xxxxx>
    Account Manager: <xxxx>
    Location where I am picking these 3:
    navigation:select any AR responsibility
    customer->standard(query with any customer)->customer address
    we have enabled 'site use information' dff in customer address window, from this dff we are taking these 3 parameters.
    reason to add these 3 parameters:
    we cant treat all the customers same. so we need to send some smooth(no harsh) dunning letters to some of our most trusted customers. so how can we identify gud customers in the list.
    so we have enabled site use information dff. those customers who is have values for these 3 parameters. will be treated as v good and reguler customers for us. so for them we can send other dunning letters.
    note*: this is to identify the customers like reguler customers,non requler customers.
    bez in spwaned program we have parameters like 1.customer low 2.customer high. thats it .so it is very difficult to find out the nature of customer.
    pls advice me on this..to proceed further..
    Thanks
    Devender

  • No printing date is printed while running the dunning activity?

    Hi SAP Experts,
    The dunning proposal is created successfully but when I run the  dunning activity the dunning level is updated with issue date but the printing date is not printed. Can any one let me know the root cause of this issue.
    Thanks

    Hi Moin,
    You are right in saying, that the print date field in the dunning history gets updated after the dunning activity is executed successfully.
    This is a standard SAP functionality and if the dunning level is getting incremented, then the print date field should also get updated in the Dunning History.
    Is this happening for all accounts or some of them?
    As a starting point, I would recommend you to start seeing the application logs for the Dunning Activity, once it gets completed. 
    Hope it helps...
    Thanks,
    Amlan

  • FI Dunning Letter: Requirement to get Sales Organisation of the letter

    Hi folks,
    I would like to know how to get the Sales Organisation of the dunning letter. Basically the dunning is performed from transaction f150 and the company code is the factor for deciding the texts to be printed on it. Now I have a requirement where I have to print a few texts on the dunning letter based on the Sales Organization.
    Can you please help me identify from where I'll get the Sales Org.
    Thanks in advance.
    Rahul

    Hi
    You don't need to change the print because sold to party and bill to party are both customer for FI, so u need only to know the right customer code.
    Max

  • AR Statement /Dunning Letter Report Issue

    Hi Guys,
    I have an issue in the Customer statement report in XMLP. There are two Concurrent Program for this Print Statement (i.e; Print Statement and Statement Generate Program) Here Print Statement runs with respect to the ARXSGPO.rdf file and Statement Generate Program runs with respect to the spawned program.
    I followed the following steps to view the output in PDF using XMLP.
    1. I used ARXSGPO.rdf which is from "Print Statement" Concurrent Program.
    2. I have given the exact short name(ARXSGPO) of Print Statement to the Defination and Template also attachment in XMLP responsibility.
    3. When i see the output after both parent (Print Statement) and child(Statement Generate Program) completed successfully. I can able to see the output only in XML format. Obvisouly it should display in PDF format right?..
    Do we need any other steps to go through to achieve this AR statement report. Same issue i have with the Dunning letter report. Please drive me if any one already worked for these two reports in xmlp.
    Awaiting your comments
    with regards
    Prabu

    Hi Prabu,
    Please refer to solution on forum:
    AR Statement is not displaying PDF output where it used to display earlier.
    Regards,
    Gareth
    Blog: http://garethroberts.blogspot.com/

  • Dunning Letter with dued invoices copies attached

    Hi experts.
    The client is requesting to attach to the dunning letter copies from each dunned open invoice in a contract account.
    In other words, the dunning correspondence delivered to the customer will contain:
    1. A first page, with dunning information, as a dunning letter we all use.
    2. Other pages, as much as necessary, each one for each invoice dunned. Like physical copies from original invoice.
    How should we implement this?
    Best regards.

    Hello,
    I'm not too sure whether this can be achieved via Contract Account. But you can do in another way <workaround?>
    In FPSEC1, you can create a security deposit. Here you can upload the scanned documents.
    As security deposit you post would be a statistical posting <no posting to GL>, it should not be an issue to you.
    Or else alternatively if you have CRM also in your project, you can get this done by them. In T-Code CIC0/CICO, one can view the correspondence letters <I remember that you need to have a 'Z' program for this..check with your CRM colleagues>.
    Rgds
    Rajendra

  • Cannot print preview Dunning Letter

    My client is using SAP B1 2005 SP1 Patch 42.
    Dunning term and dunning level has been properly set up.
    We have also design the dunning letter for dunning level 1, eg called it DunningLetter#1
    When using Dunning Wizard, SAP prints the letter for dunning letter for dunning level 1 with no problem. However it does not allow preview on the screen.,
    Therefore, we try to running Customer Ageing by Due date so that we can see the dunning level, if needed change it. However, when try to print preview dunning letter, it shows nothing on the screen. However, it can be printed directly to the printer.
    We received feedback from the SAP Business One forum that this is a known limitation. Is there any plan to allow Print Preview for Dunning Letter?
    In addition, we notice that the Dunning Letter format printed on Customer Ageing Report by Due Date is not the same format as the version in Dunning Wizard.  It looks like we need to design the Letter at both place.
    Please advise.

    Hi
    Please follow this link 
    https://websmp202.sap-ag.de/notes
    You should have S user id and Password
    After get in to the portal please give your Note number
    Regards
    Rashid

  • Creation of Dunning Leter

    Hi,
      explain the steps to create dunning letter?
      how should i retrieve the letter from PLD to dunning letter levels?

    Hi Subashini
    You can get to the dunning terms from Administration > Setup > Business Partners > Dunning Terms, or select the Navigation Arrow next to Dunning Terms on the Payment Terms TAB of the BP master. You can also go to Administration > Setup > Business Partners > Dunning Levels.Then click on the PLD (Pencil) and select the letter you want to edit.
    The dunning terms can be set up per customer or group of customers if there are multiple ways of treating customers. If not then you will only need 1 dunning term. On the dunning term, select the first row and choose the level letter for it (usually 1). Then set the parameters such as effective after (days) - based on due date. A new line will automatically be added as you tab through the columns. On the next row select the next level letter (usually 2) and so on. If you only need 3 levels for example, then you only need to change the PLD for the level letters selected.
    The level letter will be selected based on the days over the due date and whether or not the BP has been dunned before. Under the accounting TAB of the BP Master, it will display the last dunning run date and level for each BP.
    Hope this helps
    Kind regards
    Peter Juby

Maybe you are looking for