PO Release Procedure Issue
Hi,
I had done SPRO settings for Purchase Order release properly with a condition that if the total value is >1,000 EURO the order has to be released. I had checked in the simulation and it is working fine.
But when I am creating a PO whose value is more than 1,000 euros , i am not getting the PO Release tab in the po header on saving the document. Checked the procedure once again and it is looks fine....
Please advice what might be the possible reasons for the same.
Thanks ,
Vengal Rao.
Hi Ajit,
Thanks ...
As release strategy was not entered , the procedure did not work, I deleted the existing one and created a new one using CL20N and now it is working.
Regards,
Vengal Rao.
Similar Messages
-
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. -
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 mehi,
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 -
Purchase Requisition Release Procedure Modification
Hi
In Purchase Requisition Release, we have two deviations in business requirement from standard SAP behaviour:
1. In multistep release, system allows PR release to be revoked by a lower level release authorized person even though higher level release has been done. Example, PR Release has release codes A1, A2 and A3, A2 can revoke release even after A3 has released the same. How do I prevent this from happening?
2. If business requirement is to have release procedure based on item cost per unit and not on total value of the line item, how can this be achieved?
Appreciate any guidance on these issues
Thanks
SriramHi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
gwa_event_container-element = 'PurchaseRequisition'.
gwa_event_container-value = gwa_im_eban-banfn.
append gwa_event_container to gi_event_container.
clear: gwa_event_container.
gwa_event_container-element = 'ItemOfRequisition'.
gwa_event_container-value = gwa_im_eban-bnfpo.
append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
and bnfpo = gwa_im_eban-bnfpo .
if sy-subrc <> 0 .
call function 'SWE_EVENT_CREATE'
exporting
objtype = 'BUS2009'
objkey = gwa_objkey
event = 'zcreated'
tables
event_container = gi_event_container
exceptions
objtype_not_found = 1
others = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi -
We added new set of release strategies to existing ones (SAP 4.. Since some of added release strategies no longer required, the team deleted it. The characteristic used for the class are:
1. PO Document TYpe
2. PO Purchasing Group
3. PO Purchasing Org
4. PO Total Value (CEKKO-GNETW)
The class and characteristics not being changed.
The new strategies are tied to different document type, group and values
After doing this, the whole release strategies (old and new) are no longer being picked up during creation of PO. we have checked all srelease strategies(27 of it) and the characteristics values and confirmed it's exclusively assigned.
Appreciate help from all friends out there to identify possible cause to this issues and how to make it work again. Thanks
Regards.
ArfanDear Srini,
My mistake. The release procedure also include the purchasing org.
Regards
Arfan -
I have configured the PO release procedure for PO with header value of more then 25000. In the process I have created the following -
1. Custom Characterstic
2. Custom class
3. Release group
4. Release code
5. Release indicator
6. Release strategy
but the problem I am having is that the workflow event 'ReleaseStepCreated' is generated in the system even for PO with header value of less than $25000. Also the 'Release' tab is not appearing in the PO header.
Please help. Appreciate you time.
Sridhar JamiI think this issue is also related to mis entries in SWEC.
Go thru' this Note 797775 - Entry in Transaction SWEC hinders workflow. Verify all the steps stated in this note even you think it might not be the right note.
Regards, IA -
Purchase requisition release procedure through User-Exit
Hi Workflow Guru,
I have a requirement to configure purchase requisition workflow . the workflow should trigger through release strategy.
The approver should determine through user-exit and the approver should determine based on value and quantity and that can be define in user-exit. as per my knowledge the value should mantain in SPRO-Release procedure. Please clarify me is it possible through user-exit. I am worked on user-exit for release procedure based on purchasing group.
Thanks in advance.
Regards,
Ranjan TiwariHi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
gwa_event_container-element = 'PurchaseRequisition'.
gwa_event_container-value = gwa_im_eban-banfn.
append gwa_event_container to gi_event_container.
clear: gwa_event_container.
gwa_event_container-element = 'ItemOfRequisition'.
gwa_event_container-value = gwa_im_eban-bnfpo.
append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
and bnfpo = gwa_im_eban-bnfpo .
if sy-subrc <> 0 .
call function 'SWE_EVENT_CREATE'
exporting
objtype = 'BUS2009'
objkey = gwa_objkey
event = 'zcreated'
tables
event_container = gi_event_container
exceptions
objtype_not_found = 1
others = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi -
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 -
Release procedure for p.o.
hi sapgurus,
here is the scenario,
i have as issue ( for P.O value only)
1) if the value is < 2 lacks then one person will release.
2) if the value is > 2 lacks then 2 persons will releasehi,
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.
Follow these steps
G.Ganesh Kumar -
Restriction for PO release procedure
Dear All,
I have to restrict the PO release procedure.
Suppose there are only 3 person can release the PO but i have to restrict that 3 person for that PO quantity.
suppose, PO quantity 1000.
Person 1 --> Can release up to 1000.
Person 2 --> Can release 1000 to 5000.
Pesron 3 --> Can release 5000 to 10000.
Here quantity is 1000 ,
Then person 1 should release the PO and others should not.
and if quantity is 10000 ,
then person 3 should release and others should not release.
Right now in my client site anyone from this persons are able to release the PO.
So i want to restrict them by PO quantity.
Please let me know that, for this any BADI or User exit is available in system.(Or is there any customization need to be done and how)
If yes how to apply that, give me step by step procedure to solve the above issue.
Please give your inputs to come out of this problem.
Thanks & Regards,
Sanket.hi,
in the exit i have mentioned ,use the import parameters which contains structures which has fields related to that u mentioned which r populated at runtime.
check tht fields in the structures for specific users u want to rstrict.
ex:
if sy-uame = < >.
else.
endif. -
Release Procedure for A/c Assigment PRs
Dear Experts,
As per user requirement,we need to create Release procedure with classification for Purchase Requisitions based on a/c assignment category(F internal order)for protects.But there is already existed release strategy had characteristics document type,purchase group,can i add new character for item category F (internal order ) for the release class,please tel me field and structure.
Thanks in advance.
VarunHi Varun,
the new characteristic is CEBAN-KNTTP.
Pls. read FAQ note 365604 carefully /the whole note/.
Part 2e) is addressing your issue:
If you make changes to the class (add or delete a
characteristic), the system cannot determine the release for this
class. Then you must adjust all release strategies
correspondingly. (If you added a new characteristic, you must
maintain the characteristic value).
Please check also if you are using overall release strategy or item wise release strategy in your PR. . In the overall release, the system only considers the characteristics that are IDENTICAL for all items (like in all PR items you have acc. ***. category F).
Please check also note 326102 to avoid performance issues with PRs without acc. ***. category.
Regards,
Edit -
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. -
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 -
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.
Maybe you are looking for
-
HT2729 How can I move a rented movie from my iPhone4s to my computer?
I am tryingt to move a movie I rented on my iphone4s to my macbook so I can watch it on a bigger screen but cannot figure it out!
-
Why does the internet on my new macbook pro not work when my old macbook's does?
Why does the internet on my new macbook pro not work when my old macbook's does? I'll have to turn the wifi off and back on multiple times to get the internet to continue to work on my Macbook Pro (running mountain lion but did it on lion also) when
-
[SOLVED] TF2 (Team Fortress 2) glitchy during gameplay
Check out this awesome glitchy video Any ideas on why this is happening? Thanks! I don't think I got it installed in time for the penguin :-( EDIT, because I forgot to list information: Video card: 05:00.0 VGA compatible controller: Advanced Micro De
-
MacbookPro w 2nd display problem
When I attach a second display to my MacBook Pro the screen goes dark after about 10 sec while I can continue to work on the second screen. Is that a hardware or settings problem? I have checked all display options, tried other monitors, mirroring et
-
I have the iPad2. I use Folder Plus to open Pdf files. There is an option within Folder Plus to re-open in Adobe Reader where I am able to add text. I have yet to discover how to save the file after I have added the text. Please point me in a directi