Activate Release Status in condition table

HI,
Some has created a pricing condition table and it is being used since 5 years.
Now client had a requirement where he wants release mechanism for any new condition records created.
For this SAP provided a standard functionality of release status.
In our case release status button is not checked while creation of condition table.
Now how to reactivate the release button in the condition table.
Regards,

Hi Uday
We can't activate release function in old tables just like that. You have to create new table with same fields but with release status activate. For copying old condition records in this new table you can use
SD_MOVE_A004_TO_A304 report. As you can see with its name this report is for tables 004 and 304. If you want to copy records from 004 to 304 you can use this report. In your case you must have some other tables but if you show this report to your ABAPer he would be able to generate a new report using your tables.
You can take a look on following document provided by SAP and see the conversion section at the end of this document.
http://help.sap.com/saphelp_46c/helpdata/en/9b/3b1a2bc925d311b60f0060b03c2bff/content.htm
Thank$

Similar Messages

  • Use of Release Procedure  / status in Condition Table

    What is the purpose of Release Procedure / Release status when creating condition tables ?

    Hi
    Release procedures are used in condition tables to control whether the condition types for these condition tables have to be read during pricing condition determination or not.
    If the condition table status is released then only the condition types will be read during pricing determination. If the status is not released, then they can be used for information purposes or for simulation of pricing.
    The release status is controlled by processing status too, which can be seen in condition record creation screen.
    So in crux, the processing status with Release status help in simulation of pricing, blockign the condition records from being read during pricing etc.
    For more information an F1 help on the following path will give you some more information.
    SPROSD-BF-PRICING-DEFINE PROCESSING STATUS----Here read the documentation meant for this link. You will get some more clarity on this.
    Rwd point if it helps.
    Reward points if it helps.

  • Process Status & Release Status for Condition Record

    Hi Gurus,
    Pls help me out in the the following scenario.
    I want to activate Authorization level check for Condition records.
    For example, Product price PR00 is being entered by first level.
    After verification done by second level only, that condition record to be used for sales order processing.
    I have gone through Process status & Release Status. But not getting full clarity on this.
    Rgds,
    Senni.B

    Hi,
    Please go through the following information.
    [Relase Procedure for Condition Record|http://help.sap.com/saphelp_47x200/helpdata/en/a4/af9e78e69611d2ace10000e8a5bd28/frameset.htm]
    [Release Procedure for PR|http://www.sap123.com/showthread.php?t=59]
    Reward if helpful.
    Thanks and Regards,
    Naveen Dasari

  • Release status for condition records

    Hello,
    When ever a user changes the price in the condition record, I want the price to be in blocked status initially. Sales document should only pick tht price when it is release by the concerned person.
    Could you tell me how is the authorization given to some users based on the processing status.
    Thanks and Regards,
    Pavan P.

    I tried to make the Processing status as blank and tried to save it and assigned the release status "Blocked". This doesn't seem to work. Any other ideas?

  • Condition Tables with Release status

    When we create condition tables, we have the option of creating them with release status or without release status. What is the difference? What is release status?
    Thanks,
    Venkat

    hi,
    The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
    Release status has the following characteristics:
    no entry: released
    A: blocked
    B: released for price simulation
    C: released for price simulation and planning
    The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
    Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
    When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
    A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
    The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
    If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
    The release status of conditions in an agreement can only be changed, if
    the condition record has release status in the key
    the agreement has the release status released
    Otherwise the condition record always has the release status of the agreement.
    The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
    If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
    The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
    source : Library.
    regards

  • Hai release status

    what is this release status in the condition table creation what does it indicate
    In pricing procedure det we found condition type  field what is the purpose of this
    thanks

    Hi Kishore,
    The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
    Release status has the following characteristics:
    • no entry: released
    • A: blocked
    • B: released for price simulation
    • C: released for price simulation and planning
    The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
    Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
    When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
    A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
    The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
    If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
    The release status of conditions in an agreement can only be changed, if
    • the condition record has release status in the key
    • the agreement has the release status released
    Otherwise the condition record always has the release status of the agreement.
    The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
    If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
    The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
    In pricing, only those conditions are used, those have the release status 'released'.
    Reward points if it helpful
    Cheers,
    Govind.

  • Release strategy in Condition records

    Hello
    We have a requirement where we can maintain price rates for condition type using VK11 and these rates are audited and released by audit team then only Sales team can use that rates in Sales order.
    Regards,
    Nimit

    Hi,
    You can use release and processing status without agreement.
    You have to create processing status in customizing and assign a release status to the processing status.
    For example, create 2 processing status, 1 = For approval with a release status blocked and one processing status Release with a release status = released.
    Your condition table must be marked with the release status flag.
    Then when you will create condition record then you will be able to enter a PROCESSING Status for your condition record. (release status will remain grey) The release status will be automatically assigned : it will take the release status assigned to your processing status.
    Hope it helps !
    I have a question about the processing status : do you know how to MASS change it on condition records ?
    Myriam.

  • Processing and Released Status when we create a new Condition table

    Hi all
    I created a new condition table in M/03, and assigned one field to it, Generated and saved. Then added the condition table in the access sequence. There appeared two more lines below the field that i have assigned. One is Processing status and the other is released status, both are having green lights. what are these and what is its impact.
    inputs will be highly appreciated
    thanks

    I myself could find the answer

  • What is the purpose of the release status in creating condition table

    hi gurus,
    can you please tell me the purpose of the release status and validity date in creating condition table for pricing?
    thanks,
    Paul

    Dear John
    The release status controls in which scenarios the condition records are found.
    If the status is set at 'B', for example, then the corresponding records  are taken into account during a pricing simulation, but are not used in current documents.
    The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status.
    thanks
    G. Lakshmipathi

  • ME21N - in which table saved the release status for specific release code ?

    and for the specific po number.

    Hi
    You will find all Release codes in T16FS
    Release procedures are used in condition tables to control whether the condition types for these condition tables have to be read during pricing condition determination or not.
    If the condition table status is released then only the condition types will be read during pricing determination. If the status is not released, then they can be used for information purposes or for simulation of pricing.
    The release status is controlled by processing status too, which can be seen in condition record creation screen.
    So in crux, the processing status with Release status help in simulation of pricing, blockign the condition records from being read during pricing etc.
    For more information an F1 help on the following path will give you some more information.
    SPROSD-BF-PRICING-DEFINE PROCESSING STATUS----Here read the documentation meant for this link. You will get some more clarity on this.
    <b>Reward points</b>
    Regards

  • Table for PO release status

    hi,
    im developing PO Smartform.in that i have to display PO release status ie; whether it is released or not released(ME22N----->click on HEADER--
    >click on RELEASE STRATEGY).from which tables i can fetch this data .please help.

    Hi
    Take the fields from EKKO that are related to PO release startegy
    FRGGR
    <b>FRGSX</b>
    FRGKE
    FRGZU
    and check the tables
    T16FG
    <b>T16FS</b>
    T16FB
    for the release codes
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • How to maintain SAP Release status in table COTPL

    Hi All,
    We have upgraded our system from ECC EHP4 TO ECC EHP 5. Now our SAP Release is 702 but in table COTPL
    still the SAP Release status is 701 becuase of which there is error in some of our sap jobs.
    Request you all to help us. How we can maintained SAP Release in table COTPL?
    Thanks

    Hi,
    You can try using priority field in the rule. Please check this.
    Priority for Responsibilities
    If you are using responsibilities for role resolution in Workflow, you can provide individual responsibilities with priorities.
    Example: There are various responsibilities for a standard role for processing orders, grouped, for example according to order value (one responsibility for orders up to a certain value, another for orders with a greater order value).
    Assuming that orders for a particular customer are always to be processed with the same responsibility (and therefore by the same agent), you can access it via another responsibility with a higher priority that contains the customer name as the only criterion. The responsibility (-ies) with lower priority, and therefore the order value, is then no longer taken into account during agent determination.
    Use only numeric values here, and note that, logically, the responsibility with the highest numberic value in this field has the highest priority.
    Procedure
    1. Sequence Priority of Objects
    In Create mode, assign a priority to the objects you wish to rank.
    To do so, assign an alphanumeric value (1, 2, 3... or A, B, C...) to each object.
    In Change mode, overwrite the value in the field.
    2. Priority When Defining Evaluation Paths
    In the Priority field, enter the priority or priorities for objects that should be considered in evaluation paths. Enter "*" if you want to have no restriction.
    3. Priority for Responsibilities
    Maintain the priority directly in the detail screen for the responsibility or in the overview screen for the responsibilities for the rule. Note that you must use numeric values here. On the overview screen, the system sorts the responsibilities in descending order of priority.
    Hope this helps.
    Feel free to revert back.
    -=-Ragu

  • Processing status & release status

    Hi,
    There is a configuration which says: DEFINE processing status.
      Can somebody expalin in details the use of it  .
    In short i would like to know about the processing status & release status.
    thanks,
    prithika

    Prithika,
    Processing Status and Release status work closely both are interlinked. you can define processing status and assign it to condition record. Release status controls in which scenarios the condition record are found.
    The release status can only be maintained directly for agreements. For condition records, this is done via the processing status.
    Configuration for Processing status can carried out using
    IMG --> SD --> Basic Functions --> Pricing --> Define Processing status
    Here you can create processing status and Release status will be assigned according to the scenarios if it were "B",  "Release for pricing simulation" will be assigned to the processing status.
    Using Tcode SM30, choose Table/View: "/BEV3/CHA_KOND".
    Activate Enter Conditions Indicator
    Click maintain and use the options provided.
    Regards
    Sathya

  • Can we change Condition Tables

    Dear Experts,
    can you please tell me can we change condition tables for SD example 017/018?
    T code for this is M/04
    Requirement is now i need to check the checkbox With Release Status..
    Can anybody help me?
    Sachin
    Edited by: Sachin Bidkar on Aug 12, 2011 8:44 AM

    Hi Max,
    Thanks for the reply.
    Actually my requirement is to change processing status through ME12 for purchasing info records
    And My query is suppose i add this field in T681E, then will it allow to change the processing status in ME11/12?
    Please guide me.
    Thanks & Regards,
    Sachin Bidkar
    Edited by: Sachin Bidkar on Sep 23, 2011 2:36 PM

  • Add fields in fieldctlg in Create condition table in SPRO

    Hi Experts,
    How can we add more fields in fieldCatlg table which appears in 'Create Condition Table' in Sales Distribution head in SPRO.
    Please Suggest.
    Rajiv Ranjan

    Hi Rajiv
    Please go through this extract from documentation:
    Creating New Data Fields in a Communication Structure
    Data fields are created in the Data Dictionary. You create data elements and fields in the Data Dictionary as well as integrate them in the relevant structures. Use following check list when you create new data fields:
    1. Check whether an identical data field already exists in the standard system
    If you want to use the order reason (AUGRU) for pricing, for example,
    the data element already exists.
    If you want to use parts of the product hierarchy, for example, you must create a new data element (e.g. ZZPRODH1).
    Remember that new data fields must begin with the letter "ZZ" or "YY" because SAP has selected this name convention to protect modifications of the customer during a release changeover. Create a new domain for the new data element.
    If you want to use a new partner function, such as a selling agent (Z1) you have to create a new partner function (Z1) and a new data element (ZZVRTZ1) in Customizing.
    2. Using the source tables, check wether the field is used at header or at item level, which determines the structure in which the field is included. The source tables are listed in the section "Supplying Fields Within the Communication Structure and Using Them in Condition Tables" below.
    The order reason, for example, is included in table VBAK, the product hierarchy in table VBAP.
    3. Integrate the field in the appropriate communication structure by means of an INCLUDE.
    For pricing, for example, you include header fields in KOMKAZ, item fields in KOMPAZ: For the field name enter the field description new fields and make sure that they begin with ZZ or YY. For example, enter ZZAUGRU, ZZPRODH, and ZZVRTZ1 and assign them to the SAP data element AUGRU, or the new data elements you have just created ZZPRODH1 and ZZVRTZ1.
    The description of the individual functions will inform you about the structures into which the fields must be integrated.
    4. Activate the structure.
    5. Include a new field in table T681 and allocate it to the application in which is to be used.
    Example
    A new field for pricing, has the allocation A, V, 001.
    When you have succesfully added the new fields in the communication structure, you will be able to find the same in FIELD CATALOG under the acess squences definition. Please check the same...
    Regards
    Eswar

Maybe you are looking for