Subpartition Template COMPRESS NOCOMPRESS parameter

Hi ,
I'm trying to create a table with subpartitions by list already partitioned by list,
I want to configure that some of my subpartitions are compressed and the rest nocompressed,
but I couldn't find how to specify it,
I could specify if the partition at all is compressed or not but not a subpartition level,
Thanks in advance

Hi,
I'm afraid it's not possible to specify this at the subpartition level at the moment.
I have logged an enhancement request on this.
Thanks for reporting this issue,
David

Similar Messages

Modify SUBPARTITION TEMPLATE

Is it possible to change the SUBPARTITION TEMPLATE of the table which has got the data.
I want to add one more value
to the subpartiion template.
SUBPARTITION TEMPLATE
(SUBPARTITION PRD VALUES ('303', '660', '148', '150') TABLESPACE TEST,
   SUBPARTITION PRD1 VALUES ('238', '76') TABLESPACE TEST,
complete Table script .
CREATE TABLE SYSADM.TEST1
BUSINESS_UNIT       VARCHAR2(5 BYTE)          NOT NULL,
FI_INSTRUMENT_ID    VARCHAR2(20 BYTE)         NOT NULL,
FI_IBALTYPE_CD      VARCHAR2(10 BYTE)         NOT NULL,
ASOF_DT             DATE,
ASOF_STATUS         VARCHAR2(2 BYTE)          NOT NULL,
FI_BALANCE_AMT      NUMBER(18,3)              NOT NULL,
FI_BALANCE_BCE_AMT NUMBER(18,3)              NOT NULL,
FI_ACCRINT_AMT      NUMBER(18,3)              NOT NULL,
FI_ACCRINT_BCE_AMT NUMBER(18,3)              NOT NULL,T
CURRENCY_CD         VARCHAR2(3 BYTE)          NOT NULL,
BASE_CURRENCY       VARCHAR2(3 BYTE)          NOT NULL,
FI_LST_PAYMNT_DT    DATE,
PROCESS_INSTANCE    NUMBER(10)                NOT NULL
TABLESPACE TEST
LOGGING
PARTITION BY RANGE (AS_DT)
SUBPARTITION BY LIST (BUSINESS_UNIT)
SUBPARTITION TEMPLATE
(SUBPARTITION PRD VALUES ('303', '660', '148', '150') TABLESPACE TEST,
   SUBPARTITION PRD1 VALUES ('238', '76') TABLESPACE TEST,
PARTITION JUN_2011 VALUES LESS THAN (TO_DATE(' 2011-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    NOLOGGING
    NOCOMPRESS
    TABLESPACE TEST
( SUBPARTITION JUN_2011_PRD VALUES ('303', '660', '148', '150')    TABLESPACE TEST,
    SUBPARTITION JUN_2011_PRD1 VALUES ('238', '76')    TABLESPACE TEST
PARTITION JULY_2011 VALUES LESS THAN (TO_DATE(' 2011-08-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    NOLOGGING
    NOCOMPRESS
    TABLESPACE TEST
( SUBPARTITION JULY_2011_PRD VALUES ('303', '660', '148', '150')    TABLESPACE TEST,
    SUBPARTITION JULY_2011_PRD1 VALUES ('238', '76')    TABLESPACE TEST,
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;

Please do not multi-post.
https://community.oracle.com/thread/2617016
https://community.oracle.com/thread/2617018
https://community.oracle.com/thread/2617024

SUBPARTITION template

Is it possible to modify the subpartition template of the table which has got data.
I want to add one more value to SUBPARTITION of the template.
SUBPARTITION TEMPLATE
(SUBPARTITION PRD VALUES ('303', '660', '148', '150') TABLESPACE TEST,
   SUBPARTITION PRD1 VALUES ('238', '76') TABLESPACE TEST,
CREATE TABLE SYSADM.TEST1
BUSINESS_UNIT       VARCHAR2(5 BYTE)          NOT NULL,
FI_INSTRUMENT_ID    VARCHAR2(20 BYTE)         NOT NULL,
FI_IBALTYPE_CD      VARCHAR2(10 BYTE)         NOT NULL,
ASOF_DT             DATE,
ASOF_STATUS         VARCHAR2(2 BYTE)          NOT NULL,
FI_BALANCE_AMT      NUMBER(18,3)              NOT NULL,
FI_BALANCE_BCE_AMT NUMBER(18,3)              NOT NULL,
FI_ACCRINT_AMT      NUMBER(18,3)              NOT NULL,
FI_ACCRINT_BCE_AMT NUMBER(18,3)              NOT NULL,T
CURRENCY_CD         VARCHAR2(3 BYTE)          NOT NULL,
BASE_CURRENCY       VARCHAR2(3 BYTE)          NOT NULL,
FI_LST_PAYMNT_DT    DATE,
PROCESS_INSTANCE    NUMBER(10)                NOT NULL
TABLESPACE TEST
LOGGING
PARTITION BY RANGE (AS_DT)
SUBPARTITION BY LIST (BUSINESS_UNIT)
SUBPARTITION TEMPLATE
(SUBPARTITION PRD VALUES ('303', '660', '148', '150') TABLESPACE TEST,
   SUBPARTITION PRD1 VALUES ('238', '76') TABLESPACE TEST,
PARTITION JUN_2011 VALUES LESS THAN (TO_DATE(' 2011-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    NOLOGGING
    NOCOMPRESS
    TABLESPACE TEST
( SUBPARTITION JUN_2011_PRD VALUES ('303', '660', '148', '150')    TABLESPACE TEST,
    SUBPARTITION JUN_2011_PRD1 VALUES ('238', '76')    TABLESPACE TEST
PARTITION JULY_2011 VALUES LESS THAN (TO_DATE(' 2011-08-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    NOLOGGING
    NOCOMPRESS
    TABLESPACE TEST
( SUBPARTITION JULY_2011_PRD VALUES ('303', '660', '148', '150')    TABLESPACE TEST,
    SUBPARTITION JULY_2011_PRD1 VALUES ('238', '76')    TABLESPACE TEST,
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;

Please do not multi-post.
https://community.oracle.com/thread/2617016
https://community.oracle.com/thread/2617018
https://community.oracle.com/thread/2617024

SUBPARTITION TEMPLATE modify

Is it possible to modify the existing SUBPARTITION TEMPLATE. Table has got data.
I want to add one more value to the SUBPARTITION in the template.
SUBPARTITION TEMPLATE
(SUBPARTITION PRD VALUES ('303', '660', '148', '150') TABLESPACE TEST,
   SUBPARTITION PRD1 VALUES ('238', '76') TABLESPACE TEST,
table script.
CREATE TABLE SYSADM.TEST1
BUSINESS_UNIT       VARCHAR2(5 BYTE)          NOT NULL,
FI_INSTRUMENT_ID    VARCHAR2(20 BYTE)         NOT NULL,
FI_IBALTYPE_CD      VARCHAR2(10 BYTE)         NOT NULL,
ASOF_DT             DATE,
ASOF_STATUS         VARCHAR2(2 BYTE)          NOT NULL,
FI_BALANCE_AMT      NUMBER(18,3)              NOT NULL,
FI_BALANCE_BCE_AMT NUMBER(18,3)              NOT NULL,
FI_ACCRINT_AMT      NUMBER(18,3)              NOT NULL,
FI_ACCRINT_BCE_AMT NUMBER(18,3)              NOT NULL,T
CURRENCY_CD         VARCHAR2(3 BYTE)          NOT NULL,
BASE_CURRENCY       VARCHAR2(3 BYTE)          NOT NULL,
FI_LST_PAYMNT_DT    DATE,
PROCESS_INSTANCE    NUMBER(10)                NOT NULL
TABLESPACE TEST
LOGGING
PARTITION BY RANGE (AS_DT)
SUBPARTITION BY LIST (BUSINESS_UNIT)
SUBPARTITION TEMPLATE
(SUBPARTITION PRD VALUES ('303', '660', '148', '150') TABLESPACE TEST,
   SUBPARTITION PRD1 VALUES ('238', '76') TABLESPACE TEST,
PARTITION JUN_2011 VALUES LESS THAN (TO_DATE(' 2011-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    NOLOGGING
    NOCOMPRESS
    TABLESPACE TEST
( SUBPARTITION JUN_2011_PRD VALUES ('303', '660', '148', '150')    TABLESPACE TEST,
    SUBPARTITION JUN_2011_PRD1 VALUES ('238', '76')    TABLESPACE TEST
PARTITION JULY_2011 VALUES LESS THAN (TO_DATE(' 2011-08-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    NOLOGGING
    NOCOMPRESS
    TABLESPACE TEST
( SUBPARTITION JULY_2011_PRD VALUES ('303', '660', '148', '150')    TABLESPACE TEST,
    SUBPARTITION JULY_2011_PRD1 VALUES ('238', '76')    TABLESPACE TEST,
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;

Please do not multi-post.
https://community.oracle.com/thread/2617016
https://community.oracle.com/thread/2617018
https://community.oracle.com/thread/2617024

Subpartition templates and DBMS_Metadata.Get_DDL

Does anyone know of a way to get DBMS_Metadata.Get_DDL to specify a subpartition template clause instead of spitting out a specification for every subpartition? I'm finding a 6,000 line create table statement to be a little unwieldy ...
This is 10.2.0.4

Does anyone know of a way to get DBMS_Metadata.Get_DDL to specify a subpartition template clause instead of spitting out a specification for every subpartition? I'm finding a 6,000 line create table statement to be a little unwieldy ...
This is 10.2.0.4

Template depends on parameter

Hi!
I have one input parameter p_template_name and few rtf templates.
Is it possible to make that template depends on parameter?
(if :p_template_name=1 then use template1.rtf
if :p_template_name=2 then use template2.rtf)
How can l do this?
Thanks!

Ops...
This looks nice, but when i whrte row <?import:file:///d:/temp/tctemplates.rtf?> into my rtf template as in article,
Publisher gives me error: "The report cannot be rendered because of an error".
What's wrong?

What is compress=y parameter in exp?

HI all,
Can anybody throw light on compress=y parameter.Does it really compresses the backup?

CONSISTENT
Default: n
Specifies whether or not Export uses the SET TRANSACTION READ ONLY statement to ensure that the data seen by Export is consistent to a single point in time and does not change during the execution of the exp command. You should specify CONSISTENT=y when you anticipate that other applications will be updating the target data after an export has started.
If you use CONSISTENT=n, each table is usually exported in a single transaction. However, if a table contains nested tables, the outer table and each inner table are exported as separate transactions. If a table is partitioned, each partition is exported as a separate transaction.
Therefore, if nested tables and partitioned tables are being updated by other applications, the data that is exported could be inconsistent. To minimize this possibility, export those tables at a time when updates are not being done.
Table 1-2 shows a sequence of events by two users: user1 exports partitions in a table and user2 updates data in that table.
Table 1-2 Sequence of Events During Updates by Two Users
TIme Sequence User1 User2
1
Begins export of TAB:P1
No activity
2
No activity
Updates TAB:P2
Updates TAB:P1
Commits transaction
3
Ends export of TAB:P1
No activity
4
Exports TAB:P2
No activity
If the export uses CONSISTENT=y, none of the updates by user2 are written to the export file.
If the export uses CONSISTENT=n, the updates to TAB:P1 are not written to the export file. However, the updates to TAB:P2 are written to the export file because the update transaction is committed before the export of TAB:P2 begins. As a result, the user2 transaction is only partially recorded in the export file, making it inconsistent.
If you use CONSISTENT=y and the volume of updates is large, the rollback segment usage will be large. In addition, the export of each table will be slower because the rollback segment must be scanned for uncommitted transactions.
Keep in mind the following points about using CONSISTENT=y:
CONSISTENT=y is unsupported for exports that are performed when you are connected as user SYS or you are using AS SYSDBA, or both.
Export of certain metadata may require the use of the SYS schema within recursive SQL. In such situations, the use of CONSISTENT=y will be ignored. Oracle Corporation recommends that you avoid making metadata changes during an export process in which CONSISTENT=y is selected.
To minimize the time and space required for such exports, you should export tables that need to remain consistent separately from those that do not.
For example, export the emp and dept tables together in a consistent export, and then export the remainder of the database in a second pass.
A "snapshot too old" error occurs when rollback space is used up, and space taken up by committed transactions is reused for new transactions. Reusing space in the rollback segment allows database integrity to be preserved with minimum space requirements, but it imposes a limit on the amount of time that a read-consistent image can be preserved.
If a committed transaction has been overwritten and the information is needed for a read-consistent view of the database, a "snapshot too old" error results.
To avoid this error, you should minimize the time taken by a read-consistent export. (Do this by restricting the number of objects exported and, if possible, by reducing the database transaction rate.) Also, make the rollback segment as large as possible.
taken from
http://download.oracle.com/docs/cd/B1050101/server.920/a96652/ch01.htm_

COMPRESS=Y parameter in exp comand in signifies that

in oracle,COMPRESS=Y parameter in exp comand in signifies that

Check:
>
COMPRESS
Default: y
Specifies how Export and Import manage the initial extent for table data.
The default, COMPRESS=y, causes Export to flag table data for consolidation into one initial extent upon Import. If extent sizes are large (for example, because of the PCTINCREASE parameter), the allocated space will be larger than the space required to hold the data.
If you specify COMPRESS=n, Export uses the current storage parameters, including the values of initial extent size and next extent size. The values of the parameters may be the values specified in the CREATE TABLE or ALTER TABLE statements or the values modified by the database system. For example, the NEXT extent size value may be modified if the table grows and if the PCTINCREASE parameter is nonzero.
Note:
Although the actual consolidation is performed upon import, you can specify the COMPRESS parameter only when you export, not when you import. The Export utility, not the Import utility, generates the data definitions, including the storage parameter definitions. Therefore, if you specify COMPRESS=y when you export, you can import the data in consolidated form only.
Note:
LOB data is not compressed. For LOB data, values of initial extent size and next extent size at the time of export are used.
>
URL: http://download.oracle.com/docs/cd/B10501_01/server.920/a96652/ch01.htm
Edited by: AP on Dec 13, 2010 6:05 AM

How to add subpartitions to the existing subpartition template

Hi All,
My Question is ,how to add Subpartition to the exiting subpartition template. e
like i have created a table with subpartition template with with 5 subpartitions like
subpartiton one_1 value (121)
subpartition two_2 value(122)
and now i one to add one more subpartitin to the existing subpartition template(Like modify the existing subpartition templete).
subpartition three_3 value(123)
Could any suggest me.
Thanks
Sree

>
My Question is ,how to add Subpartition to the exiting subpartition template.
>
Follow the example in the section for 'Modifying a Subpartition Template' in the VLDB and Partitioning Guide
http://docs.oracle.com/cd/E11882_01/server.112/e25523/part_admin002.htm#i1007904
>
You can modify a subpartition template of a composite partitioned table by replacing it with a new subpartition template. Any subsequent operations that use the subpartition template (such as ADD PARTITION or MERGE PARTITIONS) now use the new subpartition template. Existing subpartitions remain unchanged.
If you modify a subpartition template of an interval-* composite partitioned table, then interval partitions that have not yet been created use the new subpartition template.
Use the ALTER TABLE ... SET SUBPARTITION TEMPLATE statement to specify a new subpartition template. For example:
ALTER TABLE emp_sub_template
SET SUBPARTITION TEMPLATE
(SUBPARTITION e TABLESPACE ts1,
SUBPARTITION f TABLESPACE ts2,
SUBPARTITION g TABLESPACE ts3,
SUBPARTITION h TABLESPACE ts4

COMPRESS/NOCOMPRESS in IMP/EXP

When saving a database from Ora 9.2.0.1.0, EXP adds a NOCOMPRESS option to each table definition. This appears to be an invalid IMP option when importing into Win98 Personal Ora 9.0.1.1.0. Is it possible to overide creation of this flag, or ignore it on import (editing the DMP file seems to be prevented by a hashcode in the header).

Do it again and add IGNORE=y and post the results.
oracle@chopin:~> imp help=y
Import: Release 8.1.7.0.0 - Production on Fri Dec 5 11:29:47 2003
(c) Copyright 2000 Oracle Corporation. All rights reserved.
You can let Import prompt you for parameters by entering the IMP
command followed by your username/password:
Example: IMP SCOTT/TIGER
Or, you can control how Import runs by entering the IMP command followed
by various arguments. To specify parameters, you use keywords:
Format: IMP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
Example: IMP SCOTT/TIGER IGNORE=Y TABLES=(EMP,DEPT) FULL=N
or TABLES=(T1:P1,T1:P2), if T1 is partitioned table
USERID must be the first parameter on the command line.
Keyword Description (Default) Keyword Description (Default)
USERID username/password FULL import entire file (N)
BUFFER size of data buffer FROMUSER list of owner usernames
FILE input files (EXPDAT.DMP) TOUSER list of usernames
SHOW just list file contents (N) TABLES list of table names
IGNORE ignore create errors (N) RECORDLENGTH length of IO record
GRANTS import grants (Y) INCTYPE incremental import type
INDEXES import indexes (Y) COMMIT commit array insert (N)
ROWS import data rows (Y) PARFILE parameter filename
LOG log file of screen output CONSTRAINTS import constraints (Y)
DESTROY overwrite tablespace data file (N)
INDEXFILE write table/index info to specified file
SKIP_UNUSABLE_INDEXES skip maintenance of unusable indexes (N)
ANALYZE execute ANALYZE statements in dump file (Y)
FEEDBACK display progress every x rows(0)
TOID_NOVALIDATE skip validation of specified type ids
FILESIZE maximum size of each dump file
RECALCULATE_STATISTICS recalculate statistics (N)
VOLSIZE number of bytes in file on each volume of a file on tape
The following keywords only apply to transportable tablespaces
TRANSPORT_TABLESPACE import transportable tablespace metadata (N)
TABLESPACES tablespaces to be transported into database
DATAFILES datafiles to be transported into database
TTS_OWNERS users that own data in the transportable tablespace set
Import terminated successfully without warnings.
oracle@chopin:~>
*****************************************************+
When an a dump file is produced with COMPRESS or NOCOMPRESS, it carry special implications hard to change
after the export was made up.
Joel P�rez

Template function default parameter instantiated unnecessary

Hi,
I think the following is valid C++ code. The default parameter of template (member) function should not be instantiated until it is actually required.
Is it a bug of CC?
$ cat enumid.cc
template<class T>
class TClass
public:
void f(int i = T::EnumID);
class Unknown;
class X
public:
TClass<Unknown> m;
$ CC -c enumid.cc
"enumid.cc", line 5: Error: EnumID is not a member of Unknown.
"enumid.cc", line 11: Where: While specializing "TClass<Unknown>".
"enumid.cc", line 11: Where: Specialized in non-template code.
1 Error(s) detected.
$ CC -V
CC: Sun C++ 5.8 2005/10/13
Thanks,
Qingning

You are right. This test case is valid and shows compiler bug
C++ Standard 14.7.1-1
The implicit instantiation of a class template specialization causes the implicit instantiation of the declarations, but not of the definitions or default arguments, of the class member functions, member classes, static data members and member templates; and it causes the implicit instantiation of the definitions of member anonymous unions.
If you have a service contract with Sun, please file a bug report via your service channel. You can be kept informed about progress, and get pre-release versions of the compiler that fix the bug.
If you don't have a service contract with Sun, please file a bug report at bugs.sun.com.
If you prefer not to file the bug report yourself, let me know, and I'll file one for you.

Data Templates by Example - parameter error

Tim, there is an error in the EMPLOYEES.xml data template in your 11/29/06 blog. The Q1 sqlStatement references p_DeptNo but the parameter section defines it as pDeptNo. Of course, the two names should match.
By the way, where can I find documentation on the properties element used in your data template example? I did not find any of these properties described in the current user guides.
Thanks and regards, Rob

The current release 5.6.2 does not supports the properties. These are the part of our comming release 5.6.3 and they are well documented in 5.6.3 User Guide.
Regards
Ashish

Call a web template with default parameter in BEx Web Application D

In BEx Web Application Designer, As in traditional way. Assume that I have a query which have parameters. When I create a web template using this query and excute it. the first page is displayed and I should input the parameters at this page(for example: "Period/Fiscal"). after I input the data and press Enter key. the <b>reporting page</b> is displayed.
And Now I hope I can run the template at another way: the template should <b>direct go to the reporting page</b> with the preset parameters (for example: "Period/Fiscal = 2005.006").
thanks

Hi,
Alternatively you may use command URL, to enforce the variable value during calling up the web template. For example:
http://yourAppServer:yourPort/SAP/BW/BEx?CMD=LDOC&template_id=yourTemplate&var_name_1=myParameterVariable&var_value_ext_1=4711
In the implementation you may create a web template that redirect the URL to above reporting link, so the user will directly see your reporting page.
For detail you may check in the WAD documentation.
Hope this helps.
Message was edited by: Eddo

Report parameter does not show up in rtf template

Hi all
I was able to produce an rtf file based on the XML bellow. I could create the header with the customer name and the invoice list with the totals. However, I already tried by any means to insert the AS_OF_DATE parameter in the rtf template but it never appears. Do I have to put it between a <?for-each?> <?end for-each?>. This must be a simple question but I’m very new to this.
Thanks in advance for any help.
Octavio
<?xml version="1.0"?>

<ARXAGMW>
<LIST_G_SETUP>
<G_SETUP>
<COMPANY_NAME>TUI Portugal, SA.</COMPANY_NAME>
<COAID>101</COAID>
<FUNCTIONAL_CURRENCY>EUR</FUNCTIONAL_CURRENCY>
<IN_SET_OF_BOOKS_ID>50</IN_SET_OF_BOOKS_ID>
<FUNCTIONAL_CURRENCY_PRECI>2</FUNCTIONAL_CURRENCY_PRECI>
<CONVERT_FLAG>Y</CONVERT_FLAG>
<LIST_G_SEL_CREDIT_OPTIONS>
<G_SEL_CREDIT_OPTIONS>
<INCLUDE_CREDIT_HIGH>Y</INCLUDE_CREDIT_HIGH>
<IN_ON_ACCOUNT_LOW>N</IN_ON_ACCOUNT_LOW>
<CREDIT_OPTION_MEANING>Age</CREDIT_OPTION_MEANING>
<LIST_G_SEL_OPTIONS>
<G_SEL_OPTIONS>
<PRINT_ON_ACCOUNT_FLAG></PRINT_ON_ACCOUNT_FLAG>
<SORT_OPTION>C</SORT_OPTION>
<SUMMARY_OPTION>I</SUMMARY_OPTION>
<FORMAT_DETAILED></FORMAT_DETAILED>
<INVOICE_TYPE_PRINT></INVOICE_TYPE_PRINT>
<CUSTOMER_NAME_PRINT></CUSTOMER_NAME_PRINT>
<BALANCE_DUE_PRINT></BALANCE_DUE_PRINT>
<LIST_G_COMPANY_CUST>
</LIST_G_COMPANY_CUST>
<LIST_G_COMPANY_INV>
<G_COMPANY_INV>
<COMPANY_INV>01</COMPANY_INV>
<LIST_G_INV_INV>
<G_INV_INV>
<SORT_FIELD1_INV></SORT_FIELD1_INV>
<INV_TID_INV>*</INV_TID_INV>
<SORT_FIELD2_INV>10FC</SORT_FIELD2_INV>
<LIST_G_CUST_INV>
<G_CUST_INV>
<CUST_NAME_INV>Academia Contemporânea do Espectáculo</CUST_NAME_INV>
<CUST_NO_INV>1011</CUST_NO_INV>
<CUST_ID_INV>*</CUST_ID_INV>
<CUST_STATE_INV></CUST_STATE_INV>
<CUST_CITY_INV>Porto</CUST_CITY_INV>
<CONTACT_SITE_ID_INV>*</CONTACT_SITE_ID_INV>
<LIST_G_SITE_INV>
<G_SITE_INV>
<ADDR_ID_INV>*</ADDR_ID_INV>
<AMT_DUE_REMAINING_INV>*</AMT_DUE_REMAINING_INV>
<LIST_G_1>
<G_1>
<INVNUM>10FC*526</INVNUM>
<CONS_BILLING_NUMBER></CONS_BILLING_NUMBER>
<LIST_G_INVOICE>
<G_INVOICE>
<DUE_DATE_INV>26-OCT-07</DUE_DATE_INV>
<INVOICE_TYPE_INV>10FC</INVOICE_TYPE_INV>
<CLASS_INV>INV</CLASS_INV>
<PAYMENT_SCHED_ID_INV>*</PAYMENT_SCHED_ID_INV>
<DAYS_PAST_DUE2>*</DAYS_PAST_DUE2>
<AMOUNT_ADJUSTED_INV></AMOUNT_ADJUSTED_INV>
<AMOUNT_APPLIED_INV></AMOUNT_APPLIED_INV>
<AMOUNT_CREDITED_INV></AMOUNT_CREDITED_INV>
<GL_DATE_INV>26-SEP-07</GL_DATE_INV>
<DATA_CONVERTED_INV></DATA_CONVERTED_INV>
<PS_EXCHANGE_RATE_INV>1</PS_EXCHANGE_RATE_INV>
<B0_INV>0</B0_INV>
<B1_INV>0</B1_INV>
<B2_INV>0</B2_INV>
<B3_INV>0</B3_INV>
<B4_INV>1</B4_INV>
<B5_INV>0</B5_INV>
<B6_INV>0</B6_INV>
<COMP_AMT_DUE_REM_INV>181.54</COMP_AMT_DUE_REM_INV>
<C_DATA_CONV_FLAG_INV>0</C_DATA_CONV_FLAG_INV>
<C_AMT_DUE_REM_INV>181.54</C_AMT_DUE_REM_INV>
<C_AMT_DUE_REM_INV_DSP> 181.54 </C_AMT_DUE_REM_INV_DSP>
<C_AMOUNT_CH_INV>0</C_AMOUNT_CH_INV>
<C_AMOUNT_CR_INV>0</C_AMOUNT_CR_INV>
<C_AMOUNT_RISK_INV>0</C_AMOUNT_RISK_INV>
<C_AMOUNT_CLAIM_INV>0</C_AMOUNT_CLAIM_INV>
<C_INV_BALANCE>181.54</C_INV_BALANCE>
<C_COMP_BAL_INV>181.54</C_COMP_BAL_INV>
<C_INV_BALANCE_DSP> 181.54 </C_INV_BALANCE_DSP>
<C_INV_B0>0</C_INV_B0>
<C_INV_B0_DSP> </C_INV_B0_DSP>
<C_INV_B1>0</C_INV_B1>
<C_INV_B1_DSP> </C_INV_B1_DSP>
<C_INV_B2>0</C_INV_B2>
<C_INV_B2_DSP> </C_INV_B2_DSP>
<C_INV_B3>0</C_INV_B3>
<C_INV_B3_DSP> </C_INV_B3_DSP>
<C_INV_B4>181.54</C_INV_B4>
<C_INV_B4_DSP> 181.54 </C_INV_B4_DSP>
<C_INV_B5>0</C_INV_B5>
<C_INV_B5_DSP> </C_INV_B5_DSP>
<C_INV_B6>0</C_INV_B6>
<C_INV_B6_DSP> </C_INV_B6_DSP>
</G_INVOICE>
</LIST_G_INVOICE>
<CONS_BILL_DISP>10FC*526</CONS_BILL_DISP>
</G_1>
</LIST_G_1>
<PERCENT_B0_ADDR>0</PERCENT_B0_ADDR>
<PERCENT_B1_ADDR>0</PERCENT_B1_ADDR>
<PERCENT_B2_ADDR>0</PERCENT_B2_ADDR>
<PERCENT_B3_ADDR>0</PERCENT_B3_ADDR>
<PERCENT_B4_ADDR>100</PERCENT_B4_ADDR>
<PERCENT_B5_ADDR>0</PERCENT_B5_ADDR>
<PERCENT_B6_ADDR>0</PERCENT_B6_ADDR>
<SET_PERCENT_ADDR>0</SET_PERCENT_ADDR>
<TOTAL_SITE_AMT>181.54</TOTAL_SITE_AMT>
<TOTAL_SITE_AMT_DSP> 181.54 </TOTAL_SITE_AMT_DSP>
<TOTAL_SITE_B0>0</TOTAL_SITE_B0>
<TOTAL_SITE_B0_DSP> 0.00 </TOTAL_SITE_B0_DSP>
<TOTAL_SITE_B1>0</TOTAL_SITE_B1>
<TOTAL_SITE_B1_DSP> 0.00 </TOTAL_SITE_B1_DSP>
<TOTAL_SITE_B2>0</TOTAL_SITE_B2>
<TOTAL_SITE_B2_DSP> 0.00 </TOTAL_SITE_B2_DSP>
<TOTAL_SITE_B3>0</TOTAL_SITE_B3>
<TOTAL_SITE_B3_DSP> 0.00 </TOTAL_SITE_B3_DSP>
<TOTAL_SITE_B4>181.54</TOTAL_SITE_B4>
<TOTAL_SITE_B4_DSP> 181.54 </TOTAL_SITE_B4_DSP>
<TOTAL_SITE_B5>0</TOTAL_SITE_B5>
<TOTAL_SITE_B5_DSP> 0.00 </TOTAL_SITE_B5_DSP>
<TOTAL_SITE_B6>0</TOTAL_SITE_B6>
<TOTAL_SITE_B6_DSP> 0.00 </TOTAL_SITE_B6_DSP>
<C_SITE_PAYMENTS_DSP> 0.00 </C_SITE_PAYMENTS_DSP>
<C_SITE_PAYMENTS>0</C_SITE_PAYMENTS>
<C_SITE_RISK>0</C_SITE_RISK>
<C_SITE_CREDITS>0</C_SITE_CREDITS>
<C_SITE_CREDITS_DSP> 0.00 </C_SITE_CREDITS_DSP>
<C_SITE_BALANCE>181.54</C_SITE_BALANCE>
<C_SITE_BALANCE_DSP> 181.54 </C_SITE_BALANCE_DSP>
<SEL_CONTACT_INV> </SEL_CONTACT_INV>
<C_CONTACT_NAME_INV></C_CONTACT_NAME_INV>
<C_CONTACT_PHONE_INV></C_CONTACT_PHONE_INV>
<C_CONTACTS_INV></C_CONTACTS_INV>
</G_SITE_INV>
</LIST_G_SITE_INV>
<D_CUST_NAME_INV>Academia Contemporânea do</D_CUST_NAME_INV>
<TOTAL_INV_AMT>181.54</TOTAL_INV_AMT>
<TOTAL_INV_AMT_DSP> 181.54 </TOTAL_INV_AMT_DSP>
<TOTAL_INV_B0>0</TOTAL_INV_B0>
<TOTAL_INV_B0_DSP> 0.00 </TOTAL_INV_B0_DSP>
<TOTAL_INV_B1>0</TOTAL_INV_B1>
<TOTAL_INV_B1_DSP> 0.00 </TOTAL_INV_B1_DSP>
<TOTAL_INV_B2>0</TOTAL_INV_B2>
<TOTAL_INV_B2_DSP> 0.00 </TOTAL_INV_B2_DSP>
<TOTAL_INV_B3>0</TOTAL_INV_B3>
<TOTAL_INV_B3_DSP> 0.00 </TOTAL_INV_B3_DSP>
<TOTAL_INV_B4>181.54</TOTAL_INV_B4>
<TOTAL_INV_B4_DSP> 181.54 </TOTAL_INV_B4_DSP>
<TOTAL_INV_B5>0</TOTAL_INV_B5>
<TOTAL_INV_B5_DSP> 0.00 </TOTAL_INV_B5_DSP>
<TOTAL_INV_B6>0</TOTAL_INV_B6>
<TOTAL_INV_B6_DSP> 0.00 </TOTAL_INV_B6_DSP>
<SUM_INV_BALANCE>181.54</SUM_INV_BALANCE>
<SUM_INV_BALANCE_DSP> 181.54 </SUM_INV_BALANCE_DSP>
<SUM_ONACC_CR_INV>0</SUM_ONACC_CR_INV>
<SUM_ONACC_CR_INV_DSP> 0.00 </SUM_ONACC_CR_INV_DSP>
<ONACC_CONV_CH_INV> </ONACC_CONV_CH_INV>
<ONACC_CONV_CR_INV> </ONACC_CONV_CR_INV>
<ONACC_CONV_RISK_INV></ONACC_CONV_RISK_INV>
<SUM_ONACC_CH_INV>0</SUM_ONACC_CH_INV>
<SUM_ONACC_CH_INV_DSP> 0.00 </SUM_ONACC_CH_INV_DSP>
<SUM_ONACC_RISK_INV>0</SUM_ONACC_RISK_INV>
<SUM_ONACC_RISK_INV_DSP> 0.00 </SUM_ONACC_RISK_INV_DSP>
<SUM_CLAIM_INV>0</SUM_CLAIM_INV>
<SUM_CLAIM_INV_DSP> 0.00 </SUM_CLAIM_INV_DSP>
<SEL_PERCENT_INV>0</SEL_PERCENT_INV>
<PERCENT_B0_INV>0</PERCENT_B0_INV>
<PERCENT_B1_INV>0</PERCENT_B1_INV>
<PERCENT_B2_INV>0</PERCENT_B2_INV>
<PERCENT_B3_INV>0</PERCENT_B3_INV>
<PERCENT_B4_INV>100</PERCENT_B4_INV>
<PERCENT_B5_INV>0</PERCENT_B5_INV>
<PERCENT_B6_INV>0</PERCENT_B6_INV>
</G_CUST_INV>
</LIST_G_CUST_INV>
<C_LABEL2_INV>Total For Type</C_LABEL2_INV>
<C_LABEL3_INV>Type</C_LABEL3_INV>
<FLEX_TYPE_INV>10FC</FLEX_TYPE_INV>
<TOTAL_INV_INV_AMT>181.54</TOTAL_INV_INV_AMT>
<TOTAL_INV_INV_AMT_DSP> 181.54 </TOTAL_INV_INV_AMT_DSP>
<TOTAL_INV_INV_B0>0</TOTAL_INV_INV_B0>
<TOTAL_INV_INV_B0_DSP> 0.00 </TOTAL_INV_INV_B0_DSP>
<TOTAL_INV_INV_B1>0</TOTAL_INV_INV_B1>
<TOTAL_INV_INV_B1_DSP> 0.00 </TOTAL_INV_INV_B1_DSP>
<TOTAL_INV_INV_B2>0</TOTAL_INV_INV_B2>
<TOTAL_INV_INV_B2_DSP> 0.00 </TOTAL_INV_INV_B2_DSP>
<TOTAL_INV_INV_B3>0</TOTAL_INV_INV_B3>
<TOTAL_INV_INV_B3_DSP> 0.00 </TOTAL_INV_INV_B3_DSP>
<TOTAL_INV_INV_B4>181.54</TOTAL_INV_INV_B4>
<TOTAL_INV_INV_B4_DSP> 181.54 </TOTAL_INV_INV_B4_DSP>
<TOTAL_INV_INV_B5>0</TOTAL_INV_INV_B5>
<TOTAL_INV_INV_B5_DSP> 0.00 </TOTAL_INV_INV_B5_DSP>
<TOTAL_INV_INV_B6>0</TOTAL_INV_INV_B6>
<TOTAL_INV_INV_B6_DSP> 0.00 </TOTAL_INV_INV_B6_DSP>
<TOTAL_INV_INV_BALANCE>181.54</TOTAL_INV_INV_BALANCE>
<TOTAL_INV_INV_CREDIT>0</TOTAL_INV_INV_CREDIT>
<TOTAL_INV_INV_RISK>0</TOTAL_INV_INV_RISK>
<TOTAL_INV_INV_CLAIM>0</TOTAL_INV_INV_CLAIM>
<TOTAL_INV_INV_CASH>0</TOTAL_INV_INV_CASH>
<SET_PERCENT_INV_INV>0</SET_PERCENT_INV_INV>
<SUM_PERCENT_B0_INV>0</SUM_PERCENT_B0_INV>
<SUM_PERCENT_B1_INV>0</SUM_PERCENT_B1_INV>
<SUM_PERCENT_B2_INV>0</SUM_PERCENT_B2_INV>
<SUM_PERCENT_B3_INV>0</SUM_PERCENT_B3_INV>
<SUM_PERCENT_B4_INV>100</SUM_PERCENT_B4_INV>
<SUM_PERCENT_B5_INV>0</SUM_PERCENT_B5_INV>
<SUM_PERCENT_B6_INV>0</SUM_PERCENT_B6_INV>
</G_INV_INV>
</LIST_G_INV_INV>
<TOTAL_COMPANY_INV_AMT>181.54</TOTAL_COMPANY_INV_AMT>
<TOTAL_COMPANY_INV_AMT_DSP> 181.54 </TOTAL_COMPANY_INV_AMT_DSP>
<SET_GSUM_INV_AMT> 181.54 </SET_GSUM_INV_AMT>
<SET_GSUM_INV_B0> 0.00 </SET_GSUM_INV_B0>
<SET_GSUM_INV_B1> 0.00 </SET_GSUM_INV_B1>
<SET_GSUM_INV_B2> 0.00 </SET_GSUM_INV_B2>
<SET_GSUM_INV_B3> 0.00 </SET_GSUM_INV_B3>
<SET_GSUM_INV_B4> 181.54 </SET_GSUM_INV_B4>
<SET_GSUM_INV_B5> 0.00 </SET_GSUM_INV_B5>
<SET_GSUM_INV_B6> 0.00 </SET_GSUM_INV_B6>
<SET_PAY_CR_MEMOS_INV> 0.00 </SET_PAY_CR_MEMOS_INV>
<SET_RISK_INV> 0.00 </SET_RISK_INV>
<SET_CLAIM_INV> 0.00 </SET_CLAIM_INV>
<SET_GPERCENT_INV>0</SET_GPERCENT_INV>
<SET_GSUM_INV_BALANCE> 181.54 </SET_GSUM_INV_BALANCE>
</G_COMPANY_INV>
</LIST_G_COMPANY_INV>
<SET_SEL_OPTIONS>1</SET_SEL_OPTIONS>
</G_SEL_OPTIONS>
</LIST_G_SEL_OPTIONS>
<SET_CREDIT_OPTIONS>Age</SET_CREDIT_OPTIONS>
</G_SEL_CREDIT_OPTIONS>
</LIST_G_SEL_CREDIT_OPTIONS>
<CA_FUNCTIONAL_CURRENCY>EUR</CA_FUNCTIONAL_CURRENCY>
<ACCT_BAL_APROMPT>Empresa</ACCT_BAL_APROMPT>
<ACCT_FLEX_BAL_SEG>c.SEGMENT1</ACCT_FLEX_BAL_SEG>
<ACCT_BAL_LPROMPT>Empresa</ACCT_BAL_LPROMPT>
<REPORT_NAME></REPORT_NAME>
<SUB_TITLE>22-FEB-08</SUB_TITLE>
<APP_MAX_ID></APP_MAX_ID>
<ADJ_MAX_ID>74399</ADJ_MAX_ID>
<PS_MAX_ID></PS_MAX_ID>
<SET_UNID_PHRASE>Unidentified Payments</SET_UNID_PHRASE>
<SET_BUCKET_TITLES>1</SET_BUCKET_TITLES>
<SET_FTR_LABEL></SET_FTR_LABEL>
<SET_COLUMNS>1</SET_COLUMNS>
<SET_CURRENCY>EUR</SET_CURRENCY>
<UNID_CH>0</UNID_CH>
</G_SETUP>
</LIST_G_SETUP>
<RP_COMPANY_NAME>TUI Portugal, SA.</RP_COMPANY_NAME>
<RP_REPORT_NAME>Aging - 7 Buckets Report</RP_REPORT_NAME>
<RP_DATA_FOUND></RP_DATA_FOUND>
<RP_SUBTITLE> 22-FEB-08</RP_SUBTITLE>
<AS_OF_DATE>22-FEB-08</AS_OF_DATE>
<UNID_PHRASE>Unidentified Payments</UNID_PHRASE>
<SHORT_UNID_PHRASE>Unidentified Payme</SHORT_UNID_PHRASE>
<TOP0>Não</TOP0>
<TOP1>Até</TOP1>
<TOP3>Até</TOP3>
<TOP2>Até</TOP2>
<TOP4>Até</TOP4>
<TOP5>Mais de</TOP5>
<TOP6>Em</TOP6>
<BOT0>Vencido</BOT0>
<BOT1>30 Dias</BOT1>
<BOT2>60 Dias</BOT2>
<BOT3>90 Dias</BOT3>
<BOT4>180 Dias</BOT4>
<BOT5>180 Dias</BOT5>
<BOT6>Litígio</BOT6>
<BUCKET_LINE_TYPE_0>CURRENT</BUCKET_LINE_TYPE_0>
<BUCKET_LINE_TYPE_1>PAST</BUCKET_LINE_TYPE_1>
<BUCKET_LINE_TYPE_2>PAST</BUCKET_LINE_TYPE_2>
<BUCKET_LINE_TYPE_3>PAST</BUCKET_LINE_TYPE_3>
<BUCKET_LINE_TYPE_4>PAST</BUCKET_LINE_TYPE_4>
<BUCKET_LINE_TYPE_5>PAST</BUCKET_LINE_TYPE_5>
<BUCKET_LINE_TYPE_6>DISPUTE_PENDADJ</BUCKET_LINE_TYPE_6>
<BUCKET_DAYS_FROM_0>-99999999</BUCKET_DAYS_FROM_0>
<BUCKET_DAYS_FROM_1>1</BUCKET_DAYS_FROM_1>
<BUCKET_DAYS_FROM_2>31</BUCKET_DAYS_FROM_2>
<BUCKET_DAYS_FROM_3>61</BUCKET_DAYS_FROM_3>
<BUCKET_DAYS_FROM_4>91</BUCKET_DAYS_FROM_4>
<BUCKET_DAYS_FROM_5>181</BUCKET_DAYS_FROM_5>
<BUCKET_DAYS_FROM_6></BUCKET_DAYS_FROM_6>
<BUCKET_DAYS_TO_0>0</BUCKET_DAYS_TO_0>
<BUCKET_DAYS_TO_1>30</BUCKET_DAYS_TO_1>
<BUCKET_DAYS_TO_2>60</BUCKET_DAYS_TO_2>
<BUCKET_DAYS_TO_3>90</BUCKET_DAYS_TO_3>
<BUCKET_DAYS_TO_4>180</BUCKET_DAYS_TO_4>
<BUCKET_DAYS_TO_5>999999999</BUCKET_DAYS_TO_5>
<BUCKET_DAYS_TO_6></BUCKET_DAYS_TO_6>
<BUCKET_CATEGORY>DISPUTE_PENDADJ</BUCKET_CATEGORY>
<GSUM_CUST_B0></GSUM_CUST_B0>
<GSUM_CUST_B1></GSUM_CUST_B1>
<GSUM_CUST_B2></GSUM_CUST_B2>
<GSUM_CUST_B3></GSUM_CUST_B3>
<GSUM_CUST_B4></GSUM_CUST_B4>
<GSUM_CUST_B5></GSUM_CUST_B5>
<GSUM_CUST_B6></GSUM_CUST_B6>
<GSUM_CUST_PERCENT_B0></GSUM_CUST_PERCENT_B0>
<GSUM_CUST_PERCENT_B1></GSUM_CUST_PERCENT_B1>
<GSUM_CUST_PERCENT_B2></GSUM_CUST_PERCENT_B2>
<GSUM_CUST_PERCENT_B3></GSUM_CUST_PERCENT_B3>
<GSUM_CUST_PERCENT_B4></GSUM_CUST_PERCENT_B4>
<GSUM_CUST_PERCENT_B5></GSUM_CUST_PERCENT_B5>
<GSUM_CUST_PERCENT_B6></GSUM_CUST_PERCENT_B6>
<GSUM_CUST_AMT></GSUM_CUST_AMT>
<GSUM_CUST_BALANCE>0</GSUM_CUST_BALANCE>
<GSUM_ONACC_AMT_CREDIT_CUST>0</GSUM_ONACC_AMT_CREDIT_CUST>
<GSUM_ONACC_AMT_CASH_CUST>0</GSUM_ONACC_AMT_CASH_CUST>
<GSUM_PAY_CR_CUST>0</GSUM_PAY_CR_CUST>
<TEMP_SUM_CUST></TEMP_SUM_CUST>
<GSUM_CUST_B0_DSP></GSUM_CUST_B0_DSP>
<GSUM_CUST_B1_DSP></GSUM_CUST_B1_DSP>
<GSUM_CUST_B2_DSP></GSUM_CUST_B2_DSP>
<GSUM_CUST_B3_DSP></GSUM_CUST_B3_DSP>
<GSUM_CUST_B4_DSP></GSUM_CUST_B4_DSP>
<GSUM_CUST_B5_DSP></GSUM_CUST_B5_DSP>
<GSUM_CUST_B6_DSP></GSUM_CUST_B6_DSP>
<GSUM_CUST_AMT_DSP></GSUM_CUST_AMT_DSP>
<GSUM_CUST_BALANCE_DSP></GSUM_CUST_BALANCE_DSP>
<GSUM_PAY_CR_CUST_DSP></GSUM_PAY_CR_CUST_DSP>
<C_DATA_CONV_GSUM></C_DATA_CONV_GSUM>
<TEMP_ONACC_CR_CUST></TEMP_ONACC_CR_CUST>
<TEMP_ONACC_CH_CUST></TEMP_ONACC_CH_CUST>
<RP_FTR_LBL>Grand Total:</RP_FTR_LBL>
<C_DATA_CONV_GSUM_INV></C_DATA_CONV_GSUM_INV>
<GSUM_INV_B0>0</GSUM_INV_B0>
<GSUM_INV_B1>0</GSUM_INV_B1>
<GSUM_INV_B2>0</GSUM_INV_B2>
<GSUM_INV_B3>0</GSUM_INV_B3>
<GSUM_INV_B4>181.54</GSUM_INV_B4>
<GSUM_INV_B5>0</GSUM_INV_B5>
<GSUM_INV_B6>0</GSUM_INV_B6>
<GSUM_INV_PERCENT_B1>0</GSUM_INV_PERCENT_B1>
<GSUM_INV_PERCENT_B2>0</GSUM_INV_PERCENT_B2>
<GSUM_INV_PERCENT_B0>0</GSUM_INV_PERCENT_B0>
<GSUM_INV_PERCENT_B3>0</GSUM_INV_PERCENT_B3>
<GSUM_INV_PERCENT_B4>100</GSUM_INV_PERCENT_B4>
<GSUM_INV_PERCENT_B5>0</GSUM_INV_PERCENT_B5>
<GSUM_INV_PERCENT_B6>0</GSUM_INV_PERCENT_B6>
<GSUM_INV_AMT>181.54</GSUM_INV_AMT>
<GSUM_INV_BALANCE>181.54</GSUM_INV_BALANCE>
<GSUM_ONACC_AMT_CR_INV>0</GSUM_ONACC_AMT_CR_INV>
<GSUM_ONACC_AMT_CH_INV>0</GSUM_ONACC_AMT_CH_INV>
<GSUM_PAY_CR_INV>0</GSUM_PAY_CR_INV>
<TEMP_SUM_INV>0</TEMP_SUM_INV>
<GSUM_INV_BALANCE_DSP> 181.54 </GSUM_INV_BALANCE_DSP>
<GSUM_PAY_CR_INV_DSP> 0.00 </GSUM_PAY_CR_INV_DSP>
<GSUM_INV_B0_DSP> 0.00 </GSUM_INV_B0_DSP>
<GSUM_INV_B1_DSP> 0.00 </GSUM_INV_B1_DSP>
<GSUM_INV_B2_DSP> 0.00 </GSUM_INV_B2_DSP>
<GSUM_INV_B3_DSP> 0.00 </GSUM_INV_B3_DSP>
<GSUM_INV_B4_DSP> 181.54 </GSUM_INV_B4_DSP>
<GSUM_INV_B5_DSP> 0.00 </GSUM_INV_B5_DSP>
<GSUM_INV_B6_DSP> 0.00 </GSUM_INV_B6_DSP>
<GSUM_INV_AMT_DSP> 181.54 </GSUM_INV_AMT_DSP>
<TEMP_ONACC_CR_INV>0</TEMP_ONACC_CR_INV>
<TEMP_ONACC_CH_INV>0</TEMP_ONACC_CH_INV>
<C_PS_MAX_ID></C_PS_MAX_ID>
<C_ADJ_MAX_ID>74399</C_ADJ_MAX_ID>
<C_APP_MAX_ID></C_APP_MAX_ID>
<C_CONVERT_FLAG>Y</C_CONVERT_FLAG>
<C_CREDIT_OPTION_MEANING>Age</C_CREDIT_OPTION_MEANING>
<C_FUNCTIONAL_CURRENCY>EUR</C_FUNCTIONAL_CURRENCY>
<C_FORMAT_DETAILED></C_FORMAT_DETAILED>
<C_SORT_OPTION>C</C_SORT_OPTION>
<C_SUMMARY_OPTION>I</C_SUMMARY_OPTION>
<REF_CURR_CODE_INV>EUR</REF_CURR_CODE_INV>
<C_CUST_SUM_LBL></C_CUST_SUM_LBL>
<C_ONACC_AMT_CR_CUST></C_ONACC_AMT_CR_CUST>
<C_ONACC_AMT_CH_CUST></C_ONACC_AMT_CH_CUST>
<C_ONACC_AMT_CR_INV>0</C_ONACC_AMT_CR_INV>
<C_ONACC_AMT_CH_INV>0</C_ONACC_AMT_CH_INV>
<C_CREDIT_APPLIED_LATE_CUST></C_CREDIT_APPLIED_LATE_CUST>
<C_UNID_CH></C_UNID_CH>
<C_CREDIT_APPLIED_LATE_INV>0</C_CREDIT_APPLIED_LATE_INV>
<C_UNID_CH_INV>0</C_UNID_CH_INV>
<C_SUMMARY_MEANING>Brief</C_SUMMARY_MEANING>
<C_FORMAT_MEANING>Invoice Summary</C_FORMAT_MEANING>
<SET_MEANINGS></SET_MEANINGS>
<C_INDUSTRY_CODE>C</C_INDUSTRY_CODE>
<C_COMPANY_TITLE></C_COMPANY_TITLE>
<C_BAL_SEGMENT_LPROMPT></C_BAL_SEGMENT_LPROMPT>
<C_PAYMENT_MEANING>Payment</C_PAYMENT_MEANING>
<C_RISK_MEANING>Risk</C_RISK_MEANING>
<C_ONACC_AMT_RISK_INV></C_ONACC_AMT_RISK_INV>
<TEMP_ONACC_RISK_INV></TEMP_ONACC_RISK_INV>
<C_RISK_OPTION_MEANING>Do Not Show</C_RISK_OPTION_MEANING>
<GSUM_ONACC_AMT_RISK_INV>0</GSUM_ONACC_AMT_RISK_INV>
<GSUM_RISK_INV_DSP> 0.00 </GSUM_RISK_INV_DSP>
<GSUM_RISK_CUST_DSP></GSUM_RISK_CUST_DSP>
<GSUM_ONACC_AMT_RISK_CUST>0</GSUM_ONACC_AMT_RISK_CUST>
<CF_PAYMENT_MEANING>Payment</CF_PAYMENT_MEANING>
<CF_RISK_MEANING></CF_RISK_MEANING>
<CF_RISK_OPTION_MEANING></CF_RISK_OPTION_MEANING>
<CF_ACCOUNTING_FLEXFIELD></CF_ACCOUNTING_FLEXFIELD>
<GSUM_CLAIM_CUST_DSP></GSUM_CLAIM_CUST_DSP>
<GSUM_CLAIM_AMT_CUST>0</GSUM_CLAIM_AMT_CUST>
<GSUM_CLAIM_INV_DSP> 0.00 </GSUM_CLAIM_INV_DSP>
<GSUM_CLAIM_AMT_INV>0</GSUM_CLAIM_AMT_INV>
<C_CLAIM_OPTION_MEANING></C_CLAIM_OPTION_MEANING>
</ARXAGMW>

hi Rex,
your requirement is u want to show your report parameter in rtf(template).
create a placeholder column get your parameter in the placeholder column.
and run the report to generate XMl.
use the placeholder column in template to show parameter.
Regards
Rajesh

Template and parameter evaluated many times

Hello,
I defined a template using ui:composition. This template has one parameter which is used about 20 times.
Template :
<ui:composition>
<h:outputText value="#{myParam}" />
</ui:composition>
in the file using the template :
<ui:decorate template="mytemplate.xhtml">
<ui:param name="myParam" value="#{myComponent.myMethod(otherParam)}" />
</ui:decorate>
The problem is that the myComponent.myMethod is called every time that myParam is used in the template. And of course, the call to this component requires time. Why is myParam not evaluated only once when it is passed to the template ? How can I do to achieve this ?
Thanks for your help.

I can't comment on the why, but I can make a suggestion on your last question. Change your myComponent.myMethod(otherParam) code so that the result cached for subsequent calls.

Subpartition Template COMPRESS NOCOMPRESS parameter

Similar Messages

Maybe you are looking for