You are on page 1of 13

FS for Payment details requirement

Functional Specification Payment details requirement


Document Reference:
Document Status:

Version:
1.0
Review [Draft/Review/Signed Off]

Author:

Malati Bhatt

Last Revision Date:


Date Created:
Date Printed:

26/12/2016
26/12/2016

RFS Payment details requirement


1 of 13>

26 Aug. 16

<Page

FS for Payment requirement

Document Information
Business Area

FI

GAP/CR ID
FS Definition Form ID
SAP R/3 Version

6.0

Global / Market

Approval
Approved by
Process Team
Lead
Development
Team Lead

Name

Role

Signature

Date

Document History
Version
1.0
1.1
1.2
1.3

Reason for change


Initial creation

RFS payment requirement

Date
26 Aug. 16

08/09/2016

<Page 2 of 13 >

FS for Payment requirement

Table of Contents
1. General Information..................................................................................................4
2 Business Needs & Requirements............................................................................5
3 Assumptions..............................................................................................................5
4 Issues..........................................................................................................................5
5 Functional Details......................................................................................................5
5.1 Current functionality..............................................................................................5
5.2 Required functionality............................................................................................5
6 Technical Details........................................................................................................6
6.1 SAP User-Exits6
6.2 Function Exits...................................................................................................6
6.3 Field Exits..........................................................................................................6
6.4 Menu Exits.........................................................................................................7
6.5 Screen Exits......................................................................................................7
6.6 Search Help Exits.............................................................................................7
6.7 Search Help assignment..................................................................................7
6.8 BADI...................................................................................................................7
6.9 Custom Transaction.........................................................................................8
6.10 Requirement routine......................................................................................8
6.11 Business Transaction event (If any..)...........................................................8
6.12 Substitution.....................................................................................................8
7 Custom Tables/Structure in SAP.............................................................................9
8 Data Source consideration.....................................................................................10
8.1 Data Validation................................................................................................10
9 Error Handling..........................................................................................................10
9.1 Error Messages...............................................................................................11
10 Security Requirements/ Authorization Details..................................................11
11 Testing Scenarios.................................................................................................11
12 Additional Information and attachments...........................................................11

RFS payment requirement

08/09/2016

<Page 3 of 13 >

FS for Payment requirement

1. General Information

AREA (SAP SYSTEM COMPONENTS):

Date:

Short description:
Tel no:
Tel no:

REQUESTED BY:
AUTHOR:

Program Transaction code:


Task ID/Demand Number:
Project Name:
Priority:
Complexity:
Volume of data:
Mode:
Frequency:

High/mandatory
Medium/recommended
Low/optional
High
Medium
Low

DATE AVAILABLE FROM:


Online
Background
Daily
Weekly
Monthly
Biweekly
Others (Specify) :

Technical information:
1. Type of Enhancement

2.Module /Sub module


Information
3. Data Object (Purchase
order/sales order etc.)

User Exit
BADI
Custom transaction
event
Substitution & Validation Others
Sap Std program modification

Requirement routine
Business transaction

FI
Payment details extraction
NA

4. Dependency on any object


General information:
1. Results if no conversions are
created:
APPROX. DURATION OF DEVELOPMENT
WORK (IN MAN-DAYS):

Is there an alternative in the


standard system?
Description of alternative:
Reasons why alternative is not
acceptable:
Reference Document

RFS payment requirement

Legal requirements not fulfilled


Lack of essential business information
Lack of functions compared to legacy system
Others (Specify):

Yes

No

Performance problems
Others (Specify) :
Any Dev or doc which is of use

08/09/2016

Complexity

<Page 4 of 13 >

FS for Payment requirement

Business Needs & Requirements


Requirements:

BAPI is required for fetching payment details of employees. Payments details will be required
for all the expenses (travel claims) which are processed in concur travel management portal.
This BAPI will be executed in back ground and output will be pushed to concur.

Assumptions

Issues
Issue
#

Issue
owner

Date
Raised

Issue Description

Issue Resolution

Functional Details
5.1

Current functionality

In Marico current functionality is not available.

5.2

Required functionality

From SAP table REGUP four fields are required base on below selection criteria

Run date
Indicator: Only Proposal Run? YES
Vendor number are constant 1000 -19999
Reference number are constant E001 -E999999

RFS payment requirement

08/09/2016

<Page 5 of 13 >

Resolved
By & Date

FS for Payment requirement

The output data should fetch in one Ztable for further process
Output
Claim ID (Reference)
Payment Amount
Payment Document Number
Payment Date

RFS payment requirement

08/09/2016

<Page 6 of 13 >

FS for Payment requirement

Technical Details

Field

Key/Sort

Data
element

Type

Length

Check table

Description

6.1 SAP User-Exits


Enhancement

Main Program

Includes

Form Routines

N.A

6.2 Function Exits


Main Program Logical
trigger Point

Enhancement

Function Module
Name

Includes

N.A

6.3 Field Exits

Enhancement

Main
Program
Name

RFS payment requirement

Function
Module
Name

Field Exit Id

08/09/2016

Screen
Number

Screen
Field
Name

Conditions
for
execution

<Page 7 of 13 >

FS for Payment requirement

N.A

6.4 Menu Exits


Enhancement

Menu/Path

Function/Transaction Code

N.A

6.5 Screen Exits


Enhancement

Screen
Number

Main Program Name

Program Name & Sub-Screen


Number

N.A

6.6 Search Help Exits

Field
Name

Field Description

Import /
Export
(I/E)

Key
Field

Data
Element

Type
(CHAR,
NUMC)

Length

Default
Value

(Y/N)

N.A

6.7 Search Help assignment


Standard Search
Help

Collective Search Help

Elementary Search Help

N.A

6.8 BADI
BADI Name

RFS payment requirement

Methods

08/09/2016

Comments

<Page 8 of 13 >

FS for Payment requirement

:
ZASP_IOCHE
CK

6.9 Custom Transaction


6.10

Requirement routine

Menu/Submenu
Routine number
Business logic required

6.11

Business Transaction event (If any..)

6.12

Substitution

<For FI related transaction specifically>


Validation
Description

Substituted Field

RFS payment requirement

Fields required
for validation

Derived from
Field

Point of
Validation

Table
used in
validation

Table used in
Substitution

08/09/2016

Business Rules

Business Rules

<Page 9 of 13 >

FS for Payment requirement

Custom Tables/Structure in SAP

Table Name
Short text
Size category
Table maintenance
allowed
Data class
Buffering
Table maintenance
generation
Authorization Group
Field
Data
Name
Element

Elaborated in detail in TS Template

Domain Type

Length Check
TableField

Key
Field

Foreign Description
Key

Comments

Data Source consideration

Field name /
Description

RFS payment requirement

Table Field Name

08/09/2016

Comments / Calculations / Field


Manipulations

<Page 10 of 13 >

FS for Payment requirement

8.1 Data Validation


Table Field Name
NA

Validation Rule
NA

Error Handling

9.1 Error Messages

Error Message
Number
1.
2.

10

Error Message Text


(70 characters)
NA

Error Conditions
NA

Security Requirements/ Authorization Details

RFS payment requirement

08/09/2016

<Page 11 of 13 >

FS for Payment requirement

11

Testing Scenarios

Go to Tcode SE37 (Function Module)

Press Enter

Click on Test Directory Select Variant Testing

Then Execute & Click on ET_RESULT

Output

RFS payment requirement

08/09/2016

<Page 12 of 13 >

FS for Payment requirement

12

Additional Information and attachments

Payment
Confirmation.docx

RFS payment requirement

08/09/2016

<Page 13 of 13 >

You might also like