Changes in Released po

Hi,
I made one PO. Got it released and after that i was able to change the rates in PO, which shouldnt have actually happened.
For further changes i should have revoked the release and did the changes.....
What is wrong with my release startegy?
Regards,
Satyendra

Dear Sat,
In the release indicator that u used in the release strategy, maintain the changeable value = "1", so no change can be made after release using the release indicator, and need to revoke the release first to able the change, please check.
Regards,
w1n

Similar Messages

Error message needs to be generated in case of change in released PO.

Hi all,
please help me how to solve this issue
<b>issue1:</b>
Error message needs to be generated in case of change in released PO.
1) change in incoterms,
2) payment terms,
3) quantity
4) rate.
The system should allow for change on the higher side.

Hi ,
I think you point no 3 & 4 can be solved using option available in release startegy and for point 1 & 2 u have to try with some user_exits. I think so , others can comment on this .
Thanks
Dipak

Restrict to change the released document

hii all,
i am seeking for a suggestion whether its avalable in standard sap or not.
i want to restrict to change the released document. once,document has released, then chage shud not affect.
thanks.

Hi,
For this you only need to set the changeablity from the release indicator to "1".
Best Regards,
Arminda Jack

Po header change after release

Dear All
We require list of PO for last one month PO header or tiem level text has been changed after release
Regards
Dishant

Hi,
You can use the following report to get you all the changes in PO. Ask your ABAP person to run it for you.
http://www.sap-img.com/mm001.htm
It is an ABAP program contributed by one of the SAP members, which reports all the changes made in PO and list out the details per document.
Hope it helps,
Best regards
Amit Bakshi

Po change after release and printout

Dear Experts,
My client require if we change the PO in any field ( expect qty and amount ) our po should be go in the po release again we using release indicator 4 and 6 but we want release should be go if we change any field like date tax code text payment terms etc.
RCR

Hi,
System determines new release strategy only if there are any changes in the characteristic values in the PO. (The characteristics that you must have defined for the PO release strategy configured in your case, like PO value, document type, Plant, etc.)
By your question, it appears that you do not want to change even the date and text fields after PO is released, and in case you do the changes, then again the PO has to be released.
For this, you need to use the release indicator, which won't allow any changes after PO is final released. Hence, when any of the field is required to be changed, the release will be required to be cancelled first, then the changes can be done. After doing the necessary changes in your fields, like, date, text, etc., PO will again be subjected to release, and will have to be released again to proceed further.
Regards,
Zafar.

Purchase order changes after release

Hi,
How can I block a purchase order to any changes after release it and then, in case of need, mark for deletion the purchase order itens?
Regards,
Maria

Hi,
To block any changes in the purchase order to after release, set Changeability indicator as 1 for Release ID "R" in following path & save.:
SPRO ->MM - Purchasing -> PO -> Rlease Procedure for PO -> Define Release for PO -> Release Indicator
NOTE:If you set Changeability indicator as 3, PO can be changed after release and trigger a new release strategy based on value changes.
Regards,
Biju K

How can Change PO Release Indicator to Released Status

Hi Gurus,
We are having an issue here, which user accidentally re-triggered customized program to re-trigger the release strategy of old PO documents.
This program basically reset the PO release startegy status and update the PO with the latest PO release strategy configuration. It's using FM ME_REL_STRATEGIE_EKKO.
So, currently some of the old PO which previously been fully released and closed PO (with GR & IR completed). So, we dont think that it's right for these old PO to be approved again, also the relevant approvers also refused to do so.
Is there any way that we can use the same FM to change the release indicator to R from S? Appreciate your help. Thanks!
Regards,
Michelle

may i suggest you accidently trigger the program to close the release strategy for all POs by modify class characteristics.
and then reopen the release strategy for necessary POs.
or maybe, you can trigger the program to close the release strategy for old POs.
please see below for details:
How to turn off Release strategy
Edited by: JiQing Zhao on Jun 14, 2011 1:19 PM

PO status if you change the release strategy procedure

What will happen to the half released PO/PRS if we change the release strategy?

Hi,
It won't Happen for Half release PO Document. The rerelase will get affect once the final release done or No release initiated to the document.
SAM

Detail changes for release creation on schedule aggreements

Hi Experts,
Landscape:
-we have a standard ERP 6.0 system with an external EDI converter
-IDoc data exchange via RFC connection
-IDoc SAP standard (without modifications or add ons): message type: DELINS, basic type: DELFOR01
If we create a release on a schedule aggrement, all schedule lines in forecast comes out as expected.
When we delete some schedule lines, these lines exported to IDoc with quantity 0 and have an aggregation per week. So we have the following structure in IDoc:
E1EDK09 (head data)
|-E1EDP10 (pos data)
      |-E1EDP16 (schedule line): aggregation per week (IDoc field PRGRS = W), quantity 0
      |-E1EDP16 (schedule line): aggregation per day (IDoc field PRGRS = ' '), quantity 10
      |-E1EDP16 (schedule line): aggregation per week (IDoc field PRGRS = W), quantity 200
      |-E1EDP16 (schedule line): aggregation per week (IDoc field PRGRS = W), quantity 200
      |-E1EDP16 (schedule line): aggregation per month (IDoc field PRGRS = M), quantity 9000
So far so good. This looks fine.
But our standard EDI converter expect the IDoc data starting with days, weeks, months aggregation. If the first schedule line with aggregation weeks are send, the converter expect all other schedule lines with aggregation per week or per month.
It is possible to change the release creation in the IDoc without coding in User-Exits, just with customizing?
regards,
Steffen
Edited by: Steffen Froehlich on May 3, 2010 1:31 PM (accidentally clicked on Post than Save button)

Hi,
   Go to MN04 transaction and maintain the "Date/Time" as 3 for the specific output type condition record as shown below:
   Test the scenario again with a new PO. Now, system wont generate the spool immediately after release and save in ME29N and the output will be "in process" mode (yellow signal). You can process the output in ME9F transaction to display and print.
Regards,
AKPT

Will releasing my app in iTunes connect change the release date?

Hi there,
I have an unusual situation. We submitted version .9 of our app to the appstore, and it was approved. Even though the game is not done, we did this because we wanted a version that we could submit to the Indiecade festival (deadline today!), and we wanted to be able to send them a promocode rather than have to go through all of the hoops of UDID and all that.
We have a release date set for far in the future, and we also have the game set to 'pending developer release'.
Even though the game was approved and is ready for us to 'release' to the store, it wont yet spit out promocodes for us yet, because it is not 'live'. I want it to go live, but not actually be available on the store. I think this will work, I'm just concerned that if we push that button, it will change our release date and actually make the game available on the app store.
Can anyone confirm that this is NOT what will happen? I hope I'm making my situation clear. Thanks very much.
Chris

I would suggest you contact the iTunes Store via your iTunes Connect account and ask them. That's the way you'll get definitive answers; we're all just fellow users here.
Regards.

LCM Change and Release Management - How to maintain job integrity

Hi
We are using BO in a three scale landscape. DEV, QA and PRD are all are in a same network. I installed Business Objects Life Cycle Manager 3.1 SP3 on my dev system.
I created a job for DEV -> QA. (Multiple iterations - for changes in DEV while testing)
Once the final version is tested in QA, those objects suppose to be moved from QA -> PRD not directly from DEV -> PRD. Because when i make a copy of the existing job, that's not allow me to change the source system.
Now, my question is, I want to maintain integrity of job promotion, means I want to move the same objects which tested in QA to PRD,
1. DEV -> QA -> PRD. Is it possible in LCM or any other tool?
2. Is it possible to change the source system of LCM jobs?
3. To maintain the interity, is it required to create two jobs
DEV -> QA - Job1
QA -> PRD - Job2 (With same objects as in Job1)
4. What is the right approch for BO Change and Release Management?
Thanks
Deep

Same query as in How to maintain LCM job integrity while promoting?
Please do not cross post. See the [Rules of Engagement|http://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement].
Closing and locking this thread as the one mentioned above is in the correct forum.
- Ludek

Blocking Changes in Released Process Orders

Hi Experts,
I need to block manual changes in Released Process Orders ( both in quantity and date) in APO. So, I need some userexit/BADI/FM which can help me to stop this change.
Can anybody suggest something for this ?

Hi Ulrich,
Can you please explain a bit further --when this BAdI comes into picture ? When you save the Product view ?
Is there something similar for Detailed Scheduling Planning Board also ?

[Fake News] Arch Linux to change its release cycle

Today the Arch Linux community proclaimed that Arch Linux will change its release cycle and version numbering, as this was requested by billions of corporate goonies, Freemasons and Illuminati throughout the universe.
Releases will henceforth be scheduled in intervals deemed posh by the GNU/Linux community at the particular moment. The version numbering will be based on year the a new release is being published. Arch Linux "2016" will be released in early 2006. All following releases will have an offset of at least 10 years to underline how much more pure dead brilliant Arch Linux is compared to Mandrake.
To achieve a smooth transition, an transitional release will be made at once, named "Useless Marketing Edition". The Arch Linux FTP server will be configured allow one download of the iso image only. This will also be an experiment to find out how the community will be able to spread such a limited edition.
An Arch Linux user who wishes to remain nameless said in an exclusive interview with the almighty incinerator: "This is a great opportunity for Arch Linux, the new release numbering will confuse and divert computer illiterate lusers from installing our beloved Arch Linux, freeing us from answering stupid support requests. Now we can finally start to work towards our ultimate goal: To become the only GNU/Linux community being as elitist as OpenBSD's."

Ach guys, you don't get it :-(
The version numbering scheme was supposed to mock the fact Mandrake plans to release their "2006" version in 2005. That reminds of old times, when (computer) magazines were trying to beat each other releasing the most up-to-date issue to the market. The whole affair became absolutely silly, there were magazines that had the "April" issue hitting the shelves at the end of January. These "issue number wars" occur every now and then.
The funny scenario I can imagine is that other (GNU/Linux) vendors could jump onto that train and "predating" their releases further and further.
The rest is just various mockery about lusers and other things found in the Mandrake's press release. And of course the arrogantly elitist OpenBSD community always deserves getting their arses whipped ;-)

Need to shift to HANA , from Change and release management

Hi All,
Please advice me, I am working as Change and release coordinator , which is technology independent, i have hands on SQL and Mainframe, now i would like to shift my career to SAP HANA, please advice if this is a suitable option

Hi Chandru,
You have a very good job as a change and release coordinator. Why don't you try SAP Release Management job in project because it is a niche and good. If you learn SAP Solution Manager ChARM then it will take you to SAP Release Management job.
If you still looking for SAP HANA, then it can also suits but you can check SAP HANA Administrator. However, check out the option as SAP Release Management job.
Best of luck.
Regards
GGOPII

A problem about change request release se10,urgent!

hello,everyone,
when I use tcode se10 to release my change requestno,
an error occured:
'test call of transport control program (tp) ended with return code 0232',what it mean?who knows?
pls give me help,.thanks very much.

Hi Niuniu,
Try this to vaoid the problem.
On Transport Domain Controller:
- goto /nSTMS
- Overview -> Systems
- Click client then select u2018SAP Systemu2019 -> Update Configuration (Ctrl+F2)
- Extras -> Generate RFC Destinations
- Repeat this for Controller instance itself ! ! !
On Domain Clients:
- goto /nSTMS
- Overview -> Systems
- Client its instance (eg DEV) then u2018SAP Systemu2019 -> Update Configuration (Ctrl+F2)
- Extras -> Generate RFC Destinations
Dont forget to reward points if found useful.
Thanks,
Satyesh

Internal change after Release

Hi
Scenario
We are using internal order (Investment) for capital budgeting.
We have created two roles a)Z_FI_IOCREATION for order creation, change
and display and b)Z_FI_IORELEASE exclusively for releasing the order.
End users create the order and their HOD's release the oders.
Requirement
End users can change the order n number of times but only before
Release of the order.
After release of Order if the order is changed by end user the orders
should be available for Release again. This way we contol the change of
orders after approval. How this can be addressed.
Regards
Ganesh

Hi,
Try whether you do not give authroization for change of Internal Order through transaction code KO02.
Trust this helps much!
Cheers!

Changes in Released po

Similar Messages

Maybe you are looking for