Archit BBP FI V1.0 30092010
Archit BBP FI V1.0 30092010
Archit BBP FI V1.0 30092010
Business Blueprint
Financial Accounting
BBP_FI_V1.0
SIGNATORY
NAME
TITLE
Prepared by
Zensar-Consultant
Reviewed/
Approved by
A Sreenivasan
Zensar-PM
Reviewed by
Bhushan Punekar
CTM-Lead
Reviewed/
Approved by
Reviewed/
Approved by
BPO
Govind Joshi
Client-PM
DATE
SIGNATURE
Document Control
Document ID
ZTL/2010/PRJ-252/FI/03
Compliance Status
Mandatory
Security Classification
Company Restricted
Issue Date
Document Status
Prepared by
Quality Review
JN Rao
Authorized by
Sreenivasan A
Distribution
Document History
V1.0
Draft,
Revised,
Final
B Sreenivasa Rao
Page 2 of 189
DOCUMENT CONTROL:
S NO
Revision
Creation Date
Last Modified
Remarks
1
2
3
4
5
Page 3 of 189
Table of Contents
1.
INTRODUCTION............................................................................................8
2.
3.
2.1
Financial Accounting........................................................................................... 8
2.2
CO Module Overview.......................................................................................... 9
Enterprise Structure..............................................................................11
3.1
Client................................................................................................................ 12
3.2
Operating Concern............................................................................................13
3.3
Controlling Area................................................................................................13
3.4
Company Code.................................................................................................13
3.5
Segments......................................................................................................... 14
3.6
Sales Organization............................................................................................ 14
3.7
Distribution Channel......................................................................................... 14
3.8
Divisions........................................................................................................... 15
3.9
Purchasing Organization...................................................................................15
3.10
Plant................................................................................................................. 16
3.11
3.12
3.13
3.14
Chart of Accounts.............................................................................................21
Global settings......................................................................................22
4.1
Currency........................................................................................................... 22
4.2
4.3
Document Types...............................................................................................23
4.4
Document Numbering.......................................................................................23
4.5
Posting Key....................................................................................................... 25
4.6
Posting Period................................................................................................... 26
4.7
4.8
Exchange Rates................................................................................................27
4.9
Tax procedure................................................................................................... 28
4.10
Page 4 of 189
Master Data..........................................................................................35
5.1
FI
5.1.1
5.1.2
5.1.3
5.1.4
5.1.5
5.1.6
5.1.7
5.1.8
5.1.9
Master Data..................................................................................................35
General Ledger.............................................................................................. 35
Customer Account......................................................................................... 40
Vendor Account............................................................................................. 42
Bank Accounting........................................................................................... 45
House Banks................................................................................................. 45
Fixed Assets.................................................................................................. 46
Material Master............................................................................................. 52
FI - Master Data - Transaction / Activity Chart...............................................54
Financial Accounting Master data Integration:............................................54
5.2
CO Master Data................................................................................................55
5.2.1 Cost Elements............................................................................................... 55
5.2.2 Cost Element Groups.....................................................................................57
5.2.3 Cost Center................................................................................................... 57
5.2.4 Cost Centre Groups.......................................................................................58
5.2.5 Activity Types................................................................................................ 59
5.2.6 Activity type groups......................................................................................59
5.2.7 Statistical key Figures....................................................................................59
5.2.8 Internal Order................................................................................................ 60
5.2.9 Profit Centers................................................................................................ 60
5.2.10
Material Master - Costing Views.................................................................61
5.2.10.1
5.2.10.2
5.2.10.3
5.2.10.4
5.2.10.5
5.2.10.6
5.2.11
5.2.12
6
6.1.4
6.1.5
6.1.6
6.1.7
6.1.8
6.1.9
6.1.9.1
6.1.9.2
6.1.10
6.1.11
Sample Documents............................................................................................... 71
Account Assignment Models................................................................................... 72
Recurring Document.............................................................................................. 72
GL Process Steps.......................................................................................78
General Ledger Integration:....................................................................81
6.2
Accounts Payable.............................................................................................. 81
6.2.1 Vendor Down Payment..................................................................................82
6.2.2 Down payment request.................................................................................82
6.2.3 Vendor Invoice without Purchase Order.........................................................84
6.2.4 Goods Receipt based Vendor Invoice Verification..........................................86
6.2.5 Goods Receipt based Invoice Verification for Imports....................................90
Page 5 of 189
6.2.6
6.2.7
6.2.8
6.2.9
6.2.10
6.2.11
6.2.12
6.2.13
6.2.14
6.2.14.1
6.2.14.2
6.2.15
AP Process Steps.....................................................................................100
6.3
Accounts Receivable.......................................................................................102
6.3.1 Sales Invoices posting to Accounting..........................................................102
6.3.2 Credit Memo Processing..............................................................................103
6.3.3 Customer Down Payment............................................................................103
6.3.4 Customer Incoming Payment......................................................................104
6.3.5 Receipt of Post Dated Check from Customer...............................................104
6.3.6 Bills of Exchange......................................................................................... 105
6.3.7 Agent Commission Recognition...................................................................106
6.3.8 Tax Collected at Source on Scrap Sales.......................................................106
6.3.9 Dunning Customers for overdue receivables...............................................106
6.3.10
Credit Management.................................................................................107
6.3.11
Closing Operations..................................................................................107
6.3.11.1
6.3.11.2
6.3.12
AR Process Steps.....................................................................................109
6.4
Asset Accounting............................................................................................111
6.4.1 Asset Acquisition......................................................................................... 112
6.4.1.1
Direct Capitalization............................................................................................. 112
6.4.1.1.2 Acquisition in Asset Accounting with Vendor........................................................113
6.4.1.1.3 Acquisition in Asset Accounting without Vendor....................................................114
6.4.1.2
Asset under Construction / Capital WIP..................................................................114
6.4.1.2.1 Assets under Construction without Internal Order / Project....................................114
6.4.2
6.4.3
6.4.4
6.4.4.1
6.4.4.2
6.4.5
6.4.5.1
6.4.5.2
6.4.5.3
6.4.6
6.4.6.1
6.4.7
Asset Depreciation......................................................................................119
6.4.7.1
6.4.7.2
6.4.7.3
Page 6 of 189
6.5
Cash and Bank Accounting.............................................................................126
6.5.1 Bank Accounting......................................................................................... 126
6.5.1.1
Check Payment.................................................................................................. 126
6.5.1.2
Check Receipt.................................................................................................... 127
6.5.1.3
Bank Reconciliation Statement (BRS).....................................................................128
6.5.1.3.1 Automatic Bank Reconciliation.......................................................................... 129
6.5.1.3.2 Electronic Bank Statement and Manual Bank Statement.......................................130
6.5.1.4
Liquidity Forecast................................................................................................ 131
6.5.1.5
Cash Position..................................................................................................... 133
6.5.2
6.5.2.1
6.6
Taxes............................................................................................................... 136
6.6.1 Tax on Sales and Purchases.........................................................................136
6.6.2 Excise Duty................................................................................................. 137
6.6.3 Service Tax.................................................................................................. 141
6.6.4 Extended Withholding Tax (TDS).................................................................145
6.6.4.1
6.6.4.2
6.6.4.3
6.6.4.4
6.6.4.5
6.6.4.6
6.6.4.7
6.6.4.8
6.6.4.9
6.6.4.10
6.6.5
6.6.6
Integration considerations...................................................................151
Process Requirements.........................................................................156
Reporting requirements.......................................................................176
10
Output requirements...........................................................................188
11
12
Authorizations.....................................................................................190
13
History of Change......................................................................................191
1. Introduction
The purpose of this document is to compile the requirements gathered during business
process design workshops. And also Arch has submitted the User Requirement document.
Page 7 of 189
This document describes the design of the proposed solution and implications for the
business process. This document is to communicate the new business solution and
expected changes to the business process. The information needs to include:
Authorizations
With the information conveyed by this document, the business should be able to approve the
proposed
solution.
The
Process
Definition
Document
becomes
the
master
Financial Accounting
The Financial Accounting Module is a complete accounting system capable of recording all
business transactions. The system has the following features:
Powerful tools for real-time evaluation and reporting of current accounting data.
Comprehensive tools (balance lists, journals, balance audit trails and other standard
reports) for documenting accounts.
FI Module
Components
Description
Page 8 of 189
Asset Accounting
Bank Accounting
2.2
CO Module Overview
Page 9 of 189
Controlling.
This component is used to track the occurrence of costs in the
organization. As costs are incurred, they are assigned or posted
to the appropriate Cost Center. The posting and assignment of
costs to Cost Centers not only makes Managerial Accounting
possible but is a vital step in using other CO components. The
standard hierarchy of the CO Area includes all Cost Centers and
provides the ability to analyze costs at different positions.
It is a very flexible tool that can be used for a wide variety of
Internal Orders
Page 10 of 189
CO
Module
Description
Components
also provides the tools for calculating the Work in Process and
the variances at the period end closing.
Profitability
(CO-PA)
for
price
determination,
customer
selection,
3. Enterprise Structure
Within the Financial Accounting Module, specific high-level organizational structures are
defined. These Enterprise Structures provide a direction for how the solution operates and
how business functions, data and reporting are defined.
The Enterprise Structure in SAP Financial Accounting and Controlling as below:
Page 11 of 189
3.1
Client
The client is the highest level in the SAP System hierarchy. Specifications or data entered at
this level are valid for all company codes and for all other organizational structures. Each
Client contains a separate and unique set of master data, and data tables.
The following will be the client numbers for Arch:
Server
Development
Development
Sandbox
Quality
Production
Solution
Manager
3.2
Client
100
200
300
500
700
Purpose
Configuration and Development environment
Pre-test, to conduct the initial testing by Consultant
Training / Testing / Practice to all users
Testing - Unit and Integration testing
Production - To record all business transactions
252
Operating Concern
An operating concern represents an organizational unit of the company, which provides the
sales and marketing information in a uniform structure. It is the valuation level for Profitability
Analysis (CO-PA).
Page 12 of 189
By setting off the costs against the revenues, an operating profit for the individual market
segments that are defined by a combination of classifying characteristics (such as product
group, customer group, country, or distribution channel) can be calculated. The market
segments are known as profitability segments in CO-PA.
3.3
Operating Concern
Description
1000
Controlling Area
Controlling Area is an Organizational Unit in Controlling Module which is used for Cost
Accounting. Data in the Controlling Area is simultaneously updated with the various postings
in the Financial Accounting / Material Management / Sales and Distribution / Production
Planning / Human Capital Management modules.
The Controlling Area for Arch is given below:
Controlling Area
1000
3.4
Description
Arch Controlling Area
Company Code
Company Code is the Organizational Unit of Financial Accounting for which a complete selfcontained set of accounts can be drawn up for purposes of external reporting. This includes
recording of all relevant transactions and generating all supporting documents required for
financial statements. At each Company Code level Balance Sheet and Profit and Loss
Account and all financial statements can be generated. Statements required for Legal
Reporting can be generated / balanced at Company Code level. Company code is used for
various processes within Financial Accounting in order to balance entries, post transactions
and manage security.
Description
Arch Pharmalabs Limited
Page 13 of 189
3.5
Segments
Segment is the can be an organizational unit or a sales area or a division of the company. It
has both the functionalities of the Business area as well as the Profit Centre and it can be
termed as an organization with in the main company code and is like a group of Profit
Centre. The segment as such is derived from the assigned profit centre.
Segments will be activated in future.
3.6
Sales Organization
Sales Organization is an organizational element, which represents all activities of Sales and
Distribution module with in SAP such as Sales, Distribution of goods and services, Billing. It
is an organizational unit within logistics that structures the company according to its sales
requirements.
The Sales Organizations for ARCH are:
Company
Sales
Code
1000
1000
3000
3000
Code
1100
1500
3100
3500
3.7
Org
Sales Organization Description
Arch Domestic Sales Organization
Arch Export Sales Organization
Avon Domestic Sales Organization
Avon Export Sales Organization
Distribution Channel
Distribution channels are the means through which the sold materials reach the customer.
A distribution channel can be assigned to one or more sales organizations.
The Sales Distribution Channels are:
Distribution
Channel
10
20
30
90
Description
Direct
Depot / Warehouse
Inter-company Sale
Stock Transfer
Page 14 of 189
3.8
Divisions
A division can be defined as a Product group or business segment or line of business that
could be made up of a wide-ranging spectrum of products. This entity normally groups
together saleable materials and services for the purpose of responsibility and analysis.
The Sales Divisions for Arch are:
Division
10
20
31
32
40
51
90
90
92
3.9
Description
Intermediates
API
CRAMS Intermediates
CRAMS API
Agro Chemicals
Services
Others
Job work
Scrap Sales
Purchasing Organization
Description
CPO - Mumbai
Arch - Maharashtra
Arch - Tarapur factory
Arch - Badlapur Unit
Arch - Taloja G - 6 Unit
Arch - Taloja R & D Unit
Arch - Tarapur, Plot E-64 & E-82
Arch - Dombivali unit
Arch - Turbhe R & D Unit
Arch - Tarapur W/H
Arch - Bhiwandi
Arch - Bhiwandi W/H
Arch - Andhra Pradesh
Page 15 of 189
3.10 Plant
Plant is an organizational unit within a company code. A Plant is an organizational unit that
divides the enterprise according to production, procurement, distribution and Stock storage
area etc. It is a place where materials are produced, or goods and services are provided.
Plant
Plant Description
Plant
Location
1000
1000
1000
1000
1000
1100
1101
1102
1103
1104
Head Office
Arch Pharmalabs ltd - Tarapur factory
Arch Pharmalabs ltd - Badlapur Unit
Arch Pharmalabs ltd - Taloja G - 6 Unit
Arch Pharmalabs ltd - Taloja R & D Unit
Mumbai
Tarapur
Badlapur
Taloja
Taloja
Activity
ARCH
HO
MFG
MFG
MFG
R&D
Page 16 of 189
Company
Code
1000
1000
1000
1000
Plant
1105
1106
1107
1151
Plant Description
Arch Pharmalabs Ltd- Tarapur, Plot- E-64 & E-82
Arch Pharmalabs ltd - Dombivali unit
Arch Pharmalabs ltd - Turbhe R & D Unit
Logical Port- Maharashtra
1000
1000
1000
1152
1153
1161
Plant
Location
Tarapur
Dombivali
Turbhe
Maharashtra
Andhra
Pradesh
Haryana
Tarapur
1000
1000
1171
1172
Tarapur
Bhiwandi
1000
1173
Bhiwandi
1000
1000
1000
1000
1000
1200
1201
1202
1203
1272
Hyderabad
Hyderabad
Hyderabad
Hyderabad
Hyderabad
1000
1271
Hyderabad
1000
1301
Gurgaon
MFG
1000
1000
1000
1302
1371
1372
Bonding
Bonding
MFG
NE
Depot
E Depot
NE
Depot
ARCH
RO
MFG
MFG
MFG
E Depot
NE
Depot
Gurgaon
Gurgaon
Gurgaon
1000
1471
Vadodara
1000
3000
1571
3101
Bhiwadi
Solapur
3000
3000
3000
3200
3201
3251
Head Office
Avon Organics Limited - Sadasivpet unit
Logical Port- Maharashtra
3000
3000
3000
3252
3253
3401
Hyderabad
Hyderabad
Maharashtra
Andhra
Pradesh
Haryana
Vadodara
R&D
E Depot
E Depot
NE
Depot
NE
Depot
MFG
AVONHO
MFG
Bonding
3000
3171
Bhiwandi
Activity
MFG
MFG
MFG
Bonding
Bonding
Bonding
MFG
NE
Depot
Page 17 of 189
Description
Arch Credit Control Area
3000
Page 18 of 189
1000
Maintenance plant is the organization in which technical objects and main work
centers can be maintained
In a Planning plant, maintenance task lists are defined for the respective
maintenance plants, material planning is carried out on the basis of bills of material in
task lists and orders, maintenance plans are managed and scheduled, maintenance
notifications are created and maintenance orders can be handled.
Company
Code
Maintenance
Plant
1101
Arch Pharmalabs
Tarapur factory
ltd
1000
1102
Arch Pharmalabs
Badlapur Unit
ltd
1000
ltd
1000
1103
Arch Pharmalabs
Taloja G - 6 Unit
1104
Arch Pharmalabs
Taloja R & D Unit
ltd
1000
1000
1105
Arch
Pharmalabs
LtdTarapur, Plot- E-64 & E-82
1105
1000
1106
Arch Pharmalabs
Dombivali unit
Plant Description
Maintenance
Planning
Plant
1101
1102
1103
1104
ltd
Plant Description
1106
Page 19 of 189
1000
1107
1000
1161
1000
1201
Merven Unit
1202
Arch Pharmalabs
Siddipet Unit
1000
1107
Arch
Pharmalabs
Ltd- 1105
Tarapur, Plot- E-80 & E-81
Arch Pharmalabs ltd - 1201
- 1202
ltd
1000
1203
1000
1301
3000
3101
Solapur unit
3201
3000
Description
Arch Chart of Accounts
The numbering logic for Arch GL account, the first digit represented as follows,:
Page 20 of 189
2 - Assets
3 - Revenues
4 & 5- Material Consumption & Manufacturing Expenses
Employee Benefits & Administrative Expenses
Selling Expenses & Interest and other charges
Depreciation, Deferred Expenses & Appropriations
9 - Secondary Cost Elements
Page 21 of 189
Global settings
4.1
Currency Settings
Document types
Document numbering
Tax structure
Currency
Arch Pharmalabs Limited will use Indian Rupees (INR) as the base currency. The Company
will define all other currencies in relation to the Indian Rupees.
Sl No
Company Code
Currency
Group Currency
1000
INR
INR
4.2
Fiscal year variant represents the accounting period as per the financial year of an
organization. A fiscal year is usually for 12 months (12 periods). A fiscal year need not
correspond to the calendar year. The fiscal year variant specifies the number of posting
periods and special periods in a fiscal year. The fiscal year variant also determines the
posting periods during posting.
In addition to the normal 12 posting periods, SAP supports additional 4 months to post the
Book Closure, Audit and Year end entries.
Fiscal year variant for Arch can be as follows
Page 22 of 189
4.3
Variant
V3
V3
Description
April to March, 4 Special Periods
April to March, 4 Special Periods
Document Types
Document types are required in SAP ECC 6.0 system to create and post financial documents
(e.g. Bank Payment Voucher, Receipt Voucher etc.)
The document type controls the following:
Document Number
Document types are defined at the client level and are therefore valid for all company codes.
The standard system is delivered with document types which can be used, changed, or
copied.
Document
Type
AA
AB
AF
C0
Text
Asset posting
Accounting document
Depreciation Postings
Cash Voucher
Rev.
Type
AA
AB
AF
C0
Doc. No.
Range
12
11
13
16
From No.
12000001
11000001
13000001
16000001
To No.
12999999
11999999
13999999
16999999
Page 23 of 189
Text
Cash Receipt
Cash Payment
Bank Transfers
Customer document
Customer credit memo
Customer invoice (FI)
Customer payment
Excise document
Vendor document
Vendor credit memo
Account Maintenance
Vendor invoice (FI)
Vendor payment
Price change
Sub. cred. memo stlmt
Purchase
Invoice
document
Billing document
G/L account document
Settlement Documents
WHT Documents
Data transfer (upload
entry)
Goods issue
Goods receipt
Inventory document
Goods issue/delivery
Recurring entry doc.
Sample document
CO-FI Posting
Payment posting
Bank reconciliation
Hard
JV
(Journal
Voucher)
Soft JV (Provisional JV)
Rev.
Type
CP
CR
BT
DA
DG
DR
DZ
ED
KA
KG
KP
KR
KZ
PR
RA
From No.
17000001
18000001
19000001
20000001
21000001
22000001
23000001
87000001
30000001
31000001
47000001
32000001
33000001
38000001
51000001
To No.
17999999
18999999
19999999
20999999
21999999
22999999
23999999
87999999
30999999
31999999
47999999
32999999
33999999
38999999
51999999
RE
RV
AB
SL
TD
39
90
80
84
85
39000001
9000000001
80000001
84000001
85000001
39999999
9999999999
80999999
84999999
85999999
UE
WA
WE
WI
WL
Z0
ZP
ZR
14
40
42
48
44
46
89
88
34
60
14000001
40000001
42000001
48000001
44000001
46000001
89000001
88000001
34000001
60000001
14999999
40999999
42999999
48999999
44999999
46999999
89999999
88999999
34999999
60999999
JH
JS
52
53
52000001
53000001
52999999
53999999
Page 24 of 189
Reverse
Types
D
Posting Key
12
11
09
19
11
Credit memo
19
21
Credit memos
32
29
39
31
Vendor Invoice
22
32
21
39
29
40
Debit entry
50
50
Credit entry
40
70
Debit asset
75
75
Credit asset
70
Posting Keys
Description
Debit / Credit
01
Customer Invoice
02
For each posting key, a reversal-posting key may be defined. The reversal-posting key is
used to reverse a document posted in financial accounting. A Document can be reversed in
Financial Accounting if the following conditions are fulfilled
Page 25 of 189
4.6
Posting Period
Once a fiscal year is defined, it is possible to specify whether a period is allowed for posting
or not. In order to standardize maintenance of accounting period especially across the
group, SAP ECC 6.0 system allows the specification of open or close status to be
maintained via a posting period variant.
Following posting period variant will be created for Arch.
Posting Period Variant
1000
3000
Description
Arch Posting Period Variant
Avon Posting Period Variant
Company Code
1000
3000
Description
G001
G003
G004
Cost Accounts
G007
Asset Accounts
G012
Receivable/Payables Clearing
G019
Other receivables/Payables
G029
Revenue Accounts
Page 26 of 189
4.8
Description
G067
Reconciliation Accounts
Exchange Rates
Exchange rates can be defined for each currency pair. Exchange rates will be maintained
under exchange rate type and can be used for the following purposes.
Usage
Purchase Rate for Imports
Sales Rate for Exports
Revaluation Rate for Open items
Excise / Custom Rate
Average Rate
For all the exchange rate types, Currency Translation ratios will be maintained as below:
Exchange Rate Type
K
K
K
K
K
K
K
D
D
D
D
D
D
D
R
R
R
R
R
R
R
ED
ED
From
DEM
EUR
JPY
USD
SGD
AUD
GBP
DEM
EUR
JPY
USD
SGD
AUD
GBP
DEM
EUR
JPY
USD
SGD
AUD
GBP
DEM
EUR
To
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
INR
Page 27 of 189
Country
Tax Procedure
Tax type
Other fields
A0
V0
IN
IN
1TAXINN
1TAXINN
A (Sales tax)
All other active fields blank
V (Purchase tax) All other active fields blank
Page 28 of 189
A document is created in Financial Accounting for each posting in Controlling. This means
that the detailed information contained in the CO documents is always available in reports in
New General Ledger Accounting.
Value flows within controlling that are relevant for General Ledger Accounting such as
assessments, distributions, confirmations, and CO-internal settlements are transferred
immediately. The FI documents are posted with the business transaction COFI. They contain
the number of the CO document. This means that you can call up the CO document from the
FI document, and vice versa.
If a document could not be transferred because the posting period was blocked in Financial
Accounting or no account was found, for example, the document is included in a post
processing work-list.
The following variant will be created and assigned to the Company Code 1000 and 3000.
Cross Segment
Cross Fund
Page 29 of 189
4.1.3
Document Splitting Characteristics for GL Accounting
Here you specify to which document splitting characteristics document splitting applies, for
example, profit centre or segment. Arch requires to draw the P&L and Balance sheet based
on Profit centre wise and Business segments. To take care this business requirement both
profit centre and segment is considered as scenario which required to be mapped.
COA
1000
1000
1000
1000
1000
1000
1000
Account
from
11110000
12000000
12200000
12310010
12340000
12410000
12410300
Account
to
11299999
12099999
12299999
12339999
12349999
12410299
12419999
Categeroy
1000
1000
1000
1000
4000
3000
1000
Description
Balance Sheet Account
Balance Sheet Account
Balance Sheet Account
Balance Sheet Account
Cash Account
Vendor
Balance Sheet Account
Overrd.
Page 30 of 189
Page 31 of 189
Every business transaction that is entered is analyzed during the document splitting process
by the system. In this process, the system determines which splitting rule needs to be
applied to the document. In order to determine the splitting rule by the system, must assign a
business transaction variant to each Document Type.
Splitting rule is assigned appropriately, to the relevant documents must meet requirements.
These requirements relate in particular to certain item categories. This information is
specified for each business transaction variant and is checked against the current document
during posting. If the document does not meet these requirements, the system rejects the
posting, stating that document split is not able carryout.
Document type is generally used for a large variety of business transactions that would also
have to be treated differently in document splitting.
While posting the transactions, system will check the combination of GL Account and
Document Type to arrive the splitting rules.
Example Bank Transaction posting
Document type
- Payment Transactions
The following are the splitting rules assigned to the Document Types.
Page 32 of 189
Name
Standard
Unspecified posting
Unspecified posting
Unspecified posting
Unspecified posting
Unspecified posting
Unspecified posting
Unspecified posting
Customer invoice
0001
0001
0001
0001
0001
0001
0001
0001
Standard
Standard
Standard
Standard
Standard
Standard
Standard
Standard
Customer invoice
Customer invoice
Payments
Unspecified posting
Unspecified posting
Unspecified posting
Vendor invoice
Vendor invoice
Vendor invoice
Clearing
transactions
(account maint.)
Vendor invoice
Payments
Unspecified posting
Unspecified posting
0001
0001
0001
0001
0001
0001
0001
0001
0001
Standard
Standard
Standard
Standard
Standard
Standard
Standard
Standard
Standard
0001
0001
0001
0001
0001
Standard
Standard
Standard
Standard
Standard
Unspecified posting
0001
Standard
Unspecified posting
Vendor invoice
Vendor invoice
Customer invoice
0001
0001
0001
0001
Standard
Standard
Standard
Standard
Unspecified posting
Unspecified posting
Unspecified posting
0001
0001
0001
Standard
Standard
Standard
Unspecified posting
0001
Standard
Unspecified posting
Unspecified posting
Unspecified posting
Unspecified posting
0001
0001
0001
0001
Standard
Standard
Standard
Standard
Page 33 of 189
Payment Clearing
1010
Name
Standard
Standard
0001
0001
0001
0001
0001
0001
0001
0001
Standard
Standard
Standard
Standard
Standard
Standard
Standard
Standard
0001
Standard
GL Account
Page 34 of 189
5 Master Data
7.1 FI Master Data
7.1.1
General Ledger
The basic element of the master data structure in the GL is the chart of accounts. Chart of
Account will be assigned to a Company Code. Chart of Account contains the master list of
general ledger accounts that are required for external reporting for the Company Code /
organization.
Chart of Accounts is a classification of GL accounts, through GL account grouping i.e.
Balance Sheet Accounts, PL Accounts. It provides a framework for the recording of values,
in order to ensure an orderly recording of accounting data.
The chart of accounts contains the definitions of all GL accounts that are going to be used by
the Organization.
In SAP, the GL account traditionally represents what most organizations refer to as the
natural account (e.g. travel expense, sales revenue etc). The internal/management reporting
structures such as cost centers are not embedded in the GL account. These structures are
represented in the Controlling module.
General Ledger Master Data Maintenance Functions
SAP provides the following functionality for maintaining GL account master records:
Create a new account centrally ( both COA and Company Code level)
Change an account
Display an account
Page 35 of 189
Text
Share Captial - Equity Shares
Share Captial - Share Application Money
Res & Sur - Capital Reduction Reserve
Res & Sur - Securities Premium Account
Res & Sur - Debenture Redemption Res A/c
Res & Sur - General Reserve
Res & Sur - Subsidy (State Investment)
Res & Sur - Accumulated P& L A/c
Secured Loans - Debentures
Secured Loans - Term Loans
Working Capital Loans
Hire Purchase Loans
Unsecured Loans
Deferred Tax Liability
Sundry Creditors
GR/IR Clearing Accounts
Other Clearing Accounts
Initial Balances
Outstanding Liabilities
Salary Payables
Duties & Taxes - TDS
Duties & Taxes - Sales Tax
Duties & Taxes - Excise Duty & Service Tax
Provisions - Taxation
From No.
11100000
11200000
11300000
11400000
11500000
11600000
11700000
11800000
12100000
12200000
12300000
12400000
12500000
13100000
14100000
15100000
15200000
15300000
15400000
16000000
16100000
16200000
16300000
19100000
To No.
11199999
11299999
11399999
11499999
11599999
11699999
11799999
11899999
12199999
12299999
12399999
12499999
12599999
13199999
14199999
15199999
15299999
15399999
15499999
16099999
16199999
16299999
16399999
19199999
Page 36 of 189
19299999
21199999
21299999
21399999
22199999
22299999
22399999
22499999
23199999
23299999
23399999
23499999
23599999
23699999
23700000
23800000
24100000
25100000
31000000
32000000
40100000
40200000
40300000
41100000
42100000
42200000
42300000
42400000
42500000
43100000
44100000
51100000
23799999
23899999
24199999
25199999
31099999
32099999
40199999
40299999
40399999
41199999
42199999
42299999
42399999
42499999
42599999
43199999
44199999
51199999
Page 37 of 189
Field Description
Description
Company Code
Account currency
Indicator:
Only
Manage Allows you to maintain balances only in local
Balances in Local Currency
currency
10
11
Valuation Group
12
Tax Category
Page 38 of 189
Sr. No.
Field Description
Description
13
14
15
16
Indicator:
management
17
18
Sort Key
19
20
Indicator: Posted automatically This indicator means that the account can be
only
only posted through by way of automatic
system postings. No manual entry would be
possible.
Open
Page 39 of 189
7.1.2
Customer Account
The customer master record contains all the data required to do business with the customer.
Data in customer master records also control how transaction data is posted and processed
for a customer. Individual fields within the customer master record are also used:
Change an account
Display an account
Block/unblock an account
The above operations may be undertaken at the general/company code level, the sales area
level or centrally against both levels.
The ARCH accounts receivable account maintenance will be centralized with ARCH Co SAP
Support Team, Hyderabad, and that the creation of any new accounts will go through an
approval process.
Data in the customer master is stored in 3 views:
General Data: Data that applies to all company codes and sales areas (e.g.
customers name, addresses, language and telephone data).
Company Code/Accounting Data: Data that is specific to a company code (e.g. the
reconciliation account number, payment terms and dunning area).
Page 40 of 189
Account
Group
Numbering
Scheme
From
Number
To
Number
1
2
3
4
5
6
7
8
ZE01
ZD01
ZE02
ZD02
ZE03
ZD03
ZDIC
ZDIP
Exports (Sold-to-Party)
Domestic (Sold-to-Party)
Exports (Ship-to-Party)
Domestic (Ship-to-Party)
Exports (Bill-to-Party)
Domestic (Bill-to-Party)
Inter Company Customer
Plants (For Stock Transfer)
10
20
11
21
12
22
90
09
100000
200000
110000
210000
120000
220000
900000
1000
109999
209999
119999
219999
129999
229999
909999
9999
Payment Terms
Payment terms enable the system to determine the required terms of payment automatically.
The specified terms of payment are assigned using a key. This key can be:
Stored in the master record of the customer account (in the sales view and in the
accounting view)
Entered when the logistics documents (in the sales order and the outgoing invoice,
for example) are created (or changed)
Page 41 of 189
7.1.3
Vendor Account
The vendor master record contains all the data required to do business with the vendor. Data
in vendor master records also control how transaction data is posted and processed for a
vendor. Individual fields within the vendor master record are also used:
As default values when posting items to the account. E.g. payment terms specified in
the master record are used on invoices posted against that vendor.
For processing business transactions e.g. bank details and the types of payment
method (check or bank transfer)
Change an account
Display an account
Block/unblock an account
The above operations may be undertaken at the general/company code level, the
purchasing organization level or centrally against both levels.
The Arch accounts payable account maintenance will be centralized with Arch Support
Team, Hyderabad, and that the creation of any new accounts will go through an approval
process.
Data in the vendor master is stored in 3 views:
Page 42 of 189
Company Code/Accounting Data: Data that is specific to a company code (e.g. the
reconciliation account number, payment terms, and payment methods).
Account
Group
Numbering
Scheme
From
Number
To
Number
1
2
3
4
ZDOM
ZIMP
ZCPD
ZCPI
Domestic Vendors
Import Vendors
Domestic Capital Vendors
Import Capital Vendors
10
11
12
13
100001
110001
120001
130001
109999
119999
129999
139999
Page 43 of 189
ZEXV
ZSER
ZSCV
ZTPV
ZMFG
ZFIN
ZEMP
ZINT
ZPLJ
ZMGT
ZOTV
ZPLT
Expense Vendors
Service Vendors
Sub Contract Vendors
Transport Vendors
Manufacturer
Finance Vendors
Employee Vendors
Affiliated Vendors
Plants (For Job Work)
Allied Vendors
One Time Vendor
Plants (For Stock Transfer)
140001
150001
160001
170001
180001
190001
200001
210001
220001
230001
240001
1000
149999
159999
169999
179999
189999
199999
209999
219999
229999
239999
249999
9000
Payment Terms
It is the key for defining payment terms composed of cash discount percentages and payment
periods. It is used in purchase orders and invoices.
Some of the payment terms applicable for Vendors is given below:
Payment Term
Payment Description
M001
M002
100% DP at Sight
M003
M004
M005
Payment Description
SD60
SD90
SE90
Terms of payment include settings for the payment terms, the day limit, the baseline date for
payment, and installment payments. Baseline date determines the date from which payment
terms will be calculated. The Baseline date will be defaulted from the Document Date of the
document. The Payment Due date is arrived as follows:
Page 44 of 189
Description
Check
Bank Transfer
Vendors as Customers:
ARCH has vendors as customers. Hence in the customer master data, vendor field is
updated with Vendor. And in vendor master data, customer field is updated with customer
code. By this ARCH will know the net payables/receivables.
7.1.4
Bank Accounting
Bank Accounting takes care of the transactions, which take place with the Banks the
company, is dealing with. It is further subdivided on the basis of incoming & outgoing
payments. House banks take care of all the banks with which the organization deals with on
a day-to-day basis. House bank Master records contain all information about the particular
house bank and also the Accounts maintained by the organization in the respective House
bank.
7.1.5
House Banks
A house bank is any banking institution with which the organization conducts business. Bank
master record data includes the bank key, the name of the bank, the address and country
specification. Each house bank of a company code is represented by a bank ID and every
account at a House Bank by an account ID. G/L accounts will be created and assigned for
Page 45 of 189
Account ID
Bank Key
Account No.
Branch
CA01
Fort
5001624845
Fort,
Mumbai
ALM01
Allahabad
Bank
CC01
Fort
50019150341
Fort,
Mumbai
AXM01
Axis
Bank
Ltd Fort - CC01
OD
Fort
004010300020873 Fort,
Mumbai
7.1.6
Fixed Assets
The Fixed Asset Master Data component is used for recording the master data of fixed
assets on an individual asset basis. A fixed asset is defined as an individual economic good
that it is recognized in the balance sheet at the time of closing, and is in the long-term
service of the enterprise.
Asset Classes: From an accounting point of view, the asset class is the most important
element for structuring fixed assets. Each asset must be assigned to one asset class only.
The asset class assigns the assets and their business transactions to the appropriate
general ledger accounts. Several asset classes can be assigned to the same account. This
makes it possible for fixed assets to be structured in more detail at asset class level.
Data for Calculating Asset Values
Depreciation terms in the asset master record can be specified for each depreciation area. In
order to make these specifications, the master record contains an overview of the
depreciation areas. In addition, there is a detailed display available for each depreciation
Page 46 of 189
Number
range
NR From
NR To
1000
Land Freehold
10
110000001
110999999
1100
Land Leasehold
11
111000001
111999999
1200
12
112000001
112999999
1250
13
113000001
113999999
1300
14
114000001
114999999
1350
15
115000001
115999999
2000
20
120000001
120999999
2050
21
121000001
121999999
2100
22
122000001
122999999
2200
23
123000001
123999999
2250
24
124000001
124999999
2300
Lab Equipment-LVA
25
125000001
125999999
2400
26
126000001
126999999
2450
27
127000001
127999999
2500
Safety Equipment-LVA
28
128000001
128999999
2600
29
129000001
129999999
2650
30
130000001
130999999
2700
31
131000001
131999999
Page 47 of 189
NR From
NR To
2800
32
132000001
132999999
2850
33
133000001
133999999
2900
Electrical Installation-LVA
34
134000001
134999999
3000
35
135000001
135999999
3050
36
136000001
136999999
3100
37
137000001
13799999
38
138000001
138999999
3250
39
139000001
139999999
3300
40
140000001
140999999
3400
Computers SLM
41
141000001
141999999
3450
Computers WDV
42
142000001
142999999
3500
Computers LVA
43
143000001
143999999
Vehicles SLM
44
144000001
144999999
Vehicles WDV
45
145000001
145999999
Software
46
147000001
147999999
4100
Software LVA
47
147000001
147999999
4200
Product Development
48
148000001
148999999
4300
Technology
Copyright
49
149000001
149999999
4400
50
150000001
150999999
5000
51
151000001
151999999
5100
52
152000001
152999999
320
0
3600
3650
4000
Transfer/
Patent
&
Once the asset classes are defined different asset master records will be created under the
asset classes.
Page 48 of 189
Assets Class
Company Code
Description of assets
Serial number
Location
Cost Center
Plant
Vendor Name
Room No.
Evaluation Group
Depreciation Key
Location field in master data will be used by ARCH for the purpose of entering/identifying
the physical location of asset.
Evaluation Groups: Evaluation groups can be used for reports to sort assets
according to the criteria required. You can use 4 evaluation groups. The evaluation
groups first have to be configured and then allocated correctly to the asset master
records.
The following will be the some of the evaluation groups for Arch:
Evaluation Group
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
Description
AIR COMPRESSOR
AIR CONDITIONER
AIR CURTAIN
AIR HANDLING UNIT
AMBULANCE
ANALYSER
APPARATUS
ATTENDANCE SYSTEM
AUTO DISINTEGRATION TEST M/C
AUTO TITRATOR
AUTOCLAVE
Page 49 of 189
Page 50 of 189
Page 51 of 189
7.1.7
Material Master
Material Master represent the various goods that are the subject of business activity.
Material Masters are used for goods which can be traded, used in manufacture, consumed,
or produced.
The data contained in the material master record is required for many functions like
Purchasing data for ordering, Inventory management data for posting goods movements and
managing physical inventory and also accounting data for material valuation.
Since materials are processed by various functional groups within a company and each
group will stores different information for the materials, the material master is subdivided into
information grouped by various functions or uses. Each group has a different view of the
material master record and is responsible for maintaining the data to support its function.
The valuation area is the organizational level at which material is valuated. When stock is
valuated at plant level, you can valuate a material in different plants at different prices. For
Arch, each Plant will represent a Valuation Area. Existing Material Types and Valuation
Classes are used for the valuation area of Company code Arch.
The Accounting views contain important data which is relevant to the Financial Accounting.
Consequently, only the Finance Department will have the authorization to maintain this view.
Important fields
Price Control - indicates the price control used to valuate the stock of a material. In the SAP
System, there are two types of price control:
Page 52 of 189
If a material is assigned a standard price (S), the value of the material is always calculated at
this price. If goods movements or invoice receipts contain a price that differs from the
standard price, the differences are posted to a price difference account. The variance is not
taken into account in valuation.
Valuation using a moving average price results in the following:
The price in the material master is adjusted taking into account the delivered price.
If a material is assigned a moving average price (MAP), the price is automatically adjusted in
the material master record when price variances occur. If goods movements or invoice
receipts are posted using a price that differs from the moving average price, the differences
are posted to the stock account; as a result, the moving average price and the value of the
stock change.
For Arch all the materials i.e. Raw materials, packing material, spares will be valued using
Moving Average Price and Lab Chemicals will be valued at Moving Average.
Valuation Class is used to combine materials for assigning G/L accounts so that you do not
have to manage a separate stock account for each material. Based on the Material Types
the Valuation class will be assigned in the Material Master. Valuation Class determines which
stock account and offsetting account to be posted based upon goods movement.
Page 53 of 189
7.1.8
Sl.No Transaction
T.code
1
Create/ Change / FS00
Display / Block GL
Account
4
5
7.1.9
Input
Output
User Role Controls
GL
Account General
FI Master GL to
be
Number,
Ledger
User
created under
Account
Account
existing
Group,
Text, created
Account
Sort Key, Field
Group
Status Group
Customer Account FD01/FD02 Account Group Customer
FI Master Account
create/Change/
/ FD03 / Company
Account
User
Group
and
Display
/ FD05
Code
Reconciliation
Block/Unblock
Name, Recon
Account
customer
(FI
Account,
Customers)
Payment terms
Vendor Account FK01/FK02/ Account Group Vendor
FI Master Account
(FI
Vendors) FK03
/ Company
Account
User
Group
and
Create / Change / FK05
Code
Reconciliation
Display
/
Name, Recon
Account
Block/Unblock
Account,
Vendor
Payment terms
House
Bank FI01/ FI02 / Bank Country House Bank FI user
Master Create / FI03
and Bank Key key
Change / Display
Asset
Master AS01
/ Asset
Class, Asset Master FI Master Asset Class
Create / Change / AS02
/ Text,
Cost
user
Display
AS03
Centre
Sl No
1
Module
CO
MM
SD
Details
To create the Primary Cost Elements, it is required to have the
corresponding General Ledger Account in the FI System.
Cost center and Profit center will be assigned corresponding Company
code
Material Master is being created in Material Management module.
Accounting 1 and Accounting 2 views will be extended on need basis.
Vendor Masters created in Material Management Module can also be
used for postings directly in Financial Accounting since Company code
relevant data will be maintained.
Customer Masters created in Sales and Distribution module can also
Page 54 of 189
7.2
CO Master Data
The Master data for Controlling, the following items are covered.
Ref No.
Description
Cost element
Cost center
Activity type
Internal Order
Profit Center
10
11
Material Master
7.2.1
Cost Elements
The cost element tells the nature and origin of cost. Cost Element is used for entering all
costs within the entire cost accounting system.
Cost element is of two types
Primary cost element: A primary cost element is an item in a chart of accounts, which is
used within controlling area to record the value-assigned to cost objects.
Secondary cost element: Secondary cost element exists only in Controlling. Second Cost
Element will be used to allocate costs within CO. Secondary cost element will not have any
link to GL in financial accounting.
Important Fields in Cost Elements
Page 55 of 189
Description
Primary costs/cost-reducing revenues
Revenues
Sales deduction
The Cost element category for the Secondary Cost Elements differ from primary cost
element. For secondary cost element below categories are used.
Cost Element Category
31
42
43
Description
Order/project results analysis (For Order Analysis)
Assessment (Allocation purpose)
Internal activity allocation (Activity Type purpose)
Page 56 of 189
7.2.2
Cost Element Groups
Cost elements will be grouped for the purpose of allocation, planning, analysis and reporting.
One cost element can be assigned to multiple groups, based on the reporting requirements.
7.2.3
Cost Center
Cost center is the smallest organizational unit within the companys overall organizational
structure which collects cost for the purpose allocation, analysis and reporting.
Creation of new Cost Center: Whenever a new Cost Center is to be created, the Cost
Center Group and the Profit Center for the same would have to be determined.
Page 57 of 189
Cost Center category: Cost center categories determine the type of activity.
Department: In this field, enter the name of the department to which the cost center
belongs. Then it can be used for evaluations
Hierarchy Area: under which hierarchy group the cost center going to be creating.
Profit center: The actual postings made to the Cost Center are updated to this Profit
Center.
7.2.4
Cost Centre Groups
To combine similar cost centers to form cost center groups. You may then combine similar
groups into further groups to create a cost center hierarchy
You can use cost center groups:
Distribution
Assessment
Page 58 of 189
7.2.5
Activity Types
The Activity Type classifies the specific activities that are provided by one or more Cost
Centers. If a Cost Center provides activities for other Cost Centers, Orders, Processes, etc.
then it implies that its resource is being used. The costs of these resources need to be
allocated to these receivers of the activity. Activity Types serve as the tracing factors for this
cost allocation. To plan and allocate the activities, the system records quantities that are
measured in activity units.
Important Fields
Activity Unit: For production related activity type unit of measure hour is used.
Cost Center categories: Indicator determining for which cost center types an activity
type is allowed for planning and as a sender in internal activity allocation.
Activity Type
1100
Machine Hours
1200
Labour Hours
1300
Quality Hours
1400
Power Units
7.2.6
Activity type groups
Activity type groups will be created for the purpose of analysis and reporting. The following
are the Activity Groups for Arch:
Activity Type group
1000
Name
Arch - Activity Group
7.2.7
Statistical key Figures
Statistical key figures serve as a basis for internal allocations and as references in the key
figure analysis framework.
The following are the Statistical Key Figures will be used by Arch:
Statistical Key Figure
1400
Name
Power units
Page 59 of 189
7.2.8
Internal Order
Internal Orders are used to plan, collect and settle the cost of specific activity or task. They
can be monitored through their entire life-cycle i.e. from their initial creation, the planning and
posting of actual costs and the final settlement wherever required.
Statistical Internal Orders can be used for monitoring objects in Cost Accounting whereas
Real Orders can be used where the costs collected are to be capitalized.
7.2.9
Profit Centers
A profit center is a management oriented organizational unit used for internal controlling
purposes. Dividing company into profit centers allows to analyze areas of responsibility and
to delegate responsibility to decentralized units, thus treating them as companies within the
company.
Important fields in Profit Center
Profit Center Group: The standard hierarchy is a tree structure which displays the
organization of all the profit centers in one controlling area. Each profit center must be
assigned to a node in the standard hierarchy for its controlling area. This ensures that the
standard hierarchy contains all the profit centers in the controlling area.
Company Code: Company Code 1000 will be assigned to all Profit Centers of Arch.
Some of the Profit Centers for the Arch Pharmalabs Limited are as under:
Company Code
1000
1000
1000
1000
1000
Profit Center
110000
110010
110020
110051
110052
7.2.10
Material Master - Costing Views
Material master will be created part of the Logistics module. Some of the important fields
need to be updated in the Material master; the same has been discussed below.
Page 60 of 189
Define calculation bases for determination of overhead rates for particular material
groups.
Create rules for activating work in process for each material group.
The following are the Origin Groups assigned in the Material Master:
Z001 Key Material: Based on this key, Cost of the materials need to be identified in a
different line item, in cost component structure.
Variance Key: A key that ensures the object is selected during variance calculation. Also
controls whether scrap costs are reported in a separate category.
Variances can only be calculated for the orders for which a variance key has been entered.
This key is defaulted through the costing view in the material master record. If the variance
key is activated variance calculation in the variance key, the value of the scrap is calculated
at target cost and subtracted from the actual costs before the variances are determined.
Standard Variance Key 000001- Variance Calculation for orders will be used.
Costing lot size is used as the basis for costing of the material. The base quantity of the Bill
of Material should be maintained as the Costing lot size. Fixed cost will be identified for the
Costing lot size.
Page 61 of 189
Profit Center- In the material master profit center will be assigned. Based on the
assignment, while posting the financial transactions for the material movement, system will
determine the Profit Center, automatically from the Material master. Based on the Plant /
material / product segment,
Master.
7.2.10.1
Raw / Packing and Lab Chemicals
These materials are procured from the External vendor through Purchase order Process.
The material can be procured different source of supply and need to be classified based on
its duties / tax payment status. To meet this requirement, these materials are maintained
based on the following split valuation types:
Raw Materials
o Domestic purchase
o Domestic Excise Paid (excise inventorized)
o Imported purchase (Customs duty paid)
o Imported purchases (against advance license No customs duty payment )
Lab Chemicals
o Domestic purchase
o Imported purchase
Packing Materials
o Domestic purchase
The price control for all the above materials are V Moving Average Price.
7.2.10.2
Semi-finished and Finished Goods
In general goods which are manufactured internally are known as Semifinished goods or
Finished goods, based on its stage of manufacturing. In case of Arch some of the materials
are manufactured internally and purchased from external source. In view of this it is decided
to use a common material code, whether manufactured or procured. To identify the source of
the material, it has been decided to have the split valuation for the materials.
Page 62 of 189
Inhouse Manufacturing
-S
-V
Domestic Purchase
-V
Imported Purchase
-V
In case of Finished goods the following are the split valuation types and their price control as
follows:
Inhouse Manufacturing
-S
Domestic Purchase
-V
Imported Purchase
-V
7.2.10.3
Allied Products
Arch procuring some of the materials, based on the market demands and supplying to
customers and these materials are not manufactured internally.
identified as Allied Products and received in Depots and sold to the customers from depots.
In case of Allied Products the following are the split valuation types and their price control as
follows:
Domestic Purchase
-V
Imported Purchase
-V
7.2.10.4
Stores and Spares / Operating Supplies
Spares and Operating supplies are in the nature of maintenance materials. Some of the
spares and consumables are being stored in the stores and consumed based on the
maintenance schedule or breakdown maintenance. Some of the materials are used as
regular consumption i.e. Consumables, Fuel, Coal, etc.,
In case of Stores and Spares the following are the split valuation types and their price control
as follows:
Domestic Purchase
-V
Imported Purchase
-V
Page 63 of 189
Domestic Purchase
-V
Imported Purchase
-V
-V
7.2.10.5
Capital Inventory
Some of the materials, for construction of fixed assets and maintained as inventory, in the
stores. As and when required by the Project Engineering Department, stores department will
issue the goods to the project. All these nature of materials are created under the material
type Capital inventory. These materials can be procured locally and imported.
In case of Capital Items the following are the split valuation types and their price control as
follows:
Domestic Purchase
-V
Imported Purchase
-V
7.2.10.6
Split
Mat
Type
Mat Description
Val Type
Mandatory
ZRAW
Raw Material
Domestic
Domestic
Paid
Mandatory
ZLAB
Mandatory
ZPKG
Mandatory
ZINT
Mandatory
ZFIN
Val
Type
Codes
DOM
Excise DOMEP
Price
Val
Control Class
V
V
1000
IMP
IMPAL
DOM
IMP
DOM
IMP
MFG
V
V
V
V
V
V
S
1050
JOB
DOM
IMP
MFG
DOM
IMP
V
V
V
S
V
V
3050
3100
3150
4000
4050
4100
1100
1150
1200
1250
3000
Page 64 of 189
Optional
Scrap
ZSPA
Stores/SparesEngg Goods
ZOPS
Mandatory
7.2.11
ZSRP
ZCAP
Operating
Supplies
Capital Materials
DOM
SUPERSEDES: N/A
V
4500
Import - Alp
IMP
V
S
4550
3900
Domestic
DOM
6000
Imported
DomesticConsumables
IMP
DOM
V
V
6050
6100
ImportedConsumables
IMP
6150
Power/
Fuel POW
Diesel,
LDO,
Furnace oil,Coal,
different
Mat
Codes
6500
Domestic
Imported
V
V
7000
7050
DOM
IMP
Sl.No Transaction
T.code
1
Primary
Cost KA01
Element
KA02
KA03
2
Secondary
Element
Cost KA06
Delete
Element
Cost KA04
Cost
Center OKEON /
Standard
OKENN
Hierarchy
Cost Center
KS01 /
KS02 /
Input
Output
User Role Controls
/ GL
Account Primary Cost CO User
GL account
/ Number
Element will
must
be
Validity Period be created
FI Master created in the
Cost Element
User
system
Type
CO User
No
GL
Account
created with
same ID
Cost Element Cost Element CO BPO
No postings
Number
will
be
should made
deleted
CO User
/ Group ID
CO User
/ Group Name
Assign
the
Cost Elements
Controlling Are Controlling
CO BPO
Area
Standard
Hierarchy
External
10 Cost Center CO User
digit Code
is created or
Cost
authorization
Page 65 of 189
Page 66 of 189
7.2.12
Sl No
1
Module
FI
MM
Details
To create the Primary Cost Elements, it is required to have the
corresponding General Ledger Account in the FI System.
Cost center and Profit center will be assigned corresponding Company
code
Material Master is being created in Material Management module.
Costing View will be extended on need basis
General Ledger is the sub-module in which all of the financial accounting data for the legal
entity is recorded either manually or automatically through integrated processes. Business
transactions with a financial accounting impact are posted to the General Ledger submodule on a real-time basis either directly or through integration from other modules and FI
Sub-modules. Posting of entries in the general ledger are made using the accounts as
defined in the Chart of Accounts. The Financial General Ledger will allow Arch to:
Automatically and simultaneously post all sub-ledger items in the appropriate general
ledger accounts (through reconciliation accounts)
Real time evaluation of and reporting on current accounting data, in the form of
account
The general ledger will serve as a complete record of all business transactions for Arch. It is
the centralized, up-to-date reference for the rendering of accounts. Using the general ledger,
Page 67 of 189
Arch will post journal vouchers directly in the general ledger, which do not originate from a
sub-ledger or another module. Such entries could be to make corrections to the general
ledger or part of the period end process. ARCH will be able to post, Valid documents into
SAP System.
For posting a Journal Voucher, the following minimum information will be required in the
document header:
Posting date: This is the date on which the transaction is posted in the General
Ledger. It determines the posting period.
Document date: Issue date of the original document (not necessarily the same as
the posting date). For invoices it is called the invoice date.
Reference and Document header text will be additionally required for specific
Document Types.
Each Journal Voucher will have at least two line items, a minimum of one debit and one
credit.
Every line item contains a:
Posting key - a two-digit numeric key that controls how document line items are
entered and posted. The posting key
Specifies the account type i.e. Customer, Vendor, General ledger account, Asset
and Material.
Contains Field Status definitions that are used as a factor in determining the
screen layout while posting transactions.
Page 68 of 189
Amount All amounts shall be converted to the Company Code currency, if the
Document Currency is a foreign currency by the system automatically.
Since it is posted at the Company Code level, where balanced financial statements are
ensured, a document can only be posted if the total debits equal to the total credits. In the
system, a document is created for every business transaction and receives a unique
document number. Document number ranges are defined per company code and are
assigned to each document type in the system. Number ranges will be defined for each
fiscal year for financial documents.
8.1.2
Parking and posting Parked documents
Arch will be using the Document Park and Post functionality as a measure of introducing
internal control procedures. Both complete and incomplete documents can be parked and
then posted at a later date by a different user.
Parking Documents
Information entered as part of a parked document is only checked as to whether it exists.
Only a few fields - for example the posting key and account number will be the required
entry fields.
The authorization checks carried out for document parking are basically the same as those
made for standard document entry and processing. Instead of the activity "posting", the
activity "parking" is required for document parking.
Page 69 of 189
Down Payments
Vendor/Customer clearing
Page 70 of 189
8.1.3
8.1.3.1
Sample Documents
This is a template accounting entry. This helps the user in having a pre- entered accounting
entry. The Document and Posting dates can be changed at the time of posting the
document. Such sample transactions may be used for repetitive kind of transactions to save
Page 71 of 189
8.1.3.3
Recurring Document
Recurring Documents are created for processing transactions that are of routine and
repetitive nature. A recurring document needs to be created as a reference document. For
every recurring entry, a first run date and repeat run timeframe need to be given. At any point
in time, recurring entries pertaining to a specified period may be processed using options of
periodic processing.
Alternatively, a time schedule for processing these transactions may be entered and system
would automatically carry out the processing of such prescheduled transactions.
Recurring entries may be used for transactions recurring at periodic intervals.
In ARCH recurring entries can be used for recurring transactions like insurance, Interest and
rent etc.
Recurring documents can have two types of Schedule posting dates:
Page 72 of 189
Date Schedule If the posting has to be done on irregular intervals, i.e. date is not
the same for all the posting periods, Run Schedule will be created, with the dates
actually to be posted. Based on the dates mentioned in the run schedule, system will
post the documents. Posting date determined based on the dates specified in rn
schedule.
8.1.4
Fast Entry Screens
Fast entry screens are used for quick entry of transactions having multiple line items. Fast
entry screens may be best used when majority of the fields are suppressed for a particular
business process transaction. This would simplify the procedure of document entry by
adopting a simplistic screen for document entry.
Entries in the fast entry screens would have similar validations at the time of posting as
compared to a normal transaction entry screen. The users can use the fast entry screens for
transactions with multiple line items.
Fast entry screens may be best utilized for general ledger / customer / vendor transactions
having multiple line items.
The following layout can be used for Arch for fast entry screen:
Layout
ZARCH
8.1.5
Description
Fast entry layout screen for Arch
Document Change
Some of the fields in the posted accounting document can be changed i.e. Header Text, Line
Item Text, Assignment Field, etc. Some of fields, in the posted accounting document, system
will not allow any changes i.e. Posting Key, Amount, Cost Center, Profit Center, etc. For
control purpose, all fields are being in display mode except Line item text and Document
Header reference (if the document is not cleared).
Page 73 of 189
User can reverse the posted document using the document reversal option. It is possible for
a user to make an error while posting. In order to provide an audit trail of the correction, the
user must reverse the document using the Document Reversal option.
The system provides a function to reverse G/L, A/R and A/P documents both individually or
in mass. When reversing a document, a reversal reason code must be entered to explain the
reversal. The reason code also controls if the reversal date is allowed to be different from the
original posting date. Documents with cleared items cannot be reversed. The document
must first be reset.
Document reversal is possible in SAP only if
All entered values (such as cost center, and tax code) are still valid
If a line item from a source document has been cleared, a reversal can only be carried out
after the clearing is reset.
Mass Reversal can also be done for a particular set of documents.
8.1.7
Open items reflect unfinished transactions. For example, a Liability that has not been settled
remains in the Liability account as an open item until it is settled. The open items of an
account can only be cleared once posting an identical offsetting amount to the account is
made. In other words, the balance of the items assigned to each other must equal zero.
During clearing, the system enters a clearing document number and the clearing date in
these items.
Open item management is automatically set for customer and vendor accounts. For GL
accounts, however, the open item management option has to be set in the master record
before any postings are done to the GL Account.
Open item management would be set for the following GL accounts:
Page 74 of 189
Open items of an account can be cleared manually using the Account Clearing function, or
they can be cleared automatically by the system. Automatic clearing is especially useful for
clearing accounts in the GL account area.
Chart of Account
accounts
Type
From
Account
To
account
Criterion
Remarks
1000
1000
1000
1000
1000
1
A
A
1
999999999
Z
Z
29999999
ZUONR
ZUONR
ZUONR
ZUONR
XBLNR
D
D
K
S
S
8.1.8
Financial Statement Versions
The financial statement version forms the basis for creating a balance sheet and profit and
loss statement. The SAP standard Financial Statement analysis allows for the comparison of
financial statements from two time periods, and the determination of the differences in the
individual financial statement items. Financial statement can be carried out for the following
time periods:
Year comparisons
Half-year comparisons
Quarterly comparisons
Monthly comparisons
In addition to financial statement, SAP provides a standard Balance Display report (Trial
Balance). This report facilitates the evaluation of transaction figures.
The following are the Financial Statement Versions for ARCH:
Sl. No.
Chart of Accounts
Page 75 of 189
The following are the operations that are to be covered as a part of closing operations
The operations shall cover:
Monthly closings
Yearly closings
8.1.9.1
Procedures
2
3
Post the Provisional entries using sample document program and account
assignment model
Complete all the outstanding journal entries related to month end closing.
Asset Accounting
Project AUC Posting
Capitalize AUC Assets to Regular Assets
Depreciation Posting
Evaluate all Clearing Accounts (target to keep Zero balance in clearing
accounts)
GR/ IR clearing
Bank Sub-Accounts
Cash to Asset Clearing
Cash Bank Clearing
Cenvat Clearing
Page 76 of 189
Step
Procedures
8
9
Trial Balance
10
10
8.1.9.2
Year end closing
Year-end closing comprises all activities involved in closing the financial year apart from
Month-end closing activities.
The check list for year-end process will be documented after the Realization Phase of this
project.
The below proposed flow for year-end processing shall be used as a guideline for this
blueprint as the activities may not be finalized until Realization phase.
Process Overview Explanation
Step
Procedures
AUC Tracking
Trial Balance
Page 77 of 189
8.1.10
SUPERSEDES: N/A
GL Process Steps
Main process
Description
1. General
2.
Parking
the document:
3. Sample
Document
of
Transaction
Process of SAP
code
FS00
F-02
FB03
FS10
authorization
F-65
is
every
FBV0
F-01
month
of
F-02
recurring
F.15
F.14
will be used.
Whenever there
is
FBD1
/ accrual
deferral
deferral
documents
reverse
the
Reversing
the
accrual
deferral document
transaction.
of Whenever there is an Individual reversal
documents
error while posting SAP Mass reversal
Cleared item reversal
offers a methodology to
6. Reversal
FBS1
reason
is
F.81
FB08
F.80
See
cleared
items and do
un clearing and
reverse
it,
Page 78 of 189
Description
Process of SAP
code
FBRA
(to see
recently
cleared items),
ranges
were
reversal reversal
Reversal of reversal
documents
from
FI
as
per
By using SAP we can see
given
7. General
Ledger
account
analysis
for
FAGLL03
the
layout
of
accounts
clearing
F-02
center etc.,
Open
items
8. Account
F.81
in
ex.
FAGLB03
GL
Like
Without
Specification
of
Clearing Currency
F.13
ascending / descending
9. Foreign
currency
revaluation
transaction
represented
in
loss
or
F-02
the
FAGL_FC_VAL
OB59
profit
Repayment
(outgoing F-07
payment)
Revaluation of FC Transaction
FAGL_FC_VAL
can
sent
be
to
Page 79 of 189
Description
Process of SAP
SUPERSEDES: N/A
Transaction
code
those GL accounts to
Based
company
code
maintainonthe
balances.
or document type wise
payables
can
regrouped
be
receivables
to
10. Regroup
payables
receivables
Customer
Regrouping
F101
balance
Use
F101
to
to
group
payables / receivables.
11. Maintain
GR/IR
Clearing
MR11
Account
Whenever it is required to
accounts and FS00
calculate interest on GL Define GL
accounts
an
interest attach the interest indicators
12. Interest
calculation:
indicator
is
attached
with
set
the
and
GL
8.1.11
Sl No
1
Module
FI
Details
To create the Primary Cost Elements, it is required to have the
Page 80 of 189
MM
8.2
Accounts Payable
In SAP, Accounts Payable works on sub-ledger concept and each vendor account is
assigned to a General Ledger Account. Such GL Account is updated as and when
transactions are posted to the Vendor Account. Such GL Accounts purpose will be to collect
the transactions posted into vendors that are link to it (through Vendor Master Record). Such
GL Accounts will not allow to post any direct entry into it.
Accounts Payable is the sub-module in which the financial accounting transactions involving
vendors and employees are recorded and administered. All postings in Accounts Payable
are recorded simultaneously in General Ledger. The components of Accounts Payable will
be closely integrated with components of Materials Management to support an automated
Procurement Cycle.
Primary tasks required for managing Accounts Payables include:
Ability to use systematic verification of invoices against purchase orders and goods
receipts
Material Vendors
Page 81 of 189
Service Vendors
Employee Vendors
Bills of Exchange
Transport Vendors
8.2.1
Vendor Down Payment
Advance payments will be made according to the terms of payments with the vendor. The
advance payments made to the vendor will be tracked as distinct from the normal payments
made to the vendor. The posting for down payments will be carried out to a G/L account
other than the Reconciliation GL Account assigned in the Vendor Master, which is called
Special GL account.
Special GL Indicator
A
B
Text
Down Payments other than Capex
Down Payments-Capital Items
8.2.2
Down payment request
A Down Payment Request is raised by the authorized person requesting for down payment.
Based on the request, a down payment may be released to the particular vendor and
request item is cleared.
When posting in SAP, processing of a down payment involves a number of steps:
All down payments to Vendors can be paid only with reference to Down Payment Request
for the same or can be made down payment direct without reference to Down Payment
request. These Down Payment Requests shall identify the Vendor to whom the payment is
to be made, the special G/L indicator, the amount and the requested date for payment. The
Page 82 of 189
8.2.3
Page 83 of 189
In this case, there will not be any three way match and expenses will be posted directly from
the Vendor invoice itself. An FI invoice entry in SAP is made through transaction code FB60
or F-43 without reference to Purchase Order.
TDS will be calculated automatically by the system if applicable and on the basis of tax
codes assigned in Vendor Master code can be posted to TDS Payable account at the time of
posting of invoice/credit memo.
ARCH receives Vendor Invoices in respect of expenses for which Purchase Orders are not
created. These Invoices would be accounted for directly in the FI Module without any
procurement process. Since there are no preceding documents like Purchase Orders,
Goods Receipt / Service Entry Sheet, the Invoice would be physically verified and approved
by the concerned Department Head responsible for incurring the expense.
For posting a Vendor Invoice, the following minimum information will be required in the
document header:
Vendor Code
Posting Date: This is the date on which the transaction is posted in the General
Ledger and vendor sub ledger. It determines the posting.
Document date: Issue date of the original document (not necessarily the same as
the posting date). For invoices it is called the invoice date.
Reference: The Invoice No. (As mentioned by the Vendor in the Invoice) shall be
entered as Reference and the system shall check if an earlier Invoice has been
Page 84 of 189
Document type
Currency
G/L Account number: The G/L Accounts created for Arch in the operating Chart of
Accounts 1000.
Amount: All amounts shall be converted to the Company Code currency INR if the
Document Currency is a foreign currency.
Additional assignments including Cost Center would be required depending on the G/L
Account used. The Assignment field (alphanumeric, up to 18 characters) is updated
automatically with the data from the field referenced in the Sort Key field of the general
ledger account. A value in the Assignment field can also be manually entered.
8.2.4
Goods Receipt based Vendor Invoice Verification
The main task of the Invoice Verification component is to complete the procedure of
materials procurement by posting the vendor invoice and to pass on information concerning
the invoice to Financial Accounting and subsequent applications. Invoices that originate in
procurement of services can also be processed.
ARCH will use GR based invoice verification for all Domestic procurement processes.
An Invoice against a Purchase Order will be processed with reference to the Purchase Order
Number or the Delivery Note. An invoice for a service will refer to a service entry sheet.
Goods-receipt-based Invoice Verification must be defined in all purchase orders. Each
invoice item can then be matched up uniquely with the goods receipt item.
All deliveries or services provided by a vendor can be settled in a single invoice. On the item
list all purchase order items that match the reference allocation and that are ready to be
invoiced will be suggested.
Page 85 of 189
Posting Date
Invoice Amount
The following information will be then copied from the Purchase Order:
Invoice items
Quantity, Amount
Tolerances limits may be specified for different types of variances which are defined in the
various Tolerance Keys. When processing an Invoice, each item shall be checked for
variances between the invoice and the Purchase Order or Goods Receipt.
In the material master defined that the Goods Receipt of the material is subject to inspection
then the Invoice for the material should be blocked for payment due to Quality
Inspection/usage decision.
Page 86 of 189
Double Invoice Check: Double Invoice check can be marked in Vendor Master and
the system will check for the incoming invoices and credit memos for
double/duplicate entries at the time of entry.
In checking for duplicate invoices, the system compares the following characteristics
default:
Vendor
Company Code
Page 87 of 189
Page 88 of 189
8.2.5
Purchase Orders in foreign currencies are created for imports of Raw material, or semifinished goods and capital assets. In case of Invoice Verification in respect of imports, the
currency of the document is determined from the Purchase Order currency. The exchange
rate differences are calculated from the exchange rate at the time of the goods receipt and
the exchange rate at the time of the invoice receipt. The difference between them will be
automatically calculated and posted to separate G/L Account so that the amounts posted in
Local Currency to GR/IR Clearing Account are identical.
Custom duty paid on the imports purchases is added in the value of the raw material. Also
other charges, related to the delivery, like transportation, clearing agent charges are added
to the value of material.
8.2.5.1
Page 89 of 189
Page 90 of 189
8.2.5.2
Duty Payment
Purchase order in the name of bonding vendor with two line items, one is for transfer
and another for returns
8.2.6
Invoice for Delivery Costs
Freight charges are sometimes planned in the purchase order. More often, they are not
known in detail when the purchase order is created and are entered only in Invoice
Verification on the basis of information in the invoice. Therefore, delivery costs can be
divided into:
Planned delivery costs which are entered at item level in the Purchase Order
For planned delivery costs, postings will be made to the GR/IR clearing account at goods
receipt. These postings are cleared when the invoice is posted.
Unplanned delivery cost will be posted to separate expense accounts when the stock is not
available.
8.2.7
In normal business transactions, there are instances whereby vendors will send credit
memos in order to reduce invoices. Such cases might arise due to incorrect invoiced amount
or rejection of goods. A credit memo is then required to substantiate the adjustment.
Page 91 of 189
Being an adjustment entry, credit memo shall affect Financials module only unless the
adjustment is related to MM such as good return etc.
The processes are similar to invoice processing. Only the accounting treatment will be
different. In SAP for only value related adjustment credit notes, FI can pass direct adjust
entry with reference to the particular invoice document. When the goods are rejected, the
process of credit note related to quantity and value is routed through Materials Management
and this process is similar to vendor bill booking process through logistics invoice
verification.
booking.
8.2.8
ARCH has various types of transaction excluding salary payments with its employees. For
the purpose of recording these transactions separately, the employees shall be created as
Vendor Accounts.
Since the majority of transactions with employees are in the form of advances related to their
carrying out their official duties, the normal reconciliation account for the Employee Vendor
Accounts shall be Employee Advances. Special G/L Transactions would be used for the
purpose of tracking different advances.
The following Special GLs identified for employee advances tracking:
Special GL Indicator
1
2
3
8.2.9
Description
Salary Advance
Travel Advance - Domestic
Medical / other Advances
Payments to Vendors
Payments can be manual payments and automatic payments from time to time to pay the
outstanding Vendor Invoices which are due for payment. If the outgoing payment involves a
payment in foreign currency, the defaulted local currency would have to be changed to the
foreign currency being used for payment. The exchange rate maintained as on the Posting
Date which is defaulted can be changed if the buying rate is different.
Page 92 of 189
Manual payment (Write the check manually and post the corresponding accounting
entry into the Vendor account and bank account)
Post + Print ( Select the House Bank, Payment Method, Vendor, Open Item. Based
on which System will post the accounting document and print the check)
Automatic Payment (Based on the house Bank and Range of Vendors, system will
select the open due items for payment. Post vendor wise accounting entry and print
the check correspondingly Vendor wise. If the payment method is bank transfer,
system will not print the check and it will generate the DME file)
If the payment is being made through the printed check the following Header Data would be
maintained first
i.
ii.
iii.
iv.
The bank sub-account would be determined automatically from the House Bank.
Both normal open line items and special G/L line items can be selected while making the
payment. Additional selections can be made based upon specific fields including Amounts,
Document Number, Reference, etc. Additional field of Net Due Date will be available in the
display and for sorting so that the open items can be sorted based on their due dates.
Any under-payment or over-payments within the tolerance limits shall be accounted for in the
specified G/L Accounts. Similarly, in the case of payment in foreign currency any gain / loss
between the exchange rate for the payment and the original / revaluated open item will be
posted to separate Gain and Loss on realized foreign exchange G/L Accounts.
Page 93 of 189
Bills of Exchange
These
transactions are maintained independently of other transactions in the subsidiary ledger and
are posted to an alternative reconciliation account in G/L. This allows the user an overview
of Bills of Exchange payable at any stage.
Step 1:
Vendor Invoice
ARCH post a vendor invoice through FI transaction or MM Transactions.
Step 2:
Step 3:
Description
Bills of Exchange
Page 94 of 189
These
transactions are maintained independently of other transactions in the subsidiary ledger and
are posted to an alternative reconciliation account in G/L. This allows the user an overview
of retention money payable for each Vendor.
Special GL Indicator
H
8.2.12
Description
Retention Money
In some of the cases, Post dated cheques will be issued to vendors against supply /
services. In some cases the Checks issued to Regional office, to use them in case of
emergency or payment of duties. The following are options available:
Through Special General Ledger Transaction clear the Invoice and post PDC Open
item to Vendor
Post the payment document with a posting date as Post dated check date
Post dated cheques can be routed through Special General Ledger Transaction clear the
Invoice and post PDC Open item to Vendor:
Make document posting with post with clearing transaction with special GL
indicator(T):
Dr. Sundry creditor account
Cr. Sundry Creditors PDC account
On PDC due date: Make payment entry with bank GL. The following entry will be
posted:
Dr. Sundry Creditors PDC Account
Cr. Bank cheque issue account
In the above scenarios, whenever the PDC is accounted, Vendor open items will also
be cleared, so that duplication of payment can be controlled.
Page 95 of 189
In case of checks issued to Regional office (blank value) or vendors (not over amount), will
be posted into the system as a Noted Items. So that user will get the track of the checks
issued. On obtaining the correct payment amount the noted item will be reversed and normal
payment accounting document will be created.
8.2.13
Correspondence
The account statement created for vendors is an extract from the Vendor account,
which enables to check the items for information purposes. The account statement
displays the balance carried forward, all items in the chosen period and the closing
balance of the account.
The open items list is a special form of account statement. It is also sent to the
Vendors for verification or information purposes. The open items up to the chosen
key date are displayed in this list.
Both letters contain the document number or reference document number, the
document date, the document type, the currency and the amount for every item as
well as the balance of the open items at the key date.
Ageing of Vendor accounts will be done from invoice date(s) of open invoices
following standard SAP application. Ageing of unadjusted Debit notes may also be
done by using separate filter by document type in the Vendor account.
8.2.14
Closing Operations
Objective
The following are the operations that are to be covered as a part of closing operations
The operations shall cover:
Monthly closings
Yearly closings
Page 96 of 189
Once all parked documents are completely posted and payments for the month are
completed, the posting period for vendors can be closed. This is to prevent the occurrence
of back posting invoices to the previous period after reports are generated.
Before posting period can be closed, other month end processing activities such as
executing the recurring program need to be performed if applicable.
Opening the new period and closing the previous period are two parts of the closing
procedure.
In SAP closing of activity is centralized and vendor posting can be blocked for all the
location after completing the vendor related transactions for that month. This will avoid delay
in closing the month end and results in streamlining of closing activity.
Month-end closing comprises all activities involved in closing a posting/accounting period.
Accounting period is a division of a companys fiscal year. The number of periods and
definition of period are to be determined during configuration.
Each posting into the system must be associated with an accounting period. This is to
ensure that each transaction can be reported in the corresponding period. In the same
token, periods must be controlled to ensure validity of the reports.
The below proposed flow for month-end processing shall be used as a guideline for this
blueprint.
Process Overview Explanation
Step
Procedures
Accounts posts /
deletes the
outstanding
parked documents
AP Ageing
Vendor Balances
Page 97 of 189
Step
Procedures
8.2.14.2
At the end of the fiscal year, carry forward program is required to be executed to carry
forward the vendor and vendor account balances to the new fiscal year. After running
the carry forward programs, when a transaction is posted to the previous year, the account
balances in the current year are immediately updated automatically. Balance carry forward
program is done after entries are completed.
In SAP year end closing is similar to the month end process with additional activity of carry
forward of balances to next year. The advantage of this is even after balances are carry
forwarded to next year, any entries to previous year will automatically update the opening
balance of next year.
Year-end closing comprises all activities involved in closing the financial year apart from
Month-end closing activities.
The below proposed flow for year-end processing shall be used as a guideline for this
blueprint.
Process Overview Explanation
Step
Procedures
applicable.
After completed all the additional postings. Close the posting period / fiscal
in special
period,
if
year and open the new period / Fiscal year. System allow for the current
4
AP Ageing
Vendor balances
Page 98 of 189
8.2.15
AP Process Steps
Main process
Description
Transaction
Process of SAP
code
Creation of GL accounts FS00
(for all sundry creditors,
inventories etc)
Creation
of
Vendor
GL
&
Withholding
tax
Attach
withholding
codes
to
account
Payment
2. Advance Payment
the
tax
vendor
posting
(if
FI
posting
F-43
FK10N
3. Banks:
XK03
is XK02
vendors)
To See the party wise
XK02,
master
Invoice
When
XK01,
F-49
F-48
F-43
F-54
F-44
cleared.
Payment to Vendor by Creation of check lots
FCH1
Payment through bank
F-53
Check
Manual check updating or FCH5 or F110.
when automatic payment
Page 99 of 189
Description
Process of SAP
program
is
SUPERSEDES: N/A
Transaction
code
configured
FCHN
check FCHR/FCH6
encashment date
Un-issued
check FCH3
cancellations
Issued
check FCH8.
cancellations
By using SAP we can
see the line items /
FBL1N
FBL1N
balances
of
vendors
5. Account Clearing
layout
of display by
has
all
F-44
been
vendor
8.3
Accounts Receivable
The billing document is a document which supports the creation of customer invoices, credit
or debit memos, and the recording of the financial impact of these transactions in the
general ledger. In ARCH, the Billing Document or Sales Invoices created in Sales &
Distribution Module will automatically create an Accounting Document. The Accounts
Department shall as part of the closing process verify that the policies in respect of Revenue
recognitions have been followed for the Sales Invoices. The Billing Document and the
Delivery Documents in respect of the Sales Invoices which do not meet the Revenue
recognition criteria will be cancelled / reversed.
As a result of the creation of a billing document, integration to the Financial Accounting
module occurs with the automatic creation of an accounting document containing the
following accounting entries:
Debit to the customer account (sub-ledger) and the appropriate general ledger
reconciliation account assigned to it
The Payment Term maintained in the Sales Area segment of the Customer should be the
same as in the Accounting Document. Consequently changes in the Payment Term will be
allowed while creating the Sales Order or Billing Document. A change in the Payment Terms
in the Sales Order would be considered as a credit-sensitive field for the purpose of Credit
Management and due date calculation.
8.3.2
Credit memo will be created when a customer is over-billed. It adjusts previous entries that
were overstated. Therefore, posting a credit memo always leads to a credit posting on the
customer account.
Some of the Customers will make the advance payment along with their orders. Advances
are treated as Down Payments in SAP System. Down payment is to be made with reference
to Sales order in case of both export sales and domestic sales. If the customer pays an
amount in advance, a down payment is captured in a separate GL account distinct from the
normal reconciliation GL Account which is used for normal transaction. This is a special GL
Account. This account is used to record only transaction related to down payment. This
Advance can be adjusted against the invoice after goods are dispatched.
Special GL Indicator
A
Text
Down Payments from Customers
Customer account is linked with General Ledger Account by a reconciliation account. All
transactions related to customer are automatically posted to this reconciliation account.
Special GL Account is the reconciliation account used to record the down payment
transaction to a separate account than the normal reconciliation account.
8.3.4
This function allows user to record receipts from customers in the system and adjust them
against invoices and debit memos. In the case of payments received against invoices, the
invoices can be adjusted against the payments. In case the payment is not with reference to
specific Invoices, the receipt is recorded as an On Account receipts, and linked to one or more
invoices later or the oldest invoice is adjusted. Invoices, advances and debit memos can be
settled to the extent of the outstanding amount. Incoming payment can be booked partially.
Invoices, advances and debit memos can be partially settled.
8.3.5
The receipt of Post Dated Checks (PDC) will be handled differently by ARCH since such checks
cannot be considered at the time of receipt of the check as a realized payment. ARCH will be
using Special G/L Indicator T for this purpose so that the normal Accounts Receivable
Reconciliation G/L Account Balances are not affected. Instead the alternate Reconciliation G/L
Accounts balances will be updated with the PDC amounts when the Customer Account is
credited with this Special G/L indicator. A separate G/L Account shall be used to represent the
Checks in Hand which shall be debited at the time of receiving such PDC.
When the check is deposited in the bank on the instrument date, the Check in Hand Account is
cleared with the posting to the Checks Receipt - Sub Account. The amount shall be transferred
to the main Bank Account upon the realization of the check. The normal open item shall be
cleared against the special item in the Customer Account subsequently to reflect the correct
receivable amounts.
In case of dishonor of check, the Customer Account shall be manually blocked for delivery and
all the payment documents reversed.
Special GL Indicator
T
Text
Customer - Post date cheques
8.3.6
Bills of Exchange
Customers make the payment to ARCH by accepting the Bills of Exchange. BOE document is
sent from ARCH and duly accepted for payments as per the terms of the payment. ARCH will
discount the accepted BOE with the Banker and take proceeds. BOE liability will be monitored.
Banker will send the BOE to the Customer Banker for payment. Based on the BOE due date
Customer makes the payment to the Banker.
Bills of exchanges are handled as special G/L transactions by ARCH. These transactions are
thus maintained independently of other transactions in the subsidiary ledger and are posted to a
Dr
Dr
Dr
Cr
Bill paid by the customer for the Bills under Bill Receivable account (not discounted /negotiated
i.e. bills sent on collection.
Bank
Dr
8.3.7
Cr
8.3.8
Tax will be collected while sales of Scrap. This can be captured by maintaining a tax code and
respective GL will be assigned. While billing document post in Financial accounting
8.3.9
ARCH will send Customers a payment reminder or a dunning notice to remind them of their
outstanding debts. The dunning program duns the open items from Customer Accounts in which
the overdue items create a debit balance. It will select the overdue open items, determines the
dunning level of the account in question, and creates a dunning notice. It then saves the
dunning data created for the items and accounts affected.
The Dunning Procedure controls how dunning is carried out by the system. ARCH and AVON
will use Dunning Procedure 1000 ARCH Dunning Procedure which has a dunning interval of
14 days and 4 dunning levels for dunning the customers.
The dunning levels will be calculated based on the number of days the open items are in
arrears. The dunning program determines the accounts and items which are to be dunned, the
dunning level and all other details necessary for dunning. The dunning program produces a
dunning proposal list. The dunning proposal list can be created as often as required since the
dunning data for the item and in the account is not updated until the dunning notices have been
printed.
The dunning proposal list can be edited by raising or lowering the dunning level of some line
items, blocking some line items from being dunned, or removing dunning blocks. The print
program prints the dunning notices. It will update the fields Dunning level and Dunning date
in each line item, and dunning date and level in the master records.
The dunning texts will be different for each of the dunning levels. Only those Customer Accounts
which contain a dunning procedure in the master record will be included in the dunning run.
8.3.10
Credit Management
ARCH will define Credit Limits for each Customer to minimize its Credit risks. Automatic Credit
check will be applied for each Customer at the point of creation of Sales Order
8.3.11
Closing Operations
Objective
The following are the operations that are to be covered as a part of closing operations
The operations shall cover:
Monthly closings
Yearly closings
8.3.11.1
Once all parked documents are completely posted and payments for the month are
completed, the posting period for customers can be closed.
occurrence of back posting invoices to the previous period after reports are generated.
Before posting period can be closed, other month end processing activities such as
executing the recurring program need to be performed if applicable.
Opening the new period and closing the previous period are two parts of the closing
procedure.
The below proposed flow for month-end processing shall be used as a guideline for this
blueprint.
Process Overview Explanation
Step
Procedures
Accounts posts /
deletes the
outstanding
parked documents
8.3.11.2
SUPERSEDES: N/A
Procedures
AR Ageing
Customer Balances
At the end of the fiscal year, carry forward program is required to be executed to carry
forward the customer and customer account balances to the new fiscal year. After
running the carry forward programs, when a transaction is posted to the previous year, the
account balances in the current year are immediately updated automatically. Balance carry
forward program is done after entries are completed.
In SAP year end closing is similar to the month end process with additional activity of carry
forward of balances to next year. The advantage of this is even after balances are carry
forwarded to next year, any entries to previous year will automatically update the opening
balance of next year.
Year-end closing comprises all activities involved in closing the financial year apart from
Month-end closing activities.
The below proposed flow for year-end processing shall be used as a guideline for this
blueprint.
Process Overview Explanation
Step
Procedures
applicable.
After completed all the additional postings. Close the posting period / fiscal
in special
period,
if
year and open the new period / Fiscal year. System allow for the current
4
AR Ageing
8.3.12
SUPERSEDES: N/A
Procedures
Customer balances
AR Process Steps
Main process
Description
Process of SAP
Creation
Reconciliation GL
1. General
&
customer
master
will
be
created
of
GL
Transaction code
accounts FS00
payment
FBL5N
and F-28
When a
customer paid
accounts
any down
payments
Link between sundry debtors OBXR
payment before
sending the
goods it will be
for
advance
F-29
F-22
2. Advance
collected in a
Payment:
special GL
FI customers)
Transfer
of advance from F-39
account by using
Special GL
by clearing
Clearing of normal item
indicator and
XD02,
F-32
cleared.
In the cases of
Creation
Exchange
payments by LC
accounts
(bills of
exchanges
Invoice posting
exchange) it will
of
for
Special
bills
GL FS00
of
F-22
Description
SUPERSEDES: N/A
Process of SAP
Transaction code
F-36
be recorded into
SAP system and
can be checked
Any payments
Receipt of BOE
Discounting with the bank
Party wise due list
Reverse Contingent liability
F-33
S_ALR_87012213
F-20
from customer
can be checked
4. Customer
Payments
payments, bills of
F-28
FBL5N
FD10N
Manual Clearing
F-32
exchange and
pending invoices
and cleared.
By using SAP we
can see the line
items / balances
of Customers and
5. Customer
account analysis
layout of display
by adding any
necessary things
like cost center
etc., into display
After the outgoing
payment has
been posted all
6. Account
Clearing
Customer
invoices can be
cleared either
age wise or one
by one.
8.4
Asset Accounting
The Asset Accounting module provide, processes required for the management of fixed
assets. The module is integrated with all other modules and data for all asset-related
transactions is updated into GL online. Accounting for assets is done on the concept of sub
ledger - all postings made to any asset are updated in the GL account and there is never any
difference between the values as shown by the asset reports and the GL balances.
The depreciation calculation process is also automatic, and depreciation is posted to the
books of accounts at pre defined periodical intervals (generally monthly). Depreciation can
be calculated according to different principles for the same asset, based on business
requirements. For example, the depreciation rates for accounting purposes and for tax
purposes can be different.
The asset master contains all the important information required, and the depreciation
calculation, postings to cost centers etc. depends upon the assignments made in the master
data.
Asset Accounting (FI-AA) transfers data directly to and from other SAP components. It is
possible to post from the Materials Management (MM) / Project System (PS) component
directly to FI-AA. At the same time, you can pass on depreciation directly to the Financial
Accounting (FI) and Controlling (CO) components.
8.4.1
Asset Acquisition
The primary business process in asset accounting is the purchase of assets and/or the
capitalization of in-house produced goods or services. The Asset Accounting component
supports various methods of handling this business process.
8.4.1.1
Direct Capitalization
Direct capitalization refers to asset acquisitions that do not have an asset under construction
phase. Instead, they are capitalized and begin depreciation immediately.
An external asset acquisition is a business transaction resulting from the acquisition of an
asset from a business partner (in contrast to an acquisition from in-house production). You
In Asset Accounting (FI-AA) in integration with Accounts Payable (FI-AP), but without
reference to a purchase order
Goods receipt
When you enter the purchase order, you determine whether the asset is posted
directly to Asset Accounting, and thereby capitalized, when the goods receipt is
posted (valuated goods receipt), or whether capitalization does not take place until
the invoice receipt is posted (non-valuated goods receipt). The first option would be
used when the goods receipt takes place before the invoice receipt.
When the
invoice is received later, there may be differences between the invoice amount and
the amount posted at the time of the goods receipt. In this case, adjustment postings
are made to the asset. No corrections are necessary for a non-valuated good receipt,
Invoice receipt
If the goods receipt was non-valuated, the asset is capitalized, line items are created
and the value fields are updated.
At this stage the system will prompt in case an advance is already paid to the vendor.
In the next step payment is processed for the fixed assets purchased while adjusting
the advance already received.
FI will post the capital items invoice while debiting the asset account and crediting the
asset acquisition clearing account.
In the next step payment is processed for the fixed assets purchased
Respective bank a/c is updated & Asset Acquisition clearing account will be cleared.
8.4.1.2
Assets under construction (AUC) is special form of tangible asset. They are usually
displayed as a separate balance sheet item and, therefore, require separate account
determination and asset classes. During the phase in which an asset is under construction,
Statistical Internal Orders will be used to control the budgets and when certain business
transactions are entered that create costs on the corresponding Internal Order, the system
checks whether the available budget or available released budget is sufficient. It uses the
tolerance limits specified in Customizing for this check. Tolerance limits can be defined as
the usage level from the current budget or the release.
Projects will be used to capture the cost of the Asset and control the budget. Initially values
will be posted to AUC assets in every month based on settlement and after completion of the
project AUC assets will be transferred to the Main Asset.
Step 1: Create Project for Capex/Create WBS element under Project
Step 2: Enter Investment Profile for WBS element
Step 3: Maintain Budget for Project/WBS element
Step 4: Release WBS element (AUC will be created automatically based on
investment profile)
Step 5: Execute Any Business Transaction against the Project (Atual costs will be
captured in the project/WBS element)
Step 6: Availability Check for Budget will performed whenever any business
transaction is executed against the Project/WBS element
Step 7: Run Month end Settlement (Periodic Settlement) to transfer the cost incurred
during the month to AUC
Step 8: During final settlement of Project/WBS costs from AUC will be transferred to
Actual Main Asset (Project / WBS status must be in TECO before running final
settlement)
Step 9: Close the Project
8.4.4
Asset Retirement
The asset disposal process includes activities for identifying, approving and accounting for
the disposal of fixed assets.
longer needed, it will either be re-deployed to another business unit that may have a need
for the asset or the company may dispose of the asset in partial or full. For assets that are
re-usable, the company may try to re-deploy the asset.
pursued and a new owner cannot be identified, the asset will then become available for sale
or scrap/abandonment.
8.4.4.1
By using Asset Retirement with Revenue from Customer option the sales process can be
initiated in the system. While booking the Retirement, system will calculate the Loss or Gain
on the Asset disposal and post necessary accounting entries. User will have option to retire
completely or he can choose partially. Accordingly system will reduce the Gross block as
well as Accumulated depreciation.
8.4.4.2
accountant will then remove the asset from the books by performing disposition posting for
loss on abandonment.
SAP Solution for the requirements:
Step #
Process Description
SAP Module
Standard
SAP
F-92 / ABAON
be
taken
into
account
for
any
further
depreciation run.
After complete retirement of assets the same shall
Standard SAP
transaction.
and
reversal
F-92 / ABAON
of
accumulated depreciation.
8.4.5
8.4.5.1
Asset Transfers
Asset Transfer Location transfer (within the Plant)
In case of transfers within the same company i.e. Intra Company transactions, the new
location need to be updated in the location field in the asset master record using AS02. The
different locations wherein the asset was located at different time intervals can be viewed in
the asset master record.
In case of transfers from one cost center to another, the same needs to be updated in the
cost center field in the asset master record using AS02. The different cost centers wherein
the asset was located at different time intervals can be viewed in the asset master record.
8.4.5.2
The following process needs to be followed for transfer of Asset from One plant to another
plant:
1. Create Non-Valuated material
2. Goods Receipt
3. Stock Transport Order
4. Take 50% balance cenvat credit if the asset is purchased during the year
5. Create Excise Invoice (Excise duty liability will be generated)
6. Create new Asset in Receiving Plant
7. Do delivery in sending Plant
8. Goods Receipt in Receiving Plant
9. Excise capture and Post in receiving Plant (Excise values will be posted)
10. Make Asset Transaction (ABUMN) for making the effect in Financial Accounting. Both
acquisition value and accumulated depreciation value will be transferred from
sending Asset to receiving asset. Values will be updated in both the profit centers.
8.4.5.3
In case of postings to a wrong asset class, transfers can be made through the system (T.
code: ABUMN) in order to transfer the assets to its correct asset class.
All the above transfers i.e. from one location to another, from one cost center to another can
be tracked through the standard reports available in the system. In case of any change in
cost centers in the asset master record, depreciation will get charged to the respective cost
centers based on specific time intervals for which they were held by each cost center. In
case the location change happens for the earlier period, the revised cost centre wise
depreciation will not be updated for the previous period.
8.4.6
Leased Assets
8.4.6.1
The "acquisition of a leased asset" is considered to be the entry of the leased asset in the FIAA System. This does not necessarily mean that the leased asset must be capitalized. You
can enter a leased asset simply to manage purely statistical data. You handle the asset as a
master record, with no values in the book or tax depreciation areas.
Posting the acquisition of a leased asset may be necessary for one of the following reasons:
You need to change the way bookkeeping is handled for a leased asset due to a
change in the conditions of the lease.
You need to post a leased asset to a new asset master record due to a transfer.
Before posting the acquisition of the leased asset, you must determine the bookkeeping
method to be used, either:
capitalization of the leased asset in the asset portfolio, with the present value of the
future lease payments and depreciation of the present value (capital lease)
statistical management of the leased asset (no capitalization), and direct posting of
the lease payments as rental expense in the profit and loss statement (operating
lease)
8.4.7
8.4.7.1
Asset Depreciation
Calculation of Depreciation
The depreciation areas specify the different methods for calculating depreciation for the
asset to which they are assigned. Each asset of ARCH will have at least two depreciation
areas which are defined in the Chart of Depreciation
S.No. Depreciation Area
01
01
02
15
Description
Book Depreciation area
IT Depreciation area
For each asset depreciation keys are assigned in the asset class in accordance with the
information provided in the depreciation areas to calculate the depreciation/expense and
8.4.7.2
Depreciation Keys
Some of the following depreciation keys will be created for Arch to calculated depreciation
for Fixed Assets:
Dep. Key
SL01
SL02
SL03
SL04
SL05
SL06
SL07
SL08
SL09
SL11
SL12
SL13
SL14
GWG
Description
Straight Line Method - 1.63%
Straight Line Method - 3.34%
Straight Line Method - 4.75%
Straight Line Method - 10.34%
Straight Line Method - 6.33%
Straight Line Method - 9.50%
Straight Line Method - 7.07%
Straight Line Method - 16.91%
Straight Line Method - 16.21%
Straight Line Method - 5.28%
Straight Line Method - 33.33%
Straight Line Method - 1.05%
Straight Line Method - 1.23%
LVA 100 % Complete depreciation
Separate depreciation keys will be created for WDV and will be assigned for WDV asset
classes for which depreciation needs to be calculated.
8.4.7.3
Posting of Depreciation
Revaluation of Assets
Revaluation of Assets can be posted using the Transaction Manual Value Correction. The
respective Asset Class will be debited and Revaluation Reserve A/c will be credited with the
revaluated amount. The depreciation on the revaluated portion will be adjusted against
Revaluation Reserve A/c. The System provides for accommodating revaluation requests and
updating of asset records.
8.4.9
Impairment of Assets
Impairment loss refers to carrying value of the assets is more than the recoverable amount
and value in use of the asset. Impairment loss needs to be charged off to the P&L a/c. In
case of the impairment loss is more than the carrying value of the asset, excess value over
and above carrying value of the asset shall be treated as liability in the balance sheet.
On each Balance Sheet date the enterprise should assess whether there is any indication of
impairment of an asset. An asset is said to be impaired when carrying amount of the asset is
more than recoverable amount. If yes, the enterprise should estimate the recoverable
amount and amount of impairment loss will be carrying amount less recoverable amount.
If an asset is carried at a historical cost, impairment loss will be charged to P & L A/c and if
an asset is carried at Revalued amount, impairment loss will first be set off against
revaluation reserve and for any excess over revaluation reserve will be charged to P & L A/c.
Impairment can be made through SAP Transaction code ABAW and entries passed in SAP
T-code F-02
8.4.10
8.4.11
Closing Operations
Objective
The following are the operations that are to be covered as a part of closing operations
The operations shall cover:
Monthly closings
Yearly closings
8.4.11.1
The check list for month end process will be documented after the Realization Phase of this
project.
The below proposed flow for month-end processing shall be used as a guideline for this
blueprint as the activities may not be finalized until Realization phase.
Process Overview Explanation
8.4.11.2
Step
Procedures
The system found no errors during the calculation of depreciation (such as,
incorrectly defined depreciation keys).
Planned depreciation from the automatic posting area has been completely posted to
the general ledger.
The system lists any assets that do not meet the above requirements in the log of the
year-end closing.
Procedures
Execute the standard SAP inbuilt check which will validate the pre closing
activities.
Execute fiscal year change program which will validate and carry forward
8.4.12
Main
process
Description
Transaction
Process of SAP
AS21, AS24
AS02, AS22
AM01
AS11
code
AS01, AS11,
with
F-90
Acquisition
and
clearing ABZON,
F-91
of
and
also
any
SUPERSEDES: N/A
F-48
While
sale
without
customer
Asset
Retirement
Depreciation
with Customer
Scrapping
the Manual depreciation
calculating
by
F-92
ABAON
ABAVN
ABMA
overhead orders
Unplanned depreciation
ABAA
Depreciation Planning and AFAB
Posting
posting
run
will
be
made
AIAB, AIBU,
AIST
will
be
Post Capitalization
Business
finishing
transactions
Closing
asset.
The existing asset inventory Physical asset inventory
operations
standard
report.
ABNA (Post
cap)
ABUMN
ABZU
AR01
AJRW
8.5
8.5.1
Bank Accounting
The component Bank Accounting is used to handle accounting transactions that you process
with your bank. All country specific characteristics such as the specifications for manual and
electronic payment procedures, payment forms or data media can be freely defined.
It includes the management of bank Master data, the creation and processing of incoming
and outgoing payments.
8.5.1.1
Check Payment
The Bank payment process encompasses among others, payment to Creditor (Vendor) and
Employees, Advance payments and the settlement of statutory dues or other commitments.
Cash / liquidity position at the start of each day needs be scrutinized to ascertain the
quantum of payments that can be made out for the day. This will ensure an optimization of
the available Cash/Bank balance and better utilization of the float period.
Next step would be to identify Invoices, which are to be paid either because the due date
has approached, or some other prioritization criteria.
SAP works on the principle of Open and Cleared Creditor (Vendor)/Customer line items.
An Open item represents a liability or an asset, which is pending payment or receipt. On
the subsequent payment/receipt, the Open item gets converted into a Cleared item i.e. the
liability gets exhausted on payment.
In case, if a payment has to be made to an entity other than the Invoicing party, the
Alternate payee needs to be defined at the transaction entry level. The Check in such
cases would be in the name of the Alternate payee; however liability to the Invoicing party is
Check Receipt
ARCH will process check receipt from customers by clearing open items in the Customer
Account. Posting of an check receipt will create an accounting entry, which will debit the
appropriate general ledger bank account and credit the appropriate customer account. At the
same time, a credit is posted to the general ledger reconciliation account assigned to the
Customer Account. A partial payment leaves the original invoice intact and creates a credit in
the customer account for the amount of the partial payment. No items will be cleared as a
result of a partial payment.
All incoming payments shall be routed through the Bank Check Receipt Sub account and
the amount shall be transferred to the main Bank Account upon the realization of the check.
The Bank Check Receipt Sub G/L Account shall be open-item managed so that the details
of checks in clearing can be seen from the open-item list.
In case of check dishonor the incoming payment document shall thereafter be reversed
which will clear the item in the Bank Check Receipt Sub Account and the Customer
Invoices shall again be open. Bank charges for such dishonor can be recoverable from the
Customer for which Debit Notes shall be issued to the Customer.
The following will be the some of house banks created for Arch:
Account ID
Company code
1000
1000
8.5.1.3
House
Code
ALM01
ALM01
Bank
HB Description
Allahabad Bank
Allahabad bank
Branch
Name
and Address
CA01
CC01
Fort, Mumbai
Fort, Mumbai
For each bank, apart from its main bank account, an intermediate Check Receipt & Check
issue bank account will be created. The Bank reconciliation process is based on the entries
passed through the Bank sub account and main account. The process is dependent on the
Bank Statement updating.
Any check deposited in the bank will be debited to the bank check receipt sub account and
will be credited to corresponding G/L or sub-ledger account such as customer account.
Similarly, any check issued will be credited to the bank check issue sub account and will be
debited to the corresponding G/L or sub-ledger account.
The bank statement will be uploaded in SAP ECC system or a manual bank statement entry
is done in the system.
Bank reconciliation will be carried out based on the Check number or any other unique
identification automatically captured or entered in the assignment field.
Bank Main account balance is the actual balance as per the bank statement whereas the
Bank sub accounts denote the reconciliation items. These sub accounts show those entries,
which are not cleared in the bank statement.
During uploading of the electronic bank statements, data in these files is supplied with SAPspecific information, such as:
Chart of accounts
Company code
After the import transaction is completed, the data in the bank data memory is analyzed. The
system tries to identify the individual business transactions and filter out the information
necessary for posting, for example, check numbers from the note to payee fields on the
bank statement. Note that the system will not clear the bank clearing items unless the
amount on the statement is also equal to the bank clearing items amount.
If the necessary information can be interpreted, the system will automatically post the
transactions based on the pre-defined clearing criteria. As an example, for outgoing
payments, system uses outgoing check numbers as matching criteria.
Note: The assumption for the automatic clearing is that the bank statement can
provide the necessary information required for automatic clearing (i.e. for matching
with the data in SAP system).
If the Bank Statement data is not available in standard Multi cash format, periodically the
data is obtained in the desired format from bank carrying details like document number,
check number, amount, date, etc. This file will be loaded /copied into the system and the
entries in incoming bank account & outgoing bank account will be posted to main bank
account.
If the Bank Statement data is not available in electronic format, the data will be entered
manually for bank reconciliation.
Data that cannot be matched will be manually matched and posted for clearing
8.5.1.3.2 Electronic Bank Statement and Manual Bank Statement
Main Account: Where the balance of this account will be matched with the bank
statement.
Check Issue Sub Account: Where all the check issued will be posted.
Check Receipt Sub Account: Where all the collections will be posted.
Direct Debits and Direct Credits : Where the bank directly debits and credits will be
posted.
After the automatic bank reconciliation process entries in the Check Issue Sub Account and
in the Check Receipt Sub Account will be transferred to the main account.
Following are the clearing accounts for Electronic Bank Statement (EBS)
When the bank statement is uploaded in SAP the following will happen:For checks issued out based on checks cleared in the bank account the following entry will
be passed automatically.
Account description
Check Issue Sub Account
Main Bank account
Debit /Credit
Debit
Credit
For checks received in based on checks cleared in the bank account the following entry
will be passed automatically.
Account description
Main Bank Account
Check Receipt Sub Account
Debit /Credit
Debit
Credit
Thus after uploading the bank statement in the system, the Main bank account will exactly
match with the balance shown in the bank. All the clearing accounts having balances will be
the reconciliation items
Description
ZA01
Cheque Deposit
ZA02
Deposit reversals
ZA03
Check issue
ZA04
Each business transaction will be assigned to Account symbols and Posting rules and GL
coding masking will be done against account symbols.
8.5.1.4
Liquidity Forecast
Cash Management would be designed as below for meeting the requirements of Arch
Structure for Liquidity Forecast
Planning Level:
Financial transactions in Cash management are displayed using planning levels to explain
the beginning and ending account balances. In Arch it is envisaged that Planning levels are
maintained in GL accounts for reporting in liquidity forecast
Source Symbols:
It divides the planning levels according to the sources that supply them with data. In Arch it is
envisaged that source symbols PSK, MMF and SDF will be maintained to specify that the
source is from sub ledger accounting, materials management and sales &distribution.
Planning Groups
In cash management, customers and vendors are assigned to planning groups by means of
master data entries. Planning group represents particular characteristics, behavior or risks of
the customer or vendor group. In Arch Planning groups will be maintained to categorize the
customers and vendors as per the requirement and assigned to the customer and vendor
master records. Planning levels (which tells How an amount is posted) are assigned to the
planning groups
Groupings
Zensar Technologies Limited
The summarization term under which we wish to group together the lines for levels in
the display.
In Arch it is envisaged that summarization terms are maintained to combine the planning
levels and planning groups of one grouping for the cash position and liquidity forecast
Planning Type & Memo Records
In Cash management, planning type controls the manual entry of planned memo record. For
each planning type, we specify:
The archiving category in which a memo record is stored after it becomes invalid.
In Arch it is envisaged that planning types will be maintained for manual entry of memo
records in case of expected receivables and proposed payables.
8.5.1.5
Cash Position
The Cash Position supplies information on the current financial situation in the various bank
accounts and bank clearing accounts. It is used to overview the short-term liquidity position.
The various postings made to the various G/L Accounts relevant to Cash Management is the
main source for the Cash Position.
Groupings are used to specify the set-up of the Cash Position. The grouping will determine
which level and bank account will be displayed in the Cash Position. Detailing by planning
level will provide information on the causes of bank or account transactions for bank
accounts.
The planning levels can be used by Arch are:
Level
F0
LB
8.5.2
Cash Journal
A double-entry compact journal managed in account form that records the postings for cash
transactions.
It is used to manage a company's petty cash transactions. The system automatically
calculates and displays the opening and closing balances, and the receipts and payments
totals. You can run several cash journals for each company code. You can also carry out
postings to G/L accounts, as well as vendor and customer accounts.
Separate cash journal required for each currency.
Cash balance is maintained at plant to meet day to day expenses. When cash refill is
necessary, a self-withdrawal check is drawn on the House bank Payment A/c & received at
the location.
The cash journal entries will be saved locally in the cash journal. Thereafter, the
system will calculate the balances, subsequent to which the cash journal entries
saved will be posted to the general ledger.
Cash Journal allows to post cash documents (like expenses, cash withdrawals from banks,
payments to vendors, employees etc.,) in a simple way.
Cash Journal
Description
1000
1000
1000
1000
1100
1101
1102
1103
1000
1000
1104
1106
1000
1000
1000
1000
1000
1000
1000
3000
1107
1154
1200
1201
1202
1203
1301
3101
Cash-Head Office
Cash-Tarapur T86
Cash-Badlapur
Cash-Taloja G6
Cash- Corporate R&D Centre
- I, Taloja
Cash- Dombivli
Cash- Corporate R&D Centre
- II,Turbhe
Cash-Tarapur Oncology
Cash-Hyd Regional Office
Cash- Merven
Cash- Siddipet
Cash-Sibra
Cash-Vitalife Laboratories
Cash-Solapur
8.5.2.1
Business Transactions
In Cash Journal, each transaction will be posted against particular business transaction. The
following business transactions will be used for posting the transactions through cash
Journal:
EXPENSES
REVENUE
VENDOR
CUSTOMER
RECEIPT FROM BANK
PAYMENT TO BANK
Other than the above normal business transactions, for each expenses account separate
business transactions can also be created. For each business transaction, relevant GL
account can be assigned. This facilitates the user to reduce the mistakes in selection of
GLs. Only user needs to be select the relevant business transaction. The following business
transactions can be taken for cash journals. I.e. Printing and Stationery, Travelling expenses,
Conveyance etc. While making payment, user can select relevant business transaction so
that General Ledger account will be taken automatically from business transaction.
8.6
8.6.1
Taxes
Tax on Sales and Purchases
For Arch on each taxable sale (i.e. non-exempt) and on each taxable purchase (i.e. nonexempt) made inside the respective state, a value added tax (VAT) will be applied. The rate
is determined by the kind of product, service that is purchased. The taxes on the sales and
purchase transactions are classified as exempt, zero tax rate, or standard tax rate. It is
possible for the VAT Tax on some purchases to be non refundable. For these transactions
the Vat amount will be added to the actual cost of the product.
A tax code will be set for every vendor and every material in the SAP system. This denotes
that taxes are calculated automatically. The code can be manually overwritten with a nontaxable code if taxes are not applicable to a certain transaction when the transaction is
entered. Tax codes are to be assigned to the Vendors and Materials records.
Some of the tax codes maintained for ARCH are:
Tax Indicator
Description
V9
C3
M9
CJ
CC
8.6.2
Excise Duty
Separate set of Cenvat accounts will be maintained for each excise registration. This will
help in utilization of the excise amount against credits lying in books.
Excise Group:
Excise Group will be created under each plant for specific excise registration number. All
excise related transactions i.e input credits, duty payables and utilization transaction will be
posted to the excise group. Excise Registers will also be drawn for each excise group.
SUPERSEDES: N/A
Excise duty payable based on sales invoices will be shown as payable and on hand credit
amounts will be shown while doing utilization. Against each item i.e against BED payable,
BED credit amount and against E.Cess payable, E.Cess credit amount and against SH
E.Cess payable, SH E.Cess credit amount will be selected.
The following entry will be posted, while utilization:
Dr. Excise duty BED payable
Cr. RG23A BED/RG23C BED/ PLA
Dr. Excise BED E.Cess payable
Cr. RG23A E.cess / RG23C E.Cess / PLA E.Cess
Dr. Excise SH E.Cess payable
Cr. RG23A SHE.Cess / RG23C SH E.Cess / PLA SH E.Cess
Excise duty credits or Excise duty debits can also be taken through Excise JV in SAP.
PLA Accounting:
While payment of PLA, the following entry will be posted:
Dr. PLA on hold a/c
Cr. Bank
While updation of PLA records, the entry to be posted through Excise JV and the document
will be:
Dr. PLA BED a/c
Dr. PLA E.Cess a/c
Dr. PLA SH E.Cess a/c
Cr. PLA Onhold account.
In all the above cases, wherever Excise GL accounts will be hit, in the same time excise
registers will also be updated. There wont be any separate reconciliation for financial books
with excise records. Always the balance in both the books will be tallied.
RG1 Register:
Separate transaction will be performed for updating the entries in RG1 register. The updating
can be based on movement type or material document or storage location.
Monthly Returns:
Monthly excise return i.e. ER1 form will be generated based on the excise transactions
happened during the period.
8.6.3
Service Tax
Separate Tax Codes will be defined for GTA Set Off / GTA Non Set Off and Other Service
Tax transactions.
Each Plant is created as business place. Separate set of GL accounts are defined for each
plant service tax registration accounts, where ever the registration is available.
Two sets of GL accounts will be defined. First set is meant for Input Service Tax Accounts
and the second Set is meant for Utilizable Service Tax Accounts.
Whenever the bill is accounted with service tax code, system will post service tax amount to
service tax input account. A BDC program will be made available for transfer the service tax
input amount to Service tax utilizable account. System will check whether the vendor line
item is cleared from the original entry. If it is cleared, system will transfer the balances from
Input Service Tax accounts to Utilizable service tax accounts. The balances in these
accounts are used for utilization.
The original document number and financial year is updated in the reference field of transfer
entry. With this, the track of the BED, Ecess and SHecess can be maintained.
Register will be developed per registration for GTA Input, GTA Output, Non-GTA and for
Foreign payments. Nature of service will be maintained in the vendor master Control data
tab data tab against Profession field.
Service tax liability (collected on conversion charges) can be adjusted through journal
voucher as below:
Service tax payable
Service tax utilizable account
Dr
Cr
Service tax payable on GTA should be paid directly to the Govt. Authorities and cannot be
adjusted from utilizable account. Only after payment, that much amount can be Service tax
utilization for Excise duty payment.
SUPERSEDES: N/A
While doing monthly utilization for normal excise duty, service tax utilizable GL accounts for
the concerned plant will need to be entered.
Total service tax codes indicate rates will be:
Some of the service tax codes can be defined for Input tax :
S0 Service tax Nil
S1 - For normal service tax 10+2+1
SA GTA set off
SB GTA inventorized
S2 for Service tax with VAT
S3 Service tax with CST
GTA Service Tax:
While payment of GTA service tax liability to Govt.
Service tax payable
House Bank Cheques Issue
Dr
Cr
(this amount can be taken from service tax payable GL by selecting tax codes SA
and SB for particular period)
Service tax payable on non-GTA (on conversion charges etc.) will be adjusted through JV as
below:
Service tax payable
Service tax utilizable account
8.6.4
Dr
Cr
TDS on others: TDS on Others will be categorized as per the following sections
under Income Tax Act, are being tracked in SAP System.
8.6.4.1
Any new section which attracts TDS can be configured as Official Withholding Tax Key
8.6.4.2
Recipient type:
The vendors from whom TDS is deducted need to be classified as Company and Others.
Recipient type enables categorization of the vendors. This categorization is required for
creation of separate challan and printing the TDS certificates
8.6.4.3
Withholding tax types are defined at client level to represent the various types of withholding
taxes for i.e. 194C, 194J, 194I
whether the deduction of TDS will take place at the time of invoice verification or at the time
of payment. These withholding tax types can be used once these are linked to the Company
codes. Withholding tax types shall be configured as per ARCH requirement.
8.6.4.4
Withholding Tax Codes:
The various sections of the Income tax Act prescribe the rate at which the Tax is to be
deducted. Withholding tax codes are used to define the rate at which tax is to be deducted
and the base amount on which the tax is to be calculated.
Vendor master: WHT type /codes shall be maintained in the Vendor master as applicable to
the vendor. Tax computation will be done by the system based on the WHT type/code
maintained in the vendor master at the time of invoice entry and also advance payments.
maintained and user needs to select the tax code. If multiple TDS sections are applicable to
a particular vendor, then all the tax types and tax codes for invoices applicable for those TDS
sections must be maintained in the vendor master. However at the time of invoice entry the
user has to select the correct tax type and code and exclude those which are not applicable.
System will facilitate manually enter the taxable amount: - At the time of posting user shall
amend the base amount.
Once the tax is calculated, it should be posted to the respective account Tax Payable A/c
automatically is a standard functionality. TDS Payable Account will be maintained section
wise and Recipe wise (whether Co or OT)
Exemptions rates will be maintained at the Vendor Master level for deducting tax to vendors.
Accounting entry at the time of Invoice entry:
Dr Expense a/c
Cr Vendor
Cr TDS Payable
(Separate GL accounts shall be created section wise like TDS payable Contractors,
TDS payable - Professional fee. etc.)
Accounting entry for advance payment to vendors:
Dr. Vendor Advance a/c
Cr. Bank a/c
Cr. TDS Payable
The following are the WHT types and codes, which will be maintained for ARCH:
WHY
Type
I1
I1
I1
I3
I3
I3
I4
I4
I4
WHT
Code
I1
I9
F1
I1
I9
F1
I1
I9
F1
Description
Sec 194C - Contract Inv Co/Firms 2%
Sec 194C - Contract Inv Hu/Indiv 1%
Sec 194C - Contract Inv 20%
Sec 194A - Interest Inv Co/Firms 10%
Sec 194A - Interest Inv Hu/Indiv 10%
Sec 194A - Interest 20%
Sec 194D - Ins Comm Inv Co/Firms 10%
Sec 194D - Ins Comm Inv Hu/Indiv 10%
Sec 194D - Ins Comm. Inv 20%
Tax Rate
2
1
20
10
10
20
10
10
20
8.6.4.5
I1
I9
F1
I1
I2
F1
I1
I9
F1
I1
I9
F1
I1
P1
P9
F1
P1
P9
F1
P1
P9
F1
P1
P9
F1
P1
P9
F1
P1
P9
F1
P1
P9
F1
10
10
20
2
2
20
10
10
20
10
10
20
2
1
20
10
10
20
10
10
20
10
10
20
2
2
20
10
10
20
10
10
20
TDS remittance:
Remittance will be made through the system by standard T-code J1INCHLN. Challans will
be updated for each section wise, corporate and Non corporate separately. Due dates will be
defined in the configuration for each section wise.
Cr Bank a/c
8.6.4.6
Bank challan number will be updated in the system through standard T code J1INBANK.
This will link the remittance challans with the external bank scroll number. No accounting
entry will be generated.
8.6.4.7
TDS certificate:
Certificates for the vendors can be generated by T Code- J1INCERT. Certificates cannot be
generated more than once. However duplicate certificate can be issued.
8.6.4.8
Quarterly E-Returns:
E-Returns for TDS shall be generated from the system by T code J1INQEFILE. The return
shall be converted into required excel file and can be validated for filing.
8.6.4.9
8.6.4.10
A separate set of WT tax code & tax type shall have to be created for customers. Following
accounting entry shall be generated at the time of receiving the payment:
Dr.
Bank a/c
Dr.
Cr.
Customer a/c
8.6.5
Forms Capturing
Form Capture Procurement: For purchases made against form C, Sales tax forms needs
to be submitted to the Vendor. The forms can be availed from the Sales Tax Department on
submission of relevant documents like invoice, monthly returns filing details etc. The details
can be tracked in SAP by developing the report. It contains the following process:
All the purchases made against C form will be displayed in one table.
Forms issued against purchases invoice will be recorded against the invoice no.
Balance line items for which forms are to be issued can be identified.
Form Capture Sales: Sales made against form C/ H, Sales tax forms needs to be
submitted to be collected from customers. These forms can be issued by the customers
quarterly basis. Such forms need to be recorded in SAP for better control. The details can be
tracked in SAP by developing the report. It contains the following process:
All the Sales made against Form C or Form H will be considered in one table.
Forms received against billing documents can be maintained against the billing
document number.
Balance line items for which forms are to be issued can be identified.
The above forms tracking requirement will be taken up through ABAP development.
8.6.6
Other Taxes
Other than sales tax and excise duty, Navi Mumbai tax needs to be paid for purchase made
for Plants located in Navi Mumbai. 1% cess will be calculated on the total purchases during
the month and month end provision needs to be made for the tax payable and subsequently
the same will be paid.
9 Integration considerations
Chart of Accounts:
The operating chart of accounts is shared by Financial Accounting as well as Controlling.
The accounts in a chart of accounts can be both expense or revenue accounts in Financial
Accounting and cost or revenue elements in cost/revenue accounting.
General Ledger Account:
Automatic account determination / posting is one of the most powerful methods to determine
the correct G/L account to post to by considering the type of transactions and other factors.
This feature provides a lot of flexibility and eliminates the need to hard code the G/L account
in the source code.
FI CO Integration:
The operating chart of accounts is shared by Financial Accounting as well as Controlling.
The accounts in a chart of accounts can be both expense or revenue accounts in Financial
Accounting and cost or revenue elements in cost/revenue accounting. Relevant GL-P&L
accounts are maintained as cost elements in Controlling.
MM FI Integration:
MM and FI are integrated by way of automatic account assignments to GL accounts for
material movements types, which have an impact on financial information. Also valuation
classes are linked to FI for purpose of providing inventory valuation and other material
movement postings in FI.
SD FI Integration:
SD account assignments depend on the condition tables & access sequences to determine
the correct G/L account. One can set up condition tables / types to use different
characteristics such as:
Account keys
These account modifiers are used to assign different G/L accounts to various condition
types.
The following Customer Account Assignment groups will be created for Arch:
Customer
Account Description
Assignment Group
11
12
21
31
41
Domestic - Normal
Domestic - SEZ
Export
Merchant Export
Affilated Cos.
The following Material Account Assignment groups will be created for Arch:
Material
Account Description
Assignment Group
10
20
31
32
40
45
51
90
91
92
Intermediates
API
CRAMS-Intermediates
CRAMS-API
Agro Chemicals
Trading Material
Services
Others
Job work
Scrap sale
Description
Sales Revenue
Sales Returns
Excise duty collected
Insurance
Freight charges collected
Commission
Process
FI
CO
Organisation
Controlling
Structure
Centres, Currencies
Elements
Controlling
generates
MM
Area,
Cost
Plant,
Locations,
SD
Storage
Purchase
Organization
PPQM
Sales Organization,
Distribution
Channel, Division
Document
Material Document is
posted
Invoice
Creation
Controlling
generated
Document
Delivery
Processing
Post Goods Receipt
Return
Invoice
Credit Memo
Controlling
generated
Controlling
generated
Document
Material Document is
posted
Document
Materials Management
Purchase
Documents
Purchase
Requisition
Purchase
Commitments
Requisitions
will
be
Assignment object
Purchase
Commitments
Purchase Orders
Order
will
be
Inventory Management
Goods Receipts
Goods Issue
Subsequent
Controlling
generated
Controlling
generated
Controlling
Adjustments
Document
Document
generated
Accounting Document generated
Transfer Postings
Cancellation
Document
Controlling
Document
generated
of
documents
Physical Inventory
Controlling
Document
generated
Accounting Document generated
Controlling
Document
generated
Service Entry
Controlling
Document
generated
FI
CO
MM
SD
PPQM
Invoice Verification
Invoice
Subsequent Credit
Document
generated
Controlling
Document
generated
Accounting Document generated
Subsequent Debit
Controlling
Document
generated
Accounting Document generated
Credit Memo
Cancel
Controlling
Controlling
Document
generated
of
invoice
documents
Controlling
Document
generated
Production Planning
Goods issue against
Process Order
Confirmation
of
Material Document is
posted
Document
generated
Goods
Receipt
against
Process
Order
Settlement
Document
generated
Controlling
Process Order
Process
Controlling
Order
Controlling
Document
generated
Controlling
generated
Material Document is
posted
Document
Material Document is
posted
10 Process Requirements
Req. Ref #
Requirement
SAP Process
Purchase Invoice Booking Procedure
001/001
It
should
check
tax Based on Purchase
schedule at the time of Order entered Invoice
booking the invoice
verification, system will
check tax schedule of
PO.
001/002
On saving the invoice in the On posting the invoice
system it should reflect in document
Vendor
vendor account.
account
will
be
updated.
001/003
System should check for GR qty. will be copied in
GRN and bill qty at the Invoice verification and
time of booking
that qty. can be cross
check with Vendor bill
qty.
001/004
System should check the System will check PO
PO rate and invoice rate at rate, since PO will be
the time of booking the entered in Invoice.
invoice.
001/005
Form capturing option at Based on requirement,
the time invoice booking
process needs to be
developed
001/006
In case of RM local and Local Purchase GR
import Purchase booking based
invoice
the system should check all verification and Import
the standard measures Purchase Invoice
which are needed which verification for duty, GR
booking the invoice
based
on
invoice
verification and Invoice
verification for Material
001/007
In case of PM local and System will check the
import Purchase booking standard measures for
the system should check all invoice verification:
the standard measures PO Terms Supplier,
which are needed which Material, Qty, Price
booking the invoice
Goods Receipt - Qty.
and Value
Invoice verification will
be posted as per PO
and GR and consider
tolerances maintained
for price or Qty.
001/008
In case of Engg local and System will check the
import Purchase booking standard measures for
the system should check all invoice verification:
the standard measures PO Terms Supplier,
Status
Standard
Standard
Standard
Standard
Development
Standard
Standard
Standard
001/009
001/010
001/011
001/012
SAP Process
SUPERSEDES: N/A
Status
Standard
Standard
Standard
Standard
001/013
001/014
SAP Process
SUPERSEDES: N/A
Status
Payment Procedure
002/001
At the time of making the
advance , system should
ask for PO allocation and it
should also check for
previous advances
002/002
002/003
002/004
In
Purchase
Order Standard
itself, Down Payment
details
will
be
maintained and will be
tracked up to invoice
verification.
In case of part payment PO will be available for Standard
made in advance against a next
advance
for
particular PO then that PO balance amount.
should again be available
for next advance for
balance amount if any.
If for the vendor TDS is TDS conditions will be Standard
applicable then at the time maintained in Vendor
of making the advance Master. While making
payment system should advance payment or
prompt for TDS deduction
invoice
verification,
system will proposed
for TDS deduction.
System should check at the Since
the
advance Standard
time of making advance details will be entered in
payment against PO that Purchase order itself,
SAP Process
SUPERSEDES: N/A
Status
Advances
Recon Standard
accounts needs to be
created for each type
i.e. RM Local, RM
Import, Service Local,
Service
Import,
Expenses payment. If
advance
recon
accounts maintained as
above, all advances
can be routed through
different Special GL
Indicators.
IOUs will be treated as Standard
advances in SAP
Limit control can be put Standard
for Cash or Petty cash if
it routed through cash
journal
Standard
Standard
Standard
Standard
Development
SAP Process
SUPERSEDES: N/A
Status
capturing
process
needs to be developed
005/006
Provision for TCS for scrap Provision
will
be Standard
sales to be finalized
available by maintaining
a condition type in
Scrap Sales pricing.
005/007
Sale in transit Export for Instead of Cost of Work around
month end change over. goods sold account,
(BL Date & CI Date)
Sale in Transit account
will be hit and the same
will be reversed while
billing.
005/008
Excise rebate receivable Will be traced through a Standard
has to be tracked in SAP
separate excise sub
transaction type.
Stock Transfer Procedure
006/001
In case of inter branch Postings will happen to Standard
transfers the system should Stock accounts and
take care of entries for STO Inter
unit
clearing
accounts.
006/002
In stock transfer from plant Excise component will Standard
to plant the system should be taken into RG23D
not expense out the excise register, in case of
component
Depo transfer.
Loan & Rent Accounting Procedure
007/001
ECS / cheque recurring Recurring entries can Work around
entries to be automated
be
automated
by
maintaining background
scheduling
on
a
particular
period
in
every month.
Credit Note-Debit Note Procedure
010/001
Quantity rebate to be
Work around
automatically
calculated
(On sales as well as
purchase).
010/002
Debit and credit note Debit and Credit note Standard
should be passed in system can be routed through
with reference to vendor or MM and SD module
customers bills so that no with reference to the
double discount should be invoice
or
billing
given to customer against documents.
the same Invoice.
010/003
Purchase Return & Sales Can be captured while Development
Return
should
be developing
the
considered in Purchase Purchase and Sales
Register & Sales Register registers.
respectively.
Bank Reconciliation Procedure
SAP Process
SUPERSEDES: N/A
Status
Customer Master
017/001
Proper Customer
should be possible
017/002
Proper
Vendor
should be possible
SAP Process
SUPERSEDES: N/A
Status
Standard
Standard
Standard
Standard
Not Possible
Standard
Standard
Standard
Standard
Standard
Standard
Page 160 of 189
SAP Process
SUPERSEDES: N/A
Status
Standard
Standard
Standard
Standard
Standard
Standard
021/015
021/016
SAP Process
SUPERSEDES: N/A
Status
Retirement
without Standard
revenue concept can be
used and JV credit to
expenses and debit to
asset can be used in
expenses case.
Asset
cannot
be Standard
depreciated more than
acquisition value.
In
Asset
Master
Physical
verification
date can be maintained
Whether insured or not
insured details can be
maintained in Asset
Master. For insurance
tracking, needs go for
development based on
detailed requirement
CWIP details Assets class Through separate Asset
wise ie. CWIP Buildings, classes for CWIP this
CWIP Plant and Machinery can be achieved
etc. Internal order wise
details (WBS element wise
from PS Module) required
for Pending Capitalization
Assets.
Asset Class wise balances Asset
class
wise
in Asset Module should tally balances
will
be
Standard
Standard
and
Development
Standard
Standard
021/018
021/019
021/020
021/021
021/022
021/023
021/024
SAP Process
SUPERSEDES: N/A
Status
automatically
tallied
with GL balances, since
Asset related GLs are
Reconciliation
accounts.
Plug in Assets can be Standard
directly capitalized or
can be routed through
internal
order
and
Project assets can be
routed the PS module
Physical
verification Standard
date can be maintained
in Asset Master
Needs to be developed Development
a report separately as
per the requirement
SAP Process
SUPERSEDES: N/A
Status
SAP Process
SUPERSEDES: N/A
Status
Additional
duty Standard
condition
percentage
will be maintained as
100%.
026/010
026/011
026/012
026/013
026/014
SAP Process
SUPERSEDES: N/A
Status
Pending
proof
of Standard
exports can be tracked
through EMS and open
items in Cenvat claim
receivable account is
pending
claim
receivable
PLA and TR6 Challan PLA and TR6 Challan Standard
provision to be maintained provision
will
be
in SAP
available
through
Excise JV and PLA
register can be drawn
from SAP based on
Excise group
Excise RG balances should RG register balances Standard
tally with accounts GL will be automatically
balances location wise.
tallied
with
GL
026/015
026/016
026/017
026/018
026/019
026/020
SAP Process
SUPERSEDES: N/A
Status
Standard
Standard
Standard
and
Development
Sales Tax
027/001
027002
027/003
027/004
027/005
027/006
027/007
SAP Process
SUPERSEDES: N/A
Status
Can
be
available
through GL or needs to
be developed based on
the requirement
On basis of GTO calculate Stock transfer details
Stock Transfer % of Out of can be taken from SAP
Maharashtra
and percentage needs
to be derived based on
the information
T-code require for C form, Report needs to be
H form, F form Etc developed based on the
Number update into system requirement
by Sale man after collection
of Forms
No of digit for taxation fields Validation cannot be
and duplication validation possible
should be put
Standard
and
Development
Standard
Development
Manual
check
027/011
027/012
027/013
027/014
027/015
027/016
SAP Process
SUPERSEDES: N/A
Status
Development
Standard
Standard
and
Development
Standard
Standard
Standard
Manual
check
Standard
Service Tax
028/001
028/002
028/003
028/004
028/005
028/006
028/007
028/008
SAP Process
SUPERSEDES: N/A
Status
should be cancelled.
Proper matrix on deemed Deemed
exports Standard
export treatment from sales revenue will be treated
tax and accounts angle
as domestic revenue in
Financial Accounting.
At the time of payment to
Service Tax vendor then
Service
Tax
amount
transfer to Service Tax
utilization account against
the Excise Cenvat Payable.
Service Tax GL wise report
with
Service
Tax
Registration Number of
Vendor
By
maintaining
the
Service tax utilization
account while running
cenvat
utilization
process, this can be
possible
Service tax details can
be
maintained
in
Vendor Master and the
same can be captured
in Purchase Register
Form ST/3 should generate Needs to be developed
automatically
as per the requirement
View report separately.
Needs to be developed
Service Tax/Others (based as per the requirement
on the payment made to
Vendor)
Service Tax/GTA (inward
based on the payment
made to Vendor)
Service Tax/GTA (outward
based on the payment
made to Vendor)
Consolidated
Report
Service Tax GTA (based on
the payment made to
Vendor)
Consolidated
Repots
Service Tax other + Service
Tax GTA Inward (based on
the payment made to
Vendor)
Without service Tax number Manual check
Invoice should not post in
system.
Report for Input Service Details can be taken
Distribution from HO to APL from GL line item report
locations
Utilized Service Tax Link Can be available
with ER/1 monthly Excise
Return
Service Tax Register for as Needs to be developed
per Manufacturing Register as per the requirement
Standard
Development
Development
Development
Manual
check
Standard
Standard
Development
029/013
SAP Process
SUPERSEDES: N/A
Status
Needs to be developed
as per the requirement
Development
Needs to be developed
as per the requirement
Development
Standard
and
Development
Not feasible
Output
Standard
Standard
Standard
030/004
030/005
030006
030/007
030/008
030/009
030/010
030/011
SAP Process
SUPERSEDES: N/A
Status
11 Reporting requirements
Report
Report Requirement
Req. Ref #
001/REP
- Purchase
Register
001
Location wise, state wise
and consolidated
001/REP
- Report of invoices not
002
booked location wise and
consolidated
001/REP
- Statement of Accounts
003
(Outstanding reports for
accounts payable bill wise
and party wise summary).
001/REP
- Statement of Accounts
004
(Outstanding reports for
accounts payable location
wise and consolidated).
001/REP
- Details of Purchases &
005
Input Credit available for
VAT & CST returns.
001/REP
- Report on SME unit
006
outstanding payable
001/REP
- Quantitative and value
007
wise report on purchases
during the year location
wise and consolidated.
001/REP
- For Notes to Accounts,
008
Reports
on
import
purchases
into
two
categories
as
Raw
Material & Capital Goods
giving C.I.F. value.
001/REP
- Purchase register party
009
wise, material wise, form
wise, etc
001/REP
- Forms tracking register010
Forms C, F, H, I, E1-E2
001/REP
- Month wise, location wise
011
and
consolidated
purchase summary in
columnar from.
001/REP
- Bifurcation of purchases
012
into Material wise - Raw
Material, Power & Fuel,
Engineering
Goods,
CWIP/Assets, Services,
Expenses
,
Traded
Input Parameters
Status
Company
Code/Plant/Period
ABAP
Development
Company
Code/Plant/Period
Standard
SAP
Company
Code/Profit ABAP
Centre/Vendor/Period
Development
Company
Code/Profit ABAP
Centre/Vendor/Period
Development
Company
Code/Business Standard
Place/Plant/Period/ Material SAP
Type
Company Code/GL/Period
Standard
SAP
Company
Code/Business ABAP
Place/Plant/Period/ Material Development
Type
Company
Code/Plant ABAP
/Material
Type/Material Development
Group/Period
Company
Code/Profit
Centre/Vendor/
Material
Type/ Material Code/ Period
Company Code / Plant /
Period / Form No. / Vendor
Company
Code/Profit
Centre/Vendor/
Material
Type/ Material Code/ Period
ABAP
Development
Valuation Class
ABAP
Development
ABAP
Development
ABAP
Development
Overdue Company
Code
/ Standard
002
Outstanding
Customer / Profit Centre / SAP
Age days / Date Range
009/REPBank wise Detail of Bills Company Code / GL / Standard
003
Discounted Breakup- Vendor / Date Range
SAP
Vendor-wise
(Reconciliation)
009/REPReport Showing details of Company code / House ABAP
004
packing credit facilities & Bank / Date Range
Development
its utilization.
010/REPDebit Note & Credit Note Company Code / Plant / ABAP
001
Register Location Profit Centre / Vendor / Development
wise, Tax-wise, Purchase Customer
&
Sale
Type
wise,
Material Wise, Vendor /
Customer wise.
011/REP-001 Daily
Reconciliation Company
code /
GL Standard
statement
account / Date range
SAP
012/REPDEPB & Advance License Company
code /
GL Standard
001
register
account / Date range
SAP
013/REPLocation
wise
Trial Company Code / Profit Standard
001
Balance and Consolidated Centre / PC Group / Date SAP
Range / GL
013/REPLocation wise Profit & Company Code / Profit Standard
002
Loss
Account
and Centre / PC Group / Date SAP
Consolidated
Range / GL
013/REPLocation wise Balance Company Code / Profit Standard
003
Sheet and Consolidated
Centre / PC Group / Date SAP
Range / GL
013/REPLocation wise Schedules Company Code / Profit Standard
004
and Consolidated
Centre / PC Group / Date SAP
Range / GL
013/REPLocation wise Fixed Asset Company Code / Profit Standard
005
Schedule
and Centre / PC Group / Date SAP
Consolidated
Range / GL
013/REPSales
made
from Company Code / Profit ABAP
006
warehouses should reflect Centre / PC Group / Date Development
in the profit & loss account Range / GL
of the respective location
and Consolidated
013/REPVirtual Plants to be Plants
Standard
007
created for Bonded Ports
SAP
015/REPReport on Expenditure in Company Code / GL Standard
001
Foreign currency.
Account / Profit Centre / SAP
Date Range
015/REPReport on Earnings in Company Code / Profit Standard
002
Foreign currency.
Centre / Date Range
SAP
016/REPDetail Foreign exchange Company Code / GL Standard
001
revalued report
Account
SAP
12 Output requirements
Output
Req. Ref #
002/001
Output Requirement
cheque printing with payment
advice
Status
ABAP
Development
024/001
026/003
Asset
Depreciation
document
Getting complete details of
RG-A & C
Getting Complete details of
Sales ER-1
As per ER-1
026/004
As per ER-4
026/005
As per ER-5
026/006
As per ER-6
026/007
As per ER-7
026/008
As per RG-1
026/009
MIS
027/001
Purchase Register
027/002
026/001
026/002
027/003
028/001
028/002
030/001
030/002
GL wise Summary
028/003
028/004
030/005
Output Requirement
Status
BDC Format
Format
Table development
User Exit
User Exit
Routine
BDC Format
BDC
ABAP
Development
ABAP
Enhancement
ABAP
Development
ABAP
Enhancement
ABAP
Enhancement
ABAP
Enhancement
ABAP
Development
ABAP
Development
14 Authorizations
Authorization matrix will be prepared as per the Arch role matrix.
GL master records, Customer masters, Vendor masters and Asset masters would be
uploaded through standard SAP functionality LSMW
FI-GL, FI-AR & FI-AP Open Items loaded through LSMW would have Cost Object
assignments like Cost Centre, Internal Order, Profit Centre & Profitability Segment
attached to it.
Cost Centre, Profit Centre Master Data would be uploaded through standard SAP
functionality LSMW.
Inventory of Semi Finished & Finished Goods would be uploaded at the legacy stock
value.
History of Change
Date
Version
Section
Number