TS1

Technical Specification (TS)
325I_INBOUND_IAV_DISPOSITION
Document Number: 325I Super cedes: : 325I
Revision: 0.1 Title: Simple delivery report
Author: Upender Signature/Date: 17/12/2016
Approver: Upender Signature/Date: 19/12/2016
Reference FS ID:
PETS325/SourceForgeV1.0 Initial version
Add additional reviewers and approvers as necessary.
DOCUMENT NUMBER:
TECHNICAL SPECIFICATION
Page 2 of 30
TABLE OF CONTENTS
1 Introduction 5
2 Purpose 5
3 Scope 5
4 Definitions, Acronyms and Abbreviations 5
5 Assumptions 6
6 References 6
7 Constraints and Limitations 6
1.1 Critical Design Considerations 6

1.2 Backup and Recovery 6
8 Application Requirements 6
8.1 Detail Functional Design Specifications Overview 6
8.1.1 Business Functionality 6

8.1.2 Performance Considerations 7
9 Detailed Program Design Specifications 7
a. Describe Detailed ABAP Logic (Pseudo code, Flow charts and Supporting text) 9
10 Detailed Screen Design Specifications 13
10.1 (Enter Screen Name here) 13

10.2 Screen Description 13
10.3 Screen Invocation Method 13
10.4 Screen PF Key Definitions 13
10.5 Screen Layout 13
Pictorial view of screen. 13
10.6 Screen Field List 13
Define the fields used in the program 13
10.7 Screen Attributes 13
10.8 Screen Logic / Process Before Output 13
Define the SAP processing before the screen is output. 14
10.9 Screen Logic / Process After Input 14
Define the SAP processing after the screen is input. 14
11 Detailed Report Design Specifications 14
12 Detailed LSMW Design Specifications 17
13 Detailed BDC Design Specifications 18

DOCUMENT NUMBER:
Page 3 of 30
14 Detailed Database Design Specifications20
15 Detailed File Design Specifications 28
16 Detailed Transaction Design Specifications 28
17 Detailed Form Design Specifications 29
18 Detailed Search Help / Match Code Design Specifications 30
19 Detailed Interface Design Specifications 30
19.1 General Information 30

19.2 Web services Details 31
19.3 ALE/IDOC Configuration Information 31
19.4 FTP Information 32
20 User Exits / Field Exit / Menu Exit / BADIs 33
20.1 User Exit Information 33

20.2 Field Exit Information 33
20.3 Menu Exit Information 33
20.4 Screen Exit Information 33
20.5 Enhancement Frame Work Information 33
20.6 BADI Information34
21 Detailed Workflow Design Specifications34
21.1 Workflow General Information 34

21.2 Workflow Steps in Graphical Mode 35
21.3 Start Condition 35
21.4 Triggering Event Workflow level 35
21.5 Workflow Initiator35
21.5.1 Object Details 35
21.5.2 Workflow Task 35
21.5.3 Bindings 36
21.5.4 Verification 36
Document Statistics :
Document The following is current information about the document: (Maintain all
Identification relevant section)
DOCUMENT NUMBER:
Page 4 of 30
Object ID TS_325I
Title Simple del repport

Version V0.1
Creation Date
Handshake Meeting
Date
FS Author Func Cons
Functional Spec FS_325I
name
Technical Contact Upender
Name
Technical Contact
Phone
SAP Version ECC6.0
Development Type report
Document Status Draft
FS location in
Sorceforge
Document Revision History
Originator Date Revision # Summary of Change

Udaya Bhat 23-Oct-09 V0.1 Initial Version
1 Introduction
This TS contains..
The following sections of this TS has been filled up

Reports Design
Screen Design
LSMW Design
BDC Design
Database design
DOCUMENT NUMBER:
Page 5 of 30
File design
Transaction design
Smartform/Sapscript Design
Search help/Match code Design
Interface design ALE
Inbound IDOC
Outbound IDOC
Workflow Design
Webservices/BAPI/Function modules
User Exits / Field Exit / Menu Exit / BADIs / Enhancement frame work
2 Purpose
Business wnt a report to know the delivery details by sales order in time perod
3 Scope
4 Definitions, Acronyms and Abbreviations
Name/Abbreviation Definition/Explanation
5 Assumptions
6 References
N/A
7 Constraints and Limitations
1.1 Critical Design Considerations
1.1.1 .
1.2 Backup and Recovery

DOCUMENT NUMBER:
Page 6 of 30
8 Application Requirements
. The application sections include the following.
8.1 Detail Functional Design Specifications Overview
8.1.1 Business Functionality
8.1.2 Performance Considerations
The execution of this interface should not impact the overall performance of the PETS application
9 Detailed Program Design Specifications
9.1 Program Name

Zsam_del_report
9.2 Program Description

Sample delibvery report
9.3 Execution Method

Describe in detail, the method of program invocation (JCL specifics, online, etc.)
Real time
9.4 Program Type
Online __X___ Transaction _____Zdel_rep____________
Batch _____ Job Name __________________
Development Class package

Functional Application SD
9.5 Common Subroutines

A list of common, external routines.
9.6 Exceptions to Programming Standards

A list of exceptions to the programming standards and reasons why.
DOCUMENT NUMBER:
Page 7 of 30
Create a report zsam_del_report to get the delivery detasils for sales order and time
period
Below are the fields used in selection screen
Sales order number
Creted date
Validation sales order number, table name where to validate
Cteated a tcode for report and validate the t.code auth check in initialization vent
S_tcode
Fetch the data from vbak table based on selection screen value like sales order number
and date
For all entries used to fetch the data from item table VBAP by using VBAK internaltable
Process the item internal table and read the header data and prepare final internal table
for output
ALv output is designed to present the output
9.7 List of objects impacted

A list of objects impacted (e.g. Message Class, Function Module, Include etc).
OBJECT IMPACTED TYPE DESCRIPTION Transport Request

Zsam_del_report Program Sample del repo CRTRRW198723
ZDEL_rep TCODE Salpl xm CRTRRW198723
<For a list of Transport Requests generated for FRICE Object in this document, use Attachment
5 (present at the end of this doc under section 9.2.5) for detailed Transport Request Form>
9.8 Inputs / Outputs

A list of required inputs and outputs.
DOCUMENT NUMBER:
Page 8 of 30
The following fields need to be provided as selection criteria :
Selection Field Text Field Name Select-Option (S) Singl Obligat Default
/ Parameter (P) / e/Ra ory Value
Radio-Button / nge
Check Box
The following fields should be displayed in the output:
Field Description Field Name Format
9.9 Error Messages and Classes

A list of required error messages.
Message Class Message Type Message Id Message Text Long Text
9.10 Structures
Describe internal program structure. Several methods may be used for defining the layouts (table, includes, storage map, view,
etc.)
2 Describe Detailed ABAP Logic (Pseudo code, Flow charts and

Supporting text)
10 Detailed Screen Design Specifications
All new and modified screens for this design will be defined. Repeat this section for each
screen included in this design.
DOCUMENT NUMBER:
Page 9 of 30
10.1 (Enter Screen Name here)
N/A
10.2 Screen Description
N/A
10.3 Screen Invocation Method
N/A
10.4 Screen PF Key Definitions
N/A
10.5 Screen Layout
Pictorial view of screen.
N/A
10.6 Screen Field List
Define the fields used in the program
N/A
Program Variable Variable Screen Label Data Source or Description
Variable Type Length Destination
10.7 Screen Attributes
N/A
10.8 Screen Logic / Process Before Output
Define the SAP processing before the screen is output.
N/A
10.9 Screen Logic / Process After Input
Define the SAP processing after the screen is input.
N/A
DOCUMENT NUMBER:
Page 10 of 30
11 Detailed Report Design Specifications
All new and modified reports for this design will be defined. Repeat this section for each report
included in this design.
11.1 Report Name
11.2 Report Description
11.3 Report Invocation Method
11.4 Report Application
11.5 Report Type

Processing control, managerial, operational, etc.
11.6 Report Classification

Confidential, internal use, personal, etc.
11.7 Report Medium

Special forms, paper, electronic, etc.
11.8 Report Frequency

Daily, weekly, monthly, quarterly, annually, on demand, etc.
11.9 Report Request Method

Scheduled batch job, requested by user, submitted by user, etc.
11.10 Report Timing

Estimated start time, complete time, duration, etc.
11.11 Report Originator

DOCUMENT NUMBER:
Page 11 of 30
Originator Type (person, user class, organizational Originator ID / Name Location

unit, etc.)
11.12 Report Recipients
Recipient Type (person, user Recipient ID / Send to Number of Distribution

class, organizational unit, etc.) Name Location Copies Requirements
11.13 Report Processing Environment
Printer Requirements Printing Associated System Printer Constraints /

(impact, laser, high Application Software Component Location Comments
speed, etc.) Name ID / Name
Variant Name Parameter Name Parameter Value Parameter Description
11.14 Report Layout

Pictorial view of report.
11.15 Report Layout Description
Report Field Name Logical Data Base / Table Field Name Computation / Edit Rule
11.16 Report Sort Information
Sort By Report Field Name Sort By (ascending, descending)

DOCUMENT NUMBER:
Page 12 of 30
11.17 Report Control Breaks
Breaks on Report Field Name Sub Totals for Report Field Names
11.18 Report Page Breaks

Define when page breaks occur.
Breaks on Report Field Name Conditions
11.19 Report Summary Statistics
Summary on Report Field Name Summary Condition
11.20 Report Messages
Message Number Severity Description
11.21 Report Number of Pages / Lines / Copies

N/A
11.22 Report Printing Information

Print immediately, retention period, delete after print, cover sheets, etc.
N/A
12 Detailed LSMW Design Specifications
Repeat this section for each LSMW object included in this design.
12.1 (Enter LSMW Project / Subproject / Object Name here)

N/A
12.2 Object Attributes

N/A
DOCUMENT NUMBER:
Page 13 of 30
12.3 SAP LSMW Structures/Fields Mapping to Input File
(Repeat for each structure used)
SAP Structure Name
Source Field Name SAP Field Name Description Type Length
12.4 Translation Rules / Fixed Values / User Defined Routines
SAP Field Names Translation Rules/Fixed Values/User Defined Routines
12.5 Estimated Run Time

N/A
12.6 Files Used

Identify the input, intermediate & output files associated with this LSMW Conversion.
(Repeat for each file used)- N/A
File Name:
File Type: Input/Output/Intermediate
File Path:
Delimiter (if any):
13 Detailed BDC Design Specifications
Repeat this section for each BDC session included in this design.
13.1 (Enter BDC Session Name here)

N/A
DOCUMENT NUMBER:
Page 14 of 30
13.2 BDC Transaction

N/A
13.3 BDC Screens and Fields Used

N/A
13.4 BDC Number of Transactions Anticipated

N/A
13.5 Estimated Run Time

N/A
13.6 BDC Table Names

Identify the table and associated element attributes.
Table Name Client Dependent? (Y/N)
Table Element Create Reference Update Delete

DOCUMENT NUMBER:
Page 15 of 30
14 Detailed Database Design Specifications
All new and modified databases for this design will be defined. Repeat this section for each
database included in this design.
14.1 Custom Database Table Name
14.2 Table Description
14.3 Structure Name / Append Structure Name

ZPD_GOODSMVT_DATA
14.4 Structure Description

Goods Movement item details
14.5 Change Type
New __X___ Modified _____
Field Name Field Type Field Length Key Information Field Description
MATERIAL CHAR 18 Material #
CUSTOMER CHAR 10 Customer Number
QTY QUAN 13 Quantity
DOC_HDR_TXT CHAR 25 Document Header Text
ITEM_TXT CHAR 50 Line item text
RECIPIENT CHAR 12 Recipient
REASON_MVT NUMC 4 Reason for movement
14.6 Sizing
Monthly Data Volume Online Retention (in months)
Method for Data Purge (delete, archive, etc.) ABAP Name
Data Maintenance and Security ABAP Name

DOCUMENT NUMBER:
Page 16 of 30
Frequency of Accessing Access Media (online, Archive Retention Period (in Months)
Archived Data per Month tape, etc.)
14.7 Database Triggers
14.8 Lock Objects
Table Name Field Names
14.9 Other Database Information
Action: Add Modify Delete
Modules:
A A Asset management P PP Production Planning
M
C P Project System Q QM Quality Management
S
D IS Industry Solution S System Basis
F FI Financial Accounting T Test
H H Human Resources V SD Sales and Distribution
R
I P Plant Maintenance W WF Workflow
M
K C Controlling X Peut toucher plusieurs
O modules
M M Materials Management Z Module Usage
M
Name Table Structure

Description
Development Class: Other :
Development Time : Date to Production :

DOCUMENT NUMBER:
Page 17 of 30
Delivery class:
A Application table (Master and transaction data
C Customising table, maintenance only by
customising., not SAP import
L Table for storing temporary data, delivered empty
G Customising table, protected against SAP Update.,
only INS all.
E Control table, SAP and customer have separate key
areas
S System table, maintenance. only by SAP, change =
modification
W System table, contents transportable via separate
TR objects
? Other
Maintenance thru SM31: Yes No

Authorisation group &NC& Other:
Maintenance type One step Two step
Table Information
Foreign Key Reference
Action Cardinali
ty
D M A F. Name P. D. Table D. xx-yy Table D. Element
Key Element Element
Mandt Mandt T000 Mandt 1-N
Cardinality
XX C Entry in foreign key fields can exist
1 Entry in foreign key fields must exist
YY C Each record in check table has max. of one dependent record
CN Each record in check table has any no. of dependent records
N Each record in check table has at least one dependent record
1 Each record in check table has exactly one dependent record
DOCUMENT NUMBER:
Page 18 of 30
Index
Index Unique
Description
# F. Name # F. Name # F. Name # F. Name # F. Name
1 3 5 7 9
1
2 4 6 8 0
Data
Element
Data Description Elementary type Further Field Label
Element Characteristics
Domain <search help, <short medium
<specify domain Parameter id, long heading>
Name> Default
predefined type Component
<specify Data type & name>
length Decimal spaces>
others
Domain
Domain Description Data type Data type Output Value
Characteristics Range/value
table
<specify <specify output
data type length , conversion
number routine, sign ,Low
characters Case>
decimal
places>
14.1 Custom Database Table Name
14.3 Structure Name / Append Structure Name

ZPD_MSGS
DOCUMENT NUMBER:
Page 19 of 30
14.4 Structure Description

Return Messages
14.5 Change Type
New __X___ Modified _____
Msg_TYP CHAR 1 Message type
Message CHAR 25 Return Message
14.6 Sizing
Monthly Data Volume Online Retention (in months)
Method for Data Purge (delete, archive, etc.) ABAP Name
Data Maintenance and Security ABAP Name
Frequency of Accessing Access Media (online, Archive Retention Period (in Months)
Archived Data per Month tape, etc.)
14.7 Database Triggers
14.8 Lock Objects
Table Name Field Names
14.9 Other Database Information

DOCUMENT NUMBER:
Page 20 of 30
Action: Add Modify Delete
Modules:
A A Asset management P PP Production Planning
M
C P Project System Q QM Quality Management
S
D IS Industry Solution S System Basis
F FI Financial Accounting T Test
H H Human Resources V SD Sales and Distribution
R
I P Plant Maintenance W WF Workflow
M
K C Controlling X Peut toucher plusieurs
O modules
M M Materials Management Z Module Usage
M
Name Table Structure

Description
Development Class: Other :
Development Time : Date to Production :
Delivery class:
A Application table (Master and transaction data
C Customising table, maintenance only by
customising., not SAP import
L Table for storing temporary data, delivered empty
G Customising table, protected against SAP Update.,
only INS all.
E Control table, SAP and customer have separate key
areas
S System table, maintenance. only by SAP, change =
modification
W System table, contents transportable via separate
TR objects
? Other
Maintenance thru SM31: Yes No

Authorisation group &NC& Other:
Maintenance type One step Two step
DOCUMENT NUMBER:
Page 21 of 30
Table Information
Foreign Key Reference
Action Cardinali
ty
D M A F. Name P. D. Table D. xx-yy Table D. Element
Key Element Element
Mandt Mandt T000 Mandt 1-N
Cardinality
XX C Entry in foreign key fields can exist
1 Entry in foreign key fields must exist
YY C Each record in check table has max. of one dependent record
CN Each record in check table has any no. of dependent records
N Each record in check table has at least one dependent record
1 Each record in check table has exactly one dependent record
Index
Index Unique
Description
# F. Name # F. Name # F. Name # F. Name # F. Name
1 3 5 7 9
1
2 4 6 8 0
Data
Element
Data Description Elementary type Further Field Label
Element Characteristics
Domain <search help, <short medium
<specify domain Parameter id, long heading>
Name> Default
predefined type Component
<specify Data type & name>
length Decimal spaces>
others
DOCUMENT NUMBER:
Page 22 of 30
Domain
Domain Description Data type Data type Output Value
Characteristics Range/value
table
<specify <specify output
data type length , conversion
number routine, sign ,Low
characters Case>
decimal
places>
15 Detailed File Design Specifications
All new and modified files for this design will be defined. Repeat this section for each file
15.1 (Enter Filename Here)
15.2 File Description
15.3 File Change Type
New _____ Modified _____
Field Name Field Field Key Field Description

Type Lengt Information
h
DOCUMENT NUMBER:
Page 23 of 30
16 Detailed Transaction Design Specifications
All new and modified transactions for this design will be defined. Repeat this section for each
transaction included in this design.
16.1 (Enter Transaction Name here)
16.2 Transaction Type
16.3 Transaction Program
16.4 Transaction Description
16.5 Transaction Screen Flow
17 Detailed Form Design Specifications
All new and modified forms for this design will be defined. Repeat this section for each form
17.1 (Enter Form Name Here & Specify whether it is a Smart form or SAP Script or Adobe
Forms)
N/A
17.2 Form Description
Forms Information
Form Type New Change
JetForm Application Yes No
Pre-printed Form Yes No
Layout Set Name
Output Type
Output Destination (check all that apply) Hard Copy EDI FAX
Hard copy to a specific printer
Number of forms to print per run
DOCUMENT NUMBER:
Page 24 of 30
IMG Configuration, if any

Menu Path to Generate Form
Content for Form Output

Table Name Field Name Field Description Maximum Number of
characters to print
17.3 Form Comments
N/A
18 Detailed Search Help / Match Code Design Specifications
All new and modified search help / matchcode objects for this design will be defined. Repeat
this section for each search help / matchcode object included in this design.
18.1 (Enter Search Help / Match Code Object Name Here)
N/A
18.2 Search Help / Matchcode Description

N/A
18.3 Table Name

N/A

N/A
18.5 Change Type
New _____ Modified _____
DOCUMENT NUMBER:
Page 25 of 30
19 Detailed Interface Design Specifications

19.1 General Information
Interface Type: Batch ____ Real Time ____

Direction of Interface: Inbound _____ Outbound ______ Both ___
Function Group:
MDM Usage (Harmonized, Central Mgmt)
Meta Objects Structures:
Triggering Events:
Frequency of Run
Volume files/records
Logical File Names
Physical File Names
19.2 Web services Details
Service definition ZPD_IAV_DISPOSITON

Port type Namespace (TBD during coding phase)
Port type Name (TBD during coding phase)
SOAP Application (TBD during coding phase)
WSDL URL (TBD during coding phase)
J2EE server Access Information Application server IP details needs to be filled.
Function Module/Program Name ZPD_M_IAV_DISPOSITION
19.3 ALE/IDOC Configuration Information
Message Type WMMBXY

IDOC type WMMBID02
Partner Profile (TBD during coding phase)
Port (TBD during coding phase)
Process Code WMMB
Name of the Functional Module L_IDOC_INPUT_WMMBXY
RFC Destination (TBD during coding phase)
< If Custom IDoc Type is created or used, then populate the below information >
IDOC Information
IDOC Type
Description
Segment Field Name Data Element Parent Description

DOCUMENT NUMBER:
Page 26 of 30
19.3.1 SAP Configuration
Port Configuration:
Sending Port
Receiving Port
RFC Destination
Directory
Command File
Partner Profile Configuration:

Parameter Type
Partner Number
Partner Type
Partner Role
Process Code
Function Module
Application
Message Type
IDoc Control record:

Message Code
Message Type
Basic Type
Extension
Direction
Partner Type
19.4 FTP Information
Destination or Source Systems Name

TCP/IP Address(es)
Data Set of File Name
Record Length
FTP Method CW FTP
FTP Script Manual
Collab.
DOCUMENT NUMBER:
Page 27 of 30
20 User Exits / Field Exit / Menu Exit / BADIs
A list of User Exits / BADIs used by this program or object

20.1 User Exit Information
Name of the User Exit

Name of the Main Program
Functional Module Name
Project Name if any
20.2 Field Exit Information
Name of the Field

Name of the Main Program / Structure /
Table
Project Name if any
20.3 Menu Exit Information
Name of the Menu Exit

Name of the Main Program / Menu
Project Name if any
20.4 Screen Exit Information
Name of the Main Program / Function

module
Screen Number
Subscreen numbers
Subscreen exit program name
20.5 Enhancement Frame Work Information
Enhancement Implicit
Enhancement-point
Enhancement section
Explicit
Name:
DOCUMENT NUMBER:
Page 28 of 30
Enhancement To Class <specify class name>

Class method
<specify method name>
class parameters
<specify parameters>
Function module
<specify Function module name>
Function module parameter
<specify Parameters>
Source code
Program <specify Program name>

Others <specify Object type>
<specify name>
Purpose
20.6 BADI Information
Name of the BADI Definition

Name of the BADI implementation
Development Package
21 Detailed Workflow Design Specifications

21.1 Workflow General Information
Object Name Object Type Description Name of the users who

receive the workflow (if
applicable)
<Describe all the information for the types Object Type, Method, Event, Key Field, Workflow
Template, Standard Task, Step, Rule, Function Module>
21.2 Workflow Steps in Graphical Mode
21.3 Start Condition

DOCUMENT NUMBER:
Page 29 of 30
21.4 Triggering Event Workflow level
Mention the triggering Events in the workflow level
Business object name Event Name Event Description
21.5 Workflow Initiator
21.5.1 Object Details
List the business objects created for the workflow . If any standard objects have been used
please mention .
1. Key Fields
2. Attributes
3. Methods
4. Events
21.5.2 Workflow Task
1. Workflow Container Elements
2. Steps
Mention all step names and the tasks which are attached to each step. Also
mention the reason for each step
3. User Decision
4. Agent assignment
5. Task description
6. Task Container Elements
7. Triggering events
8. Terminating Events
DOCUMENT NUMBER:
Page 30 of 30
9. Deadline monitoring
10. Escalation
11. Mail contents if any
12. Wait for event
13. Activity step
21.5.3 Bindings
21.5.4 Verification
End of Document

TS1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TS1

Uploaded by

Copyright:

Available Formats

Technical Specification (TS)

Document Number: 325I Super cedes: : 325I

Revision: 0.1 Title: Simple delivery report

Author: Upender Signature/Date: 17/12/2016

Approver: Upender Signature/Date: 19/12/2016

4 Definitions, Acronyms and Abbreviations 5

7 Constraints and Limitations 6

1.1 Critical Design Considerations 6

8.1 Detail Functional Design Specifications Overview 6

8.1.1 Business Functionality 6

10.1 (Enter Screen Name here) 13

12 Detailed LSMW Design Specifications 17

13 Detailed BDC Design Specifications 18

14 Detailed Database Design Specifications20

15 Detailed File Design Specifications 28

16 Detailed Transaction Design Specifications 28

17 Detailed Form Design Specifications 29

18 Detailed Search Help / Match Code Design Specifications 30

19 Detailed Interface Design Specifications 30

19.1 General Information 30

20.1 User Exit Information 33

21.1 Workflow General Information 34

Title Simple del repport

Document Revision History

Originator Date Revision # Summary of Change

The following sections of this TS has been filled up

4 Definitions, Acronyms and Abbreviations

7 Constraints and Limitations

1.1 Critical Design Considerations

1.2 Backup and Recovery

. The application sections include the following.

8.1 Detail Functional Design Specifications Overview

8.1.1 Business Functionality

8.1.2 Performance Considerations

9 Detailed Program Design Specifications

9.1 Program Name

9.2 Program Description

9.3 Execution Method

9.4 Program Type

Online __X___ Transaction _____Zdel_rep____________

Batch _____ Job Name __________________

Development Class package

9.5 Common Subroutines

9.6 Exceptions to Programming Standards

9.7 List of objects impacted

OBJECT IMPACTED TYPE DESCRIPTION Transport Request

9.8 Inputs / Outputs

The following fields need to be provided as selection criteria :

The following fields should be displayed in the output:

Field Description Field Name Format

9.9 Error Messages and Classes

Message Class Message Type Message Id Message Text Long Text

2 Describe Detailed ABAP Logic (Pseudo code, Flow charts and

10 Detailed Screen Design Specifications

10.1 (Enter Screen Name here)

10.5 Screen Layout

Pictorial view of screen.

10.6 Screen Field List

Define the fields used in the program

10.7 Screen Attributes

10.8 Screen Logic / Process Before Output

Define the SAP processing before the screen is output.

10.9 Screen Logic / Process After Input

Define the SAP processing after the screen is input.

Online X_ Transaction _____Zdel_rep____________

Batch _ Job Name ______________

New X_ Modified _____