Error in short pay report generation

Hi
We run reports for review of customer short pays which are set up as an SAP Query in specific user groups
These reports lists short pays for one type of customer groups. The issue I am facing is that the report is adding individual lines to be able to get the CSR identified. So the # Days open is added and then I have the Avg selected in the query. I only want the average column which would take the addition of each line on the order and then divide by the # of lines. I have the same problem with short pays and average values.
This error is seen for reports which have invoices not the ones without invoices.
Firstly I wanted to know where to address this issue using report painter transaction  GR22 or using the SA38/SE38 editors.
Any ideas as to how to solve this would be greatly appreciated.
Edited by: sapsap10 on Aug 19, 2010 7:45 PM
Edited by: sapsap10 on Aug 23, 2010 8:49 PM

Hi,
Please provide some sample data to explain you issue. Youe requirement is not very clear.
Regards,
Gaurav

Similar Messages

  • Error -241741785​1 using Report generation toolkit

    I try to use the Report Generation toolkit (Version 1.0.1) for MS Office und the example "Generate Report from Template (Excel).vi" return an Error -2417417851
    I run Labview 6.02, on Win2000 German, and use Office 97 (Everything is installed (included MS Graph))
    Did someone experienced such a problem and found a solution?
    Thank you for your Help!

    Is LabVIEW and Office both German? Under Control Panel >> Regional Options >> General, is the language set to German? How about under Regional Options >> Input Locale? Reboot if you make any changes.
    I would suggest reregistering the nireports.dll. It is located in the National Instruments\Shared\NI Reports directory.
    http://digital.ni.com/public.nsf/3efedde4322fef198​62567740067f3cc/4f811a9b23f1d46e862566f700615b7a?O​penDocument
    Next, mass compile (Tools >> Advanced >> Mass Compile...) the LLB's in the \vi.lib\addons\_office
    Chris_Mitchell
    Product Development Engineer
    Certified LabVIEW Architect

  • Error Showing While Using Report Generation ToolKit VIs

    Hi All,
               When I use report generation VIs Like Excel Easy Tables its showing following errors and i am not able to contiune using the same,
    C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\utility\NIReport.llb\Set Report Font.vi
        - LabVIEW 8.0 changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
        - LabVIEW 8.0 changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
    what might be the issue, i am using LabVIEW 8.2

    Hi,
    In
    LabVIEW 7.1 and earlier, subVIs could be kept in memory by wiring a
    constant to a Case structure and placing the subVI in a case that would
    not be executed. For example, you could wire a True constant to the
    Case structure and place a subVI in the False case of the Case
    structure, and LabVIEW would load the subVI along with the calling VI.
    However, from LabVIEW 8.0 onwards, the case structure is optimized to remove code that is not going to be executed. Changing the
    constant to a control ensures that this VI behaves as it did in LabVIEW
    7.1 and earlier. If the intent is not to keep the subVIs in memory, you
    can change this control back to a constant by right-clicking the
    control and selecting 'Change to Constant' from the shortcut menu. The
    proper way to keep a subVI in memory without calling it is to use a
    Static VI Reference.
    Good Luck!
    Warm regards,
    Karunya R
    National Instruments
    Applications Engineer

  • Error only in PDF report generation not HTML

    The same report exports fine in HTML. This only happens when exporting a PDF report:
    com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: 26---- Error code:-2147467259 Error code name:failed
    The application was developed by our developer team and it is hosted in a Windows Server 2008 R2.
    Does someone had the same problem ?
    Thank you.

    We solved but not so sure about the cause.
    It had something to do with character encoding in PDF reports.
    Thank you for all that read the question.

  • Error 1045 Using Report Generation Excel 2010

    Hello,
    The attached code throws an error 1045 when using Excel 2010.  I don't get this error when using Excel 2007.
    Please Advise
    Thanks
    Attachments:
    Source.zip ‏66 KB

    Take a look at this Knowledge Base article and see if if helps.
    Error 1045 When Using Report Generation Toolkit for Microsoft Office
    http://digital.ni.com/public.nsf/allkb/3E4102D8B91D0F9E86256CE0006BADCB
    Applications Engineer
    National Instruments

  • Cisco ISE 1.1.1.268 Giving error (Report Generation failed. Cause: Null)

    I have this issue and I would be very thankful if someone has the answer for this. When I am trying to access Operation > Report > Catalog > Posture > Posture Detail Assessment & clicking on any posture session detail icon. I am getting following attached errors.
    1.     Report Generation failed. Cause: Null
    2.     Cannot execute the statement.
    Does anyone knows how to get rid of this error & to get access of posture detail.
    Thanks

    The error message means that Active Directory server Reject the authentication attempt
    as for some reasons the user account got locked.I guess, You should ask your AD Team to check in the AD
    Event Logs why did the user account got locked.
    Under Even Viewers, You can find it out
    Regards
    Minakshi (Do rate the helpful posts)

  • Ridiculous number of directories when build includes Report Generation Toolkit

    I was getting error 7 with the report generation toolkit, so I followed the steps here and it works. Only problem is, it makes a different support directory for each individual file in the NIReport.llb directory.
    The calendar and data directories are my own. The rest are the RGT.
    Help? haha.
    CLA, LabVIEW Versions 2010-2013
    Attachments:
    buildsetup.PNG ‏49 KB

    I set NIReport.llb to always included like it said, but it wasn't showing up after I did a build. So...I left it included always, I created my own destination with the same name (NIReport.llb) on the Destinations page of the app builder, went to the Source File Settings page of the app builder, selected NIReport.llb and set the location to be my NIReport.llb folder I created. I did a build and this solved the problem and all the NIReport.llb files were placed in a NIReport.llb directory. Someone pleaseeee tell me if there is a better way, but this will work for now.
    CLA, LabVIEW Versions 2010-2013

  • Report Generation Toolkit Evaluation doesn't work

    Hello,
    I tried to insert data into an Excel file but it seems the Report Generation Toolkit Evaluation doesn't work.
    Attached file my VI.
    LV is saying i have to activate the product in order to run it. An error occurs on each Report Generation subVI, which involve i never could test my application.
    I went on Help/Activate Labview component and the evalution is well activate.
    Someone has an idea why the evaluation version doesn't run Report Generation Toolkit ? A solution asap please...
    PS : I still have 15 days evaluation left.
    Solved!
    Go to Solution.
    Attachments:
    Test_insert_data.vi ‏9 KB
    Test.xls ‏14 KB

    UP
    With message failure
    Attachments:
    Sans titre.JPG ‏50 KB

  • Report Generation Toolkit Excel errors and Libraries, Classes

    Hello All,
    I'm using the Report Generation toolkit Excel functions to handle some data and create graphs.  I'm running into problems with the Add Worksheet.vi.  At the very start of the vi, it closes the reference to Shapes.  Occasionally, the Close Ref will throw an error.  I haven't pinned down the exact cause yet (probably an invalid reference).  The error itself wouldn't be a problem.  Under other circumstances I would choose to ignore it and continue on.  The problem is, this is stored in a Class Library controlled by NI.
    Solutions I've tried without success:
    1.) Make changes, and save the new vi with another name - can't do it because it's encapsulated and the Library is password protected.
    2.) Install toolkit in something other than the default folder, so I can make changes and put it under Source Control - installer doesn't allow a new path to be entered.
    3.) Change the vi where it is.  This works until I move the source to another computer or I update Labview.  At that point I lose all my changes.
    Maybe it's just my inexperience with Classes, but I just don't see an elegant solution to this.  Ultimately I'd like to copy the library off to somewhere else and put it under Source Control so I can make changes and additions to it (NI folks - providing a password to unlock the lib would be helpful...).  Does anyone have suggestions on how I can accomplish this?
    Thanks in Advance,
    Doug

    Hi Ben,
    Sorry about the first post.  After re-reading it, it sounds more like a frustrated rant than a request for help.
    I've attached a simplified vi to try to illustrate the problem I'm having.  I'm running Excel 2007.  Please open the vi, then open Excel Add Worksheet.vi.  At the start of the vi, Close Ref for Excel.Shapes occasionally throws an error.  So far, I have not been able to consistently reproduce the error, so I can't really troubleshoot it.  As I recall, the error code is 1045.  The error is carried through the rest of the vi, causing invalid references to be written to Excel._Worksheet and Excel.Shapes, going out to NI_report.ctl.
    So, here are the issues I'm running into (other than the error itself):
    1.)Short of closing and reopening the file, there is no way to recover from the error.  After the error, there is an invalid reference in Excel._Worksheet.  There is no vi available to regenerate references in NI_report.ctl.  I could easily write a vi to start from Excel._Application and re-read them, but because NI_report.ctl is in a Class library (controlled and passworded by NI), I can't add the vi to the library.
    2.) I found that I could ignore the error by wiring around it.  If I disconnect Error Out from Excel.Shapes Close Ref and wire Error In from Excel.Sheets.Count to the Error In of the Close Ref, everything works fine.  Under other circumstances, I'd save this with a new vi name (because functionality changed) and continue on.  But, because the vi is part of a Class library (controlled and passworded by NI), I can't do this.  I can save the vi with the modifications (because Excel Add Worksheet.vi is not passworded), but if I pass the source off to someone else, they will have to make the same changes on their installation of the NI Report Generation Toolkit.
    Again, I can't reproduce the error with any regularity.  I've run the example vi I provided a few times and everything seems to work fine.  If I come up with something, I'll repost.  If you (or anyone) has an idea of what could be failing or if they've seen the problem, I'd appreciate a comment.
    Thanks again,
    Doug
    Attachments:
    Excel Fail.vi ‏15 KB

  • Open vi error for report generation toolkt

    Originally it works fine.
    Now I upgrade to win7, LV9 and office2010.
    To open the old program by 8.6.1, I reinstalled LV 8.6.1 and report generation toolkit.
    But still got the error as attached.
    Any suggestion, thanks.
    Attachments:
    ss.png ‏184 KB

    1. MS Office 2010 is not yet supported, since it's still just a beta. I believe there are couple of changes that Microsoft make, and it could cause a problem.
    2. LabVIEW 8.6.1, and all its toolkit is not supported on Windows 7. This could cause a problkem also.
    In conclusion, you should use LabVIEW 2009, Report Generation Toolkit 2009, Windows 7, and downgrade office to XP, 2003 or 2007.
    More information: http://digital.ni.com/public.nsf/allkb/C9408B9F08D​711E786256F3300701D01

  • Report Generation Toolkit Error (undefined erro)

    Does anybody know what error -214 682 7864 (0x800A01A8) means when coming from the Report Generation Toolkit.
    I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet. The error was generated all the way down in NIReportGenerationToolkit.lvlib:Excel_Get_range.vi (this is the ActiveX code).
    Any ideas? 
    nrp
    CLA

    nrp wrote:
    I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet.
    Was it the first time you attempted to write the table to that spreadsheet?
    Maybe the error is due to the spreadsheet grown oversize than its limit so that it cant accomodate the table anymore.
    What is the version of MS Office you are using? I think Office 2003 can go only upto 1024 columns...
    - Partha
    LabVIEW - Wires that catch bugs!

  • Report Generation Exe Error

    Hello,
     I am using LV 8.6.1 with the 1.13 report generation toolkit and I am having problems getting my built exe to work.  I am trying to open an excel template and populate it with new data.  I have broke the vi down to just opening excel - opening the template and then fill in some data.  But at this point excel does not open at all.  And naturally everything works fine in the development environment.
    Error Code: -2147352573
    Member not found in NI_ReportgenerationToolkit.lvlib:
    Excel_open_workbook.vi
    NI_Excel.lvclass: new reportsubvi.vi
    I read a few help pages that said to add \vi.lib\utility\NIreport.llb and LVclass directories to the project folder and add them to the always include section of the build.  But no luck so far.
    Side question:  The machine I want to use this on has 8.6.1 Full which does not have the extra excel functions that my developer has.  Is there a way to install the DEV report generation toolkit in the full version?  Then I would not need to build an exe.
    UPDATE:  I just tried the exe on a different machine that has a developer suite installed and it worked fine.  So I guess I need to find out what else I need to add to the build to make it work.
    Message Edited by _Bryan on 06-16-2010 11:58 AM
    Solved!
    Go to Solution.

    There should be some info on this in the KB.
    But first you should make sure that your version of the report generation toolkit actually supports excel 2000 (which is 10 years old)
    That should be in the release notes of the toolkit
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • Report Generation Toolkit producing error -2147417842, "The application called an interface that was marshalled for a different thread."

    Hi everybody,
    I've got an application that logs data to an Excel spreadsheet using the Report Generation Toolkit.  My VI's have worked fine in the past using Excel XP, but since I've upgraded to Excel 2007, I am getting COM errors like this one:
    "Error -2147417842 occurred at The application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi"  That is the exact wording, even with the weird punctuation and capitalization.
    The first occurrence of the error is not determinate.  Sometimes, up to 10 logging sessions, involving a new .xls file, can occur before this error pops up.  Once this error occurs, I must quit LabVIEW to resolve it.  If I try to do anything with Excel, I always get this error, although sometimes it comes out of different source VIs.  Excel_Open.vi is another.
    These logging VIs have worked just fine until upgrading to Excel 2007.  I checked, and I was using a really old version of the Report Generation Toolkit, v1.0.1.  I read the documentation and had a big sigh of relief when I realized I needed to upgraded to v1.1.2 to get Excel 2007 support.  However, even after upgrading, I'm still getting the same errors.  I'm using LabVIEW 8.0.1, and I'm also building these VIs into an application.   The error occurs both in the LabVIEW IDE and in the built application.  Does anybody out there have any idea what I can do to fix this?  I googled a little, and discovered this is a COM error, but I can't find any references to the Report Generation Toolkit specifically.
    Thanks,
    Phil
    Solved!
    Go to Solution.

    Hi Christian,
    I do not see that exact option listed, do you mean "user interface"?  I recognize the "Run in UI Thread" option, it's on the Call Library Function Node.
    I checked, and my top-level VI has "same as caller" set, and I believe all my VIs are set to "same as caller".  Are you suggesting I change my top-level VI preferred execution environment to "user interface", or just the logging sub-VIs that use the Report Generation Toolkit?
    Thanks,
    Phil
    Attachments:
    VI_properties.png ‏15 KB

  • Report generation toolkit VI error when running EXE

    A VI inside the Report Generation Toolkit (version 1.1.2), Excel Find Application Directory.vi, will not function correctly when running an EXE.  The "Current VI's path" block will return the path of the currently running EXE rather than the path of the Excel Find Application Directory VI.  (The same would be true for Word Find Application Directory.vi.)
    -Joel
    Solved!
    Go to Solution.

    Have you had a look at this knowledgebase article? The error is caused due to the exclusion of any dynamic VI.
    Ipshita C.
    National Instruments
    Applications Engineer

  • Is ms office 2013 supported for report generation​? Error 41106

    Hi
    I have a copy of LV full development suite with the Excel and Word report generation toolkit added.
    I have recently changed to using Office 365 that includes offline versions of Excel and Word from Office '13.
    When using the report generation toolkit, I get an error 41106.
    I have reinstalled the toolkit - no effect.
    I sort of assume therefore that office 2013 is not supported?
    Any hints, tips, patches or workarounds please.
    Bill

    Bill_Shepherd wrote:
    Hi
    I have a copy of LV full development suite with the Excel and Word report generation toolkit added.
    I have recently changed to using Office 365 that includes offline versions of Excel and Word from Office '13.
    When using the report generation toolkit, I get an error 41106.
    I have reinstalled the toolkit - no effect.
    I sort of assume therefore that office 2013 is not supported?
    Any hints, tips, patches or workarounds please.
    Bill
    I've seen some issues when I upgraded to Office 2010. Note that it is possible that the route cause of your problem is totally different but in my case there was some ActiveX properties or Methods call that have been changed. I solved this issue by navigating to the property/method that caused the error, clicked on it and reselected the same property/method. You could probably find some older post that discuss that. Hope this help.
    Ben64

Maybe you are looking for