Regarding Dunning PO -MAHN
Hi MM Guru's
I have maitained MAHN as an output type for PO dunning I have got Problems
1- MAHN should pop up automatically in Messege as i have already maintained the condition record via MN04
2-when I run ME9F select MAHN and click on Output Messege Tab, i Got the Red Cross befor MAHN
can you please let me know what is the problem why such type of Red Cross is cooming while doing output message
i have alreday maintained the PUK in Material master master
is there anything i missed on config side
Thanks in advance
hi
check these customization settings are done.
Financial Accounting (New) --->Accounts Receivable and Accounts Payable -->Business Transactions -->Dunning -->Basic Settings for Dunning
Financial Accounting (New) --->Accounts Receivable and Accounts Payable -->Business Transactions -->Dunning --> Dunning Procedure
Financial Accounting (New) --->Accounts Receivable and Accounts Payable -->Business Transactions -->Dunning --> Printout
Similar Messages
-
Regarding Dunning transaction F150...
Iam facing some problem to send individual dunning letters to the customers.
My requirement was i have to send dunning letter created through F150 transaction as an Email to the customers individualy.
The E-mail trigerring and am able to send the Emails also with my code but, user will execute F150 for a range of customers at a time .
and as per the standard functionality in F150 it is creating only one SPOOL for all the cuatomers and when iam converting as PDF iam getting total spool as a single PDF.
and this pdf having all customer Dunning letters, each letter having information about their DUES.
so, user cant share this with customers.
i have to splict the spool for individual customers and have to convert it has a PDF.
Friends, can any one let me know the possible ways to fulfill this requirement so that i can close the issuee.
Thanks & Regards,
Sandeepkumar Jetty.Dear Sandeepkumar,
maybe a bit late but please check this link (it helped me):
http://web.mit.edu/CAO/www/SB2002/AR/F150.htm
Best regards,
Daniel Simon -
Fields regarding the Customer MAHNA
Hello gurus,
I need to know the name of the tables for these fields. these fields are in a transaction ZF106 Customer in Company Code and I can't find the name of the tables.
MAHNA
MANSP
MADAT
MAHNS_D
DZTERM
DZWELS
STCEG
GESTYP
LANDX
Thanks in advance,
RamonaHi,
The tx. ZF106 is Developement Txn. to find the table name just follow as mentioned below.
1. Go to Txn. SE93.. enter the txn. ZF106... hit enter then you can find the program name..
or
2. Execute the Txn. ZF106.. then from the menu bar go to>Systems> Status... there you can find the Program Name...
3. Then goto Txn. SE38.. enter the Program name... and click on Display...
4. Inside you can find the Table Name for these Fields
Regards
GK. -
Dunning for Public Insitutions
Hi Experts!
How are you? We are dealing here with a situation, and we really need your help and experience in SAP ISU.
Regarding dunning, we have the following scenario with public institutions:
1 - We have one City Hall which have several water services for Schools and Hospital
2 - The billing and invoicing is done vs the school and the hospital.
3 - If any of these services (or both) have open items which are being dunned, the dunning process must be done vs the City Hall. That is to say, that in these cases we need one dunning line for the City Hall. In fact, we have to print a letter which is addressed to the city Hall, detailing the services which are being "dunned".
We are executing our dunning process by Contract Account, and we have a dunning grouping (which verifies the Alternative partner for dunning). We also have assigned to the School Contract Account and Hospital Contract Account the City Hall Partner as Alternative Dunning partner (The School and Hopsital Partners are the Account Holder for the Contract Accounts). Despite this configuration it is always generating two lines (one for each contract Account).
Do you know if the dunning run parameters are correct? Is it the grouping ok?
Any idea will be very helpful!
Best Regards!
LUCASHi Lucas,
Have you checked whether collective billing will work to your scenario ?
thanks,
VR -
Issues with Dunning: what happens after level 3 of 3 ?
Hi,
We have set up 3 dunning levels. That works fine as I could test this because we had some invoices that have moved from 1 to 2 and to 3. The letters for level 3 has been printed and the GP data has been updated. The level 3 is shown and the history shows it as well. Looks like perfect.
However, now the problem starts. These invoices are still unpaid. What happened to them regarding dunning? If I run the dunning wizard again, all formerly level 3 invoices are not in there anymore.
How do I handle this to not forget these open invoices?
Best regards,
FranzDunning will only help you on the AR aging process. Nothing can replace other processes to collect the payments. As the scenario you are given, you have to keep your original process. Any open invoice during the dunning period should be handled by manual process or wait until another.
Thanks,
Gordon -
Vendor Master Extraction from Legacy
Hi guys,
We have 2 different legacy systems here (4.5b and 4.6c) and I am trying to extract the vendor master from both of them and integrate them into the new mysap2004.
What is the best way to extract the vendor master along with the address , punchasing doc, bank details, partner functions,etc ? Any sample program for vendor master extraction is most welcome. Here is my extract layout.
ADDRESS
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
SZA1_D0100 Title (TITLE_MEDI) CHAR/30 Not used
ADDR1_DATA Name (NAME1) CHAR/40 Bring values over as is.
ADDR1_DATA Name (NAME 2) CHAR/40 Bring values over as is.
ADDR1_DATA Name (NAME 3) CHAR/40 Bring values over as is.
ADDR1_DATA Name (NAME 4) CHAR/40 Bring values over as is.
ADDR1_DATA Search Term 1 (SORT1) CHAR/20 Convert to HPC methodology.
O-First 8 char. of vendor name
R- First 8 char. of vendor name
B- First 8 char. of vendor name
ADDR1_DATA Search Term 2 (SORT2) CHAR/20 Bring values over as is.
ADDR1_DATA Street/House Number
(Street) CHAR/60 Bring values over as is.
ADDR1_DATA House Number
(HOUSE_NUM1) CHAR/10 Bring values over as is.
ADDR1_DATA Building (number or code)
(BUILDING) CHAR/20 Bring values over as is.
ADDR1_DATA Room or apartment number
(ROOMNUMBER) CHAR/10 Bring values over as is.
ADDR1_DATA Floor in building
(FLOOR) CHAR/10 Bring values over as is.
ADDR1_DATA c/o name
(NAME_CO) CHAR/40 Bring values over as is.
ADDR1_DATA Street 2
(STR_SUPPL1) CHAR/40 Bring values over as is.
ADDR1_DATA Street 3
(STR_SUPPL2) CHAR/40 Bring values over as is.
ADDR1_DATA Street 4
(STR_SUPPL3) CHAR/40 Bring values over as is.
ADDR1_DATA Street 5
(LOCATION) CHAR/40 Bring values over as is.
ADDR1_DATA City
(CITY1) CHAR/40 Bring values over as is.
ADDR1_DATA District
(CITY2) CHAR/40 Bring values over as is.
ADDR1_DATA City (different from postal city)
HOME_CITY CHAR/40 Bring values over as is.
ADDR1_DATA City postal code
(POST_CODE1) CHAR/10 Zip Code. Bring values over as is.
ADDR1_DATA Country
(COUNTRY) CHAR/3 Bring values over as is.
ADDR1_DATA Region (State, Province, County)
(REGION) CHAR/3 E.g., NJ New Jersey, CO Colorado, etc. Bring values over as is.
ADDR1_DATA Time Zone
(TIME_ZONE) CHAR/6 Bring values over as is.
ADDR1_DATA Transportation Zone
(TRANSPZONE) CHAR/10 Bring values over as is.
ADDR1_DATA Regional Structure Group
(REGIOGROUP) CHAR/8 Bring values over as is.
ADDR1_DATA P. O. Box
(PO_BOX) CHAR/10 Bring values over as is.
ADDR1_DATA P.O. Box Postal Code
(POST_CODE2) CHAR/10 Bring values over as is.
ADDR1_DATA Language Key
(LANGU) LANG/1 Bring values over as is.
SZA1_D0100 Telephone
(TEL_NUMBER) CHAR/30 Bring values over as is.
SZA1_D0100 Telephone Number Extension
(TEL_EXTENS) CHAR/10 Bring values over as is.
SZA1_D0100 Fax
(FAX_NUMBER) CHAR/30 Bring values over as is.
SZA1_D0100 Fax Extension Number
(FAX_EXTENS) CHAR/10 Bring values over as is.
SZA1_D0100 E-mail
(SMTP_ADDR) CHAR/240 Bring values over as is.
ADDR1_DATA Standard Communication Type
(DEFLT_COMM) CHAR/3 Bring values over as is.
ADDR1_DATA Data Line
(EXTENSION1) CHAR/40 Not used. Do not bring over field values.
Note: This field will be available to populate with other data during the conversion.
ADDR1_DATA Telebox
(EXTENSION2 CHAR/40 Not used. Do not bring over field values.
Note: This field will be available to populate with other data during the conversion.
ADDR1_DATA Comments
(REMARK) CHAR/50 Bring values over as is.
CONTROL
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFA1 Customer
(KUNNR) CHAR/10 Bring values over as is.
LFA1 Authorization
(BEGRU) CHAR/4 It is to be determined if this field will be used in the future. If yes, bring values over as is from HPC and populate with vendor account group code for Foods.
LFA1 Trading Partner
(VBUND) CHAR/6 Bring values over as is.
LFA1 Group Key
(KONZS) CHAR/10 Not used
LFA1 Tax Code 1
(STCD1) CHAR/16 Bring values over as is.
LFA1 Tax Code 2
(STCD2) CHAR/11 Bring values over as is.
LFA1 Fiscal Address
(FISKN) CHAR/10 Bring values over as is.
LFA1 Jurisdiction Code
(TXJCD) CHAR/15 Bring values over as is.
LFA1 VAT Registration No.
(STCEG) CHAR/20 Bring values over as is.
LFA1 Tax Office
(FISKU) CHAR/10 Bring values over as is.
LFA1 Tax Number
(STENR) CHAR/18 Bring values over as is.
LFA1 Industry
(BRSCH) CHAR/4 Bring values over as is.
LFA1 Train Station
(BAHNS) CHAR/25 Not used.
LFA1 Transportation Zone
(LZONE) CHAR/10 Bring values over as is.
LFA1 Actual QM Sys.
(QSSYS) CHAR/4 Bring values over as is.
LFA1 QM System To
(QSSYSDAT) DATS/8 Bring values over as is.
LFA1 DAK
(J_1FDAK) CHAR/8 Bring values over as is.
PAYMENT TRANSACTIONS
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFBK Bank Country Key
(BANKS) CHAR/3 Bring values over as is.
LFBK Bank Key
(BANKL) CHAR/15 Bring values over as is.
LFBK Bank Account
(BANKN) CHAR/18 Bring values over as is.
BNKA Bank Name
(BANKA) CHAR/60 Foods - Bring values over as is.
HPC Populate with Bank Account Number
LFA1 Alternative Payee
(LNRZA) CHAR/10 Bring values over as is.
LFA1 Individual Spec.
(XZEMP) CHAR/1 Bring values over as is.
LFA1 Spec. Per. Reference
(XLFZA) CHAR/1 Bring values over as is.
ACCOUNTING INFORMATION ACCOUNTING
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFB1 Recon. Account
(AKONT) CHAR/10 Bring values over as is.
LFB1 Sort Key
(ZUAWA) CHAR/3 Bring values over as is.
LFB1 Head Office
(LNRZE) CHAR/10 Bring values over as is.
LFB1 Authorization
(BEGRU) CHAR/4 Bring values over as is.
LFB1 Cash Mgmnt Group
(FDGRV) CHAR/10 Bring values over as is.
LFB1 Release Group
(FRGRP) CHAR/4 Bring values over as is.
LFB1 Minority Indicator
(MINDK) CHAR/3 Bring values over as is.
LFB1 Certification Date
(CERDT)
DATS/8 Bring values over as is.
LFB1 Interest Indicator
(VZSKZ) CHAR/2 Bring values over as is.
LFB1 Last Key Date
(ZINDT) DATS/8 Bring values over as is.
LFB1 Interest Cycle
(ZINRT) NUMC/2 Bring values over as is.
LFB1 Last Interest Run
(DATLZ) DATS/8 Bring values over as is.
LFB1 Withholding Tax Code
(QSSKZ) CHAR /2 Bring values over as is.
LFB1 Withholding Tax Country
(QLAND) CHAR /3 Bring values over as is.
LFB1 Recipient Type
(QSREC) CHAR /2 Bring values over as is.
LFB1 Exemption Number
(QSZNR) CHAR /10 Bring values over as is.
LFB1 Valid Until
(QSZDT) DATS/8 Bring values over as is.
LFB1 Exemption Authority
(QSBGR) CHAR /1 Bring values over as is.
LFB1 Previous Account No.
(ALTKN) CHAR /10 Do not bring over existing values. Will populate during vendor conversion when legacy vendor number is replaced by a new vendor number.
LFB1 Personnel Number
(PERNR) NUMC/8 Bring values over as is.
PAYMENT TRANSACTIONS ACCOUNTING
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFB1 Payment Terms
(ZTERM) CHAR/4 Refer to data mapping spreadsheet later in this spec.
LFB1 Tolerance Group
(TOGRU) CHAR/4 Bring values over as is.
LFB1 Credit Memo Terms
(GUZTE) CHAR/4 Bring values over as is.
LFB1 Chk. Double Inv.
(REPRF) CHAR/1 Bring values over as is.
LFB1 Chk. Cashing Time
(KULTG) DEC/3 Bring values over as is.
LFB1 Payment Methods
(ZWELS) CHAR/10 Refer to data mapping spreadsheet later in this spec.
LFB1 Alternate Payee
(LNRZB) CHAR/10 Bring values over as is.
LFB1 Individual Payment
(XPORE) CHAR/1 Bring values over as is.
LFB1 Bill of Exchange Limit
(WEBTR) CURR/13
Decimal/2 9999999999999.99 Bring values over as is.
LFB1 Payment Advance By EDI
(XEDIP) CHAR/1 Bring values over as is.
LFB1 Payment Block
(ZAHLS) CHAR/1 Bring values over as is.
LFB1 House Bank
(HBKID) CHAR/5 Not used. Do not bring forward existing values.
LFB1 Grouping Key
(ZGRUP) CHAR/2 Bring values over as is.
LFB1 Payment Method Supplement
(UZAWE) CHAR/2 Bring values over as is.
LFB1 Alternate Payee Indicator
(XLFZB) CHAR/1 Bring values over as is.
LFB1 Tolerance Group
(TOGRR) CHAR/4 Bring values over as is.
CORRESPONDENCE ACCOUNTING
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFB5 Dunning Procedure
(MAHNA) CHAR/4 Bring values over as is.
LFB5 Dunning Recipient
(LFRMA) CHAR/10 Bring values over as is.
LFB5 Last Dunned
(MADAT) DATS/8 Bring values over as is.
LFB5 Dunning Clerk
(BUSAB) CHAR/2 Bring values over as is.
LFB5 Dunning Block
(MANSP) CHAR/1 Bring values over as is.
LFB5 Legal Dunning Proceedings
(GMVDT) DATS/8 Bring values over as is.
LFB5 Dunning Level
(MAHNS) NUMC/1 Bring values over as is.
LFB1 Grouping Key
(MGRUP) CHAR/2 Bring values over as is.
LFB1 Local Processing
(XDEZV) CHAR/1 Bring values over as is.
LFB1 Acct. Clerk
(BUSAB) CHAR/2 Bring values over as is.
LFB1 Account with Vendor
(EIKTO) CHAR/12 Bring values over as is.
LFB1 Clerk at Vendor
(ZSABE) CHAR/15 Bring values over as is.
LFB1 Acct. Clk. Tel. No.
(TLFNS) CHAR/30 Bring values over as is.
LFB1 Clerks Fax
(TLFXS) CHAR/31 Bring values over as is.
LFB1 Clerks Internet
(INTAD) CHAR/130 Bring values over as is.
LFB1 Account Memo
(KVERM) CHAR/30 Bring values over as is.
PURCHASING DATA
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFM1 Order Currency
(WAERS) CUKY/5 Bring values over as is.
LFM1 Terms of Payment
(ZTERM) CHAR/4 Refer to data mapping spreadsheet later in this spec.
LFM1 Incoterms (Part 1)
(INCO1) CHAR/3 Refer to data mapping spreadsheet later in this spec.
LFM1 Incoterms (Part 2)
(INCO2)
CHAR/28 Bring values over as is.
LFM1 Minimum Order Value
(MINBW) CURR/13
Decimal/2 9999999999999.99 Bring values over as is.
LFM1 Schema group, vendor
(KALSK) CHAR/2 Bring values over as is.
LFM1 Pricing Date Cat.
(MEPRF) CHAR/1 Bring values over as is.
LFM1 Order Optim. Rest
(BOPNR) CHAR/4 Bring values over as is.
LFM1 Salesperson
(VERKF) CHAR/30 Bring values over as is.
LFM1 Telephone
(TELF1) CHAR/16 Bring values over as is.
LFM1 Acc. With Vendor
(EIKTO) CHAR/12 Bring values over as is.
LFM1 GR. Based Inv. Verif.
(WEBRE) CHAR/1 Bring values over as is.
LFM1 Auto.Eval. GR Setmt. Del.
(XERSY) CHAR/1 Bring values over as is.
LFM1 Auto.Eval. GR Setmt. Ret.
(XERSR) CHAR/1 Bring values over as is.
LFM1 Acknowledgement Reqd.
(KZABS) CHAR/1 Bring values over as is.
LFM1 Automatic Purchase Order
(KZAUT) CHAR/1 Bring values over as is.
LFM1 Subsequent Settlement
(BOLRE) CHAR/1 Bring values over as is.
LFM1 Subseq. Sett. Index
(BOIND) CHAR/1 Bring values over as is.
LFM1 B. Vol.Comp./Ag. Nec.
(UMSAE) CHAR/1 Bring values over as is.
LFM1 Doc. Index Active
(BLIND) CHAR/1 Bring values over as is.
LFM1 Returns Vendor
(KZRET) CHAR/1 Bring values over as is.
LFM1 Srv.-Based Inv. Ver.
(LEBRE) CHAR/1 Bring values over as is.
LFM1 ABC Indicator
(LFABC) CHAR/1 Bring values over as is.
LFM1 Mode Of Transport-Border
(EXPVZ) CHAR/1 Bring values over as is.
LFM1 Office of Entry
(ZOLLA) CHAR/6 Bring values over as is.
LFM1 Sort Criterion
(SKRIT) CHAR/1 Bring values over as is.
LFM1 PROACT Control Prof.
(PAPRF) CHAR/4 Bring values over as is.
LFM1 Revaluation Allowed
(XNBWY) CHAR/1 Bring values over as is.
LFM1 Grant Discount In Kind
(NRGEW) CHAR/1 Bring values over as is.
LFM1 Relevant for Price Determination
(PRFRE) CHAR/1 Bring values over as is.
LFM1 Relevant for Agency Business
(AGREL) CHAR/1 Bring values over as is.
LFM1 Shipping Conditions
(VSBED) CHAR/2 Bring values over as is.
LFM1 Purchasing Group
(EKGRP) CHAR/3 Bring values over as is.
LFM1 Planned Delivery Time
(PLIFZ) DEC/3 Bring values over as is.
LFM1 Confirmation Control
(BSTAE) CHAR/4 Bring values over as is.
LFM1 Unit of Measure Group
(MEGRU) CHAR/4 Bring values over as is.
LFM1 Rounding Profile
(RDPRF) CHAR/4 Bring values over as is.
LFM1 Price Marking Agreed
(LIPRE) CHAR/2 Bring values over as is.
LFM1 Rack jobbing service agreed
(LISER) CHAR/1 Bring values over as is.
LFM1 Order entry by vendor
(LIBES) CHAR/1 Bring values over as is.
LFM1 Serv. Level
(VENSL) DEC/4
Decimal/1 Bring values over as is.
PARTNER FUNCTIONS
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
WYT3 Partner Function
(PARVW) CHAR/2 Bring values over as is.
WRF02K Number (Partner)
(GPARN) CHAR/10 Map to new partner number in vendor correlation table.
ALTERNATE DATA
(Purchasing Data)
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
LFM2 Order Currency
(WAERS) CUKY/5 Bring values over as is.
LFM2 Terms of Payment
(ZTERM) CHAR/4 Refer to data mapping spreadsheet later in this spec.
LFM2 Incoterms (Part 1)
(INCO1) CHAR/3 Refer to data mapping spreadsheet later in this spec.
LFM2 Incoterms (Part 2)
(INCO2)
CHAR/28 Bring values over as is.
LFM2 Minimum Order Value
(MINBW) CURR/13
Decimal/2 Bring values over as is.
LFM2 Schema group, vendor
(KALSK) CHAR/2 Bring values over as is.
LFM2 Pricing Date Cat.
(MEPRF) CHAR/1 Bring values over as is.
LFM2 Order Optim. Rest
(BOPNR) CHAR/4 Bring values over as is.
LFM2 Salesperson
(VERKF) CHAR/30 Bring values over as is.
LFM2 Telephone
(TELF1) CHAR/16 Bring values over as is.
LFM2 Acc. With Vendor
(EIKTO) CHAR/12 Bring values over as is.
LFM2 GR. Based Inv. Verif.
(WEBRE) CHAR/1 Bring values over as is.
LFM2 Auto.Eval. GR Setmt. Del.
(XERSY) CHAR/1 Bring values over as is.
LFM2 Auto.Eval. GR Setmt. Ret.
(XERSR) CHAR/1 Bring values over as is.
LFM2 Acknowledgement Reqd.
(KZABS) CHAR/1 Bring values over as is.
LFM2 Automatic Purchase Order
(KZAUT) CHAR/1 Bring values over as is.
LFM2 Subsequent Settlement
(BOLRE) CHAR/1 Bring values over as is.
LFM2 Subseq. Sett. Index
(BOIND) CHAR/1 Bring values over as is.
LFM2 B. Vol.Comp./Ag. Nec.
(UMSAE) CHAR/1 Bring values over as is.
LFM2 Doc. Index Active
(BLIND) CHAR/1 Bring values over as is.
LFM2 Returns Vendor
(KZRET) CHAR/1 Bring values over as is.
LFM2 Srv.-Based Inv. Ver.
(LEBRE) CHAR/1 Bring values over as is.
LFM2 ABC Indicator
(LFABC) CHAR/1 Bring values over as is.
LFM2 Mode Of Transport-Border
(EXPVZ) CHAR/1 Bring values over as is.
LFM2 Office of Entry
(ZOLLA) CHAR/6 Bring values over as is.
LFM2 Sort Criterion
(SKRIT) CHAR/1 Bring values over as is.
LFM2 PROACT Control Prof.
(PAPRF) CHAR/4 Bring values over as is.
LFM2 Revaluation Allowed
(XNBWY) CHAR/1 Bring values over as is.
LFM2 Grant Discount In Kind
(NRGEW) CHAR/1 Bring values over as is.
LFM2 Relevant for Price Determination
(PRFRE) CHAR/1 Bring values over as is.
LFM2 Relevant for Agency Business
(AGREL) CHAR/1 Bring values over as is.
LFM2 Shipping Conditions
(VSBED) CHAR/2 Bring values over as is.
LFM2 Purchasing Group
(EKGRP) CHAR/3 Bring values over as is.
LFM2 Planned Delivery Time
(PLIFZ) DEC/3 Bring values over as is.
LFM2 Confirmation Control
(BSTAE) CHAR/4 Bring values over as is.
LFM2 Unit of Measure Group
(MEGRU) CHAR/4 Bring values over as is.
LFM2 Rounding Profile
(RDPRF) CHAR/4 Bring values over as is.
LFM2 Price Marking Agreed
(LIPRE) CHAR/2 Bring values over as is.
LFM2 Rack jobbing service agreed
(LISER) CHAR/1 Bring values over as is.
LFM2 Order entry by vendor
(LIBES) CHAR/1 Bring values over as is.
LFM2 Serv. Level
(VENSL) DEC/4
Decimal/1 Bring values over as is.
ALTERNATE DATA
(Partner Functions)
Source File /Table Name Field Name Field Type / Length Format Rule / Logic
WYT3 Partner Function
(PARVW) CHAR/2 Bring values over as is.
WRF02K Number (Partner)
(GPARN) CHAR/10 Map to new partner number in vendor correlation table.Hi Shareen,
Have you looked Master Data Distribution (ALE) for Vendor since your legacy system are SAP?
Please check t/code BD14 (Send Vendor Master Data) and BD15 (Get Vendor Master Data).
Hope this will give you an idea.
Regards,
Ferry Lianto -
Tab " delivery" in po .use of reminder field
Sir,
In a po there is a delivery tab where we set reminders 1,2,3
how is this functioning with delivery date as well as how are the reminders send to vendors
ply explain
regards
ameyHi Amey ,
The standard o/p type used for dunning is MAHN.
If you have already done customising for o/p type NEU in case of PO , the same customising applies to MAHN , only the o/p Form may Change.
Maintain the condition records in MN04 and monitor the same in Transaction ME91F.
Regards
Ramesh Ch -
Company Code Payment Details missing on dunningletter
Hi Expert,
I have two issues regarding dunning letter.
One is Company Code Payment Details missing on dunningletter
anthor one is Missing dunning letter for 2nd and 3rd dunning level
Could you please help us how to slove the issues.Hi Paula
Since you are trying to create Invoice with PO did you check the Vendor Root there is a attribute for company code. pls maintain the same if not maintained.
regards,
Nimish Sheth -
How to connect FI and RE module tables?
Hi Experts,
I am working on a dunning smartform. As I work for a real estate company, I have to pick few fields from RE tables like VIMI01, CHBSHTPT and VIOB01.
Business Entity
Name
Get XMETEXT<VIOB01> where
SWENR<VIOB01> = SWENR<VIMI01> and BUKRS<VIOB01> =
BUKRS<VIOB01>.
Sales Unit Type
HOMTYP<VIMI01>. Pick
HOMTYP from table VIMI01. Get DESCR field from the table CHBSHTPT where
HOMTYP<CHBSHTPT> = HOMTYP<VIMO01> and SPRAS = 'EN'.
I have seen all the tables in debugger. All the values related to customer of FI transactions are there but not related to RE. Are these logics possible?
Regards
ManiHi Mani,
better will be if you ask your functional consultant of RE, if you don't have any
RE functional support then please revert .
Have you seen my privious post ,where i have provided some links that will provide
you some knowledge regarding dunning.
Data not picking from a table -
Need help regarding the dunning form
Hi,
I have to display all the sales and payments of a cusomter for all the periods that are older than the run date in a dunning form. (i.e) if the run date is 04-aug-05 and if the slaes are there in 3 months(april, May, july) then i have to display three line items with sales and payments for that corresponding three months in the line items. As this is a dunning form i cannot change the print program. any table which have all the sales for a period which i can access directly in the script. can anyone suggest how to handle this.
regards,
AshaHi,
You can call a subroutine within a program (your z program)
/: PERFORM ADD_AMOUNT IN PROGRAM SAPLZFTP_F150
/: USING &W_AMOUNT&
/: ENDPERFORM
In the z program create this subroutine.
Form ADD_AMOUNT
-->FT_INVAR Text Symbol table for input variables
-->FT_OUTVAR Text Symbol table for output variables
FORM add_amount TABLES ft_invar STRUCTURE itcsy
ft_outvar STRUCTURE itcsy.
STATICS:
w_value_l TYPE f150d-salfw.
READ TABLE ft_invar INDEX 1.
IF sy-subrc IS INITIAL.
you can check all this part of the code how you want to
process your data whether its numeric or character or
whatever
w_value_l = w_value_l + ft_invar-value.
ENDIF. "IF sy-subrc IS INITIAL.
ENDFORM. " ADD_AMOUNT
TO BESPOKE THE PRINT PROGRAM FOR THE DUNNING
Dunning outputs use the function module FI_DUNNING_PRINT_NOTICE. You can copy this to a Z function module and make some changes to the data selection. You will have to look into the code and decide what changes you need.
The process to use a bespoke program to do the dunning print is as follows:
UNDER FI GLOBAL SETTINGS in the configuration,
There are Business Transaction Events. Within that you can configure the same to enable a Z function module in place of the standard function module (from the FUNCTION GROUP F150)
Create function group ZFTP_F150
Copy standard function module FI_PRINT_DUNNING_NOTICE of function group F150 to ZFTP_FI_PRINT_DUNNING_NOTICE in function group ZFTP_F150
Copy standard function module PRINT_DUNNING_NOTICE of function group F150 to ZFTP_PRINT_DUNNING_NOTICE in function group ZFTP_F150
Within the function module ZFTP_FI_PRINT_DUNNING_NOTICE, change function module call for PRINT_DUNNING_NOTICE to ZFTP_PRINT_DUNNING_NOTICE
Create a new include ZFTPI_ROUTINES within the function group and copy the subroutines LOG_MSG, LOG_MSG_TAB, & LOG_SYMSG from the function group F150 to this include
AS AN ALTERNATE, YOU CAN COPY THE WHOLE FUNCTION GROUP
Maintenance view TBE31 (SM30). Change the function module from FI_PRINT_DUNNING_NOTICE to ZFTP_FI_PRINT_DUNNING_NOTICE against the event 00001720 FI-FI entry
Hope this helps.
regards,
Satya -
Update Dunning level on Customer(KNB5-MAHNS)
Hi experts,
I have request to update dunning level of customer (field KNB5-MAHNS) from another system using BAPI or something.
I can't find any BAPI for this purpose.
Anybody have some ideas or solutions for this problem?
Thanks,
DrazenAs far as i know there is no "actual" BAPI to update Customer (AR) master data so you may look at IDoc [DEBMAS05|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=debmas05&adv=false&sortby=cm_rnd_rankvalue] and write a program to use it or use [LSMW|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=lsmwCustomermaster+data&adv=false&sortby=cm_rnd_rankvalue] and direct input/batch input.
Regards -
Dear all
In our system, we maintain the dunning intervals is 15 days i.e 30 / 45 / 60 and 75 days.
but now the user wants the dunning report 30 / 45 / 60 and 90 days. Instead of 75, they send the last dunning report on 90th day. In dunning procedure, how can I set to skip 75 and run the dunning report on 90th day.
Please provide your best solution
Thanks in Advance
AburoseThank you for your respond
See I like to explain ie. We have Dunning Level 1 to 6 Level
under dunning level 1 these interval days 15 ie 30/45/60/75 was using at one Dunning Procedure. In Level 2 to 6 different days are maintain.
see
General data Tab
Dunning Interval in Days 15
No. of dunning Levels 4
Min.days in arrears 6
So please provide solution for me.
Thanks. -
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
maayaHi,
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 - 2nd level dunning is not working
Hello Experts
I have received a requirement from client for configuration of two level dunning (ie 14 & 35 days). I did the following configuration
(a) Defined the Dunning Area
(b) Defined the Dunning procedure in the following manner:
Dunning Interval in days - 1
No. of Dunning Levels - 2
Total Due items for Dunning - 0
Minimum Days arreas - 14
Line Item grace period - 14
Selected -> Standard transaction dunning
Under Dunning Level Tab
Days in Arrears - 14 & 35
We are not using interest & no penality charges.
Assigned the Dunning Test with the following combination
Letter 1 u2013
W_MHND-BUKRS = Company Name
W_MHND-MAHNN = 1
W_MHND_SMABER = Dunning Area
W_MHNK-MAHNA = u2018Dunning Procedureu2019
Letter 2 u2013
W_MHND-BUKRS = Company Name
W_MHND-MAHNN = 2
W_MHND_SMABER = Dunning Area
W_MHNK-MAHNA = u2018Dunning Procedureu2019
(c) Maintained the Dunning Area in customer master data -> Company code data -> Correspondance
(d) I have posted the sales invoice with posting date and due date as 01.03.2011.
While carrying the dunning activtity through T.Code F150 (I did the 1st level run with dunning date as 22.03.2011 ) -> All the activities are going smothly like Dunning selection completed, Dunning Print out completed and Sample Printout is completed for the 1st level
The second level dunning is carried on 26.04.2011 as dunning date. However, after completion of selection perameters. the system is showing as Dunning Selection is completed bu the system log says as follows:
Date Time Message
26.04.2011 15:34:12 Job started
26.04.2011 15:34:12 Step 001 started (program SAPF150S2, variant &0000000000523, user ID AMUNNALURI)
26.04.2011 15:34:12 ****************** Log for dunning run 20110430 / TEST1 ****************
26.04.2011 15:34:13 =========================================================================
26.04.2011 15:34:13 > Account D 0000000061, company code SC01 is being processed
26.04.2011 15:34:13 > Reading account data and document information Phase 0
26.04.2011 15:34:13 > Account D 0000000061 has a payment method for incoming payments
26.04.2011 15:34:13 > Account D 0000000061 read items: 11
26.04.2011 15:34:13 > Processing and completing dunning lines Phase I
26.04.2011 15:34:13 > Doc. 0090000052/2008/001 has payment method for incoming payments, no dun.notice
26.04.2011 15:34:13 > Document 0090000380/2008/001 has new dunning level 1.
26.04.2011 15:34:13 > Doc. 0090000381/2008/001 has payment method for incoming payments, no dun.notice
26.04.2011 15:34:13 > Doc. 0090000384/2008/001 has payment method for incoming payments, no dun.notice
26.04.2011 15:34:13 > Doc. 0090000387/2008/001 has payment method for incoming payments, no dun.notice
26.04.2011 15:34:13 > Doc. 0090000614/2008/001 has payment method for incoming payments, no dun.notice
26.04.2011 15:34:13 > Doc. 1400000052/2008/002 has payment method for incoming payments, no dun.notice
26.04.2011 15:34:13 > Doc. 1800000012/2008/001 has payment method for incoming payments, no dun.notice
26.04.2011 15:34:13 > Document 0064000433/2010/001 has new dunning level 2.
26.04.2011 15:34:13 > Document 0064000437/2010/001 has new dunning level 2.
26.04.2011 15:34:13 > Document 0064000438/2010/001 has new dunning level 2.
26.04.2011 15:34:13 > Check legal dunning procedure and credit memos Phase II -
26.04.2011 15:34:13 > Minimum charges and dunning interest Phase III
26.04.2011 15:34:13 > Generate dunning data Phase IV
26.04.2011 15:34:14 Job finished
If i continue the Dunning Print & Sample Print out.. the system is showing the following logs
Date Time Message
26.04.2011 15:35:31 Job started
26.04.2011 15:35:31 Step 001 started (program SAPF150D2, variant &0000000000344, user ID AMUNNALURI)
26.04.2011 15:35:31 > Start print phase
26.04.2011 15:35:31 0 dunning notices were read
26.04.2011 15:35:31 0 dunning notices have been printed
26.04.2011 15:35:31 End dunning printout 30.04.11 / TEST1
26.04.2011 15:35:31 Job finished
Kindly let me know, did i missed any steps in the configuration??
Regards
AnilHello Renan
Thanks for your reply, I am finding difference during 1st run and 2nd level run during selection perameters in the following area.
(Note that, we are not using the Interest / charges)
During 1st level dunning the system is showing as Dunning Level Log under Phase II, Phase III, Phase IV document no.
26.04.2011 15:30:38 > Check legal dunning procedure and credit memos Phase II -
26.04.2011 15:30:38 > Minimum charges and dunning interest Phase III
26.04.2011 15:30:38 > Interest indicator 0N and currency GBP are missing in T056Z
26.04.2011 15:30:38 > Generate dunning data Phase IV
26.04.2011 15:30:38 >
26.04.2011 15:30:38 > Account D 0000000061 dunning notice/dun.area. Dunning area 58 is being processed.
26.04.2011 15:30:38 > Account D 0000000061 dunning notice/dun.level. Dunning level 1 is being processed.
26.04.2011 15:30:38 > Account D 0000000061 uses dunning procedure DG3
26.04.2011 15:30:38 > Dunning level D 0000000061 is used for account 1
26.04.2011 15:30:38 > Document 0064000438/2010/001: Dunning level 1, days in arrears 20, status <.Dpi>
26.04.2011 15:30:38 > Account D 0000000061 dunning data has been generated.
26.04.2011 15:30:39 Job finished
Where as for 2nd level dunning the system is showing under Dunning Level Log is as follows:
26.04.2011 15:34:13 > Document 0064000438/2010/001 has new dunning level 2.
26.04.2011 15:34:13 > Check legal dunning procedure and credit memos Phase II -
26.04.2011 15:34:13 > Minimum charges and dunning interest Phase III
26.04.2011 15:34:13 > Generate dunning data Phase IV
26.04.2011 15:34:14 Job finished
Due to this, i am presumed that some more configuration has been missed at my end.
Kindly revert with your observations in the above log
Regards
Anil -
Hi experts,
could you please in details explain me how to create a dunning (output type MAHN) for purchase order?
Thank you.
Regards,
J.Hi,
It's easy.
First, update the data of dunning in the vendor data, they are copied to the PO.
Second, run the tcode ME91F (eg: periodically with a job). Set the vendor, type of PO and so on. Create a variant with dinamyc data.
Finally, run ME9F for the output messages. Form MEDRUCK is prepared for urging or dunning.
I hope this helps you
Regards,
Eduardo
Edited by: Eduardo Hinojosa on Oct 15, 2009 5:51 PM
Maybe you are looking for
-
N8 Belle connection failed- access denied. NO INTE...
After the Belle update I have a problem with my internet connections. Both WiFi and mobile internet are not working at all. At first it was ok but after a while or a reboot of the device I simply cannot connect to any wifi wether it's a known one or
-
What do I need to mirror my ipad2 display to my projector?
Projector only has inputs for VGA, s-video, and RCA. I have an off brand 30-pin to RCA that was working for YouTube videos on my original iPad, but the ipad2 won't show anything using that cord.
-
Hi, I am writing queries which work very well and have managed to use a parameter to dynamically select the data I need (basically Purchase Orders raised from a Sales Order Number) SELECT T0.[DocNum], T0.[CardName], T0.[DocDate] FROM OPOR T0 INNER J
-
Changeing Scrip in Live Environment
Hi, I've update an existing script, i've uploaded it and now want to swap the script in the Application from the drop down menu box.... My question is, when i do this is there any chance of losing an inbound call, as in during the mouse click on appl
-
Change document type within transaction ABSO
Hello Experts, I am trying to change the standard document type AA to AF for the transaction ABSO. But unfortunately I am getting posted in AA which I don't want. Current situation : Created a new transaction type Z42 copying an existing transaction