on 09-25-2008 12:37 PM
Dear All,
What is characteristic and class in configuration of release strategy ??
Regards,
Rajesh Kumar
Hello
In R/3 classification, characteristics describe the properties of objects. The values of a characteristic specify these properties.
Characteristic COLOR has the values 'red', 'green', and 'blue'. When you classify an object, you use this characteristic to specify the color of the object.
Class:
The classification system allows you to use characteristics to describe all types of objects, and to group similar objects in classes u2013 to classify objects, in other words, so that you can find them more easily later.
You then use the classes to help you to find objects more easily, using the characteristics defined in them as search criteria. This ensures that you can find objects with similar or identical characteristics as quickly as possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear,
You can create release stretegy with below mention details.
For purchase Order: -
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 u2013 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 u2013 Purchase Head,
Release group: -01, release code: - 02 u2013 Auditor.
3) Release indicator: - In this step you have to define release indicator.
Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
4) Release Strategy: - This is the final step for release strategy.
Assign release code 01, 02.
Click on release prerequisites, select 02 u2013 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.
For Purchase Requisition: -
Purchase requisition is creating PPA person than PPA head release this purchase requisition.
Process of Release Strategy: -
Procedure with Classification: -
Edit Characteristics: -
For implement release strategy for purchase requisition you have to create Characteristics u2013 CT04.
For Example: -
Suppose you want to create release strategy for purchase requisition document type wise. So you create characteristics for purchase requisition document type with CT04 u2013 document_type.
Edit Classes: -
After creation of characteristics, Create Class u2013 CL01 for release strategy of purchase requisition.
For Example: -
Create class for purchase requisition like: Release_PR
Set Up Procedure with Classification: -
In this node you can maintain following details.
Release Group
Release Codes
Release Indicator
Release Strategies
Now we see above details in briefly
Release Group: -
You can maintain release group in this node. This permits the multiple usage of the same release strategy key
For example: - Create 01 u2013 Release Group for purchase requisition release strategy and assign your class of release strategy.
Release Codes: -
You can maintain release code against release group with this node.
For example: - Create release code 01 u2013 PPA Head against release group 01 u2013 release group.
Release Indicator: -
You can create release indicator with this node, like blocked, in process, Release.
For example: - Create two indicators, Like X u2013 Blocked, 9 u2013 Release.
Release Strategy: -
After click on this node you can see four different step for release strategy of purchase requisition.
Release prerequisites, Release status, Classification, Release simulation.
First off all maintain your release code in Release code tab. Than done some bellow settings.
Release prerequisites: -
Click on release prerequisites tab, change your required changes and click on continue button.
Release Status: -
In this node you can set your path of release strategy.
For example: - you want to create release strategy like when PPA head tick on release indicator at that time purchase requisition made release. So you can set it via release status.
Classification: -
In this node you have to enter value of characteristics.
For example: - enter NB u2013 standard pr for document_type.
Note: - Before enter value in Classification, You have to maintain value in characteristics u2013 CT04 in value tab.
Release simulation: -
Check release simulation for release strategy.
After done this process, Create purchase requisition for document type NB u2013 Standard PR.
At the time of check release strategy will be implemented in your purchase requisition.
You can release it via ME54N. List of purchase requisition release with ME55.
Also use below link.
[http://help.sap.com/saphelp_erp2004/helpdata/EN/18/f8843b49f6a40de10000000a11402f/content.htm]
Regards,
Mahesh Wagh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
1.For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
2.CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
3.In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
4.CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
6.OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
7. OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.