Updating Attribute value

I have a simple XML document. file.
<result success="TRUE">
<plan>
<step number="0" name="SelectTransportA"/>
<step number="1" name="SelectFlight"/>
<step number="2" name="GetMedicalFlightAccountB"/>
<step number="3" name="SelectFlight"/>
</plan>
</result>What i want is to update any "name" attribute value at runtime. I receive "number" attribute value, so on the basis of the received number, i want my name attribute value to be updated.
Just like updating a value in hashtable or vector given an index.
Regards.

It depends what you want to do, Do you just want to update the file? Then XSLT is probably the easiest. Do you want to update this in memory? Then DOM's Node.setAttribute is probably best.

Similar Messages

  • Update Attribute values of AR transaction.

    Hi All,
    We have a requirement to update the attribute of the AR transaction and have written the following code:
    DECLARE
       l_msg_count               NUMBER;
       l_msg_data                VARCHAR2 (2000);
       l_return_status           VARCHAR2 (10);
       v_batch_rec               ra_batches_all%ROWTYPE;
       v_header_rec              ra_customer_trx%ROWTYPE;
       v_errors                  arp_trx_validate.message_tbl_type;
       v_lines_tbl               ar_transaction_pub.line_tbl_type;
       v_tax_lines_tbl           ar_transaction_pub.line_tbl_type;
       v_freight_lines_tbl       ar_transaction_pub.line_tbl_type;
       v_salescredit_lines_tbl   ar_transaction_pub.salescredit_tbl_type;
       v_dist_tbl                ar_transaction_pub.dist_tbl_type;
       v_commitment_rec          arp_process_commitment.commitment_rec_type;
       v_date                    DATE;
       out_message               VARCHAR2 (4000);
       l_msg_index_out           INTEGER;
       cursor c_trx is
       select * from ra_customer_trx_all
       where customer_trx_id = 272499;--234915;
    BEGIN
       fnd_msg_pub.initialize;
       fnd_client_info.set_org_context ('328');
       fnd_global.apps_initialize (37850,50261,222, 0);
       v_date := SYSDATE - 30;--This must be a date in the open gl period
       for i in c_trx
       loop
        v_header_rec.interface_header_attribute8:= i.interface_header_attribute8;
        v_header_rec.interface_header_context:= i.interface_header_context;
        v_header_rec.default_ussgl_trx_code_context:= i.default_ussgl_trx_code_context;
        v_header_rec.interface_header_attribute10:= i.interface_header_attribute10;
        v_header_rec.interface_header_attribute11:= i.interface_header_attribute11;
        v_header_rec.interface_header_attribute12:= i.interface_header_attribute12;
        v_header_rec.interface_header_attribute13:= i.interface_header_attribute13;
        v_header_rec.interface_header_attribute14:= i.interface_header_attribute14;
        v_header_rec.interface_header_attribute15:= i.interface_header_attribute15;
        v_header_rec.interface_header_attribute9:= i.interface_header_attribute9;
        v_header_rec.default_ussgl_transaction_code:= i.default_ussgl_transaction_code;
        v_header_rec.recurred_from_trx_number:= i.recurred_from_trx_number;
        v_header_rec.attribute11:= i.attribute11;
        v_header_rec.attribute12:= i.attribute12;
        v_header_rec.attribute13:= i.attribute13;
        v_header_rec.attribute14:= i.attribute14;
        v_header_rec.attribute15:= i.attribute15;
        v_header_rec.interface_header_attribute1:= i.interface_header_attribute1;
        v_header_rec.interface_header_attribute2:= i.interface_header_attribute2;
        v_header_rec.interface_header_attribute3:= i.interface_header_attribute3;
        v_header_rec.interface_header_attribute4:= i.interface_header_attribute4;
        v_header_rec.interface_header_attribute5:= i.interface_header_attribute5;
        v_header_rec.interface_header_attribute6:= i.interface_header_attribute6;
        v_header_rec.attribute_category:= i.attribute_category;
        v_header_rec.attribute1:= i.attribute1;
        v_header_rec.attribute2:= 'NEW';
        v_header_rec.attribute3:= i.attribute3;
        v_header_rec.attribute4:= i.attribute4;
        v_header_rec.attribute5:= i.attribute5;
        v_header_rec.attribute6:= i.attribute6;
        v_header_rec.attribute7:= i.attribute7;
        v_header_rec.attribute8:= i.attribute8;
        v_header_rec.attribute9:= i.attribute9;
        v_header_rec.attribute10:= i.attribute10;
        v_header_rec.customer_trx_id:= i.customer_trx_id;
        v_header_rec.trx_number:= i.trx_number;
        v_header_rec.paying_site_use_id:= i.paying_site_use_id;
        v_header_rec.bill_to_customer_id:= i.bill_to_customer_id;
        v_header_rec.cust_trx_type_id:= i.cust_trx_type_id;
        v_header_rec.reversed_cash_receipt_id:= i.reversed_cash_receipt_id;
        v_header_rec.agreement_id:= i.agreement_id;
        v_header_rec.batch_id:= i.batch_id;
        v_header_rec.status_trx:= i.status_trx;
        v_header_rec.doc_sequence_id:= i.doc_sequence_id;
        v_header_rec.doc_sequence_value:= i.doc_sequence_value;
        v_header_rec.paying_customer_id:= i.paying_customer_id;
        v_header_rec.related_batch_source_id:= i.related_batch_source_id;
        v_header_rec.default_tax_exempt_flag:= i.default_tax_exempt_flag;
        v_header_rec.created_from:= i.created_from;
        v_header_rec.org_id:= i.org_id;
        v_header_rec.request_id:= i.request_id;
        v_header_rec.program_application_id:= i.program_application_id;
        v_header_rec.program_id:= i.program_id;
        v_header_rec.program_update_date:= i.program_update_date;
        v_header_rec.finance_charges:= i.finance_charges;
        v_header_rec.complete_flag:= i.complete_flag;
        v_header_rec.posting_control_id:= i.posting_control_id;
        v_header_rec.bill_to_address_id:= i.bill_to_address_id;
        v_header_rec.ra_post_loop_number:= i.ra_post_loop_number;
        v_header_rec.ship_to_address_id:= i.ship_to_address_id;
        v_header_rec.credit_method_for_rules:= i.credit_method_for_rules;
        v_header_rec.credit_method_for_installments:= i.credit_method_for_installments;
        v_header_rec.receipt_method_id:= i.receipt_method_id;
        v_header_rec.related_customer_trx_id:= i.related_customer_trx_id;
        v_header_rec.invoicing_rule_id:= i.invoicing_rule_id;
        v_header_rec.ship_via:= i.ship_via;
        v_header_rec.ship_date_actual:= i.ship_date_actual;
        v_header_rec.waybill_number:= i.waybill_number;
        v_header_rec.fob_point:= i.fob_point;
        v_header_rec.customer_bank_account_id:= i.customer_bank_account_id;
    --    v_header_rec.printing_option:= i.printing_option;
        v_header_rec.printing_count:= i.printing_count;
        v_header_rec.printing_pending:= i.printing_pending;
        v_header_rec.purchase_order:= i.purchase_order;
        v_header_rec.purchase_order_revision:= i.purchase_order_revision;
        v_header_rec.purchase_order_date:= i.purchase_order_date;
        v_header_rec.customer_reference:= i.customer_reference;
        v_header_rec.customer_reference_date:= i.customer_reference_date;
        v_header_rec.comments:= i.comments;
        v_header_rec.internal_notes:= i.internal_notes;
        v_header_rec.exchange_rate_type:= i.exchange_rate_type;
        v_header_rec.exchange_date:= i.exchange_date;
        v_header_rec.exchange_rate:= i.exchange_rate;
        v_header_rec.territory_id:= i.territory_id;
        v_header_rec.invoice_currency_code:= i.invoice_currency_code;
        v_header_rec.initial_customer_trx_id:= i.initial_customer_trx_id;
        v_header_rec.end_date_commitment:= i.end_date_commitment;
        v_header_rec.start_date_commitment:= i.start_date_commitment;
        v_header_rec.last_printed_sequence_num:= i.last_printed_sequence_num;
        v_header_rec.orig_system_batch_name:= i.orig_system_batch_name;
        v_header_rec.post_request_id:= i.post_request_id;
        v_header_rec.last_update_date:= i.last_update_date;
        v_header_rec.last_updated_by:= i.last_updated_by;
        v_header_rec.creation_date:= i.creation_date;
        v_header_rec.created_by:= i.created_by;
        v_header_rec.last_update_login:= i.last_update_login;
        v_header_rec.trx_date:= i.trx_date;
        v_header_rec.set_of_books_id:= i.set_of_books_id;
        v_header_rec.bill_to_contact_id:= i.bill_to_contact_id;
        v_header_rec.batch_source_id:= i.batch_source_id;
        v_header_rec.reason_code:= i.reason_code;
        v_header_rec.sold_to_customer_id:= i.sold_to_customer_id;
        v_header_rec.sold_to_contact_id:= i.sold_to_contact_id;
        v_header_rec.sold_to_site_use_id:= i.sold_to_site_use_id;
        v_header_rec.bill_to_site_use_id:= i.bill_to_site_use_id;
        v_header_rec.ship_to_customer_id:= i.ship_to_customer_id;
        v_header_rec.ship_to_contact_id:= i.ship_to_contact_id;
        v_header_rec.ship_to_site_use_id:= i.ship_to_site_use_id;
        v_header_rec.shipment_id:= i.shipment_id;
        v_header_rec.remit_to_address_id:= i.remit_to_address_id;
        v_header_rec.term_id:= i.term_id;
        v_header_rec.term_due_date:= i.term_due_date;
        v_header_rec.previous_customer_trx_id:= i.previous_customer_trx_id;
        v_header_rec.primary_salesrep_id:= i.primary_salesrep_id;
        v_header_rec.printing_original_date:= i.printing_original_date;
        v_header_rec.printing_last_printed:= i.printing_last_printed;
        v_header_rec.global_attribute1:= i.global_attribute1;
        v_header_rec.global_attribute2:= i.global_attribute2;
        v_header_rec.global_attribute3:= i.global_attribute3;
        v_header_rec.global_attribute4:= i.global_attribute4;
        v_header_rec.global_attribute5:= i.global_attribute5;
        v_header_rec.global_attribute6:= i.global_attribute6;
        v_header_rec.global_attribute7:= i.global_attribute7;
        v_header_rec.global_attribute8:= i.global_attribute8;
        v_header_rec.global_attribute9:= i.global_attribute9;
        v_header_rec.global_attribute10:= i.global_attribute10;
        v_header_rec.global_attribute11:= i.global_attribute11;
        v_header_rec.global_attribute12:= i.global_attribute12;
        v_header_rec.global_attribute13:= i.global_attribute13;
        v_header_rec.global_attribute14:= i.global_attribute14;
        v_header_rec.global_attribute15:= i.global_attribute15;
        v_header_rec.global_attribute16:= i.global_attribute16;
        v_header_rec.global_attribute17:= i.global_attribute17;
        v_header_rec.global_attribute18:= i.global_attribute18;
        v_header_rec.global_attribute19:= i.global_attribute19;
        v_header_rec.global_attribute20:= i.global_attribute20;
        v_header_rec.global_attribute_category:= i.global_attribute_category;
        v_header_rec.wh_update_date:= i.wh_update_date;
        v_header_rec.edi_processed_flag:= i.edi_processed_flag;
        v_header_rec.edi_processed_status:= i.edi_processed_status;
        v_header_rec.global_attribute21:= i.global_attribute21;
        v_header_rec.global_attribute22:= i.global_attribute22;
        v_header_rec.global_attribute23:= i.global_attribute23;
        v_header_rec.global_attribute24:= i.global_attribute24;
        v_header_rec.global_attribute25:= i.global_attribute25;
        v_header_rec.global_attribute26:= i.global_attribute26;
        v_header_rec.global_attribute27:= i.global_attribute27;
        v_header_rec.global_attribute28:= i.global_attribute28;
        v_header_rec.global_attribute29:= i.global_attribute29;
        v_header_rec.global_attribute30:= i.global_attribute30;
        v_header_rec.payment_server_order_num:= i.payment_server_order_num;
        v_header_rec.approval_code:= i.approval_code;
        v_header_rec.address_verification_code:= i.address_verification_code;
        v_header_rec.old_trx_number:= i.old_trx_number;
        v_header_rec.br_amount:= i.br_amount;
        v_header_rec.br_unpaid_flag:= i.br_unpaid_flag;
        v_header_rec.br_on_hold_flag:= i.br_on_hold_flag;
        v_header_rec.drawee_id:= i.drawee_id;
        v_header_rec.drawee_contact_id:= i.drawee_contact_id;
        v_header_rec.drawee_site_use_id:= i.drawee_site_use_id;
        v_header_rec.drawee_bank_account_id:= i.drawee_bank_account_id;
        v_header_rec.remittance_bank_account_id:= i.remittance_bank_account_id;
        v_header_rec.override_remit_account_flag:= i.override_remit_account_flag;
        v_header_rec.special_instructions:= i.special_instructions;
        v_header_rec.remittance_batch_id:= i.remittance_batch_id;
        v_header_rec.prepayment_flag:= i.prepayment_flag;
        v_header_rec.ct_reference:= i.ct_reference;
        v_header_rec.contract_id:= i.contract_id;
        v_header_rec.bill_template_id:= i.bill_template_id;
        v_header_rec.cc_error_flag:= i.cc_error_flag;
        v_header_rec.cc_error_code:= i.cc_error_code;
        v_header_rec.cc_error_text:= i.cc_error_text;
       dbms_output.put_line(v_header_rec.term_id);
       end loop;
       ar_transaction_pub.update_transaction
                             (p_api_name                   => 'AR_TRANSACTION_PUB',
                              p_api_version                => 1.0,
                              p_init_msg_list              => fnd_api.g_true,
                              p_commit                     => fnd_api.g_true,
                              p_validation_level           => fnd_api.g_valid_level_full,
                              p_batch_rec                  => v_batch_rec,
                              p_header_rec                 => v_header_rec,
                              p_receivable_gl_date         => v_date,
                              p_commitment_rec             => v_commitment_rec,
                              p_lines_tbl                  => v_lines_tbl,
                              p_tax_lines_tbl              => v_tax_lines_tbl,
                              p_freight_lines_tbl          => v_freight_lines_tbl,
                              p_salescredit_lines_tbl      => v_salescredit_lines_tbl,
                              p_dist_tbl                   => v_dist_tbl,
                              p_return_status              => l_return_status,
                              p_msg_count                  => l_msg_count,
                              p_msg_data                   => l_msg_data,
                              p_errors                     => v_errors,
                              p_recalc_tax_flag            => fnd_api.g_true,
                              p_rerun_autoacc_flag         => fnd_api.g_true,
                              p_backout_sc_flag            => fnd_api.g_true,
                              p_backout_dist_flag          => fnd_api.g_true
       IF (fnd_msg_pub.count_msg > 0)
       THEN
          FOR i IN 1 .. fnd_msg_pub.count_msg
          LOOP
             fnd_msg_pub.get (p_msg_index          => i,
                              p_encoded            => 'F',
                              p_data               => out_message,
                              p_msg_index_out      => l_msg_index_out
             DBMS_OUTPUT.put_line ('l_msg_data :' || out_message);
          END LOOP;
       END IF;
    END;However getting the below error:
    l_msg_data :Invalid payment terms id. (TERM_ID: &INVALID_VALUE)
    l_msg_data :Invalid Transaction Status &INVALID_VALUE .
    l_msg_data :Validation error(s) occurred. Rolling back and setting status to ERROR
    This was working fine sometimes back. Can anyone point the right direction. I am able to update the attribute value fron the front end.
    Thanks,
    Subhasish

    Hi All,
    Any thoughts on this ??
    Regards,
    Subhasish

  • Update attribute value in xml db in Oracle 10g

    I have a table with XML blob data
    The root element is invoice with an element billInfo and attribute type0
    I'm trying to update the attribute value using the following sql but it is not working.
    the sql goes to sucess but the value is not updated.
    Looking for a solution and I appreciate your help
    update sc.table_name
    set xml_cb= updateXML(xml_cb,'/invoice/billInfo/@type0','A')
    where id = 1 succeeded.
    select id,
    extractValue(xml_cb,'/invoice/billInfo/@type0') type_val
    from sc.table_name
    where id =1;
    ID TYPE_VAL
    1 K

    What database version are you using?
    could you show us the outcome of:
    SQL> select dbms_metadata.get_ddl('TABLE','TABLE_NAME','SC') from dual;
    and/or a
    SQL> describe SC.TABLE_NAME

  • Selcect/ update attribute value using xpath navigator/ linq to xml

    Hi Folks,
    below is my xml string and the highlighted bold attribute value needs to update. Since this element contains prefix im not able to select teh particular element. if i remove the prefixx im able to select but i need to keep prefix.
        <IOP:MtvnSvcReq xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:IOP="mtvnCWExternInteropReq" xmlns:IOP1="mtvnExtInteropReqData" xmlns:PR1="mtvnPRInteropReqData">
                              <IOP:Svc>
                                                 <IOP1:PR1>
                                                       <PR1:PRExternSSOReqData>
    <PR1:UserId>abcd</PR1:UserId>
                                                       </PR1:PRExternSSOReqData>
                                                 </IOP1:PR1>
                                </IOP:Svc>
                        </IOP:MtvnSvcReq>
    Thanks 

    Hi Pulikk,
    Do you mean you want  to change the attribute value(abcd)? If so,
    Please try the following code, i tested on my side, it changed successfully.
    //Here is the variable with which you assign a new value
    string newValue = string.Empty;
    XDocument objDoc = XDocument.Load(@"yourdata.xml");
    XNamespace IOP = "mtvnCWExternInteropReq";
    XNamespace IOP1 = "mtvnExtInteropReqData";
    XNamespace PR1 = "mtvnPRInteropReqData";
    foreach (var node in objDoc.Descendants(PR1 + "UserId"))
    node.Value = newValue;
    objDoc.Save(@"yourdata.xml");
    Have a nice day!
    Kristin
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Updated Attribute values in Z table not coming in Delta

    Hi,
    We have a generic master data datasource based on a view. View is based on two standanrd R3 tables. We also enhanced this datasource by adding few fields populated through user exit from a custom Z table.
    The datasource was initialized (delta field being 'Change date field' i.e. AEDAT).
    The issue is, if users update/modify few fields in Z table, then those records are not picked up as deltas because AEDAT field is not changed.
    How should I pull such records? If I do a repair full, will it affect delta mechanism?
    Regards,
    Vikrant.

    Hi AHP,
    Thx for replying.
    But is there any other way. At present I do not want to do any new development, its pretty urgent requirement.
    Can't I do full-repair for such records?
    Regards,
    Vikrant.

  • Changing Element Attribute Values

    I spent far to long trying to figure out how to change an element attribute value without the FDK's SetAttributes function, so I thought I'd spare someone else the time.
    Basically, you still get the attributes using the GetAttributes() function, but now you just set the beg.child.Attributes property to the updated attribute value.
    //starting with a selected element
    elemSelect=app.ActiveDoc.ElementSelection
    //get the current attributes
    var childattributes =elemSelect.beg.child.GetAttributes()
    //find the attribute and value you want to change, and change it to a new value.
    childattributes[0].values[0] = "New_Value"
    //now assign the edited attributes to the selected element.
    elemSelect.beg.child.Attributes=childattributes
    Depending on how you selected the element, I assume you could do the above with beg.parent as well, but it wasn't something I needed to consider.
    ~Christen

    Thanks for this--you've likely saved me a headache.
    While I hadn't hit this yet, it does apply to several of the projects on my to-do list. Based on the info in the OMV, I would have expected to be able to simply use a statement like myElement.Attributes[i].value[i] = "New_Value" which, as I'm sure you discovered, has no apparent effect at all.
    The other thing I noticed in my quick testing is that defining your attributes variable by using the method (x = myElement.GetAttributes()) or by referenceing the Attributes property (x = myElement.Attributes) seem to be functionally equivalent.

  • Can we update the Category attribute values of a file

    Can we update the Category attibute values of a file with out checkout the file?
    I have set the version configuration to folder and try to update the category attribute values of a file under that folder,
    It is asking to checkout the file before modifying the category attibute values.
    Is it required to checkout the file before modifying the category attribute values of that file?
    Is there any way to update the category attribute values without checkout the file?
    Please help on this

    One of the ways i can think of is using Batch Loader script for large number of files. Mention such files in Batch Loader script, and it will update category and all meta-data required in terms of next revision.
    In case number of files are less manual checkout and check-in will help.

  • InDesign CS3 crash during document open (at XML Attribute Value update for locked item)

    OS: Windows XP
    InDesign: InDesign Release 5.0.0.458   
    Plugins: No additional plugins
    I am facing crash in InDesign at following workflow
    Steps:
    1. Create a new document.
    2. Create a graphic frame.
    3. Place an Image (C:\TESTDIR\images\test-image.jpg)
    4. Tag the graphic frame (Right Click -> Autotag).
    5. Lock the layer.
    6. Save the doc at (C:\TESTDIR\files\test-doc.indd).
    7. Move the image file to (C:\TESTDIR\)
    8. Open the same document.
    9. InDesign Crash.
    Crash log:
    Adobe InDesign Protective Shutdown Log
    06/01/09 14:48:51
    Unhandled error condition
    Session started up at 2:44 PM on Monday, June 01, 2009
    Version: 5.0.0 - Build: 458
    Error Code 0xbfcd: "Cannot modify elements that contain locked content, or are contained by locked content. Please unlock or check out the content and try again."
    Command Sequence:
    > kOpenFileWithWindowCmdBoss = ""
    > kOpenFileCmdBoss = ""
      > kOpenDocCmdBoss = ""
       > kSetDocNameCmdBoss = ""
       > kSetDocNameCmdBoss = ""
    > kSetAllUsedStyleCmdBoss = ""
      > kSetAllUsedStyleCmdBoss = ""
    > kRestoreLinkCmdBoss = "Restore Link" : kBeforeDoMessageBoss @ kDocBoss (IID_ICOMMANDMGR)
    > kSetAssetAttributesCmdBoss = "" : kBeforeDoMessageBoss @ kDocBoss (IID_ICOMMANDMGR)
      > kSetAssetAttributesCmdBoss = "" : kAfterDoMessageBoss @ kDocBoss (IID_ICOMMANDMGR)
    > kXMLSetAttributeValueCmdBoss = "Set Attribute Value" : kBeforeDoMessageBoss @ kDocBoss (IID_ICOMMANDMGR)
      > kXMLSetAttributeValueCmdBoss = "Set Attribute Value" : kAfterDoMessageBoss @ kDocBoss (IID_ICOMMANDMGR)
    > kRestoreLinkCmdBoss = "Restore Link" : kAfterDoMessageBoss @ kDocBoss (IID_ICOMMANDMGR)
    Please let me know how to stop XML tag updation (execution of  kXMLSetAttributeValueCmdBoss) at document open.

    Is the first time one of these files crashes always on one system or another, or is it random across systems?
    It is random and it's not related to a file (one time i can open the file andanother time it cause an InDesign crash);
    It sounds very much like a font problem. Are you using a font manager, and if so, which one?
    We have reproduced the problem also on machine with only system's fonts.
    I forgot to say that the crashes happen only with InDesign files with InCopy files linked in.
    Thanks
    Alessandro

  • Update an attribute's Min. & Max. Attribute value after opening date

    Hi
    We have created an attribute 'projected price' on a bid invitation. The minimum and maximum attribute values will only be known after all bids have been submitted. So we need to populate the minimum and maximum attribute values after the opening date before running the evaluation report. Any assistance on how we could do this will be appreciatted.
    Regards

    I've managed to solve this by doing the following.
    <b>1) Get the items on the Bid Invitation</b>
    CALL FUNCTION 'BBP_PROCDOC_GETDETAIL'
    EXPORTING
       I_GUID                        = ip_guid
       I_OBJECT_TYPE                 = 'BUS2200'
    IMPORTING
       E_HEADER                      = ls_header
       ET_ATTACH                     = lt_attach
       ET_CONDITIONS                 = lt_conditions
       ET_DYN_ATTR                   = lt_dyn_attr
    TABLES
       E_ITEM                        = rt_items.
    <b>2) Get all the weightings for these items.</b>
      CALL FUNCTION 'BBP_PDWGT_GETDETAIL'
        EXPORTING
          i_p_guid            = ip_guid
          i_p_kind            = 'B'
          i_object_type       = 'BUS2200001'
        tables
          e_weight            = rt_weights.
    <b>3) Then updated the specific attributes values.</b>
      DATA: lt_x_weight TYPE bbpt_pds_weight_ic,
            ls_weight TYPE bbp_pds_weight_ic,
            lt_y_weight TYPE bbpt_pds_weight_ic.
      CLEAR ls_weight.
      SELECT SINGLE * INTO CORRESPONDING FIELDS OF ls_weight
        FROM bbp_pdwgt WHERE guid = ip_guid.
      IF sy-subrc NE 0.
        EXIT.
      ENDIF.
      APPEND ls_weight TO lt_y_weight.
      ls_weight-value_amount1 = ip_min.
      ls_weight-value_amount2 = ip_max.
      ls_weight-kz            = 'U'.
      APPEND ls_weight TO lt_x_weight.
      CALL FUNCTION 'BBP_PDWGT_DB_UPDATE'
        TABLES
          i_x_weight = lt_x_weight
          i_y_weight = lt_y_weight.
      IF sy-subrc EQ 0.
        COMMIT WORK.
      ENDIF.
    Regards

  • Updating Schdedule Task Attributes values in OIM through our Code.

    Hi Guys,
    My Requirement is that I should be able to update the schedule task attributes through my reconciliation code. I tried my level best to find some API but unable to locate the API's to update the schedule task attribute.
    I used to following funciton to update the schedule task attribtue value:
    public void updateScheduleTaskAttribute(long scheduledTaskKey,
    long taskAttributeKey,
    java.util.Map attributes)
    This API found is in the tcSchedulerOperationsIntf interface. However, I am unable to find any API to retrieve the scheduledTaskKeyand taskAttributeKey parameters for the currently executing schedule task. Currently, we use the getAttribute(String) method to retrieve the schedule task attributes. I would be very grateful if you could guide me on how to obtain the scheduledTaskKey. If I am able to get that, I think it would be possible to obtain the taskAttributeKey, though do let me know if there is a better approach to get this also.
    I would be highly obliged if someone could tell me some better way or a code snippet through which I can update the schedule task attribute values.
    Thanks in advance,
    Akki :-)

    Thanks a lot kevin for your reply,
    Actually there are some attributes which doesn't makes sense if they reside in IT Resources as IT Resource are meant for keeping connection parameters which will be used during provisioning. For ex: Last Reconciled Record, Last Reconciled Timestamp. These two attributes doesn't makes sense if they reside in IT Resources.
    I hope you understood my requirements.
    Hoping a ray of light :-)
    Thanks in advance,
    Akki

  • How to update attributes from OIM to AD in case of LDAPSync

    Hi All,
    In our scenario, we have LDAPSync configured for OIM AD Integration. OIM version is OIM 11gR2 PS1 (11.1.2.1.0.0)
    It is working fine and On user creation in OIM ,RealTime user creation under specified container in AD is happening.It is SSL enabled,so password is also getting updated from OIM to AD.
    But we have following conflicting scenario --
    -   As per our requirement we have to generate random password for User in OIM. For that we have PostProcess event handler implemented in OIM.
    - We have tested LDAPSync by creating user manually through OIM console. While creating user manually, we have provided value for password attribute along with other attributes.
        So, password attribute in AD will get updated for User along with all other attributes values mapped for AD from OIM.
    - But, in our scenario random password is generated for User through OIM post process event handler and it will be updated again in user profile of user created manually in OIM. This password is sent to User through mail.
      As this password event handler will get triggered after LDAPSnyc only, this password will not be update in AD for manually created user in OIM. So he can log into OIM with this new password but not to AD system.
      He will be able to login to AD system with same User ID but with password which was set at time of manual User Creation in OIM and not with the password updated in OIM user profile by PostProcess event handler.
    Is it possible to set password for user through PreProcess even handler implementation for Random Password generation. In this case also , the default OIM post process
    password generator will override the PreProcess event handler.How to resolve this issue.
    Also,when AD connector is in place in OIM environment we would be having change/update tasks for any attribute update to be send from OIM to AD.
    How this update scenario will be implemented from OIM to AD in case of LDAPSync ?
    Please provide any helpful pointer on this.
    Thanks,
    RPB

    Password :
    Increase order of calling for custom password event handler than OOTB handler.
    Update:
    you wanted to update custom fields?
    Did you check default update tasks comes with connector?

  • How to update Elements value inside existing xml file

    Hi Gurus,
    Am somehow new to java and working on xml with java, i have a scenario where i want to update the elements of my existing xml file, i know its possible as i have posted one code on this forum which updates the values of the arrtibutes of existing xml file. Ref :
    http://forum.java.sun.com/thread.jsp?forum=34&thread=186091&start=15&range=15&hilite=false&q=
    But am not able to use the same code to update the vlaues of the attribute.
    if i have this xml file :
    <?xml version="1.0"?>
    <RootElement>
    <Transaction>
    <Task9>
    <TaskID>Task9</TaskID>
    <Description>My Test Case</Description>
    <Time>12/12/2004</Time>
    </Task9>
    </Transaction>
    <Transaction>
    <Task2>
    <TaskID>Task2</TaskID>
    <Description>Testing my xml</Description>
    <Time>12/12/2004</Time>
    </Task2>
    </Transaction>
    </RootElemen>
    Now i want to update teh </Description> and </Time> field using the code that i have given above in the link.
    If any one can help me ill really appreciate.

    The value of an element is stored in a child node of that element. For example, let's say that "e" references the node <Description> then:
    e.getFirstChild().getNodeValue() => "My Test Case"

  • Updated attribute not showing up in the Front End

    Hi,
    I have to update an attribute column based on some conditions.
    Even though I have updated, the updated value is not showing up in the front end
    Moreover if I go to Diagnostics-> Examine and then query the attribute value I can see the updated Result
    What can be the reason...
    Please Advise
    Rahul

    Sounds like the Statement is not committed. Maybe you should add a
    COMMIT;
    at the end of your query.

  • How to add Navigation attributes values via ABAP while creation of CVC

    Hi,
    I have a requirement like, I have to add navigational attributes to the cvc record while CVC creation ( /sapapo/mc62 transaction).
    There were two scenarios: 1. Usually when they load master data from BW side those navigation attributes available and when we do CVC creation it's automatically picks those values. If NOT then i have to bring Market segment and Business unit navigational attributes values from ECC via RFC function module by passing MPN and End customer division as a input.
    I am facing problem when BW side if business unit and Market segment were blank.
    Do we have any Function modules available to add navigational attributes data and should update corresponding master data tables.
    Please help me step by step process on this.
    Thanks
    Ravi
    Edited by: REDDY KALLURI on Jan 22, 2011 10:30 PM

    Michael,
    Are you intending this as a commercial solution or a work around?
    To take an existing equivalent, one would build a view in the database tailored for each grid in an Oracle Forms application. Or a separate query layered over tables for each form/grid in a Delphi or Access application? Even if it is ninety nine percent the same over half a dozen forms/grids?
    And now you've added a whole slew of "slightly different" rowSetInfos to maintain.
    So if you wanted to add a column that needs to appear everywhere... you've just increased the workload multi-fold?
    That would be a management nightmare, wouldn't it? Not to mention yet more performance cost and a slower system?
    Hmmmm..... I'm not sure I like where this is headed... someone needs to do some convincing...
    null

  • Tricky! Change of navi-attribute values in ABAP and use in selections

    Hi gurus,
    now I have a teaser that really keeps me busy, and which might be interesting for some of you:
    we use several statuses in our <u>Demand Planning in SCM 5.0</u>, some of which can be switched by using a user-function macro which just basically is a ABAP function module that <u>changes navigation attribute values directly on the database</u>, meaning in the master data tables of the respective characteristic.
    Now, the code works, the values are changed accordingly, leaving the data set in object status "active" - <b>BUT</b>:
    <i>when we call a selection, it still shows the old values, even after activating master data or running the attribute change run!</i>
    This is not what we expected. Our wish was, that once the table was updated with the correct field values, we would also see them in our selections.
    <u>Details:</u>
    we have two statuses as navi-attributes to an article:
    <i>DP:</i> YES/NO, and
    <i>oDP:</i> YES/NO
    Combinations originally are: <i>DP</i> YES/<i>oDP</i> NO
    After the status change macro, the table shows the following, as expected:
    <i>DP</i> NO/<i>oDP</i> YES
    As we have two selections, one on DP status "YES", the other one on oDP status "YES", we would like to see the article vanish in the first selection and show up in the other one...
    Does anybody have an idea what is wrong and what we can do to have to proper navi-attribute values from the master data table in the selection? Does the selection not read from the database but from a buffer?
    Looking forward to your answers,
    Klaus

    Hi Fabrice,
    yes indeed, I did check the object version, and it is A.
    Problem is, the function module changes the data record which is "A" anyway. So the changed data record is active - however, I just had a look at the SID master data table, and it looks that direct changes to the P-table do not affect the X-table where the SIDs are stored. So I guess I will also have to update the X-table with the correct SID-values.
    If this works, I let you know. We will be using this change by ABAP quite often, it is rather useful.
    Regards and thanks for your prompt reply,
    Klaus

Maybe you are looking for

  • Two different main windows in one form?

    Hello - I have a requirement to print a list at the end of an invoice printout.  The invoice can cover multiple pages, and the secondary list can also cover multiple pages, one page per material.  So essentially I need two different definitions of a

  • RFC call in XI

    Hi All: <b>In my HTTP to BAPI Scenaerio I am sending the message</b>   <?xml version="1.0" encoding="UTF-8" ?> - <ns:MT_HTTP_Request xmlns:ns="http://sap.com/XI/HTTP2BAPI">   <CompnayID>001</CompnayID>   </ns:MT_HTTP_Request> <b>In MONI its Mapped to

  • Migrate Starter Album to Element 12

    I have Adobe Photoshop Element 12 installed on my new computer (Windows 8) but how do I import the album structure organizing my 4,000 photos in Adobe Photoshop Album Starter Edition 3.0 from my old computer (Windows XP)?

  • How to do a Screen Print with Pro keyboard?

    Hi everyone, I have tried a multitude of button combination but I cannot figure out how to do a Screen Print in Windows XP... I am using a Pro Keyboard from Apple which has black keys. Can anyone help me please? Rio.

  • SetCharacterEncoding in HttpServletRequest doesn't seem to work

    Hello people I make the following request on the client side String addr = "blabla:8080/servlet?" +  URLEncoder.encode(request, "UTF-8"); URL urlAddr = new URL(addr); urlAddr.openConnection();So that a post request is sent to the servlet. lets say my