Project Development Specification

Title: Number:

Table of Contents
1 JUSTIFICATION.................................................................................................................................. 3
1.1 REQUIREMENT SUMMARY AND OVERVIEW OF CONCEPTUAL DESIGN...............................................3
1.2 JUSTIFICATION.............................................................................................................................. 3
1.3 DEVELOPMENT ESTIMATES............................................................................................................ 3
2 FUNCTIONAL SPECIFICATION........................................................................................................ 3
2.1 DETAILED REQUIREMENTS............................................................................................................. 3
2.1.1 Functionality........................................................................................................................... 3
2.1.2 Assumptions.......................................................................................................................... 3
2.1.3 Constraints............................................................................................................................. 3
2.1.4 Performance Criteria.............................................................................................................. 3
2.1.5 Applications Affected.............................................................................................................. 3
2.2 REQUIRED DATA........................................................................................................................... 3
2.2.1 Input Data.............................................................................................................................. 3
2.2.2 Output Data........................................................................................................................... 3
3 TECHNICAL SPECIFICATIONS......................................................................................................... 3
3.1 DEVELOPMENT SPECIFICATION FOR FORMS AND REPORTS.............................................................3
3.1.1 General.................................................................................................................................. 3
3.1.2 Output Layout........................................................................................................................ 3
3.2 DEVELOPMENT SPECIFICATION FOR CONVERSIONS / INTERFACES / INFO CUBES / ENHANCEMENTS...3
3.2.1 General.................................................................................................................................. 3
3.2.2 Data Mapping........................................................................................................................ 3
3.2.3 Data Model............................................................................................................................ 3
3.2.4 Legacy File Details................................................................................................................. 3
3.2.5 Legacy File Layout................................................................................................................. 3
3.2.6 Load and Control Procedures................................................................................................ 3
3.2.7 Dependencies........................................................................................................................ 3
4 ADDITIONAL INFORMATION............................................................................................................ 3
4.1 TEST PLAN................................................................................................................................... 3
4.1.1 Related Business Scenario and Business Transactions........................................................3
4.1.2 Test Data................................................................................................................................ 3
4.2 BACKUP / RECOVERY.................................................................................................................... 3
4.3 SECURITY PROFILE & AUTHORIZATION........................................................................................... 3
4.4 RELATED/REFERENCED DOCUMENTS...........................................ERROR! BOOKMARK NOT DEFINED.
4.5 Attachments................................................................................................................................ 3

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

Document Control

Requirements Approvals
Name Role Signature Date

Specification Approvals
Name Role Signature Date

Change Log

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

1 Justification
BACKGROUND INFORMATION

1.1 Requirement Summary and Overview of Conceptual Design

Service Purchase Requisition contains Number of Service Activities against which Sub cost Elements need
to be maintained. Standard Schema allows Sub activity Element order units to be maintained at same units
corresponding to Activity.

Business Requirement is Sub Activity elements need to be maintained at various Units, which is not
Possible with Standard Functionality.

For This Separate Custom developed Pricing for the Service Activity need to be developed where in against
a particular Service Activity Number, Several Sub Activities with different Units will be maintained and will be
out putted.

1.2 Justification
Standard Schema doesn’t allow to maintain different units for Sub Activity, which is referring to the main
Activity and Business Requirement is to Record and Maintain the Sub Activity Costs.

1.3 Development Estimates

Task Preliminary Estimate Reviewed Estimate
IT Estimator IT Days Reviewer
Days
Functional
Specifications
Tech. Spec
Coding
Unit Testing
Repair Post
Integration Test
Total:

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

2 Functional Specification
(Completed by HP Functional Consultants)

2.1 Detailed Requirements

2.1.1 Functionality

Enhancement in Purchase Requisition Screen needs to be done at Item Level.

Requirement 1:

User will select the Service activity number and Enters the Sub Activity Elements information in
the enhancement Screen.

1. The Total value of the Service Item which includes all Cost Elements
need to be captured as gross Value and will be updated to Gross Price at the Activity Level.

2. The Cumulative Value of all the Service Activity Gross Prices to be Captured and flown to Valuation Tab.

3. Sub Activity Elements and other Information’s are captured in Input Data.

The Input for these Fileds will be inactive for other than Service PR Document Type.

Requirement 2:

Additional Custom fields required in Screen are

1. Cost Center and Installed Quantity fields required, where user enters the Values and saves the PR which
are being used for Screening Sheet Purpose.

2. Activity Number, Description for Checking the Validation of Annual Job list Requirement for the given Fiscal
Year.

3. Last PO number is being used for Service Vendor Rotation.

4. Material and description being used for Reconditioning job Process.

2.1.2 Assumptions

Sub Activity Elements need to be visible in change, display and release Levels.

2.1.3 Constraints

This Sub activities data capturing will be active only for Service PR document Type.

2.1.4 Performance Criteria

Nil

2.1.5 Applications Affected

SAP System Impact/Change Description

Message

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

SAP System Impact/Change Description

Queue

2.2 Required Data

2.2.1 Input Data

User enters the Activity Number in Service PR and then enters the Sub Activity elements in the customer Tab.

The Sub activity elements to be included are

1. Labour cost
2. Equipment Cost
3. Material Cost
4. Tax & Duties
5. Profit %
6. Others
7. Miscellanoeus Costs

Processing Logic:

1. System should allow maintaining the Sub Activity Information against Main Activity.

2. Sub Activity Information will be maintained in different units.

3. Profit % will be calculated excluding Taxes and duties.

4. Total Cost will be captured in to Gross Value Field and need to be populated to Activity Level Gross Price.

5. Cumulative Gross Price of all Activities multiplied with quantity available for each Activity pertaining to line Item
to displayed in the Valuation Tab

From System Structure or Table Structure or Table Name

Name ID

Field ID Field Name Forma Table Value / Select-Option Mandatory / Default

t Checkbox / or Parameter Optional Value
Radio Button

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

From System Structure or Table Structure or Table Name

Name ID

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

2.2.2 Output Data

To System Structure or Structure or Table Location Expected

Name Table Name Volume

Field Name Field Description Format Values

1. Against each Activity, Sub Activity information should be maintained.

2. Total Gross Value of the Sub Activity Need to be updated to Gross Price.

3. Cumulative Gross Price of all Activities multiplied with quantity available for each Activity pertaining to line Item
to displayed in the Valuation Tab .

3 Technical Specifications
(Completed by the Technical Team)

3.1 Development Specification for Forms and Reports

Complete this section for form or report development (or if an interface / conversion/enhancement/user exit or transaction
will also produce a report).

3.1.1 General
Describe the required functionality. Specify the following information wherever applicable.

SAP Menu Path:

Selection Criteria

Security

Drill Down Requirements

Similar Report/Form

Exceptions / Filters

Output Type:

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

Mode of Execution:

Special Printing/Media Requirements:

Sort Criteria:

Logo:

Bar Codes:

Distribution/Volume:

Workbook Assignment

Frequency

Dependencies

Existing Development Object System Object Name

3.1.2 Output Layout

Provide detailed information on how the report should look. Include field layout, spacing, header/footer details. Indicate
whether times should indicate local or system time. Specify paper format and paper size if not indicated in media
requirements.

Provide a ‘mock’ layout for the report on then next page showing all report columns and samples of the rows, report
headings, totals etc

3.2 Development Specification for Conversions / Interfaces / Info Cubes / Enhancements

3.2.1 General

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

Inbound/Outbound:

Frequency:

Volume:

Legacy Data Source:

Legacy Contact:

Method of Execution:

Data Cleansing Process:

Reconciliation Process:

Error Handling Method:

Post Execution Notification

Details:

Transaction Code

Menu Path

User Exit Name

Required Screens

Existing Development Object System Object Name

3.2.2 Data Mapping

Conversion:

Interfaces/Enhancements
Custom design, refer to design description above and references RDD for details.
9

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

3.2.3 Data Model

Custom design -. Refer to design description above and referenced RDD for details.

3.2.4 Legacy File Details

File Location and Name:

Logical File Name:

Variants:

Legacy File Description:

Sort Requirements:

3.2.5 Legacy File Layout

3.2.6 Load and Control Procedures

3.2.6.1 Data Load Procedures

3.2.6.2 Info Cube / Package Group Definitions

3.2.7 Dependencies

4 Additional Information
4.1 Test Plan

4.1.1 Related Business Scenario and Business Transactions

Identify the business scenario and business transactions this development will be tested with.

Business Scenario/Business Transaction

4.1.2 Test Data

Identify the test data requirement

10

Unsigned printed copies are for reference purposes only

 Project Development Specification

Title: Number:

System ID Field Name Field Value

4.2 Backup / Recovery

This section should define the general recovery strategy for this design (Only required for interfaces & conversions).

4.3 Security Profile & Authorization

4.4 Attachments
Document Name Version Brief Description

11

Unsigned printed copies are for reference purposes only