Difference between revisions of "Developing Jasper Report Solutions for Opentaps"
LeonTorres (talk | contribs) m (Protected "Developing Jasper Report Solutions for Opentaps": Sysop page [edit=sysop:move=sysop]) |
LeonTorres (talk | contribs) |
||
Line 3: | Line 3: | ||
= Overview = | = Overview = | ||
− | In this | + | In this document we will cover the full development of a Jasper Report solution for opentaps. The goal is to cover enough information so that you can create any kind of report or document desired. |
+ | |||
+ | The basis for this tutorial is the customer statement PDF that can be generated in the financials application. | ||
+ | |||
+ | * [[Image:CustomerStatementExample.pdf | Example of Customer Statement PDF]] | ||
+ | |||
+ | It is generated from the Balances by Customer report in the receivables tab. There are many features built into this particular document, which makes it an ideal candidate for study. | ||
+ | |||
+ | The PDF contains one statement for each party that was selected. Each statement contains the following information, | ||
+ | |||
+ | # Customer's billing address | ||
+ | # Company's logo, address, phone number and other contact information | ||
+ | # A list of invoices that have unpaid amounts | ||
+ | ## If the invoice is open and has a due date, then show the number of days since the invoice date to the statement date (age date) | ||
+ | # All invoice payments made in the 30 days prior to the statement date | ||
+ | # Other invoice payments made in the 30 days prior to the statement date | ||
+ | ## Any closed (fully paid) invoices related to these payments are listed for reference, so the customer knows what the payment was for | ||
+ | # Total open amount, which must be paid by customer | ||
+ | # Date brackets showing how much is past due and when. | ||
+ | ## If any amount is past due, a large PAST DUE will be displayed on the statement | ||
+ | # Layout designed for perforated page with perforation running down the right side | ||
+ | ## Information repeated on both sides for purposes of customer and return receipt | ||
+ | |||
+ | As you can see, this is a complex set of information that must be further grouped by partyId. We will cover all the steps in creating this document. | ||
+ | |||
+ | = Development Process = |
Revision as of 20:57, 22 August 2008
Contents
Overview
In this document we will cover the full development of a Jasper Report solution for opentaps. The goal is to cover enough information so that you can create any kind of report or document desired.
The basis for this tutorial is the customer statement PDF that can be generated in the financials application.
It is generated from the Balances by Customer report in the receivables tab. There are many features built into this particular document, which makes it an ideal candidate for study.
The PDF contains one statement for each party that was selected. Each statement contains the following information,
- Customer's billing address
- Company's logo, address, phone number and other contact information
- A list of invoices that have unpaid amounts
- If the invoice is open and has a due date, then show the number of days since the invoice date to the statement date (age date)
- All invoice payments made in the 30 days prior to the statement date
- Other invoice payments made in the 30 days prior to the statement date
- Any closed (fully paid) invoices related to these payments are listed for reference, so the customer knows what the payment was for
- Total open amount, which must be paid by customer
- Date brackets showing how much is past due and when.
- If any amount is past due, a large PAST DUE will be displayed on the statement
- Layout designed for perforated page with perforation running down the right side
- Information repeated on both sides for purposes of customer and return receipt
As you can see, this is a complex set of information that must be further grouped by partyId. We will cover all the steps in creating this document.