Changeability of PO after final release

Dear Gurus,
My client requirement is, PO should not be able to be changed once final release has happened. They should be able to change only after revoking the final release and again releasing it.
So, if I put changeability of Release indicator as "1", it will not allow to do any changes after final release including revoking the PO once it is outputted. How to resolve this?
Thanks,
Satish

See the changeability option under Release group
1     Cannot be changed
2     Changeable, no new determination of strategy
3     Changeable, new release in case of new strategy
4     Changeable, new release in case of new strat. or val. change
5     Changeable, new release if new strategy/outputted
6     Changeable, new rel. if new strat. or value change/outputted
     Changeable, new release in case of new strategy
to my understanding option 4 is more relevant to your requirement

Similar Messages

Restriction of revoke after final release

Hi experts,
After final release of purchasing document lets say PR or PO user should not be able to revoke it.
Any suggestions highly appreciated apart from getting it done through user exit.
Regards,
Maverick

Dear Ramesh,
Thanks for your response.
I have already set changeability to 1 but my concern is after PR final approval if a PO is created with its reference then in this PR user should not be able to revoke or cancel an approval.
I think we can do this with user exit but is there any other alternative?
regards,
Maverick
Edited by: Maverick 331 on Jun 16, 2009 1:00 PM

PR non editable fields after final release

we like to do in PR Material's short text, date, Pur Grp & Requested by heads are in editable stage after final release.
we need to make non editable mode. how we can do this...
please advice
Thanks
Rajesh G

Dear Rajesh,
You may define as Field Selection Key for your PR release indicator via customizing:
SPRO
MM -PUR-PR-Release procedure-Procedure with classification
- Set Up Procedure with Classification
-Release indicator
-Now choose your final release indicator
-Fill in FSK:
Example:
Field Selection Key FZ01
Now add this FSK to your customizing via screen layout:
SPRO:
MM-PUR-PR
-> Define screen layout at doc level
-> Add your FSK to this customizing and customize
according to the field as you want.
Best Regards,
Ian Wong Loke Foong

How to send sms to the vendor after final release of po?

Hi,
i have to develop a program which will send sms to the respective vendors after the final release of the po i.e. after final release of the purchase order, sms will be sent to the respective vendor?
So, plz help me as i have no idea on it and how to proceed ahead.

hi,
did you search?
Link: [How To Send SMS From ABAP ?;
Link: [http://www.se80.co.uk/sapreports/s/swn_/swn_test_send_sms1.htm]
Link: [http://www.sapnet.ru/viewtopic.php?p=1620]
or...the great SDN...
Link: [http://forumsa.sdn.sap.com/search.jspa?threadID=&q=sendSMSfrom+program&objID=f50&dateRange=all&numResults=15]
Configuration
Link: [http://help.sap.com/saphelp_nw2004s/helpdata/en/af/73563c1e734f0fe10000000a114084/frameset.htm]
Example from other Link: [user|Send SMS to mobile through ABAP code; in SDN
REPORT y_send_sms.
DATA: http_client TYPE REF TO if_http_client .
DATA: wf_string TYPE string ,
result TYPE string ,
r_str TYPE string .
DATA: result_tab TYPE TABLE OF string.
SELECTION-SCREEN: BEGIN OF BLOCK a WITH FRAME .
PARAMETERS: mail(100) LOWER CASE,
m_no(20) LOWER CASE ,
m_mss(120) LOWER CASE.
SELECTION-SCREEN: END OF BLOCK a .
START-OF-SELECTION .
CLEAR wf_string .
CONCATENATE
'http://www.webservicex.net/SendSMS.asmx/SendSMSToIndia?MobileNumber='
m_no
'&FromEmailAddress='
mail
'&Message='
m_mss
INTO
wf_string .
CALL METHOD cl_http_client=>create_by_url
EXPORTING url = wf_string
IMPORTING client = http_client
EXCEPTIONS argument_not_found = 1
plugin_not_active = 2
internal_error = 3
OTHERS = 4.
CALL METHOD http_client->send
EXCEPTIONS
http_communication_failure = 1
http_invalid_state = 2.
CALL METHOD http_client->receive
EXCEPTIONS
http_communication_failure = 1
http_invalid_state = 2
http_processing_failed = 3.
CLEAR result .
result = http_client->response->get_cdata( ).
REFRESH result_tab .
SPLIT result AT cl_abap_char_utilities=>cr_lf INTO TABLE result_tab .
LOOP AT result_tab INTO r_str.
WRITE:/ r_str .
ENDLOOP .

Change in Expected Delivery date (EDD) field in the PO after final release

Hello Experts,
There is a business requirement, whereby after PO final release is completed & when the PO is released for further processing, no further changes should be possible, except for the expected delivery date (EDD) field in the Delivery schedule tab of the PO Item details. Other than this, no changes should be possible in the PO, neither qty, nor price, not even the simple PO text should be allowed to get changed. In other words no field should be allowed to change.
Ideally, except the EDD field, other all fields should be in grey mode, or atleast changes in any of the PO fields (except EDD) should not be allowed to get saved after the PO is final released.
Please let me know if SAP provides any such facility, whereby you can selectively choose certain fields (like EDD field) on which Release Strategy should not be applied & changes should be allowed in these fields even after PO final release.
Thanks in advance,
Zafar.

If you go to OMET transciton and here you can assign the field selection key in the field FieldSe
and assing the User parameter EFB in user id of the user using SU3 transction
for more help see below
Create a Functional Authorization in the Following path:
Material Mangement - Purchasing - Authorization Management - Define Functional Authorization for Buyers
Now, in SU3 trxn ,Give the User Parameter EFB in the user master Parameters Tab and give the parameter value.
create the fields selction which you want use here in PO field seleciton config.

Generation of Output after Final release of Purchase Order

Hello
When a PO is subject to release procedure the output for the PO is only generated and sent when the PO has been finally approved. I would like to know is this sap standard internal feature or do we need to configure it.
If it is standard then can some throw light on what happens on background?
If it needs customization please let me know the customization details?
Regards
Mohammed

Hi,
Out put of the PO is something to do with the Release Indicator assigned for each state of release of the document.This indicator if is blocked state of a PO it prevents from outputing the message .If the indicator has the status Released by way of releasing by the concerned user than the same can be outputed.
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.
This I think is a standard behaviour of the system.
Dhruba

Problem in PR update after final release

Dear Expert,
I have problem in release PR, when PR already release (indicator release '1' -> cannot be changed), it can't be changed from ME52N. But for PR that generated from maintenance order, user still can add new item in maintenance order and PR will automatically have new item without asking new release.
Does anyone have solution for this??Thank you.
Rgds,
Desty.

Hi Desty,
This is not considered an error, please refer the question 1 of the note   493900   FAQ: Release Strategy :
1. Why can I modify a purchase requisition although I set the
     changeability of the release indicator to '1' ('Cannot be changed')
Answer.
The purchase requisition is not modifiable via a purchasing transaction
like ME52 or ME52N. But it is possible to change the purchase
requisition from any other external application like sales order,
planned order, maintenance order or network.
The Changeability functionality only concerns the purchasing
transactions. This is intended and a new release strategy determination
takes place if there is a modification of the data in the external
application.
Regards,
Mauro

Auto mail of purchase order to vendor after final approval(release)

hello all,
my requirement is that.after creation of purchse order and final release,my client want to send the puchase crder automatically to vendor via mail.
pls explain me settings for same.
i have already search the sdn threads,but not got the exact settings for this scenario.
thanx in advance for your valuable reply.
regards
simran

Hi,
You could have searched in SDN for query sending PO by e-mail to vendor. There are a lot answers. OK.
As required by you purchase order automatically will send to vendor via e-mail after final release, then set Dispatch time as 4 {Send immediately (when saving the application)} in NACE t.code in application EF for your PO output type and save. Also maintain condition record for PO output type in t.code: MN04 and keep Dispatch time as 4 {Send immediately (when saving the application)} with other parameters (document type, purchase organization etcu2026.)
For more check links for details setting e-mail setting for PO
http://www.architectsap.com/blog/sap/sap-mm-purchasing-send-purchase-order-by-mail-to-vendor-in-sap/
http://www.sap-img.com/materials/external-send-sending-po-by-email.htm
Regards,
Biju K

How to block changes in purchase order after purchase release

Dear all
Can u please tell us how to block any changes in purchase order after purchase order is released...
(We don't want any line items addition or quantity addition or any changes once purchase order is released..)We wanted this for a particular purchase order type only
Regards
Sudha

Dear Sudha
Yes it is possible to confiquire your system insuch a way where once if the PO gets final relase then it cannot be changed.Only possiblity that will be available for the user to make chanegs in PO is possible when the final release is to be reset and then make the changes.
Release Indicator: specicfies whether the PO documents is blocked or can be processed for the follow functions.
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.
And after that you can specify release statuese where you can specify which release indicator/status a PO is to have after having been released via a certain release code.
and after release simulation .
Test for the PO change after final release System will not allow you tomake changes by giving the message that the release indicator doesnot allow you make the changes in PO.
Regards
Sunny

PO Item Deletion ON Final Release

Hi ,
Can u tel me , purchase order is released by three levels of approvers then any one delete the released po line item through me22n transaction a mail should go to the all released approvers . on deletion after final release CHANGE event is triggering in SWEL...plz help me out how to solve this..
i copied standard WS20000075 to custom Z , every thing working fien , but on deletion of line item standard supports or how to approach this i am not getting ?
thanks,
sandeep..

Hi ,
After final release workflow will not be active the actual release workflow will be in completed status if all level release is complete .
So i want to send a mail to all approvers in new workflow ...
created an event deleted Ybus2012 delegation of bus 2012..
in swec transaction try to create a entry , FIELD RESTRICTIONS what to enter for my event..
when i enter AENNR , (Key for change doc. object AENNR and business object type BUS2012 are incompatible) error is coming ....
can anyone suggest me ..
thanks ..
sandeep

No amendment after PO release

Hi
I have require the solution on Purchase order.
After final release there should be not modifed Quantity /Prices
What setting we required in customizing
Thanks

hi,
One solution is :
You can make the fields as a display fields For ME22N in the display mode...so that whenever you go to the change mode of the PO you will not be able to change it...
this can be done from :SPRO>> MM>> Purchasing >> PO >> Define screen layout>> Here choose from ME22N > ANd make the fields display....
Or
You can use the changability indicator in the release strategy, if you don't allow the changed PO for the release, then automatically, it will not affect the further process...
Hope it helps..
Regards
Priyanka.P

NPE for textField text after migration from ea2 to final release , help....

I migrate an application from JSC2 EA2 to JSC2 final release
In one of my page (first page that i check after migration) I have some text field.
In a button action i used those textfields Text for some processing.
Now after i press submit key (whether text boxes are full or empty) i get null pointer exception when i try to access the textfields text
by using getTextField1().getText().toString()
can any one say where i have mistaken in my migration plane ?
Thanks

Hi,
Suggest to replace all butttons using FCS version.
There was some change from EA to FCS for buttons.
e.g. if you have multiple buttons on a Page that was created using EA
then the wrong action handler will get called
hth
John

Error compiling in FlashBuilder after downloading the final release

I've reopened my current project in the final release of flash builder and now get this error on compile.
VerifyError: Error #1053: Illegal override of updateLoadTrait in org.osmf.proxies.MediaElementLoader.
Inside MediaElementLoader I can see "@throws Error if the LoadedContext is not a MediaElementLoadedContext"
What's the MediaElementLoadedContext?

You might want to upgrade to the Sprint 10 release, which has our near-final APIs. MediaElementLoader and MediaElementLoadedContext have been replaced by other classes (you can learn more about all Sprint 10 API changes here: http://opensource.adobe.com/wiki/display/osmf/API+Lockdown+Status).

Production order status was not changed to 'CNF' after final confirmation.

Hi guru.
I experienced very special case that production order status was not changed to CNF after final confirmation.
I did final confirmation and canceled confirmation. (CNF -> REL)
And I did final confirmation again because of fixing activity quantity.
the strange thing is that production order status wasn't changed from REL to CNF.
I did confirmation again with 0 activity, thereby I solved this problem
BUT i don't know why this case happened.
Please, explain the reason.
Thanks.

Hi,
As per my observation, their is not any change in the status of the order REL with confirmation CNF, instead of this, it has change from CRTD & then to TECO.
Sequence of the status of the order as below
1) CRTD MANC NMAT SETC
2) REL NMAT SETC - Changes from CRTD to REL after releasing of the order
3) REL CNF PRC CSER ERTR OPGN SETC - After confirmation, it updated after the order REL status.
Rgd,
Chetan

Could I use jstl tag in the JSP page of Creator 2 final release?

I have a JSP page used to work well in Creator 2EA2. The page
has the following code snippets:
<c:forEach items="${SessionBean1.webQuery1.details}" var="item">
                                                    <tr>
                                                        <td class="detailKey">
                                                            <c:out value="${item.key}"/>
                                                        </td>
                                                        <td class="detailValue">
                                                            <c:out value="${item.value}"/>
                                                        </td>
                                                    </tr>
                                                </c:forEach>
...Basically, it generates a table columns.
After migrating to Creator2 final release, a fatal exception is thrown
when the page is launched :
Description: An unhandled exception occurred during the execution of the web application. Please review the following stack trace for more information regarding the error.
Exception Details: org.apache.jasper.JasperException
/Page1.jsp(148,132) According to TLD or attribute directive in tag file, attribute items does not accept any expressions
Possible Source of Error:
   Class Name: org.apache.jasper.compiler.DefaultErrorHandler
   File Name: DefaultErrorHandler.java
   Method Name: jspError
   Line Number: 43
Source not available. Information regarding the location of the exception can be identified using the exception stack trace below.
Stack Trace:
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:43)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:414)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:155)
org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes Any suggestion, or work around?
Thanks

There is something strange in the HTML for you posedt, so I cannot clearly see what you are trying to do in your JSP page. But either of the following kinds of usage would cause this kind of error:
    <h:dropDown ... items="<%= ...some Java expression ...>"/>or
    <h:dropDown ... items="${...some JSP EL expression...}"/>This is because JSF component tags allow neither Java runtime expressions nor JSP EL expressions (at least in JSF 1.1, which is what Creator 2 supports). The answer is to use a JSF EL expression instead, like this:
    <h:dropDown ... items="#{... some EL expression}"/>Craig

Changeability of PO after final release

Similar Messages

Maybe you are looking for