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
Similar Messages
-
Release strategy problem in Purchase order
Hi Guys,
I was trying to configure Release strategy for the purchase order and this button is not triggering in my purchase order.
I dont know where I was doing wrong and where might be the problem as I tried several times.
Can someone give me some good idea about it how to configure in a proper way.
If you need any further information please let me know.
Thanks
KrishnaHi
I hope you followed the following steps:
1. Create Characteristic using CT04
2. Create a class and link to the characteristic using CL02( class type: 32)
3. Configuration of release procedure
SPRO IMG->MM-> Purchasing -> PO -> Release Procedure -> Set up procedure
A) Create release group and link to class
B) Create release code
C) Set up the release indicator
D) Set up Release Strategies-> strategy and codes
E) Set up Release Strategies -> pre requisites
F) Set up Release Strategies -> status
G) Set up Release Strategies -> values for strategy
Regards,
Subhashini -
Release Procedure for every Purchasing documents
Hi,
for a procument of material eg:- Material007
Can I set Release Procedure for Purchase rquisition
then after releasing Purchase rquisition i need to create a RFQ
which is also subject to Release Procedure ,After releasing RFQ I should able to enter into a Contract,which also subject to Release Procedure ,After releasing Contract i need to create a Purchase Order which is also subject to Release Procedure,After releasing Purchase Order only I should be able to Receive the goods.
Is it possible to do this way ?Can any one help me?
ThanksWhy you want to put so many locks??????
well if case your required use below steps for all document typew in IMG.
suggestion to download the BBP from below link also
http://help.sap.com/bestpractices/BBLibrary/bblibrary_start.htm
3.4.24 Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1 Creation of Characteristics
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Characteristic
Transaction Code CT04
2. On the Characteristic screen, make the following entries.
3. In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name Description User action and values Note
Select Addnl Data tab
Table Name Table Name CEKKO
Field Name Field Name GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description Description Total net order value
Status Status Released
Data Type Data type Currency format Selected by system
Number of characters Number of characters 15
Decimal places Decimal places 2
Currency Currency INR
Interval vals allowed Interval values allowed Check this tick box
Multiple Values Multiple values allowed Select this radio button
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2 Creation of Class
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Edit Class
Transaction Code CL02
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Class PORELPROC
Class Type Class Type 032
Choose Create icon or white paper icon to create new class.
Description Description Purchase Order Release Procedure
Status Status Released
Choose Char. Tab to input characteristic name.
Characteristic Characteristic POVAL Created in above step
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3 Configuration of Release Procedure
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Materials Management Purchasing Purchase Order Release Procedure for Purchase Orders Define Release Procedure for Purchase Orders
Transaction Code SPRO
2. On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Rel. Group Release Group 02
Class Class Name PORELPROC Created in above step
Description Description PO Release Procedure
4. Choose Enter to complete the entries
5. Choose Save icon or Ctrl + S to save the entries.
6. Choose yellow arrow to go back to popup screen.
7. Choose Release Codes to select.
8. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Grp Release group 02 Created in above step
Code Release Code 01
Workflow Workflow Leave it blank
Description Description Purchase Officer
Grp Release group 02 Created in above step
Code Release Code 02
Workflow Workflow Leave it blank
Description Description Materials Manager
9. Choose Enter to complete the entries
10. Choose Save icon or Ctrl + S to save the entries.
11. Choose yellow arrow to go back to popup screen.
12. Choose Release indicator to select.
13. Choose New Entries icon and make the following entries:
Field name Description User action and values Note
Release ind. Release Indicator 1
Released Released Leave it blank
Chgable Changeability 4
Value change % Change of value 10%
Description Description Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind. Release Indicator 2
Released Released Select Check box
Changeable Changeability 6
Description Description Purchase Order Released
14. Choose Enter to complete the entries
15. Choose Save icon or Ctrl + S to save the entries.
16. Choose yellow arrow to go back to popup screen.
17. Choose Release Strategies to select.
18. Choose New Entries icon and make the following entries:
19. System will give new screen New Entries: Details of Added Entries
Field name Description User action and values Note
Release Group Release group 02
Rel. Stategy Release Strategy S1
Capital Items Release
Release Code Release Code 1 01
Release Code Release Code 2 02
20. Choose Enter to complete the entries.
21. Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22. Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23. Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24. Choose Next Screen icon or choose F8 to continue.
25. If you want to simulate the release procedure you can choose Release Simulation icon.
26. Choose Enter to complete the entries.
27. To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4 Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu Cross-Application Components Classification System Assignments Assign Object to Classes
Transaction Code CL20N
2. On the Class screen, make the following entries:
Field name Description User action and values Note
Class Type Class Type 032
Choose Enter to Assign values.
Release group Release Group 02
Rel. Strategy Release strategy S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3. Choose Enter to complete the entries
4. Choose Save icon or Ctrl + S to save the characteristic. -
How to change pricing procedure of existing purchase Order
Hi,
We have created a Purchase Order.
After PO creation, we have changed the schema group for the vendor.
Now for new Purchase Orders, new pricing procedure is determined.
We also want new pricing procedure to be determined for old Purchase Orders.
Can this be achieved?
Regards,Hi ,
It is possible to Update the Pricing procedure in Old PO. For this what you need to do is Open PO in ME22N transaction, in the header Org. Data tab remove the Purch. Org and Company Code and press Enter Key for 3 or 4 times now enter the Purch. Org and Company Code now check in the Item Data, condition tab Analysis button new Pricing procedure is picked up. Even we can change the PO Currency in this way if it is changed in Vendor master.
Hope this will help you
Best Regards,
Pradeep Naik -
Procedure to setup purchase order approval notice to a local printer
Hello Guru's,
How to setup purchase order approval notice to a local printer. will anyone guide me the step by step procedure with T-codes.
Full points for the config stepsHello Guru's,
How to setup purchase order approval notice to a local printer. will anyone guide me the step by step procedure with T-codes.
Full points for the config steps -
Release Strategy for Asset Purchase order
Hi,
I have the following client Requirement.
1. PO document type will be anything but Po created is for Asset
2. In such case, Release strategy should be approved only be certain groups only. Anyway the Account assignment category will be "A"
As we cannot control the PO Release by Account Assignment category, it has to be controlled via User Exit.
I.e., combination of Acc Assignment category and Purchasing Group should result in a particular strategy.
Can you suggest relevant user exit? This is importantly needed. Please help.
ThanksHi,
Please do the following changes,same is tested by me in Our dev server and works successfully in PO.
Go to Se11 ,open structures -CEKKO (You will find KNTTP-account assignment field is missing)
Click on append structures ,system will ask you object name ,give as anything,then put a description /
Then system will ask you to add new field in CEKKO structures.
Add field KNTTP and save ,system will generate request for the same.
Now create a characteristic as CEKKO_KNTTP and save ,don't give table name here
Once saved,re-open the CEKKO_KNTTP ,here you need to give table name as CEKKO and field name-KNTTP. Define values an save.
then add the same in class ,and then select the required assignment in CL20N ,save.
And check the PO effects,it will works.
Regards,
Sandesh Sawant -
Dear All
What is meant by Indent PO? How it is raised? If I want to delete the Indent PO how can I do it?
Note: During deleting Indent PO I am getting error saying CHECK FOR THE PAYMENT TERMS IN HEADER error no:Y210,
How to overcome this error and delete the Indent PO?
Regards
Srinihi,
The PO which is generated from the indent PR is called indent PO...
For indent PR features check the following thread:
Indent Creation
Hope it helps...
Regards
Priyanka.P -
Reg: Release Procedure of Purchase Order
Hi,
I have a requirement for release procedure of a purchase order. I have two approvers for the approval of the purchase order. The first approver should have the option whether he wants to send the po to the higher approver by selecting 'yes' or releasing the purchase order by selecting 'no'.
can anyone give me information on how to do this? as i am new to workflow.
Thanks in advance.
Regards,
Ramesh Babu Shttp://help.sap.com/saphelp_erp2005vp/helpdata/en/04/9277a346f311d189470000e829fbbd/frameset.htm
Check this link for reference.
Create a new work flow(SWDD Transaction). In that create a new task for which specify triggering event as PurchaseOrder.released of Business object BUS2012.
And then create other tasks and link as per your requirement.
For more reference on workflow: http://****************/Tutorials/Workflow/Workflow.htm -
Hi SAP guru
I am having the requirement for release procedure as follows
Purchase order with Asset (Item category) - Value Up to 50,000/- will be approved by GM
Asset (Item category) - Value more than 50,000/- will be approved by Chairman.
Purchase order other than ASSET
Value Up to 100,000/- will be approved by GM
more than 100,000/- will be approved by Chairman.
I checked in CEKKO, the field KNTTP - Account Assignment Category component is not available.
Could you please tell me how to solve this issue?
Good suggestion will be rewarded with full points.
Thanks in advance
AnandHello Anand:
The release strategy for PO only contain fields on the purchase order header (EKKO) and the account assignment is at item level (EKPO), however you can add the account assignment as customer field on structure CEKKO (CEKKOZZ structure) and fill the information on this field with the user exit M06E0004 (transactions SMOD, CMOD)
Keep in mind that the CEKKO structure has the value of all the purchase order (CEKKO-GNETW), not item by item. It means that you could not check on the release strategy the value of all the assets included in the purchase order.
Additionally check if there are cases in your installation where a purchase orders could contain several items for more that one account assignment.
I hope this help, if you have any question please let me know it.
Best regards,
Jose Luis -
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
PariHi 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 -
How to setup a release strategy for store generated purchase order
Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2teaPlease go thru the below Release Procedure and check whether you have maintained all the settings properly.
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).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
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)
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
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
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
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,
Ashok -
Release Tab in purchase order disappear after release using ME29n
Hi there,
We are busy testing support stacks (upgrading from ECC6 SAP_APPL SAPKH60305 to SAPKH60307)and we've come accross a strange problem. When we create a normal purchase order (ME21n) the purchase order does pick up a release strategy. Using the older ME28 transaction to release this purchase order, everything is fine. We can use ME28 to release the purchase order, as well as unreleasing the purchase order, as often as we want (the same purchase order). When we use transaction ME29n the release tab in the purchase order just simply disappears after saving. In the purchase order header changes, the release change is visible, but the release tab is missing. This purchase order is now not subject for release, and a goods receipt is possible without release. I checked in table EKKO as well and the release fields in this table for this purchase order is empty.
Has anybody had a similar experience? Any advise would be greatly appreciated.
Regards
Christo VermeulenHi Christo Vermeulen,
I have detected the same problem as reported by you. Did you solve it? Do you know how can I procedure to solve it?
Thanks in advanced,
Eder Nicoleti -
Purchase Order not subject to release strategy
Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisahhi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
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).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
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)
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
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
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 0
1
Classification Choose your check values
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
ravikant dewangan -
Want to restrict the Purchase order release at lower level...
Dear Friends,
The Problem i am facing is that the release strategy defined in Purchase order is such that it will be released by four authorities,
& When 4th One, The Highest authority releases the order it should not get unreleased by lower level authorities.I want to configure this.
Partially it is completed, as if Tcode me29n is used for cancel release then it is restricted by Going into
SPRO-MM-Purchasing-Purchase Order-Release Procedure for Purchase Order- Define Release Procedure for Purchase Order
& suggesting it there.into Release Indicator
But still it can get unreleased by Tcode me28.
Kindly Suggest,
Gaurav ChopraHi,
This is the standard like release srtetegy will not have the restriction only the release do the release . He can also should de release the document.
this can't control.
SAM -
ME28 Cancel release of purchase order
Hello,
when I try to perform a cancellation of a release of a PO I get an error message:
ME 175 Document already treated. Function not possible
It should be possible to cancel the release of alll released purchase orders. Can you help me?
Thanks a lot!Hi,
please read the following:
Note 493900 /12. Question :
Is it possible to cancel a release strategy when the purchase order has
been printed out ?
Answer :
With ME29N you cannot cancel a release strategy once the document has
been printed out. This behaviour constitutes a new design. Regarding
ME28 it has been decided to keep the old behaviour and you can cancel
the release if there is at least one message type which has not been
printed out.
Please note AT LEAST ONE message type has NOT been printed out with
ME28.
Alternatively, you can try the following:
- Transaction: SPRO
->MM->Purchasing->PO->Release procedure for PO
->Define relesae procedure for PO
->Release Strategies
->Release Status
- choose the button release indicator and
5 Changeable, new release if new strategy/outputted
6 Changeable, new rel. if new strat. or value change/outputted
- go into transaction ME22(N)
- you will get the warning message 06 684 stating
'Releases already effected are liable to be reset'
- change the price and save the p.o.. Now a change message will be
created and will be send to the vendor again.
- Please note that the release strategy will only be reset if the price
is increased. When it is decreased it won't be reset. But in both
cases a change message will be created and send to the vendor.
- after the change of the p.o. you will have to release it again. After
the release the change message will be printed.
Hope this will help to solve the issue,
regards,
Edit
Maybe you are looking for
-
How can I get rid of 2 cents in my Apple ID in order to change stores?
I want to make my account credit 0 to change AppStore from Canadian to American
-
Hi folks, Want to know how do we default a vendor for particular output message like Print, EDI etc. We have around 200 vendors under our company code/plant, most of the vendors have proper default output message, however there are some new vendors w
-
Experience​d Labview Programmer Needing Job in US
Hello, My name is Rollin, I have been working in for a European research facility in Grenoble, France as an Electronics Engineering Technician for 8 years. I have 3 years Hands on experience with Labview, for instrument control and data acquisition t
-
I cannot retrieve iTunes and iPhoto libraries from Time Machine after re-installing OS X
I havd just re-installed OS X on my Mac, and I cannot retrieve iTunes and iPhoto libraries from Time Machine.
-
Hello, I've exported my entire FCP Sequence and imported it into Color, where it shows up as just one long shot. I'm using Color only to apply certain nodes, with keyframes, in the Color FX room. Sometimes I go back into FCP and change filter setting