Block creation of PO if the release strategies is not applicable

HI SAP,
Can we block creation of PO if the release strategies is no applicable ?
My release strategies is on the PO header. It's only work if the PO have one Plant only. If the user put more then one plant
my release strategies will not work. how to solve this problem ?

Hi,
Check on it:-
http://www.sapfans.com/forums/viewtopic.php?f=6&t=205684&start=0&st=0&sk=t&sd=a
Re: Release Strategies in Purchase Order - possible values of caracteristics
PO Release strategy question
pherasath

Similar Messages

  • How do I turn on the notification for pop-up blocker? I accidentally clicked the option saying "do not show this notification again." I want the notification so I have the option of seeing the pop-up or not, but don't know how to turn this back on.

    How do I turn on the notification for pop-up blocker? I accidentally clicked the option saying "do not show this notification again." I want the notification so I have the option of seeing the pop-up or not, but don't know how to turn this back on.

    Type "about:config" in the location bar.
    Filter for "privacy.popups.showBrowserMessage"
    Change this to true by double clicking the preference (or right click and choose Reset)

  • The selected driver is not applicable to any supported platforms. 2012 R2 U1 for Windows 8.1 x64

    When trying to import the drivers from the Windows 8.1 x64 Dell E6330 SCCM CAB to our SCCM 2012 R2 U1 server, we receive the error "The selected driver is not applicable to any supported platforms" on a number of drivers.
    Specifying the same source directory to the test Windows 8.1 Ent x64 computer via the install driver wizard in Device manager finds and installs the missing drivers successfully (Bluetooth 4.0 Module and STMicroelectronics 3-axis Digital Accelerometer). 
    The manufacturer section of those drivers looks like this:
    bcbturms-win8x64-brcm.inf
    [Manufacturer]
    %MfgName%=Broadcom, NTamd64.6.3, NTamd64
    st_accel.inf
    [Manufacturer]
    %STM%=ST,NTAMD64
    Any idea how I can successfully import these drivers?

    Thanks for the suggestion, but the results are the same. The Grabber runs without error, but the injector errors with "Error in ConfigMgrDriverInjector.CheckIfDriverExists The SMS Provider reported an error." So I attempted to import the drivers from the
    injector's configured drivers source folder and received the exact same error I receive when attempting to import them from the Dell cab.
    Relavent part of the DirverInjector log below:
    <![LOG[Starting drivers import processs]LOG]!><time="9:50:20.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.IntegrateDrivers" context="" type="1" thread="" file=""
    <![LOG[Current folder : Bluetooth]LOG]!><time="9:50:20.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.ImportDrivers" context="" type="1" thread="" file=""
    <![LOG[Current subfolder : Dell Wireless 380 Bluetooth 4.0 Module]LOG]!><time="9:50:20.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.ImportDrivers" context="" type="1" thread="" file=""
    <![LOG[INF file found : oem14.inf]LOG]!><time="9:50:20.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.ImportDrivers" context="" type="1" thread="" file=""
    <![LOG[Driver version found : 12.0.0.7820]LOG]!><time="9:50:20.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.ImportDrivers" context="" type="1" thread="" file=""
    <![LOG[Checking driver existence]LOG]!><time="9:50:20.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.ImportDrivers" context="" type="1" thread="" file=""
    <![LOG[Error in ConfigMgrDriverInjector.CheckIfDriverExists The SMS Provider reported an error.]LOG]!><time="9:50:20.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.CheckIfDriverExists" context="" type="3" thread="" file=""
    <![LOG[Error in ConfigMgrDriverInjector.CheckIfDriverExists The SMS Provider reported an error.]LOG]!><time="9:50:21.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.CheckIfDriverExists" context="" type="3" thread="" file=""
    <![LOG[Checking driver existence]LOG]!><time="9:50:21.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.ImportDrivers" context="" type="1" thread="" file=""
    <![LOG[Error in ConfigMgrDriverInjector.CheckIfDriverExists The SMS Provider reported an error.]LOG]!><time="9:50:21.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.CheckIfDriverExists" context="" type="3" thread="" file=""
    <![LOG[Driver not foud, a problem occurred during the import process]LOG]!><time="9:50:21.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.ImportDrivers" context="" type="2" thread="" file=""
    <![LOG[End of driver is import process]LOG]!><time="9:50:21.000+000" date="7-16-2014" component="ConfigMgrDriverInjector.ImportDrivers" context="" type="1" thread="" file=""

  • Regarding the Release Strategies not getting picked up for PR

    Hi Gurus,
    1 ) I have configured a new Release strategy with Plant,Total Value,AAC and Doc.type as the Characteristics.I have assigned that to a release class and assigned values to the characteristics.
    I have configured 6 release codes and 6 different Value Intervals for 6 release strategies and assigned it accordingly. But whenever i am trying to release the PR, it is picking the first strategy only. its not picking the other strategies even it is of differnet values. Please advice what needs to be done on this.
    with Regards,
    Saakithyan

    1st of all check whether you defined release strategy for Item level or header level.
    If you defined item level check the individual item has all the 6 characteristics you defined.If any characteristic is missing then it will not pick. Provided you defined all the characteristics for classification view or CL20N.
    Thanks & Regards
    Sudhansu

  • Release stretegy is not applicable for changability 4

    Dear All,
    For POs We are using release stretegy with changebility 4 such that any change in price in existing released PO will cause the new release strategy applicable,
    In our case it is working fine also but only if change in net price, we sometime chang price affecting the effective price but not the net price,
    so can you please guide me for how we can make the new release stretegy get activated even for change in effective price or changes in price which are after net price calculation,
    Regards,
    Sdn Brower

    Hi,
    New release will be triigerd either if there is a value change or if there is new strategy determined.
    Since change in effective price doesnt change the PO net value, Looking into the CEKKO structure
    the paramter that you could use can ve REVNO, which is nothing but PO version number.
    For this to work, activate verision for the PO and include versioning into characteristics of the release startegy.
    Pls test in your sandbox if it works.
    If there is any  other better solution, pls do share.
    Harish

  • Block Creation of Production order Unless released in Order.

    Hi Experts.
    we have a requirement where we want to block the creation of production order inless it is confirmed. Is there any User exit / or anyother indicator where i can define or configure so that the MRP run and also the Creation of the production order can be block for a sales order.
    Plz advice.
    Thanks in Advance
    Rishi

    Hi
    But Manually it does allow the user to create Production order .
    I want unless, Say the delivey block at item level is removed , User should not be allowed to create the production order for the relevant line item of the sales order.
    Any more suggestion
    Thanks
    Rishi

  • I purchased Flash Builder 4.7 Premium for Mac, but the DOWNLOAD section says "Not applicable". So how do I get my download?

    Adobe has taken my money, but I don't have the ability to download the product I purchased (Flash Builder 4.7 Premium for Mac/Win). What do I do in order to download the product I purchased?

    download the trial and enter your serial number during installation, Develop games and applications | Adobe Flash Builder 4.7 Premium

  • Re-installing lightroom via download after my hard drive crashed. I have serial number but the download option says 'not applicable'.

    Re-installed my photoshop with no problems via download from Adobe.com. Lightroom purchase will not let me download, says in download link area, "not applicable"

    Which version of Lightroom?

  • Problems with the Losing Release Strategies Approvals in PO.

    Hi Experts,
    We're using the BBP_WFL_APPROV_BADI for Purchase Orders (WS14000145) the source code of BADI works fine.
    I can define all the approvers as source code.
    I'm  making  any text modification in the PO with status Awaiting Approval. This works fine, but I have a problems when i make the modification in the PO  ( Document Approved ) with status  ordered  or Error in Process , if I make the simple modification   (explo. text modification) the release strategie is re-starting again, losing all the approvers and approvalls. We need that modification not start the release strategy again.
    The re-start should be make only for values modifications (Price, Quantity).
    There is other problem with approvals preview too, the approval's preview with the ordering of approvals dissapears. When
    I make the same modification in PO with  ordered status.
    Thanks

    Hi Masa, How are you?
    I check the table BBPD_COMP_FIELDS but i didnt understand anything...I need to make tho desactivate the re-start of release strategies..WHen I make a smple modification in the PO ( for explo text documents).
    I my process now..if I make the modification in the PO with status orderer ( any modification) the system re-start the approvals levels...I need re-start only for value modifications...Could you help me?
    Thanks,
    Gustavo Nogueira

  • Are these requisition release strategies common?

    All,
    I’m designing new requisition release strategies for indirect requisitions at a chemical industry client.  I’d like to know how often you have seen the following sorts of design before:
    Existing design: Item-based release with workflow, with three dollar levels.  At the lowest levels, two strategies for each cost center approver (the one used is based on whether the desired vendor is foreign or domestic).  Characteristics assign several cost centers to each approver.  Strategies and codes are named for users, so we change configuration whenever someone changes jobs.  The codes are linked to positions, which are attached to user IDs.  Result: about 80 release codes and 140 strategies, taking a lot of time to maintain.
    Current redesign: Overall release, using 6 strategies and 6 codes based on dollar level and foreign vs. domestic.  A user exit selects the approver for each code from a custom table that stores the user IDs for each cost center, with a custom maintenance transaction for the table.
    Now the client wants both individual approval by cost center owner and items with different cost centers on a single requisition combined with approval of the overall purchase.  I’m considering item-based approval of requisitions, with the user exit and custom table, and adding overall approval of indirect POs with the overall approvers.
    Thanks for your help!

    Hi,
    No-Requisition release strategies are not common, one need to design release strategies based on business requirement. Release strategies looks simple after designing but its design needs creating thought to it.
    In your case, you can go for designing redesigning release strategies for Overall release with using 6 strategies and 6 release codes. Considering you have configured release strategies with all release values for PO document type ,PO value and Purchasing group. Now design a custom table and go for followings:
    Client---Pur Group--Rel Code1-- Rel Code2-- Rel Code3-- Rel Code4-- Rel Code5-- Rel Code6
    The search help is required to pull in purchasing group details from T024 table and SAP user ID from Table USR01
    Concept: Create Purchasing Group (OME4) as Department & assign the Department name to Cost center (KS01).
    For more refer a discussion:
    PR release: place holder for Cost center and Material grp
    NOTE: User training required crate requisition for one department only where only one cost center involved- No requisition creation allowed for multiple cost center.
    You can also go for other concept designing of your Requisition release strategies
    Regards,
    Biju K

  • Purchase requisition : problem with check release Strategies

    Hi all,
    i created a new class, new release group, new release codes etc. I think all is ok but when i launch the transaction OMGQCK for check release Strategies the system give me an error in node 'Check re release indicators' : Define a release indicator for the status "released".
    But how can i do that, i created two release indicator : 'X' for blocked and 'V' for launched but what are the options for purchase requisition ?
    Is there a special value to give the release indicator 'released' ?
    Thanks for your help.
    Edited by: ToraTora on Mar 31, 2011 5:46 PM

    Hi,
    Goto SPRO -> Materials Management -> Purchasing -> Purchase Requisition -> Release Procedure -> Procedure with classification -> Setup Procedure with Classification
    select release indicator
    by default, you will be having the following release indicators in the system,
    1     Request for quotation
    2     RFQ/purchase order
    3     RFQ/PO no change of date
    4     RFQ/PO no changes
    A     Fixed RFQ
    B     Fixed RFQ/purchase order
    X     Blocked
    please check whether you have got these or else create and then assign them to the release strategies.

  • 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

  • Release Strategy is not picking up in the PO.

    Hi All
    I have defined a Release Strategy for the Purchase Order.
    The Characteristics are
    PO category
    Pur Org
    Total Net Order Value
    All the lights are green which i check the release strategy.
    But the Release Strategy is not picking when PO is created.
    Kindly let me know what is the mistake i have dont or i need to make any corrections.
    Thanks in advance
    Renukaprasad.

    Hi Renuka,
    im using ECC6, my PO rel strategy dont have PO catergory,
    but you can try this:
    Maintained PO characteristics:
    PO doc type
    PO Plant
    PO Pur Grp
    PO total Value
    Once your PO meet this, Rel Strategy triggres.
    When you define the Rel Strategy, there is rel indicator Approved and Block, configure based on your requirement.
    Hope this helps a little
    Regards,
    Maia

  • Release Strategies in Purchase Order - possible values of caracteristics

    Hello,
    I have the following situation at hand.
    We use in a company code a release strategy for POs. One of the caracteristics is the "plant" (CEKKO-WERKS, multiple values). Strategy is working fine.
    Now I have to implement in another company code- in the same Client - the PO release strategy but this company code has about 800 Plants asociated! moreover, the release strategies in this new company are not dependent on the "plant"!
    I can not change the caracteristics in the Release strateg because this would affect the already working strategies  and SAP does not allow to asign another Class to the PO release groups.
    Is there any way I can prevent that I have to create release strategies with each of them 800 Plants in the caracteristics "Plant" ?
    Can I use something generic in the caracteristics field of the strategy?
    Thanks for any help. It would save me a lot of time!
    Aart

    Note 493900 - FAQ: Release Strategy
    1. Question :
    Why is the release strategy not determined?
    Answer :
    Please check the following points :
    You can not use Release without classification and Release with classification.
    If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.
    If you use version management, the determination of the release strategy starts when the version is completed.
    You complete a version by setting the "version completed" indicator in the version tab.
    Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
    This is true for the other structures as well (CEKKO and CESSR). See note 52225.
    For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
    For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

  • Purchase Order Release Strategies for Changed Amount

    Hi Gurus,
    We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
    Example: Configuration is PO total amount <$5K requires only L1 approval.  PO total amount >$5K requires L1 and L2 approval.  PO was created for $8K and was release using L1 and L2 approvals.  Receipts were posted to PO in the amount of $7K.  Now the buyer has added an additional line item for $1K.  The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item).  Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
    Has anyone done this before?  Any ideas??
    Thanks,
    Gabe

    from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
    User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
    This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
    The following user fields are available:
    USRC1
    USRC2
    USRN1
    USRN2
    In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

Maybe you are looking for