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?

Similar Messages

AR Statement /Dunning Letter Report Issue

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

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

To get Footer Displayed for Dunning Letter Report

Hi All
There is a requirement to Add footer to display at bottom of page in Oracle reports with Customer Number, And Sum of Transaction Amount
for Dunning Letter. Would need some hint towards fixing this Can we get this requirement using Dunning Letters
Thanks
Kamalakar.G

There are two locations on the BI Server where you need to place images:
Drive:\Oracle\Middleware\Oracle_BI1\bifoundation\web\app\res\s_blafp\images
Drive:\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\s_blafp\images
Normally no need to restart services; just clear caches and reload files and metadata. Try adding images in these locations and referencing them with HTML from your dashboard. This should give the desired result
HTML syntax for displaying image : <img width=183 height=53 src="res/s_blafp/images/YOURIMAGENAME.jpg">
Geo

Dunning Letter Email for all customers

Hi All, I need your help in my requirement, which goes like this :- In F150 tcode(ecc 6.0), which internally uses RFMAHN20 program to display all customer accounts, we can select a customer and see the dunning letter(It's a sapscript) and also take a printout. I made some changes accordingly to add the email functionality so when user checks the print preview then a pop up promts for email address( which has default value of email address assoicated with that particular customer) and send pdf letter accordingly. But my requirement is to send email to all customers who may be selected via RFMAHN20( they may be all customers who belong to the same account type). How can we achieve this in the most easy way? I already copied standard FM's associated. So can I do something in them to resolve this or any separate program is needed( if so, how?)? Please respond asap. Thank you so much...in advance

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 on Receivables Aging SAP B1 2007

You run the customer receivables aging report and double click a row on receivables aging report window. You highlight one row, there is no letter checkbox compare to SAP 2005 A. There is no Dunning Letter PLD as well. Therefore dunning letter report cannot be previewed.
Does this letter checkbox and dunning letter PLD is not available in SAP 2007 A?
Thanks,
Kay Chong

Hi,
the document [Changed Features as of Release 2007 |https://websmp101.sap-ag.de/~sapidb/011000358700000281062007E.pdf]says the following:
Dunning in Aging Report
Application Path: Financials u2192 Financial Reports u2192 Accounting u2192 Aging u2192 Customer Receivables Aging u2192 Customer Receivables Aging u2013 Details window
Availability: All countries
Used for: indicating the dunning level linked to the document/transaction and creating a dunning letter if required.
                         Availability in
                         SAP B1 2007 A or B    Functionality changed?
New installations        N/A                   No
Upgrading customers      All countries         No
So this functionality is only available for databases upgraded from an older release.
Regards,
Marcus

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.

Dunning letter

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

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

Dunning letter BG

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

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

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

What parameters should I use for a dunning letter in Crystal Reports?

Hello
I have created a dunning letter in Crystal Reports. I want to import this layout as a layout (not a report) in Business One.
The problem is that I don't know the parameters in the report so I can import the layout between the standard PLD layouts (like Dunning 1, dunning 2 dunning 3 dunning all etc). I tried a few but import fails everytime. I can't check the parameters in another report, as SAP only uses standard PLD layouts.
Does anybody know what parameters to use in this report? Thanks.

I did areal photography one time. What you have listed would not be on my short list for lenses to take at all.
Maybe you could supply a little more info of the 50-100mm ? I am going to guess you have the first version of the Canon EF-S 75-300mm? It is a faily slow lens but if these two are the only possibility, I'd choose it.
It and the XTi will work as a mattter of fact I took two XTi's on my flying photo experience. But I had the fantastic EF 70-200mm. Another thing, there is NOT a lot of room on these aircraft.
EOS 1Ds Mk III, EOS 1D Mk IV EF 50mm f1.2 L, EF 24-70mm f2.8 L,
EF 70-200mm f2.8 L IS II, Sigma 120-300mm f2.8 EX APO
Photoshop CS6, ACR 8.7, Lightroom 5.7

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.

Report for Dunning

Hi Experts,
Any one has written report for Dunning.(F150)
Scenario: transcation code F150 can't be schedule; it's runs manually by users.
we need a report same as what F150 is doing so that we can schedule in job.
if any one knows report for dunning ? I know fot he payment F110, there is a sap report progarm but not for Dunning(F150).
Can anybody suggest me ??
Thanks in advnace for the help.
Regards,
Nupur

Hi Hemanth,
Customizing:
You can go the Transaction FBMP and add your Form name as well as the Print Program name.
These would be call when ever you run the dunning Program.
From the Layoutset yuo can use the PERFORM subroutine using and changing parameters which would have the Structure ITCSY.
The Form then needs to be present in the Driover Prpgram.
Please let me know if this is useful.
Regards,
Deepak

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 Report for Portugal

Similar Messages

Maybe you are looking for