Uploaded by james varghese

SAP Configuration Guide for Janaki Corp Limited

advertisement
Janaki Corp Limited
Company Code -- JCL ---1000 Configuration
1.SPRO --- Enterprise Structure---- Definition-----Financial Accounting----- Define Company Code—
New Entry. (4 Digit Alpha Numeric)
Enter the basic details---- Save it Under a TR Number S4HK901137
2.---- Edit, Copy, Delete, Check Company code.
2.1--Copy Edit Check CC
Copy From SAP Standards . 1010 to 1000 (JCL)
GL Account Required
Controlling Area Not Required
Currency to Be changed
Transport Number-- not Required
Copy all--- Save
2.2 Edit Company Code Data--- Select Company Code 1000----Edit the name to Janki Corp Limited
and Change all the additional information (Country, Language , Currency Etc)
Controlling Area 1000 Configuration
SPRO --- Enterprise Structure---- Definition-----Controlling----- Maintain Controlling Area
Maintain Controlling Area--- New entry--- Give CO Area 1000--- Click Co Area-== CCode
**Chart Of accounts For 1000= INT hence for CO area also = INT (YCOA to be made if any error
comes for both CC and CO area)
After Creating Co area ---OMSY--- Setup Financial Year for the company code---2022/10
Plant Configuration
SPRO --- Enterprise Structure---- Definition-----Logistics General--- Define, copy ,check plant------ Copy, Check Plant----Copy
Copy from SAP STD to 1100 (No Transport Number required)
--- Define Plant – Select 1100—Rename to “Spongy Iron Plant”—Change address in address icon as
well to required one.
--Do this for other 2 plants (1200,1300 respectively)
Storage Location Creation SLOC Configuration
SPRO --- Enterprise Structure---- Definition---Material Management—maintain Storage Location—
Select Plant (1100) -- Delete SAP Std SLOC’s--- Create new entries—
Repeat for other two plants
Purchasing organisation Configuration
SPRO --- Enterprise Structure---- Definition---Material Management--- maintain Purchasing
organisation---New Entry--Enter “1000” As Purchasing Organisation code
** All The Definitions are over ---Now Over to Assignment part---
Assignment
SPRO --- Enterprise Structure----Assignmnet---Financial Accounting---Assign CoCOde to Company—
enter CC
SPRO --- Enterprise Structure----Assignmnet---Controlling—Assign Company Code to Controlling
area—Select the COarea---Click on Assignmet on left---Assign CCode to COArea---Save
After this –Go to –okkp and setup activate components---select year 2022—and Activate
Components--- Again Select COArea and enter 1000 as CCtr Standard Hierarchy
SPRO --- Enterprise Structure----Assignmnet---Logistics General---Assign Plant to CCOde—
Delete the SAP Std Mapped entry –Save
Create new entries with CCOde and Respective Plant—Save
SPRO --- Enterprise Structure----Assignmnet----- Materials Management----Assign Purchase Org to
CoCOde---Enter the cocode against the pur org
Assign Purchase Org to Plant---Delete all related to plant and the duplicates ---Create new with
designated P ORG and Plant..
**Be carefull while doing assignment of purchase org to plant…Many duplicates might be there..
** Assign Std Purchase Org to Plant is done for special Procurement purpose—Will be done later..
****Basic Enterprise structure is done…****
To test the output ---Check in EC01---Structure---Navigation.
Material Master Configuration
Setting up of Material Ledger ( Mandatory---Done By CO Consultant)
1.SPRO----Controlling---General controlling—Product Cost Controlling – Actual Costin/Material
Ledger -- assign ML types to valuation area
Valuation area= Plant Code
Assign ML Type 9000 to the valuation area—Save Under New TR number for ML Activation
2. Activate valuation areas for ML---Activate ML---Tick mark on ML Act---Assign ‘2’ (Transaction
based) In price determination.
3. To start ML in production –
CKMSTART – T code
Select Plant Code---Untick on test run---execute—Click on Start Immediately---untick print option--Confirm
Master Data
To create a material – MM01
Change---- mm01
Display ---mm03
Customization of Material Screens
1.To Customize the Screens available in MM01--SPRO---Logistics General---config Mat master---Define structure of Data Screens
**SAP Standard is ‘’21’’ …always copy from SAP STD
Copy as ‘JC’ for JCL---keep on pressing enter until all the fields are copied..
TR No- S4HK901290
2. To change the order of Sub screens inside the main screen / views—
Select the main screen where the order change is reqd—click on subscreens –here we can
edit/delete or change the order of the subscreens..
3. To change the order view of each departments/views –
-- config Mat master—Maintain order of main and subscreens—Change the chronological numbers
according to the required order—Double click to enter inside if error comes..
**OMS2—Select the material type and select all the views in it
4. config Mat master—assign screen sequence to user /plant---select first option –change ‘21’ to ‘JC’
Customization of material Type
Copy from ROH---Create new one
1.SPRO----Logistics general---Material Master—Basic settings—Define output format for material
numbers
Here we can assign the length of material Number as per requirement
** Lexicographical/leading zeros..
2. maintain company codes for material management (OMSY)
** setting up of year to the company code
3. SPRO----Logistics general---Material Master—Basic settings---material types—define attributes
**To customize the material type
Select the SAP STD---ROH---Copy and rename as per our requirement..
**** Unable to create new material type like ZCON, ZSAS---Its config and valuation class assignment
is not explained in class. VC Creation is explained in FI – MM Class.
*** Always tick mark on External Number assignment w/o check for entering external numbers
randomly.
** we can modify which all depts/views can be accessed by selecting the required depts..
To Create Material Group
SPRO----Logistics general---Material Master—Settings for key fields---Define material groups—new
entries—create the reqd entries
BP / Vendor Master Configuration
T.code to create Business partner –BP
Table -- BUT100, CVI_VEND_LINK
Views in BP
General View
Purchasing View (1100,1200,1300)
Company Code View/ Financial View (1000)
TR No.. S4HK901306
Steps
Verify the number ranges in Vendor Master (ECC) and BP (S4 HANA) whether it is available to make
both as same. It will be same for both BP and Vendor Master
Vendor
1.SPRO---Financial Accounting---Accounts receivable and payable—Vendor accounts—Create
number range
Enter all the number range as per the BBP and tick on External number range.
2. SPRO---Financial Accounting---Accounts receivable and payable—Vendor accounts—Define
Account Groups—New entries
Here we enter the account group as per BBP
3. SPRO---Financial Accounting---Accounts receivable and payable—Vendor accounts—Assign NR to
Vendor account
Here we assign the number range to the vendor Account group.
Business Partner
4. SPRO--- Cross Application Components—SAP Business partner---Business partner—Basic
settings—Number range and groupings—define number ranges
Create the same number ranges as done in Vendor master
5. SPRO--- Cross Application Components—SAP Business partner---Business partner---Basic
Settings—Business Partner Roles—Define BP role
**Checking of SAP Standards available or not
General data (0000000)
Company Code Data (FLVN00) or finance data
Purchasing Data (FLVN01)
6. SPRO--- Cross Application Components—SAP Business partner---Business partner---Basic
Settings—Business Partner Roles—Define BP role Grouping—new entries
Enter the RG title as per the BBP or as we wish..
** This is done to augment all the 3 different views in a single view
7. SPRO--- Cross Application Components—SAP Business partner---Business partner---Basic
Settings—Number range and grouping—Define Grouping and Assign Number range—New Entries
***Click on Int.Std.Grping since Vendor and BP has common number range
Here we enter the account grouping as per BBP and assign the number range to the BP group
Linking the Vendor Account to BP Grouping
8. SPRO--- Cross Application Components—Master Data Synchronization—Customer vendor
integration—Business partner Settings—Settings for vendor integration—Field assignment for
vendor integration—Assign Keys—Define number assignment BP to vendor—New Entry
** Assign BP to vendor and click on ‘SAME Nos’
While Creating BP
General DATA—All Address, information and Languages
Purchasing Data—Order Currency,
**GR Based INV Verification mandatory
** Schema Group -01 to be assigned
Company Code—Reconciliation account (Select any of Payable GL account)
To Customize the Mandatory Field Requirements for End- user
SPRO--- Cross Application Components—SAP Business partner---Business partner---Basic Settings—
Field Groupings—Configure Field Attributes as per BP Role—Select Required field to be modified—
Save
Purchase Info record
**To maintain the price for a material against a supplier with a validity period
TCode
ME11
ME12
ME13
ME11---Enter the details required---Standard Category--Enter Plant Delivery time, Std QTY, Net
price---GO to Conditions tab—Enter the Validity time.
**OMS2--- To allow qty based and Value Based updating.
Purchasing Group Configuration
OLME—Create Purchasing group—Enter the Pur Grp Data –Save .
Procurement Configuration
1.Purchase Requisition
**SAP STD Document Type -- NB
SPRO—Material management ---Purchasing --- Purchase Requisition—Define Document types—
Select SAP STD ‘NB’—Copy and create new.
**S4HK901734
TCodes—
ME51N –Create
ME52N – Change
ME53N – Display
Table –EBAN/EBKN
Screen Layout Config
SPRO—Material management ---Purchasing --- Purchase Requisition—Define Screen layout at
Document level—Copy SAP STD ‘NBB’ –Create new—
** Do Modificaions wherever required entries are mandatory
To assign the screen type to document type
Goto Document type – select the material type—Assign the screen against the material type
2.Purchase Order
**SAP STD Document Type -- NB
SPRO—Material management ---Purchasing --- Purchase Order—Define Document types—
Select SAP STD ‘NB’—Copy and create new.
**S4HK901734
TCodes—
ME21N –Create
ME22N – Change
ME33N – Display
Table –EKKO/EKPO/EKBE/EKKN
Screen Layout Config
SPRO—Material management ---Purchasing --- Purchase Order -- Define Screen layout at Document
level—Copy SAP STD ‘NBF’ –Create new—
** Do Modificaions wherever required entries are mandatory
To assign the screen type to document type
Go to Document type – select the material type—Assign the screen against the material type
3.Request for quotation
**SAP STD Document Type -- AN
SPRO—Material management ---Purchasing --- Request for Quotation—Define Document types—
Select SAP STD ‘AN’—Copy and create new.
**S4HK901734
TCodes—
ME41 –Create
ME42 – Change
ME47 – To enter Price against RFQ
ME49 – To do price comparison
Table –
Screen Layout Config
SPRO—Material management ---Purchasing --- Request for Quotation—Define Screen layout at
Document level—Copy SAP STD ‘ANA’ –Create new—
** Do Modificaions wherever required entries are mandatory
To assign the screen type to document type
Go to Document type – select the material type—Assign the screen against the material type
4. Contracts
**SAP STD Document Type – MK- Qty Based, WK- Value Based
SPRO—Material management ---Purchasing --- Contract—Define Document types—
Select SAP STD ‘MK’—Copy and create new.
**S4HK901734
TCodes—
ME31K –Create
ME32K – Change
ME33K – Display
Table –
5. Scheduling Agreements
**SAP STD Document Type – LPA
SPRO—Material management ---Purchasing --- Scheduling Agreement—Define Document types—
Select SAP STD ‘LPA’—Copy and create new.
**S4HK901734
TCodes—
ME31L –Create
ME32L – Change
ME33L – Display
Table – EKET/EKES
ERROR: Role VN not defined in master record for supplier 300020, ME329
Error: Release orders against contract 4600000017 not possible (contract not released) ME347
Release Strategy in PR
Error: INT BSX not related to Valuation class 3000
Solution
“OBYC” T code—Select the Code BSX—Enter the chart of accounts—Copy 3000—Remove ‘001’ –
Enter---save..
SE11- Data Base for release Strategy
Table –
CEKKO - PR
CEBAN - PO
1.Characteristics—Decides on what condition the approval should trigger. Eg-Doc Type, Plant code,
Buyer code, PR Total value
SPRO – MM – Purchasing – Purchase Requisition – Release Procedure – Procedure with
Classification—Edit Characteristics—Enter ‘’JC_DOCTYPE’’
Select Multiple values
Goto Additional data—Enter Table Name ‘’CEBAN’’, Field Name ‘’BSART’’
Save.
Similarly set the characteristics for required items as per the BBP
SE11—CEBAN—Take the technical terms associated with the Layman Terms
Doc Type – BSART
Plant – WERKS
Buyer/ Purchasing Grp – EKGRP
Overal PR value – GFWRT—Select The currency—Click on ‘interval values allowed.
2.Class—SAP Std—032
To link the characteristics with class
SPRO – MM – Purchasing – Purchase Requisition – Release Procedure – Procedure with
Classification—Edit Classes
Class Type – 032
Class Name – ZJC_PRRLS
Click Create—enter all the characteristics in CHAR tab
SPRO – MM – Purchasing – Purchase Requisition – Release Procedure – Procedure with Classification
– Setup Procedure with classification
PR value is given by Client or finance team
PR >= 10000 - L4
10001 =PR= 50000 – L3
50001= PR = 300000 – L2
PR >=300001– L1
3.1 Release Group—for JCL---“JC”
Release Group – New Entries – enter Rel GRp as JC—Click on OverelPReq—enter the class—Save
TR - S4HK901761
3.2 Release Code
Release Code—New Entries—Enter RLSGP – Enter the Hierarchy codes and description—Save
PR Creator – PC
Manager – L4
GM – L3
VP -- L2
CEO—L1
3.3 Release Indicator
Release Indicator—No Changes
3.4 Release StrategiesRelease Strategies—Enter release grp ‘JC’—Enter Release strategy ‘L4’—Enter release codes ‘PC’, ‘L4’
Select the Release Prerequisites, Release Status, Classification (here we give the conditions ><=)
3.5 Workflow – New Entries—Done by the ABAP Consultant
In real time we have to link the release group, release codes to plant and the user ID /Agent ID..
**SPRO – MM – Purchasing – Purchase Requisition – Define document type—Tick mark on ‘Overall
** SPRO – MM – Purchasing – Purchase Requisition – Flexible workflow for purchase requisitions—
Scenario Activation – untick all,
Activate flexible workflow for PR—Untick all our doc types
To approve the PR -T code == ME54N
To check how many PR has been created – ME5A
** The Same Process can be repeated for PO as well. We have to Choose the table CEKKO for
reference data
Pricing Procedure
SPRO – MM – Purchasing – Conditions – Define Price Determination Process—
1.Set Calculation Schema –
Define pricing procedure by copying SAP Std – RM0000 (Big)
JCLDOM
S4HK902177
After Copying from SAP Std, delete the condition type which is not required. In real time no deletion
is to be done.
--Select Calculations schema JCLDOM—Click on Control Data—Modify/Delete the fields as per
requirement.
**PB00 — Time Dependant – Commonly Used in all company—validity period exists
**PBXX -- Time Independent – no validity period –Price is constant throughout—Most companies
wont use this because price is always fluctuating
If Step and Counter have same number ,the item will populate in every PO.
2. Define Condition Type – Set condition type – purchasing – Select PB00 – Select the Pricing
procedure/Calculation Schema JCLDOM
PB00 – Gross Price -- Normal -- Automatic
RC00 – Discount – Manual – Negative – Access Sequence is not mandatory—we can enter manually.
ZC00 – Surcharge – Positive -- M
FRC1 – Freight Charges – Positive -- M
MEK1 – Tcode for Maintaining the condition Record/ Prices
** For auto population of prices (using maintained condition records), the particular condition type
should have access sequence assigned to it.
3. Maintain Condition Table – Create Condition table – Create a new table number—Select the field
Combination required to show in MEK1 Screen
Table No. A666 created with our combination- Plant/Material/vendor/Purchasing organisation
4. Define Access Sequence – Copy ‘002’—Create new ‘JCGP’—Click on Access – Select the table
number –Enter – Save – Click on Fields – Save.
** We have to copy SAP std access sequence and make new one and assign it to the condition types
5. Define Schema Group – Define Schema groups for suppliers – New Entries – Create New Schema
Groups based on – JD -domestic , JI – Import—Save.
** Suppliers are domestic or Import
6. Define Schema Determination—Standard purchase orders—new entries – Assign the Schema
group to Calculations Schema or PP , JD -- JCLDOM
**Mapping Schema Group to Calculations schema or PP. This schema group is maintained while the
BP creation step.
**Whenever we use a particular supplier, this will ensure the assigned pricing procedure is called to
the PO.
** Here the PB00 – Automatic (Means Gross price come automatically in we maintain condition
record) , but RC00,ZC00 etc are manual
** In order for automatic price population for all manual condition type, we need to assign access
sequence and also we need to update condition record for same (MEK1)
FI – MM Integration
1.Valuation ClassRaw Materials - 3000
Plant Specific data
Every plant will have different valuation class
2. Movement Type
3. Chart of Accounts
4. Material Type
Client Specific data
5. Account Category reference**Acts as Bridge btw Material Type and Valuation Class. I.e., Client level and Plant level are
connected by this. FI MM integration is happening with this.
3000(VC for Raw Material) == 0001(ACR) == ZROH/ROH (Raw Material Type)
6. Transaction Keys
Configuration Steps
1. Path: SPRO – MM – Valuation & account Assignment – Account Determination – Account
determination without wizard – Define Valuation Control –Valuation Grouping Code should be
always active.
** Valuation area is always at Plant level: SPRO – ES – Definition – Logistics General – Define
Valuation Area – Valuation Area is a Plant
2. SPRO – MM – Valuation & account Assignment – Account Determination – Account determination
without wizard – Group together valuation area – Give Val Grpng Code a number for the required
plant – save
** to make 2 or more plants follow the same valuation class—a number will be assigned to both
plants (0001) so as to identify that both follows the same VC.
3. SPRO – MM – Valuation & account Assignment – Account Determination – Account determination
without wizard – Define Valuation Class – Valuation Class – New Entries – Give the new VC and
Assign Account category reference number – Save
**we can create our own VC and assign it to the material type as per our requirement
GL account Posting
GL – General ledger – account type where business criteria-based transaction is saved separately.
In SAP, Based on the material type, the financial postings has to be done in separate accounts.
GL account is maintained against the valuation class. (OBYC)
MAP -Moving Average Price – It is automatically updated once we do the GR Posting.
**OBYC – T code where GL accounts will be maintained against transaction keys with reference to
chart of accounts/valuation class/ valuation modifier.
Transaction keys –
Goods Receipt – inventory account – BSX – Stock Increase -- Debit
GR/IR Clearing Account – WRX – Paying to vendor - Credit
FI – MM Integration cycle
User Inserts movement type in MIGO (101) – linked to a Transaction Key (BSX) – Chart of Accounts
(INT/YCOA) – Valuation Class (3000/3001-Present in material Master) – GL Account
Errors:
1.Posting Period not possible – MMPV – Give company code – enter current period and year – select
check and close period – execute.
To confirm the process, go to – MMRV –enter company code – verify the details
2. Missing connection of material XXX in plant to Material ledger.
FINS_ACDOC_CUST
135
3. Company Code Variant Error: Go to – OBBP – Enter the variant—Save
Inventory Management
T Code -- MIGO (Movement in Good Out)
1.Goods issue – Giving the Material for production or any other purpose,
Movement type:
201 – Against cost centre
261 – Against Production order
2. Good receipt – Receiving the material from a vendor, PO Process.
101 – against PO / Inbound delivery (Mostly Raw materials)
101 – Against Production order (For Inhouse MFG Products SF, FG)
101 – Against Stock Transfer Order PO (BLR to CHN)
3. Transfer Posting – transfer material from one SLOC to another. No financial implications attached,
311 Movement type, Changing the Stock Category
4. Reservation – To reserve a material
T code -- MB21
** Table for Movement Type – T156
** T Code for customizing movement type – OMJJ – Copy from SAP Std and create new
** MMBE – T code for stock availability of a material
** MB51 – T code for the complete history of a material
5. Physical Inventory – Matching of physical stock with system stock
** No GI/GR must be done during PI
ME01 – to block the stock during PI
Scenario 1:
MI01 – Create PI Doc
MI04 – Enter the Physical Stock
MI07 – Post the Difference
Movement type:
701 – Increase of stock
702 – Decrease of stock
MARD Table will give entire stock of a plant
**Error: "Check table T159L: entry does not exist"
Soln: SPRO-IMG-Material Management-Inventory Management and Physical Inventory-plant
parameters – enter the plant / copy from existing plant – Save
Scenario 2:
90% of companies follow this process
There will be 2 storage locations:
Positive stock – PS10
Negative Stock – NG10
Eg :
1.RM01 – 100
Physical – 80
So we have to do 311 movement from RM01 – 20Qty – NG10
2. RM01 – 100
Physical – 120
So we do 311 movement from RM01 – 20Qty – PS10
After Financial Approval, we post them to the system.
Inventory team will maintain the positive and negative stocks.
Special Procurement
1.Consignment Process
Supplier delivers products in advance against the consignment PO. Buyer consumes material
when required and then the Liability is settled then.
Prerequisites:
Maintain PIR for consignment with item category “K”. T Code -- ME11
Create PO with Item Category K
Steps:
Do GRN for consignment PO – 101 K.—Check MMBE for Material Stock—Stock will be
under vendor name only – no financial docs are generated at this stage
Do Goods Issue for the material and quantity to be consumed – 201 K Movement type –
from now onwards the liability has been generated – FI Docs is posted.
** Cost Centre and GL Account not configured. Hence GI could not be done.
Settle invoices – T Code: MRKO – Liability is checked here – Enter CCode, Vendor, tick on
Consignment, tick on display, tick on withdrawals not settled – Execute – Check the data
Again, Click on Settle –Execute – FI Liability has been posted –Document number will be
generated
** Tax code Not available
** TCode – MSEG – Search the movement type 201 – We will get the material against the
cost centre and GL account – This can be used for running consignment cycle.
2. Sub-Contracting Process
Steps:
Create final material with VC as YB30 (Subcontracting)
Maintain PIR for the final Product – T Code -ME11
Click on Subcontracting—Select the vendor, material, Porg, Plant – enter the date, qty ,net price, tax
code
Create SC PO with item category L. (Should be done for the finished /final product, not
components)
Maintain BoM or Maintain components in PO Screen in Material Data.
Enter material and qty to be given to the supplier
check MMBE for Material Stock Status
Use ME2O to post goods issue to vendor -- FI Doc will not be posted – Inventory will be changed
from Plant to vendor – 541 O movement type.
Enter supplier and plant details -- execute – select the components visible – click post goods issue—
in stock overview we can see the stock qty and its owner
Do GRN against SC PO and inward the material – FI Doc will be posted – 101 Movement type – 543
will be posted automatically (this is to knockout the goods issue to the vendor once he delivers the
finished good) – MIGO
**Error may come for account assignment – OBYC – Maintain Account assgn number for YB30
wherever required.
3. Returnable Transport Packaging
--inventory will be kept for actual material as well as the empty pallets or cases to return it to the
vendor
-- create a packing material
-- SAP Std Material type – VERP
Empty pallet will be tagged against the supplier number only
Steps:
Create a packing material with material type ‘VERP’
Create a normal PO for a particular material.
Do GR for the PO – Click on Transport Equipment icon – Enter Packing material, QTY, Storage
location, Vendor details – Post
** Movement type for Packing material:
501 M – Generation of material
502 M -- Reversal of material or Issue of material to the vendor
** For Packing Material – only Qty updating is enough, no value updation, since it does not incur any
financial document
** Stock for pallet is generated
Now the pallet has to be issued back to the vendor
 In MIGO – Goods Issue— select movement type 502 M – Enter material, plant vendor details –
Post.
Split Valuation
Petrol – Domestic – 100Rs
Petrol -- International -- 50Rs
Same Material has two values depending on the place of purchase
SPRO –MM – Valuation and Account Assignment – Split Valuation – Configure Split Valuation –
Global Types – Create new valuation type – PET_DOM, PET_IMP – Ext Purchase order active, Internal
Purchase order not active, Account Cat Ref 0001 (Raw Materials) – Save
Global category – Create a new valuation category JCL_SV – Select the category type – click on
‘Types --> Cat ‘ -- Activate the valuation types in valuation category
Select the valuation type – Click on ‘Cat. OUs’ – Select the plant to be activated – activate
**If SPV is activated for a material, we have to maintain the standard price for domestic and import
– In material type , we have to select the pricing type as standard instead of moving average
**While creating material Master – In accounting view we have to select the valuation category that
we created JCL_SV, only then the split valuation will be activated for the material.
** While creating PO, the system will ask which valuation type to be selected
MM60 – T Code to check the split valuation of a material
Master Data II
1.Source List
Database of a supplier who is supplying a particular material
Can be maintained only after creating an info record against the vendor & Material.
T Code to Maintain Source List – ME01
2.Quota Arrangement / Share of Business
T Code for QA – MEQ1
If one material is bought from 2 or more suppliers – its procurement is shared among them.
It may be time based or quantity-based share.
Tables – EQUK, EQUP
3.Batch Management
-- mainly done for material with expiry date
-- eg; Food products, pharma products, battery etc.
-- SLED Shelf Life Expiry Date is maintained for each batch.
Steps
--Create a material BT.100.200 – Click on Batch Management in Purchasing view
--Define characteristics – CT04 – DOL_650 – Select multiple values – Give no of characters – in values
tab – give characteristics values as Blue green red etc – save
--Define class – CL02 – Create class DOL – assign the characteristics to class—save
-- goto MM01 – Select classification view – enter the class created DOL – Select values ‘Blue green
brown etc’
--MSC1N – Create batch 1 as DOL_BLU for blue color – enter the dates like mfg, exp etc – assign the
characteristics and value – save. Repeat for creating other batches as well.
--maintain info record for the material and vendor
--Create PO – Enter the batch – Save
-- MIGO – GR – Post
MB5M – T Code to check the Shelf Life
OMCZ – Automatic batch Activation or number assignment – must be Active
MRP (MM-PP)
Consumption based Planning
--Time Based –reorder based on time
--Forecast based – reorder based on forecast (Sales & Marketing)
--Manual and Automatic Re-Order point planning – mostly used by companies
**MM Role in MRP -- Triggering procurement proposals, bringing the material on time to
the warehouse to avoid the line stoppage == generate the procurement proposals and
inward the material.
Steps:
Scenario 1 : Running MRP with valid Scheduling Agreement & Source List
1.Create material MRP.100 – MRP 1,2,3,4 Views to be added – procurement to be always
external – MRP type must be manual reorder point – MRP controller is the person doing
MRP – Lot size procedure is FIXED order qty – Re order point is 100 – Fixed lot size is 100 –
GR processing time and Planned delivery time is 1day
2.Create SA for vendor – ME31L – give validity start and end date – enter – assign material,
target qty, net price, material group – double click on material – in ‘Confcontr’ select
Confirmations (only then we can do inwarding against the inbound delivery) -- go to item
conditions – modify the validity period – save.
3. Create source list – ME01 – or while creating SA – item – maintain source list – enter
validity – select Record relevant to MRP Sch lines generated automatically – tick mark on fix
– Save.
4. Run MRP – MD01N / MD02 – Everything will be auto populated – supplier will get the
quantity notification
5.Create Inbound Delivery – VL31N – save
6. Create GR – MIGO – GR against inbound delivery.
Check the Stock in MMBE – Posted qty will be reflected
MD02—run MRP again—if the qty is more than reorder qty, MRP won’t run
Once the stock is consumed -- MIGO – Goods Issue – Consume the material – Run MRP –
Now the QTY is less than reorder point – MD02 – Save
Now the proposal is triggered – stock will again increase and will go above Reorder point.
Scenario 2: Running MRP without valid Scheduling Agreement & Source List
PR will be generated automatically based on fixed lot size –it will be created automatically
by the MRP Controller – can be seen in creator indicator tab in PR – this will be followed by
RFQ—PO – GR process .
MD04 – to check once MRP run is saved with results
Logistics Invoice Verification
Before paying to the supplier:
3- Way Matching  PO – GRN – IR  For Regular material PO
2- Way Matching  PO – IR  for PO without material Codes, account assignment based CAPEX or
OPEX PO, Services
MIRO –Movement In Receipt Out – T Code for posting invoice receipt
Invoicing – PO – GRN—IR – Submitted to finance – amount sent to the supplier
Subsequent Debit/ Debit Memo – When supplier under charged the company – company owes
supplier
Subsequent Credit/ Credit Memo – when supplier over charges the company – supplier owes
company
The above transaction happens only for amount adjustment.
Stock Transfer Order
1.STO within a plant between SLOC to SLOC – can be achieved using 311 movement type -- MIGO –
Transfer posting – 311 Movement Type – enter material, plant, slocs details – post
2.STO between plant SLOC to another plant SLOC – 301 Movement Type – Material must be defined
in both plants – MIGO – Transfer posting – 301 Movement Type – enter material, plants, slocs details
– post
3.STO between one plant to another plant with delivery and Billing – also known as Inter company
STO Process
Creation of PO in ME21N with item category U (Stock Transfer) – Done by receiving plant –
document type UB.
VL10B – Create outbound delivery against STO PO
VL02N – Do PGI – done by Supplying plant – 641 Movement type – Sales movement type
MIGO – do GR against the outbound delivery reference – Done by receiving plant – 101
Movement type.
3.1 STO between one plant to another plant without delivery and Billing
 Create STO PO with item category U and Doc Type UB
 Do GI against STO PO – 351 Movement type
Do GR against material Document
** 301 – No traceability – immediate transfer happens – Physical movement is not accounted
** 351 – Physical movement of the material is accurately tracked – only after the material reaches
destination, we can do 351 movement type
4.STO between one Company Code to another company code – we can use regular procurement
cycle and get the material
Service Procurement
Service Master
Service Entry Sheet
Invoice Verification – Generally only this is done by the companies
PO creation in ME21N without any material code – Account assignment category – ‘K’ – Untick
“GR” in delivery (** No GR is done since it is a service) – SLOC will not come for account assignment
Cost Centre K – OPEX
Internal Order F – Capex (For assets purchase, Budgeting)
CAPEX – Capital Expenditure –Asset purchase of a Company
OPEX – Operating Expenditure – To run a company what it needs
Do Invoice verification – MIRO
LSMW Legacy System Migration Workbench
1.Direct Input Method
2.Batch Input Recording
3.BAPI
4.IDOC Method
5.LTMC
Download