SAP Real Time Material by Tech Mentors-3

SAP REAL TIME COURSE
By Tech Mentors IT Technologies
Tech Mentors, Hyderabad India

Course Content:
1. System Landscape
2. Transport Request Management
3. Types of projects
4. Implementation Project Process
5. Support Project process
6. Month End & Year End Activities
7. Types of testing and tools
8. FI-MM Integration
9. FI-SD Integration
10. New GL Accounting
11. DMEE File Overview
12. Validation and Substitution rules maintenance in SAP
13. Master data and Transactional data uploading by using LSMW
14. Idocs process, Usage, and Idocs Tables
15. SAP Important table list
16. RICEFW Objects
17. SAP ECC vs SAP S4HANA Changes

System Landscape:
What is System Landscape?
System Landscape is a key design decision for distributing the SAP applications across the servers.
System Landscape design activity is done by BASIS Team,

PRODUCTION
DEVELOPMENT QUALITY 100- Pre-Production.
100- Golden Client. 100-Testing Client. 110-Production Client.

110- Golden Test Client. (Integration Testing)
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 fulfil of project requirements and to do experiments to
their Skills.
In Sandbox client, the system does not generate transport request.

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 – Preproduction 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.

Transport 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 cannot 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.
 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 Number
 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.

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 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, ECC 6.0 Ehp 7.0 to S4HANA
Roll out Project: Implementing SAP for another country / Plant / Legal entity based on
existing country / existing one. They were already into SAP for long back.

Testing Process and 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), JIRA

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.

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:

This UAT will be performed by end user’s/core business users to check whether the changes have been
done as per the requirement given by them.
Performance Testing:
The performance testing will be performed by the BASIS team to check the
system’s performance and to specify the time limit for the execution of the programs.

SAP Main Tables and Maintenance:
Table is nothing but list of fields. Here each and every transaction is stored in the tables.
There are 3 main types of tables. Transparent table, cluster table and pooled table.
Transparent table is a table that stores the data directly and exists with the same structure
both in dictionary and in database exactly with the same data and fields.
SE11: Here we can view table and structure and here you can also create, change, and
display table entry.
SE16: Here in SE16 you can view only table and extract data from the tables. You cannot view the
structure. You cannot create a table here
SE16N: Here in SE16 you can view only table and extract data from the tables. You cannot view the
structure. You cannot create a table here.
SM30 is used to maintain the Z - tables, i.e. deleted, insert, and modify the field values.

Implementation Process:
ASAP Methodology – Accelerated SAP
It is a Methodology/Process which we have to follow to implement SAP Applications successfully

to the client as per their business requirements. It contains road map 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 analyse 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
 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 Functional Specs.
 Configure the settings required based on the baseline configuration document

 Technical specifications (TS) will be prepared by ABAP team based on the FS 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 kinds of testing phases.

 SIT (system integration Testing)
 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.
Derivable Documents:
 QADB (Question and Answer Data Base): It is a key tool/template which is used to collect the
business requirements/inputs from the business team during your implementation project.
 Base line configuration document: It is a document which covers complete business

requirements need to be configured in sap system.
 GAP Analysis Documentation: In case if any client’s business requirement is not suitable or fit
into standard sap settings is called as a fitment gaps. In project preparation phase we identify
gaps.
 Functional specifications (FS): It’s a functional requirement document which includes

objective of the development (business requirement), current business process, desired
business functionality processing rules (development logic) and test scenarios.
 Business Process Procedures: BPP means list of transaction codes. It’s a list of business
transactions which the client has in the scope of the project. Total T. codes you have to show

this to clients. According to the requirement only that T. codes is kept. Through that T. codes
you have to create User Manuals.
 End User Manuals: It’s a training documents or reference documents for end users to post the
documents or to execute the documents. SAP TUTOR and UPK (User Productivity Kit) are the
tools I used to create recordings. We do it in Quality server.
 BPML (Business Process Master List): This is a most important deliverable document in the
2nd phase of the road map. In BPML all the business scenarios, processes and transactions
that have been included in the project scope are listed in excel sheet. Then the BPML will be
used for monitoring and controlling, configuration and for the test cases execution in the
realization phase.
 BDD (Business Design Document): the objective of the BDD is to document in detail the scope
of business scenarios/processes and process steps of the implementation project from the
business and technical prospective. VISIO-MS- VISIO in this we can do the object in diagram
wise. All the documents can be created at this MS-VISIO tool only.
 Configuring documents: If we look at the AP, AR, and Asset accounting, that time I have to
prepare all the documentation, how the system is going to be mapped no, that will be
documented in the SAP, that is called configuration document. Functional specifications mean,
some of the reports or programs are not fulfil the client requirement. So, we have to develop
the SAP system as per our requirements.
 Process flow charts: A flowchart is a type of diagram that represents an algorithm, workflow,
or process, showing the steps as boxes of various kinds, and their order by connecting them
with arrows. This diagrammatic representation illustrates a solution model to a given problem.
 End user Manuals: A user guide or user's guide, also commonly known as a manual, is a
technical communication document intended to give assistance to people using a particular
system. It is usually written by a technical/Functional writer, although user guides are written
by programmers, product or project managers, or other technical staff, particularly in smaller
companies.
Cutover Activities:
1. To transport requests from development to production server.
2. To give tax codes and number range interval in production server.
3. Upload GL Masters.
4. Upload Vendor Masters.
5. Upload Customer Masters.
6. Upload Asset Masters.

7. To take GL Balances in SAP. (Just before go-live)
8. To take Vendor Open Items and Advances into SAP. (Just before go-live)
9. To take Customer Open Items and Advances into SAP. (Just before go-live)
10. To take Sub Asset wise acquisition value and accumulated depreciation
value into SAP. (Just before go-live)
Note: The data takeover GL accounts created should have zero balances after
successful migration. So, for uploading accounts we are maintaining the separate
number range intervals (like 9 series). For my implemented projects we created 4
upload accounts, actually one is enough. When you upload from non-sap to sap the
account entry is like:
 Vendor balances uploading/open items:

Data takeover A/c Dr – 10000
To Vendor Account Cr – 10000
 Customer balances uploading/open

items: Customer account Dr – 10000
To data takeover A/c Cr – 10000
 Asset balances uploading/open items:

Asset account Dr – 20000
To Acc Depreciation A/c Cr – 10000 To
data takeover A/c Cr – 10000
 GL balances uploading:
Data takeover A/c Dr – 10000
To Share Capital account Cr – 10000.
During cutover how the Assets are uploaded?

When we are going live all the legacy balances should be moved to SAP. So, for Assets, first
we need to bring the asset master data, keep all the fields as optional in depreciation screen
layout.
(Menu > Environment > screen layout > Depreciation areas) and we use T. Code AS91 in
LSMW,
where asset master record will be created and also the legacy data (along with asset values)
will be uploaded into sap. Legacy data means, the total acquisition value and as on the date
when we are uploading the data what is the depreciation and net book value we upload on
that date.
Here also there are two scenarios, start of the fiscal year and mid of the fiscal year. In my
scenario starting of the fiscal year, it happened.
 At that time, we have to take only balance sheet items, like gross book value of
the asset (assets) and then accumulated depreciation (liabilities).
 If it is in the mid of the fiscal year, then we have to take two items P&L item &
depreciation and once you have recorded the values in AS91, it won’t directly hit the
GL account.
 The integration between the FI–GL accounts and asset accounting will be configured
in AO90 (accounts are assigned there). Once you have recorded AS91, it will upload
only the balances of the asset books, then you can go to asset explorer where all the
values are updated for the assets, but this amount won’t hit the GL accounts. Then
for to hit the GL account, we have to enter the values in T Code OASV like
Vehicle A/C Dr. 200000

To Accumulated Depreciation A/C Cr. 50000
To Data Takeover A/C Cr. 150000
With this OASV T. Code you do not have to change the recon account status of the GL’ s in T. Code
OAMK we can make changes to reconciliation accounts to allow balances directly.

Support Process:
Incident Management:
What is incident?
Ans: - It can an Issue, Request, Problem
Roles In support:
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)
How many types of priority for an Incident
1. Critical
2. High
3. Medium
4. Low
What is SLA?
Ans: - SLA is Service Level Agreement Between Service provider and Customer with terms and
conditions.
How many types of SLA support your company is giving:
L1 Support
L2 Support
L3 Support
What is the SLA for your client:
SLA for my client 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 8 working days
SLA for Incident Acknowledgement

If it is Critical: It should be acknowledged within 10 mints.
High : It should be acknowledged with in 1 Hour
Medium : It should be acknowledged within 1day
Low : within 1 working day.
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 be working on the incident
5. Pending : Pending with Customer
6. Cancel : Where it cancels duplicate issue
 Pending with Customer
Where consultant requires inputs or Closing confirmation from the User
 Pending with Vendor
Where consultant is working on the incident with OSS Team due to Product related issues
* Resolve: where the resolution has provided to the user and accepted to close it
* Close: Where the Incident was closed
* Reopen: - Where the incident was being reopen by the use to unhappy/un satisfaction on the
resolution provide by the consultant after closed the incident
How many Numbers 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?
Ans: - 5 – 6
What is Ticketing Tool?
Remedy tool ITSM, service now

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
Types of Change Request:
1. No impact CR (NIC)
2. Emergency CR/BUG Fix CR
3. Baseline CR
4. 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.
 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.
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 are 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.
What is OSS Note:
OSS Note are online documents published by SAP which contains information related to
 Product Error
 Product Modifications
 Product upgrade
 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.

Month End and Year End Activities:

Validation and Substitution Rules:
Validation:
It is a process of checking the values and combination of the values that are entered in the system.
The entered values are checked against the user predefined values.
 If the statement is true then system will allow you or user to post the Transaction.
 if the statement is not true the statement will issue the message as per customization.
At what level we can write validation Rules?
3 Levels we can write 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 3 levels / steps
1. Pre-requisite
2. Check
3. Message
Business Requirement:
While posting any document in SAP through F-02 or FB50, user should not forget to enter Reference field
at Document header for Doc Type SA for particular co code, not for all co codes.
So, if we made reference is the mandatory at SA doc type level, then system will ask user to enter data in
reference field for all co codes.
So, in this case we write the validation rule as below.

Pre requisite: Co code = PSL and doc type = SA
Check: Reference not is equal to blank
Message: Reference field is mandatory.
Step 1: Maintain Validation Rules for Business Requirement: GGB0
SPRO ==> FI (NEW) ==> Special purpose Ledger ==> Tools ==> Maintain Validation/
Substitution RulesMaintain Validation

(Note: Consider text in message text is Reference field is mandatory)
Step 2: Activate Validation rules in Company Code: OB28
SPRO==> FI (NEW) ==> Global Settings (NEW) ==> Tools ==> Validation/ substitution
==> Validation of Accounting Documents
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.
Substitution:
It is 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
Business Requirement:
While posting any document in SAP through F-02 or FB50, if user miss the data in this field or data
entered by user in doc header text field then system should replace with another data ( i.e PSL) for SA
doc type.
So, if we made doc header text is the mandatory at SA doc type level, then system will ask user to enter
data in doc header text field for all co codes.
So, in this case we write the substitution rule as below.

Pre requisite: Co code = PSL and doc header text =blank
or
Pre requisite: Co code = PSL and doc header text =blank or doc header text not =blank
Substitute: Constant value = PSL
Step 1) Maintain substitution
Path: SPRO=> Fin Accounting (new)=> Spl Purpose Ledger=> Tools=> Maintain Val/Sub
Rules=> Maintain Substitution GGB1

Step 2) Activate Substitution Rules for Company Code:
Path: SPRO=>Fin Accounting (New) => Fin Accounting Global Settings=> Tools=> Val/Sub=> Sub in
Accounting Documents OBBH

ALE - IDOC
ALE – Application Link Enabling
IDOC – Intermediate Document
What is IDOC?
It is an Intermediate Document which is used to distribute the Master Data, Transaction Data
from SAP System to SAP Systems or 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 or details of Master Data or Transaction Data.
Status Records: It contains status of IDOC processing.
 01 to 49 Out – Bound IDOC Numbers

 50 to 75 In – Bound IDOC Numbers

When IDOC is processed the Messages are
Out - bound:
 01 – IDOC is Created
 03 – IDOC is Processed
 30 – IDOC is ready to dispatch
In – Bound:
 51 – Application Document not Posted
 52 - Application Document not fully Posted
 53 – Application Document Posted
What is the difference between ALE Idoc and EDI Idoc:
ALE - IDOC EDI - IDOC

ALE - Application Link Enabling EDI - Electronic Data Interchange
It is used to Distribute the data from SAP-to-SAP It is used to Distribute the data from SAP-to-Non-
systems SAP systems
It uses the RFC Ports (Remote Function Call) It uses File Ports
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

SE800 – SENDING SYSTEM 800
RE810 – RECEIVING SYSTEM 810
2. Assign Logical system to client:

(Same path as above)
Ignore the Message and Enter,
Double click on Client 800
Enter Logical System SE800, save it Ignore Message and Enter,
Click on Back Arrow

 Double click on Client 810
 Enter the Logical System RE810, Save it .
 Ignore the Message and Save it .
3. Create RFC Connections: SM59
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.100.1), 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: OBB5
Path: SALE=> Modeling and implementing business process=> Global organizational units=>
Cross System Company codes
 Click on New Entries
REDDIS
Save It

5. Assign Global Company Code in T-Code: OBY6
 Click on Position
 Enter your Company Code (Ex. REDD)
 Double click on your Company Code
 Enter Global Company Code (Ex.
REDDIS), Save it .
6. Maintain Distribution Model and Distribute Views: BD64
Path: SALE=> Modeling and implementing business process=> Maintain Distribution Model and
Distribute Views
 Click on Change Button
 Click on
 Enter, Scroll Down

 Keep The Cursor on your Mode view, just you created Above
 Click on
 Enter
Save it .
For Checking Purpose: Go to Main Manu => Environment => Generate Partner Profiles
Partner System:
Click on Execute.
7. Creation Of Ports: WE21

 Select Transactional RFC
 Click on Create Button
 Do not write anything Enter
 Description – Receiving System Port 810
 RFC Destination – Click on , and Select Receiving System 810, save it .
8. Create Partner Profiles: WE20

 Expand Partner Type LS
 Double Click on RECE810
 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 – RECE810 and Execute .
NOTE: It Shows Partner Profiles are Created Successfully.


SAP Real Time Material by Tech Mentors-3

Uploaded by

Copyright:

Available Formats

You might also like

SAP Real Time Material by Tech Mentors-3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Real Time Material by Tech Mentors-3

Uploaded by

Copyright:

Available Formats

SAP REAL TIME COURSE

By Tech Mentors IT Technologies

Tech Mentors, Hyderabad India

Tech Mentors, Hyderabad India

System Landscape design activity is done by BASIS Team,

DEVELOPMENT QUALITY 100- Pre-Production.

100- Golden Client. 100-Testing Client. 110-Production Client.

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

· We should not post transaction data in this Client.

Where do you Perform Unit Testing? Ans:

Development Test Client.

· This Client is not modifiable.

In Sandbox client, the system does not generate transport request.

Tech Mentors, Hyderabad India

· This Client is also not Modifiable.

Where do you Perform Integration Testing?

Ans: In Quality System.

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

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

This client is also not modifiable.

 This client is also not modifiable.

Tech Mentors, Hyderabad India

Tech Mentors, Hyderabad India

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

Tech Mentors, Hyderabad India

Ex: Development: 100 to Development: 110 in same server.

Tech Mentors, Hyderabad India

Tech Mentors, Hyderabad India

Roles & Responsibilities:

Tech Mentors, Hyderabad India

EX-PTP cycle (procure to pay/FI to MM process), OTC (Order to Cash/FI-SD process),

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.

Ans: HPQC (HP quality center), JIRA

Tech Mentors, Hyderabad India

Tech Mentors, Hyderabad India

User Acceptance Testing:

Tech Mentors, Hyderabad India

Tech Mentors, Hyderabad India

It is a Methodology/Process which we have to follow to implement SAP Applications successfully

 Prepare project plan by project management.

Documents are company’s property.

 Conduct Kick off meeting to the Business blueprint phase.

Tech Mentors, Hyderabad India

Tech Mentors, Hyderabad India

4. Final preparation phase:

 Involved in all kinds of testing phases.

5 Go live and Support:

 Moving all transport requests into production environment.

 Base line configuration document: It is a document which covers complete business

 Functional specifications (FS): It’s a functional requirement document which includes

Tech Mentors, Hyderabad India

Tech Mentors, Hyderabad India

 Vendor balances uploading/open items:

 Customer balances uploading/open

 Asset balances uploading/open items:

During cutover how the Assets are uploaded?

Vehicle A/C Dr. 200000