SlideShare una empresa de Scribd logo
1 de 37
SAP ECC ERP - MM
By Lokesh Modem
SAP LANDSCAPE
 DEVELOPMENT – CLIENT
 QUALITY –CLIENT
 PRD –CLIENT
 SANDBOX- Testing
DEV
QTY
PRD
SAP Projects
 GREEN FIELDS – NEW IMPLEMENTATION
 BROWN FIELD – MIGRATION
 SAP S4 HANA CONVERSION – ECC TO S/4 HANA CONVERSION
 ROLL-OUT Project
 Enhancement project - W-WORKFLOW , R-REPORT I-INTERFACES
C-CONVERSION , E – ENHACEMENT F-FORM
 Technical upgradation – EHP 6 TO EHP 7 OR EHP 8
SAP Implementation – ASAP Methodology
 1 . Project preparation - 2months
 2. Business blueprint documentation -3months AS IS , TO BE , E2E ,
Requirement gathering , GAP analysis
 3. Realization – Functional – Designing & Developing of business scenarios
 4. Final preparation – Cut over , open po, ISU-561 ,
QTY – UAT , USER TRAINING , USER MANUALS , CONFIG DOC,
 5. GO LIVE & SUPPORT
SAP MODULES
 SAP TECHNICAL - ABAP PI PO BASIS
 SAP FUCNTIONAL – MM PP PM QM WM FI CO SD
 MASTER DATA
 TRANSACTION DATA
 DATA WILL BE SETTLED IN TABLES
SAP Organization structure
 Client or Company - WIPRO GROUP
 COMPANY CODE - WIPRO E-OIL , SOAP , ELECTRICAL LIGHTS , IT , INFOTECH
 CONTROLLING ORG – COSTING
 PLANT -- PURCHASING ORG -- SAL ORG  SALES AREA, DIVISION ,
DISTRIBUTION CHANNEL
 STORAGE LOCATION
 WM
 STORAGE TYPE
 STORAGE SECTION
 STORAGE BIN
 QUANT - RACK ARRANGEMENT
CLIENT
 A client is an independent organizational unit.
 A client is considered synonym for a group.
 A client is self-contained technical unit.
 General data & tables used for several organization structure are stored at
client level.
 Client is positioned in the highest level in Enterprise Structure.
 Several company code can be uniquely assigned to a client.
COMPANY CODE
 A Company Code is a legal entity & independent accounting unit.
 Balance Sheet & Profit & loss account are created at Company Code level.
 Company Code is organizational unit prepared by FI.
 Several Company Code can be uniquely assigned to a Client.
 Several Company Code under same client can have same chart of accounts.
SALES ORGANIZATION
 Sales Organization is an organizational unit of Logistics, which groups the enterprise
according to the requirement of Sales & Distribution.
 Sales Organization distributes goods & services.
 Sales Organization is liable for sold products, responsible for the customers right of
recourse & negotiating sales condition.
 One or more Sales Organization can be uniquely assigned to a Company Code.
 Sales Organization can be assigned to one or more plant. This assignment is not unique,
so several Sales Organizations can also be assigned to one plant.
 Each Sales Organization has its own master data, for eg customer & material master data,
as well as conditions, pricing & output type.
 A Sales Organization is the highest level (after the Client) to which sales figure are
summed for SD with statistics currency.
 Sales Organization can be used as selection criteria for listing of sales document, as well
as for creating delivery & billing worklist.
 Different output type can be defined for sales & billing document, for each Sales
Organization.
 Sales Organization is also used to take regional, national, international sub-division of the
market into account.
DISTRIBUTION CHANNEL
 A Distribution Channel is a mean through which saleable material or services reach the
customer.
 A Distribution Channel represents the strategies to distribute goods and / or services to the
customers. Eg: wholesale, retail, institutional, etc.
 Distribution Channel can be assigned to one or more Sales Organization.
 Same customer can be served through one or more Distribution Channel, within a Sales
Organization.
 Distribution Channel can be set as per company's marketing strategies or internal organization.
 Master data can vary (Customer & material Master data, Prices, discounts / surcharge, output
type, etc) for each Sales Organization & Distribution Channel, i.e, within Distribution Channel
master data can be defined separately.
 Master data created for one Distribution Channel can also be used in other Distribution Channel.
 Different sales document type can be defined for Distribution Channel.
 Sales Office can be assigned to Distribution Channel.
 Items in a delivery & billing documents can belong to different Distribution Channel.
 Distribution Channel can be used as selection criteria for creating lists
DIVISION
 Division represents a product line or grouping of materials or services.
 Division can be assigned to one or more sales organization.
 Division can be assigned to one or more distribution channels.
 Material always belongs to only one Division.
 Master data can vary from Division to Division.
 Different Division can share same master data, if shared master data is created.
 Sales Office can be assigned to Division .
 In sales document type, if Item Division is not activated, it will accept material from the
Division at header level only & if material at item level is from different Division from
header level, the same is not accepted.
 Item in delivery or billing can belong to different Division.
 Division can be used as selection criteria in sales document & also for creating delivery
worklist.
 Different output type can be used for printing sales document for each Division.
SALES AREA
 Sales Area is made up of combination of Sales Organization, Distribution Channel &
Division.
 It defines the distribution channel a sales organization uses to sell products from a
certain division.
 A Sales Area belongs to only one Company Code.
 During the processing of SD documents, system accesses various master data,
according to Sales Area. The system also carries out various checks concerning the
validity of certain entries according to Sales Area.
 Sales document, delivery document & billing document is always assigned to Sales
Area.
 Each SD document is assigned to exactly only one Sales Area. This assignment cannot
be changed.
 Various analyses can be carried out within Sales Area. So, Organization structure should
be as simple as possible.
 Sales Area is used for reporting & pricing.
 The customer data record contains pages (views) with the data that is specific to Sales
Area.
PLANT & STORAGE LOCATION
 In SD, a Plant represents the location from which material & services are distributed &
correspond to a distribution center. Which is also known as Delivering Plant. The relevant
stocks are kept here.
 In SD, the Plant has a central function:
 At least one Plant is necessary in order to be able to use SD module.
 A Plant is uniquely assigned to a Company code.
 Assignment between Sales organization & Plant is not unique.
 Delivering Plant is important for determining shipping point.
 For a Plant to deliver goods to the customers, it must be configured appropriately as a
delivering plant in SD customizing.
 It is possible that a Plant in one company code may have transaction with sales organization in
another company code within same client. This is known as *cross company sales.
 Plant & Storage location are organizational units that can be used by all logistic area in the
system.
DELIVERING PLANT
 For a plant to be a Delivering Plant, following are essential, i.e,
 A plant is referred as delivering plant, when the said plant is assigned to a combination
of Sales Organization & Distribution Channel.
 Plant should be uniquely assigned to a company code.
 Plant should also be assigned to sales organization & distribution channel.
 During sales process, the Delivering Plant is first used to verify stock (availability check)
& later to supply the goods the customer has ordered.
 Only if plant is a Delivering Plant, a shipping point can be assigned to a plant. Material
cannot be despatched without a shipping point.
SHIPPING POINT
 The Shipping Point is highest level organizational unit of shipping that controls shipping
activities.
 Material can enter or leave the premises of an organization through Shipping Point.
 System determines Shipping Point on the bases of Delivering Plant, Shipping Condition
from Sold to Party & Loading Group from material master.
 The transaction code OVL3 is used to maintain the determination of shipping point
 Shipping Point can be changed manually, only if it is in close proximity & relevant changes
are permitted by the system in customizing setting.
 Each outbound delivery is processed by only one Shipping Point . For example, Loading
ramp, mail depot, rail depot, group of employees, etc.
 Shipping Point is assigned to a plant.
 Shipping Point is a physical place & should be near delivering plant.
 Shipping Point can be assigned to more than one plant & a plant can also have more than
one shipping point. Assignment between plant & shipping point is not unique.
WAREHOUSE
 For efficient processing of goods receipt & goods issue, Warehouse is made up of:
 Warehouse number: The entire warehouse structure is managed under one warehouse
number.
 Storage type: The different warehouse area, which differ with respect to their
organizational & technical features, are defined as storage types.
 Picking area: The picking area groups storage bins together in the storage type.
 Staging area: The staging area is an area in the warehouse where the goods are stored
immediately after unloading or shortly before loading.
 Doors: A door within a warehouse can be used both for inbound delivery as well as
outbound delivery of goods.
For Sales & Distribution, Lean Warehouses are applicable. This b'coz lean warehouse
have fixed bins as storage type.
SALES OFFICE
 Sales Office is organizational unit responsible for sales & distribution, within geographical
area.
 Sales Office establishes contact between company & customer.
 Sales Office can be assigned to one or more sales area.
 A Sales Office can be sub divided into several sales groups.
SALES GROUP
 Sales Group is an organizational unit that carries out sales & is responsible for the process
internally.
 Sales Group can be assigned to one or more sales office.
SALES PERSON
 A sales group consists of certain number of Sales Person.
 A Sales Person is assigned to a sales office & sales group in the sales employee record.
COMBINATION
  1 CLIENT /COMPANY : N COMPANY CODES
  1 COMAPNY CODE : N PLANTS
  1 PLANT : N STORAGE LOCATION
PURCHASING ORGANIZATION
 1 . STANDARD PURCHASING ORGANIZATION
 2. REFERENCE PURCHASING ORGANIZATION –OUTLINE AGREEMNTS
 CENTRAL PURCHASING ORGANIZATION - ALL COMPANY CODES , PLANTS
 PLANT SPECFIC PURCHASING ORGANIZATION
 COMPANY CODE SPECIFIC PURCHASING ORGANIZATION
Two roles sap – consultant , user
 Consultant – spro
 User – easy access screen
SPRO
TR ORGANIZER
SE09
SPRO
 SPRO SAP REFRENCE IMG Enterprise Structure Logistics – General
Define valuation level
SAP MM Master data
 Material master
 Vendor master
 Purchase info record - MM/VM /pur org
 Source list - vm/ mm/ plant
 Quota arrangement – vm/ mm / plant / mrp grp
SAP MM OBJECTS
 Release procedure – work flow (approve) – pr / po / ses / oa
 Pricing procedure – p org, vm, calculation schema – condition-based
determination
 Output management – po print out put / grn / ir / inventory docs
 Automatic account determination - MM – FI
Sap doc types
 Rfq doc type – AN
 Purchase requisition doc type – NB
 Purchase order doc types – NB, FO , UB
 GR – WE / WA
 IR – RE / RA
SAP PTP – CYCLE
 REQUIREMENT – PR - ME51N / ME52N /ME53N
 RFQ – PRICE - ME41/ ME42 / ME43
 MAINTAIN QUOTATION - ME47
 ME49 – PRICE COMPARIOSN LIST
 PO – RFQ / PR - ME21N / ME22N /ME23N
 GR - MIGO – GR
 IR – MIRO
 VENDOR PAYMENT
Procure to Pay Cycle
 Determination of requirements - PR from Stores and other departments - ME51N
 Source determination – RFQ to vendors or Supplier or Manufacturers - ME41N
 Price Comparison - Quotations selections wrt Price /qty/quality / delivery time - ME47 / ME49
 Purchase Order processing - Create PO wrt to Selected Vendor – ME21N
 Order management / po follow ups - Delivery schedules
 Goods Receipt (GR) from Vendor or supplier – MIGO
Accounting entry -
Stock A/c debt + 10 (qty) – BSX (Business transaction event key)
GR/IR Clearing A/c Credit – 10 (qty/val)- WRX (Business transaction event key)
 Invoice Receipt (IR) to Vendor - MIRO
Accounting entry-
GR/IR Clearing A/c Debit + 10*100=1000 qty (qty/val)- WRX (Business transaction event key)
Vendor A/c Credit (value) -10*100=1000 value – KBS -(Business transaction event key)
Create Material – MM01
Create Purchase order – ME21N
MIGO – Goods Receipt
MIGO – Accounting entries
Purchase order history
Incoming Invoice Receipt - MIRO
Accounting entries at MIRO
INVENTROY
MANAGEMENT
Plant Parameters
GR /GI – Doc types & number
ranges
Reporting
All the activities for managing inventory in storage area i.e. Goods Receipt, Goods Issue, Internal Transfer
(Material movements), Reservations
LIV –
LOGISTICS
INVOICE
VERIFICATION
Invoice doc types
Number ranges
reporting
All activities related to invoicing process i.e. Invoice Receipt from Vendor, Automatic Invoice, Direct posting
for material
By Lokesh Modem
THANKS

Más contenido relacionado

La actualidad más candente

Sap sd quest_answer_2009061511245119496
Sap sd quest_answer_2009061511245119496Sap sd quest_answer_2009061511245119496
Sap sd quest_answer_2009061511245119496
Jitender Dalal
 
STO process with config 4th method
STO process with config 4th methodSTO process with config 4th method
STO process with config 4th method
Mohammed Azhad
 
411226987-SAP-MM-Implementation-Project (1).pdf
411226987-SAP-MM-Implementation-Project (1).pdf411226987-SAP-MM-Implementation-Project (1).pdf
411226987-SAP-MM-Implementation-Project (1).pdf
SekarbaluChandru
 
Automatic batch determination based on shelf life
Automatic batch determination based on shelf lifeAutomatic batch determination based on shelf life
Automatic batch determination based on shelf life
Mauricio Beltran
 

La actualidad más candente (20)

SAP D Enterprise Structure
SAP D Enterprise StructureSAP D Enterprise Structure
SAP D Enterprise Structure
 
SAP SD Configuration Document
SAP SD Configuration DocumentSAP SD Configuration Document
SAP SD Configuration Document
 
S4 HANA Business Partner Configuration@Ganesh Tarlana
S4 HANA Business Partner Configuration@Ganesh TarlanaS4 HANA Business Partner Configuration@Ganesh Tarlana
S4 HANA Business Partner Configuration@Ganesh Tarlana
 
SAP MM Business Scenarios
SAP MM  Business ScenariosSAP MM  Business Scenarios
SAP MM Business Scenarios
 
Variant Configuration Overview
Variant  Configuration  OverviewVariant  Configuration  Overview
Variant Configuration Overview
 
Rollout solution template SAP SD
Rollout solution template   SAP SDRollout solution template   SAP SD
Rollout solution template SAP SD
 
SAP SD Business Blue Print E1 Sales Template
SAP SD Business Blue Print E1 Sales TemplateSAP SD Business Blue Print E1 Sales Template
SAP SD Business Blue Print E1 Sales Template
 
SAP Enterprise Structure-Reflect Your Business
SAP Enterprise Structure-Reflect Your BusinessSAP Enterprise Structure-Reflect Your Business
SAP Enterprise Structure-Reflect Your Business
 
Make to order document
Make to order document Make to order document
Make to order document
 
Sap sd material
Sap sd materialSap sd material
Sap sd material
 
Sap sd quest_answer_2009061511245119496
Sap sd quest_answer_2009061511245119496Sap sd quest_answer_2009061511245119496
Sap sd quest_answer_2009061511245119496
 
Org structure SAP
Org structure SAPOrg structure SAP
Org structure SAP
 
Pricing soloution in sap retail
Pricing soloution in sap retailPricing soloution in sap retail
Pricing soloution in sap retail
 
Transfer of requirements in SAP SD
Transfer of requirements in SAP SDTransfer of requirements in SAP SD
Transfer of requirements in SAP SD
 
STO process with config 4th method
STO process with config 4th methodSTO process with config 4th method
STO process with config 4th method
 
411226987-SAP-MM-Implementation-Project (1).pdf
411226987-SAP-MM-Implementation-Project (1).pdf411226987-SAP-MM-Implementation-Project (1).pdf
411226987-SAP-MM-Implementation-Project (1).pdf
 
Sap configuration-guide
Sap configuration-guideSap configuration-guide
Sap configuration-guide
 
Sap sd tutorial
Sap sd tutorialSap sd tutorial
Sap sd tutorial
 
Automatic batch determination based on shelf life
Automatic batch determination based on shelf lifeAutomatic batch determination based on shelf life
Automatic batch determination based on shelf life
 
SAP EWM TRAINING
SAP EWM TRAININGSAP EWM TRAINING
SAP EWM TRAINING
 

Similar a Sap mm by lokesh modem

Sap Sd Sample Questions
Sap Sd Sample QuestionsSap Sd Sample Questions
Sap Sd Sample Questions
raheemkhan4u
 
Sap sd quest_answer_20090615
Sap sd quest_answer_20090615Sap sd quest_answer_20090615
Sap sd quest_answer_20090615
Prateek Agarwal
 
Sappowerpointpresentationdownloadfrom 120302002505-phpapp01
Sappowerpointpresentationdownloadfrom 120302002505-phpapp01Sappowerpointpresentationdownloadfrom 120302002505-phpapp01
Sappowerpointpresentationdownloadfrom 120302002505-phpapp01
myrndinfodavid
 

Similar a Sap mm by lokesh modem (20)

Sap sd question
Sap sd questionSap sd question
Sap sd question
 
Sap sd question
Sap sd questionSap sd question
Sap sd question
 
SAP SD interview questions
SAP SD interview questions SAP SD interview questions
SAP SD interview questions
 
Sap sd material1
Sap sd material1Sap sd material1
Sap sd material1
 
Sap Sd Sample Questions
Sap Sd Sample QuestionsSap Sd Sample Questions
Sap Sd Sample Questions
 
SAP Organization Structure V1.2.ppt
SAP Organization Structure V1.2.pptSAP Organization Structure V1.2.ppt
SAP Organization Structure V1.2.ppt
 
SD-Domain Overview.ppt
SD-Domain Overview.pptSD-Domain Overview.ppt
SD-Domain Overview.ppt
 
sd-domainoverview-231023124548-9a3b885e.pdf
sd-domainoverview-231023124548-9a3b885e.pdfsd-domainoverview-231023124548-9a3b885e.pdf
sd-domainoverview-231023124548-9a3b885e.pdf
 
SAP Organization Structure
SAP Organization StructureSAP Organization Structure
SAP Organization Structure
 
Sap sd quest_answer_20090615
Sap sd quest_answer_20090615Sap sd quest_answer_20090615
Sap sd quest_answer_20090615
 
Procurement process
Procurement processProcurement process
Procurement process
 
SAP IS Retail Introduction.pptx
SAP IS Retail Introduction.pptxSAP IS Retail Introduction.pptx
SAP IS Retail Introduction.pptx
 
Sd
SdSd
Sd
 
207828627 sap-bootcamp-quiz-sd
207828627 sap-bootcamp-quiz-sd207828627 sap-bootcamp-quiz-sd
207828627 sap-bootcamp-quiz-sd
 
Industry Focus: Optical Retail
Industry Focus: Optical RetailIndustry Focus: Optical Retail
Industry Focus: Optical Retail
 
Sales & distribution training overview
Sales & distribution training overviewSales & distribution training overview
Sales & distribution training overview
 
Zed-Sales™ - Channel Sales & Distribution Management System by Zed Axis Techn...
Zed-Sales™ - Channel Sales & Distribution Management System by Zed Axis Techn...Zed-Sales™ - Channel Sales & Distribution Management System by Zed Axis Techn...
Zed-Sales™ - Channel Sales & Distribution Management System by Zed Axis Techn...
 
Ppts of odoo
Ppts of odooPpts of odoo
Ppts of odoo
 
SAP Material Managament Class 1 Sample
SAP Material Managament  Class 1 SampleSAP Material Managament  Class 1 Sample
SAP Material Managament Class 1 Sample
 
Sappowerpointpresentationdownloadfrom 120302002505-phpapp01
Sappowerpointpresentationdownloadfrom 120302002505-phpapp01Sappowerpointpresentationdownloadfrom 120302002505-phpapp01
Sappowerpointpresentationdownloadfrom 120302002505-phpapp01
 

Más de Lokesh Modem

Más de Lokesh Modem (20)

Variant configuration.docx
Variant configuration.docxVariant configuration.docx
Variant configuration.docx
 
SAP S4 HANA SOURCING AND PROCUREMENT CONTENT.docx
SAP S4 HANA SOURCING AND PROCUREMENT CONTENT.docxSAP S4 HANA SOURCING AND PROCUREMENT CONTENT.docx
SAP S4 HANA SOURCING AND PROCUREMENT CONTENT.docx
 
Fiori Apps Library.pdf
Fiori Apps Library.pdfFiori Apps Library.pdf
Fiori Apps Library.pdf
 
Material Ledger Configuration.doc
Material Ledger Configuration.docMaterial Ledger Configuration.doc
Material Ledger Configuration.doc
 
SAP S4 HANA.docx
SAP S4 HANA.docxSAP S4 HANA.docx
SAP S4 HANA.docx
 
What is Cost of Goods Sold.doc
What is Cost of Goods Sold.docWhat is Cost of Goods Sold.doc
What is Cost of Goods Sold.doc
 
FSD_Stock aging Report Based On consumption.doc
FSD_Stock aging Report Based On consumption.docFSD_Stock aging Report Based On consumption.doc
FSD_Stock aging Report Based On consumption.doc
 
Sap pp org
Sap pp orgSap pp org
Sap pp org
 
SAP Solution Manger 7.2
SAP Solution Manger 7.2SAP Solution Manger 7.2
SAP Solution Manger 7.2
 
E invoice webinar_jan2020_v2
E invoice webinar_jan2020_v2E invoice webinar_jan2020_v2
E invoice webinar_jan2020_v2
 
Gst digital compliance roadmap jan2010 v1
Gst digital compliance roadmap jan2010 v1Gst digital compliance roadmap jan2010 v1
Gst digital compliance roadmap jan2010 v1
 
SAP Third party scenarios _automatives
SAP Third party scenarios _automatives SAP Third party scenarios _automatives
SAP Third party scenarios _automatives
 
Fsd for mass upload program to create and change of scheduling agreement
Fsd for mass upload program to create and change of scheduling agreementFsd for mass upload program to create and change of scheduling agreement
Fsd for mass upload program to create and change of scheduling agreement
 
Pir price updation in SCHEDULLING AGREEMENT
Pir price updation in SCHEDULLING AGREEMENTPir price updation in SCHEDULLING AGREEMENT
Pir price updation in SCHEDULLING AGREEMENT
 
Fsd zpriz price details from a017 & a018
Fsd zpriz price details from a017 & a018Fsd zpriz price details from a017 & a018
Fsd zpriz price details from a017 & a018
 
Fsd for upload program for delivery completion indicator of scheduling agreem...
Fsd for upload program for delivery completion indicator of scheduling agreem...Fsd for upload program for delivery completion indicator of scheduling agreem...
Fsd for upload program for delivery completion indicator of scheduling agreem...
 
Guidelines for xl_filling
Guidelines for xl_fillingGuidelines for xl_filling
Guidelines for xl_filling
 
Gst e way bill solution from sap
Gst e way bill solution from sapGst e way bill solution from sap
Gst e way bill solution from sap
 
Transaction code creation
Transaction code creationTransaction code creation
Transaction code creation
 
Program text elements
Program text elementsProgram text elements
Program text elements
 

Último

+971565801893>>SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHAB...
+971565801893>>SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHAB...+971565801893>>SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHAB...
+971565801893>>SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHAB...
Health
 
TECUNIQUE: Success Stories: IT Service provider
TECUNIQUE: Success Stories: IT Service providerTECUNIQUE: Success Stories: IT Service provider
TECUNIQUE: Success Stories: IT Service provider
mohitmore19
 

Último (20)

Introducing Microsoft’s new Enterprise Work Management (EWM) Solution
Introducing Microsoft’s new Enterprise Work Management (EWM) SolutionIntroducing Microsoft’s new Enterprise Work Management (EWM) Solution
Introducing Microsoft’s new Enterprise Work Management (EWM) Solution
 
Chinsurah Escorts ☎️8617697112 Starting From 5K to 15K High Profile Escorts ...
Chinsurah Escorts ☎️8617697112  Starting From 5K to 15K High Profile Escorts ...Chinsurah Escorts ☎️8617697112  Starting From 5K to 15K High Profile Escorts ...
Chinsurah Escorts ☎️8617697112 Starting From 5K to 15K High Profile Escorts ...
 
Azure_Native_Qumulo_High_Performance_Compute_Benchmarks.pdf
Azure_Native_Qumulo_High_Performance_Compute_Benchmarks.pdfAzure_Native_Qumulo_High_Performance_Compute_Benchmarks.pdf
Azure_Native_Qumulo_High_Performance_Compute_Benchmarks.pdf
 
%in Stilfontein+277-882-255-28 abortion pills for sale in Stilfontein
%in Stilfontein+277-882-255-28 abortion pills for sale in Stilfontein%in Stilfontein+277-882-255-28 abortion pills for sale in Stilfontein
%in Stilfontein+277-882-255-28 abortion pills for sale in Stilfontein
 
%in Bahrain+277-882-255-28 abortion pills for sale in Bahrain
%in Bahrain+277-882-255-28 abortion pills for sale in Bahrain%in Bahrain+277-882-255-28 abortion pills for sale in Bahrain
%in Bahrain+277-882-255-28 abortion pills for sale in Bahrain
 
LEVEL 5 - SESSION 1 2023 (1).pptx - PDF 123456
LEVEL 5   - SESSION 1 2023 (1).pptx - PDF 123456LEVEL 5   - SESSION 1 2023 (1).pptx - PDF 123456
LEVEL 5 - SESSION 1 2023 (1).pptx - PDF 123456
 
BUS PASS MANGEMENT SYSTEM USING PHP.pptx
BUS PASS MANGEMENT SYSTEM USING PHP.pptxBUS PASS MANGEMENT SYSTEM USING PHP.pptx
BUS PASS MANGEMENT SYSTEM USING PHP.pptx
 
W01_panagenda_Navigating-the-Future-with-The-Hitchhikers-Guide-to-Notes-and-D...
W01_panagenda_Navigating-the-Future-with-The-Hitchhikers-Guide-to-Notes-and-D...W01_panagenda_Navigating-the-Future-with-The-Hitchhikers-Guide-to-Notes-and-D...
W01_panagenda_Navigating-the-Future-with-The-Hitchhikers-Guide-to-Notes-and-D...
 
+971565801893>>SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHAB...
+971565801893>>SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHAB...+971565801893>>SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHAB...
+971565801893>>SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHAB...
 
The Guide to Integrating Generative AI into Unified Continuous Testing Platfo...
The Guide to Integrating Generative AI into Unified Continuous Testing Platfo...The Guide to Integrating Generative AI into Unified Continuous Testing Platfo...
The Guide to Integrating Generative AI into Unified Continuous Testing Platfo...
 
10 Trends Likely to Shape Enterprise Technology in 2024
10 Trends Likely to Shape Enterprise Technology in 202410 Trends Likely to Shape Enterprise Technology in 2024
10 Trends Likely to Shape Enterprise Technology in 2024
 
call girls in Vaishali (Ghaziabad) 🔝 >༒8448380779 🔝 genuine Escort Service 🔝✔️✔️
call girls in Vaishali (Ghaziabad) 🔝 >༒8448380779 🔝 genuine Escort Service 🔝✔️✔️call girls in Vaishali (Ghaziabad) 🔝 >༒8448380779 🔝 genuine Escort Service 🔝✔️✔️
call girls in Vaishali (Ghaziabad) 🔝 >༒8448380779 🔝 genuine Escort Service 🔝✔️✔️
 
Software Quality Assurance Interview Questions
Software Quality Assurance Interview QuestionsSoftware Quality Assurance Interview Questions
Software Quality Assurance Interview Questions
 
TECUNIQUE: Success Stories: IT Service provider
TECUNIQUE: Success Stories: IT Service providerTECUNIQUE: Success Stories: IT Service provider
TECUNIQUE: Success Stories: IT Service provider
 
%in kaalfontein+277-882-255-28 abortion pills for sale in kaalfontein
%in kaalfontein+277-882-255-28 abortion pills for sale in kaalfontein%in kaalfontein+277-882-255-28 abortion pills for sale in kaalfontein
%in kaalfontein+277-882-255-28 abortion pills for sale in kaalfontein
 
HR Software Buyers Guide in 2024 - HRSoftware.com
HR Software Buyers Guide in 2024 - HRSoftware.comHR Software Buyers Guide in 2024 - HRSoftware.com
HR Software Buyers Guide in 2024 - HRSoftware.com
 
ManageIQ - Sprint 236 Review - Slide Deck
ManageIQ - Sprint 236 Review - Slide DeckManageIQ - Sprint 236 Review - Slide Deck
ManageIQ - Sprint 236 Review - Slide Deck
 
Learn the Fundamentals of XCUITest Framework_ A Beginner's Guide.pdf
Learn the Fundamentals of XCUITest Framework_ A Beginner's Guide.pdfLearn the Fundamentals of XCUITest Framework_ A Beginner's Guide.pdf
Learn the Fundamentals of XCUITest Framework_ A Beginner's Guide.pdf
 
VTU technical seminar 8Th Sem on Scikit-learn
VTU technical seminar 8Th Sem on Scikit-learnVTU technical seminar 8Th Sem on Scikit-learn
VTU technical seminar 8Th Sem on Scikit-learn
 
Payment Gateway Testing Simplified_ A Step-by-Step Guide for Beginners.pdf
Payment Gateway Testing Simplified_ A Step-by-Step Guide for Beginners.pdfPayment Gateway Testing Simplified_ A Step-by-Step Guide for Beginners.pdf
Payment Gateway Testing Simplified_ A Step-by-Step Guide for Beginners.pdf
 

Sap mm by lokesh modem

  • 1. SAP ECC ERP - MM By Lokesh Modem
  • 2. SAP LANDSCAPE  DEVELOPMENT – CLIENT  QUALITY –CLIENT  PRD –CLIENT  SANDBOX- Testing DEV QTY PRD
  • 3. SAP Projects  GREEN FIELDS – NEW IMPLEMENTATION  BROWN FIELD – MIGRATION  SAP S4 HANA CONVERSION – ECC TO S/4 HANA CONVERSION  ROLL-OUT Project  Enhancement project - W-WORKFLOW , R-REPORT I-INTERFACES C-CONVERSION , E – ENHACEMENT F-FORM  Technical upgradation – EHP 6 TO EHP 7 OR EHP 8
  • 4. SAP Implementation – ASAP Methodology  1 . Project preparation - 2months  2. Business blueprint documentation -3months AS IS , TO BE , E2E , Requirement gathering , GAP analysis  3. Realization – Functional – Designing & Developing of business scenarios  4. Final preparation – Cut over , open po, ISU-561 , QTY – UAT , USER TRAINING , USER MANUALS , CONFIG DOC,  5. GO LIVE & SUPPORT
  • 5. SAP MODULES  SAP TECHNICAL - ABAP PI PO BASIS  SAP FUCNTIONAL – MM PP PM QM WM FI CO SD  MASTER DATA  TRANSACTION DATA  DATA WILL BE SETTLED IN TABLES
  • 6. SAP Organization structure  Client or Company - WIPRO GROUP  COMPANY CODE - WIPRO E-OIL , SOAP , ELECTRICAL LIGHTS , IT , INFOTECH  CONTROLLING ORG – COSTING  PLANT -- PURCHASING ORG -- SAL ORG  SALES AREA, DIVISION , DISTRIBUTION CHANNEL  STORAGE LOCATION  WM  STORAGE TYPE  STORAGE SECTION  STORAGE BIN  QUANT - RACK ARRANGEMENT
  • 7. CLIENT  A client is an independent organizational unit.  A client is considered synonym for a group.  A client is self-contained technical unit.  General data & tables used for several organization structure are stored at client level.  Client is positioned in the highest level in Enterprise Structure.  Several company code can be uniquely assigned to a client.
  • 8. COMPANY CODE  A Company Code is a legal entity & independent accounting unit.  Balance Sheet & Profit & loss account are created at Company Code level.  Company Code is organizational unit prepared by FI.  Several Company Code can be uniquely assigned to a Client.  Several Company Code under same client can have same chart of accounts.
  • 9. SALES ORGANIZATION  Sales Organization is an organizational unit of Logistics, which groups the enterprise according to the requirement of Sales & Distribution.  Sales Organization distributes goods & services.  Sales Organization is liable for sold products, responsible for the customers right of recourse & negotiating sales condition.  One or more Sales Organization can be uniquely assigned to a Company Code.  Sales Organization can be assigned to one or more plant. This assignment is not unique, so several Sales Organizations can also be assigned to one plant.  Each Sales Organization has its own master data, for eg customer & material master data, as well as conditions, pricing & output type.  A Sales Organization is the highest level (after the Client) to which sales figure are summed for SD with statistics currency.  Sales Organization can be used as selection criteria for listing of sales document, as well as for creating delivery & billing worklist.  Different output type can be defined for sales & billing document, for each Sales Organization.  Sales Organization is also used to take regional, national, international sub-division of the market into account.
  • 10. DISTRIBUTION CHANNEL  A Distribution Channel is a mean through which saleable material or services reach the customer.  A Distribution Channel represents the strategies to distribute goods and / or services to the customers. Eg: wholesale, retail, institutional, etc.  Distribution Channel can be assigned to one or more Sales Organization.  Same customer can be served through one or more Distribution Channel, within a Sales Organization.  Distribution Channel can be set as per company's marketing strategies or internal organization.  Master data can vary (Customer & material Master data, Prices, discounts / surcharge, output type, etc) for each Sales Organization & Distribution Channel, i.e, within Distribution Channel master data can be defined separately.  Master data created for one Distribution Channel can also be used in other Distribution Channel.  Different sales document type can be defined for Distribution Channel.  Sales Office can be assigned to Distribution Channel.  Items in a delivery & billing documents can belong to different Distribution Channel.  Distribution Channel can be used as selection criteria for creating lists
  • 11. DIVISION  Division represents a product line or grouping of materials or services.  Division can be assigned to one or more sales organization.  Division can be assigned to one or more distribution channels.  Material always belongs to only one Division.  Master data can vary from Division to Division.  Different Division can share same master data, if shared master data is created.  Sales Office can be assigned to Division .  In sales document type, if Item Division is not activated, it will accept material from the Division at header level only & if material at item level is from different Division from header level, the same is not accepted.  Item in delivery or billing can belong to different Division.  Division can be used as selection criteria in sales document & also for creating delivery worklist.  Different output type can be used for printing sales document for each Division.
  • 12. SALES AREA  Sales Area is made up of combination of Sales Organization, Distribution Channel & Division.  It defines the distribution channel a sales organization uses to sell products from a certain division.  A Sales Area belongs to only one Company Code.  During the processing of SD documents, system accesses various master data, according to Sales Area. The system also carries out various checks concerning the validity of certain entries according to Sales Area.  Sales document, delivery document & billing document is always assigned to Sales Area.  Each SD document is assigned to exactly only one Sales Area. This assignment cannot be changed.  Various analyses can be carried out within Sales Area. So, Organization structure should be as simple as possible.  Sales Area is used for reporting & pricing.  The customer data record contains pages (views) with the data that is specific to Sales Area.
  • 13. PLANT & STORAGE LOCATION  In SD, a Plant represents the location from which material & services are distributed & correspond to a distribution center. Which is also known as Delivering Plant. The relevant stocks are kept here.  In SD, the Plant has a central function:  At least one Plant is necessary in order to be able to use SD module.  A Plant is uniquely assigned to a Company code.  Assignment between Sales organization & Plant is not unique.  Delivering Plant is important for determining shipping point.  For a Plant to deliver goods to the customers, it must be configured appropriately as a delivering plant in SD customizing.  It is possible that a Plant in one company code may have transaction with sales organization in another company code within same client. This is known as *cross company sales.  Plant & Storage location are organizational units that can be used by all logistic area in the system.
  • 14. DELIVERING PLANT  For a plant to be a Delivering Plant, following are essential, i.e,  A plant is referred as delivering plant, when the said plant is assigned to a combination of Sales Organization & Distribution Channel.  Plant should be uniquely assigned to a company code.  Plant should also be assigned to sales organization & distribution channel.  During sales process, the Delivering Plant is first used to verify stock (availability check) & later to supply the goods the customer has ordered.  Only if plant is a Delivering Plant, a shipping point can be assigned to a plant. Material cannot be despatched without a shipping point.
  • 15. SHIPPING POINT  The Shipping Point is highest level organizational unit of shipping that controls shipping activities.  Material can enter or leave the premises of an organization through Shipping Point.  System determines Shipping Point on the bases of Delivering Plant, Shipping Condition from Sold to Party & Loading Group from material master.  The transaction code OVL3 is used to maintain the determination of shipping point  Shipping Point can be changed manually, only if it is in close proximity & relevant changes are permitted by the system in customizing setting.  Each outbound delivery is processed by only one Shipping Point . For example, Loading ramp, mail depot, rail depot, group of employees, etc.  Shipping Point is assigned to a plant.  Shipping Point is a physical place & should be near delivering plant.  Shipping Point can be assigned to more than one plant & a plant can also have more than one shipping point. Assignment between plant & shipping point is not unique.
  • 16. WAREHOUSE  For efficient processing of goods receipt & goods issue, Warehouse is made up of:  Warehouse number: The entire warehouse structure is managed under one warehouse number.  Storage type: The different warehouse area, which differ with respect to their organizational & technical features, are defined as storage types.  Picking area: The picking area groups storage bins together in the storage type.  Staging area: The staging area is an area in the warehouse where the goods are stored immediately after unloading or shortly before loading.  Doors: A door within a warehouse can be used both for inbound delivery as well as outbound delivery of goods. For Sales & Distribution, Lean Warehouses are applicable. This b'coz lean warehouse have fixed bins as storage type.
  • 17. SALES OFFICE  Sales Office is organizational unit responsible for sales & distribution, within geographical area.  Sales Office establishes contact between company & customer.  Sales Office can be assigned to one or more sales area.  A Sales Office can be sub divided into several sales groups. SALES GROUP  Sales Group is an organizational unit that carries out sales & is responsible for the process internally.  Sales Group can be assigned to one or more sales office. SALES PERSON  A sales group consists of certain number of Sales Person.  A Sales Person is assigned to a sales office & sales group in the sales employee record.
  • 18. COMBINATION   1 CLIENT /COMPANY : N COMPANY CODES   1 COMAPNY CODE : N PLANTS   1 PLANT : N STORAGE LOCATION PURCHASING ORGANIZATION  1 . STANDARD PURCHASING ORGANIZATION  2. REFERENCE PURCHASING ORGANIZATION –OUTLINE AGREEMNTS  CENTRAL PURCHASING ORGANIZATION - ALL COMPANY CODES , PLANTS  PLANT SPECFIC PURCHASING ORGANIZATION  COMPANY CODE SPECIFIC PURCHASING ORGANIZATION
  • 19. Two roles sap – consultant , user  Consultant – spro  User – easy access screen
  • 20. SPRO
  • 22. SPRO  SPRO SAP REFRENCE IMG Enterprise Structure Logistics – General Define valuation level
  • 23. SAP MM Master data  Material master  Vendor master  Purchase info record - MM/VM /pur org  Source list - vm/ mm/ plant  Quota arrangement – vm/ mm / plant / mrp grp
  • 24. SAP MM OBJECTS  Release procedure – work flow (approve) – pr / po / ses / oa  Pricing procedure – p org, vm, calculation schema – condition-based determination  Output management – po print out put / grn / ir / inventory docs  Automatic account determination - MM – FI
  • 25. Sap doc types  Rfq doc type – AN  Purchase requisition doc type – NB  Purchase order doc types – NB, FO , UB  GR – WE / WA  IR – RE / RA
  • 26. SAP PTP – CYCLE  REQUIREMENT – PR - ME51N / ME52N /ME53N  RFQ – PRICE - ME41/ ME42 / ME43  MAINTAIN QUOTATION - ME47  ME49 – PRICE COMPARIOSN LIST  PO – RFQ / PR - ME21N / ME22N /ME23N  GR - MIGO – GR  IR – MIRO  VENDOR PAYMENT
  • 27. Procure to Pay Cycle  Determination of requirements - PR from Stores and other departments - ME51N  Source determination – RFQ to vendors or Supplier or Manufacturers - ME41N  Price Comparison - Quotations selections wrt Price /qty/quality / delivery time - ME47 / ME49  Purchase Order processing - Create PO wrt to Selected Vendor – ME21N  Order management / po follow ups - Delivery schedules  Goods Receipt (GR) from Vendor or supplier – MIGO Accounting entry - Stock A/c debt + 10 (qty) – BSX (Business transaction event key) GR/IR Clearing A/c Credit – 10 (qty/val)- WRX (Business transaction event key)  Invoice Receipt (IR) to Vendor - MIRO Accounting entry- GR/IR Clearing A/c Debit + 10*100=1000 qty (qty/val)- WRX (Business transaction event key) Vendor A/c Credit (value) -10*100=1000 value – KBS -(Business transaction event key)
  • 30. MIGO – Goods Receipt
  • 35. INVENTROY MANAGEMENT Plant Parameters GR /GI – Doc types & number ranges Reporting All the activities for managing inventory in storage area i.e. Goods Receipt, Goods Issue, Internal Transfer (Material movements), Reservations
  • 36. LIV – LOGISTICS INVOICE VERIFICATION Invoice doc types Number ranges reporting All activities related to invoicing process i.e. Invoice Receipt from Vendor, Automatic Invoice, Direct posting for material