Functional specification documents..
HI guys,
I am new to SAP HCM..
i was wonderingg as to when is the need to write a Function spec document?
It would be great if you could give an example..
Also, what is the difference between Functioal Spec doc and functioal design document??
Thanks,
Functional-specification documents decribes business requirements and required changes that are to be applied in Project.
For Example If you company want to implement Second saturday as well fouth saturday as off days: For this you have to clearly mentioned the business requirement , what are the pre requisites required , is there ny development is required etc...
some time test cases also attached with this
Please refer these links , which will help you
http://www.premieresapconsultants.com/wisdom/2010/08/sap-functional-document/
http://www.sap-img.com/general/what-are-functional-specification-in-sap.htm
Similar Messages
-
Functional specification document
I have a requirement where i need to prepare functional specification document, could any one help me out with any fsd template on the same?
format required ( any example document will be an added advantage)Just google for "sap pi functional document template" and you'll find what you are looking for in the first page itself.
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0CDIQFjAC&url=http%3A%2F%2Fwww.piarch… -
Workflow Functional Specification Document
Hi All
I am working on a implementation project which includes Workflows. Right now I am in the process of writing the functional specification document for the Workflows. I am a functional consultant and never worked on workflows.
Can some one provide me what should be included in the functional document , how should the flow be written.
Is there any sample Workflow template anyone can share.
There are 4 places that requires workflows according to my understanding as described below in my requirement:
1. Workflow for corporate users when a notification is created or closed
2. Workflow email, forward a complaint to
Finance Manager
Quality Manager
Plant Managers
3. Workflow for forwarding to an approver, reassign task to someone else
4. Workflow to send remainder emails for open items longer than 30 days
Please provide your insights and neccesary documentation to start
Thanks,
SaiHI Prakash,
Thanks for the detailed response, it helped me a lot.
for approval to sales director, operations director and quality director an email has to be triggred simultaneously.We have predefined list depending on plant who can take corrective action and who can approve the corresponding task. Further users should have the option to select who should get the email.
For Approver Determination:
Case 1: In your scenario approver is not fixed.The approvers get selected based on plant. Try to get link between plant and all the approvers. The easy approch will be to maintain the approvers SAP ID in Z-Table against all the plant and developer will use RULE to fetch approvers from this Z-Table. The structure of Z-Table will be:
PLANT LEVEL OBJID USERID
For one plant 3 entry will be maitained here. LEVEL will help to identify the 3 types of approvers i.e. sales director, operations director and quality director. OBJID value will be US (if SAP ID will maintained in USERID), O (if Org. ID will maintained in USERID), S (if Position will maintained in USERID) etc. Benifit of this approch will be when ever you want to change any approver you have to change corresponding entry in this Z-Table no need to do changes in Workflow (As suggested by Ronen).
I used the same logic, creating a Z-Table for agents who has to approve the corrective action for taks completed. I was curious if there is a standard way to get this functionality in SAP. I am not sure about the responsibility rule that Mike was mentioning. Can you tell me which approach is a better design.
Case 2: Now I am confused since you said user can choose next level of approver. So please explain in which scenario Approver will come based on plant and in which scenario user will choose it manually. If user have to choose manually then a screen design is require. From approval screen based on user selection you need to pass the Approver in workflow.
Sorry for not putting things clealy. There are no levels for approval. Each of them are independent i.e. Sales director , Operations Manager and Quality director should get emails for approval after the Plant Manager, QA, Manager, Sales Coordinator take corrective action and the notification is closed only when all 3 of them approve the corrective action.
The user have to choose manually when the correspondng approver of that plant left the company, long vacation, took a new role etc...
Mail Notification: Extended mail notification functionaity is there. The person who will get work item in his/her SAP inbox for approval they will get mail notification in their external mail ID. All the approvers email id should be maintained along with their SAP ID in T-Code SU01. You Just need to provide mail contents in your FS, workflow developer will put same text in in mail body.
I was thinking about the SO23 distribution list for sending the emails to approvers. Also, how do the emails go to the corresonding approvers of that specific plant unless we explicity specify the email id's associated with that plant. Please clarify.
Thanks,
Sandeep -
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. -
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,
AbhishekHi 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 -
SD Functional Specifications Document
Hello Everybody,
Can somebody provide some real time requirements of SD in an implementation project?
and also explain about the legacy system (real time) eg: what are all the fields it has, how did you map them to SAP fields etc...
Point will be rewarded.
Thank you,
Venkat.Dear Venkat,
I believe that if you have no real time experience, please do not quote it wrongly. The following are basic reasons:
1. Any one providing Infomation will be able to provide only an overview.
2. The person taking an interview is ideally qualified and can judge confortably that the experience is realistic or not.
3. The more you show experience, the interview level will be on more detailed and complex level.
Hence, believe in yourself and face interviews honestly. The chances of selection will be more.
However, if such information are for knowledge enhancement, I suppose it is more helpful for knowledge of every one.
Regards,
Rajesh Banka -
FUNCTIONAL SPECIFICATION AND TECHNICAL SPECIFICATION
hi Experts,
how does a functional specification looks and a technical specification looks.
can i have these requirements with samples..
or any helpful link wher i can get in template form.
thanks i advanceFunctional Specification:
The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
Technical Specification
Technical Specification is the document prepared by the Technical consultants. These documents are prepared basing on the Functional Specification given by the Functional consultants. The Technical Specification contains the following;
GENERAL INFORMATION
DEVELOPMENT INFORMATION
BUSINESS REQUIREMENTS
DATA EXTRACTION
AVAILABLE CUSTOMISING TABLES
AVAILABLE TEXTS WITH THEIR CODING CONVENTIONS
Check the below links for useful content on Technical and Functional specs:
/thread/409073 [original link is broken]
http://www.epri.com/eprisoftware/processguide/funcspec.html
http://www.mojofat.com/tutorial/
http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci212169,00.html
http://www.devshed.com/c/a/Practices/Writing-A-Functional-Specification/
http://www.softwarereality.com/lifecycle/FunctionalSpecStandard.doc
http://www.webopedia.com/TERM/F/functional_specification.html
Reward Points if useful. -
SAP HR Functional Specification in PA Module
Hello everyone,
I want to get the overview of Functional Specification document in PA.
Need some Idea how it work..
I will appreciate if I could get the copy of Sample functional Specification in PA.
I do not need name of company or any crtical information, Just a Sample copy to see the process flow and spec compilation.
So please do send me some if you have any at "bindashr atgmaildotcom"
Thanks in advanceHello everyone !
I am still looking for the Sample.
Will highly appreciate if any of you could please help me with that.
Thank you very much in advance -
What is the significance of Functional Specification.
Please do mail me at [email protected]
Dear FARHAN FAROOQ,
The Functional Specification describes the features of the desired functinality.
It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
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.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details -
Functional Specification & RICEF
Dear Experts ,
Can anybody please provide some functional specification documents with respect to SAP PM.
Also please let me know what is basically the role of Functional consultants with respect to RICEF ?
Regards
Keerthan KumarKeerthan,
The document template for Functional specification format should be determined by the organization how they want it.
Also, Functional Specifications answers the Questions as:
1. What is the Type of requirement (from RICEF i.e., is it a Report or Enahncement or Form or Interface)
2. What is the exact requirement.
3. What are the tables and Fields involved.
4. What are the screens involved (if any).
5. What would be the selection screen (if report).
6. What would be the exact format.
7. What are the controls and authorization checks involved. etc.
Sharing hereby one sample document found on google as below but still it is how your organization wants to design it:
https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0CEcQFjAC&url=http%3A%2F%2Fbrainare…
Hope this helps.
Regards,
Chin2. -
Hi Friends,
if any body has the "Functional Specification Documents" Please send it to my mail ID [email protected]
Regards
RKNeo2001 wrote:
Now the issue is that we need to maintain a connection chain from BRS -to- SRS -to- IDD.
This connection/mapping we need for handling Change Requests and doing Impact Analysis.
We are maintaining an excel sheet for that named as RTM (Requirements Tracibility Matrix).
This PROCESS of maintaining RTM is so cumbersome. Its an overhead and consumes lots of time. Please any of u guys who is or was a part of Process, please give some suggestions or guidelines by which we can do some betterment in this workflow.We used an application called CORE. One of its main capabilities was requirements traceability. I don't remember the name of the company that supplies CORE. I am guessing that other companies provide applications with similar capabilities. -
What is the functional specification
hai
sap gurus please tell me the functional specification how can we write the functional specification
can anbody explain in details and give me one good example for functional specification?
thanks
regards
anwarFunctional Specification:
To speak at macro level that is at project manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhere organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functionality. It describes the product's features as seen by the stake holders, and contains the technical information and the data needed for the design and development.
The Functional Specification defines what the functionality will be of a particular area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step that is technical development process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional specs are prepared by functional consultants on any functionality for the purpose of getting the same functionality designed by the technical people as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis -
3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names -
8) Future Impact & Change Assessment
9) Functional Design (Module Wise)
10) Risk Assessment
11) Process Metrics and Many More-- Which has impact on Business and its work flow
Regards,
Rajesh Banka -
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 specificationHi 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> -
Inputs for reveiwing Functional specification to prepare TS document
Hello Gurus
Good day to you. Now i have a requirement for reviewing the functional specification. I have few FS documents and i want to review them and let my manager know whether those FS documents are having the required information to start up to write a TS document or not. if it is not having sufficient information or if i require more information or lack of information in FS to start up TS preparation, i need to inform my lead. This is my requirement.
Here i require your suggestions or inputs which i should take care while reviewing the existing Functional specification. Please provide your inputs as per your experience.
This is going to help me a lot.
Thanks in advance.
Regards
RajHi Raj,
While reviewing the FS below are the key points which you note:
1. FS contains explanation of the functionality.
Functionality which you are trying to convey to the technical team to build
2. Details of the mapping tables if any
Mapping tables from legacy - SAP or SAP - upstream if any with the table info and applicability
3. Validity of specific values or length -
Validation if specific dates/char/numbers for fields required in SAP.
4. Analysis of any additional dependency for the FS
Any open clarification, requirements which would be a dependency for the FS (Example Input file)
Do let me know if you need any further info.
Regards,
MKS -
Document on Functional Specifications in SAP-FI
Hi SAP Gurus,
I would like to know what is Functional Specification. Can anyone help me in providing me a document on Functional Specification (FI).
Immediate help would be very much appreciated
Best Regards
suryaHi
please refer
http://www.sceis.sc.gov/content/FI-MM_Implementation_Prep/Blueprint-Gap/1.5_support_Functional_Spec_IDT-1.pdf#search=%22Cost%20Statement%20CSKS%20-%20SAP%22
http://www.sap-img.com/general/what-are-functional-specification-in-sap.htm
http://whatis.techtarget.com/definition/0,,sid9_gci212169,00.html
http://erp.ittoolbox.com/groups/strategy-planning/erp-projectmanagement/samples-for-sap-functional-specification-1194336#
hope this helps
pushkaraj
Maybe you are looking for
-
Hp v235r flash drive not being detected on my computer
Hi, I am using hp v235r flash drive for more than 5 years. It's not being detected on my computer since two days. Can any one solve my problem, as there is lot of important data stored in it and hasn't been backed up recently.
-
Any help would be appreciated! It was an old email account and it wants me to confirm a verification, but I don't have that email anymore!
-
How do i resolve Error #2032 ?
Hi, I am using the following code to launch SWF file. When i launch the page, getting "Error #2032" from GUI. Could you please advise if any changes needs to be done in the following file? Do you think this is environmental issue? Please let us know
-
You can't open the application "Adobe InDesign CC 2014" because it is not responding.
For some reason InDesign has decided to stop responding. Acts like it wants to launch but then does nothing. When I try to launch it from the Finder rather than the Dock, I receive this message: You can't open the application "Adobe InDesign CC 2014"
-
DMS-Document Distribution Setup
Hello , I would appreciate if any one can give me some idea's on config part of Document Distribution in Document management system. I maintained recipeint list and in CVI8 i started document distribution which gave me back an internal order number l