0% found this document useful (0 votes)
154 views193 pages

SAP SD Content

This document outlines the various documents that need to be prepared for an SAP project. It discusses 12 key documents including project proposal documentation, AS-IS documentation, TO-BE documentation, functional specifications, SAP system landscape, transport request number, configuration documentation, test plans, test scripts, end user manuals, user acceptance testing documentation, and preparations of layouts for data upload. It also briefly discusses the roles in SAP projects, ASAP methodology phases, and project preparation activities.

Uploaded by

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

SAP SD Content

This document outlines the various documents that need to be prepared for an SAP project. It discusses 12 key documents including project proposal documentation, AS-IS documentation, TO-BE documentation, functional specifications, SAP system landscape, transport request number, configuration documentation, test plans, test scripts, end user manuals, user acceptance testing documentation, and preparations of layouts for data upload. It also briefly discusses the roles in SAP projects, ASAP methodology phases, and project preparation activities.

Uploaded by

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

DOCUMENTS PREPARE IN ASAP

1. PROJECT PROPOSAL DOCUMENTATION - PROJECT QUOTATION

These Documents are maintained by delivery manager

In Business blue print a lot of documentation are maintained they are


2.PREPARATION OF QADB

What type of information gather from client business process all Questionires are maintained in QADB

Base on QADB we prepare AS - IS Document


3. AS - IS DOCUMENTATION
It is a Business Process Document (BPD)

Based on AS IS Document prepare TO BE Document


4.TO BE DOCUMENTATION
Business Blue Print Document (BBP)

Develop functional Specification for that Fit Gap Anaylsis


5.PREPARATION OF FUNCTIONAL SPECIFICATIONS
Some client Busniess process are not Standard SAP solutions for that Develop solution with ABAP , we use Functional Specifica

In realization Phase document are system landscape


6. SAP SYSTEM LANDSCAPE
In these documents we maintain system landscape numbers , client numbers authorization details

7. TRANSPORT REQUEST NUMBER


What are transport request we develop for all maintain in this document

8.CONFIGURATION DOCUMENTATION
What are configurations we configurefor all we maintained for a document

9.PREPARE THE TEST PLANS


what test plans we gonna perform maintain in this documents
10. PREPARATION OF TEST SCRIPTS
In Test Scripts what values we test , what is actual result and what is expected result
who is user , who is tested it and after all we SIGNOFF from Project manager

In Final preparation what document we use


11.END USER MANUAL or OPERATION MANUAL
In Quality server we give SAP training to Enduser, for that we create a manual how to recording data in sap with screen shots

12. USER ACCEPTANCES TESTING


Again we Do the Test Plan Creation ,How to Develop Test scripts
User has been testing and he will be given the acceptance, saying all business process Mapped up here. SIGNOFF

if we work on cutover strategy then we work on some layout


13.PREPARATION OF LAYOUTS FOR UPLOAD THE DATA
By using LSMW tool ,so we prepare some layouts then send to users ,what values need to be uploaded

In interviews they ask which phase you work on project ,which documents u prepare

DOCUMENTS PREPARED
ROLES OF SAP PROJECT

6 PHASES IN ASAP METHODOLODY work flow


1st Phase
In this Phase company go and fix the project like below shown

Work flow of Project preparation

When we are working on the Project we have to know CLIENT PROJECT TEAM(client side team)
2nd Phase
BUSINESS BLUE PRINT
After KICKOFF Party , gether requirement in AS IS ,and know business process do TO BE doc, then Details REQ Gathering Sessi
In this Process we take the help of SAP BEST PRATICES , what solutions has SAP Provides for any business process
It is the one project tools we will worked out.

suppose Different Modules we have Different Busniess Process

Pharma Industy In Pharma ind they use Listing and exclusion


Manfacture Industries
Cement Industy These Industries will use Batch management

Retail sector - In Retail Industry don’t have Listing and Exclusion

So we have to know about SAP BEST PRACTICES


For Different Industries verticals will have SAP BEST PRACTICES what solutions need to be mapped up there is an Documents
Those Documents are known as BEST PRACTICE APPROCH

3.REALIZATION:-
A lot of configuration done in this Phase
Documentation also configuration Doc, Test Doc, Test plan , Test script
4.FINAL PREPARATION

Create ENDUSER MANUALS

5. GO LIVE

PROJECT DURATION
How much time we need to spend on Each phase

PROJECT DRIVERS
Different Project Drivers which we focus

SAP QUERY
Use these Tools to Generate the Repors without ABAPER HELP
SAP QUICK VIEW

FUNCTIONAL SPECIFICATION Generate Report with the Help of ABAPER


LSMW Upload Data into SAP into Legacy system

SCREEN VARIENTS Maintain field status

PARAMETERS ID Default enters will Display

MASS CHANGES Huge change at one shot, Update the changes in BULK

PROGRAMS What are different programs used for different documents

USER EXITS Based on Client Requirement ABAPER will do program

TABLES NAMES & FIELD NAMES if we want communicate with ABAPER we have good knowledge in Tables and field names

BASE PRACTICES

BASE LINE CONFIGURATION

STATUS PROFILE How we going map some authorize checks

ENHANAMENTS

TICKETING TOOLS Functionality

Keypoints
consultant never involve in testing ASAP final preparation
mmunicate with ABAPer
consultant Test here

ENDUSER Test here

FIT GAP ANAYSIS DOCUMENT


8.PROJECT KICKOFF
Finally project kick off party

7.INTERVIEW SI LEADER
They conduct interview for project selection team
6.SOW
Then arrgement will signoff

5.SELECT SI
Team leader select the implementation partner

4.Invite & Evaluate SI Prosposals


Team leader ask the bids and prosposals

3.SETUP PROJECR LEADERSHIP & SC


Team leader will select the team for the project

2. SELECT PROJECT EXECUTIVE SPONSOR


select the team leader

1.DEFINE SCOPE
Basically company will go to fixing the implementation Partner
what is Necessatiy of using SAP
what is cost
what is system functionality

CORE USER
They are subject matter Experts
They known IN & OUT of the client business process
They known PRO'S and CONs of the company

ENDUSER:-
They are just DATA entry job only work on SAP when they get order

POWER USER:-
He know how the business process mapping, Before SAP and After SAP

Power user are head of the enduser, if enduser have any issue they consult
power users even power user will not able to find out issue then consultancy

t the Gaps, we gonna prepare it then it finish it RICEFW


1
2
check onc
ASAP METHODOLOGY:-

PROJECT PREPARATION (1st Phase of the Project)

i)PROJECT IMPLEMENTATION
Two ways of Implementation Project
i) Big Bang Approch :- All Modules will go on Live in ONE DAY

ii)Phase Wise Implementation:- Each module will go LIVE in Particule day.


Ex:- SD Module one day, MM module another day like Phasewise implement

ii) PROJECT DELIVERY MODEL


Project Delivery in three Models
1)ONSITE MODEL

2)OFF SITE MODEL

3)MIX MODEL

iii)PROJECT TEAM SELECTION


There are Two Team i) CLIENT TEAM ii) IMPLEMENTATION PARTNER TEAM

i) CILENT TEAM:- Who are from client location Provide the Requirment Related to client Bussiness process ,those are CORE US

ii)IMPLEMENTATION PARTNER TEAM:- SAP Consultants who are worked on the project Gathering the Requirments from client

In implementation Partner team invlove Basic , ABAP , Functional Consultants


these all selection are take care by PROJECT MANAGER , DELIVERY MANAGER. Here SD Consultant Role is ZERO

iv)STEERING COMMITTEE
In Client Team and Implementation team Managers who are involved .
CLIENT TEAM MANAGERS:- Vice President , Core users

IMPLEMENTATION PARTNER TEAM MANAGERS:- Delivery manager, Project Manager

These Steering committee will totally involved in Managing like Budget , team etc only not in subject

SYSTEM LANSCAPE
How many landscapes (servers )will involved in project for Endusers , coreusers and consultants

Different Servers

what are hardware Require

v)PROJECT MILESTONES
Measure the Project Deadlines,
we have to maintain project milestones will maintain here like given below, In what date what things will perform ..
BBP complete on particular Date
Configuration complete on this particular date
Testing complete on particular date
Training complete for enduser on particular date
Project will GO LIVE on particular date

Meeting schedules
what are the issues we are done, what are developments we done, what Acitives done, where is project now , these things dis
Daily meeting
Weekend basic meeting like Friday
Monthly basics meeting

vi)KICKOFF PARTY
Onces everything is done about project preparation stage project is scheduled, then there is formal introducing Party b/w COR

BUSNIESS BLUE PRINT (2nd Phase of project)


Here As a Functional Consultant we will involved here

Prepare Documentation
i) BUSNIESS PROCESS DOCUMENTATION:- BPD

ii)BUSNIESS BLUE PRINT DOCUMENTATION:- BBD

First Activity we do in this Phase


VISIT THE CLIENT LOCATION , Gether the Requirement about client bussiness process is carried out.
Commuincate with core user then visit and check out practically bussniess process

HOW YOU GETHER THE REQUIREMENT OF THE CLIENT BUSNIESS PROCESS


First study Busniess process of the client
Core user will explain client bussiness process carried out
How they Received the order from Customer
How they Convert Purchase order into sales order
what all activites they are doing Provide Confrom the Delivery Date
How payment terms will carried out
How order process will done
At what bases they are provide delivering dates information
what type of Documents they are maintaining
Once customer places Order what types of output are generated either they are provided order confirmation -
- by print, mail or any other communication methods
ALL these things they will show you pratically then you get goods knowledge about client business process

and take all softcopies , if any hardcopy is there then take one copy with u
Lot of information you don’t get information , for that information maintain Documentation QADB
QADB - QUESTION AND ANSWER DATA BASE

Prepare Questioniers
what are Question you ask client about each and every concept about their business process
Ex:- Listing and exclusion is carried out is der any specific requirment is there for only for particular products
How Pricing is carried out
What are different Discounts are carried out
Like this type Questions are framed by using QADB document we will prepare

CONDUCT WORKSHOP
As a consultant we need conduct WORKSHOPS

Most of the time core users all busy with there work , so we conduct workshop onces in 2 days 2,3 hours with core users
and gether requirments from them , asking our Questions about there bussiness process.

In meeting we have to interaction with core users, take an appointment there time particular date , particular time

BUSINESS PROCESS DOCUMENT (AS IS Document)


AS - IS DOCUMENT
Before Using SAP how the client business process been carried out at client location
After prepare AS IS Document core user will check it , all there business process are cover or not,
How process flow carried out, whatever Requirment we gether are correct or not they will check and give approval

BUSNIESS BLUE PRINT DOCUMENTATION:- BBD


Based on AS IS Documentation we Prepare To-Be Documents
TO - BE DOCUMENT
After Using SAP How client business process will carried out

If we prepare AS IS document properly then easy for TO BE document preparation


Most of the times project will fail due to lake of gather information from Client bussiness process

QUICK GAP ANALYSIS


While prepare AS-IS , TO - BE mapping we have to IDENTIFY the GAPS. Which are not standard sap business process for client

To fulfill these GAPS we use RICEFW RICEFW by ABAPER will Develop solutions
RICEFW means Reports, Interface, Conversion, Enhancements, Forms and Workflow.

SIGN OFF
Once we prepare all these DOCUMENTS then we should SIGN OFF from CLIENT TEAM and IMPLEMENTATION TEAM
In Sandbox client sap consultant will check in either client business process work on SAP standard solution or not
By using Sandbox client we find the GAPS

Without Doing any kind of Perform and testing in SAP server about client business process you can't say solutions

3. REALIZATION PHASE (3rd phase)

1.SAP SYSTEM LANDSCAPE:-


SAP system landscape will be implementated in this phase

SAP Servers (Development server, Quality Server , Productions server) are installed in CLIENT LOCATION

servers are Maintained in client location only

BASIS Team go to client location setup server and provide the authorization

2. DEVELOP SAP APPLICATION


As a SAP consultant we develop the SAP Application based on client Requirement

we work as here SAP CONFIGURATOR


CONFIGURATION Client business
GOLDEN CLIENT (IMG configuration ,customization)
For configuration we work on SAP GOLDEN CLIENT in that we do Configuration and customization

TESTING CLIENT (EAS Testing , master data)


After configuration transfer the data from Golden client to Testing client for Testing Purpose by using TM

For Integration testing we do in Quality server only, why because all servers access avalible in Quality server.
3.FIT GAP ANALYSIS
After configuration and testing client business process is there any GAP, not SAP Standard solutions
Then we Develop the Solution for client Requirment which are not standard SAP then with the supported Help of ABAPER.

For Development we have to communicate with the ABAPER's with FUNCTIONAL SPECIFICATIONs.

CONFIGURATION DOCUMENTS
After configuration we need to maintain the configuration Document.

TEST SCRIPTS
Once we going to Perfrom the testing , maintain Documents what Data we are going to Testing
And we need to SIGN OFF form the PROJECT MANAGER test have been Processed all configuration done Accuratly

4.FINAL PREPARATION (4th Phase of the Project)

1. TRAIN THE ENDUSER


Here we have Give Training to Enduser in Master data, Transcation data.,

we give training in QUALITY SERVER in EASY ACCESS SCREEN only

what things we give training


1) Master Data :-customer master , Material material , vendor master ,G/L account , CMIR. BOM. Condition records

2)Transcation Data :- sales order , Purchase order, outbound delivery , inbound delivery etc..,

ENDUSER MANUAL DOCUMENT (user manual documents)


For that Training we have to give some documents for enduser with details and Screenshots.. I,e ENDUSER MANUALS

After signoff we do cut over strategy


2. CUTOVER STRATEGY

How much data need to be upload from legacy system (NON SAP ) to SAP
Either it is ONE Year Data, Two Year Data, 3 months Data

How you upload that information


A lot of information been carried out here
Exclusion(వదిలిపెట్టడం) for number of Reports , what are open order and open deliveries , open billing, pending orders etc..,
After all these anaysis complete then we upload the data

And meeting will done b/w consultants for cutover strategy they check our reportes then correct it.

How upload the data :-


suppose its 2 years data like 1 lakh data is there.
Again we create these 1 lakh sale order, NO.
In SAP cant possible create all data at one time.

So with the Help of LSMW tool we upload the data

LSMW - LEGACY SYSTEM MIGRATION WORK BENCH


Upload the data into SAP

what type of Data we upload


Master Data
Transcation Data
configuration Data (Suppose my client has 1000 sales office again we create in SAP takes time, so we upload in SAP )
3. UAT TESTING ( USER ACCEPTS TESTING)
Client need to perform the testing , for that we maintain separate client maintain in Quality server i.e, UAT client

USER will test the real time data.,

As a consultant Our Responsility to prepare TEST PLANS & TEST SCRIPTS


TEST PLANS:- In which sequence test process will carry out
TEST SCRIPT :- user will maintain all output , Actually Result, Excepted Result. Either Test is Pass or Fail

After Testing user will SIGN OFF from client

5. PROJECT GO LIVE (5th Phase)

1. ENDUSER will working on PRODUCTION SERVER

Record Day to Day transcation in SAP carried out in business

In PRODUCTION SERVER we have only one client PRODUCTION CLIENT they are working on it , only EAS screen

As a consultant we don’t have Access for PRODUCTION SERVER / CLIENT, only ENDUSER have ACCESS
By Preparing the Budget for SAP , we will consider a many of things
1) How many consultants & Endusers will work project
2) How many licenes we will used
3)What type of development will done
4)Either it is onsite project or offsite Project

PROJECT PROPOSAL QUOTATION:-


Total information of the project will maintain here

Only Documentation we prepare here is PROJECT PROPOSAL DOCUMENT prepared


by Proejct , Delivery managers
SAP consultant go to client location and implement SAP in there location

All consultants will go to client location BASIC , ABAPER , FUNCTIONAL Consultants

Miscommunication b/w consultants and clients, ask more numbers of times same
Question untill we get our Requirment.
NOT RECOMMED for FIRST TIME implement SAP
This Method suggest for Support Project

Few consutlant go to client location onsite , Remain all off site


Onsite consultant gether information and share to offsite consutlant

re CORE USERS

from client to Map bussiness in SAP

consultant goes to client place and

QADB - Question and Answer Data

AS-IS Doument need to be prepar


Based on AS-IS we need to prepar
TO-BE Document How we will im

Consultant must idetify the GAP fo

take sign off from the client team


se things discuss with client.

rty b/w CORE USERS & SAP CONSULTANT

Huge Difference b/w these two Documents

to communicate with abapers we need to prepare Functinal Specification


to prepare FS we have good knowledge on Tables and filelds
and we also prepare configuration document
and we should maintain text scripts
CONSULTANT WILL PREPARE THESE DOCUMENTS

s for client business process.


DOCUMENTATION in this Phase

Transport Request Documentation (Consutimazation, work bench Requests maintain here)

TRANSPORT MANAGEMENT Document

CONFIGURATION DOCUMENT ( After configuration we maintain Document )

TEST SCRIPT DOCUMENT (what things are going to test )


DOCUMENTS in this Phase

ENDUSER MANUAL or TRAINING MANUAL or PROCESS FLOW MANUALS


each project use different names

Q:- How much amount data you upload


First we generate all reports then checked out and upload the data.

In this tool a lot methods are there BAPI methods, Recording methods
while doing LSMW we have more data we get more errors
then we take help of ABAPER , to reslove error we use BAPI or BDC( busniess data comincation)
here our role is mainly to maintain XL , which data to transfer non sap to sap
DOCUMENTS

TEST PLANS
TEST SCRIPT
t goes to client place and study the client bussiness process and make QADB

uestion and Answer Data Base

ment need to be prepare (BPD) how bussiness process is carried out at client location before using SAP
AS-IS we need to prepare
cument How we will implement in SAP (BBD)

t must idetify the GAP for client bussiness process , for this we use RICEFW tool this process is called FIT GAP ANALYSYS

off from the client team


3. UAT TESTING
Responsible to prepare test plans and test skripts
Take sign off from client
To buy 1 license company need to pay 80,000 for 1 user 33% need to pay for annual maintainence
total we have 3 main servers
in Real time we call it as
Development server DEV Server
Quality Server QAS Server
Production Server PRD Server

Again in Development sever we have 4 clients Only SAP Consultants will have acces to Devlopment sever , no end user

Golden Client Acess only to IMG,No access to Easy Access

Testing Client No Acess to IMG,Only Access to Easy Access

Sanbox Client

Development Client Technical people have access,they do all coding here


use by abaper to do test

all transport request will be in golden client


for suppose creation of customer
all account group
number range
partner determination will be done in golden cllient
once all configure and moved to then only testing clinet will work

Transporting the development is called Transportaion Management


in this golden client is source and testing client is target
there are 2 types of transport request
Customization request Client Dependent
Workbench request Client Independent
Sandbox Client is also called Rough Client
used by consultants to get hands on SAP
what ever configurations do here we cannot move it in any another client
to identify the gaps at Blueprint phase we work in this client

QUALITY SERVER
Access to both consultants and end users

UAT ClientUSER ACCEPTANCE TESTING CLIENT End User will work on it , No IMG only East Access

Training Client Train the end user on SAP applications (Master Da

Pre Prodution Client (Only Few have this Client) Replica of prodution client
TRANSPOTATION MANAGEMENT

Custumizing Request Data Transportation is required Client Dependent

Workbench Request Data Transportation is not required Client Independent

if we work in transport request we should maintain documentation

like this your implementation partner will provide the template for you ,then you need to mai

to see list of transport request we need to go Tcode SE09/SE10

if we do the custimization in golden client and we need to transport these to test client,here g
goto target client and enter SCC1 and do transport

once your process was done,release the request


for that goto SE09 and place your cursor on request and click the symbol shown
first you need to release the child request and parent request
if you dint release the request duplication will happen
evlopment sever , no end user has acess to this

Enterprise Structure,Item Category,Document Types


Access Sequence,Condition Tables
n it , No IMG only East Access DOCUMENTS - Test Plans and Test Scripts

n SAP applications (Master Data & Transaction Data) No IMG only Easy Access
Client Dependent

Client Independent

ocumentation

for you ,then you need to maintain the details in this document

port these to test client,here golden lient is souce and test client is traget both clients will have same user name and password

e symbol shown
r name and password
Quick Viewer
Tcode for Quick Viewer SQVI
Whenever we go for reporting we have 2 screens Input Screen and Output Screen

we are going to create sample report of sales Tcode - VA05

this screen is called input screen or selection screen


we should maintain information and click on enter

This is output screen

Requirement
we should know the table names and field names before to do report
there is two ways to find filed names
1. place the cursor which you want to know click on F1 help then click on technical informatio
if table category comes under structure we can not take that table name

we should know where the abaper are craeting tables Tcode SE11 - Creating T

This is the quick viewer screen


maintain the query
clcik on create
Maintain Title
and in Data Source select table if only 1 table involved
select table join if multiple table involves
and enter table name

Select the fileds which want to display


under list fileds select your output values
under selection your input values
select the fileds and chage the nos
with the help of arrow marks

click on execute

after that you will get this screen


click on execute button
you can get the output report
you can export the report throgh export option
en click on technical information you will get filed name and table name
ake that table name

s Tcode SE11 - Creating Tables


SE16N - Fetching the Data from Tables
SAP QUERY

we are going to restrict user 1 to craete reports


craete infoset
for that goto SQ02
maintain infoset and cluck on create

Maintain table name and click on continue


and the tables and click on continue

continue with this option

this will appear in next


expand the tables and select fileds you needed
This way we can add the field

Like this you need to select all the fileds


and click on generate
Next we give acces to users who are in User group
for that goto SQ03

Maintain name of user group and click on create

and we maintain user and infosets

Click on it
Maintain users and assign infosets

Select your infoset and save it


Create Report goto SQ01

Click on Infoset Query

Select your Infoset and click on continue

and select your input and output fields


you can see the preview of output
save it
after that click on execute to generate report
Tcodes
FUNCTIONAL SPECIFICATION
To get partial tables from different then we use FS
with the help of abaper we do FS based on client requirement
REQ 2
REQ
DELIVERY DOCUMET TYPE
MOMENT TYPE
LSMW - LEGACY SYSTEM MIGRATION WORKBENCH

Uplaoding the data into SAP from NON SAP (LEGACY SYSTEM)
Uploading transactions,master data,GL accounts etc bulkly in to SAP from Lagacy

CONFIGURATION DATA
MASTER DATA In between Final preparation
TRANSACTION DATA

Total 14 steps involved in LSMW


Tocde is LSMW
Once you entered you get the beside screen

After clicking enter you will get bellow screen

If you want to create your own record click on create Object which was highlihted in above image

after clicking create you will get this

enter all the details ( Object & Name) and click on continue

click on execute button to enter in to our project you will get bellow screen
STEP 1 - Maintain Object Attributes
select this and click on execute button
they are 4 types to upload data
1.Standard Batch/Direct Input
2.Batch Input Recording
3.Bussiness Object Method (BAPI)
4.IDOC (Intermediate Documents)

Bapi and Idco will used to fetch the data

Select Batch input Recoding click on Recording overview

in this step first we are going to record one transaction follow the screens bellow
recoding means for suppose create material for that you will enter tcode and crate one material in this s
try with min views
like this maintain total values are record one creation of material
after thst save the details
after saving that you will get this scree

if you want to know field names click on default all option

now save these details in excel


copy all the field names aand description

make sure that you entry should be unique


if any filed name will be repeat delete that field
double check for that

now go back to SAP save all the details by clicking save button
come back untill change object attributes and enter your reocoding name and save it
late comeback and perform 2nd step

STEP 2 - MAINTAIN SOURCE STRUCTURES

create and maintain the structure


enter the details
create and save the structure

comeback

STEP 3 - Maintain Source Field

in this to our structure we are going to Assign the filelds


click on it go to change mode click on table maintainence
copy all the fileds and descrition and maintain
maintain type and length

save the data all fileds along with length will come in structure page
save it and come back

STEP 4 - Maintain Strucuture Realtions

click on this and make sure your structure is assigned to filed and save it and come back

STEP 5 - Maintain Field mapping and conversion rule

Go to change mode and in extras we have option AUTO-FIELD MAPPING click on that and check the filed
we should check for each and every field
if it correct click on accept or not click on refuse
save the data and come back

STEP 6 - Maintain Fixed values , Transactions , User-Defined Routines ABAPER


in this step we don’t involve
this is for ABABERS

STEP 7 - Specify Files


what that need to be updated in SAP we should specify the files name in this step
for that we create templete and forword it to end users and end user will specify data over here

copy all the filed names and create new excel and use PASTE SPECIAL option
in that click on transpose

For this all verical data will be coped as horizontal


same way copy description also
the excel is called templete
and we provide to end user , and end user will maintain all the data in the templete

end user will provide and the data , we should maintain all the details in this manner
in note pad

maintain the notepad file in for that you select legacy system for PC
maintain separater also here / is a separater
save it

STEP 8 - Assign Files


click on execute and go to change mode click on structure later click on assignment
you can get one pop up as beside picture
and it also shows the path of the text file

save this and come back


STEP 9 - Read Data
click on execute button
pop will come for permission you should allow it , later it will show how many records are readed from t

STEP 10 - Display Read Data

here we can check all the records , wether it has maintained right format are not ,once done come back

STEP 11 - Convert Data


in this it will show how many records are converted

STEP 12 - Display Converted Data


in this we can check that total records are updated in SAP

STEP 13 - Create Batch Session


click on continue for batch

STEP 14 - Run Batch Input Session


In this we need select your project and click on process
it will shows every thing like check box funtinality
it is used for cross checking

For which configuration we use LSMW?


if company having 100 plants , we need to maintain address for each one by one,but using LSMW we can
In between Final preparation Phase and Go Live we do DATA MIGARTION,In Data Migartion we use LSMW tool

above image
nd crate one material in this step
nd come back

lick on that and check the fileds are mapping correctly


specify data over here
any records are readed from text file

re not ,once done come back

by one,but using LSMW we can upload with one strech.


PARAMETER ID

it is used to fix default values , means for suppose end user try to create delivery
for that he entered VL01N after that he should enter shipping point
instead of that by default shiping point will be present
for that we use PARAMETER ID

Note - it is not applicable for all the values for doc type it is not applicable

place the cusor on field and click on F1

for example go to VL01N


place the cousor on shpping ponit click on F1

this screen will appear click on technical information icon

then you will get bellow screen


note down the parameter id
Goto SU01 tcode
you will get bellow screen

enter your user name and click on change mode

later click on parameter tab and enter parameters and value

and check the functinality

MASS CHANGE

to carry out bulk changes in transaction data and master data

for example we have 100 customers like CUST 1 to CUST 100


and for then shpping point is 01
reuirement is to change shpping point frfom 01 to 10 in one shot
Tode for this is MASS
select your object type
and click on execute button
you will get one pop up allow it

you will get this screen


select your table and click on fields
select your field and click on execute

fill the details from which and to you need to change


and click on execue
give your change value and select all the lines and click on CARRY OUT A MASS CHANGE

check the data weather it changes or not


like this you can change mass data to transaction and master data
SCREEN VARIENTS

Maintain the field status in sales documents,we can also use it in G/L accounts,with the hepl of screen varient we c
it is calles as Screen varients or Transaction Varients

REQ End user should not have the access to change the Ship-To-Party once it has to copied
Tcode for screen varient is SHD0 - Create varients

after enterning the Tcode you will get this screen

enter the TCODE in transaction code section which you want to work
click on standard varients and Give the name to it and click on create
No special character was used for name

Miantain the data


Hit on Enter now you can see all fileds in next screen

where you will see 4 option


Content = Optinal Entry
Ouput = Display Entry
Invisible = Supress Entry
Required = Requried / Mandatoy entry

make the changes according to your requirement


it will applicable for only particular document
click on continue

you will get this screen enter the details


click on continue
you will get all the field names change according to our requirements
click on continue and you will et all the fileds make the changes
click on exit and save

Maintain short text


and save it

Give the package and save it


Created the varient

Package is used to update the tables,Basics people will create package to save the data
to check transport request are SE09 and SE10
to transport data from one client to another client is SEC1
one server to another server STMS

if you want to use the particular varient


goto V0V8 and maintain the vareint over there

Perfom the test weather it works are not

Test with different senarios


he hepl of screen varient we can make fields as Optinal/Required/Suppress/Display
ave the data
STATUS PROFILE

Authorization check to documents is called status profile


it will applicable for both header and item
for suppose we have 3 users
we restric the user 1 for order creation
user 2 for delivery
user 3 for billing
it will possible through STATUS PROFILE

REQ After user 1 creating Quatation we restrict him to create order until user 2 release the quatation ?

Path - SPRO --> IMG --> Sales and Distribution --> Sales --> Sales Documents --> Define and Assign Status Profile

we should do these three things for Status Profile

STEP 1 - Define Status Profile


new screen will pop up with status profile overview

click on new entry


and fill the details click on continue

select the created one double click on that


fill the details acording to your requirement
Status - you can give numbering in this field
Status - You can give code for what you implementing
initail status - if you check this it will activated initially
lowest - it is a priority
highest - it is also a priority
remaning fileds will autofill

click on object types by selecting the first one

activate the things as per your requiremnets

in our reuirement activate sales order header and item and save it
go to new entries

maintain this for not approval and save it

goto to sencond one


select reject and goto details
check these and save it
maintain this for approval and save it

STEP 2 - Assign order type / Status profile


click on it and select your dcocument type QT and goto details
assign your status profile
maintain it and save
now test the functionality
once you create quation you are not able to create order untill the satus release
for this go to change mode quatation and goto details (VA22)

clcik on header details


click on status and click on object status

select approved come back and save it


now you can able to create order
e quatation ?

e and Assign Status Profile


OUTPUT DETERMINATION

While creating order,delivery,billing we should communicate with the user for that we communicate with different

we can activate output determination at different levels


output determination is based on condition technique

Path - SPRO --> IMG --> Sales and Distribution --> Basic Functions --> Output Control --> Output Determination --> O
the above path is only for sales order and billing , for delivery we need to go for Logistic Execution
Path - SPRO --> IMG --> Sales and Distribution --> Logistic Execution --> Shipping --> Basic Shipping Functions --> Ou

these all steps we do in output determination

maintain condition tables for sales documents


REQ Create table for Sales organization/Customer/Sales Document Type

Step 1 Tcode to Create is V/57


create table with above combination

Step 2 Create Access Sequence


click on maintain Access Sequence
click on new entry

give your access sequence


and select and click on Accesses
go to new entrys and assign your table
click on fileds to active

Step 3 - Output Type Tcode - V/30


Standard output type is already provided in SAP
click on Output Types
V1 for Sales
V2 for Shipping
V3 for billing these are standard application types

and standard life cycle types are show in picture

goto change mode and copy order confirmation

you will get this screen


change according to your requirement
and assign your access sequence
copy all the dependend entries
save this
Step 4 - Output Determination Procedure
you can go with standard one or for new entry
for creation of routine Tcode is VOFM

click on new entry


enter your procedure and selct it later click on control data

maintain the step,counter,ctype and requirement


here we maintain 2 - if order confirmed only it will activated
here 2 is routine
and save it

Step 5 - Assign Output Determination Procedure Tcode - V/43

after click on this it wil ask at what level need to active


header or item
if it is header you maintain it at document type
if it is item you maintain it at item category type
in this we assign for header
for that select your sales document and assign output procedure and output type
save it

Step 6 - Manintain Condition record


Path - Eassy Access --> Logistics --> Sales and Distribution --> Master Data --> Output --> Sales Dcoument

click on create and maintain our output type and click on Key Combination
our table will display and click on continue

maintain sales organization,Sold-to-Pary,and sales document


where M - Message transmission medium
it is the way of print like print outs,mails e.t.c.,
remember always data message will be 3
then click on communication

maintain your printer information over here


this information will provide by basis team
standard is LP01
and click on print immediately
and give no.of print outs
comeback and save it

test the senario


create oder with our sales arg,sold to party and document type
and goto change mode of order
no need to change any thing
click on sales document where you will see issue output to

and you will get this


you can check previews here
if you want to print the values of your own in output
you need to enter those values in pricing procedure under print coloum
these are the options we will get there

to write a program abaper need to go SE38 Tcode


to develop form Tcode is SE71

Universal Tcode for output is NACE


e communicate with different mediums like emails,print outs,EDI's e.tc., for that purpose we use Output Determination

-> Output Determination --> Output Determination Using Condition Technique Process
tic Execution
asic Shipping Functions --> Output Control --> Output Determination
-> Output --> Sales Dcoument --> VV11 Create
ermination
RQ 1

RQ 2

RQ 3

RQ 4

RQ 5

RQ 6

RQ 7
While runinnig genral cycle process Shipping Point SP1 and Storage Loaction SL1 is tri
triger Shipping Point SP2 and Storage Location SL2 How?

Enduser should not have the authorization to change the payment terms?

When goods are issued as Free of Charge no price is collected only tax amount need t

Offer Multiple Free Goods

ISSUE 1: For MAT X we offer MAT Y,MAT Z,MAT C as Free Goods

ISSUE 2: For MAT X if customer buys 5 quantity he will get MAT Y as Free Good
For MAT X if customer buys 10 quantity he will get MAT X 2 quantity as Free Good
For MAT X if customer buys 15 quantity he will get MAT Y 2 quantity as Free Good

ISSUE 3: Hide Free Goods Line item in Sales Document Processing

How to Offer discounts based on Ship to Party

No charge of pricing in sales orders after saved (wrto Quatation enduser should not h

No Change of Ship to party in sales order


Enhancement and User Exists

To know the name of the program go to any change mode you will get
For example we want to know the name of sales order creation follow the path VA02-->System

Tcode to check enhancement is SMOD

to create the project Tcode is CMOD


follow the path VA02-->System-->Status then you will get one screen in that Program (Screen) you will get program name in this SAPMV4
rogram name in this SAPMV45

You might also like