Cancel PO release

Hi
I have set the release procedure for PO. IN ME29N after releasing the PO i am unable to cancel the release Pls let me know how to cancel the release

Hi,
Check this link will help you.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4e/2be03b8b2a2b08e10000000a114084/content.htm
Regards,
PK

Similar Messages

Cancel the Release for PO & PR

Hi
Once PR or PO released and follow on documents are processed then release can not be cancelled .
If PR is released and Po has created , the PR release can not be reversed .
Similarly If PO released and GR has taken for that PO then release can not be cancelled .
How can I achieve this ?
Actually system allows to cancell the release even after follow on documents are processed . I obseved it in our system . Our head of Dept Released one PO and GR was taken , but afterwards he cancelled that release
Similarly If there is two step release ( R1 and R2 ) and PO was release by both . After R2 released the PO then person R1 should not able to change the PO or Cancel his release
Is there any solution to restrict such situation ? Please provide complete solution
Please help
Edited by: Bhushan Bivalkar on Dec 15, 2009 4:25 PM
Edited by: Bhushan Bivalkar on Dec 15, 2009 4:26 PM

Hi,
you can set the release status as not changeble for release indicator " Changeability of Purchasing Document During/After Release " and set the release indicator in release strategies,
rgds

Cannot cancel the release of a z segemt

Hi All,
I am getting the following error message while setting the status of IDOC segment as CANCEL RELEASE in WE31
Error while resetting release of segment Z1YV_CRRB_AUDIT
I need to add one more fields in the existing segment, but as there is error in CANCEL RELEASE of the segment i am unblae to do so.
Any help will be highly appreciated
Rgds
Kaushal

Hi,
generally first we create zsegments and then release them ten only we copy the basic type to zbasictype and then add the zsegment to it and then finally we release the basictype...This is what we do..as such in ur case it should allow u to modify the zsegment straight away when we cancel the release,but it was throwing error,so i thought to have a check at it if we relase basic type then release the segment ,may be it allows..thats why i suggested..
is it working or still u r facing some problem in it???let me know..
<REMOVED BY MODERATOR>
Regards,
Nagaraj
Message was edited by:
Alvaro Tejada Galindo

Cancellation of Release of a purchase requisition

Hi,
Currently the system allow to cancel the Release of a purchase requisition eventhought the Purchase Order already created for it.
I could not locate the any system message that actually control this.
How to disallow the cancellation of Release of a purchase requisition if the processing status is 'PO Created'.
Best regards,

Dear Eric,
We cant do cancel of PR onece PO created.not only that onece release of PR we cant cancel the PR we can do only flag the release PR.
Hope this will helps you
Prem.

Call a standard po release or cancel po release in program

Dear all,
How can I call a standard po release (me28) or cancel po release in program
to release or cancel release a po?
Thanks you
John

You need to get the report and when you double click on field ,then it goes to ME28 Transaction.
need to use set parameter id ,
see the below example and which i did in ALV ,it will call MM02 transaction.
REPORT Z_GET_REFRESH no standard page heading.
type-pools : slis.
tables : makt,
 mara.
data : i_fieldcat type slis_t_fieldcat_alv.
CONSTANTS :
gc_refresh TYPE syucomm VALUE '&REFRESH'.
data : begin of i_makt occurs 0,
 matnr like makt-matnr,
 maktx like makt-maktx,
 end of i_makt.
data : v_repid like sy-repid,
 g_user_command type slis_formname value 'USER_COMMAND',
 g_status_set type slis_formname value 'SET_PF_STATUS',
 lt_event_exit TYPE slis_t_event_exit,
 ls_event_exit TYPE slis_event_exit.
DATA:LC_GLAY TYPE LVC_S_GLAY.
select-options s_matnr for mara-matnr .
start-of-selection.
select matnr maktx from makt into table i_makt
 where matnr in s_matnr.
end-of-selection.
Fill the fieldcatlog
perform fill_field.
Call the FM
perform call_fm.
*& Form fill_field
 text
--> p1 text
<-- p2 text
FORM fill_field.
data wa_fieldcat type slis_fieldcat_alv.
clear : wa_fieldcat.
wa_fieldcat-tabname = 'I_MAKT'.
wa_fieldcat-fieldname = 'MATNR'.
wa_fieldcat-outputlen = '18'.
wa_fieldcat-seltext_l = 'Material #'.
wa_fieldcat-col_pos = '1'.
append wa_fieldcat to i_fieldcat.
clear : wa_fieldcat.
wa_fieldcat-tabname = 'I_MAKT'.
wa_fieldcat-fieldname = 'MAKTX'.
wa_fieldcat-outputlen = '40'.
wa_fieldcat-seltext_l = 'Material Desc'.
wa_fieldcat-col_pos = '2'.
append wa_fieldcat to i_fieldcat.
ENDFORM. " fill_field
*& Form call_fm
 text
--> p1 text
<-- p2 text
FORM call_fm.
v_repid = sy-repid.
LC_GLAY-EDT_CLL_CB = 'X'.
CLEAR ls_event_exit.
ls_event_exit-ucomm = gc_refresh. " Refresh
ls_event_exit-after = 'X'.
APPEND ls_event_exit TO lt_event_exit.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER =
I_BUFFER_ACTIVE = ' '
 I_CALLBACK_PROGRAM = v_repid
 I_CALLBACK_PF_STATUS_SET = g_status_set
 I_CALLBACK_USER_COMMAND = g_user_command
I_CALLBACK_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_END_OF_LIST = ' '
I_STRUCTURE_NAME =
I_BACKGROUND_ID = ' '
I_GRID_TITLE =
 I_GRID_SETTINGS = LC_GLAY
IS_LAYOUT =
 IT_FIELDCAT = i_fieldcat
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
I_SAVE = ' '
IS_VARIANT =
IT_EVENTS =
 IT_EVENT_EXIT = lt_event_exit
IS_PRINT =
IS_REPREP_ID =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IT_ALV_GRAPHICS =
IT_ADD_FIELDCAT =
IT_HYPERLINK =
I_HTML_HEIGHT_TOP =
I_HTML_HEIGHT_END =
IT_EXCEPT_QINFO =
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
 TABLES
 T_OUTTAB = i_makt
 EXCEPTIONS
 PROGRAM_ERROR = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " call_fm
 FORM USER_COMMAND *
FORM user_command USING r_ucomm LIKE sy-ucomm
 rs_selfield TYPE slis_selfield. "#EC CALLED
data i_RSPARAMS like RSPARAMS occurs 0.
CASE R_UCOMM.
 WHEN '&IC1'.
 read table i_makt index rs_selfield-tabindex.
 SET PARAMETER ID 'MAT' FIELD i_makt-matnr.
 if not i_makt-matnr is initial.
 call transaction 'MM02' and skip first screen.
 endif.
 when '&REFRESH'.
 CALL FUNCTION 'RS_REFRESH_FROM_SELECTOPTIONS'
 EXPORTING
 CURR_REPORT = v_repid
IMPORTING
SP =
 TABLES
 SELECTION_TABLE = i_RSPARAMS
 EXCEPTIONS
 NOT_FOUND = 1
 NO_REPORT = 2
 OTHERS = 3
 IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 submit z_get_refresh with selection-table i_RSPARAMS.
 rs_selfield-refresh = 'X'.
ENDCASE.
MOVE '&REFRESH' TO r_ucomm.
ENDFORM.
 FORM set_pf_status *
FORM SET_PF_STATUS USING rt_extab TYPE slis_t_extab.
DELETE Rt_extab WHERE fcode = gc_refresh.
SET PF-STATUS 'STANDARD_FULLSCREEN' OF PROGRAM 'SAPLKKBL'
 EXCLUDING Rt_extab.
*SET PF-STATUS 'STANDARD' EXCLUDING rt_extab.
SET TITLEBAR sy-tcode.
ENDFORM.
Thanks
Seshu

Cancel the Release to Accounting but not the Billing Document

Hi Gurus,
Is there a way to Cancel the release to accounting billing document but it will not cancel the billing document. I can't cancel the billing documen because it is already used as a reference to one of our orders.
I hope you can help me...
Thanks a lot!
Mon Magallanes

Hi,
As per my understanding the accounting document in itself cannot be canceled. Because once the posting is done it will be reflected in the PL. If you cancel the billing document itself then the Accounting entries would be reversed.
Thanks,
Mukund

How to cancel the release of the current segment definition-WE31-IDOC?

Hi Experts,
Am trying to add a new field to a existing custom segment type/defination. This segment type is already using in the system.
So, went to WE31 and pressed the PENCIL button for changing/adding my new field, but am geting the below message,
(1)pls let me know that does it mean CANCEL the release (Menu>Edit>Cancel Release)? if so, Can I go ahead and use this CANCEL the release? do I need to take any pre-requisites as this segment is already relased?
(2)But, you know there is another option saying 'ADD VERSION-Shift+F5', if I choose this option, its also taking me to a screen where in I can add new fields so which is correct option for me is it either (1) or (2)?
Current segment definition Z_segment_defination can no longer be changed
Message no. EA666
Diagnosis
The current segment definition Z_segment_defination of segment type Zsegment_type is already released.
System Response
The segment definition cannot be changed.
Procedure
You can either add a new segment definition or cancel the release of the current segment definition.
Thank you

so i tried to CANCEL the release by goiong menu pathEdit-->Cancel the release, but am getting the below error, How to fix it to add my new field?
Error while resetting release of segment
Thank you

Cancel the release and change the z segment in new version.

Hi,
I have a Z segment created in 4.6c.
Now we have upgraded to ECC and i want to change one of the field ( i.e data element of the field ) and I am not able to change it.
It gives me the hard error. I am unable to cancel the relase and do the modication.
If I try to add a version it doesnt accept it with out any additonal fields.
I have tried deleting the segemnt in Basic type and tried deleting the whole segemnt, but it doesn accept this way too.
Any ideas how to go about it?
Thanks,
Krishna.

Hello,
I had a similar problem when I tried to delete fields from a segment. I also wasn't able to cancel the release of the segment and the release of the extended idoc type.
The reason seems to be that the idoc extension and the segment have been set to "released" in a lower release version of the sap-system.
I was able to edit the segment when I changed the corresponding table entry in EDISDEF and set the release to the current one. However that is no solution I would like to propose.
Anyway the problem could have something to do with the release of the the sap-system. In this case I would be glad if someone could offer a solution which is more close to the standard than editing the system tables directly.

Cancel PR release

Dear friends,
Current scenario to Cancel PR Release & Cancel PO Release are as follows:
Cancel PR Release
u2022     Three level of release is available B2, B3 & B4.
u2022     First all threecodes release the PR, Status was 2 (RFQ/PO).
u2022     If B2 will cancel his release then approval of B3 & B4 will also got rejected. Status is blocked.
u2022     If B3 will cancel his release then approval of B4 will also got rejected but approval of B2 will be valid. Status is blocked.
u2022     If B4 will cancel his release then approval of B2 & B3 will be valid. Status is blocked.
Cancel PO Release
u2022     We have 3 level of release for PO: B1, B2 & B4
u2022     First all three codes release the PO, Status was R (Released).
u2022     Then B1 cancel his release. But B2 & B3 releases did not get cancelled. Status is B ( Blocked)
u2022     B2 cancelled his release. But B1 & B3 release did not get cancelled. Status is B ( Blocked)
u2022     B3 cancelled his release. But B1 & B2 release did not get cancelled. Status is B ( Blocked)
Please tell me which process is correct.
I think cancel PR release is correct.
Please correct me if I am wrong, to implement these changes in Cancel PO Release I need to change the release prerequisites of PO release strategy.
Regards
sapmm1234

Hi,
Release steps are same for both PR and PO.
It depends on how u select pre requisites in spro
Release for PR
     B1
     B1     B2
     B1     B2      B3
If B1 cancels release after B3 approval (final approval) then approvals of B2 and B3 get revoked and the status will be shown as cancelled release at B1
The above logic is applicable for PO as well.
Yes what u mentioned for PR release is correct
Regards,
Uzair

CANCEL PR release as per the sequence

Hi
We have two levels of release for PR, the first level is release and then the release goes to second level and the second level release takes place. This is working fine
But when the user cancels the release. The cancel release for both the levels taking place when the first level user is cancelling the release.
My user want the cancel release should also take in sequence that is the second level has to cancel the release and the first level.
Iam not finding any authorisation object for release cancel. i also trie dwith release indicator not changeable but not happening.
Kinldy let me know if any one have a solution for the same.
chris
Edited by: CHRIS MM on Jun 30, 2009 6:35 PM
Edited by: CHRIS MM on Jun 30, 2009 6:35 PM

Dear,
have you checked your assignment in release group-Release code -plant-Agent ID are assigned properly or not..
Check this in:
Spro-Materials Management-Purchasing-Purchase Requisition-Release Procedure-Procedure with Classification-Set Up Procedure with Classification-Workflow..
Here check , i think your all users are assigned for all tracking numbers here.
Also check your tracking number assignment in the release strategies, whether it is assigned properly or not.
reagrds
Utsav

Cancel PO - Release strategy remains active... WHY?

Sometimes, when I cancel a Purchase Order with the bin, the release strategy remains active and the approver finds the PO among the ones he has to approve, even if it has been cancelled. In many other cases, instead, when I cancel a PO the release strategy correctly disappears.
Could someone let me know why the release strategy remains active?
Thank you so much.
Fabio

Thank you for your reply but I don't agree at all with you.
In many cases, the most cases, when I delate a PO the release strategy disappears. Sometimes it remains active and I don't understand why.
The approver shouldn't see these delated PO's among the ones he has to approve.
Thanks again.
Fabio

Cancellation of Release Procedure for PO

Hi All,
We have configured 4 step realesed stretegy for PO. Releasing is working fine but we are facing probelm in cancellation.
In cancellation any step you can cancle at any step . But What we want if approval is done R1 >R2> R3> R4 same way cancellation would also follow R4>R3>R2>R1.
However currently system allows even R1 to allow cancel a fully released PO . When R1 cancle than all realease status R2>R3>R4 is also set to unreleased.
How to stop this and allow system to follow same hirarchy in cancellation also.
Thanks
Sanjay

Hi,
Once you create the characteristic and class.
You click on release procedure for Purchase orders.
Click on Release Groups.
enter your release group and release class.( If there is release group already add your release class to it).
Come out and click on Release Codes.
Enter your release codes for your release group. save
Come out and click on release Indicators. Enter release indicators and save.
Click on Release Strategies and Enter your release strategies and click on
There will be step by step procedure to give your amount for charectristics that u maintained.
pls follow that.
Thanks
Asini

Error When canceling the released idoc ?

Hi All,
I am getting the following error when i try to cancel the releaseed idoc.
" There are already views referring to extension ZG_ORDERS05. The release can only be reset if no assignments between views and extensions exist. "
Can anyone tel me how to solve this error and add a new segment to the released idoc ?
Thanks.

hi,
i think you are using a view for this idoc.
1. Check: WE20 and open your receiverdetermination.
2. Open your Outbound parameter settings
3. check the view settings at the bottom of the first tab. Are you using a view ?
if yes... check transaction WE32 and remove the view.
maybe it´s useful!
Gordon

Cancellation of release strategy

Hello to all,
i have release strategy defined for purchase requisition and i want that when a post is deleted from the purchase requisition, the release strategy is canceled and must be released again.
How to setup this.
Regards.
Zied.

Hi ,
In the release indicator mention 4 for chageability and mention some % for the value change.
You have to check your scenario for the release indicator.
Also for change in value only Release strategy will be reapplied and not in any other case.
Regards
Ankur

Cancel IDoc release

Hi,
I want to delete a segments from a released basis type that has been released in release 640.
We currently have release 700.
When I try to cancel the IDoc's release, I receive an error message noting that the release can no longer be removed.
There is an option to create a successor to the basis type in order to further develop it, but I only want to delete segments.
Any ideas ?

Hi,
go to Tcode WE19
Open your idoc here and Delete the Unwanted segments.
Then process it using Standard inbound ..
Regards,
Kumar

Cancel PO release

Similar Messages

Maybe you are looking for