Integrated Business

System (IBS)

GT FI EFNS for
CSV Accounting
Document Upload

KPMG International

November
2010

Revision History and Approval

Revision history
Version
0.1

Author

Date

Revision/CR #

28 Sept 2009

Initial Version - Updates to remove Excel

wording, use of test mode and changes to
the currency formatting.

0.2

Neta West

15 Oct 2010

John Hughes

09 Nov 2010

GT General Release Change Updates for

minor formatting changes, clarifications,
profit center number changes
Final Version

1.0

Sara Neale

Approval
Version
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0

Name
John Hughes
Debasish Jana
Bryan Dobes
Neta West
Praveen Kumar Singh
Peter Walker
QCB
Ian Stutt

Date Reviewed
09 Nov 2010
08 Nov 2010
09 Nov 2010
10 Nov 2010
08 Nov 2010
08 Dec 2010
14 Dec 2010

311129709
Page 1

Contents
1

Introduction

1.1

Purpose of the document

1.2

Request Overview

Overview

2.1

Business Driver

2.2

Key business requirements

2.3

Assumptions

2.4

High level Process overview

2.4.1

Process for Posting Accounting Documents via CSV Upload 7

2.5

Alternative Solutions evaluated

Enhancement Definition Details

10

3.1

Detailed Processing Logic

10

3.1.1

Processing Logic 10

3.1.1.1

Validation

3.1.2

Program Process Rule Information10

3.2

10

Customized Screens

11

3.2.1

Selection Screen Layout

3.2.2

Technical Details 12

3.2.3

Display Screen Layout 12

3.2.4

Technical Details 13

3.2.5

Permissible Document Types Maintenance Screen Layout

3.2.6

Technical Details 14

3.3

11

Custom Table Definition

15

3.3.1

Custom Tables

3.3.1.1

Permissible Document Types15

3.3.2

Internal Tables

15

3.3.3

Standard Tables

18

3.4

14

15

Exception Handling Rules

19
311129709
Page 2

3.5

Special Requirements

20

3.6

Dependencies

21

3.6.1

Data Dependencies

21

3.6.2

System Dependencies 22

3.6.3

Process Dependencies 22

3.7

Constraints

22

3.8

Workflow Requirements

22

3.8.1

Workflow Tasks/Notifications 22

3.8.2

Thresholds 22

Scheduling Requirements

23

Testing Requirements

24

5.1

Test Specification

24

5.2

Functional Test Scenarios

24

5.3

Test Data & Other Needs

25

5.4

Test System & Environment

26

5.4.1

Unit Test Environment 26

5.4.2

Quality Test Environment

5.4.3

Pre-Production Test Environment 26

5.4.4

System Landscape Testing

5.4.5

Stress Testing Requirement 27

5.4.6

Regression Testing Requirement 27

26
27

Globalization

28

6.1

Internationalization

28

6.1.1

Currency Format 28

6.1.2

Date Formats

6.1.3

Language

6.1.3.1

Data

6.1.3.2

Messages

6.1.3.3

User-Determined Text 28

28

28

28
28

311129709
Page 3

6.1.4

Configuration Requirements 28

6.1.5

User Interface Elements

6.1.5.1

Window Titles

6.1.5.2

Titles

6.1.5.3

Button Texts 29

6.1.5.4

Labels 29

6.1.5.5

Captions (comments/instructions/texts) 29

6.1.5.6

Tool Tips

6.1.5.7

Menus 29

6.1.5.8

Roadmap Steps

6.1.5.9

Links

6.1.5.10

Tab Labels

6.1.5.11

Table Column Labels

6.1.5.12

Field Label Texts 30

28

29

29

29
29

29
29
30

Audit Requirements/Integrity Controls/Security

31

7.1

Audit Requirements/Integrity Controls

31

7.2

Transaction Codes

31

7.3

Security/Authorization Requirements

32

7.3.1

Authorization Group

7.3.2

Custom Authorization Check 33

7.3.2.1

Requirements

33

33

Appendix

34

311129709
Page 4

1
1.1

Introduction

Purpose of the document

The purpose of this document is to document any SAP code modifications or additional processing logic
requirements to further enhance the standard SAP delivered functionality. This document forms the
basis of the Technical Specification and the development work to be performed by the development
team.
The purpose of this program is to upload and post accounting journals into SAP via a CSV spreadsheet.
The trigger for this program is the need to book accounting journals for the accounting period. This is
able to be used throughout the month and as part of the month end process.
This program will create accounting documents based on the data uploaded from the CSV file. This
CSV upload program is intended to be used for accounting journals only. The input CSV file will contain
data for accounting journals only.
The CSV upload program will post accounting journals through a Batch Data Communication (BDC)
session method. This program will create a BDC session. The BDC session will be created by calling
standard the appropriate standard function modules to park or post the accounting documents.
This upload program will first upload the CSV file and will display the data in an Advanced List Viewer
(ALV) display. The user can then review the data of the CSV file. If the user finds everything acceptable,
then they can click the process button to create a BDC session for the given data.
Once the BDC session is created the program will display the session name which is created. The user
can click on process session to go to view the batch session directly and there he can select his BDC
session which is unprocessed and then click on process button to process the session.
This program will leverage a custom table which will be used to control which document types will post as
a result of this enhancement. Member Firms will be able to create custom document types to post with
this enhancement.

1.2

Request Overview
Scenario ID

F11

Scenario Title

Financial Accounting

Process ID

F1125

Process Title

CSV Journal Upload Process

Development
Specification ID

RICEFW_FI_0002

Name of
Enhancement

Journal Upload by batch program

Brief Description:

Requesting Team
Type

The purpose of this program is to provide a process to upload and post

accounting journals into SAP via a CSV spreadsheet.

Finance

Function Exit / User Exit

Routines

SAP Code
Modification

Custom Program/Transaction
This is custom program which will have an associated custom
transaction.
Other_________________
Data latency

Real-time

Batch

On-demand

Frequency

Annually

Quarterly

Monthly

Weekly

Daily

Other

R/3

CRM

APO

EBP

BI

SEM

Systems Impacted

Other_________

Modules Impacted

FI

CO

SD

MM

PP

QM

BW

SEM

Other_________
Complexity

High

Medium

Low

Spec Created on

10/15/2010

Date required by

11/15/2010

Created by

Neta West

Phone:

201-505-2681

Functional Analyst

John Hughes

Phone:

201-505-2262

Technical Analyst

To be defined

Phone:

Business Owner

Peter Walker

Phone:

+44 1923 214530

2
2.1

Overview

Business Driver
To enable the business to:

2.2

Post the large number of accounting journals within the system by the business as part of the
period end activities

Create large journals and then efficiently process and post them

Feel comfortable using an CSV upload function to process accounting journals

Key business requirements

The following business requirements have been identified for this enhancement:

The custom validations will be invoked on the FI line item.

All other validations and substitutions will be invoked for the Company Code at the header or FI
line item.

Dates can be entered in the template using either . or /.

Only predefined document types can be used to post via CSV. These document types will be
custom.

The business is responsible for the data on each posting. If an error occurs at the time of
processing and this processing is carried out by a user other than the business then the
correction is required by business.

The postings of the journals will be able to be parked and or parked and then posted. Radio
buttons will exist on the selection screen to enable this. Where the parked button is selected
the journal postings will be parked only. This will require the relevant authorized user to log onto
the system and then review and post the parked entries.
Where the Post button is selected the program will post the journals. No subsequent action will
be required from users in the system.

The journal upload will be able to handle financial postings to assets.

It will be possible to create cross company postings.

The following business rules have been identified for this enhancement:

This upload process will support standard SAP processing of multiple currency transactions.

Accounting documents must not exceed 999 lines as this is the limitation on BSEG accounting
document line items.

The execution of the transaction will post as many journals as specified on the CSV spreadsheet.

The CSV upload program must comply with the standard SAP delivered and configured
validations. E.g. Company Code settings master data settings and document posting rules.

2.3

The CSV upload program must comply with the custom validations developed for the Member
Firm.

The CSV upload program will process the journals via batch processing (Transaction SM35).

The CSV template upload functionality is designed to be used for the following kinds of financial
journal postings:
o

Accounts Payable journals

General ledger journals

Accrual journals

Multi vendor invoices.

Accounts Receivable journals

Reversals of all documents

Fixed asset postings

Where expenses are posted to engagements, and no Engagement Phase is added, the program
will default Phase 1 on the engagement as the phase. Note: Phases are required to be entered
when posting financial entries to the Engagement.

Postings will not be able to be made directly to profitability segments.

The program will check to ensure that postings are made only to valid Company Codes
consistent with the users authorizations.

The program will only process a CSV file if the user has authorizations for all the Company
Codes and document types specified on the spreadsheet.

Assumptions
The following assumptions have been identified for this enhancement:

No Postings to CO-PA will be made using the CSV journal upload functionality. The reason is that
all CO-PA relevant postings are carried out with an associated workflow for approval and are not
carried out by finance support department.

Vendor invoices processed by the business and forwarded/received by the Finance department
are deemed pre-approved by the business.

Pre and post audit and internal control processes will be manual and are not required to be built
into the CSV upload.

Users who have access to the CSV upload will require access to FB01 in order to process the
batch job.

Relevant controls for SOX and audit compliance will be considered within the design for the AR
and AP processors.

The program will handle the users logon language and display all screens in the appropriate
language.

Users date (DD/MM/YYYY or MM/DD/YYYY) and number settings (how the units are separated)
will be used by the program. The user should maintain the spreadsheet consistent with their own
user settings for the date. (See user settings SU01)

This CSV journal upload allow to enter user defined exchange rate which different the default
exchange rate maintained in the system.

The CSV template will be consistent with the internal table structure and the structure of the file
when it is uploaded to the upload screen.

The program will be design in line with the internationalization requirements for the Global
Template. A separate document will contain the internationalization requirements for language,
currencies and date formats.

The program will be designed in line with the error handling requirements for the Global
Template. A separate document will contain the error handling requirements for the Global
Template.

The user who processes the batch job will be stamped as the user on the financial document
posting.

The transaction code is stamped in the header of the financial document posting in the field
TCODE. This will enable the user to understand what process created the financial posting.

2.4

High level Process overview

2.4.1

Process for Posting Accounting Documents via CSV Upload

2.5

Alternative Solutions evaluated

The following alternatives were evaluated as part of the creation of this functional specification:
No.

Alternatives

Evaluation

Reason for Rejection (Cost, Timeline, Change

Impact, etc.)

Usage of the existing CSV

journal upload functionality in
the base solution

Pros

Existing developed and tested functionality

No development and testing effort required

Cons

In the base solution functionality, all validation

is done in CSV via macro before uploading
the journal into system.
Coding rule will not be used in IBS Global
template.

Upload using IDoc or LSMW

solution

Pros

It is a similar tool compared with the BDC

solution. This handles the upload of data
from an CSV sheet to the SAP system,
Used generally to upload master data in
multiple tables.

Third party tool

Cons

A complex solution and difficult for further

enhancements and maintenance

Pros

Plug and play solution for CSV upload to SAP.

Maintenance can be carried out by users not
by developers.

Cons

Additional licensing and maintenance cost.

New learning curve for user to understand
specific software functionality.

3
3.1

Enhancement Definition Details

Detailed Processing Logic

3.1.1

Processing Logic

Defined below is the program logic for the CSV journal upload program.
This logic will form the basis for the program code, which will be defined as part of the technical
specification.
1. A custom program will upload the input CSV file into an internal table. The input file available
would be an MS CSV spreadsheet. The records from the uploaded file will be then split as per
the fields given in the custom document type table and will be appended into the internal tab.
2. The data in the internal table is checked with validation rules and displayed as an ALV grid.
3. The user then checks if the contents of file uploaded is correct or not. As part of this check
mandatory fields are evaluated and an information message is displayed of the fields that have
not been populated on the spreadsheet.
4. The standard function program will use this file and will generate the BDC session. After
populating this information will be transferred to the output file.
5. If the Park button is selected on the selection screen then the accounting journals that are
passed to the standard function program and will be parked only.
6. Else if the Post button is selected on the selection screen then the accounting journals that
are passed to the standard function program and will be posted.

3.1.1.1

Validation

Upon initialization of the program, the processing type (G/L, A/P or A/R) is determined based on the
calling transaction code.
This will be used later to determine that the document type(s) used is (are) legitimate and appropriate
use of the custom document check table.

3.1.2

Program Process Rule Information

The custom validations will be invoked on the FI line item.

All other validations and substitutions will be invoked for the Company Code at the header or FI
line item.

Amounts can be entered in the template using the period (.) as the decimal separator only in the
CSV format. The users number notation will be applied when the values are read from the CSV
file to the internal table.

Dates can be entered in the template using either . or /. The date must be entered on the
template in the format MM DD YYYY.

Access to SM35 must be controlled so that the user only views their batch jobs.

The AP users will access the CSV (.CSV) upload via a different transaction.
assigned to the relevant AP roles only.

A check in the program will be included to ensure that the AP users can only create invoices with
the relevant AP document types.

For AP the CSV spreadsheet should be returned to the responsible area for correction as the
sending party is the one who has responsibility to ensure the data is correct. This is a manual
(offline) step required in the process.

Sundry cost recovery AR invoices will be deemed approved by the business for entry into SAP.

Financial Accounting group users will access the CSV upload via transaction GL = ZFI_GL_UPL.
They will have access to the documents types for GL only. I.e. those document types specified
in the custom Z table grouped by processing type S.

AR users will access the CSV upload via transaction, AR = ZFI_AR_UPL. They will have access
to the documents types for AR only. I.e. those document types specified in the custom Z table
grouped by processing type D.

AP users will access the CSV upload via transaction AP = ZFI_AP_UPL. They will have access
to the documents types for AP only. I.e. those document types specified in grouped by
processing type K.

The ALV display has been updated such that when the user uploads the CSV spreadsheet to the
screen, the accounting header and line item are highlighted in different values to distinguish the
difference.

CSV Template for CSV journal upload :

This will be

Excel Accounting
Document Upload.xls

3.2

Customized Screens
A selection screen is required for this enhancement in order to execute the program.

3.2.1

Selection Screen Layout

This screen is used to enter the name of the spreadsheet to upload and the name of the batch input
session to create.

3.2.2

Technical Details

Following are the technical details of the selection screen.

Seq.
No.

Parameter
Name

Parameter
Description

Parameter

Data Type

Default

S_BURKS

Company
Code

Select
Option

BBSEGBURKS

N/A

4 Char

Mandatory

P_IFILE

Input File path

Parameter

RLGRAPFILENAME

N/A

XX Char

Mandatory

P_BNAME

Batch input
session name

Parameter

BGR00GROUP

CSV_

12 Char

Mandatory

P_PARK

Park
Document

Radio Button

Char

Yes

1 Char

N/A

P_POST

Post
Document

Radio Button

Char

N/A

1 Char

N/A

Type

Data
Length

UPLOAD

Status

3.2.3

Display Screen Layout

The following screen is then displayed after the execution of the spreadsheet upload. Here the data is
able to be reviewed.

3.2.4

Technical Details

The layout of this table is based on the custom table structure of table for the CSV upload structure. The
table name will be defined in the technical specification document.

3.2.5

Permissible Document Types Maintenance Screen Layout

One custom table will be developed which will contain the document types defined by function that are
able to be used within the program for CSV upload of accounting documents. In order to use a
document type for a function it must exist in this table first along with the function for which the document
should be used. E.g. AR = Processing type (D) and document type (DA).
It is expected that the custom table will need to be maintained over time as the document types for GL,
AR and AP expand for usage with the CSV upload.
The table is able to be maintained via a customized transaction. The table name will be defined in the
technical specification document.
Data Element

Data Type

Data
Length

Status

Processing Type

Char

Mandatory

Document Type

Char

Mandatory

3.2.6

Technical Details

The layout of this table is based on the custom table structure of table for Permissible Document Types
Maintenance screen.

3.3

Custom Table Definition

The following custom and standard tables are required for this enhancement.

3.3.1

Custom Tables

3.3.1.1

Permissible Document Types

The table will be treated as master data table will be maintainable via a custom transaction code.
The structure of table for holding document types:
Data

Data Element

Data Type

MANDT

Char

Mandatory

ZPROCTYPE
(Processing
Type)

Char

Mandatory

BLART
(Document Type)

Char

Mandatory

Length

Status

(Client)

3.3.2

Key/Non Key
Field
Key

Key

Key

Internal Tables

The user will populate a template spreadsheet which will be used to create the journal in SAP. The
template will need to be taken into an internal table in order to be validated and processed.
The user will create the header and appropriate line items for the journal, AR or AP invoice within the
CSV spreadsheet. Only one header will be required per accounting document (GL, AP or AR Invoice).
The user can create more than one accounting document on the CSV spreadsheet in order to post into
SAP. The header record distinguishes the next document within the CSV structure.
The user will have the ability to download the template upload structure from the ALV screen. This will
ensure that any changes made to the structure are made available to the user so that the templates are
consistent with the program and errors in upload are reduced.

The structure of the internal table will be as follows:

Header
Field Name

Technical
Name

Length

Data type

Status

Identification

Character

Document Date (batch input)

BLDAT

DATS

Mandatory

Document type

BLART

CHAR

Mandatory

Company Code

BUKRS

CHAR

Mandatory

Posting Date (batch input)

BUDAT

DATS

Mandatory

Exchange Rate

KURSF

DEC

Optional

Translation Date

WWERT

DATS

Optional

Currency Key

WAERS

CUKY

Optional

Calculate tax

XMWST

CHAR

Optional

Reason for Reversal

STGRD

CHAR

Optional

Planned Date for the Reverse Posting

STODT

DATS

Optional

Reference Document Number

XBLNR

16

CHAR

Optional

Document Header Text

BKTXT

25

CHAR

Optional

Ledger Group

LDGRP

CHAR

Optional

Data type

Status

Line Item
Field Name

Technical
Name

Length

Posting Key for the Next Line Item

NEWBS

CHAR

Mandatory

Company Code for the Next Line Item

NEWBK

CHAR

Optional

Account or Match code for the Next

Line Item

NEWKO

17

CHAR

Optional

Field Name

Technical
Name

Special G/L Indicator for the Next Line

Item

NEWUM

Main Asset Number

Length

Data type

Status
Optional

CHAR

ANLN1

12

CHAR

Optional

Asset transaction type

BEWAR

CHAR

Optional

Asset Value Date

SDATE

DATS

Optional

Asset Sub Number

ANLN2

CHAR

Optional

Amount in document currency (batch

input field)

WRBTR

16

CHAR

Sales Tax Code

MWSKZ

CHAR

Optional

Tax Jurisdiction Code

TXJCD

CHAR

Optional

Cost Center

KOSTL

10

CHAR

Optional

Profit Center

PRCTR

10

CHAR

Optional

Order Number

AUFNR

12

CHAR

Optional

Sales Document

VBEL2

10

CHAR

Optional

Sales Document Line Item

POSN2

CHAR

Optional

Personnel Number

PERNR

NUMC

Optional

Mandatory

Personnel Number

Optional

(*Engagement Partner)

ZZPERNR

NUMC

Value Date

VALUT

DATS

Optional

Payment Terms

ZTERM

CHAR

Optional

Payment Methods

ZLSCH

CHAR

Optional

Baseline Date

ZFBDT

CHAR

Optional

Discount Base

SKFBT

16

CHAR

Optional

Payment Block

ZLSPR

CHAR

Optional

Assignment

ZUONR

18

CHAR

Optional

Field Name

Technical
Name

Item Text

SGTXT

Length
50

Data type

Status

CHAR

Optional

* This is a field required to support the Sundry Billing Scenario.

3.3.3

Standard Tables

The following standard tables will be used within this program:

Table Name

Data Field

BBKPF

Refer to Header fields of Internal Table

BBSEG

Refer to Line Items of Internal Table

FAGLFLEXA

Relevant data fields will be updated by standard

program RFBIBL00 at the time of batch
processing.

COEP

Relevant data fields will be updated by standard

program RFBIBL00 at the time of batch
processing.

3.4

Exception Handling Rules

The following exception handling rules have been identified for this enhancement:

Common include function module will be defined for all exception messages within Finance. The
program will call the function modules to get the correct exception messages.

Upload
Error checks are upon the upload of the CSV file to the ALV display for expense accounts. These are
warnings only and should be correct in the source file OR within the screen.
Creation of the Batch Job
If mandatory fields have not been populated, header or line item data is not correct, or data values are
not correct errors will be identified upon creation of the batch job.
Processing of the Batch Job
Data errors will be identified via standard SAP error handling in transaction SM35 The user will be able
to view the error and attempted screen entries. These can then be corrected in the source file before
uploading again.
Message:
The following error handling messages will be invoked during the processing of the batch.
These are handled by standard SAP program (RFBIBL00) and will not be defined by the custom
program.

Error Message Description

Message Type

ABAP runtime error This message will be invoked

when the spreadsheet is not formatted correctly. The
spreadsheet must be formatted in line with
requirements.

Error

G/L account does not exist This message will be

invoked when the G/L account is invalid or does not
follow the 8-digit format.

Error

Account is blocked for posting This message will be

invoked when the G/L account is blocked.

Error

Cost Center does not exist This message will be

invoked when the Cost Center is invalid (locked) or
does not follow the 8-digit format required. OR Cost

Error

Error Message Description

Message Type

Indicator is incorrect.

3.5

Profit Center does not exist - This message will be

invoked when the Profit Center is invalid (locked) or
does not follow the 8-digit format required. OR
Revenue Indicator is incorrect.

Error

Company Code is not defined This message will be

invoked when the Company Code is invalid or does not
in line with the 4-digit format.

Error

Document can only be posted if it balances to zero.

Error

The total debits do not equal the total credits on the

spreadsheet.

Error

Special Requirements
User must complete the CSV sheet as per template completion guidelines. This will be defined in
appropriate user guide.
The following help information will be provided on the initial selection screen for the CSV Accounting
Document Upload, so that users will have custom help notes available. This will provide guidance and
an overview of the program for users.
Purpose
The purpose of this program is to upload and post accounting journals into SAP via a CSV spreadsheet.
The trigger for this program is the need to book accounting journals for the accounting period. This is
able to be used throughout the month and as part of the month end process.
Integration
N/A
Prerequisites
N/A
Features
Selection
The user is able to select the following details:
File Name The user selects where the CSV file is saved to upload into the program.

Parking Document The user selects this radio button if they want to park the accounting
documents in the system. A parked document is not updated to the general ledger.
Posting Document The user selects this radio button if they want to post the accounting
documents in the system. A posted document is updated in the general ledger.
Standard Variants
N/A
Output
As a result of successfully processing this program accounting journals will be posted into the
system. These could be in the format of GL journals, AP invoices, General AR invoices or
accounting migration postings.
Activities
This program will create accounting documents based on the data uploaded from the CSV file. This
CSV upload program is intended to be used for accounting journals only. The input CSV file will contain
data for accounting journals only.
The CSV upload program will post accounting journals through a Batch Data Communication (BDC)
session method. This program will create a BDC session which can be processed manually by the user
by executing transaction 'SM35'.
The BDC session will be created by calling standard program
RFBIBL00.
This upload program will first upload the CSV file and will display the data in an Advanced List Viewer
(ALV) display. The user can then review the data of the CSV file. If the user finds everything fine then
he/she can click the process button to create a BDC session for the given data.
Once the BDC session is created the program will display the session name which is created. The user
can click on process session to go to view the batch session directly and there he can select his BDC
session which is unprocessed and then click on process button to process the session.
This program will leverage a custom table which will be used to control which document types will post as
a result of this enhancement. Member Firms will be able to create custom document types to post with
this enhancement.
Example
N/A

3.6

Dependencies
The following dependencies have been identified for this enhancement:

3.6.1

Data Dependencies

There is a data dependency on the custom table with the document types. This CSV upload program
with this custom enhancement will only allow user to upload and post journals on pre-defined document
types as defined in the custom table.

3.6.2

System Dependencies

No system dependencies have been identified.

3.6.3

Process Dependencies

No process dependencies have been identified.

3.7

Constraints
No limitations or constrains have been identified.

3.8

Workflow Requirements
No workflow requirements have been identified.

3.8.1 Workflow Tasks/Notifications

No Workflow Task/Notifications have been identified.
Ms
g
Nbr

Proces
s

Work
List Type

Action
Reqd.

Summarize
d text
required

Detailed
text
required

Triggered
from

3.8.2 Thresholds
Thresholds are not relevant for this enhancement.
Scenario

Function

Threshold Requirements:
Engagement code
realization rate & function

Task Recipient

Who
receive
s it

Who
else
can see
it

Scheduling Requirements

The following scheduling requirements have been identified for this enhancement:

Job Scheduling Information

This process will be scheduled as required by each member firm.

NOTE: There will also be a manual transaction available to run the CSV journal upload process
on an as required basis.

Dependencies
No process dependencies have been identified.

Frequency
If scheduled, this process to be executed in line with the requirements of the individual Member Firm.

5
5.1

Testing Requirements

Test Specification
Refer to the attached test specification for unit tests for this enhancement:

Test Spec

5.2

Functional Test Scenarios

ID

Test Scenario
Using TCode ZFI_GL_UPL post
a general ledger accounting
entry with the following
scenarios:

Multiple general ledger

documents with different
document currencies

Post document to an Asset

Post accrual documents

Post reversal documents

Post with Post document

Post with Park document

Using TCode ZFI_AP_UPL post

a vendor invoice with the
following scenarios:

Post documents to multiple

vendors

Post with Park document

Post with Post document

Using TCode ZFI_AR_UPL post

a customer invoice with the
following scenarios:

Post documents to multiple

vendors

Post with Park document

Expected Results
An accounting journal is
created with adherence to the
standard and custom
validations.

An AP invoice is created with

adherence to the standard and
custom validations.

An AR invoice is created with

adherence to the standard and
custom validations.

Comments

ID

Post with Post

document

Test Scenario - Negative

Load incorrectly formatted CSV
upload file for:

GL journal

AP journal

AR journal

CSV upload file is created with

missing mandatory data for:

GL journal

AP journal

AR journal

CSV upload file is created with

incorrect data for:

5.3

GL journal

AP journal

AR journal

Expected Results
The ALV screen displays
upload errors prevent batch
creation(i.e. total dr/cr do not
agree, column missing, etc.)

Comments

In batch process log the batch

file is not created successfully.
Error messages are provided
in batch process log (i.e.
missing mandatory fields such
as cost center, general ledger
account)
In the batch process log the file
is not processed successfully.
Error messages are provided
in the batch process log (i.e.
vendor is blocked for posting,
company code is not defined,
etc.)

Test Data & Other Needs

Master Data

Company Code

Two Company Codes are required for testing this

enhancement

Client/Customer

At least one client should be maintained in that Company

Code for AR journal upload

VendorAt least one vendor should be maintained in that

Company Code for AP journal upload

GL Accounts

P&L and Balance sheet account should be maintained for

the Company Code chart of accounts including cross

company code automatic posting accounts

Fixed Assets

Transactional Data

5.4

At least one fix asset should exist

No existing transactional data is required for the CSV

journal upload process

Test System & Environment

5.4.1

Unit Test Environment

System

SAP Unit Test Client

Client

TBD

Test User/s
Portal

5.4.2

No specific roles will be used for unit testing.

MOSS Portal and EP for SAP

Quality Test Environment

System
Client
Test User/s

SAP Quality Test Client

TBD
General Ledger Manager
General Ledger Analyst
Accounts Receivable Manager
Accounts Receivable Analyst
Accounts Payable Manager
Accounts Payable Analyst

Portal

MOSS Portal and EP for SAP

5.4.3

Pre-Production Test Environment

System

SAP Pre-Production Test Client

Client

TBD

Test User/s

General Ledger Manager

General Ledger Analyst
Accounts Receivable Manager
Accounts Receivable Analyst
Accounts Payable Manager
Accounts Payable Analyst

Portal

5.4.4

MOSS Portal and EP for SAP

System Landscape Testing

This will be defined as part of the realization phase.

5.4.5

Stress Testing Requirement

This will be defined as part of the realization phase.

5.4.6

Regression Testing Requirement

This will be defined as part of the realization phase.

6
6.1

Globalization

Internationalization
6.1.1

Currency Format

Currency formats will be read from the users settings. There will be a subroutine in the program that will
read the settings and ensure that the currency format settings are presented to the user based on their
format.

6.1.2

Date Formats

Date formats will be read from the users settings. There will be a subroutine in the program that will read
the settings and ensure that the date settings are applied to the dates entered by the users on the CSV
spreadsheet.

6.1.3

Language

6.1.3.1

Data

The data elements contained in this custom table are referencing some standard data elements which
will be translated where required automatically.
There is one field which is referencing a custom data type. This will need to be translated.

6.1.3.2

Messages

Messages used within this enhancement are contained in the message class /KGO/FI_MSG_CLASS.
These messages will need to be translated.

6.1.3.3

User-Determined Text

There is no specific configuration associated with this enhancement.

6.1.4

Configuration Requirements

There is no specific configuration associated with this enhancement.

6.1.5

User Interface Elements

6.1.5.1

Window Titles

This is not relevant for this enhancement.

6.1.5.2

Titles

Custom text elements created for the screens associated with this enhancement are required to be
translated.

6.1.5.3

Button Texts

This is not relevant for this enhancement, as all buttons (Execute, Create Session and Process Session)
are standard and will be automatically translated.

6.1.5.4

Labels

This is not relevant for this enhancement.

6.1.5.5

Captions (comments/instructions/texts)

This is not relevant for this enhancement.

6.1.5.6

Tool Tips

This is not relevant for this enhancement.

6.1.5.7

Menus

This is not relevant for this enhancement.

6.1.5.8

Roadmap Steps

This is not relevant for this enhancement.

6.1.5.9

Links

This is not relevant for this enhancement.

6.1.5.10 Tab Labels

This is not relevant for this enhancement.

6.1.5.11 Table Column Labels

Standard table column labels are used and will be automatically translated. No custom translation is
required.

6.1.5.12 Field Label Texts

Standard field label texts are used and will be automatically translated. No custom translation is
required.

7
7.1

Audit Requirements/Integrity Controls/Security

Audit Requirements/Integrity Controls

The following audit requirements have been identified for this enhancement:

7.2

The file was approved by an employee that is included on an authorized master approver list.

Total amount in CSV file equals the amount processed in SAP.

If the total amount in the CSV file does not agree, then audit should follow through to ensure that
all rejects are handled and posted manually in the current accounting period. Hash totals must
agree within the accounting period.

Transaction Codes
The following transaction codes have been identified for this enhancement:
Transaction Code

Description

Purpose

ZFI_GL_UPL

CSV Upload for GL

To enable the posting of accounting journals

from a CSV spreadsheet.

ZFI_AR_UPL

CSV Upload for AR

To enable the posting of AR Documents

from a CSV spreadsheet.

ZFI_AP_UPL

CSV Upload for AP

To enable the posting of AP Documents from

a CSV spreadsheet.

ZFI_DOCTYPE_MNT

Maintain permissible
document types table

To enable the maintenance of the table for

permissible document types.

7.3

Security/Authorization Requirements
The following security requirements have been identified for this enhancement:
Role

Transaction

Authorization Considerations

General Ledger
Manager

ZFI_GL_UPL

General Ledger Manager will have the capability to

create the upload and processing of document types
from a CSV spreadsheet.

ZFI_DOCTYPE_MNT

The General Ledger Manager will have the ability to

maintain the table of permissible document types.
General Ledger
Analyst

ZFI_GL_UPL

General ledger Analyst will have the capability to

create the upload and processing of document types
from a CSV spreadsheet.

Accounts
Receivable
Manager

ZFI_AR_UPL

Accounts Receivable Manager will have the

capability to create the upload and processing of
document types from a CSV spreadsheet.

ZFI_DOCTYPE_MNT

The Accounts Receivable Manager will have the

ability to maintain the table of permissible document
types.
Accounts
Receivable
Analyst

ZFI_AR_UPL

Accounts Receivable Analyst will have the capability

to create the upload and processing of document
types from a CSV spreadsheet.

Accounts Payable
Manager

ZFI_AP_UPL

Accounts Payable Manager will have the capability to

create the upload and processing of document types
from a CSV spreadsheet.

ZFI_DOCTYPE_MNT

The Accounts Payable Manager will have the ability

to maintain the table of permissible document types.
Accounts Payable
Analyst

ZFI_AP_UPL

Accounts Payable Analyst will have the capability to

create the upload and processing of document types
from a CSV spreadsheet.

7.3.1

Authorization Group

The transaction code to maintain the custom table will be associated with the authorization group ZFIN.

7.3.2

Custom Authorization Check

The program must ensure that users are able to process the accounting journals based on the following:
1) For authorized Company Codes only
2) For authorized document types from the custom table only
This will be achieved through program logic that will be called upon processing of the program.

7.3.2.1

Requirements

Standard SAP authorization checks and objects should be used.

Values for the Company Code should be defined as a field on the selection screen

Values of document type and Company Code should be checked on the spreadsheet that is
being uploaded

Appendix

Related/Referenced Documents
Document Name

Version

Brief Description

KPMG

General Release

GT FI Blueprint F1121

IBS_BP_F1121_AccountsPayable

Accounts Payable

General Release

KPMG
IBS_BP_F1122_AccountsReceivable
KPMG IBS_BP_F1125_GeneralLedger

GT FI Blueprint F1122
Accounts Receivable

General Release

GT FI Blueprint F1125
General Ledger

General Release

KPMG
IBS_BP_F1126_FixedassetAccounting

GT FI Blueprint F1126 Fixed

asset Accounting

Attachments
Document Name
CVS Accounting Document

Version

Brief Description
CVS Accounting Document
Upload Template

Excel Accounting
Document Upload.xls

Upload

Testing Spec Template

Test Spec

Blank Testing Spec Template

 2010 KPMG International Cooperative (KPMG International), a Swiss entity. Member firms of the
KPMG network of independent firms are affiliated with KPMG International. KPMG International provides
no client services. No member firm has any authority to obligate or bind KPMG International or any other
member firm vis--vis third parties, nor does KPMG International have any such authority to obligate or
bind any member firm. All rights reserved.
The information contained herein is of a general nature and is not intended to address the circumstances
of any particular individual or entity. Although we endeavour to provide accurate and timely information,
there can be no guarantee that such information is accurate as of the date it is received or that it will
continue to be accurate in the future No one should act on such information without appropriate
professional advice after a thorough examination of the particular situation.