Sapscript Proforma Billing Document v1.0

SAP Implementation Of 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 – SAP ScriptFast Track Proforma Billing Document

Document Reference: TBDVersion: v1.0 Document Status: Signed off

Author: Anup Das

Last Revision Date: 21-Nov-2006Date Created: 21-Nov-2006Date Printed: 21-Nov-2006

SAPScript_Proforma_Billing_Document_v1.0 21-Nov-2006 < of 15>



Document Control

Business Area Proforma Billing Document

GAP ID TBD

FS Definition Form ID TBD

SAP R/3 Version ECC 5.0

Location / Site TBD

Approval and Distribution

Approved by Name Role Signature DateProcess Team Lead

TBD TBD TBD TBD

Development Team Lead

TBD TBD TBD TBD

Document History

Version Reason for change Date1.0 Initial Version 21.11.20061.11.21.3

SAPScript_Proforma_Billing_Document_v1.0 21-Nov-2006 < of 15 >



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...........................................................................................................................................................................9FIELD MAPPING..............................................................................................................................................................................9

7. STANDARDS TEXTS/TEXT MODULES...............................................................................................................................................12

4.2 TRANSLATION...............................................................................................................................................................................12

8. LAYOUT DETAIL............................................................................................................................................................................13

9. CUSTOM TABLES/STRUCTURE IN SAP...........................................................................................................................................14

10. ASSUMPTIONS..............................................................................................................................................................................15

11. ERROR HANDLING.........................................................................................................................................................................15

12. LANGUAGE OF TEXTS....................................................................................................................................................................15

13. TESTING SCENARIOS.....................................................................................................................................................................15




1. General Information

AREA (SAP SYSTEM COMPONENTS):

SD Date: 15.11.2006

Short description: Billing Document

REQUESTED BY: TBD Tel no: TBD

AUTHOR: Anup Das Tel no: TBD

Program Transaction code: SAP Script

Task ID/Demand Number: TBD

Project Name: SAP Implementation at PIL

Priority: High/mandatory Medium/recommended

Low/optional

Complexity: High Medium Low

Volume of data: Medium DATE AVAILABLE FROM:

TBD

Mode: Online Background

Frequency: Daily Weekly Monthly Biweekly Others (Specify) :

Technical information:

1. Layout created using: Sapcript Smartform Subroutine pool Text Elements Standard Texts Text Id Print Program

General information:

1. Results if no conversions are created:

Legal requirements not fulfilled Lack of essential business information Lack of functions compared to legacy system Others (Specify):

DURATION OF DEVELOPMENT WORK

(IN MAN-DAYS):

5 Days

Is there an alternative in the standard system?

Yes No

Description of alternative:

Reasons why alternative is not acceptable:

Performance problems Complexity Others (Specify) :




2. Business Needs & RequirementsPower 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

Proforma Invoice – Is used for the purpose of billing verification prior to receipt of the standard invoice, for issuance of an import license as well as for SGS inspections. In addition this document is used for issuance of a Letter of Credit when one is required by the Customer. The Proforma Invoice is faxed to the customer upon customer request. It contains the following billing-related information: Sold-to party name & number, Ship-to party name & number, purchase order date & number, sales order number, ship date, item information, pricing information, and delivery information.

The purpose and scope of this functional specification is to communicate the need for the SAP Script development of a Pro Forma Invoice for export. A Proforma invoice appears exactly the same as a customer invoice. The difference is that this invoice does not need to be paid. Therefore, the system does not forward data to Financial Accounting (FI). No statistical data is created on the basis of Proforma invoices




3. Issues

None

Issue #

Issue owner

Date Raised

Issue Description Issue Resolution Resolved By & Date




4. SAP Script/Forms

4.1 Current Functionality

Output type RD00Program NameLayout Form NameIMG path to access output type and layout set assignmentType of solution (Standard R/3, custom ABAP)

R/3

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): RD00Form Types: Proforma Invoice (Billing Document output)Transmission medium: PrintLegal requirements:Type of printer:Paper Size: Letter A4: 8 ½” x 11”Orientation: Portrait/Landscape: PortraitSpecial stationary to be used: None. Invoice will be printed on plain white paper.

4.4 Customizing requirementsThe 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.




6. Technical Details

Layout windows

Reference Print on page Label Position

Name

W1 All Pages X Y

Date Window

W2 All Pages X Y

Title window

W3 All Pages XY

Bill To Party Window

W4 All Pages XY

Ship To Party Window

W5 All Pages XY

Sold To Party Window

W6 All Pages XY

Billing Header Deatils

W7 All Pages XY

Order Details

W8 All Pages XY

Main window

W9 All Pages XY

Header Window

W10 All Pages XY

Total Window

W11 All Pages XY

Remarks Window

Field Mapping

Field FieldDescription

Functionality Logic Print on page

Font Font Format

Window

H1 Date Current Page/Total Pages

PAGE/SAPSCRIPT-FORMPAGE

All 10 Helve W1

H2 Title Proforma Invoice Standard Text All 14 Helve W2




H3 Invoice Number

Billing Document VBDKR-VBELN All 10 Helve W2

H4 Bill To Party Address

Billing Address Details

ADRC-NAME1,ADRC- CITY1,ADRC- POST_CODE1,ADRC- PO_BOX,ADRC- STREET,ADRC- REGION,ADRC- COUNTRYFor parvw ‘BP’

All 10 Helve W3

H5 Ship To party Address

Shipping Address Details

ADRC-NAME1,ADRC- CITY1,ADRC- POST_CODE1,ADRC- PO_BOX,ADRC- STREET,ADRC- REGION,ADRC- COUNTRY For Parvw ‘SH’

All 10 Helve W4

H6 Sold To Party Address

Sold To Details ADRC-NAME1,ADRC- CITY1,ADRC-POST_CODE1,ADRC- PO_BOX,ADRC- STREET,ADRC- REGION,ADRC- COUNTRY For Parvw ‘SP’

All 10 Helve W5

H7 Billing DetailsInvoice Date,Customer Purchase Order’s no.Payment Terms

VBDKR-FKDAT,VBRK-BSTNK_VFVBRK-ZTERM

All 10 Helve W6

H8 Order No. Order Number VBDKR-VBELN_VAUF All 10 Helve W7

H9 Delivery No. Delivery Number VBDKR-VBELN_VL All 10 Helve W7

I1 Item No Item No VBRP-POSNR All 10 Helve Main

I2 Material No. Material No. VBDPR-MATNR All 10 Helve Main

I3 Material Description

Material Description

VBDPR-ARKTX All 10 Helve Main

I4 Quantity Quantity and Unit VBDPR-FKIMGVBDPR-VRKME

All 10 Helve Main

I5 Gross Weight Gross Weight and Unit

VBDPR-BRGEW, VBDPR-GEWEI

All 10 Helve Main

I6 Net Value Net value of the billing item

KONV-KBETR All 10 Helve Main

F1 Total Quantity

Total quantity Sum of all I4 All 10 Helve W9




F2 Total Net Value

Total Net Value Sum Of all I6 All 10 Helve W9

F3 Remarks Remarks Standard Text

Refer to Logic in Label 6 All 10 Helve W10




7. Standards Texts/Text Modules

Reference Text Print on page

Label Position

Font Output Format

Font Format

H1 Page All 10 Bold Arial

H2 Proforma Invoice

All Label 1 14 Bold Arial

H3 Invoice No. All 10 Bold Arial

H4 Bill To Party All Label 2 10 Bold Arial

H5 Ship To Party All Label 3 10 Bold Arial

H6 Sold To Party All Label 5 10 Bold Arial

H7 Billing Details All Label 4 10 Bold Arial

H8 Order No. All 10 Bold Arial

H9 Delivery No. All 10 Bold Arial

I1 Item No. All Label 7 10 Bold Arial

I2 Material No. All Label 8 10 Bold Arial

I3 Description All Label 9 10 Bold Arial

I4 Quantity All Label 10 10 Bold Arial

I5 Gross Weight All Label 11 10 Bold Arial

I6 Net Value All Label 12 10 Bold Arial

F1 Total Quantity All Label 15 10 Bold Arial

F2 Total Net Value All Label 14 10 Bold Arial

F3 Remarks All Label 16 10 Bold Arial

F3 This is a Proforma Invoice

All Label 16 10 Bold Arial

4.2 TranslationNo Translation required. If some translation needs to be done then we can translate the standard texts through SE63 transaction and by providing the source and destination language.Reference Description of use

(in Language1)Description of use (in Language2)

Description of use (in Language3)

Text module Name

Notes

NA NA NA NA NA NA




8. Layout Detail

Position of Left Margin (Specify Unit)

2.37 CM

Position of Right Margin(Specify Unit)

0.33 CM

Position of Logo(Specify Unit)

NA

Logo(Specify Logo)

NA

Position of Main Window(Specify Unit)

2.40 CM Left Margin and 10.07 CM Upper Margin




9. Custom Tables/Structure in SAPNo Such Custom Tables required.

Table Name NAShort text NASize category NATable maintenance allowed

NA

Data class NABuffering NATable maintenance generator

NA

Authorization Group NAField Name

Data Element

Domain Type Length Check Table-Field

Key Field

Foreign Key

Description

NA NA NA NA NA NA NA NA NA

Comments




10. Assumptions

Requirements:Steps needed to be followed for configuring the output type RD00.>> Go to NACE transaction>> Select Application as V3 and click on Output Types Tab>> Select RD00 from the list of Output types displayed and click on processing routines

>> Here change the program name and form name according to your design.Don’t give any Smartform Name.

11. Error HandlingNone

12. Language of texts

English EN.

13. Testing Scenarios

Normal Functionality - test cases that ensure the report functions as it should. ID Description1 The Proforma invoice layout with all the header and item details would be displayed.234Exception - special logic or exceptions (e.g. report should exclude certain specific condition)

56Error Handling - functionality in case of errors (e.g. Error Message or Error Log )

7

8


Sapscript Proforma Billing Document v1.0

Documents

Transcript of Sapscript Proforma Billing Document v1.0