Release strategy H8 Update

Hi Experts,
We wanted to know who changed the release strategy H8 value  in our SAP system.
Found that PRD System release strategy GT value has been updated somehow with in six months.
please let us know how to check find out who updated value?.
Thanks
Malai

Hello Malai,
I think that for "Release Strategy" questions you should opan a thread under category SAP Community Network Forums » SAP Solutions » ERP - Logistics Materials Management (MM).
Please, go to  and formulate your question.
Best regards,
Rafa

Similar Messages

  • Release Strategy not updated in PR

    Hello,
    We had a purchase requisition that was released manually via ME54n. The status of the PR is "approved" (which it should be) in  the tables in SAP. (We have tables in SAP for the front end portal to view the status of PRs). However, when we look at the PR in me53n, on the release strategy tab at item level, it still shows "release possible". And we are unable to create a PO from that PR.
    Not sure why the tables got updated correctly but not in the PR itself in me53n.
    Any help would be appreciated!
    Thank you,

    Thx for reply ...
    But here in my case , the status "FOR OVERALL RELEASE" is only being appeared for few PRs, for all other PRs either the status is "IN Release" or "Release Completed".
    Although all PRs are subjected to OVERALL Release.
    I couldn't identify the reason why only few PRs have "FOR OVERALL RELEASE".Also like to share all such PRs has already been approved by approvers but instead of "Release complete" , system is showing me status "FOR OVERALL Release"
    Appreciate if you could let me know the reason for the same.\
    regards
    Shrey

  • FM Budget Update when reducing Purchase Orders versus Release Strategy

    Hi,
    We noticed that whenever we reduce the amount of a Purchase Order, the budget is immediately returned to the budget independently of its release status. The budget should only be returned once the changes have been accepted (i.e. at the end of the release strategy).
    How can this be achieved? Do I need to make changes to the customisation or are there Badi's and/or user-exits that can be used to change the behaviour?
    Many thanks in advance.
    Regards,
    Guy

    Hello Guy,
    The budget keeps beeing consumed even though the purchase requisition has been rejected.
    The commitment item will only be reduced if you set the deletion indicator.
    This means that the budget is not returned just by rejecting the purchase requisition.
    Regarding the point that the budget was consumed even if the po was not released, I kindly ask you to check the following information:
    According to note 597854, the SAP internal BAdI 'ME_COMMTMNT_PO_RELEV' is defined in a manner allowing you to decide whether the order updates the commitments of the purchase order or not, corresponding to the header data of the purchase order.
    The following exceptions are valid in this case:
    o  Purchase orders that already have a purchase order history or
    o  Purchase orders, that were actively saved (not held) and already
       released, or are not subject to release,
    I suggest you to check the BAdIs 'ME_COMMTMNT_PO_RELEV' and 'ME_COMMTMNT_PO_REL_C' and their documentation.
    Also, please review attached note 942582 - BAdI ME_COMMTMNT_PO_REL_C
    I hope this information will help you to solve this incidence.
    Best Regards,
    Vanessa Barth.

  • Issue with retriggering Release Strategy

    Hi all,
    We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
    As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
    16. Question :
    Why is there no release strategy determination when a program changes in
    background a purchasing document which corresponds to the classification of
    a release strategy ?
    Answer :
    This is the system design that a release strategy determination can only be
    triggered through a user action and not by changes made in background
    process.
    If you create a document (e.g. PO, Contract, etc), the determination of the
    release strategy takes place only in case of a user event like checking or
    saving the document.
    Kindly suggest any best practise to retrigger release strategy  for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
    Regards,
    Anand Sampath

    Hi Arnand,
    After investigation by searching customer messages database ,I found              
    other customer has  similar problem as the release strategy has changed           
    after creation of the SES please review the  explanation from developer           
    :(whose release code is 03 )                                                                               
    When you try to revoke the acceptance of the service entry sheets                 
    in ML81N or ML81, the 'Enter release code' pop  up window appears, but            
    entering the code that is determined via the menu path Goto -> Entry              
    Sheet -> Release Strategy (which is the 03), the SES remains the same.            
    Nothing changes. The status does not vary and no error or warning                 
    message is issued.                                                                               
    Checking the customizing for the release strategy, the release code               
    03 should have never been assigned to the SES 800024272 as the values             
    for the relevant characteristics were not included under that code.               
    I do not know how it was managed to accept the SES.                                                                               
    Now, when you try to revoke it, it seems that no release                          
    strategy can be determined, not even including the values RCARESANO               
    and 012 between the valid values for the characteristics of the release           
    code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS                        
    (CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).                                                                               
    The only Possibility is to change now the SES so that the release                 
    strategy can be re-determined by the system.This is the Only possible             
    way that the system can  redetermine the Release Strategy , but it will           
    not be possible to do so as the SES is already accepted with the Old              
    strategy and it does not admit any further changes.                               
    To be able to change it you would need to revoke the SES first,                   
    but this Will also not be possible as the Release Strategy was changed            
    and the system still applies the old rules for determining the Release.           
    Solution to our Problem                                                                               
    The Only way to revoke the SES is to Restore back the Old Strategy that           
    was prior to 03 in the customizing.So now what will happen is that by             
    applying the Old Rules the System will be able to revoke the SES that#s           
    using the Old one. Once the necessary SES are revoked then go back to             
    customizing and apply the new strategy as it was did now, and                     
    Change the SES and save , the new value of the Release Strategy will get          
    updated in the table ESSR and the field frgsx will now have 03.                                                                               
    Problems associated if the Release strategy is changed                                                                               
    Actually the release strategy is not supposed to be changed when there     
    are some documents in the System that uses it and even if you change the   
    Strategy the Old records will not get AUTOMATICALLY UPDATED by the        
    system.The Release Strategy routine has to run again to update the         
    values. This is Possible by changing the document SES ,                    
    This change will happen only if the SES is not accepted and if its         
    accepted then you need to revoke and to revoke you need to restore the     
    old strategy , revoke and then change the SES , and have to go back to     
    customizing and Start using the New strategy from now on by doing so the   
    Routine will update the old record with the new strategy.                 
    b) You may want to use CEKKO-BADAT(Requisition Date) or any other
    structure in CEBAN or CEKKO and create a new release strategy    
    to differentiate the old release strategy.
    Hope this helps,
    Kind Regards,
    Matthew

  • Release strategy problem

    I am working on configuration of PO release strategy.
    I have two plants in one PO. I included both as values in characteristics and then selected in OMGS (classification) but release strategy is not working when I created purchase order with both plants but works with single plant.
    Does anybody know why ?

    Hi,
    Release strategy for PO with  line item charcterstics like Plant, item category, material group etc., gets updated into the structure CEKKO as blank if two different values found in a document.  For this type you need to create a assign a value as blank for the Plant.
    Ex: Release strategy S1 for plant 1000 with Charctertic value 1000
          Release strategy S2 for plant 1100 with charcterstic value 1100
          Release strategy S3 for both plants 1000, 1100 with charcterstic value " BLANK"
    Regards,
    Ramakrishna

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    MM06E003 Number range and document number
    MM06E004 Control import data screens in purchase order
    MM06E005 Customer fields in purchasing document
    MM06E007 Change document for requisitions upon conversion into PO
    MM06E008 Monitoring of contr. target value in case of release orders
    MM06E009 Relevant texts for "Texts exist" indicator
    MM06E010 Field selection for vendor address
    MM06E011 Activate PReq Block
    MMAL0001 ALE source list distribution: Outbound processing
    MMAL0002 ALE source list distribution: Inbound processing
    MMAL0003 ALE purcasing info record distribution: Outbound processing
    MMAL0004 ALE purchasing info record distribution: Inbound processing
    MMDA0001 Default delivery addresses
    MMFAB001 User exit for generation of release order
    MRFLB001 Control Items for Contract Release Order
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
    MEETA001 Define schedule line type (backlog, immed. req., preview)
    ME590001 Grouping of requsitions for PO split in ME59
    M06E0005 Role determination for release of purchasing documents
    M06E0004 Changes to communication structure for release purch. doc.
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06B0004 Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED Purchasing Document Posted
    SMOD_MRFLB001 Control Items for Contract Release Order
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_REQ_POSTED Purchase Requisition Posted
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_BSART_DET Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN Commitment for return item
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CHECK_OA Check BAdI for Contracts
    Reward points if useful
    Rgds,
    Naren

  • Release Strategy for contracts.

    Hi gurus,
    Good day,.
    Please help on this.
    We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
    Example.
    Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
    Thank you.

    Dear Acel,
    The example you given was working just fine and correct.
    a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    -> The release strategy will only be reset if the total net value for the contract was higher the previous
    value but not lower.
    As your example, quantity was updated to 1200, then it will reset when changing from 1000
    to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
    release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
    In system, it always assume if you had approved for the total value of the higher 1 before, then
    it should be fine for the lower total net value for your management and therefore not need to re-approve
    again for redundancy job. This was very logic in common business scenario in many companies.
    However, like in your example , if you had define a different release strategy for a value that met the
    the 1100 quantity, it will redermine the different release strategy. For example:
    USD 1 for every quantity = 1
    Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
    USD 1200 for quantity = 1200.
    Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
    Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
    Release strategy C for 1200 , characteristics from USD 1200 onwards
    Then if you change the quantity from 1200 to 1100, it will redetermine the release
    strategy B which means from Release strategy C to Release strategy B. If you
    only had Release strategy C that had a characteristics from 1000-1200, then
    it will keep the Release strategy C as released and it won't be reset unless
    if you had change it and the condition of the total net value was higher than any value
    before.
    Hope this will explain the logic.
    Ian Wong

  • Release Strategy Get cancelled - Reg

    Hai,
    We are in SAP R/3 -ECC 6.O
    Release stratgey has been set for the Purchase order  and its works well for so many years.
    The issue is , Some of the P.O alone , when the Header Terms & condition changed , Like adding one text line, or Some space or some dot, comma, The Release Strategy gets Re - Triggered ( Plz mind that , i have not changed any P.O Qty  / Value/ Organisation entities/ Material Group/ Material/Tax code)
    Kindly update , The reason - Why Release strategy gets re triggred for the , already Released P.O.
    Regards,
    PS

    Release strategy gets retriggered only in case you have changed the amount or qty thereby increasing the amount of the PO
    but as you say that you have not changed any thing which will impact the amount of the PO but the RS still gets re-triggered then we are left with only one option that some user exit has been active for this or some BADI please take help of abaper to find out the exit for this

  • Release strategy config

    Hello All,
    Does all the release strategy config for Scheduling Agreements automatically gets updated in POs also?
    e.g. we have a scenario whereas the once released SAs should not come into release procedure at all. (I know this speaks somewhat uncommon, but this is how the requirement is). For this I have made the following config:
    MM>Purchasing>SA>Release procedure for scheduling agreements>Define Release procedure for scheduling agreements>Release Indicator> 1. B         6                           blocked
                                                        2. C         6          100%       changeable
                                                        3. R         2                           released
    It is serving the purpose for SAs, but the same is also spilled over to PO config, which we donot want
    Is there any ay which we can check it getting effected for POs?
    Thanks.

    H
    Hi please create some characteristics  which you may be using exclusively for PO alone. These characteristics should not be used in S.A. I guess if you are using SA as your major transaction for material movement then most probably you will be using PO for cost center and some other emergency purchase in that case It should not be a problem for you.  This strategy if Im not wrong spills over to RFQ/CONTRACT/SA/PO, we need to take call based upon  the utilisation factor.
    Regards

  • Release strategy(urgent)

    hi,
       i have doubt regarding PO creation.
      Purchase Order has to be approved after modidfication, but,
          release strategy is not getting updated when i am modifying my PO......so i can't approve it..........
    and i am chaning quantity,delivery date, price and condition type, actually i want to know wht is the problem......... and why this is happening......
    and "on wht factors will the release startegy depend ?????????"

    Hi,
    Please can you clarify the following.
    You are saying that it should be approved ONLY after modifying it.
    But was it caught by the release strategy BEFORE it was modified?
    Or are you saying that when a released PO is modified you want the strategy to be reapplied?
    Steve B

  • Purchase Requisition Release Strategy with classification

    Hi there,
    Please help,
    I have the release strategy and workflow working. (Overall Release)
    Problem is that Org Structure is not updated so workflow has been configure going to (US) user. As i am using workflow option 1 which is resolved via Group, Code & Plant, I have to have a code for every region and manager to resolve the workflow. I am not using plant as business requirement is overall release.
    Scenario is that there are 8 regions with 1 senior region manager and 1 executive.
    The region managers can each release up to 20k. Senior region manager must release from 20k - 50k. Executive must release from 50k -250k.
    Release Codes:
    Regions = L1 - L8
    Senior Region Manager = SR
    Executive = X1
    Characteristics are:
    DocType = NB
    AccAsingment = K (Cost Centre requisitions)
    Purchasing Group = (Each region has own group)
    TotValue = 0k -20k, 20k - 50k, 50k - 250k.
    Now the release strategies.
    Even though it is the same senior manager and executive why do i have to create a new strategy for every region's escalation above 20k taking into account that the business requirement is that the correct region manager has to release before the senior manager can release? It just seems so pedantic when i would rather just add the correct Purchasing Group everytime.
    This is only one leg of the Org Structure there are over 40 depts, and managers that will create and release. Do i really need a strategy for every single scenario?
    Thanks for taking the time to read.

    Hello,
    Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
    Cheers !

  • Purchase Requisition Release strategy for MRP based Requisition

    Hello Gurus
    We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
    Thanks
    Nick

    Hi,
    If you want include the MRP related PR in Release strategy.
    You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
    So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
    there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
    But it will  not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
    I think first one is best suited.
    rgds
    Chidanand

  • Release strategy in sales order is required before MRP run

    Hi Experts,
    My requirement is Release strategy in sales order is required before MRP run. My client is doing the following process:
    1) Creation of Sale order (MTO).  Ex: User creates 10 sale orders per day.
    2) MD04- Stock Requirement List. All 10 Sale orders should be displayed. So no problem here.
    3) MD50-Make to order-Planning . Here when user gives the sale order number and sale order item and press enter, then only the released sale orders should be allowed and the rest sale orders it should throw a error message and it should not allow to process further.
    How this situation can be addressed in SAP.
    Kindly post some hints and comments.
    Regards,
    Kiran.

    Hi Kiran,
    Define and Assign status profile BS02 at sales order detail (line item) lets say with create and release status
    SD>Sales>Sales documents>Define and assign status profile
    Have create status as default while creating SO with item
    And do a user exit change for MD50 with ABAP consultant help and release it when user keys in SO and item.
    For other line item I believe it will give an error
    Pls try and update if it solves your requirment
    Regards,
    Siva

  • PO release strategy for changes in price ($ and %)

    Hello,
    I have searched this forum and others to find an answer to my question, but as I was unsuccessful, I decided to post my question here.
    I have a requirement for a PO release strategy that involves triggering the release strategy only if the total value of the PO has increased over a certain dollar amount or %.  I will need to calculate the difference in the total value between the original PO and the changed PO. 
    Example:
    Original PO total net value is $1000
    PO after a price change - total net value is $1500
    Total net value has increased by $500 or 50%.
    Tolerance for price change is $200 or $20, so tolerance has been exceeded.
    I know I will be using the total net order value (CEKKO-GNETW).  I will have my tolerances in a custom table, and I will need to take the difference in the total net value from the changed PO and the original PO and check against my custom tolerance table.  I also know that I will use a user defined field (CEKKO-USRC1) to indicate if the tolerance has been exceeded or not.  I know that I will put this tolerance check code in the M06E0004 enhancement for changes to communication structure for release of PO.
    What I don't know is where will I find the previous total net order value once the PO has been changed?  Is the only place that information is stored in the change logs?  If so, what is the change log table name?  Or is there a different table that would contain this information?
    Thanks in advance for any help you can provide.
    Sincerely,
    Angela

    Update:
    I utilized function module EXIT_SAPLEBND_002 as a solution to this.  I got the old PO value from the database table EKPO, and I got the new/changed value from the I_CEKKO structure which is accessible from this FM.
    I check to see if my tolerance has been exceeded. If it has, I pass a 'Y' as a tolerance flag via CEKKO-USRC1.
    I originally thought about using the change document tables, but I discounted this when I discovered that those tables weren't updated at the time that the function module EXIT_SAPLEBND_002 was being hit.

  • Email functionality for PO Release Strategy:

    Email functionality for PO Release Strategy:
    >When PO is blocked an email must be sent out to the first approver.
    >If there is a second approver there should be sent out an e-mail after the first level is approved and soon.
    >When a PO is released by last approver an e-mail must be sent to the creator of the PO
    I need develop this demand without workflow.     
    I found an Exit 'EXIT_SAPMM06E_013' which is triggering when 'ME21N' is executed.
    But i'm unable to update the table EKKO before my code is executed.
    Here i need Rel. gr(FRGGR),
                Rel Str.(FRGSX),
                Rel Indicator(FRGKE),
                subject to release(FRGRL) AND
                Rel Status(FRGZU) from table EKKO to check whether the PO is Blocked or Released.
    Based on the values got from the table EKKO, i need pick email ids from ZTable which stores Email Ids.
    I'm able to get the PO no which is currently genereated and i need to pass this PO no. to table EKKO to get the above fields.
    But Table EKKO is updating in the database after the execution of my code.
    What do i need to do to get table EKKO updated in the database before my code is executed.

    Email functionality for PO Release Strategy:
    >When PO is blocked an email must be sent out to the first approver.
    >If there is a second approver there should be sent out an e-mail after the first level is approved and soon.
    >When a PO is released by last approver an e-mail must be sent to the creator of the PO
    I need develop this demand without workflow.     
    I found an Exit 'EXIT_SAPMM06E_013' which is triggering when 'ME21N' is executed.
    But i'm unable to update the table EKKO before my code is executed.
    Here i need Rel. gr(FRGGR),
                Rel Str.(FRGSX),
                Rel Indicator(FRGKE),
                subject to release(FRGRL) AND
                Rel Status(FRGZU) from table EKKO to check whether the PO is Blocked or Released.
    Based on the values got from the table EKKO, i need pick email ids from ZTable which stores Email Ids.
    I'm able to get the PO no which is currently genereated and i need to pass this PO no. to table EKKO to get the above fields.
    But Table EKKO is updating in the database after the execution of my code.
    What do i need to do to get table EKKO updated in the database before my code is executed.

Maybe you are looking for