Functional specification invoices Printing

Dear friends,
I require the functional specification for for the different types of invoice printing.
Please send me the samples.
Regards,
Vishal
[email protected]

Similar Messages

Functional Specification Invoice

Hi Guru's
Any Bady Could u Pls Send Functional Specification For Invoice With Tax.
My Mail ID is [email protected]
Regards
Sriram

A functional specification (or sometimes functional specifications) is a formal document used to describe in detail for software developers a product's intended capabilities, appearance, and interactions with users. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code. (At least one major product development group used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for a word processing system, then declared that the user's guide was the functional specification. The developers were challenged to create a product that matched what the user's guide described.) Typically, the functional specification for an application program with a series of interactive windows and dialogs with a user would show the visual appearance of the user interface and describe each of the possible user input actions and the program response actions. A functional specification may also contain formal descriptions of user tasks, dependencies on other products, and usability criteria. Many companies have a guide for developers that describes what topics any product's functional specification should contain.
For a sense of where the functional specification fits into the development process, here are a typical series of steps in developing a software product:
Requirements. This is a formal statement of what the product planners informed by their knowledge of the marketplace and specific input from existing or potential customers believe is needed for a new product or a new version of an existing product. Requirements are usually expressed in terms of narrative statements and in a relatively general way.
Objectives. Objectives are written by product designers in response to the Requirements. They describe in a more specific way what the product will look like. Objectives may describe architectures, protocols, and standards to which the product will conform. Measurable objectives are those that set some criteria by which the end product can be judged. Measurability can be in terms of some index of customer satisfaction or in terms of capabilities and task times. Objectives must recognize time and resource constraints. The development schedule is often part or a corollary of the Objectives.
Functional specification. The functional specification (usually functional spec or just spec for short) is the formal response to the objectives. It describes all external user and programming interfaces that the product must support.
Design change requests. Throughout the development process, as the need for change to the functional specification is recognized, a formal change is described in a design change request.
Logic specification. The structure of the programming (for example, major groups of code modules that support a similar function), individual code modules and their relationships, and the data parameters that they pass to each other may be described in a formal document called a logic specification. The logic specification describes internal interfaces and is for use only by the developers, testers, and, later, to some extent, the programmers that service the product and provide code fixes to the field.
User documentation. In general, all of the preceding documents (except the logic specification) are used as source material for the technical manuals and online information (such as help pages) that are prepared for the product's users.
Test plan. Most development groups have a formal test plan that describes test cases that will exercise the programming that is written. Testing is done at the module (or unit) level, at the component level, and at the system level in context with other products. This can be thought of as alpha testing. The plan may also allow for beta test. Some companies provide an early version of the product to a selected group of customers for testing in a "real world" situation.
The final product. Ideally, the final product is a complete implementation of the functional specification and design change requests, some of which may result from formal testing and beta testing.
The cycle is then repeated for the next version of the product, beginning with a new Requirements statement, which ideally uses feedback from customers about the current product to determine what customers need or want next.
Most software makers adhere to a formal development process similar to the one described above. The hardware development process is similar but includes some additional considerations for the outsourcing of parts and verification of the manufacturing process itself.
Regards,
Rajesh Banka

Need Function Module for Printing Rates,Discounts and Taxes in Invoice.

Hi All,
For our Invoice printing I need to get a function module which will provide me the rates,discounts and taxes against each item line of the Invoice No.
Finall it will be printed accordingly.
Can anyone help me regarding this with input parameter example.
Thx in Adv.

Hi,
As far as I know there is no fun module to print all this stuff.
You have to get this data from KONV table by passing the VBRK table KNUMV field.
Then check for all the Rates and amount KBETR and KWERT fields for the respective condition Types.
You have to loop the KONV internal table and write all the condition rates and amounts in the script driver program.
see any Std script for this.
Regards,
Anji

Functional Specification Documents for SAP Sales and Distribution

Dear Gurus,
I am having the problems of Invoice Output..... the default out put generated by the SAP is completely different from the hard copy of the Invoice of the Client. ppl say that I have 2 take the help of ABAPers to define the smart forms for the invoices of different company codes.... i had conversation with the ABAPers.... butthey are asking the format, wht ever the change we are looking for..... I am not be able to get the exact format.... how 2 provide this to ABAPers in FS format.
can any one pls send me ( or provide me the link to download the same from the SDN website) these Functional Specification Documents for Sales and distribution.
Wishes,
Abhishek

Hi there,
1st try to understand what is a functional specification doc before asking for it.
Functional specs is a doc in which you include what is the business requirement. If it requires a change to change to existing configs / code, then you will give the progs & the location where you will need to change. If the requirement is a totally new one, then yuo will explain the requirement in detail & possibly give the progs / code if there are any.
In your case, your client has a specific invoice format which is different from which SAP gives, in such cases, you will need to define a new Invoice output for eg ZINV. Define it as a print output. You will need to define a new print prog for the new output in which you will call smart forms to define the layout & fields.
Ask your business user to send the invoice copy which he has. Scan it & include it in the functional specs which you prepare. Mention all the fields which you want in the layout. Ask the ABAPer to code the invoice format in the same way. ABAPer is free to define any convinent name as per the guidelines (which he will be aware). You will need to assign that in the form routines of the output.
As a functional consultant you will need to give the field mappings (from where you get the data) for all the fields which you wish to print in the output. All that should be included in the func specs.
So there is no standard func specs that you can follow. Each func specs varies on the requirement. So dont ask these kind of questions in SDN forum. If you dont know how to define func specs, ask how to define. Dont ask people to send the sample func specs. Thats against the rules of conduct.
Regards,
Sivanand

Functional specification required for Me57 requirement

In SAP MM, Transaction ME57, I want to pull in the Common Inventory Quantity (Not Project or Sales Order Stock) of the Material which is maintained on the Purchase Requisition.
And also in the T code MB52 screen, the Inventory Quantity i want to bring it. It will be ALL Common Inventory in the Plant (minus Storage Loc a001 for Plant a000). Again, this should NOT pull in Project or Sales Order stock. Only Common Inventory.
I would like a rough functional specification draft ASAP. Pleas help.

Hi prasanna,
we can get SAP idoc types in tcode we31.For every requirment there will be different message type.
For example we want idoc type for account invoice receipt.
First find out message type for that purpose which can be found in we81-ACC_INVOICE_RECEIPT.
Get this message type and search in we82 where we can find message type and idoc type linkage.
try this way.
Reward if it is usful.
Thanks,
Srikanth.A

Maintain Output for delivery & invoice printing

I have maintained the output condition types in VV21 & VV31 to have automatic output option during my Delivery note printing & invoice printing.
And I have also maintained the Output determaination procedure & assigned to my delivery & invoice doument types.
But when I goto VL02n & issue to output, the next output screen pops up, but without the output types that I have maintained.
So I cannot send to the print option. Can you let me know if something is missing?
regards
pri

Hi Ann,
Just check the condion types tables as which combination you have selected, eg ., customer/country like that.
Now if that is correct see whether the proper out script or form has been assigned to V2( Shipping ) and V3 (Billing )applications in Transaction code " NACE ".
see while maintaining the condition records at VV21 whether the partner function is SH ( Ship to party ) and VV31 where it should be BP ( Bill to party).
See if it helps.
Thanks & Regards
Sadhu Kishore

Intercompany AR Invoices Printing with No Amount/Description

Greetings,
I'm currently having an issue with Intercompany invoicing. The process is working fine and the accounting is correct, however, when the invoices print all they show is the date and invoice number... The rest is a blank document with no description of the line items.
On our other Intercompany invoices it shows everything and lists Intercompany ar in the description of each line item. I'm only having this issue with one of the Orgs but I can't find anything in the interco setup or customer setup that could be causing this.
Does anyone have any idea as to what this issue could be? I'm on the functional side.
Thank you!

Hi,
i assume that you are using a CUSTOM REPORT for printing the Invoices generated by the system .. and this custom report should pick up relevant data based on the Invoice number ....
If above is the case, chances are more likely due to a validation that might have been placed in the custom report .. which is to pick invoices pertaining to particular operating unit and not for others ...
ELSE,
if the custom report picks up operating unit automatically based on the responsibility you use for running the report ... try running the report using different responsibilities and see the output ...
(Also do not use the copy option while submitting the concurrent program, re-enter the parameters afresh ..)
Regards,
Ivruksha

Automation of invoice printing?!!!!!!

hi all ,
I am new to sap script. my requirement is i have a z program and a z form for invoice printing ., in foreground its working fine.,, problem is i want to print invoices automatically when the user creates a invoice and clicks save.,, what has to be done now ? i am not clear about output types and spool plz help me out.,
reg
kannan

Hi Kannan.
To use the sapscript in an invoice, it must be associated with the output message.
Check:
transaction SPRO->Sales and Distribution->Basic Functions->Output Control->Output Determination->Output Determination using the Condition technique->Mantain Output Determination for Billing Documents.
Then, in VF03 check what message is being called. Is it is, for example RD00, you shoud assign the print program and sapscript to the output message.
But i think normal invoice only has the SMARTFORM option, instead of SAPSCRIPT.
In Smartform you must use this SPRO procedure too.
Reward usefull ideas!
Best regards.
Valter Oliveira.

Functional Specification Document needed

hi guys ...
i have been asked to write the functional specification document for the following issue... i have never wrote any functional Spec. till now... can n y one write it down for me...or tell me the exact format of how to write it down...
The issue is as follows....thx.
Invoice enhancements for tagging, serial number and email identification
1. Add the Customer Tagging Text to the invoice document.
2. Add Serial Number to the invoice.
3. Change the subject line for the emailed invoice from the generic "SPX Invoice $000000001" to the more meaningful format "SPX Invoice <invoice number>, SO <sales order number>, for <customer name>", the order acknowledgement already has a similar format
Please do reply.... thanks in advance.

Hi,
Broadly in SAP there will be two types of Consultants - Functional and Technical. Technical consultants are mainly working on developments / changes in programs using ABAP language.
On the other hand Functional Consultants understand the business process from Business users and map the functionality in SAP by doing required configurations and by designing reports.
Here comes the Functional Design Specification. The report / an extension is developed by Technical resource, but the design / explanation has to be given by Functional Consultant in such a way that Technical Consultant is able to understand it. In other words it should be a media for converting Business language into a language understood by Technical Consultant.
So, in a Functional design of a report Functional Consultant should furnish the following information:
   - Assumptions made
   - Pre requisites to be met for executing the report / transaction
   - Main Tables from which data to be selected
   - Selection Parameters for executing the report.
   - Logic for the Program
   - Layout of the report
Thanks
Murali.

How to print batch numbers on the AR invoice print out

Hi Gurus;
Here is my question; I need to be able to print batch numbers on the print out of AR invoices, I used variable 492 in PLD and I am able to see the batch numbers directly linked with the AR invoice, meaning that I wont be able to see batch numbers that I entered on the Delivery even is the delivery doc was copy to the AR invoice.
Is there anyway that I can see the batch numbers on the AR invoice print if I entered the batch number on the delivery and then copied that delivery to an invoice??
My client wants to be able to send their customers and invoice with a batch number but he always follow the process from sales order to delivery and delivery to AR invoice and what this means is that he always entered the batch numbers on the delivery documents.
Please help me!!!
Thanks
Jenny

If the ad hoc printer mode is not available for the envy, there are some reasonably cheap ways to get a wifi network in your car. A cheap router from best but will generate the wifi network. Does not matter if you have Internet or not. A ifi device will also work, and most/ all of them run on batteries. Lastly, if you have a smart phone or I phone that generates a wifi hotspot, that may be enough to support the printing function. ( I need to test my I phone later today to see if that works.)

Functional Specification for Document Status

Hi friends,
Can anybody provide FS (Functional Specification) for the folowing scenarioes
PART-A
1.No. of Enquiries received, Quotation not sent.
2.Avg. age of Enquiry
3.No. of Quotation sent. Order(Contract) not received.
4.Value of Quotation sent. Order(Contract) not received.
PART-B
1.No. of Delivery made, PGI not made
2.VALUE of Delivery made, PGI not made
3.No. of PGI made, PROFORMA INVOICE not made
4.VALUE of PGI made, PROFORMA INVOICE not made
5.No. of Proforma Invoice made, EXCISE INVOICE not made
6.VALUE of Proforma Invoice made, EXCISE INVOICE not made
7.No. of EXCISE INVOICE made, COMMERCIAL. INVOICE not made
8.VALUE of EXCISE INVOICE made, COMMERCIAL. INVOICE not made
"Thanks in advance"
Reagrds,
Srikky

Hi,
The output type available for Quotation rejection is ABSA and the programme name is SAPFM06P.Form routine ENTRY_ABSA.The form Medruck need to be changed by your abaper as per the text you need to incorporate.
Dhruba

Smart Form Functional Specification

Hi Gurus,
I have to design a smart form functional specification, but i don't have any idea about how to prepare the functional specification?
can anybody send me the smart form functional specification template ?
which helps me to prepare the specification

Hi Devi,
Here is the FS for Form,
Functional Specification Document for Forms
Authors
Approved By
TABLE OF CONTENTS
1     OVERVIEW SECTION:     3
1.1     DOCUMENT OVERVIEW:     3
1.2     REVISION HISTORY:     3
1.3     OPEN ISSUES:     3
1.4     EXTERNAL REFERENCES:     3
1.5     REQUEST OVERVIEW:     3
1.6     GENERAL PROCESSING REQUIREMENTS:     4
2     BUSINESS/FUNCTIONAL REQUIREMENTS     5
2.1     REQUIREMENT DESCRIPTIONS:     5
2.2     BUSINESS DRIVER     5
2.3     TO-BE BUSINESS PROCESS:     5
2.4     TO-BE BUSINESS PROCESS FLOW DIAGRAM:     5
2.5     ASSUMPTIONS:     5
2.6     DEPENDENCIES:     5
2.7     RISKS:     5
2.8     SECURITY:     6
2.9     OTHER REQUIREMENTS:     6
3     FORM SECTION     7
3.1     REPORT SELECTION SCREEN:     7
3.2     STANDARD FORM NAME:     7
3.3     FORM LAYOUT:     7
3.4     DATA SOURCE:     7
3.5     SPECIAL REQUIREMENTS PROCESSING:     7
3.6     HOW TO EXECUTE THE FORM:     8
4     UNIT TEST PLAN SECTION     9
4.1     FUNCTIONAL UNIT TEST PLAN:     9
5     USER GUIDE REQUIREMENTS     10
5.1     USER GUIDE REQUIREMENTS:     10
6     APPENDIX     11
6.1     APPENDIX:     11
1     Overview Section:
1.1     Document Overview:
(Provide the high level identification information about the object to be developed. Id, title, Release etc)
Project      Project Atlas
Development Object ID:     SC-F-125
Development Object Title:     Purchase Order Form
Release:
Process Team:     Supply Chain
Process Area:     Procure-to-Pay
1.2     Revision History:
{This section should be filled with other details about the owner of functional specs, current status of document as explained in the status key etc}
Date Modified     Version     Modified By     Description of Change(s)
1.3     Open Issues:
(Any open issues should be reported in this section)
Issue #     Issue Date     Issue Title / Description     Priority     Resolved Date     Any Other Comments
1.4     External References:
(Identify any documents referenced in any part of this document. (Attach documents where possible.)
Document Title     Filename     Author     Identifier (Version/Date)
Process Flow diagram      N/A
Screen Shots if any     N/A
Sample data file     PO Form Layout (Single Page)     Erik Kraus     1/ (10/11/2006)
Sample data file     PO Form Layout (Multiple Pages)     Erik Kraus     1/ (10/11/2006)
1.5     Request Overview:
Complexity     0   High
1   Medium
0   Low
System(s) Impacted     1   R/3
0   CRM
0   BW
0
     0   Other
Existing SAP transaction(s) involved?     ME22N, ME23N
New SAP transaction(s) involved?     ME22N; then click Messages to print or Print Preview to view.
Menu path for transaction(s)     Logistics  Materials Management  Purchasing  Change
1.6     General Processing Requirements:
(Check the appropriate boxes for e.g. if the development object is an batch report that runs monthly, then check the Online and Monthly boxes in the Processing mode and frequency section and also provide the expected data volume if known)
Processing Mode:     1   Online
0   Batch
Frequency     0   Annually
0   Quarterly
0   Monthly
1   Daily
     1   Real Time
1   Ad-Hoc
1   Others
Expected Data Volume
2     Business/Functional Requirements
Section 2 describes what is needed. This information is used to build the design (how to do it) in Sections 3 and on
2.1     Requirement Descriptions:
Describe the purpose of the object. Brief overview
The purchase order form is used to display the purchase order in SAP. This form can also be sent to the supplier via e-mail or fax in SAP. The PO can also be displayed in the Print Preview screen and printed out as well.
2.2     Business Driver
The PO Form is standard in SAP. Modifications to the form will be necessary to meet the needs of the purchasing organizations at Sage. The PO form is necessary so that all the details of the purchase order can be faxed/ emailed to the supplier and also can be printed out into a hard copy form for internal purposes. The PO form also needs to be able to be viewed via the print preview icon in SAP.
2.3     To-Be business process:
Describe the To-Be business process
Customized Sage Purchase Order Form.
2.4     To-Be business process flow diagram:
Describe the To-Be business process flow diagram
N/A
2.5     Assumptions:
List all the assumptions that were made when developing this object
1)     Standard SAP PO Form will need to be modified from its standard layout.
2)     Font for Purchase Order form will be Times New Roman
3)     PO Form will be created in English
2.6     Dependencies:
List all the dependencies that were made when developing this object
N/A
2.7     Risks:
(What are the risks that make this development unique? What risks need to be proactively dealt with in order to be successful? What data sources are needed but not readily available? Are there any risks or concerns that make this development out of the ordinary?)
N/A
2.8     Security:
(Any security requirement for this object)
2.9     Other Requirements:
(If there are any other requirement which is not covered under section 2)
N/A
3     Form Section
Type:      0 SAP Script     1 Smart forms
3.1     Report Selection Screen:
Describe the selection screen of the program. Specify fields for selection and what checks are needed after the user has entered their criteria.
Field Name     Select Options / Parameters / Radio Buttons / Check Boxes     Default Values
From To     Validation
     Required /Optional     F4 Values
N/A     N/A     N/A     N/A     N/A     N/A
3.2     Standard form name:
Give the name of the SAP Script or Smart form name if copied from SAP
MEDRUCK Form in SAP
3.3     Form Layout:
Describe the form layout for each page.
The PO form will contain information at the Header Level, Item Level, and Authorizations levels.
Header Level:
The header level will contain all the supplier, bill-to party/address, and ship-to party/address information. The header level will also contain the payment and shipping terms, logo, page number, purchase order title, purchase order number, supplier number in SAP, and the PO date.
Item Level:
The item level will contain the item number, material and description, order unit, quantities, date required, unit cost, and the total amount of the line-item. The item-level will also contain the line-item text of purchase order.
Authorization:
The authorization section of the form will contain the name, telephone number, and email address of the purchasing agent.
Other:
-The Total Amount and Currency will be displayed to the right of the Authorization information.
-The layout will include sections and fields with borders. For example the Ship-To, Bill-To, and Supplier will be enclosed in rounded edge boxes. The Layout can be viewed in the Attachments section:
portion of section 3.4. which will show an example of a PO with only one page and a PO with multiple pages.
3.4     Data Source:
Identify the data that has to be appeared in the forms. Table Name-Field Name
All the fields will be available on the SAP standard form MEDRUCK. Any additional fields that are not on the standard form will need to be added. The mapping for additional fields not in the standard form will be shown below in each section (Header Level, Item-Level, and Authoriztions) if required.
Please see below for the required fields in the form:
This Section will contain details on the Header, Line-Item, and Authorization sections of the form. A section for attachements will also be inlcuded at the end.
I. Header Information:
The following fields will be displayed for the header information.
-     Title: Purchase Order
-     Logo: The Sage Software logo will appear in the top left corner of the form.
-     PO Creation Date (MM/DD/YYYY)
-     Supplier Number
-     PO Number
-     Page Number
-     Bill to Name and Address
-     Supplier Name and Address
-     Ship to Name and Adress
-     Payment Terms: (not on standard form, see field mapping section below)
-     Shipping Terms: (not on standard form, see field mapping section below). The shipping terms are the same as the incoterms in SAP. There are two fields for the incoterms and both will be used for the shipping terms.
-     Header Text
Additional Notes for Header Fields:
PO creation date should be in format MM/DD/YYYY
Page Number should be in format Page 1 of 1, Page 2 of 3, etc format
The Bill To name and address will come from the company code that is assigned to the plant in the purchase order.
The Ship To name and address will come from the storage location in the first line-item on the purchase order if the SC Vendor box is not checked on the delivery address tab of the purchase order. If the SC Vendor box is checked on the delivery address tab, then the Ship To address will come from the delivery address tab on the purhcase order from the central address management system.
The Supplier name and address will come from the vendor master in the purchase order.
The central address management system will need to be queried when looking up the Bill To, Deliver, and Supplier addresses.
Header Text: The text to be inserted here will be pulled from the Header Text in the purchase order.
Example: Text is pulled from the Header text with the green checkmark.
If the PO Form requires additional pages, then the header information should be duplicated on the subsequent pages.
Additional Fields :
Field Mapping for additional header fields that are not on the Standard SAP PO (MEDRUCK) Form . These fields can also be viewed on the PO Forms in the Attachments section.
PO Form Additional Fields
Field Name     SAP Table/ Field Name
Payment Terms     MEPO1226-ZTERM
Shipping Terms (incoterms1)     MEPO1226-INCO1
Shipping Terms (incoterms 2)     MEPO1226-INCO2
II. Item Level Information
The following fields will be on the PO form for the item-level:
-     Item Number
-     Material
-     Material Description
-     Unit (Unit of Measure)
-     Quantity
-     Date Reqd (MM/DD/YYYY)
-     Unit Cost
-     Amount
Each field will have an allotted amount of characters, so that all the text can fit on the line-item. Using .5 inch margins with times new roman 10pt font; there are 105 possible characters in microsoft word for the line-item details to fit on the line. The fields are broken down as follows with their allotted characters to accommodate the 105 allowed spaces:
Characters:
Item Number: 1-3
Material: 6-18
Descriptoin: 6-36
Unit: 39-49
Quantity: 44-56
Date Required: 60-69
Unit Cost: 77-86 (Commas and Delimals will be included in the Price. Two total decimal Spaces)
Amount: 92-103 (Commas and Delimals will be included in the Price. Two total decimal Spaces)
The Numbering Ranges above can be viewed below line-item 040 in the PO Form Outline (Sinlge Page) document in the Attachments section.
Note: These number ranges are shown as an example of what the form should like. They do not have to match up identicle to the specifications listed above.
Additional Notes for Line-Item Fields:
- Material Description will be displayed directly below the Material on the next line.
- Item Text: The Item text will be displayed if there are any item texts from the Purchase order. The text will be displayed two lines below the Material description. So there will be one line without any text. Also, the next line-item on the PO form will be displayed two lines below the item-level text; so there will be only one line with no text between the line-item with text and the subsequent line-item. Line items 020 and 030 depict this in the PO Form Outline_v1 document in the attachments section. The Line Item text will come from the Material PO text (identified below with a green checkmark) from the line-item on the purchase order as shown below.
- The Date Required Format will be MM/DD/YYYY.
- For every item in the purchase order, the program should loop through each item and check to see if the returns item box is checked (MEPO1211-RETPO). If this box is flagged on the purchase order, then the purchase order form needs to be updated with a return indicator. This indicator can be viewed on line-item 030 of the attached word document PO Form Outline (Single Page) in the Attachments section.
- The line-item fields should have the following alignment:
Material: Left
Material Description: Left
Unit: Left
Qty.: Right
Date Required: Left
Unit Cost: Right
Amount: Right
- If the line-items do not fit on one page, then they should continue on to subsequent pages. The Header information should be copied to all the subsequent pages and the authorization section will be displayed on the last page as well as the total amount and currency. This example can be viewed in document PO Form Outline (Multiple Pages) in the Attachments section.
Dislclaimer:
A disclaimer will also be included in this section and after all the line-items. The disclaimer text is still pending. An example of a disclaimer is shown in the PO Form Outline (Single Page) after line-item 040. This document can be found in the Attachments section.
If a PO requires multple pages, the the disclaimer will be displayed on the last page after the last line-item.
III. Authorization Information
This section will contain the purchasing agent: The purchasing agent will be the person who created the purchase order. This section will also contain their telephone number and email address.
The first and last name of the person who created the purchase order should be displayed here. This can be looked up in the users profile. The user profile will also contain their email and telephone number.
The field names for can be viewed below or in the PO Form Outline (Single Page) document in the Attachments section.
PO Form Additional Fields
Field Name     SAP Table/ Field Name
First Name     ADDR3_DATA-NAME_FIRST
Last Name     ADDR3_DATA-NAME_LAST
Telephone Number     SZA5_D0700-TEL_NUMBER
Email     SZA5_D0700-SMTP_ADDR`
Attachments:
3.5     Special Requirements Processing:
Describe the processing required to support any special requirements (e.g. signatures, logos, OCR, bar coding etc.).
3.6     How to execute the form:
Describe how to trigger the form e.g. Standard SAP transaction code or custom transaction code etc. If standard SAP transaction code describe the menu path
The form needs to be able to be viewed and printed.
To View:
Transaction ME22N or ME23N; Then Click the Print Preview   icon to view the Form.
To Print:
1) Transaction ME22N.
2) Click Messages
3) Select Output NEU and medium 1 Print output
4) Click the Further data button as shown in the screen shot above
5) Select 4 Send immediately (when saving the application)
6) Click Back   then Click Save
7) Select LOCAL for logical Destination
8) Click Save again
4     Unit Test Plan Section
4.1     Functional Unit Test Plan:
Document the criteria to be used for validating programming accuracy and positive/ negative results
Step     Scenario     Expected Results
Number     Description of what is being tested in this step     Description of what is expected to happen in this step
1     Go to Transaction ME22N and Display PO Form by clicking the Print Preview Icon     Form should mirror the forms in the Attachments section.
2     Go to Transaction ME22N and Print PO Form     PO Form should print as showed in the Print Preview Screen and the forms the Attachments section.
3     Create PO that will force PO form to cross multiple pages and then click Print Preview     PO Form should have Header information on all pages and line-item shoulds continue on to the subsequent pages. Authorization, Total Amount, Currency, and Disclaimer will be on the last page. The page numbers should also be correct and in the right format. This should mirror the PO Form Outline (Multiple Pages) document in the Attachments section.
4     Go to Transaction ME22N and print PO as in step 3     PO Form shoul print as showed in the Print Preview Screen and the PO Form Outline (Multiple Pages) document in the Attachments section.
5     User Guide Requirements
A User Guide must be provided to assist the person responsible for running the program(s). The User Guide must be in cookbook-style (required elements with step by step instructions) and annotated screen prints. The User Guide will be required in the running of the object in the Production environment as well as the QA and Test environments.
5.1     User guide Requirements:
N/A
6     Appendix
6.1     Appendix:
N/A
Hope it will help ..
Regards,
Arjun.
<b>Reward the points if it hepls</b>

In BI Publisher RTF table layout issue for invoice printing

Hi,
I am working on check printing and invoice printing project on bi publisher and i am facing one issue. That is i have used section break on check priting so because of that if the the records are more than 20 then check will print on second page and on first page there would be void printed othervise it should print on first page only. In this case the preprinted stationary is not having invoice table form. we are using blank preprinted stationary to print this .
Now i have done with invoice and cheque layout but in output if the number of records are more than 20 then its going to second page but the problem is that invoice table break into two parts and and the end lineof table layout is not coming on first page .even on second page i am not getting start layout line to make complete table outline.
I want that full table layouton both the pages of the table. i have tried to to create table skeleton and used it as a watermark to print all the records on it but it is coming in to the middle of the page .so it not working.
Please anyone knows the solution on this problem please let me know or share your thoughts on this issue.
As i have tried many options but still stuck into this issue .Kindly help me.
Regards,
Prachi G.

Hmmm ... sounds like a regression bug.
I would contact support, provide, the version you are using, layout template, sample XML data, 2000 RTF output and 2003 RTF output and ask them to investigate.
Tim

Please update the functional specifications for Vendor Balance Report

Dear All,
Please update the functional specifications for Vendor Balance Report with
proper descriptions.
Please include
1. How your selection screen should look like..
2. Output format ( in an excel sheet)
3. Logic for every field in the output format (viz. .. how do link the
vendors from the selection screen to the BKPf and BSEG tables, how do you
find open and closed items in BSEG , etc.)
Please avoid statements like 'The total value of all the break-up should
tally with the balance as shown in FBL1N for a given vendor for the given
day.'
You need to give the logic for the FBL1N, in that case.
Regards
Rama Mohan

Hello again,
Regarding having them update the specs, one can dream. Dreams are free. LOL. Hopefully the memory makers will update their specs as more makers start supporting a large memory configuration.
The 4GB sticks I am using are http://shop.kingston.com/partsinfo.asp?ktcpartno=KTL-TP667/4G
I did not do an extended test of the sticks in my MBP. Their home is in the ThinkPad I have because it is running Windows Server 2008 with Hyper-V.
As you can see from the link above, these little suckers are pricey. But consider the price of 2GB SoDIMMs were $950 when they entered the market a couple of years ago. The price will drop.
I asked the Kingston rep that sent these to me if online sites like newegg.com would have them soon. She indicated no, but the corporate buying sites like CDW and Zone would. So check around. They just started shipped a couple of weeks ago so be patient.
If you have any other questions, please stop by http://blogs.technet.com/keithcombs/archive/2008/07/05/testing-my-apple-macbook- pro-with-8gb-of-ram.aspx and ask there. I'll see them much more quickly.
Cheers,
Keith Combs
Microsoft

Report for MSR Invoice Print is to meet Russian and ukairaine Local Legal

is there any standard report for Misslenious sales report(MSR)Invoice Print is to meet Russian and ukairaine Local Legal needs.

hdfhdfh

Functional specification invoices Printing

Similar Messages

Maybe you are looking for