sap PRRelease Procedures

1、release procedures (approval) can be used for purchase requisitions (pr), purchase orders (po), rfqs, outline agreements and service entry sheets. the principle is exactly the same for all. if you can master one, you will know them all.lets set up release procedures for pr for the following example:

2、our company have got 2 plants: plant 3100 (london) and plant 3600 (new york). for new york (plant 3100), if pr item value is between 0 - 1000 dollars, then pr needs to be released by one person (person b) for new york (plant 3100), if pr item value is bigger than 1000 dollars, then pr needs to be re

3、leased by two people (first by person b, then person c) for london (plant 3600), if pr item value is bigger than 1000 dollars, then pr needs to be released by two people (first by person a, then person c).key terminology: release codes -the different levels that the approval will go through. release

4、 groups -grouping of strategies. release strategy -unique, set of condition, sequence and levels of releases. every line in diagram is a strategy (so we have 3). release indicator / status -the status of pr as it moves through the strategy. example block (cant create po yet) or final release (can cr

5、eate po from pr)here is a summary of the steps to follow to set up our example: create characteristics & link to comm. structre (ceban for pr) create class & link to characteristic create release groups & link to class create release codes release indicator set up strategies- strategies & codes- pre

6、requeirements- status- assign values for strategies set overall / item for doc type (pr only) create and allocate autorisation profiles- details of setting it up -create characteristics & link to communication structure (ceban for pr)here we define which fields are used to determine the strategy tha

7、t will kick in. in our case we used plant and item value. not all fields in the pr can be used. for a full list of fields that can be used to determine the release startegy, see tcode se12 table ceban.so the two fields that will be used is:field ceban-werks forplantfield ceban-gswrt foritem valuewe

8、need to create a characteristic for every field. tcode ct04any characteristic name can be used. keep something descriptive to avoid confusion.for item value - lets create characteristic z_gswrtfirst go toadditional datatab and enter the table/field (and enter) enter currency to be used in thebasic d

9、atatab.also selectmultiple valuesandintervals allowedthe intervals allowed will allow us to assign a range of values, example: if pr value is 0 - 1000 usd .save the characteristicfor plant - characteristic z_werksagain, the table/field name in additional data to enter table/fieldagain set multiple v

10、alues and save the characteristicthe multiple values is to assign more than one plant to strategy, example: if pr for plant 3100andplant 3600 is .create class & link to characteristiccreate a class (simply to group the characteristics). again any name can be used. tcode cl01 - create class. the clas

11、s type must be 032.configure release proceduresabove actions was all master data. we now need to do some configuration. menu:img materials management purchasing purchase requisition release procedure procedure with classification set up procedure- (tcode omgq in older sap versions)create release gro

12、ups & link to classwe have two groups to create aa and ab. we need to indicate the class we are working with, in out case z_pr.create release codescreate all the release code / group combinations. this is all the dots in diagram above. so we have 4.later on, authorisation profiles will be linked to

13、these code / group combinations.release indicatorfirst we create the different statusses that the pr can be in throughout it lifecycle. later on (below), we will be linking using these statusses. here is the standard sap indicators, wou probably wouldnt need to add any.we will be using two of these

14、- x (block) and 2 (released) under the details section, you can indicate which documents can be created from this pr. for indicator 2, one can create pos and rfqs.withfield selectionyou can define which fields can be changed. this is the same indicator that gets used with document type configuration

15、 to make some fields read only, mandatory, hidden.set up strategies - strategy & codesevery line in our diagram above is a strategy. so we have threelets call them:group aa / startegy s1 - code l1 (for plant 0001)group aa / startegy s2 - code l1 & l2 (for plant 0001)group aa / startegy s2 - code l1

16、& l2 (for plant 0002)here are the settings for aa / s2 set up strategies - prerequisitesfor every strategy, we need to define a release prerequisites. this indicate if one code need to take place before the other. in this case, level 2 (l2) can only take place if level 1 (l1) has been released.set u

17、p strategies - statusthis is also done for every strategy. the screen is dependant on what groups were linked to the strategy as well as prerequisites that was set up. in this example:- if nobody release it then pr is block.- if l1 release the pr, the pr is still blocked- if l1 and l2 release the pr

18、, the pr can be converted to rfq/poout of interest, the reason why there is not a l2 only option is because of the setting in the prerequisites.set up strategies - values for strategiesthe values linked to strategies are master data (not configuration) and can be set in two places. either within the

19、 configuration itself - selecting the classification buttonor, in classification, example cl24n both methods work, the advantage of cl24n is that all the strategies can be viewed easier.set overall / item for doc type (pr only)for puchase requisitions, there is an option to release either on item le

20、vel or on document level. for po / rfq / contracts, one can only release on header level. back to the pr, it is highly recommended to use item release. this can be done in two places.firstly where the groups were created on the document type configuration for prconfig menu:materials management purch

21、asing pr define document types(for pr overall release, need to set the overall release indicator when creating or maintaining pr document type and at the meantime should create the a release strategy withsetting the overall release indicator.)create and allocate authorisation profilesin our example

22、we will have three people releasing, so three profiles will need to be created. authorisation profiles can be created using tcode pfcg.usage of pfcg are not being discussed here, but see below for relevant screen where the profile was created.- using release procedures -create a purchase requisitionlets create a pr, and see if the release procedure kicks in. in our case we will create