SAP Landscape

Development__ Quality__ Production

Development Client

all configuration steps usually takes place in Development Client

all configuration changes are tested by Consultants in Development Client

Quality Client

No Configuration

Configuration Settings are Tested by Clients [Users]

Production Client

No Configuration

End users do the Business Transactions

it's a Live System Environment

Credentials
First we have to ask the IT Person to install SAP Logon Pad and MS Office if they are not
available.

as a Consultant we have to ask the following details where we are going to start work

Client Number ___ we don't use Client No's like 800, 000, and 001 in Real Time.

User ID

Password

Connection Parameters or String ID

once we ask the connection details then we get details like

Description : as our wish wise

Application Server : ***********

Instance Number : ***

System ID : ***

SAProuter String : may be given or not.

How to Add Connection Parameters or String ID

once we get the above details then we have to configure the Development, Quality and
Production Systems

first Create for Development[DEV]

First Click on Create button____ then pop with Screen__ Click on Next __ then it will ask for
following details

Description : as our wish

Application Server : ***********

Instance Number : ***

System ID : ***

SAProuter String : may be given or not.

then click on Finish.

To check for that Click on Right button on respective Connection Parameter and Select
Properties.

Similarly do for the rest of them [ QTY and PRD]

Development BOX

From Development there are 2 Clients within DEV.

Golden Client and Sandbox Client

These two are within the control of Consultant to do Configurations and Testing

Quality Box

it's back up of Production Client. Users can do the testing based on the Configuration in
Development Client and as well as Production Postings to check whether they get issues or not.

SAP Parts
There are 2 parts in SAP.

Configuration Part - SPRO - Golden Client

Postings Part - SAP Menu - Sandbox

SAP Data Types
Three types of data in SAP

 Configuration Data or Table Data

 Master Data
 Transactional Data

Configuration Data or Table Data

all SPRO Data consider as Configuration data or table data. Table data can be moved from One
client to other client using Transport Request whereas Master data and Transactional data
can't move.

Master Data

G/L Master, Customer Master, Vendor Master, Asset Master, House Bank, Profit Center, Cost
Center, Internal Order and Cost Elements etc.., these are the Master Data.

Transactional Data

all postings through different Transaction Codes like FB50, FB60, FB70, F-02, ME21N, etc.....

these are consider as Transactional data.

Transactional data is Controlled by Master Data, Posting Keys and Field Status Group.

About Transport Request

To do the Transport Request T CODE = SCC1 -[ in Target Client]

once we create the transport request then we have to logon to Target Client and then

Source Client = ****

Transport Request = *********

 if we want to check transport request list in source client then use T-Code = SE09
 once we release the TR from Development to Quality then we can't save changes in the
same TR.
 But if we move TR from Golden to Sandbox then whatever changes done in Golden can
save in same TR.
 First we have to Release the Sub TR and then Main TR.
 when we save changes in Request then we have to give Main TR Number or Respective
TR.
 We have to move Transport Request as Dependence [Sequence].
 If we save changes in wrong Transport Request then we have to delete changes in that
Transport Request and do changes then save into correct Transport Request.
  We always have to release TR from Golden Client[where we do Configuration]
 We can't copy sub TR'S {Single Change}from One TR to Other
 if want to copy TR from one to other then we have to give Main TR[Multiple Changes]

If we create any configuration step say like create company code and save in One Transport
Request. and then later do changes and then save in Different TR. when move changes from
one client to other client through Transport request, first move changes whatever done in first
TR 1 and then move TR No 2. do Testing with this Scenario.

Delete and Change TR

 go to SE09 , place cursor on the Transport request and choose delete button.
 we can also change TR , Place cursor on TR and then click on Display Request and
Change button, then choose Properties , now change whatever changes required and
then save it.
 Change of TR is only Possible before release TR. After release then we can't do any
changes.
 Before Release TR, we have to make sure proper settings are ok or any changes done to
existing TR. to check for this expand your sub task until end.

We can also add sub tasks to Main Tasks. place cursor on main task then choose add user.

we can also change owner when we both consultants have to save in same TR. It's just giving
access to other person to save in Our TR.

If both consultants want to save in same TR then add sub task and give access[change owner]
to other consultant to save changes in sub task

Work Bench and Customizing TR

Almost 99 % of Functional Consultants get Customizing Request when they save changes

Almost 99 % of Technical Consultant get Workbench Request when they save changes

Functional People get Workbench request when they usually do Validation, Substitution and
Insert Fields like that kind of Programming Settings

Transport Request from Development to Quality

 To do this first we have to logon to Quality first then follow the steps
 To import TR from Development to Quality Transaction Code in QTY is STMS_IMPORT
 Always we have to give main Transport Request Number to Basis Consultants
 First check whether required Transport Request is available or not.
 Place Cursor on Request and then on Filters, enter if it's not work then click on Refresh.
 if the TR is not available then we have to release TR first in Development.
 once TR is available in Quality then Select TR no then select IMPORT Request
button[Lorry Button]
  we have to give Target Client no, where we import TR in Target Client . select OPTIONS
and then tick the first box. finally enter.
 Once we release TR from Dev to QTY and then if User is not accept Changes, then we
have to come back to Dev and do changes and save in New TR. then release TR from
DEV to QTY, once User is accepted the changes then it's time to RELEASE TR from QTY to
PRD. then we have to provide both TR No. First Configuration TR and Changes TR to
Basis Consultant to Move to Production. these have to be done in Sequence Wise.
 when we import new TR, which has been done Changes to Old TR then we have to
select first 4 check boxes in OPTIONS.

R/3 Structure
R/3 Stands for Real Time 3 Tier Arch structure

 Presentation Layer
 Application Layer
 Data Base Layer

About Data Types and TABLES

We have three types of Data in SAP , that they are

1. Configuration Data or Table Data

2. Master Data
3. Transactional Data

Configuration Data or Table Data

The data which is store in Tables, known as Configuration Data or Table Data.

E.g.: T001, T880, and T004

Master Data

When we create Master Records in SAP that is going to be stored in Master Data.

E.g. : SKA1 and SKB1

Transactional Data

when postings are done[Transaction Takes Place] in SAP that they are going to be stored in
Transactional Data.

E.g. : BKPF and BSEG

Note:

 When changes take place in Table data then the changes are going to be update in both
Transport Request[Transport Request Tables], and as well as Normal Tables
  When it comes to Changes in Master Data and Transactional Postings then they are
saved only in Normal Tables not in Transport Request. it is because of when we do any
changes in Master Data or Transactional Data it doesn't ask for Transport Request.

TABLES

Here are the following tables in which data is stored.

BKPF = Document Header level data

BSEG = Document Line Item Level

FAGLFLEXA = General Ledger: Actual Line Items

FAGLFLEXT = Document Header Level [New G/L]/ General Ledger: Totals

FAGLFLEXP = General Ledger: Plan Line Items

SKA1 = G/L Master [Chart of Accounts]

SKB1 = G/L Master [ Company Code Level]

BSIS = G/L Open Items

BSID = Customer Open Items

BSIK = Vendor Open Items

BSAD = Customer Cleared Items

BSAK = Vendor Cleared Items

BSAS = GL Cleared Items

BSET = Tax Details

WITH_ITEM = Withholding tax info per W/tax type and FI line item

BSE_CLR = Additional Data for Document Segment: Clearing Information

Configuration Data is stored may be in 1 or 2 Tables

Master Data may be stored in 1-5 tables more or less

Transactional Data would be stored in 5-15 tables more or less

Cluster Tables

Cluster Tables Contains both Open and Cleared items

BSEG

FAGLFLEXA

FAGLFLEXT

Index Tables

Index Tables contains either Open or Cleared Items

BSIS, BSIK, BSID, BSAS, BSAK, BSAD

Table FAGLFLEXA

In table FAGLFLEXA we can have a view in Ledger wise. if we maintain New G/L Concept then
we can look at above table.

BSEG

Whatever transaction post in Document then the line items should store in BSEG Table and if
we select document display and then ledger wise selection, now the view documents store in
FAGLFLEXA.

Types of Projects
here we have 5 types of Projects as following,

 Implementation Project
 Support Project
 Rollout Project
 Enhanced Project
 Up gradation Project

Implementation Project

here we define, any Org that is going to adopt SAP from NON SAP Software, where it is require
Initial Configuration as per the requirement of business that is treated as Implementation
Project.

Support Project

when the Org has SAP Software and where it is require Support from respected consultants for
day to day issues in their business activities within Software related then it is consider as
Support Project.

Rollout Project
if the Org is using SAP Software for certain Company codes and they would like to extend the
SAP to other company codes then we have to extend that features to respective new company
codes. it is not that much work required as compared to Implementation Project as we already
done configuration in implementation. so we can extend those features to new company code.

Rollout can be classified as Following

Company Code Rollouts

Module Rollouts

Plant Rollouts

Enhanced Project

when the Org has adopted SAP Software and the features which it has by default, are not
suitable to business requirements then some developments are required to set the SAP in
accordance with requirement of business. Developments should be in a lot not in small amount
of counts, as we also do some developments in Support Project also. This kind of Project is
treated as Enhanced Project.

We always do only developments in Enhanced Projects. the following are some of examples
are Z Programs Creating, Z Programs Developing, Smart Forms, Reports, Preparing Interfaces or
Modifying and Workflows etc.. these developments we treat as Z developments.

Up gradation or Migration Project

whenever we migrate from version wise say for e.g. from version EHP 5 to EHP 6 within SAP
then it is considered as Migration Project or Up Gradation Project.

Implementation
Majorly we Consider ASAP Methodology in Implementation Project.

we have 5 phases of ASAP Methodology

 Project Preparation
 Business Blue Print
 Realization
 Final Preparation
 Go Live and Support

About Questionnaire Prepared by Consultant

as a Consultant we have to prepare questionnaire, which includes the questions that have to
discuss with Client or Core Team Member. Here following are some of Questions that contains
it. as a FI Consultant we have the following Responsibilities

 List of Company Codes that Present Client Has

  have to Implement both FI and CO or not
 are they under same Controlling Area Or not
 are they under same chart of accounts, Same Fiscal Year Variant
 are there any Inter-Company Code Transactions or not
 Consolidation between Company Codes required or not
 New G/L- Profit Center and Segment Reporting Required or not
 Accounting Principles followed to extract trial balance and P& L Accounts
 How many GL's , Vendors, Customers, Assets, Materials are used in Current Business
Process
 Foreign Currency Valuation requirement or not
 APP Settings with DME Required or not
 List of Taxes imposed on Goods & Services
 Dunning Procedure requirement
 Manual BRS or EBRS
 Support of Banking System for MT940 ..
 Interest Calculation. etc..................................................

Project Preparation

as a part of Implementation, this is the first phase where we discuss lot of things about Scope of
Implementation. when Client got a Purchase Order from Consulting Company, the core
members from Client Side and Consultants, including Project Head have a discussion. in this
discussion they introduce each and every one from Higher levels of Client Side as well as from
Consulting Company. They decide time frames to complete each phase, Responsible Persons
from Both sides, Cutover Activities, Project Chart, and Templates like AS IS, TO BE, BBP,
Functional Specs, Technical Specs, GAAP Analysis, Configuration Documents, Text Cases and
Text Scripts, Transport Request Forms, and User Manual Template. It has the following overall
components

 Project Agreement
 Project Scope
 Project Planning
 Project Team
 Software and Hardware Facilities
 Other facilities
 Project Kick of Date

Business Blue Print

before coming to start business blue print, consultant has to prepare a Questionnaire
document for Client where he is going to raise some questions related to business.

in business blue print we have the following docs to be prepared and sigh off by client side.
  AS IS Document
 TO BE Document
 Business Blue Print Document
 GAAP Analysis Document

we, as a SAP consultant must have to take the sign off from client[ Token of Acceptance].

AS IS Document

as is document is prepared by Core team members of Client Business. it is the current business
process of Client. this document includes structure of their business process, i.e. how their day
to day business activities, monthly activities, yearend activities, and how they extract reports.
the following examples give just an idea about of it.

Day to Day Activities:

Posting Vendor Invoices, Customer Invoices, Printing reports to the day, Miscellaneous
Expenditure postings, Daily Reconciliation of Bank, Vendors, Customer Balances. Daily
Payments, Daily Receipts, Daily Interest Run. By the overview it's recording of daily transactions
related to Entire Business.

Monthly Activities

it's recording of monthly related postings. some of those are Monthly Interest Run, Monthly
TDS Reports, TCS Reports, Vendor Balance Reports, Customer Balance Reports, Monthly
Outstanding Payments, Monthly Reconciliation Reports, Transfer of Balances at the end of
Month, closing and open the month at certain point of Month, any valuations etc..... it's all
about monthly dependent Activities.

Year End Activities

here we discuss with client, what business transactions usually take place at the end of Year.
some of examples are, Prepare Profit & Loss Account, Balance Sheet , and Cash and Funds Flow
Statements etc. open and closing Financial Year, Prepare reports for future reference etc....

In the overview of AS IS Document we have get the information related to entire business
transaction on period wise, Category wise, department wise, it's like all financial related
information which would be helpful in Preparing TO BE Document.

TO BE Document

it is Prepared by SAP Consultants as part of their main responsibility in implementation. TO BE

Document is consider as future business process of Client in SAP Software.
Business Blue Print

In TO BE document we just give high level hierarchy. when it comes to BBP we have to explain
in detail. here it's better to go with Part wise[ e.g. G/L , AP, AR, INTEGRATION, ASSET
ACCOUNTING etc..] since as we can get sign off on each part when it's completed so that we
don't need to wait until finish all to get to be sign off by Core Team Member from Client Side.

we have to prepare each and every process in detail in BBP where as we give just higher level in
TO BE Document.

What is BBP- The Process definition document is the main deliverable of business blueprint
phase. the Purpose of this document is to verify that a proper understanding of requirements
has been communicated. The business blue print also finalizes the detailed scope of the project.

GAAP Analysis

if Client business process requirement is not meet in the Standard SAP then we should have to
Provide proper solution to the client.

according to that first, we have to analyze the requirement, if can't find it then should need to
raise OSS Note to SAP. They may give proper solution whether need any developments or any
additional features adopt based on the requirement of Client Business Process.

Realization
once we finish Project Preparation, Business Blue Print then it's time to go with Realization.
Realization deals with the whole Configuration Process and related activities.

The following are activities consider in Realization Phase.

1. Configuration
2. Unit Testing & Integration Testing
3. Configuration Document
4. Test Cases & Test Scripts
5. Functional Specs
6. TR Checklist

Configuration

whatever the configuration required as per the client requirement which have been approved
by client in Business blue Print, is takes place in SAP in this phase. we mention the steps what
configuration have been done in this phase.
Unit Testing & Integration Testing

Unit Testing - whatever we have done the configuration in Golden Client then it has to be
tested in Testing Client[Sandbox]. Normal testing only related to FI is consider as Unit Testing.
it is likely to, post a document, display, change, creation of master data etc....related to FI is
referred as Unit Testing.

Integrated Testing- whatever we do testing with neither cross modules nor cross systems[ e.g.
FI-MM, FI-SD, FI-PP. from Oracle to SAP, TALLY to SAP, Quick Books to SAP.]

Configuration Document

whatever configuration we do in Golden Client that has to be maintained in detail in

Configuration Document. for e.g. Creation of GL Accounts, Customer Master Creation, Vendor
Master Creation , Account Group Creation, etc....- we have to maintain detailed information in
this step.

Test Cases & Test Scripts

Test Scripts - the data whatever we do configuration in golden client that has to be tested in
Sandbox Client. For that testing Purpose we have to maintain some steps.

 e.g. Process Step- for Creation, change, display , delete, block and delete etc...
 T-CODE
 Input Data/ Special Information- data required for this test.
 Test Results
 PASS OR FAIL
 Remarks

Test Cases - whatever we have done in the Test Scripts that has to be presented in the format
of Screen Shots. for example, We post a FB50 document that has to be presented in screen
shot. whether it is working fine or not should be defined in Test Script.

Transport Request Check List

Before move to Final Preparation phase we have to fill the Transport Request form in which we
specify how many Transport Requests have been Created for Configuration Settings. here as a
Consultant, has to fill the some fields related to Transport Request Details. Business Users
usually follow different type of formats for Transport Request. Here some of some of examples
are as follows.

Division - Company Code

Request Type - Workbench / Customizing

Transport Request No - MSD1023250

Source Server/Client - Development

Target Server/Client - QTY/PRD

Tested on - Sand/QTY

Released - or not

TR Owner - Usually when get Support Project Error

Final Preparation
once we complete the Realization Phase then we have to Transport all Change to Final
Preparation where user usually do all testing. in Final Preparation we have following Steps

 User Manual
 User Training
 UAT Assistance
 Cutover Activities

User Manual

once we complete the Realization Phase then next step in ASAP is Final Preparation. within this
Final Preparation the first step is User Manual. here actually user doesn't know about how to
use the SAP so we have to provide User Manual. User Manual is nothing explain the Procedure
in Documentation. For e.g. FB50 Posting. user doesn't know how to post FB50 posting. so we
have to Provide Procedure how to use that, what parameters required to post that FB50 like T-
Code, Company Coder, Document Type, Doc Date, Post Date, Reference, G/L Account, Business
Area, Profit Center etc in Documentation is referred as User Manual.

User Training

once we provide the User Manual to Business Owner then has to give training to Their Users,
Core Team Members and Heads. Training will be provided to users according to their roles.
whenever we provide training to Users then Core Team Member should be also with them. it's
also need to provide training to Heads of business in the areas of Getting reports, in this time
also Core Team Members should be with Heads.

UAT Assistance

UAT refers to User Acceptance Testing. once we provide training to the Business Users, he will
test each and everything by watching test cases and test scripts. once he is satisfied with testing
we should need to get User Acceptance Test Sign off.
Cutover Activities

once we have user acceptance test sign off then it's time to start Cutover Activities. when we
process cutover activities we should need to go with some of following actions carefully,

as a First case, We have to get Trial Balance [TB]

Once we have Trial Balance Sheet, then we should verify whether Debit Balances equal to
Credit Balances.

it's better go with segregation process of Trial Balance Sheet as like follows

 General Ledgers
 Customers
 Vendors
 Assets
 Materials

Before upload Trial Balances into SAP, first we should have to upload Master Data and then
Transactional Data[ Balances]. we do this process through LSMW by Batch Input Method.

Before Upload Master Data first we have to send a copy Excel format sheet to business to enter
data into new excel sheet. once we receive data from them then we have to cross check,
whether data entered correctly or not, list of G/L's , Customers, Vendors, Assets, and Materials
correctly match with Trial Balance records or not.

in addition to the G/L's List provided by Business it should require some Technical and Upload
G/L's.

Note:

 when we upload balances into specific ledgers then we can't post balances direct into
Reconciliation Ledger Accounts.
 it's better to Create New Document Type when we upload Balances.

Technical G/L's

 GR / IR Clearing Account
 SR / IR Clearing Account
 Asset Acquisition Clearing Account
 Retained Earnings Account
 Zero Balance Clearing Account
 FICO Real Time Integration Account
 Profit Center Clearing Account
In addition to the above technical accounts we should require the following upload accounts.

Upload Accounts

 Initial Upload G/L Accounts

 Initial Upload Customers
 Initial Upload Vendors
 Initial Upload Assets
 Initial Upload Materials

Upload of Data Through LSMW and BDC

We can upload the data like Master Data and Transactional Data through LSMW and BDC. But
the process is different.

LSMW - within LSMW we have BAPI and Batch Input Recording methods.

BDC - within BDC we have BAPI and Normal Transaction.

BDC
 in BDC we have procedure like first we have to maintain Recording. For recording
Transaction Code is SHDB. in SHDB we do recording related to business requirement and
then save it. copy fields to Excel Sheet and pass it to ABAP Person.
 He does the field mapping and develop a program. for that program he assign one
Transaction Code and pass it to Functional Consultant[FI/CO, SD, MM]. for example T
Code like ZF11.
 as a FICO consultant, once we prepare Excel Sheet with required data[this excel sheet
data must be related to recording data in SHDB] then copy it word and save it.
 Now execute the ZF11 Transaction Code and give inputs and execute it. then it would
ask you for file, then we have to upload word file which have been saved before. it
would create one batch input session. go to SM35 and run session.

LSMW
Note Points

 if we upload trial balance in mid of financial year then we to upload both P&L Accounts
and Balance Sheet Accounts
 if we do this process at the end of fiscal year then we have to upload only Balance Sheet
Accounts only

Transactional Data Upload T - Codes

 Asset Balances Upload - AS91/OASV

 Inventory Balances Upload - MB1C
  Customer Balances Upload - F-02
 Vendor Balances Upload - F-02
 Normal GL Balances Upload - F-02

 Have two methods LSMW and BDC

 Legacy System Migration Work Bench & Batch Data Communication
 Within LSMW we have methods of Batch Input Recording, BAPI, and IDOC.
 We follow the Batch Input Recording Method as more than others

Not sure about the Transport Request in LSMW

Has the opportunity of Export and Import from one client to other client

we can't do master data in Configuration Client

we can't do LSMW in Production Client Directly.

we usually create in Quality Client and export that, in Production Client import that lsmw data.

For more G/L's it's better to go with Display Errors Only in Batch Input Session. before that we
have to go with process foreground with limited G/L's.

About Material Cutover

First we have to upload Material Master Data and then Transactional Data.

we could do the reconciliation first when we have the Trial Balance. it should match with our
Excel Sheet to Trial Balance.

in SAP, MM-FI Reconciliation can check in Transaction Code MB5L

when upload material wrongly in MB1C, mistake can happen in material master in areas like
due to not upload Quantity related things then has to reverse the document in MIGO by giving
Movement Type 562 . if Price Related Mistakes then have to Reverse the document in MIRO.

Usually it is part of MM consultant but when he does the Material Cutover Activities then there
are two important things to make sure as a FI Consultant that whether he is mention Profit
Center and Price Control & Price. this can be mandatory if we implement the NEW GL Concept.

Upload Master Data- when MM Consultant upload master data for material then as a FI
Consultant we have to make sure Price, Price Control and Profit Center.

Upload Transaction Data- when upload the transaction data then we should have to use one
material Upload account. we have to give Movement Type 561.
Asset Cutover

Before go to cutover activities of asset related we have a expert views to check whether our
configuration is working fine or not. for this purpose we have an option that is called
Consistency Check in Asset Accounting. This is for high level of check with configuration what
we have implemented for Asset Accounting.

Assets can Upload in two different ways

END or START of Financial year or

Mid of the Financial Year

Before Assets can upload into SAP from Non SAP we have to create first Asset Master and then
Asset Values. we have two T Codes to do this AS01 and AS91. Through AS01 we can do only
Master Data Creation, but from AS91 can do both Asset Master Data Creation and as well as
Values upload.

To Perform the cutover activities of asset we have some pre-requisites that have to be
consider.

 Set Company Code Status

 Specify Transfer date/ last closed fiscal year
 Specify last period posted in Prev. System [Transfer during FY]

for Assets cutover we follow AS91.

we have different scenarios for asset upload based on time sense.

 End of Financial Year = APC Value- Acc.Dep Value = Net Book Value
 Mid of Fin. Year with Previous year Capitalization = APC Value - Acc.Dep - Ord. Dep =
Net BV
 Mid of Fin. Year with Current Year fiscal Capitalization = APC Details from Transactions
tab and then Ord. Dep from Takeover Values.

Asset Cutover values can upload through in two ways. F-02 or OASV.

OASV- we can upload total value of asset in this transaction code. without changing any
parameters.

F-02- we can upload total value of asset in this transaction. with changing in OAMK transaction
code. here we have to eliminate the Reconciliation Account for Particular asset.

We can Reconciliation asset balances in ABST2 Transaction code.

Note:

 Table - TABA = Depreciation Posting Documents

 OASV = To Upload the asset values into Asset Reconciliation accounts
  AS91 = To Upload asset master data and transactional date
 OAMK = To Upload asset values in F-02, can remove reconciliation account option
here.
 ABST2 = once we upload all asset data then we can do reconciliation between
asset balance and G/L Balances
 AS01 = To Upload the asset master data.

Types of Testing
here in SAP there are some types of testing exists.

1. Unit Testing
2. Integration Testing
3. Regression Testing
4. Roles Testing
5. Performance Testing
6. User Acceptance Testing

Unit Testing

Checking the Configuration which has been done in Golden System, within one module is
known as Unit Testing. here it is checking configuration whether it is working fine or not in
Sandbox is consider as Unit Testing. it's usually done by Consultants in Sandbox. it is like do
configuration and do testing to come to know configuration working or not. within Unit Testing
we have 2 types of testing. Positive Testing and Negative Testing. Positive Testing refers to,
Testing with reference to specified configuration is known as Positive Testing. whereas Negative
Testing, Testing with Unspecified Configuration.

E.g.

1.here consultant did configuration in Golden Client for TDC and TCS within FI Module. later he
move changes to Sandbox and do testing here. this kind of testing is called as Unit Testing.

2. In MM Module Consultant do configuration for Plant in Golden Client and then later he will
move changes to Sandbox and here he will test whether configuration for plant working fine or
not. like this within module Configuration Check is treated as Unit Testing.

Integration Testing

Checking of results working fine or not in between Cross Modules or Cross Systems is known as
Integration Testing. Cross System testing is also known as Interface Testing. in briefly, Checking
of Configuration Settings and Z programs with Cross Modules or Cross Systems is consider as
Integration Testing.

E.g.

1. Here FI Consultant performed configuration in OBYC Settings which is related configuration

for both FI and MM in Golden Client. later changes will move to Sandbox and do testing here by
posting MIGO and MIRO to come to know whether documents posted correctly or not related
to FI and MM. This type of Cross Module Testing is known as Integration Testing

2. if i am using both SAP and Tally [Non SAP] software, if i want to fetch the data from non SAP
to SAP then we have to develop a program and then migrate data from Non SAP to SAP. Here
we have to test whether the data flows correctly or not from NON SAP to SAP. this kind of Cross
Systems testing is called Integration Testing. once the data flows correctly then do testing for
execution is known as Unit Testing. for example, post a document through FB50, then check
whether documents posted correctly or not.

Regression Testing

if we do any additions or developments or changes to existing Settings then it shouldn't affect

to existing settings later. it should be remain same without any affect on existing.

E.g. we have a document related to Hospital it included Patient Name, Patient No, Date, Time,
Address, Ration Card no. now due to Hospital Requirement they want to add one field say for
example, they want to add Aadhar No field in the document. so once we do development for
existing document by adding aadhar no then later document should not get affect. it must be
working fine without any affect on other fields. this type of testing is called regression testing.

Roles Testing

This testing is usually performed in Final Preparation of Implementation Project. this can be
done by both FI or respective and BASIS Consultants. here we create roles with Transaction
codes in respective of their duties. later we assign roles to respective User ID and Password.
then later we have to check whether that particular user can access only that assigned
transactions or not. this kind of Testing is called Roles Testing.

E.g. I created a role named GL Role and assign transaction codes FB50,FV50,
F-02,FB08,FB03,FB02,FB03,FS10N. Now i have user id : siva123 and Password : t1000. now i will
assign my GL Role to this User ID and Password. so now user id can be access only above
transaction codes. now it is time to check whether above user can access assigned transaction
codes or not, and to check whether he can access other transaction codes. this type of Testing
is called Roles Testing.
Performance Testing

usually ABAP Consultant can take over this Testing with the help of BASIS and other respective
Consultants. here it is, to execute a program or any other application or document etc..,
checking of length of time it would take to get result. This type of testing is known as
Performance Testing.

E.g. i want to see GL Balance reports, when I execute the transaction code FS10N or FAGLB03
and then with inputs in selection screen then i will get output. so here checking duration of
time taken to get output. like this to know any issues during execution related to time we do
this kind of Testing.

User Acceptance Testing

This testing is usually performed in Quality System by Users. whatever the configuration is done
by Consultants in Development System, will be checked by Users to come to know whether
configuration working fine or not.

E.g. Consultant did the configuration related to Automatic Payment Program[APP Settings].
later consultant will check this configuration in Sandbox to know working fine or not, this
Testing is known as Unit Testing. then later he/she move changes to Quality. Here User will
Check whether APP Settings working fine or not. this testing is called User Acceptance Testing.

FUNCTIONAL SPECS
we have to write functional Specs in the following cases. here it is RICEFW

 R - Reports
 I - Interfaces
 C - Conversions
 E - Enhancements
 F - Forms [ Smart Forms ]
 W - Workflows

Reports
Mass Transactional can see in Reports. e.g. FBL1N, FBL3N, FBL5N, FS10N etc....
Note Points

To see all reports in SAP , Transaction code - SAP1

when get a requirement from client that for specific repots then we have to check whether it is
available in SAP or not then only if it is not available then we have to go with Z developments.
to see what are the standard reports in SAP, give a SAP1 transaction code in command field.

A to X = Standard Transactions or Standard Reports

Y to Z = Customized Reports or Customized Transactions

Length and Type can be seen in SE11 Transaction Code.

Forms [Smart Forms]

we have to write Functional Specs for Smart Forms also. Smart Forms are nothing but Printing
Forms where Client Requirement's other than Standard in SAP. writing of functional specs for
smart forms like as Reports.

Note

we usually have print forms for Dunning, Bank Statements, Correspondence- Open Item List,
Account Statement, Cleared Item List, Current Balances etc.. all these for both Customers and
Vendors.

Interfaces
with the help of RFC [Remote Function Call ] we can connect both SAP and Non SAP Systems, is
known as Interfaces. for Interfaces, we have to write functional specs for RFC.

we have both Inbound RFC's and Outbound RFC's.

Inbound RFC

for inbound RFC, we should have 2 RFC. one for connection and download file into SAP and
store it. other for update data into sap.

Outbound RFC

for Outbound RFC we have only one RFC in which it will be used to send the data to Non SAP.

E.g. 1

I have both SAP and Non SAP Systems i.e. Sales Force. if I Create Customer Master Data in Sales
Force that has to come into SAP System. for this i have to develop RFC which will help to
connect SAP and Non SAP System. with the help of FRC Customer Master Data Created in Sales
Force, that will flow into SAP System.
E.g. 2

if we have to maintain exchange rates in SAP then we have to get them from Different Online
Services i.e. Bloomberg, Routers etc....

For this service we have to develop RFC. once we execute RFC then i will go to respective
website server and will download exchange rates. once we have exchange rates in SAP then we
have to execute one Program called RFTBFFOO then it will update exchange rates in OB08.

Note:

 For OB08, RFTBFFOO is the important Program.

 To execute RFC, Transaction Code - SE37.
 To execute BAPI's Transaction Code- SE37
 To execute Functional Module Transaction Code- SE37
 To execute Programs Transaction Code is - SE38

BAPI's
To execute BAPI's we have go to Transaction Code SE37.

BAPI's are executed to perform some activities in background program

Example 1

We usually post documents in FB50, FB60 and FB70 in front screen [ Presentation Layer].

we can post same documents in BAPI as well by executing them in SE37.

To post a document in BAPI, we have to execute two BAPIs.

 BAPI_ACC_DOCUMENT_POST
 BAPI_TRANSACTION_COMMIT

For Instance, we can post document related to FB50 through BAPI.

Process

go to SE37

give BAPI_ACC_DOCUMENT_POST in Functional Module Field and Execute it.

give the input details in DOCUMENTHEADER

 Bus. Trans- RFBU, User Name- SAPUSER, Header Txt- post fb50, Company Code- MKIA,
Doc_Date - 11.09.2017, Postg_Date - 11.09.2017, Trans Date- 11.09.2017, FISC- 2017,
Period-06, Document Type - SA,

now it is related to normal GL, so give inputs in ACCOUNTGL field.

Item No _Acc[line Item]- 1, GL Account - 240000, Item_Txt - Cash as Capital, Company

Code- MKIA, Business Area - MKAB, Profit Center - 1000, place Cursor on line item 1
and add one more line item. Item No_Acc - 2, GL Account - 100000, Item Txt - Capital,
Company Code- MKIA, Business Area - MKAB, Profit Center - 1000.

Now Specify amount inputs in CURRENCYAMOUNT field.

Item No_Acc - 1, Curre - Inr, Amt_Doccur - 500, place cursor on line item 1 and add one
more line item. Item No_Acc - 2, Curre - Inr, Amt_Doccur = 500-

Now Execute it. or it's better to save the inputs as Variant which will be useful. i saved as FB50.
but don't execute it if save as variant

Now come back to SE37 again and give BAPI_TRANSACTION_COMMIT, From Functional
Module on top Select Execute and then Test Sequence. here give first
BAPI_ACC_DOCUMENT_POST and then BAPI_TRANSACTION_COMMIT and then Execute it.

now you have to fill inputs here like Document Header Details and GLACCOUNT Details OR if
you save the inputs previously then From Test Data Directory select Variant and execute then
Come Back here we have to specify Wait - 2 and then Execute. here we get out put RETURN
- 000.

Now go to FB03 and check documents.

Note:

in FB50 or FB60 or FB70 we can't post Automatic Accounts where as in BAPI we can.

in general BAPI's, RFC'S and Functional Module are similar [ more or less].

BTE [Business Transaction Events]

 Transaction Code to Execute BTE is - FIBF.
 For BTE we have to create respective Functional Module in which it has both Functional
work and Technical work.
 BTE is used for to send the Dunning Notes, Payment Advice, Account Statements such as
Open Items and Cleared items through emails to customers and vendors.
 It's also used for to get more line items in FBL3N, FBL1N and FBL5N.
 For Instance, if want to get offset account details like offset a/c name, offset a/c
number and offset a/c type[K,D,S,A,M] in FBL3N then we can Use BTE.

We have two Configuration Steps in BTE.

1. Go to FIBE and from settings__Products__of Customer. new entries here we give ******
Under Product, then give Text, and keep Check box √ below A for Activation.

2. Come back to FIBF, from Settings__Process Modules__of a Customer. New entries, below
Process give ****** for respective requirement, specify Functional Module which have been
developed by ABAPer, and assign Product which have been created in previous step.

Process for Various Requirement

00001040 - Dunning

00002040 - Payment Advice

00001650 - additional line items in FBL3N.

Workflows
workflows are used for Parked documents, Hold Documents in FI, PO in MM, and SO in SD, in
which they have to approved by higher authorities.

for instance, we post a document in FB50 which has a restriction to post. once we park the
document then it goes to higher level for approval through mailing. once he got all that kind of
documents then he will approve and documents post here. this kind of action we treated as
workflow which has to be developed by ABAP.

As a FICO Consultant, he has to know that when user park the document, whether it goes to
higher level authority or not for approval purpose through auto mailing.

when higher level approve the document then whether the document post or not, and if reject
whether the status come to user or not through auto mailing.
FUNCTIONAL CONCEPTS
New GL
In New GL we have 5 concepts such as following,

 Document Splitting
 Parallel Ledger Accounting
 Profit Center and Segment Reporting
 Extended Data Structure [FAGLFLEXA, FAGLFLEXT, and FAGLFLEXP]
 FI-CO Real Time Integration

Document Splitting

in document splitting we have 3 types of splitting

 Active Splitting
 Passive Splitting
 Zero Balance Clearing
Active Splitting

in active splitting if we give profit center or Business Area in one line item then they will updated in
other line items automatically.

for instance- post a document in FB60, here we give vendor and expense line item. we don't give profit
center and business line item for vendor where as we give them for expense line item. from expense
line item business area and profit center updated to vendor line item.

Passive Splitting

in passive splitting we don't present any business area or profit center or segment. with reference to the
document number which has already posted, passive splitting will work by updating business area and
profit center and segment from posted document number. here also active splitting works to update
other line item business area, profit center and segment.

for example- we already post a document in FB60. when we do payment through F-53 here we don't
give any business area, profit center and segment. here with reference to invoice document number it
update the business area, profit center and segment. here we have another line item bank account
which has not mentioned in invoice document number so here active splitting works to update business
area, profit center and segment.

Zero Balance Clearing

when we post a document , if we give different profit centers or business area then zero balance
clearing will trigger.

in addition to the above we have configuration steps for Document splitting.

Parallel Ledger Accounting
 we have leading ledger and non leading ledger concepts in this concept.
 Leading Ledger is provided by SAP by default.
 as per the requirement of Business we configure Non Leading Ledgers [US GAAP, IFRS,
or for other Legal Requirements]
 we can also configure Ledger Groups i.e. Combination of Ledgers for Posting Purpose.
say for example i have 0L, MX[IFRS] and MY[US GAAP] ledgers. i can create MA ledger
group with the Combination of 0L+MX or MB Ledger group with the Combination of
0L+MY. it's all up to business requirement.
 if i post a document in FB50 then it will update to all Leading and Non Leading Ledgers.
0L,MX and MY
 If i want to post a document in particular ledger then i have to use FB50L.


Profit Center & Segment Reporting

Both Profit Center and Segment are Organizational Elements

Segment is a Configuration data and it is Highest Element

Profit Center is a Master Data and it is Lowest Element

Profit Center have a Validity Period where as Segment doesn't have

One Profit Center can assigned to only one segment

One Segment can assigned to multiple Profit Centers

we can lock the Profit Center where as we can't Segment

we can assign Profit Center to Company Code. in other hand we can't assign Segment to
Company Code directly.

For Instance, have a Scenario like following

Profit Centers-------------

1000

2000

3000
Segments-------------------

Retail

Textile

Cement

Wood

from above example if we produce Retail, Textile and wood at profit center 1000 then we can't
assign multiple Segments to One Profit Center. in this case we have to Consider Highest
Element that as we have to Consider Retail, Textile, Cement and Wood as Profit Centers and
1000,2000 and 3000 as Segments.

Extended Data Tables [ FAGLFLEXA, FAGLFLEXT and FAGLFLEXP ]

If we have New GL ----- FAGLFLEXA, FAGLFLEXT and FAGLFLEXP

If we don't have New GL------- GLTO

FAGLFLEXA------- GL Actual Line Items

FAGLFLEXT--------GL Total Line Items

FAGLFLEXP--------GL Plan Line Items

in FS10N we can't get GL balance on Ledger Wise

in FAGLB03 we can get on Ledger Wise Balance

FBL3N give reports on line item wise but not possible through Ledger Wise Line items

FAGLL03 give reports on Ledger wise line item basis

FBL3N reads the data from BSEG Table

FAGLL03 reads data from FAGLFLEXA

FS10N---------------------GL Balance normal

FAGLB03------------------GL Balance Ledger Wise

FBL3N----------------------GL Line items normal

FAGLL03-------------------GL Line items Ledger Wise

Some Note Points

 Group Currency is a Client Level Setting

 Local Currency or Company Code Currency is a Company Code Level Setting
 in OB22 1st Local Currency is triggered from Company Code Creation [OX02]
 In OB22 2nd Local currency -Group Currency[30] is triggered from SCC1
 when we post a document in FB50 or FB01 or in any we can get Local Currency 2
amount type from OB22
 In FB50 we can't give Posting Keys where as in F-02 we can give posting keys Manually.

Validations and Substitutions

 To write the Validation Rule Transaction Code is = GGB0
 To activate Validation Rule with Company Code T Code = OB28
 we can't assign multiple Validation Rules for one Company Code
 we shouldn't create multiple rules in Validation for under one Company Code. we have
to create Step in this case to add any Validation Condition.
 To write the set rule then we have to go to GS01
 SET Rule = Change-GS02, Display-GS03, Delete-GS04.
 Before Transport Validation We have to make sure with Production System by
comparing Steps and then conditions in that Steps.
 We can assign one validation rule for multiple Company Codes.
 while we transport Validation rule then we have to uncheck box named Transport Sets.
 Changes can be save in Transport request.

 To write Substitution Rule Transaction Code is = GGB1

 To activate Substitution Rule with Company Code T Code = OBBH
 If we have Validation Rule for one Particular Field then we can't write Substitution Rule
for that particular field
 If any field not find in Substitute then Go to SM30 and give table name VWTYGB01 and
uncheck the respective Boxes.
 If any Validation or Substitution or not working fine then go to SE38 and then execute
the Program RGUGBR00

User Exit Rule

if Substitution or Validation could not find in Tables like BKPF and BSEG then have to go other
Tables in this case we should use User Exit.
For Example- Company Code = MKIA

Document Type = SA

Posting Key= 21-39

Text should be = Vendor Name

in the above example we can get company code, Document Type, and Posting Key from tables
BKPF and BSEG but not Vendor Name[LFA1]. in this case we have to write User Exit.

Pass BSEG_LIFNR to LFA1_LIFNR and fetch LFA1_NAME1

FI - MM Integration
In FI-MM we have the following steps

1. Purchase Requisition - ME51N - No Accounting Document

2. Purchase Order - ME21N - No Accounting Document
 Material Purchase Order
 Service Purchase Order
 Asset Purchase Order
3. Release Purchase Order - ME29N - No Accounting Document
4. Goods Receipt - MIGO
5. Invoice Verification - MIRO
6. Vendor Payment - F-53 or F110 or F-58
7. BRS - FF67 or FF_5

Movement Type at the time of MIGO is 101

Based on Movement type Transaction keys are triggered.

at the time of PO, in account assignment tab-we can assign here whether is asset or cost
related or service related description. in Item Category Tab- we specify here category of item
say for example service or text or consolidation related etc.....

In transaction keys we assign GL accounts.

at the time of MIGO, Plant is triggered based on PO and GL would be trigger based on Valuation
Class.

in OBYC Settings, Based on Valuation Class GL account is triggered at the time of MIGO.
Valuation Class is Intermediate between Material Master and GL Account.
At the time of PO Under the Delivery Tab If we select GR Non Valuated then no accounting
document post at the time of MIGO, Only Material Document will post.

Note Points

 In FI-MM Integration, Movement types are linked to Transaction Keys. in transaction

keys we assign the GL accounts. Transaction keys are placed in OBYC.
 when we do PO here we give Vendor, Material and Plant. no accounting document is
generated here.
 At the time of MIGO accounting document is generated here. entry is like Inventory and
Clearing Account. Inventory account is picked from BSX. based on Valuation Class and
Plant it picks respective inventory account. valuation class is assigned in Material
Master and Plant is given at the time of PO. in OBYC we combine the Plant and
Valuation Class.GR/IR or SR/IR account will be picked from WRX Transaction Key. in WRX
also we assign Valuation Modifier[Plant] and Valuation Class.
 At the time of MIRO, accounting docs generate like GR/IR or SR/IR and Vendor accounts.
Here Vendor is picked from PO and GR/IR or SR/IR from WRX Transaction Key.
 at the time of Tax accounts, these are picked from Conditions Tab in PO. Condition
Records are Maintained in FV11. Tax GL's are linked to Account Keys in OB40 and these
Account Keys are linked to Tax Procedure.

FI-SD
Sales order - VA01

Outbound Delivery - VL01N

in outbound delivery movement type is 601

at the time of delivery we have 1. Picking Request - No accounting document

and 2. Post Goods Issue [PGI] - COGS A/C DR and Inventory a/c CR

Billing = VF01.

general entry like Customer Account is Debit and Sales revenue account is Credited.

Note Points

 at the time of PGI in Delivery accounting entries are COGS and Inventory. COGS is
picked from GBB Transaction Key and Inventory from BSX In OBYC Setting. in GBB we
give Valuation Modifier, General Modifier and Valuation Class. with the combination of
Valuation Modifier, Valuation Class and General Modifier GL'S are assigned. Valuation
Class is Assigned in Material Master and Plant is given in Sales order along with Material.
Inventory account is also picked same as above except General Modifier assignment.
 at the time of Billing Account entries are picked from VKOA Settings. here entries like
Customer, Sales Revenue, Sales Discount, Freight Revenue and Tax accounts.
  Customer account is Picked from Sales Order and other entries except Tax are picked
from VKOA Settings. in VKOA, V-is for Sales & Distribution, KOFI- is for account
determination for FI, AAG for Customer-which is picked from Customer Master, AAG for
Material-which is Picked from Material Master. Account keys are Picked from Pricing
Procedure. Tax accounts are picked from Conditions Tab in Sales Order. Condition
Records are maintained in VK11. Tax related GL's are linked to Account keys in OB40.
These account keys are linked to Pricing Procedure.

Account Determination in OBYC & OB40 at the time of Transport Request

When we do any changes or doing any configuration then we have to save in Transport Request
in Golden Client and then have to Release to Quality, Later to Production. Before release TR we
have to Cross check with Production Client to Avoid the Overwrite issues.

For Example,

Development Production

Transaction key - BSX Transaction Key - BSX

GL’s assigned in BSX - 19 GL’s assigned in BSX - 25

if I do any change or configuration like add one more GL in BSX in Development Client and save in
TR and then release TR to Production then all 25 GL’s gone in Production and will be 20. This is
because of overwriting by new change in Development. Now the GL’s as
GL’s assigned in BSX - 20 GL’s assigned in BSX – 20
If we want get back all 25 TR’s in Production then look for Old TR which has been released with 25
GL’s.
So always is care full before release TR with this setting to Production. Check with Production
Client and Development Client. For instance take above example; we have 19 GL’s in DEV and 25
GL’s in PRD. In this case first copies the rest 6 GL’s to DEV manually and then does required change
or configuration and save in TR which will be released to PRD later.
Note
This kind of Precaution has to take when we do settings for OBYC, OB40 and Validations &
Substitutions.
Copy all PRD and DEV Transactions in Excel format and check with True or False formula appliance in order to check
all GL’s with respective Valuation class and Plant are same or not.

DMEE

FS00

APP

FOREIGN CURRENCY VALUATION

OBY6