XMLSequence and extract attribute

Hi all,
From this XML :
<execute-transaction app-ref="SRSRSimpleMult" app-sn="458" login="CARNI">
     <context key="Env:LOGIN" value="CARNI"/>
     <context key="Env:APP_SN" value="458"/>
     <context key="Env:APP_REF" value="SRSRSimpleMult"/>
</execute-transaction>I would like to extract all the "key" attribute...
The following select returns the good result but all is in 1 row :
select extract(XMLTYPE('<execute-transaction app-ref="SRSRSimpleMult" app-sn="458" login="CARNI">
     <context key="Env:LOGIN" value="CARNI"/>
     <context key="Env:APP_SN" value="458"/>
     <context key="Env:APP_REF" value="SRSRSimpleMult"/>
</execute-transaction>'),'*/context/@key') FROM DUAL;So I use XMLSequence (and not XMLTable because I'm still on Oracle 10g1) but the following select returns nothing
select COLUMN_VALUE FROM table(xmlsequence(extract(XMLTYPE('<execute-transaction app-ref="SRSRSimpleMult" app-sn="458" login="CARNI">
     <context key="Env:LOGIN" value="CARNI"/>
     <context key="Env:APP_SN" value="458"/>
     <context key="Env:APP_REF" value="SRSRSimpleMult"/>
</execute-transaction>'),'*/context/@key')));However if I simply remove the "@key" in the XPath expression, the select gives me back a good result ! (but with the context tag that I don't care)
Can someone tell me why the SELECT doesn't return a result when the xpath expression contains the "@key" attribute ?
Thx

select xt.*
FROM  table(xmlsequence(extract(XMLTYPE
                    ('<execute-transaction app-ref="SRSRSimpleMult" app-sn="458" login="CARNI">
                        <context key="Env:LOGIN" value="CARNI"/>
                        <context key="Env:APP_SN" value="458"/>
                        <context key="Env:APP_REF" value="SRSRSimpleMult"/>
                      </execute-transaction>')
                               , '/execute-transaction/context'))) xt;
COLUMN_VALUE
<context key="Env:LOGIN" value="CARNI"/>
<context key="Env:APP_SN" value="458"/>
<context key="Env:APP_REF" value="SRSRSimpleMult"/>
3 rows selected
select rownum as "ROW"
     , extract(value(xt),'/context/@key') as "RESULT"
FROM   table(xmlsequence(extract(XMLTYPE
                     ('<execute-transaction app-ref="SRSRSimpleMult" app-sn="458" login="CARNI">
                         <context key="Env:LOGIN" value="CARNI"/>
                         <context key="Env:APP_SN" value="458"/>
                         <context key="Env:APP_REF" value="SRSRSimpleMult"/>
                        </execute-transaction>')
                                 , '/execute-transaction/context'))) xt;
ROW RESULT
  1 Env:LOGIN
  2 Env:APP_SN
  3 Env:APP_REF
3 rows selectedEdited by: Marco Gralike on Mar 30, 2011 12:43 PM

Similar Messages

  • Datasources and Extract structure

    Hi guys,
    I am pretty confused about DataSources and Extract structure.
    Can someone please explain it me in simple words.

    Hi Zubin,
    Data Source is a consoliated list of fields available and the extract structure is a data dictionary structure which illustrates the fields with additional technical elements like DATA ELEMENT , DOMAIN ans so on...
    To make it more clear look at this description from F4 help:
    A DataSource is an object for retrieving data. The DataSource is localized in the OLTP system.
    It has
    an extract structure,
    an extraction type, and
    an extraction method.
    The extract structure describes the fields of the internal table that contain the extracted data. The extraction type describes which type of extractor the DataSource uses. The extraction method extracts the data and transfers it into an internal table with the same type as the extract structure.
    The DataSource also contains information on the type of data that it stages, for example, attributes, transactional data, hierachies, or texts. It can also support different types of data update.
    Extract Structure for a DataSource
    The extraction structure for a data source shows the format in which the DataSource, or the extractor for the DataSource, transfers its data.
    A data element must be assigned to each field of the extraction structure. This allows in the Business Information Warehouse an intelligent mapping between field names and InfoObjects using just this data element.
    The extract structure must be created in the DDIC as a dictionary structure or transparent table. A view is not permitted here since it would then not give you the option to add an append.
    Appends enable you to convert your individual requirements and own "Business Logic" in the extraction process. You can fill the fields in the append using function enhancements.
    Hope this helps
    Thanks,
    Raj

  • How can i extract attributes from XML-file

    Hi!
    I want to extract XML-files.
    And the most tags are no problem,but how can i extract attributes?
    Here is a part from the XML-Schema:
    <xs:complexType name="ATT_LIST">
              <xs:sequence>
                   <xs:element name="ATTRIB" minOccurs="0" maxOccurs="unbounded">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="VALUE"/>
                             </xs:sequence>
                             <xs:attribute name="ATTNAM" use="required"/>
                        </xs:complexType>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
    Thanks for help.
    With best regards.
    Nicole

    Hi!
    If i delete one '/' i get the error message:
    data can't be found'
    This is my xml-file:
    <?xml version="1.0" encoding="UTF-8"?>
    <INSOBJ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sv6:8080/sys/schemas/SCOTT/sv6:8080/public/mydocs/inspection_pda_schema.xsd">
         <INSP_PDA>
              <SYSID>900000438</SYSID>
              <INSPECTOR/>
              <INSDAT>20001223</INSDAT>
              <INSOBJ_TYP>MSP-Mast</INSOBJ_TYP>
              <INSOBJ_ID1>BAM / Bad Aussee / Bad Mitterndorf/Grundlsee</INSOBJ_ID1>
              <INSOBJ_ID2>MITTERNDORF 2 - M 259</INSOBJ_ID2>
              <INSOBJ_ID3>239</INSOBJ_ID3>
              <INSOBJ_NAME>259</INSOBJ_NAME>
              <PDA_PORTION>0000000391</PDA_PORTION>
              <GESQUALITAET/>
              <AUSFALLSEINSCH/>
              <ANMERKUNGEN/>
              <LAGE_NORD>48,2281993</LAGE_NORD>
              <LAGE_OST>14,2394658</LAGE_OST>
              <HOEHE/>
              <GPS_STATUS/>
              <KOORD_SYSTEM/>
              <KOORD_EINHEIT/>
              <PLZ/>
              <ORT/>
              <STR_ORTSTEIL/>
              <NUMMER/>
              <BEZEICHNUNG/>
              <GRUNDBESITZER/>
              <TELENR/>
              <ERREICHBARKEIT/>
              <ATT_LIST>
                   <ATTRIB ATTNAM="BAUWEISE">
                        <VALUE>E-Mast</VALUE>
                   </ATTRIB>
                   <ATTRIB ATTNAM="HOLZART">
                        <VALUE>KIEFER</VALUE>
                   </ATTRIB>
              </ATT_LIST>
              <MZ_LIST>
                   <MAS_ZU MZ_NAM="AUSHOLZEN">
                        <VALUE>J</VALUE>
                        <BEMERKUNG/>
                        <INSP_AM/>
                        <INSP_VON/>
                        <DONE_AM>N</DONE_AM>
                        <DONE_VOM/>
                        <URSACHE>2</URSACHE>
                        <DRINGLICH>2</DRINGLICH>
                        <ZIEL_DAT/>
                        <MZ_PARAM_LIST/>
                   </MAS_ZU>
                   <MAS_ZU MZ_NAM="ALLGEMEIN-ANMERKUNG">
                        <VALUE>2 Isolatoren</VALUE>
                        <BEMERKUNG/>
                        <INSP_AM/>
                        <INSP_VON/>
                        <DONE_AM/>
                        <DONE_VOM/>
                        <URSACHE>2</URSACHE>
                        <DRINGLICH/>
                        <ZIEL_DAT/>
                        <MZ_PARAM_LIST/>
                   </MAS_ZU>
                   <MAS_ZU MZ_NAM="Stange erdfaul/hohl">
                        <VALUE>J</VALUE>
                        <BEMERKUNG/>
                        <INSP_AM/>
                        <INSP_VON/>
                        <DONE_AM/>
                        <DONE_VOM/>
                        <URSACHE/>
                        <DRINGLICH/>
                        <ZIEL_DAT/>
                        <MZ_PARAM_LIST/>
                   </MAS_ZU>
                   <MAS_ZU MZ_NAM="Masttyp nicht normgerecht">
                        <VALUE>J</VALUE>
                        <BEMERKUNG/>
                        <INSP_AM/>
                        <INSP_VON/>
                        <DONE_AM/>
                        <DONE_VOM/>
                        <URSACHE/>
                        <DRINGLICH/>
                        <ZIEL_DAT/>
                        <MZ_PARAM_LIST/>
                   </MAS_ZU>
              </MZ_LIST>
         </INSP_PDA>
         <INSP_PDA>
              <SYSID>900000437</SYSID>
              <INSPECTOR/>
              <INSDAT>20001223</INSDAT>
              <INSOBJ_TYP>MSP-Mast</INSOBJ_TYP>
              <INSOBJ_ID1>BAM / Bad Aussee / Bad Mitterndorf/Grundlsee</INSOBJ_ID1>
              <INSOBJ_ID2>MITTERNDORF 2 - M 259</INSOBJ_ID2>
              <INSOBJ_ID3>239</INSOBJ_ID3>
              <INSOBJ_NAME>259</INSOBJ_NAME>
              <PDA_PORTION>0000000391</PDA_PORTION>
              <GESQUALITAET/>
              <AUSFALLSEINSCH/>
              <ANMERKUNGEN/>
              <LAGE_NORD>48,2281993</LAGE_NORD>
              <LAGE_OST>14,2394658</LAGE_OST>
              <HOEHE/>
              <GPS_STATUS/>
              <KOORD_SYSTEM/>
              <KOORD_EINHEIT/>
              <PLZ/>
              <ORT/>
              <STR_ORTSTEIL/>
              <NUMMER/>
              <BEZEICHNUNG/>
              <GRUNDBESITZER/>
              <TELENR/>
              <ERREICHBARKEIT/>
              <ATT_LIST>
                   <ATTRIB ATTNAM="BAUWEISE">
                        <VALUE>E-Mast</VALUE>
                   </ATTRIB>
                   <ATTRIB ATTNAM="HOLZART">
                        <VALUE>KIEFER</VALUE>
                   </ATTRIB>
              </ATT_LIST>
              <MZ_LIST>
                   <MAS_ZU MZ_NAM="AUSHOLZEN">
                        <VALUE>J</VALUE>
                        <BEMERKUNG/>
                        <INSP_AM/>
                        <INSP_VON/>
                        <DONE_AM>N</DONE_AM>
                        <DONE_VOM/>
                        <URSACHE>2</URSACHE>
                        <DRINGLICH>2</DRINGLICH>
                        <ZIEL_DAT/>
                        <MZ_PARAM_LIST/>
                   </MAS_ZU>
                   <MAS_ZU MZ_NAM="ALLGEMEIN-ANMERKUNG">
                        <VALUE>2 Isolatoren</VALUE>
                        <BEMERKUNG/>
                        <INSP_AM/>
                        <INSP_VON/>
                        <DONE_AM/>
                        <DONE_VOM/>
                        <URSACHE>2</URSACHE>
                        <DRINGLICH/>
                        <ZIEL_DAT/>
                        <MZ_PARAM_LIST/>
                   </MAS_ZU>
                   <MAS_ZU MZ_NAM="Stange erdfaul/hohl">
                        <VALUE>J</VALUE>
                        <BEMERKUNG/>
                        <INSP_AM/>
                        <INSP_VON/>
                        <DONE_AM/>
                        <DONE_VOM/>
                        <URSACHE/>
                        <DRINGLICH/>
                        <ZIEL_DAT/>
                        <MZ_PARAM_LIST/>
                   </MAS_ZU>
                   <MAS_ZU MZ_NAM="Masttyp nicht normgerecht">
                        <VALUE>J</VALUE>
                        <BEMERKUNG/>
                        <INSP_AM/>
                        <INSP_VON/>
                        <DONE_AM/>
                        <DONE_VOM/>
                        <URSACHE/>
                        <DRINGLICH/>
                        <ZIEL_DAT/>
                        <MZ_PARAM_LIST/>
                   </MAS_ZU>
              </MZ_LIST>
         </INSP_PDA>
    </INSOBJ>
    Thanks for help.
    With best regards
    Nicole

  • Report or table to extract attributes linked to a user

    Hi all,
    I am looking for a standard report that I can use in order to extract the CAT attributes of my users.
    For sure it is possible one by one with FM BBP_READ_ATTRIBUTES but I need it for some hundred users.
    Is there a way without a z-report?
    Thanks and best regards
    AD

    Hi,
    Useful links:
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/srm/codeSample2-Reporttodisplayuserattributes
    Re: standard program/FM/Table which lists all user ids and their attributes
    BR,
    Deepti.

  • I need help. My ipad 2 was stuck in recovery mode. i tried to connect it to itunes and restore but after downloading the file and extracting the software there is a pop up message that says "the device is full" i dont know what to do. Its been 2 days now.

    I need help. My ipad 2 was stuck in recovery mode. i tried to connect it to itunes and restore but after downloading the file and extracting the software there is a pop up message that says "the device is full. Deleting files and emptying your recycle been will help you restore." how am i going to erase files if i can't open my ipad. i dont know what to do. Its been 2 days now. please help. thanks.

    yes i am sure. This are the exact words... "The iPad "iPad" could not be restored. The disk you are attempting to use is full. (Removing files and emptying the recycle bin will free up additional space". i tried some options, hard reset, redsnow, tinyumbrella but still it's stuck.

  • Bursting with translation and security attributes?

    Hi folks,
    I've been lurking on the forum for a while and despite not always finding a solution, existing threads normally pointed me in the right direction - so thanks :)
    I'm working on EBS 11.5.10 with the latest Bi-Publisher 5.6.3 (5472959) and bursting (5968876) patches installed.
    I have successfully done the following individual AR Invoice Bi-Publisher tasks:
    1. translated an invoice RTF template by attaching an xliff file to the data definition,
    2. applied security attributes to the template to restrict updates on the resulting PDF,
    3. burst a custom AR invoice print and emailed the resultant pdf's.
    The PDF generated by the combined Invoice print correctly applies the translation and security attributes; however when I run the "XML Publisher Report Bursting Program" to the XML file the resultant burst PDF's do not apply the translation or security attributes. I assume this a limitation of bursting control files? If so, is this on the list of future enhancements to Bi-Publisher?
    Here's an example of my control file document entry, I have included locale and pdf-security entries - these don't cause an error but equally don't generate the desired result (p.s. I know I'm emailing on a PRI filter - it's just a test):
    <xapi:document output-type="pdf" delivery="att_email">
    <xapi:template type="rtf"
    location="/usr/tmp/xxxINVOICE3.rtf"
    locale="fr-US"
    pdf-security="true" pdf-encryption-level="1" pdf-permissions-password="xxxxxx"
    filter=".//G_INVOICE_HEADER[PRINTING_OPTION='PRI']" >
    </xapi:template>
    </xapi:document>
    Thanks
    Dave

    =================
    ==Properties Idea's
    =================
    You would have happened to try applying the security stuff in the application for your template? Try that and see if the pdf properties get set.
    If that doesn't work your left with two options:
    1. create a java concurrent program and set the properties manually.
    2. Log a tar.
    =================
    ==local idea's
    =================
    Are you sure you don't have to create template config for the locale? i suspect that's why it's not applying the xliff translation. Also, your NLS_LANG needs to be set to FRENCH for the approriate template to be applied. If your logged-in as english your french format template will not be applied, neither will the translation. As an example you can query vl table and you'll only get american (us) but if you alter your session you'll get the translation for that language when your query the table.
    location="xdo://xxxAR.xxx_XML_PRINT.fr.US"
    try it out and see if that works. Note: This will only work if your session NLS_LANG is set to FRENCH.

  • How can I read the bootstrap files and extract the fragment-URLs and fragment-numbers in plain text?

    How can I read the bootstrap files of any HDS Live stream and extract the fragment-URLs and fragment-numbers in plain text?
    Could it be that it is some kind of compressed format in the bootstrap? Can I uncompress it wirh  f4fpackager.exe? Could not find any download for f4fpackager.exe. I would prefere less code to do so. Is there something in Java of JavaScript, that can extract the fragment-numbers?
    Thank you!

    Doesn't sound too hard to me. Your class User (the convention says to capitalize class names) will have an ArrayList or Vector in it to represent the queue, and a method to store a Packet object into the List. An array or ArrayList or Vector will hold the 10 user objects. You will find the right user object from packet.user_id and call the method.
    Please try to write some code yourself. You won't learn anything from having someone else write it for you. Look at sample code using ArrayList and Vector, there's plenty out there. Post in the forum again if your code turns out not to behave.

  • Front end Backend Modeling Configuration Reporting and Extraction.

    Hi..All
    Can Any one plz explain the terms "Front end","Back end" related to Modeling,Configuration,Reporting and Extraction.
    Thanks & Regards
    Jonn
    <u>[email protected]</u>

    Hi,
    Frontend is the reporting aspect, i.e Workbooks, queries, Web reporting, Crystal reports, etc.
    Its called the frontend as that's what the users see and they don't see what goes on in the 'backend' i.e Config and Extraction, data manipulations, etc.
    Modeling is used to design the cube, ODS, etc. Also modeling concepts can be used to design frontend queries as well.
    Cheers,
    Kedar

  • Global and Tp Attributes

    Hello Friends,
    I need to store some additional information in the DFF of OE_ORDER_HEADERS_ALL.
    The problem is that, all the columns from attribute1 to attribute20 have already been used. It has been observed that, there are some TPATTRIBUTES 1 to 15 as well as Global attributes.
    Only thing which I understood is, TP and Global attributes are used for country specific and localizaiton purposes, however since we are not using Trading partner, and these columns are free.. Is it feasible (without any impact) to use them? and in that case, Will the form of Sales Order show these additional DFFs?
    I tried to check, however Global attribute DFF was not found on the form , for TP attributes, it was found but was covered by field Order Source .. Any suggestions?
    Best Regards

    Hi
    Extended attribute :-
    Group of attribute value hold this values .
    from 001 to 10000 - product category . you can mention
    otherwise PRCAT = 001 ,002......10,000 you have to make one by one single entry.
    hope you understand now the use of extended attributes.
    br
    muthu

  • Display entity-attributes and global-attributes in the same screen

    Hi,
    I have a question about entity.
    Is it possible to display in the same screen, entity-attributes and global-attributes?
    thanks
    Rosalia

    Hi Rosalia,
    You can only display attributes from the current entity and the entity or entities that it is contained by (the parent entities).
    So if you had the following data model
    Global
    ..the person
    ...the income
    the person is contained by global.
    the income is contained by the person (which is contained by global).
    If you want to create a person-level question screen, you can display global attributes on that screen by using subsitution like %global_field_1%. You cannot, however, input global attributes on that screen (ONLY attributes belonging to the person)
    If you want to create an income-level question screen, you can display attributes from the person such as "tell us about %person_name%'s income..." as well as global attributes. Again, you cannot input person or global attributes on that screen (ONLY attributes belonging to the income)
    However it only works from child-to-parent containment relationships! You cannot have a global question screen which loops through the person instances and displays attributes from the person, or from the income out-of-the-box.
    We have managed to implement this using custom controls.
    You can map individual attributes back up to the parent level, and then display them,
    such as
    the first person's name = InstanceValueIf(the people, the person's name, the person's id = 1)
    the first person's name is now a global attribute and can be displayed on global question screens.
    Hope this helps!
    Ben

  • File and boolean attribute on item

    Hi,
    I work with Oracle9iAS Portal PL/SQL API (9.0.2.6).
    I define an item type (CAID = 213/ ID = 37399) with several attributes. When I try to create/modify an item I have problems with boolean attributes and file attributes.
    In case of boolean attributes, I'm not able to set the value to true. I try with several values (IS_ON, True, 1) but the attribute is still set to false. Is there anything wrong with the value I assign to the attribute before creating the item ? When I try to create the item and then modifying the attribute, the value stay to false.
    For the file attributes, I use the upload_blob function inside wwsbr_api and the file appear in the wwdoc_document table. I set the file attribute value with the return value of the upload_blob function.
    When I call the add_item_post_upload, an error occurs (ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException : -29532)
    Is this a bug or not ?
    Thanks Eddy.
    For help see my sample code below :
    (ID of attribute, page, region are correct. I also test each type of attribute separately)
    declare
    l_master NUMBER;
    l_store portal.wwsto_api_session;
    l_custom_attribute portal.wwsbr_type.array := portal.wwsbr_type.empty;
    l_custom_attribute_id portal.wwsbr_type.array := portal.wwsbr_type.empty;
    l_custom_attribute_caid portal.wwsbr_type.array := portal.wwsbr_type.empty;
    l_custom_attribute_data_type portal.wwsbr_type.array := portal.wwsbr_type.empty;
    l_str VARCHAR2(100);
    l_Blob BLOB;
    l_filename VARCHAR2(100);
    begin
    -- set context
    portal.wwctx_api.SET_CONTEXT('ctx','ctx01','');
    -- load a session (Allow use of set_Attribute ...)
    DBMS_OUTPUT.put_line('Load session');
    l_store := portal.wwsto_api_session.load_session('ctx','ctx');
    -- set parameters
    -- item type = 'Item_ed'
    l_store.set_attribute('ITEM_TYPE', 37399); -- Item type id
    l_store.set_attribute('ITEM_CAID', 213); -- Item type caid (page group owner of item type)
    l_store.set_attribute('PAGE_GROUP_ID', 213); -- Page group
    l_store.set_attribute('FOLDER_ID', 37179); -- Page within page group
    l_store.set_attribute('REGION_ID', 3216); -- Region id within page
    -- see wwv_user_corners to determine template of page
    -- see wwsbr_all_folder_regions for region display_name and region id (for template)
    -- Get date format to insert right date string
    SELECT DISTINCT value
    INTO l_str
    FROM v$nls_parameters
    WHERE parameter = 'NLS_DATE_FORMAT';
    dbms_output.put_line('date format ins : ' || l_str);
    -- define attributes (for example, id are hardcoded
    DBMS_OUTPUT.put_line('Define attributes');
    -- 1080 = PRODUCT_CODE
    l_custom_attribute(1) := 'MEHI';
    l_custom_attribute_id(1) := 1080;
    l_custom_attribute_caid(1) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(1) := 'text';
    -- 1081 = PRODUCT_AUTHOR
    l_custom_attribute(2) := 'ESTAT';
    l_custom_attribute_id(2) := 1081;
    l_custom_attribute_caid(2) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(2) := 'text';
    -- 1469 = LANGUAGE
    l_custom_attribute(3) := 'fr';
    l_custom_attribute_id(3) := 1469;
    l_custom_attribute_caid(3) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(3) := 'text';
    -- 3 = title
    l_custom_attribute(4) := 'title value';
    l_custom_attribute_id(4) := 3;
    l_custom_attribute_caid(4) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(4) := 'text';
    -- 50 = wwsbr_text_
    l_custom_attribute(5) := 'wwsbr_text_ value';
    l_custom_attribute_id(5) := 50;
    l_custom_attribute_caid(5) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(5) := 'text';
    -- 1464 = Release date
    l_custom_attribute(6) := TO_CHAR(TO_DATE('21-JAN-2004 10:00 AM', 'DD-MON-YYYY HH12:MI PM'),l_str);
    l_custom_attribute_id(6) := 1464;
    l_custom_attribute_caid(6) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(6) := 'date';
    -- 1108 = download
    l_custom_attribute(7) := 'http://www.oracle.com/';
    l_custom_attribute_id(7) := 1108;
    l_custom_attribute_caid(7) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(7) := 'url';
    -- 1485 = CDROM
    l_custom_attribute(8) := '1';
    l_custom_attribute_id(8) := 1485;
    l_custom_attribute_caid(8) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(8) := 'boolean';
    -- 1111 = PAGE_NB
    l_custom_attribute(8) := '1';
    l_custom_attribute_id(8) := 1111;
    l_custom_attribute_caid(8) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(8) := 'number';
    -- 1783 = COVER_IMAGE
    -- get image
    SELECT BANNER
    INTO l_Blob
    FROM metadata_tbl
    WHERE PRODUCT_CODE = 'caa10000';
    -- upload image in repository
    l_filename := portal.wwsbr_api.upload_blob('BANNERupload',l_Blob, 'image/pjpeg');
    DBMS_OUTPUT.put_line('filename : ' || l_filename);
    l_custom_attribute(9) := l_filename;
    l_custom_attribute_id(9) := 1783;
    l_custom_attribute_caid(9) := portal.wwsbr_api.SHARED_OBJECTS; -- = 0
    l_custom_attribute_data_type(9) := 'file';
    DBMS_OUTPUT.put_line('Insert item starts');
    l_master := portal.wwsbr_api.add_item_post_upload(
    p_caid =&gt; l_store.get_attribute_as_number('PAGE_GROUP_ID'),
    p_folder_id =&gt; l_store.get_attribute_as_number('FOLDER_ID'),
    p_display_name =&gt; 'Insert : MEHI',
    p_type_id =&gt; l_store.get_attribute_as_number('ITEM_TYPE'),
    p_type_caid =&gt; l_store.get_attribute_as_number('ITEM_CAID'),
    p_region_id =&gt; l_store.get_attribute_as_number('REGION_ID'), --to set or default
    p_display_option =&gt; portal.WWSBR_API.IN_PLACE,
    -- p_category_id in number default general_category,
    -- p_category_caid in number default shared_objects,
    -- p_perspectives in g_perspectiveidarray default g_perspectiveidemptyarray,
    -- p_perspectives_caid in g_caid_array default g_empty_caid_array,
    -- p_author in varchar2 default wwctx_api . get_user,
    -- p_image_name =&gt; l_filename,
    -- p_image_alignment in varchar2 default align_left,
    -- p_description in varchar2 default null,
    -- p_keywords in varchar2 default null,
    -- p_file_name =&gt;l_filename, --in varchar2 default null,
    p_text =&gt; 'text field',
    -- p_url in varchar2 default null,
    -- p_plsql in varchar2 default null,
    -- p_plsql_execute_mode in varchar2 default null,
    -- p_plsql_execute_user in varchar2 default null,
    -- p_folderlink_id in number default null,
    -- p_folderlink_caid in number default null,
    -- p_publish_date in varchar2 default null,
    -- p_expire_mode in varchar2 default permanent,
    -- p_expiration in varchar2 default null,
    -- p_master_item_id in number default null,
    -- p_hide_in_browse in number default no,
    -- p_checkable in number default no,
    -- p_parent_item_id in number default 0,
    p_attribute_id =&gt; l_custom_attribute_id,
    p_attribute_caid =&gt; l_custom_attribute_caid,
    p_attribute_data_type =&gt; l_custom_attribute_data_type,
    p_attribute_value =&gt; l_custom_attribute
    DBMS_OUTPUT.put_line('Insert item ends. Item identifier : ' || l_master);
    -- Invalidate cache from SQLPLUS
    portal.wwpro_api_invalidation.execute_cache_invalidation;
    DBMS_OUTPUT.put_line('Cache invalidated');
    -- Drop session
    portal.wwsto_api_session.drop_session('ctx','ctx');
    -- Clean context
    portal.wwctx_api.clear_context;
    COMMIT;
    exception
    WHEN portal.wwctx_api.AUTHENTICATION_EXCEPTION THEN
    DBMS_OUTPUT.PUT_LINE('AUTHENTICATION_EXCEPTION : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.CANNOT_INSERT_DOCUMENT THEN
    DBMS_OUTPUT.PUT_LINE('CANNOT INSERT DOCUMENT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.DUPLICATE_FOLDER THEN
    DBMS_OUTPUT.PUT_LINE('DUPLICATE_FOLDER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.DUPLICATE_ID THEN
    DBMS_OUTPUT.PUT_LINE('DUPLICATE_ID : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.DUPLICATE_NAME THEN
    DBMS_OUTPUT.PUT_LINE('DUPLICATE_NAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.FOLDER_VERSIONING_IS_AUDIT THEN
    DBMS_OUTPUT.PUT_LINE('FOLDER_VERSIONING_IS_AUDIT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.FOLDER_VERSIONING_IS_NONE THEN
    DBMS_OUTPUT.PUT_LINE('FOLDER_VERSIONING_IS_AUDIT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ILS_DISABLED THEN
    DBMS_OUTPUT.PUT_LINE('ILS_DISABLED : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ILS_DISABLED_FOR_ITEM THEN
    DBMS_OUTPUT.PUT_LINE('ILS_DISABLED_FOR_ITEM : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_CAID THEN
    DBMS_OUTPUT.PUT_LINE('INVALID CAID : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_CATEGORY THEN
    DBMS_OUTPUT.PUT_LINE('INVALID CATEGORY : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_EXPIRE_DATE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_DATE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_EXPIRE_DATE_FORMAT THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_DATE_FORMAT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_EXPIRE_NUMBER THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_EXPIRE_NUMBER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_FOLDER THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_FOLDER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_FOLDER_ID THEN
    DBMS_OUTPUT.PUT_LINE('INVALID FOLDER ID : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_ITEM_ID THEN
    DBMS_OUTPUT.PUT_LINE('INVALID ITEM ID : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_ITEMTYPE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID ITEMTYPE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_MOVE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID MOVE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_NAME THEN
    DBMS_OUTPUT.PUT_LINE('INVALID NAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_NUMBER THEN
    DBMS_OUTPUT.PUT_LINE('INVALID NUMBER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_PERSPECTIVE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID PERSPECTIVE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_PLSQL_EXECUTE_USER THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_PL/SQL_EXECUTE_USER : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_PUBLISH_DATE_FORMAT THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_PUBLISH_DATE_FORMAT : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_PUBLISH_DATE_VALUE THEN
    DBMS_OUTPUT.PUT_LINE('INVALID_PUBLISH_DATE_VALUE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.INVALID_USERNAME THEN
    DBMS_OUTPUT.PUT_LINE('INVALID USERNAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ITEM_CREATION_ERROR THEN
    DBMS_OUTPUT.PUT_LINE('ITEM_CREATION ERROR : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ITEM_NOT_FOUND_ERROR THEN
    DBMS_OUTPUT.PUT_LINE('ITEM NOT FOUND ERROR : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.ITEM_UPDATE_ERROR THEN
    DBMS_OUTPUT.PUT_LINE('ITEM_UPDATE_ERROR : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.MISSING_DISPLAY_NAME THEN
    DBMS_OUTPUT.PUT_LINE('MISSING DISPLAY NAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.MISSING_ITEM_TYPE THEN
    DBMS_OUTPUT.PUT_LINE('MISSING ITEM TYPE : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.MISSING_NAME THEN
    DBMS_OUTPUT.PUT_LINE('MISSING NAME : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.MISSING_PLSQL_EXECUTE_USER THEN
    DBMS_OUTPUT.PUT_LINE('MISSING plsql execute user : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NAME_TOO_LONG THEN
    DBMS_OUTPUT.PUT_LINE('name too long : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NO_ITEM_REGION THEN
    DBMS_OUTPUT.PUT_LINE('not item region : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NO_MASTER_ITEM_ID THEN
    DBMS_OUTPUT.PUT_LINE('no master item id : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NOT_ENOUGH_PRIVS THEN
    DBMS_OUTPUT.PUT_LINE('not enough privs : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NULL_EXPIRE_DATE THEN
    DBMS_OUTPUT.PUT_LINE('null expire date : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.NULL_EXPIRE_NUMBER THEN
    DBMS_OUTPUT.PUT_LINE('null expire number : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.PERMISSION_DENIED THEN
    DBMS_OUTPUT.PUT_LINE('permission denied : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.PLSQL_REQUIRED THEN
    DBMS_OUTPUT.PUT_LINE('plsql required : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.QUOTA_EXCEEDED THEN
    DBMS_OUTPUT.PUT_LINE('quota exceeded : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.REQD_ATTR_MISSING THEN
    DBMS_OUTPUT.PUT_LINE('reqd attr missing : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.UNKNOWN_ERROR THEN
    DBMS_OUTPUT.PUT_LINE('unknown error : ' || sqlerrm);
    ROLLBACK;
    WHEN portal.wwsbr_api.URL_REQUIRED THEN
    DBMS_OUTPUT.PUT_LINE('url required : ' || sqlerrm);
    ROLLBACK;
    when OTHERS then
    DBMS_OUTPUT.PUT_LINE('OTHERS : ' || sqlerrm || ' : ' || sqlcode);
    ROLLBACK;
    end;

    Hi Eddy:
    On Friday, we put in a TAR with Oracle support about the identical problem. When editing an item using the API, the boolean attributes always reset. The values of the boolean attributes aren't even being changed. The only reason we need to set them again is the limitation of the API where you have to feed all attributes back in.
    So far, Oracle has said it sounds like a bug and they want to know the exact sequence of steps to repeat it.
    Rgds/Mark M.
    Portal 9.0.2.6

  • How to get nodes and its attributes of an XML file usiong DOM parsing?

    how to get nodes and its attributes of an XML file usiong DOM parsing?
    i am new to XML parsing.......
    Thanking you........

    import org.w3c.dom.Document;
    import org.w3c.dom.*;
    import javax.xml.parsers.DocumentBuilderFactory;
    import javax.xml.parsers.DocumentBuilder;
    import org.xml.sax.SAXException;
    import org.xml.sax.SAXParseException;      ...
    //Setup the document
    DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance();
         DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
         Document doc = docBuilder.parse (new File("MY_XML_FILE.xml"));
    //get elemets by name
         String elementValue = doc.getElementsByTagName("MY_ELEMENT").item(0).getTextContent();
    //This method can return multiple nodes, in this instance I get item(0) , first nodeRead the api for other methods of getting data.

  • [svn] 4143: Fixed problem with metadata in SelectionFormatTextStyles. as so that named colors work for selectionColor, unfocusedSelectionColor, and inactiveSelectionColor attributes on Gumbo components.

    Revision: 4143
    Author: [email protected]
    Date: 2008-11-19 14:53:40 -0800 (Wed, 19 Nov 2008)
    Log Message:
    Fixed problem with metadata in SelectionFormatTextStyles.as so that named colors work for selectionColor, unfocusedSelectionColor, and inactiveSelectionColor attributes on Gumbo components.
    Thanks, Glenn!
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-18070
    Reviewer: Glenn
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18070
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/styles/metadata/SelectionFormatTextStyles .as
    flex/sdk/trunk/frameworks/projects/wireframe/bundles.properties

    Revision: 4143
    Author: [email protected]
    Date: 2008-11-19 14:53:40 -0800 (Wed, 19 Nov 2008)
    Log Message:
    Fixed problem with metadata in SelectionFormatTextStyles.as so that named colors work for selectionColor, unfocusedSelectionColor, and inactiveSelectionColor attributes on Gumbo components.
    Thanks, Glenn!
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-18070
    Reviewer: Glenn
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18070
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/styles/metadata/SelectionFormatTextStyles .as
    flex/sdk/trunk/frameworks/projects/wireframe/bundles.properties

  • Develop a report to migrate territories and its attributes

    Hi All,
    My requirement -> create territories, assign BP and attributes to it through a custom report. Using BAPI BAPI_TERRITORY_CREATE I manage to create territories but assign BP and Attributes i did not find any FM and BAPI. kindly guide me how i can assign BP and Attributes to a territories.
    By debugging transaction crmm_terrman i found some FMs but not working for me.
    regards,
    Noor Gani

    Hello Noor,
    I'm not sure but if you are talking about the marketing attributes, you can definitely use FM - CRM_MKTBP_ASSIGN_ATTRIBUT_TAB
    You need to pass the profile id, partner id and marketing attributes data. Thats it.
    I think the FM you ar eusing for terrritory is fine. It should work.
    I hope this helps.
    Thanks
    Vishal

  • [JS-CS4] - How to read the XML Element and its Attributes

    Dear All,
      I have the doubt regarding: reading the xmlElement and its attributes.
    Here I droping the xml script
    //============= Start ======================//
    var myDoc = app.activeDocument;
    var Fpath = File("../Projects/Entity_map.xml");
      if (Fpath.exists)
       Fpath.open("r");
       var Cont= Fpath.read();
      var roots = new XML(Cont);
      var myEveryName = new Array();
      var myEveryContent = new Array();
      var myEveryAttributes = new Array();
      traverse(roots);
    //$.writeln(myEveryName);
    //$.writeln(myEveryContent);
    $.writeln(myEveryAttributes.length);
    for(var i=0; i<myEveryAttributes.length; i++)
      $.writeln(myEveryAttributes[i]);
    function traverse(tree) {
        myEveryName.push(tree.name());
    myEveryContent.push(tree.text());
      myEveryAttributes.push(tree.getAttribute);
    // you get the contents by using .text() insted of .name()
        if(tree.elements().length() > 0) {
            for(var i=0; i<tree.elements().length(); i++) {
                traverse(tree.elements()[i]);
    //============== End =====================//
    and the XML Structure is
    //===============XML =====================//
    <?xml version="1.0" encoding="UTF-8"?>< Entity_Convertion>
    < Entitys char="Ç" GID="173"/></ 
    Entity_Convertion>
    //===============End ====================//
    Here I'm getting the XML Elements and its contents, but not xmlAttributes.
    Please any one can help me, then I will appreciate...
    Thanks & Regards
    T.R.Harihara SudhaN

    Dear All,
      I have the doubt regarding: reading the xmlElement and its attributes.
    Here I droping the xml script
    //============= Start ======================//
    var myDoc = app.activeDocument;
    var Fpath = File("../Projects/Entity_map.xml");
      if (Fpath.exists)
       Fpath.open("r");
       var Cont= Fpath.read();
      var roots = new XML(Cont);
      var myEveryName = new Array();
      var myEveryContent = new Array();
      var myEveryAttributes = new Array();
      traverse(roots);
    //$.writeln(myEveryName);
    //$.writeln(myEveryContent);
    $.writeln(myEveryAttributes.length);
    for(var i=0; i<myEveryAttributes.length; i++)
      $.writeln(myEveryAttributes[i]);
    function traverse(tree) {
        myEveryName.push(tree.name());
    myEveryContent.push(tree.text());
      myEveryAttributes.push(tree.getAttribute);
    // you get the contents by using .text() insted of .name()
        if(tree.elements().length() > 0) {
            for(var i=0; i<tree.elements().length(); i++) {
                traverse(tree.elements()[i]);
    //============== End =====================//
    and the XML Structure is
    //===============XML =====================//
    <?xml version="1.0" encoding="UTF-8"?>< Entity_Convertion>
    < Entitys char="Ç" GID="173"/></ 
    Entity_Convertion>
    //===============End ====================//
    Here I'm getting the XML Elements and its contents, but not xmlAttributes.
    Please any one can help me, then I will appreciate...
    Thanks & Regards
    T.R.Harihara SudhaN

Maybe you are looking for