Standard Business Processes in SAP MM

7/25/2019 Standard Business Processes in SAP MM

1/71

Standard Business Processesin SAP MM

Contents

.

STOCK PURCHASE NON ERS VENDORS

2.

STOCK PURCHASE ERS VENDOR

3. DIRECT CHARGE PURCHASE NON STOCK ITEM

4.

DIRECT CHARGE PURCHASE SERVICE

5. STOCK TRANSPORT BETWEEN PLANTS
http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928749http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928749http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928749http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928750http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928750http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928750http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928751http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928751http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928751http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928752http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928752http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928752http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928753http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928753http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928753http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928750http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928751http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928752http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928753http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928749


2/71

6. CONSIGNMENT PURCHASE

7.

RECURRING PAYMENTS USING INVOICING PLAN

. MISCELLANEOUS PURCHASING

!. INVENTORY MANAGEMENT

.

S"#$% P&'$()*+ N#, ERS V+,-#'*
http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928754http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928754http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928754http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928755http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928755http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928755http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928756http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928756http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928756http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928757http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928757http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928757http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928754http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928755http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928756http://sapfreelancing.com/blog/detail/id/u2w2x2x2/title/Standard_Business_Processes_in_SAP_MM#_Toc345928757


3/71

Scenario brief: In this scenario, material stock relevant forMRP Planning are planned and procured. Dependingon MRP Tpe, !ot si"ing procedure, #vailabilit $heck andother parameters as set in material master and MRP

con%guration, a dail MRP batch &ob determines 'ithin thede%ned planning hori"on, 'hich are the parts that havefallen belo' reorder point (based on Re)uirements vs.Planned receipts*. #n entr is made against the material inMRP Planning +ile, and Planned rder-Purchase re)uisitionis generated (as per MRP parameters*.

Purchase re)uisitions are automaticall converted toPurchase rders, against 'hich oods receipt to relevantPlant-Storage !ocation is performed. +inall vendor invoiceis created, blocked invoices, if an, are cleared b relevantauthorit and /endor paments are e0ecuted.

Pre1re)uisites:

Material master 'ith all relevant %eld details including MRPand Purchasing data %elds. Refer document 2PTP3$urrentState Document3PTP Master Data3v45 for details onrelevant %elds in material master.

Source assignment records should e0ist for the material forauto P creation from PR. This 'ould include utlineagreement ($ontract*-Source !ist-Purchasing Info records.

$on%gurations and master data associated 'ith all processob&ects including Purchase re)uisition, Purchase rder,oods Receipt, Invoice Receipt, Material movements and#ccounts postings should be complete and valid.

Process +lo' in S#P:

Step 1.Re)uirements for usage of stock material aregenerated in the sstem for the material. Re)uirementscan be generated through manuall created reservationsor Reservations automaticall generated through plannedre)uirement for stock material in transactions such as

Maintenance rder 6component planning.


4/71

Manuall created reservations

Transaction code: M789

nter 7ase Date (Date on 'hich materialconsumption-movement* is e0pected, Movement

Tpe ('here the material 'ould be consumed*,Plant (Plantissuing or receiving the material*

The relevant movement tpes for manual creationconsumption re)uirement of the material at #7$ 'ouldinclude 849 6 $onsumption for $ost centre, 889 6$onsumption for Pro&ect.


5/71

In main screen, select $onsumption ob&ect based onMovement tpe (for e0ample. $ost $entre*, MaterialID, ;uantit and save the reservation

#uto created reservations 6 Maintenance rder Planning

Transaction code: I


6/71

Step 2. Create PR via MRP Run

Transaction code: MD49 (MRP Run for a Plant*, MD4= (Single1

item, Single1!evel*, MD7T (7atch mode 1 Dail batch run,automated*

#uto 7atch is set for Dail run at #7$.

MD4= (Single1item, Single1!evel*


7/71

Step 3. Create Automatic Purchase Order

Transaction code:M@A (#utomatic creation of Purchaserder from Re)uisitions*


8/71

nter selection parameters such as Plant, MaterialID, Purchase Re)uisition ?o. etc. and e0ecute the transaction

Purchase rder created can be searched in P !ist Report

transactions like M8! (7 /endor*, M8M (7 Material*,M8B (eneral* and so on.

Step 4. Receive Stock

Transaction code:MI3R

Transaction MI is mostl used for oods Receipt but as per0ecutable actions con%gured on MI transaction, #49oods has not been set. It is set in transaction MI3R


9/71

Material document posted can be displaed in TransactionM74=.n oods receipt for Stock material, the follo'ing #ccountingentries are posted, if material has Moving #verage Pricing

set:Stock #-c Dr R-IR #-c $rIn case of Material 'ith Standard pricing, and in casePurchase price is diCerent from Material standard price,Stock #-c Dr

Price DiCerence #-c Dr R-IR #-c $r$ancellation of the oods receipt movement can be donethrough transaction M7ST


10/71

?ote: #s per print output setting and Printer assignmentsetting for output condition tpe in con%guration transactionM=, at #7$, R of stock items against a Plant-Storage!ocation 'ould generate a R ?ote being printed to therespective Printer mapped in M=.


11/71

Step 5. Create endor !nvoice

Transaction code:MIR

In case of P being marked for R17ased I/ (P 1> Item

details 1> Invoice tab*, Invoice can be created against oodsreceipt postings onl, 'hereas if it is marked as Invoicereceipt, Invoice can be created against the Purchase rder asa 'hole.

7asic Data Section:

Invoicing date, Posting date, Reference, Reference Documentcategor (0. Purchase rder-7ill of !ading-Deliver ?ote etc.*and Reference Document ?o are entered.

Tick on $alculate Ta0 option to calculate Ta0 if an. nter the?et amount in the #mount %eld, till the 7alance is 4.44

Pament section:


12/71

Pament terms, Pament method, Pament 7lock, veralldiscount (if an* can be set in this section

ther sections of the Invoice 'hich can be maintained

include Details section(for Enplanned Deliver $ost,Planning !evel 6 F#: 7locked for pament etc*,Ta0, #mountSplit(to split total amount as per pamentterms*, $ontacts,?ote (for maintaining a detailed note onInvoice*

Simulate and Save the invoice document. #s b default

Invoice documents ma be marked for Pament block, it getsblocked for further clearance.


13/71

Step ". Re#ease B#ocked !nvoice

Transaction code:MR7R

nter selection details in initial screen and e0ecute thereport.


14/71

Select Invoice and click on the reen +lag to release theInvoice, and save to release.

n Invoice Posting, the follo'ing #ccounting entries areposted:R-IR #-c Dr

Ta0 #ccount Dr (if ta0es are applicable* /endor reconciliation #-c $r

Step $. %&ecute Pa'ment Run

Transaction code:+994

Pament run is e0ecuted b the #ccounts paabledepartment. # brief of the transaction is provided belo'.

In initial screen, Run date and Identi%cation is entered for thepament proposal.Ender the Parameter tab, enter $ompan code, Pamentmethod (as relevant*, ?e0t pament date, /endor

#ccounts (if speci%c vendors are to be paid*, 0change ratetpe (in case of pament in +oreign currenc*


15/71

In +ree selectionsection, +ield ?ame (for e0ample 6 InvoiceDocument ?o or a !ist of them* can be speci%call selectedor e0cluded

In #dditional !ogsection, !og tpes and /endor-$ustomer

account range can be maintained


16/71

In Printout-Data Medium section, relevant Program variantscan be set

n Save, parameters for Pament Program run for PamentRun date is saved.

The ?e0t steps are to Schedule the proposal and 0ecute thePament Runin the initial screen of the Transaction


17/71

The ?e0t steps are to Schedule the proposal.


18/71

n entering Start Date-Time, etc. and clicking on reen Tick,it 'ill give a message 2Proposal has been released5

The pament run 'ill be e0ecuted b the sstem as perscheduled Date-Time


19/71

Post Pament, the follo'ing #ccounting entries are posted:/endor Reconciliation #-c $r

7ank #-c Dr

2.

S"#$% P&'$()*+ ERS V+,-#'

Scenario brief: RS or valuated Receipt Settlement isapplicable for /endors 'hich are marked for #uto RSsettlement in /endor master 6> Purchasing Data 1>$ontrol Data section.

In this scenario, post oods receipt, #uto RS Invoices arecreated, 'hich are then sub&ect to Pament run. Thisscenario generall applies for regular-periodic purchasesfrom established vendors.

Pre1re)uisites:

/endor Master should be setup 'ith checkbo0 for #uto RSsettlement and R 7ased I/.Details of /endor mastersetting is elaborated in document 2PTP3$urrent StateDocument3PTP Master Data3v45.

In the Purchasing Info record, for the /endor 6 Material 6Purchasing rgani"ation combination, ?o RS checkbo0should not be set. Details of Purchasing Info record settingis elaborated in document 2PTP3$urrent State

Document3PTP Master Data3v4

$on%gurations and master data associated 'ith all processob&ects including Purchase re)uisition, Purchase rder,oods Receipt, Invoice Receipt, Material movements and#ccounts postings should be complete and valid.



20/71

Step 1.Purchase re)uisition for the material is generatedbased on automated MRP run as detailed in previoussection of this document

Step 2. Purchase re)uisition is Source assigned andconverted to Purchase rder

Transaction code:M@G

This Transaction is sub&ect to the fact that the Material doesnot have alread have a source assigned to it, sa through a

+i0ed vendor or single Purchase Info record 'ithin the currentvalidit period etc. In such cases transaction M@A asdetailed in previous section can be used.nter relevant details in the selection screen like PurchaseRe)uisition ?o (if kno'n*,Purchasing roup, MaterialID, Material roup etc. as relevant and e0ecute thetransaction

Select the displaed Purchase re)uisition and click on #ssign

automaticall or assign manuall. In case of multiple


21/71

available sources, users 'ould have to choose from theavailable sources. Save once after assigning the Source.

?e0t stage is to process assignment and convert thePurchase re)uisition to a Purchase rder. Select the Purchasere)uisition line and click on #ssignments tab


22/71

Select the #ssignment line and click on tab Process#ssignment.

The sstem automaticall proposes the Purchase rder

Tpe, Purchase rder Date,Purchasing roup, Purchasing


23/71

rgani"ation. $lick to continue, dit and save the Purchaserder.nsure that RS , R 7ased I/ and Invoice Receipt indicators

are ticked in Purchase rder 1> Item 1> Invoice section. Inv.Receipt should be unchecked. #lso, under Deliver tab,oodsReceipt indicator should be ticked.

Message utput set for rder can be checked b clickingon Messagestab


24/71

enerated messages can be displaed in MA+ Transaction

Step 3. oods receipt is carried out against the Purchaserder 6 as detailed in previous process section of this

document

Step 4. $reation of RS Invoice

Transaction code: MRR!nter selection parameters in initial screen. It is usuallrecommended to %rst run it in a Test run mode and thenperform an actual run. In the %eld Doc. Selection, if Purchase

rder ?o. is kno'n it can be directl on Purchase rder, elseit can be set on /endor, if vendor is kno'n.

There is also a checkbo0 for Settle oods 6 Item H PlannedDeliver cost, 'hich must be checked for settling Item andPlanned Deliver costs (if an*. Remove Test run check foractual run.


25/71

# !ist output screen 'ith +I document no. (RS Invoice*generated 'ould come up, if the transaction has not beenrun in Test mode.

Step 5. /endor Pament 'ould be performed usingsimilar procedure as documented in %rst process section.

3.

D.'+$" C()'/+ P&'$()*+ N#, *"#$% ."+0


26/71

Scenario brief: Direct $harge purchase refer to manuallcreated Purchase re)uisitions created for consumption of?on stock items directl to an account assignment ob&ect

such as B1 $ost centre, P1 Pro&ect, +1 Maintenance rder etc.Manual creation of Purchase re)uisitions can take placedirectl in MM module, through Purchase re)uisition creationtransactions or in certain cases automaticall in othermodules in relevant transaction. +or e0ample 6 'hen a ?on 6stock item is planned directl inside a Maintenance rder(under component section*, sstem can be set toautomaticall generate a Purchase re)uisition for the non1

stock item 'ith account assignment 2+5. So 'hen oods 'illbe received, the goods and relevant costs 'ill directl beposted to the maintenance order.?on stock Purchase re)uisitions 'ith #ccount assignment areusuall sub&ect to a Release procedure 'hich is de%ned asper characteristics values of $lass PR3R!#S in sstem.Details of Release Strategies and their de%ningcharacteristics values can be checked for above class and

class tpe 4=8 in transaction code $!8?

Pre1re)uisites:$on%gurations, master data and inter1module integration

associated 'ith all process ob&ects including Purchasere)uisition, Purchase rder, oods Receipt, InvoiceReceipt, Material movements and #ccounts postingsshould be complete and valid.


Step 1. Purchase re)uisitions are manuall created 'ith#ccount assignments or created automaticall through ?onstock component planning in Maintenance rderM@9? 6 Manual PR $reation

#ll details are entered including Material ID (ifkno'n*-Te0t (if no material ID is kno'n*,Material roup (as


27/71

relevant*, Purchasing roup (+or DirectPurchase*, ;uantit, Enit,Deliver Date, Plant (receivingplant* etc. and Purchase re)uisition is saved.

#lso Item details pertaining to #ccountassignment, /aluation, and other mandator %elds shouldbe %lled. Sstem 'ill automaticall point out to re)uired%elds that are missing entries.

I


28/71

Sstem 'ill prompt user for entering mandator detailspertaining to Material roup,Purchasing roup under thePurchasing Data tab against the !ine item. ther optional%elds like /endor, Planned Deliver Time etc. as relevant canalso be entered.

7ased on setting on component line, sstem can betriggered to generate a Purchase re)uisition for the ?on


29/71

stock item either #fter rderrelease or Immediatel or ?ever.Details of Purchase Re)uisition, linked to the Maintenance

rder can be directl found inside Maintenance rder 1>Purchasing Data section.

Step 2. Purchase re)uisitionis released b relevantauthorit based on Release code identi%ed b sstem basedon Purchase re)uisition value etc., and correspondingapproving limits of approver

Transaction code: M@


30/71

The Purchase Re)uisition is released and saved.Step 3. #ssignment of Source and Processing ofassignment to create Purchase rder from Purchasere)uisition.

Transaction: M@G


31/71

Process is same as detailed in previous process sections inthis document.

Step 4. oods receipt against the Purchase rder

Process is same as detailed in previous process sections in

this document.Step 5. Invoice Receipt


this document.

Step ". /endor Pament


this document.

4.

D.'+$" C()'/+ P&'$()*+ S+'1.$+

Scenario brief: Service Procurement is a ma&or procurementactivit at #7$. Services procured ma be segregated underseveral categories including $ontract !abour hire, +leet)uipment hire, $onsulting services, Pro&ect 7ased servicesand Miscellaneous services among others. +urther, servicesare categori"ed from JKS perspective as nsite services,

Csite services etc. to ensure that vendors compl as perJealth and Safet norms. ngoing $MIP Pro&ect aims atbuilding up an S#P based process to perform Jealth K Safetrelated capabilities of vendors prior to assigning them 'orkthat 'ould re)uire due compliance.+or details of Service master maintenance and categories ofservices, refer to the document 2PTP3$urrent StateDocument3PTP Master Data3v45


32/71

Service entr sheets are %lled up b e0ternal Service vendorsin an application called I$#PS 'hich is a Portal basedapplication built for that purpose and accessible toauthori"ed vendors. I$#PS functionalities have not been

detailed in this document o'ing to controlled and limitedaccess to the application.

Pre1re)uisites:

$on%gurations, Service master data and inter1moduleintegration associated 'ith all process ob&ects includingPurchase re)uisition, Purchase rder, Service ntr,

Invoice Receipt, Material movements and #ccountspostings should be complete and valid.


Step 1. $reation of Service Purchase Re)uisition.

Transaction: M@9? (Manual $reation of PurchaseRe)uisition*- I


33/71


34/71

#ccount assignment details and other re)uired details ,if an,should be %lled up. $heck and save Purchase re)uisition.

I


35/71

Service details are to be maintained under the 0ternaltabat the bottom of the peration tab

7ased on con%guration setting on Maintenance rder tpefor %eld peration 6 Res-Pre) creation, Service PR ma becreated on Save or on release or ?ever for the maintenancerder tpe.


36/71

Purchase re)uisition pertaining to services created fromMaintenance rder can be checked in MM 6 PurchaseRe)uisition !ist Reports (+or e0ample. M@# transaction, 'ith#ccount assignment categor set as +* or directl inside

Maintenance rder under peration 1> #ct. Data tab

Step 2. #pproval of Purchase Re)uisition b authori"edperson.#s detailed in previous process section of this document.Step 3. Source #ssignment and $onversion to Purchaserder.

#s detailed in previous process section of this document.Step 4. Service ntr sheet created against Purchaserder, and performed Service )uantit accepted for posting

Transaction: M!L9? (In S#P*- Service entries done throughI$#PS not in scope of this document. Separate documentsma e0ist on the same in #7$ Portal.


37/71

The Purchase rder ?o is entered b clicking on therPurchase rder tab. Then click on $reate entr sheet iconand enter values of Short Te0t, Document Date, PostingDate andReference

$lick on Service selection tab


38/71

If #dopt +ull ;uantit is not ticked, sstem 'ill propose forservice entr ?et pending hours (Planned hours 6 #lreadentered hours*, and if it is ticked, sstem adopts full )uantitas planned. It is better to be left unchecked.

In ne0t screen select the service line and click on tabServices (#dopt Services*

The sstem automaticall adapts the service line into theService entr sheet under #ccept Data tabEsers should no' update the #ctual ;uantit of service thathas been performed, to be accepted for posting.


39/71

To accept and Post the service entr, click on reen +lag onTask bar and save the Service entr sheet.

Step 5. Invoice created for services performed andaccepted#s detailed in previous process section of this documentStep ". /endor paments

#s detailed in previous process section of this document


40/71

5.

S"#$% T'),*2#'" 3+"4++, P5),"*

Scenario brief:This scenario refers to internal procurementof Stocks, bet'een Plants 'here one plant 'ould be a

supplier or vendor plant and the other 'ould be a receiveror customer plant. In this process the customer plant'ould raise a ST Purchase rder for deliver of goodsagainst the suppling plant. The suppling plant 'ould inturn create a sales order against the re)uirement 'ithrecipient plants $ustomer ID.

The process 'ould follo' a 91step procedure, if set in STcon%guration setting bet'een a pair of plants and P

Tpe or8 6step stock Transfer 'ith suppling plant issuing

out the stock from its Enrestricted use stock, stocktransferred to Stock in Transit and receiving plant %nallreceiving from Stock in transit to Enrestricted use stock. Inone step procedure as soon as stocks are issued out ofsuppling plant, it 'ould get posted to stock in receivingplant.

In #7$ process perspective there is no integration setup ofPTP (S#P MM* 'ith S#P ;M module. Ideall, as per S#P best

practice guidelines, on receipt of oods at receiving plant,there should be check on ;ualit parameters of the goodsdelivered and onl on passing the parameters is the stockdeclared as Enrestricted. +or e0. In case of +inished productof Mining, rade check 'ith factors such as Metal content,Moisture content etc. should ideall be checked and recordedsstem. In such a scenario, stocks 'ould get posted to;ualit Inspection stock, generating inspection !ots against'hich Result Recording and Esage decision is recorded,

based on 'hich the stock gets transferred to 7locked stocko@r Enrestricted use stock.

Pre1re)uisites:

# /endor master should e0ist and be assigned against thesuppling plant and a $ustomer master should e0ist andhave been assigned in MM ST con%guration against thereceiving plant.


41/71

The material master should be active in both plants andshould have at least a Purchasing vie' in receiving plantand a Sales vie' in suppling plant

+or deliver relevant ST, all necessar deliver relevantcon%guration settings should have been done on MM side

$on%gurations, master data and inter1module integration

associated 'ith all process ob&ects including ST Purchaserder, utbound Deliver-oods issue, Inbounddeliver-oods receipt, Sales billing (if relevant*, Invoiceveri%cation (if sales billing is relevant*, Materialmovements and #ccounts postings should be complete

and valid.


Step 1. $reation of ST Purchase rder (Tpe E7*

Transaction: M89?

nter Jeader detailsincluding Suppling Plant, Purchasergani"ation, $ompan $ode,Purchasing roup etc. asrelevant

nter Item details including Material ID, P

;uantit, Deliver Date, Recipient Plant,Storage!ocation, Item Pricing $ondition details, $on%rmationcontrol ke 'ith Deliver details (under $on%rmations to beset to Inbound deliver if relevant to same*


42/71


43/71


44/71

$heck document for completeness and save the document

Step 3. $reating an utbound Deliver for Sales rder

Transaction: /!94In the Sales rders tab of the Transaction, enter the Salesrder ?o. and e0ecute. TheDeliverdate and $alcRuleDeNtDlv$rDt %elds for selecting the Salesdocuments relevant for deliver should be correctl chosen.

Select the relevant Deliver item line and click on $reate in7ackground


45/71


46/71


47/71


48/71

n posting oods issue, movement tpe O9 is e0ecuted'hich results in

Stock in Transit at receiving plantDr

Inventor at suppling plant $r

If there are +reight charges included, accounting document'ould sho' follo'ing entries:Inventor Transfer #-c Dr +reight-$ustom $learing #-c $r

This can be checked in Material movement document in

transaction M74=


49/71


50/71

Step 5. $reate Inbound deliver at Receiving plant

Transaction: /!=9? ($reate Inbound Deliver '.r.t P*nter /endor and P ?umber and proceed


51/71


52/71

$heck under Item overvie' enter #ctual R date,update Deliver ;uantit and Receiving plant and click onPost oods Issue

The resulting goods movement results in transfer posting ofstock:

Stock in Transit $r


53/71

Enrestricted (ER* Stock at receiving plant Dr$heck against Stock in receiving plant in MM7-M7@8transactions. The ER stock value 'ould go up.

Step $. Sales order billing-Release to #ccounting (nl

applicable in case of Intercompan billing 6 provided thatthere is a business process for same*

Transaction: /+49-/+48#bove scenario e0ecuted bet'een Plants under samecompan code. Jence no subse)uent billing (at suppl side*or invoice receipt (at recipient side* is applicable. Invoicereceipt, 'here applicable, 'ould follo' a similar process as

documented under previous process scenarios of thisdocument.

6.

C#,*./,0+," P&'$()*+

Scenario brief: $onsignment process is based on the /MI(/endor Managed Inventor* concept of procurement. /endorhas phsical and %nancial control of the stock 'hich is stored

at customer premises unless customer 'ithdra's completeor part of stock from the designated vendor consignment


54/71

stock for personal usage. This 'ould create a liabilit on thecustomer 'hich is to be paid-settled to vendor.

Purchasing Info records and $ontracts for $onsignment items

are maintained 'hich is the basis of source assignment 'hileconversion of a Purchase re)uisition to a Purchase rder. ndeliver of a $onsignment item, oods receipt 'ould resultin stocks being stored in /endor 6 $onsignment stocksegment. n re)uirement of stock, oods issue fromconsignment stock to account assignment ob&ect (such asre)uesting $ost $entre, Pro&ect etc.* is e0ecuted using therelevant movement tpe. #uto invoice for consignment stockusage is created 'hich is further sub&ect to Pament run.

Pre1re)uisites:

$on%gurations, master data and inter1module integrationassociated 'ith all process ob&ects including Materialmovements and #ccounts postings should be completeand valid.


Step 1. $onsignment Purchasing Info record creation K$onsignment $ontract creation.Details of above are provided in the document 2PTP3$urrent

State Document3PTP Master Data3v45Step 2. Purchase re)uisition created for consignment item

Transaction: M@9?

nter relevant Item level details, such as Item $ategor (Q Bfor $onsignment*, Material ID,;uantit, Recipient

Plant, Deliver Date etc. as relevant and save the Purchasere)uisition.


55/71


56/71

In MM7 Report, the stock received of $onsignment materialat recipient Plant-Storage !ocation 'ould be displaed under/endor $onsignment stock.


57/71

Step 5. oods issue for consumption from /endor$onsignment stock

Transaction: M799-M79#-MI3I

oods from $onsignment stock can be issued out forconsumption to $ost $entre (movement tpe 849 B*, Pro&ects(movement tpe 889 B* and so on. To reverse movements,movement tpes are 848 B ($onsignment consumption for$ost centre reversal*, 888 B ($onsignment consumption forPro&ect reversal* and so on.


58/71

During $onsumption, associated 'ith Material Document are#ccounting, $ontrolling and $onsolidation documents (if$onsolidation active*. The accounting document 'ould resultin follo'ing entries:

$onsignment stock $learing #-c $r Stock consumption #-c Dr

In MM7 report, the consignment stock 'ould be reduced bthe amount consumed.


59/71


60/71


61/71


62/71

Scenario brief: $ertain procurements are done on a regularbasis and 'ould involve pament on a periodic basis, sa atthe end of each month. Such paments can be planned usingan Invoicing plan set in the Purchase order. Purchase order

created is a +rame'ork Purchase rder. In such cases, thereis no oods receipt performed. n a periodic basis, Invoices'ould be generated through auto settlement report in!ogistics Invoice /eri%cation.

Pre1re)uisites:

/endor should have been set up for auto RS settlementInvoicing Plan details should be set in Purchase rder

(+rame'ork P*$on%gurations, master data and inter1module integration

associated 'ith all process ob&ects including Materialmovements and #ccounts postings should be completeand valid.


Step 1. $reation of +rame'ork Purchase rder

Transaction: M89?$hoose rder tpe 2+5 and enter other detailsat Jeaderand Itemlevel of Purchase rder

Jeader details 'ould include /endor Data, rgani"ational

Data such as Purchasing rg.,Purchasing roup, $ompan$ode, /alidit Start date, /alidit nd date, etc.

Item details 'ould include #ccount assignment ke (B1 $ostcentre, P1Pro&ects etc.*,Material ID-Shortte0t, ;uantit, Enit, Price per unit, Material roup, Plant, etc.

# crucial section to be %lled in is the Item details 6 Invoice

section, 'here on#'Invoice receipt and RS are to beticked and Invoice Plan details are to be %lled, 'ith planned


63/71

invoice dates. Invoice amount 'ould be e)ual to the price ofthe item against 'hich Invoicing plan has been set.$lick on Invoicing plan tab and Invoicing Plan tpe is to be

selected from dropdo'n

In Deliver section of Item detailseither oods receiptshould be unchecked or it can be set to R 6 ?on1valuated


64/71

Step 2. $arr out #utomatic settlement (Invoicing Plan*

Transaction: MRISIn the Initial screen enter the details kno'n 6 such as$ompan code, Plant, /endor, Purchasing Document etc.Initiall e0ecute it in Test run mode

n removing the Test run checkbo0 in initial screen, Invoice

document 'ould have been generated.


65/71


66/71


67/71


68/71


69/71


70/71


71/71

#fter hour oods issue

#fter hour oods issues at #7$ refers to a custom

transaction MI3

Standard Business Processes in SAP MM

Documents

Transcript of Standard Business Processes in SAP MM