Dunning letter option

when i try to acces to dunning letter through Customer Receivables Ageing Form don't appear the columns Letter and Level.
how can i put those columns on to have the possibility to print dunnings letters?
regards,

Hi,
This option was disabled for new customer databases only. Those migrated from 2005 A SP1 keep the feature in.
The motivation was to promote usage Dunning Wizard for generation of Dunning Letters and Aging Report for Customer Statements.
Morever, enhancements introduced recently to Dunning Wizard and generation of dunning letters are not reflected completely if a letter is generated via Aging Report.
Regards,
Peter Dominik
B1 Solution Management
SAP AG

Similar Messages

Dunning Letter Creation in XMLP running into Error

Hi All,
Although I'm trying to create a report from the seeded Dunning Letter concurrent program that is giving the intended XML files but when running the XML Report Publisher Concurrent program, the program is erroring out with the following error:
*****************************************Start of Log *************************************
XML Publisher: Version : 11.5.0 - Development
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XDOREPPB module: XML Report Publisher
Current system time is 11-AUG-2006 09:13:51
XML Report Publisher 5.0
Updating request description
Waiting for XML request
Retrieving XML request information
Preparing parameters
Process template
--XDOException
java.lang.reflect.InvocationTargetException: oracle.xdo.parser.v2.XPathException: Extension function error: Method not found 'set_xslt_locale'
     at oracle.xdo.parser.v2.XSLExtFunctions.getMethod(XSLExtFunctions.java:285)
     at oracle.xdo.parser.v2.XPathExtFunction.evaluateMethod(XPathExtFunction.java:267)
     at oracle.xdo.parser.v2.XPathExtFunction.evaluate(XPathExtFunction.java:225)
     at oracle.xdo.parser.v2.XSLVariable.getValue(XSLVariable.java:205)
     at oracle.xdo.parser.v2.XSLStylesheet.processVariables(XSLStylesheet.java:638)
     at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:503)
     at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:485)
     at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:264)
     at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:150)
     at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:187)
     at java.lang.reflect.Method.invoke(Native Method)
     at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(XSLT10gR1.java:580)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:378)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:197)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:156)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:916)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:869)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:204)
     at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1497)
     at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:913)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:1766)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:1277)
     at oracle.apps.xdo.oa.cp.JCP4XMLPublisher.runProgram(JCP4XMLPublisher.java:807)
     at oracle.apps.fnd.cp.request.Run.main(Run.java:148)
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
Current system time is 11-AUG-2006 09:13:59
**************************************End of Log *******************************************
As u can c from the error, it seems to indicate that I'm using the method 'set_xslt_locale' which evidently I'm not using in my Template. Does anyone 've any ideas as to why this error is been thrown out.
I even tried putting a template with just the text as 'This is a test Template' in the RTF Template. I still get the above errors.
Any potential workaround too greatly appreciated.
Thanks for ur time.

One thing of note is that when I downloaded the template using XDOLOADER, the xml publisher seems to 've created a .xsl file that has reference to the method mentioned above. So although, I'm not referencing it, XMLPublisher created .xsl is referencing it n hence the error. Also, I do remember having read that 'set variable..' method refernced above is only available for a higher version of XMLP. I think I'm on 5.0.
So the question is do I've to upgrade to 5.5 or can I make do with 5.0 version? I would love to get around this problem without the upgrade.
Thanks

Dunning letter through email

Hi,
I want to send dunning letter ( Tcode F150) through email.As per SAP note 328124, I copied OPEN_FI_PERFORM_00001040_P into z FM. Also add new entry for 00001040 event in FIBF tcode.But still when Iam running the Tcode F150, it shows print preview option.Email is not sent to the user. When I debug the program, it stops in std. FM ( i.e OPEN_FI_PERFORM_00001040_P ) not in Z FM that I have created. Please guide on this issue.
Thanks & Regards,
Anagha Deshmukh

Did you activate your product? FIBF -> Settings -> Products -> Customer (click the checkbox)

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 F150 issue

Hi ,
I want to send dunning letter through F150 tcode.The customer wants both option email as well as print.I have done the coding for both.But the program takes only one option at a time. The client wants both the option that send mail as well as print.How to do this.
Thanks & Regards,
Anagha Deshmukh

Hi,
You can [Check this. Hope this might be helpful|Sending dunning letters by email;. And also [Check this thread.|Dunning letters Option - Print/email;.
Thanks,
Abhijit

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 Set in Accounts Receivable

Please explan how can i create dunning letter sets for customized customer environment, where can i find funciton to create dunning letter set and how cna i attach with specific customer
i can not find any function link in the accounts receivable responsibility or nor in vision operations
Please reply me as soon as possible

hi,
There is a functionality available in the Oracle Receivables Module.
For Creating the Dunning Letter for the specific customer or for all the customers we need to do some preliminary setups to the profile of the customer,.
Steps:
1) Create a Dunning Letter format. -
Navigate to Receivables->Setup->Dunning Letter->
2) Create a Dunning Set Letter format.
Navigate to Receivables->Setup->Dunning Letter Set-
3) Attach the same to the profile of the customer.
Navigate to Receivables->Customers-> Profile-> by updating here the system will asks you the update all the profiles / Existing profile/ Not to update the profile.
If you want to update to all the profiles then you can choose the appropirate option, otherwise choose the existing profile only.
4) Customers->Query the Customer-> Go to Bill to Site -> Menu Profile-Transaction-> choose the dunning letter over there then it only apply to this customer.
If you need any clarification Please feel free to update in this forum.
Srikanth

Dunning Letter for Single Customer in Version 2007A SP01 PL09?

From the SAP Help I feel I am going mad am I?
"From the SAP Business One Main Menu, choose Reports Sales and Purchasing Aging Customer Receivables Aging .
The Customer Receivables Aging - Selection Criteria window appears.
Select filtering options to display the customers you want.
Set the report options to Age by Due Date and double-click the customer row to display all the documents composing the debt.
Select the Letter column to schedule this invoice for a dunning letter.
You can manually change the dunning level by choosing the Level column. "
I don't see the Letter column? am I missing something that is very obvious?

After you run the report a list of customer will be listed with their debt (0-30, 31-60, 61-90, 90+)...
Notice that a row number is given per customer on the left of each row.
Double click that row number, then you will see a list of invoices with its balances, the last two columns on that window are (Level, Letter) check the box for letter and then you will be able to change the Dunning Level
Good luck

Dunning letter (email) PDF attachment or body of email

Hi experts,
What is the industry practice for dunning letters when sent via email? Attach them as a pdf to the email, or add all the content of the dunning letter to the body of the email to make it easier for the customer to receive the message?
Thanks,
Mario

Hi Mario,
It all depends on the functionality that and payment option that are provided.
If the dunning letters contains and payment/remittance slip(through which customer can make payment in bank, outlet or post office) than the letter should go as PDF attached to mail with body saying that its the reminder for payment being missed,
But if the payment option is not like as described above than you can send the the letter in html body mail.
Regards

Dunning letters Option - Print/email

Hello Frens
Our Customer needs an option to either print or email dunning letters. Currently the settings which we have done checks if email id is present and then emails the letters, but now the requirement has changed.
When F150 Transaction is run, is there any way in which we can prompt or choose if the dunning letter has to be printed or emailed?
Can anyone give me some solution on this?
Thanks in advance!
Regards
Preeti

Hello,
Please check the function module. You need to incorporate the logic to trigger the both. Meaning that though there is an email address in the customer master record, it should spool a copy to SP02. Please take help of ABAPer.
Regards,
Ravi

Customers are receiving first dunning letter on more than one occasion

Hi All,
We are facing a problem in Dunning letters.
Say for example A customer has bline date on 21.1.2009 and payment terms are 30days and grace days as D2 for first level and D14 for second level letter. So when the duedate comes and on 23.2.2009 (after grace days) the first level dunning letter comes out in the run and again in next run on 24.02.2009 also the same invoice is being picked up and letter is generated and so on. Line items is not getting updated once after the letter is generated.
Can any one look into this situation and let me know the root cause of this.
Thanks and Regards
Srihari Bolla

Hi,
Your dunning procedure might have selected the option 'always dun' for all the dunning levels, if so deselect the option and do your testing, usually this option will be selected for the highest dunning level of the dunning procedure.
Best regards
Suresh Addagiri
SAP FICO/sabrix consultant.

Dunning letter language in French instead of English

Hi,
We're on SBO 2007A SP01 PL07. Trying to use the Dunning for the first time - changed the default template to English (from French) but the letter still comes up in French. Have tried assigning the template to use, to BP, but keeps coming up in French.
Anyone know how this can be fixed so the letter is in English?
Thank you,
Heather

Hi Gordon,
I think the problem stems to the fact that for Canada localization, even though you select English when creating the database, the PLD templates all default to the French version, not English (I have submitted this for a product development as support says it's not a bug). The fix is to change the default PLD template to the English version.
In this case, we are making the English template the default but the Dunning letter still appears in French. If I click on the PLD template and select 'Edit Layout', the letter/template is in English.
Just to confirm your suggestions, multi-language support is not activated, Help file is in English. The problem is the PLD template option.
Thank you,
Heather

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 as Crystal Report: What tables? (SAP B1 9.0)

Dear Experts,
I am being asked to revise the Dunning Letters for our clients. The existing PLDs for each Dunning Letter shows most data fields as system variables. The existing Crystal Report for Dunning Letter 1 is a conversion from the PLD and doesn't show table information for most of the report's main items. There are tables in the report but they are standard ones (OADM, OADP, OCRD, OHEM, OSLP). It also includes a "table" called "PLD__ITEMS" which has all the PLD system variables and no B1 table or field/column information.
As I'm just now starting to work with dunning letters, I see that I can't even run this report in Crystal. The PLD__Items datasource prompts me for a file path and class name. Any ideas what one enters here to run the report outside of B1 (from the Crystal report designer)?
The main focus of my question is: Has anyone created a Crystal Report to replicate the Dunning Letter and if so, what tables are involved and how are they connected? If I can create a Dunning Letter entirely in Crystal, I can replicate it across all clients and get the correct fields/columns of data the clients want. The inclusion of the PLD__Items apparently limits my ability to test the results. I would prefer to avoid the PLD limitations.
Thanks for any assistance.

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.

Dunning Letter Report for Portugal

Hi All
For Dunning Letter Portugal language rdf file made some changes in layout like removing break for credit
and debit transactions and moving address field to right side
But fields from Dunning letter setup in applications (first line) is getting truncated to half even after redoing changes it is behaving
in similar way any hints on fixing this issue will be helpfull
Thanks
Kamalakar.G

Hi Husain...Thanks for immediate response. There is already data being pulled by standard function modules like PRINT_DUNNING_NOTICE(copied into Z). Can we use that in simpler way(without the need of any new driver program with all the data population again)? And your answer is correct which I already thought earlier and kept it as a last resort, because I need to populate all the data again, convert spool to pdf and send pdf's to all selected customers And one more thing is that the requirement is to schedule a background job which takes care of sending all the emails . So any more ideas?

Dunning letter option

Similar Messages

Maybe you are looking for