Re-Activate Release Procedure anytime when perform changes in PO

Hello,
I need to know how can I reactivate Release Procedure in PO, anytime the PO was changed in Header or Items, doesn't matter what type of change is.
Let say if I will fix by user exit, 
What fields told me there is a change in PO?  
What fields I need to modify to reactivate the Release Strategy for PO?
I appreciate any help.
Hector

hi,
PO release strategy will get set again if and if u have increase the old net value of po,
but in this scenario u suggest ur client about the version management, PO version will get updated if u make any change in document nad new version will be created.
i think clinet is more concern that any change in PO document must be noticed
so i think version management is good option
regards,
pankaj

Similar Messages

  • Release procedure for PR quantity change

    Hi...
    I have set a release procedure for PR. when i try to change the PR system does not allow me to change the QUANTITY.
    where to i set the changeblity indicator so that for a specified percentage system will retain the same release strategy.

    Spro>MM>Pur>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification>Release indicator
    Here double click the Indicator and maintain the values in the fields
    Changeabil.
    Value Change
    The field Changeabil have options of
        Changeable, new release in case of new strategy
    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
    and in the field Value Change
    Pls maintain the Value in %

  • PR release procedure problem

    We are using SAP 4.7 EE Version.
    Regarding PR release procedure, I have created PR release procedure by using characteristics with Plant, Total value of the item, document type, creation indicator and account assignment category.
    Created class PR_RELEASE with above-mentioned characteristics. The same is used in PR release procedure.
    When I am creating PR, the release procedure not picking up for standard procurement (stock material) account assignment category.
    We have identified the problem with account assignment category u2018 u2018 (Standard) while creating PR. For other account assignment categories (K, U, X, A), it is working fine.
    Recommend any SAP note numbers if you have or known.
    Points will be rewarded.
    Thanks,
    SK
    Edited by: s k on Jun 9, 2008 2:11 PM
    Edited by: s k on Jun 9, 2008 2:12 PM

    Hi
    Blank Account assignment does not work, as you cannot create a chracteristic Value as Blank.
    You need to create a new release strategy without the account assignment category chracter.
    Or remove the account assignment Chracterisitc from the release strategy
    Thanks & Regards
    Kishore

  • QuickTime 7 error: changes duration when performing Add and Scale

    Sometimes, when using "Edit - Add to Selection & Scale" to place an image over a portion of a movie, QuickTime Player 7 will incorrectly change the duration of the movie, sometimes increasing the time by HOURS!
    This may be an old problem, but I couldn't find any mention of it in the past year on the forum.
    To make it easy to reproduce, I created the following AppleScript. Usually I can only get 5 to 10 iterations before failure.
    (* Demonstrate QuickTime bug
    This script demonstrates an error that QuickTime Player 7 commits when adding an image to a movie.
    (This error also occurs when performing this operation manually, but it's faster to use AppleScript to demonstrate it.)
    R. Lougheed, December 2010
    set maxTestCount to 90 -- QuickTime has a limit of 99 tracks
    set sampleMovie to (choose file with prompt "Select a movie" default location (path to movies folder) without invisibles)
    tell application "QuickTime Player 7"
    activate
    close every document saving ask
    open sampleMovie
    set movieRef to (a reference to document 1)
    -- get a frame to paste in
    tell movieRef
    set movieDuration to duration
    tell me to set midTime to round (movieDuration / 2)
    set current time to midTime
    copy
    end tell
    end tell
    set inTime to round (movieDuration / 3)
    set outTime to 2 * inTime
    set successCount to 0
    set newMovieDuration to movieDuration
    repeat until ((newMovieDuration ≠ movieDuration) or (successCount > maxTestCount))
    with timeout of (1 * hours) seconds -- default timeout is 2 minutes
    tell application "QuickTime Player 7"
    activate
    tell movieRef
    select at inTime to outTime
    add with scaled -- this should NOT change the duration of the movie
    set newMovieDuration to duration
    if newMovieDuration = movieDuration then set successCount to successCount + 1
    end tell
    end tell
    end timeout
    end repeat
    activate
    if newMovieDuration = movieDuration then
    display dialog ("QuickTime Player successfully ran " & successCount & " Add-with-scale operations.") buttons {"Great!"} default button 1
    else
    display dialog ("QuickTime Player erroneously changed the movie duration after " & successCount & " successful operations.") buttons {"Bummer"} default button 1
    end if

    Thank you very much Hiroto !! But I've still some issue that I can't resolve by my self...
    I don't understand how to take this script (who works very well) and to use it in a different file. Actually, I wanna ask this script by 6 different other applescript file with a different movie (one in English, one in French, one in German, one in Dutch, one in Spanish and one in Italian). So I try an applescript like this :
    set FR to LancerFilm()
    tell FR
    quitQT()
    set x to "/Desktop/Robin.des.bois.2010.DVDrip.VF.XVid.avi"
    setFilm(x)
    startFilm()
    end tell
    I tried this code at the end of the file who contains the main script and in an other file. For the first one, I receive an error message who says me : +Can't find the file /Desktop/Robin.des.bois.2010.DVDrip.VF.XVid.avi+. And for the second one (wich is the solution that I wanna have for the final script), the system says me : +<<scrip>> doesn't understand the message LancerFilm+.
    If somebody can help me it will be awesome.
    I have an other question. At the end of the movie what must I do to launch another movie, automatically (so in the same script) in loop ?
    PS: Sorry for my pour English

  • Release procedure CHANGE

    hi sap guru's
    i have PR WITHout classification release procedure,
    i am created pr (service)against project, and released it
    againn my client want to add one activity in pr, and they want to again release it (re-release)that pr
    i am allready cansale release on that pr, when ME52N THEY NOT TO ALLOW CHANGE ,ALL PR GET GREY AREA,HOW I CAN ADD ONE ACTIVITY
    how i can do this
    regard'd

    Hi
    PR Release Procedure : http://www.sap123.com/showthread.php?t=59
    Regards
    Ram

  • Release of po when two plants with two difrent procedures

    Hi,
    i am having one po with two line items .one line item with one plant and other with an other plant.two plant have difrent releasing procedure.what r the customisations required to pick the system related releasing procedure when it pick item one releasing procedure for plant1 and item 2 releasing procedure 2 automatically.
    Thanks,
    Sydanna

    If  you are talking about the PO release process, then it is not possible ..
    The PO release Strategy will be applicable to entire PO, Not for Line Item wise..
    As the Plant will be at Item Level, If you set two release strategies for two plants,
    then you will not get release strategy for PO,
    If you delete the First Line Item then the Release Strategy for Second Line Item will trigger..
    Similarly, If you delete the Second Line Item then the Release Strategy for First  Line Item will trigger..
    Try to Choose Header Level fields for PO Release process..
    If the release process is for PR, Then check this Link
    http://www.sap123.com/showthread.php?s=525f3288cbee4cb09d1d97b365f8c532&t=59

  • Can the release is reset in PO when the change is not about value?

    Dear gurus,
    I have one requirement that when PO is released, the buyer would still be able to change it. Any changes that he made (for example the material PO text) then it should reset the release strategy.
    In the config i already put the changeability to 6, and then put 0 in value change, but when I change the PO the status is not reset to blocked.
    Please help.
    Best regards,
    John.

    Please see (the second part of) my comment in
    Re: release strategy is not reset in PO?
    Reproduced here for your ease:
    You can use the release user exit. If the PO is in change mode and Save option is selected, then increase the value in the user exit (This does not increase the PO value actually, just fools the release strategy into thinking that the value has increased).
    Lakshman

  • Change of authorisation for release procedure

    dear gurus,
    in release procedure the final release person (x) left away.
    and new person (y) came.
    so here i need to change the name of (x) with (y).
    I need the procedure same.only name to be updated and authorisation.
    Plz suggest.
    Thanks & Regards
    Bhanu

    Hi Mr.jurgen
    here in my company names are defined,not with their designation.
    Their need is to replace Y name instead of X name in Release strategy.
    (what ever x having authority releases need to e assigned to y including change in name)
    Thanks & Regards
    Bhanu

  • Is it anticipated that itunes (not itunes radio) will go up to rev. 12 when iOS 7 is released?   Are there any changes anticipated?

    Is it anticipated that itunes (not itunes radio) will go up to rev. 12 when iOS 7 is released?   Are there any changes anticipated?

    We don't know. Nothing has been released.

  • Release Procedure in Indent/Purchase Order

    I want to customise release strategy in indent and Purchase order in SAP. Kindly provide me steps to configure this. will apperitiate your efforts.
    Manjit

    Hi Manjit,
    Release Procedure for Purchase Orders
    In this section, you set up a release procedure for purchase orders (POs).
    Requirements
    If you want to use workflow to release POs, you must make the standard and basic settings for workflow (Basis -> Business Management -> SAP Business Workflow).
    How do you set üp a release procedure for POs?
    To set up the release procedure, you must make a series of settings in Customizing. This section provides you with an overview of the necessary activities.
    You must perform the following steps:
    1. Create characteristics and classes
    For more on this topic, see Edit Characteristics and Edit Classes.
    Note
    If you wish to link your release procedure to workflow, you must perform steps 2 and 3 . You make these settings in Customizing for Business Workflow (Basis -> Business Management).
    Otherwise, continue with step 4.
    Define organizational plan
    For more on this topic, see Edit Organizational Plan.
    Assign standard tasks and activate event-receiver linkage.
    For more on this topic, see Perform Task- Specific Customizing.
    1. Set up release procedure for RFQs
    a) Create release group
    b) Create release code
    c) Create release indicator
    d) Create release strategy
    Note
    You need only carry out the following step if you wish to link your release procedure to workflow.
    e) Assign release code to a user
    For more on this topic, see Define Release Procedure for POs.
    2. Check release strategies
    For more on this topic, see Check Release Strategies.
    Further notes
    For more information, refer to
    · Implementation of a Release Procedure for Purchasing Documents
    · Release of Purchasing Documents (SAP Library -> Basis -> Business Management (BC-BMT) -> SAP Business Workflow (BC-BMT-WFM) -> Reference documentation -> BC Workflow Scenarios in the Applications -> MM Materials Management: Workflow Scenarios)
    Edit Characteristic (CT04)
    In this step, you create characteristics for a release procedure for purchase orders (POs).
    Classification characteristics are the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchasing document (e.g. purchase order or RFQ).
    Example
    Release condition for release strategy EA:
    Characteristic Characteristic value
    Total net value of PO Above $10,000
    If the total value of a purchase order exceeds $10,000, release strategy EA is assigned to this PO.
    Requirements
    In communication structure CEKKO you will find all the fields that can be used as characteristics for a release condition (e.g. BSART for the order type and GNETW for the total order value).
    Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEKKO in the field Database table , and choose "Display".
    Note
    If you wish to define a separate release strategy for the various document categories (PO, RFQ, etc.), you must create a characteristic for each relevant document category.
    Activities
    1. Create a characteristic for each field from communication structure CEKKO that is to be a criterion for your release strategy. You have a free choice of names for the characteristic.
    2. Enter the table name and the field name on the tab page Additional data (for example, table CEKKO for field GNETW).
    Note
    o Do not select any of the indicators in the area Procedure for value assignment on the tab page Additional data. Only if none of these indicators is marked can you assign a value or value interval to the characteristic when defining your release strategy.
    o When you create a characteristic for a currency-dependent field (e.g. GNETW), a box appears in which you must enter the currency for the relevant value. The system then converts the currency of the purchasing document into this currency.
    3. Check the data for the chosen field on the tab page Basic data.
    If you want to enter several values or a value interval for a characteristic, set the Multiple values indicator in the area Value assignment.
    Note
    Value intervals can only be specified for numerical values (e.g. an interval of $10,000 to $15,000 for the value of the purchase order.
    4. Check the texts for the field on the tab page Descriptions.
    5. You can maintain default values for a characteristic on the tab page Values.
    If you maintain values here, these values will be displayed as input help under Create Procedure with Classification -> Release Strategy -> Classification . If you wish to use not only the input help but also other values, you must select the Additional values indicator.
    Note
    You can also maintain ' ' as a default value. For example, for account assignment: ' ' for stock material, 'k' for cost center, and 'a' for asset.
    6. If you want to restrict the use of a characteristic to particular class types, specify the relevant class types on the tab page Restrictions. For example, class type 032 for the release strategy.
    Further notes
    Further information on characteristics is available in this Customizing activity via Help -> Application help.
    Customer exits
    Customer exit M06E0004 enables you to change the communication structure for determining the release strategy for purchasing documents.
    Edit Class( CL02 )
    In this step, you create classes for a release procedure for purchase orders (POs).
    You use a class to group together characteristics that are to constitute a release condition for a release strategy. In the step "Define Release Procedure for Purchase Orders " you assign this class to the release strategy.
    Activities
    1. Create a class with the class type 032. You have a free choice of names for the new class (e.g. REL_RFQ for the release of RFQs).
    2. Assign a name for the new class on the tab page Basic data.
    3. You can view an error message if different characteristics with identical values have been assigned to a class. To be able to do so, select the Check with error message indicator in the Same classification area.
    4. If appropriate, select terms to be used as search criteria in searches for your class on the Keywords tab page.
    5. Assign your characteristics to the class via the tab page Characteristics.
    Further notes
    Further information on classes is available in this Customizing activity under Help -> Application help.
    Define Release Procedure for Purchase Orders
    In this step, you set up the release procedure for purchase orders (POs) and can link it to workflow. (Note that in this context "releasing" means "approving", or giving the "green light" to a document.)
    Requirements
    · In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
    · You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure ( Authorization Management -> Create Authorization Profiles and Assign to Users).Activities
    Here you define the following:
    ·     Release group
    ·     Release codes
    ·     Release indicator
    ·     Release strategy
    ·     Workflow
    Release group
    Create a release group for your release procedure and assign it to a class. In the process, you assign release conditions to the release procedure.
    Release codes
    Here you create the release codes you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field
    The Workflow indicator is also used to control role resolution:
    ·     "1 - Role Resolution with Group, Code and Plant (T16FW)"
    Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
    ·     "9 - Role Resolution via User Exit"
    Here you use the customer exit M06E0005 to define a role resolution of your own.
    Release indicators
    A release indicator shows the release status of a PO.
    Via the following settings, 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.
    Attention:
    The following release indicators are necessary for every release procedure:
    o     Release indicator for initial status
    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.
    The Released indicator must not be selected for this indicator.
    o     Release indicator for released status
    This indicator is assigned to the PO when it is released.
    The Released indicator must be selected for this indicator.
    Release strategies
    Create a release strategy for your release group and assign your release codes accordingly.
    ·     Release prerequisites
    With the release prerequisites , you specify the order in which the individual release points (individuals or departments) represented by the release codes may release the document.
    Example
    The following table shows release prerequisites for a strategy with four release codes.
    Code/Release prerequisite
              01     02     03     04
         01     -               
         02          -          
         03               -     
         04                    -
    In this release strategy, the codes 01, 02, 03, and 04 must successively release the purchase order.
    Read the table from left to right. For instance, the third line for release code 03: For code 03, release via code 01 and code 02 is a prerequisite. That is to say, the PO must be released via codes 01 and 02 before it can be released via code 03.
    ·     Release statuses
    Here you specify the status a PO has after certain release points have effected release.
    Specify which release indicator/status a PO is to have after having been released via a certain release code.
    ·     Classification
    In classification, you maintain the values assigned to the characteristics. Via the characteristics and their values, you specify the POs to which your release strategy is assigned.
    Maintain values (individual values or intervals) for your characteristics.
    Example
    Two characteristics and their values have been maintained in classification for release strategy 'EA':
    - Document type - 'NB - standard purchase order'
    - Total value - above $10,000
    All POs with the document type 'NB' and a total value in excess of $10 ,000 are thus subject to a release procedure with the release strategy 'EA'.
    ·     Release simulation
    The release simulation function enables you to check which status a PO will achieve with your release strategy if release is effected by a certain release point.
    Choose "Simulate release" and release the document with the desired release code by double-clicking. The system shows you which status the PO now has as a result of this release.
    Workflow
    Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.
    You can assign a processor ID either directly or indirectly:
    o     Direct processor assignment:
    Enter a user name.
    o     Indirect processor assignment:
    Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.
    Customer exit
    Customer exit M06E0005 enables you to define your own role resolution which determines the person responsible for releasing purchasing documents in workflow.
    Further notes
    Further information on how to set up a release procedure linked to workflow is available via the menu options Help -> Application Help.
    Check Release Strategies
    In this step, you can check whether the basic settings for your release strategy are complete and correct.
    Checks
    The following checks are carried out for purchasing documents:
    ·     Basic checks
    The system checks whether the necessary release groups exist in the system. For example: Whether a release group has been deleted even though an associated release strategy still exists.
    ·     Checks regarding release groups and release classes
    The system checks whether the release groups and the assigned classes have been maintained correctly. For instance, whether
    o     A class has been assigned to the release groups and whether it exists in the system
    o     Characteristics - which exist in the system and are linked to the communication structure - have been assigned to the class
    o     A customer exit must be maintained for a characteristic
    ·     Checks regarding release codes
    The system checks whether the release codes have been maintained correctly
    ·     Checks regarding release indicators
    The system checks whether the release indicators have been maintained correctly. For example: Whether release indicators exist for the statuses "Blocked" and "Released".
    ·     Checks regarding release strategies
    The system checks whether the release strategies have been maintained correctly. For example, whether:
    o     Release codes have been assigned to the release strategy
    o     The relevant release indicators have been assigned to the initial and final statuses of a release strategy
    ·     Checks regarding link to workflow
    The system checks whether the link between your release procedure and workflow has been maintained correctly. For example, whether:
    o     A processor (member of staff responsible for processing) has been assigned to a workflow-relevant release code and is defined in the organizational plan
    o     A customer exit is necessary for the role resolution
    Result
    The result of these checks is displayed in a log. Further information is available in the Customizing activity under Help -> Application Help.
    Activities
    1. Start the check by performing the Customizing activity.
    2. Check whether any error or warning messages are displayed.
    3. If necessary, correct your Customizing settings for the release procedure.
    4. Re-run the check after making corrections.
    Rewards if Helpful
    Regards
    Sanjay L

  • PR release procedure no longer working-error MEPO 822

    I've raised a message previously regarding PR release problem. Now i've found something that need expert helps to clarify on this.
    Situation :
    One of my client(ABC) implemented release procedure for PR which is not assign to value limit. It is by document type. They had 2 document types; NB and RNB.
      NB = NOT subject to release
      RNB = SUBJECT to release.
    So when they :
    create a PR with document type RNB - it will goes for approval.
    create a PR with document type NB - it will not go to approval.
    It was working fine until after they created a new document type which copied from NB, called ZTP.
      ZTP = NOT subject to release.
    They did not touch anything on PR release configuration. However, the release has no longer working. Means, when they create PR with document type RNB, it will NOT go for approval as it suppose to. I've check in configuration, all are fine.
    Findings:
    I've created a PR, and go to ME45N to release it but system prompt me an error message
    "Purchase requisition 10000066 cannot be released". I check on the message data,  the error coming from MEPO, message number 822.
    So i check in OSS and found a note which is similar to this case.
    Note 939371 - Overall release PR using ME54N gives error MEPO 822
    Link : https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=939371#Text
    But my question is,is it also applied to ME51N and without external application as per my client's case?
    Please anyone help.
    Thanks.

    Hi guys!
    Wants to share something. I had a problem to release my PR. When i want to release PR via ME54N, system give me error message "Purchase requisition 10000066 cannot be released". When i checked message data, it is coming from MEPO Messafe 822. So i asked SAP, they said this one is caused by different issue. Here's the reply from SAP.
    Here's the reply from SAP :
    Purchase requisition 10000066 cannot be released
    Message no. MEPO822
    Now click the other requisition button and let say
    choose Purchase requisition 10000068,
    Execute ME54N again:
    Purchase requisition 10000068 cannot be released
    Message no. MEPO822
    Comment/explanation:
    The log incidence seems not having problem with release
    strategy as it was ok but it was the last PR was called
    everytime ME54N was called. This same as it works in enjoy
    transaction ME21N/ME22N or ME51N/ME52N.
    For example, When using ME21n or ME22n to create or change PO,
    after saving the PO. There are 2 ways to exit the transaction,
    1, enter another T-code or use /n to exit directly.
    2, use 'F3' or the 'green tick' to exit ME21n (or ME22n)
    Then you can access ME23n to see the difference.
    For the 1st way, ME23n won't display the last PO created in ME21n
    For the 2nd way, ME23n will display the last PO just created!!!
    Please see attached consulting note 595627 that explains a new
    functionality as of release 470:
    Due to performance problem, a decision had to be taken about the way to
    use transactions. If you leave transaction ME21N/ME22N via the
    exit button (F3), the expected PO will be displayed next time you use
    these transactions. But if you quit abruptly (/nXXX) the PO number
    won't be saved for the next transaction ME2?N.
    As SAP note is the official document to explain system behavior,
    this document is provided by SAP developement to explain this system
    behavior to customers.
    In your case, you had used ME54N and this was same as you use ME53N.
    The last PO always display. You may try to view Purchase requisition
    with release strategy, for example Release group R1, Rel. strategy
    R1, then after this execute transaction ME54N again, the message
    MEPO822 will not be there anymore.
    Hope this will help you guys if you're having the same problem in future.
    Thanks,
    Crystal.

  • Service Entry Sheet Release Procedure

    Dear all,
    I want to assign a new Plant to an existing service entry release strategy. In CL20N for Class Type 032 and maintaining the Release Group and Release Strategy I want, I hit ENTER and the Class SERVICE_RELEASE is displayed, which is correct (it is a service entry release procedure).
    Selecting the item and displaying the values for the Class, I have Plant, Order Type and Cost Centre. I added a new row, include a new Plant and hit Save. I get the message "Saving changes to assignments" and then I exit the screen.
    However, to double check that the object has been assigned to the class, I check in SPRO>Materials Mgt>External Services Mgt>Define Rel. Procedure for Service Entry Sheet> Release Strategies to confirm that the object was created in the classification for service entry release procedure. BUT IS NOT THERE!
    However, if I performed the assignment in Classification in SPRO for the release strategy, and check in CL20N, IT IS THERE!!
    How come I have created in CL20N and it is not displayed in SPRO for the same release strategy? The object assignment was successful with no error msg. It is not possible that you have done it in CL20N and you have to do the same in SPRO, right? Doesn't serve the purpose..
    Pls help.
    Thank you.

    Dear Sir,
    Go to CL02 give the Class and Class type, click on change icon
    Copy the characteristic of Plant from Char. Tab
    Then Go to CT04
    give characteristic which is copied from class and click on change icon.
    enter your new plant in Values tab, Save back
    Go to CL20N, give release group and release code for which you want to maintain the new plant.
    give the plant  and save enter.
    i hope this will help you.

  • Release procedure problem

    Hi Gurus,
              I created a release procedure for PO. i created a single chs based on total amount of PO and assigned it to a single class. then configured it for 5 release codes. all the simulation is working fine.
              But when I created the PO worth of 6 laks, which is above the level of last release code >=5 laks. when i go for release in ME29N or ME28 its giving an information message saying "document is not applicable for release procedure. in ME28 i am getting "message no documents found" for my release code and release group combination.
              Where should i have gone wrong. give me some suggestions.
    Thanks & Regards,
    Poorna.

    Hi,
    Your Maximum amount of PO which is applicable for release strategy is 5 Lakhs for your last release code.
    Now if you create the PO for 6 lakhs then how the system will consider the release strategy.
    Thats why you will not find the same in ME29N or ME28 to release the PO.
    So you need to change your Characteristics value for last release code from = 5 lakhs to >= 5lakhs.
    then system will consider the release str for any value above 5 lakhs for that last release code,
    rgds
    gsc

  • The screen on my macbook has malfunction. When I change the brightness to zero and return to the first level of brightness it works briefly but then the screen starts to flicker brightness and quickly extinguished.

    The screen on my macbook has malfunction. When I change the brightness to zero and return to the first level of brightness it works briefly but then the screen starts to flicker brightness and quickly extinguished. It seems to be a bad contact, it would not be normal for a quality product that should have, he has less than two years of use. Not because of the bad use or crash. Someone with the same problem or can help me? It's really a contact problem? I've done all the procedures recommended by the online support. Thanks.

    Hey everyone in Apple world!
    I figured out how to fix the flashing yellow screen problem that I've been having on my MBP!  Yessssss!!!
    I found this super handy website with the golden answer: http://support.apple.com/kb/HT1379
    I followed the instructions on this page and here's what I did:
    Resetting NVRAM / PRAM
    Shut down your Mac.
    Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    Turn on the computer.
    Press and hold the Command-Option-P-R keys before the gray screen appears.
    Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    Release the keys.
    I went through the 6 steps above twice, just to make sure I got rid of whatever stuff was holding up my bootup process.  Since I did that, my MBP boots up just like normal.  No flashing yellow screen anymore!!   
    (Note that I arrived at this solution when I first saw this page: http://support.apple.com/kb/TS2570?viewlocale=en_US)
    Let me know if this works for you!
    Elaine

  • Effect of payment terms on release procedure

    Hi gurus,
    Will their be any impact of payment terms on release procedure of purchase order?
    As and when we change payment terms in a PO which is released earlier, the release procedure tab is getting disappeared
    I hope my question is clear
    Kindly reply soon
    regards,
    prasad

    Hi Prasad Sathya
    Be sure that Payment term in Po will not have any impact on release procedure. if u check the Table CEKKO throgh T code SE11 , there will not be any field for payment term. then how to create characteristic for the payment term.
    and it is not logic to create Release procedure based on the Payment terms
    friendly
    Manickss
    pl don't forget to reward if helpful

Maybe you are looking for