Parameters in Dunning Letter in Crystal?
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.
Hi Wendy,
Please repost to the SAP Business One Application space.
-Abhilash
Similar Messages
-
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 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. -
Import Crystal Reports Dunning letter as SAP Business One layout
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.
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. You also don't get any errormessage when the layout cannot be imported.
Anybody knows what parameters to use in this report? Thanks.
Regards ThijsHello Gordon/ Rahul,
Thanks for yor reply.
I already created a Crystal report that runs as a report. In this case you select the WizardName and the report will give an output of all dunning letters in this report.
Unfortunately it is not possible to import this report because when I do that I only get the error that SAP Business One couldn't import the layout. EXporting a layout is af course not possible because only PLD layouts are available in dunning.
Regards Thijs -
'Dunning Letter Print from Dunning Letter Generate'
hi,
How can i run the "Dunning Letter Print from Dunning Letter Generate" standard program without runing the spwaned program called 'Dunning Letter Generate'.I mean i want to run the 'Dunning Letter Print from Dunning Letter Generate'(execution method: report) independently.
I need to pass the parameters to the 'Dunning Letter Print from Dunning Letter Generate' directly instead of passing to the spwaned program ''Dunning Letter Generate".
Thanks
DevenderHi 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 -
Dunning Letter Creation in XMLP running into Error
Hi All,
Although I'm trying to create a report from the seeded Dunning Letter concurrent program that is giving the intended XML files but when running the XML Report Publisher Concurrent program, the program is erroring out with the following error:
*****************************************Start of Log *************************************
XML Publisher: Version : 11.5.0 - Development
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XDOREPPB module: XML Report Publisher
Current system time is 11-AUG-2006 09:13:51
XML Report Publisher 5.0
Updating request description
Waiting for XML request
Retrieving XML request information
Preparing parameters
Process template
--XDOException
java.lang.reflect.InvocationTargetException: oracle.xdo.parser.v2.XPathException: Extension function error: Method not found 'set_xslt_locale'
at oracle.xdo.parser.v2.XSLExtFunctions.getMethod(XSLExtFunctions.java:285)
at oracle.xdo.parser.v2.XPathExtFunction.evaluateMethod(XPathExtFunction.java:267)
at oracle.xdo.parser.v2.XPathExtFunction.evaluate(XPathExtFunction.java:225)
at oracle.xdo.parser.v2.XSLVariable.getValue(XSLVariable.java:205)
at oracle.xdo.parser.v2.XSLStylesheet.processVariables(XSLStylesheet.java:638)
at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:503)
at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:485)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:264)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:150)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:187)
at java.lang.reflect.Method.invoke(Native Method)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(XSLT10gR1.java:580)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:378)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:197)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:156)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:916)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:869)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:204)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1497)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:913)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:1766)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:1277)
at oracle.apps.xdo.oa.cp.JCP4XMLPublisher.runProgram(JCP4XMLPublisher.java:807)
at oracle.apps.fnd.cp.request.Run.main(Run.java:148)
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
Current system time is 11-AUG-2006 09:13:59
**************************************End of Log *******************************************
As u can c from the error, it seems to indicate that I'm using the method 'set_xslt_locale' which evidently I'm not using in my Template. Does anyone 've any ideas as to why this error is been thrown out.
I even tried putting a template with just the text as 'This is a test Template' in the RTF Template. I still get the above errors.
Any potential workaround too greatly appreciated.
Thanks for ur time.One thing of note is that when I downloaded the template using XDOLOADER, the xml publisher seems to 've created a .xsl file that has reference to the method mentioned above. So although, I'm not referencing it, XMLPublisher created .xsl is referencing it n hence the error. Also, I do remember having read that 'set variable..' method refernced above is only available for a higher version of XMLP. I think I'm on 5.0.
So the question is do I've to upgrade to 5.5 or can I make do with 5.0 version? I would love to get around this problem without the upgrade.
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 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.GHi 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 -
How can the dunning letter shows O/S amt and corresponding aging bucket?
Hi,
I am going to implement the dunning letter setup in R12. Our user request to have the dunnng letter layout which should show all regular dunning details but also the aging info of the outstanding invoices, i.e. which aging bucket the outstanding amount will be shown. Anybody have idea and help? Thanks a lot.
EdmondThank 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. -
Hi,
explain the steps to create dunning letter?
how should i retrieve the letter from PLD to dunning letter levels?Hi Subashini
You can get to the dunning terms from Administration > Setup > Business Partners > Dunning Terms, or select the Navigation Arrow next to Dunning Terms on the Payment Terms TAB of the BP master. You can also go to Administration > Setup > Business Partners > Dunning Levels.Then click on the PLD (Pencil) and select the letter you want to edit.
The dunning terms can be set up per customer or group of customers if there are multiple ways of treating customers. If not then you will only need 1 dunning term. On the dunning term, select the first row and choose the level letter for it (usually 1). Then set the parameters such as effective after (days) - based on due date. A new line will automatically be added as you tab through the columns. On the next row select the next level letter (usually 2) and so on. If you only need 3 levels for example, then you only need to change the PLD for the level letters selected.
The level letter will be selected based on the days over the due date and whether or not the BP has been dunned before. Under the accounting TAB of the BP Master, it will display the last dunning run date and level for each BP.
Hope this helps
Kind regards
Peter Juby -
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 2005Hi 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 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.GHi 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 - email/pdf problem
I want to email a dunning letter to a customer.
I have executed a dunning run.
I go back to the Recommendation report for the dunning run - when I highlight the row under the customer name and click print preview I can see a preview of the dunning letter I want to email.
When I click the 'Email' button and click 'Yes' to attach an edited report I thought that would attach the letter to an email as a PDF? (I have send E-Mail via Microsoft Outlook' selected)
But when I check my Outlook sent box the email has been sent but there is no attachment of the dunning letter - it's just an empty email?
I tried again and examined the 'Send message' box that appears when I click the 'Email..' button.
The data tab shows the dunning run listed but the Attachments tab has nothing listed.
Should the file be listed here if it had correctly attached?
Incidentally when I click the PDF button this just brings up the same print preview instead of making a PDF of the letter - is this significant i.e is the PDF function not working hence the 'attach edited report' function also cannot work?
I'd be grateful for advice on emailing dunning letters correctly
KarenHi Andrew,
Check this Link
Re: Email Dunning Report to the BP
Re: Automatic Dunning By Email
Regards
Jambulingam.P -
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 ChongHi,
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 -
Dear all,
I have configurated dunning with charges and interest. The charges appears in the dunning run but not the interest. I have done following:
- Entered interest indicator in the dunning procedure
- Ticked calculate interest on level 2 and 3 in dunning procedure
- Entered charges on dunning level 2 and 3
- Entered an interest rate in transaction OB42
Is there anything else I need to do for getting interest on dunning level 2 and 3?
We don´t have separate interest calculation (interest invoices), only interest on dunning.
Thanks in advance!
Best Regards LDear Maurizio,
Exactly, I want the interest to be visible on the print out but no FI document posted. But why is there no iterest in my dunning run and print out?
First havn´t enter any interest in OB42 and then I get information in log: Interest indicator 01 and currency EUR are missing in T056Z. So it seems that my configuration should work but not..
I have entered in transaction OB81:
01, EUR, 20110101, 1, Debit interest; arrears interest calc. 0,00, Premium 7,000000 (7% is our interest)
01, EUR, 20110101, 2, Credit interest; arrears interest calc. 0,00, Premium 7,000000 (7% is our interest)
Is above correct?
I have read note 82995 and 874603. In note 874603, do I have to do all settings for interest calculation when I only want interest as information on printout? I understand the note that the information about interest calculation is when I have interest calculation separate from dunning (as FINT) and I don´t need to do all those settings when only information on dunning letter. Correct?
Thanks in advance!
BR L
Maybe you are looking for
-
I can not find a newer version.
-
Is there anyway that Mail 4.2 on OS X 10.6.3 can utilize a mailbox in a secured sparse bundle file system? This is what I would like to have: I use two imap accounts with various mailboxes within them, and I have a set of mailboxes on my Mac. I would
-
Problem with mail after downloading lion
i just loaded lion. opened mail, i have new messages however they will now open in the reading pane "loading"
-
Hi Friends, I know the procedure of Cancle excise Invoice 1 - Cancle GRN - MIGO 2 - Post Excise Invoice - J1IEX 3 - Cancle the Excise Invoice - J1IEX But when i go to post Excise Invoice in J1IEX i am getting following error " No Part I exists for a
-
BEFW11S4 2.1 firmware problem
Hi, While attempting to update to firmware on a BEFW11S4 v2.1 to 1.45.10 from a MacBook Pro I am getting the following error message: Upgrade action is not finish!! Upgrade file pattern error. I've followed the instructions as closely as I can and