RSME Question & Answers

Organizational Structure:

Creation of Company Code: T Code: OX02 (4-character alpha numeric code)

The company code is a smallest organizational unit for which a complete self-contained
set of accounts can be drawn up for purposes of external reporting.

The process of external reporting involves recording all relevant transactions and
generating all supporting documents for financial statements such as balance sheets and
profit and loss statements.

Business Area: T Code: OX03

Business area is an organizational unit of financial accounting that represents a separate

area of operations or responsibilities within an organization and to which value changes
recorded in Financial Accounting can be allocated.

You can create financial statements for business areas, and you can use these statements
for various internal reporting purposes

What Is Business Area in SAP – Why Profit Center Accounting Is Better than
business Area

Business area will have many profit centers. For example Vehicle is a business area in a
company. Vehicle can be cars and Bikes etc. Here Vehicle is business area and Cars and
Bike are profit centers. In broad Vehicle is a profit center. But as it has sub areas those
are profit centers. So profit centers cannot be replaced with business area and vice
versa. We can replace business area by Profit centre, only condition is that it should be
in same controlling area. The business area is more like a business unit of a company.
You can have multiple profit centers within a business area.
Main distinguish factor is that distribution and assessment in possible in profit center
but not in business area.
One more distinction is that Business area need not be attached to any organization
structure. But profit centers can be created only under the controlling area.

Defining posting period variant: T Code - OBBO

SAP FI Posting period variant is used to maintain accounting periods that are open for
posting and all closed period are balanced. This is used for opening and closing period
in the fiscal year for posting purpose.
Open and close posting periods: T Code - OB52
You can assign these posting periods to one or more company codes.

Fiscal year variant: T Code –OB29

In SAP, Fiscal year variant (FYV) is a variant that controls parameters for a

financial year, such as managing financial accounting year and posting period
variants to open and close posting periods.

What is year shift in fiscal year?

Year shift filed is used for non-calendar year fiscal year variants.

+1 indicates that a fiscal year is later than the calendar year.

Ex:
-1 indicates that a fiscal year is before the calendar year.

Period texts
Field status variant: T Code: OBC4

While posting the transactions we need to input many fields like cost center, profit
center, plant etc

In some scenarios cost center will be required (for expense posting) , in some plant will
be required(inventory postings), value date in Bank accounting ....etc

It will be cumbersome (awkward = Uncomfortable) to input all the fileds in all the
scenarios .so we can make the input of the filed as Required (which need to be given to
post the transaction), Optional (we can enter those or we can leave), Display (we
cannot edit the field) and suppressed (will not be displayed while posting).SO we can
set the status of the filed as R/O/D/S

There are 4 statuses for each field:

1. Suppress: The field is hidden in screen
2. Optional: The field is available in screen; you can keep it blank or fill it.
3. Require: The field is available in screen, and you have to fill it.
4. Display: The field is available in screen, but it's grayed out, you cannot fill anything
in here.

Assigning Global parameters to Company Code, T Code OBY6

Global parameters are divided in to two categories.
Accounting organization parameters
Chart of accounts–OB62
Company - OX16
Credit control area – OB38
Fiscal year variant - OB37

Processing parameters

Field status variant - OBC5

Posting period variant - OBBP
Maximum Exchange rate deviation
Company code to controlling area
(Tick): Negative postings permitted
 FI-GL

T Codes for General Ledger Accounting

Business Process Map to SAP
General Ledger Master Data Maintenance
Display Chart of Accounts S_ALR_87012326
Create General Ledger account centrally FS00
Create General Ledger account at company code Level FSS0
Create Primary cost/revenue element FS00
Change General Ledger account at Chart of Accounts level FS00
Collective change on Chart of Accounts data OB_GLACC11
Collective change on Chart of Accounts Description OB_GLACC13
Change General Ledger at Company Code level FSS0
Collective change on Chart of Accounts on company code
level OB_GLACC12
Change Primary cost/revenue element FS00
Display General Ledger Account FS00
Display changes on one General Ledger account FS04
Posting GL Document FB50
General Ledger Document Processing
Post General Ledger document FB50
Park Document FV50
Post Parked Document FBV0
Edit Parked Document FBV2
Delete Parked Document FBV0
Enter Recurring Document FBD1
Delete Recurring Document F.56
Change Document FB02
Change Cross CC Document FBU2
Display Single Document FB03
Display Cross CC Document FBU3
Display Parked Document FBV3
Display Recurring Document FBD3
Display Changes Parked Document FBV5
Display Changed Document S_ALR_87012308
Reversal of Individual Document FB08
Mass Reversal of Documents F.80
Reverse Cross CC Document FBU8
Reset and Reverse Cleared Items FBRA

Chart of Accounts T Code - OB13

In SAP, the Chart of Accounts (COA) is defined at the client level

And assigned to each company code

It is a list of General Ledger account’s master data that fall under different account
groups of a company code. This grouping mechanism helps to develop better financial
reports.

Operative chart of accounts:

The operating chart of accounts contains the G/L accounts that you use for posting in

your company code during daily activities. Financial Accounting and Controlling both
use this chart of accounts. You have to assign an operating chart of accounts to a
company code

Country specific chart of accounts:

Country Chart of Accounts - The country chart of accounts is used to meet the country-
specific legal requirements. Though it is optional to assign to a company code, you
will need such a chart when you work with a different operating chart of accounts the
country chart of GL account number in the alternate account number filed of the GL
master record of the operating COA

Group Chart of Accts

Chart of accounts which is used in the corporate group.

You can enter a group account number as additional information in the G/L accounts of
the chart of accounts you are using. The system checks whether the group account
number exists in the corporate chart of accounts.

Example

If the structure of the chart of accounts is predetermined by national legal requirements,

you can define a corporate chart of accounts. All accounts receive a group account
number which is the same for all accounts of that particular type in various different
charts of accounts.

For consolidation purposes, you can define the balance sheet and P+L by using group
account numbers, i.e. they do not need to be defined differently per country
Account groups creation with different field status: T Code - OBD4

Acc. From To
CoA G Name account account
NCCA SHAR SHAREHOLDERS' FUNDS 1000000 1099999
NCCA LOAN LOAN FUNDS 1100000 1199999
NCCA CURL CURRENT LIABILITIES &PROVISION 1200000 1999999
NCCA FIXA FIXED ASSETS 2000000 2099999
NCCA INVE INVESTMENTS 2100000 2199999
NCCA CURA CURRENT ASSETS,LOANS & ADVANCE 2200000 2999999
NCCA SALE SALES 3000000 3599999
NCCA OTIN OTHER INCOME 3600000 3799999
NCCA NOIN NON-OPERATIONAL INCOME 3800000 3999999
NCCA COGS COST OF GOODS SOLD 4000000 4199999
NCCA DIEX DIRECT EXPENSES 4200000 4399999
NCCA IDEX INDIRECT EXPENSES 4400000 4899999
NCCA DE&T DEPRECIATION & TAX EXP 4900000 4999999
NCCA SECC SECONDARY COST ELEMENTS 9010000 9019999
NCCA INTI INITIAL UPLOAD GL ACCOUNTS 9090000 9099999
Field status for current assets loans and advances

Ex: - Double click on Account control

Define document types (OBA7)

KR – Vendor Invoice KZ – Vendor Payment, KA –Vendor Document

DR – Customer Invoice, DZ – Customer Payment, DA – Customer Document

AA – Asset Posting, AB – Accounting Document, AF – Depreciation Posting

Document type number ranges –FBN1

Creation of GL Masters: T Code - FS00

1. Example: In ECC 6.0 We need to select Radio button for which GL Account we
are creating Example: Balance sheet account Or P&L Statement account.
2. In the Short Text field, enter a short description for the new GL account.

Remaining all are same Control data, and create/bank/Interest

But in S4 HANA given drop down as below

GL account type
1. Balance sheet account
2. Non Operating expenses Or Income
3. Primary cost Or Revenue accounts
4. Secondary cost account
Account group
SHAREHOLDERS' FUNDS
 LOAN FUNDS
CURRENT LIABILITIES &PROVISION
FIXED ASSETS
INVESTMENTS
CURRENT ASSETS,LOANS & ADVANCE
SALES
OTHER INCOME
NON-OPERATIONAL INCOME
COST OF GOODS SOLD
DIRECT EXPENSES
INDIRECT EXPENSES
DEPRECIATION & TAX EXP
SECONDARY COST ELEMENTS
INITIAL UPLOAD GL ACCOUNTS

Give the short text: Capital Account

Sort Key:

Sort Keys are used to populate the Assignment number field in the line items of
customers or vendors or general ledgers.

The content of this Assignment number field can be populated in a customer or vendor
or general ledger document when the document is created:

 either manually
 or automatically by the system

For all GL Accounts sort key is given as 001 (Posting date)

Open Item Management:

Open Item Management in SAP FI. ... Open item means the line item is open and it's
not cleared by a clearing transaction i.e. it's an unfinished transaction in SAP. This
allows us to check whether a particular vendor transaction has been paid or not.
 Parking - FV50
In SAP, User can be provided with Limited Authorization Amount for Posting.

For example, an Accounting clerk has authority to post documents to a maximum

amount $5000.  .While feeding document he finds that the document amount is $10000
for which he does not have the authority.

In such cases, SAP has provided Park Facility for the document which allows the user
to save the document but the amount is not posted in the G/L Accounts .The document
can be later reviewed by High Authority Personnel who has appropriate posting
amount authorization. Once approved, the document is posted in G/L Accounts.

Retained earnings account T Code – OB53

Is used to carry forward the balance from the one fiscal year to the next fiscal year, to
automatically carry forward the balance to next fiscal year. You can define P&L
statements as per COA and assign them to the retained earning accounts.

FI-AP

Define Account Groups with Screen Layout (Vendors) OBD3

1. Local Vendor
2. Import vendor
3. Government Vendor
4. Whole sale vendor Etc.,

Create Number Ranges for Vendor Accounts (XKN1) FOR CUSTOMER XDN1

Assign Number Ranges to Vendor Account Groups (OBAS) FOR CUSTOMER OBAR

Creation of Vendor Master: BP (Business Partner approach in S4) IN ECC =VENDOR –

FK01, CUSTOMER FD01
 FI Banking

Configuration for House Banks. FI12_HBANK

Manual Bank Reconciliation:

1. Create and Assign Business Transactions

Menu path: Financial Accounting -> Bank Accounting -> Business Transaction ->
Payment Transactions -> Manual Bank Statement -> Create and Assign Business
Transactions

Ex: Posting rule ZIN for Incoming payments

Posting rule ZOUT for Outgoing payments

Interpretation algorithm

An interpretation algorithm enables you to find separate outgoing payments using the
reference information returned by the bank.

2. Define Variants for Manual Bank Statement

Menu path: Financial Accounting -> Bank Accounting -> Business Transaction ->
Payment Transactions -> Manual Bank Statement -> Define Variants for Manual
Bank Statement

Ex: Variant: NWSV and Its Name: xyz BRS Variant

3. Define Posting Keys and Posting Rules for Manual Bank Statement

Menu path: Financial Accounting -> Bank Accounting -> Business Transaction ->
Payment Transactions -> Manual Bank Statement -> Define Posting Keys and
Posting Rules for Manual Bank Statement

Create Account symbol – 1.Main bank account, 2. Incoming bank account, 3.

Outgoing bank account
Assign Account to Account Symbol: 1.Main bank account, 2. Incoming bank
account, 3. Outgoing bank account.

Account modification: will be the + Sign for 3 accounts

Currency: Will be the + Sign for 3 accounts
GL Account: Will be the +Sign *1 for Incoming account
Will be the +Sign *0 for the main bank account
Will be the +Sign *2 for Outgoing account

Bank Reconciliation: FF67

Required – Bank key, Bank account, Currency, Statement number, statement date

Configuration for Automatic Payment Program T code FBZP

1. All company code

paying company code

Sending company code

2. Paying company code

Min amount for incoming payment

Min amount for outgoing payment

And assign form

3. Payment methods in country

Payment method For Ex: - T =Bank Transfer

Payment method for = outgoing bank payments

Create payment medium format (/dme_ncsa)

Assign payment medium format (/dme_ncsa)
Create payment medium format: T Code OBPM1: Used together with the DMEE
tree type to uniquely identify a format tree.

Create payment medium format as below

Required master record specification

Radio Button: Street P.O. Box Or P.O. Box Postal code
Posting details: Document type for payment =ZP (Payment Posting)
Clearing document type = ZV (Payment Clearing)
4. Payment methods in company code

Amount Limit:
Minimum Amount:
Maximum Amount:

Foreign payments / foreign currency payments (Select all the three radio
buttons)

Foreign Business partner allowed

Foreign Currency allowed
Customer/Vendor Bank abroad allowed
Also Tick Or Select radio button of Always Payment Advise

Create & Assign payment medium format to bank – OBPM4

5. Bank Determination –

Ranking order: here we need to give Ranking for House banks. through which
payments will be done

Bank accounts enhancement: You want to define a ranking of multiple accounts

for the same house bank. In this case, do not make any settings for the selected
combination of house bank, payment method, and currency in the classic view,
rather define the account determination exclusively in the view "Bank Accounts
(Enhanced)".

Here we have to maintain Bank accounts in order wise

For Ex: there are 1 to 15 outgoing bank accounts are available in one House bank
i.e., BAI So here we have to maintain 1-15 order wise, while doing payments the
system will take as per the available balances.

Available amount: Here maintain maximum available amount

6. House bank: Create house banks and its accounts ID’s

 Data Medium Exchange (DME)

Create DME Tree T Code – DMEE

The DME Tree is divided in to 3 parts
1. Header Level
Structure-Field Mapping Node Rema
Nodes name Length Procedure Node value Level order rks
Date FPAYH-LAUFD C10   DD.MM.YYYY Level1 1  
Company code FPAYH-ZBUKR C4   xxxx Level1 2  
xxxxxxxxxxxxxxxxxxx
Bank Reference FPAYH-DOC1R C24   xxxxx Level1 3  
             
2.Transaction level

Sequence No. FPAYH-LFDNR 5 Structure field Number Level 2 1  

Payment type #NA C4 Constant NEFT/RTGS Level 2 2  

House Bank FPAYHX-UBNKY C15 Structure field SBI OR CITI Level 2 3  

Bank ID FPAYHX-UBKNT C35   10000222 Level 2 4  

Payer IFSC FPAYHX-USWIF C11   CITI0000001 Level 2 5  

Vendor Name FPAYH-ZNME1 C40   Vendor No.11 Level 2 6  

Vendor Bank
account FPAYH-ZBNKL C15   xxxxxxxxxxxxxxx Level 2 7  

Vendor bank IFSC FPAYH-ZSWIF C11   IDBI0000002 Level 2 8  

Currency FPAYH-WEARS C5   INR Level 2 9  

Amount FPAYH-RWBTR P12   300000 Level 2 10  

Trailer Level
Own mapping -
No of Items     atoms Level 1 1  

Total Amount     Aggregation Level 1 2  

 Configuration of DME Tree Technical attributes

Step 1: DME Tree

1. Administrative data

a. Tree type: PAYM ( Which is standard one) XML Tree

b. Format tree: /ZDME_XXXX (it can be created followed by back slash)
c. Description: (DME Format tree for NCSA for APP)
d. Documentation: ZDME_XXXX_DMEE
e. Version must be 0

2. Format attributes
a. Fmt.spec.strct (Format specific structure): If created own format take here

Otherwise follow the standard format

Note: Format specific structure means: created own format in DME tree
and created as a source field.

b. Field type: there are two option here we select 1 (Fields are separated by
Delimiter)

Give symbol (~) for the below

I. In segment group
II. In segments
III. In composites

3. Levels : Levels have to be created In the output file how many times header
data can be printed and how many times transaction level data printed and
how the trailer level it will be printed.

I. Level Repetition factor

0 9999999
1 1 Header Level
 2 9999999 Transaction Level
3 9999999 Trailer Level

4. Sort/Key fields:

The system sorts data selected by the application program according to the
sort fields as they are defined in the format tree. After the data is sorted, it is
transferred line by line to the DME Engine, which is used to generate the
output file.

You can additionally mark sort fields as key fields.

Header date: Here we are mapping structure and source field as date

Transaction data: Here we are mapping structure and source field as

Sequence number

5. File data:

DMEE: Character String Contains Permitted Characters

Normal; only the characters entered above are permitted in the file.

Step 2 Create Segment Group

Segment group (SEG_GRP_BANK): Created the lower level of the DME Tree.

Step 3 Create Segments

Segments (1. Header level 2.Transaction level 3.Trailer levels): Are created under the
segment group.

Header level: we create below segments at lower level.

1. Date
2. Company code

3. Bank Reference

Transaction Level: we create Payment details and under this lower level we create the
following
 1. Sequence Number
2. Payment type

3. House bank

4. House bank ID

5. Payer IFSC Code

6. Vendor Name

7. Vendor Bank Account

8. Vendor Bank ID

9. Vendor Bank IFSC Code

10. Currency

11. Amount

Trailer Level: Trailer level has to be created at the same Transaction level and under
these lower level two elements have to be created as below

1. Number of items: Go to detailed level and give name as Number of item Length
as 40 to 50 and go to mapping procedure and select Own mapping (atoms) then
go to atom handling tab and press F4 button and select Concatenate in element
with spaces.

To print Text as Number of items Or Number as 16 or 5 etc.,

We need to create 2 atoms under the lower level of Number of items

I. Number of items: give the name as Number of items and same in the
description , give length as 15 and go to source field and give field constant as
Number of items
II. Number: give the name as Number and same in the description , give length
as 4 and type as Number go to source field and give field constant as
Number of items

Note: Here we are trying to achieve the how many payments (Number of items)
we are processing through the APP and what is the total amount of all the
transactions.

So that we have to use here Aggregation option: for this one pre requisite is one
technical node under payment details (Transaction level) lower level
And give name as Technical Node give Reference as TECH, Length as 1 & Type
as Number. Then go to source tab give the Constant as 1

After creating reference under payment details as TECH then go to the number
under the Trailer segment click on the number and go to the aggregation give
reference ID as TECH and give the aggregation as Number of occurrences.
 2. Total Amount: Create Total amount under the Trailer lower level and click on
the total amount node and give name as Total amount.

Here we need a reference (Technical node). Go to Payment details under this go

to amount and click on it and give the reference ID as AMOUNT

And go to conversion function give as AL,2

AND SAVE IT

Total amount

Unit testing

Creating vendor invoices

Running APP

And generating DME File

Fixing DME Tree Issues

Issues in the format as below

1. The main issue is the format of file all the transactions are coming in one row
instead of coming one by one

Go to DMEE T Code and click on DME Tree Technical Properties, click on file
data (is for output file) and select the below

a. Carriage returns
b. Line field after this

Coming to the header segment here also we can select the above

Go to consistency check.
2. Date format is coming YYYY.MM.DD Instead of DD.MM.YYYY

Solution: Go to T Code DMEE and click on Date There you will find the Conversion
function at detailed level

Conversion functions are we can change as below

Char
Date
Time
Currency

For the above date format change go to conversion function and click F4 button
And select date format as DD.MM.YYYY

SAVE IT

3. Sequence Number is coming as all 00000 (Zeros) Instead of coming sequence

number

Solution: Go to T Code DMEE and click on Sequence number there you will find
the Length as 5 and its character must be selected as Number at detailed level.

4. Payment type is coming as RTGS for below 2 lakhs amount Instead of coming
NEFT

Go to T Code DMEE and click on Payment type: previously mapping procedure

taken as constant, and length was 4, in source field given as RTGS/NEFT, That is
the reason payment type is capturing as RTGS (First 4 letters from RTGS/NEFT).

Solution: Go to own mapping procedure and right click on payment type

Under payment type create 2 atoms, to print payment type in the output file as
RTGS if the amount will be the >= 2, 00,000/-

1. RTGS: Click on the RTGS and go to condition tab and give source structure
in argument 1 and field in argument 2 and type give as 2 (argument is source
structure field), Operator give as >= Argument 2-1=2,00,000/- and argument
2-2 give as 1 (Argument is a constant)
 2. NEFT : Click on the NEFT and go to condition tab and give source structure
in argument 1 and field in argument 2 and type give as 2 (argument is source
structure field), Operator give as < Argument 2-1=2,00,000/- and argument 2-
2 give as 1 (Argument is a constant)

5. House Bank name is not capturing as per the above configuration.

Correct field & technical name at table level

6. Amount: in amount place coming more than 2 decimals

Solution: Go to T Code DMEE and click on Date There you will find the Conversion
function at detailed level

And select the Conversion function as AL2.

 Electronic Bank Statement (EBS)

1. Create Account symbols T Code OT83

2. Assign Account to account symbols – New entries
3. Create keys for posting rules –Posting rules
4. Define posting rules –New entries
5. Assign external transaction types to posting rules
6. Assign bank accounts to transaction type

Pre-requisites for EBS

1. Create GL Accounts
2. Create House Bank

Create GL Accounts as below T code FSOO

1. Main Bank (House bank) account GL (Current assets loans and advances-BS)
2. Incoming Bank account GL Current assets loans and advances-BS)
3. Outgoing Bank account GL (Current assets loans and advances -BS)
4. Bank Charges GL (Expenses Account -IS)
5. Bank charges Forex GL (Expenses Account -IS)
6. Internet Expenses GL (Expenses Account -IS)

Crate House Bank T Code FI12_HBANK

After creating house bank go to Configuration for EBS

1st Step - Create Account symbols –T code OT83

Account Symbol Account symbol description

Z100 Main Bank (House bank)
Z200 Incoming Bank account
Z300 Outgoing Bank account
Z400 Bank Charges
Z500 Bank charges Forex
Z600 Internet Expenses
2nd Step - Assign Account to account symbols – New entries

Account Account Currency GL Account Account

symbol Modific symbol
ation description
Z100 + + +++++++++0 Main bank
Z200 + + +++++++++1 Incoming
Z300 + + +++++++++2 Outgoing
Z400 + + 4400001 B. Charges
Z500 + + 4400002 B. Ch. Forex
Z600 + + 4400003 Internet exp

1. The above 1st 3 Account symbols are for bank related account symbols. So if
client is having multiple house banks, we have to configure as masking the
Account modification with symbol of (+) as same for the currency (if multiple
currencies are maintaining) and also mask the GL Accounts in the same way.
2. For account symbols Z400 to Z600 are related to expenses GLs so we need to maintain
here GL account number in the GL account column.

3rd Step - Create keys for posting rules

Posting rule Text

Z100 Clear customer –Dr to main Bank account
Z200 Clear Outgoing payment –Cr Main bank account
Z400 Dr . Bank Charges ---Cr . Main bank account
Z401 Dr. Bank charges Forex ----Credit Main bank account
Z402 Dr. Interest ---Credit Main bank account
4th Step – Define posting rules

Z100 – Customer receipt

Accounting entry

Main Bank account Dr….. XXXX

To Customer Account XXXX

Field posting area – Bank Account

Field Document type – ZR (Bank Reconciliation)

Field posting type – 5 (Clear credit GL account)

Z200 (Vendor Payments)

Outgoing Bank account Dr…… XXXX

Main Bank Account XXXX

Field Document type – ZR (Bank Reconciliation)

Field posting type – 4 (Clear Debit GL account)

Z400 (Bank Charges)

Bank Charges account Dr…………..

Main Bank Account

Field Document type – ZR (Bank Reconciliation)

Field posting type – 1 (Posting to GL account)

Step 5 - Assign external transaction types to posting rules

External Transaction +/- Sign Posting Rule Interpretation Algorithm

NTRF + Z100 021 - Reference Document
NTRF - Z200 020 - Document Number
NCHG - Z400 000 – No interpretation

Note: Since external transaction (NCHG) is same for other expenses like Z401 & Z402 here we
cannot assign same posting rule.

NTRF: NTRF is called BTC i.e., Business Transaction Code, with the combination of +/-

And BTC will be assigned to posting rules in configuration

1. NTRF = Transfer Receipts/ Payments

2. NCHK = Payment by cheque
3. NCHG = Bank charges

Step 6 – Assign Bank Accounts to transaction types

Bank Key Bank Account Transaction type

12345 09876543211 MT940
 Vendor number 2005
Customer 26

Statement 1
Main Bank 5000
Direct
Reciepts (26) 1000 deposits 021: Reference number
-
Payments (2005) 1500 Payments 020: Document number
Bank Charges -500 000: No inter pretation
Bank closing balance 4000

1 Post vndor invoice

2 Post Customer invoice
3 Make payment to vendor

Understanding journal entries

Journal entries are divided in to 3 types

1. Payment to vendor.
2. Receipt from customer
3. Direct debit by bank

Payments
Payment to vendor against invoice (Payment method, Cheque/Transfer)

a. At the time of vendor invoice booking (In case of Invoice booking from MM side)

The entry will be:

GR/IR Clearing account Dr…………XXXX

To Vendor account …..XXXX

b. At the time of vendor invoice booking (In case of Invoice booking from Finance
side)
The entry will be

Expenses payable account Dr ………XXXX

Vendor account ……XXXX

When cheque issue to the vendor or transfer payment to the vendor

The entry will be:

Vendor account Dr………………XXXX

To Outgoing clearing account …………XXXX

Note: If we are doing payments through Automatic Payment Program (APP) The
APP will be post the above entry Or Payment can be made through manually
through T code F-53 (Post with clearing)

By the above payment options all vendor open items are cleared and amount will be
parked in outgoing payment clearing account

When you upload the EBS file in to SAP, Then system will post the following entry
(need more clarity uploading EBS File)

The entry will be:

When amount debited to main bank account.

Outgoing payment clearing account Dr…………….. XXXX

To Main Bank account

 Receipts
Receipts from the customer against bill (Payment method direct deposit)

Direct Deposit: In this scenario there is no entry by end user

When you upload bank statement in to SAP system will post the following entry

Main Bank account Dr…………..XXXX

To Customer account …………………XXXX

Receipts from the customer against bill (Payment method Cheque)

a. When you book the invoice (Billing to Customer)

Customer account Dr…………….XXXX

To Sales account ………………………XXXX 9848115440

b. When we receive Cheque/Direct Deposit from the customer

Incoming payment clearing account Dr………….XXXX

To Customer account …………………………………XXXX

c. When amount credited to main bank

Main bank account Dr…………………….

To Incoming payment clearing account

Bank commission/ other direct debit (DD) expenses debited by bank system will post
the below entry

When bank charges debited to main bank

Bank Charges account Dr……………..XXXX

To Main bank account ………………..XXXX
4.

Defining Special GL Transaction like Down Payments. 

Special GL Transaction for Vendor down payments T Code: OBYR 

Payment process

First create vendor advance account and ling it to the main vendor reconciliation
account as linked in the above screen

Second
Special GL Transaction for Customer down payments T Code: OBXR 

Example for Vendor down payment

In the above screen assign special GL Indicator to Vendor Reconciliation account

Special GL transactions are not directly posted to the GL account even though these
are related to the vendor or customer sub ledger accounts.
These transactions are shown separately in the balance sheet.
There are special posting keys/indicators defined in the system to regulate the
postings. You need to specify the special GL indicator like F-Down Payment
request, A-Down Payment etc for processing a transaction. The system will
automatically define the posting keys for posting these special GL transactions.
Posting keys are (09-Customer debit), (19-Customer credit), 29& 39 are for vendors.
There are three types of Special GL Transactions
1) Free Offsetting entries (Down Payment)
2) Statistical Posting (Guarantee)
3) Noted Items (Down Payment request).

There are few Special Transactions in business such as Bills of Exchange

transactions, Down payments Letter of Credit. These special transactions are not
directly posted to the accounts but are posted through the Special GL Indicators
which are reconciliation accounts. An example of down payment made would
further clear:-

1. When you make a down payment to vendor:-

Vendor Spl. A/c Dr. (This is the special GL A/C)
To Bank

2. After MIRO, when you clear down payment: - T. Code F-54

Vendor A/c Dr.
To Vendor Spl. A/c

3. At Final payment
Vendor A/c Dr.
To Bank

FI-AR: Creation of customer Master, Customer Account Groups, Dunning

Program for Customer Accounts and Defining Terms of Payment.  
FI-AA: Chart of Depreciation, Account determination, Screen Layout, Asset Class,
Asset master data.  

Asset Accounting
1. Copy reference chart of accounts: T Code: EC08
2. Assign chart of depreciation to company code: T Code: OAOB
3. Specify Account determination: SAP Menu path: SPRO-> Financial accounting ->
Asset Accounting -> Organizational structure ->Asset Classes ->Specify account
determination.
4. Create screen layout rule: SPRO-> Financial accounting -> Asset Accounting ->
Organizational structure ->Asset Classes -> Create screen layout rule.
5. Define number range interval: T Code –AS08
6. Define Asset Class: T Code - OAOA
7. Determine depreciation area in the asset class: T Code - OAYZ
8. Assignment of general ledger accounts: T Code AO90
9. Specify Intervals & posting rules: T Code – OAYR
10. Define screen layout for Asset Master Data: SPRO-> Financial accounting ->
Asset Accounting -> Master data -> Screen layout -> Define screen layout for
Asset Master Data
11. Define Screen layout for asset depreciation area: T Code – AO21
12. Define depreciation methods: : SPRO-> Financial accounting -> Asset
Accounting -> Depreciation -> Valuation method -> Depreciation key
->Calculation methods -> Define base methods
a. Base method
b. Declining balance method
c. Define multi level method.
13. Maintain Depreciation keys: T Code – AFAMA
14. Depreciation Run: T Code – AFAB

Asset Accounting Unit testing

1. Create Asset Master: T Code – AS01

2. Asset Acquisition with Vendor: T Code –F-90
3. Asset Retirement with customer: T Code –F-92
4. Asset Retirement by scrapping: T Code – ABAVN
5. Asset Transfer: T Code – ABUMN
6. Asset Under Construction: T Code -AIAB
 Integration of FI with MM

OBYC Settings

BSX - Inventory posting

Valuation GL Account GL Account code
Class
3000 Raw Material 223101 (Raw Material)
3040 Spare parts 223102 (Spare parts)
3050 Packaging 223105 (Packing Material)
3060 Consumables 223107 (Consumables)
3100 Trading goods 223111 (Finished goods)
7900 Semi-finished products 223103 (Semi finished goods)
7920 Finished products 223104 ( Finished goods)
7930 Scrap Material 223108 (Stock scrap)

WRX – GR/IR clearing account

Account assignment

Valuation GL Account
Class
3000 GR/IR Clearing article
purchases
3101 GR/IR Clearing services

GBB – Offsetting entry for stock posting

General Modification:
General modification key is a key that has a different meaning depending on the
business transaction and which is used to differentiate account determination. The
meaning is preset in the SAP System and cannot be changed.
Examples: When making offsetting entries for inventory postings, you enter the key
which is assigned to the transaction type and posting string.
General Description
Modificatio
n
AUA Order Settlement
AUF Goods receipts for orders (without account assignment) for
order settlement AUA is not maintained
AUI Subsequent adjustment of actual price from cost center
directly to material (with account assignment)
BSA For initial entry of stock balances
INV For expenditure/income from inventory differences
VAX For goods issue for sales orders without account
assignment object (the account is not a cost element )
VAY For goods issue, sales orders with account t assignment
object account is a cost element
VBO Consumption from stock of material provided to vendor
VBR Internal goods issue (ex: for cost center)
VKA sales order account assignment (for example, for individual
purchase order)
VKP project account assignment (for example, for individual
PO)
VNG scrapping/destruction
VQP sample withdrawals without account assignment
VQY sample withdrawals with account assignment
ZOB goods receipts without purchase orders (mvt type 501)
ZOF goods receipts without production orders(mvt types 521
and 531)

You can also define your own account groupings. Which for those with Z01 thru ZAX it
appears are custom for your company?
If you intend to post goods issues for cost centers (mvt type 201) and goods issues for
orders (mvt type 261) to separate consumption accounts, you can assign the account
grouping ZZZ to movement type 201 and account grouping YYY to movement type 261
 Integration of FI with SD

Go to VKOA and assign GL Accounts along with chart of accounts

We need to create GL accounts and assign here

Condition type Account Account key (T GL Account

assignment Code –OV34)
group
KOFI 01 (Domestic ERB (Rebate Sales 411101 (Sales finished
revenue) deduct) goods)

KOFI 01 (Domestic ERL (Revenue) 411101 (Sales finished

revenue) goods)

KOFI 01 (Domestic ERS (Sales 413601 (Sales discount)

revenue) deductions)
KOFI 02 ( Export ERL (Revenue) 413601 (Sales discount)
revenue)
KOFI 02 ( Export ERS (Sales 413601 (Sales discount)
revenue) deductions)
KOFI 03 (Inter Unit Sales Inter unit 414001 (Sales inter unit)
sales)
KOFI 03 (Inter Unit ERS (Sales 413601 (Sales discount)
sales) deductions)

Handling tickets on priority based as per SLA.  

Updating master data and transactional data using Legacy System Migration
Workbench (LSMW)
Define Object Attributes: Here once you go to LSMW t code and execute it, it’s go the LSM
Workbench screen there you click on Display>>>change button. Once you click on it the screen
goes to change mode there you have to fill the following

1. Object description
2. Tick the data transfer radio button a. Once only b. Periodic
3. Select batch input recoding and fill the recording name and click on recording overview
4. System redirected to new screen: here you have to click on new recording
5. Once you click on it asks you recording and its description (you have to fill it ) and
continue
6. Once you click on continue it asks you the Transaction code which you want upload the
data
For ex: FS00 For GL Master. Once you fill and continue it. It will asks you to create one GL
Master which you what to upload similar data.

II 7. Once you save/create master data. System redirected to GL account master record
maintenance. Here we have to give names step by step whatever we filled in master data
(FS00). Here wherever you filled the data it updated along with table name. so you can find
it easily and you can name it for your convenient.

8. Save it & go back

Define Source Structures: Just create source structure by naming it as GL Master and save it &
go back Define Source Fields: here double click on define source field and go to
display>>>>change. Once you double click on it, it gives you different option then you put cursor
on the structure then you go to table maintenance tab then it gives you the following to update
1. Field name, 2. Field type, 3 Length, 4 Description. Once note down in the excel file go back
and click on the object overview. There you can find all the field names, copy and paste in excel.
And go back to the source structure step and paste all the 4 fields & save it.

Define Structure Relations: Execute & save it

Define Field Mapping and Conversion Rules: Once you execute it, it redirected to field mapping
and rules, here we need to assign, (by putting cursor on each field) different source fields to
target field. And save it

Define Fixed Values, Translations, and User-Defined Routines: Here once you execute it, it will
be redirected to LSMW: Fixed value, Translation & User defined routines.
Put cursor on the fixed value and go the create new: fill as BUKERS as technical name of company
code and description and Company code. And save it, and once again go back and put a cursor on
BUKERS and go to change button & fill all the field like Output length as 4 and Value as company
code (which we are uploading the data through LSMW.

Specify Files: Here we need to prepare excel file by taking all fields which related to GL master
data (ex: filled in the step source structure 1 st column Filed names) and transpose it as horizontal
and fill the master data which you need to upload & create it as text file in text document for
uploading.
One the master data file is ready: Go to specify file and execute it. Then next go to legacy data:
on the PC (front end) and double click on it. It redirected to another window where you can
upload the file and select the required fields as File content: Data for one source structure,
Delimiter: Tabulator, File structure: Field order matches source structure definition, File type:
Record end marker text file, Code page: ASCII. Save it. And go back

Assign Files: Execute assign file and go to display >>>>change button and save it

Read Data: Go to read data and execute it, it redirects to lsm workbench import data for project
1, Accounting GL Master. Again execute. It shows you how many number of items you uploaded.
If its correct go and save it.

Display Read Data: we can check here what fields have been mapped in the GL master data Or
any other legacy data.

Convert Data: by executing converted data, we can check 1. how many transactions read 2. how
many records read 3. How many transactions written 4. How many records read.

Display Converted Data: we can check here what fields have been mapped in the GL master data
Or any other legacy data.

Create Batch Input Session: execute batch input session and select the radio button keep batch
input folder

Run Batch Input Session: Execute run batch input session and its redirected to batch input
session overview. Under this select batch and click on process. Once you click on the process it
give you the another window, there we need to select radio button as display errors only and
another additional function is we need to select as Dynpro standard size.

Start Direct Input Program:

Start IDoc Creation
Start IDoc Processing
Create IDoc Overview
Start IDoc Follow-Up
Master Program for Periodic Data Transfer

Prepared unit testing

Sample document
UT_Newaco_CO_Cos UT script.xls
t Center Master Data Creation.doc
User Acceptance Testing (UAT) scripts

Solving the issues being allocated to me by the Team lead

Analyzing and troubleshooting problems to find optimum solutions.
Discuss with users to get the incident details when required to resolve as early
possible.
Closing of issues within the stipulated time period based on the priority
Prepared unit Testing & User Acceptance Testing (UAT) scripts
Attend status meetings internally along with the team members

Based on given Key Data Structure (KDS) & Business Blue Print (BBP), we Carry
out preparations for SAP customizing and ASAP programming in Controlling
Configured Basic setting of Controlling, Defining Primary and Secondary cost
elements, Cost Center accounting, Profit Center accounting & Product Costing
Preparation of UT Script Document for controlling (CO –CEA, CO-CCA, CO-
PCA & CO-PC)
Preparation User Manuals for End users training for Controlling