How to configure release strategy in case of document parking ?

Hi experts,
                  I have a requirement wherein i have to create a workflow with four level approval when a document is parked before it can be posted.
The approval is by company code,reacon code and the amount .For example for a particular reason code for particular amount one person has to approve,if the amount is greater then 2 people have to approve, so on.
Is it possible to configure such a release strategy in SPRO ?
Kindly help,
thanks in advance,
regards
Ashwin

If it are FI Invoice you're talking about, it's possible.
Do you have access to the best practices of Public sector management ? There's an example on how to implement an FI workflow.
If not, check workflows on the object FIPP

Similar Messages

  • How to configure release procedure for rate contracts release

    Dear all,
    How to configure release procedure for rate  contract following are the requirements
    they are two release codes c1 & c2 <=100000,>=100000
                    if  c1 is not there c2 has to be approved
         Change in the value of the rate contract contract
         Change in the validity of the rate contract
         Addition of deletion of line items
    While using a non u2013 released rate contract in the PO an error message should shoot out.
    Also the logic should be changed while using the rate contract in the PO.
    The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
    It should be possible to refer existing valid rate contracts in purchase orders.
    Regards,
    bhaskar

    Hi,
    In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables  for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
    class in standard is the same FRG_EKKO, you can use the same for contract.
    To distinguish if it's a contract or PO, EKKO-BSART can be used.
    For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
    You can restrict the document type to set up the release strategy for only contract.
    Of cause, you can also create your own release class Z* for contract copying standard
    one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
    OLME:
    -> contract
    ->Release Procedure for Contracts
    ->Define Release Procedure for Contracts
    ->Release Groups
    If you have already created the PO release class.
    Assign a new chracteristic of Document Category -BSTYP
    Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
    http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES

  • How to do release strategy work flow in MM

    how to do release strategy work flow in MM. for purchase order release how to do release strategy work flow. please give elaberate steps

    1: Install SAP - your IT support team should be able to help you with this
    2: Start the SAP Logon Pad (it is in the Start menu if you use Windows - look around)
    3: Go to transaction SPRO
    4: Navigate the structure, go to materials management, purchasing and then look around
    5: Read the documentation for each activity
    6: Perform the activities
    Seriously, you will be amazed by how much you can learn by actually making an effort.
    PS: I see you <b>expect</b> 10 points for your one-line replies, so this one should be worth at least 50.

  • Configure Release Strategy for Contract

    Hi All,
    I want to Configure Release Strategy for Contract.
    I have configured Release Strategy  for PO. Is the process for both is similar?
    What should the table & field name should we use for configuring Release Strategy for Contract.
    Pls. guide.
    Regards,

    Thanks Neeraj for the reply.
    For PO, I have used Table CEBAN, Field BSART, GNETW.
    Could you pls. suggest what fields should we use.
    Also tell me what would be process of releasing the contract using ME35K, as the Screen seems to be different from ME29N.
    Regards,

  • New Release Strategy in case of PO amendment

    Dear All,
    We have the release strategy at PO level on 3 parameters,
    Purchasing Group, Value and Document type.. for each parameter we have created the characteristics EKKO- EKGRP, EKKO-BSART, EKKO-GNETW. Till date system is working ok and trigreeeing the release strategy as per it should.
    When ever users edit the PO, again system sets the release strategy as per above logic.
    Now our requiremet is, when ever user edite the PO value or PO quantity, system should trigger a new release strategy.I come to know that, SAP have a provision to maintain the release strategy on "Version level also", I have tried the same but i facing one problem, when we try to create the characteristic based on Version , system creates it and put field name "REVNO", data types is coming "CHAR".
    Can any one send me a user manual and steps for this.
    Thanks in advance,.
    Vikas

    Hi,
    You can set a control within Config. there is a parameter called as release indicator.
    Follow this IMG path:
    SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
    1     Cannot be changed
    2     Changeable, no new determination of strategy
    3     Changeable, new release in case of new strategy
    4     Changeable, new release in case of new strat. or val. change
    5     Changeable, new release if new strategy/outputted
    6     Changeable, new rel. if new strat. or value change/outputted
         Changeable, new release in case of new strategy
    Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
    Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
    So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.
    Hope this explanation was clear.
    Prashant Rathore.

  • How to assign Release strategy with new PO type

    Hi experts,
    I have created new PO type but the same is not mapped with release strategy at the time of raising purchase order.
    I have done the following steps :
    a ). Creation of new doc type via SPRO > MM > PURCHASING > PO > DEFINE PO TYPE
    b).  Edit characterstics in release strategy via path SPRO > MM > PURCHASING > PO > RELEASE PROECURE FOR PO > EDIT CHARACTERSTICS > VALUES  (  MENTION NEW PO TYPE & DESC. HERE )
    Still I am unable to find release strategy tab in purchase order. Please help.
    Suggestions / Rewards will be highly appreciated.
    Regards,
    ( Rajneesh Gulati )

    Hi ,
    I dont know how much customisation u have complited ,
    But for release strategy
    1 Following are the imp charecrticities ct04 you have to define
    Order type (Purchasing)
    Plant
    Total net order value ( with  table &  field)
    2.check or create relese group is assighned to appropriate class cl01 (with above charecricities )
    3.define relese code ( in this u define release level --supervisor , manager etc)
    4.release indicator  (block ,release)
    5.define the group with strategy in that specify prerequisites,release status,classification (specify to the document & plant you want to maintain)
    6.create po me22.  In me29 you can release it( unless u cant process)
    Dev

  • 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

  • PR overall release strategy (with shared PR document types)

    We are asked to configure 'overall' PR release for some of the plants of our client.Now ,we know,  this needs to be configured in two places in SPRO. One, in release group definition & two, document type (PR) definition. Our issue is that the doc types involved here is shared by some other plants as well who doesn't need 'overall' release. Is it possible to configure the requirement without disturbing the unwilling plants ?

    Hi ,
    The PR release strategy can be done at Item level also ,which has to be set that the PR has to be released at item level and after doing it ,all the item values can become characteristics values for the release strategy
    The Plant can be taken as one of the characteristic.
    The view CEBAN gives all the related views.
    check the below LInk for Futher information on the same.
    http://www.scribd.com/doc/531679/Release-Procedure-for-Purchase-Requisitions
    hope so it helps
    Regards
    Anjanna.

  • Release Strategy in purchase order document type

    Hi Gurus..
    I'm tring to tweak the single RS in the system.
    I've set the charcteristic using table CEKKO field BSART, restriction 032, I've set two document types as the Characteristic Value (ZLOG - ZADM). Then I´ve set the class with this characteristic, Created Release Groups & linked to class , Created Release Codes, Release Indicator, and Set up strategies
    .. but  It doesn´t pick any release strategy.
    The funny thing is if I delete the document types values entered in CL20N it works for all doc typs, but if I set the docs types that it should take to pick the RS it doesn't work at all...
    Please advice..

    I´m not such a abapper but I guess there is not values taken to ekko, does it ring a bell?
                                            BUKRS                                       
                                            BSTYP                                       
                                            BSART                                       
                                            BSAKZ                                       
                                            LIFNR                                       
                                            SPRAS                                       
                                            EKORG                                       
                                            EKGRP                                       
                                            WAERS                                       
                                            BEDAT                                             00000000
                                            LLIEF                                       
                                            KUNNR                                       
                                            RESWK                                       
                                            LBLIF                                       
                                            INCO1                                       
                                            KTWRT                                             0.00
                                            LIFRE                                       
                                            WERKS                                       
                                            MATKL                                       
                                            LTSNR                                       
                                            USRC1                                       
                                            USRC2                                       
                                            USRN1                                             0000000000
                                            USRN2                                             0000000000
                                            GNETW                                             0.00
                                            SUBMI                                       
                                            MEMORY                                       
                                            KONNR                                       
                                            REVNO                                       
                                            PDUMMY                                       
                                            KDATB                                             00000000
                                            KDATE                                             00000000
                                            EBELN

  • How to configure a new third party sales document type?

    Hi SAP SD gurus,
    I am new to the SAP world, I need your help in configuring a new third party sales document type for a site.
    There are existing third party document types being used in the region, but the client wants an entirely new third party document type that is activated for CREDIT MANAGEMENT.
    I just need your inputs, as how to go about it. If I copy from an existing third party sales doc. What additional steps do I need to follow? Like Item category config, copy control settings, and credit management.
    Is there a need to create new billing types?
    Also as per process, by creating a new document type, how will it affect the logistic processes, if any?
    Thanks a lot in advance for your valuable inputs.

    Hello,
    You can create new document type under following customization path
    SPRO>>Sales and Distribution>>Sales>>Sales Documents>>Define Sales Document Types
    Now create new document type by copying the standard document type OR
    Now go to
    SPRO>>Sales and Distribution>>Sales>>Sales Documents>>Sales Document Item>>Define Item Categories
    which is already defined for third party sales (TAS)
    Now assign this iteme category to your new document type
    SPRO>>Sales and Distribution>>Sales>>Sales Documents>>Sales Document Item>>Assign Item Categories
    Assignment needs to be done in combination of sales document type and item category group (BANS)
    Now
    SPRO>>Sales and Distribution>>Sales>>Sales Documents>>Schedule Lines
    Assignment of schedule line is already done as you are using the standard one.
    Lastly, you may need to maintain copy control for your newly created sales document type for this go to
    SPRO>>Sales and Distribution>>Sales>>Maintain Copy Control for Sales Documents
    (Copying Control: Sales Document to Sales Document)
    Here you can define copy control requirements.
    BR,
    Tushar

  • How to configure Item Category in Purchase Order document

    Hi
    Can someone tell me how to configure the Item Category in Purchase ORder document?  This field is displayed next to Account Assignment in PO screen.
    Thanks,
    Lin-Lin

    I think your issue is screen layout of the PO
    please go to
    SPRO-MM-Purchasing-Purchase order-Define Screen Layout at Document Level
    here you can select the ME21N and double click on it
    on field selection of basic data you can make item category is optional than it will be avialable
    if still you find the problesm than check your field selection of your document type and change that field selection as above mentioned.

  • Release Strategy in MM PO document

    Hi,
        Could you please any one can clear my doubt in Release Procedure for P.O/PR. I can configure release procedure two level based on value.
       Now my doubt is where these two different users going to get their authority. Is it through Parameter ID using T.code SU01. If so What is the parameter ID (FGB, FGE, FGR, BFC, FAB)  and Value I need to maintain for this user.
    Kind Regards,
    Sankar.K

    Sankar,
    For PO releases, the release codes are assined to users in role maintenance (PFCG). So, one user can perform release by using code, which assigned to his role.
    regards
    sairam akundi

  • Add release strategy in the PO document type

    Dear all,
    I create one PO Return but there is no release strategy in ME28, what should I do to add the release strategy for that PO doc type.
    Thanks
    Pauline

    Pauline,
    I would suggest you to please post this query in ERP MM forum to get it answered asap.
    Regards,
    Faisal

  • Release strategy:ME53N : Older PR documents shows, modified PR rel.strategy

    Hi Friends
    We have updated the sequence of release codes for certain PR release strategies. But when we moved the changes production, i observe that all the older PR documents (Which were released last year and completed) also shows the updated release strategy in transaction ME52N/ME53N.
    Can someone pls some explain? Is this normal?
    SAP doesnt store the release strategy and its sequence of release codes, which were determined at the time of document creation?
    Thanks for your help...Raj

    Hi,
    There is no change in the older documents.
    The documents are older by few years.
    I have checked few documents randomly, the tcode ME53N shows only the updated release strategy.
    I did some investigation today on this.
    i think system will not keep the release strategy pertaining to document creation.
    It will just store Release Group and Release strategy in the Purchase Requisition tables (like EBAN).
    And when ever we try to display the document it will go and read the release strategy sequence from relevant tables.
    Hope someone helps to validate if my investigation is correct.
    Good day..

  • Release strategy behavior for purchase documents

    Hi all,
    I'm working at a company that recentily has implanted SAP. We noticed last week that the approved documents, like PR, PO, RFQ etc.. can be modified by the users and that documents doesn't modify its approval status, I mean, they remains approved.
    I'd like to know if is there any standard way to configure the SAP to not allow any modification in an approved document, or if an approved document has been modified, it resets its approval status to pending approval again.
    Thanks in advanced,
    Rodrigo

    Rodrigo wrote:
    > I'd like to know if is there any standard way to configure the SAP to not allow any modification in an approved document,
    For this, Use OLME -> Purchasing -> Purchase Order -> Release Procedure for Purchase Order --> Define Release Procedure for Purchase Orders -> Release Indicator chose the last level for Changeability as "1 Cannot be changed"
    Rodrigo wrote:
    > if an approved document has been modified, it resets its approval status to pending approval again.
    For this, Use OLME -> Purchasing -> Purchase Order -> Release Procedure for Purchase Order --> Define Release Procedure for Purchase Orders -> Release Indicator chose the last level for Changeability as "4 Changeable, new release in case of new strat. or val. change"

Maybe you are looking for