SQL Server Performance

Invoice/Statement Process Implementation

Discussion in 'SQL Server 2005 Reporting Services' started by latingntlman, Jul 10, 2008.

  1. latingntlman New Member

    The company has our dept to try to come up w/ a solution for our current invoice/statement process and implement an email function for sending out invoices to customers w/email address. Below is the current process and what's desired.
    1) Customer places an order via internet or call center.
    2) A process runs that prints a pick ticket for order fulfillment.
    3) A nightly batch process runs that creates a print batch of invoices for order items that have shipped.
    4) The batch is printed in the morning by accounting and invoices are manually separated and mailed to the customers.
    What accounts wants to happen:
    1) Customer places an order via internet or call center.
    2) A process runs that prints a pick ticket for order fulfillment.
    3) For any customers that have an email address, email then the invoice electronically in PDF format.
    4) A nightly batch process runs that creates a print batch of invoices for any wholesale orders not emailed.
    5) The batch is printed in the morning by accounting and invoices are manually separated and mailed to the customers.
    How do we get Reporting Services to auto-create these invoices nightly and batch email them to a dynamic list of recipients without creating an individual subscription for each customer. We need something simple, accurate, dynamic, and bulletproof. Eventually this will be rolled out to all customers.
    Another solution I can think of is to create a .Net application that would do the processing, imbed the Reporting Services invoice in an email, or attach as PDF, and send the email to the customer. This would be a lot of development work and would require this external application to be managed and monitored.
    Any ideas?
    thx,
    John
  2. satya Moderator

    You need extensive development of Reporting Services technology here and BOL refers that:
    Report Definition Language Programming
    Report Definition Language (RDL) is a set of instructions that describe layout and query information for a report. RDL is composed of XML elements that conform to an XML grammar created for Reporting Services. You can add your own custom functions for controlling report item values, styles, and formatting by accessing code assemblies from within report definition files. Moreover, RDL can be generated programmatically. You can build third-party tools and applications that generate RDL in much the same way that Report Designer generates RDL. For more information about using custom assemblies with reports, see /msdn.microsoft.com/mshelp" />Using Custom Assemblies with Reports. For more information about generating RDL with custom applications, see Generating Report Definition Language Programmatically.http://www.holbornbooks.co.uk/books/201305/Teo-Lachev/SQL-Server-2005-Reporting-Services-in-Action/ the book by Teo Lachev can get more information for you.
  3. billflo_ian New Member

    John,
    we have an application, www.billflo.com, that does much of the front-end work you are looking for. Its free and very user friendly which would allow your account people to manage the messaging and interaction with the customer.
    I'm happy to talk with you in more detail if its of interest.
    Regards
    Ian Sweeney

Share This Page