Deleting wrong values

hi when i click mt delete button it delete wrong information or values,it does not delete the value from the table it goes and delete value from my forms i drag and drop the correct delete button,am in jdeveloper 11.1.1.6.0
my button is
<af:commandButton actionListener="#{bindings.Delete1.execute}"
                                        text="Remove Member"
                                        id="cb8" immediate="true"/>

hi this is what i have done
<af:commandButton actionListener="#{bindings.Delete1.execute}"
                                        text="Delete"
                                        id="cb10">
                        <af:setActionListener from="#{true}"
                                              to="#{pageFlowScope.addMember.deleteAction}"/>
                      </af:commandButton>
    private boolean deleteAction = false;
    private boolean EditAction = false;
    private boolean createAction = false;
    private ViewRowImpl selectedJobs;
    public void setDeleteAction(boolean deleteAction) {
        this.deleteAction = deleteAction;
    public boolean isDeleteAction() {
        OIDOperations   oIDOperations= new  OIDOperations();
        Map<Object,String> mp=new HashMap<Object, String>();
        mp.put(getusrname(),getusrname());
        oIDOperations.dropUsrRole(getorgname(), mp);
        System.out.println("deleted user" +mp);
        return deleteAction;
    public void setEditAction(boolean EditAction) {
        this.EditAction = EditAction;
    public boolean isEditAction() {
        FacesContext ctx = FacesContext.getCurrentInstance();
        ExpressionFactory ef = ctx.getApplication().getExpressionFactory();
        ValueExpression ve = ef.createValueExpression(ctx.getELContext(), "#{row.Username}",String.class);
        //ValueExpression ve1 = ef.createValueExpression(ctx.getELContext(), "#{row.jobId}",String.class);
        String Username  = (String)ve.getValue(ctx.getELContext());
        if(this.getSelectedJobs() != null){
            this.EditAction=getSelectedJobs().getAttribute("Username").equals(Username);
        return EditAction;
    public void setCreateAction(boolean createAction) {
        this.createAction = createAction;
    public boolean isCreateAction() {
        return createAction;
    public void setSelectedJobs(ViewRowImpl newselectedJobs) {
        this.selectedJobs = newselectedJobs;
        if(this.selectedJobs != null){
            this.EditAction = true;
        }else{
            this.EditAction = false;
            this.createAction = false;
            this.deleteAction = false;
    public ViewRowImpl getSelectedJobs() {
        return selectedJobs;
    }

Similar Messages

  • How to delete the values from TKOMV at runtime after creating PO

    Hi,
      How to delete the values from TKOMV at runtime after creating PO from IDOC. I am creating PO through IDOC, subsequently need to create Sales order and again need to create 2nd PO with reference of Purchase Requestion(created with sales order). At the time creation of 2nd PO the Header conditions are appearing twice and net price value is appearing wrong.
    Thanks in advance.

    Hi Padma
    Can you do this activity once the company code is in to production. I guess you can not do this activity, if the company code is already in to live. Setting or resetting of the recon accounts will hinder the previous actitivity. Infact resetting of the company code is also not a good option.
    Any how, thanks for the inputs. Please let me know whether i can do this activity only at the subledger level which will not impact other modules. The one solution i can figured out is , reverse all the transactions for the corresponding asset in the year of takeover and pass the entries again in the same year correctly which will have effect in Subledger and also in general ledger. But the business people will not allow this, since for a big client it will require lot of authorizations and approvals. Infact the vendor also, is cleared. So we have to reverse the cleared documents as well which is again a task and require approvals as well.
    Thanks and regards
    Seshu.

  • KEPM....Delete plan values..

    Hi Experts-
    Here i am facing on eissue pls suggest....
    In KEPM i did planning for 2011, that is updated with wrong values and with wrong combination......
    I have deleted all steps in KEPM, but still i am getting those values in KE30 report....pls guide me how to delete plan values...
    Pls suggest how to delete those values and what steps need to take in planning?
    Thanks
    Chandu

    Hi Reddy Anna
    You can use transaction KE1C in order to delete planning data.
    But transaction KE1C does not phyically delete entries made in table CE2xxxx. The method used in this situation is the reversal method (the line item is reversed out of the table by posting a negative line item).
    If you want to delete these line items totally then I would suggest that you use the archiving transaction SARA. This will reduce the table size.
    You also have a delete option in KEPM but this is normally for large volume of data and you can check if it is useful in your case.
    You could also use KE13N to post the delta to edit/correct the entries. For example for customer A and product B you have revenue of 1000 (but it should be 900). In that case you can post a line item of -100 so that the result is 900.
    You can see which option is most suitable for you
    br, Ajay M

  • ALV grid abort processing, if wrong value

    Hello,
    i've a editable alv grid.
    Is it possible to abort at event data_changed/data_changed_finished, if an value is wrong (f.e. to high < 500), and write the old value back.
    Best regards,
    TomSd

    Hello Thomas
    The sample report <b>ZUS_SDN_ALVGRID_EDITABLE_10</b> provides a possible (perhaps not the most elegant) solution for your problem.
    *& Report  ZUS_SDN_ALVGRID_EDITABLE_10
    *& Description: Reset false values entered in editable ALV list
    *&              to original values
    *& Example:     Column SORT_KEY allows values from '000'-'150'
    *               -> reset if value > '010'
    *& Thread: ALV grid abort processing, if wrong value
    *& Link: https:||<a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="669430"></a>
    REPORT  zus_sdn_alvgrid_editable_10.
    TYPE-POOLS: abap.
    INCLUDE <icon>.  " NOTE: replace by TYPE-POOLS: icon. on >= 6.20
    DATA:
      gd_repid         TYPE syrepid,
      gd_okcode        TYPE sy-ucomm,
      gs_layout        TYPE lvc_s_layo,
      gt_fcat          TYPE lvc_t_fcat,
      go_docking       TYPE REF TO cl_gui_docking_container,
      go_grid          TYPE REF TO cl_gui_alv_grid.
    TYPES: BEGIN OF ty_s_outtab.
    INCLUDE TYPE knb1.
    TYPES: END OF ty_s_outtab.
    TYPES: ty_t_outtab    TYPE STANDARD TABLE OF ty_s_outtab
                          WITH DEFAULT KEY.
    DATA:
      gt_outtab        TYPE ty_t_outtab,
      gt_outtab_pbo    TYPE ty_t_outtab.
    *       CLASS lcl_eventhandler DEFINITION
    CLASS lcl_eventhandler DEFINITION.
      PUBLIC SECTION.
        CLASS-DATA:
          mo_data_changed    TYPE REF TO cl_alv_changed_data_protocol.
        CLASS-METHODS:
          handle_data_changed
            FOR EVENT data_changed OF cl_gui_alv_grid
            IMPORTING
              er_data_changed
              e_onf4
              e_onf4_before
              e_onf4_after
              e_ucomm
              sender,
          handle_data_changed_finished
            FOR EVENT data_changed_finished OF cl_gui_alv_grid
            IMPORTING
              e_modified
              et_good_cells,
          handle_user_command
            FOR EVENT user_command OF cl_gui_alv_grid
            IMPORTING
              e_ucomm,
          handle_toolbar
            FOR EVENT toolbar OF cl_gui_alv_grid
            IMPORTING
              e_object
              e_interactive.
    ENDCLASS.                    "lcl_eventhandler DEFINITION
    *       CLASS lcl_eventhandler IMPLEMENTATION
    CLASS lcl_eventhandler IMPLEMENTATION.
      METHOD handle_data_changed.
    *   define local data
        DATA:
          ld_idx     TYPE i,
          ls_cell    TYPE lvc_s_modi,
          ls_msg     TYPE symsg.
        FIELD-SYMBOLS:
          <lt_outtab>  TYPE ty_t_outtab,
          <ls_outtab>  TYPE ty_s_outtab.
        ASSIGN er_data_changed->mp_mod_rows->* TO <lt_outtab>.
        LOOP AT er_data_changed->mt_mod_cells INTO ls_cell
                WHERE ( fieldname = 'ZUAWA' ).
          ld_idx = syst-tabix.
          IF ( ls_cell-value <= '010' ).
            READ TABLE <lt_outtab> ASSIGNING <ls_outtab> INDEX ld_idx.
            MODIFY gt_outtab FROM <ls_outtab> INDEX ls_cell-row_id. " !!!
          ELSE.
            CLEAR: ls_msg.
            ls_msg-msgv1 = 'Value'.
            ls_msg-msgv2 = ls_cell-value.
            ls_msg-msgv3 = 'too high (> 010)'.
            CALL METHOD er_data_changed->add_protocol_entry
              EXPORTING
                 i_msgid     = '00'
                 i_msgty     = 'E'
                 i_msgno     = '398'
                 i_msgv1     = ls_msg-msgv1
                 i_msgv2     = ls_msg-msgv2
                 i_msgv3     = ls_msg-msgv3
    *             I_MSGV4     =
                 i_fieldname = ls_cell-fieldname
                 i_row_id    = ls_cell-row_id
                 i_tabix     = ls_cell-tabix.
            DELETE er_data_changed->mt_mod_cells  INDEX ld_idx.
            DELETE er_data_changed->mt_good_cells INDEX ld_idx.
          ENDIF.
        ENDLOOP.
        IF ( syst-subrc = 0 ).
          er_data_changed->display_protocol( ).
        ENDIF.
    **    cl_gui_cfw=>set_new_ok_code( 'REFRESH' ). " not possible on 4.6c
        CALL METHOD cl_gui_cfw=>set_new_ok_code
          EXPORTING
            new_code = 'DUMMY'
    *      IMPORTING
    *        RC       =
      ENDMETHOD.                    "handle_data_changed
      METHOD handle_data_changed_finished.
    *   define local data
        DATA:
          ls_outtab      TYPE ty_s_outtab,
          ls_cell        TYPE lvc_s_modi.
      ENDMETHOD.                    "handle_data_changed_finished
      METHOD handle_user_command.
      ENDMETHOD.                    "handle_user_command
      METHOD handle_toolbar.
    *   define local data
        DATA:
          ls_button    TYPE stb_button.
        ls_button-function  = 'DEFAULT'.
        ls_button-icon      = icon_mass_change.
        ls_button-quickinfo = 'Set default value for column'.
        APPEND ls_button TO e_object->mt_toolbar.
      ENDMETHOD.                    "handle_toolbar
    ENDCLASS.                    "lcl_eventhandler IMPLEMENTATION
    START-OF-SELECTION.
      SELECT * FROM knb1 INTO TABLE gt_outtab UP TO 20 ROWS
        WHERE bukrs = '1000'.
      gt_outtab_pbo = gt_outtab.  " store PBO data
    * Create docking container
      CREATE OBJECT go_docking
        EXPORTING
          parent                      = cl_gui_container=>screen0
          ratio                       = 90
        EXCEPTIONS
          OTHERS                      = 6.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Create ALV grid
      CREATE OBJECT go_grid
        EXPORTING
          i_parent          = go_docking
        EXCEPTIONS
          OTHERS            = 5.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Build fieldcatalog
      PERFORM build_fieldcatalog.
      PERFORM set_layout.
      SET HANDLER:
        lcl_eventhandler=>handle_toolbar               FOR go_grid,
        lcl_eventhandler=>handle_data_changed          FOR go_grid,
        lcl_eventhandler=>handle_data_changed_finished FOR go_grid.
    * Display data
      CALL METHOD go_grid->set_table_for_first_display
        EXPORTING
          is_layout       = gs_layout
        CHANGING
          it_outtab       = gt_outtab
          it_fieldcatalog = gt_fcat
        EXCEPTIONS
          OTHERS          = 4.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      go_grid->set_toolbar_interactive( ).
      CALL METHOD go_grid->register_edit_event
        EXPORTING
          i_event_id = cl_gui_alv_grid=>mc_evt_enter
        EXCEPTIONS
          error      = 1
          OTHERS     = 2.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Link the docking container to the target dynpro
      gd_repid = syst-repid.
      CALL METHOD go_docking->link
        EXPORTING
          repid                       = gd_repid
          dynnr                       = '0100'
    *      CONTAINER                   =
        EXCEPTIONS
          OTHERS                      = 4.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * ok-code field = GD_OKCODE
      CALL SCREEN '0100'.
    * Flow logic (no elements on screen):
    *  PROCESS BEFORE OUTPUT.
    *    MODULE STATUS_0100.
    *  PROCESS AFTER INPUT.
    *    MODULE USER_COMMAND_0100.
    END-OF-SELECTION.
    *&      Module  STATUS_0100  OUTPUT
    *       text
    MODULE status_0100 OUTPUT.
      SET PF-STATUS 'STATUS_0100'.
    *  SET TITLEBAR 'xxx'.
      CALL METHOD go_grid->refresh_table_display
    *      EXPORTING
    *        IS_STABLE      =
    *        I_SOFT_REFRESH =
        EXCEPTIONS
          finished       = 1
          OTHERS         = 2.
      IF sy-subrc <> 0.
    *     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDMODULE.                 " STATUS_0100  OUTPUT
    *&      Module  USER_COMMAND_0100  INPUT
    *       text
    MODULE user_command_0100 INPUT.
      TRANSLATE gd_okcode TO UPPER CASE.
    * Fetch changes on ALV grid
      go_grid->check_changed_data( ).
      CASE gd_okcode.
        WHEN 'BACK' OR
             'END'  OR
             'CANC'.
          SET SCREEN 0. LEAVE SCREEN.
        WHEN 'DUMMY'. " do nothing but pass PAI -> list refresh at PBO
        WHEN OTHERS.
      ENDCASE.
      CLEAR: gd_okcode.
    ENDMODULE.                 " USER_COMMAND_0100  INPUT
    *&      Form  BUILD_FIELDCATALOG_KNB1
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM build_fieldcatalog .
    * define local data
      DATA:
        ls_fcat        TYPE lvc_s_fcat.
      CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
        EXPORTING
    *     I_BUFFER_ACTIVE              =
          i_structure_name             = 'KNB1'
    *     I_CLIENT_NEVER_DISPLAY       = 'X'
    *     I_BYPASSING_BUFFER           =
    *     I_INTERNAL_TABNAME           =
        CHANGING
          ct_fieldcat                  = gt_fcat
        EXCEPTIONS
          inconsistent_interface       = 1
          program_error                = 2
          OTHERS                       = 3.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      " Set required fields editable
      LOOP AT gt_fcat INTO ls_fcat
                      WHERE ( fieldname = 'ZUAWA'  OR
                              fieldname = 'BUSAB' ).
        ls_fcat-edit    = abap_true.
        MODIFY gt_fcat FROM ls_fcat.
      ENDLOOP.
      DELETE gt_fcat WHERE ( fieldname = 'ZINRT' ).
    ENDFORM.                    " BUILD_FIELDCATALOG
    *&      Form  SET_LAYOUT
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM set_layout .
      CLEAR: gs_layout.
      gs_layout-cwidth_opt = abap_true.
      gs_layout-zebra      = abap_true.
    **  gs_layout-stylefname = 'CELLTAB'.
    ENDFORM.                    " SET_LAYOUT
    Regards,
      Uwe

  • Webi base on BW query based on Infoset comes back with wrong values

    Hello:
    I have a Webi report on an OLAP Universe, on Bex Query.
    The bex query is based on 1 INFOSET.
    When I run the webi report the values that comes back a totally wrong values.
    The correct results are not brought back.
    When I do a test with crystal reports to the infoset, I can see the correct values.  (I'm aware crystal uses different drivers).
    The test is BW query designer, and crystal brings back proper values from Infoset based BW query.
    Webi on Infoset based BW Query comes back with wrong data.
    query is simple.
    Pull in 3 attributes, 3 key figures, where componentkey = "111"
    I get 36 rows in Crystal and 36 rows in Bex Analyzer, 36 rows in BW query designer (web analyzer).
    I get many rows in webi (almost like a CARTENSIAN product).
    I search a round this forum but still did not see a conclusive answer to this problem.
    But I see another thread that several others faced this same issue without a resolution.
    My environment.
    BOE XI 3.1 SP2
    No fix packs
    SAP IK 3.1 SP2
    HPUX-IA64
    Thanks in advance for any help.
    Dwayne

    Was this problem ever solved?
    I am having a similar problem with an infoset based query.
    I have created the BW infoset, and confirmed that the correct data is returned from the underlying infoproviders. A simple BW query on that infoset yields the same results.
    Create the universe, and then the WEBI, and WEBI now shows hundreds of records where I expect 10. Data is being returned in WEBI that definitely shouldn't be there. It's almost like the restrictions applied in the characteristic restriction area of my BW query are being ignored, even if I include them in the WEBI query.
    Cheers,
    Andrew

  • Full Points sure: Wrong values populating in report (BEX)

    Hi Gurus,
    I got an Issue on CRM Report. Report is populating wrong values. 
    In the report, We have structure called “Opportunity” (in that structure fields are New opportunity, Close opportunity, Win opportunity and Open opportunity) in query and  One key figure called “Revenue”.
    On revenue we have one condition with variables.  But, in that condition everything is fine.
    The Condition Screen is like this:
    Radio Button: Single characteristic  is selected
    "Opportunity Sales ID" selected in Characteristics.
    Keyfigures:                                            
    Revenue                      New Opp                      TOP N             TOP X OPP
    Revenue                      Open Opp                     TOP N             TOP X OPP
    Revenue                      WINS                           TOP N             TOP X OPP
    Revenue                      Lost                             TOP N              TOP X OPP
    everything is right in this: If we select top 10 opportunities. we are getting wrong values
    for ex:  if we select top 10 Opportunities (in the selection screen)  means “REVENUES”.
    We are getting 12 values. 10 values are correct remaining 2 values are wrong..
    There is no Update routine for “revenue” keyfield.
    Can please suggest me on this…… What are possibilities for wrong values ...
    FULL POINTS SURE FOR THIS………………
    THANKS,
    KN

    Hi All,
    Can anybody answer... this...
    thanks,
    KR

  • Bug in 1.5.1 Deleting number value in data grid

    Hello,
    it is not possible to set a number in a column to NULL by simply deleting the value
    DROP TABLE tab_test;
    CREATE TABLE tab_test(
    dat DATE
    ,num NUMBER
    ,var VARCHAR2(2)
    INSERT INTO tab_test (dat,num,var)
    VALUES (TO_DATE('01.01.2009','dd.mm.yyyy'),4,'ff');
    COMMIT;Open the table in SQL Developer and select data tab.
    Deleting the date value and commiting is ok
    UPDATE "RVS_FE"."TAB_TEST" SET DAT = TO_DATE('', 'DD.MM.YYYY') WHERE ROWID = 'AAA6Q0AAGAABHUlAAA' AND ORA_ROWSCN = '10443975276'
    Commit Successful
    Deleting the number value and commiting raises an error
    UPDATE "RVS_FE"."TAB_TEST" SET NUM =  WHERE ROWID = 'AAA6Q0AAGAABHUlAAA' AND ORA_ROWSCN = '10443975285'
    One error saving changes to table "RVS_FE"."TAB_TEST":
    Row 1: ORA-00932: inconsistent datatypes: expected NUMBER got DATE
    Rollback Successful
    Deleting the char value and commiting is ok
    UPDATE "RVS_FE"."TAB_TEST" SET VAR =  WHERE ROWID = 'AAA6Q0AAGAABHUlAAA' AND ORA_ROWSCN = '10443975285'
    Commit Successful
    Regards
    Marcus
    Edited by: Marwim on 26.11.2008 08:59

    Jim, I could reproduce and see the error, no change columns order.
    You can use the Marwim script's and, on the data grid, select the column DATE, delete value and commit.
    On the data grid, select the column var, delete value and commit.
    On the data grid, select the column num, delete value and commit -> get error.

  • IP : Delete a value in e cell without entering zero

    We have an input ready planning layout created with WAD. In WEB user deletes a value in a cell without entering zero instead. When we refresh data former value appears again. When the user enters zero to the cell we have no problem. When we execute the query with BEX and delete the value in cell without entering zero, there is no problem also. Is there a parameter in WAD to check this?

    Hi
    If you create a "Delete" function and provide the same on layout it will delete the same from the cube. However, the user need to enter the line # which he/she wants to delete from the layout. Ofcourse, entering zero in the input for Key Figure will help delete the values from cube but if it has any corresponding calculations (say salary or revenue)....it will not get nullified. It is always good idea to provide a standard delete function on the layout.
    Regards
    Srinivas

  • How to delete null values in a table

    hi all,
    tell me please any one how to delete null values in a table
    example:
    in emp table is there
    empno ename job mgr sal deptno
    7900 scott 7902 2000 10
    7499 clerk 7900 20
    7834 james manager 3000 30
    like this in the above emp table there are some null values are there
    so how to delete the null values in emp table
    thanks,
    regards.
    Edited by: user9195968 on Feb 25, 2010 6:30 AM

    not too sure what you mean, perhaps you could supply a table description and some sample data
    but, consider
    delete from table_1 where column_1 is null
    commit
    /

  • How to delete duplicate value in movement type 541 & 542(alv report)

    hi experts,
    i have some problem in alv report,
    input we can give some movement type for ex(101,102,541,542, etc)
    how to delete duplicate value in 541 and 542.
    regards
    gunasekaran.

    Try:
    Delete adjacent duplicates from ITAB comparing FIELD1, FIELD2.
    to do this the ITAB must be Sorted first.!

  • Updated CODE1 is showing wrong values in 2LIS_05_QE1

    Hi all,
    I'm using 2LIS_05_QE1 extractor to report over qualitative data in BW. When the code of the characteristics is updated, the extractor takes 2 records, before and after images. The extractor is gathering wrong values for the CODE1 field  in the before image.
    REQUEST     DATAPAKID     RECORD     ROCANCEL     PPLNKN     MERKNR     CODE1     GRUPPE1     ZHLNSTAT
    REQU_4KVR0APSV0RSZ7N70IOR0F95L     1     5120          5     40     0     CIBAU038     1
    REQU_4KPIA4UG5G1IKN6DE3XFWKIS9             3     4045     X     5     40     0     CIBAU038     -1
    REQU_4KPIA4UG5G1IKN6DE3XFWKIS9             3     4046          5     40     75     CIBAU038     1
    REQU_4KYF8YNIEMXNZI7P2Y5BM21W9     3     4045     X     5     40     0     CIBAU038     -1
    REQU_4KYF8YNIEMXNZI7P2Y5BM21W9     3     4046          5     40     75     CIBAU038     1
    We have changed the characteristic two times, now we can see two of the before images with the ROCANCEL field marked with = 'X'. The problem appears in the second before image which is not taking the actual value of the CODE1 field (75), instead is showing the value in zero. Then, when I report over the key figure in the table above ZHLNSTAT (quantity of values) the results are showing 2 values for CODE1=75 and -1 values for CODE1=0.
    Any ideas?

    I have checked Datasource and CODE1 is not a hidden field...apart from this field there are other fields too which I can see in Datasource in R/3 about dont see them in BW ....
    Please let me know what could be wrong.
    Thanks,
    Murtuza.
    Edited by: Murtuza Morwala on Jun 27, 2009 7:36 AM

  • Delete COPA value fields in a productive system

    Does anyone have practical experience with deleting COPA value fields in a productive system?
    The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
    An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
    I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
    Cheers, Peter

    To delete characteristics or value fields, you should perform the following       
    activities:                                                                               
    1. Delete the corresponding characteristics and value fields from      
    Customizing in all clients (this includes forms, reports, planning     
    layouts, and so forth). To locate characteristics and value fields, use
    the appropriate where-used list in the Customizing Monitor. You can    
    access it by choosing Tools -> Analysis -> Check Customizing Settings  
    (TA KECM).                                                             
    You can jump directly from the where-used list to the relevant         
    Customizing transaction and then delete the appropriate field there.   
    2. Switch to the screen for maintaining the data structure of an       
    operating concern (Maintain operating concern).                                                                               
    3. If you need to effect other changes to the datastucture for the     
    operating concern before making any deletions, effect those changes and
    save the data structure.                                                                               
    4. In order to be able to select the fields of the data structure,     
    choose Extras -> Characteristics (or Value fields) -> Unlock.                                                                               
    5. Select the characteristics and value fields to be deleted and remove
    them from the data structure with the "Reset fields" function.                                                                               
    6. Reactivate the operating concern. The system starts by checking
    whether the operating concern contains any data and whether the fields   
    to be deleted are still being used in any Customizing settings.                                                                               
    7. If none of the fields are still in use, the system then starts the    
    re-activation. If the operating concern does not contain any data or     
    does not require the database system to be converted, the tables are     
    activated. You are then able to activate the environment for the         
    operating concern. In this case, the following activities no longer      
    apply.                                                                   
    If the operating concern already contains data, a system message tells   
    you that the database needs to be converted. If you proceed, an          
    activation log appears (at the top of the list).                                                                               
    8. Analyze the activation log. If it only contains error messages        
    telling you to convert the tables, proceed with the next activity.       
    You must otherwise remove the cause of the errors before the tables can  
    be converted. In this case, you should answer "No" to the next prompt,   
    which asks whether the conversion transaction should start.                                                                               
    9. If you still only receive error messages telling you to convert the   
    tables, choose "Back" and start the conversion.                                                                               
    10. Plan a job for the conversion. A list of the tables to be converted  
    is shown for this. If the tables only contain a small amount of data     
    (less than 10 000 records), then all the tables can be converted in one  
    job. In that case, you can select all the tables.                        
    For larger tables, conversion should take place in several jobs.                  
    However, you should ensure that table CE4xxxx (where xxxx = operating             
    concern) is the last table to be converted.                                       
    Warning. No other changes can be made to the operating concern during             
    the conversion.                                                                   
    A copy of the table is generated during the conversion. The database              
    system should have sufficient memory available for this copy.                     
    To schedule conversion as a job, use the "Schedule selections" function.          
    You can display the current status of the conversion by selecting the             
    "Refresh" icon. Tables disappear from the list once they have been                
    converted sucessfully. If a conversion is taking a while, it is also              
    possible to leave the transaction. You can then continue the conversion           
    using DB requests -> Mass processing in one of the following ways:                
    With the job overview. You access this by choosing System -> Services ->          
    Jobs.                                                                             
    Using the database utility transaction. You access this by choosing               
    Utilities -> Database Utility in the ABAP Dictionary menu.                        
    You can use the status function to call up the status of the operating            
    concern during operating concern maintenance. You need to activate all            
    tables after conversion.                                                                               
    11. To analyze errors that have occurred during the conversion, you can           
    use the database utility transaction by choosing Extras -> Logs. The log          
    has the same name as the conversion job: TBATG-date. You can also                 
    restart the conversion with this transaction.                                     
    For more information on the database utility, choose Help -> Application          
    help while still in the above transaction.                                                                               
    12. Once you have activated all the tables in the operating concern,    
    generate the operating concern environment from within operating concern
    maintenance.                                                            
    You can then use the operating concern again.                           
    Please, refer to the IMG documentation under Controlling ->             
    Profitability Analysis -> Structures -> Define operating concern        
    -> Maintain operating concern, for further details.                     
    Hope it helps

  • HTMLDB_APPLICATION.G_F01 has wrong value!

    HTMLDB_APPLICATION.G_F01 has wrong value!
    Hello again,
    I have a search page in my app (here the user defines the search criteria) P1.
    The page branches to P130, where the result is shown. This second page contains a region of type 'SQL Query (PL/SQL Function Body Returning SQL Query)'. The code for this dynamic query is 231 lines of code, so I want to spare you scrolling through it here . What it basically does is generating SQL QRY's such as the following:
    select     distinct(sq.SAMPLE_ID) XXX,
    'ID: '||sq.SAMPLE_ID||'
    ' ||'Type: '||sq.SAMPLE_TYPE||'
    ' ||'Collection Date: '||sq.COLLECTION_DATE SAMPLE_INFO,
    'Aliquots (T/A): '||to_char(sq.ALIQUOTS_TOTAL)|| '/' ||to_char(sq.ALIQUOTS_AVAILABLE)||'
    ' ||'Volume (T/A): '||to_char(sq.VOLUME_TOTAL,'990D00')|| '/' ||to_char(sq.VOLUME_AVAILABLE,'990D00') AVAILABILITY,
    'Age: '||sq.PATIENT_AGE||'
    ' ||'Gender: '||sq.PATIENT_SEX||'
    ' ||'Bloodtype: '||sq.BLOOD_TYPE||'
    ' PATIENT_INFO,
    DML_SERVICE.get_Diagnoses(sq.SAMPLE_ID) DIAGNOSES,
    DML_SERVICE.get_Medications(sq.SAMPLE_ID) MEDICATIONS,
    DML_SERVICE.get_Interferences(sq.SAMPLE_ID) INTERFERENCES,
    DML_SERVICE.get_LabData(sq.SAMPLE_ID) LABDATA,
    decode(to_char(sq.ALIQUOTS_AVAILABLE), '0', null, htmldb_item.text(1, '1', 1, 2)) ORDER_QTY,
    decode(to_char(sq.ALIQUOTS_AVAILABLE), '0', null, htmldb_item.checkbox(2,sq.SAMPLE_ID)) ORDER_ME
    from SEARCH_V01 sq
    where sq.DIAGNOSIS = 'D-Dimer'
    order by 1 desc
    The DML_SERVICE functions just return a string(Varchar2). At the right side of the report I have two columns, one with a textfield (ORDER_QTY, default: 1) and one with a checkbox (ORDER_ME) for each line.
    For each line where the checkbox is checked, a process (On Submit - after Comp and Val) places the order for the requested quantity (this is done by inserting an Order ID into the ALIQUOTS table -> see bold update statement below).
    The process follows:
    declare
    alq_qty number;
    alq_id number;
    cnt number;
    begin
    cnt := 0;
    for i in 1..HTMLDB_APPLICATION.G_F02.count
    loop
    select count(*) -- set alq_qty to number of available alq's
    into alq_qty
    from ALIQUOTS a
    where a.SAMPLE_ID = HTMLDB_APPLICATION.G_F02(i)
    and a.ORDER_ID = 0;
    insert into D_DEBUG (ID, DD) values (1, 'wanted: ' || HTMLDB_APPLICATION.G_F01(i) || ' available: ' || alq_qty); -- REMOVE!!!
    if alq_qty > to_number(HTMLDB_APPLICATION.G_F01(i)) then -- if there are enough alq's
    alq_qty := to_number(HTMLDB_APPLICATION.G_F01(i)); -- set alq_qty to number of ordered alq's
    end if;
    for n in 1..alq_qty
    loop
    select min(ID)
    into alq_id
    from ALIQUOTS
    where sample_id = HTMLDB_APPLICATION.G_F02(i)
    and order_id = 0;
    insert into D_DEBUG (ID, DD) values (1, 'alq_id: '||alq_id); -- REMOVE!!!
    update ALIQUOTS
    set order_id = :P130_SELECT_ORDER
    where id = alq_id;
    cnt := cnt + 1;
    end loop;
    dml_service.upd_sample_record(HTMLDB_APPLICATION.G_F02(i)); -- refresh data in SAMPLE table
    end loop;
    :P130_MSG := 'Assigned '||cnt||' aliquots to order: '||:P130_SELECT_ORDER;
    end;
    Now my problem is that this process does what it should, sometimes. When I enter 6 in one row and check the checkbox and enter 4 in another row and check that checkbox and then press SUBMIT, 10 aliquots are assigned to my order.
    Sometimes.... the other times the process just orders 2 aliquots, one of each line and disregards the number entered in the textfield.
    Or so it may seem: I added some lines to write debug info into D_DEBUG (see above.) From those entries you can assume that the content of HTMLDB_APPLICATION.G_F01(i) is in fact '1' when the process does its work. So I think the problem lies somewhere in the creation of htmldb_item.text(), (I went through the API of that htmldb_item again and again...)
    Also: I can reproduce / recreate this error. It's totally weird: for some rows it (always) works and for some it (always) doesn't !!!
    So, any help, any suggestion is really appreciated (I'm currently working on bringing the crucial part of this to marvel.oracle.com)
    -David-
    [Edited by: sleuniss on Jul 15, 2004 12:18 PM]
    Changed subject line.

    Now the subjectline is right, but the indentation is gone.... :-(
    again the SQL query:
    select     distinct(sq.SAMPLE_ID) XXX,
               'ID: '||sq.SAMPLE_ID||'
    ' ||'Type: '||sq.SAMPLE_TYPE||'
    ' ||'Collection Date: '||sq.COLLECTION_DATE SAMPLE_INFO,
               'Aliquots (T/A): '||to_char(sq.ALIQUOTS_TOTAL)|| '/' ||to_char(sq.ALIQUOTS_AVAILABLE)||'
    ' ||'Volume (T/A): '||to_char(sq.VOLUME_TOTAL,'990D00')|| '/' ||to_char(sq.VOLUME_AVAILABLE,'990D00') AVAILABILITY,
               'Age: '||sq.PATIENT_AGE||'
    ' ||'Gender: '||sq.PATIENT_SEX||'
    ' ||'Bloodtype: '||sq.BLOOD_TYPE||'
    ' PATIENT_INFO,
               DML_SERVICE.get_Diagnoses(sq.SAMPLE_ID) DIAGNOSES,
               DML_SERVICE.get_Medications(sq.SAMPLE_ID) MEDICATIONS,
               DML_SERVICE.get_Interferences(sq.SAMPLE_ID) INTERFERENCES,
               DML_SERVICE.get_LabData(sq.SAMPLE_ID) LABDATA,
               decode(to_char(sq.ALIQUOTS_AVAILABLE), '0', null, htmldb_item.text(1, '1', 1, 2)) ORDER_QTY,
               decode(to_char(sq.ALIQUOTS_AVAILABLE), '0', null, htmldb_item.checkbox(2,sq.SAMPLE_ID)) ORDER_ME
    from     SEARCH_V01 sq
    where  sq.DIAGNOSIS = 'D-Dimer'
    order    by 1 desc
    and the process:
    declare
       alq_qty number;
       alq_id number;
       cnt number;
    begin
       cnt := 0;
       for i in 1..HTMLDB_APPLICATION.G_F02.count
       loop
          select count(*) -- set alq_qty to number of available alq's
           into alq_qty
           from ALIQUOTS a
           where a.SAMPLE_ID = HTMLDB_APPLICATION.G_F02(i)
           and a.ORDER_ID = 0;
    insert into D_DEBUG (ID, DD) values (1, 'wanted: ' || HTMLDB_APPLICATION.G_F01(i) || ' available: ' || alq_qty); -- REMOVE!!!
          if alq_qty > to_number(HTMLDB_APPLICATION.G_F01(i)) then -- if there are enough alq's
             alq_qty := to_number(HTMLDB_APPLICATION.G_F01(i)); -- set alq_qty to number of ordered alq's
          end if;
          for n in 1..alq_qty
          loop
             select min(ID)
              into alq_id
              from ALIQUOTS
              where sample_id = HTMLDB_APPLICATION.G_F02(i)
              and order_id = 0;
    insert into D_DEBUG (ID, DD) values (1, 'alq_id: '||alq_id); -- REMOVE!!!
             update ALIQUOTS
              set order_id = :P130_SELECT_ORDER
              where id = alq_id;
             cnt := cnt + 1;
          end loop;
          dml_service.upd_sample_record(HTMLDB_APPLICATION.G_F02(i)); -- refresh data in SAMPLE table
       end loop;
       :P130_MSG := 'Assigned '||cnt||' aliquots to order: '||:P130_SELECT_ORDER;
    end;
    -David-

  • My apple id is wrong email address on i pod i can download as it comes up with right email but to update wrong email how do i delete wrong email

    my apple id is wrong email address on i pod i can download as it comes up with right email but to update wrong email how do i delete wrong email

    You have to go to Settings>Store and log out of one account and log into the other account.  If you have updates available for apps that were purchased from more than one account, you have to update the apps individually until the remaining apps were purchased from one account.

  • TDS certificate wrong values down payment clearing

    Hi,
    we are using 4.7 version with patch level Sap &APPl( accounts &
    Logistics) SAPKH47029. we are using extended witholding tax. with three
    tax codes. Tds + Surcharge, Ecess , SHEcess
    we made vendor downpayment Rs5000/-. at the time my TDS is
    TDS+Surcharge= 550, Ecess=11, SHEcess= 6, Total tax= Rs567/-
    we made vendor invoice Rs10000/- at the time TDS is
    TDS+Surcharge= 1100, Ecess=22, SHEcess= 11, Total tax= Rs1133/-
    We cleared downpayment using F-54 aginst invoice.
    at the time it has reversed the Downpayment tds entry Rs567/-
    i made remittance challan J1INCHLN amount RS 1133/- it is correct.
    While generating TDS certificate it is showing wrong values. Rs 1116/-
    it is showing two line items.
    Amount paid TDS Surcharge Educat cess Total tax
    9450.00        500  50              1                 549.00
    5000.00        500 50              17                567.00
    Total 1116.00
    But it is showing correct value in Querterly e returns J1INQEFILE

    Hi,
    Note Number: 1124300

Maybe you are looking for