ME_PROCESS_PO_CUST method PROCESS_HEADER to reset release status of doc

Hi Everyone,
I have read lots of threads regarding the implementation of BAdI ME_PROCESS_PO_CUST. However, I could not find one which fits our requirement which is the resetting/ restart of the release status of a PO whenever a released/approved PO has been changed not only in the quantity field but also in the other details of the document.
I believe that the method to be used in this sense is the PROCESS_HEADER. Would you know any logic which could help me restart an already released PO document whenever any changes have been made to the document?
Kindly send your recommendations.
Thanks and regards,
Reymar

Hi,
I used this code:
CALL METHOD im_header->get_data
RECEIVING
re_data = lmpoheader.
IF lmpoheader-frgke = 1 AND
lmpoheader-frgzu IS NOT INITIAL.
lmpoheader-frgke = 2.
lmpoheader-frgzu = ''.
CALL METHOD im_header->set_data
EXPORTING
im_data = lmpoheader.
ENDIF.
After saving the PO document, the fields FRGKE and FRGZU were not changed. When I debugged the code, the values of the fields were changed. I just don't know if the last CALL METHOD has been properly executed so that IM_DATA may contain the changed values.
Thank you and regards,
RE
Edited by: Reymar Ellazo on Apr 21, 2009 6:19 PM

Similar Messages

EXIT_SAPLEBND_002 of M06E0004 User exit to Reset Release Status if PO

Hi All,
I have implemented a user-exit EXIT_SAPLEBND_002 of M06E0004, as advised, which can reset/cancel the release status of a certain PO document when a certain field has been changed aside from the quantity and price fields.
I would just like to ask if how woud the exit know if something in the document has been changed by the user if he goes to me22n? Basically, the requirement was that everytime a user changes the partially released PO in the header data and other fields aside from price and quantity, the release status should be reset to start all over again.
I have this code, but this should only be ran if a partially released PO has been changed in most of its fields (header/item).
DATA: wa_ekpo TYPE ekpo,
 wa_bekpo TYPE ekpo,
 lv_frgke TYPE ekko-frgke,
 tx_ekko TYPE char200,
 tx_ekbe TYPE char200,
 lv_frgzu TYPE ekko-frgzu.
FIELD-SYMBOLS: <fs_ekko> TYPE ekko.
tx_ekko = '(SAPLMEPO)ekko'.
ASSIGN (tx_ekko) TO <fs_ekko>.
If <fs_ekko>-frgke = '1' AND
 <fs_ekko>-frgzu IS NOT INITIAL.
<fs_ekko>-frgke = '2'.
<fs_ekko>-frgzu = space.
ENDIF.
UNASSIGN <fs_ekko>.
Kindly send some recommendations.
Regards,
RE

Add this code in user exit exit_saplbend_002 .
Code=> This code use to change release status on PO amount decrease and increase.
================================
**** Start of changes for Release status change on PO amount decrease .
E_CEKKO = I_CEKKO .
DATA : wa_bekpo type BEKPO,
 wa_ekpo TYPE ekpo,
 WA_CEKKO TYPE CEKKO,
 w_reset(1) TYPE c VALUE 'X'.
if sy-tcode eq 'ME22N' OR sy-tcode eq 'ME22'.
WA_CEKKO = I_CEKKO .
IMPORT WA_CEKKO = WA_CEKKO FROM MEMORY ID 'ZREL_COST'.
IF SY-SUBRC NE 0.
EXPORT WA_CEKKO = WA_CEKKO TO MEMORY ID 'ZREL_COST'.
ENDIF.
ENDIF.
if ( sy-tcode eq 'ME22N' OR sy-tcode eq 'ME22' )
and sy-ucomm eq 'MESAVE' or sy-ucomm eq 'MECHECKDOC'.
*Import/Export the origninal values.
*Check if the limit is passed.
LOOP AT it_bekpo INTO wa_bekpo .
SELECT SINGLE NETWR FROM ekpo INTO wa_ekpo-netwr WHERE ebeln eq wa_bekpo-ebeln and ebelp eq wa_bekpo-ebelp.
IF SY-SUBRC EQ 0.
IF wa_bekpo-netwr < wa_ekpo-netwr.
 w_reset = 'X'.
endif.
ENDIF.
ENDLOOP.
*IF limit passed - reset the value to high limit beyond tolerance.
IF w_reset = 'X'.
E_CEKKO-GNETW = WA_CEKKO-GNETW + 1000000.
ENDIF.
endif.
**** End of changes for Release status change on PO amount decrease .

Error while resetting release of segment

Hi Experts,
We have one custom IDoc.I am trying to add new field to one of the segment.So i am trying to cancel release status of segment using we31.But i am getting error Error while resetting release of segment ZXXXXX Message no. EA259 .I checked many of SDN threads but no where exact solution is mentioned for this.Current release for the message type is 701.so we are on same version now also.I put a break-point in LEDIJF05 in form CHANGE_CLOSE_SEGDEF.i observed it is failing at line 625 and
can not unclose segment: release of last version is not SAP-version*.Can any body tell me what is the exact issue.
Thanks in advance,
Vijay

Hi Vijay,
If the SAP version and the version segment released last time is the same, then this problem should not occur. If you are still facing the issue, add a version to the existing segment. You should be able to add the new field then.
Regards,
Parthiban

ME38 resets Release strategy of Scheduling agreement

Hello,
It seems when the users change the delivery date in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
I cannot understand why this happens.
Has anyone encountered such a problem before.
Thanks
Sunil

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

PO release status is not updated.

Dear Expert,
Configuration of PO Release Strategy:
Release Indicator B & R.
Indicator B : Changble field is 4
Indicator R : Changble field is 1 ( Cann't be changed)
Note : For PR , Business case is same , Upon final release users are not allowed to change the PR & PO.
Transaction:
1. PR Creation & Release --- Working fine.
1. PO w.r.t PR Creation & Release --- PO release ( ME29N)status is getting changed from B to R, But release status of PO getting reset from R to B when I am trying to View/Change/cancel Release ME23N/ME22N/ME29N.
When I am using the above said T-Code, there I am seeing that PO is un-release, Though I ahve released the PO.
I am not able to understand why system is behaviing such way.
Help me out to resolve this issue.
Rgds,
Manoj

Hi,
Keep Changeability Indicator BLANK in Indicator B & for Indicator R , you can keep Changeability Indicator 1 ( Cann't be changed) as your business required in configuration of PO Release Strategy:
For Example:
Release Indicator B & R.
Release ID..........Released.........Changeability Indicator.........Description
Indicator B ........{ }..........................{ }......................................Blocked
Indicator R ........................................................................Released
Now try creating PO & then release, sure it will work.
Regards,
Biju K

ME51(2/3/4)N Reset release purchase requisition

Hello,
I need to reset the issue of the purchase request after a specific condition occurs.
To reset the issue I found the user exit EXIT_SAPLMEREQ_010
(Includes ZXM02U12 MEREQ001 and extension).
I first used this function:
 CALL FUNCTION 'ME_REL_STRATEGIE_EBAN'
 EXPORTING
 i_eban_new = wa_im_eban
 I_EBAN_OLD = IM_T_EBAN_PERS
 I_EBKN_NEW = IM_T_EBKN
 I_EBKN_OLD = IM_T_EBKN_PERS
 I_XCLASS =
 I_CHANGE_OK =
 I_CHECK_ALWAYS =
 IMPORTING
 E_EBAN = wa_eban
 E_RESET = wa_ereset
but I did not understand how to use it.
Then I used the field-symbol:
DATE f_FRGKZ (30) VALUE '(SAPLMEREQ) EBAN-FRGKZ'.
FIELD-symbols <FRGKZ>.
ASSIGN (f_FRGKZ) TO <FRGKZ>.
 MOVE 'X' TO <FRGKZ>.
But a dump is generated on the move: Error at assignment: overwritten protected field.
HELP ME - I don't know what to do.
Edited by: Ermelinda86 on Jul 8, 2010 10:36 AM

Hi Ermelinda86,
I had a problem similar to what you're experiencing. I solved by changing appropriately customizing.
The route from the transaction "spro" is as follows:
Material Management --> Purchasing ---> Purchase Requisition ---> Release Procedure -
> Procedure with classification ---> Set Up procedure with classification -
> Release Indicator
Material Management --> Purchasing ---> Purchase Requisition ---> Release Procedure -
> Procedure with classification ---> Set Up procedure with classification -
> Release Strategies ---> Release Statuses
I also found a useful guide at this link:
http://www.sap123.com/a/59/
Bye
Prode

Reset release

we have one PR (already released and get five level approval)and PO(already done GR/IR).
now, is there any way we can reset the release status(from approval to initial release status for the PR?), how to do it?
Thanks

Hi,
After PR approved(released), Purchase Order created and also GR/IR done. Now, it not is possible to correct PR quantity or PR release revoked because for that PR already done PO and GR/IR(link available with PR).
If you want any emergency PR release revoked the following steps are doing :
a) GR/IR canceled after that
b) PO line item canceled, now PR opened (PO link canceled) and then PR release double click, the release revoked and any modification to be done the particular PR.
Hope, it is useful for you.
Regards,
K.Rajendran.

Reset Release while editing in VA02

Hi All,
I have activated status profile and selected the object types below.
Sales Order Header
Sales order item.
I have created the following in BS02.
10 CRTD Create SO 10 30 1 1 - Create Delivery - Forbidden (for User1)
20 REL Release SO 20 30 1 1 - Create Delivery - Allowed (for User2)
Now, the problem is, after releasing, if user1 is editing something in VA02, it should reset release. And, again release should be done by user2. I checked in status profile for reset release for CRTD status. But i did not find anything. Please help.
Regards,
Rosh

Hi,
I dont think it is possible to reset the status. You can look for user exit at sales order save to re set the status. In short it will be a development and not a standard config.
Regards

BI_PROCESS_TRIGGER event job in released status ONLY

HI ALL,
I WANT TO TRIGGAR PC TWICE IN DAY 5 PM AND 2AM.
1.I CTEATED EVENT IN SM62 (ZSDPC_EVENT)
2.I CTEATED SE 38 PROGRAM (zsdpp_pc_event_program )LIKE BELOW
REPORT zsdpp_pc_event_program.
DATA: gv_time TYPE sy-uzeit,
 eventid TYPE btceventid.
gv_time = sy-uzeit.
eventid = 'ZSDPC_EVENT'.
IF ( gv_time GE '170000' AND gv_time LE '170000' )
 OR ( gv_time EQ '020000' AND gv_time LE '200000' ).
CALL METHOD cl_batch_event=>raise
 EXPORTING
 i_eventid = eventid
 EXCEPTIONS
 excpt_raise_failed = 1
 excpt_server_accepts_no_events = 2
 excpt_raise_forbidden = 3
 excpt_unknown_event = 4
 excpt_no_authority = 5
 OTHERS = 6.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDIF.
3.I SPECIFIED AFTER EVENT IN MANAIN VARIANT .ACTIVATED AND SCHEDULED PC
4. THEN RUNE THIS PRORGAM IN SM36
BUT MY PROBLEM IS IN SM37 JOB BI_PROCESS_TRIGGER event job in released status ONLY
please guide me if i am wrong .
REGARDS,
KP

It is supposed to be in Released status.
The BI_PROCESS_TRIGGER job is scheduled to run based upon the event being triggered (from your ABAP program). The only thing this job does is trigger the event that runs the next process in your process chain. If you set up the Start variant in your PC to schedule "After Event" and you set the periodic flag, then after the BI_PROCESS_TRIGGER job finishes, it will reschedule itself. So, there will always be a BI_PROCESS_TRIGGER job in a Released status.
Again, the BI_PROCESS_TRIGGER job does not run the entire chain. It only triggers the next processes in your chain.
Does this help?
PS. Are there any BI_PROCESS_TRIGGER jobs in a Complete status? If not, then there is an issue with your ABAP program.
Edited by: Geo on May 4, 2009 11:13 AM

Release status

hi experts,
i want to know about Release status.
what is use of it?
where ll be use such release status?
if helpful answer points ll be rewarded.
thanks,
velmurugan...

You have already been told that this field is for information only, and that SAP's own use of the field is inconsistent. So it is not possible (in my opinion) to say how you should interpret the different values. I can tell you what I think:
Obsolete should mean the workflow is no longer in use (no new workflow instances will be started) - possibly because it has been replaced by a new workflow template.
Released should mean the workflow has been tested and accepted, and has now been released for use in a productive environment.
Implemented should mean the workflow has been developed and is being tested.
Modeled is a status I am more uncertain about. Possibly used to indicate that the steps have been defined, but the development (e.g. of BOR/Class methods) has not been completed.
Not defined seems quite pointless to me. One question is whether it refers to the release status itself (i.e. no release status has been defined) or to the workflow (i.e. the workflow has not been defined (yet)).
In summary: don't worry too much about the release status of workflows. I would recommend setting it to "Released" when a workflow is ready for production, and that's the only important status. Well ... almost the only one. "Obsolete" is equally important.

Report for Service Eetry Sheet Release Status

I have created a Service Entry Sheet which has 4 Levels of approval. How will I come to know which level is completed and which one is pending?
Is there any standard report available?

Hi,
then create z report
use
     ESSR-FRGGR - release group
     ESSR-FRGSX - release strategy
     ESSR-FRGZU - release status
     ESSR-FRGKL - release indicator
     ESSR-FRGRL - release not yet completely effected
Regards
Kailas Ugale

Release status of a function module

Hello,
how can I find out (where) the release status of a function module (if a function module has a status "released for customer")?
regards
zeno

- start SE37
- click on the "attribute" tab
- check on the right section in the bottom area
Markus

Include the Content Released status flag in default WC data control

Hi,
We have integrated custom webcenter portal application with UCM for documents integration. The integration was done using default data control.When we change the document which is getting displayed in the portal from UCM and check it into the system, wokflow gets triggered properly and the content status shows review status. But when we access the document in the portal, at that point of time new document is visible even though the content is still not released from the system.
Can anyone of you let me know how to include the released status of the content in the default data control so that we can avoid this situation
Regards,
Boopathy

First of all, I think this is more a question to WebCenter Portal, because it is how WebCenter Portal components are written.
Another thing is, that this is probably 'works as designed' and there might be good reasons for that. Since PS3, WebCenter (Portal) exposes some of UCM's functionality, among them ability to approve items in a workflow. This is the reason why it makes a good sense that items are available. Of course, they should be available only to approvers; also unapproved items should not appear if an item is displayed via Content Presenter (compare to a document published on a website via WCM). If you found such a behaviour, please, report it to MetaLink as it might be a bug.

Table for PO release status

hi,
im developing PO Smartform.in that i have to display PO release status ie; whether it is released or not released(ME22N----->click on HEADER--
>click on RELEASE STRATEGY).from which tables i can fetch this data .please help.

Hi
Take the fields from EKKO that are related to PO release startegy
FRGGR
FRGSX
FRGKE
FRGZU
and check the tables
T16FG
T16FS
T16FB
for the release codes
Reward points for useful Answers
Regards
Anji

Reset Release Strategy for any change in the Purchase Order

Hi,
Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
If so, where do we need to make the configurations.
I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
Thanks in Advance.
S.Raghavan

hi sandesh,
sorry, i know it's too late.
i tried your suggestion, it works blocking the purchase order after release strategies are setted.
sandesh, raghavan:
i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
regards
f

ME_PROCESS_PO_CUST method PROCESS_HEADER to reset release status of doc

Similar Messages

Maybe you are looking for