Release Status is different in CL24N and table KSSK

Hello All,
For a Release strategy in the transaction code CL24N i see it is in status 3 - incomplete.
However if i go to table KSSK, i see it in status 5.
Can you please explain, why in table KSSK, it is showin as status 5 and what does status 5 mean?
Regards,
Neetha

Hi,
It's showing properly, Check it once agian with correct Release strategy in CL24N & KSSK table.
Regards
Ravi Shankar.

Similar Messages

  • Waht are differances etweent structures and tables

    plz answer this questions

    Hi,
    Basiclly, a structure does not have data and table does. A structure is a set of fields, and you can access that fields in your program using:
    structure-field1 = value1.
    structure-fiels2 = value2.
    structure-fieldn = valuen.
    So, you can not access an structure by SE16, it's not make sense. You can view the definitions of structure using SE11 transaction.
    Also, structures cannot store group of records But it can able to hold a SINGLE record.
    Whereas,
    SAP table is a place where the data can be stored which uses any SAP structure.
    watch this link from sap help also.
    <a href="http://help.sap.com/saphelp_47x200/helpdata/en/ac/3547360f2ea61fe10000009b38f839/frameset.">http://help.sap.com/saphelp_47x200/helpdata/en/ac/3547360f2ea61fe10000009b38f839/frameset.</a>
    Regards,
    Gaurav
    <b>Reward points if helpful</b>

  • EXIT_SAPLEBND_002 of M06E0004 User exit to Reset Release Status if PO

    Hi All,
    I have implemented a user-exit EXIT_SAPLEBND_002 of M06E0004, as advised, which can reset/cancel the release status of a certain PO document when a certain field has been changed aside from the quantity and price fields.
    I would just like to ask if how woud the exit know if something in the document has been changed by the user if he goes to me22n? Basically, the requirement was that everytime a user changes the partially released PO in the header data and other fields aside from price and quantity, the release status should be reset to start all over again.
    I have this code, but this should only be ran if a partially released PO has been changed in most of its fields (header/item).
    DATA: wa_ekpo TYPE ekpo,
          wa_bekpo TYPE ekpo,
          lv_frgke TYPE ekko-frgke,
          tx_ekko TYPE char200,
          tx_ekbe TYPE char200,
          lv_frgzu TYPE ekko-frgzu.
    FIELD-SYMBOLS: <fs_ekko>  TYPE ekko.
    tx_ekko = '(SAPLMEPO)ekko'.
    ASSIGN (tx_ekko) TO <fs_ekko>.
    If <fs_ekko>-frgke = '1' AND
       <fs_ekko>-frgzu IS NOT INITIAL.
    <fs_ekko>-frgke = '2'.
    <fs_ekko>-frgzu = space.
    ENDIF.
    UNASSIGN <fs_ekko>.
    Kindly send some recommendations.
    Regards,
    RE

    Add this code in user exit exit_saplbend_002 .
    Code=> This code use to change release status on PO amount decrease and increase.
    ================================
    **** Start of changes for Release status change on PO amount decrease .
    E_CEKKO = I_CEKKO .
    DATA : wa_bekpo type BEKPO,
           wa_ekpo TYPE ekpo,
           WA_CEKKO TYPE CEKKO,
           w_reset(1) TYPE c VALUE 'X'.
    if sy-tcode eq 'ME22N' OR sy-tcode eq 'ME22'.
    WA_CEKKO = I_CEKKO .
    IMPORT WA_CEKKO = WA_CEKKO FROM MEMORY ID 'ZREL_COST'.
    IF SY-SUBRC NE 0.
      EXPORT WA_CEKKO = WA_CEKKO TO MEMORY ID 'ZREL_COST'.
    ENDIF.
    ENDIF.
    if ( sy-tcode eq 'ME22N' OR sy-tcode eq 'ME22' )
      and sy-ucomm eq 'MESAVE' or sy-ucomm eq 'MECHECKDOC'.
    *Import/Export the origninal values.
    *Check if the limit is passed.
    LOOP AT it_bekpo INTO wa_bekpo .
    SELECT SINGLE NETWR FROM ekpo INTO wa_ekpo-netwr WHERE ebeln eq wa_bekpo-ebeln and ebelp eq wa_bekpo-ebelp.
    IF SY-SUBRC EQ 0.
    IF wa_bekpo-netwr < wa_ekpo-netwr.
        w_reset = 'X'.
      endif.
    ENDIF.
    ENDLOOP.
    *IF limit passed - reset the value to high limit beyond tolerance.
    IF w_reset = 'X'.
    E_CEKKO-GNETW = WA_CEKKO-GNETW + 1000000.
    ENDIF.
    endif.
    **** End of changes for Release status change on PO amount decrease .

  • 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

  • Field and Table for PGI status updation

    Hi All,
    I want to know in which field and table the PGI status will get updated.
    i.e. once we do the PGI for a delivery in which table will this PGI status gets updated.
    Thanks in advance for help.
    Harini

    Hi Harini,
    In Table VBUK you 3 different status related fields for  sales documents.
    Over all status field name GBSTK ( here it gives the total status of praticular sales document) here you see options
    A  Not yet processed      ( This means its complete open)
    B  Partially processed     ( This means the sales doc is partially processed)
    C  Completely processed  ( This means the sales doc is completly processed)
    Delivery status  and over all delivery status field name LFSTK and LFGSK respectively, these 2 fields will be same always ( here it gives the total status of praticular sales document) here you see options
    A  Not yet processed      ( This means its completly  open)
    B  Partially processed     ( This means the delivery doc is partially processed)
    C  Completely processed  ( This means the delivery doc is completly processed)
    So overall status can be  different then delivery or overall delivery status.
    If sales document has 100 quantity for 1 material, if delivery is done for 50 quantity.
    Then over all status field name GBSTK will be B  Partially processed and delivery and overall delivery will be C  Completely processed  .
    Regards
    vK

  • 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

  • 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

  • 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

  • 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

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

  • 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

  • Purchase Order released date field and table name

    Hi,
    Please tell me the  Purchase Order released date field and table name.
    Regards
    Deepak

    Hi,
    Table : EKKO.
    Fields : FRGKE,FRGZU.
    You can get release date of PO from CDHDR  table.
    give object value as your po number and check.dont forget to give leading zeros.
    The udate will be date field and transaction will be me29n for relaesed po.

  • Relation between different GUID and tables in RPM

    Hi All,
    can you tell me the relation between different GUID and tables in RPM. Many thanks.
    Regards,
    J B

    Hi Deepesh,
    Try the foll. join :
        SELECT  fragment_guid  INTO  (some internal Table)
             FROM  comm_pr_frg_rod
             WHERE  product_guid  = (your product guid list)
    This should give u a complete match of the products.
    Hope this helps.
    Regards,
    Raviraj

  • Execute BAPI for different input values and dispaly data in a table

    Hi all,
    I have a specific problem about executing BAPI multiple times for different input values and didplay result in a table.
    I am using the code similar to the following logic.
    Bapi_Mydata_Input in = new Bapi_Mydata_Input();
    wdContext.nodeBapi_Mydata_Input().bind(in);
    String in = wdContext.currentperdataElement.getnumber();
    in.setDestination_From(10)
    wdThis.wdGetMydataComponentController().executeBapi_Mydata_Input();
    in.setDestination_From(20)
    wdThis.wdGetMydataComponentController().executeBapi_Mydata_Input();
    in.setDestination_From(30)
    wdThis.wdGetMydataComponentController().executeBapi_Mydata_Input();
    And I want to display the data in a single table. I want the result in a table for Bapi execution based on input parameters passed 10,20 30.
    But I am getting the table data only for the input parameter 30.I mean its actually display the data in table only for the last input parameter.
    So May I ask you all if you know the solution for this problem.PLease advise me with some tips .or sample code is very much appreciated.I promise to award points to the right answer/nice advises.
    Regards
    Maruti
    Thank you in advance.

    Maruti,
    It seems that WDCopyService replaces content of node, rather then adds to content.
    Try this:
    Bapi_Persdata_Getdetailedlist_Input frelan_in = new Bapi_Persdata_Getdetailedlist_Input();
    wdContext.nodeBapi_Persdata_Getdetailedlist_Input().bind(frelan_in);
    final Collection personalData = new ArrayList();
    String fr1 = wdContext.currentE_Lfa1Element().getZzpernr1();
    frelan_in.setEmployeenumber(fr1);
    wdThis.wdGetFreLanReEngCompController().executeBapi_Persdata_Getdetailedlist_Input();
    WDCopyService.copyElements(wdContext.nodePersonaldata(), wdContext.nodeNewPersonaldata());
    for (int i = 0, c = wdContext.nodePersonaldata().size(); i < c; i++)
      personalData.add( wdContext.nodePersonaldata().getElementAt(i).model() );
    String fr2=wdContext.currentE_Lfa1Element().getZzpernr2();
    frelan_in.setEmployeenumber(fr2);
    wdThis.wdGetFreLanReEngCompController().executeBapi_Persdata_Getdetailedlist_Input();
    WDCopyService.copyElements(wdContext.nodePersonaldata(), wdContext.nodeNewPersonaldata());
    for (int i = 0, c = wdContext.nodePersonaldata().size(); i < c; i++)
      personalData.add( wdContext.nodePersonaldata().getElementAt(i).model() );
    wdContext.nodeNewPersonalData().bind( personalData );
    Valery Silaev
    EPAM Systems
    http://www.NetWeaverTeam.com

  • Java transports across different SPS, EHP and release

    Hi All,
    During an SPS/EHP upgrade, there is generally a transport freeze in the development landscape from DEV ->QA->PRD. This due to the incompatibility between the systems. SAP Note explaining the same is 1090842.
    I understand that same is true for the Java developments as well. As the SC imported into track are specific to release and SP levels of the WAS. These would have to be adjusted and re-build, (after SPS/EHP upgrade of WAS) so that it refers to the new versions. But these new builds are possible in NWDI, which has not been updated. But these releases cannot be transported to QA before QA is also upgraded to same SPS/EHP as for DEV.
    Please let me know if my understanding is correct. If yes, then is there a similar SAP Note/documentation available as for ABAP one explaining the same?
    Appreciate your inputs on the same.
    Thanks and Regards,
    Arundeep Singh

    Hi Mark,
    Thanks for your reply. Your reply seems to talk more on the different release of NWDI and runtime systems.
    My query is not about the relation of NWDI and Runtime Java systems compatibility. I want to know the restrictions on transports in which the Runtime system landscape, DEV->QA->PRD, when an SPS/EHP on release is being upgraded on runtime systems. The scenario where standard SAP developments has been modified is clear and there is good enough documentation available [here|https://cw.sdn.sap.com/cw/docs/DOC-17604]. Let me try to explain the case again.
    1. Only the Runtime systems landscape being upgraded. NWDI remains the same.
    2. No SAP standard development has been modified.
    3. There is only custom development, but it has build and/or runtime dependency on standard SAP SWCV. e.g. dependency on JTECH 7.00
    4. Now DEV runtime Java system is upgraded, lets say to EHP1. That means the JTECH will change from JTECH 7.00 to JTECH 7.01 in Runtime DEV system.
    5. Now, I beleive that custom development/ SLD configuration should be adjusted so that custom development now depends on JTECH 7.01 and not on JTECH 7.00.
    6. If this custom development is not modified and transported to QA system, it may not work as the JTECH version is different in DEV and QA.
    7. There could be another option at point 5. It may be chosen not to change the dependency to new JTECH 7.01. but then it may not build or run properly as JTECH in DEV is now JTECH 7.01.
    Similar case would be there in case of SPS as well. It is just in case of SPS it is more subtle. The SLD dependencies will remain same. But I wonder if any library/interfaces gets updated/deprecated then the applications may not run as expected. I understand the code is generally downward compatible, but not always.
    This is why, I was checking if there is some official document explaining such scenarios. I am still searching. If I came across something i will provide the links.
    Thanks and Regards,
    Arundeep Singh
    PS: I am not a Java developer. My judgement is purely based on the general logic.

Maybe you are looking for