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

Similar Messages

'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

Cannot print preview a excel document Via DMS

Hi,
When we go to CV02n/CV03n and click on 'Originals' Tab and double click the excel document, we can see the excel document within DMS. If we click the Microsoft Office button and go to Print we do not see the 'print preview' highlighted.
Is there any setting in Micrsoft or DMS
Thanks and regards
Shahnawaz Mohammed

Hi Shahnawaz,
SAP DMS standard features not supporting preview function. You can use page set up to make adjustments.
Regards,
Ravindra

Printing Dunning Letter at Customer Aging

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.
Is this how it is supposed to work? Ie, we cannot print preview dunning letter.

Hi Shwu
This is a known limitation on SAP Business One. You could try printing to a document generator or PDF, but unfortunately the system updates the dunning level with each print regardless of printer.
Kind regards
Peter Juby

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 Printing Issue

Hi All,
We are facing an issue with Dunning letter printout. When printing the dunning letter, additional log information is also getting printed.
Does anyone know any config setting in this regard. Any pointers in this regard are much appreciated.
Thanks & Regards,
Ajay

Hi All,
Any pointers for the above query.
Thanks in Advance,
Ajay

XML DUNNING LETTER TEMPLATE ISSUE

Hi every one,
I mapped the fields for the dunning letter report in RTF file.
I have an issue when i work into dunning letter template for xml report.
My Client wants to run the dunning letter by choosing the different languages before they run the concurrent program.
I dont knw where to write xml coding to make this report for mutiple languages and you please could any one knw the answer step by step.
please drop the solutions immediately and its very urgent.
Regards
Prabu

Set the language preference on the customer site on the "Characteristics" tab, then when the program "Dunning Letter Print from Dunning Letter Generate" runs you will have a separate output for each language. Then run each output through the "XML Report Publisher" program and choose which XML template to run.

Replace Oracle Report Dunning Letter to BI-Publisher Dunning Letter

HI,
Are their any documents who is telling me, how I can use the output of "Dunning Letter Print from Dunning Letter Generate".
I have Already tried to create an "RTF" document, and placed it in BI Publisher of Oracle EBS R11.5.10.
I have Created Data Definition, Simple one
I have replaced the output of "Dunning Letter Print from Dunning Letter Generate" to XML.
But the BI Publisher doesn't pick up the output.
So I have done the following thinks.
1. Change output type of "Dunning Letter Print from Dunning Letter Generate" to XML
2. Copied XML out put to my workstation.
3. Make an example MSWord Document
4. Test the XML output file in MSWord and it seems to work
5. Create in EBS BI Publisher and data definition called "ARDLP_NON_SRS"
6. Create in EBS BI Publisher and Template Called "ARDLP_NON_SRS" defined with Default Output Type = PDF
7. Restart "Dunning Letter Generate" Output is created but result is XML output, and not PDF output as defined in BI Publisher Template.
what do I wrong.
Thanks for your reply.

Check the data definition setup - is the code = to the program short name? make sure that they are both in capital letters

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 XML not displaying XML version of Dunning Letter

I have changed the Output Format for "Dunning Letter Print from Dunning Letter Generate" to XML. When I run the Dunning Letter Generate process, though, the XML output in the Dunning Letter Print from Dunning Letter Generate does not display the XML of the Dunning Letter. Instead, the following XML is displayed:
<?xml version="1.0"?>

<ARDLP>
<LIST_G_CORRESPONDENCES>
</LIST_G_CORRESPONDENCES>
<R_INTEREST_RATE></R_INTEREST_RATE>
<R_DEFAULT_COUNTRY>NL</R_DEFAULT_COUNTRY>
<C_TRX_NUMBER>APP-00001: Unable to find message: AR_REPORTS_TRX_NUMBER</C_TRX_NUMBER>
<C_PO>APP-00001: Unable to find message: AR_REPORTS_PO</C_PO>
<C_DEBIT>APP-00001: Unable to find message: AR_REPORTS_DEBIT</C_DEBIT>
<R_DEFAULT_COUNTRY_DESC>M-3M-WM-4M-zM-6M-uM-5M-e</R_DEFAULT_COUNTRY_DESC>
</ARDLP>
Is there any specific setup required to generate the appropriate XML for the Dunning Letter?

Kit
It is definitely possible to use XML Publisher for dunning letters. I would suggest your sample run did not select anything for dunning as the XML looks correct otherwise. The problem with this approach is that it is not a single step process to get the letters. You will only ever get XML from the dunning letter print report as there is nowhere in the submission screen to tell it what template to use. Therefore you will need to modify the after report trigger to submit the XML Report Publisher concurrent program to automatically pick up the XML and create the letters.
You might want to look at the standard functionality in collections or advanced collections (not sure about collections but definitely in advanced) as there is some standard functionality in there for Dunning which uses XML Publisher templates. The setup is a bit onerous (not sure what the developers were thinking) but at least you can use XMLP as standard.
Cheers,
Dave

Dunning Letter Generate program Isues

Hi All
We are Running Dunning Letter Generate for Dunning letter set (SIS_1GER) for 2 dates (20-Jul-2011, 15-Aug-2011) for Staged Dunning
In Dunning Letter Print from Dunning Letter Generate output we are not getting same customers Would like to know the reason why Same customers are not picked in successive runs How we can fix to get Dunning Letter Generate output same customers with different Dunning levels
Thanks
Kamalakar.G

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

Problem with Dunning letter

I have printed the Dunning letter to be sent to the customer and when i looked at the signature part there are two signatures are appearing where only one signature is supposed to be there.
could please help how to resolve this like where i need to check for the possibilities?
Thanks in Advance for the help.

Hi,
You need to check the program which is generating dunning notice in your case. You can reach your dunning form in following way:
1. T-Code FBMP
2. Select your dunning procedure
3. Click on Dunning texts
4. enter your co.code & select account type
5. You will find forms corresponding your dunning levels
6. Select the level you get two signatures then
click Goto (on top) > Display Form
7. now click on utilities > Form info
This will bring out detailed info about your form.
You can review the footer of this with your ABAPer and thus would be able to find the root cause of the issue.
Please let me know if this helps
Warm Regards
Harpreet

Dunning letter error

Under the Insurance Log when trying to print a dunning letter in advance print I keep receiving this error "RuntimeException; nested exception is java.lang.NullPointerException." Does anyone know how I can correct the error...
This is only happening on newer "Jobs" that we have in our system... maybe I am missing something along the lines in setup??
Edited by: 795046 on Sep 15, 2010 2:19 PM

Aha, I saw this back in 2008, and the solution was the same. I see that I had a ticket out with Primavera at the time, but all that history is lost now. So I'm not sure if I ever figured out the underlying cause.
Cheers,
Daniel

Outgoing Payment Print Preview Error

Hi
We upgraded SAP form 2007B to 8.81 PL08. when we click print preview in Outgoing Payment. Its Showing Error Message as :
No matching records found 'Outgoing Payment' (OVPM) (ODBC-2028) [message 131-183] Its coming for all the user.
Why its coming. could any one knows how to solve this.
Thanks and Regards,
Sudhir B.

hi Sudhir,
please check the ff SAP note. this is a known issue from SAP
1. [1524636 - Cannot print/preview Incoming/Outgoing Payment|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3030303135323436333626]
2. [1584189 - Cannot print/preview Incoming/Outgoing Payment|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3030303135383431383926]
note:
you need to use S-Account to access this notes
regards,
Fidel

Value pass to Smartform when Print/Preview

Hi,
I've a custom print program and smartform. All my selecting data codes are in Smartform. How do I let Smartform knows whether I'm doing a preview or print? What values should I pass into Smartform?
I'd like to achieve something as follows:-
IF print preview.
DO a.
ELSE.
DO b.
ENDIF.
Please share your thoughts.

Hi Brad,
Actually it is not the data selected that determines the print preview. Let me give a clearer scenario.
When user clicks Print Preview, user able to see a preview of the form. However, when user clicks Print, form is printed and some data is saved to a custom table.
Currently, both print preview and print will save the data to the custom table. So I'd like to know how to prevent data being saved into the custom table when user performs a print preview.
Thanks.

Cannot print preview Dunning Letter

Similar Messages

Maybe you are looking for