Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 1 (10)
Prepared Document responsible/Approved
Date Version Relation
A
No. 2
SAP Technical Specification
Development object:
Title:
Contents
1 General Information - Required.............................................................2
2 Documentation History - Required........................................................4
3 Technical Design Approval - Required.................................................5
4 Execution Information - Required.........................................................6
5 SAP Information - Required...................................................................6
6 Pseudo code / Process Specification - Required.................................7
7 Interface/Conversion Information - Optional........................................8
8 Report Layout – Optional.......................................................................9
9 Error processing - Required..................................................................9
10 Unit Test Plan - Required.....................................................................9
11 Reference Documents........................................................................10
File name: Created by:
Printing Date: 22/05/2011 Page 1 of 10
Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 2 (10)
Prepared Document responsible/Approved
Date Version Relation
A
No. 2
Template Local / Global
Release
Company
1 General Information - Required
Frequency:
BAPI
IDOC Function
Doc. Created
Object Type
Basic type:
Extension:
Message type:
Msg Function:
Process Code:
Trigger:
General:
Sender Port:
Sender Partner
Partner Type
Partner Func
General:
Recipient Port
Partner No
Partner Type
Partner Func
Error Handling
File name: Created by:
Printing Date: 22/05/2011 Page 2 of 10
Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 3 (10)
Prepared Document responsible/Approved
Date Version Relation
A
No. 2
Author :
Requestor:
Purpose &
Description
Functional
Specification
File name: Created by:
Printing Date: 22/05/2011 Page 3 of 10
Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 4 (10)
Prepared Document responsible/Approved
Date Version Relation
A
No. 2
2 Documentation History - Required
Document History
Modified By Date Modified
Functional Date Functional Approval
Approval
Technical Approval Date Approved
Modification History
# Description of Change Document Section Modified Requested By
File name: Created by:
Printing Date: 22/05/2011 Page 4 of 10
Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 5 (10)
Prepared Document responsible/Approved
Date Version Relation
A
No. 2
3 Technical Design Approval - Required
Your signature indicates that you have carefully reviewed and approved each of the following sections contained in this
document. Additionally you agree the solution, when constructed according to this design, will meet the requirements of
your business process as outlined in the respective functional specification document.
Approval signatures Name/Signature Date
Functional
Representative
Approval
Technical Team
Representative
Approval
This documentation meets the standards set for technical design by the SAP Shared Service Center (SHC)
Approval signatures Name/Signature Date
SHC
Development
Lead
SAP Policies &
Procedures Specialist
File name: Created by:
Printing Date: 22/05/2011 Page 5 of 10
Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 6 (10)
Prepared Document responsible/Approved
Date Version Relation
A
No. 2
4 Execution Information - Required
Run trigger THROUGH TRANSACTION CODE ZRLL1.
Frequency Once every month i.e. on 6th - To be scheduled in background
Further Processing
Workflow
Requirements
Selection Screen 1000
Security
Requirements
Timing /
Dependencies
Controls/
Reconciliation
Method
Controls/
Reconciliation
Reporting
Restart/
Recovery
Procedures
5 SAP Information - Required
SAP Functionality ALV GRID DISPLAY
Application Module MM
(i.e. FI-GL)
SAP Transactions
SAP Dependencies
File name: Created by:
Printing Date: 22/05/2011 Page 6 of 10
Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 7 (10)
Prepared Document responsible/Approved
Date Version Relation
A
No. 2
6 Pseudo code / Process Specification - Required
DATA This section describes any CUSTOMIZED ABAP repository objects created or edited
DICTIONARY
OBJECTS BKPF BSEG
Logical database
Customized IT_BKPF IT_BSEG IT_RECORD
Tables
Idocs
BAPI Infor:
Object Type
Supertype
Object Name
Program
Name Z_RLL1_INVOICE
Description INVOICE LIST DISPLAY
Method
Authorization
objects
Transaction SE38 SE93
Codes
Output
Requirement
Function Module REUSE_ALV_GRID_DISPLAY
PSEUDOCODE
Edits;
Validations;
Special Logic
Program Logic:
File name: Created by:
Printing Date: 22/05/2011 Page 7 of 10
Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 8 (10)
Prepared Document responsible/Approved
Date Version Relation
A
No. 2
Conversion
SAP User Exit
Code
Enhancements
SOURCE CODE
MODIFICATION
7 Interface/Conversion Information - Optional
Interface ID
Interface Name
Inbound/Outboun
d Interface
Automated/Manua
l Interface
Replacement or
New Interface
Interface File
Information
Source/Target
Data format
Delivery method
Location and
name of interface
data file
Person responsible
for the data file
Interface data file
archiving
requirement
Person responsible
for the data file
Volumes
Approximate
number of
records:
Approximate
variance:
Availability of test
data
File name: Created by:
Printing Date: 22/05/2011 Page 8 of 10
Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 9 (10)
Prepared Document responsible/Approved
Date Version Relation
A
No. 2
8 Report Layout – Optional
Vendor Master data to MUSLEV
9 Error processing - Required
Error
There are a number of options for error handling, been discussed.
Processing
Error CALLING FUNCTION MODULE
Handling
choice 1
Error DEBUGGING THE PROGRAM (/H)
Handling
choice 2
Error
Handling
choice 3
Selected Choice
DEBUGGING THE PROGRAM (/H)
of error
handling
10 Unit Test Plan - Required
Unit Document below the plan for the testing of this solution based on the information in the preceding sections. This
Test description should draw together the work identified above and summarize the sequence of events required to
Plan complete execution. The signoff column of this document should contain both the technical and functional
representatives signatures/initials involved in the unit testing.
Objective Objective Test Test Condition Data Expected Results Sign Off
ID Description Condition Ref.
ID
Comments:
Objective ID
Revision Document below the plan for the revision control of this solution based on the information in the preceding
Control sections. This description should draw together the work identified above and summarize the sequence of
events required to complete execution. The signoff column of this document should contain both the technical
and functional representatives signatures/initials involved in the revision control.
Date Description of Section Requester of Functional Team Dev Lead Change Request
Revision Revised Revision Member Responsible Approval
Approval
File name: Created by:
Printing Date: 22/05/2011 Page 9 of 10
Security Page No.
FRICE TECHNICAL SPECIFICATION Internal 10
Prepared (10)
Document responsible/Approved
Date Version Relation
A
No. 2
11 Reference Documents
Reference Documents
SAP ABAP VOLUME 3
SAP BLACK BOOK
File name: Created by:
Printing Date: 22/05/2011 Page 10 of 10
