0% found this document useful (0 votes)
206 views44 pages

Real Time Course

The document provides an overview of key topics related to an SAP implementation project including: 1. The system landscape which describes the different environments like development, quality, and production. 2. Transport request management which is used to move changes between clients. There are customizing and workbench requests. 3. Types of testing conducted like unit, integration, regression and more. Integration testing is done in quality and unit testing in development.

Uploaded by

Venu Gattamaneni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
206 views44 pages

Real Time Course

The document provides an overview of key topics related to an SAP implementation project including: 1. The system landscape which describes the different environments like development, quality, and production. 2. Transport request management which is used to move changes between clients. There are customizing and workbench requests. 3. Types of testing conducted like unit, integration, regression and more. Integration testing is done in quality and unit testing in development.

Uploaded by

Venu Gattamaneni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 44

FICO Real time Course Content

1. System Landscape
2. Transport Request management
3. Types of Testing
4. Types of Projects
5. ASAP Methodology
6. Incident management & Change Request Management
7. Deliverable documents in Implementation project from each phase.
 QADB (Question and Answer database)
 Baseline configuration document
 GAP analysis
 FSpecs (Functional Specification)
 Test cases
 BPML (Business Process master List)
 BPP (Business Process Procedures)
 BDD (Business Design Documents)
 Process flows
 End-user manuals
 Cutover Activities
8. LSMW (Legacy System Migration workbench)
 Master data uploading
 Transactional data uploading
9. BDC (Batch data Conversion)
10. BAPI (Business Application Programming Interface )
11. Complex Incidents faced in real time (very very useful for interviews)
12. How to Raise OSS message?
13. Maintain Authorization Profiles
14. How to write Queries in SAP?
15. SAP Imp tables & maintenance and programs
16. New GL accounting features
17. Integration FI-MM & SD
18. Maintain Validation and substitution rules for business requirements by using SETs.
19. ALE Idocs (Application Link Enabling-Intermediate Documents)
20. PRICEFW objects
 P-Programs
 R-Reports
 I-Interfaces
 C-Conversions
 E-Enhancements
 F-Forms
 W-Workflow

21. Auto Clearing

Assistance on resume preparation and Interviews handing tips

Page 1 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
1. SYSTEM LANDSCAPE
1. What is System Landscape?
System Landscape is a key design decisions for distributing the SAP applications
across the servers.

The System Landscape is design by BASIS

DEVELOPMENT QUALITY PRODUCTION

100- Golden Client. 100-Testing Client. 100- Pre Production.


110- Golden Test Client. (Integration Testing) 110-Production Client.
120-Sand Box. 110-Training Client.

I. Development Server – Development System – Development Environment:-

1. Client 100- Golden Client- Development Client – Configuration Client: This is the Client
where the functional teams perform configuration activities and ABAP team develops the
Programs, Reports etc. as per the client requirements.

 We should not post transaction data in this Client.

 We should not create any master data unless they are mandatory for maintain account
determination for automatic postings.

2. Client 110- Golden test Client – Development Test Client- Configuration Test Client:

This is the client where we do most of unit testing by functional team and development teams.

Where do you Perform Unit Testing?

Ans: Development Test Client.

 This Client is not modifiable.

3. Client 120 – Sand Box: This is the client which used by Configurations and developers to do
research and prototyping of how to fulfill of project requirements and to do experiments to their
Skills.

In Sandbox client, the system doesn’t generate transport request.

Page 2 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
II. Quality System – Quality Server – Quality Environment.

1. Client 100- Testing Client: This is a Client where we do perform Integration Testing by
Functional Teams.

This Client is also not Modifiable.

Where do you Perform Integration Testing?

Ans: In Quality System.

2. Client 110 – Training Client: This is a Client where we prepare end user Manuals and
Conduct training for end users.
Q: In which phase of the project road, we conduct end users training?
Ans: Final Preparation Phase.

III. PRODUCTION SYSTEM:


1. Client 100 – Pre production Client: It is nothing but a mirror of production client.
Generally this client would be

 Used to upload transactional data into SAP before production system.

 Used to simulate the similar kind of issues in production systems for further
analysis

This client is also not modifiable.

2. Client 110- Production Client: This is the client where the end users post day to day live
business transactions.

 This client is also not modifiable.

 The consultant should not create any master records and post any transactions in this
client.

Page 3 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
2. TRANSPORT REQUEST MANAGEMENT
Transport Request is like a vehicle which is used to carry/move the changes from one client to
another client.
How Many types of Transport Requests:
1. Customizing request.
2. Work Bench request.
1. Customizing Request: Generally the customizing request would be generated for all
customizing activities done by functional consultants. Ex: Company code creation, Define
Chart of accounts, Set up APP settings etc.,
This is a client Dependent request.
It means, the changes will be available only in that particular client.
2. Work Bench Request: Generally, the Work Bench request would be generated for all the Z-
objects done by ABAP team,
Ex:-Developing programs, reports, Interfaces, Forms etc.
Additionally, the workbench would be generated for few IMG activities done by functional
consultants like “Transport Validation and substitution rules maintained, Create Variants.
This is a client Independent.
It means, the changes saved under workbench request would be available across all clients in the
server.
How many types of request status available in SAP?
They are mainly two types of status for each request.
 Modifiable.
 Released.

1. Modifiable: Once transport request is created either it is customizing request or workbench


request by default it would be in modifiable status; So, it can be used for saving all the
changes required again and again.
2. Released: Once Transport request was released it can’t be reusable for further changes.
How to release transport request (TC: SE09 / SE10):
 User: SAPUSER.
 Select Customizing request check box.
 Select Modifiable check box & deselect released check box.
 Select display button.

Page 4 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 Expand the transport request number.
 Keep the cursor on customizing task number.
 Click on release directly button (F9). (Truck symbol).
 Keep the cursor on Main request number.
 Click on release directly button.
 Click on refresh button.
 Select back arrow button.
 Deselect Modifiable check box & Select released check box.
 Select display button.
How to Import the changes from one client to another client:
Ex: Development: 100 to Development: 110 in same server.
 Go and Login to Target client.
 Go to TC: SCC1.
 Source Client : 100
 Transport Request for instance: DM0K900055
 Select Including Request Sub Task.
 De select test run check box.
 Select Start Immediately button.
 Click on Refresh button.
 Go and Check Changes.

How to Import the changes from one Client to another Client from different Servers:

 Go and Login to the Target Client. (Ex: Development 100 to Quality 100).
 Go to TC : STMS (STMS : SAP Transport Management System)
 Click on Import overview button & Press enter.
 Double click on Transport request number.
 Specify the source client (Ex: Development 100).
 Click on refresh button.
 Go and check the changes.

Page 5 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
3. TYPES OF TESTING

1. Unit Testing
2. Integration Testing
3. Regression testing
4. Negative testing
5. User Acceptance Testing (UAT)
6. Performance Testing

Unit Testing:-

It is nothing but a piece of testing. Means, where do we perform testing for one object is called as a
unit testing.

EX: Create G/L master record, Post G/L document, delete cost element, etc.

Integration testing:

It’s kind of testing where we conduct testing for more than one object is called as an integration
testing.

EX-PTP cycle (procure to pay/FI to MM process), OTC (Order to Cash/FI-SD process), Automatic
Payment process (APP), etc.

Where do you conduct unit testing and integration testing?

Ans: - Unit testing is performed in development server in golden test client

Integration testing is performed in quality server.

What is the tool that you have used for testing in your company?

Ans: HPQC (HP quality center),

Regression Testing:-

This is kind of testing where we perform testing for the existing objects, to ensure the existed objects
got affected due to the new changes done in the system.

Ex: When you configured settings for new company code-2000, performing the testing for already
existed company code -1000 is called as regression testing.

OR

When you develop a new program/object, performing the testing for already existed related program,
is called as a regression testing.

Note: - Generally, the regression testing is performed in supporting projects, not required in
implementation projects.

Page 6 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
Negative testing:-

It means, performing the testing with incorrect values is called as a negative testing.

Ex:-when you develop a program for a particular company code-1000, it should work only for the
company code -1000.It should not work for any other company code. However, here, we need to
perform testing with company code-2000 is called as a negative testing.

User Acceptance Testing:-

Performing the testing on the objects by end users/core business users to check whether the changes
have been done as per the requirement given by them.

Performance Testing:-

The performance testing has to be performed by the BASIS team to check the system’s performance
and to specify the time limit for the execution of the programs.

Page 7 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
4. TYPES OF PROJECTS
1. Implementation project / Development Project.
2. Support & Maintenance Project.
3. Up gradation Project / Migration Project.
4. Roll out Project.
Implementation Project: It is a Pure development kind of project where we map / design client
business requirements in SAP system for the first time by using ASAP methodology.

Supporting & Maintenance Project: After implementing the SAP successfully for the Client
business requirement, we would provide continuous support to the client on to maintain day to day
business transactions.

Roles & Responsibilities:

 Issues Resolution.
 Provide assistance to the users during month end and year end activities.
 Configure the new activities to the existing system as on when required.
 Keep maintain documentation for all the changes done the system.
 Provide Process Improvement suggestions.
Up gradation / Migration Project: Migrating from old version to new version is up gradation
project.
Ex: From 4.7 EE to ECC 6.0. or ECC 6.0 to ECC 6.0 EhP 7.0
Roll out Project: Implementing SAP for another country / Plant / Legal entity based on existing
country / existing one. They were already in to SAP for long back.

Page 8 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
5. ASAP METHODOLOGY
It’s a Methodology/Process which we have to follow implement SAP Applications successfully
to the client as per their business requirements. It contains road maps of 5 phases

1. Project preparation
2. Business blueprint phase
3. Realization phase
4. Final preparation
5. Go live And Support.

1. Project preparation:
 Prepare project plan by project management.
 Recruiting the team members
 Prepare SOW (Statement of Work)
 Setup SANDBOX server by BASIS team
 Interacting with client business team and analyze their business process and
understand their requirements.
 Collecting the existing client business (AS-IS) documentation.
 Conducting the SAP awareness training to the core team members
 Identifying the GAPs.

Documents are company’s property.

2. Business blueprint:
 Conduct Kick off meeting to the Business blueprint phase.
 Conducting the workshops
 Prepare all deliverable documents: QADB
 Base line configuration documents:
 Gap Analysis Documents
 BPML (Business process master list)
 BPP (Business process procedure)
 BDD (Business design documents)
 Process flow documents
 Design future state SAP system
 Functional Specifications (FS) for all PRICEFW objects

3. Realization phase:
 Development server will be setup by BASIS team
 Conduct KT sessions to the technical team on FSpecs.
 Configure the settings required based on the baseline configuration document.

Page 9 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 Technical specifications (TSpecs) will be prepared by ABAP team based on the FSpecs
approved.
 Provide test data for all the development objects (PRICEFW objects)
 Resolve the defects raised during the testing.
 Involved in preparation of end user manuals.
 Involved in unit testing
 Prepare test cases and execute.
 Capture the test results of unit testing

4. Final preparation phase:


 Involved in all kind of testing phases
 SIT (system integration Testing)
 BIT (Business integration testing)
 BUT (Business users Testing) or UAT (User Acceptance Testing)
 Conduct training to the end users
 Quality server will be setup by BASIS team
 Performing the cutover activities
 Production server will be setup

5. Go live and Support:


 Moving all transport requests into production environment.
 Involved in post (implementation support) go live activities/ hyper care support.

Page 10 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
6.1. INCIDENT MANAGEMENT
What is incident?

Ans:- It can a Issue, Request, Problem

How Many Levels of Supporting you’re providing your client?

Ans:- Service Level 1 (SL1)

Service Level 2 (SL2)

Service Level 3 (SL3)

Service Level 4 (SL4)

Service Level 5 (SL5)

Service Level 1: Incident Management

*Resolving all incident raised by user

*Providing Assistance to the User during month end Closing Activities

*Clarify all user doubts/concerns/Questions etc.

*Process implements Suggestions (PIS)

Service Level 2: BASIS Administration

Service Level 3: Change Request Management

Service Level 4: Project Management

Which handle the project like implementation of New GL functionality, E –Invoice Process, SERA
Functionality, Implementing Bank communication Management (BCM) in APP

Service Levels: Problem Management

The issues which are occurring repeatedly the objective of problem is to prevent the problems from
happening to eliminate re occurring incidents

How many types of priority for an Incident

1. Critical
2. High
3. Medium
4. Low

Page 11 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
What is SLA?

Ans:- SLA is Service Level Agreement , Between Service provider and Customer with terms and
conditions

SLA for your Client?

It is

1. Critical – It Should be resolve within One Hour


2. High – within one working day
3. Medium-within three working days
4. Low – within 10 working days

How many types of status for a Ticket?

1. New :- When the Incident was created newly


2. Open :- When the Incident was not customized by any team after creation
3. Assigned :- When the Incident assign to any team member
4. Working Problem:- When the Consultant has started to working on the incident
5. Pending :- Pending with Customer
6. Cancel :- Where it cancel duplicate issue
7. SSO :- Single sign out (where consultant login in real time environment)

1. Pending with Customer

Where consultant requires inputs or Closing confirmation from the User

2. Pending with Vendor

Where consultant is working on the incident with OSS Team due to Product related issues

*Resolve: - where the resolution has prove to the user and accepted to close it

*Close:-Where the Incident was closed

*Reopen:- Where the incident was be open by the use to unhappy/un satisfaction on the resolution
provide by the consultant after closed the incident

How many Number of Incidents do you receive monthly?

Ans: 50 – 60

How Many no of Incident did You Resolve?

Ans:- 10 -15

What is team Size in Supporting Project?

Page 12 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
Ans:- 5 – 6

What is Ticketing Tool?

Ans:- Remidy ITSM7

Many of Ticketing Tools?

1. Remedy
2. Service Manager
3. SD Man

HP SD (Service Desk).

Page 13 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
6.2. CHANGE REQUEST MANAGEMENT
It is a request from business team to make the changes to the existing system
Ex: The change can be any configuration activity or development objects
Types of Change Request:
1. No impact CR (NIC)
2. Emergency CR/BUG Fix CR
3. Normal CR
4. Baseline CR
5. Capacity CR
No Impact CR: It is pre-approved transaction list we don’t require any further approval to work on
the CR

Emergency CR/BUG FIX CR


It is a kind to Change request where the incident leads to create a change Request for the Incident
Resolution
The Emergency CR must be created with reference to incident number
The Emergency CR is created by Consultant
ABAP Consultant called BUG Fix CR

Normal CR

 Base line CR: if any change requires less than 8 working days then it would be treated as a
Baseline CR
 Capacity CR: If any a change requires more than 8 working days then it would be treated as
a capacity CR
 SLA for Incident Acknowledgement
 If it is Critical :- It should be acknowledge within 10 mints
 High :-It should be acknowledged with in 1 Hour
 Medium :-It should be acknowledged within 1day
 Low :-within 1 working day.
Capacity CR: If There is any development can be Object (PRICEFW). Which Requires more than 8
working days is treated as Capacity CR The Change of the CRs will be moved to production System
only in the released Ex:( Quality Released )

Emergency CR / BUG CR:


It is a kind of Change request which has to be created by consultant with reference to Incident
Created by User.
Status: When the Incident was duplicated by user we can cancel the Incident and the Status will be
cancel Status
The Emergency CR is created by Consultant.

Page 14 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
9. BDC (Batch data Conversion)
It is a complete ABAP program. It works by simulating the User input from
Transaction screen via ABAP program.

It is mainly used to upload Transaction data or Master data into the SAP system.

Difference between LSMW & BDC:

LSMW BDC
LSMW is used to straight forwarding BDC is also used to upload Transactional
data Data with more conversional rule and for
creating automatic line items.

How to record the object in BDC development:

1. Go to T.Code: SHDB
2. Click on new recording button
3. Recording PARK_DOC or ASSET_DOC (Any master data upload)
4. T.Code: F-65
5. Start recording (Ref= Check double invoice) ==> ENTER
6. Document date/ Posting date/ Doc type/ Co. Code / Currency/ Period/ Ref Header
data.

Page 15 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
12. How to raise OSS Message
OSS: Online Service System

Generally we would approach OSS team for the issue which are related to SAP Product by using SID
in service market place

Go to

 www.service.sap.com
 Click on SAP Support portal button
 Click on Report an incident button
 Click report and SAP Incident button
 Enter User ID & Password
 Choose System (Which system you facing Problem)
 Enter Key words of the issue in search item field
 Select the component
 Ex: AP_AP_

Path:- Financial A/c  AP Basic Structure

1. Click on Continue Button


2. Click on Create Incident Button
3. Select the Priority

Description:

 Enter Short description about issue

 If you want to enter Screen No

 You want to attach the file you can attach


 Click on send Incident Button

Note: One Number will generate

 Go to home Screen
 Click on View My Incident Button
 Click on View my Incident on request Button
 Ex: Difference between FS10N & FBL3N both are not matching
 Ex: FI MM in Balance

What is OSS Note:

Ans: OSS Note are online documents published by SAP which contains information related to

 Product Error
 Product Modifications
 Product upgrade

Page 16 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 Consulting Note
 Customizing Note
OR
OSS Note are corrections & Suggestions given by SAP for the Standard Objects

What is T code to upload OSS Note into SAP System?

Ans:- T Code - SNOTE

This activity only basis team not by SAP Consultant.

Page 17 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
13. MAINTAIN AUTHORIZATION PROFILES
1. Create role:

 Click on create role button in easy access screen (PFCG), Role name: AP_ROLE (text)
 Click on create button, Dec: Role for Accounts Payable
 Click on SAVE
 Click on MANU button
 Click on Add Transaction button
Transaction Code: FB60, F-43, F-44, ME23N, FBL1N, FB65, F110 & SU53
 Press ENTER ==> Assign Transaction Button
 After press ENTER save it
 Click on Authorizations Tab
 Scroll down
 Click on Change Authorizations tab button

NOTE: Here you would like to control the Authorization Organizational unit level you can enter
Organizational elements like Co. Code & Purchasing Group.

 Click on Enter & SAVE

NOTE: To control the access at activity wise

Ex: Create Change, Display & Delete etc. Expand the Financial Accounting

 Click on SAVE

NOTE: Here system will generate a Default profile for the Role

 Press ENTER ==> Click on GENERATE button


 Once again click on GENERATE button
 SAVE & select back arrow

NOTE: In case the profile was not generated successfully, Click on once again GENERATE button
& Save it.

2. How to create User IDs (SU01):

 Enter User name: KVREDDY


 Click on Create button
Title: Mr.
Last name: KVREDDY
First name: Nil
 Click on log on data tab
Initial password: welcome123
 Click on Defaults tab
Note: If you would like to change the Dismal format & Date format

Page 18 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 Click on Parameters tab (Functional Consultant job)
Note: In case you would like to value as default field
Ex: Co Code & Controlling Area etc.

How to find the Parameters id:

 Go to the particular field


 Keep the cursor in the field & Press F1
 Click on Technical information button
Ex: Parameters id: BUK for Co Code

Note: Parameters id & Role will do BASIS Consultant

 Click on parameters tab


 Parameter id: BUK
 Parameter value: 1000
 Click on Roles tab
 Role: AP_ROLE ==>ENTER

Note: If you would to change the date ==> save it

 Go on Logon with User id Created


Client: 800
Password: welcome123 ==> ENTER

Note: You can see here User menu Sap menu

 Enter new password


 Repeat password
 Enter ==> Once again Enter

Ex: Here we can see the 2 ways

 User menu
 Sap menu

You are not authorized to see use T.Code: F-47

 After you get the message Enter T.Code: SU53


 You need the send screen shot & Send it to BASIS Consultant

How to add additional T.Code to the Role:-

Go to T.Code: PFCG ==> Enter the Role Ex: AP_ROLE ==> Click on Change button.

 Click on menu tab


 Click on add Transaction button
 Enter the Transactions ==> Enter ==> Save
 Click on Authorization Tab Scroll down

Page 19 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 Click on Change Authorization tab button
 Click on Generate button ==> Click on once again Generate button ==> Save

How to Unlock the User id:

 Go to T.Code: SU01
 Click on Lock button
 Click on Unlock button ( Master user id: DDIC/SAP* & PW: 19920706)

Page 20 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
14. How to write Queries in SAP
a. Go to SQUI
b. Enter Quarries name ==> Execute
c. Menu ==> System ==> Status ==> Copy the Program name
d. Go to T. Code: SE93
A to X = Standard T.Code
Y to Z = Customized T.Code
e. Click on create button
f. Display GL ACCOUNT management with open item (short text)
g. Select “Program and Selection Screen (Report Transaction)”
h. Enter ==> SAVE ==> Package ($tmp) ==> Enter (SE38)

List out Vendor Account with particular Recon a long Description:

 LFA1 = General Data


 LFB1 = Co. Code
 LFM1 = Purchase order

SE11 ==> To Check Tables Exit or Not.

Page 21 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
16. New General ledger Accounting
New general ledger functions available as in ECC 6.0 on words.

By Activity New GL Functionality

1. The new functionalities (or) new ledger accounting available.


2. In IMG server the functional accounting menu is replaced by functional accounting new,
functional accounting global settings is replaced by financial accounting global settings
new
3. General ledger accounting replaced by general ledger accounting new.
4. Some transactions are absolute.

Functions (or ) New Features


1. Parallel ledger accounting.
2. Document Splitting.
3. Segment wise reporting.
4. Real time integration CO to FI.
5. Foreign currency Validation of different validation area approach.
6. Accounting principle approaching in generating the reports.
7. Document general ledger view functionality.
8. Closing cockpit (as on ECC6 (or)Ecc4).
9. Cost of sales accounting.
10. Profit center wise reporting.

Effects on existing functionalities.

Tables (Old) New Description


GLTO FAGLFLEXT GL Account Totals
GLPCA FAGLFLEXA Profit center actual line items
GLPCT FAGLFLEXT Profit center totals
GLPCP FAGLFLEXP Profit center plan line items

T Codes

Old New Description


F-02/ FB01 FB01l Post GL document
FB50 FB50l Post GL document
FBL3N FBGLL03 Display GL account line
items
FS10N FAGLB03 Display GL Balances
F.05 FAGL _FC_Val Foreign currency valuation
F.16 FAGLGVTR GL account balances carry
forward

Page 22 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
Functionalities

a. Profit center accounting is not necessary to activate to use profit center as it has been part of
FI.
b. Dummy profit center is no longer mandatory.
c. Reconciliation ledger is no longer valid it replaced real time integration variant to CO to FI.
d. Special purpose ledger is also no longer valid it is replaced with parallel ledger accounting.

How to activate new general ledger accounting

SPRO:- FA ->FAGS(New)-> Activate new general ledger accounting.

Note :- When you activate (new) GL accounting and if you post any transactions system will update
the values not only in (New) G/L tables. But also update the vales in classic G/L account table
(GLT0).

In case if you don’t want to the system to update the values classic ledger tables.

You can deactivate the updating the classic ledger tables. After comparing ledger and table and
ensure the values are matched properly.

Compare ledger (special purpose G/L & new G/L)

SPRO:- FA (New)-> FAG settings (New) -> tools -> compare ledger T Code – GCAC

Deactivate update of classic ledger GLTO

SPRO:- FA (New)-> FAG settings (New) -> tools -> compare ledger T Code – GCAC

Note: - once new G/L accounting is activated amount be reversal back changes.

Write -> update

Read -> full the data

Parallel Ledger Accounting

What is ledger?

Ans ledger is used for reporting purpose.

How many types of ledger do we have in SAP?

Ans two types

1. Leading ledger
2. Non leading ledger

Page 23 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
What is leading ledger?

Ans : leading ledger is used for consolidation reporting purpose, where we follows some accounting
principles.

Note:

1. You must define one of the ledger as a leading ledger.


2. You can not define more than one leading ledger.
3. When you post the transactions to each co. code the data will be updated in the leading ledger
automatically.

What is non leading ledger?

Ans: Non leading ledgers are nothing but additional (or) parallel ledger to the leading ledger.

The non leading ledger are used for local accounting principles.

EX: USGAP, German GAAP, TAX Reporting, Indian GAAP etc.

The non leading ledger must be defined at CO. Code specific.

Step-1

Define ledger for general ledger accounting

 Click new entries

Led Ledger name Total table


1L Non leading ledger -1 FAGLFLEXT
2L Non leading ledger-2 FAGLFLEXT

Save. It

Note: once the ledger is created it will be created as a ledger group with a same key.

Step-2:

Define currencies of leading ledger

How many currencies we can maintain maximum in a co code?

Ans: 3 currencies apart from our local currency and we can maintain 2 parallel currencies.

It can be a group currency, hand currency, global company currency, index based currency.

Co code - sap

City type – 10

Page 24 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
Valuation – 0

Exchange rate type – M

Date type- 3

Currency types:

10 – Co code currency

20 – Controlling are currency

30 – Group currency

40 – Hard currency

50 – Index based currency

60 – Global company currency

10- Company code currency

in which currency the co code is created is a company code currency / local currency.

The company code currency key is executed from the co code creation.

20 – Controlling area currency

In which currency the controlling area created is a controlling area currency which is executed from
controlling area creation screen.

T code OKKP

30 – Group currency

Group currency is used for consolidation reporting purpose. The group currency key is defined at
client level T code SCC4

40 – Hard currency

Hard currency is used as country specific second currency for high inflation purpose. Hard currency
is define in country level t code -OY01

50 – Index based currency

It is country based fictitious based currency, which is stimulated for external reporting purpose.

(Ex: tax returns) in some countries with type inflation.

Page 25 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
60- Global company currency

Which is defined at company level. Not company code level T code  OY01 (OR) ox15

Step- 3 Define and activate non leading ledgers

 Click on new entries

Co code Company name CI Currency Cur2 Cur3 Cur3 C3 Fv Pv

9999 Srinu groups 10 INR 30 USD 60 INR K4 1000

Save it.

Step – 4 assign scenarios and customer fields to ledger

What is the standard scenario in SAP has provided

Scenarios Long Text


FIN-CCA Cost center update
FIN-CONS Preparations for consolidations
FIN-GSBER Business area
FIN-PCA Profit center update
FIN-SEGM Segmentation
FIN-UKN Cost of sales activity

Objective:-

In this activity we specify the scenarios which determines what fields in the ledger are to be updated
when it is requires posting from other application component.

Step-5 define ledger group

What is ledger?

Ledger group is nothing but contribution of ledgers for the purpose of applying the same functions
and the process of general ledger accounting to the group as a whole.

When we part the transactions of the data will be updated with all the ledgers assigned in the group.

Note:- when the ledger is created the system automatically generates a ledger group with a same
name in this way we can post the data to individual ledger (or) access it when using functions, where
you only enter ledger groups not ledgers.

Step-6:- what is a representative ledger

The representative ledgers are used to determine the posting period variant.

Page 26 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 We must define one of the ledgers as represent ledgers.
 In case if the leading ledger exists a ledger group than represent ledger must be the leading
ledger.

Note:- when the posting period of representative ledger is open the postings will be made to all other
assigned ledgers hoe ever their postings periods are closed.

Step- 7 define document types for general ledger

Spro FA(New) FAG settings (new)  document  document types  define document types
for general ledger view.

Note:- in this activity we defined document type for non leading ledges.

 Ledger –1L

Type number range

SA SA

Save.

Step-8 define document type for general ledger

Spro  FA (New) FAGS(new)  document  document no ranges document types in general


ledger view  define document no ranges for general ledger view.

co code - 9999

 Click intervals!

SA 2015 100 199

Save it.

Step-9 Define document types for entry view a ledger

SPRO  same path as above.

Page 27 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
18.1. VALIDATION
What is Validation?

It’s a process of checking the values and combination of the values that are prefund/ entered
in the system. The entered values are checked against the user predefined values. If the statement is
true then system will allow you, user to post the Transaction.

In case if the statement is not true the statement will issue the message as user customization.

Step 1: Maintain Validation Rules for Business Requirement: GGB0

SPRO ==> FI (NEW) ==> Special purpose Ledger ==> Tools ==> Maintain Validation/
Substitution Rules

At what level we can write validation Rules?

3 Levels validation rules in Sap

1. Document header level


2. Line item level
3. Complete Document level

How many steps are there while maintaining Validation Rules/ Steps?

There are levels / steps

1. Pre-requisite
2. Check
3. Message

Requirements:

 Particular Co. Code


 Particular GL A/C
 Particular Profit Center
 Expand the financial Accounting
 Keep the cursor on Line item
 Click on create Validation button
 Enter Validation name in a Text field
1. Validation name: Z001 ==> Validation rules for Co. Code
2. Click on step button
3. Enter validation description (Business Area- 1000)
4. Profit center validation ==> After entering
 Double click on Prerequisite
 Double click on Accounting Document Segment
 Click on display technical name (In case technical names not enable) button
 Click on the find button

Page 28 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
Enter the search item (BUKRS) ==> Technical name for Co. Code

1. Press enter
Double click on technical name (BSEG_BUKRS)
Click on (=)
Click on (Constant) button
Enter your co. code: VSLH
Press enter
Click on (AND) symbol
Click on (FIND) button
2. Enter the search term (HKONT) ==> Technical name for GL Account
Double click on technical name (BSEG_HKONT)
Click on (=)
Click on (Constant) button
Enter your GL no: 200500
Press enter
Double Click on (Account document symbol)
Click on (FIND) button
3. Search term (PRCTR) ==> Technical name for Profit center
Double click on technical name (BSEG_PRCTR)
Click on (=)
Click on (Constant) button
Enter your Profit center: PC001
Double Click on MESSAGE
Click on Maintain message button
Click on next free number button
Double click on message numbers
Enter the Message description: Please enter Profit center (PC001)
SAVE ==> Select back arrow
Select your message type: E (error)
Select your message no: custom 032
NOTE: Here the transport request number is not generated.

How to activate Validation rules in Company Code: OB28

SPRO==> FI (NEW) ==> Global Settings (NEW) ==> Tools ==> Validation/ substitution
==> Validation of Accounting Documents

Under validation of accounting document enter Particular details:

 Click on new entries


 Co. Code: VSLH
 Select call up point toll: Line item
 Select your Validation: Z001
 Select Activation level : 1 ==> SAVE

Page 29 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
NOTE: 1 is Activate & 0 is Inactivate ==> SAVE

NOTE: We cannot activate more than one validation to company code at the same call point.

Go & Check the Validation Requirement Record: F-02

NOTE: Where we want write validation?

Ans: Development client.

Excursuses:

1. Scenario: Co. Code ==> GL A/c ==> Amount Limits


2. Scenario: Particular ==> T.Code ==> Document type
3. Scenario: Co. Code ==> GL A/c ==> Business Area
4. Scenario: Co. Code ==> T.Code ==> Business Place Validation
5. Scenario: Duplicate check for AR invoices ==> Document type & Activity type ==> Pre
requisites Check ==> Exit User for FI_CO with the help of ABAPER.

How to create sets: GS01

Set is nothing but combination of Values.

SPRO ==> FI (NEW) ==> Special Purpose Ledger ==> Tools ==> Set Maintenance ==> Sets ==>
Set maintenance

SET Name: GL_ACCOUNT ==> Basic Settings ==> Basic Settings Select radio button.

Table: BSEG ==> Enter ==> Field name: HKONT ==> Enter

From Value to Value: 200100 to 200200 ==> SAVE

Prerequisites:

1. Co. Code AND GL in GL_ACCOUNT


2. Co. Code AND NOT in GL_ACCOUNT

How to transfer validation rules: GGT9

SPRO==> FI (NEW) ==> Special purpose ledger groups ==> Tools ==> Transport ==> Transport
Validation.

 Select validation name: Z001


 Click on Select all radio buttons (Total 5 buttons)
 Then Execute it
 Create separate request ==> TR for validation rules ==> Press ENTER ==> SAVE

NOTE: System generate work bench request.

NOTE: Message classes or Numbers are not transferred.

Page 30 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
18.2. SUBSTITUTION
It’s an automatic process of replacing the entered values with pre-defined values, in case if the
statement is not good.

At what level we will do substitution Rules:

1) Document Header Level


2) Item Level
3) Complete Document Level

How many steps are there while writing the Substitution Rules:

1) Prerequisite
2) Substitution

How to add additional fields to the Substitution fields table:

T-code: SM30 (Table Maintenance)

 View/Table VWTYGB01
 Click Maintenance Button
 Ignore the message and go ahead

EX: Business Place field needs to be enable/included in the Substitution fields list.

 Click on Position button


 Class numbers 009, Enter
 Page down
 De-select Exclude check box against GSBER

NOTE: Here we can add/remove additional Fields in Substitution Fields List.

Write Substitution:

T-code: GGB1

Path: SPRO=> Fin A/c ing (new)=> Spl Purpose Ledger=> Tools=> Maintain Val/Sub Rules=>
Maintain Substitution

Scenario:

For a particular Co. Code & for a particular G/L Account should always be posted with default
Business Area.

 Expand Financial Accounting


 Keep the Cursor on the Line Item
 Click on Create Substitution

Page 31 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 Substitution Name – FIN_Sub
 Text – Substitution Rules For Company Code – VENU
 Click on Step Button
 Close the Table
 Ignore the warning Message and Enter
 Enter Step Description – Substitution for Business Area
 Double click on Prerequisite
 Click on Display Technical Name Button
 Double click on Accounting Document Segment
 Click on Find Button
 Enter Search Term BUKRS
 Double click on BSEG-BUKRS -Company Code
 Click on =
 Click on Constant Button
 Enter Company Code – VENU
 Click on AND Button
 Click on Find Button
 Enter Search Term HKONT
 Double click on BSEG-HKONT- G/L
 Click on =
 Click on Constant Button
 Enter G/L Account-200200
 To delete the Data, Keep the curssor on the Element which you want to delete and Click on
Delete Element Button
 Double click on Substitution
 Click on Insert Substitution Entry
 Select the Fields for which you lick to write Substitution (Ex: Business Area - GSBER )

How would you like to substitute field BSEG-GSBER ?

1) Constant value
2) Exit (Some Coding is required by ABAP)
3) Field – Field assignment
 Select Constant Value
 Enter Business Area - Constant value VSLH, Save it.

NOTE: Here we didn’t get any Transport Request.

Activate Substitution Rules For Company Code:

Path: SPRO=>Fin A/c ing (New) => Fin A/c ing Global Settings=> Tools=> Val/Sub=> Sub in
Accounting Documents

T-Code: OBBH

Page 32 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
Click on New Entries

Co Code Call up Point Substitution Activation Level


VSL 2 – Line Item FIN_SUB 1- Activate

Save it.

Go and Post One Entry with another Business Area in Company Code VSL with G/L Account
200200 (T-code: F-02)

EX: Company Code – VSL; G/L A/c: 200200 and Business Area: VSLH

Check the Results.

Page 33 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
19. ALE – IDOC
ALE – Application Link Enabling

IDOC – Intermediate Document

What is Idoc:

It’s an Intermediate Document which is used to distribute the Master Data, Transaction Data from
SAP System to SAP Systems or/and NON-SAP to SAP System.

How many Types of IDOC’S we have ?

There are 2 Types,

1. In-Bound IDOC – Inflow to SAP


2. Out- Bound IDOC – Outflow from SAP

How many types of records are there in IDOC’S ?

There are 3 Types,

1. Control Records
2. Data Records
3. Status Records

Control Records: It contains all administration data.

 Idoc Type ( i.e., Inbound or Outbound)


 Message Type
 Basic Type
 Sending System
 Receiving System

Data Records: It contains data elements / details of Master Data or Transaction Data.

Status Records: It contains status of IDOC processing

 In - Bound Status Records,


 01 to 49 Out – Bound IDOC Numbers
 50 to 75 In – Bound Numbers

When IDOC is processed the Messages are,

Out – Bound:

 01 – IDOC is Created
 03 – IDOC is Processed

Page 34 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 30 – IDOC is ready to dispatch

In – Bound:

 53 – Application Document Posted


 51 – Application Document is not Posted

What is the Difference Between ALE – IDOC and EDI – IDOC ?

ALE – IDOC EDI - IDOC


It’s used to Distribute the Data from SAP to It’s used to Distribute the Data from SAP to
SAP systems. NON – SAP systems.
It uses the RFC Ports (Remote Function It uses File Ports.
Call).
It uses SAP R/3 connections. It uses IP connections.

Configuration Steps for ALE – IDOC ( Client 800) : T-Code: SALE

1. Define Logical System:

Path: SALE=> Basic System=> Logical Systems=> Define Logical System

 Ignore the Message and Enter,


 Click on New Entries
SEND800 Sending System 800
RECV810 Receiving System 810

Save it .
Create Request and Save it the Request.

2. Assign Logical System to Client:

Path: Same as Above

 Ignore the Message and Enter,


 Double click on Client 800
 Enter Logical System SEND800, Save it .
 Ignore Message and Enter,
 Click on Back Arrow
 Double click on Client 810
 Enter the Logical System RECV810, Save it .
 Ignore the Message and Save it .

Page 35 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
3. Create RFC Connections:

Path: SALE=> Communication=> Create RFC Connections

 Click on Create Button.


 RFC Destination – Receiving System 810
Connection Type – 3
Description 1- Receiving System 810, Save it .
 Click on Technical Settings Tab
 Enter the IP Address in Target Host Field
 To Know the IP Address of the System,
 Click Win+R
 Enter CMD
 Enter IPCONFIG ( Ex. 192.168.11.12), Save it .
 Click on Logon & Security Tab
 Language – EN
Client – 810
User – SAPUSER
Password – india123, Save it .
 Ignore message and Enter
 Click on Connection Test Button From Above
 Click Back Arrow
 Click Remote Logon Button From Above
 Click Exit Button and Save it .

4. Define Global Company Code:

Path: SALE=> Modeling and implementing business process=> Global organisational


units=> Cross System Company codes

 Click on New Entries


VENU Global Company - VENU

Save It .

5. Assign Global Company Code in T-Code: OBY6

 Click on Position
 Enter your Company Code ( Ex. VENU)
 Double click on your Company Code
 Enter Global Company Code ( Ex. VENU), Save it .

Page 36 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
6. Maintain Distribution Model and Distribute Views:

Path: SALE=> Modeling and implementing business process=> Maintain Distribution


Model and Distribute Views

T-Code: BD64

 Click on Change Button


 Click on

 Enter,

 Enter, Scroll Down


 Keep The Cursor on your Mode view, just you created Above
 Click on
 Enter,

Save it .

7. Creation Of Ports:

T-Code: WE21

 Select Transactional RFC


 Click on Create Button

Page 37 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 Don’t write anything Enter
 Description – Receiving System Port 810
 RFC Destination – Click on , and Select Receiving System 810, Save it .

8. Create Partner Profiles:

T-Code: WE20

 Expand Partner Type LS


 Double Click on RECV810
 Click on in Out- Bound Parameters
 Partner Role – LS
 Message Type – GLMAST
 Receiver Port – Enter the Number you created in WE21 (Ex. A000000055)
 Save it . If the Package Size Comes Enter 100 And Save Again.
 Click Back Arrow ,
 Double Click on SEND800
 Click on in In – Bound Parameters
 Partner Role – LS
 Message Type – GLMAST
 Process Code – GLMA, Save it .

9. Go to T-Code BD64
 Click on and Select your mode view you created in Point number 6.
 Keep the cursor on your model view and from Menu=> Environment=> Generate
Partner Profiles
 Enter Partner System – RECV810 and Execute .

NOTE: It Shows Partner Profiles are Created Successfully.

Page 38 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
Configuration Steps for ALE – IDOC (Client 810) : T-Code: SALE

1. Create RFC Connections:

Path: SALE=> Communication=> Create RFC Connections

 Click on Create Button.


 RFC Destination – Sending System 800
Connection Type – 3
Description 1- Sending System 800, Save it .
 Click on Technical Settings Tab
 Enter the IP Address in Target Host Field
 To Know the IP Address of the System,
 Click Win+R
 Enter CMD
 Enter IPCONFIG ( Ex. 192.168.11.12), Save it .
 Click on Logon & Security Tab
 Language – EN
Client – 800
User – SAPUSER
Password – india123, Save it .
 Ignore message and Enter
 Click on Connection Test Button From Above
 Click Back Arrow
 Click Remote Logon Button From Above
 Click Exit Button and Save it .

2. Define Global Company Code:

Path: SALE=> Modeling and implementing business process=> Global organizational


units=> Cross System Company codes

 Click on New Entries


VENU Global Company - VENU

Save It .

3. Assign Global Company Code in T-Code: OBY6

 Click on Position
 Enter your Company Code ( Ex. VENU)
 Double click on your Company Code
 Enter Global Company Code ( Ex. VENU), Save it .

Page 39 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
4. Maintain Distribution Model and Distribute Views:

Path: SALE=> Modeling and implementing business process=> Maintain Distribution


Model and Distribute Views

T-Code: BD64

 Click on Change Button


 Click on

 Enter,

 Enter, Scroll Down


 Keep The Cursor on your Mode view, just you created Above
 Click on
 Enter,

Save it .

5. Creation Of Ports:

T-Code: WE21

 Select Transactional RFC


 Click on Create Button

Page 40 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 Don’t write anything Enter
 Description – Sending System Port 800
 RFC Destination – Click on , and Select Sending System 800, Save it .

6. Create Partner Profiles:

T-Code: WE20

 Expand Partner Type LS


 Double Click on SEND800
 Click on in Out- Bound Parameters
 Partner Role – LS
 Message Type – GLMAST
 Receiver Port – Enter the Number you created in WE21 (Ex. A000000055)
 Save it . If the Package Size Comes Enter 100 And Save Again.
 Click Back Arrow ,
 Double Click on RECV810
 Click on in In – Bound Parameters
 Partner Role – LS
 Message Type – GLMAST
 Process Code – GLMA, Save it .

7. Go to T-Code BD64
 Click on and Select your mode view you created in Point number 4.
 Keep the cursor on your model view and from Menu=> Environment=> Generate
Partner Profiles
 Enter Partner System – SEND800 and Execute .

NOTE: It Shows Partner Profiles are Created Successfully.

NOTE: Before transferring the G/L Master Records we have to MOVE THE TRANSPORT
REQUEST FROM CLIENT 800 TO 810 IN T- CODE: SCC1

Logon in Client 810 and go to T-Code: SCC1

Page 41 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
Don’t Forget to Select

Click

It Will Shows

Click YES.

Program ran Successfully Message will Appear.

In Client 800 (Sending System):-

1. Create G/L Master Records: T- Code: FS00

2. Send G/L Master Records From Client 800 to 810: T- Code: BD18

Execute it .

Note: Here we will get Message “Master IDocs set up for message type GLMAST”. Click Enter.
Then, we will get “Communication IDoc(s) generated for message type GLMAST”

3. Display IDOC’S: T- Code: WE02/WE05

 Enter Creation Date – ( on which date the BD18 is run)


 Enter Logical Message Type – GLMAST
 Click Execute .
 Status Shows GREEN.
 Double Click on IDOC Number and see the Details.

4. Re- Process the IDOC’S: T- Code: BD87

Incase the IDOC’S fails, we have to Re- Process the IDOC’S in BD87.

Page 42 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
 Enter IDOC NUMBER that failed in WE02/WE05
 Enter Partner System – RECV810
 Enter Message Type – GLMAST
 Execute .

Logon Client 810:

Go to T – Code WE02/WE05

 Enter Created On – ( on which date the IDOC was run)


 Enter Logical Message – GLMAST
 Execute .
 See the IDOC Status.

Important IDOC Message Types:

1. Master Records:
 GLMAST : G/L Master Records
 CREMAS : Vendor Master Records
 DEBMAS : Customer Master Records
 MATMAS : Material Master Records
 COSMAS : Cost Center
 PRCMAS : Profit Center
 COELEM : Cost Element
 EXCHANGE_RATE : Exchange Rates

2. Transactional Data:
 INVOIC : Invoice / Billing Document
 PAYEXT : Payment Information
 DIRDEB : Direct Debit
 FINSTA : Bank Statement

List of Important T – Codes in IDOC’S:

 WE02/WE05 : To check IDOC Status


 SM59 : To configure RFC Connections
 WE20 : To create Partner Profiles
 WE21 : To create Ports
 WE30 : To create Basic Idoc Types
 WE81 : To create Message Types
 WE82 : To assign message Types & IDOC Types
 WE31 : To create Segments

Page 43 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL
20. PRICEFW
 Programs
 Reports
 Interfaces ==>Nonstop-SAP (Connecting)
 Conversions ==> BDC – Batch Data Conversions
 Enhancements
 Forms ==> BSIK ==> Vendor ageing
 Workflow

Programs: To Execute any kind of Program – SE38

SE36 ==> To create Background Job

SM37 ==> Display the Job

 How to create background jobs:


 Go to T.Code: SM36 ==> Enter the job name recurring entry
 Click on define Step button
 Enter Programming of the Transaction & Variant
 Click on check button ==> SAVE
BDC- Batch Data Conversions
 Click on start button
 We scheduled immediately or Time & Date
 Click on immediately ==> once again SAVE it
 Display job overview: SM37
 Enter ABAP Program name
 Execute it
 Check that Status & Date
 Click on refresh button
 Then click on Job & Check output whether it is Created or Not
 Go back & click on Spool button.

Page 44 of 44
KVREDDY, RAMAKRISHNA & VENUGOPAL

You might also like