Release Procedure for every Purchasing documents

Hi,
for a procument of material eg:- Material007
Can I set Release Procedure for Purchase rquisition
then after releasing Purchase rquisition i need to create a RFQ
which is also subject to Release Procedure ,After releasing RFQ I should able to enter into a Contract,which also subject to Release Procedure ,After releasing Contract  i need to create a Purchase Order which is also subject to Release Procedure,After releasing Purchase Order only I should be able to Receive the goods.
Is it possible to do this way ?Can any one help me?
Thanks

Why you want to put so many locks??????
well if case your required use below steps for all document typew in IMG.
suggestion to download the BBP from below link also
http://help.sap.com/bestpractices/BBLibrary/bblibrary_start.htm
3.4.24     Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works.  The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle.  The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1     Creation of Characteristics
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Characteristic
Transaction Code     CT04
2.     On the Characteristic screen, make the following entries.
3.     In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name     Description     User action and values     Note
Select Addnl Data tab                
Table Name     Table Name     CEKKO     
Field Name     Field Name     GNETW     
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab               
Description     Description     Total net order value     
Status     Status     Released      
Data Type     Data type     Currency format     Selected by system
Number of characters     Number of characters     15     
Decimal places     Decimal places     2     
Currency     Currency     INR     
Interval vals allowed     Interval values allowed     Check this tick box     
Multiple Values     Multiple values allowed     Select this radio button      
4.     Choose Enter to complete the entries
5.     Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2     Creation of Class
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Class
Transaction Code     CL02
2.     On the Class screen, make the following entries:
Field name     Description     User action and values     Note
Class     Class     PORELPROC     
Class Type     Class Type     032     
Choose Create icon or white paper icon to create new class.
Description     Description     Purchase Order Release Procedure     
Status     Status     Released     
Choose Char. Tab to input characteristic name.
Characteristic     Characteristic     POVAL     Created in above step
3.     Choose Enter to complete the entries
4.     Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3     Configuration of Release Procedure
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Define Release Procedure for Purchase Orders
Transaction Code     SPRO
2.     On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Rel. Group     Release Group     02     
Class     Class Name      PORELPROC     Created in above step
Description     Description     PO Release Procedure     
4.     Choose Enter to complete the entries
5.     Choose Save icon or Ctrl + S to save the entries.
6.     Choose yellow arrow to go back to popup screen.
7.     Choose Release Codes to select.
8.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Grp     Release group     02     Created in above step
Code     Release Code     01     
Workflow     Workflow     Leave it blank     
Description     Description     Purchase Officer     
Grp     Release group     02     Created in above step
Code     Release Code     02     
Workflow     Workflow     Leave it blank     
Description     Description     Materials Manager     
9.     Choose Enter to complete the entries
10.     Choose Save icon or Ctrl + S to save the entries.
11.     Choose yellow arrow to go back to popup screen.
12.     Choose Release indicator to select.
13.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Release ind.     Release Indicator     1     
Released     Released     Leave it blank     
Chgable     Changeability     4     
Value change %     Change of value     10%     
Description     Description     Purchase Order Blocked     
Go to 2nd line and input the following values:
Release ind.     Release Indicator     2     
Released     Released     Select Check box     
Changeable     Changeability     6     
Description     Description     Purchase Order Released     
14.     Choose Enter to complete the entries
15.     Choose Save icon or Ctrl + S to save the entries.
16.     Choose yellow arrow to go back to popup screen.
17.     Choose Release Strategies to select.
18.     Choose New Entries icon and make the following entries:
19.     System will give new screen New Entries: Details of Added Entries
Field name     Description     User action and values     Note
Release Group     Release group     02     
Rel. Stategy     Release Strategy     S1     
          Capital Items Release     
Release Code     Release Code 1     01     
Release Code     Release Code 2     02     
20.     Choose Enter to complete the entries.
21.     Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22.     Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default.  Choose Continue.
23.     Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24.     Choose Next Screen icon or choose F8 to continue.
25.     If you want to simulate the release procedure you can choose Release Simulation icon.
26.     Choose Enter to complete the entries.
27.     To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4     Assignment of Values to Release Procedure 
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step.  If you do not want release procedure you may change the value to Zero.
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Cross-Application Components  Classification System  Assignments  Assign Object to Classes
Transaction Code     CL20N
2.     On the Class screen, make the following entries:
Field name     Description          User action and values     Note
Class Type     Class Type          032     
Choose Enter to Assign values.
Release group     Release Group          02     
Rel. Strategy     Release strategy          S1     
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR  against filed Value.
3.     Choose Enter to complete the entries
4.     Choose Save icon or Ctrl + S to save the characteristic.

Similar Messages

  • T.Code for Release Procedure for Purchase Order Type

    Hi Frd
    im working in ECC 6.0.
    OMGS is t.code for Release Procedure for Purchase Order Type in SAP 4.6.
    Can anyone tell me what is the t.code for Release Procedure for Purchase Order Type in ECC 6.0 .the OMGS t.code is not working in ECC.
    Thanks
    By
    Pari

    Hi Rajasekharan,
        Go to tcode ME22 and enter the Purchase order number.
    inside the Display screen,u can see a GREEN flag button on the Application Toolbar.
        Click on a item and press the Green Button.
    U will see the release code,provided the Purchase order is set to release strategy,after that Go to tocde ME28 enter the release code ,along with Document number and then release the Purchase order.
    Actually the tcode for releasing purchase order is ME28
    Reward points if useful.
    Cheers,
    Swamy Kunche

  • Define Release Procedure for Purchase Orders

    Hi Friends,
    We are changing Release procedure for purchase orders for one department from > $ 5000 to > $ 10000.
    We defined three characteristics for the class namely Purchasing Order Document, Purchasing Order Type and Ner Order Value which is Currency data type. I Defined Release Procedure for Purchase Orders in configuration master. It's working fine, I mean the Net order Value field is updated in Configuration Client.
    After transporting the above change to the Testing Client, the Net Order Value field did not update in testing Client even though I created Characteristics in Testing Client (as characters are not transportable, I created them seperately in Testing Client). I can't update the Net Order Value manually in Testing Client as it says "Client 010 (test) has status 'not modifiable' "
    Please tell me how to update that field, as the net order value didn't change even after transport. I can't change manually in testing Client as the status is "not modifiable"

    Hi,
    Yes I have already done that.
    In SPRO,
    After hitting the following:-
    MM --> Purchasing --> Purchase Order --> Release Procedure for Purchase Orders --> Define Release procedre for Purchase Orders
    I have to process the objects in the following sequence,
    Release Group, Release Code, Release Indicator, Release Strategy & Workflow.
    Upto Release Indicator it is fine. After hitting Release Strategy, I should select the release strategy (which I just created) and display. Then 4 buttons will be displayed namely,
    Release Prerequisites, Release statuses, Classification, Release simulation.
    Upto Release statuses it's fine. Afeter hitting Classification,
    the values of Purchase document & Order type are populated, but the Total Net Order Value is Blank. It is supposed to populate the amount & 10,000. But it is not.
    Actually that amount will be stored in the field GNETW of table CEKKO. But CEKKO is a Structure not a table. So I can't update the field.
    Please advice me...
    Thank You,
    Nag

  • Release procedure for Document Park / Post

    Dear FI experts,
    We want to set release procedure for Customer Credit Notes (FB75)
    For this we did following configuration -
    FI >> FI Global Setting >> Document >> Document Parking (all setting w.r.t. release approval)
    Created and parked a document using FB75.
    In MM procedure we give the authorisaiton of Release code to respective users and then he is able to release the PO.
    What is to be done in this case ?
    What is the process / tcode for releasing this parked document.
    Thanks & Regards
    Rajesh

    Hi Prem
    Thanks for ur reply
    I tried MRBR but system is giving following message -
    There are no blocked invoices that match your selection
    Message no. M8654
    In MM release procedure , authorisation of Release code is given to respective users and then he is able to release the PO.
    What is to be done in this case ?
    Can you please explain??
    Regards
    Rajesh

  • Release procedure for Purchase orders

    Hello SAP Gurus,
    Can anyone explain in steps the release procedure for purchase orders and also can any one explain how it differs from Puchase requisition release procedure.
    Thanks
    NDS

    Hi
    Release procedure for Purchase orders here is process flow.
    Go to spro>img>materials management>purchassing>Release procedure for Purchase orders
    1. Create characterstics  -Intially you will create characterstics based on which you would like to release a purchase order.
    Charactrestics are like plant, purchase order value,purchase group etc.. Assign characterstics to release class 032.
    2. Create Release group say 01 and create release codes like pm(project manager), gm(general manager) etcc..
    3.  Create a Release starategy say s1 and assign release group to it 01 and release class 032 and department to whom this release stategy applies say MM. define the order of release say first pm followed by gm etc..
    4.  under classfication define value limits for release of purchase order.
    5. define release indicators
    6. simulate the release
    7. assign if there is any workflow.
    hope it helps.

  • Release Procedure in Indent/Purchase Order

    I want to customise release strategy in indent and Purchase order in SAP. Kindly provide me steps to configure this. will apperitiate your efforts.
    Manjit

    Hi Manjit,
    Release Procedure for Purchase Orders
    In this section, you set up a release procedure for purchase orders (POs).
    Requirements
    If you want to use workflow to release POs, you must make the standard and basic settings for workflow (Basis -> Business Management -> SAP Business Workflow).
    How do you set üp a release procedure for POs?
    To set up the release procedure, you must make a series of settings in Customizing. This section provides you with an overview of the necessary activities.
    You must perform the following steps:
    1. Create characteristics and classes
    For more on this topic, see Edit Characteristics and Edit Classes.
    Note
    If you wish to link your release procedure to workflow, you must perform steps 2 and 3 . You make these settings in Customizing for Business Workflow (Basis -> Business Management).
    Otherwise, continue with step 4.
    Define organizational plan
    For more on this topic, see Edit Organizational Plan.
    Assign standard tasks and activate event-receiver linkage.
    For more on this topic, see Perform Task- Specific Customizing.
    1. Set up release procedure for RFQs
    a) Create release group
    b) Create release code
    c) Create release indicator
    d) Create release strategy
    Note
    You need only carry out the following step if you wish to link your release procedure to workflow.
    e) Assign release code to a user
    For more on this topic, see Define Release Procedure for POs.
    2. Check release strategies
    For more on this topic, see Check Release Strategies.
    Further notes
    For more information, refer to
    · Implementation of a Release Procedure for Purchasing Documents
    · Release of Purchasing Documents (SAP Library -> Basis -> Business Management (BC-BMT) -> SAP Business Workflow (BC-BMT-WFM) -> Reference documentation -> BC Workflow Scenarios in the Applications -> MM Materials Management: Workflow Scenarios)
    Edit Characteristic (CT04)
    In this step, you create characteristics for a release procedure for purchase orders (POs).
    Classification characteristics are the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchasing document (e.g. purchase order or RFQ).
    Example
    Release condition for release strategy EA:
    Characteristic Characteristic value
    Total net value of PO Above $10,000
    If the total value of a purchase order exceeds $10,000, release strategy EA is assigned to this PO.
    Requirements
    In communication structure CEKKO you will find all the fields that can be used as characteristics for a release condition (e.g. BSART for the order type and GNETW for the total order value).
    Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEKKO in the field Database table , and choose "Display".
    Note
    If you wish to define a separate release strategy for the various document categories (PO, RFQ, etc.), you must create a characteristic for each relevant document category.
    Activities
    1. Create a characteristic for each field from communication structure CEKKO that is to be a criterion for your release strategy. You have a free choice of names for the characteristic.
    2. Enter the table name and the field name on the tab page Additional data (for example, table CEKKO for field GNETW).
    Note
    o Do not select any of the indicators in the area Procedure for value assignment on the tab page Additional data. Only if none of these indicators is marked can you assign a value or value interval to the characteristic when defining your release strategy.
    o When you create a characteristic for a currency-dependent field (e.g. GNETW), a box appears in which you must enter the currency for the relevant value. The system then converts the currency of the purchasing document into this currency.
    3. Check the data for the chosen field on the tab page Basic data.
    If you want to enter several values or a value interval for a characteristic, set the Multiple values indicator in the area Value assignment.
    Note
    Value intervals can only be specified for numerical values (e.g. an interval of $10,000 to $15,000 for the value of the purchase order.
    4. Check the texts for the field on the tab page Descriptions.
    5. You can maintain default values for a characteristic on the tab page Values.
    If you maintain values here, these values will be displayed as input help under Create Procedure with Classification -> Release Strategy -> Classification . If you wish to use not only the input help but also other values, you must select the Additional values indicator.
    Note
    You can also maintain ' ' as a default value. For example, for account assignment: ' ' for stock material, 'k' for cost center, and 'a' for asset.
    6. If you want to restrict the use of a characteristic to particular class types, specify the relevant class types on the tab page Restrictions. For example, class type 032 for the release strategy.
    Further notes
    Further information on characteristics is available in this Customizing activity via Help -> Application help.
    Customer exits
    Customer exit M06E0004 enables you to change the communication structure for determining the release strategy for purchasing documents.
    Edit Class( CL02 )
    In this step, you create classes for a release procedure for purchase orders (POs).
    You use a class to group together characteristics that are to constitute a release condition for a release strategy. In the step "Define Release Procedure for Purchase Orders " you assign this class to the release strategy.
    Activities
    1. Create a class with the class type 032. You have a free choice of names for the new class (e.g. REL_RFQ for the release of RFQs).
    2. Assign a name for the new class on the tab page Basic data.
    3. You can view an error message if different characteristics with identical values have been assigned to a class. To be able to do so, select the Check with error message indicator in the Same classification area.
    4. If appropriate, select terms to be used as search criteria in searches for your class on the Keywords tab page.
    5. Assign your characteristics to the class via the tab page Characteristics.
    Further notes
    Further information on classes is available in this Customizing activity under Help -> Application help.
    Define Release Procedure for Purchase Orders
    In this step, you set up the release procedure for purchase orders (POs) and can link it to workflow. (Note that in this context "releasing" means "approving", or giving the "green light" to a document.)
    Requirements
    · In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
    · You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure ( Authorization Management -> Create Authorization Profiles and Assign to Users).Activities
    Here you define the following:
    ·     Release group
    ·     Release codes
    ·     Release indicator
    ·     Release strategy
    ·     Workflow
    Release group
    Create a release group for your release procedure and assign it to a class. In the process, you assign release conditions to the release procedure.
    Release codes
    Here you create the release codes you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field
    The Workflow indicator is also used to control role resolution:
    ·     "1 - Role Resolution with Group, Code and Plant (T16FW)"
    Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
    ·     "9 - Role Resolution via User Exit"
    Here you use the customer exit M06E0005 to define a role resolution of your own.
    Release indicators
    A release indicator shows the release status of a PO.
    Via the following settings, you can define the release indicators you need for your release procedure:
    ·     The Released indicator is used to specify whether messages (PO documents in output format) may be transmitted for a purchase order with this indicator.
    ·     The Changeability indicator shows the effect of changes to the PO (a change to a PO may require a new release strategy to be determined, for instance).
    ·     By means of the Value change indicator, you can specify that the release strategy is to be re-started if a PO is changed and the value of a PO item thereby increases by a certain percentage (e.g. 10%). Set the Changeability indicator to "4 - Changeable, new release in case of new strategy or value change" or "6 - Changeable, new release in case of new strategy or value change/outputted" and enter a percentage in the Value change field.
    Attention:
    The following release indicators are necessary for every release procedure:
    o     Release indicator for initial status
    If the PO is subject to a release strategy, it must normally be released before it can be transmitted to the vendor. Therefore, when a PO is created, it is assigned a release indicator that blocks it from being outputted in message form.
    The Released indicator must not be selected for this indicator.
    o     Release indicator for released status
    This indicator is assigned to the PO when it is released.
    The Released indicator must be selected for this indicator.
    Release strategies
    Create a release strategy for your release group and assign your release codes accordingly.
    ·     Release prerequisites
    With the release prerequisites , you specify the order in which the individual release points (individuals or departments) represented by the release codes may release the document.
    Example
    The following table shows release prerequisites for a strategy with four release codes.
    Code/Release prerequisite
              01     02     03     04
         01     -               
         02          -          
         03               -     
         04                    -
    In this release strategy, the codes 01, 02, 03, and 04 must successively release the purchase order.
    Read the table from left to right. For instance, the third line for release code 03: For code 03, release via code 01 and code 02 is a prerequisite. That is to say, the PO must be released via codes 01 and 02 before it can be released via code 03.
    ·     Release statuses
    Here you specify the status a PO has after certain release points have effected release.
    Specify which release indicator/status a PO is to have after having been released via a certain release code.
    ·     Classification
    In classification, you maintain the values assigned to the characteristics. Via the characteristics and their values, you specify the POs to which your release strategy is assigned.
    Maintain values (individual values or intervals) for your characteristics.
    Example
    Two characteristics and their values have been maintained in classification for release strategy 'EA':
    - Document type - 'NB - standard purchase order'
    - Total value - above $10,000
    All POs with the document type 'NB' and a total value in excess of $10 ,000 are thus subject to a release procedure with the release strategy 'EA'.
    ·     Release simulation
    The release simulation function enables you to check which status a PO will achieve with your release strategy if release is effected by a certain release point.
    Choose "Simulate release" and release the document with the desired release code by double-clicking. The system shows you which status the PO now has as a result of this release.
    Workflow
    Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.
    You can assign a processor ID either directly or indirectly:
    o     Direct processor assignment:
    Enter a user name.
    o     Indirect processor assignment:
    Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.
    Customer exit
    Customer exit M06E0005 enables you to define your own role resolution which determines the person responsible for releasing purchasing documents in workflow.
    Further notes
    Further information on how to set up a release procedure linked to workflow is available via the menu options Help -> Application Help.
    Check Release Strategies
    In this step, you can check whether the basic settings for your release strategy are complete and correct.
    Checks
    The following checks are carried out for purchasing documents:
    ·     Basic checks
    The system checks whether the necessary release groups exist in the system. For example: Whether a release group has been deleted even though an associated release strategy still exists.
    ·     Checks regarding release groups and release classes
    The system checks whether the release groups and the assigned classes have been maintained correctly. For instance, whether
    o     A class has been assigned to the release groups and whether it exists in the system
    o     Characteristics - which exist in the system and are linked to the communication structure - have been assigned to the class
    o     A customer exit must be maintained for a characteristic
    ·     Checks regarding release codes
    The system checks whether the release codes have been maintained correctly
    ·     Checks regarding release indicators
    The system checks whether the release indicators have been maintained correctly. For example: Whether release indicators exist for the statuses "Blocked" and "Released".
    ·     Checks regarding release strategies
    The system checks whether the release strategies have been maintained correctly. For example, whether:
    o     Release codes have been assigned to the release strategy
    o     The relevant release indicators have been assigned to the initial and final statuses of a release strategy
    ·     Checks regarding link to workflow
    The system checks whether the link between your release procedure and workflow has been maintained correctly. For example, whether:
    o     A processor (member of staff responsible for processing) has been assigned to a workflow-relevant release code and is defined in the organizational plan
    o     A customer exit is necessary for the role resolution
    Result
    The result of these checks is displayed in a log. Further information is available in the Customizing activity under Help -> Application Help.
    Activities
    1. Start the check by performing the Customizing activity.
    2. Check whether any error or warning messages are displayed.
    3. If necessary, correct your Customizing settings for the release procedure.
    4. Re-run the check after making corrections.
    Rewards if Helpful
    Regards
    Sanjay L

  • Error in Release procedure for PO

    Hi
    I have created a release procedure for Purchase groups and plants. But now I want to add a new Purchasing group to the same strategy. How to do this.

    Hi Garapati,
    Release strategy is configuration in customisation screen. Do not merely do assignment of object via CL20N or CL24N. Though assigning the object would work, but is better to do it in customisation.
    Go to this path: -
    SPRO>IMG>Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Order (Execute)-->Release Strategies
    Go to: Position>Identify the Group> Identify the Release Strategy code
    (How to know what is the release strategy code? In the PO where a release strategy for this value and characteristic is triggered, you can go to the Header-->Release Strategy tab, you would be able to see that the release strategy is triggered. Simply remember the release strategy code. If you already know the code, ignore this step)
    When the search is complete and located the right release strategy that you want to amend, select it and click on Details.
    Inside, go to Classification. Check that this release strategy contain the characteristic that you want to amend. You would be able to see the Characteristic "Purchasing Group" already maintained. Click on Purchasing Group line and click on "Add rows" icon below, then key in the the Purchasing Group value that you want to add.
    Hit Back, and then Save this customisation.
    Now, the PO release strategy will trigger the Purchasing Group you just added if the PO details entered matched the Purchasing Group, Plant and Document Type value that you maintained for this release strategy.
    Hope this helps.
    Rgds.

  • 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

  • Release Procedure For Contract

    Dear Gurus,
                                 I have created a release procedure for Purchase Order.Now i created a Contract , it also asking for release.I dont know y its happening??
                                Is ter any link between Po release and Contract Release??
    Plz Explain ....
    Thanks in advance...........

    Hi,
    Whatever document types you give in release procedure will undergo Approval process.
    Since you have given MK & WK, your contract has been blocked for release. Unless it is released, it cannot be used for further transactions, say creation of PO.
    Tcode to release contract is ME35K.
    Release it using your release group & release codes, Afterwhich you will be able to create PO with contract reference.
    If you donot want contract to undergo release procedure, please do not mention WK or MK in values for doc characteristics. Give the document type of PO alone. Say NB (standard PO)
    Regards,
    Divya

  • Release procedure for p.o.

    hi sapgurus,
    here is the scenario,
    i have as issue ( for P.O value only)
    1) if the value is < 2 lacks then one person  will release.
    2) if the value is > 2 lacks then 2 persons will release

    hi,
    3.4.24 Releasing Procedure for Purchase Documents
    Use
    This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
    3.4.24.1 Creation of Characteristics
    Procedure
    1. Access the activity using one of the following navigation options:
    IMG Menu Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Characteristic
    Transaction Code CT04
    2. On the Characteristic screen, make the following entries.
    3. In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
    Field name Description User action and values Note
    Select Addnl Data tab
    Table Name Table Name CEKKO
    Field Name Field Name GNETW
    Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
    Select Basic Data tab
    Description Description Total net order value
    Status Status Released
    Data Type Data type Currency format Selected by system
    Number of characters Number of characters 15
    Decimal places Decimal places 2
    Currency Currency INR
    Interval vals allowed Interval values allowed Check this tick box
    Multiple Values Multiple values allowed Select this radio button
    4. Choose Enter to complete the entries
    5. Choose Save icon or Ctrl + S to save the characteristic.
    3.4.24.2 Creation of Class
    Procedure
    1. Access the activity using one of the following navigation options:
    IMG Menu Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Class
    Transaction Code CL02
    2. On the Class screen, make the following entries:
    Field name Description User action and values Note
    Class Class PORELPROC
    Class Type Class Type 032
    Choose Create icon or white paper icon to create new class.
    Description Description Purchase Order Release Procedure
    Status Status Released
    Choose Char. Tab to input characteristic name.
    Characteristic Characteristic POVAL Created in above step
    3. Choose Enter to complete the entries
    4. Choose Save icon or Ctrl + S to save the characteristic.
    Result
    Class type 032: Class PORELPROC created.
    3.4.24.3 Configuration of Release Procedure
    Procedure
    1. Access the activity using one of the following navigation options:
    IMG Menu Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Define Release Procedure for Purchase Orders
    Transaction Code SPRO
    2. On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
    3. Choose New Entries icon and make the following entries:
    Field name Description User action and values Note
    Rel. Group Release Group 02
    Class Class Name PORELPROC Created in above step
    Description Description PO Release Procedure
    4. Choose Enter to complete the entries
    5. Choose Save icon or Ctrl + S to save the entries.
    6. Choose yellow arrow to go back to popup screen.
    7. Choose Release Codes to select.
    8. Choose New Entries icon and make the following entries:
    Field name Description User action and values Note
    Grp Release group 02 Created in above step
    Code Release Code 01
    Workflow Workflow Leave it blank
    Description Description Purchase Officer
    Grp Release group 02 Created in above step
    Code Release Code 02
    Workflow Workflow Leave it blank
    Description Description Materials Manager
    9. Choose Enter to complete the entries
    10. Choose Save icon or Ctrl + S to save the entries.
    11. Choose yellow arrow to go back to popup screen.
    12. Choose Release indicator to select.
    13. Choose New Entries icon and make the following entries:
    Field name Description User action and values Note
    Release ind. Release Indicator 1
    Released Released Leave it blank
    Chgable Changeability 4
    Value change % Change of value 10%
    Description Description Purchase Order Blocked
    Go to 2nd line and input the following values:
    Release ind. Release Indicator 2
    Released Released Select Check box
    Changeable Changeability 6
    Description Description Purchase Order Released
    14. Choose Enter to complete the entries
    15. Choose Save icon or Ctrl + S to save the entries.
    16. Choose yellow arrow to go back to popup screen.
    17. Choose Release Strategies to select.
    18. Choose New Entries icon and make the following entries:
    19. System will give new screen New Entries: Details of Added Entries
    Field name Description User action and values Note
    Release Group Release group 02
    Rel. Stategy Release Strategy S1
    Capital Items Release
    Release Code Release Code 1 01
    Release Code Release Code 2 02
    20. Choose Enter to complete the entries.
    21. Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
    22. Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
    23. Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
    24. Choose Next Screen icon or choose F8 to continue.
    25. If you want to simulate the release procedure you can choose Release Simulation icon.
    26. Choose Enter to complete the entries.
    27. To save the settings choose Save icon or Ctrl + S.
    Result
    Release procedure is saved.
    3.4.24.4 Assignment of Values to Release Procedure
    As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
    Procedure
    1. Access the activity using one of the following navigation options:
    IMG Menu Cross-Application Components  Classification System  Assignments  Assign Object to Classes
    Transaction Code CL20N
    2. On the Class screen, make the following entries:
    Field name Description User action and values Note
    Class Type Class Type 032
    Choose Enter to Assign values.
    Release group Release Group 02
    Rel. Strategy Release strategy S1
    Choose Enter.
    System will give Class name in Assignments, Double choose Class Name.
    System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
    3. Choose Enter to complete the entries
    4. Choose Save icon or Ctrl + S to save the characteristic.
    Follow these steps
    G.Ganesh Kumar

  • Release Procedure for PO not getting applied

    Dear All,
    I have created a Release procedure for PO, for the field  - Order Type. I have defined & followed all the steps i.e., Characteristic, Class, Rel. Groups, Rel. Codes, Rel. indicator & Rel. strategy.
    Then i go to CL20N and assign object to class.
    But when i create a PO & try to release it in ME29N it says 'Purchasing Doc. cannot be released"
    The same release procedure was working fine few days back.
    Kindly let me know if i have missed out some steps or someother settings need to be made.
    Regards,

    hi kedar
    I tried that, still I get the message "No suitable Purchasing Documents found"
    any settings to be checked in characteristics ?
    Hey, and one more thing... everytime I exceute ME28 or ME29n, and later when i try to open Class...... i get an error message "Class type 032: Class <class name> being processed by <username>"
    Then i have to go and delete in the locked entries, only then I can see the Class.
    Rgds,

  • Release Procedure for PO in two currencies

    Hi
    I have to create PO release procedure for PO for Two Currencies based on the below characteristics
    1.Company code
    2.Document type
    3.Purchasing group
    4.Net order value in both INR and USD
    Can Any body help me
    I tried but the system is not triggering release procedure

    Hi,
    Maintain class as follows
    CEKKO_GNETW=Total net order value,Data type-CURR,Number of chars-15,Decimal places-2,Unit-INR
    If you have maintain exchange rate in PO  under delivery/Invoice tab then system will auto triggering release strategy as per maintain value in release strategy,
    Normally document currency is converted into company code currency and company code currency is converted into characteristic currency
    If your company code currency is INR , then any foreign currency PO shall be appropriately converted internally by the system(based on the currency converstion setting ) and this is applicable on which the specific release strategy will be applied.
    Please also refer SAP note 493900 for system behaviour.
    Refer Question no.13 in SAP note-493900
    How is the currency converted?
    Answer :
    The header currency is converted to local currency (company code currency) and then the local currency is converted to the characteristic currency.
    Regards,
    Sandesh Sawant

  • PR release procedure for material types

    Hi all,
    I have a question, I created new release procedure for combination :
    1. NB pur.requsition, purchasing group + material type (let sey roh.. etc)
    2. YNB pur.requsition, purchasing groups + material type (ZSTE-001, ZSTE-002, ZSTE-003).
    - 3 characteristcs for pur.groups, doc.type and material type.
    - 1 class
    - 2 release groups (E1 and P1)
    - For release group P1, In rel.strategy in classification I entered values for pur. requisition (NB), purchasing groups (001,002, 003 ect) and material types (ZUSL-001.. ect)
    - For release group E1, in rel. strategy in classification entered values
    values for pur. requisition (YNB), purchasing groups (001,002, 003 ect) and material types (ZSTE-001, ZSTE-002, ZSTE-003)
    So, problem is that if I enter pur.requisition YNB and material type ZSTE-001, needs release; if I add item with material type ZUSL-001, there is no release.
    How can I restrict the values so that is giving error if by mistake is entered between material types ZSTE-001, ZSTE-002, ZSTE-003 material type ZUSL-001 in document type YNB, which is not allowed to be entered?
    Thanks in advance,
    Anchi

    Hello
    In PR you can set up this release strategy without classification release strategy.
    w/o classification strategy you can define the release line item wise. so you can give diiff materual group you can enter with line item wise.
    Laxman

  • With classification release procedure for PO

    Dear Experts ,
    here one issue is with classification release procedure for PO
    when I create characteristics
    in Additional data
    table name :-- Cekko field name  :-- match code
    enter
    click all sec charars then which block I select to go next screen
    and fill name is right or ?
    please help me

    hi,
    in additional data field you have to give the field name of characteristic you are maintaining. like if you want to maintain characteristic as document type of the PO then we have to give the field name for document type mentioned in table CEKKO i.e. BSART.
    then you have to do the value assignment. here you have to tick the check box for "NOT READY FOR INPUT".
    JASH

  • Release procedure for ASSET

    Hi SAP guru
    I am having the requirement for release procedure as follows
    Purchase order with  Asset (Item category)   - Value  Up to 50,000/-  will be approved by GM
                                  Asset (Item category)   - Value  more than 50,000/-  will be approved by Chairman.
    Purchase order other than ASSET
                                                        Value  Up to 100,000/-  will be approved by GM
                                                        more than 100,000/-  will be approved by  Chairman.
    I checked in CEKKO, the field KNTTP - Account Assignment Category component is not available.
    Could you please tell me how to solve this issue?
    Good suggestion will be rewarded with full points.
    Thanks in advance
    Anand

    Hello Anand:
    The release strategy for PO only contain fields on the purchase order header (EKKO) and the account assignment is at item level (EKPO), however you can add the account assignment as customer field on structure CEKKO (CEKKOZZ structure) and fill the information on this field with the user exit M06E0004 (transactions SMOD, CMOD)
    Keep in mind that the CEKKO structure has the value of all the purchase order (CEKKO-GNETW), not item by item. It means that you could not check on the release strategy the value of all the assets included in the purchase order.
    Additionally check if there are cases in your installation where a purchase orders could contain several items for more that one account assignment.
    I hope this help, if you have any question please let me know it.
    Best regards,
    Jose Luis

Maybe you are looking for

  • How to set fire action event for particular rows in a table

    HI All, I have a requirement in which I want to set fire action event for particular rows in a table based on some condition. The table has columns like fullname,employee id etc. So i want to set fire action event for particulars rows only which will

  • Because iTunes wasn't working, I restored my iPhone by resetting it, and it's stuck in DFU. What do?

    Due to my phone not syncing, I decided to look up how to restore an iPhone without iTunes, and found that if you reset it on the phone, that'll restore it. I did that, and now it won't go past DFU or the apple logo. I'm deathly confused. What do?

  • Connecting to AS 400 via 5250 Emulator Session

    Hi, I am trying to connect to an as400 server via the sgd 5250 enhancement package. I created an testobject where i specified the hostname of the as 400 server and set the port to 23/tcp. Now I tried to start the application as webtop or independent

  • How to load the text to Masster data

    Hi Experts, I am not able to load the  text for master data. We have postal code(0POSTALCODE)  Master data InfoObject , in this we have field called Prizm, it's 'Z' field (ZPRIZM). I would like to load the description for this filed(text), for exampl

  • Regarding Generated Inspection Points

    Hi Gurus, I am doing in process inspection(Type 03) & using inspection points 150(Generated inspection points). In operation details i have maintained time related & given time factor as 1 hr.When i am releasing order inspection lot is generated but