Professional Documents
Culture Documents
Page 1 of 28
206604137.doc Document SAP Sales Order Manangement Scenario 1 - Consignment Process Usage guidelines and Specific Instructions: Document Flow- The flow of the document is generic. Specific changes to the flow will e re!uired to e done " the compan" team to suit the compan" conte#t. Document Content-The content e#plains the functional specification in a generic manner. Specific changes are re!uired to e made to meet compan" re!uirement. Section 1 The overall usiness re!uirements along with the assumptions$ dependencies$ target audience$ processing method$ output t"pe and volume of transactions are to e clearl" specified in this section. Section 2 This section caters to the detailed functional re!uirement. The process flow diagram is to e compulsoril" designed and documented here. %iner details li&e the section and sorting criteria$ SAP transaction are to e furnished in this section. Section 3 - All the configuration steps to carr"ing out the functional design needs to e documented here. Section 4 The section needs to cover all the &e" usiness test conditions that the design has to satisf". Section section. All issues that have cropped up so far and their present status are to e highlighted in this
Page 2 of 28
206604137.doc Document SAP Sales Order Manangement Scenario 1 - Consignment Process Document Information Deli!era"le #ame $ut%or &wner 'eam Status (ersion Document )e!iew * Sign-off Signatories )ole #ame Signature Date 'onsignment Processing (uruva"urappan Ra)an Accenture S* *raft 1.0
Date 0+,1-,2012
&t%er )elated Documents <Please insert links to related Documents (issues, data entities, etc.).> Related Document Comment
Page + of 28
Contents
1. Overview and Scope................................................................................................................................................. 1.1 Functional Description..........................................................................................................................................6 1.2 Dependencies / Constraints................................................................................................................................... 1.! "ssumptions......................................................................................................................................................... 1.# $ransaction %olume............................................................................................................................................. 1.& Fre'uenc( and $iming.......................................................................................................................................... 1.6 Processing $(pe................................................................................................................................................... 1.) *utput $(pe (*nline/Print/+preads,eet)................................................................................................................ 1. -etention -e'uirements........................................................................................................................................ 1.. "udience and Distri/ution.................................................................................................................................... !. Detailed "unctional Re#uirements.........................................................................................................................10 2.1 Functional +peci0ication......................................................................................................................................11 2.2 Process Flo2 Diagram........................................................................................................................................12 2.! +"P $ransaction.................................................................................................................................................21 2.# 3rror 4andling...................................................................................................................................................22 2.& +ecurit( and "ut,ori5ation..................................................................................................................................22 2.6 6anguage details.................................................................................................................................................22 2.) Processing and *perational Considerations..........................................................................................................22 2.).1 Per0ormance.................................................................................................................................................22 2.).2 7atc, -e'uirements......................................................................................................................................22 2.).! Data 8aintenance -e'uirements...................................................................................................................22 2.).# -e9use Details..............................................................................................................................................22 2.).& 8ulti9compan(, 8ulti9:urisdiction Considerations.........................................................................................22 2.).6 *t,er............................................................................................................................................................2! 2. C,ange 8anagement -e'uirements....................................................................................................................2! $. Design ....................................................................................................................................................................!% !.1 Design 0or Consignment Fill9up..........................................................................................................................2# &'e (elow con)iguration need to (e carried out:.......................................................................................................!% Sales document *+, needs to (e created )rom t'e standard document t-pe +,.....................................................!% Document t-pe *+, must (e made cop- relevant )or deliver- t-pe *." and (illing t-pe *"/ 0pro)orma invoice1!% 2tem categor- *+,3 created (- cop-ing standard item categor- +,34 t'is will (e made pricing relevant )or trans)erring prices and e5cise duties in t'e pro)orma invoice and )urt'er in t'e e5cise invoices................................!% !.2 Design 0or Consignment ;ssue ............................................................................................................................2# &'e (elow con)iguration need to (e carried out:.......................................................................................................!% Sales document *+6 needs to (e created )rom t'e standard document t-pe +6.....................................................!% Document t-pe *+6 must (e made cop- relevant )or deliver- t-pe *." and (illing t-pe *"!. .............................!% !.! Design 0or Consignment -eturn .........................................................................................................................2# &'e (elow con)iguration need to (e carried out:.......................................................................................................!% Sales document *+R needs to (e created )rom t'e standard document t-pe +R....................................................!%
Page . of 28
206604137.doc Document SAP Sales Order Manangement Scenario 1 - Consignment Process Document t-pe *+R must (e made cop- relevant )or deliver- t-pe *.R and (illing t-pe *R6 0Credit memo )or Returns1........................................................................................................................................................................!% !.# Design 0or Consignment Pick9up.........................................................................................................................2& &'e (elow con)iguration need to (e carried out:.......................................................................................................!7 Sales document *+A needs to (e created )rom t'e standard document t-pe +A....................................................!7 Document t-pe *+A must (e made cop- relevant )or deliver- t-pe *.R................................................................!7 %. &esting Re#uirements.............................................................................................................................................! #.1 <e( 7usiness $est Conditions.............................................................................................................................26 #.2 $ec,nical $est Conditions...................................................................................................................................26 #.! -isk and Controls $est Conditions......................................................................................................................26 #.# $esting Considerations/Dependencies ................................................................................................................26 7. Outstanding 2ssues..................................................................................................................................................!8 . Appendi5................................................................................................................................................................!9 6.1 =lossar( o0 $erms..............................................................................................................................................2 Sales Document :eader ; &'e sales document t-pes represent t'e di))erent (usiness transactions in sales4 suc' as in#uir- processing4 #uotation processing4 and consignment stoc< processing. 0"or e5ample4 Document t-pes *+,4 *+64 *+R and *+A 'as (een created )rom t'e standard document t-pes +,4+64+R4+A1....................................!9 Sales Document 2tem ; 2tem categories toget'er wit' t'e sales document t-pes represent t'e di))erent (usiness transactions in t'e SAP s-stem. &'e item categories contained in t'e standard SAP R=$ S-stem4 toget'er wit' sales document t-pes> represent t'e most common (usiness transactions. 0"or e5ample4 2tem categor- *+,3 'as (een created )rom t'e standard item categor- +,31...........................................................................................................!9 Sc'edule line ; &'e division o) an item in a sales document according to date and #uantit-. "or e5ample4 i) t'e total #uantit- o) an item can onl- (e delivered in )our partial deliveries4 t'e s-stem creates )our sc'edule lines and determines t'e appropriate #uantities and deliver- dates )or eac' sc'edule line........................................................!9 Sc'edule line categor- ; A classi)ication t'at distinguis'es (etween di))erent <inds o) sc'edule line. &'e categordetermines 'ow t'e s-stem processes t'e sc'edule line. .......................................................................................................................................................................................!9 3um(er ranges ; A num(er range is provide )or all document t-pe and will (e uni#ue )or eac' o) t'em. 0"or e5ample4 Sales order document t-pe can 'ave %000000000 to %/////////1. .......................................................................................................................................................................................!9 Movement t-pe ; A classi)ication <e- indicating t'e t-pe o) material movement 0)or e5ample4 goods receipt4 goods issue4 p'-sical stoc< trans)er1. .......................................................................................................................................................................................!9 ?oods movement ; A p'-sical or logical movement o) materials leading to a c'ange in stoc< levels or resulting in t'e consumption o) t'e material. .......................................................................................................................................................................................!9 Availa(ilit- c'ec< )or sales ; &'e indicator is determined as a proposal in con@unction wit' t'e respective re#uirements t-pe. 2t can (e c'anged in individual s'ipping transactions. :owever4 onl- one restriction is e))ective. .......................................................................................................................................................................................!9 6.2 "dditional +upporting/-e0erence Documentation................................................................................................2
Page / of 28
Indi!idual re.uirements on consignment issue Sales order t"pes =78>= will e created " cop"ing standard SAP sales order t"pe =8>? and ma&e use of it as glo al template for the scenario. #um"er range: o 78> :'onsignment 5ssue;3 0000000001 @ 0.<<<<<<<<
Page A of 28
Indi!idual re.uirements for Consignment )eturn Be will create following order t"pes for sales$ deliver"$ and illing " cop"ing standard SAP and ma&e use of them as template for the scenario. Sales order t,pe: o 78R copied from 8R. Deli!er, order t,pe: o 7CR copied from CR. /illing document t,pe: o 7R> copied from R>.
#um"er range for sales order: o 78R :'onsignment return;3 0A00000000 1 0A.<<<<<<< #um"er range for deli!er, order: o 7CR :Return deliver";3 0<00000000 1 0<<<<<<<<< #um"er range for "illing document: o 7R> :'redit for Return;3 0<00000000 1 0<<<<<<<<< /illing "loc0 o 9illing loc& should not e set " default ecause approval is performed outside the s"stem..
Indi!idual re.uirements for Consignment pic0-up 6rder t"pes for sales and deliver" elow will e created " cop"ing standard SAP and ma&e use of them as template for the scenario. Sales order t,pe: o 78A copied from 8A. Deli!er, order t,pe: o 7CR copied from CR.
#um"er range for sales order: o 78A :'onsignment pic&up;3 0A00000000 1 0A.<<<<<<< #um"er range for deli!er, order: o 7CR :Returns deliver";3 0<00000000 1 0<<<<<<<<< Deli!er, "loc0 o *eliver" loc& should not e set " default ecause approval is performed outside the s"stem. Status of pic0ed up stoc0 o Pic&ed up stoc& should e returned to '6DPAEF with loc&ed status. Personnel of the sales department needs to specif" storage location for return at P(R.
SAP does not have a proper movement t"pe to realiGe this re!uirement. Hence$ personnel of logistics department manuall" changes stoc& status from unrestricted to loc& " using a function of transfer posting as wor&around.
Page - of 28
1.3 Assumptions
0*escri e an" assumptions made while completing this design. Bhat functionalit" is e#pected of configuration or other developments that pass information to this development and,or retrieve the information processed " it :e.g.$ performance$ triggers$ e#ceptions$ etc.;I2 %or sales department$ it ma&es heav" wor&load to manage this consignment process due to following reasons. 1. The place is ph"sicall" far from Plant and stoc& movements cannot e seen. 2. Dan" activities are involved for consignment process especiall" for consignment issue such as calculating actual goods issue !uantit"$ creating sales order and deliver order$ post good issue and etc.
1. !rocessing Type
>Please indicate t,e t(pe o0 processing used /( t,e reportE i.e. 7atc,, -eal $ime etcA
Page 8 of 28
206604137.doc Document SAP Sales Order Manangement Scenario 1 - Consignment Process Audience ?roup Ase=Distri(ution 6stimated 3um(er Asers
Page < of 28
The ne#t step is proforma invoice creation and then the last step is to create the >#cise 5nvoice.
Consignment Pic<;up
The consignment pic&1up process ta&es place for various reasons such as in the case '6DPAEF stops trading with a customer. This scenario starts when a customer re!uests '6DPAEF sales department the return of consignment stoc& to '6DPAEF4s ph"sical location. AuthoriGed personnel of sales department chec&s the achieved condition for the transaction first and informs to personnel of the sales department whether the authroiGed personnel approves it. Then the personnel of the sales department creates consignment pic&up order. The operator creates deliver" order for the consignment pic&up order and prints out pic&ing list and deliver" note. Pic&ing list is used to chec& !uantit" of actual stoc& pic&ed from customer location and deliver" note is sent to the customer as proof of this transaction. This scenario doesn4t involve illing process ecause the transfer of inventor" ownership doesn4t occur.
Consignment Return
The consignment return ta&es place when a customer wants to return product under customer possession to '6DPAEF as consignment stoc& and to receive a credit for the return. This scenario starts when a customer re!uests returning a product to the '6DPAEF sales department. 5f '6DPAEF accepts$ then an operator of sales department creates consignment return order$ the deliver" order$ and conducts post goods receipt in se!uence ased on the agreed return condition such as !uantit". The operator needs to chec& on SAP the increase of consignment stoc&. %or approval process$ authoriGed person needs to verif" and approve the return outside the s"stem efore '6DPAEF accepts it. Bhen customer sends a proof which indicates the stoc& is received properl" as consignment once again$ the personnel of sales department chec&s that there is no difference etween the proof and SAP post good receipt !uantit" and forward vouchers to personnel of the illing department. The last step of this scenario is posting a credit memo for the return. 'redit memo is manuall" created in the s"stem " personnel of the illing department and the credit note is printed out automaticall". The illing department personnel conducts a final chec& on the credit note and sends it to the customer.
Page 11 of 28
Page 12 of 28
Page 1+ of 28
Page 1. of 28
Page 1/ of 28
Page 1A of 28
Page 1- of 28
Page 18 of 28
Page 1< of 28
+. ..
J%01 K155E
J%01
Page 20 of 28
Page 21 of 28
2. 1anguage details
0Specif" multi @ site re!uirements here e.g. language re!uirements2
2.".3 Data 3aintenance )equirements >6ist an( re'uirements 0or t,e maintenance o0 data, i0 re'uired.A Bot applica/le. 2.".4 )e4use Details >;nclude an( in0ormation regarding t,e re9use o0 code 0rom ot,er de?elopments on ot,er pro:ects or e?en 2it,in t,e same pro:ect, suc, as sample code or rele?ant documents/re0erences.A Bot applica/le. 2.".5 3ulti4company5 3ulti46urisdiction Considerations 0Specif" multi @ site re!uirements here e.g. language re!uirements2
Page 22 of 28
206604137.doc Document SAP Sales Order Manangement Scenario 1 - Consignment Process 2.". #t&er >6ist an( ot,er special printing re'uirements like Duple@ Printing, Compan( speci0ic standard ,eader 0ooter etcA
Page 2+ of 28
3- Design
Con0iguration steps 0or eac, su/9processes *ptions -ecommendation and Decision
'%e "elow configuration need to "e carried out: o o o Sales document 789 needs to e created from the standard document t"pe 89. *ocument t"pe 789 must e made cop" relevant for deliver" t"pe 7C% and illing t"pe 7%< :proforma invoice; 5tem categor" 789E created " cop"ing standard item categor" 89E$ this will e made pricing relevant for transferring prices and e#cise duties in the proforma invoice and further in the e#cise invoices.
'%e "elow configuration need to "e carried out: o o Sales document 78> needs to e created from the standard document t"pe 8>. *ocument t"pe 78> must e made cop" relevant for deliver" t"pe 7C% and illing t"pe 7%2.
'%e "elow configuration need to "e carried out: o o Sales document 78R needs to e created from the standard document t"pe 8R. *ocument t"pe 78R must e made cop" relevant for deliver" t"pe 7CR and illing t"pe 7R> :'redit memo for Returns;.
Page 2. of 28
'%e "elow configuration need to "e carried out: o o Sales document 78A needs to e created from the standard document t"pe 8A. *ocument t"pe 78A must e made cop" relevant for deliver" t"pe 7CR.
Page 2/ of 28
4- 'esting )e.uirements
&ransaction Description Steps
Page 2A of 28
- &utstanding Issues
2ssue 3o Description Assigned &o Status 2mpact Resolution
Page 2- of 28
6- $ppendi7
.1 :lossary o, Terms
&erm De)inition
Sales *ocument Header 1 The sales document t"pes represent the different usiness transactions in sales$ such as in!uir" processing$ !uotation processing$ and consignment stoc& processing. :%or e#ample$ *ocument t"pes 789$ 78>$ 78R and 78A has een created from the standard document t"pes 89$8>$8R$8A; Sales *ocument 5tem 1 5tem categories together with the sales document t"pes represent the different usiness transactions in the SAP s"stem. The item categories contained in the standard SAP R,+ S"stem$ together with sales document t"pesM represent the most common usiness transactions. :%or e#ample$ 5tem categor" 789E has een created from the standard item categor" 89E; Schedule line 1 The division of an item in a sales document according to date and !uantit". %or e#ample$ if the total !uantit" of an item can onl" e delivered in four partial deliveries$ the s"stem creates four schedule lines and determines the appropriate !uantities and deliver" dates for each schedule line. Schedule line categor" 1 A classification that distinguishes etween different &inds of schedule line. The categor" determines how the s"stem processes the schedule line. Eum er ranges 1 A num er range is provide for all document t"pe and will e uni!ue for each of them. (For example, Sales order document type can have 4000000000 to 4999999999). Dovement t"pe 1 A classification &e" indicating the t"pe of material movement :for e#ample$ goods receipt$ goods issue$ ph"sical stoc& transfer;. (oods movement 1 A ph"sical or logical movement of materials leading to a change in stoc& levels or resulting in the consumption of the material. Availa ilit" chec& for sales 1 The indicator is determined as a proposal in con)unction with the respective re!uirements t"pe. 5t can e changed in individual shipping transactions. However$ onl" one restriction is effective.
Page 28 of 28