SAP MM ( Release Procedure & STO )
Pls. help me answering the question :
1. What is the basic difference between PO release procedure and PR release procedure though the process are same ?
2. Define the steps for multiple release procedure .
3. What is purchasing document type in STO ?
Hi
The Difference between
PR Release and PO Release
1.Header level and Item level Header level only
2.With and w/o Classification With Classification
Doc type for STO UB and Item category is U
Regards
AKM
Similar Messages
-
Dear all,
how the system identifies if the purchasing dociment subjected release procedure or not ?
will award points .
rgdshi,
you set release strategy for each and every purchasing document. its mentioned in SPRO.
release strategy for
1. PR
2. PO
3. COntract etc
release strategy is trigerred based on
1. characteristics like PO value, plant etc
2. class
3. release strategy
you define these two in SPRO. system checks the document for the above mentioned criteria and trigers appropriate release strategy.
regards,
anand -
Workflow Concept for Release Procedure in SAP MM
Dear Support,
Please help me to understand the concept of Workflow in Release Procedure , and pls provide me any usefull Configuration
document so that I can able to Map .
So pls help me to sending document for workflow for Release Procedure.
ThanksDear Mr. venkatesh,
Mail will trigger in mentioned combination.
If you have mentioned same login id then mail go to one login id related mail or if you have mentioned different login then go to diffrenet login id.
1R 01 HOD IT US SAPMM01
1R 02 HOD HR US SAPPM01
1R 03 HOD FI US SAPPS01
1R 03 HOD FI US SAPPS01
Thanks
madhurendra Sharma -
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. -
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 PMHi
Blank Account assignment does not work, as you cannot create a chracteristic Value as Blank.
You need to create a new release strategy without the account assignment category chracter.
Or remove the account assignment Chracterisitc from the release strategy
Thanks & Regards
Kishore -
How to configure release procedure for rate contracts release
Dear all,
How to configure release procedure for rate contract following are the requirements
they are two release codes c1 & c2 <=100000,>=100000
if c1 is not there c2 has to be approved
Change in the value of the rate contract contract
Change in the validity of the rate contract
Addition of deletion of line items
While using a non u2013 released rate contract in the PO an error message should shoot out.
Also the logic should be changed while using the rate contract in the PO.
The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
It should be possible to refer existing valid rate contracts in purchase orders.
Regards,
bhaskarHi,
In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
class in standard is the same FRG_EKKO, you can use the same for contract.
To distinguish if it's a contract or PO, EKKO-BSART can be used.
For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
You can restrict the document type to set up the release strategy for only contract.
Of cause, you can also create your own release class Z* for contract copying standard
one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
OLME:
-> contract
->Release Procedure for Contracts
->Define Release Procedure for Contracts
->Release Groups
If you have already created the PO release class.
Assign a new chracteristic of Document Category -BSTYP
Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES -
Purchase Order release procedure
Hi All,
My client is having following requirement for Purchase Order release procedure.
Plant 1 - 1 Release code (Manager)
Plant 2 - 2 Release Codes (Manager, Sr Manager)
Plant 3 - 3 Release Codes (Purchase Officer, Manager, Sr Manager)
All plants are assigned to one company code. Please advise me how I can map above requirement in sap.
Thanks & Regards,
NagiHi Nagi,
In PO Realease startegy configuration, you need to decide and select the Release objects for which the system should trigger release for the document. you should work with Characteristics for each object (Your requirement is for 3plants) so in one of your characteristic WERKS should be your field along with other characteristics based on your requirements such as Total Net Value, Doc type etc.
Create Characteristics in CT04 for the class type 032 and proceed maintaining the release Group and Release codes as per your requirement.
Refer the following thread and revert if any confusions...
http://**********************/2008/11/release-procedure-release-strategy-main.html
Regards
Shiva -
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 -
Release procedure with classification not getting triggered
Hi,
I have configured the new release procedure for the PR release of type with classification, but its not getting triggered. Earlier my SAP system had without classification in place, but I wanted to have with classification. Can any one suggest how do I switch between two.
Ideally once I create the release group in with classification procedure that procedure gets activated and gets triggered. Unfortunately its not happening in my case. I tried deleting the entries from the without classification side too, but still it doesnt respond. Is there in patch or note missing.
Your suggestion would be highly appreciated.
sachinHi Jurgen,
I am configuring it for PR and with classification method. Well for simplification I am using just purchase group as characteristics, but still its not working. Earlier system had without classification in place, as its there in a default system and used to get triggered. When I created new procedure its not getting triggered. To be assured I deleted the data from witout classification, but still its not working.
Where as I did the same setting for PO, its working and giving me correct releaes strategy.
My characteristic is PRGRP using the communication structure CEBAN and field as EKGRP
Please suggest me on this.
sahcin
Edited by: sachin sagane on May 18, 2010 6:32 PM -
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 -
Hi SAP Gurus,
We do release procedure in PR with Account assignment category K.Here ,for collective release in pr (ME55),check box is disabled... Kindly help me how we enable the check box.We use scope of list as "F".All customization for release procedure is correct.
Thnks & Regards
SAP MM UserYou use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
Features
Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code. Once effected, a release can also be cancelled with the same code (that is to say, the original status is reinstated).
If linkage to SAP Business Workflow has been defined for a release code, rejection is also possible. This is only possible for purchase requisitions.
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
Purchase Requisition
The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
Release Procedure for Purchase Requisitions
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
Without classification
With this procedure, requisitions can only be released at item level.
The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
Release Procedure for External Purchasing Documents
External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
sri -
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 -
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 -
BDC/LSMW for SPRO to MM to Purchasing to PR to Release Procedure to ...
Hi experts,
May I know those screen in SPRO can do BDC or LSMW? I am facing problem on trying up the BDC using SM35 on the following screen. (I can't get the transaction code).
The path is:
SPRO -> MM -> Purchasing -> PR -> Release Procedure -> Set up Procedure With Classification -> Release Strategies.. The SAP program is SAPL0ME2, but I can't execute it using SE38 since it's a program Type 'F'.
So may I know any possible way for us to use recording approach on these to do Mass insertion of data?
Thanks.
Cheers,
Wong
Edited by: Julius Bussche on Sep 12, 2008 10:37 AMHi Vijay,
First, you can try on SM30, V_T16FS. Simply double-click on 1 release strategy, then Click on "Classification". You will see the classification screen allow us to enter value on each characteristic of the class.
However, I try using SHDB (recording), it shows empty screen on the value for class in the 'Classification' screen.
Thanks.
Cheers,
Isaac. -
Hello,
I try to implement workflow using the mulitilevel release procedure of purchase order (copy of WS20000075), my question is how you can achive the situation that workitem will be send to the receiver (next person in release level hierarchy) only when the previous approver approved it?
Greetings
Karolrefer the following links
http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/e0bbdb3c-d640-2a10-d3b2-e4d9b90536a6
http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/30488d68-8451-2a10-d993-bb36e56a1dc8
http://www.youtube.com/watch?v=2DjFcyiVXvU
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70fef212-b6cb-2c10-e085-c84b80d7068e
Maybe you are looking for
-
I Need to Locate my RAZR, HOW DO I?
SO I PAY VERIZON WIRELESS OVER A THOUSAND DOLLARS A YEAR FOR THE PAST 4 YEARS AND MY RAZR GOT STOLLEN AND THEY TOLD ME AT THE STORE THAT THERE IS NOTHING THEY CAN DO TO LOCATE MY DEVICE THAT I PAYED **** NEAR $300 DOLLARS FOR AND I PAY THE INSURANCE.
-
Cannot resolve symbol: class OracleDriver
Attempting to compile a servlet on Apache Server using same jdeveloper jdbc libraries: classes12.jar & nls_charset12.jar Error message: $compilejava2.sh ProdJobs ProdJobs.java:361: cannot resolve symbol symbol : class OracleDriver location: package d
-
Firefox 4 will not let me keep my bookmarks listed on the side bar. I can open them there but once I click somewhere else they go away. On previous Firefox versions I could display my bookmark folders down the left side of my screen and just leave th
-
Arrays that work with Java Class
Good Day all. Currently, I am working on a program that is giving me a bit of trouble starting...can anyone give me assistance and try to tell me what I am doing incorrectly? Here is the tasking: Main Method 1. Output statement to screen saying this
-
Tried updating firefox but it is not compatible with leopard op. If I try to re-install the older version will my bookmarks still be there?