PR Release Strategy for DOCUMENT TYPE

Hi Gurus,
I have created a Document Type in PR & I want to set a Release Startegy for ONLY that Document Type.
Can anybody explain me step by setp procedure for this ?, I have gone thru one link :
http://www.sap123.com/showthread.php?t=59
but I could not set the relase startegy. May be I am missing something ??
Thanks & Regards,
Vikas

If you want to define the release strategy only for doc type
then
create the class using CL02
create the chra for Doc type using CT04  - the table is CEBAN and the field is BSART
then assign the doc type value in char (after you create the char then go back and assign the value)
now assign your char to your class
now go to SPRO and goto PR release strategy config -  procedure with classification
go to Set Up Procedure with Classification
create your release group by assigning the calss you have created (make sure this config should have only one class)
create release code
release indicator is already exist in sap so you don;t need to create
create your release strategy and assign the value in classification tab of release strategy
this will work
but make sure that - if you are creating only for doc type means all the reqs created for this doc type will be blocked by the system. so if you have reqs like if this doc type and the amount >5000 then only block then you have to have amount is also you char in your class
hope this will give you a cleat idea

Similar Messages

  • Release strategy by document type wise

    in our current project we are prepare lot document type in PO. some document type i need release strategy some no need
    how i have assingn that
    pls explain the steps

    create a characteristic with CEKKO--BSART and assign the same in your class and further use this characteristic in your release strategy.
    regards,
    Indranil

  • Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

    Hi Friends,
    I have a issue to fix. The issue is releated to PR.
    There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
    I have to retrigger the release strategy for all the affected PR's.
    The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
    Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
    Regards,
    Manjunath K

    Hi,
    Refer the discussion to triggers release again on release code addition/change in release strategy.
    release code is changed on PR release strategy - old PR can´t be approved
    Regards,
    Biju K

  • Release Strategy for a new material type in PR

    Dear Friends,
    One of our client require new Release Strategy for a particulat material type PR. Can u pl provide me the steps to configure a new release strategy for PR for a particular Material type.
    Regards,
    Ask

    Hi,
    Create a Char for your material types in CT04(MARA-Table,Field-MTART) and assign the same to your Class in CT02.
    Then follow all the cusmozation path for your PR release startegy .
    For Config part refer the below wiki link it may help you.
    http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
    http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM?focusedCommentId=195723808#comment-195723808

  • What is the use of Release Strategy for Sales Document

    Hi,
    Can i know what is the use of Release Strategy for Sales Document? Difference between lowest level and Highest level.

    Hi,
    Can i know what is the use of Release Strategy for Sales Document? Difference between lowest level and Highest level.
    Lowest Status No: Sale Document can have several statuses at the same time. However, only one of the statuses may have a status number. If another status with a status number is activated; the old status with status number is deactivated. This is only valid under certain conditions. The system makes a note of the status with the highest status number that has been reached up to the present. The "lowest number" of this status number determines which status number a new status must have.
    Highest Status No: Sales Document can have several statuses at the same time. However, only one of the statuses may have a status number. If another status with a status number is activated, the old status with a status number is deactivated, provided the new status number does not exceed the 'highest number' defined for the old status number
    If you want more clarity try to check below link
    http://www.sapfunctional.com/SD/ReleaseStrategy/Index.htm
    Regards,
    Prasanna

  • 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 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

  • 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, RFQ & Contract

    Hi,
    We have created release strategy for PO, RFQ & Contract.
    Characterisitc is created for Target Value for Header Area (CEKKO-KTWRT)
    for RFQ & Contract it working fine but for PO not triggering.
    what can be the cause.
    Pls guide.

    Hi,
    Melih is right, for POs you can not use the target value.
    What you might do is to include the document type and CEKKO-GNETW as additional characteristics and then set for contract document types the GNETW blank, and for PO documet type the target value blank. Blank means any value should fit.
    I hope this hint helps!
    Best Regards,
    Arminda Jack

  • Release strategy for Return PO

    Hi,
    Can we create Release strategy for Return PO's. ?
    Regards
    Sunil

    Hi,
    The process for return PO is:
    Process:
    - Create a return PO
    - Create a outbound delivery
    - Goods issue
    Release Strategy can be created for All Document Types as Document Types being one of the determining factors for Release strategies. So under Classification data Characteristics which we maintain determine the release strategies for a Particular Purchasing documents. Actually it depends on your Business case that for what all documents you want to have a release strategy config.
    regards,
    Prashant Rathore.

  • Release strategy for Future validity period- (Outline agreements)

    Dear All,
    I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
    E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
    I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
    How to set up release strategy in the above case.
    Thanks in Advance.
    Regards
    Amar

    Hi Amar,
    1) if you maintain a target value (EKKO-KTWRT) in the header of the            
    contract this value is the basis for the determination of the release          
    strategy. If the target value is 0, the system will cumulate the               
    values of the items and will use this value for the determination.                                                                               
    2) So if the target value is 0 and you change the price of a condition         
    with a validity period in the future the system will react in the              
    following way:                                                                               
    Example:                                                                       
       the contract contains one item with quantity = 100 and a net price          
    of EUR 5,-.                                                                    
       all contracts with a target value from EUR 0 - 1.000,- should be            
    subject of a release strategy                                                  
       the contract is created and released on October the 1st                     
       ME32K -> October the 2nd you define a new price of EUR 7,- with a           
    validity period from 03.10.09 - 30-10.09 -> you save the contract              
    -> the release strategy is not reset, as the start date is not                 
    reached yet (system date < startdate of validity period)                       
       ME32K October the 3rd you change a field in the contract -> the             
    release strategy is reset                                                                               
    This is system design that a release strategy can only be reset through        
    an action by the user. The determination of the release strategy can't         
    be triggered automatically in the background.      
    If you create a document which is subject of an overall release strategy      
    (e.g. p.o., contract) the determination of the release strategy takes         
    place when the user hits the 'save' button or chooses the 'check'             
    function.                                                                     
    So there must be a kind of event that tells the system that something         
    has changed.                                                                               
    Regards,
    Edit

  • Release strategy for auto created PO's

    Hi Guys,
    I have a requirement to implement release strategy for automatically created PO's.
    PR's are created automatically and we have a program which create PO's automatically.
    we would want to release them before generating output to vendor.
    could anyone please have any inputs here.
    regards
    mittu

    Hi!
    You may use your existing release strategy or create a new one (depending on your requirement). You just have to add/ use the document type you used for your auto-generated POs.
    Hope this helps! =)

  • 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

  • Purchase Requisition Release strategy for MRP based Requisition

    Hello Gurus
    We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
    Thanks
    Nick

    Hi,
    If you want include the MRP related PR in Release strategy.
    You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
    So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
    there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
    But it will  not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
    I think first one is best suited.
    rgds
    Chidanand

Maybe you are looking for