Workshop

What is Projects/ Introduction to Projects?

 A Project is defined as a task to create a product (or) to provide a service.

 Projects will have Cost, Duration & Resources to work on the project.

Types of Projects in SAP

 In SAP we have below different types of projects,

o Implementation Project
o Support Project
o Rollout Project
o Upgrade Project

Real-time Scenarios
MRF Client / Customer
TCS Implementation in Partner / Consultant
SAP Vendor
Non – SAP means Legacy System
TAG a Project means – Assigning a Project

What is Implementation Project?

 If any client/ customer wants to team up their business operating system into SAP then
they will raise request to Implementation Partner (any IT Company) to convert
operating system into SAP.
 Converting client’s business operations into SAP System for first time then it is called
Implementation Project.
 Implementation Project takes 8 to 12 months duration based on project size.

Implementation Partners Clients

IBM MRF
TCS HERO
Accenture Asian Plants
Deloitte Jindal Steels
Mind Tree Sony
Yash Titan
Wipro Nestle
NTT Data Honda
Infosys Bajaj
 Some Other IT Companies Tvs Motors
Ford
Hindustan Motors
Maruthi
Big Bazar
Coco-cola
Tata Chemicals
Ambuja Cement
LG Polymers
Dr Reddys
Adani Group
Zandu
Cipla
HAL
Mankind Pharma
BHEL
GAIL
BSNL
BOSCH
BEML
CEAT
DMART

Methodologies in SAP

 Implementation partner required proper methodology (route map) to implement SAP to

Companies (any industry).
 In SAP we have following route maps to implement, they are
o ASAP – Accelerated SAP
o AGILE
o SCRUM
o S – IMPLE
o RUN SIMPLE
o ACTIVATE (S4 HANA)
 ** In ECC version all companies used ASAP Methodology but after S4 HANA started
using ACTIVATE.
What is ASAP Methodology?

 ASAP is a route map (or) a methodology used to implement SAP to companies in

different stages?
 Stages is also called as Phases.
 In ASAP we have 5 different maps/phases.
 Client’s business process will be implemented into SAP in 5 different stages.

Phases in ASAP Methodology?

1. Project Preparation Phase

2. Business Blue-Print Phase
3. Realization Phase
4. Final Preparation Phase
5. Go-Live Phase

1. Project Preparation Phase

 In Project Preparation Phase both the management team will involve to finalize
Infrastructure, License, and Consultants etc.
 Once consultants got finalized them both clients end users team & implementation
team consultants will approach to have introduction & project overview discussion
which is called Kick-off Meeting.
 In this Kick-off meeting both the teams will introduce each other, then client project
manager will give project overview.
 Once project overview is done then we consultants have to prepare questionnaire.
(Questions list to know clients business process in details)

2. Business Blue Print Phase (BBP)

 Business Blue Print is a phase as well as a document.
 BBP Document consists of AS-IS & TO-BE documents.
o AS-IS document consists of clients current Non-SAP business.
o TO-BE document consists of clients business operations.
 Once Questions list is ready then we consultants will drop an Email to client’s end users
to know the answers for the questions & once client started to explain business process
we consultants will capture in a document called AS-IS. This will be done by individual
module consultants.
 While Mapping AS-IS & TO-BE process we will get GAP in clients requirement. We will
prepare a separate document called GAP Topics.
  Once BBP document is ready then we consultants will explain to client users & project
managers, if they satisfied with the TO-BE document then they will give Approval (Sign
off) to next phase. This entire explanation process happens in the form of meeting
called Sign-Off Meeting.

3. Realization Phase
 Along with this BBP Phase in parallel our internal IT Team & Basis team will make SAP
Servers – Clients/Systems/ User ID’s ready.
 Once BBP Signoff is done from clients, then we consultants will start configuration (or)
TO-BE Document mapping in SAP Development server – Golden Client. This
Configuration phase is called Realization Phase.
 Consultants will configure every business process of client in SAP starts from
Organization Structure.
 Once Standing Configuration is done then we consultants will move setting to testing
client of development server for testing. Once testing is done then consultants will sit
with ABAP Team to cover GAP.
 Testing’s will be done by individual module consultant (unit testing) & other module
consultants (Integration Testing).

What is Transport Request - TR?

 Each & Every configuration in Development Server – Golden Client will be stored under
TR – Transport Request.
 TR will be used to move the configuration from One Server to Another Server (DEV-
QAS-PRD).
 The Data Maintained, Edited, Deleted (or) Copy in IMG Screen of development server
will store in TR Form.
 We have following ways to select TR to store configuration.
o Last Used TR
o We can create new TR by selection Create Option.
o We can select existing TR’s by using own request option.

Types of TR’s

 We have Parent TR (main TR) & Child TR (sub TR) every configuration will store under
Child TR of Main TR.
 If we want to move TR from development server to quality server we need to release TR
but if we want to move from Quality Server to Production Server TR release is not
required.
How to Release TR’s?

 If we want to move a TR from Development Server to Quality Server we need to release

TR but if we want to move from Quality Server to Production server TR release is not
required.
 Use T Code – SE01/SE09/SE10 to Check, Delete, Release TR’s.
o Go to T Code – SE01.
o Give User.
o Then Activate Modifiable Status Check Box then press enter.
o System will display all TR’s List related to the User.
o Select Main TR then Expand (+) now select Sub TR.
o Click on Release Icon to release Sub TR.
o Now Select Main TR again & release it.

How to Move TR’s?

 We can move TR’s from Client to Client & Server to Server.

Client to Client TR Movement?

 If we are moving configuration from Golden Client to Testing Client of development

then we will use this Client to Client Concept.
 We don’t want any TR release for this & it will be moved by module owners.
 T Code – SCC1
 Go to T Code – SCC1 in testing client.
 Maintain Source client (golden client code), give main TR, activate including Subtask
Checkbox.
 Click on Start Immediately Option.

Server to Server TR Movement

 If we are moving data for DEV-QAS-PRD Servers then we will use this concept.
 We have to release TR’s to move data from server to server.
 T Code – STMS_IMPORT
 Login into destination server then go to T Code – STMS_IMPORT, select the TR then
click on Import Option.
 In real-project TR’s will be moved by BASIS Consultants but, we individual module
consultants should share TR’s list in excel in proper sequence.
 Cutover means whatever data in Non – SAP should be maintained same in SAP
4. Final Preparation Phase
 Once all the TR’s are transferred to Quality Server then we will start 4th phase. I.e. Final
Preparation Phase.
 Before starting this phase we consultants have to provide training to end users, once
training is done we will give 15days time for testing.
 In this phase client end users of all the departments will perform testing in quality
server, if they found everything okay, then they will give acceptance note called UAT.
 Clients will do testing in Quality Server.
 UAT – User Acceptance Test and please find below UAT format but company to
company format may change.

S. No Topic T Code Input Expected Actual Result

Result Result
1 Creation of MM01 MT, MD, Material Material Accepted
Material fields etc 00001 00001
Master Created Created
2 Change MM02 Material Material Material Accepted
Material Code 0001 0001
Changed Changed

 Once UAT is done then we consultants will start cutover activities and prepare for go-live.

Cutover Activities

 Decide Cutover Date.

 Decide Go-Live Date.
 Move all TR’s to production server in a sequence, this will be done by BASIS Team.
 Once all TR’s are moved then we consultants have to create again number ranges,
characteristics, class, condition tables etc. in production servers.
 Data Uploads – We consultants have to upload clients Non-SAP (legacy system) data into
SAP is called Data Uploads.
o From MM we will upload below data
 Material Master Data
 Vendor Master Data
 Initial Stock Upload (Opening Stock)
 Open orders & GR creation capturing.
 Once everything uploaded & moved in production then we will hand over the project to
client called Go Live.
What is Cutover & Go Live Dates?

 The date on which the client’s legacy data extracted and uploaded in SAP is called Cutover
Date. Once cutover is decided then clients will not enter any data in their legacy systems.
They will stop all their payments & purchases b/w cutover & go live dates. If there is any
data left even after go live, then it will be entered manually.
 The date on which first entry is posted on SAP then it is called Go Live Date.

Go Live & Post Go Live Support

 After all cutover activities & gaps fulfillment we will hand over the project to clients called
Go Live Phase. Once Go Live is done then clients will enter all business transaction entries
in SAP.
 After GO live we consultants have to give support to clients for safe entry in SAP. This will
be for 4 weeks to 6 weeks depends on agreement b/w clients & implementation partners.
Providing support immediately for Go live is called Post Go Live Support.
 Once Post Go Live support is done then actual support project will start.

Meetings in Implementation Project

 Kick Off Meeting – Phase 1

 Sign Off Meeting – Phase 2
 Go Live Meeting (Project Handover Meeting)

Documentation in Implementation Project

 Questionnaire (List of Questions)

 AS – IS & TO – BE
 BBP Document
 User Manuals
 Test Cases
 UAT
 Configuration Document
 T Codes List
 Reports List
Templates in Implementation Project

 Material Master Data Upload

 Vendor Master Data Upload
 Initial Stock Upload Template
 GAP Analysis
What is Gap Analysis in Implementation Project?

 As we are aware after receiving client’s requirement we consultants will search solution in
standard SAP. If there is no solution in standard SAP, then it is called GAP.
 To Fulfill this GAP we will do following activities:
o We will check for alternative (work around).
o We will take ABAPERS by preparing FSD document.

List of GAPS in Real-time Implementation Project?

 PO Print Out.
 In the collective number (10chars) field of the RFQ. The number in series should be
automatically generated by the system while document is saved.
 PR Print out.
 Delivery Challan Printout for subcontracting.
 Purchase Register (MM+FI).
 RICEFW
What is RICEFW?

 In Real-time projects RICEFW team is also called ABAP Team.

 RICEFW team helps to cover GAP in the project.
 RICEFW stands for,
o R – Reports
o I – Interface
o C – Conversions
o E – Enhancements
o F – Forms
o W – Workflows
 RICEFW concept is applicable to all modules. Development of these concepts required
separate time & team. Separate team will work on development of programs, scripts.

RICEFW

R – Reports

 Developing new reports (or) database output (reports) by executing program. If clients
requires any new reports for their business then we consultants will take the help of
ABAPers to develop.
 Standard Reports
o Ex – ME2N, MM60, MB51, MB5B, MB52, ME20 etc.
 Customized Reports
o Developed by Functional & ABAP Consultants (new reports).
o Ex – Purchase Register, Sub – Contracting report etc.

I – Interface

 In some projects/clients some of the business process like Storing of material, Planning,
and Involve Uploads are executed in External System. (non sap system)
 Linking Non SAP system & SAP system to transfer data is called Interface. IDOCS concept is
used to transfer data.
 Functional consultants will provide what data need to be transferred (or) what data need to
be received.
 Ex – What Fields, What Numbers etc. to ABAP system.
C – Conversions

 Conversion means converting data from one format to another format (or) from one system
to another system.
 Ex – Transferring data from client’s legacy system to SAP system. During Implementation
project clients will change their business operations from Non-SAP to SAP then we
consultants have to upload whatever data is available in Non-SAP into SAP.
o Ex – Material, Vendor, Stock Upload, Open PO’s etc.
 Uploading tool is LSMW, LTMC, and BDC etc.

E – Enhancements

 Enhancements means we are adding our functionality to standard SAP screens.

F – Forms

 Forms are nothing but printouts.

 Ex – PO Print, PR Print, DC Print (Delivery Challan) etc.

W – Workflow

 Workflows means flow of work.

 Workflow suggests the name who will work next. It will flow the work from one person to
another person.
 Sequence from work to configure this workflow concept functional module will coordinate
with ABAP Consultant and provides the details.

Note – Functional Module Consultants will provide requirements to ABAP Consultants in the
form of FSD(Functional Specific Document)
 FSD
How to Prepare FSD?

 The Functional Specific Document – FSD will prepare detailed design which explains in
details how the requirements will fulfilled requirements/develop.
 In SAP, if functional consultants didn’t got solution, then they will prepare on FSD
Document with clients required and they will share the same with ABAP consultants for
development.
 FSD Document will be prepared by functional consultants.
 2. Support Project
 After Go-Live clients will get support of consultants called Go-Live Support. Once go-live
support is done then actual support will start which is called AMS – Annual Maintenance
Support (or) AMC – Annual Maintenance Contract.
 In this AMS companies (service providers / IT Company & clients) will go for an agreement
called SLA – Service Legal Agreement. Consultants will work as SLA.
 In Support Project consultants will help to resolve the client’s issues in SAP System.
 Issues is called Tickets in SAP. Tickets will exchange by using Ticket Tool.
 SAP Support Project which includes handling tickets is called Issue Tracking System. The
errors (or) bugs forwarded by the end user to the support team are prioritized under three
severity they are High, Medium, and Low. Each and every severity as got its time limits
before that we have to fix error.
 SAP also provides SAP Solution Manager (SOLMAN) which is also called as Ticketing Tool.
General concept of tickets; handling of tickets is called Issue Tracking System. The Errors
(or) bugs forwarded by the end user to the support team are prioritized under three
severity High, Medium & Low.

Consultant Role – Support Project

 The Main job of the supporting consultant is to provide assistance on line to the clients
where SAP is already Implemented for which the person should be very strong in the
subject and the process which are Implemented in SAP at the client side to understand to
analyze to accurate & to give the right solution in right time.
 This is the job of support consultant.

Work Process in Support Project

 The Customer (or) the end user logs a call through any Ticketing Tool (or) by Mail
(RADIX/Server now).
 Each one of the support team is a part of support group.
 Each consultant and client will have access to ticketing tool.
 Whenever a client logs a call (or) creates a ticket in tool he/she has to maintain to which
work group. Ex – PTP, DTC, Production, FI, CO etc.
 Once the calls came to work group the Support Consultant (or) the team needs to send and
IR (Initial Response) to the user depending upon the priority of the calls (Top, High,
Medium, Low, None), then the error is fixed, debugged by the Support Consultant (or) the
Team.
 Then after testing properly by generating TR (Transfer Request through the BASIS &
Transfer to Further Servers).
 Then it is informed to end users/customers/ super users about the changes, which have
moved to production server by CTS – Change & Transport System Process.

Note – In Summary if any configuration (or) customization is required to solve the issue, then
the consultant have to work on Development Client, then the end user will test in the Quality
Server Client (QAS) and after approval BASIS consultant will move changes to Production
System.

Real time Example of Support Project

 End user not able to create STO Purchase Order for a Supplying Plant from a New Plant,
since they got Shipping Point error in PO, hence the document becomes incomplete & he
will not be able to proceed further like PO, Delivery, Billing etc.

Steps to be followed:

 Set Priority like Low, Medium, & High.

 Now you need to solve this ticket and you would analyze the problem & identify that the
SAP configuration has to be done for the new plant.
 You would request a transport for Development client (Dev) to BASIS & you do the change
& request one more transport to BASIS for QA client. Then end will test the same by
creating a purchase order for the new plant & approves it.
 Finally, you request a transport to move the changes to Production once the change is
deployed in production, then the TICKET is close.
 This is just an example, in real – time sometimes we will get issues with severity High in your
day – day support.
 3. Rollout Project
 If client is extending their business such as Adding New Business (or) New Branch and if
they want to use SAP then we consultants have to go for rollout project to extend client
business operations to new business (or) branch.
 We have 2 different types of rollouts,
o Company Code Rollout.
o Plant Rollout.
 In this rollout project our consultant’s role is to create new plant & assignment along with
other plant configurations.
 We have to extend master data’s to new plants & company code.
 4. Upgrade Project
 If client wants to upgrade to latest version of SAP then we have to go Upgrade Project.
 In this upgrade project BASIS Consultants will take clients backup then servers will be
upgraded in Development --- Quality --- Production (DEV – QAS – PRD) sequence. Once
upgrade is done we functional module consultants will check the latest changes and informs
to client.

What is CR?

 CR stands for Change Request.

 Change Request concept will come in support project. After Implementation, if clients
wants to add (or) modify to the existing configuration in SAP.

Points to be noted?

 Before CR, consultants should do Analysis, Effects on existing system settings.

 Consultants should get approval from authorities to perform CR.
 CR may include ABAP changes (or) only functional changes.
 CR Request can be maintained in solution manager (SOLMAN) if it is configures in project.
 CHaRM (Change Request Management) is a tool delivered with SAP solution manager & it is
a proper approval process & it tracks change request, transport requests.
 LSMW
What is LSMW?

 LSMW stands for Legacy System Migration Workbench – ECC. It is a tool use in SAP to
Transfer data from Non SAP to SAP System.
 Non – SAP system is also called as Legacy System.
 The main function of SAP LSMW tool are as follows,
o Import Data – Data in Spread Sheet Tables & (or) sequential files.
o Export Data – Converts the from source format to target format.
o Legacy Data – Converts data into target format to upload data.

T Code – LSMW

1. Section 1 – Record the LSMW

 Under this heading we will record the Fields & T Code to be uploaded.
 Go to T Code – LSMW
 Maintain Project (Ex – Z Material/ Y Material)
 Give Sub-Project (Ex – Z Material/ Y Material), Object (Ex – Material Creation / Vendor
Creation/ Stock Upload)
 Click on Creation Icon.
 Maintain Project Description, Sub-Project Description, and Object Creation Description.
(Ex – Material Creation).
 Then click on Execute.

Select Step No 1 – Maintain Object Attributes

 Click on Change Icon.

 Click on Batch Input Recording Button.
 Click on Recording Overview at right side (mountain icon).
 Click on Create Icon.
 Maintain Recording Details
o Recording – YMM01
o Description – Material Creation
o Continue.
 Give Transaction Code (T Code) – which needed to be uploaded (ex – MM01).
 Maintain the fields which needed to be recorded & save the data. (Do not click on fields
which you don’t needed).
 Click on Default All & check your recording.
 Save the data. (Step 1 is recorded).
 Click on Recording Field.
o Click Space Bar then system will display recording name automatically then select
the name & save the recording.
 Go Back.
 Click on Object Overview (mountain Symbol).
 Click on Tables
 Check the Recorded Fields & Copy all 4 columns (Field Name, Field Description, Type, and
Target Length).
 Open New Excel Sheet.
o Post it in Excel Sheet 1.
o Open Sheet No2 in same excel and rename it to template.
o Copy all the fields from Sheet 1, right click and paste in Transpose Mode.
o Make all the fields in proper format & share with client for Legacy Data, & in this
format clients will share Legacy Format Data to Consultants.
 Go back to SAP screen.

Select Step No 2 – Maintain Source Structure

 Select step no 2 – maintain source structure and execute.

 Click on Change Icon.
 Click on Create Icon.
 Give Source Structure Name (Ex – Z Material 1 / Y Material 1)
 Give Description (Ex- Material Structure)
 Continue & Save & go back, system will select step 3 automatically.
Step No 3 – Maintain Source Fields

 System will select step no 3 maintain source fields automatically and execute it.
 Click on Change Icon.
 Click on Source Structure.
 Click on Table Maintenance Icon.
 Copy the recording fields format from excel and paste in SAP.

Field Name Type Length Field Description

MBRSH C 1 Industry Sector
MTART C 4 Material Type
KZSEL_01 C 1 KZSEL_01
MAKTX C 40 Material Description
MEINS C 3 Base Unit of Measure
MATKL C 9 Material Group
BRGEW C 17 Gross Weight
GEWEI C 3 Weight Unit
NTGEW C 17 Net Weight
 Go back – go back system will select step 4 automatically.

Step No 4 – Maintain Structure Relations

 System will select step 4 automatically and execute it.

 Click on Change Icon.
 Double Click on Source Structure Name
 Continue () & Save it.
 Go back – system will select step 5 automatically.

Step No 5 – Maintain Field Mapping & Conversion Rules

 System will select step 5 automatically and execute it.

 Click on Change Icon.
 Click on Extras in Menu Bar
o Click on Auto field Mapping & Continue ().
o Click on Accept Proposal for all recorded fields. (If we are having 100 fields, we
have to accept proposal for all).
o Once Auto Field Mapping is completed, Continue () & save the step 5.
 Note –
 Once we receives the template filled with data back from client. Then we will check the
fields, formats, length etc.
 If all the data is correct then copy the data & open a note pad & paste, & click backspace.
Save the note pad on desktop.
 Now go to SAP, use LSMW T Code to upload data into SAP.

2. Section 2 – Data Upload Through LSMW

 Go to T Code – LSMW.
 Give Project, Sub – Project, Object.
 Execute.

Step 1 – Specify Files (Step 7 in LSMW)

 Select Step 7 in LSMW specify files and execute.

 Click on Change Icon.
 Click on Legacy Data on the PC.
 Select the Notepad file from Desktop.
 Give Name (Ex – Material Upload).
 File Contents
o Activate Data for One Source Structure (Table).
 Delimiter
o Activate Tabulator.
 Continue & Save it.
 Go back – system will select step 2 automatically.

Step 2 – Assign Files (Step 7 in LSMW)

 System will select step 2 automatically and execute it.

 Double click on Source Structure Name.
 Continue ()
 Go back and system will select step 3 automatically.
Step 3 – Read Data (Step 8 in LSMW)

 System will select step 3 automatically.

 Execute – Execute
 Check Allow.
 Check the count, should be same with note pad lines.
 Go back – go back.
 System will selects step 4 automatically.

Step 4 – Display Read Data (Step 9 in LSMW)

 System will select step 4 automatically and execute it.

 Continue ().
 Click on any line and check the data.
 Go back – go back.
 System will select Step 5 automatically.

Step 5 – Convert Data (Step 10 in LSMW)

 System will select Step 5 automatically.

 Execute – Execute
 Check the convert count, it should be same with read data.
 Go back – go back.
 System will select Step 5 automatically.

Step 6 – Display Converted Data (Step 11 in LSMW)

 System will select Step 5 automatically.

 Execute.
 Continue ()
 Check data.
 Go back – go back.
 System will select step 7 automatically.
Step 7 – Create Batch Input Session (Step 12 in LSMW)

 System will select Step 7 automatically.

 Execute – Execute
 Batch is created – continue.
 System will select step 8 automatically.

Step 8 – Run Batch Input Session (Step 13 in LSMW)

 Select Session Line.

 Click on Process Icon.
 Activate Display Error Button.
 Activate Extended Log & Export Mode.
 Click on Process.
 Once Batch Input session is completed (means data uploaded) exit the batch. (Batch input
session is completed nothing but data upload is completed.)
 S4 HANA
What is S4 HANA?

 S4 HANA stands for SAP Business Suite 4 SAP HANA. It brings the next big wave of
innovation to SAP customers, similar to R2CR3.
 SAP S4 HANA Abbreviations:
o S – Stands for simple & it is fourth version of SAP business suite after R1, R2, and R3
& ERP architecture.
 SAP S4 HANA is an ERP Business suite based on SAP HANA in memory database which
allows companies to perform quick transactions.
 SAP Releases S4 HANA in February 2015 and new companies (clients) will migrate to S4
HANA as it is next generation to the SAP business suite.
 SAP S4 HANA is easier to use and it helps to solve more complex problems and handles
large amount of data.
 One of the key to S4 HANA is that it uses SAP FIORI rather than using traditional GUI.
 SAP FIORI is a collection of commonly used S4 HANA functions that are displayed simple,
really designed tile that can be accessed across various devices including Desktop, tablets
(or) mobile devices.
Benefits of S4 HANA
S4 HANA allows you to:

 Reinvent business models.

 Drive new revenues and profits.
 Connect with customers through any channel to deliver value.
 Access the internet of things and big data.
 Simplify your processes, drive them in real – time and adapt instantly.
 Gain insight to any data, in real – time – supporting instant decision making.
SAP S4 Hana will simplify IT landscape and reduce cost of ownership (TCO), through:

 Reducing your data footprint.

 Working with larger data sets in one system saving hardware costs, operational costs, and
time.
 Choice of deployment: cloud, on premise, or hybrid to drive quick time – to – value.
 Innovation is also made simple with an open platform (SAP HANA Cloud Platform) to drive
application – for example, predicting, recommending and simulating – while protecting
existing documents.
 Finally business users can leverage a simple, role – based user experience based on modern
design principles that minimize training and increase productivity.
Activate Methodology

 Previously we used ASAP Methodology in traditional system but in S4 HANA we started

using ACTIVATE methodology.
 SAP Activate provides ready to use guided configuration, key deliverable and accelerators
(documents, templates) which is supported for SAP S4 HANA cloud and On – Premise
solution.
 SAP Activate is the innovation adoption framework that expedites SAP S4 HANA
implementations throughout the customer lifestyle. It offers ready-to-run digitized business
and technology processes, guided configuration and next generation methodology.
Phases in Activate Methodology

MM Simplification in S4 HANA

 New material type SERV is introduced in place of DIEN – Services.

 Material number range length is extended to 40 Chars earlier it was 18 Chars.
 Material ledger made mandatory in Material Master accounting 1 view (FI Change).
 Vendor Master is removed completely in S4 HANA in that place Business Partner concept is
introduced. Same for customer master also (SD).
 T Code changes in SAP MM Module in S4 HANA:
o XK01, XK02, XK03, XK04, XK05, XK06, XK07, MK01, MK02, MK03, MK04, MK05,
MK06, FK01, FK02, FK03, FK04, FK05, FK06 are replaced with T Code – BP.
o MB1A, MB1B, MB1C, MB02, MB03, MBRL, MBST are replaced with T Code – MIGO.
o Batch Management T Codes:
 MSC1, MSC2, MSC3 replaced with MSC1N, MSC2N, MSC3N
 SAP introduced new output management in S4 HANA. BRF+ - Business Rule Framework
(T Code – OPD). It is unified solution across – SD, MM, and FI.
 It is fully integrated with FIORI
 User can send multiple messages to multiple recipients using multiple channel at same
time.
 User can configure without ABAP Program.
 SAP has introduces new table MATDOC in S4 HANA. It is a central table contains all
materials documents and history.
 In data uploads SAP introduced LTMC tool. In this tool template will be available ready-
made but in LSMW templates to be prepared mandatory.
What is LTMC?

 Whenever we are implementing SAP S4 HANA to the companies, we can migrate master
data & business data’s from Non-SAP system to SAP by using Migration Cockpit.
 LTMC can transfer Master Data’s, Transaction Data & Balances.
 It only works in Web browsers.
 LTMC is advanced version of LSMW.
 It is mainly useful for Green Field Implementation. (Software Development)
How do we activate LTMC?

 Users must run the T Code – SICF in the client system.

What is the difference between LSMW & LTMC?

 LSMW – Stands for Legacy System Migrate Workbench & it is tool to upload data in SAP
System by preparing Manual Templates.
 LTMC – Stands for Legacy Transfer Migration Cockpit & it is a data migration tool available
in S4 HANA with ready-made template.
What is SAP HANA?

 SAP HANA stands for “High Performance Analytic Appliance”. It is a multimodal database
that stores data in its memory instead of keeping it on Disc (CD).
 SAP HANA is a fast and powerful database which provides real-time information quickly.
 In HANA we have One Cloud Edition & One Premises Edition and for this we need physical
server installation required.
 Business Partner
Business Partner

 Business partner is an Add-on in SAP S4 HANA Server & this is replace of Vendor &
Customer in SAP.
Define BP Roles

 BP roles represents the functionality of Vendor.

 SAP is designed below standard BP roles,
o FLVN00 – Company Code BP Role
o FLVN01 – Purchasing BP Role
 We can use above standard BP codes (or) we can customize by copying standards by going
below path.
Path
o SPRO --- IMG --- Cross Application Components --- SAP Business Partners --- Business
Partner --- Basic Settings --- Business Partner Roles --- Define BP Roles --- Enter.
o Click on Position
o Give – FLVN00/ FLVN01, Enter.
o Select BP Role Line
o Click on Copy as icon
o Give your own name (6 Chars) (Ex – ZFINAN)
o Give Title & Description.
o Enter & Save.

Suggestion: In Real time do not copy, go with standards

Define BP Role Grouping

 Under this we are going to group both BP finance and purchasing.

Path
o SPRO --- IMG --- Cross Application Components --- SAP Business Partner --- Business
Partner --- Basic Settings --- Business Partner Roles --- Define BP Role Grouping ---
Enter.
o Click on New Entries
o Give Role Grouping (6 Chars) (Vendor Account Group, Ex - ZDOMV)
o Title – (Ex – ZDOMV Domestic Vendor)
o Description – (Ex – ZDOMV Domestic Vendor)
o Press Enter
 o Double click on BP Role Grouping -> BP Roles on left side
o Click on New Entries
o Maintain BP Roles for both Purchasing & Finance.
o Enter & save.

BP Role Title
ZPURCH Purchasing
ZFINAN Finance

Define Number Ranges for Business Partner

 Under this we are going to define number ranges for Business Partner.
T Code – BUCF
Path
o SPRO --- IMG --- Cross Application Component --- SAP Business Partner --- Business
Partner --- Basic Settings --- Number Ranges & Grouping --- Define Number Ranges --
- Enter.
o Click on Change Intervals
o Insert Line
o Give Serial Number, From & To Numbers (Either Internal/ External (not both))
o Enter & Save.
Assign Number Range

 To Assign Number Range use below path.

Path
o SPRO --- IMG --- Cross Application Component --- SAP Business Partner --- Business
Partner --- Basic Settings --- Number Ranges & Groupings --- Define Groupings &
Assign Number Ranges --- Enter.
o Click on New Entries
o Give Role Grouping (ZDOM) (4 Chars)
o Maintain Description (ZDOM Domestic Vendor)
o Assign your number range codes in Respective Number Ranges Fields.
o Enter & Save.
Define Field Selection of Business Partner

 We can control field behavior of business partner by using below path.

Path
o SPRO --- IMG --- Cross Application Component --- SAP Business Partner --- Business
Partner --- Basic Settings --- Field Groupings --- Configure Field Attributes per BP Role
--- Enter.
o Double Click on Configure Field Attributes for Each Role Category.
o Click on Position
o Give your BP Role (Purchasing & Finance)
o Enter
o Double click on BP Role & manage the fields.
Define BP Role Direction Vendor to BP

 In this settings we assigned BP Roles to vendor account groups for vendor master record.
 When you process this settings, then the vendor will be created by using vendor account
group based on BP Role Assigned.
 Define Vendor Account Group & Field Selection (OMSG T Code)
 Create Number Ranges for Vendor (Same as BP Number ranges) & activate external number
range box. (T Code OMSJ)
 Assign Number range to Vendor Account group.
Master Data Synchronization/Assign BP Account Group & Vendor Account Group
Path
o SPRO --- IMG --- Cross Application Component --- Master Data Synchronization ---
Customer/ Vendor Integration --- Business Partner Settings --- Settings for Vendor
Integration --- Field Assignment for Vendor Integration --- Assign Keys --- Define
Number Assignment for Direction BP to Vendor --- Enter.
o Click on New Entries
o Give BP Grouping Number & Maintain Vendor & Activate Same number box.
Clients Role in Business Partner
Create Business Partner (Vendor)

 Go to T Code – BP
 Click on Vendor Type – Person/Organization /Group (always click on Organization)
 Select BP Role & immediately click on Create Icon.
 Select Grouping from drop down which decides the number range.
 Enter all mandatory (or) general details in General Data Tab.
 Click on Company Code option
o Give your Company Code, enter
o Maintain all required fields.
 Click on Purchasing Option
o Maintain all required fields.
 Then Save the Business Partner.
 GST
GST (Goods Service Tax)

 GST is an Indirect tax throughout India to replace existing multiple taxes levied by the
Central and State Governments.
 The GST is a Tax on Goods & Services sold domestically.
 The Tax is included in the final price and paid by the customers & passed to the government
by sellers.
 The GST bill was passed in Parliament on 29th of March 2017 & came into effect on 1st July
2017.

Types of GST’s

 SGST - State Goods & Service Tax

 CGST - Central Goods & Service Tax
 IGST - Integrated Goods & Service Tax
 UGST – Union Territory Goods & Service Tax

SGST

 It is used by the state government on Intra State (Same State) transaction. The revenue
collected by State Government through GST is earned by the State Government.

CGST

 This is for Central Government on Intra State Goods & Service Transaction. The Central
Government Collects the revenue generated through Central Goods & Services Tax. This
revenue is shared between Central & State Government.
 Ex – If Same State dealer is selling the goods to same state customer, then SGST & CGST will
get calculate. SGST amount will be to State & CSGST amount will be to Central.

IGST

 Integrated Goods & Service tax is calculated on Inner State (between 2 states) goods &
service transaction. It is applicable in Imports & Exports also.
 Applicable GST rate are determined by the combination nature of purchase and Harmonized
System of Nomenclature (HSN) code assigned to material.

GST Calculation

Nature of Purchase Before GST After GST

Goods Purchase within the Excise + VAT CGST + SGST
State
Goods Purchase inter state Excise + CST IGST
Import Purchase BCD, CVD, AED, CESS, ECESS IGST
Inward branch transfer (Intra Excise / No Excise No Tax
State)
Inward Branch Transfer (Inter Excise / No Excise IGST
State)
Job Work Expense No Tax, only VAT CGST + SGST

CGST SGST IGST UGST

GST Rate 2.5 2.5 5 *
% Bands 6 6 12 *
9 9 18 *
14 14 28 *

 As discussed GST applicable rates are determined based on Nature of Purchase and HSN
Codes.

What is HSN Code?

 HSN Code is a 4 to 8 Digits Uniform Code that classifies products. It is used for classify
products in various sections.
 ** SAC stands for Service and Accounting Code & it is used to classify services.

How to Create HSN Code?

 Go to T Code – J1ID
 Select Chapter ID button
 Click on Maintain Icon
 Click on New Entries
 Give Chapter ID (HSN Code)
 Maintain UOM – (Ex – Kgs)
 Maintain Description as per law – (Ex – Construction Products)
 Save.

How to Assign HSN Code in Material Master?

 Go to T Code – MM01
 Give Material Number, Industry Sector, Material Type.
 Select Foreign Trade Export/ Import View, Enter
 Give your plant, enter
 Go to Foreign Trade Data Tab
o Control Code
 Assign HSN Code in this field.

Consultant Role

Configuration Steps

Steps T Code
Assign Tax Procedure to Country OBBG
Define Tax Access Sequence OBQ2/ QBYZ
Define Condition Types (TAX) OBQ1/ OBYZ
Create Account Types OBCN
Define Tax Procedure OBQ3/ OBYZ
Assign GL to Account Keys GL OB40
Create Tax Code in Country FTXP
Maintain Tax Condition Records FV11

Changes in SAP after GST

 Earlier we used tax procedure TAXINJ. It is a tax calculation procedure for Indian Version
and it supports formula based calculation but in TAXIN condition based support.
 HSN code is mandatory in material master & it will be created in J1ID T code.
 Maintain Vendor GST Number in Tax Number 3 Field. (IN3 – Indian Tax 3)
 System added a new tab called INDIA in Purchase Order Item Data Level & in that we can
check HSN code copied from Material Master & same will copy to Invoice Screen MIRO.
 System added below new transaction codes,
o J_1IG_INV – This T Code is added in STO for GST Invoice & it is used in Inter STO.
o J1IGSUBCON – Create Challan.
o J1IGRECON – Subcontracting Reconciliation.

GST Condition Types in SAP

CGST JICG IN Central GST

SGST JISG IN State GST
IGST JIIG IN Integrated GST
UGST JIUG IN Union Territory GST
CGST JICN IN Central GST – ND
SGST JISN IN State GST – ND
IGST JIIN IN Integrated GST – ND
UGST JIUN IN Union Territory GST – ND
CGST JICR IN CSGT Reversal Charge
SGST JISR IN SGST Reversal Charge
IGST JIIR IN IGST Reversal Charge
IGST JIMD IN Import GST deduct
IGST JIMN IN Import GST – ND
***ND – Non Deductible
 Warehouse Management
 Warehouse management is one of the module in SAP which will be used to store company’s
materials in Racks & Bins.
 Warehouse management streamlines and controls all warehousing processes to create an
efficient operation. It allows user to manage all structures present in a warehousing
operation regardless of their complexity, while monitoring stock differences & controlling
hazardous materials.

Benefits

 Faster Inventory Process

 Accurate Goods Tracking
 Warehouse Automation
 Better Organization
 Customize to fit your operation
 Reduce warehouse costs
 Increase Visibility
 Improve Compliance

Warehouse Management Organization Structure

Storage Storage Storage

Type Type Type

Storage Storage Storage

Section Section Section

Storage Storage Storage

Bin Bin Bin

Where MM Ends from there WM Starts

Define Warehouse Management Organization Structure
Define Warehouse Number

 Warehouse is a 3 Character Code with 25 Characters Description.

 It will be assign to Plant & Storage Location. (Can Assign to Several Plants & Storage
Locations).
Path
o SPRO --- IMG --- Enterprise Structure --- Definition --- Logistics Execution --- Define,
Copy, Delete, Check Warehouse Number --- Enter
o Double click on Copy/ Delete/ Check Warehouse Number
o Click on Copy As Icon
o Give From Warehouse Number – 001(Standard)
To Warehouse Number (your own 3 char code) – (Ex) WM1
o Continue --- Continue
o Go back
o Double click on Define Warehouse Number Line
o Click on Position
o Give your own Warehouse number
o Maintain your own Warehouse Description
o Enter & Save.
Assignment of Warehouse Number to Plant/ Storage Location

 One Warehouse number can be assigned to multiple plants & storage locations.
Path
o SPRO --- IMG --- Enterprise Structure --- Assignment --- Logistics Execution --- Assign
Warehouse number to Plant/ Storage Location --- Enter
o Click on New Entries
o Give your Plant, Storage Location, Warehouse Number
o Enter & Save.
Warehouse Integration

RFC Inventory
Radio Frequency Management
Connection

Warehouse
Management

QM SD – Sales &
Quality Distribution
Management

Define Storage Types

 Number of areas can be defined within the warehouse to store the products is called
Storage Types.
 Ex –
o Fast Moving Materials
o Slow Moving Materials
o Bulk Materials etc.
Path
o SPRO --- IMG --- Logistics Execution --- Warehouse Management --- Master Data ---
Define Storage Type --- Enter
o Select 001 Warehouse line.
o Click on Copy As icon
o Give your Own Warehouse Number & save.

Note – When we copy warehouse number from Standard 001 then storage types will copy
automatically. We can add new storage type by copying 1.

Define Storage Sections

 This storage type can be divided several areas called Storage Sections.
 Storage Section contains Storage BINS, where product will store physically.
 Path
o SPRO --- IMG --- Logistics Execution --- Warehouse Management --- Master Data ---
Define Storage Section --- Enter

Note – When we copy warehouse number from Standard 001 then storage sections will copy
automatically and if required we can add new storage sections by using copy as Icon.

Create Storage BINS

 We can create storage bins manually/ system will also create bins automatically.
T Code – LS01N

Path
o SAP Easy Access Screen --- SAP Menu --- Logistics --- Logistics Execution --- Master
Data --- Master Data --- Warehouse --- Storage Bin --- Create --- LS01N Manually
o Give your Warehouse Number – WM1
o Give your Storage Type – 001
o Give Storage Bin – your own code (ex – 08.01.2022 (10 chars))
o Maintain Storage Location – 001
o Maintain Maximum Weight of the box and Total Capacity of Box.
o Maintain Storage Bin Type (Ex- B1)
o Enter & Save.

Storage Bin T Codes

LS01N Create Storage BIN
LS02N Change Storage BIN
LS03N Display Storage BIN

Define Number Ranges in Warehouse Management

Path
 SPRO --- IMG --- Logistics Execution --- Warehouse Management --- Master Data --- Define
Number Ranges --- Enter
 Click on For Transfer Requirement
o Give Warehouse Number
o Click on Change Intervals
o Insert Line
o Give Serial Number, From & To number ranges (10 digits, Interval)
o Enter & Save
o Go back – go back
 Click on For Transfer Order
o Give Warehouse Number
o Click on Change Intervals
o Insert Line
o Give Serial Number, From & To number ranges (10 digits, Interval)
o Enter & Save
o Go back – go back
 Click on For Quant
o Give Warehouse Number
o Click on Change Intervals
o Insert Line
o Give Serial Number, From & To number ranges (10 digits, Interval)
o Enter & Save
o Go back – go back
 Click on For Past Change Notice (PCN)
o Give Warehouse Number
o Click on Change Intervals
o Insert Line
o Give Serial Number, From & To number ranges (10 digits, Interval)
o Enter & Save
o Go back – go back
 Go to Assignment
o Click on Number Ranges
o Go to Position
o Give Your Warehouse Number
o Assign all your serial numbers in their respective fields (Transfer Requirement,
Transfer Order, Quant, & Post Change Notice (PCN).
SAP MM – IM & WM Inward Process Flow

Purchase Create PO Goods

PR Release PO Release Receipt Note
Requisition wrt PR
(GRN)

MM-Purchasing & Inventory

MM-Inwards

Transfer Order Transfer Order Transfer

Confirmation Creation Requirement (TR)
 Production Planning
Production Planning Module

 PP is one of the important module in sap that helps businesses to plan the manufacturing,
sale and distribution of goods. ...
 SAP PP activities include material requirements planning, bill of material, routings and
capacity planning.
 SAP PP is an important module of SAP. It tracks and makes a record of the manufacturing
process flows, for example, the planned and actual costs. Also, goods movements from the
conversion of raw material to semi-finished goods.
 It is fully integrated with the other SAP modules like SD, MM, QM, and FICO & PM.
Organization Structure in SAP PP

 In any Production manufacturing location will be plants and storage location within the
plants.
 Importance of Plant and storage locations in Production Planning module -
o All Production master data is created at Plant level.
o Planning activities are also performed at Plant level.
 Production Confirmation process and related goods movement occur at plant and storage
location level.
Master Data in SAP PP

 Material Master
 BOM - Bill of material
 Work center
 Routing
 Production version
 Master data is generally static for any company and is very rarely changed depending on the
requirement. There are 5 master data to be maintained in Production Planning module.
Material Master

 The material master contain information on all the materials that a company procures,
produces, stores, and sells. It is a number uniquely identifies a material master record, and
hence a material.
 Materials with the same basic attributes are grouped together and assigned to a material
type such as finished, raw material, etc.
 It is used for the following purposes:
o To purchase materials
o For Goods Movement postings such as goods issue or receipt in inventory
management and also for physical inventory postings
o In invoice verification for posting invoices
o In sales and distribution for sales order fulfillment process
o In production planning and control for material requirements planning, scheduling,
and production confirmation processes.
Bill of Material (BOM)

 A bill of material is a complete, formally structured list of the components together with the
quantity required to produce the final product or assembly.
 BOM's are used in material requirement planning and product costing.
 You can also create up to 99 alternative BOMs for a single product.
 For Products having variants, you can create Super BOM, which has all possible types of
components used to manufacture different types of variants, and the appropriate
component is selected based on characteristic chosen in the sales Order.
 For example, Product Cycle can contain all types of frames (with different colors and sizes)
and desired frame is selected in production order based on color and size chosen in the
sales order.
Work Center

 A Work Center is a machine or group of machines where production operations are

performed. Work centers are used in task list operations (Routings).
 It contains the data for
o Scheduling
o Capacity
o Costing
Routing

 Routing is nothing but a sequence of operation performed at the Work Center. It also
specifies the machine time, labor time, etc. for the execution of operations.
 It is also used for scheduling of operations and used in standard cost calculation of the
product.
Production version

 The production version is a combination of BOM and Routing data for production. It is a
linkage between BOM & Routing and determines the manufacturing process.
 There can be multiple production versions as per different manufacturing process to
produce the product.
Demand Management

 The function of Demand Management is to estimate requirement quantities and delivery

dates for finished products and important assemblies. Demand Management uses PIR
(planned independent requirements) and customer requirements.
 Planning strategies must be defined for a product. It represents the methods of production
for planning and manufacturing. There are two methods by which we can do this.
 Make to Stock: Production of goods without having sales orders, i.e., stock is produced
independently of orders.
 Make to Order: This strategy applies to the production of material for a specific individual
sales order or line item.
Material Requirement Planning (MRP)

 MRP determines any shortages and creates the appropriate procurement elements. It does
net requirement calculation and generate planned orders for in-house produced materials
and purchase requisition for raw materials.
 It does lead time scheduling and calculate production dates in planned orders.
 It explodes the BOM and generates procurement proposals at each BOM levels.
Production Orders

 The output of MRP will be "Planned Orders", which needs to be converted to production
orders for further execution of the process.
 The Production Order is firmed receipt element, which is not affected by MRP run, unlike
Planned Orders.
 Production Order is a document which specifies what material needs to be produced and in
what quantity. It also contains the BOM components and routing operation data to be
performed at the work center.
 Production Order is released for execution, and material availability checks can be carried
out which determines if there are any missing components.
Production Order Confirmation

 When goods are produced physically at the shop floor, then production order must be
confirmed.
 During confirmation, components materials can be consumed automatically via back flush
mechanism and Goods receipt of material can be performed automatically via operation
Control key in Routing.
 However, instead of auto goods movement, manual Goods Issue and receipt can be
performed separately from confirmation.
 Any failed goods movement due to a deficit of component stock can be reprocessed
manually.
 Activity costs such as machine, labor, etc. will also be updated in the production order
during confirmation on an actual basis.
 The order gets CNF (Confirmed) and DLV (Delivered) status after final confirmation and final
Goods receipt.
 If confirmation is posted wrongly, then we can cancel the confirmation and post it again
with correct data.
Production Order Close

 After the production order is delivered completely or we don't want to execute the order
further then Order should be technically completed.
 After Order gets TECO (technical completion) status, it gets deleted from stock/requirement
list and is no longer considered in material requirement planning run. All dependent
reservations also get deleted from the system.