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

Similar Messages

Zahlungslauf - seit 2007A SP01 PL09 - Ansprechpartner wird benötigt

Hallo zusammen,
seit wir beim Kunden auf die Version 2007A SP01 PL09 upgedatet haben,
funktioniert der Zahlungslauf nicht mehr wie gewohnt.
Teilweise werden zu bezahlende Rechnungen nicht übernommen. Es kommt zwar keine Fehlermeldung, in der Protokolldatei liest man dann aber dass im Geschäftspartner der Ansprechpartner fehlt.
Wird im Geschäftspartner der Ansprechpartner eingetragen funktioniert alles wie gewohnt.
Weiß jemand warum das eingebaut wurde? Wozu sollte man beim Zahlungslauf einen Ansprechpartner benötigen, wenn dieser in der Bankdatei gar nicht mitübertragen wird?!
Derzeit ists mühsam da man immer die Protokolldatei kontrollieren muss, ob nicht doch Zahlungen in der Bankdatei fehlen könnten, obwohl diese zuvor ausgewählt wurden.
Warum exisistiert diese Abfrage nun?
Weiß jemand ob der Ansprechpartner ab einer bestimmten Höhe der Zahlung verlangt wird?
LG
Elisabeth

Hallo,
danke für den Hinweis.
Weiß vielleicht jemand wo ich diese Änderung nachlesen könnte?
Die Dokumentation der Notes bzw. die Listung aller behobenen Fehler im Update durchzusuchen hilft mir auch nicht.
Habe bis dato nichts gefunden.
Will ich nämlich über Inserts und Updates in der Datenbank alle leeren Felder automatisch befüllen, so muss ich mir ebenfalls eine kleine Routine bauen, die die Standardfelder befüllt und die Einträge in der Tabelle OCPR entsprechend einfügt.
Den Aufwand zahlt mir keiner!
LG Elisabeth

One dunning letter for Multiple Customers

Hi SAP Gurus,
In dunning i want to create one dunning letter for Multiple Customers, what necessary settings that i have to do.please help me.
Thanks in Advance.
RAVI

If it is single email address for all the customers of a sales organization, then you can maintain the email address at the sales organization level in t.code OVX5. If SPRO side change is not allowed, then you either maintain in SO10 text, or alternatively you can think about adding it in Z-table if it is easy to maintain and available in your system.
Regards,

Separate Dunning Letter for Individual line items

Hi All,
Please let me know if it is possible to produce a separate dunning notice for each individual line item in an invoice.
Thanks,
Naresh

Hi,
1.loop at Line item.
Write_form.
endloop.
2.This will give the seperate dunning letter for each invoice line item.This can be write in the driver pg.
Regards,
Shiva Kumar

Need to maintain more than one address for single customer.

Dear All,
I need to maintain more than one address for single customer, Is it possible? If so how can I maitain kindly send the details.
Rgds
Srinivasan.K.R.

Dear Srinivasan,
I don't think you can maintain the more than one address for single customer as per the standard.
You can this options
1.You can create different ship to parties as per the addresses.
2.You can change the address manually while creating sales order for single customer.
I hope this will help you,
Regards,
Murali.

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

Amount spliting in 3 line items for single customer

Hi All,
Here i am facing one small issue at the time of billing docment relesing to finance.
here i am getting 3 line items for single cumenter, custmoer debited in 3 line itmes.
why i am geting 3 line items can any one help me in this issue.
thanks
kiran

Hi,
If you have new GL with document splitting active then if you have created billing for 3 items then system can split the customer line as well into 3 lines in GL view particularly if you have 3 items are getting credited to separate GL Accounts as sales revenue.
In Classic GL view you will not see customer line getting split. Hoep it helps you.
Regards,
Sanjay

Multiple shipping address for single customer

Dear All,
I have a regular customer who needs to have his goods delivered to several constant locations. How can I capture the delivery address of all the locations.
Regards
Rasheed

Hi Rasheed,
Create the different ship to parties using XD01 and Account Group Ship to Party.
Assign these ship to parties to the customer in partner functions in XD02.
Next when you create teh sales order, you will have multiple options to chose from.
But in each case, one Sales Order can have only one Sold to PArty and One Shipped to PArty.
You may have to create another SO with same PO and Same Sold to PArty and Choose the next Shipped to Party option which you must have assigned in the Customer Master.
Cheers
Edited by: Mohammed Raheel on Jun 8, 2009 10:19 AM

SBO 2007A SP01 PL09 HF_04 (B12007A0109HF_04-10003612)

I tried upgrading my PC to this SBO version but the upgrade fails with "Error Accessing Parser Dll...." error. I got some postings here on the SDN that i need to install Miscrosoft Visual C++ 2005 Redistibutable. This is did not solve the problem.
Just to make sure it wasn't a problem with my PC, i tried upgrading a second PC; same problem.
Does anyone know if there is a problem with this setup ? Thank you in advance.

Hello,
You should download the install Miscrosoft Visual C++ 2005 Redistibutable SP1
http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
on this thread:
Error Accessing Parser Dll
Regards
J

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.

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

Send Dunning Letter to Customer thorugh Email ID

Hi anybody,
Please explain to me how to send dunning letters into customer using Customers Mail IDs . My users asked to me once do Dunning letter F150 all customers dunning letter send corresponding customer mail address.
How do I setup in SAP send mail to customer. Please explain steps of send mail to customer.
I will appreciate goods answers to me.
Thanks
Regards,
S.Muthu

Sending dunning letters by email
Hope this thread is useful.
Regards,
Ravi

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

Dunning letter - email/pdf problem

I want to email a dunning letter to a customer.
I have executed a dunning run.
I go back to the Recommendation report for the dunning run - when I highlight the row under the customer name and click print preview I can see a preview of the dunning letter I want to email.
When I click the 'Email' button and click 'Yes' to attach an edited report I thought that would attach the letter to an email as a PDF? (I have send E-Mail via Microsoft Outlook' selected)
But when I check my Outlook sent box the email has been sent but there is no attachment of the dunning letter - it's just an empty email?
I tried again and examined the 'Send message' box that appears when I click the 'Email..' button.
The data tab shows the dunning run listed but the Attachments tab has nothing listed.
Should the file be listed here if it had correctly attached?
Incidentally when I click the PDF button this just brings up the same print preview instead of making a PDF of the letter - is this significant i.e is the PDF function not working hence the 'attach edited report' function also cannot work?
I'd be grateful for advice on emailing dunning letters correctly
Karen

Hi Andrew,
Check this Link
Re: Email Dunning Report to the BP
Re: Automatic Dunning By Email
Regards
Jambulingam.P

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

Similar Messages

Maybe you are looking for