Solution Design Document

SPV Formation

MSRDC-VBSL Prepared by: itelligence, ABM

Page 1 of 27
 Solution Design Document

Document Control:

Title SPV Formation

Process Name SPV Formation & General Ledger

Sub Process Name  SPV Formation

 GL Master Data

 Transactions

Version:

Versio Date Created by Notes

n
ABM Knowledgeware Ltd in
V0 04.02.2020 Consortium with Itelligence India
Software Solutions Pvt. Ltd.

MSRDC-VBSL Prepared by: itelligence, ABM

Page 2 of 27
 Solution Design Document

Table of Content

1. Business Process Description and Objectives............................................................................5

2. Current Scenario As Is Process (BPD).......................................................................................6
3. Process Flow Chart.................................................................................................................... 7
4. SAP Process Steps.................................................................................................................... 8
5. Gap Analysis.............................................................................................................................. 9
6. Master Data Details.................................................................................................................... 9
7. Key Data Structure (KDS)........................................................................................................... 9
8. Data Migration requirements....................................................................................................25
9. Development Objects (RICEFW)..............................................................................................25
10. Roles and Authorizations..........................................................................................................25
11. Reports..................................................................................................................................... 26
12. Assumptions............................................................................................................................. 28

MSRDC-VBSL Prepared by: itelligence, ABM

Page 3 of 27
 Solution Design Document

Process ID
FI-01_SPV_GL_STRUCTURE
Process Description
VBSL SPV Formation & General Ledger

Abbreviations:

Initials Description
COA Chart of Accounts
GL Account General Ledger Account
SPV Special Purpose Vehicle
CAFO Chief Accounts and Finance Officer
CFO Chief Finance Officer
WBS Work Breakdown Structure

MSRDC-VBSL Prepared by: itelligence, ABM

Page 4 of 27
 Solution Design Document

1. Business Process Description and Objectives

This document describes the proposed (TO-BE) SPV Formation and GL Structure for MSRDC.
The process flow described in this document is based on the ‘AS-IS’ documents. The detailed
workflow of the TO-BE process is mentioned in ‘Process Flow’ Section of this document.

The content of this document forms the basis for system configuration and testing phase.

After a detailed department wise process evaluation viz Finance, Engineering, Legal, it is
observed that, VBSL will be created as one Special Purpose Vehicle (SPV) Entity and the same
will have the Enterprise Structure that replicates their operational structure for the business
operations in SAP.

SPV‘s Enterprise Structure is the basis on which the business processes are designed and
relevant master data objects are maintained in different modules of SAP. The To-Be processes
defined in this document can be adapted by following departments.

 Engineering (including Land Administration)

 Finance and Accounts
 Legal
 General Administration
 Commercial
 Secretarial

VBSL will have its Chart of Accounts (COA) adopted from its parent organization – MSRDC.
The COA contains the list of General Ledger accounts categorized into a broad classification of
Assets, Liabilities, Incomes and Expenses.

The SAP general ledger account is an account that is updated each time a user posts a
financial transaction in the SAP system. General Ledger Accounts constitute master data
in Financial Accounting.

From the reporting perspective, Assets and Liability Accounts will form part of the Balance
Sheet and Income & Expenses will be reflected in the Trial Balance in SAP.

MSRDC-VBSL Prepared by: itelligence, ABM

Page 5 of 27
 Solution Design Document

This document is prepared on the basis of best practices, which have been considered to
ensure a reliable accounting system with minimum governance of MSRDC
 Special periods in SAP will be defined for VBSL to effect the year-end adjustments during
the audit period.
 Accounting document numbers are internally generated with no dependence on the year.
In other words, the document number generated in one year will never be found in any
other year for the given document type.
 GL Accounts will be structured with 8 digits number code in various categories like
Liabilities, Assets, Incomes and Expenses.
 Accruals are expected to be posted into General Ledger on a monthly mode and will be
reversed at the beginning of next month.

2. Current Scenario As Is Process (BPD)

Refer BPD Document Number : FI-01_BPD_VBSL_SPV Formation_V1

MSRDC-VBSL Prepared by: itelligence, ABM

Page 6 of 27
 Solution Design Document

3. Process Flow Chart

Componen
SAP Component Component Description
t Values
Funds Management
2000 VBSL Funds Management Area
Area
Controlling Area 2000 VBSL Controlling Area
Company Code 2000 VBSL Company Code
Plant 2000 VBSL Plant Code
2001 VBSL Corporate Office
2002 Site Camp1
Storage Location 2003 Site Camp2
2004 Casting Yard 1
2005 Casting Yard 2
Purchasing
2000 VBSL Purchasing Organization
Organization
P01 Engineering Construction
P02 Engineering Consultancy
Purchasing Group P03 Legal Consultancy
P04 Administration
P05 Operation & Maintenance
Profit center Standard
2000 VBSL Profit center Standard Hierarchy
Hierarchy
Cost Center Standard
2000 VBSL Cost Center Standard Hierarchy
Hierarchy

Enterprise Structure:

MSRDC-VBSL Prepared by: itelligence, ABM

Page 7 of 27
 Solution Design Document

MSRDC-VBSL Prepared by: itelligence, ABM

Page 8 of 27
 Solution Design Document

4. SAP Process Steps

Following steps are required to create a relationship between various master data associated
with Funds Allocation Process.

Step As is Process To Be Process Step To Be Transaction

Step System Code
General Ledger General Ledger created in Chart of
1 Creation Accounts and Company Code of VBSL SAP FS00, FSP0

Profit Centre created in Controlling

2 Area and assigned to Company Code SAP KE51
of VBSL
Cost Centre created in Controlling Area
3 and assigned to Company Code of SAP KS01
VBSL
Posting the transactions into General
4 GL transactions SAP FB50
Ledger

5. Gap Analysis

GAP No. As is Process To Be Process Step Remark

Step

No Gaps are identified.

6. Master Data Details

Sr. Description Codification Codification Pattern Remark

No. Required
To be created by OSO for
1 GL Accounts Yes Please refer KDS data
VBSL
To be created by OSO for
2 Cost Centre Yes Please refer KDS data
VBSL
To be created by OSO for
3 Profit Centre Yes Please refer KDS data
VBSL

MSRDC-VBSL Prepared by: itelligence, ABM

Page 9 of 27
 Solution Design Document

7. Key Data Structure (KDS)

The design of this process is based on the following critical configuration and master data
structures.

 FM Area: The Funds Management Area (FM Area) is the commercial organizational unit,
within which Budget Management is conducted. It structures the business as viewed from
Budget Management point of view.

IMG Path: SPRO → Enterprise Structure → Definition → Financial Accounting →

Maintain FM Area

SR Data type & code

. FM Area FM Area Description length
No
1 2000 VBSL Funds Management Area Alpha Numeric – 4

 Controlling Area: Controlling Area is an Organizational Unit in which the costs and
revenues that are posted to the objects like Projects (WBS Elements), Real Estate Objects,
Internal Orders and Cost Centres are updated in the controlling module.

IMG Path: SPRO → Enterprise Structure → Definition → Controlling → Maintain

Controlling Area

SR. Controlling Data type & code

Controlling Area Description
No Area length
1 2000 VBSL Controlling Area Alpha Numeric - 4

 Company Code: Company Code is the Organizational Unit of Financial Accounting for
which a complete self-contained set of accounts can be drawn up for purposes of external
reporting. At each Company Code Level, Balance-Sheet and Profit and Loss Account and
other financial statements such as Trial-Balance, Cash Flow etc. can be generated.

IMG Path: SPRO → Enterprise Structure → Definition → Financial Accounting → Edit,

Copy, Delete, Check Company Code

Company Data type & code

SR. No Company Code Description
Code length
1 2000 VBSL Company Code Alpha Numeric – 4

MSRDC-VBSL Prepared by: itelligence, ABM

Page 10 of 27
 Solution Design Document

 Fiscal Year: Financial Accounting period is also called “fiscal year” which consists usually
of 12 months, for which the company produces financial statements and ensures its
statutory compliances.

SAP has several fiscal year variants pre-defined and Indian Companies follow variant V3
which is defined with April as first period and March as last period. The example for fiscal
year numbers is shown below:

IMG Path: SPRO → Financial Accounting → Financial Accounting Global Settings

→ Fiscal Year and Posting Periods → Maintain Fiscal Year Variant

Fiscal Year Fiscal Year Variant

Fiscal Year Fiscal Year
Variant (up to Description (up to Periods
From To
2 characters) 30 characters)
Apr - Mar, 4 special
V3 1 to 12 Apr 2019 Mar 2020
periods

 Posting Period: A “posting period” is a period within a fiscal year for which transaction
figures are updated. Every transaction that is posted is assigned to a particular posting
period.

Posting periods can be maintained for each account type, i.e. Assets (A), Customers (D),
Vendors (K),Materials (M), G/L Accounts (S), and Contract Accounts (V). It is not mandatory
to maintain the posting periods for each account type because by specifying account type
“+” (all account types) posting periods can be maintained for all account types in a company
code.

VBSL will have the following posting period structure.

IMG Path: SPRO → Financial Accounting → Financial Accounting Global Settings →

Fiscal Year and Posting Periods → Maintain Fiscal Year Variant

Fiscal Year Fiscal Year Variant Posting Period

Posting
Variant (up to Description (up to 30 Number (up to 2
Month
2 characters) characters) characters)

MSRDC-VBSL Prepared by: itelligence, ABM

Page 11 of 27
 Solution Design Document

V3 Apr - Mar, 4 special periods 1 April

V3 Apr - Mar, 4 special periods 2 May
V3 Apr - Mar, 4 special periods 3 June
V3 Apr - Mar, 4 special periods 4 July
V3 Apr - Mar, 4 special periods 5 August
V3 Apr - Mar, 4 special periods 6 September
V3 Apr - Mar, 4 special periods 7 October
V3 Apr - Mar, 4 special periods 8 November
V3 Apr - Mar, 4 special periods 9 December
V3 Apr - Mar, 4 special periods 10 January
V3 Apr - Mar, 4 special periods 11 February
V3 Apr - Mar, 4 special periods 12 March

 Special Periods: Special posting period is defined while defining the fiscal year variant. At
the year end, external auditor will audit the company’s books of accounts. During this audit,
year-end closing entries will be entered for adjustments to the books of accounts in these
special periods. Since the audit happens after the relevant fiscal year and the periods are
locked in the system, the relevance of special periods assumes importance for the
adjustment entries.

In VBSL, the V3 Fiscal Year Variant will be used with 12 posting periods for the day to day
postings and 4 special periods for audit and other compliance adjustment entries after the
last normal period is locked. The special period postings for the financial year will be
posted into 12th period date (last date) by providing special period input (13, 14, 15, 16)
during the transaction posting.

 Document Numbers : In SAP, every Financial Accounting document which has to be

posted, is assigned with a number which is identified uniquely with respect to the SPV and
the type of document. The document numbers are generated either internally or derived
from the source application.

IMG Path: SPRO → Financial Accounting → Financial Accounting Global Settings

→ Document  Document Number Ranges

For every document number range, the following must be specified.

o A two-character code
o Period until when (a year value) it is valid
o An interval from which it will be chosen and

MSRDC-VBSL Prepared by: itelligence, ABM

Page 12 of 27
 Solution Design Document

o Whether it will be used as internal or external assignment

o The document number range intervals should not overlap
o Document number can be up to ten characters long
In VBSL, Year Independent number ranges will be used. It means number ranges need not
be maintained every year.

 Document Types: Document Type is used to distinguish between different business

transactions and to classify the accounting documents. It is also used to determine the
number range for documents and account types such as asset, material, vendor, etc. for
posting. As per SAP best practises it is recommended to use SAP standard document
types.

IMG Path: SPRO → Financial Accounting → Financial Accounting Global Settings →

Document  Document Types

Common Document Type Keys are as follows –

Document Type Document Type Description

AA Asset Posting

AN Net Asset Posting

DR Customer Invoice

DZ Customer Payment

KA Vendor Document

KG Vendor Credit Memo

 Plant: Operational unit within a company code; who can Procure, produce goods / services
and make them available for the company.

IMG Path: SPRO → Enterprise Structure → Definition → Logistics General  Define,

Copy, Delete, Check Plant

SR. Data type & code

Plant Plant Description
No length
1 2000 VBSL Company Code Alpha Numeric - 4

MSRDC-VBSL Prepared by: itelligence, ABM

Page 13 of 27
 Solution Design Document

 Storage Location: Storage location is an organizational unit which actually differentiates

between different material stocks in a Plant or also a location where the actual services are
availed.

IMG Path: SPRO → Enterprise Structure → Definition → Materials Management →

Maintain storage location

Data type & code Storage

Sr. No. Description
length Code
1 Alphanumeric – 4 2001 VBSL Office
2 Alphanumeric – 4 2002 Site Camp1
3 Alphanumeric – 4 2003 Site Camp2
4 Alphanumeric – 4 2004 Casting Yard 1
5 Alphanumeric – 4 2005 Casting Yard 2

 Purchasing Organization: Purchasing Organization is an organizational unit under

company or plant, which is responsible for procurement activities according to requirements.
It is responsible for external procurement.

IMG Path: SPRO → Enterprise Structure → Definition → Materials Management →

Maintain purchasing organisation

Sr. Data type & Purchase

Name
No code length Organization
1 Numeric – 4 2000 VBSL Purchasing Organization

 Purchasing Group: Purchasing groups (buyer groups), which are responsible for day-to-
day buying activities

IMG Path: SPRO → Materials Management → Purchasing → Create Purchasing

Groups

Sr. Data type & code Purchasing

Name
No length Group
1 Alpha Numeric - 3 P01 Engineering Construction

MSRDC-VBSL Prepared by: itelligence, ABM

Page 14 of 27
 Solution Design Document

2 Alpha Numeric - 3 P02 Engineering Consultancy

3 Alpha Numeric - 3 P03 Legal Consultancy
4 Alpha Numeric - 3 P04 Administration
5 Alpha Numeric - 3 P05 Operation & Maintenance

 Chart of Accounts (COA) : A “chart of accounts” is a classification of General Ledger (G/L)

Accounts. A chart of account must be assigned to each company code. This chart of
accounts is the operative chart of accounts and is used in both financial accounting and
cost accounting.

The chart of accounts provides a framework to a Legal Entity for the codification and
standardization of GL Accounts, based on the nature of transactions and facilitate reporting
of accounting information, that meets the statutory and other managerial requirements. In
VBSL, below nomenclature can be adopted to define Chart of Accounts.

IMG Path: SPRO → General Ledger Accounting → Master Data → GL Accounts →

Preparations → Edit Chart of Accounts List

Chart of accounts (up to 4

Description (up to 50 characters)
characters)
VBSL VBSL Chart of Accounts

 General Ledger Operations

The General Ledger operations are carried out in Financial Accounting module of SAP and two
types of activities influence such operations in SAP – Master Data and Transactions.

Financial Accounting Master Data

In SAP, the master data that needs to be maintained for a legal entity, is dependent on the
processes it has. For VBSL, the master data for Accounts and Finance processes include
following:

o General Ledger Accounts

o Cost Elements

MSRDC-VBSL Prepared by: itelligence, ABM

Page 15 of 27
 Solution Design Document

o Cost Element Group

o Profit Centre
o Profit Centre Group
o Cost Centre
o Cost Centre Group
o Funds Centre
o Fund Commitment Item

Funds Centre, Fund and Commitment Item are described in the SDD document for Funds
Allocation.

The other elements of master data are explained in the below pages:

General Ledger Master

The General Ledger forms the backbone of all the financial systems. General ledger is the main
accounting record of a business which uses double-entry book-keeping. It captures all business
transactions through integration with other operational areas of the company to ensure that
accounting data is always complete and accurate.

In SAP, a ledger code will be defined to represent a Leading Ledger with INR currency and
assigned to VBSL Company Code to effect the Financial Postings into General Ledger and all
the transactions of Accounts Payable, Accounts Receivable and Assets are integrated with
General Ledger with Control Accounts defined within the General Ledger.

In VBSL, the numbering convention of GL Accounts will be done in a way where the user can
identify the nature of GL based on its first digit as an Asset / Liability / Income / Expense.
As a best practice, it is suggested to define the GL Structure as an 8 digit code in the Chart of
Accounts with an intelligence to differentiate subgroups in the broader categories of Asset /
Liability / Income / Expense as follows

1.1 1XXXXXXX Liability Accounts

1.2 1 00 100 01 Liabilities / Owners Equity / Type of Equity / Sequence number
2.0 2XXXXXXX Asset Accounts

MSRDC-VBSL Prepared by: itelligence, ABM

Page 16 of 27
 Solution Design Document

2.1 2 00 100 01 Assets / Fixed Assets / Type of Fixed Assets / Sequence number
3.0 3XXXXXXX Incomes Accounts
3.1 3 00 100 01 Incomes / From Operations / Type of Revenue / Sequence number
4.0 4XXXXXXX Expenses Accounts
4.1 4 00 100 01 Expenses / Operating Expenses / Type of Expense / Sequence number

Below points have to be considered with respect to G/L accounts:

 Master records for each G/L account will be created and maintained at each company code
level.

 The master record contains information and controlling parameters that which control the
entry and processing of business transactions in G/L account.

 G/L accounts will also be used for posting transactions from other modules of SAP.
(MM/PS/ PM, etc.)

There are two segments in the General Ledger Master record:

 Chart of Accounts Segment

 Company Code segment

Chart of Accounts Segment

In this segment, specifications that apply to the entire G/L account master record are captured.
These include:
 The G/L account number and G/L account name

 Whether the account is a balance sheet account or an income statement account

 Data that controls the creation of a master record in a company code, such as the account
group.

Company Code segment

The information, which is specific to a particular Company, is maintained in the Company code
segment of the General Ledger Master record. This data controls how one enters and
processes business transaction data in the appropriate account as well as how the account is
managed within a company code.

MSRDC-VBSL Prepared by: itelligence, ABM

Page 17 of 27
 Solution Design Document

Below are some of the specifications which will be made for each G/L account:

 Currency: The account currency has to be specified as INR.

 Reconciliation Account for Account Type: This will specify the control accounts for the sub
ledgers.

 Open Item Management: It will be maintained for accounts that require open item
management. E.g. Bank sub-accounts, GR/IR Clearing account, etc. are maintained in
Open Item Management.

 Line Item Display: It will be retained for accounts for which line items are to be stored
separately. E.g. Bank main accounts, all expense accounts, all balance sheet accounts,
excepting accounts which are of the nature of reconciliation accounts.

Cost Elements
Cost elements are defined in the controlling module of SAP and are assigned to various objects
such as cost centers, internal orders, etc. Basically, their function is to classify and analyze the
cost for internal reporting purposes. The integration between the expense accounts in financial
accounting and cost elements in management accounting is essential for reconciliation
purposes. Therefore, posting to a Cost Element is done through a posting to an
Income/Expense type G/L account.

Cost Element Groups

Cost Element Group is the grouping of cost elements for cost allocation and reporting
purposes.
Cost Element Group Description
DIR_EXP Direct Expenses Group
OPER_EXP Operational & Other Expenses
Profit Center Standard Hierarchy:
Represents the top node in Controlling Area for Profit Centers.
Standard Hierarchy Description
2000 Profit center Standard Hierarchy VBSL

Profit Centre

MSRDC-VBSL Prepared by: itelligence, ABM

Page 18 of 27
 Solution Design Document

Profit Centers in SAP are created to understand operating profit of each area of responsibility. A
Profit Center is an organizational unit that operates independently within the company and
monitored for all Financial Accounting transactions. Typically, SAP systems derive Profit
Centers based on the assignment to other objects that could be material master, cost center,
WBS Element and Internal Order.

For VBSL, the Profit Centers are codified as listed below: In the 6-digit code of profit center, first
4 digit represents Company Code and the remaining two digits represent department code.

Sr. No. Profit Center Description

01 200001 VBSL Common Profit Centre
02 200002 VBSL Commercial Department
03 200003 VBSL Administration
04 200004 VBSL Engineering
05 200005 VBSL Finance and Accounts
06 200006 VBSL Legal
07 200007 VBSL Secretarial

Profit Center Group

Profit Center Group is used to for grouping of Profit Centers for reporting purpose.

Profit Center Group Description

Operations Operations Group Profit Centres
Admin Administration Group Profit Centres

Cost Center Standard Hierarchy

Represents the top node in Controlling Area for Cost Centres.

Standard Hierarchy Description

2000 Cost Center Standard Hierarchy VBSL

Cost Center

An organizational unit that represents a defined location of cost incurrence and can be used for
tracking the origin of the cost. Cost Centers can be defined on the basis of Department,
Functional requirements, Allocation criteria, Physical location or Responsibility for costs. It is
proposed to consider Departments as Cost Centers.

MSRDC-VBSL Prepared by: itelligence, ABM

Page 19 of 27
 Solution Design Document

Cost Centers are codified as a combination of Profit Center and Department. For the purpose
of codification, department codes have been mentioned in Department list.

List of VBSL Departments:

Sr. No. Department Code Department description

1 01 Common
2 02 Toll Monitoring
3 03 Administration
4 04 Engineering
5 05 Finance & Accounts
6 06 Legal
7 07 Secretarial

List of Cost Centers:

Sr. Cost Cost Centre Profit

Profit Centre Description
No. Centre Description Center
01 20000101 Common Cost Center 200001 VBSL Common Profit Centre
VBSL Commercial
02 20000201 Toll Monitoring 200002
Department
03 20000301 Administration 200003 VBSL Administration
04 20000401 Engineering 200004 VBSL Engineering
05 20000402 Maintenance 200004 VBSL Engineering
06 20000501 Finance and Accounts 200005 VBSL Finance and Accounts
07 20000601 Legal 200006 VBSL Legal
08 20000701 Secretarial 200007 VBSL Legal

Cost Center Group

Cost Center Group is used for grouping of Cost Centers for cost allocation and reporting
purpose.

Cost Center Group Description

MSRDC-VBSL Prepared by: itelligence, ABM

Page 20 of 27
 Solution Design Document

Operations Operations Group Cost Centers

Admin Administration Group Cost Centers

 Financial Accounting Transactions

General Ledger Posting Functions

Below are the posting functions associated with General Ledger Accounts in SAP. In other
words, following activities can be performed as part of posting function

I. Post
A document consists of a document header and at least two document line items:
The document line item is a part of the document that contains information on an item. This
includes the amount, an account number, whether the item is a debit or credit and
additional information depending on the transaction to be posted. A document line item can
also contain additional account assignments (for example, profit centre, cost centre) and an
explanatory text. Also ‘Search’ feature is available at line item level in standard for account
number, cost objects, additional account assignment by its name, company code etc. which
will be used to find the related codes for the transaction posting activity.

II. Clear
The clear function is associated with General Ledger Accounts that are maintained with
open item management in the legal entity segment. The post function will generate open
items in the GL accounts which are maintained with open item management in its master
data. The open items can be cleared from the account either by post with clearing function
or by clear option. Both the functions are available in automatic and manual mode in SAP.

Post with clearing will generate net amount in the same account on the opposite side of its
balance and make the account balance zero and set all the open items as cleared items in
the respective General Ledger Account.

For Clear function, the open items posted must be equal to zero as a balance and the
function will generate a clearing document number and set all the open items as cleared
items in the respective General Ledger Account.

MSRDC-VBSL Prepared by: itelligence, ABM

Page 21 of 27
 Solution Design Document

III. Reversal
An accounting document that has been already posted can be reversed if any of the details
entered were found to be incorrect. If the original document contains the open item account,
the reversal will convert such account open items to cleared items and for non-open item
accounts it will post to the opposite side of the account. A document once reversed, cannot
be re-reversed in SAP.

IV. Accrual & Deferrals

Accrual of an expense is reporting as an expense in the period in which they occur
irrespective of the payment made.
Deferral of expenses means that a payment is made in one period, but the expense itself
will be reported as an expense in a later period.

In Accrual/Deferral document method, provisions are made at the month end and the same
are reversed on the first day of the next month.

 Tolerance Group for GL Accounts : For G/L account clearing, tolerance groups define the
limits within which differences are accepted and automatically posted to predefined accounts.
The groups defined here can be assigned in the general ledger account master record. The G/L
account clearing tolerance can be specified both, in amount as well as percentage rate.

IMG Path: SPRO → Financial Accounting → General Ledger Accounting → Business

Transactions→ Open Item Clearing  Clearing Differences → Define Tolerance Groups for
G/L Accounts.

Name of Field Value for VBSL

Company code 2000
(G/L account clearing) Tolerance group <blank>
Name of tolerance group Tolerance Group of VBSL
Debit posting 1.00
Credit posting 1.00
Debit posting Percentage 0.0
Credit posting Percentage 0.0

MSRDC-VBSL Prepared by: itelligence, ABM

Page 22 of 27
 Solution Design Document

 Tolerance Group for Employees: An “employee tolerance group” is a unique combination of

various amount limits for employees. It determines:

 The maximum document amount the employee is authorized to post.

 The maximum amount the employee can enter as a line item in a customer or vendor account.

 The maximum cash discount percentage the employee can grant in a line item.

 The maximum acceptable tolerance for payment differences for the employee.

Payment differences are posted automatically within certain employee tolerance groups. This
way, the system can post the difference either by correcting the cash discount or by posting to
a separate expense or revenue account. In this respect you define:

 The amounts or percentage rates up to which the system has to automatically post to a
separate expense or revenue account, else, if it is not possible to correct the cash discount or
up to which difference amounts the system is to correct the cash discount. In this case the cash
discount is automatically increased or decreased by the difference using employee tolerance
groups.

Name of Field Value for VBSL

(Employee) Tolerance group <blank>
Company code 2000
Currency INR
Amount per document 9,999,999,999,999.00
Amount per open item account
9,999,999,999.00
item
Cash discount per line item 5.000%
Amount 10.00
Percent 10.0%
Cash discount adjusted to 10.00
Amount 100.00
Percent 10.0%

 Retained Earnings Account : At the end of a fiscal year, the system carries forward the balance
of the P&L account to the “retained earnings account”. Retained earnings account is specific to
the chart of accounts.

MSRDC-VBSL Prepared by: itelligence, ABM

Page 23 of 27
 Solution Design Document

IMG Path: SPRO → Financial Accounting → General Ledger Accounting → Master Data
→ G/L Accounts  Preparations  Define Retained Earnings Account

Name of Field Value

Chart of accounts VBSL
Transaction BIL (Balance carried forward)
P&L statement account type X
Account XXXXXX

 Financial Statement Version : A “financial statement version” is a hierarchical positioning of G/L

accounts. This positioning can be based on specific legal requirements for creating financial
statements. It can also be a self-defined order.

For VBSL, Financial statement version can be maintained as 2000.

IMG Path: SPRO → Financial Accounting → General Ledger Accounting → Master

Data → G/L Accounts  Define Financial Statement Versions (T-Code -- OMSF)

Financial statement version Financial statement version name (up to 50

(up to 4 characters) characters)
2000 Financial Statement – VBSL

8. Data Migration requirements

There are no Data Migration Requirements in this process

9. Development Objects (RICEFW)

There are no Development Objects in this process.

Sr. Object Object Description F/R/I/C/E/W** FS Ref.*

No. No. Type

Functional Specification Reference

** F – Forms, R – Reports, I – Interfaces, C – Conversion, E – Enhancements, W – Workflow

MSRDC-VBSL Prepared by: itelligence, ABM

Page 24 of 27
 Solution Design Document

10. Roles and Authorizations

Sr. Role SAP Transaction Create/Chan

Activity Description
No Code ge/Display
FC10N,
1 ZS:FI_CAFO Legal Entity Management All
S_ALR_87012284
FC10N,
2 ZS:FI_CFO Plant In-Charge All
S_E38_98000088
S_ALR _87013611,
3 ZS:FI_CO_CFO Cost Control All
KSB1
KP06, KSB1N,
4 ZS:FI_CO_ACC_MNRG Cost Management S_ALR87013611, All
FB50

5 ZS:FI_ACC_GL_ MGR Revenue Generation FB50, F-02 All

Operations and
6 ZS:FI_ACC_O&M_ACC MCI8 All
Maintenance In-Charge

11. Reports

Following are the standard reports that are available in the SAP System

Transaction Codes Description

FC10N Financial Statement
S_ALR_87012277 GL Account Balances
S_ALR_87012291 Line Item Journal
S_ALR_87012333 GL Account List
S_ALR_87013611 Cost Centers: Actual/Plan/Variance

Report FC10N
Field Name Field Description
Account Number GL Account Number
Text for B/S P&L Item GL Account Number Description
Total of Reporting Period Amount of Reporting Period
Total of the Comparison Amount of Comparison Period

MSRDC-VBSL Prepared by: itelligence, ABM

Page 25 of 27
 Solution Design Document

Period
Absolute Difference (Difference between Reporting
Absolute Difference
and Comparison period)

Report S_ALR_87012277
Field Name Field Description
CoCd Company Code
G/L acct GL Account Number
Short Text GL Code Short Description
Crcy Currency
Balance Carry forward Balance Carry forward from Last Fiscal Year
Debit Blnce of Reportng
Debit Balance of Current Year
Period
Credit Balance Reporting Per. Credit Balance of Current Year
Accumulated Balance Accumulated balance till Date

Report S_ALR_87012291
Field Name Field Description
CoCd Company Code
Pstng Date Posting Date
Entry Date Entry Date
DocumentNo Document Number
Itm Line item
Doc..Date Document Date
PK Posting Key
SG Special G/L Ind.
Account GL Account Number
User Name User Name
Local Currency Local Currency
Debit/Credit Amount Debit/Credit Amount
Tax Code Tax Code
Assignment Assignment (Narration)

Report S_ALR_87012333
Field Name Field Description
ChAc Chart of Accounts

MSRDC-VBSL Prepared by: itelligence, ABM

Page 26 of 27
 Solution Design Document

G/L account General Ledger Account Number

CoCd Company Code
Long Text General Ledger Account Long Description

Report S_ALR_87013611
Field Name Field Description
Cost Elements Cost Elements
Act. Costs Actuals Costs posted for respective period
Plan Costs Plan Cost maintained for Cost Element
Var.(Abs.) Variance in Actuals and Plans Value
Var.(%) Variance in %

12. Assumptions

Following are the assumptions on which the SDD has been prepared and they had to be
considered in view of relevant information not being available from MSRDC for VBSL:

 The Financial Closure for VBSL Project is not yet obtained by MSRDC and that
determines the TRA Structure of VBSL. In SAP, the Funds Management and the project
budgeting activities are associated with this assumption, hence any variation in the terms
of TRA structure might have an influence on these processes in SAP.

 As VBSL is not a Profit oriented project, Profit Centre does not denote the Actual profit
earned, however, considering the technical requirements of SAP in S4 HANA, Profit
Centre has been derived based on the Cost Centre Structure of MSRDC.

MSRDC-VBSL Prepared by: itelligence, ABM

Page 27 of 27