No release strategy for service PO

Purchasing document xxxxxxx cannot be released
Message no. MEPO823
I created release strategy for service entry sheet through following process.
1. Created three characterstics(service_val, serv_plant & ZSER_DOC TYPE) and assigned it to class 032 (gave it name service entry sheet) Communication structure CESSR and fields WERKS etc...
2. Than maintained all the config setting for service entry sheet through External service management..Maintained release groups, release codes, release strategy and r and maintained all the values .
3.I made a service PO with doc type FO
Now i dont get a tab of release on the service PO tab and get the above error.
Just let me know step by step how to config release strategy for service entry sheet.Do we need to maintain all above entries...?
For PO we have release strategy maintained for all document types and i am able to release the PO.
Regards,
Shailendra

Keep the release strategy at Plant level only....All the purchasing docs will get blocked

Similar Messages

  • Want to change my existing Release strategy for - PR, PO & Service Entry

    Hallow Experts ,
    Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
    1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
    2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my  service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
    thanks in advance.
    regards
    vb

    Dear Vikrant,
    1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
    Sol:  Not  Required but , doing it is recomandaed
    2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
    thanks in advance.
    Sol: No Only thing you have to  do is that   go to your class 32 and   chek what is the charaterstic define for the purchasing group  copy it
    2 Now go to  Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
    3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group ,  that  group will now in fact of release Strategy

  • Release strategy for PO and Service Entry Sheet

    Hi
    I maintain characteristics- Plant, Doc Type , Order Value & Purchasing Group for PO release strategy.
    should I maintain the same characteristics for service entry sheet ?
    the approval will be the same for both

    Hi,
    The Po reselase strategy can be set up separately from the entry sheet release strategy, so you can use even different characteristics for your entry sheet release strategy. These are not connected!
    Please read note 672719 question 5 - How can I set up a release procedure for service entry sheets?
    Note: The release strategy must be based on the structure CESSR.
    The PO release strategy is based on the structure CEKKO.
    For the SEs release strategy you must create a different class.
    Regards,
    Edit

  • Release stretegy for service PO

    Hi gurus,
    please help in one isssue, client is having release stretegy for service PO which is applicable for for only P.Gr 1 and 2, this is having three stage release stretegy. He want other pur. groups to be included in release stretegy and it should be two stage release strategy. please help how I can do it
    regards
    vikrant

    Hi Vikrant,
    follow the path
    IMG>Material Management>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Release Strategies
    Here define the new release strategy,
    Give the required Release codes, i.e 2 levels of approvals
    Goto "Release Pre-requisits",
    Define "release statuses",
    Then SAVE it,
    then go to "classifications", and give all the parameters same as tye other release strategy but that of EKGRP (Purchasing Grp) give the new purchase grp.
    But make sure that your CLASS contains the Purchase Grp as one of the Characterstics.
    and hence forth when ever you will make a PO with with any of these Pur Grp then the new release strategy can trigger.
    Hope It will Help you further.
    Regards,
    Yawar Khan

  • Release startegy for service PO

    Hi,
    Can you people help me out with release startegy for Service PO and service entry sheet?
    Regards,
    Satyendra

    Hi,
    Please refer below mention format.
    SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
    Three steps involved in release process of purchase order.
    1) Edit Characteristic: -
    Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP
    2) Edit Class: -
    After creation of characteristic, create class for release purchase order. In which you can take reference of
    Class Type: - 032,
    Status: - Release,
    Class group: - Release strategy class,
    And put reference of your characteristic, which are created by you in first step.
    E.g: - Class u2013 REL_PO
    3)Define Release Procedure of purchase order: -
    In this step four processes involved.
    1) Release Groups
    2) Release Codes
    3) Release indicator
    4) Release Strategies
    1) Release Group: - In which you can define release strategy group
    For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    2) Release code: - In which you can define release code. Enter value as
    Release group: - 01,release code: -01 u2013 Purchase Head,
    Release group: -01, release code: - 02 u2013 Auditor.
    3) Release indicator: - In this step you have to define release indicator.
    Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
    4) Release Strategy: - This is the final step for release strategy.
    Assign release code 01, 02.
    Click on release prerequisites, select 02 u2013 check box and click on continue.
    Click on release status button, enter release indicator X, I, S and click continue
    Click on classification button, Enter values of purchasing group for which you want to created release strategy.
    Note: - Create characteristics for service order document type in CT04.
    Regards,
    Mahesh Wagh

  • Release strategy for PREQs created from PM work order

    Hi All,
    I have an issue with determining  release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
    We have activated release strategy for Purchase requisition based on the following characteristics:
    CEBAN_PLANT
    CEBAN_COST_CENTER_GROUP
    CEBAN_MANUAL
    Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding  cost center goups.
    In the user exit we have consider to cases:
    The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
    The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
    The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
    We have defined  for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
    Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
    Best Regards,
    Desislava

    Hi,
    For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
    Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
    Regards,
    Raj

  • Release strategy for GR?

    Hi,
    My company has requirement that GR should be subject to approval process before it can be posted. As far as I know there is no standard functionality in SAP for this (at least in ECC, as in SRM there is one).
    Has anyone encounter this before? And how you deal with this? I have tried to persuade the user to drop this, but the problem is they already have this functionality in their legacy (which is custom made web based application), so it is pretty hard to argue with them in this area.
    Any help will be appreciated.
    Best regard

    Hi Yosea,
    Yes you said is right that there is no Release strategy. And can't imagine the situation in the legacy as well for this approval process thru Release strategy while doing the GR. But there is another way of accepting the goods either partial or full using movement types, you can do so.
    My question is why do you (i.e., your client or company) want to control (through the approval process) at Goods receipt level. That makes complex and un logical as well, thats why there is an approval process comes into picture at PO (Purchase order is an external purchase document and is going out to an external party /vendor /supplier) against that they can supply the material /provide the services to the Organization/company and is required to control before issuing this perticular document called PO (i.e., work order and is required to be controlled thru Electronic release strategy in SAP) instead of manual before in legacy since there is money matter involved and needs to control over investment on Inventory /services purchases.
    But where as GR, this is an incoming document, what the meaning in controlling it through approval process. That is the way you have to conveincene the client or company.
    Ok fine. If still they want this functionality to be implemented (that is to controlling at the GR level for the goods coming in. Then there is another way to control it through receiving the stocks into different stock types using the respective movement types, but not through Release strategy such as Blocking (GR blocking), Quality stock (for checking the quanlity standards thru Quality Inspection) and then later you can move these stocks to Unrestricted use stock, so that this can be allowed to use further.
    I dont think there is a functionality in the SRM as well. As I know that you can receive the Goods in SRM through Online Desktop confirmation that too partial or full quantity, that is nothing accepting/approval for the Partial or full quantity that is received against the PO which is created wrto to respective Shopping cart. And that is how you can control the goods that are coming inside / received at Stores/WH inorder to maintain the good quality of Inventory.
    Note: Controll always suggested at the time of making agreement  (i.e., Release strategy for the PO) but not at the time of receiving the goods. Here while receiving the goods only thing that a Stores person can see tmainly is needs to check for the Quantity, Quality of the goods that are ordered, Delivery time, Mode of transport, Shipping instructions, etc. This will help them further in evaluating the vendor.
    Hence there is no logic is going for that option
    Hope it clarifies,
    Regards,
    Sapsrin

  • MM - ML81N, Release Procedure for service entry sheet

    Hi Gurus, 
    I would like to active the realease strategy for service.
    in order to customize I  set:
    -Relase Groups
    -Release Codes
    -Release indicator
    -Release startegues 
    Then I run ML81N TRX and I called a sheet to try.  This sheet had to has done to one of the  release strategy set... 
    on the menu (of this trx ML81N)Entry Sheet->Set Status->Release (is still turn off)
    Where is the problem?, anybody could help me?
    Tks in advance,
    Nacho

    Hi,
    please read the FAQ note 672719, question 5:
    Setting up a release procedure is explained in the following short                         
    example: All service entry sheets with material group 007 are supposed                     
    to be subject to a release strategy. This release strategy requires that                   
    the service entry sheets must be released with release code A1. Only the                   
    cost center manager has the authorization for release code A1.                                                                               
    A) Create a characteristic for the material group:                                                                               
    o  Call Transaction CT04. (Path in the SAP menu in R/3 Enterprise:                     
           Cross-Application Components -> Classification System -> Master                     
           Data -> Characteristics)                                                                               
    o  Specify a name for the characteristic, for example CESSR_MATKL,                     
           and choose the 'Create' pushbutton.                                                                               
    o  On the 'Basic data' tab page, enter a description and keep the                      
           'Released' status.                                                                               
    o  On the 'Addnl data' tab page, enter table name CESSR and field                      
           name MATKL (Material group).                                                                               
    o  Enter class type 032 (Release strategy) on the 'Restrictions' tab                   
           page and then save the characteristic.                                                                               
    Note: The release strategy must be based on a field of structure CESSR.                    
    Using Transaction SE11, you can display which other fields are available                   
    in addition to the material group (field MATKL).                                           
    B) Create a class to which you assign the characteristic:                                                                               
    o  Call Transaction CL02. (Path in the SAP menu in R/3 Enterprise:                                 
           Cross-Application Components -> Classification System -> Master                                 
           Data -> Classes)                                                                               
    o  Enter a class name, for example FRG_ESSR, and class type 032 (for                               
           release strategy) and then choose the 'Create' pushbutton.                                                                               
    o  On the 'Basic data' tab page, enter any name. (Keep the                                         
           'Released' status.)                                                                               
    o  Enter characteristic CESSR_MATKL on the 'Char.' tab page and then                               
           save the class.                                                                               
    C) Now carry out the required Customizing settings. Follow IMG path                     
    (Transaction SPRO) 'Materials Management -> External Services Management                                                                               
    Seite 4                                                                               
    -> Define Release Procedures for Service Entry Sheet'                                                                               
    o  At first, you must create a release group (for example 03). For                  
           that, choose 'Release Groups', then choose 'New Entries', enter                  
           'Rel. Group' = 03 and 'Class' = FRG_ESSR. Save the entry. The                    
           system automatically determines value 3 (for entry of services                   
           performed) for the release object.                                                                               
    o  Now create release code A1 for release group 03. Choose 'New                     
           Entries' and specify the following values: Grp = 03, Code = A1,                  
           and description, for example cost center manager.                                                                               
    o  Create two release indicators, for example A and B. Select the                   
           'Released' field for release indicator B and save the entries.                   
           (Note: A release strategy must at least contain two release                      
           indicators. The first indicator (here A) must be defined as                      
           locked, the last indicator as released. Furthermore, the general                 
           changeability of the service entry sheet and the behavior for                    
           value changes are defined via the release indicators.)                                                                               
    o  Finally create the release strategy. Choose 'New Entries' and                    
           specify the following values: Release group = 03, release                        
           strategy, for example RS, release codes = A1. Assign the two                     
           release indicators A and B via 'Release statuses'. Assign                        
           material group 007 via 'Classification'. Save the release                        
           strategy.                                                                               
    D) Assign the authorization for release code A1 and release group 03 to                     
    the cost center manager. In role maintenance (Transaction PFCG), you can                    
    for example use the default values for Transaction ML85 for that.                           
    Regards,
    Edit

  • Release strategy for PO and Contract

    Hi,
    I maintain characteritic for PO
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    I maintain characteristic  for contract
    Company code
    Target Value
    Doc Type
    Purchasing group
    My class consist of
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    Company code
    Target value
    Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
    Q2:  What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
    Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
    Thank for your advice

    First of all
    For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
    You have to maintain all the characteristic value then only it will trigered release.
    Check the release indicator as well.
    Hope it will help.

  • Release strategy for quantity contract

    Hi Gurus,
    In quantity contract ..  target value will not filled by the value(in header details) as it is quantityt contract.
    We may have different line items with different cost..
    my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
    please explain/clarify
    regards
    subbu

    Hi,
    The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined  based upon the total net value of the entire purchasing document.
    Cheers,
    HT

  • Release Strategy for SA/Contract/PO

    Hi friends,
    Should we have different release groups and release codes in contracting/ SA/ PO.
    Because...
    I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
    But i want to maintan only 2 characteristics in release strategy for contract  [plant, total net order value]
    because the same is reflecting in contract config also.
    Is it possible..please help me frnds.
    Prabhu

    Hi Prabhu,
    Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
    Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
    Regards

  • Release Strategy for Contract is not getting picked whereas it is ok for PO

    Dear Experts,
    I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    Kindly resolve the issue.
    Satish

    S0004830404 wrote:
    Dear Experts,
    >
    > I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    > I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    >
    > Kindly resolve the issue.
    >
    > Satish
    hi,
    use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
    Thanking you

  • Release strategy for Schedule lines in SD

    Hello All
    Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
    I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
    Thanks in advance.

    Hello,
    I think you are in the wrong forum. Please choose the right forum category and post it there.
    Matthias

  • Release strategy for Scheduling Agreement(SA)

    Dear Forum,
    This issue is with regards to the release strategy for Scheduling Agreement(SA)
    Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
    Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
    We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
    Warm Regards
    Nainesh
    SAP ECC 6.0

    Hi,
    What's the SA Type that was created via MRP.
    If it's LP (without release document), release will not do anything BUT
    If it's LPA (release document), then you will not be able to Post the GR until release is affected.
    Thanks.
    Scheduling Agreement can be categories as
    1) LP (without release document) and
    2) LPA (with release document)
    If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
    Thanks.
    NanoSAP  
    Posts: 58
    Registered: 1/5/09
    Forum Points: 6 
       Re: release strategy for Scheduling Agreement(SA)  
    Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply 
    Dear Mr.Satish,
    Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

  • How to setup a release strategy for store generated purchase order

    Hi there,
    Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
    Greatly thank for your help.
    Kind Regards,
    2tea

    Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
    PO RELEASE STRATEGY
    The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data Table name CEKKO Field name GNETW and press enter
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group Rel. Object Class Description
    02 REL_PUR Rel. Strategy for PO
    Release codes - New entries
    Grp Code
    02 01
    Release indicators
    Release indicators Release Description
    0 Blocked
    1 X Release
    Release Strategy
    Release group 02
    Rel.strategy 01
    Release codes 01
    Release status 01
    Classification Choose your check values
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order.
    Regards,
    Ashok

Maybe you are looking for

  • I need help to find and open a job app that I exported, was able to fill out and sign and saved and now can't open it? What did I do wrong?

    I need help to find and open a job app that I exported, was able to fill out and sign and saved and now can't open it? What did I do wrong?

  • How to call a java method asynchronously

    Hello All, I am using a managed bean for calling a method to send email after records are commited, the email is sent through pl sql procedure in oracle database. But this procedure takes some time to send the email , due to which the next page navig

  • Document url link on webdynpro iview

    Dear All We have developed  custom webdynpro ivew. Assigned that ivew to page and can display in ESS submenu. and one more km doc iview is there for document disply. But requirement is when enduser access webdynpro ivew  , in the same page there shou

  • Screen Flicker Notes

    Ok this is an odd one I noticed today when I was looking at my notes on my Iphone 4 that any links or phone numbers would flicker every once in a while but Anything that was not a phone numbers of web link would not flicker. I thought something was w

  • Copa document not generated.

    Hi Experts, When a Sales & Distribution document posts through to accounting it generates an FI document, Profit Center document but unfortunately COPA document is not created. You are requested to please tell how to create COPA document from Sales &