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

Similar Messages

  • 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

  • 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

  • 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

  • Contract and release order for service: connection and field selection

    Hi Experts,
    I have some questions about contract and release order (PO against contarct) for services.
    A -I want ot know if there is any standar way to oblige the creation of a release order to a contract. I mean i had some users  that create a release order w/o reference to the contract and it works fine anyway. The document is a copy of the NB. I cant find the way to reference the 2 purchase document clearly.
    B - Using a release order, when copying the item from contract catalogue by clicking the service selection icon,  description and net price are correctly copied:  the description is not modifiable  but the net price can be change by the user. Can some body explain me where to modify this setting? where is the field selection and where in SPRO step by step please,
    thanks in advance
    Livio

    ... Nobody is so nice to suggest me any solution?  
    For the point A probably the only way is user-exit.... but for B i don't have any idea, please let me know
    thanks
    Livio

  • Release date for service pack for 9.2

    When is the release date for weblogic 9.2 sp1? What bug fixes are included in this release?

    I'd suggest contacting [email protected] for this type of information
    -- Rob
    WLS Blog http://dev2dev.bea.com/blog/rwoollen/

  • Release Procedure for Service Entry Sheet Wr to the Purchasing document

    Hi,
    I have configured the Service entry sheet release procedure on the basis of Purchase order document type by creating Characteristic With table -field (CESSR - BSART) and also class is maintained where the defined characteristic has been assigned.Release group is assigned to the class and all necessary customizing activities carried over. I assigned release group n Strategy thru Cl20n and also checked in Cl30n for the document type where system is exactly proposing only one value for the document type. But when i create Service entry sheet thru ML81N after saving the document i checked for release strategy through Goto-> Service entry sheet -> Release Strategy which is grey mode.
    I tried thru ML85 System says that no suitable purchasing document is available for release.
    thank u
    Nagarjuna
    Edited by: yalamanchi nagarjuna on May 31, 2009 1:33 PM

    the same configuration is not working in DEV environment but working fine in Quality and PRD

  • 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

  • No release for service PO

    I have craeted Service PO for Doc type FO, but there is no release strategy for that PO. FO has been maintained in configuaration...
    Error "Purchasing document 4500000046 cannot be released
    Message no. MEPO823
    I created release strategy for service entry sheet..has it overwritten that of PO? I dont think this could be the reason...Regards

    Hi
    Most of the time the cause of this error message is customer user exits
    which are implemented and activated on your system. Please deactivate
    an user exit used in these transactions and retest the issue.
    If the issue still happens, please open a ticket for SAP, it would be necessary to check in your system.
    Best Regards,
    Arminda Jack

  • Release startegy of Service Entry Sheet

    I configured release strategy for Service entry sheet with Release code 08.
    When i actually go to ML81N to release the same, i get same code in the drop down but when i select the same (08), it gives me "error  Release with code 08 not possible", instead it allows only to release the same with Release code R1 which is the code for Purchase Requisition.
    What could be the problem ?
    Regards,
    Shail

    Hi,
    I have just configured two release strategies for entry sheet's and they work correctly in our development sandpit. when I moved these to the test client, the config is showing correctly but the internal tables have not updated properly.
    This gives me the same error, but that is because the system cant actually find the release code.
    Is this the same problem you are having? If so I can post the solution for you.
    Cheers,
    Tim

  • Release date for JRE version 1.4.2_13

    Does anyone have a scheduled release date for JRE Version 1.4.2_13? I'm in need of this patch as it fixes some Oracle Forms Client Issues.
    Thanks in advance.

    Hi Jason,
    Can you please let me know the release date for Service Manager 4.1.
    Also please guide me where can I find the functionality difference between 4.1 and 4.2
    Thanks and Regards
    Neha Mahanty

  • Best Practices for Service Entry Sheet Approval

    Hi All
    Just like to get some opinion on best practices for external service management - particularly approval process for Service Entry Sheet.
    We have a 2 step approval process using workflow:
    1 Entry Sheet Created (blocked)
    2. Workflow to requisition creator to verify/unblock the Entry Sheet
    3. Workflow to Cost Object owner to approve the Entry Sheet.
    For high volume users (e.g. capital projects) this is cumbersome process - we looking to streamline but still maintain control.
    What do other leaders do in this area?  To me mass release seems to lack control, but perhaps by using a good release strategy we could provide a middle ground? 
    Any ideas or experiences would be greatly appreciated.
    thanks
    AC.

    Hi,
    You can have purchasing group (OME4) as department and link cost center to department (KS02). Use user exit for service entry sheet release and can have two characteristics for service entry sheet release, one is for value (CESSR- LWERT) and another one for department (CESSR-USRC1) .Have one release class for service entry sheet release & then add value characteristics (CESSR- LWERT) and department characteristics (CESSR-USRC1). Now you can design release strategies for service entry sheet based on department & value, so that SES will created and then will be released by users with release code based on department & value assigned to him/her.
    Regards,
    Biju K

  • 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

  • How to install downloaded Oracle Forms Developer/Services 6i Release 2 for linux

    Hi folks,
    I downloaded d2k6irelease2.tar (Oracle Forms Developer/Services 6i Release
    2 for linux) from
    http://otn.oracle.com/software/products/forms/htdocs/linuxsoft.html
    I untar the file on my linux machine however the extracted files don't
    seem to contain any installing program. I didn't find products.jar in the
    files and there are no script to install the software. I read the attached
    doc, however it only assumes that the installation is from CD-ROM. The doc
    doesn't help anything for this downloaded software. I wonder if anyone
    here know how to install it. Thank you so much.
    Best regards,
    Kai Huang

    There should be a text based installer in the /orainst sub-
    directory
    In that directory, just run the script:
    ./orainst
    The installer seems to require libXm.a, which wasn't included in
    my RH 7.1 installation, so I had to install the motif-
    development libraries before the full install would complete
    successfully.

  • Workflow Required for Service Entry release

    Hi !,
    Can anyone help me out by provide input as i want to have a workflow to be generated based on a Text feild (Sap Login ID) which user will be entering in a Text feild in Service Entry Sheet. What it should do is :
    1. Should Validate with my provided list of Approved Users. (Separate table entry to be maintained with reqd T-code).
    2. Mail to be triggered to his(Approver) SAP and Outlook ID for the release to be made with Document Information.
    3. He Should be able to Approve / Release through Workflow.
    4. Creator should be informed for the Approval Done.
    Please forward your comments.
    MM

    Please check these helpfull links:
    workflow for service entry sheet(ML81N)
    Re: Workflow Template(WS) or Workflow Task(TS) for Service Acceptance (SES)
    Re: Workflow issue on service receipting
    Service Entry Sheet Workflow
    Edited by: Afshad Irani on Jun 3, 2010 2:48 PM

Maybe you are looking for

  • LOOP DOUBT INSIDE  PACKAGE

    CREATE PACKAGE EMP_PKG AS CURSOR EMP_CUR IS SELECT EMPNO,DEPTNO,SAL,HIREDATE FROM EMP WHERE DEPTNO=30; PROCEDURE P_EMP; PROCEDURE P_GET_SAL(V_EMPNO NUMBER); PROCEDURE P_GET_LOC(V_EMPNO NUMBER); Now inside my Package Body INSIDE THE MAINPROCEDURE P_EM

  • Linux clearing of screen after command (man, vi, etc.) termination

    One small nuisance in perhaps every Linux distro is the clearing of the screen after the execution of commands like man, vim or git. I find this irritating because I might be very interested in seeing the output of say, 'git log' and comparing it wit

  • Use lexical parameter in select statement

    Hi, I have a report like below: select d.dname, &par1 mgrSal, &par2 empSal from emp e, dept d where d.deptno=e.deptno and d.deptno = :dno; Here the &par1 and &par2 are calling a function like: :par1 := ' f(:dno, :job)'; in the after parameter form. t

  • Read Receipts and Conversations

    It would be great if we could get read receipts included with conversations. For instance, if I send an email with a subject of "Project Update", I get a read receipt that's titled "Read: Project Update". The receipt isn't included in the conversatio

  • Question about creating an SQL search

    Hi, In the app I am developing the user can search one of my database tables by one or more of three fields. If a field is left blank is there anyway to set up an SQL statement so that a dummy search criteria is entered for that field? That probably