Physical Process in MM [SAP Journey videos]

 Basic Procurement/Purchase cycle

 Purchase Requisition: If some material in production line is not available or due to some part
damage machine is not working due to which whole production line has stopped. Then the
following steps shall be taken

 The worker will inform the supervisor

 The supervisor will fill in the purchase requisition slip with details of requirement and sign it

 Supervisor will get it signed from Production head and return the slip to the worker and ask
him to collect the required material from store or warehouse

 Worker will submit the slip to store clerk. Clerk will check if the material is available in the
stores or warehouse

 If material is in stock, the clerk of store or warehouse department will issue good to the
worker. This is updated in SAP system and overall stock is updated

 Worker then replaces the part and the production line is online again

 If material is not in stock, the clerk of stores will generate an indent and inform the Purchase
dept of deficit of the material and request for particular goods. Simultaneously, the store
dept will check minimum level of other material quantities and create indent for them as
well, if required

 Goods requisition slip will be generated by goods/store dept and sent to purchase dept.
Purchase department will check for approved vendor list in SAP. If the supplier is new, we
will have to do registration of new vendor (i.e. creation of new vendor XK01)

 Then enquiry or RFQ is sent to vendors via SAP, to which vendors will send quotation
through mail or other means. This quotation is updated in SAP by the Purchase dept

 Purchase dept will then compare quotations of quotations received from vendors. Purchase
dept will request for samples from specific vendors accordingly, if required. The part which
is found proper is finalized or approved by the dept which requires the part

 Then, purchase order for that part or material is placed for that specific vendor

 Goods sent by vendor is received at company premises

 These goods are then received by the store dept which checks whether the material being
received is according to the purchase order or not

 Then material is sent to quality dept for checks

  Finally an MR (Material receipt) is generated which is signed by store dept, HOD of the dept
which requires the material

 If rejected by HOD for some reason, material will be returned to the vendor

 If approved by HOD, material is issued to that dept by store dept

 Store dept then checks PO, MR and bill details and gets it signed by GM and sends it to the
accounts dept

 Accounts dept then processes the documents and Invoice receipt is done and payment is
made to vendor through SAP

 Basic Procurement cycle if material not available in stores is as below

 PR created using TC ME51N

 RFQ created using TC ME41

 Quotation created and compared using TC ME47 and ME49

 Finalize vendor using TC ME47

 Create PO using TC ME21N for the approved vendor

 PO has to be then released through authorized personnel

 Goods receipt using TC MIGO

 Invoice verification using TC MIRO

SAP R/3 Architecture [SAP journey video]

 R represents real time and 3 represents 3 tier or three layer architecture comprising of a.
Presentation layer b. Application layer and c. Database layer

 Presentation layer is used by SAP End user, Customers and Vendors

 Application layer is used by SAP Consultants

 Database layer is used by SAP hardware and BASIS team

 All the three layers are inter connected with each other by means of Internet Connection
Manager
  There are various work process to which different jobs or processes or transactions in SAP are
assigned [Transaction code SM50 is used to check which processes have been worked on i.e.
Process overview]

 Dialog Work process – These are used for running short running commands or
transactions like MMBE, etc

 Background work process – Used for running large programs like updating salaries of all
employees

 Update work process – Used for updating existing master data using TC
MM02/XK02/ME12 etc

 Spool work process – Used for taking printout of any documents

 Enqueue work process – Used for limiting or restricting access to various users

SAP Installation and login [https://www.youtube.com/watch?v=8z0n1quoGYw&t=13s]

 Install and enter relevant data such as IP address, etc for a specific client

 One can add as many clients as desired. These clients can be modified, deleted, etc

 For logging in on a specific client, select the client and enter user id and password to do so

 Based on client login parameters, a default client number will appear on login screen

 RZ10 – Use to edit client profiles such as client number. Below is the screenshot for the same
[https://www.youtube.com/watch?v=fBhNrVJppfw] [8:00] [Not relevant to MM]

 It is used to change static and dynamic parameters. For static change server has to restarted and
for dynamic change server doesn’t need to be restarted

Types of projects in SAP [https://www.youtube.com/watch?v=F8wk7Wn6KjE&t=605s]

 Implementation – Requirements gathered and implemented for the first time

  Support/Maintenance – Issues resolved in the form of tickets internally/externally. Support
project always has a ticketing tool. Remedy and solution manager tool is a famous ticketing tool.
End user when faces a problem while using SAP, reports it to the support team through ticketing
tool. Support team gets notified and they resolve it. Every ticket has a priority or severity
(Low/Medium/High) based on which time to solve it will be decided or order of solving it will be
prioritized

 Up gradation – When client wants to upgrade to latest version of software. Up gradation gets
the work in the same way as in the implementation project. A lot of things already exist in
software and it only needs to be copy pasted. A few new things we have to implement from the
scratch which has not been implemented in the old version

 Roll-out: If a company has already implemented SAP for a geographical location (USA) for a
specific business and it wants implement the same business in some other geographical location
(Europe), then roll-out project is carried out. Reference of existing objects/data is taken of
implemented geographical location, so that work can be done faster

SAP System Landscape

 Development Sever – All configurations are done in this server. Only implementation partner
has access. Purchased by client, accessed by Implementation partner

 Quality Server - Testing is done in this server. Purchased by client, accessed by Implementation
partner

 Pre-production Server – This is an optional server used by client for testing. Purchased and
accessed by client

 Production Server – Only client has access. This the server on which client runs his/her business.
Purchased and accessed by client

 IDES Server – Also known as Sandbox testing. Purchased and accessed by implementation
partner for R&D purpose

 800 client only used in IDES

 100, 110, etc used in real-time servers

 Development server has multiple client(s) whereas production server has a single client

SAP Implementation stages [https://www.youtube.com/watch?v=lFNGZgJx-zQ]

 Project Preparation (AS-IS/TO-BE Document preparation) – Contract sign

 Implementation partner discusses the business processes with the client

  High level team of client will speak with team leads and project managers of
implementation partner

 Here business flow of the client will be understood

 Scope of project and resources required is also discussed

 This phase will run for 15-30 days

 People with 5-10 years of experience will be involved in this phase

 10-15 people from software company (Implementation partner) will go to client side for
discussion

 Business blueprint – Requirement gathering

 The purpose of this phase is to achieve a common understanding of how the company
intends to run SAP to support their business

 In Standard ASAP 8, it consists of detailed documentation of results gathered during project

preparation phase

 There is also Agile ASAP 8. In it, testing of what is done is done on regular basis. This is not
the case for standard ASAP, where testing is done at the end

 This phase runs for 30-60 days

 It involves people with 3-10 years of experience

 As-is and To-be & Gap analysis documents are prepared

 Blueprint is also prepared which mentions all the terms and conditions which is then signed
by the client

 Only when the client signs off, the only realization stage is started

 Realization – Customizing SAP based on business blueprint requirements

 The system configuration in standard ASAP is done in two work packages

i. Baseline configuration - Major scope

ii. Final configuration – Remaining scope

 In agile ASAP, work is divided, and testing is done after each work is done

 This phase will run for 3 to 6 months

 0-5 yrs experience people get involved in this phase

  Work flow: Business requirement exists Functional specification document (gives clear
idea on how a configuration has to be done Technical specification documents (For ABAP
and BI consultants) Buddy TestingUnit test planTransportDocumentation User
Acceptance Test

 After creation of functional specification by a team member, other team member will
approve it

 Buddy testing  A team member will check whether configuration done is proper or not

 Unit test plan  A document a functional consultant will hand over to the testing team,
which will be checked by the testing team and do the testing accordingly. The document will
also include screenshots of testing done in buddy testing. Here it will be checked, whether
for right input, right output id coming and similarly for wrong output relevant error message
is appearing i.e. both positive and negative test scenarios are checked. These positive and
negative test case scenarios have to be shown as screenshots in unit test plan

 Transport After unit testing, transportation moves all the developments or customizations
to the next server. [Servers available in system landscape is Development server, Quality
server and production server]

 After transportation, testing team approves it. Then documentation has to be prepared. It
gives details of which cubes a consultant has created or what configurations have been done
or what programs have been developed. There is internal (within SAP) and external (word
document) documents

 User Acceptance testTest carried out by end user i.e. from client side

 Final preparation/Testing - End and Super user training and verification

 It includes testing, end user training, system management and cutover activities to finalize
readiness to go live

 It also resolves all critical open issues

 On successful completion of this phase, client can run business in live SAP system

 Types of tests carried out are

 Integration test

 Performance test

 Shear test

 Load test
  This phase will run for 30-60 days

 All Bugs raised by testing team has to be resolved in this stage by different functional
consultants ASAP

 Go live and support – Handover of SAP

 The purpose of this phase is to move from a project-oriented, pre-production environment

to live production operation

 This will be the live system in which client will work

 Testing will also be done in live/production system

 This phase will run for 15-30 days

 Operate(ASAP 8)

 Ensure the operability of the solution

 To ensure stability in the project i.e. the SAP software is running properly

LSMW (Legacy System Migration work Bench)

1. Batch Input Recording Method

[https://www.youtube.com/watch?v=z_GzJYlF1OU&feature=youtu.be]

 It is used to convert master data (Material master, Vendor Master, Info Record and Source List)
in bulk i.e. in 1000s from Legacy system (Excel) to SAP

 Recording method is used

 TC used is LSMW. Fields available are Project, Subproject and Object. We can create new project
as well by clicking on create button. Give relevant project name and description. Then dialog
appears for entering Subproject name and description. Then option appears for entering Object
name and description. Project name can be given as Rollout/Implementation/Up gradation.
Subproject can be given as Master data migration. Object can be given as Raw Material
creation/Finished goods creation/Vendor Master creation/etc. Object will be the final object we
have to provide

 Then click on execute. User can view 14 important steps to be carried out

i. Maintain object attributes:

 There are various methods available shown here – Standard batch input method/Batch
Input recording method/BAPI/IDOC. BAPI and IDOC have more of a technical involvement.
Normally Batch input method and Batch input recording methods are used. Most popular
method is Batch input recording method

 Click on Display/change to edit the options. Click on Batch input recording method, then
click on icon recordings overview on the right side. User will be directed to new screen titled
Recordings of project

 Click on create button. A dialog box appears asking for the recording name. Give relevant
name. Then system will ask for the transaction code that needs to be used. Enter MM01 for
instance, if Master data needs to be updated. Then click on Enter

 User will now be directed to material master creation screen. Recording is very sensitive,
avoid usage of mouse clicks, and try using TAB and ENTER buttons

 Enter external material name or numbering. Click on Tab and select relevant Industrial
sector. Click on Tab and select relevant Material type. Then through Tab button go to Select
View(s) icon and press Enter

 Select view(s) dialog box appears. Through mouse, select the first view i.e. Basic Data 1 and
then by using Tab go to green Tick box on Left bottom and click on Enter. Then system will
take user to Basic Data 1 screen

 Enter material description. Similarly using TAB button enter other relevant data in Basic Data
1 screen i.e. capture various fields based on requirement

 After entering all required data in Basic Data 1 screen, use mouse click on icon on top right
which shows list view of other available screens. Click on Basic data 2, similarly enter data in
desired fields. Then again keep clicking on top right button and choose desired views one at
a time and enter data at required fields

 Do remember to enter all mandatory fields

 If user doesn’t want to enter any further data, press ENTER. A dialog box appears in which
system will ask if user wants to save the data. Click on Yes

 Material will be created

 Here we have recorded the mandatory and important fields which are required while
creating the material

 Once these fields are captured, system records these fields, and all such these fields with
relevant data of thousands of materials can be entered in the excel sheet, which will then be
uploaded in SAP
 Once the recording is completed, the system shows all the fields in which data has been
entered. Click on Default All button on top left. By doing so, all the fields that have been
recorded will get displayed on the screen

 Then, click on save button to save the recording. Then Go Back, user can see the record. Go
further back, under batch input recording radio button, there is a recording field, select the
created recording. Then click on save button

 Then come further back to the main screen of LSMW

 User can observe that the system has already taken him/her to the next step

 User must remember to keep ready data of fields recorded in an excel sheet in advance

**Creation of LSMW file to be uploaded in SAP**

 Click on object overview

 Dialog box appears stating if the fields should be displayed as List view or Table view. Click
on Table view

 System will show entire fields which are copied i.e. Structure (Recording name), Structure
description (Recording description), Target field name (as stored in ABAP dictionary), Field
Description (fields that have been entered during recording), Type (Char/Decimal) and
Target Length

 Copy the data under columns target field name, field description, type and target length by
right clicking anywhere on screen and saving it in Excel format. Ignore rows with table name
and Tcode while doing so. Go to Excel and paste it. Give the sheet name in which user copies
as recording data. This will be your 1st sheet

 2nd sheet in excel name it as “Source structure”, 3 rd sheet as “Reference data” and Last sheet
as “Uploading data”

 Copy data from 1st sheet, paste in second sheet, delete field description column. Change all
data under Type column as “C”. Give column naming as Field, Character type and Length

 Copy data from 1st sheet and past in 3 rd sheet as paste special by using transpose option.
This will be the data format. Enter relevant data for each row from company data file. If user
wants to activate Automatic PO, type X under relevant column or keep it blank

 In 4th sheet, user has to copy from 3 rd sheet, but only has to keep field name and actual data
to be uploaded

 Importance of 3rd sheet is that, field description row comes handy while entering actual data
  Copy data from 4th sheet and paste it in a text file (text document). Through LSMW only text
file can be uploaded in SAP

ii. Maintain source structures

 Double click

 Click on Display/Change mode on top left

 Click on create structure button. A dialog box appears in which source structure name and
description has to be entered

 Save it and come back to main screen

iii. Maintain Source fields

 Click on display/change mode on top left

 Select the source structure and click on table maintenance button. User can see the
format. For filling data here, copy data from sheet 2 of excel i.e. “Source structure” and
paste it here. Then click on enter. All the data for Field description column will be taken
from the system automatically. Some descriptions such as Plant and storage location don’t
come and hence need to be updated manually

 Then click on Save and come back to previous screen

 Below the source structure whatever the fields have been added can be seen here. Save it
and come back to main screen

iv. Maintain Structure Relations

 Click on display/change mode on top left

 Double click on option below Structure relations and save it and come back

v. Maintain field mapping and conversion rules

 This is a very important and sensitive option

 Click on display/change button on top left

 Select Fields column, Go to Extras and click on Auto Field Mapping

 A dialog box will appear with some options, don’t modify. Press Enter or Click on Green
Tick on left bottom

 An auto field mapping proposals dialog box will appear. Just click on Accept proposal as
many times as number of fields. User can observe fields keep changing on Right side of
 Proposal 1 option. Here system is mapping source field to recording field. After all fields
are accepted, a dialog box appears stating Auto field mapping complete. Click on Green
tick box or press Enter. In subsequent screen, one can see the mapping has been done

 Come back to main screen

vi. Maintain field values, translations, user defined functions

 Unimportant step, double click and view its contents and come back to main screen

vii. Specify files

 Manually go to this option and double click

 This is an important activity where we will be uploading the text document containing
actual master data

 Click on display/change mode

 Here multiple options can be seen giving options from where data needs to be pulled.
Select Legacy data [On the PC (Front End)] and click on Create button

 A dialog box will appear, don’t change any settings, and browse the text file to be
uploaded and select it. Give any relevant name

 Under Delimiter option select Tabulator option, since the data we are uploading is in
table format

 Under file structure option, Check option Field names at Start of File option, if the file
which is being uploaded has the first row as field names. Also, second option under file
structure must be checked. Then click on continue

 User can see the file path and other option selected. Then click on Save and come back
to main screen

viii. Assign Files

 Click on change/display mode

 Just Save it and come back to main screen

ix. Read data

 Do not change any settings and click on execute button

 System will show how many entries/rows (as count i.e3 or 300 or 3000) are there in the
data file i.e. no. of rows
  Then come to main screen

x. Display Read data

 A dialog box will appear. Do not change anything and click on continue button

 Over view of file to be uploaded can be seen i.e. there will be as many rows as no. of
materials or vendors. By clicking on it individually, the data to be uploaded for each row
can be viewed. Due to some reason if any wrong entry can be seen, then data file can
rectified and uploaded again

 Come back to main screen

xi. Convert Data

 Converting the data uploaded from PC to SAP

 Just click on execute. It show how many rows of data are going to be converted

 Go back to main screen

xii. Display converted Data

 A dialog box will appear. Don’t change anything and click on continue button.

 Legacy system data has been converted to SAP data. Overview of the file converted can be
seen. Click on it to view the contents or data being converted

 Any point u find any error, change data in excel, paste in text document. Save it. Go to
Specify Files option in LSMW and upload it again, and repeat the steps after it again

 Also, if additional data has to be uploaded again and again, user has to repeat process or
steps from Specify Files option only, previous steps don’t have to be repeated

 Remember, whenever new data is copy pasted in same text document with Ctrl+A and
Ctrl+V option, and upload the file again, then old data will be replaced by new data

xiii. Create batch input session

 Nothing has to be changed here. Only option Keep batch input folder(s) option has to be
checked

 Click on execute

 A dialog box will appear stating no. of batch input folders along with transactions (no. of
rows) being created

 Click on continue
  Come to main screen

xiv. Run Batch Input Session

 Select the row and click on process. Remember there might be multiple entries or rows.
By viewing the status in Stat column user can check the status i.e. whether it processed or
new. We always have to select the row with New entry status and then click on Process
icon

 A dialog box appears with Processing mode and additional functions option

 Under Additional functions, Extended log, Expert mode and Dynpro standard size should
always be selected

 Under processing mode – (i) Process foreground – The whole process of entry of data as
done during recording will be gone through. It is done for few materials for validation
purpose. Select Process foreground and click on process. Keep pressing enter and system
will keep taking you to next screen. If any mistake an error will be thrown and user will be
allowed to rectify. Generally not done when bulk data upload has to be done. It is done
only for checking or validation purpose (ii) Display errors only – Select this option and
click on Process button. If there is error, system will throw an error message. If there is no
error, system will directly process and a dialog box will appear stating Processing of batch
input session completed. and (iii) Background – Happens at back end

 Go to MM60 to check materials are successfully created or not

 Point to remember : Say user uploaded 500 material and next time user wants to upload
new 1000 materials below the old ones(500), then new 1000 material data should be
copied and pasted in a separate/new text document and then uploaded

 Point to remember: After copying data from excel to text document, remember to do
backspace at the end of last row in text document

2. IDOC Method

 SE11 – To check [ABAP dictionary – To view various tables]

 Table name – EDIDC – Control record IDOC

 Table name – EDIDD and EDIDD_OLD – Data Record IDOC. It is a data structure used for storing
data

 Table name – EDIDS – Status record IDOC

25. Transport organizer

  It is used to transport configurations from one server to another server i.e. from development
server to quality server, etc. It is used by functional consultant

 SE09 and SE10 both are nearly similar. Used for creating and viewing transports. While creating
a transport, there are four options under request type, of which two are used. Customizing
requests option is used by functional consultant and Workbench request is used by technical
consultants

 SE01 – only for viewing

 Transport request (Request number) can be created using TC SE09 or SE10. While creating
organizational structure such as Company, company code, etc, user has to click on own request
and select the request number created through SE09 or SE10 while saving data. Company
created is given a task number which is assigned under request number created. Further
organizational structure created are given task number in incremental order under the request
number

 Rather than using SE09 or SE10, user can create Request number, while creating organization
structure itself.

 Sometimes user doesn’t have access to create a new request, in that case reporting person or
senior has to be asked to do so

 By default the Transport Request (TR) is in modifiable state. Before transporting transport
request (TR) to any server, Request number and Task number has to be released i.e. need to be
converted from modifiable state to released state. First task number has to be released, then
only Request number can be released. For releasing, a truck like icon is present. Once released
in any server, no modifications or additions can be done under that TR

 Transporting from one server to other server, say, development to quality server is done by
Basis team. Functional consultant shares the request number to be transported with the basis
team, and the basis team does the transportation job

Batch Data Communication

 Batch Input: It is used to transfer data between non-R/3 system to R/3 system or R/3 system to
R/3 system

1. SAP MM Components and sub-components [guru99 website or app]

 i. Master data

 Material Master

 Vendor Master

 Source List

 Info Record

 Quota arrangement

ii. Purchasing

 Request for quotation

 Purchase Requisition

 Purchase order

 Invoice verification

iii. Inventory

 Physical Inventory

 Inventory Management

iv. Material resource planning

 Consumption based planning

2. Organizational Structure [Class notes]

 Create company using TC OX15

 Create company code using TC OX02

 Assign company code to company using TC OX16

 Create plant(s) using TC OX10

 Assign company code to plant(s) using TC OX18

 Create storage location using TC OX09 [Plant selection dialog box will appear]

 Create Purchasing organization using TC OX08

  Create Purchasing group using TC OME4

 Assign Purchasing Organization to company code using TC OX01

 Assign Purchasing organization to Plant using TC OX17

3. Creation of Material type, Material group, Number range and check relevant data related to
material [Class notes]

 Most frequently used material types are…FERT (Finished product), HALB (Semi-finished
product), ROH (Raw materials) and HAWA (Trading goods)

 Go to material types page using TC OMS2

 Select a standard material, and create a new material type using copy icon

 Enter relevant data such as New Material type name with text, Account category reference, etc

 Check option “External no assignment w/o check” to enable external numbering while creating
Material Master

 Select the new material type created and click on Quantity/value updating

 Select quantity updating and value update check box for relevant valuation area/plant for the
newly created material type

 Material group – represents a group or sub-group of materials based on certain criteria. One
may group materials by the type of raw material used to produce it, by production technique,
etc. To view which materials lie under a material group, TC MM60 can be used

 Create material group using TC OMSF

 Create number range and assign it to material type created using TC MMNR. To create number
range group, Click on Groups (Maintain). Then, go to Menu bar, MoreGroupInsert. Enter
text and number range. Number range can be chosen by using F4 button, where available
number ranges options can be seen and chosen from. Press Enters and Save. Then double click
on Material types (Color of material types will change on doing so) and select the created group
and click on Element/Group button. On doing so, all the Material types will be assigned under
the Number range group. To check number range assigned, select the group and click on
maintain button. [ https://www.youtube.com/watch?v=a5nS2aRJT2k
https://www.youtube.com/watch?v=17nrSHNnEVE]

 Use TC’s MM60/MMBE/MB51/MB52/MB1A/ MB1B/ MB1C/ME2O to check data related to

material such as Basic/Stock availability for single material/Movement type or documents/ Stock
 availability for multiple material /Goods issue/Transfer posting/Goods receipt/Stock monitoring
[Move it in downwards at relevant stage]

 MMBE

 Unrestricted use

 Quality inspection

 Reserved

 Rcpt reservation

 On-order stock

 Consignment

4. Material master

 Use TC MM01/MM02/MM03 to create/edit/display material

 While creating material after entering TC MM01, select industry sector, material type. Material
name or number can be entered manually, if not, it will be automatically created from the
number range assigned to the material type

 After clicking enter, select desired views

 After clicking enter, select plant, storage location, sales org, distr. channel

 In basic tab, enter material description, material group, currency, unit, etc

 In Purchasing view, enter purchasing group, purchasing value key, etc

 In Accounting view, enter valuation class, etc

 In other views enter relevant data ;D

  There is also an additional data tab with sub-tabs of Descriptions, Units of measure, etc. Here
one can give material descriptions in multiple languages, equate 1 form of unit of measure into
other form. E.g. 1 pallet can be equated to 12 pieces

 To create a material from existing material, use TC MM01, apart from selecting material number
(optional), industry sector, and material type; enter existing material under Copy from section.

 After clicking enter, select views required. Then click enter again and select organizational levels
such as plant, stor. location, etc

 Change data in respective views as per requirement

 Material can be blocked or unblocked using TC MM05

 Material can be deleted using TC MM06

 Extending material to other plants using TC MM01

4.1 Mass creation (by LSMW, discussed in earlier sections) and Mass maintenance of Material master

 Multiple materials can be created at once using below functions

 eCatt tool

 LSMW (Legacy System Migration Workbench)

 BDC (Batch Data Communication) recordings

 BAPI (Business Application Programming Interface)

 Mass creation is never considered to be end users responsibility. LSMW, BDC and BAPI are
considered to be developers or consultants work

 But as a module specialist one can do mass maintenance using TC MM17. Such mass
maintenance requires that all the data for the materials and organizational levels one selects
should be the same. It is used for mass changing of material master data. If something can’t be
accomplished by this transaction, it can be done using LSMW, BDC or BAPI

 Enter MM17 TC. Select the data that needs to be changed. Click on execute. Enter the material
range or list for which the data needs to be changed. Click on execute. For the list of materials
displayed, click on Select fields button. Select fields dialog box appears. Here, select fields for
which data needs to be changed and click on left arrow button. In next screen, one can see
existing data for the screen, and space for entering new data. Enter new value. Click on column
heading. Overwrite the data by clicking a button. Execute
4.1 Material master views [Guru99 website or app]

 Basic views – They give general information about the material

 Material description – Can be maintained in many languages

 Base Unit of Measure – This is the unit of measure in which material stock is managed. E.g.
Pieces, crater, etc

 Division – 10, 20, 30, 40 for finished goods, trading goods, services, etc for categorizing
materials

 Weight unit – Unit in which product weight is entered

 Material group

 EAN/UPC – Besides usage in bar coding, it is particular utilized in warehouse management as

a unique identifier for material and package combination. One material can have several bar
codes

 Classification view – Create a class and assign desired characteristics. Generally helpful for sales

 Materials can be classified in order to be found by their class, batch characteristics, etc. E.g.
TV sets can have different dimensions and colors. We can create a class, say General, and
add two characteristics, dimension and color, with their respective values. Later this class
along with their respective characteristic can be used to find a TV of specific dimension or
color

 Sales organization data 1

 Plant, Sales organization and dist channel organizational levels for which material needs to
be extended is to be selected

 Then

 Sales organization data 2

 Sales General / Plant view

 Foreign trade / Export view

 MRP View 1

 MRP View 2

 MRP View 3
  MRP View 4

 Plant data – storage 1 view

 Warehouse Management 1 view

 Warehouse Management 2 view

 Quality Management view

 Accounting 1 view

 Accounting 2 view

 Costing 1 view

 Costing 2 view

 Purchasing view

 Foreign trade import view

 Purchase order text view

 Additional data

5. Vendor Group/ Number range/ Vendor Master

 Create Vendor account group using TC OMSG. Give an account group number (can be
alphanumeric), name and any other relevant data. One can make this a onetime vendor group
by checking relevant box

 Define a number range and assign it to account group using TC OMSJ

 Use TC XK01/XK02/XK03 to create/edit/display vendor centrally. It will comprise of general,

company code and purchasing data. After entering TC XK01, enter vendor number (optional, if
not entered, automatic updation from number range will happen), company code, purchasing
organization and account group

 In subsequent screens, enter address, accounting data and purchasing data

 Vendor can also be created/edited/viewed using TC’s MK01/MK02/MK03 and FK01/FK02/FK03

 Vendor can be blocked or unblocked using TC XK05

 Vendor can be deleted using TC XK06

  List of vendors can be displayed using TC MKVZ

6. Source List/ Info Record

 It is used to maintain a list of vendors against a material for a certain validity period. Vendor can
be made fixed or blocked

 Create/Edit/Display source list using TC ME01/ME04/ME03. After creation of source list, Source
list option has to be checked in Purchasing tab while creating/editing a material i.e. in Material
Master

 Use TC ME0M to view source list materials

 Info records are used to maintain pricing and tax code for a material and vendor combination. If
the material and vendor combination for which info record is maintained is used while creating
a PO, pricing and tax code data is automatically updated in PO

 Procurement types in Info Record are – Standard, Subcontracting, Pipeline and Consignment

 Number range can be created using TC OMEO

 Create/Edit/Display Info record using TC ME11/ME12/ME13. While creating info record, enter
material, vendor, purchasing org and plant data. Also select info category i.e.
Standard/Subcontracting/Pipeline/Consignment

 In general data, enter three reminders, material no used by vendor, return agreement, etc

 In Purch. Org. Data, enter planned delivery time, purchasing group, standard quantity, max and
min quantity, net price per procurement unit, incoterms, etc. Here, quantity conversion option
is also available i.e. 1 pallet can be made equal to 100 pieces, etc.

 Conditions – It is used for maintaining pricing conditions. One can observe, net price entered in
Purch. Org data, is transferred as Gross price in conditions tab. Here additional conditions, valid
from and to and amount per unit can be entered

 Text – Standard info record and purchase order notes can be written here. They will appear in
PO only if relevant check box is ticked

 To view list of info records per material and per vendor use TC ME1M and ME1L

7. Quota Arrangement

 It is a master data and source determination component in which we list all the source of
suppliers/vendors and assign quota quantity for a particular period, material and plant
 It is used for allocation of certain quantities of material to a source of vendor. Quota is allocated
to several vendors to purchase a material. Restriction is set to how much maximum quantity of
material can be bought from each vendor

 Once the maximum capacity for any vendor is reached , system will not allow to create PO for
that vendor and ask to choose from other available suppliers

 1st step: is to Define quota arrangement usage by going to path

SPROIMGMMPurchasingQuota arrangementDefine quota arrangement usage

 Click on New entries. It can be created as numeric or alphabetic

 Check relevant options such as PO, Schedule line, Requisition, etc. Save it

 2nd step: Main quota arrangement usage in Material Master

 TC MM02

 In purchasing view of material master, give “Quota Arrangement usage” that is created in 1 st
step

 3rd step: Create quota arrangement

 Create/Edit/Display quota arrangement using TC MEQ1/MEQ4/MEQ3

 Enter material and plant data

 Enter valid to date and press enter, Valid from will get updated automatically

 Select the above entered row and click on item overview

 Select value for column P i.e. Internal/External procurement type

 Enter vendor data, quota value as 1 and maximum quantity/allocation as some value

 If no other vendor is there, % quota will show as 100%

 Allocated quantity for the first time will be zero as PR/PO has not yet been created

 As we keep on creating new vendors Quota % will keep getting evenly distributed among all the
vendors being added

 After creation of PO for any vendors in the quota list, allocated (used) quantity will get
automatically updated in quota arrangement for that specific vendor

 Very rarely such quota arrangements are applied in real time

7. Fiscal Year and Posting period

 Create/Maintain fiscal year variant using TC OB29. If u want calendar year Select the created
fiscal year variant and click on Periods on the Left

 Assign fiscal year to company code using TC OB37

 Creating posting period using TC OBBO

 Open and close posting period using TC OB52

 Assign posting period to company code using TC OBBP

 Maintain company code data using TC OMSY

 View posting period using TC MMRV

 Close posting period using TC MMPV

7.1 Posing Keys

 Account type

 Customer (D)

 Asset (A)

 Vendor (K)

 Ledger (S)

 Type of posting

 Debit

 Credit

8. Chart of Accounts

[https://www.youtube.com/watch?v=E2zM2lgPwIg
https://www.guru99.com/how-to-create-chart-of-accounts.html]

 Create chart of accounts using TC OB13

 Assign COA to company code using TC OB62

  Define Account groups using TC OBD4. Under COA created, an account group is given, under
which a range is assigned for G/L accounts. One can create as many account groups under the
chart of accounts as per requirement. Each acct group under COA will have a range of G/L
accounts

 Define Retained earnings account using TC OB53

 Create the field status variant and the field status group [SPRO>Financial Acctg>Financial Acctg
Global Settings>Document>Line Item>Controls>Define Field status variant]

 Assign the field status variant to the company code using TC OBC5

 Create G/L account using TC FS00. Create as many G/L accounts as desired. Use Copy button
when G/L account to be created has same/similar properties of an existing G/L account. In
control data tab, for option Recon. Account for account type, select vendors, if u r going to
assign the G/L account created to a vendor. Remember, one material/material type has one
valuation class, one valuation class of the material will multiple G/L accounts based on the
materials movement type. Hence, for the same valuation class of a material, a separate G/L is to
be maintained for respective movement types such as BSX, WRX, GBB, etc.

9.0 MM-FI Integration

 Each process has various modules integrated

 Account determination is a configuaration step available in SPRO

 Each integration of a MM with other modules is a configuarion process which is available in

SPRO

 G/L account is created by Finance for each processes. Each process can have a separate G/L
account. E.g. Raw material receipt will have one G/L account, Goods issue will have other G/L
account

 Good movement type also decides the type of G/L account

 G/L account is a property of FI. They will decide how many accounts they want to have. Good
expenses will have one account, Stationary related one account, rent payments, etc. This will
make reporting easier i.e. an accounting can give a senior segragation of various expenses i.e.
each G/L account will give expenses occured for one process such a transportation cost over a
year, food expenses over a year, etc

 MM will decide material type, material groups and materials

  MM has to segregate no. of materials into/under material types as first hierarchy, 2nd hierarchy
u 'll segregate some material groups, a material while being created from a material type will be
allocated under a material group

 Generally no. of material group is nearly equal to no. G/L account or even more

 Two main processes under MM are

 Procurement

 Inventory Management

 While making a PO, G/L accounts are coming automatically in our PO. Except when u enter a
material data which is not in Material Master. In this case, Account assignment tab appears in
Item section, where one needs to enter G/L account data manually

 When u do normal Goods receipt or movement , 101 related G/L account will come
automatically. If u do goods issue related movement, 201, then G/L account associated with it
will come automatically

 MM is material...FI is G/L account...and valuation class is the bridge b/w material and G/L
account OR b/w MM and FI

 One material is assigned to one valuation class

 One valuation class can be assigned to more than one G/L accounts[For instance, 5 G/L accounts
are 1. Expenses 2. Receipt 3. Scrap 4. Transfer stock 5. Sales....It shows for same material u r
doing 5 types of movements]. To which G/L account a material will be assigned will be
dependent on movement type during goods movement and during Purchasing, account
assignment category will play the role to get respective G/L account

 1 Material -> 1 valuation class-> 5 G/L accounts (Multiple G/L accounts)

 Movement type of material will decide which G/L account has to be triggered for that material
during goods movement among the available 5 G/L accounts

 Valuation class is assigned to a material in Accounting 1 view

 Automatic account determination configuration settings:

[Explanation in next section. Briefing done below]

-> Valuation area means plant. One company code can have many valuation areas/plants

-> One valuation grouping code will have valuation areas for which the G/L account will be same
->No of account category reference will be equal to no. of material types

->Assign Material type to ACR

->Assign valuation class to ACR

->Indirectly, Material type is assigned to Valuation class

->Then, Assign valuation class to G/L account. Note, one valuation class can have multiple G/L accounts

9. Automatic Account determination [https://www.youtube.com/watch?v=KFg4l6MurPw]

 SPRO->Material Management->Valuation and account assignment->Account Determination-

>Account determination without wizard. Below highlighted options are available to work with

 Define Valuation control. Here, valuation grouping code should be active using TC OMWM

 Group together valuation areas. Group together valuation area, Company code, Chart of
accounts by giving a grouping code using TC OMWD. Each plant under a company code is given
a separate valuation area [90% of business rule follow plant as a valuation area]. All such
valuation areas of respective plants under a company code are grouped and given one common
valuation grouping code. For all valuation areas/plants for which we want a similar G/L account ,
we group with a single number i.e. valuation grouping code. This is useful when one valuation
class has to be used in multiple valuation areas /plants. Valuation is nothing but plant itself.
When plant is created, it appears as valuation area as well in SAP. Valuation grouping code is
created in this transaction itself by manual entry

 Define valuation classes using TC OMSK

 Account category reference: No of ACR will be equal to no. of material types

 Valuation class: Assign valuation class to ACR. Valuation classes are created and
simultaneously assigned to ACR. In other words, material type is not directly assigned to
a valuation class but through ACR

 Material type/Account category reference: Material type is assigned to ACR.

 Indirectly one material type is assigned to a valuation classes. If the above 3 steps are
carried out, during material creation, only those valuation class selection will be visible
that are linked to the material type via account category reference. ACR is a medium
 between material type and valuation class [Till u have created bridge between Material
and Valuation class]

 Define account grouping for movement types using TC OMWN. As per standard system, we
won’t make any changes in this configuration step until we create any new movement type.
Transaction event keys and account modifiers are assigned to various movement types.
Transaction keys are associated with movement types

 Configure Automatic Postings [From here u’ll create bridge between Valuation class and G/L
account] using TC OBYC. This is the important configuration step in Automatic Account
Determination. In this step valuation class is assigned to G/L accounts. Cancel and click on
Account assignment Tab if going through SPRO path, else, u directly appear at destination if TC
OBYC is used. A single valuation class can hold a separate G/L account in a respective transaction
key. Transaction key are associated with movement types. Important transaction keys are

 Inventory Posting (BSX): After clicking on it, a dialog box appears asking for chart of
accounts (COA). After entering COA, one can assign G/L account for a valuation class. All
these G/L accounts are for stocks

 Offset entry for inventory posting (GBB): Called consumption account. Here valuation
modifier=valuation grouping code. VBR document or modifier is used

 GR/IR clearing account (WRX)

 PRD

 While making PO, if Account assignment category is taken as K (Cost center), which is for
consumption, then for the material, w.r.t to its material type, a valuation class is there, for
which a G/L account is assigned in GBB[offset entry for inventory posting], will appear
automatically in a new Account assignment tab. This G/L account will further be shown during
good receipt as well

 If while making a PO no account assignment category is taken, then material is not of

consumption type, hence no account assignment tab appears. G/L account will be seen during
goods receipt, etc

10. Purchase Requisition [Guru99 – Website or app] [Document type: NB]

 MRP-> PR -> Assign source to PR -> Release PR -> Convert PR to PO -> Goods Receipt ->Invoice

 MRP (Material Resource Planning) creates procurement proposal and later gets converted into
Purchase Requisition. MRP is a system function to determine the material requirements on both
the material and BOM level. A BoM (Bill of Materials) is a list of components and sub-
 components a single material is consisting of. Remaining steps after MRP for completing the
purchasing process are shown in previous point

 Procurement doesn’t have to start by MRP, it can be initiated by consumption based planning or
by direct PR or PO

 Number range creation for PR. It can be assigned to existing document type or newly created
one. It is of two types – internal and external range. Internal are automatically incremented by
system and external are assigned manually. By default, internal is taken into consideration, but
if external range is to be made active, checkbox indicating so has to be clicked

 Standard document type used is NB. A new document type can be created using existing NB
document type based on requirement

 Requirement tracking number – is used for tracking specific requirements. It can be entered
during PR, PO, Contract, Sch Agrmnt and RFQ creation. When created during PR, it is copied into
PO. It is maintained on item level and items can be selected by this number in several reports
like MELB. Enter TC MELB. Choose documents (PO/PR/RFQ…etc). Click on continue. One will be
taken to initial selection screen. Here, Requirement tracking number and other relevant data
can be entered to display the list of relevant documents

 Source determination – It can be done using Quota arrangement, Source List, Outline
agreement, Info Record. Best possible vendor is determined. To use the source determination,
one needs to tick the Source Determination check box on the PR initial screen.

 Assignment of source – If multiple sources are found, then outline agreements have priority
over others. If not found, manual search has to be done

11. Request for Quotation/ Purchase Requisition/ Purchase Order

[https://www.guru99.com/overview-of-quotations-how-to-create-rfq.html

https://www.guru99.com/how-to-create-quotations.html

https://www.guru99.com/how-to-compare-price-for-different-quotations.html]

 RFQ is created to obtain pricing, terms and conditions, deliverables, etc from various vendors to
select the best source for the procurement needs
  Create RFQ using TC ME41. Screens that will appear are Initial screen, Header data, Vendor
Address button (within Header data), and Item overview screen (within Header data). Repeat
the process to send the RFQ to all the vendors from which you are requesting a quotation

 Use TC ME42 and ME43 to edit and display RFQ. If collective number is maintained in quotation,
such quotations with common collective number can be reviewed using TC ME4N

 Use TC ME47 for updating the quotation or creating quotation received taking RFQ document as
reference. Quotation data can be updated using Item details and additional data icon. If any
changes are to be made in same quotation, same TC ME47 is to be used. To display the updated
data use TC ME48. This process can be repeated to create quotation for all of the RFQs
associated with various vendors for the procurement of same material. If certain vendor doesn’t
answer RFQ, then quotation for such vendors is not created

 To select the best possible vendor, prices of various quotations of vendors for a material can be
compared using TC ME49. Collective number entered while creating RFQ can be used for
comparison. If collective number is not available, we must enter all quotation numbers. Before
executing, check options under Price calculations section. After comparing, one can decide
which offers to accept and which to reject

 Selecting or rejecting a quotation – After comparing various quotations through TC ME49, select
the quotation of vendor that needs to be selected or rejected and click on quotation icon, and
you will be navigated to ME47 transaction OR you can directly go to ME47 transaction.

 If you want to select the vendor for procurement, u may update InfoUpdate field in quotation
data section. InfoUpdate field is used to update info record. Save it

 If you want to reject the vendor, tick the Rejection Indicator check box under quotation data
section without updating the InfoUpdate field. Save it. U will be prompted to print rejection
message to inform vendor the status of his order

 Repeat the above two steps for remaining vendors

8. Direct PO [Document type: NB]

 It is the beginning of procurement cycle. Procurement cycle can also be started from
MRP/PR/RFQ

 It has three main sections – Header, Item overview and Item detail

11. PO from PR
12. PO from RFQ

13. Consumable PO (Cost centre K)

14. Blanket PO

15. Import PO [a. Currency change b. Invoice value differs from PO value due to currency and custom
duty, etc]

16. Resolve posting period error

17. Resolve account determination error

18. Service PO [https://www.youtube.com/watch?v=zKTSoTkdL1o]

 Create service no. using TC AC03 [Note: Activity no]

 Create PO using TC ME21N

 Maintain service entry sheet using TC ML81N [Alternative of goods receipt]

19. Scheduling agreement [Document type: LP – Release without documentation or LPA – Release
with documentation]

[https://www.youtube.com/watch?v=VTFyYtrwwbg&t=145s https://www.youtube.com/watch?
v=mf4yhSyDvDo&t=345s]

 Create SA directly using TC ME31L

 Print/Transmit agreement to vendor using TC ME9L

 Edit and view existing SA using TC ME32L and ME33L

 Maintain schedule i.e. create orders (similar to creating PO) using TC ME38

 Print/Transmit delivery schedule to the vendor using TC ME9E

 View list of agreements or contracts using TC ME2N

 Goods receipt using TC MIGO

 Invoice using TC MIRO

  SA can also be created with reference to existing PR, RFQ and contract

20. Contract [https://www.youtube.com/watch?v=LZ8tR9FOshk] [Document type: MK-Quantity

contract, WK – Value contract]

 Create contract using TC ME31K

 Create PO using TC ME21N for the above contract created

 Goods receipt using TC MIGO

 Invoice using TC MIRO

 View contract list using TC ME2N

 Contract can also be created with reference to existing PR or RFQ

 It is of two types – Quantity based and Value based

21. Automatic PO creation from PR

[https://www.youtube.com/watch?v=XQa8IELgdeA]

Create/Edit material master using TC MM01/MM02 and check source list and automatic PO in
purchasing tab

Create/edit vendor master using TC XK01/XK02 and check automatic purchase order in
purchasing data tab

Create info record by combination of material and vendor using TC ME11

Create/maintain source list using TC ME01. Enter data of vendor and check fixed source box

Create PR using TC ME51N. Enter material and organization data. Also enter info record
document number (It appears automatically when source determination box is checked).
Check source determination box and click on Assign source of supply in source of supply tab
under Item tab after entering plant and material data

Create automatic PO from PR using TC ME59N. Check option Per requisition

Purchase order is created automatically. DO MIGO and MIRO to complete the PO cycle
**SPECIAL PROCUREMENT PROCESS**

22. Subcontracting [https://www.youtube.com/watch?v=19OHLCFMkO4]

 Create, if not already, materials to be sent as raw material and to be received as semi-finished or
finished product to/from vendor using TC MM01

 Create purchase info record for material which we are going to receive from vendor using TC
ME11

 Create Bill of Material (BOM) for material which we are going to receive from vendor using TC
CS01. Then in subsequent screen, enter the materials which will be sent as raw material to the
vendor

 Check whether the raw material to be provided to vendor is in stock or not using TC MMBE

 If material not in stock, do so by using TC MB1C. Use movement type as 561. Enter the raw
materials to be provided with desired quantity. This didn’t work for you, so u added the material
using normal GRN process…[PO->GR]

 Check again whether stock position has been updated using TC MMBE

 Create PR using TC ME51N. Select item category as L (Subcontracting). Enter details of the
material to be received from vendor

 With reference to above PR, create PO using TC ME21N. In material tab of Item, a component
icon can be seen, which after clicking will display the list of raw materials to be provided in order
to obtain the desired material from vendor. Please note PR step can be skipped based on
requirement, but remember to keep item category as L while creating PO directly

 Do transfer posting to vendor using TC MB1B and movement type 541 as movement type.

 Do stock monitoring to vendor using TC ME2O. Enter components or raw materials to be

provided. A list of components or raw materials will appear. Select the check box and click on
Post Goods Issue This part is mostly done by SD consultant. For now remember, ME2O use only
for stock monitoring].

 Use either MB1B or ME2O

 Check the stock position using TC MMBE [Don’t keep repeating this step unnecessarily]

 Goods receipt using MIGO using 543 O as movement type [In material section after clicking on
or selecting raw material below material to be received will have 543 O and material to be
received will have movement type 101]. After clicking on + button besides material short text,
 one can see the raw materials or components of the material received from vendor. In header
movement type for data goods receipt will always remain 101.

 Invoice using MIRO

23. STO [Inter-company (Diff company code) and intra-company (Same company code)] [Yet to perform
practical]

https://www.youtube.com/watch?v=w5nNZqrP-0k&t=203s

https://www.youtube.com/watch?v=QW76t-dCbT4&t=173s

https://www.youtube.com/watch?v=beLUMYeFyH4

Inter-company STO

 Purchase order created by purchasing organization of plant of a company (acts as customer)

requiring material and sends to the sales team of plant of a company (acts as vendor) who
will be providing the material. NB PO document type is used [For STO or intra STO use PO
document type as UB]

 Outbound delivery is created by vendor. NLCC delivery document type, which is for
replenishment delivery, is used [For STO or intra STO use NL as delivery document type]

 Goods are issued by the vendor

 Intercompany invoice/billing is created by sales team of vendor for customer. IV document

type is used [For STO or intra STO use F8 proforma type]

 Goods receipt take place in plant of customer

 Invoice is done by the customer

 Note: Customer’s company is billed. Delivery takes place from plant of vendor to plant of
customer. PO created by purchasing organization of customer i.e. vendor plant created by
purch org. Outbound delivery is done by sales area of vendor i.e. Customer created by sales
area

 While creating vendor, by the company requiring the material, the vendor has to be created
and simultaneously assigned to its plant

 While creating customer, by the company sending the material, should create the customer
in its plants sales area. Also partner functions for the customer, if any, has to be maintained
by it
 Common material has to be created/used in both the plants of vendor and customer. Also, it
should exist in the sales area of sending and receiving plant. Check using TC SE16 and SE16n

 Go to SPRO->IMG->MM->Purchasing->Purchase order->Set up stock transport order. Here

following three activities need to be setup

 Define shipping data for plants [Here, the company sending the material links the
customer to its receiving plant]

 Assign delivery type and checking rule [Used for setting up out bound delivery.
Document type NLCC is used. Normal purchase orders don’t have outbound
delivery types]. Here the supplying plant with document type NB is assigned
delivery type NLCC for the customer.

 Assign document type, one-step procedure, underdelivery tolerance [Here, goods

issue and goods receipt are carried out together. This is a single step scenario. In
two step scenario both are carried out separately for the purchasing document.
This node allows us to setup as single step or two steps]. Here we link supplying to
the receiving plant to the purchasing document type and setup the type of delivery
process you want i.e. one step or two steps

 Do the copy control setup from delivery documents to billing documents using TC VTFL. For
ISTO delivering document would be NLCC i.e. NLCC (Delivery type) to IV(Billing type) control
should exist

 After above settings are done, create PO using ME21N. Use standard PO which is for NB
type. Enter vendor number or data, which is of the supplying plant. This PO will be created
by the purchasing organization of the company requiring the material. Maintain info record
before creating this PO. A shipping tab can be seen whenever a STO or inter-company STO is
created

 After the above settings are done, [One step process] PO will be created by the purch
organztn of company/plant needing the material using TC ME21N. Vendor will be taken as
plant of company providing the material and document ype is taken as NB. Material created
as common by both plants will be taken. Info record of material and vendor can be
maintained so dat price and other details can be obtained directly. Also, shipping tab
appears which will have shipping data which have customer details to which materials will
be delivered. Based on configuarion done, delivery type will appear as NLCC

 Create outbound delivery for purchase order document using TC VL10G. Enter shipping
point and purchasing document no. Then select the row associated with the PO and click on
Background tab. This will create outbound delivery of type NLCC. Note the outbound
delivery number
  Again select d same row, go to log, do to documents, go to disp doc , u will see outbound
delivery details. Process this delivery document by entering picking details of the sending
plant. IBS (Inter-company billing status) can be viewed in status overview tab. Then post
goods issue is done, goods issue document (movement type 645) can be seen in purchase
order history of PO. Since it is a one step process, it will also show goods receipt (movement
type 101) in receiving plant. Both Issue and receipt were possible at the same time, only
when configuration is done in node Assign document type, one-step procedure,
underdelivery tolerance

 Now billing document will be created by the sending company using TC VF01. Enter
outbound delivery number. If copy control settings are already done between NLCC and IV,
then click on execute directly, Inter-company IV billing document is created

 Invoice is done using MIRO

24. Consignment [https://www.youtube.com/watch?v=2l9kTfQcJBU]

 Create material master using TC MM01/MM02

 Create consignment Info record using TC ME11 . Enter tax code

 Create consignment PO using TC ME21N. Enter item category as K and info record number

 Create GR using TC MIGO and movement type 101K [Business area error solution needs to
be found]. After GR, goods are received in Vendor consignment area

 Monitor stock overview using TC MMBE and check vendor consignment stock

 Create transfer posting using TC MB1B and movement type 411K [Transfer from vendor area
to unrestricted area]

 Create consignment settlement using TC MRKO [Invoice]

25. Pipe line [https://www.youtube.com/watch?v=WJbtJouRKWs] [Was not able to perform practically]

 Create a new material with material type as pipe line

 MRP and forecast tabs don’t appear in material master

 Create info record using TC ME11. Don’t forget to enter relevant tax code

 Perform goods issue/GR using TC MB1A/MIGO and movement type 201 P

 Perform invoice using TC MRKO

28. Pricing procedure [https://www.youtube.com/watch?v=BHEEYg69MB8&t=9s]

 SPRO->Img->MM->Purchasing->Conditions->Define price determination process

 Go to Maintain condition table and create condition table [TC M/03]. Give 3 digit no for table if
allowed else just press enter. Select Material and Vendor and other relevant attributes from
right and move to left. Based on combination of these selected attributes various discounts,
charges, are applied during PO. For selected combination only pricing procedure is created in
purchase order. Click on execute. Create object directory entry icon appears, select Local object.
Log appears, note table no. Condition table can be edited or displayed using TC M/04 and M/05

 Go to Define Access sequences. It is a search strategy. Whenever a price procedure is called in a

PO, then the access sequence is responsible for searching all the tables and putting the relevant
pricing procedure in PO. Create a new access sequence, give same name to access sequence as
that of the table created (not necessarily). After saving, select the created access sequence, and
click on ACCESSES on the left. Accesses is a number given to particular access sequence. Enter
data and check exclusive. Enter as many accesses for multiple tables as per requirement i.e.
there will be as many accesses as no. of tables. Select an access and click on fields. All attributes
and their associated data selected during creation of condition table appear. Just save it

 Go to Define condition types. There are three calculation types-Quantity, % and value based.
Condition types are parameters you want to include in PO when a price procedure is called. Eg:
Discount, freight charges, gross price, etc. Click on Define condition type. Create new one or
copy an existing one [RA01, etc] and create new. Enter relevant data. Save it. Create as many
condition types as per requirement. Rename condition type, if required. Select the access
sequence created. Select the condition class (Prices, discount, tax, etc), calculation type (%,
quantity, and value), condition category (Basic price, cash discount, input tax). Select plus or
minus. Enter any other relevant data if required.
  Define calculation schema (Pricing procedure). Here we create a price procedure or copy paste
[RM0000] an existing one and create it. Save it. Select the pricing procedure created and click on
control data on the left. Here, bring all the variables created in condition type. Each condition
type will fall under a step. Keep a proper numbering difference between each steps, so that any
forgotten step can be incorporated in between them e.g. 100, 200, 300, etc

 Define Schema group. Create vendor and purchasing schema group and assign purchasing
schema group to purchasing organization

 Using TC XK02, go to purchasing data of desired vendor and assign the vendor schema group

 Define schema determination. Define calculation schema for standard purchase orders. Here
assign schema group –vendor, PurOrg and pricing procedure

 Maintain condition record for each condition type created using TC MEK1. Here all attributes
selected while creating condition table will appear row-wise. Enter relevant data

 While making PO when vendor, material and organizational data is entered, pricing done will
automatically appear

29. Release procedure or strategy [https://www.youtube.com/watch?v=mZTlg_AnQIU]

 Required for PR, Contract, PO, Service entry sheet

 Taking PR into consideration, Release procedure can be done

 With Classification – PR can be released at both Item and Header level. This can be decided
at release group level or Purchase Requisition document type level

 Without classification – Only item level release is possible with this method

 With classification is most important and is mostly used by companies

 Path…SPRO->IMG->MM->Purchasing->PR->Release procedure->Procedure with classification

 The characteristics that are used for release are

 Document type

 Value

 Purchasing group

 Plant (can also be used)

 Use TC CT04 for creating the above characteristics. For document type characteristic, Give a
characteristic name, and click on new icon, enter description and select multiple values button
in basic data tab. Click on Additional data tab, enter table and field name as CEBAN and BSART.
Certain data will be pulled from ABAP dictionary which can be seen automatically updated in
basic data tab. In values tab, Enter character values as NB and any other created if any. In the
same tab, check additional values tab. In restriction tab, enter 032 as class type. This is optional.
For using header level release, Document type that will be used, for instance, say NB, an
additional check box has to be ticked for NB. The path for the same is
SPROIMGMMPurchasingPurchase RequisitionDefine document types. Here, go to
the relevant document type, in our case NB, and tick check box under column name Overall
Release of Requisitions

 For characteristic type Value, Give a characteristic name, and click on new icon, enter
description and select multiple values button in basic data tab. Also check option Interval values
allowed in Basic Data Tab. Click on Additional data tab, enter table and field name as CEBAN and
GFWRT (for Header level release procedure), GSWRT(for item level release procedure). For
Contract, GNETW is used as field name. Certain data will be pulled from ABAP dictionary which
can be seen automatically updated in basic data tab. In values tab, Enter various amount ranges
as per requirement. In the same tab, check additional values tab. In restriction tab, enter 032 as
class type. This is optional

 For characteristic type purchasing group, Give a characteristic name, and click on new icon,
enter description and select multiple values button in basic data tab. Click on Additional data
tab, enter table and field name as CEBAN and EKGRP. Certain data will be pulled from ABAP
dictionary which can be seen automatically updated in basic data tab. In values tab, Enter
desired purchasing groups as per requirement. In the same tab, check additional values tab. In
restriction tab, enter 032 as class type. This is optional

 For characteristic plant, enter table and field name as CEBAN and WERKS

 While creating characteristics for PO, table name will be given as CEKKO

 While creating characteristics for Contract, table name will be given as CEKKO

 If single value is selected in characteristic, then only single value can be selected during release
strategy creation. If multiple value is selected in characteristic, then multiple values can be
selected during release strategy creation

 Class is a header level for a characteristic i.e. a class will be created for PR which will have
specific characteristics; a class can be created for PO which will have specific characteristics, etc.
Use TC CL02, give a class name and enter 032 as class type which is for release strategy. Then
click on create button. Enter description in basic data tab. In characteristics tab, enter all the
characteristics created for Purchase requisition
 Click on icon Setup procedure with classification

 First activity is release groups creation - is created for the class. One can have multiple
release groups depending on various combinations of release code or approver and
variation in price value of PR. Here u can determine whether u want header level or item
level release

 An error “Please check release classes (see long text)” will appear while creating Release
Group. It occurs because there are multiple release class for same type document. Ensure,
there is only one release class on one document i.e. one release class for Purchase
Requisition in our case [https://answers.sap.com/questions/8546479/please-check-
release-classes-see-long-text.html]

 Release code is an approver. It is a two digit code. These are the members of an
organization responsible for releasing a PR, PO, Contract, etc. We can have max 8 release
codes

 Release indicators are of three types – Released(Approved by all approvers), blocked(Not

approved by a single approver) and partial release(Approved by few but not all)

 Release strategy – We can have as many strategies as per business requirement. It can be
based on department wise, value wise, combination of department and value wise. Each
strategy will have n no. of approvers based on requirement. Basically, based on number of
total value or amount combinations, there will be as many release strategies. Here release
codes are added in order. Then in release prerequisites, release code check box are
clicked. In release status, when the status will be blocked and when released can be
viewed. After clicking on classification, select required values for document type,
purchasing group, value range and plant for which release strategy should be effective.
First save. Then, click on release simulation, one can check whether the release strategy is
working.

 By clicking on Additional Tab, in Values Tab while creating a characteristic, manual or new
values can be added in Classification Tab

 The release strategies created can be edited using TC CL20N

 Workflow

 Create a PR using TC ME51N. Based on combination of data, release strategy tab will appear
with relevant data

 Single or multiple PRs at a time can be released. Generally multiple PRs are released at the same
time. Single PR release is used in test systems

 Use TC ME55 to release collective PR

  Use TC ME54N to release PR individually (Used in test systems)

 For releasing PO, enter TC ME28, enter release code and release group. Check options, set
release and release prerequisite fulfilled. Execute. On the next screen, choose the PO u want
to release and click on release button. In ME22N and ME23N, one can c that the status of PO
has changed to released

 Transporting release strategy – Transport request are created for all functions i.e. Release
group, release code, release indicator, release strategy which can be transported from one
server to other server. Then characteristics and class have to be created again in the new server
and use CL24N. Refer below two answers for further help

 Answer 1: Create your characteristics and classes in the Production environment, then for the
release strategy, whatever transport you have created like release codes and strategy please
send it to the production environment, then either use cl24/CL24N for value assignment for
characteristics or go-to the release strategy config and define the classification value for The
Strategy

 Answer 2: You need to create release characteristic and release class in production system and
then transport the TR of all release groups, release codes, release indicator & Release Strategy
BUT In Release Strategy, in Classification segment, you can not enter Values directly, You need
enter all respective values in t.code: CL20N/CL24N by entering Class Type WITH RELEASE CLASS
with Release Group & Release Strategy OR can use ALE for transporting all Release Strategies
with respective values in it

Material Requirement Planning [MRP] Part 1 [Theory]

[https://www.youtube.com/watch?v=TXlD6w2UV6s]

Inputs

i. MPS [Master Production schedule]

 The marketing dept informs about the requirement of the client by specific time or by
specific data

 It always deals with end product

ii. BOM [Bill of Materials]

 It will tell us what materials are required to make that end product

iii. Inventory
  It provides data on how much material is available

Processes

i. BOM explosion

 On combining MPS and BOM, we get BOM explosion

 It just shows, for N number of end product(s), what and how much material is required

 This process of finding the gross requirement is called BOM explosion

ii. Netting

 BOM explosion combined with inventory, is called Netting

 Say, BOM explosion requirement is 500, and 200 is available in Inventory, so netting is 500-
200=300, which will be the requirement

iii. Off setting

 Say product is to be delivered by week 3, hence it started to be made by week 2, and say a
specific material/part takes one week to come. Hence such part(s) needs to be ordered in 1 st
week, product making process will start in 2 nd week and it will be delivered to client in 3 rd
week

Output

i. What to order

ii. When to order

iii. How much to order

Material Requirement Planning [MRP] Part 2 [Settings]

 One can maintain MRP parameters for respective plant(s) using path IMG-> Production-> MRP->
Plant parameters-> Carry out overall maintenance of plant parameters or by using TC OPPQ.

 Plant data in TC OPPB [Direct procurement] gets automatically updated after executing previous
step. [OPPB (Direct procurement) is a sub option of OPPQ]

Material Requirement Planning [MRP] Part 3 – For Direct procurement process

[https://blogs.sap.com/2012/10/24/direct-procurement/ ]

 Perform steps under Material Requirement Planning [MRP] Part 2

 Then, in continuation, either by using OPPQ, click on Direct Procurement under

Maintain Planning Run option. For Direct procurement/production, choose option 3 i.e.
Trigger Direct Procurement in Requirements Planning

 The above step can be done directly by using TC OPPB. After entering TC, click on Plant
button, then select the desired plant, double click on it and choose required option
under Direct procurement/production text

 Define special procurement Key

 IMG-> Production-> MRP-> Master data-> Define special procurement type [For
ECC only (maybe)] or it can be done by clicking Special Procurement button under
Maintain Master data option using TC OPPQ

 IMG-> Materials Management-> Consumption Based Planning-> Master data->

Define special procurement type [For S/4 HANA and ECC (maybe)]

 The above two path difference has to be confirmed in ECC and S/4 HANA.
Remember Material Requirement Planning and Consumption Based Planning. Also,

 Create a Special Procurement type by copying an existing one. For creating direct
procurement type, copy a standard with procurement type 51.Give name of relevant
plant, and make sure direct procurement check box under As BOM component is
ticked or selected. Save it

 After doing the above step, go to material master using TC MM02. Select view MRP2
and enter special procurement created. Save it

Inventory Management

Setting Plant Parameters [https://answers.sap.com/questions/2619027/parameters-for-plant-xx-not-

maintained-in-inventor.html]

 Go to SPROIMGMM Inventory Management and Physical InventoryPlant Parameters

 Copy paste plant 0001 and create plant parameters for your plant. Save it

 This step avoids error “Parameters for plant xx not maintained in inventory management” while
creating reservation
Assign factory calendar to plant [https://www.tutorialkart.com/sap-pm/create-factory-calendar/]

 Use TC SCAL

 Select Factory calendar Radio Button and click on change button

 Click on create on new button. Enter Factory calendar ID, description, from and to Year, Holiday
calendar Id, and Workdays. Save it. Take reference from existing factory calendars if required

 Use TC OX10. Double click your plant. Select Factory calendar created in previous step. Save it

Reservation [Steps Setting Plant Parameters & Assign factory calendar to plant are mandatory before
creating Reservation]

 Enter TC MB21

 Enter desired movement type and plant

 Enter relevant data in subsequent screen to create reservation

 Reservations are relevant to MRP, and when MRP is run, reservations will appear on the MRP
list for that material

 Use TC MD04 to view MRP list for a material. To execute TC MDO4, one must maintain MRP
parameters for respective plant(s) using path IMG-> Production-> MRP-> Plant parameters->
Carry out overall maintenance of plant parameters or by using TC OPPQ.

Movement Types [https://www.youtube.com/watch?v=OGGg273z888]

 It is broadly classified into three categories

 Goods receipt

a. Full GR receipt. After GR, material document is created which can be checked using TC
MB03. It has material document under Accounting document. Using MB03 or directly
MM02/MM03, one can check value and quantity for that material has been be updated

b. Partial GR receipt. In quantity tab, enter the no of quantities actual received. Say PO
was created for 10, but vendor has sent 5, then GR has to be done for 5 only.

c. Canceling GR (Full or partial). Say PO was created for 10 pcs, but vendor sent 5 pcs only,
and mistakenly GR was created for 10 pcs, then this GR can be cancelled fully or
partially. Use TC MIGO, but use movement type 102 instead of 101 which is for receipt.
Go to GR screen using TC MIGO, Select GR and PO, just like normal GR, enter PO
number, and at the corner instead of 101, use 102 movement type. Go into items
details, click on quantity tab, if GR is to be cancelled, let the quantity remain 10
(Assuming you will be creating fresh GR for actual quantities received after cancelling). If
 GR is to be kept, but only extra quantity (5 pc) received is to be removed, den enter
quantity as 5. Click Item Ok. Click on Check and then on Post button. Then Save it. Using
MB03 or directly MM02/MM03, one can check value and quantity for that material has
been be updated

d. Return delivery to vendor (When goods received are damaged).

 Transfer

 Goods issue

 MBST is used to change or reverse the movement type

 MB51 is used to check details for a list of materials such as movement types, material
documents (PO/GR/Stock entry/exit), etc. This is one of the most important transaction code.
[https://www.youtube.com/watch?v=FTjGBF-u_ig]

 MB03 is used to check movement type associated with a single material

 MMBE single material stock overview

 MB52 multiple materials stock overview

 Movement type associated with Goods receipt for MM [TC MB1C]

 101 – Material or Goods receipt against standard PO

 561 – Initial stock uploading

 501 – Goods receipt without purchase order

 Movement type associated with Material Transfer [TC MB1B]

 309 – Material to Material transfer. Basic requirement for transferring one material to other
material is that they should have same base unit of measure. This is generally used to make
some adjustments in inventory. It will involve a receiving material (destination) and source
material (to be transferred). No need to go to MB51 for checking, click on Transfer posting
option on top left in MB1B TC itself. Go to Display, one can check the material document
directly

 311 - Storage location to storage location transfer for same organization

 321 – Quality inspection to unrestricted. There is an option in Material Master to make

quality inspection mandatory. This will make sure that no goods r used or processed until
they r quality inspected. One can not make it mandatory in all cases but for specific cases
 only by not using material master option, but by activating quality inspection part while
creating purchase order

 541 – Subcontracting, Unrestricted to Subcontractor

 Movement type associated with Goods issue [MB1A]

 By end of financial year, if company wants to know cost incurred by each department, then
for that purpose company can create cost centre for every department

 Cost centre is cost collector which collects cost from different sources

 201 – Consumption for cost center from warehouse

 201 K - Consumption for cost center from consignment store

 201 P - Consumption for cost center from pipeline

 202 P - Consumption for cost center from pipeline – reversal

 261 – Consumption for order from warehouse [PP module]

 After goods issue, the dept for which material has been transferred through TC MB51
through cost center variable

 Creating a Movement type [TC OMJJ]

 SPRO  IMG  MM  Inventory Management & Physical Inventory  Movement type 

Edit/Create

 Enter copy from (existing MT) and copy to (new MT)

 Select the Movement type from which you want to create an existing copy and click on copy
button

 Give a name to new movement type and save it

 Select the new movement type created, click on Field selection on the left, and user select
which option needs to be kept mandatory and non-mandatory

32. Physical Inventory

 Counting what is in stock and comparing with stock count in SAP inventory system, and making
any necessary adjustments to make counts in systems match the physical warehouse

 Physical inventory method generally used is Cycle counting

  Steps in physical inventory are

 Physical Inventory - Creation of physical inventory document using TC MI01

 Inventory count - Then physical counting is done and Inventory count is updated using TC
MI04

 Post differences - Then difference in physical count and SAP system are posted using TC
MI07

Transfer posting

 Enter TC MB1B

 Enter relevant movement type, plant and storage location

27. Reporting

30. Tables

30.1. Batch Management

33. Valuation and split-valuation

34. Document types

35. Invoice

36. MRP and CBP Configuration

38. MM-SD Integration

39. Return PO

 Create vendor for return process using XK01. Enter relevant data. In purchasing data view, check
Return vendor check box under Control data section

 Customer default data dialog appears for entering account group and shipping conditions. In
Customer create : Billing Sales area screen, enter Tax classification

 When data is saved, customer is created automatically. or is crea

40. Quota

41. RTP
42. Print commands

 Purchase order – TC ME9F

43. Item category and Account Assignment category

44. Fields mandatory and non-mandatory

Transaction code finder in SAP and export in Excel

 Enter TC SE16

 Enter table name TSTC

 Say user wants to find transaction codes starting with ME, then ME* should be entered in
transaction code field and press enter. List of all transaction codes starting with ME will appear
along with description stating the use of transaction code

 Along with transaction code columns, there are various other columns along with description
column. When user wants to reduce/increase the columns while viewing, do below

 SettingsFormat ListChoose FieldsCheck/Uncheck the fields according to requirement and

click on Save for background processing and click on copy. The screen will be updated
accordingly

 For exporting the list in excel format, goto, EditDownloadSpreadsheetPress EnterGive

file name and directoryGenerate

Service Now (Ticketing Tool)

 Detect & Record  Classify & Prioritize  Investigate & Diagnose  Resolution & Restore 
Incident closure

 Steps involved are

a. Detect and record: Will be detected by end user from client side and will convey to support
team help desk via email/telephone who will then record the incident in the software

b. Classify and prioritize:

 Based on information provided by end user on the incident/issue, help desk team will
assign the incident to a relevant team
  Based on no. of users being affected, impact will be decided and based on effect of
business urgency will be decided. Combination of data of urgency and impact will result
in priority of the incident to be solved

c. Investigate and diagnose: The team assigned the problem will investigate the incident with
the help of details given while recording the incident. This process involves understanding
and getting to know the issue

d. Resolution and restore: Resolution is applied by the support team or given to the end user
from client side. This process involves quick or temporary fix to get the issue resolved

e. Incident closure: It can be customer acknowledgement that he/she no longer faces the issue
or could be an automated process

 Roles of Users

a. First line (Initial contact)

 Helps the user in raising the ticket

 1st person contacted by the end user

 Opens or created the ticket or incident

 Gathers and analyze relevant information from the user

 Resolves the ticket

 If not able to resolve, escalates the ticket

b. Assignee

 A member of the group to which the ticket is assigned

 Works on the incident

 Communicates progress to user and gets more information if required

 If not able to resolve, escalates the ticket to appropriate person

c. Queue manager

 Timely assignment or acceptance of tickets and their resolution

 Restoration of service

 Options available on left side of screen

a. Create new – For recording a new incident

 b. Assigned to me – Display all incidents assigned to a member of a team

c. Open – All open/active incidents/issues can be viewed. Value in any field can be modified
by double clicking on it

d. Open unassigned – Incidents not assigned to anyone

e. Resolved – All resolved incidents

f. All – All incidents/issues

g. Overview

h. Critical incidents map – Shows actual world map with locations having critical incidents
highlighted

i. Setting – On top left. User can personalize the view i.e. add/reduce column variables

 Options after clicking on create new incident button on left

a. Number – Automatically created

b. Caller – End user who has raised the incident

c. Category – Software/Hardware/Networking. For SAP it will be MM/SD/PP/FI

d. Subcategory – Email/Operating system. For SAP, if MM selected as category, sub-category

can be selected as Material master

e. Business server

f. Configuration item

g. Short description – While typing incident description, related search results appear below

h. Contact type – Email/Phone/Walkin

i. State – New/In progress/On hold/Resolved/Closed/Cancelled

j. Impact – High/Medium/Low

k. Urgency - High/Medium/Low

l. Priority – Depends on combination of Impact and Urgency

m. Assignment group – Team which will work on the incident. In your case, MM

n. Assigned to – Assignees from assignment group selected

 o. Three parallel tabs appear named Notes, Related records, Closure information. These are
used while closing the incident

p. Submit – After entering the above data, click on Submit button top right

40. Interview questions

 Sub-contracting – If finished product produced is less for the raw material provided, what should
be done?

 121 – Subsequent adjustment for sub-contracting (Excess/Under consumption)

 Where are the unit conversion options present?

 Additional data in Material Master

 Purchasing tab in Info record

 Weights/Quantities of Item detail tab in PO

 Difference between created unit in MM and order unit & how to link them

 What are the valuation classes available for standard material types?

 Material master views

 Difference between Release strategy of PR and PO

 Table name CEBAN (PR) and CEKKO (PO)

 Release of PR by ME55 and PO by ME28

 How material is linked with plant

 During creation of material type user checks value and quantity update check box for
various plants/valuation for the by selecting the desired material type. Since all materials
are created by using material type, material is indirectly linked to plant

 Also while creating material, a dialog box appears asking the user to select a plant o which
the material will be associated

 Difference between Info Record and Pricing Procedure

 IR only condition types can be added/created, in PP condition types can created and
calculation process can be done

 How to release multiple/single PO/PR

  ME55 (Multiple…in Live system) and ME54N (Single…in Test system)…PR

 ME28….Release of PO

 Where is moving price seen?

 PO

 How to change vendor address after MIGO

 In business partner in vendor master

 Use of MMBE

 Check unrestricted stock

 Check stock under quality/inspection

 Difference between PBXX and PB00

 Types of master data

 Material master

 Vendor master

 Source List

 Info record

 Types of price control

 Difference between price control

 Vendor account group use

 Material group use

 To classify certain materials under a group having similar process or characteristics

 Purchasing organization type

 Centralized

 De-centralized

 What is purchasing group

 Valued v/s non-valuated material

 Use of schema group

 In pricing procedure to link a procedure to a purchasing organization, vendor via purchasing

and vendor schema group

 How to change price after PO

 Blanket PO

 Types of Info Record

 Standard

 Sub contracting

 Consignment

 Pipeline

 Use of source list

 Maintain various sources of vendors for procurement of a material. A vendor can be made
fixed or even blocked in a source list

 Movement types – all [Done]

 Accounting entries in GRN [Done]

 Maximum release levels

 8

 Release with classification v/s without classification

 WC – Item level and header level release

 WdC – Only item level release

 Where it is decided, whether v want item level or header level release

 Release Group – By default it is item level release, if check box indicating header level is
checked, then it becomes header level release

 Role of Account Category Reference

 Links Valuation class to material type

 No. of ACR is equal to No. of material types

 What is trading material

 What is free goods

 What is MRO material type

 List – Internal and external purchase documents

 Internal – PR

 External – PO, RFQ, Contract

 Standard document types for all purchase documents

 NB – PR, PO

 LP, LPA – Scheduling Agreement

 WK, MK - Contract

 Functions of material type

 Mass change of PO TC

 Mass release of PO TC

 ME28

 Difference between LP and LPA [In scheduling agreement]

 https://answers.sap.com/questions/4841474/difference-between-lp-and-lpa-scheduling-
agreement.html

 The scheduling agreement delivery schedule is created in the SAP System. In order that the
information in the delivery schedule can be transmitted to the vendor, the system generates
a message for the schedule

 If you are using scheduling agreements without release documentation (document type LP),
the message is generated directly

 If you are using scheduling agreements with release documentation (document type LPA),
you must explicitly generate SA releases

 What is material document and TC to view it

 MB51

 What happens when goods receipt is posted

 What is P2P cycle

PR (Direct or through MRP)Determine source of supply (RFQ)PO from PRGRIV

 What are procedures for MRP

 Can one material type have multiple valuation class and vice versa

 One material can have multiple valuation class through split-valuation

 This comes in use when one material is obtained from multiple vendors at different prices

 How to hold PO

 Hold button on top screen

 Find the held PO using Document overview option

 How to delete/block/unblock PO

 It can be done on item overview. There are buttons to delete/block/unblock

 How to transport release strategy [Check in release strategy section]

 Table name for contract in release [CEKKO]

 https://answers.sap.com/questions/5198013/contract-release-strategy.html

 If any field missed during recording using Batch recording method, should recording be done
again?

 Account entries for sub-contracting [Done]

 How to fine vendor for late delivery

 Add a new condition for adding fine in Conditions tab of purchase order

 Sub-contracting challan

 Use of Addl Planning button in Purchase order

 Use of Default Values button in PO

 Whenever user wants certain data to always appear by default while creating a PO, Default
Values button is used. It can be done for both Header and Item level

 Standard and moving price

 [https://answers.sap.com/questions/4673784/tabs-in-purchase-order.html]