tpc saarthi fs_fico module_cash & bank sub module_v 1.0

Functional Specification

Project Saarthi-Enabler to Business Transformation

22nd Nov 2013

TATA Power-Saarthi Project Functional Specification V1.0

Document Control

Revision History

Date Version

Author Description

25.11.2013

V1.0 Renu Bhasin Cheque – HDFC Bank

Distribution

Name Title Document Version Date

Approval Signatures

Name Title Document Version

Signature Date

Printed copies are current on date of printing only - 04/10/2023. Always refer to the electronic version for the current release. of 11

© Copyright Capgemini 2011


Table of Contents

1. <SECTION 1>...................................................................................................................................... 4

1.1 <SUB SECTION>.............................................................................................................................. 41.2 <SUB SECTION>.............................................................................................................................. 4

2. <SECTION 2>...................................................................................................................................... 4

2.1 <SUB SECTION>.............................................................................................................................. 4

3. GENERAL REQUIREMENTS..............................................................................................................4

3.1 BUSINESS DRIVER........................................................................................................................... 43.2 CURRENT FUNCTIONALITY................................................................................................................43.3 DESIRED FUNCTIONALITY.................................................................................................................43.4 ASSUMPTIONS................................................................................................................................. 43.5 CONSTRAINTS................................................................................................................................. 43.6 PERFORMANCE CRITERIA.................................................................................................................43.7 APPLICATIONS AFFECTED................................................................................................................4

4. REQUIRED DATA................................................................................................................................ 5

4.1 INPUT DATA.................................................................................................................................... 54.2 OUTPUT DATA................................................................................................................................. 54.3 DATA MAPPING............................................................................................................................... 54.4 LEGACY FILE DETAILS.....................................................................................................................5

5. FORM / REPORT DESIGN.................................................................................................................. 7

5.1 GENERAL........................................................................................................................................ 75.2 SELECTION CRITERIA....................................................................................................................... 75.3 OUTPUT LAYOUT............................................................................................................................. 9

6. CONVERSION / INTERFACE DESIGN...............................................................................................9

6.1 GENERAL........................................................................................................................................ 96.2 DEPENDENCIES............................................................................................................................. 106.3 SCHEDULING CONSIDERATIONS......................................................................................................10

7. ENHANCEMENT / MODIFICATION DESIGN....................................................................................11

7.1 GENERAL...................................................................................................................................... 117.2 REQUIRED SCREENS..................................................................................................................... 117.3 Screen Layouts........................................................................................................................... 11




1. <Section 1>

1.1 <Sub Section>

1.2 <Sub Section>

2. <Section 2>

2.1 <Sub Section>

3. General Requirements

3.1 Business DriverDescribe the business need and/or justification for the function.

For day to day Business operations, cheque payments are made on huge basis. Business requires the cheque payments is to be printed automatically through SAP system which will help to smoothline the Business operations and help in time consuming.

3.2 Current FunctionalityDescribe the current functionality.

Curently the functionality of cheque printing is available in SAP Ver ECC 5.0. Since SAP is reimplementing to latest ver. ECC 6.0 ( EHP7 ), the cheque printing program is to be incorporated in the new SAP version.

3.3 Desired FunctionalityDescribe the desired functionality.

The Standard SAP Form ( F110_PRENUM_CHK) and print program ( RFFOUS_C ) is to be created as ‘Z’ and then the modifications of Cheque fields is to be set as per the layout provided by Business.

3.4 AssumptionsState assumptions made that would impact development, test, and/or implementation of this solution.

NA

3.5 ConstraintsState any business or system constraint that will hinder development.

3.6 Performance CriteriaIdentify any system performance criteria that must be met.




3.7 Applications AffectedList of the application areas being changed or affected by this design.

SAP Module Impact/Change Description

NON-SAP System

Impact/Change Description

4. Required Data

4.1 Input DataDescribe the data required to support the development. Where possible include input field definition (Structure or Table Name, Field Name, Field Description, Format, Values). Include this information when there is no data mapping or corresponding legacy data file.

From System Name

Structure or Table Name

Structure or Table Location Expected Volume

Field Name Field Description Format Values

4.2 Output DataDescribe the data created from this development. Where possible, include output field definition (Structure or Table Name, Field Name, Field Description, Format, Values). Include this information when there is no data mapping or corresponding legacy data file.

To System Name

Structure or Table Name

Structure or Table Location Expected Volume

Field Name Field Description Format Values

4.3 Data MappingSAP fields are mapped to non-SAP (legacy) fields in the field map. The required field map rules should be described in the field map to ensure the appropriate mapping are done. This information is required for conversions.




4.4 Legacy File DetailsInclude details about all legacy data files used for input or output. This information is pertinent for conversions and file-based interfaces. For each one, specify the following information wherever applicable.

File Location and Name:Logical File Name:Variants:Legacy File Description:Sort Requirements:

Legacy File Layout:Indicate precise layout of data file. Indicate field names, key, starting position, length and format. Field names should match those indicated in under data mapping. Also indicate any required filtering.

Ref

Record

Name

Field Name Key

Field

T

y

p

eLength

Starting Position

Format Comments

5. Form / Report DesignComplete this section for form or report development. In this context, a form refers to a printed form and not an SAP screen.

The Standard SAP Form ( F110_PRENUM_CHK) and print program ( RFFOUS_C ) is to be copied as ‘Z’ and modification is to be done as per cheque layout provided by Business.

5.1 GeneralDescribe the required functionality. Specify the following information wherever applicable.

SAP Menu Path:

SAP Menu Path to generate the cheque printing is done in two ways :

A] SAP Menu Accounting Financial Accounting Accounts Payable Document Entry Outgoing Payment F-58 - Post + Print Forms OR

B] SAP Menu Accounting Financial Accounting Accounts Payable Document More Functions Print Payment Forms ( FBZ5 )

Output Determination:

Output Type: .PDF

Mode of Execution: Cheque




Program Name: RFFOUS_C

Sapscript Form : F110_PRENUM_CHK

Layout Set Name: HDFC Cheque Form

Standard Text:

Special Printing/Media Requirements: To be printed on continuous stationery of HDFC Cheque on Printer :

Sort Criteria:

Logo:

Bar Codes:

Distribution/Volume:

5.2 Selection CriteriaSpecify all parameters to the form or report.

Field Name

Table Field / Checkbox / Radio Button

Select-Option (S) or

Parameter (P)

Comments (Range, Single/Multiple Selection, Patterns, Mandatory, etc.)

Default Value

Short Key of House Bank

PAYR-HBKID

Payment Method

REGUH-RZAWE

Payment Doc.No

REGUH-BELNR

Cheque Date REGUH-LAUFDPayee Name REGUH-

ZNEM1, REGUH-ZNEM2

Cheque Amount in Fig.

REGUH-RBETR

Procedure :

Step 1 :

As the Business requirement is to print cheques on pre-printed stationery which is separated with a perforation between two cheques, you need to copy the Standard SAP Form ( F110_PRENUM_CHK) and print program ( RFFOUS_C ) and make them as ‘Z’ and modify the




form as per custom requirement.

Step 2 :

As mentioned in Step 1, the new Z- SmartForm and Z – print program name will be assigned in the FI IMG customizing for Cheque printing.

Step 3 :

A] The Functional process for generating the Payment Document Number which triggers the Print Program .(ZRFFOUS_C)

There are two ways to generate the Payment Document Number :

01 ] Tcode : F-58 ( Payment with Printout : Header Data )

02] Tcode : FBZ5 ( Print form for Payment Document )

B] Following Tables will be used for Cheque printing :

REGUH Settlement data from the payment program REGUP Edited invoice items from the payment program REGUD Formatted data for printing the forms SPELL Amounts and digits in words. FSABE Data on accounting clerk.

C] Logic :

The Custom Z-Print program is assigned to the Payment Method ‘C’ ( Cheque ) of relevant Country and Company code.

01 ] As per the Short key of House Bank ( PAYR – HBKID ), it will check whether the payment method ( REGUH –RZAWE ) = ‘C’ ( Cheque ) and will get the list of Payment Document Number ( REGUH – BELNR ) to be printed on Cheque format.

02] As per the Payment Doc.Number ( REGUH – BELNR ), the other field data is fetched to print on the cheque form.

Sr.No.Field name on Cheque SAP Field name Table - Fieldname

1 Date Cheque Date REGUH-LAUFD

2 Pay Vendor / Payee nameREGUH-ZNME1, REGUH-ZNEM2

3 Rs.Cheque Amount in Figures REGUH-RBETR




4 Rupees :Cheque Amount in Words

Functional Module 'SPELL_AMOUNT' is used to convert Cheque Amount in Words

5.3 Output LayoutAttach a form or report layout. Include field layout, spacing, header/footer details. Indicate whether times should indicate local or system time. Specify paper format and paper size if not indicated in media requirements.

HDFC cheque form layout has been attached below. As per the above logical procedure the data will be fetched and should be pre-printed on continous stationery of cheque form within the relevant Space of each field.

After creating the cheque form layout through Abap Team , foll. are the activities for Basis Consultant :

1] The Basis Consultant will check the driver attached to the Printer .

2] The Output device type ‘SAPWIN’ is to be selected and access method as ‘F’ ( print on front end computer )

3]The Page format and spool format created by Abap consultant will be assigned to ‘SAPWIN’ by Basis Consultant.

6. Conversion / Interface DesignComplete this section for conversion or interface development.


Inbound/Outbound:Frequency:Volume:Legacy Data Source:Legacy Contact:Method of Execution:Mode of Handling:Data Cleansing Process:Reconciliation Process:Data Consistency Check:Error Handling Method:Interface Process Log Details:




Post Execution Notification Details:

6.2 DependenciesDescribe any dependencies, such as data that must be loaded or converted prior to execution.

6.3 Scheduling ConsiderationsDescribe any scheduling considerations. Specify the following information wherever applicable.

Synchronous/Asynchronous:Load Balancing/Parallel Processing:Other System Loads at Time of Process Run:Time Window for Execution:Triggering Mechanism/Process:




7. Enhancement / Modification Design


Transaction Code:Menu Path:User Exit Name:

7.2 Required ScreensList all required screens. Describe their purpose and flow.

7.3 Screen LayoutsComplete the following attachment for each screen.



tpc saarthi fs_fico module_cash & bank sub module_v 1.0

Technology