Release procedure in POs and classes.

Hi,
in SPRO, Logistics - General, Materials Management, Purchasing, Purchase Order, Release Procedure for Purchase Orders, Edit Class, I see a long list of class.
If 032 is specific for a release strategy what are the others classes useful for ?
Best regards

Hi,
To work with workflow you have to define work flow at the time of Release code creation then with respective role has defined & assigned to the concerned user.
Regards
Ravi shankar.

Similar Messages

Release procedure in POs.

Hi,
what is the difference in purchase order strategy between Characteristic and Class ?
Best regards

Hi,
Check your settings with the below Link
http://www.sap123.com/showthread.php?t=59
Characteristics are features / values defined on which release stratergy should be applied.
Class is where all the characteristics are assigned a single class..
This class is in deed assigned to release groups and the release groups to release stratergies
Thanks & Regards,
Kiran
Edited by: Kiran. V on Jul 3, 2008 11:57 AM

Release procedure for PR and PO?

why a PR can be released at both item and header level whereas a PO can only be released at header level?

Hi,
Which version you are using right now in 4.6c/4.7/ECC.
As of ECC version you cann't define the PR release strategy at the Header level, which has some drawbacks on that.
You can define at the item level only.The reason behind this is
In PR several line items can be included in PR and may be of the different value & different department also for the same material from the same vendor if you define at the Header level then total value will consider of all the line items so it is difficult to assign to who the concerned release codes.Individual User department can release at the item level.
But in PO you will place the order to single vendor so if you define the release strategy at the header level ,because you are placing the PO to one vendor so the total value goes to the single vendor only. Thats why in PO it is at Header level.So any particular Purchasing department can release for the total value.
rgds
Chidanand

Class type in release procedure

Dear gurus,
pls explain class type significance in release procedure?

Purpose
The class type is a central concept in the classification system. The class type determines how classes are processed, and how objects can be classified and retrieved in these classes. In Customizing for Classification, you define the settings for a class type. You define class types for a specific object type, such as materials. You can then use classes of this class type to classify objects of this object type.
When you first create a class, you must enter a class type for the class. Each class type is a closed system. There is no link between the different class types.
Features
The class type determines the following:
Which object types you can assign to a class
Which class maintenance functions you can process
Whether you can classify objects in more than one class
Which class statuses, organizational areas, and text types are supported in class maintenance functions
Whether you can use engineering change management for classification
Which filter functions you can use to restrict the search result
Class types 001, 300, and 200 are defined for materials. In Customizing for Classification, you define the settings for a class type.
All materials can be classified with class type 001. Class type 300 is for variant configuration. Class type 200 is for classes that are used as class items in bills of material. You can classify the same materials separately in these class types.
You can use class type 012 to classify characteristics. This class type is defined only has the Keywords, Characteristics, and Texts screens in class maintenance functions. You can only classify characteristics in characteristics maintenance functions you cannot use the assignment functions in the classification menu. In this case the indicator Classify master record only was set. No organizational areas were maintained for the characteristics. For this reason, if you create a class of class type 012, you cannot select any organizational areas.
hope it gives you some information.
Regards
Seema

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

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

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

Release procedure triggering for fields not classified

Hello experts,
The classification for release procedure for PO in our current system are using 3 fields:
1) Company code
2) P.Org.
3) Currency : >0 currency unit
Now, when we change an existing text in the PO, no release procedure is triggered. But in case, if we add a new text to the PO (any new text at header or item level), the release procedure is triggered and goes for approval. Please guide me as why the addition of text to a PO is triggering the release procedure and what should I do to avoid so.
Thanks.
Richa

Hello Biju,
The reply from ABAP team is as below:
I checked all enhancements mentioned by you in trailing mail.
No active code logic found. "
Thanks.
Richa

Creating a new "Class type" in release procedure.

Hi guys,
how can I create a new <b>"Class type"</b> in release procedure?

Hi,
But I do not know why anyone would create a new batch type for release strategies, it is totally unnecessary and provides no additional options. The class type indicates which objects can be classified and there is already one for release strategies.
You can create a new class or add characteristics to the existing class used in the release strategy anyway.
Ther is also NO WAY that two classes can be used in the release strategy and this new class type would not change this either???
Steve B

Release procedure problem and error

Dear Friends ,
I facing some major problems in release procedure , i had configured one release procedure in 4levels , due to some reason i had deleted 3release groups and codes due to it was not working . But after deleteing in purchase order it showing all release level and only firest level is working unable to make MIGO and other release levels are not working . The relese code which i had created is appearing in RFQ/CONTRACT etc automatically . I had not created for this any release level . It's very very different case ....till date never faced and heared . How to resolve this probelm . Due to what reasons this kind of problems occurs .
RB

Hi,
Try to delete all the release procedure available in the system.
First try to do the documents coorectly and configure.
You might have done mistake in assigning the charcteristics to the class
Please try create a NEw release procedure once again.
Don't worry about the procedure in the RFQetc...
G.Ganesh Kumar

Reg. Characteristics and Class for PO release stretagy

Dear Experts
We want to release PO, what should be the Characteristic and Class, how to create the both. Pls advise the required table and class name.
Thanks
Rajakumar

hi,
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 like PURCHASE ORDER.
you can find it under menu path:
SPRO > MATERIAL MANAGEMENT > PURCHASING > PURCHASE ORDER > RELEASE PROCEDURE FOR PURCHASE ORDER > EDIT CHARACTERISTIC.
you can create charateristic based on plant,document type,value,purchase group.
In the basic data screen we have to enter the following inputs.
1DESCRIPTION                     PLANT
2STATUS                                     RELEASED
3DATA TYPE                     CHARACTER FORMAT
4NUMBER OF CHARACTER     4
5VALUE ASSIGNMENT     MULTIPLE VALUES
In the description screen we have to enter the language and description
In the restrictions screen we have to enter the class type.
Class type is the top-level unit of control for classes
The class type is used to define a number of parameters, such as:
u2022     The objects that can be classified in a class.
u2022     Whether objects of different object types can be classified in the same class.
u2022     Whether an object can be classified in more than one class of the same class type.
u2022     The class maintenance screens that can be processed.
Each class must be assigned to exactly one class type. There is no connection between the individual class types.
In the restriction screen we have to enter class type u201C032u201D.
We use a class to group together characteristics that are to constitute a release condition for a release strategy. In this step we assign this class to the release strategy.
menu path is : SPRO > MATERIAL MANAGEMENT > PURCHASE ORDER > RELEASE PROCEDURE FOR PURCHASE ORDER > EDIT CLASS
there should be only one class for all the release procedure.
for po the table is cekko and for pr it is ceban
jash

Help to modify the Release procedure without disturbing the existing class

Hi All,
We have a requirement to modify the existing workflow approval procedure for PR and PO to include a case, where the PO amount is less than certain value (say 100 EUR) and the material group is equal to certain value, then we need to include the approval levels L2 (defined for PR) and X2 (defined for PO).
Taking the case for PO`s, please note the following information,
Existing release Strategies & release Levels for PO are
51          Level X4
52          Level X4 + X3
53          Level X4 + X3 + X2
54          Level X4 + X3 + X2 +X1
Characteristics used
Total Net order Value
Purchasing organization
Order Type
Purchasing Group
Example : If the PO triggering a Release strategy 51 and if the conditions PO Value and Material Group satisfied then in addition to X4 system should send the PO Approval to X2 also. Similarly if the Po triggering the Release strategy 52 then in addition to X4 + X3, approval from X2 also required (provided if the condition satisfies).
Solutions tried
1) We can achieve the requirement by adding a dummy variable in the Characteristics and defining the new release strategy 55 with Level X4 + X2 and using the User Exit EXIT_SAPLEBND_002 .But we donu2019t want to touch the Characteristics and class because this is used by other companies also.
2) Also we can add a characteristic Material group with value equal to the required value and define 2 new release strategies 55 with Level X4 + X2 and 56 with Level X4+ X3 +X2.For all the other release strategies we can maintain the material group value as blank. Since the characteristics used by many companies we donu2019t want this option also.
Request your valuable suggestion to meet the above requirement, without disturbing the existing characteristics and Classes, would be highly appreciable.

>
MadhanRaj S wrote:
But we cannot use those because these are used by other companies of the same organization.
>
> We need a solution other than these two options with out disturbing the existing charecteristics and class.
It looks to me like you need a new release strategy for the company that is different. This is a perfectly normal way to use release strategies and is exactly what they are designed for.
Cheers,
Mike

How to close an open PO of partial GR and release procedure

Hi friends,
I would like to know how to close an open PO where partial GR has done on it and release procedure exists for that particular PO.
I would also like to know if Invoice is not done for a PO and GR is done, then can we call it as open PO?
Please clarify
Thanks
Jyothi

hi antony..
thank u antony a lot...i ve tried it and working fine..
but can we go in me22n to tick delivery complete for a PO which has already been released? it is showing "u cannot make change because it has already been output
regards,
jyothi

Work Flow and Release procedure

Hi,
What is the coorelation between the Work flow and Release Procedure in the MM Module.
Where exactly they both correlate ????
Where the Release Procedure stops and where the Work flow takes over ???
If with an example it wud be easy.
wth rgds
SVU123

check
/people/sapna.modi/blog/2007/02/19/workflows-for-dummies--introductionpart-i
/people/sapna.modi/blog/2007/04/27/workflows-for-dummies--workflow-builderpart-ii

Release procedure in POs and classes.

Similar Messages

Maybe you are looking for