Dunning letter script form translation

Hi!
I am translating dunning script form to chinese language(ZH), original script form is in Enlgish language.
I have selected langage ZH key in the header data of form, but while creating the form in chinese langauge system is giving following error:
Form *ZSOLLECITON01_* language EN should not be translated to ZH
Message no. TD114
The same form name is available in EN language.
I am using transaction code SE71 where  I am inserting above form name and langauge key ZH and try to create form?
Can any one explain me how to create above form in ZH language?
regs,
Ramesh

Hi,
Please copy that from.
Goto SE71
Give ur form name and required language click on change
and click ok
It opens the form
In menu options form--->copyfrom
Give your form name and original language
Save and Activate.
It resolves ur problem.
Regards,
Venkat

Similar Messages

  • 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

  • Script or smartform for Dunning Letter????

    Hi All, I have to develop a SF for Dunning Letter. When I checked in standard Program for Dunning Letter printing, there SSF FM.... But my doubt is can we go for Smartforms??? When I checked in the customization, there is a SF for dunnig letter.. but they didnot use it... So Kindly answer me...

    Hi Jyothsna,
    Do we need to write Z driver program?
    You donot nee dto write a a driver program.There is a standar program that calls the smartform.if you have to make chnages in it for your requirment, you can just copy this into a z program and change it.
    -- If Yes, where to assign program??
    SPRO -> fin accounting -> acc recv & payables -> business transaction -> dunning -> printout -> Assign dunning Form.
    -- Cant we go for the Standard prog as it also has the SSF FM??
    as i mentioned above, yes you have to use the standard program. Only thing if you intend to make changes in program then you will have to copy it to a z program.

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

    I would like to display 4 levels in script for dunning letter BG for Bank Guarantee.
    Bank Guarantee Dunning letters (BGDL) are reminders that are sent out to customers with overdue and outstanding Bank guarantees.
    In KONE Germany 4 dunning levels will be used; the 4 th dunning level represent the legal level.
    Officially Germany has only 3 dunning levels for output but use the 4 dunning level plus a manual to-be enter dunning block, to track the legal cases.
    The first dunning letter will be sent out to the customer (AR) if he has outstanding BG that are overdue.
    Dunning level 2 will be used for outstanding open items that are 14 days overdue.
    Dunning level 3 will apply to outstanding open items that are 28 days overdue.
    Dunning level 4 represent the legal dunning after 42 days overdue and special dunning block after given to layer or collection agency. No dunning print out.
    I copied standard script and doing changes .
    Configuration location is given below.
    Financial Accounting > Accounts Receivable and Accounts Payable > Business Transactions > Dunning > Dunning Procedure > Define Dunning Procedures (F150)
    u2022     Program Name: RIPRJT00 and form name  F150_BE_DUNN_01.
    Any body knows dunning letter form user want to display form in 4 levels .
    1st level contain different infomation
    2nd level contain different information
    3rd level contain different information
    4th level contain different information
    user is creating test data for each form when he select first level it should trigger first level dunning information same way all levels.
    Which base it will trigger I am thinking it will trigger by text element
    1st level text element 511
    2nd level text element 512
    3rd level text  element 513
    4th level text element 514
    Please suggest me the logic for doing.

    We have customized Dunning Letter
    It used to work perfectly sometime back ...I dont know what went wrong suddently it is giving error when tried to run Custom Dunning Letter Print gving error "The file cannot be opened because it has no pages." [/b
    Not able to understand what might be wrong??
    I checked data for one customer in EBS (Customers>Customer Standard>Input customer number (xxxxxx)>Button Find>Button Ok>Button Open>Tab Characteristics) Even though in EBS form I saw that Language field contains value but respective field in DB was empty.
    My question when we run Dunning Letter from which level does oracle picks up the language??
    Is it from Address level of the customer??
    We have different environments which are clones of production. when I tried to run Dunning Letter in DEV environment which is used for building and testing which was a recent clone of production, it worked for me...not able to understand why it is not working in production??
    Best, KK

  • Dunning letter details

    Hi All,
      I need the the table name and fields for the follwing mentioned fields that are used in Dunning letter.
    Debtors name,
    street address,
    city,
    state,
    Month day,year,
    account balance,
    account number,
    debtor,
    due amount.
    Thanks,
    Rakesh.

    Hi Rakesh,
    In SAP script / Forms you can found back the table names for printing:
    Form: F150_DUNN_01
    Some tables are:
    MHND                           Dunning Data                              
    MHNDO                          Dunning data version before the next chang
    MHNK                           Dunning data (account entries)            
    MHNKA                          Version administration of dunning changes 
    MHNKO                          Dunning data (acct entries) version before
    Paul

  • Dunning letter via email with invoice attachments

    Hi Experts,
    We have requirement where in dunning letter should be send to customer via email along with invoice attachments.
    We have copied standard script F150_DUNN_02 to custom one as per requirements and configured it in SPRO. We are using BTE 1040 to fetch the customer email address and assign it to structure c_finaa-intad.
    This serves the purpose partially. The email goes to customer with dunning letter as an attachment properly.
    The question here is how to send additional invoice attachments in the same mail? For example, if dunning letter contains 3 line items, then email should have 4 attachments( 1 dunning letter and 3 invoices).
    Is it possible by some config steps? or please suggest me suitable approach to solve the problem.
    Appreciate your help.
    Thanks
    Swati

    Hi Partha,
    Here are the steps that you can follow :
    1. Using following SPRO path assign the dunning form.
    Financial Accounting (New) > Accounts Receivable and Accounts Payable > Business Transactions > Dunning > Printout > Assign Dunning Forms
    2. There is standard BTE (00001040) that is provided by SAP which is called when dunning is run. SAP has also provided sample function module SAMPLE_PROCESS_00001040 to indicate how to use the BTE. The FM imports I_KNA1 strutcure and pass back structure C_FINAA.
    3. Copy the standard FM to custom Z-FM and using I_KNA1-ADRNR fetch customer email address. If email is maintained, set c_finaa-nacha = 'I' and c_finaa-intad - <email>.
    4. You can also set the title of PDF file in email by setting c_itcpo-tdtitle as per requirement.
    5. Goto transaction FIBF. Settings-> Process Modules-> of SAP Application
    6. Add new entry with Process 00001040, application FI-FI and function module as custom FM created in step 3.
    Above steps are enough if you want to send dunning email to customer. If there is a need to send invoices as an attachments along with email then there is a need to enhance the standard FM PRINT_DUNNING_NOTICE. I used following approach to achieve the purpose.
    a. I created another custom FM to send invoices which I am calling from PRINT_DUNNING_NOTICE. For this, I am using implicit enhancement option to modify standard code. With this option, I am able to send 2 emails back-to-back one with dunning letter and other containing all invoice attachments with respect to dunning letter.
    Let me know, if you need further guidance.
    Regards,
    Swati

  • Dunning Letter for transaction F150

    Hi,
    I have developed a dunning letter , level 2 for transaction F150.
    As per the requirement it should display the balance in the beging rather than in last (as it was before)
    so I coped the print program and did some changes and Assigned that program to my sap script....
    but when i am going in debugging....
    it is taking the old program only...
    Anybody having any idea where to configure my new program??
    Thanks and Best Regards.
    Kusum.

    Hi Dubey,
    You can check the following customizing settings :
    Define Dunning Forms (with SAP Forms)
    We Require some standard u201CSPROu201D settings  :
    The standard settings allow us to create dunning notices using SAP Smart Forms, we must first define the corresponding function module in u201CSPROu201D.
    1. Financial Accounting (New) Financial Accounting Global Settings ( New )  -->Business Transaction Events.
    The SAP Business Framework screen appears.
    2. Choose Settings -> P/S function modules -> ... of an SAP appl. .
        Continue..
    3. Under the Business Transaction Event (BTE) "1720" with application indicator FI-FI, change the function module name and save your entries.
    Standard settings in u201CSPROu201D
    Financial Accounting (New)--> Accounts Receivable and Accounts Payable -->Business Transactions --> Dunning --> Printout ->Assign dunning forms.
    Select u2018Dunning Procedureu2019 and choose u2018Forms for normal dunning procedureu2019
    Choose u2018Company Codeu2019
    Change the name of your dunning form
    I thought, it will work for your requirement.
    Thanks
    Raghava Vakada

  • Invoice number on F150 dunning letter

    Hi,
    We need to have invoice number on the dunning letter on the trans code F150. May I know what are aspects or points we need to suggest to Abapers form the FI point of view
    Thank you
    Chaithra

    hi,
    Henri
    Thanks for your response. May i know in detail about it please. Where to write these sap scripts please.
    Thank you
    Chiathra

  • Changing text into dunning letter

    Hi
    I am trying to change some std text in the dunning letter. But we have some customized form/script for this and not using the std one.And for some reason i am not able to find that form/script.. Could somebody please help me in finding the actual report/FM/script/form which is in use. How to go about it.
    Thanks in advance
    Regards
    Hrishikesh

    Hi,
    Try these tables..
    T047D                            Form selection for legal dunning proceedings
    T047E                            Form selection for dunning notices         
    TD47D                            Form selection legal dunning procedure in loans
    TD47E                            Form selection for dunning notices            
    Thanks,
    Naren

  • Dunning letter split per dunning level

    Hello,
    I have a requirement to print separate dunning letters per level for each customer (2 level procedure, 10days and 17days). The problem is that we have all levels in the dunning letter being printed out now; 0, 1, 2. We probably can live with having 1 and 2, how can we avoid the 0. I have removed the check for box 'print all items' but it still prints any item which has been due for more than a day. I would like only items with level 1 or 2 to be displayed.
    I am seeing some documentation which suggests that we can do that at company code level, but not sure where.

    Hi
    When you have area  0 1 and 2 you can set the values from 1 and to 2 in 0 and 1.
    In you Dunning letter you have to meve the texts to.
    In your sap script /form you can say start on a next page for the next dunning level. When the Header and Footer is set up correct, only (sub)totals by level you can sent it out as 2 letters

  • Dunning letter with smartform

    Hi experts,
    I have to create a form for dunning letter with (smartforms) for the transaction F150
    and really I don't know how I will do it.
    I don't know how to pass the fields run on, identification customer to the formulaire for getting data for display?
    notice in this moment I have letter displayed with the form sapscript Y_F150_DUNN_01, that I have to change the letter to a form with smartforms?

    Hi Mohamed,
    because I did not believe SAP doesn't provide smartforms dunning I checked it.
    In Customizing Financial Accounting->Accounts Receivable and Accounts Payable->Business Transactions->Dunning->Printout the documentation says "Note that you can define dunning forms using either SAPScript or SAP     
    Smart Forms."
    The Docu for "Define Dunning Forms (with SAP Smart Forms)" explains how-to:
    Requirements                                                                               
    The standard settings allow for creating dunning notices using              
    SAPScript. If you wish to print your dunning notices using SAP Smart         
    Forms, you must first define the corresponding function module.              
         1. In Customizing for Financial Accounting, choose Financial             
         Accounting Global Settings ->  Business Transaction Events.              
         The SAP Business Framework screen appears.                               
         2. Choose Settings -> P/S function modules -> ... of an SAP appl. .      
         3. Under the Business Transaction Event (BTE) "1720" with                
         application indicator FI-FI, change the function module in               
         FI_PRINT_DUNNING_NOTICE_SMARTF and save your entries.                                                                               
    SAP provides a predefined example form for dunning notices:                                                                               
    o   F150_DUNN_SF                                                                               
    Activities                                                                               
    1.  Make sure the function module FI_PRINT_DUNNING_NOTICE_SMARTF has       
        been defined (see above).                                                                               
    2.  Create a dunning form or change the example form to meet your          
        requirements for the various dunning notices.                                                                               
    I checked it and it looks really easy!
    Any quetsions? Feel free to ask.
    Regards,
    Clemens
    P.S.: If you don't expect more answers, please close the thread.

  • Dunning letter -smartform - F150_DNN_SF

    hi all,
    am creating a smart form for dunning letter F150_DUNN_SF , we have three levels of dunning based on the past due days.
    level 1 , level 2 and level 3 and each level has its own format for print output. so basically i need to trigger three smart forms for a customer.
    I have created to three forms but functional team assigned it to the dunning level .
    now my question is how these forms are triggered by dunning level and where should i do customization based on the dunning level in order to print the corresponding format the presumption that customer will always have three dunning levels of past due invoices.
    example if there are 20 invoices past due.
    10 Invoices- dunning level 1 ---trigger smartform 1
    5 Invoices-dunning level 2 --trigger smartform 2
    5 Invoices- dunning level 3-trigger smartform 3.
    thanks
    GOVI

    The form trigger by dunning level is part of the dunning procedure configuration in the IMG.  If I understand your question correctly though, it does not make sense for one customer to have multiple dunning levels.  A customer has a single dunning level within a company.  The customer may have various balance ages but only a single dunning level, which is assigned by the dunning program based on the dunning area.

  • F150 : Dunning letter print

    Hi,
    I customized Form for a Dunning letter (level 1) in Tcode FBMP, but when I tried to print a dunning letter I get this message : 'Form ZF150_DUNN_1 does not exist'
    Is there any other customizing point must I do ?
    Please advise
    Regards.

    HI,
    It seems that the dunning form is not assigned properly
    In FBMA  click on dunning procedure - > dunning text - > give Company code -> And check whether form is assigned there
    Atlast   Try OBL6 might give you some idea
    hope this helps
    pbb

  • Dunning letter - F150

    Hello all experts.
    I have a great request, who can help me with some information on dunning letter u2013 transaction code f150.
    I set the type of correspondence, i assigned to the F150_DUNN_01 to form SAPF150V program, i allocated the printing correspondence RFKORD10 to the company code, I created a new dunning area, dunning keys, dunning procedure (FBMP), 
    I set interest rates for calculating penaltys and when i run the transaction f150, it appear the with the positions of customer bills, but i is not penalty, instead appears a line called " dunning tax" in wich the system that divides the balance in 1000.
    I'm interested to appear in dunning the penalty for each line ithemes
    Please can you help me with some information or documentation with something more to the purpose.
    Thank you in advance.

    Hello,
    Into FBMP, at the dunning levels, you have to check "Calculate interests";
    Then you have to Define Interest Calculation Types into OB46 transaction.
    Then into dunning procedure, Define Interest Rates into OB42 transaction.
    Hope my answers will help.
    Regards,
    Aurelien

Maybe you are looking for