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

Similar Messages

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

Which custom. steps for "Accounts Receivable Pledging Indicator" (KNB1)?

Hi All,
Could anyone show me the customizing steps to set the "Accounts Receivable Pledging Indicator" (KNB1-CESSION_KZ)?
Thanks
Galdalf

Hi ,
Pledging indicator is basically used in the Accounts Receivable Factoring Process. Factoring is the process of the transfer of a receivable from the previous creditor (assignor) to a new creditor (assignee).
The Menu Path for creating the Pledging indicator is as below:
Financial Accounting > Accouts Receivable and Accounts Payable> Customer Account > Master Data > Preperation for creating master data > Define Accounts Receivable Pledging Indocator
This indicates in the master record that a customer should be involved in the accounts receivable factoring procedure. The indicator is automatically transferred to the line item during posting but can also be entered manually.
Also you can refer to the thread A/R Functionality in SAP for more details of the process.
Hope it helps
SJ
Edited by: Sumit Jain on Jul 7, 2009 1:32 PM

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

Set Customerwise Debtor accounts in Accounts Receivable

Hi All,
I need to set customerwise debtor accounts when a transaction is created in accounts receivables.
That is when I enter a transaction for customer A, then account debited must be customer A debtor account.
Can I do this in oracle ebusiness suite?

Hi
Please let me know the reason for going to this approach. This is actually defying the logic of general ledger and subledger.
Although, from the system perspective this is possible to be done. You can create multiple natual account codes representing each of your customer and attach this account to the customer bill to site use level. Ensure that your autoaccounting is set to pick up natural account from the customer site level.
This apporach is quite cumbersome and difficult to maintain. Also creates duplicacy of data.
Thanks
Vinit

How can I set up a "receive only" email account in Outlook 2010

I have an Outlook 2010 email account that receives emails from a "Fax-to email" service, and I'd like to make that accout "Receive Only". Is it possible to do that, and if so, how.
Capt. Dinosaur

Hi
As per the information and details provided by you, to set up a
“Receive Only”email account in Outlook 2010, please follow these steps: -
You have a few options available to you. You can set up the account with
a fake SMTP server name and configure the Send/Receive group to not send mail from this account, or you can use a different, valid account for the Outgoing server, just in case you accidentally use the wrong account when you compose a message.
First, create the account in Outlook: -
Fill the name and address fields with the desired information. Select
POP3 account type and enter the incoming server name.
In the Outgoing server field, type
nomail.
Enter the correct username and password for the incoming mail account.
If you want to verify the incoming server is correctly configured, click on
Test Account Settings, and then choose the dialog after the incoming server is verified.
Deselect the option to
Automatically test account settings when the Next is clicked.
Click on the
Finish to return to Outlook.
Because Outlook will error on every manual send and receive when it can not find the outgoing server error, you need to change the
Send and Receive Settings for this account.
Press
Ctrl+Alt+A to open the Send/Receive Settings dialog. (or you can go to
Send/Receive tab, Send/Receive Groups and select Define Send/Receive Groups.
Click the
Edit button.
Select the receive-only account, then deselect
Send Mail Items.
Click on the
OK, then Close to return to Outlook.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G

Set up Company Codes for Contract Accounts Receivable and Payable

HI,
I need clarification on "Set up Company Codes for Contract Accounts Receivable and Payable"
When a company code "ABCD" isn't set up for contract accounts receivable and payable (Menu path:
SAP Insurance -> Collections/Disbursements -> Organizational Units -> Set up Company Codes for Contract Accounts Receivable and Payable), are postings on this company code "ABCD" within FS-CD not allowed and blocked ?
Is it mandetory to specify company codes to post in Contract Accounts Receivable and Payable in SAP FS-CD.

Yes . It is mandatory to extend company code chart of accounts to CA/CR and FSCD.
Srinivas

Create Sales Order with Contract Accounts Receivable and Payable Set

I have successfully created a Sales Order using BAPI BAPI_SALESORDER_CREATEFROMDAT2. Then, I need to set value to Contract Accounts Receivable and Payable in the Sales Order Header Data (Goto -> Header -> Accounting).
How do I do that? Can I assign a value to Contract Accounts during creation of Sales Order using BAPI BAPI_SALESORDER_CREATEFROMDAT2?

Hi Andrew Tan,
iam trying to creats sales order but i cannot able to creats sales order.
I had used BAPI_SALESORDER_CREATEFROMDAT2 to create
iam getting an message as
SALES_HEADER_IN has been processed successfully
SALES_ITEM_IN has been processed successfully
Order receipt/delivery not possible, credit customer blocked
help me out of this problem
Pleases send me the code for this creation.
Waiting for your reply.
Thanks,
sayyed.

Customers are receiving first dunning letter on more than one occasion

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

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

Dunning letter

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 via email with invoice attachments

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

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

How to setup dunning letter print out directly

Hi anybody,
I want print dunning letter F150 directly into printer. how do i setup in SAP. is there any setup in configuration of dunning letter printout?.
Please explain to me steps of dunning letter printout.
Thanks
Regards,
S.Muthu

Dear S.
go into the customizing (Transaction SPRO):
Here Financial Accounting
--> Accounts Receivable and Accounts Payable
--> Business Transactions
--> Dunning
--> And here you can set up the basis settings then. And of cours the printouts.
Hope this helps you to go on,
Jessica

4th Dunning Letter not Printing....

hi All,
The 4th address line is not printing on the Dunning letters. This is the 1st time we have run dunning letters in my company.
Also I need where u201Cwe have an accounting clerk assigned, how can we update and change accounting clerk on dunning letters?u201D
Please let me know where exactly i need to change the settings....
Cheers.....

Hello,
Please check the form assigned to your dunning procedure.
IMG ==> Financial Accounting ==> Accounts Receivable and Accounts Payable ==> Business Transactions ==> Dunning ==> Printout ==> Assign Dunning Forms
Please check up with your ABAPer the logic put into the form. I believe the FORMS that you have assigned to the dunning procedure needs some correction.
Regards,
Ravi

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

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

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

Dunning Letter Set in Accounts Receivable

Similar Messages

Maybe you are looking for