FUNCTIONAL SPECIFICATION wricef

SCENARIO (BUSINESS AREA): FINANCE

Business Process:

How to use the Template

Blue text is always intended as

instructions, guidelines, explanations, hints, and tips. It has to be removed when
the document is finalized. To provide a consistent representation of this document to the customer, chapters should
not be deleted or inserted. Required additions should be made as sub-chapters to existing chapters.
Chapters that are not relevant should be marked as such (that is, add “not relevant” or “not applicable”).

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
Delete Revision History section below if not applicable for the document!

Version Date Description

0.1 February 4, 2010 <Text here>
0.2

1 of 18
` 2 of 18
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 18
1. Purpose of this document
The Specification is the basis for the developments that will be done by SAP. <Customer> has to verify and approve it
formally. Realization starts only after approval.

Within the SAP Custom Development Methodology, the Specification is the link between the business requirements
(normally given in the solution proposal) and the technical design (a separate document). It has the following goals:
• Reference to the business requirements (customer requirements) given in the solution proposal.
• Show the mapping into standard SAP products.
• Describe the solution from an external (user or customer) point of view.
Implementation details (database model, report names, and so on) are generally NOT part of the Specification.
[Customers shall be enabled to recognize that all their requirements are taken into consideration. For approval of the
Specification they have to understand the solution.]

` 4 of 18
2. General Object Overview

Object Overview

GST_GAF Business
Object ID
Process

ECC6 SAP FINANCE

SAP Release
Module

( X ) Report
( ) Interface
( ) Conversion
Object Type ( ) Enhancement
( ) Form
( ) Workflow
GST GAF Report
Object Title
GST GAF Report
Object Description

Mock Up ID / Name

UT / SIT / UAT Required

Cycle of Testing /
Development
Sprint Cycle
Completion Date

Complexity of Object Simple / Medium / Complex Priority Low / Medium / High

SAP Transaction SAP Program

Name Name

Similar SAP Similar SAP

Transaction Program

FS CONTROL

` 5 of 18
 <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

2.1 Process Requirements Reference

Process Reference
Requirement ID
Requirement This program will be used by WSM to execute the Malaysia GST Audit File
Description Report. This program will also generate an XML file as per RMCD
specification.

Gap to be addressed This is a Malaysian GST statutory requirement report to be generated monthly
and kept for audit purposes.

Alternative SAP
Standard Solution

2.2 Generic WRICEF Descriptions

Justification
It is crucial that the detailed information transmitted between RMCD and businesses are complete,
accurate and in a format that is readable by MyGST (RMCD audit software). Hence, it is important for
SAP to generate a GAF. The GAF is a file containing a standard set of accounting information set out.
Businesses should be given the flexibility of selecting the time period for which the GAF is required.
GAF should be a pure collection of data either in flat file format using “pipe” delimited text file format or
in XML 1.0 file format. WSM has chosen to use the XML format. [As per email from Terri dated 26th
December]

FUNCTIONAL DESCRIPTION / DESIGN

The report will allow users to display the GAF report and output to the format specifically required by
RMCD in XML 1.0 format.

` 6 of 18
TRANSACTION VOLUME
The expected number of records to be displayed on this report is approximately 80,000 line items per
year for one company code.

FREQUENCY & TIMING

The report will be run on an ad hoc basis when requested by RMCD. It could be run on a monthly basis
or yearly basis.

DEPENDENCIES
All journals have been posted for the particular period.

AUTHORIZATION REQUIREMENTS

Authorization check on company code (F_BKPF_BUK).

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

REPORT, ETC)

` 7 of 18
3. 1. Object Specific Design
3.1 1.1 Reporting (operational and analytical)

Reporting
WRICE Description Report Type Data Elements Relevant KPI Owner
F-ID (ABAP, BI,
BOBJ)
XX-xx- ABAP
R001

Selection Criteria

Table/ Field Format Defau Table Select Mandator Field

Structur Name lt Value/ Option or y or Labels
e Name Value Checkbox/ Paramet Optional
Radio er
Button/
Radio
Button
Group
BKPF- Company Select Mandator Company
BUKRS code Option y code
BKPF- Fiscal Year Select Mandator
GJAHR Option y Fiscal Year
BKPF- Period Select Mandator
MONAT Option y
(From
and To) Period
BSEG- Tax Code Select Optional
MWSK Option
Z (Multiple) Tax Code
BSEG- GL Select Optional
HKONT Account Option
(Multiple) GL Account
BKPF- Document Select Optional
BELNR Number Option Document
(Multiple) Number
Output to Checkbox Optional Output to
file file
Server Optional File Path
Path

` 8 of 18
Functional Design, Validation and Variants
There are two outputs in this program:
1) To output the GAF requirement in an ALV format report
2) To output the GAF in XML format as per the guidelines given by RMCD

GAF report in ALV format

These report consist of four portions:

1) Company code data
2) Supplier data
3) Customer data
4) GL balances and transaction data

Company code data

Business Name
- Map to table T001 from company code selection parameter. Get field ADRNR from T001 and
map to ADRC. Concatenate field NAME1 and NAME2

Business RN
- Map to table T001 from company code selection parameter. Get field ADRNR from T001 and
map to ADRC. Get NAME4.

GST No
- Map to table T001 from company code selection parameter. Get T001-STCEG.

Period Start
- The first day of the calendar month from the Period From selection parameter

Period End
- The last day of the calendar month from the Period To selection parameter

GAF Creation Date

- System date when the report was generated

Product Version
- CVERS_TXT-STEXT

GAF version
- System automatically assigned (sequential number plus 1) when the option output to file is
selected.
- Format: MYXXYYYY9999; XX=company code, YYYY=Year, 9999=sequential number. (The last
number will be stored in an internal table)

Supplier data
- Basically is to list all open and closed AP line items that have a posting date within the period
range and fiscal year. (BSIK and BSAK posting date BUDAT within the period specified).
- Only report line items that fulfil the following additional criteria:
a) BSEG-KOART = S or A
b) BSEG-HKONT not equal to 47900910 or 47900920

` 9 of 18
 Supplier Name
- Map BSIK-LIFNR and BSAK-LIFNR to LFA1-LIFNR. Concatenate field LFA1-NAME1 and
NAME2.

Supplier BRN
- Map BSIK-LIFNR and BSAK-LIFNR to LFA1-LIFNR. Get LFA1-NAME4.

Invoice Date
- BLDAT from BSIK and BSAK

Invoice No
- XBLNR from BSIK and BSAK

Import Declaration Number

- Map BSIK-BELNR & GJAHR and BSAK-BELNR & GJAHR to BKPF-BELNR & GJAHR. Get
BKPF-BKTXT.

Line No
- Concatenate “Supplier name” and “Invoice No”. Assign 1 to the first line item and 2 to the
second line item found and so forth.

Product Description
- BSEG-SGTXT

Purchase Value MYR

- BSEG-DMBTR

GST Value MYR

- Use function module GET_TAX_PERCENTAGE (ALAND=MY, DATAB=initial, MWSKZ=BSEG-
MWSKZ, TXJCD=TAXMY. Get the percentage and multiply with BSEG-DMBTR.

Tax Code
- BSEG-MWSKZ

FCY Code
- BKPF-WAERS (If MYR, change to blank)

Purchase FCY
- BSEG-WRBTR (leave blank if WAERS is MYR)

GST FCY
- From value GST Value MYR, divide BKPF-KURSF.

Customer data
- Basically is to list all open and closed AR line items that have a posting date within the period
range and fiscal year. (BSID and BSAD posting date BUDAT within the period specified).
- Only report line items that fulfil the following additional criteria:
c) BSEG-KOART = S or A
d) BSEG-HKONT not equal to 47900910 or 47900920

Customer Name
- Map BSID-KUNNR and BSAD-KUNNR to KNA1-KUNNR. Concatenate field KNA1-NAME1 and

` 10 of 18
 NAME2.

Customer BRN
- Map BSID-KUNNR and BSAD-KUNNR to KNA1-KUNNR. Get field KNA1-NAME4.

Invoice Date
- BLDAT from BSID and BSAD

Invoice No
- XBLNR from BSID and BSAD

Line No
- Concatenate “Customer name” and “Invoice No”. Assign 1 to the first line item and 2 to the
second line item found and so forth.

Product Description
- BSEG-SGTXT

Supply Value MYR

- BSEG-DMBTR

GST Value MYR

- Use function module GET_TAX_PERCENTAGE (ALAND=MY, DATAB=initial, MWSKZ=BSEG-
MWSKZ, TXJCD=TAXMY. Get the percentage and multiply with BSEG-DMBTR.

Tax Code
- BSEG-MWSKZ

Country
- Map BSID-LIFNR and BSAD-LIFNR to ADRC. Get LAND1 and map to T005T-LANDX50

FCY Code
- BKPF-WAERS (If MYR, change to blank)

Purchase FCY
- BSEG-WRBTR (leave blank if WAERS is MYR)

GST FCY
- From value GST Value MYR, divide BKPF-KURSF.

GL Balance and Transaction Data

- This section is to list all the GL accounts (selection parameter) opening balance and line
items. List all GL line items (FAGLFLEXA table) that have a posting date (BUDAT) within
the company code, period range and fiscal year. BKPF posting date (BUDAT) within the
period specified. FAGLFLEXA-RLDNR always = 0L.

Transaction Date
- FAGLFLEXA-BUDAT

Account ID
- FAGLFLEXA-RACCT

` 11 of 18
 Account Name
- Map FAGLFLEXA-RACCT to table SKAT-SAKNR and Language=EN. Get SKAT-TXT50.

Transaction Description
- Map FAGLFLEXA-BELNR and BUZEI to BSEG to get BSEG-SGTXT

Name
- From FAGLFLEXA-DOCNR, RBUKRS and RYEAR, map to BSEG-BELNR, BUKRS and
GJAHR. For those records found, search for line item with BSEG-KOART=K or D. For K,
map BSEG-LIFNR to LFA1-LIFNR. Concatenate LFA1-NAME1 and NAME2. For D, map
BSEG-KUNNR to KNA1-KUNNR. Concatenate KNA1-NAME1 and NAME2.

Transaction ID
- FAGLFLEXA-DOCNR

Source Document ID
- FAGLFLEXA-DOCNR

Source Type
- From FAGLFLEXA-DOCNR, RBUKRS and RYEAR, map to BSEG-BELNR, BUKRS and
GJAHR. For those records found, search for line item with BSEG-KOART=K or D. For K,
then AP, for D then AR.

Debit
- FAGLFLEXA-HSL (if amount >0)

Credit
- FAGLFLEXA-HSL (if amount <0)

Balance
- To determine the opening period, get the “From Period” and minus 1. E.g. From Period is 1,
then opening period is 0. If opening period is 0, add up all amounts in FAGLFLEXT-HSLVT
for that particular GL, year and company code. If the opening period is 2, then add up all
amount for period 0 (HSLVT), period 1 (HSL01) and period 2 (HSL02).

Report Output

Output Method

Example:
The report output in ALV format.

Should the “Output to File is tick”, an XML file will be generated and saved to the server file path as
follows:

\\kul-008\Common\data\InterFile\UAT\SAP_GST\GDE

The XML file naming convention:

CCCC.YYYY.MM.VVVV (Company Code.Year.Month.Version Number)
Example would be MY01.2014.05.0001
Version Number is from the internal table field name “GAF Version” and reset to 0000
every year

` 12 of 18
 Month is the month in which the report is generated

Main Heading

GST Audit File

Sub Heading

Not Applicable.

LAYOUT
Table/Structure Field Format Default Value Column Name Translation Rule
Name Name (i.e.
decimal
places)

DRILLDOWN REQUIREMENTS

Not Applicable

TOTALING

The totaling requirement is mentioned in the GAF filed mapping file.

SORTING

Users will be able to sort on any column. Default sort sequence will be by posting date.

PAGE BREAK

Not Applicable

ERROR HANDLING

` 13 of 18
 Typical errors include: No data found for given selection criteria.

3.2 Interfaces

Interface

WRIC Description Interface Applications Data Elements Frequency / Owner

EF-ID Method Volumes

XX-xx- GAF File File download SAP-FI Ad-hoc/

I001 and Upload 80,000 per
company per
year

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

When the “Output file” parameter is selected, the program generates an XML file and saves in a server
path. The file will be submitted to RMCD for audit purpose when required.

File Specifics

GAF SHOULD BE A PURE COLLECTION OF DATA EITHER IN FLAT FILE FORMAT USING “PIPE”
DELIMITED TEXT FILE FORMAT OR IN XML FILE FORMAT. XML 1.0 FILE FORMAT IS THE
CHOSEN OUTPUT FORMAT.

Mapping SAP Fields to Source / Target

The fields’ specification is provided by RMCD guidelines attached in 2.2 above. The fields mapping is
also provided in the attachment in section 3.1.

` 14 of 18
 Reconciliation Procedures & Audit Requirements
Reporting
To reconcile with standard transactions and reports, e.g., FS10N, FBL1N, FBL3N and FBL5N.

Approach

Metrics

Error Handling

3.3 1.1 Data Conversion / Historical Data

Conversions

WWRICE Conversion Source Conversion Conversion # of Objects Owner

F-ID Object Activities Method (manual to be
(e.g. / automated) converted
cleansing)

XX-xx-
C001
1Mapping SAP Fields to Source / Target

Not Applicable

Reconciliation Procedures & Audit Requirements

Reporting

Approach

Metrics

Error Handling

` 15 of 18
 3.4 1.2 Enhancements

enhancements

WRIC Description Data Object Functional Alternative SAP Reason Owner

EF-ID (Sales Order) Gap Standard

XX-xx-
E001

Functional Design / Flow, Validation and Variants

Flow

Design

3.5 1.3 Output (e.g. forms)

Output

WRIC Description Data Object Output Type Frequency Volumes Owner

EF-ID (Sales (Form, EDI, etc.)
Order)
XX-
xx-
O001

Process Flow Diagram

Not Applicable

Form Layout

N NA

Printer Requirements

` 16 of 18
 NA

Legal Requirements

NA

Existing Sample Forms

NA

3.6 1.4 Workflow

Workflow

WRIC Description Business / Data Object Engaged Parties Owner

EF-ID (Sales Order)
XX-
xx-
W001

Process Flow Diagram

NA

3.7
Trigger Events
Transactions and Batch Programs that trigger the workflow

Start Conditions

Rules and Determination

Standard Rules
Latest End, Latest Start

` 17 of 18
4. 2. Test Conditions
Business Test Conditions (To be furnished by the Functional Consultant)

Scenario # Input Selection Criteria Expected Result

1 Select Period 1 to 12 Full year report generated

2 Select Period 3 to 12 Opening balances of GL accounts are as of

end February.

3 Select Output File parameter An XML file is generated and saved in the
server folder.

` 18 of 18