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

Similar Messages

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 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

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

PO Release strategy, error: class POCLASS class type 032

All SAP Gurus,
We are configuring new PO release strategy.
When we go to Release strategy - classification
(Release procedure for PO - Define release procedure for PO - Release Strategies - classification)
It gives following error: Error in classification (class POCLASS class type 032).
Where we can maintain the classification?
Regards,

Dear,
Please follow bellow detail.
SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
Three steps involved in release process of purchase order.
1)     Edit Characteristic: -
Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP
2)     Edit Class: -
After creation of characteristic, create class for release purchase order. In which you can take reference of
Class Type: - 032,
Status: - Release,
Class group: - Release strategy class,
And put reference of your characteristic, which are created by you in first step.
E.g: - Class - REL_PO
3)     Define Release Procedure of purchase order: -
In this step four processes involved.
1)     Release Groups
2)     Release Codes
3)     Release indicator
4)     Release Strategies
1)     Release Group: - In which you can define release strategy group
For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
2)     Release code: - In which you can define release code. Enter value as
Release group: - 01,release code: -01 - Purchase Head,
Release group: -01, release code: - 02 - Auditor.
3)     Release indicator: - In this step you have to define release indicator.
Like X - Blocked, I - Under process, S - Release.
4)     Release Strategy: - This is the final step for release strategy.
Assign release code 01, 02.
Click on release prerequisites, select 02 - check box and click on continue.
Click on release status button, enter release indicator X, I, S and click continue
Click on classification button, Enter values of purchasing group for which you want to created release strategy.
Regards,
Mahesh Wagh

Release procedure is applyaing for all doc types

Hi all
I have configured release procedure for PO only for 2 document types, i have used EKKO-BSART structure name.and in values i have given only 2 document types, but the release applying for all document types of PO, plz help how to set to apply only that 2 doc types...
thanks
ramesh Reddy'

Hi,
Is there any other Char defined other then documents type.
For PO release with document type use CEKKO-BSART and then check the same.
Just change the field in Char and also reenter the char in the class.
Then reenter the class in the config and save and then try to simulate the release in ME21N with prefered documents types.
It will work.

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

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.

Release procedure for Purchase Requsition and especially f. a document type

Dear Experts,
how can I establish a release procedure. I need to set up the procedure
without classification. But it depends on a document type.
I have been to the customizing section with spro
Materials Management/Purchasing/Purchase Requisition/Release Procedure
and have choosen "Set up Procedure without classification. ".
But can I assign a document type and how is the handling generally with.
Release Codes
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Thanks
Ilhan

Hi Ramesh,
You are saying:
"Click on the Release strategy button under item tabs". Where is this button.
All what I have is: Tab for "Material Data", "Quantities", "Valuation", "Account Assignment",
"Source of Supply", "Status", "Contact Person", "Texts","Delivery Adress", "Customer Data",
on calling of Tcode me54n I get immediatly a message
"Purchase Requisition 5000000131 can not be released" although I didn't enter any number in it
Why does it refer to a PR Nr. generally . I think it is pre-filled- How can I call this transaction without this message ? Or how can I call this transaction so that I can type in my own Purchase Rq-Nr.
Regards
Ilhan

T.Code for Release Procedure for Purchase Order Type

Hi Frd
im working in ECC 6.0.
OMGS is t.code for Release Procedure for Purchase Order Type in SAP 4.6.
Can anyone tell me what is the t.code for Release Procedure for Purchase Order Type in ECC 6.0 .the OMGS t.code is not working in ECC.
Thanks
By
Pari

Hi Rajasekharan,
Go to tcode ME22 and enter the Purchase order number.
inside the Display screen,u can see a GREEN flag button on the Application Toolbar.
Click on a item and press the Green Button.
U will see the release code,provided the Purchase order is set to release strategy,after that Go to tocde ME28 enter the release code ,along with Document number and then release the Purchase order.
Actually the tcode for releasing purchase order is ME28
Reward points if useful.
Cheers,
Swamy Kunche

Service Entry Sheet Release Procedure

Dear all,
I want to assign a new Plant to an existing service entry release strategy. In CL20N for Class Type 032 and maintaining the Release Group and Release Strategy I want, I hit ENTER and the Class SERVICE_RELEASE is displayed, which is correct (it is a service entry release procedure).
Selecting the item and displaying the values for the Class, I have Plant, Order Type and Cost Centre. I added a new row, include a new Plant and hit Save. I get the message "Saving changes to assignments" and then I exit the screen.
However, to double check that the object has been assigned to the class, I check in SPRO>Materials Mgt>External Services Mgt>Define Rel. Procedure for Service Entry Sheet> Release Strategies to confirm that the object was created in the classification for service entry release procedure. BUT IS NOT THERE!
However, if I performed the assignment in Classification in SPRO for the release strategy, and check in CL20N, IT IS THERE!!
How come I have created in CL20N and it is not displayed in SPRO for the same release strategy? The object assignment was successful with no error msg. It is not possible that you have done it in CL20N and you have to do the same in SPRO, right? Doesn't serve the purpose..
Pls help.
Thank you.

Dear Sir,
Go to CL02 give the Class and Class type, click on change icon
Copy the characteristic of Plant from Char. Tab
Then Go to CT04
give characteristic which is copied from class and click on change icon.
enter your new plant in Values tab, Save back
Go to CL20N, give release group and release code for which you want to maintain the new plant.
give the plant and save enter.
i hope this will help you.

PR release procedure problem

We are using SAP 4.7 EE Version.
Regarding PR release procedure, I have created PR release procedure by using characteristics with Plant, Total value of the item, document type, creation indicator and account assignment category.
Created class PR_RELEASE with above-mentioned characteristics. The same is used in PR release procedure.
When I am creating PR, the release procedure not picking up for standard procurement (stock material) account assignment category.
We have identified the problem with account assignment category u2018 u2018 (Standard) while creating PR. For other account assignment categories (K, U, X, A), it is working fine.
Recommend any SAP note numbers if you have or known.
Points will be rewarded.
Thanks,
SK
Edited by: s k on Jun 9, 2008 2:11 PM
Edited by: s k on Jun 9, 2008 2:12 PM

Hi
Blank Account assignment does not work, as you cannot create a chracteristic Value as Blank.
You need to create a new release strategy without the account assignment category chracter.
Or remove the account assignment Chracterisitc from the release strategy
Thanks & Regards
Kishore

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

Purchase Order release procedure

Hi All,
My client is having following requirement for Purchase Order release procedure.
Plant 1                    -    1 Release code (Manager)
Plant 2             -    2 Release Codes (Manager, Sr Manager)
Plant 3             -    3 Release Codes (Purchase Officer, Manager, Sr Manager)
All plants are assigned to one company code. Please advise me how I can map above requirement in sap.
Thanks & Regards,
Nagi

Hi Nagi,
In PO Realease startegy configuration, you need to decide and select the Release objects for which the system should trigger release for the document. you should work with Characteristics for each object (Your requirement is for 3plants) so in one of your characteristic WERKS should be your field along with other characteristics based on your requirements such as Total Net Value, Doc type etc.
Create Characteristics in CT04 for the class type 032 and proceed maintaining the release Group and Release codes as per your requirement.
Refer the following thread and revert if any confusions...
http://**********************/2008/11/release-procedure-release-strategy-main.html
Regards
Shiva

Message Error in classification (class REL_PREQ_ITEM class type 032

Hi gurus,
Can anybody plz explain me to solve the following message. This comes when i hit the classification button in the release strategies step in the release procedure
Error in classification (class REL_PREQ_ITEM class type 032
Thanks
Anusha

I made changes to 4 strategies in the development client and they seemed to work fine. so i pushed them to quality system. and now out of the 4 startegies for two strategies i get this message. When i mean i changed the strategy in the development client, i refer to the characteristics on the classification of a release startegy, i replaced a purchasing group and changed the dollar amount out of the chracterisitics doc type, account assignemnt category, total dollar value, purchasing group and plant. I tested to make sure that the release startegy kicks off when all the conditions are met for that startegy in pur req in the development environment. But now this does not happen in the quality system. I get that message and also the release startegy is not getting kicked off in the quality environment
Thanks
Anusha

Class type in release procedure

Similar Messages

Maybe you are looking for