FUNCTIONAL SPECIFICATION wricef

Scenario (Business Area): FI

Business Process:

This document is intended to specify RICEFW object from a functional perspective. It will be followed by a
technical specification. This document has three main sections
General Object information, to be filled in for all RICEFW objects
Object specific section, only relevant sections need to be filled in, e.g. if this document specifies a
report fill out the general information, the report specific and
the test condition section at the end.
This document builds and refers to two preceding documents
Requirements - BPR
Solution design BPD
In addition, all RICEFW object are consolidated in the RICEFW list

The project manager and the quality manager have to revise this template before it is used for the project
and especially before it is given to the customer
Be sure to delete these instructions when you have finished!

Author Document Location (repository/path/name)

<Author> <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Final <Date> Confidential

REVISION HISTORY

Version Date Description

0.1
0.2

REVIEW AND APPROVAL

1 of 22
Name
Customer Project Manager

Name Date (YYYY-MM-DD)

SAP Project Manager

Name Date (YYYY-MM-DD)

Key Stakeholder

Name Date (YYYY-MM-DD)

Key Stakeholder

` 2 of 22
TABLE OF CONTENT

1. PURPOSE OF THIS DOCUMENT........................................................................................................4

2. GENERAL OBJECT OVERVIEW.........................................................................................................5
2.1 Process Requirements Reference.................................................................................................6
2.2 Generic WRICEF Descriptions......................................................................................................6
3. OBJECT SPECIFIC DESIGN............................................................................................................... 8
3.1 Reporting (operational and analytical)...........................................................................................8
3.2 Interfaces..................................................................................................................................... 12
3.3 Data Conversion / Historical Data................................................................................................15
3.4 Enhancements............................................................................................................................. 17
3.5 Output (e.g. forms)...................................................................................................................... 18
3.6 Workflow...................................................................................................................................... 20
4. TEST CONDITIONS........................................................................................................................... 21

` 3 of 22
1. Purpose of this document
The purpose of this document is to specify the background information, business requirements, functional design, and
the scope of the development for the Vessel General Ledger reports. This document will be used by the Technical
Consultants in order to develop the program. This is also to be used by the Internal Support Team for supporting the
system.

` 4 of 22
2. General Object Overview

Object Overview

Business
Object ID
Process

SAP FI
SAP Release
Module
( X) Report
( ) Interface
( ) Conversion
Object Type
( ) Enhancement
( ) Form
( ) Workflow
Object Title Vendor Payable Data REPORT

Object Description

Mock Up ID / Name

Required
Cycle of Testing / C1 / C2 / C3 / C4 Development
Sprint Cycle
Completion Date
Simple / Medium /
Complexity of Object Priority Low / Medium / High
Complex
SAP Transaction SAP Program
Name Name

Similar SAP Similar SAP

Transaction Program

FS Control
<Customer>
Functional Consultant
Process Owner
Author and Phone
and Phone
Number
Number

Planned Date of FS Actual Date of FS

Completion Completion

FS Approved By FS Approval date

Other Contact and Other Contact and

Phone Number Phone Number

` 5 of 22
2.1 Process Requirements Reference

Process Reference
Requirement ID
Requirement As per the business requirements, a customized Z report(ABAP) will
Description be developed for new cash call report
Gap to be
addressed
Alternative SAP
Standard Solution

2.2 Generic WRICEF Descriptions

Justification
[Provide a high level description reason from deviation from standard SAP reports or BW
reports.

FUNCTIONAL DESCRIPTION / DESIGN

WSM requires a report to view Vendor Payable details in desired format.This

report will be used for the VA company codes only. This new report contains the
information related to vendor details, expenses (actual expenses spend on the
particular period) with respective company code wise (vessels) in required
format.
In this report WSM can analyse the vendor data by selecting given option like
posting date wise, due date wise and total item data wise.
The report will extract with required input selection parameters and same
will be sent to vessel owners with detail information.

TRANSACTION VOLUME

As per the business requirements, a customized Z report(ABAP) will be

developed for new cash call report

` 6 of 22
FREQUENCY & TIMING

DEPENDENCIES

AUTHORIZATION REQUIREMENTS

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING

REPORT, ETC)

` 7 of 22
3. Object Specific Design

3.1 Reporting (operational and analytical)

Reporting

WRICEF Description Report Type Data Elements Relevant KPI Owner

-ID (ABAP, BI,
BOBJ)

Selection Criteria

` 8 of 22
Table/ Field Name Format Defaul Table Select Mandator Field
Structur t Value/ Option or y or Labels
e Name Value Checkbox Paramet Optional
/ er
Radio
Button/
Radio
Button
Group
BKPF BUKRS Select Comp
option any
Code
LFA1 LIFNR Select Vend
option or
accou
nt
BKPF MONAT Paramet Repor
er ting
by
perio
d

BKPF GJAHR Paramet Fiscal

er year

FLAGF RPMAX Paramet Postin

LEXA er g
period
BKPF BLDAT Radio Paramet Postin
button er g
Date
BSEG ZFBDT Radio Paramet
button er Due
Date
BSIK AUGDT Radio Paramet Open
button er Items

` 9 of 22
Functional Design, Validation and Variants

Processing logic :

A) In order to populate values in the Report, the relevant data needs to be

extracted from the SAP database. The information is related to vendor
information and vendor line items are kept in SAP Tables BKPF, BSEG and LFA1.

1) Go to BKPF table and fetch document numbers, and pass these values in BSEG.

Selection parameters-BKPF :

Company Code-> BKPF-BUKRS

Invoice Date(Doc Date)-> BKPF-BLDAT
Invoice No(Doc Number)-> BKPF-BELNR

2) Go to table BSEG and pass the document numbers, fetch the below vendor
information and populate the respective fields.

Selection parameters-BSEG:

Company Code-> BSEG-BUKRS

Venodr Code-> BSEG-LIFNR
Vendor Name-> LFA1-NAME1
Invoice No.-> BSEG-BELNR
Invoice Date-> BKPF-BLDAT
Invoice Due date-> BSEG-ZFBDT
Ref Key 3-> BSEG-XREF3
Ref Key 1-> BSEG-XREF1
Curr. Code-> BSEG-PSWSL
Cur Amt-> BSEG-WRBTR
Amount USD -> BSEG-DMBTR ( if local currency is USD)
Text Description -> BSEG-SGTXT
GL Expense Code -> BSEG-HKONT

` 10 of 22
Report Output

Output Method
Example:
Saved to File / Sent to print / Send to email account / Download to excel
The sample out put is attached as object below.(As per the requirement, excel output will
be provided) .

Vendor payable
Main Heading
extract - cash call (1R).xlsx
Example:
The main report heading will be: Vendor Payable Data REPORT

Sub Heading

Example:

LAYOUT
Table/Structure Field Name Format Default Value Column Name Translation Rule
Name (ie
decimal
places)
BKPF BUKRS Company Code

BKPF BLDAT Invoice Date

BKPF BELNR Invoice No

BSEG BUKRS Company Code

BSEG LIFNR Venodr Code

LFA1 NAME1 Vendor Name

BSEG BELNR Invoice No

` 11 of 22
BKPF BLDAT Invoice Date

BSEG ZFBDT Invoice Due

date
BSEG XREF3 Ref Key 3

BSEG XREF1 Ref Key 1

BSEG PSWSL Curr. Code

BSEG WRBTR Cur Amt

BSEG DMBTR Amount USD

BSEG SGTXT Text

Description
BSEG HKONT

DRILLDOWN REQUIREMENTS

TOTALING

Example:
Number of contracts matching user selection criteria to be displayed at the bottom of the report

Any page-break requirements?

Example:
Users will be able to sort on contract type and vendor. Default sort sequence will be by contract type.

Any page-break requirements?

Example:
Page breaks will be used where necessary to prevent overflow of retrieved data

Typical errors include: No data found for given selection criteria.

` 12 of 22
3.2 Interfaces
<Identify all interfaces required to provide inputs to or outputs from this part of the process. Provide a
functional description of the interfaces including the source and type of data.>

Interface
WRIC Description Interface Application Data Elements Frequency / Owner
EF-ID Method s Volumes
XX-
xx-
I001

Interface Process Flow Diagram, incl.Transfer Method/ Network Integration

File Specifics

` 13 of 22
MAPPING SAP FIELDS TO SOURCE / TARGET
[Please provide details of the expected mapping between the Source / Target system and
SAP fields. This can either be done within a table in this document or as an attached Mapping
Document.

Specifications for the following elements should be present on the Mapping document (where
applicable):

SAP Transaction
SAP Screen number
SAP Table name
SAP Field name (functional)
SAP Field name (technical)
SAP field length
SAP field type
Mandatory / Optional flag
Source / Target Field ID
Source / Target Field Name (functional / technical)
Source / Target Field length
Source / Target Field type
Mapping Details
Implementation Comments

` 14 of 22
RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS

Reporting
[Please describe any reporting that is expected to be provided in support of this interface]

Approach
[Detail the method of data reconciliation e.g. reports produced in SAP]

Metrics
[Provide details on the metrics used to facilitate reconciliation e.g. Record Count]

Error Handling
[Include potential errors, notification procedures, and contingency procedures.]

` 15 of 22
3.3 Data Conversion / Historical Data
<Note all master and transactional data conversion requirements. Please note specific fields that are unique
to this design and the business requirement that drives that design. Note whether manual and automated
data conversion requirements. Provide details of all data required from Legacy Systems (Consider System
name, level of detail, time dimension). Identify requirements for historical data conversion mandatory for the
process. This is not meant to be an exhaustive functional spec but a place to list conversions related to this
process.>

Conversions
WWRIC Conversio Source Conversio Conversion # of Owner
EF-ID n Object n Activities Method Objects to
(e.g. (manual / be
cleansing) automated) converted

1MAPPING SAP FIELDS TO SOURCE / TARGET

[Please provide details of the expected mapping between the Source / Target system and
SAP fields. This can either be done within a table in this document or as an attached Mapping
Document.

Specifications for the following elements should be present on the Mapping document (where
applicable):

SAP Transaction
SAP Screen number
SAP Table name
SAP Field name (functional)
SAP Field name (technical)
SAP field length
SAP field type
Mandatory / Optional flag
Source / Target Field ID
Source / Target Field Name (functional / technical)
Source / Target Field length
Source / Target Field type
Mapping Details
Implementation Comments

` 16 of 22
RECONCILIATION PROCEDURES & AUDIT REQUIREMENTS

Reporting
[Please describe any reporting that is expected to be provided in support of this interface]

Approach
[Detail the method of data reconciliation e.g. reports produced in SAP]

Metrics
[Provide details on the metrics used to facilitate reconciliation e.g. Record Count]

Error Handling
[Include potential errors, notification procedures, and contingency procedures.]

` 17 of 22
3.4 Enhancements
<Specify the enhancement based on the proposed gap resolutions listed in the Detailed Requirements and
Design documents. Provide as much detail on the requirements and design considerations as you can. If
there is a large enhancement then consider detailing that in a separate design or functional spec. document.
>

enhancements
WRIC Description Data Object Functional Alternative Reason Owner
EF-ID (Sales Order) Gap SAP Standard

Functional Design / Flow, Validation and Variants

Flow
[Please provide the flow of object to be enhanced. For example in the program XYZ go to
screen/Sub screen 101 there modify/add a field]

Design
How should the data be processed in the program functional logic?

` 18 of 22
3.5 Output (e.g. forms)
<Identify outputs and forms>

Output
WRIC Description Data Object Output Type Frequency Volumes Owner
EF-ID (Sales (Form, EDI, etc.)
Order)
XX-
xx-
O001

Process Flow Diagram

[Please insert a flow diagram describing the form output procedure e.g. Purchase Order input
using transaction ME21N; save Purchase Order automatically generates Purchase Order
Form printout]

Form Layout
[Please provide a sample layout for first, subsequent and last pages, detailing actual
positions of output fields, fonts, font sizes]

Please indicate if there is pre-printed stock and which portions are on the pre-printed stock

Example:

Form Title Date: xxxxx1

User: xxxxx2

ID Value Description
xxxxx3 xxxxx4 xxxxxxxxxx5
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx

` 19 of 22
Printer Requirements
Duplex Printing, label printing, label dimensions, standard, etc.

Legal Requirements
Determine if there is any text that is required legally on the form, including font size, text to be
printed on the back of documents,

Existing Sample Forms

[If an existing program is available to be enhanced, provide details in this section]
Program Name
Menu / Transaction
Legacy Form name
Legacy Program Title
Legacy Form Number
Related Transactions

` 20 of 22
3.6 Workflow
<Identify workflow requirements for this process. Provide detailed requirements for the workflow. e.g., purchase order
approval process and authority levels etc.>

Workflow
WRIC Description Business / Data Object Engaged Parties Owner
EF-ID (Sales Order)
XX-
xx-
W001

Process Flow Diagram

[Please insert a flow diagram of the workflow]

Trigger Events

Transactions and Batch Programs that trigger the workflow

Start Conditions

Rules and Determination

Standard Rules

Latest End, Latest Start

Requested End , Requested start

` 21 of 22
4. Test Conditions

BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)

[Please indicate the business level test conditions that should be used to verify successful
operations of the Report]

[Document all technical scenarios associated with this development. Examples would include
1) testing an error-free run; 2) testing the exception processes; 3) testing the error handling.]

[Document all control scenarios associated with this development. Examples would include 1)
Rounding of dollars and cents; 2) Audit trail processing; 3) Reconciliation reporting]

Scenario # Input Selection Criteria Expected Result

` 22 of 22