Customisation of release procedure

hi,
how to do the customisation of release procedure.
thanks
katrina

The aim of this release procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle. The person responsible processes the relevant document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This procedure provides for the release (approval) not only of requisitions (i.e. internal purchasing documents), but also of the external purchasing documents RFQ, purchase order, contract, scheduling agreement and service entry sheet.
1. Create Characteristics
2.Create class
3.Set up release strategy with classification
4.Create release group
5.Create release code
6.Create release indicator
7.Create release strategy
Important Transaction codes
ME51N Create Purchase Requisition
ME21N Create Purchase Order
ME54N Individual Release (PR)
ME55    Collective Release (PR)
ME29N Individual Release (PO)
ME28    Collective Release (PO)
Communication Structure for characteristics
CEBAN - Purchase Requisition
Commonly used fields u2013
BSART     Purchase requisition document type
ESTKZ     Creation indicator (purchase requisition/schedule lines)
EKGRP     Purchasing group
AFNAM     Name of requisitioner/requester
MATNR     Material Number
WERKS     Plant
LGORT     Storage location
BEDNR     Requirement Tracking Number
MATKL     Material group
GSWRT     Total Item Value
CEKKO - Purchase order
BUKRS     Company Code
BSART     Order type (Purchasing)
LIFNR     Vendor's account number
EKORG     Purchasing Organization
EKGRP     Purchasing group
BEDAT     Purchase Order Date
INCO1     Incoterms (part 1)
WERKS     Plant
MATKL     Material group
GNETW     Total net order value
The fields from EKKO that are related to PO release strategy
FRGGR
FRGSX
FRGKE
FRGZU
Check the tables for the release codes
T16FG
T16FS
T16FB
SAP Help : http://help.sap.com/saphelp_47x200/helpdata/en/75/ee14a355c811d189900000e8322d00/frameset.htm

Similar Messages

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.

Release Procedure for Quantity Contract

Dear All,
We have a business requirement to ensure that Quantity Contracts are released by the Account Receivable Accountant before the Sales Support Staff can create Sales Orders against them.
Process : Create Quantity Contract (VA41) -> Release Contract (VKM3)->Create Sales Order (VA01)
Currently, users can create sales order against the quantity contract before the contract has been released.
I need guidance on how to implement system control to prevent this creation of Sales Orders before Quantity Contracts are released..
How can i configure release procedure for quantity contract?
Any assistance will be appreciated.
Many Thanks

Hi
There is a concept of User Status / Status Management in SAP. By using this you can set status as default that is Blocked, and then the authorised person can release the document, only after that a person can create an Order, with reference to that Contract.
The Customisation setting is in :- IMG> sales and Distribution>Sales > Sales Document>Define and assign User Profile(T Code is BS02)
To know more about this you can search the Forum, also check the below given Link:-
[http://web.mit.edu/sapbiz/docs/Explanation%20of%20Status%20Management%20functionality%20v3.doc]
[http://help.sap.com/saphelp_crm40/helpdata/en/73/29943a7acb9023e10000000a114084/content.htm]
Hope this will help you.
Regards
Amitesh Anand

Role conflict in release procedure

Dear All,
We have one scenario, we want to create two release procedures for different value of po i.e. >1 Lac and <= 1 Lac, we have one group and three person with these codes
01 engineer
02 manager
03 general manager.
Now for first release strat (< 1 lac)we want to keep two levels
01 engineer
02 manager
for second release strat ( >= 1 Lac)we will keep two levels
02 manager
03 general manager.
Group will be same for three of them and for both the release strat. now can anyone tell me that the role of 02 manager is conflicting between two release strat.
Because after implementign same release strategies, we are not able to release the po with code 02 for first release strat.
we are getting msg express document was terminated...
i think there is some prob in release proc itself..eventhough simulation is getting done ok in customisation.
Please reply at earliest

Hi,
Check
http://www.sap123.com/showthread.php?t=59

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

Use of Release Procedure / status in Condition Table

What is the purpose of Release Procedure / Release status when creating condition tables ?

Hi
Release procedures are used in condition tables to control whether the condition types for these condition tables have to be read during pricing condition determination or not.
If the condition table status is released then only the condition types will be read during pricing determination. If the status is not released, then they can be used for information purposes or for simulation of pricing.
The release status is controlled by processing status too, which can be seen in condition record creation screen.
So in crux, the processing status with Release status help in simulation of pricing, blockign the condition records from being read during pricing etc.
For more information an F1 help on the following path will give you some more information.
SPROSD-BF-PRICING-DEFINE PROCESSING STATUS----Here read the documentation meant for this link. You will get some more clarity on this.
Rwd point if it helps.
Reward points if it helps.

PR release procedure no longer working-error MEPO 822

I've raised a message previously regarding PR release problem. Now i've found something that need expert helps to clarify on this.
Situation :
One of my client(ABC) implemented release procedure for PR which is not assign to value limit. It is by document type. They had 2 document types; NB and RNB.
NB = NOT subject to release
RNB = SUBJECT to release.
So when they :
create a PR with document type RNB - it will goes for approval.
create a PR with document type NB - it will not go to approval.
It was working fine until after they created a new document type which copied from NB, called ZTP.
ZTP = NOT subject to release.
They did not touch anything on PR release configuration. However, the release has no longer working. Means, when they create PR with document type RNB, it will NOT go for approval as it suppose to. I've check in configuration, all are fine.
Findings:
I've created a PR, and go to ME45N to release it but system prompt me an error message
"Purchase requisition 10000066 cannot be released". I check on the message data, the error coming from MEPO, message number 822.
So i check in OSS and found a note which is similar to this case.
Note 939371 - Overall release PR using ME54N gives error MEPO 822
Link : https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=939371#Text
But my question is,is it also applied to ME51N and without external application as per my client's case?
Please anyone help.
Thanks.

Hi guys!
Wants to share something. I had a problem to release my PR. When i want to release PR via ME54N, system give me error message "Purchase requisition 10000066 cannot be released". When i checked message data, it is coming from MEPO Messafe 822. So i asked SAP, they said this one is caused by different issue. Here's the reply from SAP.
Here's the reply from SAP :
Purchase requisition 10000066 cannot be released
Message no. MEPO822
Now click the other requisition button and let say
choose Purchase requisition 10000068,
Execute ME54N again:
Purchase requisition 10000068 cannot be released
Message no. MEPO822
Comment/explanation:
The log incidence seems not having problem with release
strategy as it was ok but it was the last PR was called
everytime ME54N was called. This same as it works in enjoy
transaction ME21N/ME22N or ME51N/ME52N.
For example, When using ME21n or ME22n to create or change PO,
after saving the PO. There are 2 ways to exit the transaction,
1, enter another T-code or use /n to exit directly.
2, use 'F3' or the 'green tick' to exit ME21n (or ME22n)
Then you can access ME23n to see the difference.
For the 1st way, ME23n won't display the last PO created in ME21n
For the 2nd way, ME23n will display the last PO just created!!!
Please see attached consulting note 595627 that explains a new
functionality as of release 470:
Due to performance problem, a decision had to be taken about the way to
use transactions. If you leave transaction ME21N/ME22N via the
exit button (F3), the expected PO will be displayed next time you use
these transactions. But if you quit abruptly (/nXXX) the PO number
won't be saved for the next transaction ME2?N.
As SAP note is the official document to explain system behavior,
this document is provided by SAP developement to explain this system
behavior to customers.
In your case, you had used ME54N and this was same as you use ME53N.
The last PO always display. You may try to view Purchase requisition
with release strategy, for example Release group R1, Rel. strategy
R1, then after this execute transaction ME54N again, the message
MEPO822 will not be there anymore.
Hope this will help you guys if you're having the same problem in future.
Thanks,
Crystal.

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

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

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

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

Release procedure problem

Hi Gurus,
          I created a release procedure for PO. i created a single chs based on total amount of PO and assigned it to a single class. then configured it for 5 release codes. all the simulation is working fine.
          But when I created the PO worth of 6 laks, which is above the level of last release code >=5 laks. when i go for release in ME29N or ME28 its giving an information message saying "document is not applicable for release procedure. in ME28 i am getting "message no documents found" for my release code and release group combination.
          Where should i have gone wrong. give me some suggestions.
Thanks & Regards,
Poorna.

Hi,
Your Maximum amount of PO which is applicable for release strategy is 5 Lakhs for your last release code.
Now if you create the PO for 6 lakhs then how the system will consider the release strategy.
Thats why you will not find the same in ME29N or ME28 to release the PO.
So you need to change your Characteristics value for last release code from = 5 lakhs to >= 5lakhs.
then system will consider the release str for any value above 5 lakhs for that last release code,
rgds
gsc

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

Release procedure for this concept.

Dear Seniors,
1) I had set release procedure already for contract and purchase order. Whenever i do po w.r.to contract, i have to release both contract and PO to do GRN. For example, consider vendor X and Y, i have contract for these 2 vendors and i have released that contract too. When i raise PO w.r.to that contract with vendor X and Y, it should not ask for release. How could i set that and where can i do that particularly for that two vendor X and Y? For remaining vendors, it should ask for release at PO level also. kindly suggest me please.
2) Normally if we set message determination for PO, we can see print preview before release also. I would like to see the print preview after release of that PO. Before release of that PO, it should not show me the print preview. How could i set that ? Kindly suggest me please.
3) I am having 400 plants, if i want to maintain 400 sloc for those plants correspondingly. Do i need to do that manually or is there any tcode to create sloc in mass ?
Kindly clear my doubt please.
Regards,
JanaMM
Edited by: JanaMM on Sep 9, 2009 8:02 AM

Hi,
Solution for 1)
Simple way to tackel this is to create saperate document type for PO s which are created with reference to contract
Solution for 2)
Use development by using BADI in PO.
us logic check field FRGKE(release status) in EKKO.
Solution 3)
Create BDC for the extation of storage locations.
T-code = MMSC
regards,
sujit

Customisation of release procedure

Similar Messages

Maybe you are looking for