Functional/technical specification


Other [Enter additional information.] Reports



Download 456.17 Kb.
Page3/4
Date09.06.2018
Size456.17 Kb.
#54051
1   2   3   4




      1. Other

[Enter additional information.]


    1. Reports




      1. Requirements Overview




Report Nature

☐ Operational

☐ Managerial

☐ Strategic

☐ Regulatory

☐ Others (explain):

Preliminary Report Type

☐ Webl

☐ BEx Web

☐ Xcelsius/Dashboard

☐ Crystal Reports

☐ ABAP

☐ BOBJ

☐ Report Painter

☐ Unknown

☐ Other (explain):

Report Use

☐ Internal

☐ External

Frequency of Usage/Data Refresh

☐ Daily

☐ Weekly

☐ Monthly

☐ Quarterly

☐ Annually

☐ Other (explain):

Report Replacement

☐ New Report

☐ Report Replacement

Transaction Code

Program Name (SE 38)

Description


























































      1. As Is Screen Capture or Mockups




        1. Report #1

Report Name




Transaction Code




Program Name




Selection Screen




Report Output







        1. Report #2

Report Name




Transaction Code




Program Name




Selection Screen




Report Output







        1. Report #3

Report Name




Transaction Code




Program Name




Selection Screen




Report Output







      1. Data Fields/Report Layout (Excel Template)

[Attached Excel “Report Data Fields” specifies the following:

  • Fields required in the report

  • Field Details ( Type, Selection Screen, Default Values, Filters)]




Report

Field List/Field Specification File Path






















      1. Predecessor and/or Dependencies




        1. Predecessor

Description

RICEFW ID

Related Document(s)






















        1. Dependencies

Description

RICEFW ID

Related Document(s)






















      1. Special Requirements




History Data




Formatting




Printing




Data Confidentiality & Security




Broadcasting/ Distribution




Graphs/Charts







      1. User/User Groups




User Groups/Roles

Special Authorization Requirements
















      1. Source Systems




Source System







T-Codes










      1. Other

[Enter additional information.]


    1. Forms




Type of Development: (What kind of report development is this?)

☐ Modification of Standard SAP Report/Form

Name of Standard Report/Form:


☐ Custom Form

Have you looked at possible standard Reports/Forms? ☐ Yes ☐ No




      1. Layout Information




Form/Report Layout

Sample Layout



High Level Logic






Calculations and Formulas (Fill out any Calculations or Formulas for this report)

Seq. #

Calculate Field Description

Required Calculation and Source Fields

Field Format

1










2










3













    1. Interfaces




      1. Interface Summary




Interface Type (Inbound/Outbound)




Interfacing Systems




Frequency (Real time/Batch)




Batch Frequency

☐ Batch ☐ Online

Any Encryption/ Decryption Requirements

☐ Annually

☐ Quarterly

☐ Monthly

☐ Weekly

☐ Daily

☐ Real Time

☐ Ad-Hoc

☐ Other (specify):

Expected Volume







      1. Configuration requirements



      1. Data Mapping Template





      1. Control and Audit Requirements

[List all Control/Audit Processing requirements for the development of this object (this section must be filled out for interfaces and conversions).]


Control/Audit Processing Requirements





    1. Conversions




      1. Conversion Summary




Source System




Approximate Volume







      1. Legacy Data Extraction Process




Legacy Data Extraction Process

What is the process that the legacy team will use to extract data from the legacy systems (i.e. timing, automated, manual, tools that will be used, etc. )

[The extract file will need to be in a text format and will be for all valid assets to be converted. The data extraction file will be saved on the Share Drive in text format, unless specified otherwise. The target name will be the Object ID name (upper case)_Process appended with “.txt” (lower case) (Example: ZMMDC3003_Extract.txt).
**The extraction will need to be done on a periodic basis to allow for extraction during integration and cutover testing.
Note: Please contact the Legacy Team Developer for the following items:

  • Batch Program

  • Legacy File Name

  • Target Name of Text file]







      1. Risk Assessment




Data Quality Risk Assessment

This section will refer to a matrix that discusses the various risks each conversion possesses. This matrix will be contained in an excel spreadsheet outside of this document.









      1. Data Cleansing Assessment




Data Cleansing Assessment

What is the process that will be used in order to cleanse the data before being loaded into SAP.







      1. Data Validation Requirements




Data Validation Requirements

How will the team validate the integrity of the data once loaded into SAP.







      1. Manual Conversion Contingency




Is Manual Conversion Possible? If so please describe approach

Please include who will load the data, number of resources needed, time necessary to load, etc.







      1. Sequence of Conversion Activities (including dependencies)




Sequence of Conversion Activities

Please list step by step activities for performing the conversion from the extraction activity through SAP data validation. Please include all associated dependencies.

The following sequence will be followed for this conversion:










      1. Data Mapping Template





      1. Control and Audit Requirements

[List all Control/Audit Processing requirements for the development of this object (this section must be filled out for interfaces and conversions).]


Control/Audit Processing Requirements






  1. TECHNICAL SPECIFICATION




    1. General Object Overview

[Enter information about type of object, overall design]


    1. Report / Interface/ Dialog Program Information




Program Information

Type of Program

(Report, Interface, Dialog Program)



Transaction code




Transaction Description




Program Name




Screen Number




What SAP transaction(s) do this involve?




Menu path for transaction(s)




Provide Selection - options & Parameters (if applicable)




Selection Option(s) Description

Field Name

Default (Mandatory, Value, etc.)








































      1. Screen validations/ Screen flow logic



      1. Output layout



    1. Class Information




Class Details (Interface Framework)

Class Name




Super Class Name




Global Attributes

Attribute Name

Type/Visibility

Default Value




























Methods

Method Name

Description

Method Parameters (Name/Type/Visibility)










Flow Logic:










Flow Logic:










Flow Logic

Events

Event Name

Description

Event Parameters

Event Handler Method Name
































































    1. Process Flow




Process Flow







    1. Program Structure




Program Structure





    1. Enhancements/User Exits




Object Definition

Object Type:

☐ SAP User Exit

☐ Function Exits

☐ Field Exit

☐ Menu Exit

☐ Screen Exit

☐ BADI

☐ Other:




Enhancements (This section to be deleted if object does not belong to this classification)

Enhancement Name:




Name and type of SAP Exits/ Objects that need to be enhanced:




Describe Enhancement:







Business Object Enhancement

Business Object:




Name:

Program:




Events Created:




Methods Created:







    1. Data Conversion




Object Definition

Conversion Method:

☐ LSMW

☐ ABAP Program

☐ Test Tool (eCATT, etc.)

☐ Other (specify):




Conversion Approach

Object Details

[Custom program will be outlined in section 2.1. For all other objects describe details of conversion methodology here.]

Data Mapping/Translation using the data mapping template outline in Section 1.7.8




Error Correction Mechanism




Audit Reporting




Error Reconciliation Process, if any







    1. Forms




      1. Type of Form




Form Type (SAP Script, Smart Form, or PDF

Form Name







Form Attributes



Page Properties



Page Layout (Windows and Logic)


Window Name:

Name of Element

Format Options

Logic













Window Name:

Name of Element

Format Options

Logic













Window Name:

Name of Element

Format Options

Logic












*If any print program is developed document that in section 2.2


    1. Custom Development

[Functional details of custom transaction can be incorporated here. Number of screens required and flow diagram can be included, provide the selection screen shot along with the table name and field name and screen shot for the required output.
Only to be filled when creating a z-Table for your Enhancement. This section should detail the attributes of any custom table used, and the properties of its fields.
Note: Existing SAP Data Elements and/or Domains should be used whenever possible when creating custom table fields, in order to avoid unnecessary typos.]


Table Name




Short Text




Size Category




Table Maintenance Allowed




Data Class




Buffering




Table Maintenance Generation




Authorization Group




Field Name

Data Element

Domain

Type

Length

Check Table Field

Key Field

Foreign Key

Description


















































































Comments





Download 456.17 Kb.

Share with your friends:
1   2   3   4



The database is protected by copyright ©ininet.org 2024
send message
    Main page
Guide
Instructions
Report
Request
Review