Вы находитесь на странице: 1из 21

Report Advance Payments

ABAP Training
Display Outstanding Advance Payments

Document Status: Draft


Date: 03/14/2012
Version: v1.0

Revision History
Date
15/03/2012
20/03/2012

Version
1.0
1.0

Description
Creation
Modification

Author
Pravesh
Shumsheid

Report Technical Design - <Report Name>

Template instructions
The text within the body of the document is color-coded:

Text marked in blue needs to be deleted, as it contains instructions and guidance to the author only
Text marked in red is showing an example how to fill in the template and needs to be replaced by the
final content
Text marked in black (the rest of the document) needs to be kept as this provides the framework and
chapters of the template.
Delete this instruction section before finalising your document.
A final document will have no blue or red text

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 3 / 21

Report Technical Design - <Report Name>

TABLE OF CONTENTS
1.

2.
3.

4.

5.

6.

7.
8.

Technical Design .........................................................................................................................................6


1.1
Document Information ..........................................................................................................................6
1.2
Related Documents ..............................................................................................................................6
Sign-off Checklist ........................................................................................................................................7
Document History .......................................................................................................................................8
3.1
Revision History ....................................................................................................................................8
3.2
Quality Review ......................................................................................................................................8
3.3
Approval / Sign-off ................................................................................................................................8
Development Overview .............................................................................................................................10
4.1.
Requirements Summary .................................................................................................................... 10
4.2.
Assumptions ...................................................................................................................................... 10
4.3.
Dependencies / Constraints .............................................................................................................. 10
4.4.
Objects or Transactions Affected ...................................................................................................... 10
4.5.
Transaction Volume ........................................................................................................................... 10
4.6.
Standards .......................................................................................................................................... 10
4.7.
Security, Integrity, and Controls ........................................................................................................ 10
4.8.
Error Messages ................................................................................................................................. 10
4.9.
Estimation of Effort ............................................................................................................................ 10
Detailed Technical Specifications ...........................................................................................................10
5.1.
Technical Flow Diagram .................................................................................................................... 11
5.2.
Technical Flow Description ................................................................................................................ 11
5.3.
Selection Screen Details.................................................................................................................... 11
5.4.
Report Fields ..................................................................................................................................... 11
5.5.
Report Details .................................................................................................................................... 13
5.5.1.
Main Heading ............................................................................................................................. 13
5.5.2.
Sub-heading .............................................................................................................................. 14
5.5.3.
Totaling ...................................................................................................................................... 14
5.5.4.
Sort Criteria ................................................................................................................................ 14
5.5.5.
Page Breaks .............................................................................................................................. 14
5.5.6.
Interactive Capabilities ............................................................................................................... 14
5.5.7.
Report Paper Size ..................................................................................................................... 16
5.5.8.
Report Color Definition .............................................................................................................. 16
5.6.
Security and Authorization ................................................................................................................. 16
5.7.
Processing and Operational Considerations ..................................................................................... 16
5.7.1.
Dependencies ............................................................................................................................ 16
5.7.2.
Batch Requirements .................................................................................................................. 16
5.7.3.
Restart/Recovery Procedures.................................................................................................... 17
5.7.4.
Data Maintenance Requirements .............................................................................................. 17
5.7.5.
Re-use Details ........................................................................................................................... 17
5.7.6.
Multi-company, Multi-jurisdiction Considerations ...................................................................... 17
5.7.7.
Other .......................................................................................................................................... 17
Technical Requirements ...........................................................................................................................18
6.1.
Database Tables ................................................................................................................................ 18
6.2.
External Programs ............................................................................................................................. 18
6.3.
Development Class ............................................................................................................................ 18
6.4.
Message Class .................................................................................................................................. 18
6.5.
Program ID ........................................................................................................................................ 18
6.6.
Program Type .................................................................................................................................... 18
6.7.
Conventional Report .......................................................................................................................... 18
6.8.
Module ............................................................................................................................................... 18
6.9.
Transport Number(s) ......................................................................................................................... 18
Testing Requirements...............................................................................................................................19
7.1.
Key Unit/Assembly Test Conditions .................................................................................................. 19
Outstanding Issues ...................................................................................................................................20

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 4 / 21

Report Technical Design - <Report Name>

9.

Appendix ....................................................................................................................................................21
9.1.
Glossary of Terms ............................................................................................................................. 21
9.2.
Additional Supporting/Reference Documentation ............................................................................. 21

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 5 / 21

Report Technical Design - <Report Name>

1. Technical Design
Start Date

End Date

1.1 Document Information


Document Location
Application
Team
Business / Process Owner
Functional Designer
Developer
Status
Priority
Complexity

Link Design Folder Sharepoint


SAP STAIRS

Not Started / In Progress / In Review / Completed / Approved

High / Medium / Low


Simple / Medium / Complex / Very Complex

1.2 Related Documents


Blueprint Document
RICEFW Inventory
Conversion Approach
Functional Design

Link to Blueprint Document


To be defined
Link to Functional Design

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 6 / 21

Report Technical Design - <Report Name>

2. Sign-off Checklist
Use the following checklist to guide your completion of the Functional Design Document

Standards and Consistency


Has the correct template been used and all sections been completed as required?
Are the correct details (Business Owner for sign-off, status etc) displayed on the front page?
Have all the assumptions been documented properly so that there are no open issues in the document?
Has the document history been continuously updated?

Integration and Dependencies


Have all inputs and outputs been identified and confirmed?
Have all referenced documents been listed (other business process designs, sub process designs,
spreadsheets, information papers, etc.)?

Design
Has the report development technique been identified?
Has an example of existing RICEF object been included?
If the report is of type modification (custom development), has it been approved?
Have all areas of impact been identified?

Performance
Have the performance implications, metrics and targets been documented?
Has the performance and volume usage of the report development been considered?

Exceptions and Error Handling


Have the exceptions and likely errors been defined and listed?
Does the document describe what steps (if any) need to be taken after an exception has been raised?
Have all the applicable business scenarios been considered, along with the corresponding test conditions?

Usability From the user perspective


Has the report attempted to maximize the efficiency of the user (i.e. simple to use, intuitive, quick to use)?
Are any manual steps clearly defined and carefully designed?

Flexibility From a business perspective


Have all steps been clearly identified and documented so new functionality can be added in the future?

Additional information
Has security been considered (e.g. authority checking considered, target group of users who should be
given access to the report etc)?
Are the test conditions sufficiently detailed to enable a full test of all required functionality?

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 7 / 21

Report Technical Design - <Report Name>

3. Document History
3.1

Revision History

Author

Version Rev. date

Summary of Changes

Section

Pravesh Beeputh

1.0

Creation of a report to display outstanding


advanced payments

Page

3.2 Quality Review


The following have been nominated as quality reviewers for this Product:
Name

Title

Date of Issue

Versions

3.3 Approval / Sign-off


This document requires approval from the following individuals:
(Signed approval forms are filed in the quality section of the project files)
Name

Role

Date

Signature

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 8 / 21

Report Technical Design - <Report Name>

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 9 / 21

Report Technical Design - <Report Name>

4. Development Overview
4.1. Requirements Summary
To write a report to control the vendor payments and to avoid duplicate payments

4.2. Assumptions
N/A

4.3. Dependencies / Constraints


N/A

4.4. Objects or Transactions Affected


N/A

4.5. Transaction Volume


N/A

4.6. Standards
N/A

4.7. Security, Integrity, and Controls


N/A

4.8. Error Messages


N/A
Error Number

Error Message

Corrective Action

4.9. Estimation of Effort


Estimated Hours
Comments

5. Detailed Technical Specifications

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 10 / 21

Report Technical Design - <Report Name>

5.1. Technical Flow Diagram

Clients

Advanced Payments

Vendors

Monitoring

Send Report by Mail

5.2. Technical Flow Description


Clients make advanced payments to vendors. These advanced payments have to be monitored:
1. To control vendor payments
2. To prevent duplicate entries from occurring.
3. To send the PO details to a particular user as mail.

5.3. Selection Screen Details

Name
GJAHR
BUKRS
BNAME

Table Field/Check
Box/Radio Button
Table Field
Table Field
Table Field

Select - Option(S)
or Parameter(P)
(P)
(P)
(P)

Comments

Default
Value

Fiscal Year
Company Code
User Id

5.4. Report Fields


Level 1

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 11 / 21

Report Technical Design - <Report Name>

Level 2

Field#/
Label

SAP
Table

SAP Field
Name

Print
Cntl

Format/
Length

Field Calculations

MANDT
BUKRS

BSIK
BSIK

P
P

3
4

N/A
N/A

LIFNR
GJAHR

BSIK
BSIK

P
P

10
4

N/A
N/A

UMSKZ

BSIK

N/A

UMSKS

BSIK

N/A

DMBTR

BSIK

13

N/A

WRBTR

BSIK

Client
Company
Code
Vendor
Fiscal
Year
Special
G/L
Indicator
Special
G/L
Transactio
n Type
Local
Currency
Amount
Document
Currency
Amount

13

N/A

MANDT
LIFNR
EBELN

EKKO
EKKO
LFA1

Client
Vendor
Purchasin

P
P
P

3
10
35

N/A
N/A
N/A

Comments

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 12 / 21

Report Technical Design - <Report Name>

BUKRS

EKKO

BSTYP

EKKO

BSART

EKKO

AEDAT
STATU

EKKO
EKPO

MATNR

EKPO

MENGE

EKPO

BPRME

EKPO

EBELP

EKPO

g
Document
No
Company
Code
Purchasin
g
Document
Category
Purchasin
g
Document
Type
Date
RFQ
Status
Material
No
Purchase
Order Qty
Order
Price Unit
Item No

35

N/A

35

N/A

10

N/A

P
P

N/A
N/A

N/A

N/A

N/A

N/A

Field # = Number used in report layout to indicate placement (across and then down)
Print Control Codes
H =Header (Field that is in the header)
F =Footer (Field in the footer)
P =Page Continuation (Line Item data on which no page break should occur)
S =Start new page (Field on which a page break takes place. Typical fields for page breaks are 'plant,
product group, GL account)
B =Beginning of data group (Sometimes a sort on a field in a report is performed in order to group
information logically although we do not necessarily do a page break on that sort field.
E =End of data group (Often there is something that identifies the end of a logical grouping. Most
often this is a total or subtotal.)

5.5. Report Details


5.5.1. Main Heading

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 13 / 21

Report Technical Design - <Report Name>

5.5.2. Sub-heading
N/A

5.5.3. Totaling
Subtotals by Client and Company Code for local amount
Grand Total for local amount

5.5.4. Sort Criteria


Sort by Client & Company Code

5.5.5. Page Breaks


Page break by Company Code

5.5.6. Interactive Capabilities


Expand and Collapse selection on Company Code and Client

Details of the PO will be available when double clicking on it

User can either preview PO Details or send by mail

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 14 / 21

Report Technical Design - <Report Name>

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 15 / 21

Report Technical Design - <Report Name>

5.5.7. Report Paper Size


5.5.8. Report Color Definition
5.6. Security and Authorization
N/A

5.7. Processing and Operational Considerations


5.7.1. Dependencies
No dependencies

5.7.2. Batch Requirements


<<Include details required for batch processing (e.g., variant set-up, reconciliation requirements,
etc.).>>

Submission
Scheduling Considerations
Run Frequency
Start Date
Start Time
Estimated Volume Per Run
Parameters/File Dependencies
Job Dependencies
Constraints
Variant Required

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 16 / 21

Report Technical Design - <Report Name>

o
o
o

Field Text
Suggested Value
Description

5.7.3. Restart/Recovery Procedures


5.7.4. Data Maintenance Requirements
<<List any requirements for the maintenance of data,if required.>>

5.7.5. Re-use Details


<<Include any information regarding the re-use of code from other developments on other projects or
even within the same project, such as sample code or relevant documents/references.>>

5.7.6. Multi-company, Multi-jurisdiction Considerations


5.7.7. Other

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 17 / 21

Report Technical Design - <Report Name>

6. Technical Requirements
6.1. Database Tables
BSIK - Accounting: Secondary Index for Vendors
EKPO Order Details

6.2. External Programs


Smart Form : Z11_CASE_STUDY_3

6.3. Development Class


N/A

6.4. Message Class


N/A

6.5. Program ID
Z002_CASE_STUDY_3

6.6. Program Type


Executable Program

6.7. Conventional Report


6.8. Module
6.9. Transport Number(s)
CTS Request Number

CTS Task Number

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 18 / 21

Report Technical Design - <Report Name>

7. Testing Requirements
7.1. Key Unit/Assembly Test Conditions
Use the test scenario excel template for SAP

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 19 / 21

Report Technical Design - <Report Name>

8. Outstanding Issues
Issue
No

Description

Assigned To

Status

Impact

Resolution

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 20 / 21

Report Technical Design - <Report Name>

9. Appendix
9.1. Glossary of Terms
Term

Definition

9.2. Additional Supporting/Reference Documentation

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreement

Page 21 / 21