SAP Script Customer Open Items

SAP Implementation at PIL
SAP Script Functional Specification
Note: As this is a case study that simulates a real life development object, some fields will be marked as
TBD and highlighted in Blue. These fields should be having real values, in customer development
specifications
Functional Specification - Forms

Customer Statement
Document Reference:
Version:
Document Status:
TBD
v1.0
Signed off
Author:
Bharathithasan Pandian
Last Revision Date:

Date Created:
Date Printed:
30-Nov-06
30-Nov-06
30-Nov-06
SAP Script Customer open items
30-Nov-06
<Page 1 of 14>
Document Control
Business Area
Finance
GAP ID
TBD
FS Definition Form ID
TBD
SAP R/3 Version
ECC 5.0
Location / Site
TBD
Approval and Distribution

Approved by
Process Team
Lead
Development
Team Lead
Name
TBD
Role
TBD
Signature
TBD
Date
TBD
TBD
TBD
TBD
TBD
Document History
Version
1.0
1.1
1.2
1.3
Reason for change

Initial Version
Date
30-Nov-2006
30-Nov-06
<Page 2 of 14 >
Table of Contents
1. GENERAL INFORMATION..............................................................................................................4
2. BUSINESS NEEDS & REQUIREMENTS..........................................................................................5
3. ISSUES........................................................................................................................................6
4. SAP SCRIPT/FORMS....................................................................................................................7
4.1 CURRENT FUNCTIONALITY..........................................................................................................7
4.2 PRINTING EXISTING SOLUTION....................................................................................................7
4.3 DESIRED FUNCTIONALITY...........................................................................................................7
4.4 CUSTOMIZING REQUIREMENTS....................................................................................................7
5. FORM LAYOUT.............................................................................................................................8
6. TECHNICAL DETAILS.....................................................................................................................9
LAYOUT WINDOWS......................................................................................................................9
FIELD MAPPING........................................................................................................................10
7. STANDARDS TEXTS/TEXT MODULES...........................................................................................12
8.TRANSLATION.............................................................................................................................12
9. LAYOUT DETAIL..........................................................................................................................12
10. CUSTOM TABLES/STRUCTURE IN SAP......................................................................................13
11. ASSUMPTIONS..........................................................................................................................14
12. ERROR HANDLING....................................................................................................................14
13. LANGUAGE OF TEXTS...............................................................................................................14
14. TESTING SCENARIOS................................................................................................................14
30-Nov-06
<Page 3 of 14 >
1. General Information
AREA (SAP SYSTEM COMPONENTS):
Short description:
FI
REQUESTED BY:
FORMTEXT TBD
Tel no:
AUTHOR:
Bharathithasan Pandian
Tel no:
Program Transaction code:

Task ID/Demand Number:
Project Name:
Complexity:
YFICUSTSTAT
FORMTEXT TBD
FORMTEXT SAP Implementation at PIL
High/mandatory
Medium/recommended
Low/optional
High
Medium
Volume of data:
Medium
Priority:
Mode:
Frequency:
Technical information:
1. Layout created using:
General information:
1. Results if no conversions are
created:
DEVELOPMENT WORK
(IN MAN-DAYS):
Is there an alternative in the
standard system?
Description of alternative:
DURATION OF
Reasons why alternative is not

acceptable:
Date:
30-Nov-2006
Customer Statement
FORMTEXT
TBD
FORMTEXT
TBD
Low
DATE AVAILABLE FROM: FORMTEXT TBD

Online
Background
Daily
Weekly
Monthly
Biweekly
Others (Specify) :
Sapcript
Smartform
Subroutine pool
Text Elements
Standard Texts
Text Id
Print Program
Legal requirements not fulfilled
Lack of essential business information
Lack of functions compared to legacy system
Others (Specify):
5 days (Coding+Testing)
Yes
No
Correspondence request in SAP

Performance problems
Complexity
Others (Specify) : Correspondence can be request for one
customer only at a time and a different layout is needed
30-Nov-06
<Page 4 of 14 >
2. Business Needs & Requirements

Power India Limited started its operation in the year 1965. From its humble beginning in a small
town of Maharashtra called Ranjangaon PIL has achieved several milestones and today it is one
of the largest manufactures of storage batteries in India. Currently the company is having seven
production facilities in India namely Ranjangaon, Pune, Nashik, Chennai, Hosur, Gurgaon and
Durgapur respectively.
Power India Limited, the flagship company of the Oscar group is the market leader in the
storage battery industry. It manufactures wide range of batteries from 2 Ah capacities to 10500
Ah to cover the broadest spectrum of applications.
The SAP Implementation at Power India Limited (PIL) will achieve the following:
1. Standardize and streamline the business process
2. Establishing an Integrated information repository
3. Improvement in the area of Planning
4. Complete visibility of stock
PIL has a huge customer base worldwide. As a part of their business strategy PIL sends all its
customers a monthly statement of all its transactions with them. The finance department at PIL
has this huge responsibility of churning out all the financial transaction the company has done
with its customers for a give period and then send the details to its customer is a particular
format. As a part of the implementation the finance department wants this process to be
automated wherein the user selects a particular set of customer and a period and it would like
all the financial transactions for all those customers in that period will be printed customer wise.
SAP has a solution in the form of correspondence requests (which is the standard procedure for
any communication requirements with customer) but the issue with this standard solution is that
the user has to request for the correspondence of each customer separately (One by one) and
the existing standard layout varies greatly from the requirement of PIL, hence a custom program
has to be developed to extract all the financial transactions of a given set of customer (multiple
customers) for a given period and print them in a statement format per customer.
30-Nov-06
<Page 5 of 14 >
3. Issues
None
Issue
#
Issue
owner
Date
Raised
Issue Description
30-Nov-06
Issue Resolution
Resolved
By & Date
<Page 6 of 14 >
4. SAP Script/Forms
4.1
Current Functionality
Output type
Program Name
Layout Form Name
IMG path to access output type
and layout set assignment
Type of solution (Standard R/3,
custom ABAP)
4.2
SAPScript Form
RFKORD10
F140_CUS_STAT_01
SAP Standard Transaction FB12
Standard R3
Printing Existing Solution
Menu Path for transaction:

Values to be used and output
type:
Actions to be taken:
4.3
Desired Functionality
Output type(s):
Form Types:
Transmission medium:
Legal requirements:
Type of printer:
Paper Size:
Orientation: Portrait/Landscape:
Special stationary to be used:
4.4
SAPScript Form
Customer Statement
Printer
TBD
A4
Landscape
No
Customizing requirements
The functional consultant will customize the following output types:

Output type
Program Name
Layout Form Names
Development system
30-Nov-06
<Page 7 of 14 >
5. Form Layout
Refer to the following for an output samples for Window mapping, Label Description and Field
mapping.
Layout.xls
Logic for the driver program.

Selection screen details
Name
Company
code
Customer
Posting From
Date
Posting To
Date
Table-Field /
Check Box /
Radio Button
with group
Table Field
Parameter
(P) / Selectoption (S)
P
Comments (Range,
Single/Multiple
selection, Patterns,
Mandatory etc.)
Mandatory
Table Field
Table Field
Single/Multiple
Selection/Mandatory
Mandatory
Table Field
Mandatory
Default Value
Data Selection logic.

Select all the document numbers (BELNR), Document Date in Document (BLDAT), Document
Type (BLART), Currency Key (WAERS) into an internal table IT_BKPF from the table BKPF
where company code (BUKRS) = Company code entered in the selection screen and the
Posting Date in the Document (BUDAT) between Posting From date and Posting to date
entered in the selection screen.
Select Customer (KUNNR), Accounting Document Number (BELNR), Amount in document
currency (WRBTR) into an internal table IT_BSEG from BSEG for all entries in IT_BKPF where
BELNR = IT_BKPF-BELNR, Account type (KOART) = D.
Get all the distinct customers in IT_BSEG and get their names from KNA1, where
KNA1-KUNNR = BSEG-KUNNR.
Call the script once for each customer.
30-Nov-06
<Page 8 of 14 >
Steps for creating the Object.

1. Create the SAP Script layout
2. Create the driver program
3. Create a transaction code (YFICUSTSTAT) for the driver program. Please note that if this
transaction code already exists you can create transaction code with any other name.
Flow logic for printing the customer statement.
1. Execute the transaction created by you.
2. Select the required customers, company code and a suitable posting date.
3. Execute the program,
4. If there is data available for the give selection criteria, then the program will call your script.
5. This will bring a popup window asking the printer/output device type LOCL and click on print
preview to view the output of your script.
6. Technical Details
Layout windows
Reference
W1
Print on page
All Pages
W2
All Pages
W3
All Pages
W4
All Pages
W5
All Pages
30-Nov-06
Label Position
Left : 1,00 CM
Top : 1,00 CM
Width : 4,00 CM
Height : 2,00 CM
Left : 9,00 CM
Top : 1,00 CM
Width : 12,00 CM
Height : 2,00 CM
Left : 25,00 CM
Top : 1,00 CM
Width : 3,00 CM
Height : 2,00 CM
Left : 1,00 CM
Top : 4,00 CM
Width : 6,50 CM
Height : 2,00 CM
Left : 1,00 CM
Top : 7,00 CM
Width : 27,70 CM
Height : 10,00 CM
<Page 9 of 14 >
Reference
W6
Print on page
All Pages
Label Position
Left : 9,00 CM
Top : 18,00 CM
Width : 11,75 CM
Height : 2,00 CM
Field Mapping
Referen
ce
Field
Field
Descripti
on
Ref1
Text
Customer
Statement
Ref2
Text
Period
From &1
To &2
Functionality
Logic
&1 -
Print on
page
Font
All Pages
Times
14
W2
All Pages
Times
12
W2
All Pages
Times
14
Posting
From Date
Font
Format
Window
&2
Posting To
Date From
selection
screen
Ref3
KNA1Name1
Name
Ref4
Text
Document
No
All Pages
Times
12
W5
Ref5
Text
Document
Date
All Pages
Times
12
W5
Ref6
Text
Document
Type
All Pages
Times
12
W5
Ref7
Text
Item Text
All Pages
Times
12
W5
Ref8
Text
Currency
All Pages
Times
12
W5
Ref9
Text
Amount
All Pages
Times
12
W5
Ref10
BSEGBELNR
Document
No
All Pages
Times
12
W5
Name of the
customer
30-Nov-06
KNA1Name1
where
KNA!KUNNR =
BSEGKUNNR
Bold
W4
<Page 10 of 14 >
Ref11
BKPFBLDAT
Ref12
BKPFBLART
Ref13

Document
Date in
Document
Document
type
All Pages
Times
12
W5
All Pages
Times
12
W5
BSEGSGTXT
Item Text
All Pages
Times
12
W5
Ref14
BKPFWAERS
Currency
Key
All Pages
Times
12
W5
Ref15
BSEGWRBTR
All Pages
Times
12
W5
REF 16
T001BUTXT,
T001ORT01,
T001LAND1.
Amount in
document
currency
Company
name ,
City and
Country
All Pages
Times
12
W6
All Pages
Times
12
W3
Ref17
Ref18
Page no
and
current
date
Company
Logo
Company
Logo
Print the
company name
in the first line
and the city and
country in the
second line.
Page no in the
format : Page
1/1.
Date in
DD.MM.YYYY
Company Logo
30-Nov-06
All Pages
W1
<Page 11 of 14 >
7. Standards Texts/Text Modules

Reference
Text
Print on
page
Label
Position
Font
Output
Format
Font
Format
8.Translation
Reference
Description of use
(in Language1)
Description of use
(in Language2)
Description of use
(in Language3)
Text
module
Name
Notes
9. Layout Detail
Position of Left Margin
(Specify Unit)
Position of Right Margin
(Specify Unit)
Position of Logo
(Specify Unit)
Logo
(Specify Logo)
Position of Main
Window
(Specify Unit)
1.00 Cm
1.00 Cm
As given in Layout windows
EnjoySAP
As given in Layout windows
30-Nov-06
<Page 12 of 14 >
10. Custom Tables/Structure in SAP

Table Name
Short text
Size category
Table maintenance
allowed
Data class
Buffering
Table maintenance
generator
Authorization Group
Field
Data
Name
Element
Domain Type
Length Check
TableField
Key
Field
Foreign Description
Key
Comments
30-Nov-06
<Page 13 of 14 >
11. Assumptions
12. Error Handling
13. Language of texts
All texts will be in English.
14. Testing Scenarios

Normal Functionality - test cases that ensure the report functions as it should.
ID Description
1
All the data should be displayed in their respective windows. Data selection can be verified with the output of
the standard transaction FBL5n for the same set of inputs / Selection screen parameters the documents and
their values in the output should match with the output of the standard transaction
2
3
4
Exception - special logic or exceptions (e.g. report should exclude certain specific condition)
5
6
Error Handling - functionality in case of errors (e.g. Error Message or Error Log )
7
30-Nov-06
<Page 14 of 14 >

SAP Script Customer Open Items

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

SAP Script Customer Open Items

Uploaded by

Copyright:

Available Formats

SAP Implementation at PIL

SAP Script Functional Specification

Functional Specification - Forms

Last Revision Date: