sap script customer open items

FS_Template_Forms

SAP Implementation at PIL SAP Script Functional Specification

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 SHAPE \* MERGEFORMAT

Functional Specification - FormsCustomer StatementDocument Reference:TBD Version:

v1.0

Document Status:

Signed offAuthor:

Bharathithasan PandianLast Revision Date:

30-Nov-06Date Created:

30-Nov-06Date Printed:

30-Nov-06Document 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 byNameRoleSignatureDate

Process Team LeadTBDTBDTBDTBD

Development Team Lead TBDTBDTBDTBD

Document History

VersionReason for changeDate

1.0Initial Version30-Nov-2006

1.1

1.2

1.3

Table of Contents41.General Information

2.Business Needs & Requirements53. Issues64. SAP Script/Forms74.1Current Functionality74.2Printing Existing Solution74.3Desired Functionality74.4Customizing requirements75. Form Layout86. Technical Details9Layout windows9Field Mapping107. Standards Texts/Text Modules128.Translation129. Layout Detail1210. Custom Tables/Structure in SAP1311. Assumptions1412. Error Handling1413. Language of texts1414. Testing Scenarios14

1. General Information

Area (SAP System components):FI Date:30-Nov-2006

Short description:Customer Statement

Requested by:TBD

Tel no:TBD

Author: Bharathithasan PandianTel no:TBD

Program Transaction code:YFICUSTSTAT

Task ID/Demand Number:TBD

Project Name:SAP Implementation at PIL

Priority: FORMCHECKBOX High/mandatory FORMCHECKBOX Medium/recommended FORMCHECKBOX Low/optional

Complexity: FORMCHECKBOX High FORMCHECKBOX Medium FORMCHECKBOX Low

Volume of data:MediumDate available from:TBD

Mode: FORMCHECKBOX Online FORMCHECKBOX Background

Frequency: FORMCHECKBOX Daily FORMCHECKBOX Weekly FORMCHECKBOX Monthly FORMCHECKBOX Biweekly

FORMCHECKBOX Others (Specify) :

Technical information:

1. Layout created using:

FORMCHECKBOX Sapcript FORMCHECKBOX Smartform FORMCHECKBOX Subroutine pool

FORMCHECKBOX Text Elements FORMCHECKBOX Standard Texts

FORMCHECKBOX Text Id FORMCHECKBOX Print Program

General information:

1. Results if no conversions are created: FORMCHECKBOX Legal requirements not fulfilled

FORMCHECKBOX Lack of essential business information

FORMCHECKBOX Lack of functions compared to legacy system

FORMCHECKBOX Others (Specify):

duration of Development work

(in man-days):5 days (Coding+Testing)

Is there an alternative in the standard system? FORMCHECKBOX Yes FORMCHECKBOX No

Description of alternative:Correspondence request in SAP

Reasons why alternative is not acceptable: FORMCHECKBOX Performance problems FORMCHECKBOX Complexity

FORMCHECKBOX Others (Specify) : Correspondence can be request for one customer only at a time and a different layout is needed

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 process2. Establishing an Integrated information repository3. Improvement in the area of Planning4. 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.

3. Issues

NoneIssue #Issue

ownerDate RaisedIssue DescriptionIssue ResolutionResolved By & Date

4. SAP Script/Forms4.1 Current FunctionalityOutput typeSAPScript Form

Program NameRFKORD10

Layout Form NameF140_CUS_STAT_01

IMG path to access output type and layout set assignmentSAP Standard Transaction FB12

Type of solution (Standard R/3, custom ABAP)Standard R3

4.2 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):SAPScript Form

Form Types:Customer Statement

Transmission medium:Printer

Legal requirements:

Type of printer:TBD

Paper Size:A4

Orientation: Portrait/Landscape:Landscape

Special stationary to be used: No

4.4 Customizing requirements

The functional consultant will customize the following output types:

Output type

Program Name

Layout Form Names

Development system

5. Form Layout

Refer to the following for an output samples for Window mapping, Label Description and Field mapping.

Logic for the driver program.

Selection screen details

NameTable-Field / Check Box / Radio Button with groupParameter (P) / Select-option (S)Comments (Range, Single/Multiple selection, Patterns, Mandatory etc.)Default Value

Company codeTable FieldPMandatory

CustomerTable FieldSSingle/Multiple Selection/Mandatory

Posting From Date Table FieldPMandatory

Posting To Date Table FieldPMandatory

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.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

ReferencePrint on pageLabel Position

W1All PagesLeft : 1,00 CM

Top : 1,00 CMWidth : 4,00 CM

Height : 2,00 CM


Top : 1,00 CM

Width : 12,00 CM

Height : 2,00 CM


Top : 1,00 CM

Width : 3,00 CM

Height : 2,00 CM


Top : 4,00 CM

Width : 6,50 CM

Height : 2,00 CM


Top : 7,00 CM

Width : 27,70 CM

Height : 10,00 CM


Top : 18,00 CM

Width : 11,75 CM

Height : 2,00 CM

Field Mapping

ReferenceFieldField

DescriptionFunctionalityLogicPrint on pageFontFont FormatWindow

Ref1Text Customer StatementAll PagesTimes

14W2

Ref2TextPeriod From &1 To &2&1 - Posting From Date&2 Posting To Date From selection screenAll PagesTimes

12W2

Ref3KNA1-Name1Name Name of the customerKNA1-Name1 where KNA!-KUNNR = BSEG-KUNNRAll PagesTimes

14BoldW4

Ref4TextDocument NoAll PagesTimes

12W5

Ref5TextDocument DateAll PagesTimes

12W5

Ref6TextDocument TypeAll PagesTimes

12W5

Ref7TextItem TextAll PagesTimes

12W5

Ref8TextCurrencyAll PagesTimes

12W5

Ref9

TextAmountAll PagesTimes

12W5

Ref10BSEG-BELNRDocument NoAll PagesTimes

12W5

Ref11BKPF-BLDATDocument Date in DocumentAll PagesTimes

12W5

Ref12BKPF-BLARTDocument typeAll PagesTimes

12W5

Ref13BSEG-

SGTXTItem TextAll PagesTimes

12W5

Ref14BKPF-WAERSCurrency KeyAll PagesTimes

12W5

Ref15BSEG-

WRBTRAmount in document currencyAll PagesTimes

12W5

REF 16T001-BUTXT,

T001-ORT01,

T001-LAND1.Company name , City and CountryPrint the company name in the first line and the city and country in the second line.All PagesTimes

12W6

Ref17Page no and current datePage no in the format : Page 1/1.

Date in DD.MM.YYYYAll PagesTimes

12W3

Ref18Company LogoCompany LogoCompany LogoAll PagesW1

7. Standards Texts/Text Modules

ReferenceTextPrint on pageLabel PositionFontOutput FormatFont Format

8.Translation

ReferenceDescription of use (in Language1)Description of use (in Language2)Description of use (in Language3)Text module NameNotes

9. Layout Detail

Position of Left Margin (Specify Unit)1.00 Cm

Position of Right Margin(Specify Unit)1.00 Cm

Position of Logo(Specify Unit)As given in Layout windows

Logo(Specify Logo)EnjoySAP

Position of Main Window(Specify Unit)As given in Layout windows

10. Custom Tables/Structure in SAPTable Name

Short text

Size category

Table maintenance allowed

Data class

Buffering

Table maintenance generator

Authorization Group

Field NameData ElementDomainTypeLengthCheck Table-FieldKey FieldForeign KeyDescription

Comments

11. Assumptions12. 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.

IDDescription

1All 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

8

SAP Script Customer open items30-Nov-06

18SAP Script Customer open items30-Nov-06

_1226490412.xlsSheet1

Company LogoRef 1 Ref 2Page 1/1Ref 17

REF 18Date(Current Date)

Customer NameRef3

Document NoRef4Document DateRef5Document TypeRef6Item TextRef7CurrencyRef8AmountRef9

Ref10Ref11Ref12Ref13Ref14Ref15

Company AddressRef 16

W1

W2

W3

W4

W5

W6

Sheet2

Sheet3

sap script customer open items

Documents