Release Strategy in PO for direct materials not driven by MRP

We have a requirement to enable release strategy for purchase orders created for direct materials that are not driven from an MRP requirement for a single plant.
Request you to let me know how I can make this work.
I have an option to make it mandatory to have Preq for these PO's and can enable release strategy for Preq which are created other than MRP.
request to let me know if there are other options in PO's itself where I can find that the Purchase orders are created directly and put release strategy in it.
Thanks and Regards
Murali

Hi Murali,
Standard SAP provides PO release strategy at header level only and not at item level.
So you can create a new PO document type and allow use of only this document type for manual PO creation.
Then set-up PO release strategy for newly created document type, where one of the primary characteristic will be Order Type (Purchasing).
Hope this will fulfill your requirements.
-Ravi

Similar Messages

  • Collective Invoice Posting for Direct Materials

    Hi ,
    We have extended classic scenario with R/3 backend and we are posting Collective Invoices for multiple POs for direct materials ( order type ECDP).Invoices fail to transfer to backend.BD87 /WE02 log in R/3 indicates the following error -->Acct assgt 01 for order item 2200000070 00001 does not exist
    Message no. M8140
    Also ,if I try posting the invoices in R/3 using MIRO, there are no errors.
    Thanks,
    Gourang

    Several notes show up for M8140.
    316657, 615114, 506930 in the SRM area.
    493604, 810917 for BAPIs may also be relevant.
    334765 recommends creating a support message for further analysis.
    Kind Regards, Suresh.

  • Asking Account Assignment Category for Direct Materials

    Experts,
    ECS Scenario with PPS, ECC EHP4, SRM7.0.
    The system is giving error as 'account assignment category is missing' for 'direct materials'. We have same problem while creating SC in SRM also and for PDP als.
    Items with account assignment are working perfecly fine for both SC and PDP, for same product category.
    For PDP: System did not give any error at PR stage, but if see log in SLG1 in SRM, we see that, it did not transfer to SRM as 'account assignment category' is missing.. moreover, If we create a standard PO item, for the same material group (without reference to PR) it is pefectly working. GR, IR everything is fine in ECC... So there should not be any problem in ECC account assignment(?).
    We have not implimented any BADI. Just used the standard, as it is... Product category, location, storage location are maintained in PPOMA_BBP. Accounting system for vendor is also maintained...
    What could be other possiblities? kindly help.
    GH

    hi
    Can you create sc see  account assignment folder though ypu order as direct material in PPS scenario?
    please check BBP_PDIGP-subtype =dp and external requirement.
    SAP has designed like that for PPS scenario
    Direct materials with account assignment
    check with SAP, Learn that SRM not creates a shopping cart for direct materials for the purchase requests.
    since they are throwing explicitly error message
    'account assignment category is missing' for 'direct materials'
    Muthu

  • Error message if no release strategy is applied for PO

    Dear All,
    In some cases there is no release strategy is applied for a PO, but still system is allowing me to make GRN against this PO.
    Is there any way to encounter this
    Means if no release strategy is applied for that PO then system might not allowed to SAVE PO.
    OR
    While making GRN against this PO, System will give message Like say ...  no release strategy is applied for the PO..
    Please reply  ...URGENT
    Regards,
    Rakesh Shelar

    Dear Thanx.
    my requirement is to block further processing of PO for which release strategy is not applicable due to some wrong combinations put while crating PO.
    In this, case  system is allowing to take GRN against such POs without release strategies

  • Configure of New Release strategy in PR for ERSA Mat type

    Dear Friends,
    Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
    Regards,
    Ask

    ashokkumardash wrote:>
    > Dear Friends,
    >
    > Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
    Hi,
    Create Characteristic for Material type and Communication structure CEBAN and a create class with 023 and assign character to class and create Release group and code for MRP controller and finally assign this particulate role to the MRP controller User ID and he release the same.

  • How to set the Release Strategy without classification for PR

    Hi,
    I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
    I crated the Release Codes, however not able to find what options to choose in the following steps :-
    Release indicator
    Assign Release Indicators
    Release Points: Prerequisites
    Determination of Release Strategy
    Regards,
    Yogesh

    1. Release codes                                                            
       Create the release codes.     For  Purch. Officer, Manager and Sr. Manager                                                                               
    Like PO, MG, SM                                      
    2. Release indicators                                                       
       Define release indicators and branch to the detail screen. Here you      
       define whether fixed purchase requisitions may be changed by Materials   
       Planning, for example, and whether an RFQ or a purchase order may be     
       created from the requisition.                                            
       You can also determine the field selection here.                                                                               
    In the area "Changes after the start of the release procedure", you      
       specify whether a requisition may be changed after the release           
       procedure has begun. You specify whether the strategy has to be          
       redetermined after changes, or whether the release procedure has to      
       start all over again from the beginning.                                                                               
    This parameter bears a relation to the parameter "Value change". For     
       example, previous releases are not cancelled if the value of the         
       requisition item after the change does not exceed plus 10% of its        
       original value.                                                                               
    Attention:                                                               
       Be sure to create a release indicator (e.g. B for "blocked") that        
       serves as the starting point for subsequent indicators. Do not set the   
       indicators for release for the issue of RFQs and PO on the detail        
       screen for this indicator.                                               
       Also create a release indicator characterizing the released status.      
       Set the indicators for release for the issue of RFQs and PO on the       
       detail screen.                                                           
    You can use sytem defined indicator in this case you don’t have to do anything                                                                               
    3. Assignment of release indicators                                         
       Assign a release indicator in dependence on the status of the release.                                                                               
    Example:                                                                 
       You create a release strategy S1 consisting of two release codes 01      
       and 02. Release with 01 is a prerequisite for release with 02. If        
       release has been effected with 01, the requisition has been given the    
       "all clear" for the issue of RFQs.                                       
       You have created the release indicators B (blocked), 1 (cleared for      
       issue of RFQs) and 2 (cleared for RFQs and PO).                          
       Now enter the following as assignment:                                                                               
    Strategy   C1  C2  C3 ...                                                
       S1                          B (blocked)                                  
       S1         X                1 (RFQ)                                      
       S1         X   X            2 (RFQ/PO)                                                                               
    4. Release prerequisites                                                    
       Define which release codes are involved in a release strategy. Specify   
       whether a code is set for a release status following release, and        
       whether one release status is a prerequisite for another (+).            
       Example:                                                                 
      Strategy   Code  C1  C2  C3 ...                                  
    S1         01    X                                               
    S1         02    +   X                                                                               
    5. Determination of the release strategy                            
    Determine the conditions under which each release strategy is    
    assigned. The criteria are account assignment category, material 
    group, plant, and value of the requisition item.                                                                               
    Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
    E.G if you will not define the Material group here but it will default in req in that case this will not work that’s the reason you have to work with Classification.               
    <b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

  • Release Strategy with Workflow for PR & PO

    Hi Experts,
    I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
    So User should get the information about the releases for PR & PO.
    But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
    Points will be awarded .
    thanks & rgds
    Swamy

    Hi Swamy,
    The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
    How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
    Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
    How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
    How to configure?
    Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
    For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
    For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
    Maintain the details u already have in hand:
    For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO.  After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
    Hope this will give you an idea how the workflow works and how to configure it.
    Rgds.

  • MB1C via LSMW for Serialized Materials not loading all Items

    Dear Experts,
    I am using LSMW to load initial entry of materials with serial numbers using Tcode MB1C. The challenge i am having is that not more than three(3) of the serials get uploaded the remaining are not loaded. I have items that have varying quantities. What could be responsible for this?

    Hi,
    Insted of LSMW  make a abap program using   'BAPI_GOODSMVT_CREATE'  it is simple and works properly.
    regards,
    zafar

  • Is there any way to ask Siri for directions and not have navigation automatically start?

    Sometimes I just want to know how far and how to get to a destination without using turn by turn navigation. If i ask Siri how far a place is I get the distance in air miles not driving. So then if I ask how to get there Apple maps opens and begins turn by turn navigation. I would rather ask and then select to start  if I want, this is how it works with Google Now. Has anybody figured out a way to do this? If not Apple should make it an option in settings.

    Hi there,
    If you are publishing to a video format ( .mp4 ) output then it is not possible to insert the interactivity like buttons, or click boxes.
    If you have published the .swf, .htm or HTML 5 and if you have embedded a video inside that then that can have a button or click box on the last slide.
    Please elaborate more on your requirement and also tell the version of Adobe Captivate and Operating System.
    Thanks.

  • Release strategy against material type

    Hi
    Our customer requires a separate to group of people to release Raw Material POs and a person to release Spare Parts related POs. How can I set release strategy according to material type?

    Hi,
    These 2 purchases (Raw Mat & Spare Parts), are they being purchased by the same Purchasing Group?
    If different, you can use Purchasing group as a classification in your release strategy.
    Or Material Groups as a classification?
    Currently, i dont know if there is a way to differentiate between material types in PO for your release classification.
    Maybe you can use Exit to control CEBAN-USRC1 where, It includes the first few characters of your material number range.
    Im assuming that you have:
    1) SP001001 for Spare parts
    2) RM001001 for Raw Materials
    So you can use SP, for Spare parts release strategy and RM for Raw Materials Release Strategy.
    Im not sure if this works, just an idea.

  • PO Release Strategy not triggerred for particular Total Net Order Value

    Dear,
    I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
    For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
    All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
    But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
    Please suggest for solution.
    Thank you.
    Warm Regards.

    Dear All,
    While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
    But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
    May I know how the value for this field gets calculated.
    Thank you.
    Warm Regards.

  • Purchase Order not subject to release strategy for contract rel. strategy

    Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
    So I have checked this release strategy with this codes:
    CL24N ok,
    CT04 ok,
    CL30N ok,
    CL20N ok,
    Release simulation in release strategy works,
    Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
    Thank you for your help in advance.

    I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
    I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
    Also compare your release strategy settings with many existing documents in SCN.
    Check your Classification should be like that.
    You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

  • Release strategy for RFQ's not triggered after change

    Folks,
    Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
    1) document type (AN)
    2) purchasing type (RFQ purchasing document)
    It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
    Message was edited by:
            MdZ

    Hi,
    For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
    As RFQ don't have any specific table where the data is stored related to RFQ.
    So we Use CEKKO which only identifies the document type of RFQ.
    In your case in initial process while creating the RFQ release strategy is active.
    What change you have made to the Released RFQ.
    rgds
    Chidanand

  • Release Strategy to be reset for any change in purchase order

    Hi Experts,
    At present the release strategy configured is for any change in the value of the purchase order, the release strategy is reset. Now the the client wants that for even any text change of a word, text, quantity, value, addition, deletion the release strategy should be reset.
    Can any one guide to configure the release strategy for any change. Also please provide the list of standard parameters/scenario (E.g. change of price, change of quantity etc) for which the release strategy can be configured to be reset.
    Thanks in advance.
    AJ

    Hi Diwakar,
    I too have the same problem. I tried with Changeable indicator "1". The system does not allow to make any change to the Purchase Order even after the first level of Release. But the requirement is that the system should Reset the Release Strategy for even minor Change in the PO.
    Regards,
    S.Raghavan

  • Backend Source of Supply not supported for Direct Material in SRM

    Hi ,
    When creating S/C or PO in SRM for Direct Material , backend Source of Supply ( i..e Purchasing Info Record or Backend Contracts ) not availble to select as a sourc of supply .
    In our case, we are planning to maintain the sourc of supply (PIR or Contracts) in back end MM system only , then how can pick up the same ?
    Can anyone please suggest on this .
    Regards
    NAP

    NO Prashanta,
    It is still pending for me . i just raised OSS message to SAP ...but SAP saying that
    " I checked and found that in the classic scenario , Direct Materials cannot use backend contracts. The behavior described above is in accordance with the system design. Only local sources of supply (local contracts and interlinkages) can be
    used in the direct material scenario, as well as as in the extended classic scenario . Therefore the above error message which you get "Specify a valid contract" is valid."
    I replied with the doubt that "Thanks for reply but we are not convenience, since what we learnt from
    different SAP Blogs, Below SAP help and SRM Experts discussion forum
    is, for Ext Classic Scenario (since for direct materials it always
    tales by default Ext Classic Scenario, although we implemented Classic)
    Local SRM contract and Supplier List are the possible Source of Supply.
    As per SAP help documentation for Self-Service Procurement (Extended
    Classic) on below link
    http://help.sap.com/saphelp_srm70/helpdata/en/e0/f6be5157a24340bf7b1279854a52e1/frameset.htm u201CYou can assign the sources proposed by the
    system to items automatically (for example, if there is a single
    contract for the item being procured) or manually in the case of a
    quota arrangement, contract, or supplier from a supplier listu201D
    As per SAP help documentation for Sourcing Using Supplier Lists on
    below link,
    http://help.sap.com/saphelp_srm70/helpdata/en/d8/33ec56f17f4404806072749f7e764f/frameset.htm u201CIn supplier lists, you can also manually allocate
    back-end contracts from specific systems. This enables more effective
    sourcing for back-end contractsu201D
    In the Supplier List there is facility to enter the ECC Contract
    Number. Supplier List donu2019t support local SRM contract. It supports
    only ECC Contract /item.
    As per your reply, do you mean to say that Source List is not a valid
    Source of Supply for Direct Material in Classic Scenario (i.e. Ext
    Classic scenario)? If not, then why the backend ECC Contract displays
    as a Source of Supply, when we check the u201COrder as direct Materialu201D?
    Kindly suggest"
    Lets see.what SAP now replies.
    Simultaniously I'm looking some enhancment
    If you have nay update/soultion then please share with me.

Maybe you are looking for