3010_t14_sap report technical design - cs3

8/2/2019 3010_T14_SAP Report Technical Design - CS3

1/21

Report Advance Payments

ABAP Training

Display Outstanding Advance Payments

Document Status: Draft

Date: 03/14/2012

Version: v1.0


2/21

Revision History

Date Version Description Author

15/03/2012 1.0 Creation Pravesh

20/03/2012 1.0 Modification Shumsheid


3/21

Report Technical Design -

2011 DCDM Consulting. All Rights Reserved. Proprietary Information. Not to be disclosed without prior written agreementPage 3 / 21

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 thefinal content

Text marked in black (the rest of the document) needs to be kept as this provides the framework andchapters of the template.

Delete this instruction section before finalising your document.

A final document will have no blue or red text


4/21



TABLE OF CONTENTS

1. Technical Design ......................................................................................................................................... 61.1 Document Information ..........................................................................................................................61.2 Related Documents ..............................................................................................................................6

2. Sign-off Checklist ........................................................................................................................................ 73. Document History ....................................................................................................................................... 8

3.1 Revision History ....................................................................................................................................83.2 Quality Review ......................................................................................................................................83.3 Approval / Sign-off ................................................................................................................................8

4. Development Overview ............................................................................................................................. 104.1. Requirements Summary .................................................................................................................... 104.2. Assumptions ...................................................................................................................................... 104.3. Dependencies / Constraints .............................................................................................................. 104.4. Objects or Transactions Affected ...................................................................................................... 104.5. Transaction Volume ........................................................................................................................... 104.6. Standards .......................................................................................................................................... 104.7. Security, Integrity, and Controls ........................................................................................................ 104.8. Error Messages ................................................................................................................................. 104.9. Estimation of Effort ............................................................................................................................ 10

5. Detailed Technical Specifications ........................................................................................................... 105.1. Technical Flow Diagram .................................................................................................................... 115.2. Technical Flow Description ................................................................................................................ 115.3. Selection Screen Details.................................................................................................................... 115.4. Report Fields ..................................................................................................................................... 115.5. Report Details .................................................................................................................................... 13

5.5.1. Main Heading ............................................................................................................................. 135.5.2. Sub-heading .............................................................................................................................. 145.5.3. Totaling ...................................................................................................................................... 145.5.4. Sort Criteria ................................................................................................................................ 145.5.5. Page Breaks .............................................................................................................................. 145.5.6. Interactive Capabilities ............................................................................................................... 145.5.7. Report Paper Size ..................................................................................................................... 165.5.8. Report Color Definition .............................................................................................................. 16

5.6. Security and Authorization ................................................................................................................. 165.7. Processing and Operational Considerations ..................................................................................... 16

5.7.1. Dependencies ............................................................................................................................ 165.7.2. Batch Requirements .................................................................................................................. 165.7.3. Restart/Recovery Procedures.................................................................................................... 175.7.4. Data Maintenance Requirements .............................................................................................. 175.7.5. Re-use Details ........................................................................................................................... 175.7.6. Multi-company, Multi-jurisdiction Considerations ...................................................................... 175.7.7. Other .......................................................................................................................................... 17

6. Technical Requirements ........................................................................................................................... 186.1. Database Tables ................................................................................................................................ 186.2. External Programs ............................................................................................................................. 186.3. Development Class ............................................................................................................................ 186.4. Message Class .................................................................................................................................. 186.5. Program ID ........................................................................................................................................ 186.6. Program Type .................................................................................................................................... 186.7. Conventional Report .......................................................................................................................... 186.8. Module ............................................................................................................................................... 186.9. Transport Number(s) ......................................................................................................................... 18

7. Testing Requirements............................................................................................................................... 197.1. Key Unit/Assembly Test Conditions .................................................................................................. 19

8. Outstanding Issues ................................................................................................................................... 20


5/21



9. Appendix .................................................................................................................................................... 219.1. Glossary of Terms ............................................................................................................................. 219.2. Additional Supporting/Reference Documentation ............................................................................. 21


6/21



1. Technical Design

Start Date End Date

1.1 Document Information

Document Location Link Design Folder SharepointApplication SAP STAIRSTeam

Business / Process Owner

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

Priority High / Medium / LowComplexity Simple / Medium / Complex / Very Complex

1.2 Related Documents

Blueprint Document Link to Blueprint DocumentRICEFW Inventory

Conversion Approach To be definedFunctional Design Link to Functional Design
http://sharepoint.eu.umicore.com/sites/isps/Stairs/Design/Forms/AllItems.aspxhttp://sharepoint.eu.umicore.com/sites/isps/Stairs/Design/Forms/AllItems.aspxhttp://sharepoint.eu.umicore.com/sites/isps/Stairs/Design/Forms/AllItems.aspx


7/21



2. Sign-off Checklist

Use the following checklist to guide your completion of the Functional Design Document

Standards and ConsistencyHas 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 DependenciesHave 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.)?

DesignHas 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?

PerformanceHave 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 perspectiveHas 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 perspectiveHave 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 begiven access to the report etc)?Are the test conditions sufficiently detailed to enable a full test of all required functionality?


8/21



3. Document History

3.1 Revision History

Author Version Rev. date Summary of Changes Section Page

Pravesh Beeputh 1.0 Creation of a report to display outstandingadvanced payments

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


9/21




10/21



4. Development Overview

4.1.Requirements SummaryTo write a report to control the vendor payments and to avoid duplicate payments

4.2.AssumptionsN/A

4.3.Dependencies / ConstraintsN/A

4.4.Objects or Transactions AffectedN/A

4.5.Transaction Volume

N/A

4.6.StandardsN/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 HoursComments

5. Detailed Technical Specifications


11/21



5.1.Technical Flow Diagram

Advanced Payments

5.2.Technical Flow Description

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

5.3.Selection Screen Details

Name Table Field/CheckBox/Radio Button

Select - Option(S)or Parameter(P)

Comments DefaultValue

GJAHR Table Field (P) Fiscal YearBUKRS Table Field (P) Company CodeBNAME Table Field (P) User Id

5.4.Report Fields

Level 1

Clients Vendors

Monitoring

Send Report by Mail


12/21



Level 2

Field#/Label

SAPTable

SAP FieldName

PrintCntl

Format/Length

Field Calculations Comments

MANDT BSIK Client P 3 N/ABUKRS BSIK Company

CodeP 4 N/A

LIFNR BSIK Vendor P 10 N/AGJAHR BSIK Fiscal

YearP 4 N/A

UMSKZ BSIK SpecialG/L

Indicator

P 1 N/A

UMSKS BSIK SpecialG/LTransaction Type

P 1 N/A

DMBTR BSIK LocalCurrencyAmount

P 13 N/A

WRBTR BSIK DocumentCurrencyAmount

P 13 N/A

MANDT EKKO Client P 3 N/ALIFNR EKKO Vendor P 10 N/AEBELN LFA1 Purchasin P 35 N/A


13/21



gDocumentNo

BUKRS EKKO CompanyCode

P 35 N/A

BSTYP EKKO PurchasingDocumentCategory

P 35 N/A

BSART EKKO PurchasingDocumentType

P 10 N/A

AEDAT EKKO Date P N/ASTATU EKPO RFQ

StatusP N/A

MATNR EKPO MaterialNo

P N/A

MENGE EKPO PurchaseOrder Qty

P N/A

BPRME EKPO OrderPrice Unit

P N/A

EBELP EKPO Item No P 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 groupinformation 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. Mostoften this is a total or subtotal.)

5.5.Report Details

5.5.1. Main Heading


14/21



5.5.2. Sub-heading

N/A

5.5.3. Totaling

Subtotals by Client and Company Code for local amountGrand 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 CapabilitiesExpand 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


15/21




16/21



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

Submission

Scheduling Considerations

Run Frequency

Start Date

Start Time

Estimated Volume Per Run

Parameters/File Dependencies

Job Dependencies Constraints

Variant Required


17/21



o Field Texto Suggested Valueo Description

5.7.3. Restart/Recovery Procedures

5.7.4. Data Maintenance Requirements

5.7.5. Re-use Details

5.7.6. Multi-company, Multi-jurisdiction Considerations

5.7.7. Other


18/21



6. Technical Requirements

6.1.Database TablesBSIK - Accounting: Secondary Index for VendorsEKPO Order Details

6.2.External Programs

Smart Form : Z11_CASE_STUDY_3

6.3.Development Class

N/A

6.4.Message ClassN/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


19/21



7. Testing Requirements

7.1.Key Unit/Assembly Test Conditions

Use the test scenario excel template for SAP


20/21



8. Outstanding Issues

IssueNo

Description Assigned To Status Impact Resolution


21/21



9. Appendix

9.1.Glossary of Terms

Term Definition

9.2.Additional Supporting/Reference Documentation