Query: Data length of InfoObjects

Hi all,
I am new to BW. I'll try to put my question as best as I can.
Let's say I create a new infoobject(characteristic) and I give its data type as CHAR and length as 12. Now while loading data will it be a problem if the data for this infoobject is not 12 characters long? I mean what if the length is less than 12 characters?
Thanks,
Satyajit.

Hi Satyajit,
No..It will not be a problem. It is similar to any database defintion where you define the maximum length. So even if it is less it would not be an issue.
Bye
Dinesh

Similar Messages

Query Data Block issues

We have a legacy Forms and Reports application(~750 items combined). I suspect the applications were developed initially under 6i, but they work quite well under 10GR2, and is testing well under 11GR2 (which we plan on migrating to soon). We ran into an issue the other day for Data Query Blocks, and wanted your expert opinion on it.
Due to a change in business requirements, we recently had to increase the length of a database field (from 20 to 30). We went into Forms Developer, made the appropriate changes, and recompiled them all successfully. Everything *seems* to work fine, but we noticed we get failures on any item that tries to utilize that extra 10 characters. Apparently this is because the Query Data Block seems to use a cached/stale copy of the database field sizes, and still expects a size of 20! What we realized now is that we have to go into each of those forms, and REFRESH the Data Block (through the Data Block Wizard) for every one of them.
My question is this: is there anyway to force the Form to refresh those Query Data Blocks absent going into each one and REFRESHING it? We've tried compiling through Forms Developer, and through Batch Compiles, and nothing seems to get those cached copies to update. I'd really prefer to tackle this issue once and for all since we are prepping for migration testing. Frankly I suspect the table space was tweaked a good bit over the years since development (before I ever got here), and if they didn't REFRESH those Data Blocks properly, a great many of the Forms will be suffering this same cached/stale view problem.
Appreciate your thoughts,
Dave

Q_Stephenson,
That's an excellent suggestion. I have seen vague hints and allegations of Forms manipulation using that method, but never felt comfortable with my overall knowledge(*) of Forms to look at it that deep. I think it's time to clear some space and dig into the topic for a better look.
Thank you,
Dave
(*) The majority of my programming background is in Java; it's only been recently that I've had to really dig deep into Forms.

Querying Data from 3rd Party System

We would like to query data from a 3rd party (non-SAP) system. Our BW is an MSSQL DB and the 3rd party is also an MSSQL DB. We do not want to physically load the data from the external system we just want to use the BW query tools to display the data.
Is this possible? I thought this is what a Remote Cube would be used for but SAP's instructions on Remote Cubes are vague and confusing.
       1.      In BW, create a source system for the external system that you want to use.
       2.      Define the required InfoObjects.
       3.      Load the master data:
·        Create a master data InfoSource for each characteristic
·        Load texts and attributes
       4.      Define the RemoteCube
       5.      Define the queries based on the RemoteCube

Hi Jon,
SAP RemoteCube is an InfoProvider. This is a special RemoteCube that allows
you to define queries with direct access to transaction data in other SAP systems. SAP RemoteCubes are defined on the basis of an InfoSource with flexible updating, and assume the characteristics and key figures of the InfoSource.
Use/Data Flow
Unlike with other RemoteCubes, it is not necessary to program extractors. The
same extractors are used to select data in the source system that are also used when replicating data into the BW. When executing a query, each navigation step sends a request to the extractors for the assigned source systems. In addition, characteristics selection and selection criteria for these characteristics are transformed to fields in the transfer structure, in accordance with the transfer rules. They are transferred to the extractor in this form. The delivered datasets run through the transfer rules in BW and are filtered once again in the query.
In your case Remote cube can be an option .
Cheers
Raja

How to Compare Data length of staging table with base table definition

Hi,
I've two tables :staging table and base table.
I'm getting data from flatfiles into staging table, as per requirement structure of staging table and base table(length of each and every column in staging table is 25% more to dump data without any errors) are different for ex :if we've city column with varchar length 40 in staging table it has 25 in base table.Once data is dumped into staging table I want to compare actual data length of each and every column in staging table with definition of base table(data_length for each and every column from all_tab_columns) and if any column differs length I need to update the corresponding row in staging table which also has a flag called err_length.
so for this I'm using cursor c1 is select length(a.id),length(a.name)... from staging_table;
cursor c2(name varchar2) is select data_length from all_tab_columns where table_name='BASE_TABLE' and column_name=name;
But we're getting data atonce in first query whereas in second cursor I need to get each and every column and then compare with first ?
Can anyone tell me how to get desired results?
Thanks,
Mahender.

This is a shot in the dark but, take a look at this example below:
SQL> DROP TABLE STAGING;
Table dropped.
SQL> DROP TABLE BASE;
Table dropped.
SQL> CREATE TABLE STAGING
2 (
3          ID              NUMBER
4 ,       A               VARCHAR2(40)
5 ,       B               VARCHAR2(40)
6 ,       ERR_LENGTH      VARCHAR2(1)
7 );
Table created.
SQL> CREATE TABLE BASE
2 (
3          ID      NUMBER
4 ,       A       VARCHAR2(25)
5 ,       B       VARCHAR2(25)
6 );
Table created.
SQL> INSERT INTO STAGING VALUES (1,RPAD('X',26,'X'),RPAD('X',25,'X'),NULL);
1 row created.
SQL> INSERT INTO STAGING VALUES (2,RPAD('X',25,'X'),RPAD('X',26,'X'),NULL);
1 row created.
SQL> INSERT INTO STAGING VALUES (3,RPAD('X',25,'X'),RPAD('X',25,'X'),NULL);
1 row created.
SQL> COMMIT;
Commit complete.
SQL> SELECT * FROM STAGING;
        ID A                                        B                                        E
         1 XXXXXXXXXXXXXXXXXXXXXXXXXX               XXXXXXXXXXXXXXXXXXXXXXXXX
         2 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXX
         3 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXX
SQL> UPDATE STAGING ST
2 SET     ERR_LENGTH = 'Y'
3 WHERE   EXISTS
4          (
5                  WITH    columns_in_staging AS
6                  (
7                          /* Retrieve all the columns names for the staging table with the exception of the primary key column
8                           * and order them alphabetically.
9                           */
10                          SELECT COLUMN_NAME
11                          ,       ROW_NUMBER() OVER (ORDER BY COLUMN_NAME) RN
12                          FROM    ALL_TAB_COLUMNS
13                          WHERE   TABLE_NAME='STAGING'
14                          AND     COLUMN_NAME != 'ID'
15                          ORDER BY 1
16                  ),      staging_unpivot AS
17                  (
18                          /* Using the columns_in_staging above UNPIVOT the result set so you get a record for each COLUMN value
19                           * for each record. The DECODE performs the unpivot and it works if the decode specifies the columns
20                           * in the same order as the ROW_NUMBER() function in columns_in_staging
21                           */
22                          SELECT ID
23                          ,       COLUMN_NAME
24                          ,       DECODE
25                                  (
26                                          RN
27                                  ,       1,A
28                                  ,       2,B
29                                  ) AS VAL
30                          FROM            STAGING
31                          CROSS JOIN      COLUMNS_IN_STAGING
32                  )
33                  /*      Only return IDs for records that have at least one column value that exceeds the length. */
34                  SELECT ID
35                  FROM
36                  (
37                          /* Join the unpivoted staging table to the ALL_TAB_COLUMNS table on the column names. Here we perform
38                           * the check to see if there are any differences in the length if so set a flag.
39                           */
40                          SELECT STAGING_UNPIVOT.ID
41                          ,       (CASE WHEN ATC.DATA_LENGTH < LENGTH(STAGING_UNPIVOT.VAL) THEN 'Y' END) AS ERR_LENGTH_A
42                          ,       (CASE WHEN ATC.DATA_LENGTH < LENGTH(STAGING_UNPIVOT.VAL) THEN 'Y' END) AS ERR_LENGTH_B
43                          FROM    STAGING_UNPIVOT
44                          JOIN    ALL_TAB_COLUMNS ATC     ON ATC.COLUMN_NAME = STAGING_UNPIVOT.COLUMN_NAME
45                          WHERE   ATC.TABLE_NAME='BASE'
46                  )       A
47                  WHERE   COALESCE(ERR_LENGTH_A,ERR_LENGTH_B) IS NOT NULL
48                  AND     ST.ID = A.ID
49          )
50 /
2 rows updated.
SQL> SELECT * FROM STAGING;
        ID A                                        B                                        E
         1 XXXXXXXXXXXXXXXXXXXXXXXXXX               XXXXXXXXXXXXXXXXXXXXXXXXX                Y
         2 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXX               Y
         3 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXHopefully the comments make sense. If you have any questions please let me know.
This assumes the column names are the same between the staging and base tables. In addition as you add more columns to this table you'll have to add more CASE statements to check the length and update the COALESCE check as necessary.
Thanks!

Advantage of data transfer from infoobject to ODS

Hi,
1)what is the advantage of bringing data first in infoobject and then moving into DSO ?? why cant we directly bring into DSO?why we need infoobject in between
2) can we use infocube in Infoset? if no then y?

Hello,
You don't normally feed data from InfoObject to DSO. You normally feed InfoObject and DSO. The DSO can only have the key of the InfoObject, everything else related to that InfoObject is already loaded.
For example you have InfoObject employee. This InfoObject can be categorized by this:
employee_key employee_name employee_addr
1 xpto bla bla bla
In the DSO you can only feed the key of the employee, in this example 1. With InfoObjecte loaded you can use a relation of the key to read the other fields in the query, in this example you could read employee name and address in the query created over the DSO even if DSO only has the employee key.
InfoSet previously (in BW 3.x) didn't support InfoCubes, because InfoCubes isn't a flat table like a DSO or InfoObject tables.
Now SAP manage to support it under the new version of Netweaver 2004s BI 7.
Diogo.

Use evdre to query data from a SQL View

Hi all
I believe that it is possible to use evdre to query data from a SQL View. If this is possible then how does one go about setting it up in the evdre options (assuming that the view has already been created)?
Regards,
Byron

Byron, perhaps this is no longer supported, it might be worth opening up a case at service.sap.com on this. However, I did find the following on Page 11 of the "Usages and Considerations of EVDRE" pdf file. This doc is imbedded in the helpfile for BPC 7 SP5 (which was released in August of 2009, well after note 1315011 was last updated.
It looks like you are limited to one custom view per application, since you have to name the view in a parameter at the APPLICATION level. Go into BPC Administration, login to the application related to the custom view, choose "Set Application Parameters" and enter the name of the view to the Application Parameter called "EVDRE_QUERYVIEWNAME" If it is not listed, go ahead and create it at the bottom of the Application parameter screen.
Also: I interpreted the following info from Page 10 of the same doc:
In your EVDRE, set the following options:
QueryEngine: MANUAL
QueryType: enter either NEXJ OR TUPLE see below:
NEXJ - Use two-dimensional queries using the nonemptycrossjoin function
TUPLE - Use two-dimensional queries using tuples"
And I'm assuming you'd enter a Y for the following two parameters:
QueryViewName
"..to enforce the query engine to use a used-defined SQL view of the fact tables, when trying to read the values using SQL queries. This option is typically used in conjunction with the SQLOnly option (see below). "
Option SQLOnly
"..to enforce the query engine to only execute SQL queries, when reading data. This can be achieved using this option."

Data length error in record 86.

Data length error in record 86.
Message no. FV147
Diagnosis
An error occurred in the processing of the data to be imported. It is highly probable that this is a data error.
Contact your data provider.
System Response
Any account statement processing currently underway and any outstanding is being terminated.
Procedure
Check the structure of the supplied data. If the statement data you have obtained is error-free, you can simply restart the program. All those statements which have already been imported correctly will not be reimported.
{1:F01SCBLINBBXXXX3446100003}{2:O9400634140719SCBLINBBXXXX34461000031407190634N}{3:{108:00000000000718}}{4:
:20:14071905fr309439
:25:52205785839
:28C:611
:60F:D140718INR792788,04
:61:1407180718CR100000,00N169NONREF
:86:IN36701407187774 VIJBH14199069837
IN36701407187774 VIJBH14199069837
AGARWAL AGENCIES
:61:1407180718CR150000,00N169NONREF
:86:IN36701407187251 SBIN414199017384
IN36701407187251 SBIN414199017384
EAGLE FOOTWERE
:61:1407180718CR100000,00N169NONREF
:86:IN36701407187052 SAA96678573
IN36701407187052 SAA96678573
TANVEER TRADERS
:61:1407180718CR98000,00N169NONREF
:86:IN36701407186828 SBIN314199982628
IN36701407186828 SBIN314199982628
MODERN AGENCY
:61:1407180718CR179000,00N169NONREF
:86:IN36701407186029 SAA96670577
IN36701407186029 SAA96670577
BALAJI ENTERPRISES
:61:1407180718CR60000,00N169NONREF
:86:IN36701407185397 367845438
IN36701407185397 367845438
SAKSHI ENTERPRISES
:61:1407180718CR2000000,00N169NONREF
:86:IN3670140718H568 SBIN414199360804
IN3670140718H568 SBIN414199360804
RELAXO FOOTWEARS LIMITED
:61:1407180718CR38000,00N169NONREF
:86:IN3670140718G554 CBINH14199566672
IN3670140718G554 CBINH14199566672
WONDER WALK AGENCIES
:61:1407180718CR113000,00N169NONREF
:86:IN3670140718F851 JAKA140718621672
IN3670140718F851 JAKA140718621672
JYOTI SALES PROP MR AMIT VOHRA S
:61:1407180718CR54200,00N169NONREF
:86:IN3670140718F006 BKIDN14199343033
IN3670140718F006 BKIDN14199343033
SHAH FOOT WEAR
:61:1407180718CR64000,00N169NONREF
:86:IN3670140718F094 BKIDN14199343132
IN3670140718F094 BKIDN14199343132
MUSKAN TRADERS
:61:1407180718CR114500,00N169NONREF
:86:IN3670140718F423 SBIN414199302946
IN3670140718F423 SBIN414199302946
GOUTAM DISTRIBUTORS
:61:1407180718CR63000,00N169NONREF
:86:IN3670140718D651 SD1141261589
IN3670140718D651 SD1141261589
M K FOOTWEAR
:61:1407180718CR67913,00N169NONREF
:86:IN3670140718D057 SBIN414199247753
IN3670140718D057 SBIN414199247753
SSS PG STORES
:61:1407180718CR130000,00N169NONREF
:86:IN3670140718D183 UTBIN14199275937
IN3670140718D183 UTBIN14199275937
GOPAL SHOES
:61:1407180718CR48000,00N169NONREF
:86:IN3670140718C628 CBINH14199546949
IN3670140718C628 CBINH14199546949
AGGARWAL FOOTWEAR
:61:1407180718DR5000000,00N506PIRLXOIN01A00468
PIRLXOIN01A00468
:86:PIRLXOIN01A00468 SCBLR12014071800003757
CASH SCBLR12014071800003757
RELAXO FOOTWEARS LIMITED
SIN09373C0000423 00001 PIRLXOIN01A0
0468
PIRLXOIN01A00468
:61:1407180718DR4000000,00N506PIRLXOIN01A00469
PIRLXOIN01A00469
:86:PIRLXOIN01A00469 SIN09373Q0000468
PIRLXOIN01A00469-SIN09373Q0000468
SB3670140718HK96
SIN09373C0000424-00001 PIRLXOIN01A0
0469
:61:1407180718DR1699195,25N699TRF
:86:316031790865 PAY001
316031790865 PAY001
GRAND WISE ENTERPRISES LIMITED
AKMP037
USD28,030.8 60.5755/INR743.76 1
DEBIT IMEX CUSTOMER A/C
:61:1407180718CR480000,00N195NONREF
:86:IL36701407182157 BARBR52014071800734481
CASH BARBR52014071800734481
APNA FOOT WEAR
SENDER IFSCBARB0CHARMI
IL36701407182157
:61:1407180718CR235000,00N195NONREF
:86:IL36701407185517 SBINR52014071801147506
CASH SBINR52014071801147506
PRAKASH FOOT WEAR
FUND TRF FRM 33174969142 TO52205785
SENDER IFSCSBIN0016310
IL36701407185517
:61:1407180718CR500000,00N195NONREF
:86:IL36701407185083 SBINR12014071801142317
CASH SBINR12014071801142317
MODERN FOOTWEARS
SENDER IFSCSBIN0001521
IL36701407185083
:61:1407180718CR800000,00N195NONREF
:86:IL36701407184746 HDFCR52014071851912408
CASH HDFCR52014071851912408
FASHION SQUARE
SENDER IFSCHDFC0000412
IL36701407184746
:61:1407180718CR332000,00N195NONREF
:86:IL36701407184713 SBINR52014071801140001
CASH SBINR52014071801140001
WINGS POLYMERS
SENDER IFSCSBIN0001581
IL36701407184713
:61:1407180718CR450000,00N195NONREF
:86:IL36701407184302 FDRLR52014071800031798
CASH FDRLR52014071800031798
ABHINAV ENTERPRISE
SENDER IFSCFDRL0001492
IL36701407184302
:61:1407180718CR650000,00N195NONREF
:86:IL36701407183976 UCBAR32014071800058993
CASH UCBAR32014071800058993
GAYLORD SHOE AND CHAPPAL
SENDER IFSCUCBA0000048
IL36701407183976
:61:1407180718CR700000,00N195NONREF
:86:IL36701407183860 SBINR52014071801134507
CASH SBINR52014071801134507
FOOTWEAR HOUSE
RTGS TGH CHQ NO 172867
SENDER IFSCSBIN0008602
IL36701407183860
:61:1407180718CR250000,00N195NONREF
:86:IL36701407183487 SBINR52014071801131379
CASH SBINR52014071801131379
PRATAP AGENCY PROP MRS SUNITA KUMRA
SENDER IFSCSBIN0014152
IL36701407183487
:61:1407180718CR254740,00N195NONREF
:86:IL36701407182511 HDFCR52014071851915942
CASH HDFCR52014071851915942
HEPHZIBAH AGENCIES
SENDER IFSCHDFC0001498
IL36701407182511
:61:1407180718CR398000,00N195NONREF
:86:IL36701407182496 BARBR52014071800726312
CASH BARBR52014071800726312
RAZA FOOT WEAR
SENDER IFSCBARB0BASTIX
IL36701407182496
:61:1407180718CR300000,00N195NONREF
:86:IL36701407182349 KKBKR52014071800664337
CASH KKBKR52014071800664337
M M DISTRIBUTORS
PAYMENT
SENDER IFSCKKBK0000958
IL36701407182349
:61:1407180718CR61136,00N169NONREF
:86:IN3670140718C504 IOBAN14199026875
IN3670140718C504 IOBAN14199026875
M S CHINNS TRADERS
:61:1407180718CR79995,00N169NONREF
:86:IN3670140718C142 SBIN414199219784
IN3670140718C142 SBIN414199219784
FRONTIER TRADING COMPANY
:61:1407180718CR100000,00N169NONREF
:86:IN3670140718B731 SBIN414199200112
IN3670140718B731 SBIN414199200112
SHRI AMBEY TRADERS
:61:1407180718CR125000,00N169NONREF
:86:IN3670140718B521 N199140025581074
IN3670140718B521 N199140025581074
SHYAM BROTHERS
:61:1407180718CR68000,00N169NONREF
:86:IN3670140718A144 1205061871400003
IN3670140718A144 1205061871400003
POPULAR TRADERS PROP PISHORI LAL SETHI
:61:1407180718CR41000,00N169NONREF
:86:IN3670140718A044 P14071849681718
IN3670140718A044 P14071849681718
AKSHAY FOOTWEARS
:61:1407180718CR50000,00N169NONREF
:86:IN3670140718A099 BARBH14199284604
IN3670140718A099 BARBH14199284604
STAR ENTERPRISE
:61:1407180718CR100000,00N169NONREF
:86:IN3670140718A002 SAA21370357
IN3670140718A002 SAA21370357
JAI OMKAR ENTERPRISES
:61:1407180718CR120000,00N169NONREF
:86:IN36701407189725 UTBIN14199269504
IN36701407189725 UTBIN14199269504
SANTI STORES
:61:1407180718CR100000,00N169NONREF
:86:IN36701407189538 SBIN414199107266
IN36701407189538 SBIN414199107266
VINAYAK TRADING
:61:1407180718CR100000,00N169NONREF
:86:IN36701407189842 SAA3564919
IN36701407189842 SAA3564919
SKY STYLE MARKETING PROP.ABHISHEK S
:61:1407180718CR120000,00N169NONREF
:86:IN36701407189384 MAHBH14199609866
IN36701407189384 MAHBH14199609866
ROYAL FOOT WEAR
:62F:D140718INR1697499,29
:64:C140718INR59273846,71
-}{5:{CHK:CHECKSUM DISABLED}{MAC:MACCING DISABLED}}

SAP REPLAY
Regarding the incidence itself, kindly consider that The 86-record
limitation is not a bug of the program, but the standard design.
The error is coded as FV147, when the Note to Payee in Record 86
exceeds 65 characters in Program RFEKA400.
You will need to contact your Bank in order to obtain a correct file:
I have attached some documentation on this message that will allow your
bank to create it.
Otherwise, you may use the following user-exit (SAP NOTE 494777):CMOD
Enhancement Exit Name FEB00004 > EXIT_RFEKA400_001.
This User Exit is called in RFEKA400 in the line: PERFORM
PROCESS_RAW_DATA TABLES SWIFT. In Include ZXF01U06, you have
the option to process the raw data.
Hope this information is useful to you.

Not able insert ,query data from forms

hi,
I am not able to insert data or query data from forms(10g devsuite).getting error frm-40505,frm 40508 .i am able to insert and select record from sql plus.the block ihave created is control block .it is connected to the table using the properties.
should i do anything to insert record.please help

the block ihave created is control block .it is connected to the table using the properties.A Control Block, by definition, is a non-database block. This means the block is not directly connected to a table so you have to manually display data in the block and any DML you want to perform on data in this block you must do manually as well.
There are four database objects you can base your database block on; 1) a Table, 2) a View, 3) From Clause Query (basically an In-line View), and 4) a database stored procedure. I recommend you use one of these four methods rather than manually display your data.
Craig...

Is there a way to consolidate calculations used in SQL Query Data Sets?

I am building SQL Query Data Sets against multiple DB Views which all have different date formats. I have the date parameter working well, but want to consolidate the changes that I have to do to it especially for the quarter. For example the SQL against a monthly view would use "where year_month > to_char(:ST_DATE, 'YYYY-MM')" which is not too hard, but to make that work for the quarterly view I need several concats and a decode to get a "> '2012-Q2'". I would like not to have to do this within every where clause. I had put this into a global element hoping to use that in a filter for the data set, but the filter does not have access to global elements only parameters.
Is there any way to refer to a calculated global element from the data set to do this? I am using Layout Templates, so even if I wanted to I could not do the condition within the template.
     Thanks,
     Rick

Change the following line to include the red coloured parts
<div class="MasterColumn" spry:repeat="ds4" spry:setrow="ds4" spry:hover="MasterColumnHover" spry:select="MasterColumnSelected">
<span>{Dsp_#}</span><span>{Dsp_WkDay}</span><span>{Dsp_Event}</span>
</div>
The add the following style rule to your document:
.MasterColumn span {
    display: inline-block;
I hope this helps.
Ben

How can I query data from XML file stored as a CLOB ?

Hi folks,
please see below sample of XML file, which is stored in "os_import_docs", column "document" as CLOB.
I would like to query this XML file using some SQL select.
How can I query data form below XML?
<?xml version="1.0" encoding="UTF-8"?>
<etd>
<header>
    <AR>000000000</AR>
    <AW>0</AW>
    <CT>S</CT>
    <CU>H</CU>
    <CZ>SS48</CZ>
    <BU>4</BU>
    <CH>0032</CH>
    <CK>2012-11-01</CK>
    <CL>21:18</CL>
    <CW>225</CW>
    <CX>0</CX>
    <CF>SS-CZL18</CF>
    <DV>2</DV>
</header>
<account_group id="234">
    <account id="234">
      <invoice id="000742024">
        <da>
          <AR>000742024</AR>
          <AW>0</AW>
          <CT>D</CT>
          <CU>A</CU>
          <CH>0032</CH>
          <BY>31-10-2012</BY>
          <CA>25-10-2012</CA>
          <AB>234</AB>
          <AA>234</AA>
          <BS>88754515</BS>
          <AD>Mike Tyson</AD>
          <AC>Mike Tyson</AC>
          <AZ>CZ6521232465</AZ>
          <AE/>
          <CG>A</CG>
          <AL>A</AL>
          <BZ>.</BZ>
          <AH>Some street</AH>
          <AI/>
          <AF>Some city</AF>
          <AK>Kraj</AK>
          <AG>CZ</AG>
          <AJ>885 21</AJ>
          <CR>21-11-2012</CR>
          <AY>602718709</AY>
          <AV>800184965</AV>
          <AP/>
          <AO/>
          <AQ/>
          <AN/>
        </da>
        <da>
          <AR>000742024</AR>
          <AW>0</AW>
          <CT>D</CT>
          <CU>A</CU>
          <CH>0032</CH>
          <BY>31-10-2012</BY>
          <CA>25-10-2012</CA>
          <AB>234</AB>
          <AA>234</AA>
          <BS>88754515</BS>
          <AD>Mike Tyson</AD>
          <AC>Mike Tyson</AC>
          <AZ>CZ6521232465</AZ>
          <AE/>
          <CG>A</CG>
          <AL>L</AL>
          <BZ>Mike Tyson</BZ>
          <AH>Some street</AH>
          <AI/>
          <AF>Some city</AF>
          <AK>Kraj</AK>
          <AG>CZ</AG>
          <AJ>885 21</AJ>
          <CR>21-11-2012</CR>
          <AY/>
          <AV>800184965</AV>
          <AP/>
          <AO/>
          <AQ/>
          <AN/>
        </da>
        <detaildc CH="0032" AB="234" BS="11888954" BB="32" BA="CZ" AT="" CI="7077329000002340342" AU="" DU="1Z48395" CB="CZK">
          <dc>
            <AW>0</AW>
            <CT>D</CT>
            <CU>C</CU>
            <BY>31-10-2012</BY>
            <CA>25-10-2012</CA>
            <CV>8151</CV>
            <BT>12111</BT>
            <CJ>1</CJ>
            <AM>0</AM>
            <DR>PC</DR>
            <DS/>
            <DO>25-10-2012</DO>
            <DQ>18:42</DQ>
            <CE>1</CE>
            <BH>8151</BH>
            <CY>8151 SHELL MALKOVICE P</CY>
            <DP>049336</DP>
            <DT/>
            <BQ/>
            <BR>500000</BR>
            <CN>30</CN>
            <CM>030</CM>
            <BO>160,00</BO>
            <BF>38,900</BF>
            <BC>6224,00</BC>
            <BI>32,417</BI>
            <CD>B</CD>
            <BG>0,600</BG>
            <BK>31,817</BK>
            <BJ>0,000</BJ>
            <DI>8</DI>
            <BP>20,00%</BP>
            <CC>CZK</CC>
            <BM>5090,67</BM>
            <BN>1018,13</BN>
            <BL>6108,80</BL>
            <BD>5090,67</BD>
            <BE>1018,13</BE>
            <DW>6108,80</DW>
            <CO>Nafta</CO>
          </dc>
        </detaildc>
        <dt>
          <AR>000742024</AR>
          <AW>0</AW>
          <CT>D</CT>
          <CU>T</CU>
          <CH>0032</CH>
          <BY>31-10-2012</BY>
          <CA>25-10-2012</CA>
          <AB>234</AB>
          <AA>234</AA>
          <BS>11888954</BS>
          <BB/>
          <BA>CZ</BA>
          <DG>1</DG>
          <CN>30</CN>
          <CM>030</CM>
          <DF>160,00</DF>
          <DH>litr</DH>
          <DJ>20,00%</DJ>
          <DD>5090,67</DD>
          <DE>1018,13</DE>
          <DC>6108,80</DC>
          <DB>CZK</DB>
          <DA>P</DA>
          <AX/>
          <CQ/>
          <CP/>
        </dt>
        <dt>
          <AR>000742024</AR>
          <AW>0</AW>
          <CT>D</CT>
          <CU>T</CU>
          <CH>0032</CH>
          <BY>31-10-2012</BY>
          <CA>25-10-2012</CA>
          <AB>234</AB>
          <AA>234</AA>
          <BS>11888954</BS>
          <BB/>
          <BA>CZ</BA>
          <DG>2</DG>
          <CN/>
          <CM/>
          <DF>160,00</DF>
          <DH>litr</DH>
          <DJ/>
          <DD>5090,67</DD>
          <DE>1018,13</DE>
          <DC>6108,80</DC>
          <DB>CZK</DB>
          <DA/>
          <AX/>
          <CQ/>
          <CP/>
        </dt>
        <dt>
          <AR>000742024</AR>
          <AW>0</AW>
          <CT>D</CT>
          <CU>T</CU>
          <CH>0032</CH>
          <BY>31-10-2012</BY>
          <CA>25-10-2012</CA>
          <AB>234</AB>
          <AA>234</AA>
          <BS>11888954</BS>
          <BB/>
          <BA>CZ</BA>
          <DG>19</DG>
          <CN/>
          <CM/>
          <DF/>
          <DH/>
          <DJ/>
          <DD>5090,67</DD>
          <DE>1018,13</DE>
          <DC>6108,80</DC>
          <DB>CZK</DB>
          <DA/>
          <AX/>
          <CQ/>
          <CP/>
        </dt>
        <dt>
          <AR>000742024</AR>
          <AW>0</AW>
          <CT>D</CT>
          <CU>T</CU>
          <CH>0032</CH>
          <BY>31-10-2012</BY>
          <CA>25-10-2012</CA>
          <AB>234</AB>
          <AA>234</AA>
          <BS>11888954</BS>
          <BB/>
          <BA>CZ</BA>
          <DG>8</DG>
          <CN/>
          <CM/>
          <DF/>
          <DH/>
          <DJ/>
          <DD>5090,67</DD>
          <DE>1018,13</DE>
          <DC>6108,80</DC>
          <DB>CZK</DB>
          <DA/>
          <AX/>
          <CQ/>
          <CP/>
        </dt>
      </invoice>
    </account>
</account_group>
<footer>
    <AR>999999999</AR>
    <AW>0</AW>
    <CT>S</CT>
    <CU>T</CU>
    <CZ>SS48</CZ>
    <BU>4</BU>
    <CH>0032</CH>
    <CK>2012-11-01</CK>
    <CL>23:04</CL>
    <CW>225</CW>
    <BX>1</BX>
    <CS>7</CS>
    <BW>0000000000000610880</BW>
</footer>
</etd>sample - not working:
    select x.*
    from os_import_docs d
         ,XMLTABLE('/etd/header'
                    PASSING httpuritype(d.document).getXML()
                    COLUMNS
                       response_status varchar2(50) PATH 'AR'
                    ) x
   where d.object_id = 2587058
     and rownum = 1;
ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: 6196, maximum: 4000)Many thanks,
Tomas

Hello,
many thanks for the reply. Your examples are very usefull for me.
To answer your questions.
An XML structure:
/etd
    /header - repeat in each row in output
    /account_group/account
        /invoice
            /da - repeat for each details under "selected "invoice
            /detaildc/dc - the lowest level
            /detaildn/dn - the lowest level
            /dt - repeat for each details under "selected "invoice
    /footer - repeat in each row in outputI would like to to have a 1 row for each "record" in /detaildc section and include related nodes at higher levels.
Please see below XML file, which is simplified file of example in first post, but includes a complete xml structure which needs to be queried in db.
<?xml version="1.0" encoding="UTF-8"?>
<etd>
<header>
    <AR>000000000</AR>
    <CK>2012-10-31</CK>
    <CF>SS-CZL19</CF>
</header>
<account_group id="234">
    <account id="234">
      <invoice id="EI08P4000">
        <da>
          <AR>EI08P4000</AR>
          <AD>Mickey Mouse</AD>
        </da>
        <detaildc DU="1Z56655" CB="EUR">
          <dc>
            <DO>16-10-2012</DO>
            <CY>ASFINAG POST_MAUT</CY>
            <BM>1940,60</BM>
            <CO>Dalnicni znamka</CO>
          </dc>
        </detaildc>
        <detaildc DU="2Z55050" CB="EUR">
          <dc>
            <DO>17-10-2012</DO>
            <CY>ASFINAG POST_MAUT</CY>
            <BM>1328,10</BM>
            <CO>Dalnicni znamka</CO>
          </dc>
        </detaildc>
        <detaildc DU="2Z90001" CB="EUR">
          <dc>
            <DO>27-10-2012</DO>
            <CY>ASFINAG POST_MAUT</CY>
            <BM>185,10</BM>
            <CO>Poplatek</CO>
          </dc>
        </detaildc>
        <dt>
          <AR>EI08P4000</AR>
          <DG>8</DG>
        </dt>
      </invoice>
    </account>
    <account id="234">
      <invoice id="EI13T7777">
        <da>
          <AR>EI13T7777</AR>
          <AD>Mickey Mouse</AD>
        </da>
        <detaildc DU="1Z48302" CB="EUR">
          <dc>
            <DO>26-10-2012</DO>
            <CY>SANEF 07706 A 07704</CY>
            <BM>232,10</BM>
            <CO>Dalnicni poplatek</CO>
          </dc>
        </detaildc>
        <detaildc DU="1Z48302" CB="EUR">
          <dc>
            <DO>20-10-2012</DO>
            <CY>TEST A 07704</CY>
            <BM>30,10</BM>
            <CO>Poplatek</CO>
          </dc>
        </detaildc>
        <dt>
          <AR>EI13T7777</AR>
          <DG>8</DG>
        </dt>
      </invoice>
    </account>
    <account id="234">
      <invoice id="EI327744">
        <da>
          <AR>EI327744</AR>
          <AD>Mickey Mouse</AD>
        </da>
        <detaildn CI="707732 00000234" >
          <dn>
            <BY>30-10-2012</BY>
            <BM>8,10</BM>
          </dn>
        </detaildn>
        <detaildn CI="707732 00000234" >
          <dn>
            <BY>30-10-2012</BY>
            <BM>399,50</BM>
          </dn>
        </detaildn>
        <dt>
          <AR>EI327744</AR>
        </dt>
      </invoice>
    </account>
    <account id="234">
      <invoice id="EI349515">
        <da>
          <AR>EI349515</AR>
          <AD>Mickey Mouse</AD>
        </da>
        <detaildc DU="1Z56514" CB="EUR">
          <dc>
            <DO>29-10-2012</DO>
            <CY>ALLAMI AUTOPALYAKEZE</CY>
            <BM>1240,60</BM>
            <CO>Dalnicni znamka</CO>
          </dc>
        </detaildc>
        <detaildc DU="1Z56515" CB="EUR">
          <dc>
            <DO>19-10-2012</DO>
            <CY>ASFINAG POST_MAUT</CY>
            <BM>7428,10</BM>
            <CO>Dalnicni znamka</CO>
          </dc>
        </detaildc>
        <detaildc DU="1Z56515" CB="EUR">
          <dc>
            <DO>12-10-2012</DO>
            <CY>UK</CY>
            <BM>954,10</BM>
            <CO>Poplatek</CO>
          </dc>
        </detaildc>
        <dt>
          <AR>EI349515</AR>
          <DG>8</DG>
        </dt>
      </invoice>
    </account>
</account_group>
<footer>
    <CZ>SS47</CZ>
    <BU>4</BU>
    <CH>0032</CH>
    <CK>2012-10-31</CK>
    <CL>01:25</CL>
</footer>
</etd>Expected output
AR     CK     CF             AR4             AD             DU     CB     DO             CY                     BM      CO                AR5             DG     CI             BY               BM6     CZ     BU       CH       CK7    CL
0     41213     SS-CZL19     EI08P4000     Mickey Mouse     1Z56655     EUR     16-10-2012     ASFINAG POST_MAUT     1940,60     Dalnicni znamka        EI08P4000     8                                    SS47     4     32     41213     01:25
0     41213     SS-CZL19     EI08P4000     Mickey Mouse     2Z55050     EUR     17-10-2012     ASFINAG POST_MAUT     1328,10     Dalnicni znamka        EI08P4000     8                                    SS47     4     32     41213     01:25
0     41213     SS-CZL19     EI08P4000     Mickey Mouse     2Z90001     EUR     27-10-2012     ASFINAG POST_MAUT      185,10     Poplatek        EI08P4000     8                                    SS47     4     32     41213     01:25
0     41213     SS-CZL19     EI13T7777     Mickey Mouse     1Z48302     EUR     26-10-2012     SANEF 07706 A 07704      232,10     Dalnicni poplatek EI13T7777     8                                    SS47     4     32     41213     01:25
0     41213     SS-CZL19     EI13T7777     Mickey Mouse     1Z48302     EUR     20-10-2012     TEST A 07704               30,10     Poplatek        EI13T7777     8                                    SS47     4     32     41213     01:25
0     41213     SS-CZL19     EI327744     Mickey Mouse                                                                      EI327744          707732 00000234     30-10-2012     8,10     SS47     4     32     41213     01:25
0     41213     SS-CZL19     EI327744     Mickey Mouse                                                                      EI327744          707732 00000234     30-10-2012     399,50     SS47     4     32     41213     01:25
0     41213     SS-CZL19     EI349515     Mickey Mouse     1Z56514     EUR     29-10-2012     ALLAMI AUTOPALYAKEZE     1240,60     Dalnicni znamka        EI349515     8                                    SS47     4     32     41213     01:25
0     41213     SS-CZL19     EI349515     Mickey Mouse     1Z56515     EUR     19-10-2012     ASFINAG POST_MAUT     7428,10     Dalnicni znamka        EI349515     8                                    SS47     4     32     41213     01:25
0     41213     SS-CZL19     EI349515     Mickey Mouse     1Z56515     EUR     12-10-2012     UK                      954,10     Poplatek        EI349515     8                                    SS47     4     32     41213     01:25

Use JDBC to query data for JSP Report

Hi all,
I met a trouble when use JDBC to query data,
it can show data in report builder, but get error when call from url for exxample: http://localhost:8889/reports/TestJDBCReport.jsp
found error message:
javax.servlet.jsp.JspException: rwlib-1: REP-4100: Failed to execute data source. REP-0069: Internal error JDBCPDS-62000:Invalid sign-on parameter P_JDBCPDS
javax.servlet.jsp.JspException: rwlib-1: REP-4100: Failed to execute data source.
REP-0069: Internal error
JDBCPDS-62000:Invalid sign-on parameter P_JDBCPDS
anyone know pls help me
Many thanks

As a general rule, it's a good idea to separate the
presentation (JSP and HTML) from the business rules
(database access). I know you didn't do that on the
AS/400, you had display files and business logic in
the same program (at least, we certainly do in ours),
but it's a good policy to follow in the web world.
That means, don't put your database access code in
the JSP. Other than that, it depends on the data.
If you have simple data (e.g. customer's name and
d address) then a Java bean would suffice. If you
have complex data (e.g. customer's payment history)
then a bean still might suffice. You would use an
"include" if you had some data (static or dynamic)
that you wanted to appear in several different pages
in the same form.Thanks, I figured putting the code in the JSP was not the best way, but I wasn't sure about the other options.

Query data from MS SQL db through Oracle ? By using JAVA ?

Hi folks,
I would like to sync our one table in oracle db with table in different system, stored in MS SQL database.
What would be the easiest option for connection from Oracle to MS SQL db to be able to query data from MS SQL through some Oracle package?
If possible, I would like to keep all "tricky steps" within Oracle database. I heard about option with Java, but so far we have no experience with java in Oracle.
Our database: Oracle 11g Database Standard Edition One
Many thanks,
Tomas

C:\Users\tomeo>dg4pwd HELIOS
ORACLE Gateway Password Utility
Constructing password file for Gateway SID HELIOS
For user account SYSTEM
OPW-00001: Unable to open password-file (RC=0)
C:\Users\tomeo>

Trying to query data from a view - ORA-01882 and ORA-02063 Errors

Hey there,
I tried to query data from a view that was provided by a colleague. This view works fine and gives correct data using PL/SQL Developer or SQLPLUS, but in SQL Developer, I get the following error:
ORA-01882: Time zone region not found
ORA-02063: preceding line from SYSTOOLS
01882.00000 - "timezone region %s not found"
* Cause: Specified reason name was not found
* Action: Please contact Oracle Customer Support
Vendor Code 1882
Where comes this error message from?! SYSTOOLS is the database link.
Can't see an obvious reason for this error.
OS is Windows 2000 SP4, SQL Developer is v1.1.1.25 BUILD MAIN-25.14
Regards,
Thomas

From Oracle Messages 'Cause and Action'
http://www.oracle.com/technology/products/designer/supporting_doc/des9i_90210/cmnhlp72/messages/ora_messages.htm
ORA-01882, 00000, "timezone region %s not found"
Cause: The specified region name was not found.
Action: Please contact Oracle Customer Support.
Maybe invalid region in NLS_LANG?
"select * from v$nls_parameters"
Starting this script in all developer program and compared result...

The data type of InfoObject 0ORGUNIT is incompatible with field 0ORGUNIT

I am trying to create a DataSource in BW to load the organizational hierarchy from HR R/3 to BW. I get the message "The data type of InfoObject 0ORGUNIT is incompatible with field 0ORGUNIT,"
Our BW version is 3.5; the version of HR R/3 is SAP ECC 6.0.
I'm not sure what this message means but if I continue to click OK, I get transfer structures for the org attributes and hierarchies but not the text. The key to the text is 60 characters. Shouldn't the key be the org unit, which is in format NUMC 8?
I was able to create this DataSource last summer, when HR was in a different version (4.6?) with no issues. Does anybody have any idea what's wrong and what I can do about it?
Thanks!

Would be nice if you could share the resolution they found,
since that might help other people as well.
For instance, me.... as we face exactly the same problem at the moment !!
Ch

With clause in SQL query data model

Hello!
isn't it possible to use the with clause in sql query data models?
for example following query:
WITH
a_test as (
select dummy from dual
select *
from a_test
brings up a "XML Parsing Error: no element found"-error...
BR Paul

I tried a slightly different query (see below) and the query worked fine and retrieved data.. I did not get any errors.
WITH
a_test as (
select 'dummy' from dual
select *
from a_test
This works as well.. retrieving the value of the parameter
WITH
a_test as (
select :Test_ID from dual
select *
from a_test
thanks,
BIPuser

Query: Data length of InfoObjects

Similar Messages

Maybe you are looking for