Reply from Tomasz_J on Jun 9 at 1:35 PM Hi Sham,
The above advices are obviously very useful but most of them focus on some details, neglecting the others. I think what you really need is a genuine birds-eye view on the "solution landscape". Here a couple of my remarks, the result of 12-year experience in SAPscript, smart form and Adobe form programming.
The question is what you really need. Logically, an invoice list is a set of invoice numbers.
Thus, the simplest solution is what follows:
1. Create and setup an appropriate INVOICE LIST (IL) output type using NACE;
2. As the IL print program, write a simple Z-program which will :
2.1. At time of printing, use the IL number to create a relevant VBRL internal table;
2.2. Copy the output settings from the NAST record as passed from RSNAST00;
2.3. In a loop over the VBRL int. table, in each loop cycle, call the existing INVOICE print program in a way analogous to how the RSNAST00 report calls the invoice print program during regular invoice printout (that means setting the structure values of NAST and TNAPR accordingly -- you must arbitrarily set the INVOICE output type to one of the existing output types!!).
3. The above-described solution will produce a set of successive invoice printouts, each of which is identical to the output as generated by using VF02 for each of the constituent invoices. Its main advantage is that you don't have to change anything at all in the existing invoice smart form and print program. One of the main drawbacks is that the IL's number is never mentioned anywhere in the resulting set of printed pages and e.g. some of the invoices might simply get lost because someone carelessly threw away two of the 10 pages from the printer tray etc. -- there is no way of telling if the set of paper pages is complete or not. And so on, and so on.
4. Thus, If you wanted some additional features, you would have to turn to more programming.
4.1. One feature people want is an invoice list cover page: a simple page with e.g. payer's address, vendor's addresses, the INVOICE LIST title and its number. The cover page might also have a simple list of all the constituent invoices printed one below another.
You might also want each of the invoices to have the invoice list number added beneath the invoice number. Finally, you might also want to print an ending page, saying e.g. "end of invoice list no. ....".
4.2. Such solutions require additional smart forms. If you don't change anything in a single invoice's printout, you might still avoid making any changes to the existing invoice print program/form. However a cover and/or ending page for the invoice list require additional smart forms. One for the cover page, the other -- for the ending page. The smart forms will be very simple. However, you must remember, that the page numbering will be "local" for each of the following: a. invoice list; b. each invoice (each will start from 1). c. the ending page. thus, on the cover page you will most often "page 1/1" (if the cover page fits in just one physical page), then each invoice will be numbered independently 1, 2, 3... , 1,2,3 ... 1,2,3, finally the ending page will be again numbered as "page 1". Moreover, you have limited control over the spool request creation.
4.3. So, the best solution is to copy the existing INVOICE print program and form to the Z-versions, and assign them to all the relevant INVOICE output types. Then, modify the INVOICE print program and form so that the pages will be numbered consistently (not quite an easy task but a feasible one, anyway and it does not require much work -- rather, much knowledge). It must be done smartly -- so that the IL-specific features would be ignored in a single invoice printout. Finally, call the modified, Z-, INVOICE print program from your INVOICE LIST print program for each of the constituent invoices. At any rate, the changes to the INVOICE print program /form will be fairly scarce.
Such an approach will ascertain future development consistency, as in a case when someone modifies how the e.g. payer's address is output -- this change will be automatically taken into account into both the single, regular invoice printout and in the printout of a invoice that is an invoice list constituent.
5. This text is long but based on practice and focusing on the most important features of such an IL development. Patience and Good luck !
Regards,
Tomasz
| | | ---------------Original Message---------------
From: Josef
Sent: Thursday, May 31, 2012 9:19 AM
Subject: Billing Document Does Not Exist in VF22
Hi Gurus,
Currently we are working on creating a new smartforms for Invoice list (VBRK-VBTYP = 3).
This invoice list will be printed out via VF22.
We've setup the new output type in NACE and call the print program - RLB_INVOICE for this newly created ZSMARTFORMS.
Anyhow, found out that the print program RLB_INVOICE only support VBRK-VBTYP 'M','N','O','P','S','U','5', and '6'.
Any idea how to deal with this or anyone have alternate print program to use? Truly appreciate for the answer..
Regards,
Sham. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
