Purchase Requisition (PR) is an internal purchasing document in SAP R/3. It is used to give notification to responsible department (purchasing/procurement) of requirements of materials and/or external services and keep track of such requirements. PR must contain information about quantity of a material or a service and the required date.It can be created directly (manually, through ME51N T-code) by a person or indirectly by another SAP component (such as material requirement planning/MRP, maintenance order of Plan Maintenance/PM module, production order of Production Planning/PP module).PR then can be processed to be an external purchasing document (such as Purchase Order/PO) or internal purchasing document (such as Stock Transport Order/STO).In SAP R/3, PR can be processed directly to be PO/STO or must be approved/released before it can be processed to be PO/STO.

If we want that PR must be approved/released before it can be processed to be PO/STO, we must set up a release procedure for that PR.The first thing to do in setting up a release procedure for a PR is to decide whether we will approve/release that PR for:

Overall PR

If we release a PR, all items in that PR will be released and then can be processed to be PO/STO. If we don’t release it, none of its item will be released nor can be processed to be PO/STO. Or,

Item-wise

We must release item per item of a PR in order to make them ready to be processed to be PO/STO. If we don’t release some of PR items, the other items can be released and processed to be PO/STO.

In an SAP R/3 client, all PRs with a particular PR Document Type can use just one of the above options. If we have more than one PR Document Type, we can set some of them use “Overall PR” release procedure and others use “Item-wise” release procedure, depends on our business process needs.We can set the option in the process “Define Document Type” of Purchase Requisition that can be accessed by “OMEB” T-code or through menu paths of “SPRO” T-code: Materials Management – Purchasing – Purchase Requisition – Define Document Type, as per below image:

If we want that a PR Document Type use “Overall PR” release procedure, we must tick the “Overall release of purchase requisitions

(OverReqRel)” indicator. If we don’t tick that indicator, it means that PR Document Type will be released with “Item-wise” procedure.The next thing to do is determining the criteria/parameters of PR that must be approved/released by specific person. For example:PR of raw material that has value less than USD 50,000.00 can be released by operational manager. PR of that item that has value USD 50,000 or more must be approved by operational manager and operational director. PR for production equipment must be approved by Asset Manager and operational director, whatever its cost.In SAP R/3 there are two release procedures that we can choose:

1.Release Procedure without classification

This procedure can only be used for “item-wise”. It can’t be used for “Overall PR”. The criteria that can be used with this procedure to distinct the PR approval processes are limited to: PR item value, material group, account assignment, and plant. We can’t use this procedure if we want to distinct the PR approval process by other criteria such as Purchasing group, document type, storage location, or something else.The only reason we should use this procedure is its simplicity. But if we want more flexibility in determining the PR release procedure we should use the other option. In this Step we won’t explain the “Release Procedure without classification” in detail. We will explain the other option (Release Procedure with classification) in detail.

2.Release Procedure with classification

With this procedure, we can choose whether we want to release the PR for “Overall PR” or “item-wise”. And the main reason why we should use this procedure is because we can choose more criteria to distinct the PR approval process. The criteria are not limited to PR item value, material group, account assignment, and plant only.

SAP R/3 has provided a communication structure “CEBAN” that we can use to make criteria/parameters to determine the PR approval process. Each field in “CEBAN” can be used as parameters. These parameters must be defined in SAP R/3 as a “Characteristic”. Some “characteristics” that are used as parameters to determine a release condition for a release strategy can be group as “Classification”.

The fields of “CEBAN” communication structure are:BSART: Purchase requisition document typeBSAKZ: Control indicator for purchasing document typeESTKZ: Creation indicator (purchase requisition/schedule lines)EKGRP: Purchasing groupERNAM: Name of Person who Created the ObjectERDAT: Date on which the record was createdAFNAM: Name of requisitioner/requesterTXZ01: Short textMATNR: Material numberEMATN: Material number

WERKS: PlantLGORT: Storage locationBEDNR: Requirement tracking numberMATKL: Material groupRESWK: Supplying (issuing) plant in case of stock transport orderMEINS: Purchase requisition unit of measureBADAT: Requisition (request) dateLPEIN: Category of delivery dateLFDAT: Item delivery dateFRGDT: Purchase requisition release datePSTYP: Item category in purchasing documentKNTTP: Account assignment categoryLIFNR: Desired vendorFLIEF: Fixed vendorEKORG: Purchasing organizationVRTYP: Purchasing document categoryKONNR: Number of principal purchase agreementKTPNR: Item number of principal purchase agreementINFNR: Number of purchasing info recordDISPO: MRP controllerBWTAR: Valuation typeBMEIN: Order unitKANBA: Kanban indicatorBPUEB: Adopt requisition price in purchase orderUSRC1: User field format character for release strategyUSRC2: User field format character for release strategyUSRN1: User field numeric for release strategyUSRN2: User field numeric for release strategyGSWRT: Total value of item.INCLUDE: Communication Structure: Requisition Release for User ExitPDUMMY: Dummy function in length 1.INCLUDE: Release Strategy: Account Assignment FieldsSAKTO: G/L account numberGSBER: Business AreaKOSTL: Cost CenterVBELN: Sales and distribution document numberVBELP: Sales document itemVETEN: Schedule lineANLN1: Main asset numberANLN2: Asset sub-numberAUFNR: Order NumberWEMPF: Goods recipientABLAD: Unloading pointKOKRS: Controlling AreaKSTRG: Cost ObjectPAOBJNR: Profitability segment number (CO-PA)PRCTR: Profit centerPS_PSP_PNR: Work breakdown structure element (WBS element)NPLNR: Network Number for Account AssignmentAUFPL: Routing number for operations in the order

IMKEY: Internal key for Real Estate objectAPLZL: Internal counterVPTNR: Partner account numberFIPOS: Commitment ItemFISTL: Funds CenterGEBER: FundDABRZ: Reference date for settlementPSP_PNR: Work breakdown structure element (WBS element)GSFRG: Overall release of purchase requisitionsGFWRT: Total value of requisition for overall release procedureWAERS: Currency KeyEvery time a user create a PR, SAP R/3 will pass the PR data (value of PR’s fields) to the corresponding fields of “CEBAN” communication structure. Then, based on the value in each field that we use as characteristics, SAP R/3 will determine which PR release strategy will be assigned to the PR.For previous example: if we choose PR item value and material group as characteristics, and the PR item value field (GSWRT) that was entered by user is USD 55,000, and the material group is “raw material” then this PR must be approved by operational manager and operational director.In this Step we have explained about the basic concept of PR Release Strategy procedure. In the next Steps we will show.

Scenario

A company has four plants (A000, B000, C000, and D000). Each plant has a stock controller and plant manager. Each plant produces specific sub-assembly and products, and they can be transferred from one plant to another. A000 also acts as the Head Office where Asset Manager and Operational Director perform their tasks.

All PRs created need to be released/approved by specific person according to the following conditions:

1.

Because usually they create a Stock transfer request/STR (PR with item category “U: Stock Transfer”) that contains a lot of items, they decide that STR needs to be approved by its supplying-plant stock-controller with “overall PR” procedure (header level).To make this procedure runs well, the company has an internal policy that an STR can contain only items with same supplying plant. If someone needs STR from two supplying plant, he/she must create two different PR. They also have created a PR document type that specific for STR. That document type only allows “U: Stock Transfer” item category.

2.

PR for external procurement (PR with item category other than “U: Stock Transfer”) needs to be approved with “item-wise” procedure (item level). The release strategy of the PR depends on the account assignment and the total item value.

o Item with “standard (inventory)” account assignment that has total value less than USD 10,000 needs to be approved by its stock controller.

o Item with “standard (inventory)” account assignment that has total value USD 10,000 or more needs to be approved by its stock controller and plant manager.

o Item with “Asset” account assignment needs to be approved by Asset Manager whatever its total value and wherever it’s requested.

o Item with “Cost Center” account assignment that has total value less than USD 5,000 needs to be approved by plant manager.

o Item with “Cost Center” account assignment that has total value USD 5,000 or more needs to be approved by plant manager and operation director.

Based on the above scenario we are asked to configure the PR release procedure.PR Release Strategies MatrixFrom the above scenario we know that we have to use both “Overall PR” and “item-wise” procedures. We also know the criteria/parameters that determine the release strategy (who has the authorization to release/approve PR). To make it easier to understand, we can make a release strategy matrix like the following tables:

Each row in the above “Release Strategies” tables is a release condition, which if a PR meets the condition, then associated release strategy will be assigned to that PR. For instance, if a PR meets condition at the first row of “Release Strategies” table for “item-wise” release procedure, then that PR needs to be approved by Stock Controller A.

The one thing that must be carefully considered in PR release procedure configuration is to ensure that all possibilities of PR parameter’s value combinations (all release conditions)

have been anticipated by PR release strategies. Once we determine the release conditions, if there are PRs which don’t meet any conditions, then that PRs will be considered that they don’t need any approval/release processes. So, they will be available to be processed to the next step (to become a PO or STO).

If we don’t want that happen (if we want all PRs needs to be approved), we have to ensure that each PR created must meet one of the release conditions. In our scenario, we can ensure that, for example, by creating a PR document type for STR that only allows “U: Stock Transfer” item category; and another PR document type that only allows “Standard”, “A: Asset”, and “K: Cost center” item categories.

After creating the PR Release Strategy matrix, then we start to configure it on SAP R/3. You can read Step by step SAP configuration for PR Release Procedure/Strategy.

PrerequisitesBecause we use both “Overall PR” and “item-wise” release procedure, we must distinct the document type of PR for each of them. So, we must create a PR document type for “Overall PR” release procedure, such as ZST, and another PR document type for “item-wise” release procedure, such as ZNB.

We can create PR document type by copying from SAP standard PR document type (NB) with “OMEB” T-code or through menu from “SPRO” T-code: Material management – Purchasing – Purchase Requisition – Define Document Type. We must tick the “Overall release of purchase requisitions” indicator for ZST document type.

Step 1 – Edit characteristicsCharacteristics are criteria/parameters that determine the release condition of release strategies of PR. If a release condition is satisfied, the associated release strategy is assigned to the PR.For PR Release Strategy we can create characteristics from fields that have been provided by SAP in “CEBAN” communication structure that has been explained in the previous Step about the basic concept of SAP PR Release Strategy.

From the matrix that has been created before in this Step, we know that characteristics that qualified for our needs are:

Item category (for Overall PR release) Supplying plant (for Overall PR release) Account Assignment (for Item-wise release) Total item value (for Item-wise release) Plant (for Item-wise release)

The corresponding fields of CEBAN are:

PSTYP: Item category in purchasing document

RESWK: Supplying (issuing) plant in case of stock transport order KNTTP: Account assignment category GSWRT: Total value of item WERKS: Plant

We can create characteristics: ZCEBAN_ PSTYP, ZCEBAN_ RESWK, ZCEBAN_ KNTTP , ZCEBAN_ GSWRT , ZCEBAN_ WERKS (or anything else name you like).The following SAP screenshots show step by step how to create a characteristic:

Through “CT04” T-code or menu from “SPRO” T-code: Material Management – Purchasing – Purchase Requisition – Release Procedure – Procedure with Classification – Edit Characteristics.

Input this field:- Characteristic: Name that uniquely identifies a characteristic.We make these 5 characteristics one by one: ZCEBAN_ PSTYP, ZCEBAN_ RESWK, ZCEBAN_ KNTTP , ZCEBAN_ GSWRT , ZCEBAN_ WERKS.

Push the “create” button as pointed by red arrow on the above image.

Go to “addnl data” tab Input these fields:- Table name: “CEBAN”- Field name: the corresponding field in “CEBAN” communication structure of the characteristic that we want to create.

Go to “Basic data” tab. Description and data type are copied from “CEBAN” communication structure.Input these fields:- Value assignment indicator: “Multiple values” if we want more than one value can be assigned to a characteristic, or “single-value” if we want only one value can be assigned to this characteristic. For our scenario, we should choose “Multiple values” for all characteristics.- Interval vals allowed: This indicator defines whether we can enter an interval as a value for a numeric characteristic. For “total value of item/ZCEBAN_GSWRT” characteristic we should tick this indicator. For other four characteristics we don’t need this indicator as their data types are not number/currency.

Go to “Values” tab. Input the values of the characteristic we make. We have determined these values in PR Release Strategies Matrix that we made in the previous Step, but for some fields (such as PSTYP), we must map them to the values that store by SAP and its table.ZCEBAN_ PSTYP values: 0 (for standard item cat.); 7 (for U: Stock Transfer item

cat.)ZCEBAN_ RESWK values: A000; B000; C000; D000ZCEBAN_ KNTTP values: A (Asset); K (Cost Center); blank (Standard)ZCEBAN_ GSWRT values: >=0; <5000;>=5000; <10000;>=10000ZCEBAN_ WERKS values: A000; B000; C000; D000

Go to “addnl data” tab Make sure that “Not ready for input” indicator is not selected.Click the “Save” button, and make other characteristics.

Step by step SAP configuration screen shots of how to create characteristics for PR release procedure for other characteristics (ZCEBAN_ PSTYP, ZCEBAN_ RESWK, ZCEBAN_ KNTTP , ZCEBAN_ WERKS).

Step 2 – Edit ClassesClass is a group of characteristics that constitute a release condition for a release strategy.From previous Step (part 2), we have created five characteristics that will be used to determine the PR release strategy, which are:

ZCEBAN_ PSTYP (for Overall PR release): characteristic for “Item category in purchasing document”

ZCEBAN_ RESWK (for Overall PR release): characteristic for “Supplying (issuing) plant in case of stock transport order”

ZCEBAN_ KNTTP (for item-wise PR release): characteristic for “Account assignment category”

ZCEBAN_ GSWRT (for item-wise PR release): characteristic for “Total value of item”

ZCEBAN_ WERKS (for item-wise PR release): characteristic for “Plant”

Because we will use both of “overall PR” and “item-wise” release procedure, at least we must create two classes. One class is for “overall PR” release procedure (such as “ZPR_Overall”) and other one is for “item-wise” release procedure (such as “ZPR_item”).ZCEBAN_ PSTYP and ZCEBAN_ RESWK characteristics must be assigned to ZPR_Overall class.ZCEBAN_ KNTTP, ZCEBAN_ GSWRT, ZCEBAN_ WERKS must be assigned to ZPR_item class.

The following SAP screenshots show step by step how to create classes:

Through “CL02” T-code or menu from “SPRO” T-code: Material Management – Purchasing – Purchase Requisition – Release Procedure – Procedure with Classification – Edit Classes.

Input these fields:- Class: class name that uniquely identified a class, such as: ZPR_Overall and ZPR_item. We will create these classes one by one.- Class Type: type of class. SAP standard class type of classes for PR Release Procedure is “032” (class type: Release Strategy). Other class types are used for different purpose such as batch management, equipment class, etc.

Click “create” button as pointed by red arrow in the above image.

Input this field:- Description: description of the class.

Go to “char” tab. Input this field:- Characteristics: characteristics that must be assigned to this class and will be used to constitute a release condition for a release strategy.For ZPR_Overall class, we assign ZCEBAN_PSTYP and ZCEBAN_RESWK characteristics.

Press “enter” or click button as pointed by red arrow on the above image.

Click “save” button, and then create another class (ZPR_Item).

Now we will explain step by step how to set up PR Release Procedure with classification. This can be done through “OMGQ” T-code or menu from “SPRO” T-code: Material Management – Purchasing – Purchase Requisition – Release Procedure – Procedure with Classification – Set Up Procedure with Classification.

From the above screen, we will perform four activities which are defining: Release group, Release code, Release indicator, and Release strategy. In this case study we don’t use workflow.

Step 3.1 - Set Up Procedure with Classification – Define Release GroupBecause we will use both of “overall PR” and “item-wise” release procedure, at least we must create two Release groups. One release group is for “overall PR” release procedure (such as “ZO”) and other one is for “item-wise” PR release procedure (such as “ZI”).

Click “Release group” button as pointed by red arrow on the above image.

Click “New Entries” button as pointed by red arrow on the above image to create new release groups.

Input these fields on the above screen:- Release Group: a two characters code that uniquely identified a release group.- OverReqRel indicator: indicator whether this release group is for “overall PR” release procedure or not.- Class: class that will be used form PR release procedure (created in previous Step (part3)).

Press “enter” or click the button pointed by red arrow on the above image.

Click “save” button and “back” button.

Step 3.2 - Set Up Procedure with Classification – Define Release CodeRelease code is a two characters code to identify the person who has the responsibility to review the PR (so he/she will approve/release or refuse to approve the PR). In the previous Step (part 1) we have created PR Release Strategy Matrix. From that matrix we know that there are 10 persons who have the responsibility to review the PR. We need to identify them by defining a release code for each of them, such as:

Stock Controller A : SA Plant Manager A : PA Stock Controller A : SB Plant Manager A : PB Stock Controller A : SC Plant Manager A : PC Stock Controller A : SD Plant Manager A : PD Asset Manager : AM Operational Director : OD

SA, SB, SC, SD release code are used in both of “overall PR” (“ZO” release group) and “item-wise” release procedure (“ZI” release group), while other release codes are only used in “item-wise” release procedure (“ZI” release group).

Then we need to configure these release code in SAP as follow screen shots.

Click “Release code” button as pointed by red arrow on the above image.

Click “New entries” button as pointed by red arrow on the above image.

Input these fields on the above screen:- Release group- Release code- Release code description

Press “enter”, click “save” button and “back” button.

Step 3.3 - Set Up Procedure with Classification – Define Release Indicator

Release indicator is an indicator that shows the release status of a purchase requisition. Each PR (or its item) that meet one of the conditions of PR release procedure (such as one of the rows in PR Release Strategy matrix that we have created in previous Step (part 1)) will be assigned with a release strategy and a release indicator.

The best practice in business (which decides that PR must be released before it goes to the next process) is each PR that has just created will be assigned a “block” release indicator. It means that we can’t process it to be RFQ/PO. That PR needs to be approved by specific person (specific “Release code” that we have created at previous Step (part 4)). After that person release it, that PR will be assigned new release indicator (can be “block” if the release strategy still needs the next person or release code to approve that PR; or ”release for RFQ and PO” if the approval process is completed).

Release indicator determines several things such as:

a. Release status of PR.It determines whether a PR can be processed to be RFQ and PO, or not; whether a PR can be changed by material planning (you can read our previous step to know more about materials planning) or not.

b. Field selection key.By assigning a specific field selection key for a release indicator we can specify which fields in a PR with this release indicator can be changed or must be populated. For example, we can set that PR with “blocked” release indicator can be changed its quantity and price field (so we can revise it before the approval process complete), and PR with “release for RFQ and PO” can not be changed its quantity and price field.We can define a field selection key for PRs with “OMF2” T-code or through menu in “SPRO” t-code: Material Management – Purchasing – Purchase Requisition – Define Screen Layout at Document Level.

c. Changes after start of release process.With the Changeability indicator, we can specify the effects of changes to a PR that has been assigned a release strategy to it. There are four possibilities:

1-Cannot be changed.We can’t change the PR data once it’s been assigned with a release indicator with this changeability indicator.

2-Changeable, no new determination of strategy.There are two conditions:

o If the PR has not been released before by any release code.If we change the PR data, such as quantity (so the item value also change), supplying plant, plant, etc, SAP will check the release procedure and will change the release strategy if the new data causes change of release strategy. For example: a PR is created for plant B000 with cost center account

assignment and the item value is USD 7500, so this PR will be assigned a release strategy that should be released by plant manager B and Operational Director. Assume that plant manager B has not released the PR yet. Then we change the item value of the PR, for example is USD 4500 and plant is C000. With this changeability indicator, this change will assign new release strategy (that needs to be approved by plant manager C only because the item value is less than USD 5000) to the PR.

o If the PR has been released before by any release code. If we change the PR data, such as quantity (so the item value also change), plant, supplying plant, etc, SAP will not check the release procedure and will not change the release strategy.For example: a PR is created for plant B000 with cost center account assignment and the item value is USD 7500, so this PR will be assigned a release strategy that should be released by plant manager B and Operational Director. Assume that plant manager B has released the PR. Then we change the item value of the PR, for example is USD 4500 and plant is C000. With this changeability indicator, this change will not assign new release strategy (although the plant change to C000 and the value become less than USD 5000), so it still needs to be approved by Operational Director.This can lead to a more serious problem. For example, another scenario. Assume that PR with cost center account assignment in plant A needs to be approved by:- plant manager A only for value less than USD 5000.- plant manager A and Operational Director for value USD 5,000 – 10,000- plant manager A, operational Director, and President Director for value more than USD 10,000.If we create a PR that has value USD 7500, then that PR will be assigned the release strategy that needs to be approved by plant manager A and Operational Director. Assume that plant manager A has released the PR. Then we change the value to USD 15,000. It should be approved by President Director. But with this Changeability indicator (2), the PR does not need to be approved by President Director instead it can be processed to be RFQ/PO as soon as Operational Director approve it.So, be careful using this no.2 Changeability indicator.

3-Changeable, new release in case of new strategy.This is same as the default value (blank) for “blocked” release indicator.We can change data of the PR, and the release strategy assigned to the PR will be changed if the change causes the new release strategy (even if the PR has been released before by any release code). Any release by any release-code before we change the PR (that causes a new release strategy) will be reset and release procedure will start from the beginning of the new release strategy.But if the change does not cause a new release strategy then the release procedure will not be changed.

4-Changeable, new release in case of new strategy or value change.This changeability indicator is similar with no.3-, but with an additional check. We can change data of the PR, and the release strategy assigned to the PR will be changed

if the change causes the new release strategy (even if the PR has been released before by any release code). Any release by any release code before we change the PR (that causes a new release strategy) will be reset and release procedure will start from the beginning of the new release strategy.Assume that we change the PR value but this change does not cause a new release strategy. Different with no.3-, this indicator will also reset any release by any release-code before we change the PR if the increase value exceeds the tolerance limit that we define in the customizing (e.g. 10%).For example: a PR is created for plant B000 with cost center account assignment and the item value is USD 8,000, so this PR will be assigned a release strategy that should be released by plant manager B and Operational Director. Assume that plant manager B has released the PR. Then we change the item value of the PR, for example to be USD 8500 (the same release strategy). SAP will check the increase of PR value. Because the increase is less than 10%, SAP will not reset the approval of plant manager B. This is the same if we use changeability indicator no.-3.But if we change the item value to be USD 8,900, SAP will reset the approval of plant manager B because the increase is more than 10% of the previous value (USD 8,000). So, the plant manager B has to release that PR again. If we use changeability indicator no.-3, the approval of plant manager B will not be reset.Maybe, this is the safest changeability indicator to be used in business.

SAP R/3 has provided a set of standard release indicator that can be used in most of PR release procedure, so we don’t have to define it anymore. In this case study we will not define other release indicator. The standard release indicator can be seen as follow:

Click the “details” button to display or change the selected “release indicator” details.

Input the field values and choose the indicators in the above image according to our business needs as explained before.

Click the “save” button and “back” button.

Step 3.4 - Set Up Procedure with Classification – Define Release StrategyIn previous step (part 1), we have defined PR Release Strategies Matrix. In the Release Strategies table of that matrix, we have identified all the possible release conditions. Each of condition must be released/approved by specific person (on the Approver 1 and Approver 2 field). A Release Strategy is a release condition and its corresponding approver. From the matrix, we define Release Strategies and identified each of them with a Release Strategy code, such as: A1, A2, A3, A4, A5, B1, B2, B3, B4, B5, C1, C2, C3, C4, C5, D1, D2, D3, D4, D5, AM as per following tables:

After defining the Release Strategies, then we need to configure these in SAP as the following screen shots.In this example we will define release strategy A5. This release strategy is for PR with item-wise release procedure (document type "ZNB" that we have defined in the previous step), “cost center” account assignment, “>= USD 5000” total item value, at “A000” plant. The PR that is assigned with this release strategy needs to be approved/released by Plant Manager A and Operational Director.

Click the “New entries” button to create a Release Strategy.

Input these fields:-Release group: Release group that corresponding with the release strategy. We have defined the Release group at previous Step (part 4).-Rel. strategy: Release strategy code that we’ve defined on the previous tables.-Rel. strategy description.-Release Codes: release codes which represent specific persons that responsible and able to release/approve the PR. We have defined Release codes at previous Step (part 4).

Click “Enter” or the pointed button on the above image.

Click “Release prerequisites” button on the above image.

With the release prerequisites, we can specify the order in which the individual persons represented by the release codes may release the document.In this example, the release code PA must release the PR first, so then release code OD be able to release it. In other words, release code PA approval is the prerequisite of release code OD approval.

Click “continue” button on the above image.

Click “Release Statuses” button on the above image.

Here we can specify the status a PR has after certain release points have affected release.We specify which release indicator/status a PR is to have after having been released via a certain release code.We have defined Release indicators in the previous Step (part 5).In this example:-If release code PA and OD have not released the PR, then the status of PR is “S: Blocked”.-If the release code PA has released the PR, but release code OD has not yet, then the status of PR is ”S: Blocked”.-If the release code PA and OD have released the PR, then the status of the PR is “2: Release for RFQ/purchase order”.

Click “continue” button on the above image.

Click “Classification” button on the above image.Here we can maintain the values assigned to the characteristics. Via the characteristics

and their values, we specify the PRs to which the release strategy is assigned. We have defined characteristics in the previous step (part 2).In this example we will assigned these values to the characteristics for this A5 Release Strategy:- Account Assignment category characteristic is assigned with “K: cost center”- Total value of item characteristic is assigned with “>=5000”- Plant characteristic is “A000”.The following screen shots show how to assign "K" value to the "Account assignment category" characteristic.

Then we have to assign the

appropriate values to other characteristics with the same way as per below image.

After all characteristics been assigned the appropriate values then click "back" button as per above image.

Click "save" button.

From the above explanation, we have defined “A5” Release strategy. Then we must define other Release strategies in a similar way that we have done before.

Once we have done this step, we have completed the SAP PR Release Procedure configuratijavascript:void(0)on. All PRs created in SAP will be assigned with one of the release strategies that we have defined.