Restriction for PO release procedure

Dear All,
I have to restrict the PO release procedure.
Suppose there are only 3 person can release the PO but i have to restrict that 3 person for that PO quantity.
suppose, PO quantity 1000.
Person 1 --> Can release up to 1000.
Person 2 --> Can release 1000 to 5000.
Pesron 3 --> Can release 5000 to 10000.
Here quantity is 1000 ,
Then person 1 should release the PO and others should not.
and if quantity is 10000 ,
then person 3 should release and others should not release.
Right now in my client site anyone from this persons are able to release the PO.
So i want to restrict them by PO quantity.
Please let me know that, for this any BADI or User exit is available in system.(Or is there any customization need to be done and how)
If yes how to apply that, give me step by step procedure to solve the above issue.
Please give your inputs to come out of this problem.
Thanks & Regards,
Sanket.

hi,
in the exit i have mentioned ,use the import parameters which contains structures which has fields related to that u mentioned which r populated at runtime.
check tht fields in the structures for specific users u want to rstrict.
ex:
if sy-uame = < >.
else.
endif.

Similar Messages

How to configure release procedure for rate contracts release

Dear all,
How to configure release procedure for rate contract following are the requirements
they are two release codes c1 & c2 <=100000,>=100000
                if c1 is not there c2 has to be approved
     Change in the value of the rate contract contract
     Change in the validity of the rate contract
     Addition of deletion of line items
While using a non u2013 released rate contract in the PO an error message should shoot out.
Also the logic should be changed while using the rate contract in the PO.
The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
It should be possible to refer existing valid rate contracts in purchase orders.
Regards,
bhaskar

Hi,
In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
class in standard is the same FRG_EKKO, you can use the same for contract.
To distinguish if it's a contract or PO, EKKO-BSART can be used.
For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
You can restrict the document type to set up the release strategy for only contract.
Of cause, you can also create your own release class Z* for contract copying standard
one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
OLME:
-> contract
->Release Procedure for Contracts
->Define Release Procedure for Contracts
->Release Groups
If you have already created the PO release class.
Assign a new chracteristic of Document Category -BSTYP
Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES

Regarding releasing procedure for p.o.

hi sapgurus,
the configuration for p.o. release procedure is working perfectly but whenever i go to me29n or me28 i am getting two step release procedure but in industry if the manager has given excess to me29n/me28 then himslef ca release the p.o by means of clicking both release steps, that means without general manager review the manager can release the p.o by means of clicking both. hence i am willing to restricate each user's acess to other stepd release procedure.
examaple
in me29n/me28 :-
1) manager.
2) general manager.
in this case i want the manager to click on his resepctive release step and should not allow to acess the general manager's relase step's.
thanking you
praveer

hi,
please visit
www.sap123.com
there is a thread which explain very clearly for the release procedure for PO.
In PR (With classification0 there is only difference , you use CEBAN communication structure instead of CEKKO for PO)
Regards,
vijay

Release procedure for RFQ

Hello All,
I'm trying to configure release strategy for RFQ, but it's not working.
I have create characteristics for CEKKO-BSART,CEKKO-BSTYP,CEKKO-EKGRP,CEKKO-WERKS.
Have assigned objects to classes. Release indicators are assigned properly.
But in ME41 it is not getting activated. What could be the reason? I think I have made a mistake somewhere.
Thanks in advance,
Piyush

Hi,
Is it necessary to assign release code & release group to user id?
Because I have never done it for any release procedure uptill now.
Please explain the same.
Thanks in advance,
Piyush

Release Procedure in Indent/Purchase Order

I want to customise release strategy in indent and Purchase order in SAP. Kindly provide me steps to configure this. will apperitiate your efforts.
Manjit

Hi Manjit,
Release Procedure for Purchase Orders
In this section, you set up a release procedure for purchase orders (POs).
Requirements
If you want to use workflow to release POs, you must make the standard and basic settings for workflow (Basis -> Business Management -> SAP Business Workflow).
How do you set üp a release procedure for POs?
To set up the release procedure, you must make a series of settings in Customizing. This section provides you with an overview of the necessary activities.
You must perform the following steps:
1. Create characteristics and classes
For more on this topic, see Edit Characteristics and Edit Classes.
Note
If you wish to link your release procedure to workflow, you must perform steps 2 and 3 . You make these settings in Customizing for Business Workflow (Basis -> Business Management).
Otherwise, continue with step 4.
Define organizational plan
For more on this topic, see Edit Organizational Plan.
Assign standard tasks and activate event-receiver linkage.
For more on this topic, see Perform Task- Specific Customizing.
1. Set up release procedure for RFQs
a) Create release group
b) Create release code
c) Create release indicator
d) Create release strategy
Note
You need only carry out the following step if you wish to link your release procedure to workflow.
e) Assign release code to a user
For more on this topic, see Define Release Procedure for POs.
2. Check release strategies
For more on this topic, see Check Release Strategies.
Further notes
For more information, refer to
· Implementation of a Release Procedure for Purchasing Documents
· Release of Purchasing Documents (SAP Library -> Basis -> Business Management (BC-BMT) -> SAP Business Workflow (BC-BMT-WFM) -> Reference documentation -> BC Workflow Scenarios in the Applications -> MM Materials Management: Workflow Scenarios)
Edit Characteristic (CT04)
In this step, you create characteristics for a release procedure for purchase orders (POs).
Classification characteristics are the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchasing document (e.g. purchase order or RFQ).
Example
Release condition for release strategy EA:
Characteristic Characteristic value
Total net value of PO Above $10,000
If the total value of a purchase order exceeds $10,000, release strategy EA is assigned to this PO.
Requirements
In communication structure CEKKO you will find all the fields that can be used as characteristics for a release condition (e.g. BSART for the order type and GNETW for the total order value).
Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEKKO in the field Database table , and choose "Display".
Note
If you wish to define a separate release strategy for the various document categories (PO, RFQ, etc.), you must create a characteristic for each relevant document category.
Activities
1. Create a characteristic for each field from communication structure CEKKO that is to be a criterion for your release strategy. You have a free choice of names for the characteristic.
2. Enter the table name and the field name on the tab page Additional data (for example, table CEKKO for field GNETW).
Note
o Do not select any of the indicators in the area Procedure for value assignment on the tab page Additional data. Only if none of these indicators is marked can you assign a value or value interval to the characteristic when defining your release strategy.
o When you create a characteristic for a currency-dependent field (e.g. GNETW), a box appears in which you must enter the currency for the relevant value. The system then converts the currency of the purchasing document into this currency.
3. Check the data for the chosen field on the tab page Basic data.
If you want to enter several values or a value interval for a characteristic, set the Multiple values indicator in the area Value assignment.
Note
Value intervals can only be specified for numerical values (e.g. an interval of $10,000 to $15,000 for the value of the purchase order.
4. Check the texts for the field on the tab page Descriptions.
5. You can maintain default values for a characteristic on the tab page Values.
If you maintain values here, these values will be displayed as input help under Create Procedure with Classification -> Release Strategy -> Classification . If you wish to use not only the input help but also other values, you must select the Additional values indicator.
Note
You can also maintain ' ' as a default value. For example, for account assignment: ' ' for stock material, 'k' for cost center, and 'a' for asset.
6. If you want to restrict the use of a characteristic to particular class types, specify the relevant class types on the tab page Restrictions. For example, class type 032 for the release strategy.
Further notes
Further information on characteristics is available in this Customizing activity via Help -> Application help.
Customer exits
Customer exit M06E0004 enables you to change the communication structure for determining the release strategy for purchasing documents.
Edit Class( CL02 )
In this step, you create classes for a release procedure for purchase orders (POs).
You use a class to group together characteristics that are to constitute a release condition for a release strategy. In the step "Define Release Procedure for Purchase Orders " you assign this class to the release strategy.
Activities
1. Create a class with the class type 032. You have a free choice of names for the new class (e.g. REL_RFQ for the release of RFQs).
2. Assign a name for the new class on the tab page Basic data.
3. You can view an error message if different characteristics with identical values have been assigned to a class. To be able to do so, select the Check with error message indicator in the Same classification area.
4. If appropriate, select terms to be used as search criteria in searches for your class on the Keywords tab page.
5. Assign your characteristics to the class via the tab page Characteristics.
Further notes
Further information on classes is available in this Customizing activity under Help -> Application help.
Define Release Procedure for Purchase Orders
In this step, you set up the release procedure for purchase orders (POs) and can link it to workflow. (Note that in this context "releasing" means "approving", or giving the "green light" to a document.)
Requirements
· In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
· You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure ( Authorization Management -> Create Authorization Profiles and Assign to Users).Activities
Here you define the following:
·     Release group
·     Release codes
·     Release indicator
·     Release strategy
·     Workflow
Release group
Create a release group for your release procedure and assign it to a class. In the process, you assign release conditions to the release procedure.
Release codes
Here you create the release codes you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field
The Workflow indicator is also used to control role resolution:
·     "1 - Role Resolution with Group, Code and Plant (T16FW)"
Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
·     "9 - Role Resolution via User Exit"
Here you use the customer exit M06E0005 to define a role resolution of your own.
Release indicators
A release indicator shows the release status of a PO.
Via the following settings, you can define the release indicators you need for your release procedure:
·     The Released indicator is used to specify whether messages (PO documents in output format) may be transmitted for a purchase order with this indicator.
·     The Changeability indicator shows the effect of changes to the PO (a change to a PO may require a new release strategy to be determined, for instance).
·     By means of the Value change indicator, you can specify that the release strategy is to be re-started if a PO is changed and the value of a PO item thereby increases by a certain percentage (e.g. 10%). Set the Changeability indicator to "4 - Changeable, new release in case of new strategy or value change" or "6 - Changeable, new release in case of new strategy or value change/outputted" and enter a percentage in the Value change field.
Attention:
The following release indicators are necessary for every release procedure:
o     Release indicator for initial status
If the PO is subject to a release strategy, it must normally be released before it can be transmitted to the vendor. Therefore, when a PO is created, it is assigned a release indicator that blocks it from being outputted in message form.
The Released indicator must not be selected for this indicator.
o     Release indicator for released status
This indicator is assigned to the PO when it is released.
The Released indicator must be selected for this indicator.
Release strategies
Create a release strategy for your release group and assign your release codes accordingly.
·     Release prerequisites
With the release prerequisites , you specify the order in which the individual release points (individuals or departments) represented by the release codes may release the document.
Example
The following table shows release prerequisites for a strategy with four release codes.
Code/Release prerequisite
          01     02     03     04
     01     -
     02          -
     03               -
     04                    -
In this release strategy, the codes 01, 02, 03, and 04 must successively release the purchase order.
Read the table from left to right. For instance, the third line for release code 03: For code 03, release via code 01 and code 02 is a prerequisite. That is to say, the PO must be released via codes 01 and 02 before it can be released via code 03.
·     Release statuses
Here you specify the status a PO has after certain release points have effected release.
Specify which release indicator/status a PO is to have after having been released via a certain release code.
·     Classification
In classification, you maintain the values assigned to the characteristics. Via the characteristics and their values, you specify the POs to which your release strategy is assigned.
Maintain values (individual values or intervals) for your characteristics.
Example
Two characteristics and their values have been maintained in classification for release strategy 'EA':
- Document type - 'NB - standard purchase order'
- Total value - above $10,000
All POs with the document type 'NB' and a total value in excess of $10 ,000 are thus subject to a release procedure with the release strategy 'EA'.
·     Release simulation
The release simulation function enables you to check which status a PO will achieve with your release strategy if release is effected by a certain release point.
Choose "Simulate release" and release the document with the desired release code by double-clicking. The system shows you which status the PO now has as a result of this release.
Workflow
Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.
You can assign a processor ID either directly or indirectly:
o     Direct processor assignment:
Enter a user name.
o     Indirect processor assignment:
Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.
Customer exit
Customer exit M06E0005 enables you to define your own role resolution which determines the person responsible for releasing purchasing documents in workflow.
Further notes
Further information on how to set up a release procedure linked to workflow is available via the menu options Help -> Application Help.
Check Release Strategies
In this step, you can check whether the basic settings for your release strategy are complete and correct.
Checks
The following checks are carried out for purchasing documents:
·     Basic checks
The system checks whether the necessary release groups exist in the system. For example: Whether a release group has been deleted even though an associated release strategy still exists.
·     Checks regarding release groups and release classes
The system checks whether the release groups and the assigned classes have been maintained correctly. For instance, whether
o     A class has been assigned to the release groups and whether it exists in the system
o     Characteristics - which exist in the system and are linked to the communication structure - have been assigned to the class
o     A customer exit must be maintained for a characteristic
·     Checks regarding release codes
The system checks whether the release codes have been maintained correctly
·     Checks regarding release indicators
The system checks whether the release indicators have been maintained correctly. For example: Whether release indicators exist for the statuses "Blocked" and "Released".
·     Checks regarding release strategies
The system checks whether the release strategies have been maintained correctly. For example, whether:
o     Release codes have been assigned to the release strategy
o     The relevant release indicators have been assigned to the initial and final statuses of a release strategy
·     Checks regarding link to workflow
The system checks whether the link between your release procedure and workflow has been maintained correctly. For example, whether:
o     A processor (member of staff responsible for processing) has been assigned to a workflow-relevant release code and is defined in the organizational plan
o     A customer exit is necessary for the role resolution
Result
The result of these checks is displayed in a log. Further information is available in the Customizing activity under Help -> Application Help.
Activities
1. Start the check by performing the Customizing activity.
2. Check whether any error or warning messages are displayed.
3. If necessary, correct your Customizing settings for the release procedure.
4. Re-run the check after making corrections.
Rewards if Helpful
Regards
Sanjay L

Customisation for PO Release (different Values for different Doc Types)

Dear Experts,
I need to configure for PO release procedure where in the Characteristics would be Plant (2 Plants), Doc Type (3 types - Standard PO, Imports PO & Capital PO) and Value (2 stage release: 0-100000 & >100000 INR for Std PO, 0-200000 & >200000 INR for Imports PO and 0-300000 & >300000 INR for Capital PO).
Please let me know where I shoud define the different Values for different Docs for the Release procedure to work properly.
Or let me know the entire procedure for achieving the same.
Regards,
MNP

Hi MNP,
You have to create different CLASSes in IMG with the possible combination of different characteristics,
EX. CLASS EKKO11 - Plant A, Doc type- Std PO, Value- 0-100000 & >100000 INR
CLASS EKKO22- Plant A, Doc type- Import PO, Value- 0-200000 & >200000 INR
CLASS EKKO33- Plant A, Doc type- Capital PO, Value- 0-300000 & >300000 INR and same for other plant
then assign these classes to the respective Release group.
regards,
Pravin

Release Procedure without Classification

Hi Experts,
i have create a release strategy for the release procedure without classification, which PR document type i use for this? NB?
Do i need to assign a PR document to this release procedure?
Thanks

Hi Chun,
You can not use one release strategy with classification and one more without classification at a time in the system. Only one will work.
For your case, already you have Overall release, and I suggest you go for second class with Itemwise release. With classification, it's possible to use two release strategies at a time based on the document type. ("Overall Release " check box for document type)
Umakanth

Problem on PO release procedure

Dear all
I have some difficulties over Release procedure.
I have to apply release procedure on contract and standard purchase orders and i successfully completed the configuration of release procedure on contract.
For release procedure on PO, i created the required class and charaseristics.
I am getting confusion while maintaining release group.
for contract i have maintained the release group as under.
Rel Grp Rel Obj Class Description
02 2 Z_CONTRACT_RELPROC Contract Release procedure
Kindly guide me what to be maintain in release group for PO release procedure.
Thanks & Regards
Prasant sekhar

Hi,
You can not assign More than One Class to "Release Groups".
Create all the Characteristics for RFQ, Contract, PO etc for CEKKO table ...
Then Assign all these Characteristics to a Class...
Then maintain
Release Groups
Release Codes
Release indicator
But Create Diff Release Strategies for RFQ, Contract & PO...
for each Release Strategies you can maintain Same Release Group or Diff Release Group..
whenever you are trying to create Release Strategie, You will Blank Characteristics for that "Release Strategies",
There you can select the parameters.
Thx
Raju

SAP MM ( Release Procedure & STO )

Pls. help me answering the question :
1. What is the basic difference between PO release procedure and PR release procedure though the process are same ?
2. Define the steps for multiple release procedure .
3. What is purchasing document type in STO ?

Hi
The Difference between
   PR Release                                   and            PO Release
1.Header level and Item level                             Header level only
2.With and w/o Classification                            With Classification
Doc type for STO UB and Item category is U
Regards
AKM

Release Procedure - Initial Setup

Hi All,
I have a PR release procedure, as well as a workflow with email notifications, completely setup and working in our sandbox server. However, it has been several months since I configured the initial PR release, and now I am going to re-do the work in our development server.
I've re-done the customizing for the PR release in SPRO, but no release strategy is appearing in the PR. I've gone back and checked that the customizing of the release classes/characteristics/groups/codes/strategies are all identical... is there some initial configuration (any notes, activations, etc) besides this that I forgot to do this time? It's just a simple release based on user and item price. Easy to do, but for some reason it's not working.
Thanks for any help!

Hi,
First check all the basic settings for PR release procedure
1. characteristics
2.class
3.Release codes
4.Release strategies
5.classification data
Most imp check for
check if the user exit contains the line E_CEBAN = I_CEBAN
I have faced the same problem and checked few notes.
Hope if u do the above change in user exit ur problem will be solved
regards,
Uzair Hussain
Edited by: Mohd Uzair Hussain on Jun 19, 2009 8:30 PM

How restrict the release procedure tab in ME21N

Hi,
We have the Condition tab for free goods Iin PO.
Now, we want to implement release procedure in PO, and also restrict the release procedure for free goods in the same based on the combination of document type (EKKO-BSART) and free goods (USMON)field. Please provide the solution.
Regards,
Mars.

Hi
Try using the exit M06E0004.
Regards
Shiva

PR release procedure for material types

Hi all,
I have a question, I created new release procedure for combination :
1. NB pur.requsition, purchasing group + material type (let sey roh.. etc)
2. YNB pur.requsition, purchasing groups + material type (ZSTE-001, ZSTE-002, ZSTE-003).
- 3 characteristcs for pur.groups, doc.type and material type.
- 1 class
- 2 release groups (E1 and P1)
- For release group P1, In rel.strategy in classification I entered values for pur. requisition (NB), purchasing groups (001,002, 003 ect) and material types (ZUSL-001.. ect)
- For release group E1, in rel. strategy in classification entered values
values for pur. requisition (YNB), purchasing groups (001,002, 003 ect) and material types (ZSTE-001, ZSTE-002, ZSTE-003)
So, problem is that if I enter pur.requisition YNB and material type ZSTE-001, needs release; if I add item with material type ZUSL-001, there is no release.
How can I restrict the values so that is giving error if by mistake is entered between material types ZSTE-001, ZSTE-002, ZSTE-003 material type ZUSL-001 in document type YNB, which is not allowed to be entered?
Thanks in advance,
Anchi

Hello
In PR you can set up this release strategy without classification release strategy.
w/o classification strategy you can define the release line item wise. so you can give diiff materual group you can enter with line item wise.
Laxman

MM - ML81N, Release Procedure for service entry sheet

Hi Gurus,
I would like to active the realease strategy for service.
in order to customize I set:
-Relase Groups
-Release Codes
-Release indicator
-Release startegues
Then I run ML81N TRX and I called a sheet to try. This sheet had to has done to one of the release strategy set...
on the menu (of this trx ML81N)Entry Sheet->Set Status->Release (is still turn off)
Where is the problem?, anybody could help me?
Tks in advance,
Nacho

Hi,
please read the FAQ note 672719, question 5:
Setting up a release procedure is explained in the following short
example: All service entry sheets with material group 007 are supposed
to be subject to a release strategy. This release strategy requires that
the service entry sheets must be released with release code A1. Only the
cost center manager has the authorization for release code A1.
A) Create a characteristic for the material group:
o Call Transaction CT04. (Path in the SAP menu in R/3 Enterprise:
       Cross-Application Components -> Classification System -> Master
       Data -> Characteristics)
o Specify a name for the characteristic, for example CESSR_MATKL,
       and choose the 'Create' pushbutton.
o On the 'Basic data' tab page, enter a description and keep the
       'Released' status.
o On the 'Addnl data' tab page, enter table name CESSR and field
       name MATKL (Material group).
o Enter class type 032 (Release strategy) on the 'Restrictions' tab
       page and then save the characteristic.
Note: The release strategy must be based on a field of structure CESSR.
Using Transaction SE11, you can display which other fields are available
in addition to the material group (field MATKL).
B) Create a class to which you assign the characteristic:
o Call Transaction CL02. (Path in the SAP menu in R/3 Enterprise:
       Cross-Application Components -> Classification System -> Master
       Data -> Classes)
o Enter a class name, for example FRG_ESSR, and class type 032 (for
       release strategy) and then choose the 'Create' pushbutton.
o On the 'Basic data' tab page, enter any name. (Keep the
       'Released' status.)
o Enter characteristic CESSR_MATKL on the 'Char.' tab page and then
       save the class.
C) Now carry out the required Customizing settings. Follow IMG path
(Transaction SPRO) 'Materials Management -> External Services Management
Seite 4
-> Define Release Procedures for Service Entry Sheet'
o At first, you must create a release group (for example 03). For
       that, choose 'Release Groups', then choose 'New Entries', enter
       'Rel. Group' = 03 and 'Class' = FRG_ESSR. Save the entry. The
       system automatically determines value 3 (for entry of services
       performed) for the release object.
o Now create release code A1 for release group 03. Choose 'New
       Entries' and specify the following values: Grp = 03, Code = A1,
       and description, for example cost center manager.
o Create two release indicators, for example A and B. Select the
       'Released' field for release indicator B and save the entries.
       (Note: A release strategy must at least contain two release
       indicators. The first indicator (here A) must be defined as
       locked, the last indicator as released. Furthermore, the general
       changeability of the service entry sheet and the behavior for
       value changes are defined via the release indicators.)
o Finally create the release strategy. Choose 'New Entries' and
       specify the following values: Release group = 03, release
       strategy, for example RS, release codes = A1. Assign the two
       release indicators A and B via 'Release statuses'. Assign
       material group 007 via 'Classification'. Save the release
       strategy.
D) Assign the authorization for release code A1 and release group 03 to
the cost center manager. In role maintenance (Transaction PFCG), you can
for example use the default values for Transaction ML85 for that.
Regards,
Edit

Error in Release procedure for PO

Hi
I have created a release procedure for Purchase groups and plants. But now I want to add a new Purchasing group to the same strategy. How to do this.

Hi Garapati,
Release strategy is configuration in customisation screen. Do not merely do assignment of object via CL20N or CL24N. Though assigning the object would work, but is better to do it in customisation.
Go to this path: -
SPRO>IMG>Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Order (Execute)-->Release Strategies
Go to: Position>Identify the Group> Identify the Release Strategy code
(How to know what is the release strategy code? In the PO where a release strategy for this value and characteristic is triggered, you can go to the Header-->Release Strategy tab, you would be able to see that the release strategy is triggered. Simply remember the release strategy code. If you already know the code, ignore this step)
When the search is complete and located the right release strategy that you want to amend, select it and click on Details.
Inside, go to Classification. Check that this release strategy contain the characteristic that you want to amend. You would be able to see the Characteristic "Purchasing Group" already maintained. Click on Purchasing Group line and click on "Add rows" icon below, then key in the the Purchasing Group value that you want to add.
Hit Back, and then Save this customisation.
Now, the PO release strategy will trigger the Purchasing Group you just added if the PO details entered matched the Purchasing Group, Plant and Document Type value that you maintained for this release strategy.
Hope this helps.
Rgds.

With classification release procedure for PO

Dear Experts ,
here one issue is with classification release procedure for PO
when I create characteristics
in Additional data
table name :-- Cekko field name :-- match code
enter
click all sec charars then which block I select to go next screen
and fill name is right or ?
please help me

hi,
in additional data field you have to give the field name of characteristic you are maintaining. like if you want to maintain characteristic as document type of the PO then we have to give the field name for document type mentioned in table CEKKO i.e. BSART.
then you have to do the value assignment. here you have to tick the check box for "NOT READY FOR INPUT".
JASH

Restriction for PO release procedure

Similar Messages

Maybe you are looking for